So I am reading the tips and tricks article - GREAT article by the way! - and I come upon the note stating to not use task killer (shown below in bold).
SHOULD I USE A TASK KILLER?
Absolutely not. You have the best OS and one of the best spec'd phones ever. You would be doing more harm than good. If you do have one, uninstall, reboot and let me know what you think!
In addition, even Google at Google I/O 2010 addressed app developers and asked them to no longer include "quit" or "close" as options within their apps. I think Andronica (another great android site) summed it up well with their article, found here.
XDA user iunlock created a thread with some good debate based off this sticky. You can read all the thoughts by clicking here. In short, the overwhelming majority agreed and some have commented on seeing an increase in performance after deleting their task killers. Awesome job guys.
That having been said, I went a day. Sure, it ran smooth, but my battery life stunk.
I'd like to hear from other users on the pros/cons of using a task manager on your Vibrant. Not trying to start a flame war, just wanting to hear thoughts other than my own (and the little voices that come from the ear piece of the phone )
Personally I am completely for it, as long as you are not killing off critical processes or apps that you use on a regular basis. Bottom line here - know what you're doing.
Feedback please?
I had the exact opposite reaction after getting rid of the task manager, battery life increased.
I kept ATK, battery life improved with it. If i play games and then hit the Home button which i always do. it stays running in background and kills the battery. Didnt really notice much of an impact with performance but my battery life increased
I use task manager. people can say what they want, but lowmemorykiller is designed to kill apps when the system needs memory. our phones have a lot of memory so they are capable of keeping so many apps open, if no one believes me download a task killer and just open it up to see how many apps are really running on your phone, its ridiculous, especially if you still have the bloatware. I don't necessarily use it because my phone bogs down from so many apps (that reason was back in the day with my g1) i do it because theoretically your battery life should go up. What's worse, a task killer running, or the last 20 apps you've used? All I know is my phone runs fine, smooth, and has battery life that I really cant complain about. It's hard to really tell what is correct though, I mean theres's hundreds of posts about the gps on our phone and mine launches up, finds my exact location within 30 seconds, and navigates perfectly. Got mine the day it came out, so ive really never worried about what other people have said, i just find out for myself. try both and see what you observe to be best.
I own(ed) a G1, Google Ion, myTouch, CLIQ, Behold II, Nexus One, myTouch Slide, GARMINfone, and Samsung Vibrant.
I have never used a task killer / manager on any of them and have never experienced lag on any of them.
My battery has also lasted from wake (9am) to bed (im usually in the bed by 11pm, sleep comes much later) on all of them and that includes at least 2 hours of stereo Bluetooth music. WiFi, GPS and Sync on all day. Bluetooth and brightness are managed as needed.
I'm no developer, but I have flashed my fair share of roms, and run plenty of tests. I don't know what is best, but I do know that they are NOT NECESSARY. Are they helpful or useful to you? Possibly. If you want to use one, have fun. I see no reason for me to start now...
EDIT: I also play a fair bit of SNESoid, GENSoid, and now PSX4droid....
Also, I don't have a car charger or office charger. I only charge overnight.
If you have to use a charger during the day, you blew it.
Task Mangers slow my phone down more. I don't use them.
joe.kerwin said:
I use task manager. people can say what they want, but lowmemorykiller is designed to kill apps when the system needs memory. our phones have a lot of memory so they are capable of keeping so many apps open, if no one believes me download a task killer and just open it up to see how many apps are really running on your phone, its ridiculous, especially if you still have the bloatware. I don't necessarily use it because my phone bogs down from so many apps (that reason was back in the day with my g1) i do it because theoretically your battery life should go up. What's worse, a task killer running, or the last 20 apps you've used? All I know is my phone runs fine, smooth, and has battery life that I really cant complain about. It's hard to really tell what is correct though, I mean theres's hundreds of posts about the gps on our phone and mine launches up, finds my exact location within 30 seconds, and navigates perfectly. Got mine the day it came out, so ive really never worried about what other people have said, i just find out for myself. try both and see what you observe to be best.
Click to expand...
Click to collapse
Android has a task killer built in to kill apps if memory is low automatically.
Couldnt enjoy my phone without one.
laristech said:
Task Mangers slow my phone down more. I don't use them.
Android has a task killer built in to kill apps if memory is low automatically.
Click to expand...
Click to collapse
I know, read. I referenced that in the first line. It's a low memory killer, my phone still has 100mb of memory available even with 15-20 apps open. I'd rather have those tasks not running if i've finished with them. Plus apps also reopen periodically by themselves, auto-kill on a 3rd party task killer will kill this as soon as the phone is sleeping, the build in task killer will not.
AndroidZ28 said:
I own(ed) a G1, Google Ion, myTouch, CLIQ, Behold II, Nexus One, myTouch Slide, GARMINfone, and Samsung Vibrant.
I have never used a task killer / manager on any of them and have never experienced lag on any of them.
My battery has also lasted from wake (9am) to bed (im usually in the bed by 11pm, sleep comes much later) on all of them and that includes at least 2 hours of stereo Bluetooth music. WiFi, GPS and Sync on all day. Bluetooth and brightness are managed as needed.
I'm no developer, but I have flashed my fair share of roms, and run plenty of tests. I don't know what is best, but I do know that they are NOT NECESSARY. Are they helpful or useful to you? Possibly. If you want to use one, have fun. I see no reason for me to start now...
EDIT: I also play a fair bit of SNESoid, GENSoid, and now PSX4droid....
Also, I don't have a car charger or office charger. I only charge overnight.
If you have to use a charger during the day, you blew it.
Click to expand...
Click to collapse
There's no way your g1 ever lasted 14 hours, let alone consistently with that usage. Either that or you dont understand how some of us use our phones. The only reason this must be such a debated topic is because there truly isn't much of a difference. Will your phone have a weeks worth of battery life with one? No. Without one? No. Users preference I suppose, but before i deleted bloatware, my telenav and slacker radio were always open and i honestly never even opened them to even check them out.
That having been said, I went a day. Sure, it ran smooth, but my battery life stunk.
I'd like to hear from other users on the pros/cons of using a task manager on your Vibrant. Not trying to start a flame war, just wanting to hear thoughts other than my own (and the little voices that come from the ear piece of the phone )
Personally I am completely for it, as long as you are not killing off critical processes or apps that you use on a regular basis. Bottom line here - know what you're doing.
Feedback please?
Click to expand...
Click to collapse
People will give all sorts of anecdotal evidence one way or another about this topic. Just keep in mind that anecdotal evidence won't answer the question. It's not a simple yes/no question either.
Here's the deal. *IF* you have errant tasks that are causing partial wake issues (running too much or too often when the phone is supposedly asleep), those applications will be the culprit for your bad battery life.
These are not likely to be core tasks of the OS, or OS bundled bloatware either...but they can be. When I had my Behold II and was running ADW.Launcher, for instance, I had to use a task manager to keep parts of Touchwiz from waking up and complaining about the UI not being front-and-center. And the reason WHY I used a task manager was a simple one. It was a core data task of the embedded software that could not be REMOVED.
The best solution to partial wake issues is to identify the tasks that are causing them, and GET RID OF THAT APP. In my very specific case above I was unable to do so, so a task killer had value.
The reason why task managers can be a very bad idea are legion. The Android OS runs a lot of interdependant tasks, and killing one seemingly innocuous task can and often will start a domino effect with other tasks that rely on them. It can even cause other dependant apps to eat 100% of cpu time during sleep cycles or at other times, and make your battery life mysteriously go to hell.
So far on this Vibrant, I've found no core tasks causing partial wake issues. Third party apps and widgets however, I've found quite a few that "wake up" and cause partial wake issues (i.e. they are spending too much time working and running when the phone is in "sleep" mode). Pure Messenger Widget being one of the nastiest I've tried lately.
What do I recommend? Use the built in battery statistics, and install the market app "Spare Parts". This combination will give you the ability to glean useful information about exactly what is running and what it's doing. There are other tools and whitelist managers that you could employ as well, but this is enough for me.
And even if you are running task managers and killers, you should be using the above to know whether what you are doing is a complete waste of time or even making matters worse.
When left to its own devices, Android 2.1 does a remarkably good job managing tasks and memory, PROVIDING THAT 3RD PARTY APPS ARE BEHAVING. Since we all run a very different set of 3rd party applications and widgets, it's no wonder that people are having battery life issues (great, bad, not so bad, etc..) all over the map.
I use Advanced Task Manager Pro and I love it. The close-all widget is great because it closes everything except what you have told it not to kill, and it kills itself to that is not running down your battery either.
joe.kerwin said:
There's no way your g1 ever lasted 14 hours, let alone consistently with that usage. Either that or you dont understand how some of us use our phones. The only reason this must be such a debated topic is because there truly isn't much of a difference. Will your phone have a weeks worth of battery life with one? No. Without one? No. Users preference I suppose, but before i deleted bloatware, my telenav and slacker radio were always open and i honestly never even opened them to even check them out.
Click to expand...
Click to collapse
I don't know what to tell you other than it did.
I am a pretty heavy user, but I do have fantastic coverage and work in a bright environment so brightness stays down. SetCPU works wonders.
I tested my Vibrant today. Came off the charger at 5:30am. It's now 10pm & my phone is freaking out for juice. I think my G1 could match this.
I'm constantly pulling from Gmail & Exchange (usually on Edge - poor reception in the office). I used GPS for about 10 min on the way home. Once home I started wifi. I turned it off an hour ago to play a few rounds of Let's Golf.
That's not terrible for such a badass smart phone, I think.
-bZj
_____
-sent from my Samsung Vibrant via XDAapp
I personally will only have a task manager installed for when I'm working on my game / app projects, as to make sure they properly close when exited or to kill them if something goes wrong (neverending looping media), so I don't have to reboot the phone.
I was using atk before my last factory reset. I've decided against it now though. I've also decided not to use any more web apps when I have a perfectly good browser. Just seems like a waste of resources to me and my phone is much quicker without them. That and launcher pro have made this feel like a different phone. I think the combination makes atk unnecessary.
If I decide to keep this phone I'll reroot and clean out all the crapware. I'd prefer to keep this phone well-maintained like my computer sip that a task killer would be mostly unnecessary.
Related
Using the TasKiller widget, I average around 32M and the rom is just slow as hell.... sorry Flipz, but wow.
Going back to Damage, but before I do, anybody else have this problem? I have it killing everything pretty much.
Maybe its because I'm using Sense UI again?
im sittin at more than 70m...
dunno what else you got running.
i go from 60-84 all the time......i set the memory manager to strict and im using helix launcher with no lwp, couldnt be happier
I'm using sense (sorry, Im a fan) and with task killer set to kill everything but Music (for the widget) Mobile Defense, and AutoKiller. I average 50-60 with 72MB usually free after a fresh boot and killing all tasks that start at boot. That quickly deminishes though and hovers around 50-60. With damage control, I would average 90MB after a fresh boot and auto kill, and would stay around 80.
With 3-4 programs open (one of them being the browser) I average about 35MB with fresh. However with DC I was at 50-60.
I'm using "Moderate" settings with AutoKill that came with fresh. Strict basically turned the phone into an iphone (no multitasking) I wouldn't have the browser and just about any other program running at the same time, defeats the purpose of having a multitasking phone.
The ROM is noticeably slower than damage control, however I was still having many bugs with even DC v2.05 so having a TRULY BUG FREE rom (fresh) is worth the little bit of slower performance.
I seem to agree that Fresh seems to be a more "complete" rom although they are very close.
I always just thought that Fresh's rom comes with a lot more programs (you can remove them, search). I know under Damage's I had a lot more memory, but I didn't have Sprint Football. I need to remove it, but I have been lazy so my avail. memory is under 50m usually, I haven't bothered cleaning it out just yet though.
If you go through and take out the stuff you're not using (even just sense/launcher/android home) maybe also the lock screens/clocks, you may be able to boost your memory a lot.
poor_red_neck said:
I'm using sense (sorry, Im a fan) and with task killer set to kill everything but Music (for the widget) Mobile Defense, and AutoKiller. I average 50-60 with 72MB usually free after a fresh boot and killing all tasks that start at boot. That quickly deminishes though and hovers around 50-60. With damage control, I would average 90MB after a fresh boot and auto kill, and would stay around 80.
With 3-4 programs open (one of them being the browser) I average about 35MB with fresh. However with DC I was at 50-60.
I'm using "Moderate" settings with AutoKill that came with fresh. Strict basically turned the phone into an iphone (no multitasking) I wouldn't have the browser and just about any other program running at the same time, defeats the purpose of having a multitasking phone.
The ROM is noticeably slower than damage control, however I was still having many bugs with even DC v2.05 so having a TRULY BUG FREE rom (fresh) is worth the little bit of slower performance.
Click to expand...
Click to collapse
Having a truly bug free rom? When I am getting a text, the phone will FREEZE, and WAIT until the sound decides to play, then it will keep going.
Sometimes typing it will randomly freeze, then spit out a ton of text, then if I hit backspace, it will freeze again, erase it all, and then I have to VERY slowly type.
Its horrible. I'm sorry, but I have to go back to DC. I can't even use the phone.
Here is a good example, yesterday somebody called me, I missed the call because the phone stuck on the home screen with it ringing, finally when it popped up to answer, I hit ANSWER and it didn't do anything. Went to voice mail, I hit the missed call and it just sat there, then it flew to the call screen and then hung up right away (registered a few finger taps and decided I was hitting End Call too). Then I tried to call back, pressed the number 4 or 5 times. Finally got frustrated and threw the phone in the passenger seat. 3 minutes later it rang again and I hit the Answer button and it worked.
This is insane. God forbid I have to get an emergency call out.
Later Fresh ROM.
Wow.
I'm having a great experience with Fresh.
I have (currently) 8 apps open and I'm running 56mb Free.
No FC's at all.
grifforama said:
Wow.
I'm having a great experience with Fresh.
I have (currently) 8 apps open and I'm running 56mb Free.
No FC's at all.
Click to expand...
Click to collapse
Me too. Pretty sure there are far more folks who have low to no issues with this rom than there are folks who do.
With apps2sd I am running 64 megs.
Love this rom. No hitches. No glitches.
yall with task killers need to work smarter not harder and utilize the auto killer app and let it do all the killing based on the values in which android works....im on fresh 2.0d and really never dip below 70 or 80 and i dont run
a2sd and i really have no hiccups at all even running lwp...flipz him self said dont **** with a task killer thats prolly why the OP doesnt have alot of free memory
Dec 26: FAQ: Why You Shouldn’t Be Using a Task Killer with Android
And no offense taken. But you have to understand that DC and Fresh are based on the EXACT same build from Sprint. I use my own rom (obviously) and haven't experienced a single thing that you mentioned other than some keyboard lag, which is caused by the experimental keyboard that I put in.
And if you are still questioning speed then you can also check out...
Apr 3: Benchmarking Sprint 2.20.651.1 Based Roms
This is solid proof that the roms are the same. Get rid of your taskkiller, setup autokiller (which is a task killer in a different way. It controls when android does all that nifty stuff in the first link) and you'll have a better experience on every rom, whichever one you choose.
Out of curiousity flipz, what do you find has been the best setting for autokiller? I've been testing several out, just curious what you find works best.
ccapasso said:
Out of curiousity flipz, what do you find has been the best setting for autokiller? I've been testing several out, just curious what you find works best.
Click to expand...
Click to collapse
I keep mine on moderate or optimum.
ive noticed after a fresh install sometimes u have like 32 mb free ram.. but after a few reboots and such it levels back out up to 70 mb..
flipzmode said:
I keep mine on moderate or optimum.
Click to expand...
Click to collapse
Thanks . My mindset was Agressive would kill more, so I tried that one out. I used optimum for a while, but never moderate yet. I am probably misunderstanding the differences between each setting
I'm using the Aggressive as well, but I will let my pictures speak for themselves.
flipzmode said:
Dec 26: FAQ: Why You Shouldn’t Be Using a Task Killer with Android
And no offense taken. But you have to understand that DC and Fresh are based on the EXACT same build from Sprint. I use my own rom (obviously) and haven't experienced a single thing that you mentioned other than some keyboard lag, which is caused by the experimental keyboard that I put in.
And if you are still questioning speed then you can also check out...
Apr 3: Benchmarking Sprint 2.20.651.1 Based Roms
This is solid proof that the roms are the same. Get rid of your taskkiller, setup autokiller (which is a task killer in a different way. It controls when android does all that nifty stuff in the first link) and you'll have a better experience on every rom, whichever one you choose.
Click to expand...
Click to collapse
Exactly.
You can't really argue about one feeling more 'complete' than another one at this point. I gave flipz the Sprint leak, we both did our own customizations but they are basically the same thing. Everything is in your head. We both use the same keyboard (modded HTC one), and a LOT of it is the same stuff, so enough arguing about which one is better/worse. They really are based off the same thing now and have the same functionality. There is nothing that will run on mine that won't run on his, or anything on his that won't run on mine.
also we all use our phones very differently and run different things in combination with others so its really almost impossible to be like oh yea mines running better than yours cause one person may be all with the social networking and all that stuff and another might just need the bare basics...bottom line flash the roms that interest you and you will know what works for YOU
My phone has been running Fresh 2.0d for a few days now and with very minor changes to the base rom, it runs very smooth and fast. After having some issues with another rom I did a wrath of god level wipe on my phone and SD card, from that point on all my FC and lag issues stopped. If nothing else works I would suggest doing something along that line, start from scratch, purge everything, remake partitions etc., "Nuke it from orbit, it's the only way to be sure".
My RAM is usually around 60-70 free, but why is my internal phone memory so low after a fresh install of Fresh2.0d? I just got into rooting, tested out a few, sticking with Fresh, but my Internal memory is around 90 MB, without any other apps installed. Something wrong with this? On this page, dcdave63, shows a picture of internal memory with 131 MB free.
Anyone used this app? I tried it and it boosted my memory from 123 mb to 180 mb.
i know "if you have free memory you're wasting it". but in my opinion this combined with advanced task killer will improve battery life a lot.
its on android market, just type memory booster
Lol I experimented with these kind of apps, my opinion is that they are pretty much pointless.
I simply tell things not to auto update and removed unused junk.
Did the trick for me.
Swyped from my rooted X10i using Tapatalk.
I'll bite. How will having more free memory improve battery life?
You don't need third party apps. You have to determine which app is eating your battery life. The only thing memory booster is doing is disrupting Android's memory management processes.
Sent from my SAMSUNG-SGH-I897 using XDA App
if it could activate the full ram potential of the handset then it would be worth while but i dont see the point in the extra mem for app's.
Like I said I simply stop stuff auto updating and therefore save battery life as no apps are active, merely sitting in ram.
Swyped from my rooted X10i using Tapatalk.
I only kill programs when I want my phone in standby because I know I won't be using it. Or with programs that can still run in the background and stay active when they shouldn't.
Other than that, don't be a frequent task killer. It's not an iPhone, it's an Android phone. As much as I loathe my Xperia X10 it's far better than an iTurd.
bongd said:
I only kill programs when I want my phone in standby because I know I won't be using it. Or with programs that can still run in the background and stay active when they shouldn't.
Other than that, don't be a frequent task killer. It's not an iPhone, it's an Android phone. As much as I loathe my Xperia X10 it's far better than an iTurd.
Click to expand...
Click to collapse
Way to try to prove your cool by trying to inject irrelevant crap into the discussion. Especially ****e you obviously know sweet fa about. You do realize that when you get down to the nuts and bolts the memory management is almost identical in iOS and Android? Only difference is how it's exposed to apps. My gf has my iPhone 4 now, trust me, calling it an iTurd just makes you look a bit special - and not in a good way either.
P.S. task killers made sense on phones like mt3g that were memory limited, when you went to launch a big app like gallery it popped up straight away if there was free ram - when memory was all spoken for, the system would have to kill a bunch a tasks, so it'd hang for a while before launching your app. Can't say I noticed the need for that on my X10.
rynoon said:
I'll bite. How will having more free memory improve battery life?
Click to expand...
Click to collapse
It isn't the free memory that saves battery. It's the applications being "killed" that otherwise would need some battery power as they lie in the background doing things. Even sleeping applications have some "attention" from the kernel and that will drain (slightly) on the battery too. Every drip-drop counts.
SysGhost said:
It isn't the free memory that saves battery. It's the applications being "killed" that otherwise would need some battery power as they lie in the background doing things. Even sleeping applications have some "attention" from the kernel and that will drain (slightly) on the battery too. Every drip-drop counts.
Click to expand...
Click to collapse
And every time you want to use an app, will have to be reloaded in memory wasting more power for that task.
Anyhow, do it your way ...
The rest of the world is just stupid.
This constant debate of whether app management apps work or not is really irrelevant. Some work, some don't. Just try and find that out.
Once I listened to posters here and decided not to use ATK because of the reasoning that Android is efficient by itself. Wrong. My battery kept draining fast. Once I started using ATK and modifying the program here and there, my battery's energy consumption actually slowed down and I can go through a whole day without charging. My settings? Put ATK on safe mode and auto kill every half hour, and ignore SE's own backup app (for some reason, killing SE backup caused a disruption with the data/signal for a second).
So for everyone, just try and see whatever is recommended works.
Exactly my point. I used to use atk with similar settings to yourself and experienced greater battery drain.
I get better results with my method.
We all use our phones in different ways so it follows we would experience differing results.
Swyped from my rooted X10i using Tapatalk.
I'm trying to figure out how some people drain the batteries so fast. I have my phone set up as a wifi accesspoint, I'm using bluetooth, autosyncing my gmail and calendar but still I get more than a full day use out of it. If I listen to music over a bluetooth headset constantly I can't last a day but the juice in my headset tends to run out faster.
I can't for the life of me figure out what people do. I'm not using any task killers or what have you but still get between 18 and 24 hours of heavy usage.
I was using a task killer before reading on here about how they are useless and whatnot. But I find my phone freezes up more now that I am not using it. The battery seems to be around the same. All I do is text and use facebook and it seems to freeze up when texting or typing half the time. I am kind of wondering if it's because I text so quickly..
Just to clear things up a bit:
Many applications out there are bad.
Applications that are some real heavy battery hogs, even when prefetched in the background.
Those bad applications keeps downloading adverts now and then, executing instructions while in the background, and so on. Those applications doesn't have any sleep/standby routines , or the routines are empty.
Some applications are so badly written, they're running at "full speed" no matter what. Those extremely bad applications keeps the CPU at full speed even when in standby mode.
A good sign of this is when the phone gets hot, even when not used. It's the CPU that heats up the device.
The programmers of these bad applications have no whatsoever experience with Androids "sleep and standby" functions and therefor left them empty or half-done.
This is why killing applications helps for some, and not for others.
It all depends if one got one or more "bad" applications installed.
And Android aren't too smart either. It'll just prefetch, to what it seems, a random bunch of applications.
For me Android prefetch apps I rarely use, and skips the applications I use everyday. Weird?
If one would keep the device clean and keep those bad applications out, (of which noone can tell if it's a bad app or not. There's nothing visibly wrong about them) one wouldn't need a separate task-killer. Or if EVERY single application out there where perfectly written, accordingly to the Android model.
1st of all, thanks guys for ALWAYS helping me w/ my many issues! With that said, I have a question that nobody seems to answer when I ask it....CAN SOMEBODY PLEASE TELL ME Y 5~11 APPS ALWAYS OPEN WHEN I GET ON PHONE TO SEND JUST 1 TXT??? I don't unerstand how my camera and other stupid stuff opens just by me sending or receiving a text or gettn on the 'net! My concern is if I forget to hit apk my battery will die! Is it normal to have to hit apk after EVERY TASK I perform???
don't worry about that...this is normal for android.
all these apps are in background (and idle), so they don't consume processor power....and when you decide to call them back - then they become active.
personally i think there is no need for task killer on android.
i've noticed better battery life with out killing all the tasks (when you kill apps, the system has to use even more resources to start up those processes again, in turn stealing battery life) and no decrease in speed. android automatically kills applications that are in the background when memory becomes low. You do not need to alter the process. your phone will run well if you leave it be. watch your battery consumption. 80 percent is the display. having a few running apps wont even make a notch in you battery.
I made a post about this last night, and got lambasted lol.. but yeah.. makes utterly no sense to me, but since its "android" i guess its ok..
He's right though about the battery life, i had a task killer set to auto-kill everytime the device slept.. Battery life was terrible, since removing that this morn.. its been a more consistent drain.
Phen0m said:
I made a post about this last night, and got lambasted lol.. but yeah.. makes utterly no sense to me, but since its "android" i guess its ok..
He's right though about the battery life, i had a task killer set to auto-kill everytime the device slept.. Battery life was terrible, since removing that this morn.. its been a more consistent drain.
Click to expand...
Click to collapse
thanks guys for both responses and i apologize for the double post! i am new to the android world (came from tp-2) and just wanna make sure i'm doing all the right things...sooo much to learn...not complainin' tho!
Download startup manager from the market.
First and foremost, this will only apply to you if you have seen the following symptom:
You go to Settings -> About phone -> Battery usage -> click on the graph above and see "Awake" as a solid bar instead of (mostly) lining up with the "Screen on" spotted bar below. Here's my previous thread of when I discovered this issue when my "Awake" bar showed solid for an entire 8 hours when my "Screen on" would show frequent off/on's:
http://forum.xda-developers.com/showpost.php?p=13938317&postcount=772
I found my SGSII was getting decent battery life, but idle was certainly worse than my SGSI. I couldn't figure it out for the life of me what could be causing it given I was running the exact same apps as my SGSI 2.2.1 handset, but the solid Awake bar did not sit well with me.
Observations:
1) After 8+ hours of solid Awake, I would have no apps running under Settings -> Applications -> Running services except for those that I normally would expect in the background... Settings, NoLED, Google Voice, Swype, etc.
2) I noticed that under this "Running services" screen, if you hit Menu and select "Show cached processes," there are actually other cached processes that are in a semi-dormant state. Are they running or are they not? Hmmm....
3) After a system restart, the Awake and Screen on would line up once again.
Suspicion/Hypothesis:
Some app that I normally have running... even if I completely exit out of, it would sit under cached processes and somehow still keep the device awake.
Testing:
First, wanted to see which app when normally running would keep the phone "Awake." After a few days of testing, isolated it down to eBuddy, which is a chat client I used to have running nonstop on my Froyo SGS. So, after several hours of running eBuddy and seeing a solid Awake bar, I exited out of eBuddy properly (Menu -> Exit), ensured it was no longer running under Running services, and tested it for another 4 hours. Sure enough, with the device mostly idle and eBuddy shutdown, the Awake remained solid/on!
So, I then revisited Settings -> Applications -> Running services -> Menu -> Show cached processes, I saw eBuddy was still cached and taking up memory. So, I clicked on the process and chose Force stop. Afterwards, I let the device idle for a few hours more, and the Awake and Screen on lined up once again.
Conclusion:
I'm not sure if this is a Gingerbread bug or eBuddy bug or a combination thereof, but something changed in the code from Froyo to Gingerbread. Probably has to do with this caching feature, but there ARE apps out there that will keep your device constantly on even if you do properly exit out of them.
Solution:
I used to run "Advanced Task Killer" on my SGS with Froyo but never bothered with Gingerbread because people much smarter than me on here have said time and time again "it's not necessary for Gingerbread, you're wasting time/battery life." Well, that still may be true, but given there are these rogue apps that will cause Gingerbread to stay constantly awake, Advanced Task Killer is the best solution at this time.
(It may not be pretty, but hey, it works.)
So, I installed Advanced Task Killer, did a fresh boot, put all the system apps and other apps I don't want ever shut down (Email, Swype, Settings, etc) on the ignore list, turned the kill setting to every hour, and let it sit. I can say for the past 2 days, my idle battery life has improved significantly. Normally by the end of my work day, I'd be skimming along around 40-50%. (Keep in mind, I use the phone primarily for business, which means 2 push E-mails, 2 pull E-mails, constant text messaging, and lots of phone calls.) The last two days, I have been easily at 70-80% by the end of the day. For instance, right now at 4PM CST, I am still at 82% remaining battery.
Also, keep in mind, I have just about EVERYTHING else I don't need frozen/uninstalled through Titanium backup. This includes but not limited to WIFI Sharing, all the hubs, all the readers, all the SNS junk, AP News, Accuweather, etc.
And the most telling bit that the fix is working: My Screen on and Awake line up perfectly with no more solid bar for Awake. And, this is even after running eBuddy last night.
I know this won't help everyone, but hopefully, it will be of use for some of you. Good luck!
If you're managing to kill apps that keep the phone awake, does it prevent you from receiving messages on eBuddy when the screen is off?
dinan said:
If you're managing to kill apps that keep the phone awake, does it prevent you from receiving messages on eBuddy when the screen is off?
Click to expand...
Click to collapse
Interesting question. I had Advanced Task Killer running all last night, and I woke up to messages in eBuddy in the morning. So, my immediate answer to you would be "no," but this will probably take more testing.
Maybe, I'll set ATK to an aggressive 15 minute kill, and have someone message me after 15 minutes of idling with eBuddy running...
I have noticed that with eBuddy actively running, you cannot select it under ATK and kill it. You must exit out of eBuddy properly (Menu -> Exit) for its active process to shut down. Little did I know though... it would still float around in your "Cached processes" afterwards and keep your device Awake!
Well I've been using ATK since this morning and I can't find any change in Android OS ..
It's still high..
Anyway ATK reports that all the games I downloaded from gameshub are active..
And even if it kills them, they appear again in like 10 minutes.. It's really wierd
TMaLuST said:
Well I've been using ATK since this morning and I can't find any change in Android OS ..
It's still high..
Anyway ATK reports that all the games I downloaded from gameshub are active..
And even if it kills them, they appear again in like 10 minutes.. It's really wierd
Click to expand...
Click to collapse
I don't use game hub, but I do have a bunch of games on my device, including the larger Gameloft games. And, I can say for a fact that I do not have any of them ever running in the background.
Something else is keeping them alive, and has nothing to do with ATK. ATK will only help to kill cached processes, but if something is launching them again, that's what you need to look into stopping.
Well.. I do not like tools like the Advanced Task manager.. BUT looking at battery drainage it seems to do wonders!
8 hours of light usage (display 45 mins) --> 75% battery left
3g on (with JuiceDefender à 30 mins) + sync (so I receive whatsapp messages & mail etc)
Listened to music / radio for about 1-1.5 hours
Android OS is sadly still at 36%, Display at 22%
But this I can live with !
Thanks!
[edit]
It would obv. be nicer to be at 80+% without that Android bug... Ah, and I did delete / freeze all that Samsung crap with Titanium, didnt really help much! I can also recommend getting CPU spy to see how much your phone actually is in the sleep mode (around 80% for me!)
Breece said:
Well.. I do not like tools like the Advanced Task manager.. BUT looking at battery drainage it seems to do wonders!
8 hours of light usage (display 45 mins) --> 75% battery left
3g on (with JuiceDefender à 30 mins) + sync (so I receive whatsapp messages & mail etc)
Listened to music / radio for about 1-1.5 hours
Android OS is sadly still at 36%, Display at 22%
But this I can live with !
Thanks!
[edit]
It would obv. be nicer to be at 80+% without that Android bug... Ah, and I did delete / freeze all that Samsung crap with Titanium, didnt really help much! I can also recommend getting CPU spy to see how much your phone actually is in the sleep mode (around 80% for me!)
Click to expand...
Click to collapse
Yeah, I wouldn't run ATK unless I absolutely have to. Like I said in my first post, it is a "brute force" method of ensuring apps are completely closed out and there are no rogue cached processes keeping your device awake. Since I've installed it, the "solid Awake bar" phenomena is completely resolved... and in return, I get much better battery life.
And yes, this is of course on top of freezing just about everything Samsung and anything else I don't need or care to use.
Couldnt agree more!
One questions, what is your "Android OS" % at?
Breece said:
Couldnt agree more!
One questions, what is your "Android OS" % at?
Click to expand...
Click to collapse
8%... Display is at 62%, LOL.
Interesting ^^ Oh well.. my battery life should improve but if it stays like this I am fine with it...
Oh Hope ?
Nah, i will try it
cmd512 said:
....
Solution:
I used to run "Advanced Task Killer" on my SGS with Froyo but never bothered with Gingerbread because people much smarter than me on here have said time and time again "it's not necessary for Gingerbread, you're wasting time/battery life." Well, that still may be true, but given there are these rogue apps that will cause Gingerbread to stay constantly awake, Advanced Task Killer is the best solution at this time.
(It may not be pretty, but hey, it works.)
So, I installed Advanced Task Killer, did a fresh boot, put all the system apps and other apps I don't want ever shut down (Email, Swype, Settings, etc) on the ignore list, turned the kill setting to every hour, and let it sit. I can say for the past 2 days, my idle battery life has improved significantly. Normally by the end of my work day, I'd be skimming along around 40-50%. (Keep in mind, I use the phone primarily for business, which means 2 push E-mails, 2 pull E-mails, constant text messaging, and lots of phone calls.) The last two days, I have been easily at 70-80% by the end of the day. For instance, right now at 4PM CST, I am still at 82% remaining battery.
Also, keep in mind, I have just about EVERYTHING else I don't need frozen/uninstalled through Titanium backup. This includes but not limited to WIFI Sharing, all the hubs, all the readers, all the SNS junk, AP News, Accuweather, etc.
And the most telling bit that the fix is working: My Screen on and Awake line up perfectly with no more solid bar for Awake. And, this is even after running eBuddy last night.
I know this won't help everyone, but hopefully, it will be of use for some of you. Good luck!
Click to expand...
Click to collapse
WORKED FOR ME AS WELL< EXCELLENT!!!
Task killer is a must
Uninstalling/freezing rogue Samsung apps is a must
ONLY THE COMBINATION WORKS and it works well indeed.
Mmm bizarre! I was waiting for the hordes of people telling you that 'task killers' are unnecessary and stupid.
Thank you very much for your findings.
On my SG2 The android System process is eating almost all my battery! any solution for that?
rdy2go said:
WORKED FOR ME AS WELL< EXCELLENT!!!
Task killer is a must
Uninstalling/freezing rogue Samsung apps is a must
ONLY THE COMBINATION WORKS and it works well indeed.
Click to expand...
Click to collapse
cigaro78 said:
Mmm bizarre! I was waiting for the hordes of people telling you that 'task killers' are unnecessary and stupid.
Thank you very much for your findings.
Click to expand...
Click to collapse
Glad to hear it's working for you guys. With Advanced Task Killer running in the background, I haven't had the "solid Awake bar" reappear again... my Awake bar is always segmented and match up fairly well with my Screen on bar.
Idle battery life is very much acceptable now and definitely no worse than my SGS.
I've always enjoyed your posting and i'm glad you didn't just jump on the bandwagon like everyone else. This is definitely the type of posting we need where everyone work together to solve/identify the issues at hand.
ph00ny said:
I've always enjoyed your posting and i'm glad you didn't just jump on the bandwagon like everyone else. This is definitely the type of posting we need where everyone work together to solve/identify the issues at hand.
Click to expand...
Click to collapse
Appreciate the kind words. Like I said in my first post, many people much smarter than me/in-tune with Android have said it's unnecessary. But, you're right... there are way too many "DO THESE STEPS AND IT WILL FIX EVERYTHING" posts on here with 0 to little evidence to back up the claims. In the end, nothing beats thorough testing and proven results.
I for one hope 2.3.4 resolves this bug... ultimately, I'd like to not have to run ATK altogether. But for now, this is a solution that works.
cmd512 said:
Appreciate the kind words. Like I said in my first post, many people much smarter than me/in-tune with Android have said it's unnecessary. But, you're right... there are way too many "DO THESE STEPS AND IT WILL FIX EVERYTHING" posts on here with 0 to little evidence to back up the claims. In the end, nothing beats thorough testing and proven results.
I for one hope 2.3.4 resolves this bug... ultimately, I'd like to not have to run ATK altogether. But for now, this is a solution that works.
Click to expand...
Click to collapse
It works with Freezing/Uninstallin Samsung "bad apps" (WiFi Sharing, Social Hub, etc.). I suggest you emphasize that more in your initial post.
ATK itself helps but ATK is always late (30 minutes or one hour).
That's what I recommend to freeze/uninstall without crippling core functionality:
1 WiFi Sharing and WifiManager
2 Samsung apps (Social Hub, Days, Yahoo Finance, AP News, Games Hub, Readers Hub, Music Hub, AccuWeather)
3 Voice Command Uninstalled using Titanium
It's based on my testing using OS Monitor / ATK - those apps tend to wake up phone for no reason even when you don't use them.
Now it's 24 hours with 4 hours of screen on, no Juice Defender etc.
It works better than SGS (one) despite huge screen and excellent speed.
rdy2go said:
It works with Freezing/Uninstallin Samsung "bad apps" (WiFi Sharing, Social Hub, etc.). I suggest you emphasize that more in your initial post.
ATK itself helps but ATK is always late (30 minutes or one hour).
That's what I recommend to freeze/uninstall without crippling core functionality:
1 WiFi Sharing and WifiManager
2 Samsung apps (Social Hub, Days, Yahoo Finance, AP News, Games Hub, Readers Hub, Music Hub, AccuWeather)
3 Voice Command Uninstalled using Titanium
It's based on my testing using OS Monitor / ATK - those apps tend to wake up phone for no reason even when you don't use them.
Now it's 24 hours with 4 hours of screen on, no Juice Defender etc.
It works better than SGS (one) despite huge screen and excellent speed.
Click to expand...
Click to collapse
Well, freezing and ATK are needed to reach 2 separate goals:
1) Freezing: Needed to completely disable apps you plan on NEVER using.
2) ATK: Needed to completely close out apps you DO use when they stay cached/rogue in the background and keep your device awake.
So I do agree with you, freezing is absolutely necessary, but it really is the bare minimum. You still need ATK on top of that to actively seek out and kill battery draining apps.
I can confirm, OP solution works great on me. Thanks..
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?