Related
Hi guys
I've been getting fairly decent battery life, however am now connecting my phone to the car daily via bluetooth.
I've noticed some battery drain and after checking the built in battery stats and also better battery stats app, my Bluetooth is not turning off when I'm selecting it.
IE, connected on the drive to work, get to work, disconnected then turned off, but showing as constantly on.
Any ideas what could cause this?
Sent from my HTC One X using xda app-developers app
I have noticed the same thing when viewing battery stats although I never use bluetooth and it's always off.
Sent from my HTC One X using xda premium
Any updates or anyone else having the same problem?
I also noticed it just a minute ago. gsam monitor tells that bt was on for 6hrs+ which is the exact same time with phone radio.
Earlier this week connected to my boss' car radio for bt aux, this is the first and last time I used bt. Switched it on&off from settings, nothing changed.
SH26CW, running 4.0.4
Might be useful to give the serial no's since it is useful information about the production site and date.
Sent from my HOX via xdapp
thekillingroad said:
I also noticed it just a minute ago. gsam monitor tells that bt was on for 6hrs+ which is the exact same time with phone radio.
Sent from my HOX via xdapp
Click to expand...
Click to collapse
Same issue here, and same Android version. GSam always reports the same Bluetooth on time as the time unplugged, ie. it's saying that BT has been on all the time, while it's clearly off. I've tried different ways to switch off BT (using widget, using settings, going into Airplane mode and back) but to no avail.
Part of me is suspecting that GSam might be reading the wrong value and falsely reporting it as Bluetooth. But perhaps someone with a different battery monitoring app could check on this and confirm?
It is a bug, to solve it you will need to restart your phone.
This is the only way I find to solve this on stock 2.17/Android 4.0.4.
This bug is caused by turning your Bluetooth on and off.
I faced the same problem? But does that use battery? Actually.the Bluetooth is off.
Sent from my HTC One X using xda app-developers app
neuTrue said:
It is a bug, to solve it you will need to restart your phone.
This is the only way I find to solve this on stock 2.17/Android 4.0.4.
This bug is caused by turning your Bluetooth on and off.
Click to expand...
Click to collapse
Hmm, user fault then hheheheueh
the strange thing is, it does not consume battery at all. ok it's not connected to any device but I would think it would consume more than just %1.
may be non-discoverable makes it use less. not broadcasting anything.
neuTrue said:
It is a bug, to solve it you will need to restart your phone.
This is the only way I find to solve this on stock 2.17/Android 4.0.4.
This bug is caused by turning your Bluetooth on and off.
Click to expand...
Click to collapse
A restart sometimes fix the problem but not always. Today I had bluetooth turned off then after restarting by four hours my device reports that bluetooth has been on for 4 hours even though I didn't turn it on and it shows that it's off.
Sent from my HTC One X using xda premium
Glad I'm not the only one
I do find a reboot fixes it, but I don't want to have to reboot my phone every time I get out the car.
I'll get my serial number when I'm home and see if its the same
Sent from my Nexus 7 using xda app-developers app
I'm now having a chat with HTC live support about JB update and also asked the question about BT off issue.
He said, please follow the following steps.. Waiting for what he'll say..
So he suggested booting in safe mode, going to applications? >> manage, uncheck.. ? I'm not familiar with safe mode so I cannot surely say what he is talking about.
Has anyone tried this? Did it work?
So he sad that this will solve if an application is triggering the problem, but I haven't used any applications that use BT.
So, the next suggestion is factory reset, bullsh*t. sorry guys =)
useless post may be, but confirms that HTC official support has no fixing for this.
thekillingroad said:
Hmm, user fault then hheheheueh
the strange thing is, it does not consume battery at all. ok it's not connected to any device but I would think it would consume more than just %1.
may be non-discoverable makes it use less. not broadcasting anything.
Click to expand...
Click to collapse
Hahaha, that's funny and more towards Apple ideology.
Bluetooth was designed to be efficient. But, if its running then it consuming energy ,and that's something I don't like.
I already checked logcat/kmsg ,but nothing about this Bluetooth issue.
I didn't see anyone on JB came to complain about this, let's see what the offical JB has to offer.
hatemk said:
A restart sometimes fix the problem but not always. Today I had bluetooth turned off then after restarting by four hours my device reports that bluetooth has been on for 4 hours even though I didn't turn it on and it shows that it's off.
Click to expand...
Click to collapse
Try to disable "fastboot", and give it a try.
I am afraid nothings more can be done on stock, other option is to wait for JB and hope it already fixed.
thekillingroad said:
I'm now having a chat with HTC live support about JB update and also asked the question about BT off issue.
He said, please follow the following steps.. Waiting for what he'll say..
So he suggested booting in safe mode, going to applications? >> manage, uncheck.. ? I'm not familiar with safe mode so I cannot surely say what he is talking about.
Has anyone tried this? Did it work?
So he sad that this will solve if an application is triggering the problem, but I haven't used any applications that use BT.
So, the next suggestion is factory reset, bullsh*t. sorry guys =)
useless post may be, but confirms that HTC official support has no fixing for this.
Click to expand...
Click to collapse
Safe mode is a mode in Android, that will will disable all the 3rd party installed apps. Similar to safe mode in Windows. After your turned on your phone, just press on the volume key and it will get you there.
Beside that, I never trust customer support, and I never had a good experience with any of them.
The only good thing is about companies offering customer support, is they add job opportunities into the economy.
This problem just crept up on me. I noticed the battery was lower than normal, I checked BBS and it seems like BT never turned off. A reset would solve the problem until I turn BT back on again.
Does anyone know if this has been fixed with 4.1?
sefuwl said:
Does anyone know if this has been fixed with 4.1?
Click to expand...
Click to collapse
It seems so, at least on my One X G Sam is now reporting the correct BT on-time, whereas pre-JB it was continually on, clock ticking even after turning it off.
Sent from my HTC One X using Tapatalk 2
bluetooth
no probs here:good:
When I lock the phone using the power key after certain time it wakes up again automatically... It keeps happening... Any way to resolve this, which application is causing such an issue
Sent from my Galaxy Nexus using xda app-developers app
cldwar said:
When I lock the phone using the power key after certain time it wakes up again automatically... It keeps happening... Any way to resolve this, which application is causing such an issue
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
man, that's already the 3rd if not 4th thread abut this issue, one being opened by myself...
glad that I'm not the only one...
at beginning I thought it'd be a faulty/bent usb connector, as experienced by others, but since I am redaing of others with the same problem after upgrading, then it cannot be...
have you install;ed the OTA or started from cratch? have you cleaned dalvik cache? (I did with no avail) do you see a pattern in your wakeups? is it every x minutes? is it at random?
as regards me, it happens also when wifi and 3g and sync is off (but 2g on, that is I can only receive calls), so it cannot be anything related to signals...
I have installed BetterBatteryStats and will be sending a couple of resports to the developer trying to see if he can understand what is going on and what wakes up the phone...
I did a completely clean install... Wipe data and cache... Installed the OTA rom available on developers section.
Do tell me if you are able to find a solution.
Sent from my Galaxy Nexus using xda app-developers app
Check this bugreport:
https://code.google.com/p/android/issues/detail?id=39829
Yeah, the same thing happens to me. VZW Toro. Stock AOSP Rom. I think it's related to daydream. It didn't start happening until I enabled that functionality.
angel.de.marc said:
Yeah, the same thing happens to me. VZW Toro. Stock AOSP Rom. I think it's related to daydream. It didn't start happening until I enabled that functionality.
Click to expand...
Click to collapse
nope... daydream is off on my phone
It seems to be an issue with the WeChat app:
http://code.google.com/p/android/issues/detail?id=39625#c12
That's the original bug report. Star it for news and increase its visibility.
VuDuCuRSe said:
It seems to be an issue with the WeChat app:
http://code.google.com/p/android/issues/detail?id=39625#c12
That's the original bug report. Star it for news and increase its visibility.
Click to expand...
Click to collapse
what's wechat? something stock? new in 4.2?
Dunno, but follow the issue on that link. Answers ougta be there soon...
I do use WeChat .. let me delete this application and check ...
Deleted WeChat and disabled Day dream ... 7 minutes and phone is not waking up .. seems like the problem is resolved. ..
cldwar said:
Deleted WeChat and disabled Day dream ... 7 minutes and phone is not waking up .. seems like the problem is resolved. ..
Click to expand...
Click to collapse
I don't have wechat and the problem is there so no it's not wechat
I am in the same boat, Thegios.
No Wechat... No Daydream.
I have noticed my screen waking about every 10-15 minutes. It only happens when connected to my Wifi. My N7 does not wake at all. I have wiped the Cache and noticed my "Android System" hogging my battery stats.
I am trying to search what Apps I have settings for something like "sync only on wifi"... from there I should be able to find what is turning the screen on. I have BetterBattery Stats installed, and am trying to dig a little deeper there as well.
tanmack33 said:
I am in the same boat, Thegios.
No Wechat... No Daydream.
I have noticed my screen waking about every 10-15 minutes. It only happens when connected to my Wifi. My N7 does not wake at all. I have wiped the Cache and noticed my "Android System" hogging my battery stats.
I am trying to search what Apps I have settings for something like "sync only on wifi"... from there I should be able to find what is turning the screen on. I have BetterBattery Stats installed, and am trying to dig a little deeper there as well.
Click to expand...
Click to collapse
cant b wifi, , mine wakes up also when wifi is off and 3g is off and sync is off
I have tried with bbs as well but found notjing wrong
i've read all the reports of bugs, and the people with issues seem to have flashed the stock AOSP rom.. i dont have any of the issues described and the way i installed 4.2 was first flashing the takju 4.1.2 with nexus toolkit and then i got the 4.2 OTA from "about phone"->update.. oh and i have daydream activated.
For those of you with high android system usage, are you downloading music from Google pay music for offline usage? I did and I got this sudden increase. this has never happened to my phone before. Maybe Google play music needs update?
Sent from my Galaxy Nexus using xda premium
tanmack33 said:
I am in the same boat, Thegios.
No Wechat... No Daydream.
I have noticed my screen waking about every 10-15 minutes. It only happens when connected to my Wifi. My N7 does not wake at all. I have wiped the Cache and noticed my "Android System" hogging my battery stats.
I am trying to search what Apps I have settings for something like "sync only on wifi"... from there I should be able to find what is turning the screen on. I have BetterBattery Stats installed, and am trying to dig a little deeper there as well.
Click to expand...
Click to collapse
My problem is resolved by removing WeChat and daydream disabled...waited for like an hour and confirmed about the problem solution that worked for me.
You can try disabling that sleep mode apps in Apps settings.
Sent from my Galaxy Nexus using xda app-developers app
cldwar said:
You can try disabling that sleep mode apps in Apps settings.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
it didn't work
cldwar said:
My problem is resolved by removing WeChat and daydream disabled...waited for like an hour and confirmed about the problem solution that worked for me.
You can try disabling that sleep mode apps in Apps settings.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Your problem may have been resolved but wechat and daydream is not the solution to this as many of us aren't using either and still having this issue. I think I'm going back to bone stock 4.1.2 and going to let the OTA upgrade me to 4.2 and see what happens.
wechat is NOT the solution people, as the Google Code page suggest this is a sync issue that could be caused by a number of apps.
opensourcefan said:
Your problem may have been resolved but wechat and daydream is not the solution to this as many of us aren't using either and still having this issue. I think I'm going back to bone stock 4.1.2 and going to let the OTA upgrade me to 4.2 and see what happens.
wechat is NOT the solution people, as the Google Code page suggest this is a sync issue that could be caused by a number of apps.
Click to expand...
Click to collapse
Sorry to report this but my phone has been bone stock since I bought it, got the 4.2 OTA, not using wechat or daydream and I still have this issue.
I know there's another auto brightness thread but I think my problem is different. I'll turn it on, leave the phone in standby for a while, and when I use the phone again I find the auto brightness doesn't have the check mark there anymore? Has anyone else noticed this?
I was wondering why my battery was draining so fast when I was using it. That's when I realized my setting was at full brightness but the Auto had become unchecked so it was running at 100 constantly without auto adjusting. I've used the 100/Auto checked on all my other Samsung devices dating back to the Note 2 and S3.
I'm thinking it's a software glitch which will hopefully be fixed in a future update. If it is, I'll live with it for now...
I actually had the same issue and I found that the issue was related to game recorder app I just uninstalled and now is fine
Interesting... I don't have any kind of recorder apps so I'm kind of at a loss as to what other app could cause that...
diehardbattery said:
Interesting... I don't have any kind of recorder apps so I'm kind of at a loss as to what other app could cause that...
Click to expand...
Click to collapse
I'm suffering from this exact same issue. Very annoying because the auto brightness works well when it actually stays on.
NCSUgolfer01 said:
I'm suffering from this exact same issue. Very annoying because the auto brightness works well when it actually stays on.
Click to expand...
Click to collapse
For what it's worth, I started having other issues yesterday morning. When I first got the phone, and did the OTA, I did a factory reset as was widely recommended to do. Apparently it din't clear up everything.
What I ended up doing was, yesterday, I did another reset using the Samsung Smart Switch software. I backed up what I could, let it reset, and restored afterward. So far it's been 24 hrs and no issues.
I have the same problem with the auto brigthness with my galaxy S6 edge . but when i uninstall the car app from samsung its gone
maybe it works for you too
jekuper said:
I have the same problem with the auto brigthness with my galaxy S6 edge . but when i uninstall the car app from samsung its gone
maybe it works for you too
Click to expand...
Click to collapse
I'll try that and report back
jekuper said:
I have the same problem with the auto brigthness with my galaxy S6 edge . but when i uninstall the car app from samsung its gone
maybe it works for you too
Click to expand...
Click to collapse
I also uninstalled the car app and restarted the phone.
it was still happening, but now it ain't anymore.
if it does will post here again
godsboy7777 said:
I also uninstalled the car app and restarted the phone.
it was still happening, but now it ain't anymore.
if it does will post here again
Click to expand...
Click to collapse
Interesting.. car mode is the culprit? That's not the only bug in that app then. There's an option to auto close the app when the bluetooth connection is disconnected from the car.. it doesn't work for me.
But I'll just be sitting there doing something and if I'm in a dark room... WHAM I get blinded LOL...
I got a replacement today so I guess the saga continues...
diehardbattery said:
Interesting.. car mode is the culprit? That's not the only bug in that app then. There's an option to auto close the app when the bluetooth connection is disconnected from the car.. it doesn't work for me.
But I'll just be sitting there doing something and if I'm in a dark room... WHAM I get blinded LOL...
I got a replacement today so I guess the saga continues...
Click to expand...
Click to collapse
I installed Samsung Switch for pc and did a backup for my edge.
I then did a factory reset.
Restored the backup from Switch.
I also un-installed a Go battery saver application.
Since then no more auto-brightness switching itself off.
godsboy7777 said:
I installed Samsung Switch for pc and did a backup for my edge.
I then did a factory reset.
Restored the backup from Switch.
I also un-installed a Go battery saver application.
Since then no more auto-brightness switching itself off.
Click to expand...
Click to collapse
I did all of that, except for the app you removed. It behaved itself for a about 24 hrs and still came back. How long has it been for you?
jekuper said:
I have the same problem with the auto brigthness with my galaxy S6 edge . but when i uninstall the car app from samsung its gone
maybe it works for you too
Click to expand...
Click to collapse
diehardbattery said:
Interesting.. car mode is the culprit? That's not the only bug in that app then. There's an option to auto close the app when the bluetooth connection is disconnected from the car.. it doesn't work for me.
But I'll just be sitting there doing something and if I'm in a dark room... WHAM I get blinded LOL...
I got a replacement today so I guess the saga continues...
Click to expand...
Click to collapse
diehardbattery said:
I did all of that, except for the app you removed. It behaved itself for a about 24 hrs and still came back. How long has it been for you?
Click to expand...
Click to collapse
It has been more than 24 hours no probs, but I also have to say since doing this I have not touched the auto checkbox or slided the bar left or right at all.
did you?
I'm pretty sure I didn't... I don't remember doing anything of the sort LOL...
diehardbattery said:
I'm pretty sure I didn't... I don't remember doing anything of the sort LOL...
Click to expand...
Click to collapse
Have you updated all apps recently?
What is your specific phone model number?
All updates were done right after the restore. SM-G925T
diehardbattery said:
All updates were done right after the restore. SM-G925T
Click to expand...
Click to collapse
My phone model is SM-G925F
I've a SM-T700 Tab S 8.4 running lollipop, and I've recently noticed a bug. I don't know if it's new since the lollipop upgrade, but I didn't notice it before.
I often use it to read in the dark, so I turn the brightness down and set the touch keys to never light up. However, after a while the lights come on and stay on until the setting is altered again.
Anyone else getting a similar issue?
Hi! I think it's a common bug. I have the same problem and read that many people have it.
I'm not aware of any permanent solution, so for now i keep mine at 1.5 seconds (I'd prefer them off, but thats the best I could find!)
PS: Sorry for my English!
No need to apologize. Your English is perfect.
Sent from my SM-N900V using XDA Free mobile app
If the problem's widespread, what devices/ROMs has it been seen on? Is it Galaxy-specific, I wonder.
Same issue here
rosyatrandom said:
I've a SM-T700 Tab S 8.4 running lollipop, and I've recently noticed a bug. I don't know if it's new since the lollipop upgrade, but I didn't notice it before.
[....]
Anyone else getting a similar issue?
Click to expand...
Click to collapse
Same problem here, only on mine the only way I've found to turn them off once they come on is to restart the device. What a hassle.
I have the same problem, regardless of what I set the duration to. It never did this under Kitkat.
Mythra said:
Same problem here, only on mine the only way I've found to turn them off once they come on is to restart the device. What a hassle.
Click to expand...
Click to collapse
yeah same here, only fix I found was a reboot. think I flashed the Brazil version.
nismofreak said:
yeah same here, only fix I found was a reboot. think I flashed the Brazil version.
Click to expand...
Click to collapse
Hi! I have same problem with Brazil version also.
Might it be related to that version only?
pantezuma said:
Hi! I have same problem with Brazil version also.
Might it be related to that version only?
Click to expand...
Click to collapse
could possibly be... anyone with this issue not on the Brazil version?
Yes, same problem here with my new Samsung Tab S 8.4 SM-T700, stock 5.0.2
Putting it to 1.5 secs is the best I can do for now. I'm looking around on the app store to see if there's a different app to control this that might work (aside, the Galaxy S6 came with no way to turn these off and you have to use a separate app to do this).
nismofreak said:
could possibly be... anyone with this issue not on the Brazil version?
Click to expand...
Click to collapse
Mine is stock US (or whatever the official region is).
Mythra said:
Same problem here, only on mine the only way I've found to turn them off once they come on is to restart the device. What a hassle.
Click to expand...
Click to collapse
No need to restart/reboot, for me if I change the setting to something else (e.g., 1.5 secs etc) and then back to OFF it'll work for a while before it stays on permanently again.
levon9 said:
No need to restart/reboot, for me if I change the setting to something else (e.g., 1.5 secs etc) and then back to OFF it'll work for a while before it stays on permanently again.
Click to expand...
Click to collapse
I tried that with mine... won't work: no matter what I change the setting to they just stay on until I restart the device. I created a ticket with Samsung support last week, but no response from them so far.
Ah .. ok, that's interesting, thanks for sharing. Hopefully Samsung will issue a fix in the next update. Nice tablet otherwise.
I'm sure most, if not all, knew this, but it is definitely a software issue. I flashed CM 12.1 the other day and the touch keys stay off. Perhaps someone can look into the stock firmware and see if there's a way we can fix it ourselves?
Hey guys, I've had the same bug since upgrading to Lollipop and I found out it seems to be a bug with the power saving mode. If I turn it off, the bug stops happening. I'm also testing power saving mode with the "turn key lights off" option unchecked, and it seems to be working ok. This option can be found under settings, power saving, restrict performance.
I'll keep testing. If anyone tests it too please reply with your findings!
giancian said:
Hey guys, I've had the same bug since upgrading to Lollipop and I found out it seems to be a bug with the power saving mode. If I turn it off, the bug stops happening. I'm also testing power saving mode with the "turn key lights off" option unchecked, and it seems to be working ok. This option can be found under settings, power saving, restrict performance.
I'll keep testing. If anyone tests it too please reply with your findings!
Click to expand...
Click to collapse
I never use power saving mode, because I'm almost always near a charger, and I also had this issue. I don't think power saving mode has much to do with it. Not directly, at least.
Hi, I'm not using power savings mode, but have the same problem, so I'm not sure this mode is a factor (at least a sole factor).
Hi to all.
Somenone previously suggested this app:
https://play.google.com/store/apps/details?id=com.notquiteinsane.galaxybuttonlights&hl=en
I've been using it with and without power saving mode for 4 days and so far so good.
pantezuma said:
Hi to all.
Somenone previously suggested this app:
https://play.google.com/store/apps/details?id=com.notquiteinsane.galaxybuttonlights&hl=en
I've been using it with and without power saving mode for 4 days and so far so good.
Click to expand...
Click to collapse
Hi,
I suggested this app earlier upstream, however, it ended up not working for me. Not sure how it's working for you, but happy it is. (FWIW, I never use power savings)
after each lock when i turn the screen on with double tap or power button screen is unresponsive for good 3 seconds. This started happening after the latest camera fix update. When if i use aod and use the fingerprint through the aod this doesnt happen. tried reboot and factory reset with fresh install (no backups) tried safe mode. Same thing happens.
S20 plus exynos.
Yup happening to me too (s20+ exynos). For me the time of unresponsiveness is around 1-2 seconds. Happened after the latest update.
Yes, have been facing the same issue since "ATCH" update.
Yeah has been driving me nuts. Same problem.
I'm surprised this isn't gaining more traction? Can't be the only few experiencing this!?
Glad to see it's not only my device. Waiting for fix.
I have similar situation
I'ne noticed the same after the last update.
Chris_c81 said:
Yeah has been driving me nuts. Same problem.
Click to expand...
Click to collapse
Seriously when it happens(which it does like 90% of the time i wake the screen) i feel like i'm using a cheap 100$ phone and not a 1000$+ flagship.
Chris_c81 said:
I'm surprised this isn't gaining more traction? Can't be the only few experiencing this!?
Click to expand...
Click to collapse
This. I'm afraid if it goes unnoticed by samsung we may have to face this issue for longer.
BTW any user here with Snapdragon that has this issue. Or is this exynos only ?
anfederin said:
I have similar situation
Click to expand...
Click to collapse
Mine is Exynos
sjandroiddeveloper said:
Seriously when it happens(which it does like 90% of the time i wake the screen) i feel like i'm using a cheap 100$ phone and not a 1000$+ flagship.
This. I'm afraid if it goes unnoticed by samsung we may have to face this issue for longer.
BTW any user here with Snapdragon that has this issue. Or is this exynos only ?
Click to expand...
Click to collapse
Is there any channel to communicate this bug to Samsung? Anyone know?
Chris_c81 said:
Is there any channel to communicate this bug to Samsung? Anyone know?
Click to expand...
Click to collapse
There is an app called samsung member where you can send error reports. I have already done it, its currently under review. I suggest everyone affected to do it.
sjandroiddeveloper said:
There is an app called samsung member where you can send error reports. I have already done it, its currently under review. I suggest everyone affected to do it.
Click to expand...
Click to collapse
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
turn off the battery optimized for apps: com.samsung.android.biometric.
Go to Settings>Apps>Select "Special Access" from three dot menu>Optimise Battery Usage>select All from drop down menu>Search for "com.samsung.android.biometric"> Turn it off and Restart.
Click to expand...
Click to collapse
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
Did accordingly as above.
For a moment it felt like the issue is resolved!
But after checking several times I can confirm the issue still exists.
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
Unlock is now super faster. Issue is completely gone. Thanks [emoji4]
Sent from my SM-G986B using Tapatalk
verynuclear said:
Unlock is now super faster. Issue is completely gone. Thanks [emoji4]
Click to expand...
Click to collapse
While using the sidekey and turning off and on the screen and checking consecutively, the unresponsiveness persists in mine.
Virgo_Guy said:
While using the sidekey and turning off and on the screen and checking consecutively, the unresponsiveness persists in mine.
Click to expand...
Click to collapse
Have you restarted the phone? It didn't work until I restart mine.
Sent from my SM-G986B using Tapatalk
verynuclear said:
Have you restarted the phone? It didn't work until I restart mine.
Click to expand...
Click to collapse
Ofcourse I did. In fact restarted one more time since it didn't resolve after the first restart, post disabling the optimization.
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
I did this already and while it feels like fingerprint is faster, unfortunately this is a screen issue. You see if the screen is off and i put the finger in the correct spot it always scans my finger without any lag. The issue is occurs when -
a) I have unlocked the phone using above way, then the screen becomes unresponsive right after unlocking.
b) The screen is off and i either press the power button or double tap to wake, then the screen will be unresponsive and its during this time the fingerprint scanner doesn't scan (because the scanner doesn't know it needs to scan since the touch is unresponsive)
so TL;DR its not a FP scanner issue.
I am quiet sure Samsung is already addressing this issue for next update.