Flashed Ace2 to OxygenOS A.08 and updated to A.10, problem still persists.
Happens both with auto brightness enabled and disabled.
gavebim144 said:
Flashed Ace2 to OxygenOS A.08 and updated to A.10, problem still persists.
Happens both with auto brightness enabled and disabled.
Click to expand...
Click to collapse
Was this issue also present on ColorOS?
Disable always on display
Any unlock securities
Fingerprint, pin, code etc..
I haven't encounter any screen flashing
I have same issue, tried turning all off, did help, but i need fingerprint unlock... Autobrightness does not work at all, just dimms the screen a bit when turned on, and goes bit up when turned off, no changes in light or dark room
So i believe i figured it out, it is connected to always-on display features, which includes animation for fingerprint unlock. There is an option to turn off animation for fingerprint when display turned off, but then you have to turn on the screen before using fingerprint...
Also this phone gets pretty warm when only looking youtube or browsing, when on 120Hz refresh rate. I used setedit app to reduce it to 90Hz, much better battery life and no heat...
One last solution for the screen flickering, turn off always-on display, and turn off fingerprint animation only, it is under security/fingerprint/fingerprint animation setting, just choose none, it still litghs up the fingerprint, but has no animation, and most important, no screen flicker...
The same problem, flashing, removing the fingerprint, and using the pattern, the problem is gone
Yeah, it started again be me, so no lighting for fingerprint, and then works fine... Just turning off animation did the trick for short time
zidoon said:
The same problem, flashing, removing the fingerprint, and using the pattern, the problem is gone
Click to expand...
Click to collapse
Do you have region lock too?
jopac84 said:
Do you have region lock too?
Click to expand...
Click to collapse
Yes, I had a region lock, after contacting the seller. It was opened with TeamViewer, now 3 weeks. There are no region lock messages.
So the seller could remove it? Mine keeps saying only oneplus can remove it. Did you what he did? I am nit sure if it completely removed or just blocked... The bigger issue is these software issues, especially flickering which could damage the screen... I wonder if these issues exist on all oxygen os phones, or only on these flashed from color os
jopac84 said:
Yeah, it started again be me, so no lighting for fingerprint, and then works fine... Just turning off animation did the trick for short time
Click to expand...
Click to collapse
So turning off lighting for fingerprint fixed the problem for good?
Yes, turning off any always on display features, which includes animation and lighting for fingerprint does eliminate the problem.. i suppose it is some drivers for AOD that are incompatible. Same goes for light sensor, if you test it with software the problem is obvious, light sensor does not work at all, it is recognized, but it does not react to light changes.
Hi All,
Could anyone comment on the minimal requirements to avoid flickering and potential random restarts? At this stage I turned off AOD, turned off fingerprint for locking/unlocking (only use pass + face recognition) and turned off the auto brightness. With these settings the flickering/random restarting problem is gone. I just wonder whether there is a solution with potentially fingerprint for locking/unlocking off, but with auto brightness on and with at least basic AOD on. Thanks in advance for your help!
Hi I have the same issue screen flickering and diming after turning one the screen with in addition and the most problematic the call is blocked by a message concerning the region.
If I make a factory reset the calls work work a time then the same problem comeback
i fixed screen flicker... show fingerprint icon off, Finger print animation off, AOD off. Auto Brig off
Related
Hello,
the following problem appears when i try to unlock the phone after some hours: i can see my home screen, but the screen stays extremely dim. When i try to start an app (e.g. browser) the screen turns black. I can unlock it again, but the screen stays dim. after some unlocking the screen becomes normal (normal brightness) and also the apps are startable.
i am using autobrightness, the stock firmware, 4.1.1 (i9300xxdlih) power saver is not turned on.
thx, i hope you can help me solving this problem
fanbayer
Fanbayer said:
Hello,
the following problem appears when i try to unlock the phone after some hours: i can see my home screen, but the screen stays extremely dim. When i try to start an app (e.g. browser) the screen turns black. I can unlock it again, but the screen stays dim. after some unlocking the screen becomes normal (normal brightness) and also the apps are startable.
i am using autobrightness, the stock firmware, 4.1.1 (i9300xxdlih) power saver is not turned on.
thx, i hope you can help me solving this problem
fanbayer
Click to expand...
Click to collapse
i updated mobile phone to android versiopn 4.1.2. this morning. Unfortunately the problem still appears.
Maybe its a hardware defect?
Try to disable somehow light sensor and change settings to non auto brightness.
Sent from my GT-I9300 using xda app-developers app
d0hn said:
Try to disable somehow light sensor and change settings to non auto brightness.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
i disabled auto brightness and set the brightness to the highest level. But its still same: very dim and after a while a black screen; after a few times of unlocking, the display works normally
I have just seen the same issue on a friend's S3.
Anyone else? I feel like this is a very big issue that is still lurking in a lot of devices.
I tried it myself and I toggled the power button to turn the screen on and off.
It doesn't take long but sometimes when the screen turns back on, it's super dim and you can faintly see the lockscreen image.
You have to cycle the screen several more times to get it to the 'correct' brightness, and no it is NOT a brightness setting.
It's some hardware issue in the phone.
Sorry for the necrobump, but I only found this thread. I have this problem too since about a week back. It makes my phone useless at times. I first thought it was a software issue. I have an app (called Twilight) for dimming the screen more than normal settings and also toning it, for nightime use, and I thought that was the culprit first, but nope. I have flashed rom, recovery, wiped all caches I can think of. Still happens, just now I was in the middle of installing android revolution hd, and the screen ultradimmed on me so I can't finish the process
Thing is, a few months ago I managed to crack my screen by way of gravity and concrete. I let the samsung brand service centre in Stockholm repair it for me (it is out of warranty) and this issue with the dimming never happened before that. Then again, it didn't happen directly afterwards either... but still. So, I am thinking: either me dropping it caused more damages and this is because of that. Or the service center did a bad install of the new screen. Or, the replacement screen that was installed has a defect in itself. I am leaning a bit towards the third explanation... maybe different batches of screens?
Does anyone have any ideas? If I am to contact the service center and complain about their work I would like to be able to point towards a "known problem"...
8Fishes said:
I have just seen the same issue on a friend's S3.
Anyone else? I feel like this is a very big issue that is still lurking in a lot of devices.
I tried it myself and I toggled the power button to turn the screen on and off.
It doesn't take long but sometimes when the screen turns back on, it's super dim and you can faintly see the lockscreen image.
You have to cycle the screen several more times to get it to the 'correct' brightness, and no it is NOT a brightness setting.
It's some hardware issue in the phone.
Click to expand...
Click to collapse
Take it back, if it didn't happen before then the new screen is most likely.
It isn't a common problem
Is anyone else having issues with AOD turning off even with slight darkness. For some reason my AOD keeps turning off even though there still some light in the room. It used to stay on when I wake up at 6am when there some sunlight but now it just turns off. I have to point the phone directly to the light sometimes to get it to turn on. Don't have any screen protector that is blocking the light sensor and seems to function correctly checking the debug mode (*#0*#). I have to reboot the phone to fix the issue but after a few days it goes back to being wonky.
yeah, i updated it via Samsung Galaxy App store, then did a data clear in the setting menu and now it works. But mine did the exact same thing.
clearing the data still causes me the problem.. Only fix for me is to reboot the phone =/
Do you have a screen protector?
Tidbits said:
Do you have a screen protector?
Click to expand...
Click to collapse
I have a screen protector but have all the cutouts that isn't blocking the proximity sensor. I've tested the sensor in debug mode and no issues at all.
what was updated or installed recently that had this started happening with. It may be an app that introduced a bug. Did you try and see if there is a AOD update?
Tidbits said:
what was updated or installed recently that had this started happening with. It may be an app that introduced a bug. Did you try and see if there is a AOD update?
Click to expand...
Click to collapse
what screwed it up was the AOD update (go figures ).. I reverted back to the original before the update but somehow it's broken now. As mention it works like it should after a reboot but after a few days it becomes all wonky.
I purchased my S21 about 5 weeks ago and I am not sure if I have been experiencing this issue since I bought it but in the last week, I have noticed this issue. When my phone is locked, the AOD will either show for a few seconds to a minute or just won't show. I've ensured it is set to always show, power-saving not set to turn it off, no Bixby routines and any updates are installed for phone/AOD. I've even factory reset my phone and removed the case and screen protector and the issues are still persisting. Does anyone else experience this issue?
Disable all power management... it screws up all kinds of things.
Does AOD show if you tap the screen?
I have disabled all power management that I am aware of and still experiencing issues. I've set it to show on tap and while it worked the first time, subsequent taps do not show the AOD
Video demonstrating AOD tap to show issue
Sounds like a firmware glitch or the flash was corrupted.
Double check all AOD and screen lock settings.
Try turning AOD always on.
Try disabling screen lock... a lock out is the last thing you want anyway.
Play with it... Android's wuv attention.
The case or screen protector won't do this more than likely.
blackhawk said:
Sounds like a firmware glitch or the flash was corrupted.
Double check all AOD and screen lock settings.
Try turning AOD always on.
Try disabling screen lock... a lock out is the last thing you want anyway.
Play with it... Android's wuv attention.
The case or screen protector won't do this more than likely.
Click to expand...
Click to collapse
I normally use AOD always on, I'd tried the tap on the option to test. Going to try flashing it today to see if that helps despite the factory reset not helping.
So I've flashed the stock firmware back onto my device and the issues are still persisting. I've contacted support through the Samsung Members app and it's been escalated to the Research and Development team and am just waiting to hear back.
Did you update any Samsung apps after the reload before testing it? Go with the factory app loads.
Try disabling the lock screen... they tend to end up locking out the intended user anyway, sooner or latter.
If no one else is having this issue it very well maybe a hardware issue.
Did you ever wonder what happens when one or two micro transistor junctions out of the millions in a phone fail? Yes, well...
Unfortunately I can't recall if Samsung apps updated before I tested. I've already factory reset a few times so I'd rather avoid that for now. I've noticed the issues occur when using auto-brightness on AOD in lower light settings. When I say lower light, I mean in my study during the day which I never experienced issues with on my S20 FE. I've sent a report to Samsung Members and am waiting on them to come back to me.
The you
brodieb321 said:
Unfortunately I can't recall if Samsung apps updated before I tested. I've already factory reset a few times so I'd rather avoid that for now. I've noticed the issues occur when using auto-brightness on AOD in lower light settings. When I say lower light, I mean in my study during the day which I never experienced issues with on my S20 FE. I've sent a report to Samsung Members and am waiting on them to come back to me.
Click to expand...
Click to collapse
Did you ever get this fixed. I have the exact same issue on my s20 ultra
Edit: Nevermind just fixed it after 3 days troubleshooting. Oddly it was the the disable AOD while in power saving mode that needed to be disabled even though I don't use power saving mode. Samsung never seem to amaze me with these dumb persistent bugs.
Glad to see you solved the issue. I'd already confirmed this setting was off for me. It's still happening. Looks like it's something to do with the level of light detection as the issue only happens when I have auto brightness set for the AOD. The problem is it's not even that dark when it's happening and never occurred with my S20 FE.
Hello,
I have problem with my Nord2 - Fingerprint doesn't work on always on display unless screen is tapped once or phone is picked up.
If always on display is off - same problem. I think there is problem when screen is locked.
Yeah it's a normal behaviour of most of the phones with AOD and with fingerprint scanner under display.
The screen needs to illuminate where you place your finger in order for the fingerprint scanner to be able to read it from below the screen and the AOD don't have this possibility (it would consume to much battery to have this zone always illuminated)
You need to tap screen or pick the phone up to switch from the AOD animation to the FIngerprint animation and be able to unlock your phone.
Pouic said:
Yeah it's a normal behaviour of most of the phones with AOD and with fingerprint scanner under display.
The screen needs to illuminate where you place your finger in order for the fingerprint scanner to be able to read it from below the screen and the AOD don't have this possibility (it would consume to much battery to have this zone always illuminated)
You need to tap screen or pick the phone up to switch from the AOD animation to the FIngerprint animation and be able to unlock your phone.
Click to expand...
Click to collapse
No. It's not a normal behaviour.
Moreover, with the very initial build it was good.
Accessible always. But 1st update had few chances related to fp which broke it from aod.
Sorry I didn't meant to be rude.
I received my Oneplus Nord 2 phone with the A.05 update and already back there the AOD didn't have the possibility to scan the fingerprint . I have a colleague with the Oneplus 9 and asked him how is the behaviour of the AOD on his phone and same thing : his phone doesn't unlock when you press finger in the AOD. You need to single tap once to bring the fingerprint icon online and only after that you can unlock the phone in the AOD screen
The only thing you can do in the OxygenOS AOD settings is toggle the
"Fingerprint icon - Show fingerprint icon temporarily when the ambient display is shown" option .
Will be able to unlock the phone in AOD mode for a few seconds only after you lock the phone, after that the fingerprint icon disappear and the digitizer turn off to save battery .
Hi All,
Could anyone comment on the minimal requirements to avoid flickering and potential random restarts? At this stage I turned off AOD, turned off fingerprint for locking/unlocking (only use pass + face recognition) and turned off the auto brightness. With these settings the flickering/random restarting problem is gone. I just wonder whether there is a solution with potentially fingerprint for locking/unlocking off, but with auto brightness on and with at least basic AOD on. Thanks in advance for your help!