ok so this will happen quite often to me after messing with customizations or just using different apps. I exit apps that stay running correctly (at least ones I know I need to). my ram will fill up, or almost up and then the phone will freeze for a few seconds. when it comes back up I open system panel and close all inactive apps and anything else I feel needs to be closed. this will leave me with 50% or less free.
usually i'm not concerned, but twice now my phone has rebooted due to this. this happened once back in june and now just today. I had navigation up and when I knew where I was going I woke up the phone to exit it, but the phone was frozen. so I put it down and it actually keeps giving me directions. then I heard the start up tone, I didn't bother to look just put the phone in my pocket. a few minutes later it reboots again. again I didn't bother cause I did not need it. when I did need it I found it with no cell or 3g reception and no icons loaded up. reboot the phone manually and all is fine.
I am rooted with the latest fresh rom. but I have only been rooted for 6 days and I have been getting this memory issue the whole time I have owned the phone(release day purchase). including one reboot before rooting.
I keep reading that we should not have to worry about memory and that android takes care of it by closing apps when new apps need the memory. is this really true?
usually I keep it free by using system panel but I forget sometimes. I haven't used task killers as I read mix reviews and I like some things manual anyways.
so, is this normal? am I doing something wrong, or is there a setting I need? do I just need to go get a task killer?
what are the best task killers? and is there any programs I should not kill? or whats the optimal way to set these up?
thanx for any help you can give me
Try using Advanced Task Killer (there's a free version in the Market) and change its security settings to low, then start killing processes you don't need.
While Android is supposed to have good RAM management... Well, as you can see, it's not that great. Generally, if I get under 100MB of RAM available, I tend to go on a killing spree... Of processes.
drmacinyasha said:
Generally, if I get under 100MB of RAM available, I tend to go on a killing spree... Of processes.
Click to expand...
Click to collapse
me too... when I remember .. lol
cool I'll try out ATK
It went from extremely rarely doing it to three or four times just the other night in the span of a few hours. I can't reproduce it on command but it happens when I lock the screen and put it in my pocket. Then sometimes when I take it out it is entirely non-responsive, even the power button doesn't work. I have to remove and reinsert the battery.
It could be ADW Launcher or WidgetLocker since those are the only two programs always running, but I was hoping someone else experiences a similar issue. It hasn't happened when I normally lock it yet though, so it could also be the proximity sensor maybe?
Having the same issue (on Bell as well), but not running either of those two apps. Was almost to the point of returning the phone and then installed JM7 and it's been better, although not perfect. Last night it locked up with NoLED displaying an icon, so I've deleted that app to see if that's the issue. It hasn't locked up today, but it did reboot a few hours ago seemingly at random. :shrug:
Your internal sd card might be failing like all the other i9000m phones I see on this forum bricking themselves .
clubtech said:
Your internal sd card might be failing like all the other i9000m phones I see on this forum bricking themselves .
Click to expand...
Click to collapse
Oh, that doesn't sound pleasant at all...
I'm outside of Bell's 30 day exchange period plus I've talked for over 30 minutes, so I'll have to go through Samsung if it completely breaks. On the plus side, a phone from them should be three button recoverable.
Although I can't be without a phone for weeks, I hope it's not the SD card.
Mine Lags like crazy once every few days till the point I need to restart it. Any idea why this is do?
Sent from my GT-I9000 using XDA App
Hold your horses people....
before you jump about the lag, and or one click lag fix and such
first you have to investigate what is running on your phone.
just over the weekend (since XDA was down) i stalled over 400 Apps
my phone slowed down to snail speed, then i ran my Startup Manager software (many to choose from)
I suggest Startup Cleaner 2.0 then uncheck everything, leave only the apps that you want to run during start up
reboot your phone and presto, fast as new!
if you can find version 2.1 of startup manager that one is even better
keep note, start up manager apps are not the same as task killer apps
it only run once during start up, and it helps you easily select what should and should not run during start up, so it doesn't stay in memory after it runs
on the same topic
you should also configure your Task Killer apps to kill everything, and add only the wants you want to be running to the ignore list.
that will keep the phone working smoothly even without the "one click lag fix"
i'm still running stock on my JH2 i9000m
AllGamer said:
Hold your horses people....
before you jump about the lag, and or one click lag fix and such
first you have to investigate what is running on your phone.
just over the weekend (since XDA was down) i stalled over 400 Apps
my phone slowed down to snail speed, then i ran my Startup Manager software (many to choose from)
I suggest Startup Cleaner 2.0 then uncheck everything, leave only the apps that you want to run during start up
reboot your phone and presto, fast as new!
if you can find version 2.1 of startup manager that one is even better
keep note, start up manager apps are not the same as task killer apps
it only run once during start up, and it helps you easily select what should and should not run during start up, so it doesn't stay in memory after it runs
on the same topic
you should also configure your Task Killer apps to kill everything, and add only the wants you want to be running to the ignore list.
that will keep the phone working smoothly even without the "one click lag fix"
i'm still running stock on my JH2 i9000m
Click to expand...
Click to collapse
All gamer has a good sugestion here BUT we are going to get people flaming the fact that Android shouldnt need task managers.....
Ho hum..
TBH in my experience, I have found (after a couple of hard resets) that there appears to be a size limit for installed apps. Once I get over this size limit, I get LAGTASTIC, phone slows to a snails pace, then I remove a few of the apps and I am back at light speed again....
I cant say what the limit is, but I know when I have hit it - I would then uninstall a lame app or two and get back running.
Yes a lot of people "claims" that, but yet you do a search in Android Market, you see LOTS of Task Manager / Killer apps for every phone.
they were not designed for Galaxy S, they were designed long ago for all the other phones that had and still have the same problems of memory management causing lags
Android is not robust enough to survive without one
heck not even Windows 7 or Windows Mobiles phone
I just read that possibly the phone freezes while trying to find a signal. As this problem has only recently started, and I just recently moved into university, and many buildings receive little to no wireless signal, I think it's more than a coincidence. I'll try going to plane mode before entering lecture halls and basements.
Frostshock said:
I just read that possibly the phone freezes while trying to find a signal. As this problem has only recently started, and I just recently moved into university, and many buildings receive little to no wireless signal, I think it's more than a coincidence. I'll try going to plane mode before entering lecture halls and basements.
Click to expand...
Click to collapse
i don't think that is the case with the Galaxy S
however back then my Treo 650 did suffer from that.
if you believe that is the problem then try this
http://forum.xda-developers.com/showpost.php?p=7999389&postcount=28
more cool apps here http://forum.xda-developers.com/showthread.php?p=7999389
My Arc keeps crashing asking me to force close apps and the homescreen it lags like hell and it is getting worst all the time so bad that even opening my texts takes a couple more than 10 seconds... (I do have around 2000 texts though)
Unlocking the screen is laggy scrolling on threw the 5 homescreens is laggy...
Sync turned off.
No timespace widget.
Even after removing all widgets to test it it was laggy
I used advanced task killer to kill all the apps to try the quadrant test
and I only got 850-950 MAX!!
Compared to youtube videos that seem to get almost double scores why is my
Arc is slow is it faulty?
Is it because I only have 40mb of phone memory and about 500mb sd card memory left?
Will I just have to flash my phone and does that mean I will need to flash every 2 weeks???
I think you have installed some applications which caysing this problem I had this problem, then i flashed my phone again & installed apps again (didn't restore).. But i didn't installed all apps at once, i spent time & installed 2, 3 apps everyday to check if the app would make phone laggy or slow. Since then my phone is working awesome, my 16GB memory card is almost full, 400 MB internal memory is full (After root i have removed many useless system apps)... I have more than 4000 sms & there is no lag or slowness Quadrant score is 1650
the only time i experienced lag was with adw launcher and no fc's yet, other than that the phone has been fast - then again i don't have as many apps or data on my phone as you. one thing i did notice is that my lcd's touch sensitivity seems to be lower than other arc's, maybe a defect, but it's pretty maddening in addition to all the reboots i've been having. i've been reading about others that have issues with the battery staying in place and like me, the random reboots, this is my first android phone, so not sure if these things are normal or if it just the arc.
It's definitely apps.
Mine is superfast...
Apps and possibly task killing the wrong things.. you need to make sure that if you're going to use a task killer, you really shouldn't us it on Auto.. and you should make sure to IGNORE anything that is a system task, or anything which persistently restarts.. killing those only wastes battery.
Android isnt exactly the most stable os out their but if you know about the os and know its ins and outs it can not only be the fastest but the best os out there.
My recommendation is look up articles about using and optimizing the os, trust me it will do you a ton of good.
Hi,
It seams that sometimes Android must be reflashed on a Device, especially on Tmobile Devices it will fix most of the problems.
Another tip: Uninstall the update of gmaps and reinstall it, on my device it blocks login to gmail and gtalk from one day to another! -.-
Greetings
Alef
Nope the ARC does not Lag very often and i think its ur device's memory thats giving you the trouble along with that huge pile of messages .... or the Corrupt software that might have crept in ...
My advice would be to flash ur ARC ASAP and limit that 2000+ messages and u will see a difference. Avoid putting too many apps as well.
Arc is a Size Zero Lady ... Don't burden it with Heavy Foodstufff ...
Might create Digestion problems. Keep it Light and it'll stay FIT.
solidkevin said:
Android isnt exactly the most stable os out their but if you know about the os and know its ins and outs it can not only be the fastest but the best os out there.
My recommendation is look up articles about using and optimizing the os, trust me it will do you a ton of good.
Click to expand...
Click to collapse
What do you mean "isn't the most stable"? I've been able to keep my phone on for weeks without a reboot. Seems stable enough to me.
Ok turns out I had 110 apps I deleted al the heavy ones and am down to 60 now!! My phone now got 1200 on quadrant. I dont kill any system ups or have an auto task killer set up I just kill uneeded apps before I run benchmarks?
Plus I noticed I have some orange apps that keep coming up even though I never used them... I might have to debrand and try again but my phobe is much much more stable now thanks!!
Sent from my LT15i using XDA App
chances are it wasn't the number of apps you had which was causing the problem, but that one of them (or possible several of them!) which you deleted were badly written and hogging the processor when they should have been sitting quietly in the background..
Orange is well known for screwing devices with bloatware also.
Wow!!
That's a lot of apps you've installed and most likely loads of them are badly written like iceman said; I installed a file browser on mine not long after getting the phone which would pause the whole system for up to a minute, plus battery was highly drained.
I guess this is result of massively varied hardware for one mobile OS. (Plus bad programming)
Hai,
Since nobody bothered to answer my call to track down what drains the battery I decided to just post my findings and you do with it whatever you like...
In recent couple of months I've been experiencing quite nice battery life, almost a week on standby, which is basically on par with original LG ROM. The trick is simple:
It's happening as long as the Gallery app is NOT running.
I don't know what this piece of software does but when it's loaded to memory it stays in there and ignores attempts to terminate it, doesn't sleep when phone wants to and eats battery in a matter of single day. Unfortunately it seems some other apps use it directly or indirectly, like when Wi-Fi starts and/or by Market for example. Thus my solution is just to force close the Gallery after I finish activities which seem to require it.
I don't know whether root of the problem is with the app itself (like, CM modifications made so it's more cool, at the price) or it's just something else unearthed by certain SwiftDroid's configuration. To anyone who wishes to furher investigate my sincerest good luck. And I'd be grateful if results were published too.
hmskrecik said:
Hai,
Since nobody bothered to answer my call to track down what drains the battery I decided to just post my findings and you do with it whatever you like...
In recent couple of months I've been experiencing quite nice battery life, almost a week on standby, which is basically on par with original LG ROM. The trick is simple:
It's happening as long as the Gallery app is NOT running.
I don't know what this piece of software does but when it's loaded to memory it stays in there and ignores attempts to terminate it, doesn't sleep when phone wants to and eats battery in a matter of single day. Unfortunately it seems some other apps use it directly or indirectly, like when Wi-Fi starts and/or by Market for example. Thus my solution is just to force close the Gallery after I finish activities which seem to require it.
I don't know whether root of the problem is with the app itself (like, CM modifications made so it's more cool, at the price) or it's just something else unearthed by certain SwiftDroid's configuration. To anyone who wishes to furher investigate my sincerest good luck. And I'd be grateful if results were published too.
Click to expand...
Click to collapse
i deleted this slow sh** from /system/app and installed QuickPic!
hmskrecik said:
almost a week on standby
Click to expand...
Click to collapse
Are you joking? Should i use my phone as a doorstop,or what else?
EDIT: And,an old trick: when an app stays opened,to prevent it to reload again you have to delete his user data (works with Maps and Gmail too)
Eth4n said:
Are you joking? Should i use my phone as a doorstop,or what else?
Click to expand...
Click to collapse
You do with your phone what it damned pleases you. In case you haven't noticed the battery life is most often reported as either standby time or call time. In my typical usage battery lasts no less than two or three days but what 'typical usage' means may mean totally different things to me and to you.
Eth4n said:
EDIT: And,an old trick: when an app stays opened,to prevent it to reload again you have to delete his user data (works with Maps and Gmail too)
Click to expand...
Click to collapse
Hm, even more shotgun approach to what I described. Having user data could be the primary reason for keeping the app installed. But thanks for tip anyway, may come handy one day.
There is gr8 app on xda, better batery state. With this app you can see what aplication keep wake lock, use cpu, gps, etc...
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?