Database Develop

phone kills scheduled events

I'm having issues with several apps not triggering at specific times/notifications. Tried to whitelist Duolingo and that worked for two days and then it stopped. Podcast addict is doing the same thing. It should update every 4 hours but nothing happens. Tried to whitelist it but didn't work. The developer thinks it is the phone that kills the wake-up trigger/alarm. Anything else that I can try as it is rather annoying that various apps only work if I actually open the.
Running nougat and 4.0.2

Disable Doze Mode from Settings->Developer options. Reboot to wipe caches and check if problem is solved.

TweaknFreak said:
Disable Doze Mode from Settings->Developer options. Reboot to wipe caches and check if problem is solved.
Click to expand...
Click to collapse
I'll test that. Didn't know the reboot did that.

Eggstones said:
I'll test that. Didn't know the reboot did that.
Click to expand...
Click to collapse
What I meant by reboot was to boot into recovery mode and wipe caches.

Sorry not sure how to do that. Just going into memory clearing it from there doesn't do the trick?

Press the POWER+VOLUME DOWN keys simultaneously until the device restarts and oneplus splash screen appears. Then recovery mode will start and language selection menu will appear. Wipe caches from there. Be careful not to wipe anything else. Then restart your device. Most issues albeit small ones get resolved by doing this.

Seems like doze kills the check. If I switch doze off, podcast addict runs the check for new episodes. With it on it doesn't, even if I whitelist the app. It also seems like when it runs the new episode check , the phone kills the app as it showed up under power hungry apps. I'll see if the cache clean dies anything.

Screen Tint issue and AOD issue after Oreo update?

I just (excitedly) updated to Oreo, and now I am wishing I had not. I love the new features, but two really irritating issues presented themselves:
1) My screen is not tinted an awful color. It looks almost like my blue light filter is on (but it isn't - when I turn it on it gets HILARIOUSLY bad). Whites are not white. Adaptive mode is the worst, basic mode makes it tolerable but not good at all. My screen looked so much better before.
2) My always on display is wonky. It occasionally is so dim I cannot even see it. Sometimes it is fine, other time it's bad. No rhyme or reason to it (my lighting is the same so it's not adjusting to the environment).
Neither is these things were an issue before. Anyone else experiencing these things? Any idea how to fix either one?

Same issies
Horrible screen tint, opaque orange and the whites are awful. They work fine during initial bootup of the phone, then change. Contacted Verizon and Samsung, they are both aware and no fix as of yet to what the deal is. So do not update your note8, there's absolutely nothing exciting or great with the update. Waited 3+ months for this update, had it on my Z2 force and it was great, ABSOLUTELY blows on the note 8...

PsiPhiDan said:
I just (excitedly) updated to Oreo, and now I am wishing I had not. I love the new features, but two really irritating issues presented themselves:
1) My screen is not tinted an awful color. It looks almost like my blue light filter is on (but it isn't - when I turn it on it gets HILARIOUSLY bad). Whites are not white. Adaptive mode is the worst, basic mode makes it tolerable but not good at all. My screen looked so much better before.
2) My always on display is wonky. It occasionally is so dim I cannot even see it. Sometimes it is fine, other time it's bad. No rhyme or reason to it (my lighting is the same so it's not adjusting to the environment).
Neither is these things were an issue before. Anyone else experiencing these things? Any idea how to fix either one?
Click to expand...
Click to collapse
Try clearing the cache in recovery
You can do that by turning the phone off
Hold Volume Up+Power+Bixby and wait till the blue screen goes away
Navigate down with the volume keys and select Wipe Cache Partition with the power button.
Select Yes
Select Reboot System Now
If that doesn't help, I would either try a factory reset or flash Oreo with Odin.
I didn't do the OTA, but flashed the ROM with Odin instead and I have zero issues

Ripthulhu said:
Try clearing the cache in recovery
You can do that by turning the phone off
Hold Volume Up+Power+Bixby and wait till the blue screen goes away
Navigate down with the volume keys and select Wipe Cache Partition with the power button.
Select Yes
Select Reboot System Now
If that doesn't help, I would either try a factory reset or flash Oreo with Odin.
I didn't do the OTA, but flashed the ROM with Odin instead and I have zero issues
Click to expand...
Click to collapse
I did the OTA and also have zero issues. Agree with suggestion for factory reset...

Update
Did the wipe cache/partition and no luck.
Won't try the FDR option as that was never worked for any issues I've had in the past decsde. Always a waste of time and hassle. Unless that's a guaranteed fix by Samsung or Verizon I will wait for a software patch update or whatever else it is to fix this issue.

OP, did you have blue light filter enabled prior to Oreo update?
Furthermore, it seems to me like Samsung devices prefer having their original Android OS , meaning updates seems to make them not as true and stable as they originally were out of the box. Perhaps another little sly tactic for us users to upgrade hardware yearly.
Sent from my SM-N950U using Tapatalk

Limeybastard said:
OP, did you have blue light filter enabled prior to Oreo update?
Furthermore, it seems to me like Samsung devices prefer having their original Android OS , meaning updates seems to make them not as true and stable as they originally were out of the box. Perhaps another little sly tactic for us users to upgrade hardware yearly.
Click to expand...
Click to collapse
I had the blue light filter on before taking the Ota and don't have this issue. I turned it off just after the Ota and looks normal

MACHEK said:
I had the blue light filter on before taking the Ota and don't have this issue. I turned it off just after the Ota and looks normal
Click to expand...
Click to collapse
Yeah something definitely went wrong for OP during install. I would start fresh and reinstall or reset.

I haven't taken the update. But its a new Android version. I personally always factory reset before updating to a new Android base version. I've never had issues on any phone Samsung or not when clearing data first.
Sent from my SM-N950U using Tapatalk

autogeek said:
I haven't taken the update. But its a new Android version. I personally always factory reset before updating to a new Android base version. I've never had issues on any phone Samsung or not when clearing data first.
Click to expand...
Click to collapse
I also factory reset with ever major update and never had a problem.

The bluelight filter is off, turning it on makes it way worse. I've never had to do a FDR with any phone for an update for over a decade, but those phones were all Motorola. This is my first Samsung and it's definitely a problem with the software causing this orange effect on all the white portions of the screen. Samsung and Verizon both confirmed this has happened to several so hopefully there'll be a fix soon as this is most annoying.

reset here too. no more issues.

I've always factory reset before taking a major update.

Do you have any substratum themes installed? Substratum seems to be buggy for oreo. I disabled all the them and my lockscreen went back to normal color.

I've never used it downloaded any themes

Clearing Blue Light or Screen Tint issues with Oreo on Samsung S8
My friend had this issue on an S8 after Oreo. It started by dismissing a dialog box when launching Google Play Books then opening a book. The dialog was asking something about Blue Light mode. Dismissing apparently caused a default to Blue Light mode and Always Enable. But, we could not find a way to get back to those settings in Google Play Books. Using the system setting to turn off did not work and turning on made screen colors worse. So, we uninstalled the Google Play Books app, restarted phone. Still bad colors at this point. Next, we re-installed app. After opening app and then selecting a book the same dialog box appeared. We selected Settings this time and turned the slider to OFF for Blue Light mode. Now, the Blue Light mode is off for the app and the rest of the phone screens outside of the app. Everything seems like correct colors again.
Even if you do not use Google Play Books, maybe this process will unstick a setting for you.

I don't use or have never used Google play books. Never seen a prompt like that either

Ripthulhu said:
Try clearing the cache in recovery
You can do that by turning the phone off
Hold Volume Up+Power+Bixby and wait till the blue screen goes away
Navigate down with the volume keys and select Wipe Cache Partition with the power button.
Select Yes
Select Reboot System Now
If that doesn't help, I would either try a factory reset or flash Oreo with Odin.
I didn't do the OTA, but flashed the ROM with Odin instead and I have zero issues
Click to expand...
Click to collapse
It's funny, I actually factory reset because the cache wipe didn't work. All looked well. Then after the initial setup (with a beautiful white background), my home screen popped up, and the screen immediately got all tinted. Some setting must have restored with my account! So I factory reset AGAIN, didn't import my setting or apps, then redid everything on my phone from scratch. Now it's fine. What a pain!

RogerTheGeek said:
My friend had this issue on an S8 after Oreo. It started by dismissing a dialog box when launching Google Play Books then opening a book. The dialog was asking something about Blue Light mode. Dismissing apparently caused a default to Blue Light mode and Always Enable. But, we could not find a way to get back to those settings in Google Play Books. Using the system setting to turn off did not work and turning on made screen colors worse. So, we uninstalled the Google Play Books app, restarted phone. Still bad colors at this point. Next, we re-installed app. After opening app and then selecting a book the same dialog box appeared. We selected Settings this time and turned the slider to OFF for Blue Light mode. Now, the Blue Light mode is off for the app and the rest of the phone screens outside of the app. Everything seems like correct colors again.
Even if you do not use Google Play Books, maybe this process will unstick a setting for you.
Click to expand...
Click to collapse
I didn't get a blue light filter prompt when I opened google books.

RogerTheGeek said:
My friend had this issue on an S8 after Oreo. It started by dismissing a dialog box when launching Google Play Books then opening a book. The dialog was asking something about Blue Light mode. Dismissing apparently caused a default to Blue Light mode and Always Enable. But, we could not find a way to get back to those settings in Google Play Books. Using the system setting to turn off did not work and turning on made screen colors worse. So, we uninstalled the Google Play Books app, restarted phone. Still bad colors at this point. Next, we re-installed app. After opening app and then selecting a book the same dialog box appeared. We selected Settings this time and turned the slider to OFF for Blue Light mode. Now, the Blue Light mode is off for the app and the rest of the phone screens outside of the app. Everything seems like correct colors again.
Even if you do not use Google Play Books, maybe this process will unstick a setting for you.
Click to expand...
Click to collapse
Thanks for posting this!! I had the same problem and couldn't figure why. After reading this, I went into Google Play Books and simply turned the night light off, and problem solved! It seems the nightlight setting in Google Play Books gets stuck in Oreo and overlays everything.

Frozen screen after waking up screen

At some point after upgrading to Android 9 I started having the following issue where if the screen turns off due to inactivity and I turn it back on by pressing the power button, I see whatever screen I had open before it went to sleep but it's frozen. Scrolling touching etc still perform (invisible) actions but the screen is frozen until I either press the app switch button or perform some action that would change the current application. While the screen is frozen the drawer from the top works just fine. Also when the app that gets frozen is the desktop (I'm using the default launcher), I can see the background scrolling if I swipe left or right but the widgets don't change, they are frozen.
Does anyone else have the same problem? Any ideas what could be causing it?

Tritonio_GR said:
At some point after upgrading to Android 9 I started having the following issue where if the screen turns off due to inactivity and I turn it back on by pressing the power button, I see whatever screen I had open before it went to sleep but it's frozen. Scrolling touching etc still perform (invisible) actions but the screen is frozen until I either press the app switch button or perform some action that would change the current application. While the screen is frozen the drawer from the top works just fine. Also when the app that gets frozen is the desktop (I'm using the default launcher), I can see the background scrolling if I swipe left or right but the widgets don't change, they are frozen.
Does anyone else have the same problem? Any ideas what could be causing it?
Click to expand...
Click to collapse
FWIW I have not really solved the problem but I am circumventing it by having the screen lock immediately instead of waiting 5 minutes. That way I have to unlock with a fingerprint every time the screen is off, and unlocking refreshes the screen which "fixes" the problem.

Tritonio_GR said:
FWIW I have not really solved the problem but I am circumventing it by having the screen lock immediately instead of waiting 5 minutes. That way I have to unlock with a fingerprint every time the screen is off, and unlocking refreshes the screen which "fixes" the problem.
Click to expand...
Click to collapse
There were lot of reports of glitchy phones after the Pie update.
The cure was a factory reset or software repair with Xperia Companion
Use Xperia Transfer to back up your calls/contacts/texts before you reset the phone

Didgesteve said:
There were lot of reports of glitchy phones after the Pie update.
The cure was a factory reset
Click to expand...
Click to collapse
Can you please link a thread, where users told, that problem is solved after reset?
I have the same frozen display (since Android Pie), when turning display off and on again.
Don´t wish to reset and install all again, if that does not help.
bye,
Ralf

thegrobi said:
Can you please link a thread, where users told, that problem is solved after reset?
I have the same frozen display (since Android Pie), when turning display off and on again.
Don´t wish to reset and install all again, if that does not help.
bye,
Ralf
Click to expand...
Click to collapse
Hi Ralf,
the phone will always work better with a reset after a major update, all the Oreo applications are trying to work under Pie. Sometimes it works, sometimes it doesn't. Oreo apps aren't made to work under Pie and they can error.
here, is one example, or another, but I didn't jump to Pie because of all the negative feedback and the scores of people trying to downgrade.
A reset will fix your problem and if you use Xperia transfer then the amount of personal information lost will be minimal.

Thanks for the links.
Didgesteve said:
all the Oreo applications are trying to work under Pie. Sometimes it works, sometimes it doesn't. Oreo apps aren't made to work under Pie and they can error.
Click to expand...
Click to collapse
This sounds to me, the combination of "old" Navi-apps with Pie is the problem. May be only with Pie on some Sonys.
I'm afraid, a reset will not change the frozen display.
All other apps till now do not freeze after display-on except MagicEarth and Osmand+
This 2 apps i deinstalled (+ deleting the data) and installed again.
A reset will fix your problem and if you use Xperia transfer then the amount of personal information lost will be minimal.
Click to expand...
Click to collapse
Xperia transfer shows me only 2 apps for backup.
I'll probably try a reset in the next few days anyway.
bye,
Ralf

thegrobi said:
Thanks for the links.
This sounds to me, the combination of "old" Navi-apps with Pie is the problem. May be only with Pie on some Sonys.
I'm afraid, a reset will not change the frozen display.
All other apps till now do not freeze after display-on except MagicEarth and Osmand+
This 2 apps i deinstalled (+ deleting the data) and installed again.
Xperia transfer shows me only 2 apps for backup.
I'll probably try a reset in the next few days anyway.
bye,
Ralf
Click to expand...
Click to collapse
Looks like there is know issue with the Osmand+, the date of the post is may last year, but it may just be a 'feature'
When backing up with Xperia transfer, make sure you select all the boxes that are optional. It's things like text messages/contacts/phone history that are useful after a reset. Some apps can't be moved and have to be downloaded directly from the playstore, but Google should give you that option, after you log back in to the wiped phone.
Edit: I can recomend Sygic, free maps for one country, works without data.

In the meantime, I found more users with this problem and a little solution that another user describes:
I can confirm I have the exact same issue since Android 9 with my Xperia xz1 compact.
I normally have no lockscreen options set. So when I wakeup the Phone, it sometimes kind of 'locks' the screen. Widgets do not respond, I cannot switch home screens. The time on the status bar remains correct. If I then click on an app and go back, everythning behaves normally.
So I'm quite sure this must be a software issue, as other people have this problem to.
My workaround for now is to have a lockscreen option aktive. But I would rather have not, for conveniance.
I tested this also with safe mode and complete factory reset of the phone. The 'bug' is still there.
Click to expand...
Click to collapse
If I disable lockscreen, then apps stop when it is switched on again. However, I always have to enter pin or use fingerprint sensor, or smart lock.
This often does not work when cycling and is dangerous when cardriving.
On Android 8, the lockscreen did not need to be active.
So the problem is not Osmand and MagicEarth.
It is a Sony 9 bug with Android 9.
bye,
Ralf

Found in an other forum an easy method to reproduce the problem.
disable the screen lock (it must be set to "None");
lock the phone and then unlock it;
lock and unlock it again.
Click to expand...
Click to collapse
bye,
Ralf
---------- Post added at 01:50 PM ---------- Previous post was at 01:20 PM ----------
Because I believe that Sony will not fix the error, I could imagine a solution:
An app (possibly tasker), which puts a selectable running app from foreground while pressing the power button in the background and immediately brings it back to the foreground.
Does anyone know such a tool?
bye,
Ralf

[/COLOR]Because I believe that Sony will not fix the error, I could imagine a solution:
An app (possibly tasker), which puts a selectable running app from foreground while pressing the power button in the background and immediately brings it back to the foreground.
Does anyone know such a tool?
bye,
Ralf[/QUOTE]
So, did you ever find a solution?

Nokia 7 Plus frequently locks up, not in Safe Mode

I have a Nokia 7 Plus, running Pie, unrooted. Generally a great phone, had the charging port fixed by Nokia a few years ago.
But every now and then the screen locks up, I can usually get control back by locking the screen and waiting a moment and unlocking.
I've factory wiped my phone a few times, I've removed of my apps but today it's been terrible and seeks to be locking up more than ever.
I put it into safe mode and used chrome, with Bluetooth and wifi and had no issues at all.
Any ideas how I can diagnose and fix the issue?

benji1304 said:
I have a Nokia 7 Plus, running Pie, unrooted. Generally a great phone, had the charging port fixed by Nokia a few years ago.
But every now and then the screen locks up, I can usually get control back by locking the screen and waiting a moment and unlocking.
I've factory wiped my phone a few times, I've removed of my apps but today it's been terrible and seeks to be locking up more than ever.
I put it into safe mode and used chrome, with Bluetooth and wifi and had no issues at all.
Any ideas how I can diagnose and fix the issue?
Click to expand...
Click to collapse
Any suggestions how to potentially fix this?

Maybe worth to try the following:
1) clear system UI cache
2) Android system force stop
3) reboot
and /or
1) activate developer settings
2) under -> debugging -> Game-Driver Settings activate "prerelease-driver* for all Apps. It will survive re-starts
3) enter recovery mode and perform the graphics test
4) reboot
This is working for me since 29 May 2021. To be confirmed....

chrhei said:
Maybe worth to try the following:
1) clear system UI cache
2) Android system force stop
3) reboot
and /or
1) activate developer settings
2) under -> debugging -> Game-Driver Settings activate "prerelease-driver* for all Apps. It will survive re-starts
3) enter recovery mode and perform the graphics test
4) reboot
This is working for me since 29 May 2021. To be confirmed....
Click to expand...
Click to collapse
Thanks @chrhei
Unfortunately the issue still persists with the first option.
I'll try the 2nd one - what does the Game Driver setting do?

benji1304 said:
Thanks @chrhei
Unfortunately the issue still persists with the first option.
I'll try the 2nd one - what does the Game Driver setting do?
Click to expand...
Click to collapse
To be honest: I've no idea what it does, but it's still working for me.

Sorry to all
After 5 days of usage it happened again.
Conclusion: No fix.
Sorry for being to optimistic.

Question AOD bug

My oneplus 10 pro has AOD problem. It started a few days ago.
After screen lock, the screen turns back on and off quickly. The AOD does not appear.
I already did the test with all the AOD settings, I changed the background and nothing resolved.
I've already tested all screen lock settings and it didn't work.
I can't format my cell phone at the moment but if there is no solution I will do it.
I need your help.
oneplus 10 pro 5g
model NE2215
android version 13
compilation number NE2215_11_C.26
Thanks.

blackffear said:
My oneplus 10 pro has AOD problem. It started a few days ago.
After screen lock, the screen turns back on and off quickly. The AOD does not appear.
I already did the test with all the AOD settings, I changed the background and nothing resolved.
I've already tested all screen lock settings and it didn't work.
I can't format my cell phone at the moment but if there is no solution I will do it.
I need your help.
oneplus 10 pro 5g
model NE2215
android version 13
compilation number NE2215_11_C.26
Thanks.
Click to expand...
Click to collapse
There is no background for aod. Make sure aod toggle is on and pick a digital clock. If you are rooted disable all magisk modules and reboot to see if you messed something up.

Guys,
Oneplus support answered me about the matter. See below.
Hi Leonardo,
Thank you for the revert. Hope you are doing good.
I recommend trying to Hard Reset the phone. Since this will wipe your phone data, please make sure to backup your data files before doing the Hard Reset.
Backing Up The Data: You can sync your Google account to back up the Application data, WIFI settings, pictures and contacts. Do ensure you have enabled auto sync and backup data from settings. For music, video or other files, you can copy the files to computer by connecting the USB cable.
Please follow the instructions given below to perform Hard Reset steps:
* “Power OFF” the device and press the volume down and Power buttons simultaneously for 15-20 seconds
* Select the Language as "English"
* The recovery screen will appear on the display
* Select "Wipe data & cache"
* You should have three options saying “Reset system settings”, “Wipe cache" and “Erase everything”
* Please tap on "Erase everything”
*This would perform a reset on the phone and once the reset is completed successfully, * Select “Yes” & "Reboot” the device.
If the issue still persists even after performing all the provided steps, please get back to us. We will surely assist you with the information available.
Looking forward to your response.
Regards,
Aaron Frank
OnePlus Support.

That's the default answer they provide for every possible issue.

I did what was suggested and it worked.

Of course it did. That's basically a "switch it off and on again" on steroids.
My point is that a lot of times a factory reset is overkill, but from a helpdesk perspective that's the cheapest way to take care of the vast majority of calls witout even looking into what the issue is.
I contacted them a while ago while the .21 firmware had an issue with Android Pay, caused by Work Proflie and Clone System. It took me (and a few others) a bit of time what the actual root cause was and offer a fix. 1+ helpdesk would have still advised to facvtory reset, instead of even just looking for an actual fix.

And the issue Back again

Try to think about the exact steps you've done after the reset.

OK. after the hard reset it was working fine. The problem restarted for no specific reason. I restarted the device and the problem stopped. Then it came back. after this last system update this problem started. on my OnePlus 7 pro I didn't have this problem. I upgraded to 10 pro thinking it would get better now I'm worried about this rapidly flickering screen after lock. I continue to contact OnePlus support.

Guys, I sent another email to Oneplus support. I'm still waiting for help. Is my device faulty? Email below.
Gentlemen, good morning.
Unfortunately my problem goes far beyond what I imagined. It is not a problem of always on the display only because when I disable the service the problem continues. I've already done the Hard Reset 2 times and the problem continues. I even did the installation without using any previous configuration, however the problem ends up returning. My Oxygenos 13 version doesn't have the option to downgrade to Oxygenos 12. Am I starting to see that this is a problem specific to my device or am I wrong? Would it be a defect? This is giving me a lot of concern as with the screen flickering quickly I am afraid of my screen getting damaged. Please I need your help.

Guys, good morning. Vídeo Oneplus 10 pro bug / vídeo 2 Oneplus 10 pro bug 2
One more update for you.
I downgraded to Oxygenos 12.1. At first everything was fine. I went to sleep. When I woke up the problem came back. I'll send you a video.After restarting the phone the problem stopped. However, it is clear that this problem is on my device and not only on the operating system. I'm starting to believe it's a bug.

blackffear said:
Guys,
Oneplus support answered me about the matter. See below.
Hi Leonardo,
Thank you for the revert. Hope you are doing good.
I recommend trying to Hard Reset the phone. Since this will wipe your phone data, please make sure to backup your data files before doing the Hard Reset.
Backing Up The Data: You can sync your Google account to back up the Application data, WIFI settings, pictures and contacts. Do ensure you have enabled auto sync and backup data from settings. For music, video or other files, you can copy the files to computer by connecting the USB cable.
Please follow the instructions given below to perform Hard Reset steps:
* “Power OFF” the device and press the volume down and Power buttons simultaneously for 15-20 seconds
* Select the Language as "English"
* The recovery screen will appear on the display
* Select "Wipe data & cache"
* You should have three options saying “Reset system settings”, “Wipe cache" and “Erase everything”
* Please tap on "Erase everything”
*This would perform a reset on the phone and once the reset is completed successfully, * Select “Yes” & "Reboot” the device.
If the issue still persists even after performing all the provided steps, please get back to us. We will surely assist you with the information available.
Looking forward to your response.
Regards,
Aaron Frank
OnePlus Support.
Click to expand...
Click to collapse
No disrespect, but official support should be your absolute last option. Most of them lack adequate knowledge and training.

TheMystic said:
No disrespect, but official support should be your absolute last option. Most of them lack adequate knowledge and training.
Click to expand...
Click to collapse
I agree with you. I've been trying to resolve this for days and they haven't found a solution yet. I'm coming to conclusions with the help of other users and forums. It's disheartening.

blackffear said:
I agree with you. I've been trying to resolve this for days and they haven't found a solution yet. I'm coming to conclusions with the help of other users and forums. It's disheartening.
Click to expand...
Click to collapse
If factory reset didn't resolve the problem, then it very likely is a problem with the OS, assuming you aren't using any mods that interfere with AOD.
Check on OnePlus community site too. That would be the best place to start.

TheMystic said:
If factory reset didn't resolve the problem, then it very likely is a problem with the OS, assuming you aren't using any mods that interfere with AOD.
Check on OnePlus community site too. That would be the best place to start.
Click to expand...
Click to collapse
After the Downgrade to version 12 I realized that the problem took a while to happen but it reappeared. With less damage than version 13. When I updated again to version OxygenOS 13 the problem already restarted at the first moment. I don't use any MODs. I use the original unaltered version. I haven't done the formatting on the computer yet. Would you recommend a clean format? If so, any tutorial recommendations?

blackffear said:
After the Downgrade to version 12 I realized that the problem took a while to happen but it reappeared. With less damage than version 13. When I updated again to version OxygenOS 13 the problem already restarted at the first moment. I don't use any MODs. I use the original unaltered version. I haven't done the formatting on the computer yet. Would you recommend a clean format? If so, any tutorial recommendations?
Click to expand...
Click to collapse
Based on what you have said so far, it appears that this problem was not there earlier when you were on Android 12. But now after upgrading to Android 13, the problem has started and it continues to be present even if you downgrade back to Android 12.
Is it possible for you to record a video of this behaviour and post it here? I would also like to see your system settings for display, lockscreen and AOD.

TheMystic said:
Based on what you have said so far, it appears that this problem was not there earlier when you were on Android 12. But now after upgrading to Android 13, the problem has started and it continues to be present even if you downgrade back to Android 12.
Is it possible for you to record a video of this behaviour and post it here? I would also like to see your system settings for display, lockscreen and AOD.
Click to expand...
Click to collapse
That. You said it all. I will send the links to the videos here on system 12 and 13.

blackffear said:
That. You said it all. I will send the links to the videos here on system 12 and 13.
Click to expand...
Click to collapse
vídeo OxygenOS 12 https://drive.google.com/file/d/1Ft8_SAO8wmGmXY13y3wny8GII22c2kQ0/view?usp=share_link
vídeo OxygenOS 12 https://drive.google.com/file/d/1QNguxZtHJzPPyT_C91P2vd7zVcaWfCvZ/view?usp=share_link
video OxygenOS 13 https://photos.app.goo.gl/QdoGvdmu1T1gUtex5

blackffear said:
vídeo OxygenOS 12 https://drive.google.com/file/d/1Ft8_SAO8wmGmXY13y3wny8GII22c2kQ0/view?usp=share_link
vídeo OxygenOS 12 https://drive.google.com/file/d/1QNguxZtHJzPPyT_C91P2vd7zVcaWfCvZ/view?usp=share_link
video OxygenOS 13 https://photos.app.goo.gl/QdoGvdmu1T1gUtex5
Click to expand...
Click to collapse
I hope you haven't enabled power saving on your phone. But check that.
Also, go to
Settings/ Apps/ App Management
Click on 3 dots on top right
Show System
Search for AOD
Click on it and clear data for that app
See if it helped.
Also, try changing AOD from ALL DAY to Power Saving or Scheduled if the above doesn't help.

TheMystic said:
I hope you haven't enabled power saving on your phone. But check that.
Also, go to
Settings/ Apps/ App Management
Click on 3 dots on top right
Show System
Search for AOD
Click on it and clear data for that app
See if it helped.
Also, try changing AOD from ALL DAY to Power Saving or Scheduled if the above doesn't help.
Click to expand...
Click to collapse
I've done all that and it didn't work. I have already tested all these options.