Last night I was at home and noticed my wifi wasn't on, so I used the quick settings in the shade to toggle it. After a few seconds, wifi connected, and some unknown app took focus and closed repeatedly. After a few moments, it stopped and all was well.
I thought it was strange, so I turned wifi back off and the same thing happened. I rebooted, tried again, and got the same result. I was trying to think of a way to see what was happening, so I tried using the Screen Record function in Gravity Box, which didn't help much, because it happens so fast, and no info is displayed, just a black window that goes away quickly.
I then turned on the CPU usage in Developer Options to see if anything consistently came to the top when toggling. I saw a few apps each time Plume (Twitter), and Maildroid (email) were two of them. Both of these apps behave differently on wifi and 3G/4G (push vs. pull), so thought -maybe- it could be something with that. I uninstalled both of those, rebooted and tried again, getting the same result.
I recorded the screen when this was happening with the CPU usage displayed, and was wondering if anyone has any ideas? I don't really want to uninstall and reinstall EVERY app on my phone, so I was hoping someone may have seen this before or see something I'm missing when watching it happen.
Video: https://copy.com/8L6VTsqcdbUjVTz
Thanks for any input anyone can offer!
Do you check virus from your phone ?
I am also having this, seems to be due to 4.4.2 OTA, which I continue to delay as I am rooted.
Mine doens't only happen with wifi change, but also just randomly when using hangouts, keyboard stays out but hangouts min -> maxes quickly. I have tried freezing the update apps but it apparently didn't do anything as I was still asked to update earlier.
Only hangouts? I have that app disabled.in the app settings.
I can't say for sure that being on 4.4.2 fixed it, but I am on 4.4.2 now and it is not happening anymore.
I unlocked my bootloader and did the 4.4.2 SBF, unlocked and rooted. I installed probably 99% of the same apps (only ditched 1-2 that I never used anymore) and I am not having the flashing issue anymore.
Hard to tell for certain if the pending OTA was the cause, but it may have been.
It worked when I first booted up. After a few hours it quit. I did a factory reset, and the same thing happened. I then went through my running apps and turned them off until none were running except the system apps. Still didn't work.
Anyone else have this happen that can suggest a fix? If I have to reset and install apps one by one, how do I do that, since on signing into Google the apps auto load
gmermel said:
It worked when I first booted up. After a few hours it quit. I did a factory reset, and the same thing happened. I then went through my running apps and turned them off until none were running except the system apps. Still didn't work.
Anyone else have this happen that can suggest a fix? If I have to reset and install apps one by one, how do I do that, since on signing into Google the apps auto load
Click to expand...
Click to collapse
To fix auto load, you can change the system setting to not backup apps; it's in Settings > Backup & reset. I thought upon initial Google account sign in you could switch that setting off too, and that prevents the apps from auto-installing. I have backup turned off because on previous devices and versions of Android it was contributing to battery drain.
laur3n.newm4n said:
To fix auto load, you can change the system setting to not backup apps; it's in Settings > Backup & reset. I thought upon initial Google account sign in you could switch that setting off too, and that prevents the apps from auto-installing. I have backup turned off because on previous devices and versions of Android it was contributing to battery drain.
Click to expand...
Click to collapse
I did what you suggested, adding single apps and confirming the ambient function worked. Found an app that seemed to be the cause, and upon uninstalling it the ambient function came on line. However, about a half hour later, it stopped working again. Spent over an hour on the phone with Moto, and they figured out that ambient doesn't respond unless the phone has been asleep more than 10 seconds. That seemed to work for me. So I did my 4th reset/install of the day, and again, it worked for a while, even with all my apps (including the one that seemed to be the cause in the first place). And then, it stopped again.
I searched, and one suggestion was that ambient won't work unless you have a locked screen. I usually don't use a lock, but what the hey, I'll try it. Set up a pattern unlock and (wait for it.........).
Nope.
I'm stumped.......
Mine seems to stop displaying the ambient as well. It will display a few times initially and then stops. I don't know if it extends its sleep period after every interval or not. Also seems like if you lift up your phone to look at your ambient notifications, that disables any repeat display too
I have been on Marshmallow since the official release this past Friday. I am no rooted, never was on this phone. Phone is completely OE.
I have noticed a few issues and gripes.
1) No more volume control for just notifications. They are now controlled in with the ringer volume. To me, that sucks.
2) Smartlock is not working properly. I have to enter my password to unlock my phone 80% of the time in locations where it should be unlocked. (Home and work)
3) Where are the Doze settings?? I have looked all over for Doze and do not see it. Did T-Mobile decide not to include it?
4) I will find out for sure tonight, but when my battery got low the last 2 days, I lost LTE, was on 2G, and no wifi calling. Basically I had a phone that worked but was a paperweight. I do know there was an outage last night, I am hoping thats all it was, but I do notice my phone running slower and harder connections at lower battery levels.
4) Apps just stop working. I have to clear out my recent apps, and reboot my phone to get apps to work. Chrome wont load pages, Facebook wont load more than 20 (est) updates, news apps (local and CNN) wont refresh or load.
If anyone has had the same issues or maybe a fix, please help! Thanks in advance.
Sent from my HTC One M9 using Tapatalk
since the news of the m10 and the last update my m9 barely functions crashes all the time have reinstalled the rom from the ruu file from htc no it's never been rooted i've replaced the battery when it crashes it has to be pluged in to power on ALL my settings are lost and apps won't function. i've gotten notices not pushes thats google exchange wont function as well as some other apps have restarted in safe mode no difference only thing i can do to stop the notices is turn off the data functions wifi and data. any thoughts
Hi Guys
Never had a problem with my P9, never had a problem with software.
I am currently on EVA-L09C432B378 software (official Android 7.0) and yesterday, due to the issues with network provider, I thought that phone is playing up (no internet despite 3G icon in notification area) so I have restarted it twice or three times.
After restarts, phone was not getting any phone signal, but that was not because of my phone.
Just the network ("Three") had some issues (found out later on on their Facebook profile).
Anyway - after those restarts, I have noticed that almost all my personal settings are gone and phone is almost like it would be after factory reset. Main ringtone has changed back to the default, notification tone went back to default, notification and status bar all settings went to default, brightness settings, sleep timeout, auto-rotate went off, eye-comfort went off, vibrate when ringing went off, also the Do not disturb is now "Off" and I do have to set things like this again.
The options which did not change are Wifi, Bluetooth (including remembered networks and devices), PIN, smart unlock, fingerprint ID.
Did anyone ever had such a strange thing and do you know if there is a way to backup only the phone settings (even using built in Huawei Backup app)?
Yes i have had this a couple of times - personal prefs change, back to default keyboard, default ringtones and some (but not all) apps need to be logged in again.
Ive recently flashed up to B390 - will see if it behaves itself more!
Make sure you're not logged in as a guest on your device. Settings/Advanced Settings/User Mode
Sent from my EVA-L09 using Tapatalk
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.