Hi there,
Is there a workaround or a root function to enable Always On listening for 'OK Google' while the screen is off/AOD?
It is really bugging me but I cannot see a workaround already posted.
Thanks!
dancooper93 said:
Hi there,
Is there a workaround or a root function to enable Always On listening for 'OK Google' while the screen is off/AOD?
It is really bugging me but I cannot see a workaround already posted.
Thanks!
Click to expand...
Click to collapse
Can Tasker achieve something like this? I have only returned to Android after a 3 years break, any advice is much appreciated!
dancooper93 said:
Hi there,
Is there a workaround or a root function to enable Always On listening for 'OK Google' while the screen is off/AOD?
It is really bugging me but I cannot see a workaround already posted.
Thanks!
Click to expand...
Click to collapse
OMG. Just set up Google Assistant and enable Voice unlock. Just explore your phone.
srdjanLeo said:
OMG. Just set up Google Assistant and enable Voice unlock. Just explore your phone.
Click to expand...
Click to collapse
I have that setting enabled. It works on the lock screen where you can swipe to unlock, but not on the darker lock screen, where it shows the time and the outline of your notifications.
srdjanLeo said:
OMG. Just set up Google Assistant and enable Voice unlock. Just explore your phone.
Click to expand...
Click to collapse
I have enabled them options. It works on the light lockscreen, where you can scroll your notifications and have the 2 icons in the bottom corners.
It does not work on the darker lock screen, or the Always On Display screen, where it only shows the time and the outline of notifications you have.
dancooper93 said:
I have enabled them options. It works on the light lockscreen, where you can scroll your notifications and have the 2 icons in the bottom corners.
It does not work on the darker lock screen, or the Always On Display screen, where it only shows the time and the outline of notifications you have.
Click to expand...
Click to collapse
Works here as it should. With AOD and without. Are you rooted? If you are try other ROM. If you are not, try reflashing stock firmware with Odin or with Side Sync or whatever Samsung kies is now called.
srdjanLeo said:
Works here as it should. With AOD and without. Are you rooted? If you are try other ROM. If you are not, try reflashing stock firmware with Odin or with Side Sync or whatever Samsung kies is now called.
Click to expand...
Click to collapse
I am not rooted. I heard if you root you can only charge your battery to 0%?
Okay, I will have a look into reflashing if that'll fix it.
Are you rooted?
dancooper93 said:
I am not rooted. I heard if you root you can only charge your battery to 0%?
Okay, I will have a look into reflashing if that'll fix it.
Are you rooted?
Click to expand...
Click to collapse
Same for me Dan, works after you swipe but not from AOD, every tutorial I have seen says the same, has to be "open" before it will work.
Bixby will unlock from the AOD screen if you set that up, hope that helps
MilgeS said:
Same for me Dan, works after you swipe but not from AOD, every tutorial I have seen says the same, has to be "open" before it will work.
Bixby will unlock from the AOD screen if you set that up, hope that helps
Click to expand...
Click to collapse
What do you mean 'open'?
I have Bixby set up, which I just use to open Google now, not ideal, but it is a workaround nonetheless!
dancooper93 said:
I am not rooted. I heard if you root you can only charge your battery to 0%?
Okay, I will have a look into reflashing if that'll fix it.
Are you rooted?
Click to expand...
Click to collapse
I am rooted. With custom ROM, NOTE 8 Port.
Charging works as it should, OK Google trigger works as well. I really don't have any problem.
srdjanLeo said:
I am rooted. With custom ROM, NOTE 8 Port.
Charging works as it should, OK Google trigger works as well. I really don't have any problem.
Click to expand...
Click to collapse
It works for you because you are using a Note 8 ported ROM. Because Samsung enabled this feature on the Note 8. It will not currently work on the stock S8 ROM. Some people seem to be in a server side test to enable this feature though.
Okay, I see.
Does charging not stop at 80% for you because you are rooted?
artikle said:
It works for you because you are using a Note 8 ported ROM. Because Samsung enabled this feature on the Note 8. It will not currently work on the stock S8 ROM. Some people seem to be in a server side test to enable this feature though.
Click to expand...
Click to collapse
It was working for me on Bat Stock ROM and it is S8 ROM. I never used stock ROM so I can't say anything about that, I rooted my device and flashed custom ROM before even setting it up after unboxing.
srdjanLeo said:
It was working for me on Bat Stock ROM and it is S8 ROM. I never used stock ROM so I can't say anything about that, I rooted my device and flashed custom ROM before even setting it up after unboxing.
Click to expand...
Click to collapse
I forgot to quote you, sorry.
Question:
Does charging not stop at 80% for you because you are rooted?[
dancooper93 said:
I forgot to quote you, sorry.
Question:
Does charging not stop at 80% for you because you are rooted?[
Click to expand...
Click to collapse
It stops. But there is a workaround if you have Snapdragon version. Mine is Exynos so it is as Samsung set it up.
srdjanLeo said:
It stops. But there is a workaround if you have Snapdragon version. Mine is Exynos so it is as Samsung set it up.
Click to expand...
Click to collapse
I am now rooted
What Note 8 ROM did you use?
dancooper93 said:
What do you mean 'open'?
I have Bixby set up, which I just use to open Google now, not ideal, but it is a workaround nonetheless!
Click to expand...
Click to collapse
I meant "open" as in on lock screen re your above post, the screen after AOD, sorry for any confusion
Same here works after you swipe but not from AOD, every time tutorial I have seen says the same has to be "open" before it will work.
It's best to think of the always-on display as "Screen Off", which is why OK Google doesn't work on stock ROM. That's standard Android procedure to avoid draining the battery by always listening for voice commands.
At one point, Google Assistant was able to listen when the screen was off, so long as the phone was being charged. Unfortunately, that feature disappeared at some point in the past half year or so (which caused me some confusion when it stopped working and I could no longer find the toggle).
scatterthought said:
It's best to think of the always-on display as "Screen Off", which is why OK Google doesn't work on stock ROM. That's standard Android procedure to avoid draining the battery by always listening for voice commands.
At one point, Google Assistant was able to listen when the screen was off, so long as the phone was being charged. Unfortunately, that feature disappeared at some point in the past half year or so (which caused me some confusion when it stopped working and I could no longer find the toggle).
Click to expand...
Click to collapse
That's not true. It still works on a Google Pixel running stock Android with the screen off and not charging. You never had to have it plugged in or charging for that to work. Samsung is the ONLY Android phone I know of that OK Google doesn't work with the screen off.
Source: I've owned the Nexus 6, Nexus 5x, the Nexus 6P, the Pixel XL, a number of Galaxy phones, and a few Motorola's and a couple LGs.
Related
Well there was a thread that was going, but the OP decided to post warez links and it got closed. http://forum.xda-developers.com/showthread.php?t=2601850
I made an app with Tasker App Factory that does what the original post explains in a video (http://m.androidauthority.com/moto-x-green-notification-331710/), for those that don't have/want Tasker.
This is the first time I've shared anything that I've made in Tasker, and I can't say why it has some of the permissions it does, honestly. If anyone cna elaborate on why it does has those default permissions, that'd be great.
DISCLAIMER: As I stated above, this is my first app. I tested it on my Verizon Moto Maker edition Moto X that is rooted on 4.4. I take no responsibility for what happens to your phone or anything you do with this app. It worked fine for me, but I make no promises it will work for you.
Latest Version: https://copy.com/uUWpwXnGdJXpPIC
- Latest one adds in a few more options for how the light is displayed, and a brightness setting.
Original Version: https://copy.com/9w9TlRH2yt3L3BC
Install, run, and accept the root request (root is needed for the shell command, just as it is in the Tasker profile). It will also run the command when you boot, and starts working a few seconds after the phone turns on.
Note: If you decide you don't like it and uninstall the app, you will probably need to reboot after uninstalling to disable the LED.
Hopefully someone finds this useful. I personally don't care for it, but I like making stuff in Tasker and thought I'd give it a shot.
I just installed this. It works very well, thank you.
Installed and works. But isnt it supposed to switch off the light once the phone is charged?
Running on AT&T XT1058 KK
anirudh412 said:
Installed and works. But isnt it supposed to switch off the light once the phone is charged?
Running on AT&T XT1058 KK
Click to expand...
Click to collapse
It is set to display the LED when it is charging or full. When I get a few minutes I can update with other options.
I updated OP with a new link, newer version with more options.
very cool! Thanks!!!! Seems to be working just fine.
If you plan to add anything, a slow fade on and off would be a nice addition as well!
ssoares01 said:
very cool! Thanks!!!! Seems to be working just fine.
If you plan to add anything, a slow fade on and off would be a nice addition as well!
Click to expand...
Click to collapse
I don't know of a way to change the behavior of the LED other than what's there. It can only do things defined by the system software at this point. If anything else becomes available, I'll see about updating it.
Why does it need the permission to unlock the device?
MaKTaiL said:
Why does it need the permission to unlock the device?
Click to expand...
Click to collapse
I have no idea. I referenced it in the first post. Tasker seems to have that for all apps and I couldn't remove it. I have a lock screen PIN on my phone and it is not disabled by the app.
fury683 said:
I have no idea. I referenced it in the first post. Tasker seems to have that for all apps and I couldn't remove it. I have a lock screen PIN on my phone and it is not disabled by the app.
Click to expand...
Click to collapse
Thanks, the app works great.
Enviado de meu XT1058 usando Tapatalk
Rooted?
hello dude! Nice job,
Are necessary to be root to do this app work?
Thank You.
Josoe said:
hello dude! Nice job,
Are necessary to be root to do this app work?
Thank You.
Click to expand...
Click to collapse
Yes root is required to run the shell command.
I don't think I would bother with this for normal use however if someone stuffs a wireless charging coil inside the phone then I think it becomes very useful.
Still waiting for my coil to arrive before I crack into a phone.
Steve-x said:
I don't think I would bother with this for normal use however if someone stuffs a wireless charging coil inside the phone then I think it becomes very useful.
Still waiting for my coil to arrive before I crack into a phone.
Click to expand...
Click to collapse
Yeah I'm still undecided. I like it with the brightness nearly all the way down, like below 10. It's subtle but I can still find my phone in the dark when next to my bed (the active display shuts off from 12am-7am).
With the new update its useful to know that your battery is fully charged once the led has shut off. There is no other way to know with this phone unless you turn the screen on
Mayze23 said:
With the new update its useful to know that your battery is fully charged once the led has shut off. There is no other way to know with this phone unless you turn the screen on
Click to expand...
Click to collapse
Also true. Someone posted that one of the options was to blink while charging and stay solid when it gets full, but it doesn't seem to work properly. It just blinks until it's full and then shuts off, from what I read. If they find a way to fix it I'll add it in.
some work for notification led for other apps ??
thank u for ur work
danger2u said:
some work for notification led for other apps ??
thank u for ur work
Click to expand...
Click to collapse
Currently it only works when the phone is plugged in as a charging indicator.
Currently rooted on 4.4.
installed the program, didnt ask for root access, and the LED doesnt show up.
can someone please help me?
MaKTaiL said:
Thanks, the app works great.
Enviado de meu XT1058 usando Tapatalk
Click to expand...
Click to collapse
latest version that allows setting different lights for charging and full doesn't work....light never goes on. Previous version worked. rooted Verizon developer edition.
I think about buying the Axon 7, but got one question left and haven't found an answer anywhere:
Is the OK Google Command working without the screen being turned on or the device being charged?
Basically: is it behaving like a Nexus device would? I know many devices only react to "OK Google" if the device is turned on and/or charging.
This does not work on the Axon 7. Nexus 6P and Moto phones are the only devices I know of that do this.
Delete
xxBrun0xx said:
This does not work on the Axon 7. Nexus 6P and Moto phones are the only devices I know of that do this.
Click to expand...
Click to collapse
This is not true. When charging, I can say ok google and the devices listens to me. Also, if the screen is on and I'm not charging, I can still say ok google and it will listen.
notese said:
This is not true. When charging, I can say ok google and the devices listens to me. Also, if the screen is on and I'm not charging, I can still say ok google and it will listen.
Click to expand...
Click to collapse
Could be wrong but it sounded like he was asking if off screen voice commands worked while the phone was not charging?
xxBrun0xx said:
This does not work on the Axon 7. Nexus 6P and Moto phones are the only devices I know of that do this.
Click to expand...
Click to collapse
And the V20 apparently
xxBrun0xx said:
Could be wrong but it sounded like he was asking if off screen voice commands worked while the phone was not charging?
Click to expand...
Click to collapse
You are right! I got really used to using "OK Google" while the phone is in stand-by, i.e., screen turned off and not charging.
Why are vendors not able to properly implement this? The Snapdragon is technically able to do this.
smuurfi said:
And the V20 apparently
You are right! I got really used to using "OK Google" while the phone is in stand-by, i.e., screen turned off and not charging.
Why are vendors not able to properly implement this? The Snapdragon is technically able to do this.
Click to expand...
Click to collapse
Yeah it really breasts me. I miss that from my Nexus 6p, but that's about the only thing I miss other than camera and nougat. The snapdragon 820 is amazing and battery life on the Axon is better than the 6p.
Sorry to bring up an old thread, but I've missed being able to say Okay Google from when the screen is off like I was able to on the 6P. I've been trying to figure out why and I think maybe one of two things (maybe both) is happening. One is that the power manager automatically screen cleans the Google app. The app isn't in the power management menu so that you can toggle off screen cleaning. The other is that I think the phone turns off the mic when the screen turns off and locks. However, if I just used Google Assistant and turn off the screen, I am able to use Okay Google with the screen off if I say it a split second after I turn off the screen with the power button. Sometimes it works, sometimes I have to enter my PIN, but it always has to be right after using Google Assistant and locking the screen. Throwing this out there with the hopes that someone might be able to figure out how to get around this.
Yep same
Mike
youtu.be/wbqOni008hc
Any solutions? I want to know is it software or hardware problem?
edit: Specs
Marshmallow 6.0.1 G900HXXSACQAA/G900HOJP1CPL1/G900HXXU1CPCA
Smart Launcher Pro 3.16.06PX
Waouuuuuuu....
Never seen that before.
Backup, flash new firmware and reboot.
If problem still present, it's a material problem.
Good luck mate
Franck
Seems to be a standard problem. I have it too.
Internet forums are full of this problem.
Buy another phone than Samsung.
fgth90 said:
Waouuuuuuu....
Never seen that before.
Backup, flash new firmware and reboot.
If problem still present, it's a material problem.
Good luck mate
Franck
Click to expand...
Click to collapse
I've seeb it alot actually. I mean the wake up problem. But noone seems to fix it yet. If anyone did please tell me
Has anyone test this with older Android 5?
The "Weird" Screen in Low Brightness is AMOLED Burn-in due to intensive use, My S5 Have this problem too.
Try changing the HW overlay / Force GPU rendering in developer options, others have said that works for them, it seemed to for me also but only temporarily. I have had to stop using auto brightness.
Device not waking up is very irritating, even double tap the screen to wake has the same problem, doesn't seem to be the buttons themselves. If you have a custom rom or other way to set double pressing the power button to launch the camera it works as a workaround for me.
Thank you for all the answers guys.
Valmerost said:
Try changing the HW overlay / Force GPU rendering in developer options, others have said that works for them, it seemed to for me also but only temporarily. I have had to stop using auto brightness.
Device not waking up is very irritating, even double tap the screen to wake has the same problem, doesn't seem to be the buttons themselves. If you have a custom rom or other way to set double pressing the power button to launch the camera it works as a workaround for me.
Click to expand...
Click to collapse
Just changed:
Force GPU rendering : on
Disable hardware overlays: on
edit1:it's better than before. I will feedback later. Also gonna try that camera trick
edit2: It's same again. Tried Home2 Shortcut the get the camera trick. It also didn't work because i want my phone to be locked and it doesn't work on locked status
Any other suggestions guys?
what ROM are you guys using? Have you tried a different one?
youdoofus said:
what ROM are you guys using? Have you tried a different one?
Click to expand...
Click to collapse
It's the stock ROM. No, I'm planning to try a new ROM today.
raiwulf said:
It's the stock ROM. No, I'm planning to try a new ROM today.
Click to expand...
Click to collapse
that would be a good place to start
Flashed Wanted ROM, it's still the same. It was better at start tho and somehow it freezes less in battery saving mode.
raiwulf said:
Flashed Wanted ROM, it's still the same. It was better at start tho and somehow it freezes less in battery saving mode.
Click to expand...
Click to collapse
if thats the case, then it might be a hardware issue
this is weird af, tons of people have this issue, no solutions yet
raiwulf said:
this is weird af, tons of people have this issue, no solutions yet
Click to expand...
Click to collapse
My solution was buying an OnePlus 3T and never buy a Samsung phone again.
derAndroidler said:
My solution was buying an OnePlus 3T and never buy a Samsung phone again.
Click to expand...
Click to collapse
baaahahahahaha!!! My fiancee has a OnePlus 2 and is a pretty big fan of it. The camera app for samsung TW is far superior tho
Hi all, hopefully this has not been discussed. I searched but from the xda app search isn't so great...
Anyway wondering if anyone is having issues with trusted voice. I noticed okay Google was only working when phone was authenticated. And not from secured lock screen. Figured trusted voice was disabled, so I checked and it's just not there. (See image). I'm on 4.5.8 stock not rooted. I have tried clearing data on Google app.
Any suggestions is appreciated.
Thanks!
I wanted to use Google Assistant so had to use the beta versions of Google app and services. My Smart Lock screen is showing Trusted Voice, Trusted Face, On body, Trusted places, Trusted devices. With that being stated Google Assistant has never worked from my the lock screen which requires Trusted Voice to be enabled. Of course it's enabled on my OP5 but still doesn't work, which is a real pain in the butt.
Current versions:
Google v7.9.18.21.amd64
Google Play Services v11.5.20
I running OOS v4.5.8 with an unlocked bootloader and rooted (SuperSU). Recently I changed from stock to the Franco Kernel but Trusted voice has been available on my OP5 since I first got this device. My replacement of the stock kernel made no difference in this case.
3DSammy said:
I wanted to use Google Assistant so had to use the beta versions of Google app and services. My Smart Lock screen is showing Trusted Voice, Trusted Face, On body, Trusted places, Trusted devices. With that being stated Google Assistant has never worked from my the lock screen which requires Trusted Voice to be enabled. Of course it's enabled on my OP5 but still doesn't work, which is a real pain in the butt.
Current versions:
Google v7.9.18.21.amd64
Google Play Services v11.5.20
I running OOS v4.5.8 with an unlocked bootloader and rooted (SuperSU). Recently I changed from stock to the Franco Kernel but Trusted voice has been available on my OP5 since I first got this device. My replacement of the stock kernel made no difference in this case.
Click to expand...
Click to collapse
That's dumb! Have you tried toggling Smart lock in the trust agents of the security menu?
Also I noticed you're in Canada (eh?), mind if I ask which language you run as primary on your device? English US, Canada?
I started on English US as google assistant wouldnt fire up with Canada, but since then, I'm back to English Canada. Assistant still works, but as mentioned only when phone is unlocked.
tsuttie99 said:
That's dumb! Have you tried toggling Smart lock in the trust agents of the security menu?
Also I noticed you're in Canada (eh?), mind if I ask which language you run as primary on your device? English US, Canada?
I started on English US as google assistant wouldnt fire up with Canada, but since then, I'm back to English Canada. Assistant still works, but as mentioned only when phone is unlocked.
Click to expand...
Click to collapse
I'd read that others (UK) switched back to their native language after getting Google Assistant working and all was well. I've left it as US as primary with Canada as a second as it simply doesn't effect me. I like spelling colour as "color" which always made more sense to me.
My real reason for not switching back is that I've done a lot of home automation scripting with Google Assistant/Tasker's Voice Assist/Termux to automate my audio/video equipment and associated lighting. As far as I'm concerned Google Assistant may be in beta for built in functionality but is alpha for any third party integration. Every Google app update seems to break something while fixing other functionality (e.g. macros).
I like the automation I've created enough that I have little interest in rocking the boat at the moment. I had previously retested Trusted voice and the lock screen after updates and will again until it works. Right now I'm using a work around with an app called Caffeine (disables the lock screen timeout when charging) and Screen off (only turns the screen off but does not trigger the lock screen).
Also I may have tried toggling Trusted agents as I did so many tests and retests while working on Google Assistant functionality, I just can't remember.
I think there is something very broken with Smart Lock on this phone's stock OS.... I set up my cars BT as trusted device.... still i need to Authenticate with finger/pattern. Coming from a 6P where this all worked seamlessly it's frustrating.
My assisstant works from lock screen with "OK Google".
Stock 4.5.8 with root.
I boot into TWRP instead of flashing the recovery. Still have stock recovery.
Use Magisk v13.3 with Magisk Manager 5.1.1.
Have English (US) as my primary language with English (Australia) as my 2nd.
ultramag69 said:
My assisstant works from lock screen with "OK Google".
Stock 4.5.8 with root.
I boot into TWRP instead of flashing the recovery. Still have stock recovery.
Use Magisk v13.3 with Magisk Manager 5.1.1.
Have English (US) as my primary language with English (Australia) as my 2nd.
Click to expand...
Click to collapse
By the way how do you pull off the trick of "boot into TWRP"? I've never read about how to do that. Also what does it buy you other than maybe the GA working on the lock screen?
3DSammy said:
By the way how do you pull off the trick of "boot into TWRP"? I've never read about how to do that. Also what does it buy you other than maybe the GA working on the lock screen?
Click to expand...
Click to collapse
Just get your phone plugged into your PC and from bootloader you type "fastboot boot recovery <twrp file name>.img
It will just boot from that image instead of writing it to flash
tsuttie99 said:
Just get your phone plugged into your PC and from bootloader you type "fastboot boot recovery <twrp file name>.img
It will just boot from that image instead of writing it to flash
Click to expand...
Click to collapse
Interesting trick, thanks for the info.
Unfortunately I could not use it as I had to borrow a relatives Win10 PC just to flash TWRP in the first place as I couldn't get around that fastboot file size error multiple people experienced no matter which USB ports (v2 or v3) or adb versions I tried. Going to another computer (same model of motherboard) and TWRP was flashed in a second.
3DSammy said:
Interesting trick, thanks for the info.
Unfortunately I could not use it as I had to borrow a relatives Win10 PC just to flash TWRP in the first place as I couldn't get around that fastboot file size error multiple people experienced no matter which USB ports (v2 or v3) or adb versions I tried. Going to another computer (same model of motherboard) and TWRP was flashed in a second.
Click to expand...
Click to collapse
No worries, I've never actually used that trick as I can always think of a good reason to just have TWRP installed. But times are weird right now, I'm still 100% stock on this phone aside from oem unlock toggle being set. This is the longest I've gone on a fully stock setup. Aside from this Smart Lock/Trusted Voice issue everything is perfect on the OS.
Okay so this is weird. I can't believe i didn't try this test. I can yell "okay google" until the cows come home while the screen is off. it wont light up or unlock. However if i wake the screen THEN say okay google, my phone unlocks and assistant begins working. Is this the same for others who claim "everything is working fine for me"?
tsuttie99 said:
No worries, I've never actually used that trick as I can always think of a good reason to just have TWRP installed. But times are weird right now, I'm still 100% stock on this phone aside from oem unlock toggle being set. This is the longest I've gone on a fully stock setup. Aside from this Smart Lock/Trusted Voice issue everything is perfect on the OS.
Click to expand...
Click to collapse
I'm on stock oos & I'm using Blu kernel & Blu twrp. Blu kernel was so good on the op3T that OnePlus sent him a free op5 last week. I really like the Blu kernel, so much I switched from RR to oos for the first time. OK Google is working to unlock my phone btw.
Rebel7022 said:
I'm on stock oos & I'm using Blu kernel & Blu twrp. Blu kernel was so good on the op3T that OnePlus sent him a free op5 last week. I really like the Blu kernel, so much I switched from RR to oos for the first time. OK Google is working to unlock my phone btw.
Click to expand...
Click to collapse
Thanks for the info. Can you share if you can unlock the phone with OK google with the screen off? Scenario: Your phone is on a nearby table and you are a few feet away from it, the screen is off, the phone is not charging. Can you OK google without touching the phone?
tsuttie99 said:
Thanks for the info. Can you share if you can unlock the phone with OK google with the screen off? Scenario: Your phone is on a nearby table and you are a few feet away from it, the screen is off, the phone is not charging. Can you OK google without touching the phone?
Click to expand...
Click to collapse
There's a xda article on OK Google that has a hack to do that. I tried it it works.. But that was 3 months ago
tsuttie99 said:
Okay so this is weird. I can't believe i didn't try this test. I can yell "okay google" until the cows come home while the screen is off. it wont light up or unlock. However if i wake the screen THEN say okay google, my phone unlocks and assistant begins working. Is this the same for others who claim "everything is working fine for me"?
Click to expand...
Click to collapse
Yep, works from lock screen, not screen off...
tsuttie99 said:
Okay so this is weird. I can't believe i didn't try this test. I can yell "okay google" until the cows come home while the screen is off. it wont light up or unlock. However if i wake the screen THEN say okay google, my phone unlocks and assistant begins working. Is this the same for others who claim "everything is working fine for me"?
Click to expand...
Click to collapse
Well fancy that. I just did your test, locked screen with power button, with screen off there's no reaction to "OK Google". I then double tap the screen and the lock screen displays. Now "OK Google" unlocks the phone and Google Assistant is fully functional.
Kind of feels like a sprinter that falls inches before the finish line. What the heck Google or OnePlus? I wonder if custom ROMs have the same issue?
Thanks for noticing this phenomena and posting about it.
It's has been asked by many user in several forum but still couldn't find the answer, so please how to disable vibrate when tap fingerprint to unlock like in battery saver mode,already have root,twrp and unlocked of course,ready for mods,this should be possible but still couldn't find any threads for this,please help
afrizal87 said:
It's has been asked by many user in several forum but still couldn't find the answer, so please how to disable vibrate when tap fingerprint to unlock like in battery saver mode,already have root,twrp and unlocked of course,ready for mods,this should be possible but still couldn't find any threads for this,please help
Click to expand...
Click to collapse
Maybe there isn't a way for that yet ?
NITRO_100 said:
Maybe there isn't a way for that yet ?
Click to expand...
Click to collapse
Technically it could be done since we can disable it when in battery saver mode or in total silent mode,i have mi 5 earlier and there is mod for that yet its miui tho.
Im just thinking how much battery life we could save if that vibrate turned off,imagine we unlock the fingerprint sensor all the time right? And its always vibrate everytime we tap it.so technically we could save more battery life without sacrificing some important features
afrizal87 said:
Technically it could be done since we can disable it when in battery saver mode or in total silent mode,i have mi 5 earlier and there is mod for that yet its miui tho.
Im just thinking how much battery life we could save if that vibrate turned off,imagine we unlock the fingerprint sensor all the time right? And its always vibrate everytime we tap it.so technically we could save more battery life without sacrificing some important features
Click to expand...
Click to collapse
There is sure a way, either via some exposed module or custom rom or kernel, which either is yet not available. And the battery life is excellent on this phone, doubt that disabling vibrating will save much battery.
Hello everyone,
we finally have a way to remove this awful vibration everytime we unlock our phone through the fingerprint!
Yesterday gravitybox was released for oreo (https://www.xda-developers.com/all-in-one-xposed-module-gravitybox-android-oreo/) and comes with an option to disable this vibration, works like a charm.
I advice you tu use xposed with magisk to be systemless, or just install xposed normaly.
HEIS3NBERG said:
Hello everyone,
we finally have a way to remove this awful vibration everytime we unlock our phone through the fingerprint!
Yesterday gravitybox was released for oreo (https://www.xda-developers.com/all-in-one-xposed-module-gravitybox-android-oreo/) and comes with an option to disable this vibration, works like a charm.
I advice you tu use xposed with magisk to be systemless, or just install xposed normaly.
Click to expand...
Click to collapse
Thank you so much finally..
Hahahaha hahahaha hahhahahaha [emoji23][emoji24][emoji23][emoji23][emoji23][emoji23][emoji23][emoji23][emoji23][emoji23][emoji23][emoji23][emoji23][emoji23]
Sorry, there is no way to do it. I actually came to search how to enable vibration. After Oreo update to 8.1.0 my phone stopped vibrating or giving any sort of feedback while unlocking through finger print.
And I laughed because you are searching for exactly opposite thing and both yours and mine query are impossible.
Sent from my Mi A1 using Tapatalk
vishalgaur789 said:
Hahahaha hahahaha hahhahahaha [emoji23][emoji24][emoji23][emoji23][emoji23][emoji23][emoji23][emoji23][emoji23][emoji23][emoji23][emoji23][emoji23][emoji23]
Sorry, there is no way to do it. I actually came to search how to enable vibration. After Oreo update to 8.1.0 my phone stopped vibrating or giving any sort of feedback while unlocking through finger print.
And I laughed because you are searching for exactly opposite thing and both yours and mine query are impossible.
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
Xiaomi just make the vibration the lowest possible
I can still feel it but it is less than touching the home button vibration
You'll live with it ^^
Dead-neM said:
Xiaomi just make the vibration the lowest possible
I can still feel it but it is less than touching the home button vibration
You'll live with it ^^
Click to expand...
Click to collapse
Yes I know they have minimised it. I read it through official forums. But, what I'm saying isn't stupid. I'm not a novice when it comes to android, app development, rooting, adb, etc.
When I'm saying it is gone, it really is gone from my phone. Not even 1% vibration is there in the sensor. Updates do affect some phones differently. It happens due to various reasons and it happens! In real!
Sent from my Mi A1 using Tapatalk
vishalgaur789 said:
Yes I know they have minimised it. I read it through official forums. But, what I'm saying isn't stupid. I'm not a novice when it comes to android, app development, rooting, adb, etc.
When I'm saying it is gone, it really is gone from my phone. Not even 1% vibration is there in the sensor. Updates do affect some phones differently. It happens due to various reasons and it happens! In real!
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
Okay so yeah I though you were not noticing the vibration as it have been reduced a lot.
Now I see you have feelings so
I could suggest something
you should be able to make vibration stronger
Not sure about stock kernel
The idea is to make the default vibration stronger to see if you notice it with fingerprint
If the fingerprint vibration is based on a percentage of the default one there's a chance you can feel it and so you probably have a different vibrator or a light one that need to be set a little more high than default
This can also make non sense if fingerprint vibration is a separate value and also you can just have a bug and the best solution is to factory reset or wait the next ota to see if it's fixed
Hope you'll be able to find a solution
The fingerprint sensor still vibrates but its very faint.
Dead-neM said:
Okay so yeah I though you were not noticing the vibration as it have been reduced a lot.
Now I see you have feelings so
I could suggest something
you should be able to make vibration stronger
Not sure about stock kernel
The idea is to make the default vibration stronger to see if you notice it with fingerprint
If the fingerprint vibration is based on a percentage of the default one there's a chance you can feel it and so you probably have a different vibrator or a light one that need to be set a little more high than default
This can also make non sense if fingerprint vibration is a separate value and also you can just have a bug and the best solution is to factory reset or wait the next ota to see if it's fixed
Hope you'll be able to find a solution
Click to expand...
Click to collapse
No vibrations will change fingerprint vibration settings until I'm rooted.
I can sense mere vibrations of FOSS keyboard settings too at minimum possible (1 point).
Sent from my Mi A1 using Tapatalk
You can disable it in the Settings >> Accessibility >> Vibration and turn off "Touch Vibration".
arun.0388 said:
You can disable it in the Settings >> Accessibility >> Vibration and turn off "Touch Vibration".
Click to expand...
Click to collapse
This worked for me with my oneplus 6 on Lineage Thanks, I was finding it really irritating.