Related
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.
I am currently running ViperROM(DK28) version 3.0.3. I followed all of the instructions for fixing GPS on 2.2 and then flashed to this ROM.
Whenever I remove the DRM services I notice 2 strange things that happen:
1. Quadrant is not able to complete, it gets stuck on the first test at the Video Decoding.
2. I'm unable to select a new ringtone notification in handcent, when I press OK for my selection it hangs and I have to FC it.
The reason I want to remove the DRM services is that it appears to negatively affect battery life. I notice an improvement when they are removed. If I restore the DRM services everything starts working good again.
Any ideas?
I wont flame you,but this has been discussed plenty,search please...Anyway,you cant remove any of the 3 without losing some funcionaliy.So the only thing you can do is disable the one that runs at boot,not uninstall.I have tried this tip that orked for a day,once you have a fresh rom installed,play some music,watch a ripped movie,change a ringtone and notification,then remove all 3 services with sdx app removal or any other method you like.But like I said this will not work for more then 2 days at most
Sent from my SPH-D700 using XDA App
You're not the only one running into this issue.
I ended up rooting my Epic to get rid of all the sprint bloatware and what-not. Everything seemed to be going smooth from the stock standpoint. I removed Samsung Media hub first. Rebooted the phone and noticed nothing bad. Played around with the setup like that for a few days with no problems.
I next got rid of both the DRM service .apk's that were still running even after I got rid of the media hub... and then the problems started. For the first couple days I noticed DRAMATICALLY IMPROVED battery life and EXTRAORDINARY performance so I imagined what I did was a good thing: WRONG! A few days later, I noticed that if I assigned a sound to a notification or a ringtone *from the SD card*, that it would not work. I couldn't play sounds anymore and instead whenever I went to adjust the volume with said notes/tones selected, the Sound_service would crash.
However, I'm the only person I knew before now who has reported this issue so I'm sure there's not a lot of hubob to fix it. Every Epic is built different. Same parts or not. It's a mass-manufactured phone and each one will have its own quirks. There's my 2 cents.
I just froze the apps when I rooted with Titanium Backup but I thought I did something wrong and figured out that sound from apps seems to trigger the software crashes. No point if fixing it now. Flash DI18 and get the EC05 update and/or get EB13.
dyehya said:
I just froze the apps when I rooted with Titanium Backup but I thought I did something wrong and figured out that sound from apps seems to trigger the software crashes. No point if fixing it now. Flash DI18 and get the EC05 update and/or get EB13.
Click to expand...
Click to collapse
So can anyone confirm that the EC05 fixes the DRM issue? Otherwise there's no point in upgrading. I saw the release thread on here. Hecka people already having problems with the EC05. To upgrade for the Sprint ID packs? Won't see me do it...
Just let it do its thing. The amount of functonality you lose removing it is not worth the minute amount of battery life you'll save.
stir fry a lot said:
Just let it do its thing. The amount of functonality you lose removing it is not worth the minute amount of battery life you'll save.
Click to expand...
Click to collapse
I have to disagree about the amount of battery life I'm saving being minute. When I had this damned DRM service running, I maybe got 10-12 hours with moderate usage. Without it running and now with SRF1.0.2 running (gets rid of IQ), plus SetCPU to (clocking 200-400 when screen off, undervolting 1.0-1.2 during usage) I'm getting a good 20 hours with heavy usage or I can go 2 days without charging if I only use texting.
I do actually remember getting a good bit more battery from deleting the DRM but at the end of the day I'd rather have my music files and apps work properly. I'm used to keeping a charger on me, its just the nature of owning a smart phone.
Yeah I'm with you on that one. Hopefully this will be one challenge [ACS] will be up to digging into.
I just tried stopping it in the running services menu and tested it on a few things with no issues. Doesn't take more than 15 seconds. I'll probably start incorporating it in to my TWS/Airplane mode routine (which just happens to need around 15 seconds supposedly) whenever I reboot.
That's what alot of other people have been saying too. I guess that's what I have to do.
Some threads on SDX about this say you can use some killers to stop it at bootup (personally I've always hated killers since Android 2.0, you don't need them anymore). As long as the .apk and .odex's are there. It's only when you uninstall or freeze it that you start to run into problems 1-3 days down the line.
I use Startup Auditor and it only kills it briefly. I've read all the arguments against Task Killer but I'm still a fan of it. Its especially useful to see what programs start up on their own and I do notice better performance after killing the ones that have no business being open. For everything else I just set it to ignore them.
Anyone else expiriencing this problem? For me it goes like this:
At random times the screen gets sluggish in the transitions, and stay this way for quite a while. While this is going on, I can't long-press anything, because of the "lag" the screen doesn't register long-press, but single-press. Meaning there's a bunch of features I can't use..!
It doesn't just regard the GOlauncher stuff, but all of it, like f.ex the lock-screen - if i try yo drag the slider half-way and hold it there, it won't hold, but snaps back. If I slide quickly, I can unlock the phone, so it seems that the problem is to register touches lasting longer than 1/2 sec. or so..
Is this most likely a HW or SW problem?
I watched your video, and yes I had this problem also. Trying to unlock the phone resulted in it resetting input and being an incorrect pattern. Can you do something for me? Download mutlitouch tester (visualizer) and just hold your fingers on there, normally what it should do is stay solid, but with if your problem is the same as mine. It will blink rapidly. Mine was also periodically, the issue appeared to be with the Email and other email clients based of the stock one (not gmail or k9mail) client, so try removing all accounts on there if any. But the cause behind this was the fact that the garbage collector was running every second and it seemed to free up the memory used by the input driver. If this doesn't work, try a different ROM, like B137, or MIUI (I am using this, its great).
and most of all, let me know how you get on.
Feel free to email at [email protected].
Thanks for your reply ryronz, I'll try the multi-touch-tester next time it acts up, for now it's fixed itself again.
Are you positive it's linked to email-accounts, because I actually did just link up my exchange-account..! Could you explain this about the garbage-collector a little bit closer? Are there any settings in the exchange-account I can change to remedy the problem?
toth42 said:
Thanks for your reply ryronz, I'll try the multi-touch-tester next time it acts up, for now it's fixed itself again.
Are you positive it's linked to email-accounts, because I actually did just link up my exchange-account..! Could you explain this about the garbage-collector a little bit closer? Are there any settings in the exchange-account I can change to remedy the problem?
Click to expand...
Click to collapse
Exchange! Yup, thats when it started happening to me, and no I never found a way to solve the garbage collector thing. Its just something that happens whenever the phone feels it needs to run, there is nothing you can do to make it happen or not happen. I ended up removing the email client and using K9Mail.
Even if I don't like the answer, it's always good getting closer to the problem, so thanks
By the way I actually did an official FW-update from Huawei, and had the same problem both before and after.
So what is this garbage-collection? What kind of garbage are we talking about?
toth42 said:
Even if I don't like the answer, it's always good getting closer to the problem, so thanks
By the way I actually did an official FW-update from Huawei, and had the same problem both before and after.
So what is this garbage-collection? What kind of garbage are we talking about?
Click to expand...
Click to collapse
What the garbage collector does is when unused memory is still allocated, it will come and clear it automatically. This should only happen when the memory is used up, or near used up. But in saying that even though it is running all the time, the input driver memory should not be getting garbage collected. So my guess is its another poorly written driving from Huawei.
I have the same problem here. However I have not, up till now, been able to identify what caused the lagging (and battery drainage?).
For testing purposes, I have today deactivated the current exchange account setup, and installed another email client (Touchdown). With the new client running, the lagging was gone.
After that, I have removed Touchdown and reactivated my old account setup.
A search on Google indicates that there might be some issues with Android and the use of Exchange email....
As a new test, I have now changed the sync periode from one hour to 'push'. I found that suggestion somewhere in my search for a solution.
Maybe it is to early to conclude, but as far as I can see after a few hours with the phone mostly in standby, I can spot some improvements with regards to both the lagging and battery drainage.
Heyo bros so I'm experiencing what I'm afraid might be a problem:
I've been getting watchdog alerts regarding the "Base System" process. It notifies me that the CPU % at the time of the captures range from 40% to 60+%. Coincidence or not, it usually happens when I wake my phone from sleep- not when I unlock it, just when I press the power button. The moment the lock screen pops up, the phone's already vibrating and the watchdog notification is up in the status bar.
Battery life so far is:
9h 22m @ 74%; Phone Idle- 56% | Cell Standby- 22% | Display 17% (40m) | Android OS 3% | Voice calls- 3%
Who knows, maybe this^ looks normal. I just want to be sure.
I've heard talk of 'wakelocks' but I don't know exactly what they are, what might cause them, and how I can track them.
I'm currently running:
Atrix 4G (not 2, just for clarification)
CM7 xB^xN
Baseband reads: N_01.77.30P
Kernel version reads: 2.6.32.39-MB860-GB-Faux123-v0.2.1 [email protected] #14
Build number: GWK74
Totally honest, I don't know if that might be able to help diagnose the problem, but for what it's worth, I want to check two things:
1) I flashed Faux's enhanced stock CM7 kernel, and am pretty sure it took, but does that look to be the proper kernel version? I just want to be sure.
2) While I also flashed the "latest radio" in the CM7 xB^xN thread, I was certain there was an xx.97 radio (vs the x.77 radio that mine appears to currently have). Am I indeed on the latest radio version?
Would it hurt to reflash these two? Could either one, or maybe both, be the cause of this?
It also occurs to me: I've been using SetCPU and have ONE profile set up that forces my CPU to min/max 216/216 when the screen is off. Could that be causing it?
Thanks so much for any and all insight bros. Also, please let me know if there's any more info you might want to help diagnose what the dealio is.
Heyo guys,
I hate to bump this kinda soon, but this is definitely a problem.
It's getting to be that I don't even have to wake the phone up for the Base System to spike. I was woken up a couple times in the middle of the night by notifications saying it was really high.
You guys have any thoughts? I'd really like to get this resolved as CM7 is AWESOME.
Yes, you guessed it- I'm not anal about the fingerprint scanner or webtop. Just a stable and fully functional release.
Thanks for any help bros I really appreciate it.
Hi, new member here.
I get the same weird spike to 50-60% (and was woken up too in the middle of the night by watchdog). I have narrowed this occurrence to when I have both Watchdog & Juice Defender enabled at the same time. (Yeah it took me a while to figure out)
When I disable Juice defender the problem seems to go away. So I'm thinking one of the power saving settings turns the radio off & a core system process really does not like that.
This is on a non-rooted Atrix, I have not tested on a rooted Atrix.
So far I had to turn off the watchdog alarm so I can sleep. If anyone can think of a solution it would be appreciated!
AX-MA said:
Hi, new member here.
I get the same weird spike to 50-60% (and was woken up too in the middle of the night by watchdog). I have narrowed this occurrence to when I have both Watchdog & Juice Defender enabled at the same time. (Yeah it took me a while to figure out)
When I disable Juice defender the problem seems to go away. So I'm thinking one of the power saving settings turns the radio off & a core system process really does not like that.
This is on a non-rooted Atrix, I have not tested on a rooted Atrix.
So far I had to turn off the watchdog alarm so I can sleep. If anyone can think of a solution it would be appreciated!
Click to expand...
Click to collapse
Thanks for the insight bro. For what it's worth, I'm not running Juice defender, or any other kind of battery saver app.
Looks like a couple of us are having problems then, though. We'd both really appreciate any info, advice, or help.
Ok, it seems it was just a coincidence with Juice Defender then.
The problem may be unrelated to power savings, but it is indeed a problem.
xyrovice said:
For what it's worth, I'm not running Juice defender, or any other kind of battery saver app.
Click to expand...
Click to collapse
AX-MA said:
Ok, it seems it was just a coincidence with Juice Defender then.
The problem may be unrelated to power savings, but it is indeed a problem.
Click to expand...
Click to collapse
It doesn't have to be unrelated to power saving just because xyrovice is not running Juice Defender, there is a option for power saving in the battery settings for the Atrix that does a similar function.. Before ruling out power savings as unrelated I would make sure xyrovice is set to "performance mode".
WiredPirate said:
It doesn't have to be unrelated to power saving just because xyrovice is not running Juice Defender, there is a option for power saving in the battery settings for the Atrix that does a similar function.. Before ruling out power savings as unrelated I would make sure xyrovice is set to "performance mode".
Click to expand...
Click to collapse
I'm running CM7 and skimmed through the settings menu and didn't find anything about 0ower features. I know that in Blue ROMs there's the battery manager section, but I don't think CM7 has this. Anything else I should look at, though?
Thanks for the insight too bro.
xyrovice said:
I'm running CM7 and skimmed through the settings menu and didn't find anything about 0ower features. I know that in Blue ROMs there's the battery manager section, but I don't think CM7 has this. Anything else I should look at, though?
Thanks for the insight too bro.
Click to expand...
Click to collapse
oIc, no I dont guess you will have those settings in CM, I should have thought of that. I wish I could help because I had the exact same prob with Watchdog constantly alerting for "Android Core Processes" and "Android Media processes", but I dont get those alerts anymore. I haven't changed ROMs or anything.. The only thing I can think of is I changed the MinFree values, I used the app "AutoKiller Memory Optimizer" to change them.
WiredPirate said:
oIc, no I dont guess you will have those settings in CM, I should have thought of that. I wish I could help because I had the exact same prob with Watchdog constantly alerting for "Android Core Processes" and "Android Media processes", but I dont get those alerts anymore. I haven't changed ROMs or anything.. The only thing I can think of is I changed the MinFree values, I used the app "AutoKiller Memory Optimizer" to change them.
Click to expand...
Click to collapse
Do you know why that seemed to solve the problem...or if it even WAS the problem, per se?
Also, is there any reason CM7 would have the minfree set to a default that causes this?
Lastly, what did you alter the minfree values to? You think ROM toolbox might have this capability?
Thanks so much for saying this bro. Who knows, this might be the problem.
PS: I just tried this and am going to see if it works. Post #13 is the one that would really sum up my reaction of successful.
Hopefully maybe this helps my other bros.
xyrovice said:
1Do you know why that seemed to solve the problem...or if it even WAS the problem, per se?
2Also, is there any reason CM7 would have the minfree set to a default that causes this?
3Lastly, what did you alter the minfree values to? You think ROM toolbox might have this capability?
Click to expand...
Click to collapse
1.) no I can't say for sure what the problem was or why I no longer get the Watchdog alerts. I was just trying to think what I have changed since they stopped because I haven't changed ROMs.. Since changing the MinFree has to do with how many or what apps are left running I'm just kinda throwing it out there as a possibility since your at a loss for things to try.
2.) no I can't think of any reason, and most with CM don't have this prob right..?
3.) It's posible it does have the capability because it does allot but I am not sure.
Foreground 12
Visible 18
Secondary 36
Hidden 121
Content 129
Empty 137
possible solutionary steps I've taken:
So Update:
I actually ended up checking out my (partial) Wakelocks with betterbatterystats, and I think I may have found a problem (diagnosed with alarmdump.txt from the Alarm Manager):
1) When I first flashed CM7 I thought, "Oh well why not really get comprehensive about keeping apps up to date" and I actually, for every single app, checked the "Automatically update" box in each one's market page. This led to a CATACLYSMIC wakelock that I'm now pretty sure could be the problem.
2)Google talk also seemed to be a little active with the screen off so I unticked the "sign me in auto..." box and made sure I signed out.
Lastly (not related to wakelocks), I checked on my TTS settings (see my last post about that).
Oh also LASTLY lastly I froze the modem fastdormancy manager in TiBU (kinda just for ****s and giggles). That said though, is the consensus on this that it's pretty harmless?
So, other bro who was having a problem, check and see if this might help you at all AYY
WiredPirate said:
1.) no I can't say for sure what the problem was or why I no longer get the Watchdog alerts. I was just trying to think what I have changed since they stopped because I haven't changed ROMs.. Since changing the MinFree has to do with how many or what apps are left running I'm just kinda throwing it out there as a possibility since your at a loss for things to try.
2.) no I can't think of any reason, and most with CM don't have this prob right..?
3.) It's posible it does have the capability because it does allot but I am not sure.
Foreground 12
Visible 18
Secondary 36
Hidden 121
Content 129
Empty 137
Click to expand...
Click to collapse
Thanks for posting this. I checked ROM toolbox and it does indeed have the capability. That said, if my aforementioned possible solutions don't work, I'm turning here. Thanks for the info bro.
Watchdog is flagging the "base process" app because IT IS using over 60% of your CPU BUT it is using 60% of your CPU that is running at 216MHZ.
It's your screen off setcpu profile of 216/216, if you bump up the max to 456 the alert will go away. When you have it set as 216/216 Watchdog (I believe) thinks that is the actual max cpu speed and bases its percentages off of that. I got that warning before and after a bit of troubleshooting (actually tried several different things) found that was the problem.
I am not sure but if you "whitelist" a app in watchdog it might ignore it as well. However my alert level was set at 80% and it would still set it off, so I think the higher speed might just be better.
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...