Develop Bugs

Fingerprint scanner issue after upgrade to 9.0

So I finally took the jump to Pie. One of the smaller issues I have that I didn't before is when trying to set up my fingerprints again, I get an error on the last press which tells me to try again or try another finger.

Yes, an issue for me also. Sometimes it just does not work and other times it tells me the fingerprint sensor is dirty which it is not. Fingerprint sensor issues have been reported by others too after installing Pie. It does not seem to me to be as common as the notification issues with Pie, (which I also have), but it is talked about. I also did a factory reset a couple days after installing 9.0 which did help a couple of apps to work better but did not help the fingerprint or notification problems.
The fingerprint issue is weird as sometimes it is so bad, I think I will not be able to keep the phone, just will not work at all. Then for no discernible reason it will start working fine. It is not just a pain to have to use another login method every time the phone needs to be woken up, but I also use fingerprint sign in for a few apps and it is much harder to have to enter one of my random 14 character passwords when the fingerprint won't work.

Try to put your Ambient display Always on... see if it fixes the fingerprint problem (Google is aware of this issue) till google issues a permanent fix.

Wasn't that only a workaround for people who had fingerprint lag? I don't think it was for fingerprint reading issues.
I did notice a lot more fingerprint reading errors with Pie then redid my fingers and all has been fine.
itzik_man said:
Try to put your Ambient display Always on... see if it fixes the fingerprint problem (Google is aware of this issue) till google issues a permanent fix.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk

Weird Phone app glitch with the keypad

I'm getting a weird stock Phone app glitch with the keypad when on a call. If I dial a number and select keypad, the animation for the keypad coming up is nice and smooth. If, however, I put my ear next to the earpiece for the proximity sensor to turn off the display, move my head away so the display turns on again, and select the keypad again, the animation becomes much slower and looks choppy. I tried to replicate this on my wife's Pixel 3 and her phone doesn't do it. I cleared Phone app storage data and cache, restarted my phone, and I can still reproduce the bug. I'm on the latest March OTA. Would you guys please test it and see if you're able to reproduce the same weird glitch?

is your wifes phone also on themarch OTA?
3 or 3XL?

virtyx said:
is your wifes phone also on themarch OTA?
3 or 3XL?
Click to expand...
Click to collapse
Her phone is still on the February update and it's the Pixel 3. After further testing, it only happens after the proximity sensor is used to turn the display off and then back on. If I use the power button to turn the display off and then back on it doesn't happen. I also tested in Safe Mode and I can still replicate it. I sent feedback to Google. Not sure if anyone will care but it's a very unsual glitch.

I switched to Android Q beta 1 and it was still doing it. I ended up having to wipe everything to go back to Android P, and I didn't restore from the cloud. To my surprise it wasn't doing it, but now after some time passed, it's back to acting up. I'm on the latest March OTA. Would you guys please test it and see if you're able to reproduce the same weird glitch?
VIDEO LINK: https://photos.app.goo.gl/9U4WQXnLdHG1RSke8

Proximity sensor ignored partially?

I have a weird issue with my A2 Lite.
I tried couple of ROMs so far and it's all the same.
When I receive a call and answer it, I bring the phone to my ear and I can see that display goes off - that's good. But, despite keeping the phone close to my ear, the flash light turns on, bt or even airplane mode so it disconnects the call, it changes the screen brightness or mutes the mic during the call. It's like touch sensor was alway on with display off, so I can't even see what I'm touching and switching.
I even went back to stock MIUI to be able to run system check with *#*#64...etc. and proximity sensor works fine.
My problem is similiar to this one: https://forum.xda-developers.com/mi-a2-lite/help/lockscreen-notification-sound-proximity-t3867872.
This drives me crazy!!!
Did anyone have this problem or knows some tricks to fix it (beside smashing the sh..t on the wall)?

I experience the same thing sometimes with stock rom

keyone72 said:
I experience the same thing sometimes with stock rom
Click to expand...
Click to collapse
That - I didn't expect...
But it has to do something with the Android or kernel maybe. How does it come, that screen is being turned off but not locked (meaning insensitive for touches)?
Weird...
And I'm almost sure, it wasn't like this before... before I installed one of custom ROMs (Arrow maybe). But since then I even went back to stock Pie, so if any firmware/kernel manipulation caused it, with stock - it should've fixed.
I'm starting to dislike daisies...

3 screen off issues

Hi everyone.
I have a note 10 + 256 go exynos from france.
SInce about last update one ui2.5, I have seen 3 issues which I think are related.
- AOD tap to show not working
- Double tap to wake not working
- When I remove the phone from the ear during a call the screen does not light up anymore whereas before yes.
I almost returned the phone in warranty a short time ago because my screen only registered two fingers,a few days later I received an update that fixed this problem.
For these 3 problems I tried 3 things :
- Update touch screen firmware via *#2663#
- Factory reset
- Reflash the stock firmware with odin and frija
I also have another problem a few times a day the screen freezes, I have to lock unlock the screen and it works again..
Do you think it's a software problem or a hardware problem (damaged screen, damaged sensor or other)?
Please help me thanks.

Lol, firmware and/or software; maybe a settings or permissions issue as there are many. Hardware rarely fails unless it receives severe abuse. You can perform some of the builtin hardware tests just to be sure.
Try using the factory load if the apk in question has been updated or wait for an update that fixes it. Be sure to check the Gallaxy Store for updates.
I'm still running on Pie because it's fast, stable and functional. No scope storage that I don't want or need.
Once you get an OS optimized and running well there's little advantage to upgrading many times unless the new OS is really worth it.
Many times it's not... I'm still running W7 too.
You invariably end up with new issues, hunting down all new glitches and worse, since it's new there not many online solutions.

Thank you for your help.
I mentioned the 3 main methods of fix but of course before that I had already tried the basic things like clearing the system cache, checking the permissions of the AOD application as well as deleting this data.
I also checked the sensors with * # 0 * # but I did not find anything problematic
I even tried to flash the november update with odin and frija and I got a soft brick, so I don't even dare to try a downgrade firmware, I don't have the knowledge, I read that I had to keep the same bootloader and I get lost in the different firmwares

Those are all system apks that run in the background.
Is Android System configured correctly?
Try clearing it's data and of course the system cache.
A hard reboot as well.
It's interesting you lost the proximity sensor.

Thanks.
Yes I have cleared the system cache several times, android system too. I even did a hard reset. I think more and more of a hardware problem, because all these functions are linked to the fact that the screen does not wake up by touch when it is turned off.
the proximity sensor still works at least partially because it flashes well during a call and turns off the screen when I put the phone to my ear, but no wake up when I take it off my ear.

cyroko said:
Thank you for your help.
I mentioned the 3 main methods of fix but of course before that I had already tried the basic things like clearing the system cache, checking the permissions of the AOD application as well as deleting this data.
I also checked the sensors with * # 0 * # but I did not find anything problematic
I even tried to flash the november update with odin and frija and I got a soft brick, so I don't even dare to try a downgrade firmware, I don't have the knowledge, I read that I had to keep the same bootloader and I get lost in the different firmwares
Click to expand...
Click to collapse
cyroko said:
Thanks.
Yes I have cleared the system cache several times, android system too. I even did a hard reset. I think more and more of a hardware problem, because all these functions are linked to the fact that the screen does not wake up by touch when it is turned off.
the proximity sensor still works at least partially because it flashes well during a call and turns off the screen when I put the phone to my ear, but no wake up when I take it off my ear.
Click to expand...
Click to collapse
If it happened after the firmware update... it's in the firmware or software.
Bad firmware can sometimes blowout a cpu but doubt it damaged the hardware controlling just that one feature of the touchscreen.
If that was the case the touchscreen wouldn't work at all.
Maybe the firmware is ok but got corrupted during the download or flash.
A defective memory module could corrupt the load but again that rarely happens.
So back to the firmware/software/settings...
Maybe someone here has seen this before or has a better idea to sort it out.

Honestly I'm not sure it's exactly after an update.
It's just that it's not functions that I use very often. I don't call a lot of people and most of the time I use very little Aod and double tap2wake.
Usually when I grab my phone to use it I unlock it directly with the fingerprint.
when i mentioned the problem where my screen only recognized two fingers at this time , aod and dt2w were already weird as it only worked on the top half of the screen not on the bottom half ..the update solved the problem for the 2 fingers but not for the fact that aod and dt2w only works on the upper half.
Now for some time aod and dt2w no longer work at all no matter where I touch the screen.
I want to clarify that I use a screen protector with loca glue but that it is from the beginning and that it has never been a problem before.
I know this is a weird problem thanks for your patience

I never use a lock screen or the fingerprint sensor.
There may be a conflict because that... disable and see if that helps.
The screen could goof up the proximity sensor. Probably not but next time it's off, check it out.
No worries; these devices fascinate me.
Hope you sort it out; eventually one usually does

I never use a lock screen or the fingerprint sensor.
There may be a conflict because that... disable and see if that helps.
The screen could goof up the proximity sensor. Probably not but next time it's off, check it out.
No worries; these devices fascinate me.
Hope you sort it out; eventually one usually does

2x post

when i did the factory reset it was the first thing i tried before even resetting a password but it didn't work anyway.
For the screen protector I use the same brand from the beginning and it has never caused me a problem of this kind, but maybe this one is defective ..
I would have to remove it to try but I have lazy to change it again because I had to change it twice in a little while.
Hoping that by dint of applying the loca glue I haven't damaged anything.
Thanks

Nah the glue didn't hurt anything; it's well sealed.
The tap on AOD I never use but I double tap to turn the screen on/off. If I lost that I be witch hunting.
Try increasing the touch sensitivity if you haven't already... and make sure no other apps have accessibility permissions that could conflict. Same for device administrator permissions.
Try it in safe mode as well.

Green tint only on unlocking device - acceptable?

I bought this used s9 for quite affordable price. Everything looked fine during testing except a greenish shade which happens only when unlocked and happens for like a second.
On searching internet, i found threads, yt videos by a number of people, almost all claiming that it is an update consequence. My questions are
1. Is it a software issue? If yes, can I expect some wayto solve - official ota or root and custom or old rom (if possible at all)?
2. If not software issue, is it a software induced hardware issue? Any way to repair without paying full for display?
2.1 If i get it replaced somehow, will itcome back again?
3. In any case, if I don't get it repaired, how long can I expect the deviceto be functional; ie before this green shade becomes permanent instead of being intermittent making device unusable?
Thank you

If it only happens for a second the only thing I be concerned about by the possibility of a rootkit or virus.
If running on Android 9 or higher and you did a factory reset already, that should have killed any unwanted critters.
Do a display check with ScreenTest. If it passes it should be good to go and just a transient glitch.
You've heard of The Matrix, right?

blackhawk said:
If it only happens for a second the only thing I be concerned about by the possibility of a rootkit or virus.
If running on Android 9 or higher and you did a factory reset already, that should have killed any unwanted critters.
Do a display check with ScreenTest. If it passes it should be good to go and just a transient glitch.
You've heard of The Matrix, right?
Click to expand...
Click to collapse
Hahah
This is something different. I asked a reseller and he said that such displays may last anywhere from 1 hour to 1 year.
Internet is filled with such questions.
Can you please help answering other questions if not this one, like if downgrading to older android possible or not?

The green only lasts for a second or so when opening the lock screen?
Never any other time?
Then it's not hardware.
AMOLED displays can last for many years. ScreenTest gives you a good idea of it's condition. Generally failure is gradual with the blue pixels failing first, red last.
The boot loader version dictates if you can downgrade or not.

...

blackhawk said:
The green only lasts for a second or so when opening the lock screen?
Never any other time?
Then it's not hardware.
AMOLED displays can last for many years. ScreenTest gives you a good idea of it's condition. Generally failure is gradual with the blue pixels failing first, red last.
The boot loader version dictates if you can downgrade or not.
Click to expand...
Click to collapse
So far, only immediately after unlocking. Haven't used much tho.
People say temp fix to all such issues is to Enable Always On display and double tap to wake screen instead of using Power button.
Can you ease tell which ScreenTest app it is? Playstore shows several with similar names.

tarun0 said:
So far, only immediately after unlocking. Haven't used much tho.
People say temp fix to all such issues is to Enable Always On display and double tap to wake screen instead of using Power button.
Can you ease tell which ScreenTest app it is? Playstore shows several with similar names.
Click to expand...
Click to collapse
Like I said if it's transient it's no issue.
This is the one I use:

Hi.
My s9 has this problem which everything turns green or worst, depending on the brightness level.
I can repeat the bug 100% of the time: just use the power button to turn off the phone two times: one to put into black screen and again to turn on. Then the screen misses some horizontal lines and is all buggy.
I shall record a video to share my problem but again, this can only be avoided by using aways on display to turn on the phone and then all goes back to normal.

spamtoaster said:
Hi.
My s9 has this problem which everything turns green or worst, depending on the brightness level.
I can repeat the bug 100% of the time: just use the power button to turn off the phone two times: one to put into black screen and again to turn on. Then the screen misses some horizontal lines and is all buggy.
I shall record a video to share my problem but again, this can only be avoided by using aways on display to turn on the phone and then all goes back to normal.
Click to expand...
Click to collapse
Try clearing the system cache.
A hard reboot.
Try in safe mode.
A factory reset may help but if that fails try flashing to the same version. If Android 8 or lower it could be caused by a rootkit that a factory reset won't purged. However this isn't a typical symptom nonetheless the firmware maybe corrupted.
If none of the above works it's a hardware failure, likely the display.