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 am using hastrain 7.7 on the phireMOD_SkinnyEVO_v1.6 build. I have been having issues with the build just hanging. I searched recently to see if there was a way to find out what was causing the phone to just freeze. I found an app called OSmonitor that lets you see into what processes are taking up most of your cpu. It is supposed to let you kill the greedy ones.
To make a long story short I found out that smd_tty is taking up lite 85-90% of the cpu on top of the ohter standard processes. This is BEFORE I can even run an app or connect to the internet. its killing my battery and making it virtually impossible to run any other programs. To boot, OSmonitor does not allow me to kill it so I have to start the phone up all over again.
Does anyone know how to get around this? is there a different kernel, a script I can insert or something? If I cold just kill it and have it restart properly I would settle for that but i can't at the moment. I really like the why i have my phone set up but this is getting tiring. Thank you in advance.
LeTama is looking in to it, but there is no fix, other than not using data, yet.
so this is primarily a wrapper issue? i am asking because i am having a high cpu drain/system lock up even if i am not using data. for example, flipping through larhe pic galleries, using an app installer (which populates the apps and takes time to do so) etc... I did not know these processes were dependent on the wrapper. thanks in advance.
I have the exact same problem with all new roms I have tried. The only relatively new rom I found to not suffer from this is Core Droid 0.7.
I tried 0.8 but it had that problem so sticking with 0.7 for now. looks like between 0.7 and 0.8 Core Droid moved from letama's 0.2 to 0.4, so this might be the reason. Would be interesting to try Core Droid 0.8 with letama's 0.2, but I'm not sure how to do that
Anyways, you may want to try Core Droid 0.7. Works really great for me.
I have this problem too, when i'm using launcher pro and default launcher, when i turn back to sence it seems better
I am using an hd2, and i have noticed something that may be causing a lot of battery drain, that is consistent among every build that I have used. When I use setcpu, and give it root access, and whether i select auto detect or manually put in nexus one/snap dragon, it does not listen to the cpu cap that i put. i will exit the app, and go back to it, and the cpu clock speed with almost always exceed the cpu cap that i set, and many times, it will be running at the full 998 mhz. why is this, and how can i fix it?
I uninstalled SetCPU the other day as a little experiment. It makes f-all difference to me. In fact it makes things worse.
no longer needed with the latest kernels
metaltorizo said:
I am using an hd2, and i have noticed something that may be causing a lot of battery drain, that is consistent among every build that I have used. When I use setcpu, and give it root access, and whether i select auto detect or manually put in nexus one/snap dragon, it does not listen to the cpu cap that i put. i will exit the app, and go back to it, and the cpu clock speed with almost always exceed the cpu cap that i set, and many times, it will be running at the full 998 mhz. why is this, and how can i fix it?
Click to expand...
Click to collapse
This problem seems to relate to a kernel feature called perflock .. disabling this in-kernel allows the cpu cap in setcpu to be adhered to .. Unfortunately this is done at compile time and has no userland interface to use. I dont think its relating to all the battery drain you see but for sure if you limit cpu speeds with profiles like screen off it will have an effect.
try updateing super user libraries.
BurekUSvemiru said:
try updateing super user libraries.
Click to expand...
Click to collapse
Whats that then ?
how would i go about updating the su libraries? does anybody have an actual fix to this, because i would think my battery would be a lot better if the set cpu app was actaully working. and no, the latest kernels dont seem to be doing their job, because they all burn through juice like theres no tomorrow.
u have 2.04 installed ? it fc'd for me , now im using 2.02 no problems , try that
metaltorizo said:
how would i go about updating the su libraries? does anybody have an actual fix to this, because i would think my battery would be a lot better if the set cpu app was actaully working. and no, the latest kernels dont seem to be doing their job, because they all burn through juice like theres no tomorrow.
Click to expand...
Click to collapse
You don't update the su libraries .. su is either a static file or a link to busybox .. i cba looking right now .. probably a binary compiled statically ..
To have your issue resolved have a word with your friendly neighborhood kernel builder and ask him to disable perflock .. Its not needed for normal operation.
I'm having the same problem. Does anyone know how to get setcpu to work?! I have an HD2 running darkstone Froyo.
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