Related
Since no one replied to this message in the official CM 5.0 thread. I have decided to create a new thread and hope to find a solution to this problem.
My alarm clock would stop working randomly ever since I flashed to CM 5.0, from Beta 4 to 5..2, the problem persists. If i set an alarm that is about one hour from now, it would go off. But the real alarm I need which is supposed to go off at 8 am in the morning never goes off. Anyone had similar problems? I read Cyanogen's warning about the alarm clock problem. But seems he's just trying to remind you to reset your alarm after flashing to CM. Unluckily, I've reset my alarm numerous times and it never goes off in the morning.
Anyone can give me a hand? Thanks in advance! Overall, CM is a great ROM which gives me the option to use open vpn, which is vital for me since I'm living in China behind the GFW.
Are you by chance using any taskillers?
I do use a task-killer program. But I always keep the clock app on while i'm sleeping to try to make sure the alarm goes off on time. But it never does in the morning.
Don't use task killers on the N1, there really is no need.
cyanogen said:
Don't use task killers on the N1, there really is no need.
Click to expand...
Click to collapse
I wouldn't say that's accurate... The phone does slow down noticeably when you have 20-30+ things open
Sometimes a lot of them are running as well (using TasKiller, a lot of Yellow, including Camera, Gmail etc even when not in use and no emails being downloaded). This probably affects battery life as well.
Paul22000 said:
I wouldn't say that's accurate... The phone does slow down noticeably when you have 20-30+ things open
Sometimes a lot of them are running as well (using TasKiller, a lot of Yellow, including Camera, Gmail etc even when not in use and no emails being downloaded). This probably affects battery life as well.
Click to expand...
Click to collapse
Do you have any evidence to back this up? Yes this was a problem on older devices because many things would be fighting over the tiny amount of RAM.
You'll see lots of processes running but that's just the way Android works. Since it doesn't really benefit from simple caching like a normal linux system would, it just keeps everything running and kills unused stuff when memory is low. Most of the things you see running are either paused and using no CPU, or are services that would be periodically launched anyway.
http://developer.android.com/guide/topics/fundamentals.html#lcycles
Keeping these processes alive should actually be saving you battery rather than using it. It's more expensive to launch and restore the state of an application or service after being killed than it is to simply resume one that's been paused.
cyanogen said:
Do you have any evidence to back this up? Yes this was a problem on older devices because many things would be fighting over the tiny amount of RAM.
You'll see lots of processes running but that's just the way Android works. Since it doesn't really benefit from simple caching like a normal linux system would, it just keeps everything running and kills unused stuff when memory is low. Most of the things you see running are either paused and using no CPU, or are services that would be periodically launched anyway.
http://developer.android.com/guide/topics/fundamentals.html#lcycles
Click to expand...
Click to collapse
Yes. The phone gets slow when TasKiller shows 30 things in it. I click close all, and it's faster. Do you know my personal experiences more than I do?
Paul22000 said:
Yes. The phone gets slow when TasKiller shows 30 things in it. I click close all, and it's faster. Do you know my personal experiences more than I do?
Click to expand...
Click to collapse
I think there is likely one or two specific misbehaving applications that are giving you trouble, rather than the way the system works as a whole, thats all.
I think what Cyanogen is saying is that android does not handle running processes the way other os's do They have a lifecycle that is non-obvious to someone just looking at a process list. If you insist on killing tasks outside of the activity/service lifecycle they you _will_ get service failures (like the alarm clock) its up to you what you value more.
I have not installed any sort of task manager (outside what's in astro but I don't use it) and never see any noticeable slow down.
Anyway - back on topic.
Yes I have the same issue, never had it before.
Since flashine 5.0.2 my alarm doesn't work in the morning.
The linux kernel keeps a buffer cache of recently used files in RAM. So whenever an application wants to access something on the flash, instead of going to the flash file system, it can just get it from the file buffer cache in RAM, a significant speed increase.
If the RAM is currently being taken up by unused android apps, then that leaves less room for the buffer cache, so in theory, by killing off unused android apps more quickly, that will allow the linux kernel to allocate more space for the buffer cache and thus speeding up the system.
Am I way off here?
Dave
cyanogen said:
Do you have any evidence to back this up? Yes this was a problem on older devices because many things would be fighting over the tiny amount of RAM.
You'll see lots of processes running but that's just the way Android works. Since it doesn't really benefit from simple caching like a normal linux system would, it just keeps everything running and kills unused stuff when memory is low. Most of the things you see running are either paused and using no CPU, or are services that would be periodically launched anyway.
http://developer.android.com/guide/topics/fundamentals.html#lcycles
Keeping these processes alive should actually be saving you battery rather than using it. It's more expensive to launch and restore the state of an application or service after being killed than it is to simply resume one that's been paused.
Click to expand...
Click to collapse
I would have to agree with Cyanogen on this one. When I first got my N1, I looked towards task killers to help alleviate slowdown, but in the end, I think it's just the placebo effect in a way; you did something to try to solve the problem, and so therefore you perceive a difference.
In other words, task killers aren't needed on this beast of a phone. As for battery life (if that's an issue), look into SetCpu.
Thanks for the reply Cyanogen. I think not using task-killer, or at least not killing the clock app got my alarm working this morning. But I use task-killer not for the purpose of saving ram, but for using less data. Some programs such as facebook or a twitter client would try to connect to the internet every once in a while. I'm on a low data limit plan in China. So I don't want those programs to eat up all my data. When I'm on wifi at home, I don't worry about that. Thanks again.
Same problem. Don't use taskkillers, flashed last CM last night and didn't wake up on time this morning - alarm didn't work, thought I checked that clock icon was on place on notification bar
amwayorlando said:
But I use task-killer not for the purpose of saving ram, but for using less data. Some programs such as facebook or a twitter client would try to connect to the internet every once in a while. I'm on a low data limit plan in China. So I don't want those programs to eat up all my data.
Click to expand...
Click to collapse
Have you thought about using something like APNDroid or Toggle Data, to just switch off the cell data when you don't want to use it?
Or, Modify the behavior of the applications you don't want using data?
I have my facebook and twitter for example set to manual update only (for battery saving purposes) because there's nothing there that is critical important info, and I don't need to be notified.
Nice thread though, I'm pretty sure I try to keep people informed that task-killers aren't needed and cause issues, everywhere where it comes up. I find humor that people will still argue, even with a developer, this fact. I've had 150+ hours uptime with no slowdown (and 30 apps running) on the stock rom (without highmem support).
bofslime said:
Or, Modify the behavior of the applications you don't want using data?
I have my facebook and twitter for example set to manual update only (for battery saving purposes) because there's nothing there that is critical important info, and I don't need to be notified.
Nice thread though, I'm pretty sure I try to keep people informed that task-killers aren't needed and cause issues, everywhere where it comes up. I find humor that people will still argue, even with a developer, this fact. I've had 150+ hours uptime with no slowdown (and 30 apps running) on the stock rom (without highmem support).
Click to expand...
Click to collapse
Then please inform us of a thread that can verify what you all are saying. Not in an argumentative tone, my linpack score drastically improves after 16 hours of uptime, and a task-killer.
Rom:CM 5.0.2 -OC Kernel
wesbalmer said:
Then please inform us of a thread that can verify what you all are saying. Not in an argumentative tone, my linpack score drastically improves after 16 hours of uptime, and a task-killer.
Rom:CM 5.0.2 -OC Kernel
Click to expand...
Click to collapse
This has basically been discussed into the ground. In my eye's, its a fight vs what I like to call "Windows XP mentality", and that there was benefit on phones like the G1. With the copious amounts of memory on the N1 and droid, they cause way more harm, and immeasurable good (if any).
Summary thread: http://forum.xda-developers.com/showthread.php?t=627836
I've linked to quotes from others.
Threads/posts of interest: http://forum.xda-developers.com/showthread.php?p=5494890#post5494890
And: http://forum.xda-developers.com/showthread.php?p=5298630#post5298630
Well, this discussion is very interesting, but lets return to our problem with non-working alarm.
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.
FYI as a reference point, the screenshots below show CPU activity (a proxy for power consumption) of stock KA7 with stock KA7 Voodoo-injected kernel during an eight-hour sleep-mode test period, logged using SystemPanel. The screen shots also show apps and processes that were frozen with Titanium during this testing and that I normally keep frozen. (I unfreeze Market only when I need it.) Also note that, as a conservative user, I do not synchronize with "the cloud." You will likely get a very different result if you do.
Note the "cityscape" pattern of utilization that resulted in 3% of battery consumption over the eight hour measuring period. Also note that the only process consuming an appreciable (> 0.0%) amount of power was the "suspend" process. For those unfamiliar with these metrics, please see the following tutorial:
http://forum.xda-developers.com/showthread.php?t=823025&page=4
Prior to updating to the full KA7 to build, I was on JL5 PDA plus KA7 modem and stock KA7 Voodoo-injected kernel. Power consumption using that system was very poor. The "suspend" process was consuming an unusual amount of power. The graphs suggested that the suspend process was conflicting with other processes as it attempted to transition the CPU into sleep mode.
I hypothesize that, although workable and largely stable, intermixing components from diverse builds may not be a very good idea. Implementation of the "suspend" state is tricky business. Note that this may have implications for the credibility of custom ROMs released without appropriate sleep-mode power consumption testing...
KA7 "Battery Drain" (Power Consumption) Report (continued)
This screenshot below is simply the last (ninth) of the set of sceen shots associated with the previous post.
Nice, thanks for the smart reporting.
Vibrant, BionixV, KA7, Voodoo...
why is it that my system shows up at 0.9%, system process is 0.7%, android.process.acore 0.4%. Do i need to freeze other programs? So far i only have frozen the programs that you have frozen on the above images. Any other that i can/should freeze?
thank you
bionix v 1.3.1
Tiger blood kernal
KA7 modem
erikr189 said:
why is it that my system shows up at 0.9%, system process is 0.7%, android.process.acore 0.4%. Do i need to freeze other programs? So far i only have frozen the programs that you have frozen on the above images. Any other that i can/should freeze?
thank you
bionix v 1.3.1
Tiger blood kernal
KA7 modem
Click to expand...
Click to collapse
It is not quite that easy. I cannot tell you which apps/processes are causing you a problem because every system is different. You must use SystemPanel Pro (paid) and follow this process; there is no shortcut:
http://forum.xda-developers.com/showthread.php?t=823025&page=4
BruceElliott said:
It is not quite that easy. I cannot tell you which apps/processes are causing you a problem because every system is different. You must use SystemPanel Pro (paid) and follow this process; there is no shortcut:
http://forum.xda-developers.com/showthread.php?t=823025&page=4
Click to expand...
Click to collapse
Yeah i already read that. Seems i just have to take my time with it. How did you go about choosing what programs to freeze, and how long till you got it the way you have it posted here? thanks again.
erikr189 said:
Yeah i already read that. Seems i just have to take my time with it. How did you go about choosing what programs to freeze, and how long till you got it the way you have it posted here? thanks again.
Click to expand...
Click to collapse
You are losing me by talking in circles, Bro. You say that you already read the method for figuring out which programs to freeze (http://forum.xda-developers.com/showthread.php?t=823025&page=4) and then you are asking me how to go about figuring out which programs to freeze. This is the first sentence in the post:
"No, I do not know what other app(s) may be causing your particular version of this problem, nor does anyone else." The need to follow the method in the post to find out which programs to freeze is the whole point of the post for crissakes.
As to how long it takes to figure out your particular system, not sure. It took me many hours because I had to work out the method in the lengthy post from scratch. It should take you much less time if you simply follow the method in the post using SystemPanel. You figure out the problem apps/processes using SystemPanel and then confirm/apply the fix by freezing with Titanium.
If you get stuck somewhere in the method and have a specific question about that step, tell me where in the method you are stuck and describe what is going on at that step; and I will then try to help you.
BruceElliott said:
You are losing me by talking in circles, Bro. You say that you already read the method for figuring out which programs to freeze (http://forum.xda-developers.com/showthread.php?t=823025&page=4) and then you are asking me how to go about figuring out which programs to freeze. This is the first sentence in the post:
"No, I do not know what other app(s) may be causing your particular version of this problem, nor does anyone else." The need to follow the method in the post to find out which programs to freeze is the whole point of the post for crissakes.
As to how long it takes to figure out your particular system, not sure. It took me many hours because I had to work out the method in the lengthy post from scratch. It should take you much less time if you simply follow the method in the post using SystemPanel. You figure out the problem apps/processes using SystemPanel and then confirm/apply the fix by freezing with Titanium.
If you get stuck somewhere in the method and have a specific question about that step, tell me where in the method you are stuck and describe what is going on at that step; and I will then try to help you.
Click to expand...
Click to collapse
my bad bro
erikr189 said:
my bad bro
Click to expand...
Click to collapse
No problem.
First off, since I am apparently an "inexperienced user" I am not allowed to post in the development forum, not even as a response to an existing thread (which is where it would make sense).
So I'm posting it here instead, please feel free to move to somewhere more appropriate.
After flashing faux's kernel on my atrix (running the Alien ROM v2) I noticed that when listening to music it actually plays faster than it is supposed to. Not by a whole lot, at first I was questioning whether I was just imagining it but it does indeed change playback speed.
Now, I didn't have to actually change anything with setcpu for this to happen, just the running kernel with the default setting makes this happen. I'm guessing this could possibly happen because of the AVP overclock?
Is there some setting that can be changed to stop this from happening?
For now I flashed back to the stock kernel and music plays at normal speed.
martinisadork said:
First off, since I am apparently an "inexperienced user" I am not allowed to post in the development forum, not even as a response to an existing thread (which is where it would make sense).
So I'm posting it here instead, please feel free to move to somewhere more appropriate.
After flashing faux's kernel on my atrix (running the Alien ROM v2) I noticed that when listening to music it actually plays faster than it is supposed to. Not by a whole lot, at first I was questioning whether I was just imagining it but it does indeed change playback speed.
Now, I didn't have to actually change anything with setcpu for this to happen, just the running kernel with the default setting makes this happen. I'm guessing this could possibly happen because of the AVP overclock?
Is there some setting that can be changed to stop this from happening?
For now I flashed back to the stock kernel and music plays at normal speed.
Click to expand...
Click to collapse
Hi,
That's interesting.
I wouldn't think a setting would do that, more like surgery on how android gets it's timing information to use a RTC, if that is practical at all.
Cheers!
This has happened to me maybe two or three times now, but I want to just focus on this time it's happening right now:
I installed the Villain kernel on 3.2.1 stock rooted rom, overclocked to 1.504GHz. Initially, the scrolling in landscape was as smooth as butter, but over the past few days it's become slightly choppy, and it's really bothering me, because I know I might have done something to mess this up. My question is, how do I fix this and make it so it has unbelieveably smooth scrolling again (just like when you pull it out of the box)? I think it's one of any number of things, really. It could be that I'm using cachemate, system panel pro, that I've used autostarts to stop a ton of applications from running at start up.
I just removed all of my game icons from the 2nd page (I only have two pages) and the scrolling didn't speed up, so it's not that.
Is there a a system app that relates to the scrolling that I might have disabled because it had a name that maybe I thought I could disable in autostarts?
Thanks for any help!
Stopping apps from autostart does not guarantee a performance improvement. This is not Windows and unused RAM is lost RAM. You're using more CPU power to kill constantly autostarting apps and services thus you're draining your battery faster. If a program resides in memory it still doesn't mean it does something. As an example, there were ROMs for HD2 that were developed to load completely in its RAM for superfast performance and yet battery life was still excellent. There might be apps that behave intrusive but that's not the majority of the cases. Try to isolate them with a tool like SystemPannel but first read its description @ the Market. Additionally try freezing with Titanium backup some of the apps you're definitely not using. Hope this helps.
p. s. Try switching from interactive to ondemand governor.
Ok, thanks very much for the info! I was talking to someone else about this earlier today and the made the same point as you.