Related
I'm confused by this new feature that is being touted. I keep seeing conflicting reports:
Some claim that the "Okay Google" command works from the home screen (meaning the device must be on and unlocked)
Some claim that the "Okay Google" command works exactly how it does on the Moto X (meaning the phrase will wake the phone from sleep)
It would seem like a pretty useless feature to have if it only activates once the device is unlocked. And even if it is the other way, will this work on any Kit Kat device or just ones with a special low powered processor?
kyleallen5000 said:
I'm confused by this new feature that is being touted. I keep seeing conflicting reports:
Some claim that the "Okay Google" command works from the home screen (meaning the device must be on and unlocked)
Some claim that the "Okay Google" command works exactly how it does on the Moto X (meaning the phrase will wake the phone from sleep)
It would seem like a pretty useless feature to have if it only activates once the device is unlocked. And even if it is the other way, will this work on any Kit Kat device or just ones with a special low powered processor?
Click to expand...
Click to collapse
From what I understood,it only works when screen is on.
If it was meant to work exactly how it does on the Moto X, there would have been an altered version of the Snapdragon ( e.g. X8 ) because otherwise this is a major battery consumer. The always-on ability seems to be reserved for the Moto.
I think currently only N5 supports this and N4 support will come later, but I am not sure about that.
https://plus.google.com/106533248943352121512/posts/GANAWjSGM32
Looks like yes.
Eluveitie said:
From what I understood,it only works when screen is on.
If it was meant to work exactly how it does on the Moto X, there would have been an altered version of the Snapdragon ( e.g. X8 ) because otherwise this is a major battery consumer. The always-on ability seems to be reserved for the Moto.
I think currently only N5 supports this and N4 support will come later, but I am not sure about that.
Click to expand...
Click to collapse
i was under the impression that the snapdragon 800 chip was designed specifically with an 'always listening' feature. that one of the 4 cores is kept at low power specifically for this always listening feature
yahoowizard said:
https://plus.google.com/106533248943352121512/posts/GANAWjSGM32
Looks like yes.
Click to expand...
Click to collapse
--ish. The screen has to be on in order for it to listen. Without security (a PIN or Pattern, etc) it'll listen at the lock screen.
I use the slide unlock screen, so yes for me. No for those who use a pattern or PIN lock.
On one of the KitKat (official) pages it mentions that voice actions work on the homescreen and when in the Google Now app. The google search widget says in it "Say 'OK Google" and so does the Google Now app. So I am fairly sure it won't be included.
That being said, the CPU should be able to use the always listening feature. I really hope some devs are out their porting it right now. I have a $5 google play voucher from eating a kitkat to spend which I am willing to buy a donation app that provides always listening functionality.
This is exactly how it works on the G2. Screen has to be on for it to work.
Enddo said:
i was under the impression that the snapdragon 800 chip was designed specifically with an 'always listening' feature. that one of the 4 cores is kept at low power specifically for this always listening feature
Click to expand...
Click to collapse
Yea, but theres no low power dedicated core for OFF screen listening.
Eluveitie said:
Yea, but theres no low power dedicated core for OFF screen listening.
Click to expand...
Click to collapse
you are right. so far it seems to only be on the home screen and in the google now page
Actually, the Snapdragon 800 processor does support 'always listening' and has a dedicated chip for it. And according to this post by "The Verge" after an interview with one of Google execs, it looks like the 'always listening' feature will be added with future updates, or that's at least the impression he gives off when reading this article. Looks as if updates will be coming mid-Novemeber.
Ugh, I can't post the link to the page because I don't have '10 posts" yet.
after typing theverge.com/ -- follow it by typing in this:
2013/10/31/5051458/android-kit-kat-bring-big-updates-to-google-now-and-speech-recognition
I am pleasantly surprised to find out that Ok Google will wake up and unlock the Pixel 2. Is this one of the few phones now that this is possible? I know from an awake phone it's possible but it works on my Pixel 2 unawake ?
ghettopops said:
I am pleasantly surprised to find out that Ok Google will wake up and unlock the Pixel 2. Is this one of the few phones now that this is possible? I know from an awake phone it's possible but it works on my Pixel 2 unawake ?
Click to expand...
Click to collapse
I haven't understood the second question.
But you can wake up and unlock your phone in many old devices like the original Moto X (2013) the Nexus 5X and 6P (2015) and some Samsung Galaxies and Motorolas. It doesn't matter for how many hours they were resting with the screen off.
Not all the manufacturers enable an always listening feature in their phones hardware and also have a Google app with the OK Google always on option.
(Example: my ex Z5 Compact didn't have this feature).
So phones must have activated the Snapdragon voice activation and prepare the Google app to enable this feature or something like that.
Battery life is practically not impacted by this feature in general. But of course each feature pulls some of it.
Active Display (Ambient Display Always On) and Always Listening (Say "Ok Google" at any time) are essentials features to me that work when the phone is resting in deep sleep.
And they both appeared with the original Moto X by Motorola/Google as far as I remember. (Best ergonomic phone ever as well)
Sent from my Pixel 2
I thought the Nexus had to be charging for that. I know the Moto did.
In Nexus 5 this was not supported. But in 5X and 6P it was working and perfectly. I've been using this function since the 5X. I always use this for create reminders or set timers for the pasta cooking time etc.
I don't know about the Nexus 6
Now in the Pixel 2 I'm suffering sometimes a PIN request I don't know why. Might be for more security.
Sent from my Pixel 2
when you say it will "wake up and unlock" you're referring to the phone being locked with pin / pattern / etc. and the screen is off, correct?
yes, most phones that i'm aware of will not do this unless the phone is plugged in or the screen is on.
however, some other phones do have other options e.g. the samsung phones can "wake up and unlock" to s-voice or bixby and once unlocked you can say "ok google".
Since I got the phone, while in pocket, I reject/answer 80% of the calls. I was under the effect of "yay nexus is back, google finally gave us a cheapster" so didn't really got bothered. But days are passing by and it's getting quite annoying, so to the point, could anybody tell me why this phone wakes up the screen on incoming calls when the proximity sensor is covered (ie. in pocket?) (if it's "normal" to do so, then why?). Proxi switch is fine, it triggers during calls and shows activity on sensor testing apps and whatnot. Default calls screen and whatsapp incoming calls, (heck I can unlock the phone with the fingerprint reader in my pocket without taking it out, now explain that.) ... Cherry on top the "slide to answer" thingy is vertical, so yeah there is the problem (while sliding it out from the pocket, it answers or rejects the call). I'm considering throwing it out lol it's so annoying lately. Android 9 was the same? (I had 3 android one phones to fill the superexpensive 3 generation pixel gap) Was I living under a rock? Can anyone try it? Thanks for the helpful inputs in advance.
strapabiro said:
Since I got the phone, while in pocket, I reject/answer 80% of the calls. I was under the effect of "yay nexus is back, google finally gave us a cheapster" so didn't really got bothered. But days are passing by and it's getting quite annoying, so to the point, could anybody tell me why this phone wakes up the screen on incoming calls when the proximity sensor is covered (ie. in pocket?) (if it's "normal" to do so, then why?). Proxi switch is fine, it triggers during calls and shows activity on sensor testing apps and whatnot. Default calls screen and whatsapp incoming calls, (heck I can unlock the phone with the fingerprint reader in my pocket without taking it out, now explain that.) ... Cherry on top the "slide to answer" thingy is vertical, so yeah there is the problem (while sliding it out from the pocket, it answers or rejects the call). I'm considering throwing it out lol it's so annoying lately. Android 9 was the same? (I had 3 android one phones to fill the superexpensive 3 generation pixel gap) Was I living under a rock? Can anyone try it? Thanks for the helpful inputs in advance.
Click to expand...
Click to collapse
There is no pocket mode on stock firmware. If you'd like to add one you can use Edxposed and the dark tricks module.
Sent from my Google Pixel 3a XL using XDA Labs
As hard as I'm trying, I start to see it's nearly impossible to be completely satisfied with the stock android experience. I gave up rooting, flashing, modding long time ago. Ain't got time for that. This leaves one choice, a sad but with time will get used to it.
strapabiro said:
As hard as I'm trying, I start to see it's nearly impossible to be completely satisfied with the stock android experience. I gave up rooting, flashing, modding long time ago. Ain't got time for that. This leaves one choice, a sad but with time will get used to it.
Click to expand...
Click to collapse
Do all 3a do this? I am looking into buying one but don't want to deal with something like that. This is exactly the reason I decided not to buy Galaxy S10e - just try to Google "S10 proximity sensor". It was never officially acknowledged/fixed by Samsung and over the time people just seem to "get used to it" and stop talking about it.
I don't know mate, that's why I asked others to try it please, it's really getting on my nerves and funny thing is, these kind of problems are a hit or miss on warranty claims ... doesn't even worth to try ... and I don't want to take this to reddit either because it'll only get downvoted to a lower than hell level by biased fanboys not to mention the google product forums with the "platinum product experts" and their generic "try this and try that" answers.
So yeah I'm angry.
strapabiro said:
I don't know mate, that's why I asked others to try it please, it's really getting on my nerves and funny thing is, these kind of problems are a hit or miss on warranty claims ... doesn't even worth to try ... and I don't want to take this to reddit either because it'll only get downvoted to a lower than hell level by biased fanboys not to mention the google product forums with the "platinum product experts" and their generic "try this and try that" answers.
So yeah I'm angry.
Click to expand...
Click to collapse
I never had issues, but probably I don't understand the issue yet, so I have a question: how do you know screen is waking up in pocket? For sure it's waking up if you move the device, i.e. take is off the table or turn it around. Are you sure screen switches on in the pocket and not while you are taking it out?
AndDiSa said:
I never had issues, but probably I don't understand the issue yet, so I have a question: how do you know screen is waking up in pocket? For sure it's waking up if you move the device, i.e. take is off the table or turn it around. Are you sure screen switches on in the pocket and not while you are taking it out?
Click to expand...
Click to collapse
You can test by trying to unlock the device while covering the proximity sensor.
Without any mods it'll unlock.
But like that's the main benefit to a Google phone running stock firmware. It's a perfect base for mods.
Sent from my Google Pixel 3a XL using XDA Labs
Skittles9823 said:
You can test by trying to unlock the device while covering the proximity sensor.
Without any mods it'll unlock.
But like that's the main benefit to a Google phone running stock firmware. It's a perfect base for mods.
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
This ... Or cover like 80% of the screen, leave only a small bar uncovered on the lower part of the phone (usbc port side) and ask someone to call you. You'll see on the remaining uncovered part that the screen woke up which is hilarious. Honestly at this point I don't understand how a feature like this can be overlooked by r&d.
Sadly modding is no option for me, for safety and other reasons.
There is another thread about this in the 3a xl section, hope it doesn't count as duplicate.
strapabiro said:
Sadly modding is no option for me, for safety and other reasons.
Click to expand...
Click to collapse
What reasons? This is a Google phone. You're allowed to unlock the bootloader and flash modified software without breaking warrantee.
If you have issues, it's easy to just flash the factory image back to completely stock and relock the bootloader.
Sent from my Google Pixel 3a XL using XDA Labs
@strapabiro,
Have you tried this app?
Skittles9823 said:
What reasons? This is a Google phone. You're allowed to unlock the bootloader and flash modified software without breaking warrantee.
If you have issues, it's easy to just flash the factory image back to completely stock and relock the bootloader.
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
You're shifting the subject, but the short answer is, imagine I never had an apple product in my life but I rather buy an iphone than start doing that But that's me and that's another topic like I said, thanks though.
strapabiro said:
You're shifting the subject, but the short answer is, imagine I never had an apple product in my life but I rather buy an iphone than start doing that But that's me and that's another topic like I said, thanks though.
Click to expand...
Click to collapse
Fair argument.
Sent from my Google Pixel 3a XL using XDA Labs
Today I had my phone in my coat pocket at an appointment for about an hour hanging on a coat rack not even being touched. When I came back to, the screen was on, on the lock screen, and if was pretty warm with battery down a good 25 percent. I'm wondering if what you're talking about here has something to do with this? I was confused why or what was going on with it. No unusual apps were in memory in developer settings.
kc6wke said:
@strapabiro,
Have you tried this app?
Click to expand...
Click to collapse
I have found this "feature" annoying as well on my 3a XL. However I tired the app that you suggested and it seems to work fine. Thanks for providing a decent solution to the OPs question.
My fingerprint reader keeps disabling. I have to turn phone off and back on (reboot is not enough). However then all the apos detect a Biometrics change and I have to reenable fingerprint login for each app.
Even when it works the reader is super sensitive and keeps telling me I've had too many attempts before i pick up the phone.
While I do get the too many attempts thing I haven't had the fingerprint reader disable on my phone
For me its working just perfectly.
It works perfectly for me as well. I have found that using a case helps a lot with false reading attempts.
I also use a slim case and I'm having a very positive experience with the fingerprint reader.
Coming from a Pixel 2 XL with a reader at the back, it took me a few days to get used to thumb based unlock.
But now, I find it much more reliable than the Pixel 2 XL reader, where fingers moisture was a real pain.
Same hands (different finger being used on the 5ii and it works almost 100% of the time (and quick too).
Stock ROM and launcher.
arturiu said:
I also use a slim case and I'm having a very positive experience with the fingerprint reader.
Coming from a Pixel 2 XL with a reader at the back, it took me a few days to get used to thumb based unlock.
But now, I find it much more reliable than the Pixel 2 XL reader, where fingers moisture was a real pain.
Same hands (different finger being used on the 5ii and it works almost 100% of the time (and quick too).
Stock ROM and launcher.
Click to expand...
Click to collapse
What case are you using?
also my fingerprint sensor is absolutely flawless I haven't had any issues or anything that has caused me to be concerned or despised the fingerprint sensor. maybe I'm lucky or maybe I just knew how to set the fingerprint up properly I don't know but my experience with it has been positive
thepersona said:
What case are you using?
Click to expand...
Click to collapse
https://www.amazon.co.uk/GEEMEE-Waterproof-Anti-Scratch-Protective-Transparent/dp/B08H5931YQ
arturiu said:
https://www.amazon.co.uk/GEEMEE-Waterproof-Anti-Scratch-Protective-Transparent/dp/B08H5931YQ
Click to expand...
Click to collapse
Damn it doesn't appear that that case is available in Canada or even the US. Oh well hopefully more cases turn up when the device releases in the US
Try adding the same finger a few times. I haven't had any problems since I did that.
Do you also have this issue, that while calling, you accidentally click on the fingerprint sensor and so activate the screen while it is 'at your ear' and so you 'click' on several options and so on? It happens a lot, I have accidentally adjusted with my ear the brightness or paused the call etc. Very annoying!
I struggled a bit at first to have my fingerprint recognized when trying to unlock, often ending up typing my pin instead.
I noticed a huge improvement by sliding my thumb upwards on the sensor, instead of just pressing it still. Now works almost all the times.
November update might have improved the situation as well.
Not sure if it's something to do with a recent update but my reader is not recognising my fingerprints very well at all now. Anyone seen problems?
The other potential issue is that I've been doing a lot of DIY lately and probably worn away some of the detail on my finger ends .
wazzaworld said:
Not sure if it's something to do with a recent update but my reader is not recognising my fingerprints very well at all now. Anyone seen problems?
The other potential issue is that I've been doing a lot of DIY lately and probably worn away some of the detail on my finger ends .
Click to expand...
Click to collapse
Mine still on 58.0.A.22.21 as it's US variant but recently I am also facing issues with fingerprint scanner if the phone is in (deep?) sleep mode. Earlier it used to be just touch and go but now had to press it or try multiple time to unlock it.
Not sure what's the issue here?
No problems with my FPR. Occasionally it requires a couple of tries but that's true of every single phone on the market.
Mine seems to be working well. I am coming from a P30 Pro with the underscreen sensor, and I had a few Xperias before that. This is by far the fastest Android fingerprint sensor I've used. it seems to instantly recognize everything. It's probably on par with my pre-face ID iPhones, but i don't have one of those anymore to compare it.
I ended up disabling the fingerprint reader completely. Never works from first try when I need it, but somehow easily unlocks when I actually don't need it, as in when just holding it, putting down or in pocket. Also all those buttons on the same side is a really poor design choice, specially power right under volume. Btw, is there a way to disable the assistant button?
hovikg said:
I ended up disabling the fingerprint reader completely. Never works from first try when I need it, but somehow easily unlocks when I actually don't need it, as in when just holding it, putting down or in pocket. Also all those buttons on the same side is a really poor design choice, specially power right under volume. Btw, is there a way to disable the assistant button?
Click to expand...
Click to collapse
Everything I have read, says there's no way to disable it. I'm very surprised I have yet to activate accidentally. But, that might be because the button covers on my case are kind of stiff.
hovikg said:
Never works from first try when I need it, but somehow easily unlocks when I actually don't need it, as in when just holding it, putting down or in pocket.
Click to expand...
Click to collapse
I get the exact same behavior. Very frustrating. Totally disappointed with the fingerprint scanner.
hovikg said:
Btw, is there a way to disable the assistant button?
Click to expand...
Click to collapse
You can disable the assistant app. But if course this is only a solution if you don't use the Google assistant at all.
My favorite fingerprint reader was the Pixel 3 with the reader on the back of the phone. My least favorite has been the under-screen readers on my Huaweis. The reason is less accuracy and fingerprints.
I've had my Xperia 5 ii for a day, and have been on it a lot, and the fingerprint reader has been excellent. My problem is finding it and not dropping the phone while I look.
I got a new Watch 4 LTE from TMobile and I did get Google Pay set up on it, and it works, with limitations. It appears that when I tip my wrist back to place the watch near the reader, the screen shuts off and apparently, this may be preventing the NFC from working. If I contort myself the opposite direction so the screen doesn't shut off, Google pay works fine, but it's uncomfortable and just looks weird. As for Samsung Pay, I had it set up on my old watch and I told it I would be moving it to the new watch. This apparently requires an update of the watch app on the Watch 4, which consistently fails. I had a similar issue on my old watch and turning off WiFi on my phone seemed to fix it, but that's not the case here. Anyone have ideas? Can I sideload the Samsung Pay watch app through wireless ADB?
spyderveloce said:
I got a new Watch 4 LTE from TMobile and I did get Google Pay set up on it, and it works, with limitations. It appears that when I tip my wrist back to place the watch near the reader, the screen shuts off and apparently, this may be preventing the NFC from working. If I contort myself the opposite direction so the screen doesn't shut off, Google pay works fine, but it's uncomfortable and just looks weird. As for Samsung Pay, I had it set up on my old watch and I told it I would be moving it to the new watch. This apparently requires an update of the watch app on the Watch 4, which consistently fails. I had a similar issue on my old watch and turning off WiFi on my phone seemed to fix it, but that's not the case here. Anyone have ideas? Can I sideload the Samsung Pay watch app through wireless ADB?
Click to expand...
Click to collapse
Well... I tried Google pay at another shop and it worked fine when the screen turned off... So I'm down to Samsung Pay. Honestly, I don't have to have it with GPay working right now, but it's gonna bug the heck outta me not being able to update it.
Are your phones rooted?
inningsdefeat500 said:
Are your phones rooted?
Click to expand...
Click to collapse
No. I used to root every phone I had long ago, but I stopped doing that when I started using Google Pay and Samsung Pay. These days, I don't find a lot of reason to root anyway.
spyderveloce said:
I got a new Watch 4 LTE from TMobile and I did get Google Pay set up on it, and it works, with limitations. It appears that when I tip my wrist back to place the watch near the reader, the screen shuts off and apparently, this may be preventing the NFC from working. If I contort myself the opposite direction so the screen doesn't shut off, Google pay works fine, but it's uncomfortable and just looks weird. As for Samsung Pay, I had it set up on my old watch and I told it I would be moving it to the new watch. This apparently requires an update of the watch app on the Watch 4, which consistently fails. I had a similar issue on my old watch and turning off WiFi on my phone seemed to fix it, but that's not the case here. Anyone have ideas? Can I sideload the Samsung Pay watch app through wireless ADB?
Click to expand...
Click to collapse
Yeah I have the same issue with Google Pay. When I move my wrist to place it close to the card reader, a clock appears on top of the screen and prevents Google Pay from doing anything.. Really annoying.
I saw other people complaining about this as well on Reddit. Don't know what the solution is for now as I have already turned off the wrist gesture in the settings.
Hello, I tell you that I was able to make NFC payments work with the BBVA GO Apk in Argentina, I comment on why I think that in Latin America, it saved Chile, Brazil and Mexico, there is no application to use NFC Pay. If anyone is interested I can show them how I did. I cannot create a new thread as I am not reaching the level. Best regards Miguel.