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).
Related
hi all,
i m new user for Nexus one, i wonder what is the best task apps to auto kill when the phone in sleep mode in order to save battery. My phone havent ROOT yet, shall i do it? After i have update the Android 2.1 i found it very good compare with iphone.
thank you very much
Killing tasks won't help to save battery... don't buy the hype. Android will manage your apps for you.
No killing tasks can help your battery. There are many apps on the market that are poorly written and drain battery.
McFroger3 said:
No killing tasks can help your battery. There are many apps on the market that are poorly written and drain battery.
Click to expand...
Click to collapse
Well that makes sense... but I don't run any poorly written apps. And neither should you.
If you absolutely have to have a task killer, just download Astro File Manager. You'll need a file manager on this phone anyway, and Astro has a built in configurable task killer and can also back up apps to SD.
uansari1 said:
Well that makes sense... but I don't run any poorly written apps. And neither should you.
If you absolutely have to have a task killer, just download Astro File Manager. You'll need a file manager on this phone anyway, and Astro has a built in configurable task killer and can also back up apps to SD.
Click to expand...
Click to collapse
I try not to. But sometimes I get curious and download some random apps haha.
I use Advance Task Manager since I bought it when I had a Cliq.
It works good when I need to kill something to restart it or if I need to do a batch uninstall.
Astro is amazing and no one should have an android phone without it.
Thks all,
If so, i shall just leave as it is and not install any of those task killer or auto task etc......
But anyway to min the battery drain since there are so much apps running on RAM when the phone is in sleep mode. My battery can only last for 8 hrs from 9am till 5pm (i am so distracted, i do turn on my BT and talk on phone for at least 100mins-150mins a day.)
Thank you
chocodip said:
Thks all,
If so, i shall just leave as it is and not install any of those task killer or auto task etc......
But anyway to min the battery drain since there are so much apps running on RAM when the phone is in sleep mode. My battery can only last for 8 hrs from 9am till 5pm (i am so distracted, i do turn on my BT and talk on phone for at least 100mins-150mins a day.)
Thank you
Click to expand...
Click to collapse
Keep the screen brightness as low as you can. Also having a lot of widgets can contribute to battery drain.
uansari1 said:
Killing tasks won't help to save battery... don't buy the hype. Android will manage your apps for you.
Click to expand...
Click to collapse
while this is true, I notice that android's threshold for closing programs is lower than I prefer. It seems to start closing programs at around 25 mb free (on stock kernel and rom) as reported by ES strong's task manager. At this level there is a noticeable amount of sluggishness on my N1. Of course this only lasts for perhaps 10 seconds or so as I am switching apps or whatever until android closes the processes to free up some ram.
I've read comments like yours many times, and I go back to not using one for a while thinking I must just be paranoid. Each time I return to the task manager because I get ticked about sluggishness.
If you manage your ignore list carefully to avoid closing stuff you actually want running in the background you lose nothing. The phone is fast enough that it loads apps quickly even if they're not sitting in the ram, so I prefer to hit the autokill widget once in a while or after using something like the youtube app or other resource hogging apps that I don't use on a regular basis.
I haven't noticed a difference in battery life, but the task manager improves my experience with the phone. It seems that as long as the free memory stays around 40+ I don't see the sluggishness.
Which task killer you use?
rossiscatch said:
while this is true, I notice that android's threshold for closing programs is lower than I prefer. It seems to start closing programs at around 25 mb free (on stock kernel and rom) as reported by ES strong's task manager. At this level there is a noticeable amount of sluggishness on my N1. Of course this only lasts for perhaps 10 seconds or so as I am switching apps or whatever until android closes the processes to free up some ram.
I've read comments like yours many times, and I go back to not using one for a while thinking I must just be paranoid. Each time I return to the task manager because I get ticked about sluggishness.
If you manage your ignore list carefully to avoid closing stuff you actually want running in the background you lose nothing. The phone is fast enough that it loads apps quickly even if they're not sitting in the ram, so I prefer to hit the autokill widget once in a while or after using something like the youtube app or other resource hogging apps that I don't use on a regular basis.
I haven't noticed a difference in battery life, but the task manager improves my experience with the phone. It seems that as long as the free memory stays around 40+ I don't see the sluggishness.
Click to expand...
Click to collapse
My screen always in lowest light mode......i will try to install the advance task....hope it deos help abit.
McFroger3 said:
Keep the screen brightness as low as you can. Also having a lot of widgets can contribute to battery drain.
Click to expand...
Click to collapse
chocodip said:
My screen always in lowest light mode......i will try to install the advance task....hope it deos help abit.
Click to expand...
Click to collapse
Advance task manager also lets you set a timer for auto closing all open apps except for the ones you have on your exception list.
chocodip said:
hi all,
i m new user for Nexus one, i wonder what is the best task apps to auto kill when the phone in sleep mode in order to save battery. My phone havent ROOT yet, shall i do it? After i have update the Android 2.1 i found it very good compare with iphone.
thank you very much
Click to expand...
Click to collapse
Try Juice Defender,is free on the market and everytime you turn the screen to sleep it kills the background data to save battery and @ wake-up its normal again.Read the reviews.
rossiscatch said:
while this is true, I notice that android's threshold for closing programs is lower than I prefer. It seems to start closing programs at around 25 mb free (on stock kernel and rom) as reported by ES strong's task manager. At this level there is a noticeable amount of sluggishness on my N1. Of course this only lasts for perhaps 10 seconds or so as I am switching apps or whatever until android closes the processes to free up some ram.
I've read comments like yours many times, and I go back to not using one for a while thinking I must just be paranoid. Each time I return to the task manager because I get ticked about sluggishness.
If you manage your ignore list carefully to avoid closing stuff you actually want running in the background you lose nothing. The phone is fast enough that it loads apps quickly even if they're not sitting in the ram, so I prefer to hit the autokill widget once in a while or after using something like the youtube app or other resource hogging apps that I don't use on a regular basis.
I haven't noticed a difference in battery life, but the task manager improves my experience with the phone. It seems that as long as the free memory stays around 40+ I don't see the sluggishness.
Click to expand...
Click to collapse
I've got over 400 hours of uptime without closing ANY apps with a task killer, and haven't had ANY sluggishness. So if you're really noticing your phone slowing down (and be honest), then I'd exchange it. Frankly, I think a lot of people just "think" their phone is slowing down...
Cyanogen says don't use a Task killer!
Paul22000 said:
Cyanogen says don't use a Task killer!
Click to expand...
Click to collapse
So if cyanogen says jump of a bridge you would? lol
Just messing with you.
I ve installed the Juicedefender and advance task manger......hope meanwhile there will be sthg better. Battery usage is killing me....
uansari1 said:
I've got over 400 hours of uptime without closing ANY apps with a task killer, and haven't had ANY sluggishness. So if you're really noticing your phone slowing down (and be honest), then I'd exchange it. Frankly, I think a lot of people just "think" their phone is slowing down...
Click to expand...
Click to collapse
Yeah, I'm sure you're right.. it's all in my head.
Couple of things OP:
1. Bluetooth is a battery hog!
2. How frequent do you have email update, weather update, et al set to?
3. Did you properly calibrate your battery meter when you got your N1? (Two ways to do it, 1) follow the in box guide and charge the phone before using or 2) run down the battery until the phone shuts itself off, pull battery out, put it back in. Now, without turning it back on, put it on the charger and leave it on for a couple hours past the green light coming on, take off charge, finally turn back on)
4. Do you have WiFi running? GPS? Streaming anything?
Have you downloaded any apps from the market just on a quim? There are some pretty bad apps that will never close until you uninstall and do a soft reset, and sometimes uninstall again.
Killing apps is actually going to hurt your battery. It takes more juice to power up the CPU to open an app then it does to hold it in the RAM, unless it is a crap written app that keeps running, and running, and running... but you shouldn't be using those apps anyways.
rossiscatch said:
Yeah, I'm sure you're right.. it's all in my head.
Click to expand...
Click to collapse
It most likely is... even when apps sit idle in RAM, the CPU usage for them is 0% in almost every case. Like I said... I don't have those issues at all, so it's either in your head or you have a dud.
uansari1 said:
It most likely is... even when apps sit idle in RAM, the CPU usage for them is 0% in almost every case. Like I said... I don't have those issues at all, so it's either in your head or you have a dud.
Click to expand...
Click to collapse
I don't think it's a problem with my phone. If you don't notice then good for you. I notice it and it bothers me. Your finger pointing is neither helpful or needed.
Those of you running auto killer in your roms, did you use the aggressive settings or custom?
I'm just curious to see if anyone increased the auto kill.
I use either the aggressive or custom depending on the Rom honestly. DC ROMS= Aggressive. FRESH ROMS= strict. and all others = custom
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
I have the damagecontrol rom and I dont know if it came with auto killer or what...I restored my titanium backup and all i know is i dont have it now...is there an apk floating around for it?
Try the market
I thought it was a custom xda application. I didn't see it in
the market.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
I've been using Aggressive on Fresh 2.0d and it's been running great.
I tried Moderate for a while at first, but Homerun Battle 3D wouldn't even startup consistently. Once I changed it to Aggressive it has been working great.
Another quick note. I know Autokiller is supposed to reapply the settings on boot, but I'm not sure mine is. I haven't rebooted for a day or so, but the last couple times I rebooted I couldn't get Homerun Battle to run. Then I went into Autokiller and applied Aggressive again and it would start. Anybody else having similar experiences?
I used either the aggressive or strick on Fresh 2.0d. So far everything is running the smooth and fast. This the way HTC hero should have come out of the box.
What does each preset do? Is this for speed or battery life or both?
flammenwurfer said:
I've been using Aggressive on Fresh 2.0d and it's been running great.
I tried Moderate for a while at first, but Homerun Battle 3D wouldn't even startup consistently. Once I changed it to Aggressive it has been working great.
Another quick note. I know Autokiller is supposed to reapply the settings on boot, but I'm not sure mine is. I haven't rebooted for a day or so, but the last couple times I rebooted I couldn't get Homerun Battle to run. Then I went into Autokiller and applied Aggressive again and it would start. Anybody else having similar experiences?
Click to expand...
Click to collapse
Damn. I wish Homerun Battle 3D would run great for me. Problem is I get crummy service at work and with it going in and out of 1x and EVDO, causes the game to lag.
I have noticed sometimes on first opening HRB, it force closes but it always opens the second time.
james33440 said:
Those of you running auto killer in your roms, did you use the aggressive settings or custom?
I'm just curious to see if anyone increased the auto kill.
Click to expand...
Click to collapse
i'm running aosp 1.6 from gbhil and i used custom autokiller settings.
the way i see it they made these phones with all this ram may as well use it, what good is it to have all this free ram?
1536,3072,4096 (all default) then hidden app is 7680. content provider is 8960 and empty app is 10240. i normally run around 40-45 free ram thats about where i like it. the phone still runs fine all the way down to 20mb free but any less than that it starts going downhill.
so, im MB my settings are 30 then 35 then 40. runs great!
yeah, I get some lag now and then if I don't have great service. Playing offline seems to work fine though. I think it's just the online play that it effects. A co-worker has a Droid and his lags when playing online as well if he's in a spot without good service.
flammenwurfer said:
yeah, I get some lag now and then if I don't have great service. Playing offline seems to work fine though. I think it's just the online play that it effects. A co-worker has a Droid and his lags when playing online as well if he's in a spot without good service.
Click to expand...
Click to collapse
Well, mine actually lags on offline play too. As long as the phone isnt switching back and forth, it runs smooth.
How can you remove this autokiller crap, I have tried freshkitchen, uninstaller, and from settings-applications menu, all to no avail
vedwed said:
How can you remove this autokiller crap, I have tried freshkitchen, uninstaller, and from settings-applications menu, all to no avail
Click to expand...
Click to collapse
Using command prompt (adb)
adb shell
# rm Autokiller.apk
troyboytn said:
Using command prompt (adb)
adb shell
# rm Autokiller.apk
Click to expand...
Click to collapse
Ohh thanks much appreciated.
I did not try that way, I figured if it couldn't be done in freshkitchen then it was just built into the rom. Thanks much again
Just stop using task killers entirely. This isn't Windows Mobile guys. You're getting all OCD in here about the placebo effect.
Sawawa said:
Just stop using task killers entirely. This isn't Windows Mobile guys. You're getting all OCD in here about the placebo effect.
Click to expand...
Click to collapse
Autokiller does have a built in task killer but its real use is to tweak memory settings at boot and then shuts itself down (so Android can take care of the rest). So, in reality it is not really a task killer per say.
Fair enough, but it's still entirely pointless. I trust the device manufacturer and Android far more than I ever would the random numbers that I might otherwise delude myself into believing were somehow better.
Just let Android do its thing all of the time. It doesn't need any additional help (particularly with the process management in 2.1). Stop including this garbage in ROMs.
Sawawa said:
Fair enough, but it's still entirely pointless. I trust the device manufacturer and Android far more than I ever would the random numbers that I might otherwise delude myself into believing were somehow better.
Just let Android do its thing all of the time. It doesn't need any additional help (particularly with the process management in 2.1). Stop including this garbage in ROMs.
Click to expand...
Click to collapse
It actually very useful for making roms run smoother. By default the memory numbers are very low, which lets a TON of apps run at the same time. The higher the memory numbers the more it ends apps that you werent even using. It gives what you are currently running or recently ran more priority. Even if you dont use AutoKiller, which is just an app to adjust the memory setting, every rom comes with an edited memory setting other then htc's default. Its most commonly known as gumbo's memory settings.
Also in AutoKiller you can adjust the settings to default, or just really low like htc would have them set.
Its really not a bad thing to include in roms because most people want there rom to be smooth and as close to lag free as they can get. AutoKiller helps achieve that by ending stuff you dont currently have up making the phone run faster. Thats if you have a decently set setting. I run mine on optimum, and it doenst close unnecessary things like if im on the web it stays running.
I can understand an app like Task Killer which just terminates the apps. AutoKiller is just setting the memory setting of your phone, which end apps the same way as if the phone were running normally. Just if the numbers are higher the more apps it will end quicker freeing up more space.
Also you really trust htc and sprint?? haha good luck with that
Jus10o said:
It actually very useful for making roms run smoother. By default the memory numbers are very low, which lets a TON of apps run at the same time. The higher the memory numbers the more it ends apps that you werent even using. It gives what you are currently running or recently ran more priority. Even if you dont use AutoKiller, which is just an app to adjust the memory setting, every rom comes with an edited memory setting other then htc's default. Its most commonly known as gumbo's memory settings.
Also in AutoKiller you can adjust the settings to default, or just really low like htc would have them set.
Its really not a bad thing to include in roms because most people want there rom to be smooth and as close to lag free as they can get. AutoKiller helps achieve that by ending stuff you dont currently have up making the phone run faster. Thats if you have a decently set setting. I run mine on optimum, and it doenst close unnecessary things like if im on the web it stays running.
I can understand an app like Task Killer which just terminates the apps. AutoKiller is just setting the memory setting of your phone, which end apps the same way as if the phone were running normally. Just if the numbers are higher the more apps it will end quicker freeing up more space.
Also you really trust htc and sprint?? haha good luck with that
Click to expand...
Click to collapse
Either way it should be a choice made by the USER not someone who decides what I need or do not need on my phone. What I choose to have running or not running, there is no need for this garbage for the average joe who just wants something that does not look and feel like Sprint garbage. If its such a great and useful thing put it on the market and let users have a choice.
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.
As android builds are getting more and more closer to being daily builds, one of the standing issues that remains is battery life.
This thread is where posts concerning How to Save battery should go. NOT Questions, but suggestions. If your suggestion is one to look into, it will be added to the OP.
UPDATE: You can now use ALL GOVERNORS For the CPU! (Read more to find out how) --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
SetCPU
SetCPU, is an app more commonly used for over/under clocking devices.
This short tutorial will show you how you get the app,
get it running, and of course save battery!
*YOU NEED A ROOTFS.IMG THAT GRANTS YOU ROOT ACCESS!*
1. Get SetCPU
A. Download it from *HERE*. (The only XDA thread I could find for it)
OR
B. Support this great application and get it from the Android market by searching for SetCPU.
-----------------------------------------------------------------------------
2. Getting the App working
1. Once you have the application installed, launch it from your drawer and either grant it Root Permissions or it may auto-configure.
2. Hit Auto Detect Speeds.
3. It should show you the speeds your device it currently running at, now move over to [Profiles] and click Enable and if you want click on Notification.
-----------------------------------------------------------------------------
3. Make your profiles
1. Sleep Profile - 384 Max/245 Min- Interactive setting
(It may seem high, but this keeps it so that your device wakes up quickly)
2. Battery < 30
Max 614/460 Min- Interactive/Conservative Setting
*Try out the SetCPU Widget!*
If you have any personal settings that you think might be better than these please do post!
-----------------------------------------------------------------------------
UPDATE 9/15 ALL CPU Governors!
To use the modules use this kernel built from the GIT, and hit auto detect speeds on SetCPU again. Under the main tab choose Your preferred setting..
You can find what all the the kernels differ in in the further pages of this thread, I will update OP later.
-----------------------------------------------------------------------------
Advanced Tab
20000 Sampling Rate
30-50 Up Threshold (THIS IS THE KEY: This means when your CPU load hits 30%, it will scale up the mhz. If the phone still responds too slow for your taste, set this lower)
http://forum.xda-developers.com/showthread.php?t=777921
Check Set on Boot (And Apply)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Turning off Background Services and Adjusting Brightness
Things like Bluetooth, WiFi, Sync, GPS, and excessive brightness can really kill your battery.
A quick way to manage these settings is to hold down to add a widget on your home screen and choose [Power Widget].
This stock widget allows you to quickly see the service's your using, and the farthest one to your right allows you to switch between four brightness settings.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Using that new kernel link provided, you'll get a nice boost in standby time too! Enjoy!
Additional battery saving tips:
* Don't use a live wallpapers
* Turn off 3G connectivity (Eclair-based ROMS need apps like APNDroid to do so)
* Turn off Background-enabled data transfers in the Sync page.
the app screebl is a battery saver for whenever you have your screen on.
MOD EDIT:
Screebl Pro is a PAID FOR APP..
Link deleted and warning given please do not post warez in the future.
Mark.
Is that a Paid application from the Market? If so it is warez. (Big No-No)
Shatterv2 said:
Is that a Paid application from the Market? If so it is warez. (Big No-No)
Click to expand...
Click to collapse
no it's donation-ware. You can find SetCPU in the G1 device section of the XDA forums for free...
http://forum.xda-developers.com/showthread.php?t=505419
Can we have on our hd2 a folder with Android Sdk ? Like in a rooted one ?
aussiebum said:
no it's donation-ware. You can find SetCPU in the G1 device section of the XDA forums for free...
http://forum.xda-developers.com/showthread.php?t=505419
Click to expand...
Click to collapse
Yes that was already stated in the OP
Shatterv2 said:
*YOU NEED A ROOTFS.IMG THAT GRANTS YOU ROOT ACCESS!*
Click to expand...
Click to collapse
Can you post one?
Ultimaex said:
Can you post one?
Click to expand...
Click to collapse
read here: http://forum.xda-developers.com/showpost.php?p=7088391&postcount=4
Thanks for the tips!
Ultimaex said:
Can you post one?
Click to expand...
Click to collapse
Rooted RootFS.img files by michyprima can be found *HERE* in the Installation Instructions section.
Mark.
SetCPU forcecloses on me with dan's froyo without sense. Anybody get this combo to work for them? Also, I did replace the rootfs file.
Strange, try the new froyo build by Darkstone.
reocej said:
SetCPU forcecloses on me with dan's froyo without sense. Anybody get this combo to work for them? Also, I did replace the rootfs file.
Click to expand...
Click to collapse
Yeah, I'm using SetCPU 2.01 with Dan's v1 vanilla froyo fine. When set to use "ondemand" CPU Governor and Autodetect speeds, getting much better battery life - it's only dropping ~1% every hour now EDIT: when idle, of course
aussiebum said:
Yeah, I'm using SetCPU 2.01 with Dan's v1 vanilla froyo fine. When set to use "ondemand" CPU Governor and Autodetect speeds, getting much better battery life - it's only dropping ~1% every hour now EDIT: when idle, of course
Click to expand...
Click to collapse
Happy to help!
Next thing (when I get around to it) is probably to try out the Conservative CPU Governor module... that will correctly scale CPU power according to load (ie. 245mhz => 384, etc) instead of like On Demand, where it jumps from 245mhz => 998mhz => lower....
ATK
My favorite Ap Right now: Advanced Task Killer - you can find it on market for free. With this you can kill tasks who run in backround etc.
RuffRap said:
My favorite Ap Right now: Advanced Task Killer - you can find it on market for free. With this you can kill tasks who run in backround etc.
Click to expand...
Click to collapse
Use Taskiller. Red Icon in the market. Free App is the exact same as the paid one. Kills tasks as well but detects tasks that ATK cant. Includes features like End apps once screen turns off and kill all apps 10sec's after boot. Great App IMO.
I've found out that JuiceDefender does a good job as well. If you buy the extension (UltraDefender?) it also has a CPU governer module which regulates your CPU speed based on usage.
maseo said:
I've found out that JuiceDefender does a good job as well. If you buy the extension (UltraDefender?) it also has a CPU governer module which regulates your CPU speed based on usage.
Click to expand...
Click to collapse
No need to pay - as I mentioned before, the "conservative" cpu governor module that is freely available (do a search!) will do exactly what you mentioned when used with SetCPU.
seems it will automatically kill my Sense UI and i need time to reload it again after quitting the app, may i ask if any one know how to prevent this? i have set the lower oom but it say this setting cant last long..
BTW it kills my alarm also..
pls suggest some task killing software in which u think is gd..thanksss!
wa_xda said:
seems it will automatically kill my Sense UI and i need time to reload it again after quitting the app, may i ask if any one know how to prevent this? i have set the lower oom but it say this setting cant last long..
BTW it kills my alarm also..
pls suggest some task killing software in which u think is gd..thanksss!
Click to expand...
Click to collapse
Is there a reason you need a task killer?
Most of these are unnecessary. My understanding is that Linux uses memory different than windows and it is not necessary to kill background processes. Those apps are not using system resources, they load but generally do not use additional memory or cpu until they are needed to do something. Every time your phone has to process to kill stuff off you are using the processor, battery and resources and often android will releoad them anyways.
From my experience, I get more speed and bang for the buck by just turning off window animations.
But I could be wrong, lol, your mileage may vary..................
cyberstoic said:
Is there a reason you need a task killer?
Most of these are unnecessary. My understanding is that Linux uses memory different than windows and it is not necessary to kill background processes. Those apps are not using system resources, they load but generally do not use additional memory or cpu until they are needed to do something. Every time your phone has to process to kill stuff off you are using the processor, battery and resources and often android will releoad them anyways.
From my experience, I get more speed and bang for the buck by just turning off window animations.
But I could be wrong, lol, your mileage may vary..................
Click to expand...
Click to collapse
The issue is that some apps, even when not actively being used by the user, will continue to utilize system resources. However, there are several arguments all over these forums that task killer's typically do more harm than good. I still use "Advanced Task Killer" though.
you might like to read this
http://forum.xda-developers.com/showthread.php?t=622666
wingsaba said:
you might like to read this
http://forum.xda-developers.com/showthread.php?t=622666
Click to expand...
Click to collapse
Thanks for the link; that was very useful info, reading it now.
DonJuan692006 said:
The issue is that some apps, even when not actively being used by the user, will continue to utilize system resources. However, there are several arguments all over these forums that task killer's typically do more harm than good. I still use "Advanced Task Killer" though.
Click to expand...
Click to collapse
I used to use advanced task killer for a awhile. Don't know if it was my obsessive nature checking the thing or just the program, but battery life was a bit poor, lol. In the end I just gave up and stopped using it.
I don't like task killers.
Its saves memory but increases CPU usage.
after making these changes my phone is flying. good find!
dedraks said:
I don't like task killers.
Its saves memory but increases CPU usage.
Click to expand...
Click to collapse
yes, indeed...
alarm fix
http://forum.xda-developers.com/showthread.php?p=12043283#post12043283
http://www.dustypixels.com/blog/2010/02/01/android-app-minfreemanager-v1-5/