Related
Not intended to be a general Android vs. iOS debate! Just my experiences (and a couple questions) coming from a 6s to the S7. Before the 6s I had several Android phones, did dozens of ROMs and hundreds of flashes, so I know both platforms very well.
Galaxy S7 Pros:
- Screen is fantastic. About the perfect size for me as well.
- Very fast and fluid. I had a Galaxy S6 last year and it wasn't nearly this fast.
- Always-on screen is cool, though limited.
- Google Now blows away Siri
- Good fingerprint support.
- Great camera.
- Finally back to good third-party keyboards with Android. iOS supports them now but doesn't allow voice recognition other than in stock keyboard. Lame.
Galaxy S7 Cons:
- Battery has so far been unimpressive. I'll give it a few more days.
- No Voice Command over Bluetooth in my new car (2016 Accord EX-L V6). This is close to a deal breaker for me. The iPhone has great Bluetooth support with full voice command of Siri using the Voice button on the steering wheel.
- Also over Bluetooth, can't see the list of tracks in the current playlist, scroll through playlists, etc. iPhone has this.
- No always-on "OK Google" from screen-off. This would help a lot with the above car Voice issue if I could just say "OK Google" and have it wake up. iPhone and other Android phones have this and I'm surprised Samsung didn't also go with that. Big negative.
Really want to like and keep the S7, but the lack of good voice support in the car is a big deal for me. Anyone know of a way to either get always-on "OK Google" or steering wheel controls to support it like they do in iOS? Yes, I can use Android Auto, but I often just want to jump in the car and go rather than plug in.
A
Alpione said:
Not intended to be a general Android vs. iOS debate! Just my experiences (and a couple questions) coming from a 6s to the S7. Before the 6s I had several Android phones, did dozens of ROMs and hundreds of flashes, so I know both platforms very well.
Galaxy S7 Pros:
- Screen is fantastic. About the perfect size for me as well.
- Very fast and fluid. I had a Galaxy S6 last year and it wasn't nearly this fast.
- Always-on screen is cool, though limited.
- Google Now blows away Siri
- Good fingerprint support.
- Great camera.
- Finally back to good third-party keyboards with Android. iOS supports them now but doesn't allow voice recognition other than in stock keyboard. Lame.
Galaxy S7 Cons:
- Battery has so far been unimpressive. I'll give it a few more days.
- No Voice Command over Bluetooth in my new car (2016 Accord EX-L V6). This is close to a deal breaker for me. The iPhone has great Bluetooth support with full voice command of Siri using the Voice button on the steering wheel.
- Also over Bluetooth, can't see the list of tracks in the current playlist, scroll through playlists, etc. iPhone has this.
- No always-on "OK Google" from screen-off. This would help a lot with the above car Voice issue if I could just say "OK Google" and have it wake up. iPhone and other Android phones have this and I'm surprised Samsung didn't also go with that. Big negative.
Really want to like and keep the S7, but the lack of good voice support in the car is a big deal for me. Anyone know of a way to either get always-on "OK Google" or steering wheel controls to support it like they do in iOS? Yes, I can use Android Auto, but I often just want to jump in the car and go rather than plug in.
A
Click to expand...
Click to collapse
For the "Ok Google" Open the Google App, hit the 3 lines top left corner and select settings
There is a setting for active on any screen (but that is only when the screen is on/charging)
Also in the settings there is a hands free option, make sure you have bluetooth turned on for OK Google
Also, have you downloaded Android Auto and connected the phone via USB? I think that is the preferred method
nest75068 said:
For the "Ok Google" Open the Google App, hit the 3 lines top left corner and select settings
There is a setting for active on any screen (but that is only when the screen is on/charging)
Also in the settings there is a hands free option, make sure you have bluetooth turned on for OK Google
Also, have you downloaded Android Auto and connected the phone via USB? I think that is the preferred method
Click to expand...
Click to collapse
Thanks. Yes, done all of that and I should have mentioned Android Auto. It's not bad and does most of the stuff I want. It just requires plugging in the phone over USB versus doing everything hands/cable free. Not a huge deal, but I drive a lot and it's great with the iPhone to never have the thing out of my pocket. Today while driving to lunch I had the S7 in my pocket and just hit the button there, said OK Google and it generally worked. through my jeans I guess that's one way to work around.
A
Yeah definitely give the battery a few more cycles
make sure u turn off all the extra crapp running the back ground, the battery life for me is double of the iphone 6 but i have gps turned off at all times. also QC2.0 should be the deal breaker. it nice plugging in for a few minutes and getting a couple hours
I would add some cons:
- can't send/recieve MMS without cellurar data connection (using my S7 in polish network Play). It's very annoying especially when connected to home WiFi network. To send/recieve MMS You must: disable WiFi, enable cellular data, send/recieve MMS, disable cellular data, enable WiFi... flagship phone ffs...
- ultra weak vibration (even when strongest mode set in options)
- can't hide unnecessary apps, for example: full version of Poweramp has unlocker as separate application. In my HTC M8 I can just hide unlocker app. In S7 this is impossible.
Im considering to sell this phone.
I'm also having some heating/throttling issues. Just web-surfing for 30 minutes causes heat towards the top of the phone and the CPUs clearly throttle, making Chrome lag like crazy. I rebooted and let it cool down and it got fast again, but after a while it heated/throttled again.
Not impressive. I'm 50/50 on keeping it. Shouldn't have to deal with this kind of thing.
A
dzieciaq said:
I would add some cons:
- can't send/recieve MMS without cellurar data connection (using my S7 in polish network Play). It's very annoying especially when connected to home WiFi network. To send/recieve MMS You must: disable WiFi, enable cellular data, send/recieve MMS, disable cellular data, enable WiFi... flagship phone ffs...
- ultra weak vibration (even when strongest mode set in options)
- can't hide unnecessary apps, for example: full version of Poweramp has unlocker as separate application. In my HTC M8 I can just hide unlocker app. In S7 this is impossible.
Im considering to sell this phone.
Click to expand...
Click to collapse
weak vibration? yours may me faulty. the vibrate motor on this thing is too strong for me lol its much more than my note 4
Sent from my Samsung Galaxy S7 using Tapatalk
jayochs said:
weak vibration? yours may me faulty. the vibrate motor on this thing is too strong for me lol its much more than my note 4
Sent from my Samsung Galaxy S7 using Tapatalk
Click to expand...
Click to collapse
Nope, compared to HTC M8 it's very weak, of course all sliders in vibration menu are set to max. Yesterday checked 2 models in two different stores (Euro and Media Markt) and they also had very weak vibration.
dzieciaq said:
Nope, compared to HTC M8 it's very weak, of course all sliders in vibration menu are set to max. Yesterday checked 2 models in two different stores (Euro and Media Markt) and they also had very weak vibration.
Click to expand...
Click to collapse
Weird....I've found it to be pretty impressive vibration. Had to turn it down for my alarm in the morning, as it was vibrating itself off the stand I had it on.
Of course, it could be that I don't really rely on vibrate all that much...I actually have it almost off for calling...just use it in the morning on my alarm, as sometimes the sounds just aren't enough.
dzieciaq said:
Nope, compared to HTC M8 it's very weak, of course all sliders in vibration menu are set to max. Yesterday checked 2 models in two different stores (Euro and Media Markt) and they also had very weak vibration.
Click to expand...
Click to collapse
weird. yeah, i feel mine is super hard of a vibration. I don't use vibrate much myself though so I guess I don't really know.
Sent from my Samsung Galaxy S7 using Tapatalk
dzieciaq said:
- can't hide unnecessary apps, for example: full version of Poweramp has unlocker as separate application. In my HTC M8 I can just hide unlocker app. In S7 this is impossible.
Click to expand...
Click to collapse
Not impossible at all. Use a different launcher.
and I'm with the others. The vibration is pretty strong.
wifesabitch said:
Not impossible at all. Use a different launcher.
and I'm with the others. The vibration is pretty strong.
Click to expand...
Click to collapse
You don't even have to switch launchers. If you launch the unlocker it will say "thanks for buying" and give you the option to hide the unlocker from your launcher.
---------- Post added at 12:18 PM ---------- Previous post was at 12:11 PM ----------
dzieciaq said:
I would add some cons:
- can't send/recieve MMS without cellurar data connection (using my S7 in polish network Play). It's very annoying especially when connected to home WiFi network. To send/recieve MMS You must: disable WiFi, enable cellular data, send/recieve MMS, disable cellular data, enable WiFi... flagship phone ffs...
- ultra weak vibration (even when strongest mode set in options)
- can't hide unnecessary apps, for example: full version of Poweramp has unlocker as separate application. In my HTC M8 I can just hide unlocker app. In S7 this is impossible.
Im considering to sell this phone.
Click to expand...
Click to collapse
Why are you disabling your data connection when connected to WiFi? You're just making your life more complicated. Leave data on while on WiFi and the phone will automatically switch to data when it can't do something over WiFi (your texts).
My vibration is strong like others have mentioned.
PowerAmp unlocker hides itself once you launch it 1 time.
love it
Too much vodka there in polland i guess? He doesn't feel the vibration anymore :laugh: (no pun intended)
I really love the s7 even the battery life, but then I must say that I came from a Huawei Ascend P7 so it's quite the improvement. Amazing camera and everytime I unlock my screen I fall in love with the colors :good::good:
Hi everyone! Just got the Edge after switching to Verizon (damn Note not available thanks to recall) and I have a problem with Google Now not hearing any voice commands. If I have a bluetooth headset on it works fine, but using the phone's mic somehow doesn't work. I tested S Voice and that responds fine, but when I switch to Google it doesn't work at all. Already tried uninstalling updates and switching off permissions.
Thanks!
You know the screen has to be on, or the device has to be charging for Google Now voice commands to work right? Other than that, I don't know what the problem could be.
Yes, but even from inside the app, if I click on the mic, and hear the confirmation sound, the phone won't hear anything I say unless I deep throat the phone, and even then it misinterprets my commands. S Voice and the voice recorder app work fine, but just not Google Now.
alcaponed said:
Yes, but even from inside the app, if I click on the mic, and hear the confirmation sound, the phone won't hear anything I say unless I deep throat the phone, and even then it misinterprets my commands. S Voice and the voice recorder app work fine, but just not Google Now.
Click to expand...
Click to collapse
Is your offline language set to the language you speak? Verify that and also try to retrain the recognition. If that doesn't work I know that the S6 had problems with Google now working when S Voice wasn't disabled.
Sorry for the delay but yes it is. I have since gotten rid of the S7 Edge in order to get the Note...lucky me...but thanks for your help!
alcaponed said:
Sorry for the delay but yes it is. I have since gotten rid of the S7 Edge in order to get the Note...lucky me...but thanks for your help!
Click to expand...
Click to collapse
A little off topic, but you kept your note?
I had this issue when I had Cortana installed with Hey Cortana turned on. No chance you have that on is there?
Didn't see you had gotten rid of it....best of luck.
Outbreak444 said:
A little off topic, but you kept your note?
Click to expand...
Click to collapse
I'm waiting for the damn Pixel to ship. Just annoying because so many Note users have to buy different phones so it's getting backed up.
My S8 makes a Noise/Sound when I unlock the device with the face. Or when I have opened the camera and close it. It comes from the sensor area. Its like a " tick " but very quit. You must listen very close to hear it. Is it normal ? Or has someone the same issue ?
That's not an 'issue'.
Unlocking sound is an option in sound .
Matter of fact it's called screen unlocking sounds
Sent from my T-Mobile Galaxy S8+ using Tapatalk
howdyace said:
That's not an 'issue'.
Unlocking sound is an option in sound
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
It comes not from the speakers it comes from the device.
Yup, lock screen sound.
Rockatansky_ said:
It comes not from the speakers it comes from the device.
Click to expand...
Click to collapse
Settings -> Sounds and vibration
Toggle "Screen lock sounds" and see if it's still there.
They clearly do not understand what you are talking about. I also have that soft click noise after I unlock the device. May be from the camera, but not quite sure. I do not have face recognition on, so I doubt it is the camera. I have yet to discover what it is. If you found out, please let me know. And no guys, it is NOT the default unlock sound.....
Not sure why but after the last system update the phone will only come out of black screen sleep mode if I use the fingerprint sensor when theres an incoming call.
Any Ideas ?
This happened to me today too.
Hello, me too! Oreo Beta 2
Anyone ?
going_home said:
Anyone ?
Click to expand...
Click to collapse
Not me, I've never experienced this issue since I got the phone from N then updated to OB2, and now OB3.
Sounds like the proximity sensor may have an issue.
Do you have a screen protector or case?
I don't have that issue with a screen protector and Tudia case and B3.
It's a bug in the latest Google Dialer app. I fixed it be deinstalling the new version/updates then clearing cache and data in the dialer app. It's affecting the Pixel2 XL running 8.1 also. Fixed my issue and I won't let it install the newer dialer version from the play store
In Beta 3, I haven't experienced that problem. I did heavily on 7.1.1
Just got another update and still having black screen on incoming calls....
I'm about ready to ditch this phone and get a Pixel 2 XL.
I read where Essential is skipping the 8.0 update because of instability and going straight to 8.1.
going_home said:
Just got another update and still having black screen on incoming calls....
I'm about ready to ditch this phone and get a Pixel 2 XL.
I read where Essential is skipping the 8.0 update because of instability and going straight to 8.1.
Click to expand...
Click to collapse
happened to me last week too.. it only happened after I locked the phone, 5-10 minutes later incoming call or when unlocking the phone the phone shows back screen only for a few seconds then it went back to normal.
the problem went away after I turned off the bluetooth radio.
I've been having this issue for a while now and just today I figured out the cause. At least the cause of my specific issue. I came here to see if anyone else is having similar issues so I'll explain exactly where I'm at.
If a Bluetooth headset is connected to my phone, when a call comes in the screen stays black and I can't see who's calling. If I turn off, or disconnect the BT device, when a call comes in the screen lights up with caller ID like normal. This also affects the missed call notification that happens after a missed call. With a BT device connected, the missed call notification will not show until I wake the phone with the power button, though the notification LED will light.
I'm on stock 7.1.1 and I verified that this is also an identical issue with two other phones which were not on a stock ROM, though I can't remember what they were running. This started happening to me before the NMK24B update. I remember because I was hoping that the update would fix it. I believe it started with NMJ88C because I got my phone on NMJ32F, it updated to NMJ51B shortly after and it was fine in the beginning months.
DrvLikHell said:
I've been having this issue for a while now and just today I figured out the cause. At least the cause of my specific issue. I came here to see if anyone else is having similar issues so I'll explain exactly where I'm at.
If a Bluetooth headset is connected to my phone, when a call comes in the screen stays black and I can't see who's calling. If I turn off, or disconnect the BT device, when a call comes in the screen lights up with caller ID like normal. This also affects the missed call notification that happens after a missed call. With a BT device connected, the missed call notification will not show until I wake the phone with the power button, though the notification LED will light.
I'm on stock 7.1.1 and I verified that this is also an identical issue with two other phones which were not on a stock ROM, though I can't remember what they were running. This started happening to me before the NMK24B update. I remember because I was hoping that the update would fix it. I believe it started with NMJ88C because I got my phone on NMJ32F, it updated to NMJ51B shortly after and it was fine in the beginning months.
Click to expand...
Click to collapse
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Jank4AU said:
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Click to expand...
Click to collapse
I tried two other dialers and it didn't make a difference on my phone. Drupe did work to make the screen show who's calling again, but wow, Drupe has too much.... just, everything. All I want in a dialer is basic functions in a standard format. Drupe is like a carnival of a dialer. I'll keep trying dialers though, since that one did work, maybe another one will too. Thanks for the suggestion.
Yeah, if you just take the Drupe dialer phone icon and put that on your home screen, whenever you select it you'll go right to the normal looking dialer. :good:You may want to try ExDialer. That used to be one I'd use a lot.
Jank4AU said:
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Click to expand...
Click to collapse
Before using Drupe...
There should be a warning that goes out to all your contacts saying "I'm about to completely betray you and share EVERYTHING about you online with a company I know nothing about... Please enjoy these spam calls on me"
Sent from my PH-1 using Tapatalk
rignfool said:
Before using Drupe...
There should be a warning that goes out to all your contacts saying "I'm about to completely betray you and share EVERYTHING about you online with a company I know nothing about... Please enjoy these spam calls on me"
Click to expand...
Click to collapse
10 million downloads...good enough for me. I've used it for a long time and it's been better for me than the stock dialer. Just my opinion, no one has to use it but it sure beats a black screen when the phone rings.
I have the same problem on the pixel 2 xl. And so do lots of others. I uninstalled the phone update from the play store, and turned off auto update. So far so good. And I am on 8.1 But we will see. And it only happens when I'm on Bluetooth. Unfortunately I use it all the time for work
Sent from my Pixel 2 XL using Tapatalk
I read about some people being able to fix it by uninstalling dialer updates. Unfortunately, the Essential doesn't have any to uninstall. I'm working around it by using Drupe as my default dialer, but setting the stock dialer as the default app for dialing, if that makes any sense (When an event pops up that requires the dialer, it asks which dialer to use, I selected the stock dialer and told it always use that.) This way incoming calls trigger Drupe, which acts the way it's supposed to on Bluetooth, but I can still use the stock app for making calls and missed calls and such.
bricky23 said:
I have the same problem on the pixel 2 xl. And so do lots of others. I uninstalled the phone update from the play store, and turned off auto update. So far so good. And I am on 8.1 But we will see. And it only happens when I'm on Bluetooth. Unfortunately I use it all the time for work
Click to expand...
Click to collapse
Yeah, I'm thinking there's a Bluetooth issue (yeah,I know, news flash). But it's been widely reported that some folks are having trouble connecting to their cars Bluetooth. I use a Bluetooth adapter in my car and wireless headphones in the office. No real big issues connecting, but it can be finicky. However, once an event triggers Bluetooth, like streaming a song with Google Play to the adapter, my phones volume buttons become unresponsive. I can only change volume by going into the settings menu or from the Bluetooth device. Sucks. Waiting for the 8.1 beta to do a total clean install. Just bought the device used from Swappa and it came with beta 3 installed, not 100% sure the steps it took getting here. I guess what I'm asking is, does anyone else experience issues with their volume buttons not working occasionally?
Jank4AU said:
Yeah, I'm thinking there's a Bluetooth issue (yeah,I know, news flash). But it's been widely reported that some folks are having trouble connecting to their cars Bluetooth. I use a Bluetooth adapter in my car and wireless headphones in the office. No real big issues connecting, but it can be finicky. However, once an event triggers Bluetooth, like streaming a song with Google Play to the adapter, my phones volume buttons become unresponsive. I can only change volume by going into the settings menu or from the Bluetooth device. Sucks. Waiting for the 8.1 beta to do a total clean install. Just bought the device used from Swappa and it came with beta 3 installed, not 100% sure the steps it took getting here. I guess what I'm asking is, does anyone else experience issues with their volume buttons not working occasionally?
Click to expand...
Click to collapse
My volume buttons always work fine, BT or otherwise. Stock 7.1.1. Your issue could very well be related to OB3. I had a little bit of an issue connecting/reconnecting to some BT devices at first, but not lately, so it must have been fixed in the last few patches.
I have Mi Airdots S and to summon the Google Assistant, you double-tap the button on either headphone . If the screen is on and unlocked, everything works as expected. But if the screen is off and you want to talk to the Assistant while the phone is in your pocket (which would be a normal scenario when using headphones), all I get is a notification on the lock screen saying that you can use the Assistant with headphones while the phone is locked.
I've tried using a different pair of wireless headphones, and the result is the same. What I notice is that the microphone activates, but the phone does not receive its input. Which leads me to conclude it is not the fault of the Airdots, but this phone or MIUI 12. I've tried playing with all possible GA and phone settings, but to no avail.
Your help is appreciated.
https://support.google.com/assistant/thread/286844?hl=en
The last post
Sent from my Mi Note 10 using XDA Labs
Thanks for the answer, but that is not the issue I'm having. I don't need to wake up the phone by saying "ok google", I just want it to respond properly when I call for the Assistant using the double-tap on the headphone button.
Any other ideas?