System Process Suspend. I noticed it runs at a constant 30% until i restart my phone. Anyone else having this problem or even know what event triggers this?
Flash is nice and all, but its not enough to compensate for all the crap froyo is dishing out.
so far my issues with this are wifi not connecting, any audio out ( mp3 or stream ) sounds like utter crap, and now this battery drain.
crunchyevo said:
System Process Suspend. I noticed it runs at a constant 30% until i restart my phone. Anyone else having this problem or even know what event triggers this?
Flash is nice and all, but its not enough to compensate for all the crap froyo is dishing out.
so far my issues with this are wifi not connecting, any audio out ( mp3 or stream ) sounds like utter crap, and now this battery drain.
Click to expand...
Click to collapse
I am not having any of these issues at all, my wifi connects, my battery doesn't drain like crazy, and my Pandora sounds like I am in a concert hall!!
Were you rooted before the update? Have you tried factory reset?
nope i was never rooted. i dunno, i search around the interwebs and it seems the things i am mentioning are common occurances to froyo.
however, none of these have an answer of why it happens in the first place, besides the streaming audio part.
its funny how for the past month or so that people have reported these problems to google, they do not even give it the customary "taking it seriously" line.
so has no one noticed their locally stored music sounds flat also?? this is the one part that intrigues me since that was how i first noticed the music quality suffered.
my music sounds fine with froyo :\ however i am on a custom rom not stock froyo. Also have no wifi problems and battery so far is on par with 2.1 (was hoping for a big increase in life but oh well least it doesnt seem worse to me)
crunchyevo said:
System Process Suspend. I noticed it runs at a constant 30% until i restart my phone. Anyone else having this problem or even know what event triggers this?
Flash is nice and all, but its not enough to compensate for all the crap froyo is dishing out.
so far my issues with this are wifi not connecting, any audio out ( mp3 or stream ) sounds like utter crap, and now this battery drain.
Click to expand...
Click to collapse
Looks like for me the initial battery drain was because Market was syncing the apps. Go to Market, menu, downloads - do you see all your apps, or just paid apps? If you only see paid apps there may be some kind of sync going on between the actual installed apps and the market service. I had a lot of apps, so it took almost a day for all apps to show up. Once they did, the battery was about the same as with 2.1.
Also Market was slow throughout the "syncing period" as well.
Pandora does have two settings now, high or regular quality. After I updated to 2.2 and used it for the first time, it sounded like crap. Checked settings and it was set to the lower quality output to conserve data/power etc. I switched to the high quality and it's been back to normal.
hahaha what version are you running 2.1 2.2 cause for me i get better sound with low quality over the headphone jack then i did with high quality.
for the op i noticed a big increase in battery life with froyo maybe do a factory reset or start removing certain apps maybe remove your task killer
this sucks man
maybe this is the cause
http://www.droid-life.com/2010/08/05/new-facebook-update-is-draining-batteries/
i do not think it is the facebook app, i dont use facebook.
the main source of my battery woes is that suspend process, i saw a few posts about it, but it seems like either there is no solution or it just happens to us unlucky few so no one cares.
just out of curiosity, if you were to use systempanel and look at the percentage of that process, what are your values? my phone was on for like 6-7 hrs and i got like 2hrs of cpu time on this process.
the wifi thing is very well reported in about every forum out there and the single point failure has been the update to froyo.
the audio issue is still a mystery to me because everyone else has issues when it comes to streaming, however i also get it with local mp3's.
i am starting to extremely dislike the qc of googles product. it does not seem to be a sense integration issue, so the fault lies in froyo it seems.
Pandora / Streaming Audio fix
tinyurl.com/33cmqbt
that is only for rooted phones
We don't have this issue in CyanogenMod...
that may be the case.
correct me if I am wrong but that is not possibilityfor people who did not root beforehand
I for one have noticed a slight decline in battery performance with froyo. What I've noticed is that I have a lot of apps opening in the background that somehow are not getting closed by autostarts or autokiller. I may have just not targetted every instance where they're triggered to open in the background but this was not happening in 2.1.
Facebook 1.3 definitely caused a huge battery decline for me. After I turned off notifications in the facebook settings the battery went back to normal. It's causing partial wake time, which is killing the battery. According to the android app facebook page they are working on fixing it.
i thought i read somewhere that froyo is not working with task killers and stuff like that? correct me if i am wrong
ok so another observation based on a suggestion from another forum.
when i look at the systempanel app for my cpu usage. i will never drop below 500.
some have stated that they use setcpu for force it under and it will not.
this still has nothing to do with my crazy suspend process chugging along, but it doesnt help my battery life any either
crunchyevo said:
i am starting to extremely dislike the qc of googles product. it does not seem to be a sense integration issue, so the fault lies in froyo it seems.
Click to expand...
Click to collapse
Personally, I think that everything that's at fault isn't Googles code, but porting that code to different hardware then what it was designed for (Nexus one).
mistersquirrle said:
Personally, I think that everything that's at fault isn't Googles code, but porting that code to different hardware then what it was designed for (Nexus one).
Click to expand...
Click to collapse
i feel that does fall under quality control of a release, but you are possibly right, they just half assed the port.
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)
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?