I recently upgraded my phone (Verizon S10+ 128GB) to Android 10 with the OTA update. Since then it appears that i can't keep any apps running in the background. Before i could have a Pokemon go running, go to something else for at least an hour, and when I switched back to it was still running and i didn't need to reload it. Now I will open Pokemon Go, go to a different app and within 15 seconds i go back to Pokemon Go and it has to reload. I have even added Pokemon Go to run in the background and to the exception list under memory. Is anyone else noticing this very aggressive app killing since they have updated to Android 10? I have also noticed that while using Nova Launcher there will be times when the home screen has to completely reload. The icons will take a second to appear and another second for the widget to pop up as if Nova Launcher was reloaded. Does this have to do with the the phone killing all the apps in the background?
I am not rooted or anything. This is a completely stock phone.
That's odd, I am on AT&T and haven't noticed it. Of course I use the 3rd party app greenify as well. Maybe try a data factory reset or reflashing the Verizon firmware with Odin?
imp3r10 said:
I recently upgraded my phone (Verizon S10+ 128GB) to Android 10 with the OTA update. Since then it appears that i can't keep any apps running in the background. Before i could have a Pokemon go running, go to something else for at least an hour, and when I switched back to it was still running and i didn't need to reload it. Now I will open Pokemon Go, go to a different app and within 15 seconds i go back to Pokemon Go and it has to reload. I have even added Pokemon Go to run in the background and to the exception list under memory. Is anyone else noticing this very aggressive app killing since they have updated to Android 10? I have also noticed that while using Nova Launcher there will be times when the home screen has to completely reload. The icons will take a second to appear and another second for the widget to pop up as if Nova Launcher was reloaded. Does this have to do with the the phone killing all the apps in the background?
I am not rooted or anything. This is a completely stock phone.
Click to expand...
Click to collapse
Cohld it be this?
diehard2013 said:
Cohld it be this?
Click to expand...
Click to collapse
Don't think so. I am experiencing this issue as well and the "Don't Keep Activities" option is turned off, so it's not the developer options.
I believe it is directly tied to the OTA update to Android 10 Q. I didn't experience all this force closing of apps before the update on Android 9.
I am curious if I changed the battery mode from "Optimized" in the Phone Settings (Settings > Device care > battery > Power mode) to maybe High performance would it fix the issue? If so, then we have a problem as selecting anything from High performance would kill apps such as Nova Launcher, or if you're editing a document and need to copy and paste from another app it would kill the other app before you can go back to it. This puts your phone back to iPhone 3GS era, and we don't want that
Hope someone finds a solution.
I did a recovery Data Cache erase and that seems to have fixed it. Something must have happened during the OTA. I haven't had any complaints now.
imp3r10 said:
I recently upgraded my phone (Verizon S10+ 128GB) to Android 10 with the OTA update. Since then it appears that i can't keep any apps running in the background. Before i could have a Pokemon go running, go to something else for at least an hour, and when I switched back to it was still running and i didn't need to reload it. Now I will open Pokemon Go, go to a different app and within 15 seconds i go back to Pokemon Go and it has to reload. I have even added Pokemon Go to run in the background and to the exception list under memory. Is anyone else noticing this very aggressive app killing since they have updated to Android 10? I have also noticed that while using Nova Launcher there will be times when the home screen has to completely reload. The icons will take a second to appear and another second for the widget to pop up as if Nova Launcher was reloaded. Does this have to do with the the phone killing all the apps in the background?
I am not rooted or anything. This is a completely stock phone.
Click to expand...
Click to collapse
I have a UK, EE locked 10+ and this used to happen to me when i was running a high RAM app (games basically).
I also believe it has been reduced (eliminated?) from the last large fw update my phone went through a week ago (the samsung UI update, sorry thats a bit vague - as opposed to a more recent 128MB security update).
So i'd guess this is not carrier specific and relates to the samsung fw?
Hope this helps.
I'm experiencing this, and I've been on 10 since beta2, but it just started happening today. Even apps that I "lock" are closing almost immediately.....
Related
I know I saw various posts regarding the Launcher force closing before the 3.1 update.
After the update, I continue to get force closes on the launcher and various applications. For the most part, I only run Honeycomb designed apps with a couple of exceptions.
Anyone else continuing to have the Launcher force close after the 3.1 update? Thanks.
codeworks said:
I know I saw various posts regarding the Launcher force closing before the 3.1 update.
After the update, I continue to get force closes on the launcher and various applications. For the most part, I only run Honeycomb designed apps with a couple of exceptions.
Anyone else continuing to have the Launcher force close after the 3.1 update? Thanks.
Click to expand...
Click to collapse
Yes, I do. Did you get any other helpful replies?
glg
glgehman said:
Yes, I do. Did you get any other helpful replies?
glg
Click to expand...
Click to collapse
Me too -- just FCs randomly as best I can tell. I run lots of widgets, though. Beautiful widgets, email and gmail, wizz widgets, 360 news, music, etc. Mostly just a minor annoyance, but I'd love to get it cleared up. I've run fix permissions multiple times. Running Prime1.5 and clemsyn-blades v16.
I used to get those FC's often on the launcher and almost any app I used when I was on 3.01, but since installing 3.1 I have never got it on the launcher anymore and only seen it on a couple apps that weren't completely compatible with the TF so it seemed to fix it.
Is the problem in the lockscreen?
I installed Flyscreen after reading about it in another thread -- it adds widgets to a Honeycomb look-alike lock screen. Since it's really just an app, I was still getting the official lock screen after unlocking Flyscreen, so I went into settings -> location & security -> configure lock screen ... and set it to "off".
Suddenly, I'm not getting the launcher force closes anymore. It's only been about 12 hours (including overnight) - but I was getting a couple of closes per hour before. The lock screen settings change is the only thing I've done in/around the time that things settled down. I'm hopeful that this somehow did it.
I'm guessing that Flyscreen isn't necessary -- just changing the lockscreen settings. Maybe you could even turn them back on and not get closures? I'm happy to leave well enough alone on my tablet, but maybe this will help someone else.
** by the way - I'm running Prime1.5 with Clemsyn-BladesOC#16. But I've had the FC issue as long as I can remember, even with Primordial and stock kernels (I rooted right after getting my TF).
I have disabled HiVoice app which was using the home button using tool called Debloater! Now I am having a problem with my Huawei Honor Note 8 where I have given all permissions to Google app to act as my home button which works with the app or settings page opened but after I clear apps in the background it ceases to work until I go into Settings and disable and renable it from the Assist (changing what holding home button does). It will do the same again after clearing apps. Endless repeat. Is there a solution to this
I don't know who's bright idea it was at Huawei but clearing the running apps kills so many background processes too. Even protected processes get killed so I NEVER do that on this phone. It messes up so many notifications & running apps for me. It's one of the few things I absolutely hate about this phone. But again if you just never do it... it's kinda normal again.
I have never seen such bad management. I have resorted to keeping Facebook Messenger and Google in my recent apps list and never using kill button. This is very inconvenient. I can't forgive Huawei for doing this. Why won't they let us delete Phone Managed app even using Debloater doesn't recognise the app. This kills battery life by havinf the apps opened in recent app view. Seriously! Huawei I won't buy another phone until this is fixed. Will we be getting Nougat, this doesn't seem to be a popular phone online
It's one of the reasons I can't wait for a stock rom!
I'm going to wait until Nougat EMUI rom or Stock Nougat. I don't want to go backwards.
anyone that can help. I have gave it drop zone permission, autostart permission, trust app with all permissions and app secondary launch. nothing works!
Hi,
I noticed that with the new update to EMUI 5 my Phone Manager is not working properly.
It's not closing the marked apps on 'Close apps after screen lock' setting.
To test this i first mark an app to be closed on screen lock, when i unlock my phone the app is still running.
Also i'm receiving notifications from said app when my screen is locked (ex. facebook).
Even when i run the battery optimiser manually he states that X amount of apps have been closed on background, although they are still running...
I did my update via OTA with a fresh factory reset after it. Then i used Huawei Backup tool to restore the state of my apps. More recently i even reset the Phone Manager app data twice.
Are you experiencing any similar issues?
jpcafe said:
Hi,
I noticed that with the new update to EMUI 5 my Phone Manager is not working properly.
It's not closing the marked apps on 'Close apps after screen lock' setting.
To test this i first mark an app to be closed on screen lock, when i unlock my phone the app is still running.
Also i'm receiving notifications from said app when my screen is locked (ex. facebook).
Even when i run the battery optimiser manually he states that X amount of apps have been closed on background, although they are still running...
I did my update via OTA with a fresh factory reset after it. Then i used Huawei Backup tool to restore the state of my apps. More recently i even reset the Phone Manager app data twice.
Are you experiencing any similar issues?
Click to expand...
Click to collapse
I have the same issue on B370, VNS-L31...I think it's a general bug and it will be resolved in the next update(I hope so..)
robi10101298 said:
I have the same issue on B370, VNS-L31...I think it's a general bug and it will be resolved in the next update(I hope so..)
Click to expand...
Click to collapse
Cool, thanks for the reply!
Phone Manager was perfect for me on 4.1 not sure why they messed with it.
Protected Apps made more sense than Allow All, even the smart battery setting is gone..
My issue is the phone manager is closing apps that I want to stay open
jpcafe said:
Cool, thanks for the reply!
Phone Manager was perfect for me on 4.1 not sure why they messed with it.
Protected Apps made more sense than Allow All, even the smart battery setting is gone..
Click to expand...
Click to collapse
I always have Power Saving Mode on and I have like 5-6h screen time on, and it s OK for me...
Recently I am having notification delays with my S7 Edge G935F. I have read through some posts on this forum and other sources and can't figure it out.
Here are some of the problems:
1. notifications are often delayed for more than thirty minutes
2. if I want to manually check notification when it does not pop up, unlocking the screen does not make the notification show, I have to actually launch the specific app to see the notification
3. It is more than just not showing the notification, when I am using some instant messaging apps (like WeChat), I can't see new messages coming in while the app is running in the front. I have to press the home button and get back to home screen, then re-enter the app, then the messages show up. This happens to many other apps as well.
4. Other things go wrong as well. For example, my Android Auto was set to launch whenever I get into my car and car bluetooth is connected. It is also delayed, by more than hours. It often launches long after I finish my driving and get back home sitting on my couch.
5. Downloading new apps from Play Store has problems as well. It downloads to 100% and just stops there, it does not start installation. I have to use Settings->App to kill Play Store and re-open it to "refresh" it, then it starts to install.
6. After installation of new app, it does not show up on my screen or app draw inside my launcher. I can see the app installed in Play Store. I have to kill launcher and re-open the launcher to make it "refresh" the app list then I can see new app inside the app draw.
I have also tried a lot of ways to fix it:
1. change app to not battery optimized -> didn't fix it
2. update firmware -> didn't fix it
3. factory reset -> works for the first day then it goes wrong again
4. flash to a different firmware (official ROM in different regions) -> works for the first day then it goes wrong again
5. use third-party ROM (Lineage OS) -> completely fix the problem, but too buggy to use
I can see the general idea of what's going wrong, some events happened (connected to car Bluetooth, new messages coming, app finished downloading, new app installed, etc.) and the system is not responding correctly. I am not very familiar with Android development but I feel like something is wrong with the "event handling" or "event raising" inside Samsung's Android system.
Please post reply if you have any idea or are facing the similar problems.
EDIT:
The phone is on Android 7.0, Build Number NRD90M.G935FXXU1DQER
You've stated that flashing the custom ROM solved the problem, so maybe you should try flashing a different rom that's a bit more stable.
From personal experience i can recommend the SuperStock rom. It's stock (obviously) and it's debloated and very stable with pretty good battery life as far as i remember.
there is some info about it here: https://forum.xda-developers.com/s7-edge/help/want-to-root-custom-one-stay-stock-t3631098?styleid=18 (ignore the root part).
Hi,
did you find any solution to this problem ? cause i got the same problem, and i'm going crazy... few months already and can't figure out what is the problem...
the temporary fix i've found is disabling the "google app" in application manager... it fix the problem but i can't use any Google app features (and i like using them...).
I've found few ppl experiencing the same problem searching on internet but no one with a real fix...
if someone more experienced can help debut this it would really mean a lot...
I think it is the battery optimization setting. You may check the settings>battery>advanced settings>optimize apps. You need to keep the apps un-optimized if you want the notifications and sync.
Also, you may check if Sync is on or off.
If these two does not solve, factory reset if you are on stock ROM. If on a custom ROM, you may check a different ROM
Hi,
Thanks for your reply. Actually none of this works... The only thing that "fixes" the issue is disabling the Google app in the application manager... That's why its so weird...
The problem started around July/August 2017 for me...
As i discovered that disabling Google was fixing the problem, i assumed that they'll correct it by updating the app... But only one update of the app was ok, all others would make the problems reappear...
Messing with battery optimization settings doesn't change anything for me... Factory reset as well... The problem comes back as soon as the google app gets updated...
Try clearing cache and deleting data from the Google app the time the problem occurs
already tried... doesn't help at all...
Things were going great the last few days on Android P until this morning. All of a sudden, post a few playstore app updates, the OS became unusable. Google Services (this apk possibly got an OTA update) kept stopping in a loop and all apps started closing....which ended up blocking me from using the phone (couldn't access settings etc. and was too lazy to adb into the device to troubleshoot). Ended up rolling back to oreo. Anyone else faced this?
More information please, where you rooted, custom kernel.ect
I was getting fc'z like crazy yesterday after a fresh install, what I ended up havingto do was a factory reset in twrp and have had none since.
No root, no custom kernel/recovery. Just pure Google provided images and apps from play store
dreamtheater39 said:
Things were going great the last few days on Android P until this morning. All of a sudden, post a few playstore app updates, the OS became unusable. Google Services (this apk possibly got an OTA update) kept stopping in a loop and all apps started closing....which ended up blocking me from using the phone (couldn't access settings etc. and was too lazy to adb into the device to troubleshoot). Ended up rolling back to oreo. Anyone else faced this?
Click to expand...
Click to collapse
no such issues here (yet).
clean install, no root.
Clean install of Android P with Magisk 16.1 last night. No issues so far but I'm not even 24 hours in. I do know that the Android P dev notes from Google report that the system can get extremely unstable over time. So the OPs issues make sense.
The way I'm looking at it is if my phone runs perfectly on Android P for 5-6 days before starting to hiccup, then I have no problem quickly reflashing Android P without wiping data every 5-6 days since it takes like 30 seconds and doesn't force me to re-download or re-setup any apps. To me, this would be worth it in order to run an otherwise stable version of Android that most other phones won't get until this time next year.
But, if I only make it 48-72 hours before the phone starts really acting up, I'll probably go back to 8.1 until the next iteration of Android P dev preview is released.
Clean flashed P the day it dropped, flashed magisk and flash when both were updated to support them. Only minor crashes every other day or so.
Playstore has a "huge" bug.Did you have beta apps (like WhatsApp,play services etc)? When you go to the tab "Beta" and try to hit on an application, playstore closes without fc message.
Clean install, no root. Widgets disappear randomly once or twice a day.
afilopou said:
Playstore has a "huge" bug.Did you have beta apps (like WhatsApp,play services etc)? When you go to the tab "Beta" and try to hit on an application, playstore closes without fc message.
Click to expand...
Click to collapse
Just tested this and can confirm the same issue for me.
mrnovanova said:
Clean install, no root. Widgets disappear randomly once or twice a day.
Click to expand...
Click to collapse
Stock launcher or a differnt launcher? I've been using Nova Prime since installing Android P 2 days ago and haven't had any issues with widgets disappearing or malfunctioning.
sn0warmy said:
Just tested this and can confirm the same issue for me.
Stock launcher or a differnt launcher? I've been using Nova Prime since installing Android P 2 days ago and haven't had any issues with widgets disappearing or malfunctioning.
Click to expand...
Click to collapse
Stock Launcher. Might have to switch to NOVA. This is getting annoying.