Related
I'm having some awful slow-down issues with my N1. Like, 3 second delays between clicking widgets and their intended effect, and even longer switching between home screens (if the screens switch at all).
There's no auto task-killer enabled, I've very recently wiped and re-installed CM, and cleaned out my unused apps. I've got around 200MB of RAM free, constantly. SetCPU is keeping my processor at 461MHz or higher. This is obnoxious as balls, and I can't think of much. :s
Any suggestions?
I'm running CM 5.0.6, btw.
i have the same problem
My N1 is not rooted and I am experiencing slowdowns. When opening txt messages now take 3-5 seconds, and typing completely locks sometimes for 20 seconds. Gmail now takes 5+sec to open and other apps are also seeing this. I just had 10+ programs update themselves and all these issues started appearing suddenly. Also when exiting apps my desktop will be blank for 3-5 seconds. This just happened all within the past 2 weeks or so.
reddragon72 said:
This just happened all within the past 2 weeks or so.
Click to expand...
Click to collapse
Yeah, the issue is very recent for me too. Last week.
I am wondering if Google sent out an OTA that is prepping the phone for the 2.2 update??? The reason I say this and not point to an app is the simple fact that I have all my apps stopped completely and the issues still exist.
reddragon72 said:
I am wondering if Google sent out an OTA that is prepping the phone for the 2.2 update??? The reason I say this and not point to an app is the simple fact that I have all my apps stopped completely and the issues still exist.
Click to expand...
Click to collapse
Mmm, I dunno about that. I'm running CyanogenMod. I don't get OTA updates. Do you remember, recently, getting an OTA?
Unless it was pushed inside of a market-updated Google app (uhh.. No.), I wouldn't have got it.
Zak Jones! said:
SetCPU is keeping my processor at 461MHz or higher.
Click to expand...
Click to collapse
You set your CPU at 461Mhz?? Sure it slow down and lagging. What the point buying a 1Ghz processor phone decide let it run at 461Mhz?
Check the profile if you are not set at 461Mhz, maybe accidently make a profile setting and enable.
Or set your setCPU setting from on demand to on performance.
What kernel are you running?
Andrewtst said:
You set your CPU at 461Mhz?? Sure it slow down and lagging. What the point buying a 1Ghz processor phone decide let it run at 461Mhz?
Check the profile if you are not set at 461Mhz, maybe accidently make a profile setting and enable.
Or set your setCPU setting from on demand to on performance.
Click to expand...
Click to collapse
I think he's setting the minimum at 461 hence the "or higher" part.
Well, I can't actually help much except to suggest that perhaps you could try Kang-o-rama (see my sig) and see if that works. It's a stable and fast bundle with no apparent lag. At least I know that setup works.
If you did proceed then posted your results in that thread I might be able to assist. You shouldn't be experiencing lag with this phone... and if you still are after installing Kang-o-rama we could look at logs for you.
No promises but I know Kang-o-rama works...
Success? Sorry for the laggy reply.
JCopernicus said:
I think he's setting the minimum at 461 hence the "or higher" part.
Click to expand...
Click to collapse
Yeah, Copernicus is right, it's at a minimum of 461MHz (now 499MHz.), with a max of 998MHz, running 'on demand'.
antoniouslj said:
What kernel are you running?
Click to expand...
Click to collapse
I'm using whichever kernel comes with CM. (2.6.33.2 is specified in the relevant section of his changelog.)
djmcnz said:
Well, I can't actually help much except to suggest that perhaps you could try Kang-o-rama.
Click to expand...
Click to collapse
Yeah, won't lie, I'm sick of reinstalling all my stuff, so I don't want to do it again. If I keep having issues, I'll look into it though.
Just last night, I wiped both the data partition (factory reset?) and cleared the Dalvik(sp?)-cache. Started from scratch (without Google settings sync.), and reinstalled apps one by one. SO FAR, I haven't had the slowdown, but who knows. All I've got installed yet are the applications that I actually had desktop shortcuts to. (I didn't have very many more, but these are the ones I actually used frequently.)
Anyway, yeah, I'll see how this goes.
K, need a suggestion.
Zak Jones! said:
Anyway, yeah, I'll see how this goes.
Click to expand...
Click to collapse
Sooo, it's not going. Still experiencing the slowdown. I honestly can't think of what's doing this. Advanced Task Manager reports > 190MB free (28 processes running), SetCPU is still running at 499MHz or greater (I can't get 'show CPU to work in Dev Tools?).
Ending everything in the "All Apps" tab does not fix the problem; it's speedy for about 30 seconds, then resumes being slow, with the same problems (so maybe it's a process taking up all my CPU cycles? (But my CPU isn't scaling up like it would in that situation...))
Anything I can try doing before re-flashing and/or wiping? I'd rather avoid that, but, of course, if it's the only solution, whatever. Maybe try flashing a new ROM?
Can't think of what else to do here, gentlemen.
Get rid of SetCPU. I had it installed and it started weirding out on me, would not set the processor higher than 384 and nothing I did in the profiles would set it back to 1 GHz. After I uninstalled, my phone returned to it's normal speeds.
Zak Jones! said:
Sooo, it's not going. Still experiencing the slowdown. I honestly can't think of what's doing this. Advanced Task Manager reports > 190MB free (28 processes running), SetCPU is still running at 499MHz or greater (I can't get 'show CPU to work in Dev Tools?).
Ending everything in the "All Apps" tab does not fix the problem; it's speedy for about 30 seconds, then resumes being slow, with the same problems (so maybe it's a process taking up all my CPU cycles? (But my CPU isn't scaling up like it would in that situation...))
Anything I can try doing before re-flashing and/or wiping? I'd rather avoid that, but, of course, if it's the only solution, whatever. Maybe try flashing a new ROM?
Can't think of what else to do here, gentlemen.
Click to expand...
Click to collapse
You might not like my advice but it's likely to work:
Don't uninstall SetCPU but set your CPU min to 245 and the max to what you want. Disable profiles but select 'Set on Boot' and 'On Demand'. Do nothing else with SetCPU, leave it alone and do not use the active widget. Your current setup is crazy.
Full wipe (as you've done before) data, cache, dalvik-cache, battery, rotate and then install Kang-o-rama 0.7b1 (no, I'm not simply pushing it, I just know it so well that I can assure you it works).
Do not, under any circumstances restore any data or apps for any application with any application. As soon as you set up your Google account go into Settings | Privacy and disable "Back up my settings" and hit Okay.
Install a task manager if you like for monitoring purposes. Install SetCPU as above if you like for OC.
Install no other apps (now that's the painful part) and use your phone for long enough for you to know with certainty whether it's working as you expect.
In all honesty, if it's still broke after that then you've probably got a hardware issue. If it's working after that then slowly add your apps back until you find what's causing the problem.
Good luck, report back.
So far, uninstalling SetCPU is doing wonders for me. Y'know, over the last 15 minutes. I'll use it throughout the day and see if it keeps performing.
Space for future updates:
****ING BALLSACK. <--- First impression of Kang-o-Rama (I decided to just go for it and flash as soon as I saw it included CM.)
^^^^^^^^^^^^ That text is to be read: Kang-o-Rama is amazing. The theme is sexy, I LOVE the Desire camera, and the bundled stuff (kernel, apps, etc) are quite awesome. We'll see if it solves my performance issues.
I was getting the same thing....
Task kill setcpu and reboot it again. If you keep getting the lag then stop using setCPU.
Zak Jones! said:
****ING BALLSACK
Click to expand...
Click to collapse
It takes a twisted mind to interpret that as a complement.
Zak Jones! said:
...Kang-o-Rama is amazing...
Click to expand...
Click to collapse
But thank you!
Delete all widgets that profile your cpu in any way. Stop killing tasks with task killers. Uninstall setcpu. Set exchange email app to "PUSH". Download "Quick System Info Pro" and check what's using up Cpu.
I had the same problem and it turned out to be 2 things: SetCPU widget and exchange email app stuck in a sync cycle.
Maybe theres an ill-performing app that you installed. Since it seems you wiped your phone a couple times including cache. Did you happen to restore apps thru Titanium backup or manually one at a time thru the market.
I always wipe my phone completely and reinstall all apps manually, time consuming, but I have never had a problem.
To further diagnose your problem, see if after installing each app, try the phone to see if there are any slowdowns afterward. Again, I know this is time consuming, but trying to find the problem rather than living with it would be better.
I'm also using 5.0.6 but with no problems or slowdowns.
You can also post a logcat or look thru it yourself if you know how and see if any errors or hangups occur. Logcats are a great way to see the commands being given to your phone and this will most likely reveal your problem.
Same problem, it's annoying.
Hey all,
Sorry if this has been answered/asked already, but is there a way you can prevent SetCPU from getting killed by AutoKiller? I have the autokill-profile in AutoKiller set to "Default", but the system assigns SetCPU an OOM value of 11-14, which is the highest value for getting killed (essentially regarding it as extremely non-important). How does one PERMANENTLY set SetCPU on the "Do-Not-Kill List"?
Thanks in advance.
PS: I'm running KaosFroyo v35-1 and so I can't uninstall Autokiller.
Short answer: No
Long answer: Noooooooooooooooooooooooooooooooo
Hungry Man said:
Short answer: No
Long answer: Noooooooooooooooooooooooooooooooo
Click to expand...
Click to collapse
Lol...funny stuff
As for OP you can uninstall autokiller if you want too...just look up how to remove apps through adb or terminal on phone.
Hungry Man said:
Short answer: No
Long answer: Noooooooooooooooooooooooooooooooo
Click to expand...
Click to collapse
why cant you just lower the oom value by clicking and holding setcpu under the processed tab and select lower oom value, it will drop it to -17, which practically means it is being ignored.
"Practically" is not what he asked for. What he asked for is a permanent solution.
tyler1524 said:
why cant you just lower the oom value by clicking and holding setcpu under the processed tab and select lower oom value, it will drop it to -17, which practically means it is being ignored.
Click to expand...
Click to collapse
That only works for about 3 minutes, until the system automatically increases the OOM value back to like 12 or 13.
I don't understand... even when I have it set to system default, after a while, it still kills it. So that means, even if I were to uninstall Autokiller, the SetCPU would still be killed after a while?
Doesnt matter if its killed. Its android, itll come right back
Nikolai2.1 said:
Doesnt matter if its killed. Its android, itll come right back
Click to expand...
Click to collapse
That's the problem. SetCPU doesn't.
Acrono said:
That's the problem. SetCPU doesn't.
Click to expand...
Click to collapse
I check my processes constanly and i dont see it going away. Maybe im wrong
Maybe Autokiller is correctly determining that SetCPU is consuming more power and Country cycles than its providing. I've certainly found that to be the case with Kaos Froyo
-------------------------------------
Sent via the XDA Tapatalk App
I'm joking about Autokiller's intuition but serious about the dubious benefits of SetCPU on an already overclocked ROM
-------------------------------------
Sent via the XDA Tapatalk App
Nikolai2.1 said:
I check my processes constanly and i dont see it going away. Maybe im wrong
Click to expand...
Click to collapse
It's always killed after 10-15 minutes, even on the default setting. If I set it to aggressive, immediately after it goes into the background, it's killed within a matter of seconds.
paulbonner said:
I'm joking about Autokiller's intuition but serious about the dubious benefits of SetCPU on an already overclocked ROM
Click to expand...
Click to collapse
KaosFroyo is already overclocked? I notice a huge performance gain when I enable SetCPU and OC it to 710mhz. If KaosFroyo is indeed overclocked already, then it must be set pretty low, or at least, very close to stock settings....
Acrono said:
KaosFroyo is already overclocked? I notice a huge performance gain when I enable SetCPU and OC it to 710mhz. If KaosFroyo is indeed overclocked already, then it must be set pretty low, or at least, very close to stock settings....
Click to expand...
Click to collapse
Ocd to 710 by default
Edit: I've had the best results ditching setcpu and using the collin_ph script, just btw
I see that setcpu is at a constant 2 ooms. Now im using Zen express but idk if that makes a difference. And im set to strict
The real and best answer I have for the first post (and what I do, and advise everyone I am around to do)
Stop using Autokiller.
Android does a great job killing processes.
Most users use 4-5 apps constantly throughout the day, and if the few most commonly used ones stay in memory more often than not, the phone is FASTER, as a result of calling up apps instead of having to completely relaunch them every time.
YES, using autokiller to adjust your memory settings can help if you are normally running process-intense apps in the background (like I sometimes run a VNC for work that will chew up some processor time if I just hit 'home' when I'm done instead of killing the task, or sometimes a small game that you figured was not in memory anymore, is still chewing up processor time).
BUT
That is what, and only what, I use a task killer for. I open up Free Advanced Task Manager, kill my background process that I don't want running, and move on with life.
9 days out of 10, I don't use a task killer, and I NEVER use auto killer.
If you want to keep your phone faster than not, use 'back' to get out of apps instead of pushing 'home'. Unless 'back' is mapped to something in the app (like for some apps), back will end the process rather than leave it running.
I could write ten pages on why to not use autokiller, but a lot of guys who are a lot smarter than me will swear by it. I just find it slowing down my phone by forcing me to re-launch things like Handcent SMS, my Web Browser, and Google Voice, when I'd rather have those things stay running in the background. They don't chew up much processor time just sitting in the 'background', and my phone is WAY faster if it takes 1 second to open up each app instead of 3-6 seconds (because autokiller made my phone already automatically kill the task).
Good luck with your decision, sir.
And if you're using xtrSense, you can just set up your GScript to overclock how you want (mine's at 806800), and if you're using Froyo ROMs, you can use the battery tweak. SetCPU isn't that useful for most of these ROMs, since the methods of overclocking by collin_ph's battery tweak and xtrSense's GScript are faster and more efficient, and don't require a background process like SetCPU to be running.
But that's just my opinion. I hope it helps.
I use System Panel to basically monitor my memory instead of just relying on Autokiller to manage them for me. I also found that the way I use my phone, similar to the way pkopelek mentions, a few select apps a day, my free memory stays fairly close to what it did with autokiller installed. Average around 40-60 and if I kill a few off, up to 90-100.
One thing I have noticed is that System Panel comes with a cpu scale and shows your clock speed. With no SetCPU installed my CPU will drop down to 245 and then bounce around and finally settling back to 245 then the cycle starts again. With Collins tweak I get the same response. However, with SetCPU installed my CPU will clock down to 245 and sit there until I touch the screen. I have to believe that SetCPU is doing something that collin's isn't. Now the only way I can get it to behave this way is if I change the advanced parameters.
just my 2 cents.....
When I used AutoKiller and SetCPU (I used both between May and August) before I started using xtrSENSE v4.x, I never had a problem with SetCPU quitting working under any ROM, including any Froyo that was out at the time.
I only mean that perhaps the problem isn't between SetCPU and AutoKiller. Maybe it is the ROM??? Just guessing here.
Nikolai2.1 said:
I see that setcpu is at a constant 2 ooms. Now im using Zen express but idk if that makes a difference. And im set to strict
Click to expand...
Click to collapse
I'm using this: http://forum.xda-developers.com/showthread.php?t=685594 and the value is ALWAYS above 9. I've never had it down that low except when I temporarily add it to the ignore list (it falls out after about 5 minutes).
I apologize in advance if someone has covered this, but I discovered a nice little trick thats simple to perform and gives me roughly 2-3x additional battery life than before (if not more).
Recently I got a little fed up with my ~8hour battery life and decided to get a 3500mAh battery. Even after receiving my brand new fat battery, I was still only getting about ~16-18 hours on a charge. Well I decided to get to the bottom of this and see just what exactly was sucking away my juice.
I managed to find a handy little app named "PowerTutor" that gives a great reading of what applications are using power and approx how much. It even separates network usage from processing jobs as far as power consumption is concerned. After taking a few samples over various time frames and conditions I came to the conclusion that the biggest power consumer was actually the Google frameworks.
The simple fix to this:
Download "DroidWall", an excellent application that allows you to black or white list applications from data use. After blacklisting Google app frameworks. I saw a very significant change in battery life.
The next thing I did was grab "SetCpu" and set up a profile on event "Screenoff" to go to "powersave" mode and set my frequency 537max and 245min with a low priority. I set an additional profile for when my phone is active at full the frequency range with on demand scaling. Theres are better configurations out there I'm sure but this is just what I used on the fly. Feel free to set it up however you'd like.
I've been using my phone all weekend with moderate use (text, web, videos, etc) and now see an amazing standby time. The only problem with blocking the Gapps frameworks from having net access is that gapps specific applications can no longer update in real time. I'm a Google voice user so this started to present itself to be a problem. Luckily GVoice is capable of forwarding text to phone. And when you do that the Gvoice app will pick up the standard text as long as you have the option selected from your Gvoice account. So I just disabled standard text notifications on my phone. Now when I'm sent a text, Gvoice picks it up and I can respond with Gvoice just as nothing had changed.
Yes I already know turning your data connection would in theory do the same thing as listed above. However this way you dont have to toggle your data on and off constantly.
Hope this helps someone, if you get a chance to try this out post your results!
Interesting, may give this a shot
Sent from my PC36100 using XDA App
Breaker253 said:
The next thing I did was grab "SetCpu" and set up a profile on event "Screenoff" to go to "powersave" mode and set my frequency 537max and 245min with a low priority. I set an additional profile for when my phone is active at full the frequency range with on demand scaling. Theres are better configurations out there I'm sure but this is just what I used on the fly. Feel free to set it up however you'd like.
Click to expand...
Click to collapse
Everything else you said has peaked my interest and so when I have time I will test these suggestions.
However, I just wanted to point out that the powersave governor locks the cpu speed to the min frequency and so there really is no reason to specify a max of 537 or anything else because the powersave governor won't allow the cpu to scale beyond the min value.
On the opposite side, the performance governor locks the cpu speed to the max freqeuncy and won't allow the cpu to scale below the max value.
If you intend on using the powersave governor and want your cpu to not go above 537 then set the min value in setcpu to 537. As I said earlier, the powersave governor will lock the cpu at the min value so if you do this you will always be at 537 during screen off.
Breaker253 said:
.....set up a profile on event "Screenoff" to go to "powersave" mode and set my frequency 537max and 245min with a low priority.
Click to expand...
Click to collapse
Why set Max to 537? Powersave pegs CPU frequency to min value.
Sent from my PC36100 using XDA App
ah, didn't know that. I thought that on power save it just stepped the cpu frequency up slower and dropped it much faster. thanks for the correction .
Sent from my PC36100 using XDA App
Breaker253 said:
ah, didn't know that. I thought that on power save it just stepped the cpu frequency up slower and dropped it much faster. thanks for the correction .
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
That's the conservative governor which I personally use for sleeping and I don't change the max/min values either.
How does this affect google maps navigation, push gmail, and things like that?
Gmail seems to be pushing fine for me. Maps works also but you'll need to have gps active.
Sent from my PC36100 using XDA App
Question for you OP. you said you blocked google frameworks. I don't use google voice, so that part won't be an issue. My question is, what else is affected by the framework being blocked?
lovethyEVO said:
Everything else you said has peaked my interest and so when I have time I will test these suggestions.
Click to expand...
Click to collapse
Just since I see this error all the time, the phrase is "piqued my interest," not "peaked."
From what I've experienced, clocking too low can use more battery since the cpu has to stay at the max clock for longer periods of time to complete a task, as it is not as efficient at performing it.
I've only noticed location services (not gps) blocked. Gmail seems to be receiving updates as far as I can tell. Other than that everything seems to be working as our should.
Sent from my PC36100 using XDA App
Breaker253 said:
I've only noticed location services (not gps) blocked. Gmail seems to be receiving updates as far as I can tell. Other than that everything seems to be working as our should.
Click to expand...
Click to collapse
Looking at the DroidWall screenshot, it appears the calendar and contacts won't sync automatically either. If it wasn't for that I'd probably give this a try.
eventer289 said:
Just since I see this error all the time, the phrase is "piqued my interest," not "peaked."
From what I've experienced, clocking too low can use more battery since the cpu has to stay at the max clock for longer periods of time to complete a task, as it is not as efficient at performing it.
Click to expand...
Click to collapse
I posted that with my evo using swype and I wasn't paying attention to the auto correct. Thanks for the correction though.
Going to keep my eye on this thread.... I use google calendar EVERY day, so I need that.... Anyway to unblock certain apps?
so if i already manually sync gmail, contacts, facebook, and gCalendar, will this still help me?
Unless you temporally disable the blocking of frameworks, calendar and contacts won't be able to update with what's NOT on your phone already. You can still use your contacts and calendar, it just won't update if you made any changes from the web and not on your phone.
Sent from my PC36100 using XDA App
I'm using juice defender on my ego and it seems to work great. I'm also using setcpu to knock the sped down to 245 when the screen is off. It's also set to gradually step the speed down as the battery drains. At 75% its at 844 at 50% its at 614 and at 25% its at 422. All of them have a min of 128. My off screen life is insane. In 7 hours it went from 100% to 90% with some light use and mostly sleep time. Right now I'm at 65% with a good 3 hours of net use on my wifi and a few other things. Before all this I was getting 8 hours total.
Once a get a good week of use ill try out droidwall. It looks neat and I like its charts
Breaker253 said:
Unless you temporally disable the blocking of frameworks, calendar and contacts won't be able to update with what's NOT on your phone already. You can still use your contacts and calendar, it just won't update if you made any changes from the web and not on your phone.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Will changes to the calendar and contacts from phone still sync to Google automatically?
Wouldn't most of this be achieved by simply turning Auto-Sync off? (can be done using the Power Control widget for easy access.) Or am I missing something?
This is what I do when I want to save power. Then you can manually sync gmail and things whenever you like from within the respective apps.
I've gotta feeling you used latitude in google maps and also have the location settings all checked under settings-> location in the main android settings panel. If your not on WiFi this will drain your battery pretty decently, and even more so if you are in not so great coverage.
Hi, I am using watchDog to try to see what processes start while the phone is in sleep mode. But I cannot find anything on WatchDog that tells me what is consumming battery.
I hope I make it clear.
The situation is the following.
When the phone is sleeping, with no 3g or wifi, it takes around 10% in 8 hours. Just iddle. This happens at night. When sleeping.
As soon as I wake up, I turn on 3g. And the battery starts draining. I understand this is normal. But should the phone be awake all the time just by having 3g on?
The awake bar is almost full. Eventhough the phone is locked. This happens only when I turn 3g or wifi on.
That's basically my question. Sorry if it is misleading or something.
Regards
the phone will be awake if you installed some rogue app that connects to the net every 2 minutes to check something, or just some badly coded app.
So I should start uninstalling each app to see which is the one? Or can I use an application that will tell me that? Itried watchdog, but got no success.
Any ideas?
I've found eBuddy to keep my Awake bar completely solid... EVEN if I'm completely exited out of it. It has to do with the fact that like any other app, Gingerbread keeps a cached version of the process in the background. But in eBuddy's case, staying cached causes the phone to stay awake, so the only way to resolve this is to completely kill eBuddy and any of its cached processes.
That's why I still run ATK at 30 minute kill intervals. Getting great battery life. Here's my original post on this issue:
http://forum.xda-developers.com/showthread.php?t=1094666
almorsol said:
So I should start uninstalling each app to see which is the one? Or can I use an application that will tell me that? Itried watchdog, but got no success.
Any ideas?
Click to expand...
Click to collapse
You can start by going into settings -> applications -> running services
Tap the "menu" button and make sure you are looking at only "show services in use" as opposed to all services including cashed.
You will get a list of about 10-30 (depending on what you installed and how you configured the phone)
Then go to settings -> accounts and sync, and under "manage accounts", see what accounts you created that sync up with somehting. make sure the icons (round circles) are green only for the accounts you truly want to sync.
Also tap through each account you do want to sync and check the sync settings . If there is an account that is set to sync every 2 minutes, or is set to sync at an unreasonable short time, change that. There could also be a bunch of account you what to totally switch into "manual sync" mode, for example email addresses you do not care about.
cmd512 said:
I've found eBuddy to keep my Awake bar completely solid... EVEN if I'm completely exited out of it. It has to do with the fact that like any other app, Gingerbread keeps a cached version of the process in the background. But in eBuddy's case, staying cached causes the phone to stay awake, so the only way to resolve this is to completely kill eBuddy and any of its cached processes.
That's why I still run ATK at 30 minute kill intervals. Getting great battery life. Here's my original post on this issue:
http://forum.xda-developers.com/showthread.php?t=1094666
Click to expand...
Click to collapse
I will install ATK and follow your steps buddy. Will let you know how this worked for me.
Regards.
I will do the same. Thank you!
Have a query, What Auto Kill level should I set and what's the difference between Crazy-Aggressive-Safe? I atm at Agressive!
ithehappy said:
Have a query, What Auto Kill level should I set and what's the difference between Crazy-Aggressive-Safe? I atm at Agressive!
Click to expand...
Click to collapse
I do Crazy, 30 minutes, and Low level so that I can see all processes (including system level). I then run my phone as usual and add any/all system related processes to the ignore list.
Good luck, and hope it works for you as well.
I just made a test, and found that the app that makes my phone to be awake all the time is the MSN Talk Pro.
I disabled it, and everything went to normal.
Is this normal in IM apps, since the other person was having the issue with ebuddy?
How could I have the IM app running without having my phone awake all the time?
The task killer would definetly work, but then I would not be able to get msn messages.
Is this the only option?
Thank you.
almorsol said:
I just made a test, and found that the app that makes my phone to be awake all the time is the MSN Talk Pro.
I disabled it, and everything went to normal.
Is this normal in IM apps, since the other person was having the issue with ebuddy?
How could I have the IM app running without having my phone awake all the time?
The task killer would definetly work, but then I would not be able to get msn messages.
Is this the only option?
Thank you.
Click to expand...
Click to collapse
Let me try to explain the situation.
If you have an IM client and you want it to be ready to accept messages from your buddies, it has to be in "listening" state to "hear" from your buddies. How that "listening" state is implemented by the developer defines how much batt power the application is eating.
Two opposite example:
1) Some stupid developer coded the IM client to always stay in foreground on your phone, actively pinging the servers on the internet , asking the servers if you have new messages. Your battery is wasted big time man.
2) A smart developer coded the IM client to use Google's C2DM interface (Cloud to Device Messaging framework). Such an app will stay dormant on the phone, and will be woken up by the android core processes whenever a new message arrives for you - Google servers will wake up the app on your phone. Such an app will not waste battery much.
There are a number of variations that go in between (1) and (2) above. So there is no clear-cut good or bad app. All depends on the implementation, and also on the way you configure your phone and the app on it.
Latest version of eBuddy was supposed to use C2DM too.
Ad the new Trillian is using C2DM. I never tried any of these though, can't vouch for any.
Just keep trying various IM apps until you find one that does not stay awake.
cmd512 said:
I do Crazy, 30 minutes, and Low level so that I can see all processes (including system level). I then run my phone as usual and add any/all system related processes to the ignore list.
Good luck, and hope it works for you as well.
Click to expand...
Click to collapse
It has worked for me mate, worked well I should say. You deserve a Thanks mate.
I set it on Aggressive mode, with Auto kill at an interval of 1 hour, and NO apps but only my Power Schedule app in Ignore list, and I kept the Network On (Normally I use Flight Mode at night time), and after 9½ hours the battery drained just 2%, from 90% to 88%. Usually on Flight Mode I used to have a 3-4% drain overnight, so it's a big improvement.
BUT there are still two small but solid Awake bar present there while the Screen was off! What could be the reason? Is it because ATK was running and caused the Awake bar by itself or other apps? Take a look at the pic.
I have another query,
If I don't add any system apps (those come by default) to the Ignore list will there be any problem?
Regards.
kreoXDA said:
Let me try to explain the situation.
If you have an IM client and you want it to be ready to accept messages from your buddies, it has to be in "listening" state to "hear" from your buddies. How that "listening" state is implemented by the developer defines how much batt power the application is eating.
Two opposite example:
1) Some stupid developer coded the IM client to always stay in foreground on your phone, actively pinging the servers on the internet , asking the servers if you have new messages. Your battery is wasted big time man.
2) A smart developer coded the IM client to use Google's C2DM interface (Cloud to Device Messaging framework). Such an app will stay dormant on the phone, and will be woken up by the android core processes whenever a new message arrives for you - Google servers will wake up the app on your phone. Such an app will not waste battery much.
There are a number of variations that go in between (1) and (2) above. So there is no clear-cut good or bad app. All depends on the implementation, and also on the way you configure your phone and the app on it.
Latest version of eBuddy was supposed to use C2DM too.
Ad the new Trillian is using C2DM. I never tried any of these though, can't vouch for any.
Just keep trying various IM apps until you find one that does not stay awake.
Click to expand...
Click to collapse
Thanks man.
I will keep trying some of them. Starting with the ones you said.
almorsol said:
Hi, I am using watchDog to try to see what processes start while the phone is in sleep mode. But I cannot find anything on WatchDog that tells me what is consumming battery.
I hope I make it clear.
Regards
Click to expand...
Click to collapse
I have recently removed watchdog and noticed that battery consumption rapidly reduced...
Gmail & K9mail both use wakelocks. I don't trust them even in manual check mode. Something much more light weight seems appropriate.
It's important to get this right since the main point of a Nook NST for me is saving battery and being able to pick it up and use it straightaway. If an app starts waking up and draining battery even a little then it's no longer going to last for a month.
Using a browser such as Opera can work but it's a little clunky and so is freezing and unfreezing apps even with a widget. Any recommendations for an email app?
Not sure about email apps so this doesn't answer the question you're actually asking, but may have a functionally similar outcome. Using a CPU scaling app with profiles and setting it so the range of frequencies the CPU can use when the screen is off has both the maximum and minimum values at the lowest possible helps a lot for me.
neoman4426 said:
Not sure about email apps so this doesn't answer the question you're actually asking, but may have a functionally similar outcome. Using a CPU scaling app with profiles and setting it so the range of frequencies the CPU can use when the screen is off has both the maximum and minimum values at the lowest possible helps a lot for me.
Click to expand...
Click to collapse
Thanks buddy but I find I get a month as it is just making sure that the phone.apk and related stiff that starts after rooting is removed. I don't think I need CPU scaling because that's already working for me. Main thing is to watch those wakelocks. There are tons of apps that cause them including skype, paypal, facebook, whatsapp. Only fix is to freeze them, avoid or get the progammers to do it properly and program thier app in 2 parts