Hey guys - I am having a problem with my phone, and I am hoping someone can help? (Running stock/no-root, w/2.3.4)
A few weeks prior to the 2.3.4 release (while on 2.3.3), I noticed that an app called Bump was constantly running in the background (even though I had never launched the app before), and I'd have to constantly go in and manually kill it.
*Also I should note, Google Maps was another constant running app, that I would have to manually kill along with the Bump app.
This got tiresome, and since I wasn't using Bump anyway, I went ahead and uninstalled it. I figured that a recent update to the app/Bump, was the cause. After removing the Bump app, the problem went away (as well as the Google Maps stopped running in the background too - odd I know).
Anyway, the problem is back, but much worse this time - as this past couple of days, my phone is now running a bunch of apps in the background out of the blue!
1) Tango
2) To Market Lite
3) Google Market (even though I have Accounts & Sync/Background Data turned off)
4) Google Music
5) YouTube
6) Photaf
*Note: I have not launched any of the apps listed above in awhile, except for Google Market, which I turn on Background Data for this, and then turn off when I am done.
I have since removed Tango, but it hasn't solved the problem. It seems to happen the most when I turn my phone on (after I reboot, or if I charge over night with the phone turned off), but also will happen when phone is on during the day - with no reboot.
Anyone have an idea what's causing this, or how to fix it? TIA!
The best way to fix this is to stop worrying about it.
Apps do sometimes run in the background or have services waiting for some events to happen - it actuially HELPS battery life and performance and barely consumes any CPU cycles until something happens that triggers the app.
Killing them will drain your battery and make you crazy, more than letting the apps work as designed will.
patrixl said:
The best way to fix this is to stop worrying about it.
Apps do sometimes run in the background or have services waiting for some events to happen - it actuially HELPS battery life and performance and barely consumes any CPU cycles until something happens that triggers the app.
Killing them will drain your battery and make you crazy, more than letting the apps work as designed will.
Click to expand...
Click to collapse
Thank you for the feedback. I just found it odd that this just started happening, especially since some of the apps running were apps I haven't launched in ages (or ever used).
Also (and I forgot to mention in my post above), that a couple of the apps were running so hardcore - that it set off the alarm in Watchdog, as an app draining my battery and memory - telling me to kill it. So idk what to think, other than I find this behavior a bit odd.
Many of them are set to run based on conditions, like bootup, wifi on, widget added, etc. If you hate it, download autostarts from the market.
Sent from my Nexus S using XDA Premium App
i have a similar issue but as stated above i just leave them alone
Uhh, I cannot post this in development as I am still a newby :-(
However:
Hello,
I came from Symbian (Nokia C7-00) and liked the phone very much. Everything worked the way it should. (I was especially interested in office functionality.)
Now I bought a Galaxy Note and I really love the hardware.
But I discovered that it uses much energy and it doesn't like to sleep as often as it could. (I already returned to Android GB, which gives a better experience, but there still is room for improvement.)
1. Sometimes even though the phone simply lies around and does nothing, the last app that I forgot to close is hindering the CPU from sleeping. Why? The is no need.
2. At night I am used to turn the phone into flight mode. However I found out that this isn't the best thing for Android. In the morning, when the email app goes to push phase, the phone leaves sleep mode and seems to excitedly wait for the flight mode to get switched off. This uses *quite* a bit of battery!
These things seem strange to me. My impression is that Android is not really optimised for cell phones. If the screen is off, there is no need for CPU time, doesn't it? There is nothing urgent to do; everything could be done slowly; no hurry.
I guess the battery could last *much* longer if this would be improved.
Greetings,
corcov
corcovo said:
Uhh, I cannot post this in development as I am still a newby :-(
However:
Click to expand...
Click to collapse
Which is handy, because this thread has nothing to do with development and thus saved you from some abuse!
Regards,
Dave
Sent from my GT-N7000 using Tapatalk 2
But I already know how to click the "thanks" button
corcovo said:
But I already know how to click the "thanks" button
Click to expand...
Click to collapse
Doesn't matter.
Development, if you did not create IT, then it does not belong in development. Remember that. Otherwise you will get flamed.
Android is a mobile OS, so of course it is optimised for smart phones - not ordinary cell phones. Android acts like a computer and, if you keep a computer running Crysis 2 for example, it would burn more power than a computer just playing some music off of iTunes.
In terms of improving your battery, check your brightness. You can download widgets to adjust the brightness right from the home screens. I use these to set my brightness to its lowest whilst at home (perfectly adequate for night and indoor use away from sunlight) and turn it onto automatic when I go outside. This has saved my a bunch of battery.
If you are running a stock Samsung ROM, turn on power saving mode. I always leave it on and, frankly, I have no idea as to what it actually does. I haven't noticed a performance drop in the slightest, but if it saves a bit of battery it is worth it. Also, you could try Juice Defender or some other battery saving apps which work for some people - others not.
Finally, ensure you haven't left GPS, Bluetooth or WiFi on when not needed. Try downloading CPU Spy to check your phone deep sleeps, yet mine even without it ever deep sleeping gets around 16 hours of battery life which is still the best I have ever gotten on a smart phone. Bettery Battery Stats can show you wake-locks (apps that are keeping your phone active) also.
Brad387 said:
Android is a mobile OS, so of course it is optimised for smart phones - not ordinary cell phones.
Click to expand...
Click to collapse
I see. Well it might be a nice feature if one could add an "now be a cell phone"-option for energy enhancement, which means: if screen if off, sleep.
c.
corcovo said:
1. Sometimes even though the phone simply lies around and does nothing, the last app that I forgot to close is hindering the CPU from sleeping. Why? The is no need.
Click to expand...
Click to collapse
There are some legitimate needs for keeping the CPU from sleeping for a short period of time - such as finishing a sync operation (otherwise, the radio power spent beginning the sync is wasted). Unfortunately, some poorly written applications (Facebook for example) abuse the wakelock mechanisms and hold wakelocks when it is not justified.
2. At night I am used to turn the phone into flight mode. However I found out that this isn't the best thing for Android. In the morning, when the email app goes to push phase, the phone leaves sleep mode and seems to excitedly wait for the flight mode to get switched off. This uses *quite* a bit of battery!
Click to expand...
Click to collapse
This is not something I have ever encountered myself. "push" relies on the server to trigger something - in airplane mode, this trigger can't happen.
These things seem strange to me. My impression is that Android is not really optimised for cell phones. If the screen is off, there is no need for CPU time, doesn't it? There is nothing urgent to do; everything could be done slowly; no hurry.
I guess the battery could last *much* longer if this would be improved.
Greetings,
corcov
Click to expand...
Click to collapse
Android is well optimized for cell phones - However, it assumes that third-party applications follow Google's recommendations for power management. Unfortunately, many of them do not. The number of IM applications which choose to use their own proprietary and poorly optimized network protocols (such as Skype, it's atrocious) as opposed to Google C2DM (optimized and efficient) is astonishing.
An interesting note was that I believe much of the focus at Google I/O was on reminding app developers that they need to play nice with the system and other apps.
There are some cases where there are device-specific nonoptimalities. Compared to most Nexus devices, Exynos devices have an absurdly long time to resume from wake (1000 milliseconds), and during that resume cycle CPU frequency is locked to 800 MHz and cpuidle is disabled. This is one of the #1 causes of power drain on our device. This is also exclusively a Samsung kernel/hardware architecture problem that does not affect the Nexus S (similar CPU, but completely different modem interface) or the Galaxy Nexus (different CPU/modem interface).
In the case of our device, the modem is hung off of the CPU on a USB bus - this makes for very long resume times.
Here are obvious reasons the CPU should occasionally turn on when the screen is off:
1) MP3 playback in the background
2) Handling of background syncs - e.g. when an email or Google Talk IM comes in, wake the CPU, handle it, and pop a notification sound, then go back to sleep. Normally, this means the CPU sleeps while waiting for an interrupt from the WLAN chipset or the cellular radio. Unfortunately, some apps drive incoming data to the device far too frequently. (See my above rant about Skype's network protocols being crap compared to Google's C2DM protocol.)
3) Handling of scheduled wakeups (alarms, calendar events, etc) - these are rare and almost never consume power
Most power drain is from item 2, with third-party apps frequently behaving extremely poorly compared to Google's own application suite and sync protocols.
Now this an extensive answer which is very informative and helpful for me since insights are always soothing. Love it. Thanks!
not much to add after Entropy, but if you feel the need to get some control over battery usage you could try betterbatterystats app (and the thread) to identify battery eaters, besides that, there are few apps to check what is going on with your system when it sleeps:
- CPU Spy to show cpu states time
- Autorun Manager or Autostarts to disable triggers causing apps like FB to run without reason (those which you will find with betterbatterystats)
- Battery Monitor Widget, to check battery current consumption (mA) - this app is generally not recommended, because Note's hardware does not report the actual current, so the readings are highly estimated and because when poorly configured it can drain your battery faster, BUT otoh with refresh rate set at 5 minutes or more, it can give you some approximate orientation on how much battery you lose (better than counting %/hour by yourself) at negligible battery usage
- also, if you feel the need to disable net and sync during night, you could automate it using "lama", which is free, and in my experience does not eat much battery by itself
- and last but not least, avoid taskillers, those apps may have adverse effect, i.e. self restarting apps (by the triggers mentioned above), will get killed then restarted and so on and so on, leading to much higher battery drain
Hello everyone...
so I got the S4 about a week and a half ago and I really love it. When I first got it the battery life was great and the screen was the top killer of my battery as expected. But over the past 4 days the android os has been taking up 65% of my battery. I feel like it might be an app but then why would an app show under android os? Anyone have ideas or tip?
That happened to me on a custom rom, but not on stock. Which are you on?
I am on stock I have not rooted it as of yet.
I'd personally recommend rooting and then installing both Greenify and Better Battery Stats. Most likely it's an app running in the background and/or waking your phone up. A couple common things to watch out for:
- What are your location settings in both Maps and Facebook? Both are notorious for waking your phone up (sometimes 100 times per hour) to repeatedly report your location. If they are set to report from your device, I would turn location off and see if it fixes your battery issue.
- Google Now (to a lesser extent that Facebook and Maps) tends to search for your location as well. I personally turn Google Now off.
mjs2011 said:
I'd personally recommend rooting and then installing both Greenify and Better Battery Stats. Most likely it's an app running in the background and/or waking your phone up. A couple common things to watch out for:
- What are your location settings in both Maps and Facebook? Both are notorious for waking your phone up (sometimes 100 times per hour) to repeatedly report your location. If they are set to report from your device, I would turn location off and see if it fixes your battery issue.
- Google Now (to a lesser extent that Facebook and Maps) tends to search for your location as well. I personally turn Google Now off.
Click to expand...
Click to collapse
Thanks for the help, i will try that...but would both of those things show up under Android OS?
i think it is normal if you do not use your phone usually , android os should is the opera system of you smart phone.
So I am really angry at Android now, with all the issues and difficulties it is getting me through. Although visually and practically I still prefer it to iOS, there are some really annoying issues with it, that concern battery life/stability.
So there are apps that prevent your phone from sleeping, either leaves speaker on, or other BS. I have to close them every time I stop using the phone, to avoid a really stupid issue I had today. I recharged the phone 100% in the morning, later that day I went to check e-mails, sent a couple sms etc. and then I played this game called Pou, I left it running, the screen was off, but I didn't close it. Ended up with empty battery in 3 Hours.
This is ****ing ridiculous, what kind of smartphone is that, if it can't understand that I'm not playing games when the screen is off.
Is there at least a faster way to close all open apps, other than swiping from left to right 20 times every time you stop using the phone?!?!
What apps are causing the issue?
You're blaming the OS for the behavior of an app made by a bad developer. The vast majority of applications will not do that. iOS avoids that by limiting the cases in which an app is allowed to run in the background. You can argue that it's a superior solution for the end user, but it limits the ability for an app to actually do anything in the background.
Many custom ROMs build in a "kill all" button in the recent apps view. It's really not necessary though. You've identified an application that has this issue, so just make sure to kill that one app when you're done with it. Again, most applications won't have that problem.
raptir said:
You're blaming the OS for the behavior of an app made by a bad developer. The vast majority of applications will not do that. iOS avoids that by limiting the cases in which an app is allowed to run in the background. You can argue that it's a superior solution for the end user, but it limits the ability for an app to actually do anything in the background.
Many custom ROMs build in a "kill all" button in the recent apps view. It's really not necessary though. You've identified an application that has this issue, so just make sure to kill that one app when you're done with it. Again, most applications won't have that problem.
Click to expand...
Click to collapse
+1. I had just read a lot of silly things and ur comment relaxed me a bit. Blame a PHONE because some apps keep the phone awake... this is crazy, people should have a bit of experience before posting in this forum with so much arrogance.
This might help...
https://www.youtube.com/watch?v=JmvCpR45LKA
Sent from my Nexus 4 using Tapatalk 4
badboy47 said:
This might help...
https://www.youtube.com/watch?v=JmvCpR45LKA
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
That helped me so many times till I understood it....
The place to go, to get a definitive understanding of wakelocks is here:
http://forum.xda-developers.com/showthread.php?t=1179809&highlight=betterbatterystats
This is the thread for BetterBatteryStats, which is really all you need to troubleshoot why your device doesn't sleep enough.
Also, look at Greenify, which hibernates the apps you tell it to, a pretty unique trick.
http://forum.xda-developers.com/showthread.php?t=2155737&highlight=greenify
And as a last suggestion (frowned on by the purists at the betterbatterystats thread, but I find it really useful) use DS Battery Saver Pro, which will switch off wifi and reconnect every 10 minutes, amongst other tricks.
http://forum.xda-developers.com/showthread.php?t=2030696&highlight=ds+battery+saver
As an aside, I hear that iOS7 has impressed its user base with all sorts of hidden options which stop the phone resting, so maybe it's just a question of complexity . The good news is that, especially with the knowledge that is shared in betterbatterystats, it won't take you long to troubleshoot what your problems are, and the other 2 apps which will resolve your issues are pretty straightforward to use.
There are free versions I recall in the first post of these threads, I use the Pro version of DS Battery Saver since I prefer to configure my own profile.
Thank you everyone for replies.
I have not rooted the phone, so Greenify is no option for me, not really up to going through all rooting and ROM installing process in order to maybe succeed in solving the issue.
Specifically talking apps that leave speaker ON (It keeps hissing) and keeps phone awake, if you do not close them are following : Asphalt 8, Need For Speed Most Wanted.
The thing is I am not sure who to blame really, yes there are many apps that work normally and don't cause these issues, but then again why is the keeping the phone awake allowed in the first place, downloaded apps that would need to work that way should need special permissions. I understand there might be apps that want to keep ON/playing something after you have quit them, but if that's the case, then user should be able to deny certain permissions to prevent this from happening. The OS is complex enough, why not give even more options then or just this one at least.
Not sure how other people manage with this problem, I can't find anyone mentioning anything about Asphalt 8 and Android having this problem, people just deal with that they have battery draining to 0% in 5 hours? I know many people with smartphones 75% barely ever closes any programs from multitasker, most of them are iPhone users though. But how do they manage to live with their phone if they have this. I did manage to find people complaining about Pou draining battery, solution was to just uninstall the app, ridiculous.
I can't be the only one having these issues.
Well, the Android "style guide" has the back button as the exit function, so instead of leaving it running in the background, you may want to try backing all the way out.
It's been about a year since I played Asphalt (6 I think it was), but I vaguely remember it had an exit button which explicitly closed down the app.
Could be worth trying that. All the same, install the free xda edition of BetterBatteryStats (in the first post I think) and then look at the partial wakelocks, you'll quickly see what is stopping the phone sleeping.
paul c said:
Well, the Android "style guide" has the back button as the exit function, so instead of leaving it running in the background, you may want to try backing all the way out.
It's been about a year since I played Asphalt (6 I think it was), but I vaguely remember it had an exit button which explicitly closed down the app.
Could be worth trying that. All the same, install the free xda edition of BetterBatteryStats (in the first post I think) and then look at the partial wakelocks, you'll quickly see what is stopping the phone sleeping.
Click to expand...
Click to collapse
It really is like that, this fixes a small part of this issue! If you exit the game using the back button, the application closes the resource, but leaves it available at the multi task panel.
But, when I had iPhone, I could play the game, lock the screen, go home, for example, and continue where I left off, no battery drainage or anything. Only when you fill up the RAM memory it stops least recent processes.
Often it is very annoying to tap multiple times the back button (Sometimes even on screen you have to press quit multiple times (Quit current game & quit menu)) until you get to exit the application. And you can't continue where you left off, if you do that.
What the most bothers me about this is if I suddenly have something urgent and I don't turn off the application, my phone could drain a heavy amount of battery percentage till I remember to close them or check something on the phone/continue where I left off.
raptir said:
You're blaming the OS for the behavior of an app made by a bad developer. The vast majority of applications will not do that. iOS avoids that by limiting the cases in which an app is allowed to run in the background. You can argue that it's a superior solution for the end user, but it limits the ability for an app to actually do anything in the background.
Many custom ROMs build in a "kill all" button in the recent apps view. It's really not necessary though. You've identified an application that has this issue, so just make sure to kill that one app when you're done with it. Again, most applications won't have that problem.
Click to expand...
Click to collapse
luiseteyo said:
+1. I had just read a lot of silly things and ur comment relaxed me a bit. Blame a PHONE because some apps keep the phone awake... this is crazy, people should have a bit of experience before posting in this forum with so much arrogance.
Click to expand...
Click to collapse
Guys, this isn't the only issue with the OS. I had bad battery drainage from Wi-Fi & mobile network location setting also. I have various Google app problems, also with drainage, freezing and lag with Google Chrome, Google+ keeping phone awake. I would consider that as a property of Android OS, because the software was already installed when I got the phone. Chrome is the default and only internet browser in the beginning and it should work properly.
So I am not sure who to blame, maybe the developers can't find a workaround from the problem, because the OS is not behaving correctly, and I don't think that it's inappropriate to blame also the OS, since even the default apps and settings have problems same as some apps do.
I have used Chrome daily since it was first released for Android and have never had any real issues with it. Occasionally it will give me a problem where I need to restart the app but that's probably about once a week. Google+ should only keep the phone awake if you have it set to upload your photos automatically, and even then there's a setting to force it to only do the uploads when on the charger.
I think the key issue is that you're used to an OS that does not involve any thought from the user. I'm not saying that's a bad thing, but it's a distinctly different approach from Android. Apps are allowed to run when the phone is asleep because that can provide additional functionality. I'm sure you wouldn't complain if Pandora was playing music and thus running when the phone was asleep. And that would hit your battery hard. iOS only allows applications to run under very specific conditions, thus limiting what they can do but making sure you don't end up with any "runaway" applications. Android puts the responsibility on the developer to make their app handle battery life well and on the user to make sure they're using decent applications.
Things like the mobile network and WiFi location are used by Google Now to provide location-based data. If you would rather have the improved battery life, turn Google Now off. Some of us would rather have the functionality, but you have the option to disable it.
Keep in mind also that the Nexus 4 just doesn't get as good battery life as the iPhone 4 or newer.
raptir said:
I have used Chrome daily since it was first released for Android and have never had any real issues with it. Occasionally it will give me a problem where I need to restart the app but that's probably about once a week. Google+ should only keep the phone awake if you have it set to upload your photos automatically, and even then there's a setting to force it to only do the uploads when on the charger.
I think the key issue is that you're used to an OS that does not involve any thought from the user. I'm not saying that's a bad thing, but it's a distinctly different approach from Android. Apps are allowed to run when the phone is asleep because that can provide additional functionality. I'm sure you wouldn't complain if Pandora was playing music and thus running when the phone was asleep. And that would hit your battery hard. iOS only allows applications to run under very specific conditions, thus limiting what they can do but making sure you don't end up with any "runaway" applications. Android puts the responsibility on the developer to make their app handle battery life well and on the user to make sure they're using decent applications.
Things like the mobile network and WiFi location are used by Google Now to provide location-based data. If you would rather have the improved battery life, turn Google Now off. Some of us would rather have the functionality, but you have the option to disable it.
Keep in mind also that the Nexus 4 just doesn't get as good battery life as the iPhone 4 or newer.
Click to expand...
Click to collapse
I have never had a OS that I am fully satisfied with, that is normal, but I am always very aware for issues, always scanning for issues, I really hate that about myself, I am a perfectionist, I will not calm down until I get everything just the way I think it should be... So that makes up very difficult relations with any software I use, too bad for me.
Android apps do have more functionality, more freedom than iOS, and I very much appreciate that. BUT if that functionality results in 90% to 0% in 3 hours, when you forget to turn off 1 app after using it... please, I feel like it's a duty to take care of my smartphone, close app after you are done or the phone will die, and you will be left without a phone for the entire day.
I don't like that instability when you can make 1 thing wrong and it all goes to pieces, not when there are people using other phones with almost the same functionality and no problems like that.
No matter who I have to blame this on, I have this issue and it is because of Android & because of the developer of the app.
It's very sad, I really want Android to be more stable with this
Yukicore said:
It's very sad, I really want Android to be more stable with this
Click to expand...
Click to collapse
There are hundred millions of Android users, we don't all gets wakelocks. I don't have this problem and my phone is stable. Once you are using Android, you are no longer special and pampered in a walled garden like iOS users.
If you have battery drain due to Google services, see here: http://forum.xda-developers.com/showthread.php?t=2385843
I suggest doing a factory reset and not install crap apps like anything by Gameloft, just play them on Apple devices. If you gets a wakelock, make a shortcut on your desktop to Apps and check on what apps are running in the background, one of the app in the list could be the issue.
I know you don't want to root, but I suggest do it anyway and install Greenify, hibernate any apps you don't want autostarting when you boot up the phone. Watch out for apps that both runs in the background and ask for too many permissions. I know there is an app that limit the maximum app that can run in the background, but I don't know the name, you can set it in the phone's Developer mode, but it doesn't persist on reboot.
Maybe the difference is like moving from an automatic car (iOS) to a manual (Android).
At least before "multitasking" arrived to iOS, an app no longer in the foreground was effectively exited. Android's memory management is much more complex than that, and apps are kept in memory until a new app requires the RAM being held by a previous one.
There is a clear advantage to this since apps "reopen" instantly, but if you're not careful there could be continued drain from apps still open but not in the foreground.
Incidentally - I don't follow Apple closely - iOS7 has been slated by users for the scenario you describe, I believe!
Google's apps offer all sorts of wonderful location-based features, for which the phone inevitably needs to know its location. Coarse location (via triangulation of radio towers) is not a problem, but "fine" requires the GPS to be used, and that does drain the battery.
So you need to consider whether you want all that location based stuff from Google.
Wifi is also a big drain, and that is why I get my phone to switch on every 10 minutes via DS Battery Saver. The upside is that the phone sleeps regularly, but the downside is that Whatsapp messages etc don't arrive immediately.
As you can see, Android offers you the ability to choose to be uber-connected/always on, or to have a better battery consumption. Since each individual is different, you can choose what is important to you.
I just had that drain second time happening. I don't remember how I left that stupid game, but I ended up with 2% battery and phone turned off.
I think I exited using the back button. What the hell.
Pou is known to kill your battery.
http://forums.androidcentral.com/google-nexus-4/253092-media-server-draining-my-battery.html
http://answers.yahoo.com/question/index?qid=20130606043957AA9Tq7N
Since it's a virtual pet game the developer probably did not code it to close when you hit the Back button, so you need to kill it through Recent Apps. Or just uninstall it.
raptir said:
Pou is known to kill your battery.
http://forums.androidcentral.com/google-nexus-4/253092-media-server-draining-my-battery.html
http://answers.yahoo.com/question/index?qid=20130606043957AA9Tq7N
Since it's a virtual pet game the developer probably did not code it to close when you hit the Back button, so you need to kill it through Recent Apps. Or just uninstall it.
Click to expand...
Click to collapse
This is bad... Now it is developers fault, but why on earth should Android OS allow this kind of behavior on any app... This is not a simple background service, this was running fully when the screen was off. 2-4 hours is the screen on time averagely I get, 3.5 hours without screen on, it's damn fast draining.
Yukicore said:
This is bad... Now it is developers fault, but why on earth should Android OS allow this kind of behavior on any app... This is not a simple background service, this was running fully when the screen was off. 2-4 hours is the screen on time averagely I get, 3.5 hours without screen on, it's damn fast draining.
Click to expand...
Click to collapse
We've already been through this. You're fine with your phone's music player running in the background when the screen is off, right? It's the exact same behavior, just that Pou uses more resources and has no reason to be running. Apple puts heavy restrictions on what an app can do in the background (playing music being one of the only exceptions). Google leaves it up to the developer and user to manage it.
If you think that is a problem with the OS, I really recommend you go back to the iPhone. Not being mean or anything, but you clearly either do not understand the differences in philosophy between the two operating systems or you understand it and prefer the iOS way.
raptir said:
We've already been through this. You're fine with your phone's music player running in the background when the screen is off, right? It's the exact same behavior, just that Pou uses more resources and has no reason to be running. Apple puts heavy restrictions on what an app can do in the background (playing music being one of the only exceptions). Google leaves it up to the developer and user to manage it.
If you think that is a problem with the OS, I really recommend you go back to the iPhone. Not being mean or anything, but you clearly either do not understand the differences in philosophy between the two operating systems or you understand it and prefer the iOS way.
Click to expand...
Click to collapse
You said that user and developer can manage resources of apps, how can a user manage them? Can I fix this specific problem myself somehow?
Hey all,
So I've had my S8 since launch and I've enjoyed it but I have an issue that I've been trying to pinpoint the cause of for a few weeks now. At a high level, if I reboot the phone in the morning, I can use it all day as I wish and it works perfectly, no slowdown anywhere and good battery life. I plug the phone in at night when I go to sleep and when I wake up I start using it again. Either right after I wake up or over the course of a few hours the phone begins to slow down with things like notification shade/app switcher crawling until I either a) reboot or b) change display resolution. Doing either of these "fixes" it until the next night and then again when I wake up I have the same issues.
I've been trying to figure out what's causing this. I've tried disabling features, uninstalling apps, etc.
One thing I have found is that when I'm having this problem if I force close 'System UI' in App Manager (this is just restarting that process since you can't kill it really) the smoothness comes back but it doesn't last as long as when I either reboot or change resolution.
My theory is that something is conflicting with the Android UI and over time it's causing it to slow down. Rebooting or changing display resolution restarts the Android UI so essentially same thing.
My first question is has anyone seen this behavior where the notification shade/app switcher (native UI not apps) slow down? I know there's at least some people on Reddit with same issue. If you have this issue does FC'ing System UI 'fix' it for you temporarily?
I'm trying to figure out what is running on my phone while I'm sleeping at night which is obviously causing this. Any ideas would be helpful. Oh also when I wake up and I go into app switcher it only shows like 3 cards where before I go to bed it would be like 10+ so something is killing apps at night too. I turned off Google backup for today and will reboot before tonight to see if maybe that's it.
Appreciate your help.
Thanks.
I've had my S8+ since the launch weekend on ATT, always connected to my Gear S3, and connected to my Misfit Ray. I've not noticed any slowdown of the UI. My AOD clock is slow to show the hands if the screen is off when I use the numerical clock AOD, but nothing else observed.
I would guess you've installed (or haven't uninstalled/disabled) some apps that are using a lot of background processes. I removed/disabled the few ATT apps on the device except Call Protect, and I don't use Gmail (resource hog). I actually use very few Google apps, they're just not very well coded, it seems (maybe a "goof off" day every week isn't such a great policy?)
In settings, go to Device maintenance, click on battery, and see if anything strange is going on there under App power monitor.
I've NEVER liked Samsung phones, and I've NEVER been interested in owning one, but I saw the Galaxy Gear S3 and fell in love, and truthfully, I bought the phone as an accessory to the watch, so I'm not an apologist for any shortcomings.
Instead of restarting, go to settings/device maintenance, what's the percentage here? go to optimize, does it help? which apps use the battery most? How much RAM is available. If nothing shows up, you probably would need something like wakelock detector (it needs root) to trace apps usage, especially at night. Also you could try to force stop other apps and see which one is interfering? For example phone is slow, force stop first 10 apps, if not fixed force stop next 10, if fixed, next time force stop one at the time from that batch of tens.
Mines just started doing this the other day. I think I have an idea if the problem, I'm just trying to find proof at this point. I recently downloaded this all to let me see the upload/download speeds if my network in the notification bar. It lets you set the refresh rate, to which I set it to 2 seconds, which I knew regardless would tax my system, I just didn't expect my ui to slow to a crawl.
Delete any Bixby remapping app as well, known to cause many issues including unpredictable lag.