Database Develop

[Q] Problem after Android official update

Hi!
Yesterday my phone beeped telling me there was and Android update available, around 198MB
it came from this
dropbox.. com/s/kek0lyolyzdrjhj/2014-10-17%2020.16.39.png?dl=0
To this
dropbox.. com/s/zh92wxumigfe00e/2014-10-17%2020.38.32.png?dl=0
Everything was ok for some hours until hell broke loose
The screen will have a bad time turning on. I press the button several times with no response.
The phone is lagged as my grandpa in his grave. Apps close and even transition from one screen to the other is everything but impossible.
But, when I reboot it, it's ok for as long as I'm using it. If I lock the screen and let it aside for a while, the problems come back
No app updates in the meantime. It went from smooth to horrendous in the period of 4 or 5 hours. I didn't use it much in there, but I doubt it was malfunctioning like this
Special apps I have are Greenify pro, MinGuard (I think that's the name), SuperUser and I rooted it with Towelroot long ago
Any help will be appreciated

marioho said:
Hi!
Yesterday my phone beeped telling me there was and Android update available, around 198MB
it came from this
dropbox.. com/s/kek0lyolyzdrjhj/2014-10-17%2020.16.39.png?dl=0
To this
dropbox.. com/s/zh92wxumigfe00e/2014-10-17%2020.38.32.png?dl=0
Everything was ok for some hours until hell broke loose
The screen will have a bad time turning on. I press the button several times with no response.
The phone is lagged as my grandpa in his grave. Apps close and even transition from one screen to the other is everything but impossible.
But, when I reboot it, it's ok for as long as I'm using it. If I lock the screen and let it aside for a while, the problems come back
No app updates in the meantime. It went from smooth to horrendous in the period of 4 or 5 hours. I didn't use it much in there, but I doubt it was malfunctioning like this
Special apps I have are Greenify pro, MinGuard (I think that's the name), SuperUser and I rooted it with Towelroot long ago
Any help will be appreciated
Click to expand...
Click to collapse
If it was a factory update I'm willing to bet you lost root along with busybox. If so, TowelRoot will probably not work this time. There's another root exploit available called PurpleDrake.

shinobisoft said:
If it was a factory update I'm willing to bet you lost root along with busybox. If so, TowelRoot will probably not work this time. There's another root exploit available called PurpleDrake.
Click to expand...
Click to collapse
Thank you! I did it, re-rooted it following the instructions (indeed it looked like I'd lost my root) but the problem is not solved.
It's just a hunch, but seems to me that changing the Launcher smoothes things up. I was using Google Now Launcher and switched to both LG stock one and Solo Launcher and it seems to be ok.
I'll update the post in a few minutes to clarify it further. It could be that just those few minutes of usage after a reboot are smooth, as I stated in OP. Nevertheless, as soon as I change the launcher, the phone behaves better
Any hints? Google launcher version in Play Store is from August 1st here
Edit: bah, no luck. Same ****, regardless of the chosen launcher.
What do I do now? Try to downgrade it?

marioho said:
Thank you! I did it, re-rooted it following the instructions (indeed it looked like I'd lost my root) but the problem is not solved.
It's just a hunch, but seems to me that changing the Launcher smoothes things up. I was using Google Now Launcher and switched to both LG stock one and Solo Launcher and it seems to be ok.
I'll update the post in a few minutes to clarify it further. It could be that just those few minutes of usage after a reboot are smooth, as I stated in OP. Nevertheless, as soon as I change the launcher, the phone behaves better
Any hints? Google launcher version in Play Store is from August 1st here
Edit: bah, no luck. Same ****, regardless of the chosen launcher.
What do I do now? Try to downgrade it?
Click to expand...
Click to collapse
Wait a minute. I remember some issues changing from Quarx ROM back to stock. I walked someone else thru this once before. Lemme see if I can find that post. Otherwise I'll have to go back to stock, which isn't a problem but I'd rather not if I can avoid it. LOL.

shinobisoft said:
Wait a minute. I remember some issues changing from Quarx ROM back to stock. I walked someone else thru this once before. Lemme see if I can find that post. Otherwise I'll have to go back to stock, which isn't a problem but I'd rather not if I can avoid it. LOL.
Click to expand...
Click to collapse
There's a special place in Heaven for people like you.
It's probably clear by now, but I'm using stock rom here. I grabbed the phone in its early days, when this sub was crawling its way to glory, and we didn't even have a Recovery by that time. Since I was mostly ok with Stock, never minded doing anything special other than rooting it.

marioho said:
There's a special place in Heaven for people like you.
It's probably clear by now, but I'm using stock rom here. I grabbed the phone in its early days, when this sub was crawling its way to glory, and we didn't even have a Recovery by that time. Since I was mostly ok with Stock, never minded doing anything special other than rooting it.
Click to expand...
Click to collapse
LOL. Thanks
Here's the post.
Let me know if that does the trick.
---------- Post added at 03:42 PM ---------- Previous post was at 03:33 PM ----------
I forgot to mention, the code listed to activate LG's hidden menu is for the D415 variant.
Code:
3845#*XXX#
Change the XXX to your device model number, ie, 400, 405, 410, 415

shinobisoft said:
LOL. Thanks
Here's the post.
Let me know if that does the trick.
---------- Post added at 03:42 PM ---------- Previous post was at 03:33 PM ----------
I forgot to mention, the code listed to activate LG's hidden menu is for the D415 variant.
Code:
3845#*XXX#
Change the XXX to your device model number, ie, 400, 405, 410, 415
Click to expand...
Click to collapse
Haha I noticed that. Mine is 410 (LGD410HN, to be more precise, according to lg-firmware-rom.com).
I followed the instructions. This is what I saw: dropbox. com/s/6h721axufevchjw/2014-10-18%2019.42.10.png?dl=0
I'll update the post in a few minutes with the outcome. As far as I can see, though, things seem to be the same.
Just rebooted the phone, so it takes a few minutes for it to get sluggish.
Edit: Yeah, same thing.
It's another hunch, but every now and then pops up a message saying that a certain google process or app stopped working. Yesterday's update did have a pack of Google updates, IIRC.

Check greenified apps. Maybe it's trying greenify any system or normal app and Android it's trying wake it. Same problem here time ago

Kowalzki said:
Check greenified apps. Maybe it's trying greenify any system or normal app and Android it's trying wake it. Same problem here time ago
Click to expand...
Click to collapse
It makes sense if you take in account that the problem starts a few minutes after the phone sits idle.
I opened Greenify and there was this orange popup
dropbox. com/s/qkxeb850esfkxuo/2014-10-18%2020.40.57.png?dl=0
I disabled the auto-hibernate featuer now and unchecked the google apps that were on the list (Play Music; Play Books, Play Games, Remote Access - i think). But I didn't add any app since the update yesterday and the phone was running smooth since the last time I checked a few more, wich happened weeks ago.
I've got no clue about what may be causing the auto-hibernation problem that Greenify notes (the picture above).
I'll only be able to state for sure in a few minutes, but seems to me that the problem persists.

marioho said:
It makes sense if you take in account that the problem starts a few minutes after the phone sits idle.
I opened Greenify and there was this orange popup
dropbox. com/s/qkxeb850esfkxuo/2014-10-18%2020.40.57.png?dl=0
I disabled the auto-hibernate featuer now and unchecked the google apps that were on the list (Play Music; Play Books, Play Games, Remote Access - i think). But I didn't add any app since the update yesterday and the phone was running smooth since the last time I checked a few more, wich happened weeks ago.
I've got no clue about what may be causing the auto-hibernation problem that Greenify notes (the picture above).
I'll only be able to state for sure in a few minutes, but seems to me that the problem persists.
Click to expand...
Click to collapse
Do you have a custom recovery installed? If so, the only other suggestion I have, mainly because of the app updates, is to wipe cache and Dalvik cache and then reboot the device.

shinobisoft said:
Do you have a custom recovery installed? If so, the only other suggestion I have, mainly because of the app updates, is to wipe cache and Dalvik cache and then reboot the device.
Click to expand...
Click to collapse
No, I don't, but I'll try to install one right now.
If it doesn't work, will downgrade be the only option?

marioho said:
No, I don't, but I'll try to install one right now.
If it doesn't work, will downgrade be the only option?
Click to expand...
Click to collapse
That's what it's sounding like. I hate to say that because the only way to downgrade is to flash a KDZ. Unless someone has made a flashable zip of your stock ROM.

shinobisoft said:
That's what it's sounding like. I hate to say that because the only way to downgrade is to flash a KDZ. Unless someone has made a flashable zip of your stock ROM.
Click to expand...
Click to collapse
It's been ages since I last meddled with KDZ-ish things... I guess the "hate to say" part is because it will wipe all data from my phone, right?
I installed CWM and wiped cache and Dalvik. It asked to fix my root, I chose 'yes' and rebooted. After the phone took its sweet time to update apps, I was gifted with this popup message after normally unlocking the screen:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
It's the same error message I've been receiving constantly for a while now, as I stated before.
And, yes, things seem to be the same broken s**t as before.
Gosh, what a headache!

marioho said:
It's been ages since I last meddled with KDZ-ish things... I guess the "hate to say" part is because it will wipe all data from my phone, right?
I installed CWM and wiped cache and Dalvik. It asked to fix my root, I chose 'yes' and rebooted. After the phone took its sweet time to update apps, I was gifted with this popup message after normally unlocking the screen:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
It's the same error message I've been receiving constantly for a while now, as I stated before.
And, yes, things seem to be the same broken s**t as before.
Gosh, what a headache!
Click to expand...
Click to collapse
Unfortunately, you cannot just reflash GApps on stock like we can on custom ROMs. As for CWM asking to fix root, this generally isn't needed. So selecting "No" wouldn't hurt.
Well my friend, I'm fresh outta ideas. This may be the first issue that I've not had a fix for. LOL. Sorry. I really hate it when I can't help someone resolve an issue. It's the perfectionist in me, LOL.

Your help and almost instantaneous replies made it. I appreciate, trust me.
I'll search for that old post with LG tool and kdz files and do the deed in a few minutes. I'll update the topic and deem it Solved when I'm finished
Thank you, again

72 Hour Lockout When Flashing Rom's

I know I'm not the only one that experiences this as I've seen other users just accepting that issue.
As some of us know, when we flash from one ROM to another, there is a CHANCE where we'll get the login screen which says "The device has been reset...", which normally is followed by "Please login with the device administrator account", or something along those lines.
I've talked to Google, and I know others have also, and we're told that there is a 72 hour "security" feature that will not allow you to log into a freshly installed device, even though that device is yours and you were just using it 5 minutes prior to flashing the install.
There is no way to bypass this, at least I don't think, and Google doesn't have a way of resetting.
What I'm trying to find out is if someone was able to get around this, or has a work around because holy hell is it annoying.

Remove your google account before the factory reset??

holeindalip said:
Remove your google account before the factory reset??
Click to expand...
Click to collapse
Will that help?

Won't ask for the previous google account on login from factory reset

holeindalip said:
Won't ask for the previous google account on login from factory reset
Click to expand...
Click to collapse
Really? I'm going to have to try this. Would save a huge headache; I'll report back.

stevew84 said:
I know I'm not the only one that experiences this as I've seen other users just accepting that issue.
As some of us know, when we flash from one ROM to another, there is a CHANCE where we'll get the login screen which says "The device has been reset...", which normally is followed by "Please login with the device administrator account", or something along those lines.
I've talked to Google, and I know others have also, and we're told that there is a 72 hour "security" feature that will not allow you to log into a freshly installed device, even though that device is yours and you were just using it 5 minutes prior to flashing the install.
There is no way to bypass this, at least I don't think, and Google doesn't have a way of resetting.
What I'm trying to find out is if someone was able to get around this, or has a work around because holy hell is it annoying.
Click to expand...
Click to collapse
I searched a bit and found this:
http://www.androidpolice.com/2015/0...ne-you-might-trip-a-72-hour-security-lockout/
If that article is correct, the "chance" isn't something random, it is caused by changing your google account password. So to avoid, don't factory reset within 72 hours after changing your google account password.

http://forum.xda-developers.com/showthread.php?t=3104504

As long as you do a full device wipe before flashing you are fine. I have never had this pop up. Just properly format system, data and both caches then flash. Simple and the only real way to flash a rom.

Tried to disconnect the account, doesn't work.

Matter of fact I did change my google password recently, maybe that's why I can't do ****.

stevew84 said:
Matter of fact I did change my google password recently, maybe that's why I can't do ****.
Click to expand...
Click to collapse
That would be it.

zelendel said:
That would be it.
Click to expand...
Click to collapse
I did that on the 10th, so one more day.

stevew84 said:
I did that on the 10th, so one more day.
Click to expand...
Click to collapse
Nothing to do but wait and see. Mind the swearing. The stars dont prevent infractions. Friendly warning.

stevew84 said:
I know I'm not the only one that experiences this as I've seen other users just accepting that issue.
As some of us know, when we flash from one ROM to another, there is a CHANCE where we'll get the login screen which says "The device has been reset...", which normally is followed by "Please login with the device administrator account", or something along those lines.
I've talked to Google, and I know others have also, and we're told that there is a 72 hour "security" feature that will not allow you to log into a freshly installed device, even though that device is yours and you were just using it 5 minutes prior to flashing the install.
There is no way to bypass this, at least I don't think, and Google doesn't have a way of resetting.
What I'm trying to find out is if someone was able to get around this, or has a work around because holy hell is it annoying.
Click to expand...
Click to collapse
Leave 'OEM unlocking' enabled in developer options. It disables this feature.

It resets every reboot

holeindalip said:
It resets every reboot
Click to expand...
Click to collapse
No, it's a sticky setting that is saved somewhere else. It even survives formatting of the system partition.

On 5.1 it was just a one time use thing and would reset upon it booting the system,must have changed on 6.0

holeindalip said:
On 5.1 it was just a one time use thing and would reset upon it booting the system,must have changed on 6.0
Click to expand...
Click to collapse
i never knew it other as being sticky. Anyway... leaving it enabled disables the "forced" login to the original Google account. I was locked out once before. When that happened i restored a working TWRP backup. Rebooted and enabled 'OEM unlocking' and never had a forced login again (i flash about 2 or 3 times a day). Also... check the popup when you enable "OEM unlocking".

Yeah all device security goes out the window with it left on

I got bitten by this problem. Until there is a solution I just have to wait the 72+ hours?

UNKNOWN SOURCES keep's turning itself off...? Anyway to make it stay enabled?

Not sure why, but a friend has a S8+ tmobile and the install from unknown sources ALWAYS turns itself back to OFF....? Is there some trick to making it stay enabled?

I'm pretty sure it's happening to everyone. Feel like it's their way of saying repeatedly that they would rather you not sideload apps that you probably got for free instead of paying haha. I've done research on this as well as its more of an annoyance. Most likely will have to wait for root

Yep happens on mine also

Yup, here too. Waiting for root sucks! Hopefully something will be verified soon. You guys should really google "SM-N950U root and you'll find a slew of root methods, I'm just too scared to try them. I wish they would just say error and nothing happens rather than have the potential to brick your phone. Oh well, waiting it is.

Nathan.7118391 said:
Yup, here too. Waiting for root sucks! Hopefully something will be verified soon. You guys should really google "SM-N950U root and you'll find a slew of root methods, I'm just too scared to try them. I wish they would just say error and nothing happens rather than have the potential to brick your phone. Oh well, waiting it is.
Click to expand...
Click to collapse
Trust me, as a dev myself, you dont want to listen to those. They have been tried already. And if they worked, it would be posted all over here as all the s8's on each carrier are the same phone. We are all working diligently to figure it out.
Except me right now. I'm at the doctor refilling my adderall so I can binge work on it all weekend hah

Acoustichayes said:
Trust me, as a dev myself, you dont want to listen to those. They have been tried already. And if they worked, it would be posted all over here as all the s8's on each carrier are the same phone. We are all working diligently to figure it out.
Except me right now. I'm at the doctor refilling my adderall so I can binge work on it all weekend hah
Click to expand...
Click to collapse
Haha yup I hear you. Thanks for your help on this. Keep healthy bro!

Well I'm sorry the unknown sources not sticking is a real thing... but I'm glad its not just her phone. I was convinced something was wrong and almost reflashed the firmware just because.... but it's obviously that way for whatever the reason. You just have to turn it on before each install I suppose. No big deal.
As for root, the eng boot was leaked or developed or whatever you want to call it... bottom line its in the wild now, so I think sooner rather than later there will be at least a eng boot type of root. Nothing compares to a real unlocked bootloader. *IF* I get a Samsung again, it will be the Exynos ###F model with a unlocked bootloader... But I'm a flashaholic....... otherwise ROOTING is becoming like jailbreaking is for the iPhone (non-existent).... at least for us USA owners anyway

I had this issue at first. This is my first Samsung phone since the Note 3. I thought it was something to do with KNOX. But after a week, I reset my phone, set it up as usual. And now the unknown stays. I can't recall what I did different, but I know wiping it did something.

Araltd said:
Not sure why, but a friend has a S8+ tmobile and the install from unknown sources ALWAYS turns itself back to OFF....? Is there some trick to making it stay enabled?
Click to expand...
Click to collapse
It's a bug. Should be corrected with a future update.

From what I've done, I believe it's actually Google turning it back on with the feature in settings, verify apps. Just turn it off and it shouldn't turn off the untrusted sources anymore. Since turning it off, I haven't had issues

Acoustichayes said:
From what I've done, I believe it's actually Google turning it back on with the feature in settings, verify apps. Just turn it off and it shouldn't turn off the untrusted sources anymore. Since turning it off, I haven't had issues
Click to expand...
Click to collapse
I think that did the trick for me. I had thought I already turned that off but it came back. Once I disabled that though my unknown sources has stayed at least for a few hours now and through me installing some stuff.
EDIT: there it goes back off again! doesn't seem to be anything we can do

sm-N950 custom navigation bar icon colors
Acoustichayes said:
From what I've done, I believe it's actually Google turning it back on with the feature in settings, verify apps. Just turn it off and it shouldn't turn off the untrusted sources anymore. Since turning it off, I haven't had issues
Click to expand...
Click to collapse
How were you able to change the navigation bar icon colors from the default white to green on your sm-N950?

I have turned ON "UNKNOWN SOURCES" on my phone 2-3 days ago and it is still on.

Anyone still having this problem?

What about the built in security app lookout, I have that and the google play verify off and have never had the developer option turn its self off I think it may be that app blocking harmful apps that we want to sideload by keeping that turned off maybe lol:good::highfive::goodI have had mine on since about mid sept. when i got the phone)

Having a hell of a time fixing this &$¥€©% thing

A few days ago, some of my lights, plugged into smart outlets, stopped responding. I couldn't get them to turn off or on via my phone or my Hub.
I tried clearing my app data. No go.
So then I got the bright idea to delete my home entirely. Didn't work, either. Then I realized they had another app of their own I had forgotten I had installed, so I went into that, removed all three, and set them up again. So now those work.
But the one "smart" bulb I have installed, can't be re-added, and I can't seem to add my Hub 2 to the speaker group (my gen1 Hub and Home mini show up, though). The bulb is one of those "C by GE" ones, and I tried resetting it by following the video tutorial. Neither "wax on/wax off" method worked (basically entails turning it off and on repeatedly, counting up to 8 seconds each time). I dunno if it's on an older firmware, or a 2.8+ one, but I didn't get the "3 blinks" reaction it was supposed to elicit, either way.
So, the short of it is, even with the C by GE app, I can no longer control that light bulb or even add it. The Home app, when I choose to add a light bulb, just kicks me back to the main dashboard with all the controls. Even after clearing the app data and storage. And no matter how many times I create and delete a speaker group, I can't add my gen2 Hub to it. It doesn't show as up there, but I can otherwise control it. Wtf.
Any ideas?

Try clearing the system cache.
Try a network reset.
Check settings and permissions of all associated apks. Clear data of the same.
Is all needed hardware enabled and working?
Any new apps, firmware, updates of any kind?
Set updated apps back to factory loads.
Changes you made?
Goggle search for similar reported problems in same make and expand the search if nothing is found.
Play with it... probably something simple*.
*once you find it

Yup, tried all those options and more.

GuyInDogSuit said:
Yup, tried all those options and more.
Click to expand...
Click to collapse
Something changed.
Forgive my ignorance as I like my devices dumb as rain stupid but how are you communicating with them, blue tooth?
I don't reccomend a factory reset as the issue would likely reoccur if you don't find the root cause even if it fixed it initially.
A factory reset would help to determine if a hardware failure had occurred though.

I don't know what changed, as I hadn't added anything to this setup.

GuyInDogSuit said:
I don't know what changed, as I hadn't added anything to this setup.
Click to expand...
Click to collapse
Auto updates, destroyer of worlds...
Perhaps something in the environment has changed ie RF interference.

blackhawk said:
Auto updates, destroyer of worlds...
Perhaps something in the environment has changed ie RF interference.
Click to expand...
Click to collapse
Huh.... No idea, really.

GuyInDogSuit said:
Huh.... No idea, really.
Click to expand...
Click to collapse
Well something changed, either settings, software, firmware or hardware.
Were any apps uninstalled recently?
It's rare on Android but uninstalls can changed buried normally untouchable settings and cause hell.
Most times the operator is the prime suspect... as I've found from experience

blackhawk said:
Well something changed, either settings, software, firmware or hardware.
Were any apps uninstalled recently?
It's rare on Android but uninstalls can changed buried normally untouchable settings and cause hell.
Most times the operator is the prime suspect... as I've found from experience
Click to expand...
Click to collapse
On my phone? How would that affect a smart home hub?

GuyInDogSuit said:
On my phone? How would that affect a smart home hub?
Click to expand...
Click to collapse
You never did say how they link up?
If the hub has internet access that opens a new can of worms. Malware is omnipresent at this point with technology.

blackhawk said:
You never did say how they link up?
If the hub has internet access that opens a new can of worms. Malware is omnipresent at this point with technology.
Click to expand...
Click to collapse
They're all connected to my Nest Hub.

GuyInDogSuit said:
They're all connected to my Nest Hub.
Click to expand...
Click to collapse
Never was even aware of that... so the issue may be on the hub side.
Have/can you do a network reset on the hub?
Sometimes, surprisingly, Google will support their products free of charge. Worth a shot.
I can now see why you're learning new curse words

blackhawk said:
Never was even aware of that... so the issue may be on the hub side.
Have/can you do a network reset on the hub?
Sometimes, surprisingly, Google will support their products free of charge. Worth a shot.
I can now see why you're learning new curse words
Click to expand...
Click to collapse
I had considered contacting Google but I thought I'd ask here first since it's visible to more people who might have knowledge about it. /shrug
I'll try the reset option.
Any ideas about that bulb? Or do you think the network reset could help with this?

GuyInDogSuit said:
I'll try the reset option.
Any ideas about that bulb? Or do you think the network reset could help with this?
Click to expand...
Click to collapse
A network reset is easy and pretty painless.
Try pulling the power and battery to force it to reset.
A factory reset is the last resort. If it had any major firmware updates this becomes more likely to fix the issue.
I couldn't find any option to clear the system cache like on most Androids

blackhawk said:
A network reset is easy and pretty painless.
Try pulling the power and battery to force it to reset.
A factory reset is the last resort. If it had any major firmware updates this becomes more likely to fix the issue.
I couldn't find any option to clear the system cache like on most Androids
Click to expand...
Click to collapse
This has... a battery??

GuyInDogSuit said:
This has... a battery??
Click to expand...
Click to collapse
I think so but it's just what I saw online.
It may not be easily accessible if so it's not a good option.
A Google search for this issue might net you a solution. Probably more common than you think.

I got the three Google devices added to a speaker group finally, somehow.
The light bulb, though, just ain't showing up. It's no longer kicking me out from the light adding process, though. It just isn't detecting it.

GuyInDogSuit said:
I got the three Google devices added to a speaker group finally, somehow.
The light bulb, though, just ain't showing up. It's no longer kicking me out from the light adding process, though. It just isn't detecting it.
Click to expand...
Click to collapse
Lol, sort of funny... I hope the light bulb lights up for you soon
Try a reboot. Cycle the slave device by disconnecting it from the power perhaps?

blackhawk said:
Lol, sort of funny... I hope the light bulb lights up for you soon
Try a reboot. Cycle the slave device by disconnecting it from the power perhaps?
Click to expand...
Click to collapse
Forgot to update on this.
I did get the GE bulb working. I attempted the factory reset thing again, and seems the third time was the charm. Might have helped that I unplugged the light fixture for a few minutes first.

Question Oppo find x3 pro always-on display doesn't work after android 12.

Hello everyone, I got the update 2-3 days ago and among the improvements I realised that the always-on display does no longer turn on. I tried changing the resolution, turning the feature on and off, restarting the phone, nothing..
Anyone else with the same issue or with ideas how to fix it?
Thanks and Merry Christmas!

do you try rest your phone

Have u done factory reset after update? It is advised to do so after major updates.

leroilion02 said:
do you try rest your phone
Click to expand...
Click to collapse
Not sure if you meant to type rest or reset, but I did try resting it, however I haven't reset it. I think I'll go ahead and do that

maxellxl said:
Have u done factory reset after update? It is advised to do so after major updates.
Click to expand...
Click to collapse
No, I think I'll go ahead and do it. I just wish that the built in back up feature was able to include the pictures/videos and the music, not only contacts, settings and apps.
Do you know a way to that on the phone itself? Because I don't have a pc available to me right now

RadAustin said:
No, I think I'll go ahead and do it. I just wish that the built in back up feature was able to include the pictures/videos and the music, not only contacts, settings and apps.
Do you know a way to that on the phone itself? Because I don't have a pc available to me right now
Click to expand...
Click to collapse
Google drive upload? MS One Drive. They have an option to automatically bakcup any image/video from your phone. Btw. I suggest setting up applications from scratch - not using any backups.

I am having the same issue. It was working after the update but in my case, it stopped working after I factory reset the device. I hope they issue an update soon to solve this.

Today I received the update, I wiped the phone and the Aod stopped to work

I got my update this morning and was gutted that it broke the AOD, however, I found this fix in another thread, worked for me.
Hi, to solve the problem with the always on display you need to install this fix:
https://drive.google.com/file/d/1iDluKHpyeMUQjtK3ONS9lNrDy2bnynPs/view
and then restart the smartphone.
it worked on my find x3 lite (IT).
I hope I was helpful

I shouldn't need to remind anyone that installing the above is a MAJOR security risk.

I would also be very careful about it.

Worked absolutely perfect for me!

Me too, I uninstalled straight after, still fixed.

All fine here

If you have this issue then factory reset the phone but do not restore it via Google backup on setup.
If you restore through Google you will lose AOD.

Guest69 said:
I got my update this morning and was gutted that it broke the AOD, however, I found this fix in another thread, worked for me.
Hi, to solve the problem with the always on display you need to install this fix:
https://drive.google.com/file/d/1iDluKHpyeMUQjtK3ONS9lNrDy2bnynPs/view
and then restart the smartphone.
it worked on my find x3 lite (IT).
I hope I was helpful
Click to expand...
Click to collapse
Can I have more details about this APK (source of the APK, permissions, actions, etc.)?
There's a lot of Realme GT family users with the same problem with AOD, and should be useful if can solve the problem without the factory reset
Thank you

alberto_y said:
Can I have more details about this APK (source of the APK, permissions, actions, etc.)?
There's a lot of Realme GT family users with the same problem with AOD, and should be useful if can solve the problem without the factory reset
Thank you
Click to expand...
Click to collapse
Sorry, I don't have any details, other than what was in the link I'm afraid. I'm normally super paranoid with this sort of thing. I suppose I trusted it because it was on this site
Sorry, I've only just realised I didn't give the link to the original thread, hang on . . .

Guest69 said:
Sorry, I don't have any details, other than what was in the link I'm afraid. I'm normally super paranoid with this sort of thing. I suppose I trusted it because it was on this site
Sorry, I've only just realised I didn't give the link to the original thread, hang on . . .
Click to expand...
Click to collapse
Thank you for the kind reply.
Please in which thread/post you found this link? Posted from which XDA user?
I'm sure that you want to help, but I think it will better to be a little paranoid, to avoid security Issues
I scanned it on Virustotal, and it show in the certificate "Android Team" from "Oplus.com", and [email protected], but after a short search I didn't found a website or a confirmation about that's OnePlus.
Then it requires android.permission.CREATE_USERS (maybe to fix some rights problem that origin the problem), and another thing oplus.permission.OPLUS_COMPONENT_SAFE.
Thank you

Hi
On my Oppo Find X5 is it still not working with the fix. Is there any other way to have it? (the corner ring light not working)