Develop Bugs

[Q] Touch Key duration bug - lights stay on when set to stay off

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)

Lots of different small issues

Hi all
I have been using this phone for a month, and I have experienced a lot of different small issues, I hope someone may have solution to them.
Phone:
Mi A2 Lite, rooted (Magisk) Android one pie, January update. Has a screen protector.
Apps:
Here are some apps that I think may cause the issue that I mention below, these apps are Nova and datally. Really can't think of a third one, I don't use any cleaning app or battery performance app.
Issue:
1. Typing experience is horrible. Using stock google input, the keyboard is not very sensitive and accurate. The letter just can't be recognized even though I am sure I have pressed the key and pressed the right key. So my typing is really slow, the key doesn't display immediately (it does seem to have a delay), and for some reason I always type wrong and missing some letters, so gotta use backspace a lot.
2. It always wakes up randomly in my pocket, so I may take the phone out with torch on and airplane mode on without my awareness.
3. When I am on a call, I can accidentally press some random on screen keys.
4. The background apps AWALYS get killed, even though I have turned the battery optimization off globally, and the individual apps that I never want to be killed.
5. Messaging service apps have huge delay when delivering the notification. It may only show when I open the app. Used PNF app but couldn't fix the problem.
Does anyone have the same issue and know the fix?
I hope it is only the software problem (Pie system) and maybe I can fix it by flashing a better rom, but I don't seem to find a stable official custom ROM for Mi A2 Lite (even lineage OS is unofficial)
Many thanks

luckyvictor said:
Hi all
I have been using this phone for a month, and I have experienced a lot of different small issues, I hope someone may have solution to them.
Phone:
Mi A2 Lite, rooted (Magisk) Android one pie, January update. Has a screen protector.
Apps:
Here are some apps that I think may cause the issue that I mention below, these apps are Nova and datally. Really can't think of a third one, I don't use any cleaning app or battery performance app.
Issue:
1. Typing experience is horrible. Using stock google input, the keyboard is not very sensitive and accurate. The letter just can't be recognized even though I am sure I have pressed the key and pressed the right key. So my typing is really slow, the key doesn't display immediately (it does seem to have a delay), and for some reason I always type wrong and missing some letters, so gotta use backspace a lot.
2. It always wakes up randomly in my pocket, so I may take the phone out with torch on and airplane mode on without my awareness.
3. When I am on a call, I can accidentally press some random on screen keys.
4. The background apps AWALYS get killed, even though I have turned the battery optimization off globally, and the individual apps that I never want to be killed.
5. Messaging service apps have huge delay when delivering the notification. It may only show when I open the app. Used PNF app but couldn't fix the problem.
Does anyone have the same issue and know the fix?
I hope it is only the software problem (Pie system) and maybe I can fix it by flashing a better rom, but I don't seem to find a stable official custom ROM for Mi A2 Lite (even lineage OS is unofficial)
Many thanks
Click to expand...
Click to collapse
Try to update I never had any of those issues

I have also these problems. I have February update.

madmanwild said:
I have also these problems. I have February update.
Click to expand...
Click to collapse
Do you have all these problems? or just one or two? After seeing my configuration/apps that I installed, do you think is it app related or system related?

rob420p said:
Try to update I never had any of those issues
Click to expand...
Click to collapse
not even one of these? Your background app never get killed?
Are you using Stock Android One? did you root your phone?

luckyvictor said:
Do you have all these problems? or just one or two? After seeing my configuration/apps that I installed, do you think is it app related or system related?
Click to expand...
Click to collapse
all these problems without wakes up in pocket. killing the background application is the biggest problem for me (I use a lot of smart home app- eWelink,Room Heat,Magic Home) and it's horrible. ewelink starts 5sec after kill, Room Heat - frequent crash like a white screen...
the next problem is huge delay when delivering the notification....
I am on Stock Android One-February update,I'm allowed only cam2api...

madmanwild said:
all these problems without wakes up in pocket. killing the background application is the biggest problem for me (I use a lot of smart home app- eWelink,Room Heat,Magic Home) and it's horrible. ewelink starts 5sec after kill, Room Heat - frequent crash like a white screen...
the next problem is huge delay when delivering the notification....
I am on Stock Android One-February update,I'm allowed only cam2api...
Click to expand...
Click to collapse
You have battery optimization off? any battery improvement app? I think all these is because the 'intelligence' in Android is playing up, it doesn't understand exactly how we use the app. However, even have it turned off, the problem exists....

luckyvictor said:
not even one of these? Your background app never get killed?
Are you using Stock Android One? did you root your phone?
Click to expand...
Click to collapse
I am on stock but I do have root.havent done much modification yet waiting for twrp

rob420p said:
I am on stock but I do have root.havent done much modification yet waiting for twrp
Click to expand...
Click to collapse
Don't understand why there is such different, did you have battery optimisation off and all time since the first day you use the device?

luckyvictor said:
Don't understand why there is such different, did you have battery optimisation off and all time since the first day you use the device?
Click to expand...
Click to collapse
Honestly I don't think so I really haven't messed with the battery besides putting a %

luckyvictor said:
You have battery optimization off? any battery improvement app? I think all these is because the 'intelligence' in Android is playing up, it doesn't understand exactly how we use the app. However, even have it turned off, the problem exists....
Click to expand...
Click to collapse
Yes, all off - battery adaptation and manually set no optimization on my app...

Lock Screen unlocking problem guys, screen is unresponsive for 3 seconds.

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.

update May 2020 android 10

Everyday i always check for firmware update and now i have received new update,any body receive the update too? I think its not 10.0.4.0 version (i have reflashed to android 9 because bug Android 10.0.4.0),maybe the latest one but i dont know what the build number.do you have receive too ?

I confirm I also received updates today.

Nico100g said:
I confirm I also received updates today.
Click to expand...
Click to collapse
This is okay to update? Because before this i have problem with mobile signal 10.0.4.0

I don't know, I haven't tested yet. For now, I can say that the update is small, but it installs for very long almost 30 minutes (updated from version
11.0.4.0).
However, it installed without a problem.
The new version is 11.0.5.0 and May patches.
EDIT:
The LTE signal is stronger.
Camera sound error has been fixed
Screen Lock/Unlock sounds is work now
I haven't noticed other corrections

Nico100g said:
I don't know, I haven't tested yet. For now, I can say that the update is small, but it installs for very long almost 30 minutes (updated from version
11.0.4.0).
However, it installed without a problem.
The new version is 11.0.5.0 and May patches.
EDIT:
The LTE signal is stronger.
Camera sound error has been fixed
Screen Lock/Unlock sounds is work now
I haven't noticed other corrections
Click to expand...
Click to collapse
Looks good they have fixed bugs

Installed and can say that it seems lots faster as well
Something else I found you can change acent colour to Ocean now sure that this was not there before looks like the colour on the pixel

rockycocky said:
Installed and can say that it seems lots faster as well
Something else I found you can change acent colour to Ocean now sure that this was not there before looks like the colour on the pixel
Click to expand...
Click to collapse
How about microphone bug? Have fixed?

Wimd said:
How about microphone bug? Have fixed?
Click to expand...
Click to collapse
Just tested this installed a voice recorder app, seems to record audio and play back ok, I tested before but forgot my BT headset was on, so when I tested i could not hear as headphones are in another room

Plz,test two buton gesture, and report,on android 9 working ok on android 10 for me not working,i hope fix that bug

miloske83 said:
Plz,test two buton gesture, and report,on android 9 working ok on android 10 for me not working,i hope fix that bug
Click to expand...
Click to collapse
Just turned on 2 button gestures, and tested seems to work fine, I was able to do all the things in the tutorial

Just update,and for me two buton navigation not working, when swipe to next app phone just go crazy and open and close apps

Sim card disabling option is fixed and you can now disable them.

**** you xiaomi not fixed swipe to unlock some time must swipe 4or5 times to unlock wtf

Wow my update notification is gone ,i think its periodic offer for random user,i want to update now but the update is gone ?

Wimd said:
Wow my update notification is gone ,i think its periodic offer for random user,i want to update now but the update is gone
Click to expand...
Click to collapse
Same Here, Update Is Gone...

I got the update alright but it is back to the usual 'Installation Failed' nonsense. Uninstalling magisk doesn't make any difference. Haven't had that problem for a long while now - but it's returned to haunt me again. On the positive side though, 11.0.4.0 is working so well for me I don't want to interfere with it.

Charging issue
Does this update fix a slow charging issue?

Just got this update on my Android 9 March 20 Mi A2 Lite here and going for it. Will see how it goes and report back...

Updated from Andoid 9 (Security March) to Android 10 (Security May). Works at the momet fine.
Updated about 20 min ago.
---------- Post added at 02:25 PM ---------- Previous post was at 02:22 PM ----------
Nico100g said:
EDIT:
The LTE signal is stronger.
Click to expand...
Click to collapse
Signal strength has remained exactly the same...

p3108 said:
Just got this update on my Android 9 March 20 Mi A2 Lite here and going for it. Will see how it goes and report back...
Click to expand...
Click to collapse
I can still customise my Pixel

Question Issues afteratest update

S21fe updated to UI5.
Couple of issues.... Fingerprint reader sometimes doesn't work when phone hasn't been used for some time. When it happens I need to double tap the screen to wake it up and then scan my fingerprint again.
Also "back" gesture (where I swipe up from the right bottom of the screen) sometimes instead of going back brings up the list of background apps.
Both issues very annoying.
Anyone else experienced anything similar?

Try clearing the system cache. Double check all settings. If that flaws things get more complicated...
A factory reset may be needed, but hard to say if it will resolve the issues. Someone will need to try the latter if the former doesn't work. A global reset of settings is a less drastic option but it may not be enough and still take a lot of time.
This is one reason why I spurn upgrades on a platform that's fulfilling its mission. Lol, I'm still using UI 1.5, no glaring issues.
Unfortunately with latter versions an upgrade may resolve flaws in earlier post >1.5 variants. Tough choice once you are on Android 11 as there's no roll back on stock Samsung's for that. I wasn't locked into using 11 on my N10+'s and never will load it. 12 is even worse.
Roll back is an option for you if bootloader wasn't upgraded too. Eventually Samsung will fix it if it's a firmware/software glitch but don't hold your breath for that

blackhawk said:
Try clearing the system cache
Click to expand...
Click to collapse
With each major update, I always clean the system cache from the recovery !

jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
That may not be enough if going from 11 to 12, etc.
Rule #1 - if the OS is fast, stable and fulfilling its mission let it be! You have little to gain and a lot to lose. Although there was a big security hole in 12, not sure if it was patched already or if the patch is in what you just install. Oddly that hole isn't in 9-11.
Gookill is a mess...

I have the same problem with fingerprint unlocking. It simply doesn't work (if I press the side button, it works). Some hours ago I wiped the system cache and after that, I didn't notice the described problem. I will see in the next few hours.

Now I changed "Fingerprints -> Show icon when screen is off" to "Tap to show" instead of "On always on display" which was the default after the upgrade to Android 13.
UPDATE: The phone still has the same problem. Sometimes it simply doesn't allow it to unlock with a fingerprint. The screen is locked as hell. Only the side button unlocks it.

If you go to Lock screen>Always On Display>Show always, does that solve your problem? Mine was set to "show for new notifications" only and the fingerprint icon would disapperar after locking it.

Mine was set to "Show for new notifications". As you suggested, I changed it to "Show always" and we will see, how it works. In my opinion, it is better to show display only when something happens. But something changed and problems occurred.

Report: it didn't help. I have found out that the issue appears if the phone is locked for a while and then a notification comes. This is the reason why this problem exists also while using Android Auto. It creates a notification when it connects ... and then the phone can be unlocked with a fingerprint until the side button is pressed. I'm sure this is a bug that didn't exist before the upgrade to Android 13.

no such issues here with the eu version. definitely an upgrade in every way.

After 3 days with Android 13 on snapdragon variant, only two minor issues found here : slow charging (2h20 from 0 to 100, less than 2h before) and an "unauthorized action due to modified device" screen when rebooting, disappearing by touching "OK" button. Don't know what is unauthorized but... well. I was rooted before, now stock unrooted and relocked bootloader. It doesn't seems to lock something, everything I use is working.

I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.

d0j0m0j0 said:
I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.
Click to expand...
Click to collapse
The recent update with the December security patch seens to have resolved this issue for me.
Edit: scratch that, still not fixed...
Edit2: turning off lock scrern mods in Galaxy MaxHz seems to help.

jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
How does one do that?

xda-eh said:
How does one do that?
Click to expand...
Click to collapse
It's on the boot menu on Samsung's.

blackhawk said:
It's on the boot menu on Samsung's.
Click to expand...
Click to collapse
You're referring to accessing the recovery mode as explained here?

xda-eh said:
You're referring to accessing the recovery mode as explained here?
Click to expand...
Click to collapse
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.

blackhawk said:
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.
Click to expand...
Click to collapse
The link I provided and the one you did refer to the same thing. Only difference is my link also provides a way to do it via ADB. In any event, thanks for your response.