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.
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.
Today I had been experimenting with my battery life again and stumbled across this.
If you download advance task manager from the market. *NOTE* It is a paid application or *NOTE* This is illegal but you can download an .apk but again it is illegal and I am not encouraging you do it. *NOTE* You can purchase it and return it within 24 hours with your money back.
Step 1- Get advance task manager.
Step 2- Go into your home system and go into your default home or your home system.
Step 3- Now choose a screen in the home. Eg: 1,2,3 etc...
Step 4- Keep your finger tap'ed on the empty screen or somewhere empty in the screen. You can also just press the menu button and tap *ADD*.
Step 5- Choose widgets and find advance task manager.
Step 6- Now when you tap the widget icon, it will terminate all your applications.
Step 7- It will then direct you to a choice for your home application/s.
Step 8- You can just press lock and not choose your home and it will stay draining very little battery.
*Note* I do not guarantee this to work but it worked for me since I had my phone on the lock where I had a choice of home screen since 3:00 PM and it is now 6:00 PM...
3 hours and still full battery.
I have also previously managed to keep the battery up for 3 days and in the 3 days I was left with 15 percent battery.
I will post images if you people are having trouble *JUST PM ME OR POST BELOW IF YOU WANT IMAGES*
Appreciate the tip but since the inception of the Android OS this was one of the first and biggest tips amongst all of the community. It's nothing new. The Android OS actually does a damn good job of killing apps by itself. Unused RAM is useless RAM. It's a *nix based system.
The only time where this is good is when you have a stray app that's using CPU when it opens in the background when it shouldn't. Especially when it's keeping things awake. I only advise that you use this before locking the phone intentionally, and when you'd like it to go into a deep sleep.
I use task killers only when I'm putting my phone away for a while. Works better than when I used task killers. I'm also mindful about the apps I install and I uninstall and reinstall when need be, format my phone occasionally (I am an extremely heavy user) and defrag my SD card because of the heavy usage.
bongd said:
Appreciate the tip but since the inception of the Android OS this was one of the first and biggest tips amongst all of the community. It's nothing new. The Android OS actually does a damn good job of killing apps by itself. Unused RAM is useless RAM. It's a *nix based system.
The only time where this is good is when you have a stray app that's using CPU when it opens in the background when it shouldn't. Especially when it's keeping things awake. I only advise that you use this before locking the phone intentionally, and when you'd like it to go into a deep sleep.
I use task killers only when I'm putting my phone away for a while. Works better than when I used task killers. I'm also mindful about the apps I install and I uninstall and reinstall when need be, format my phone occasionally (I am an extremely heavy user) and defrag my SD card because of the heavy usage.
Click to expand...
Click to collapse
I agree but this worked for me and I recommend trying this. Also I agree with everything you have said and sometimes when I am out somewhere I tend to keep the phone in a deep sleep but I do not want to miss any calls or texts happening to me so I do this.
Appreciate what you have told me as well.
Also what good does formating do? (NOT SAYING IN AN OFFENSIVE MANNER, I AM JUST CURIOUS)
zm4 said:
I agree but this worked for me and I recommend trying this. Also I agree with everything you have said and sometimes when I am out somewhere I tend to keep the phone in a deep sleep but I do not want to miss any calls or texts happening to me so I do this.
Appreciate what you have told me as well.
Also what good does formating do? (NOT SAYING IN AN OFFENSIVE MANNER, I AM JUST CURIOUS)
Click to expand...
Click to collapse
Bongd is absolutely correct in what he says, the whole android system is designed to manage apps automatically, therefore while an app may appear on the task manager, they do not necessarily waste battery as they are sitting "idle"- that also means that an app will load up quicker when you go to open it, rather than if you kill the task.
Also my other point, and this is the big one, killing tasks can not only corrupt an app from working correctly but also it can cause instability to your system in the long run (because you are also killing certain tasks which are system processes) thus you notice bugs ion your phone and required to flash firmware again.
I've used advanced task manager and task panel side by side quite religiously for a while, yes it is faster and battery life does SLIGHTLY improve but trust me your phone doesn't like it.
Sent from my X10i using XDA App
zm4 said:
I agree but this worked for me and I recommend trying this. Also I agree with everything you have said and sometimes when I am out somewhere I tend to keep the phone in a deep sleep but I do not want to miss any calls or texts happening to me so I do this.
Appreciate what you have told me as well.
Also what good does formating do? (NOT SAYING IN AN OFFENSIVE MANNER, I AM JUST CURIOUS)
Click to expand...
Click to collapse
Formatting is good because just like a computer, things can get f***ed up for no reason. You can have all the correct settings but things don't happen as anticipated. It happens with any complex electronic devices, so this is why I recommend it every few months but this varies depending on how intensely you use your phone.
I use mine like crazy and tweak the hell out of it. I do it about once a month, but then again I have cell phone OCD.
The task manager helps to close apps that constantly keep connecting to the Internet, it's not about freeing up RAM it's about using the Internet connection
Some "apps" are some bad hogs when it comes to the phones recourses
Some "apps" are quite some hogs when it comes to the phones recourses.
Internet connection, Syncing, Updating ads and so on.
Some of these "bad hogs" also keep running "at full speed" in the background.
They have no whatsoever routines to save energy/recourses once loaded (background or not).
Designers of these "bad apps" don't care about battery-life, or they simply have no whatsoever knowledge/experience about mobile devices and how an application should behave on a such device.
If one are the kind who downloads lots of "cool" applications from the market, a task-killer can help allot, depending on how many "recourse hog" application one have installed and loaded in the background.
SysGhost said:
Some "apps" are quite some hogs when it comes to the phones recourses.
Internet connection, Syncing, Updating ads and so on.
Some of these "bad hogs" also keep running "at full speed" in the background.
They have no whatsoever routines to save energy/recourses once loaded (background or not).
Click to expand...
Click to collapse
yeah but we don't have any app that tells us which app is using the battery and data connections right? sure the android OS tells us the battery usage, but data?
A app to stay away from is eBay it hogs cpu time and constantly refreshes in the background, my batt goes from 2days down to 8ish hours when the eBay app is installed
Sent from my X10a using XDA App
tookieboy said:
yeah but we don't have any app that tells us which app is using the battery and data connections right? sure the android OS tells us the battery usage, but data?
Click to expand...
Click to collapse
System Panel can do this
Taskkiller stuff is not welcomed by my X10. When I kill all the apps , sometimes my connection to my operator goes down. I don't know how many necessary process' this taskkiller stuff kills as well.. I avoid "kill all" , instead I kill the ones that I'm sure that they're using internet and cpu in vain. Wish all the mobile developers use the close() method , then we won't be facing that kind of problems..
Is it possible? Can it be done without having to learn how to install and use ADB? And is it true that it lengthens battery life for the nook??? Thanks in advance!
les02jen17 said:
Is it possible? Can it be done without having to learn how to install and use ADB? And is it true that it lengthens battery life for the nook??? Thanks in advance!
Click to expand...
Click to collapse
Uninstall with titanium telephony.apk and phone.apk, in that order. You will get FC and just reboot then and you will be okay. Does it save battery life? That is up to speculation and probably not. Root explored can be used also to do it. Just delete these two files.
Airplane Mode WiFi Tool - https://market.android.com/details?id=net.geekherd.airplanemode&feature=search_result
life64x said:
Uninstall with titanium telephony.apk and phone.apk, in that order. You will get FC and just reboot then and you will be okay. Does it save battery life? That is up to speculation and probably not. Root explored can be used also to do it. Just delete these two files.
Click to expand...
Click to collapse
This is the correct answer.
I can't believe no one is being the voice of reason here.
Don't bother! It doesn't do anything for you.
http://forum.xda-developers.com/showthread.php?t=899861&highlight=phone.apk
It makes no difference, placebo at most.
photoassign said:
This is the correct answer.
Click to expand...
Click to collapse
Many times in life there is more than one correct answer. This is one of those times. Please keep that in mind the next time you choose to provide input.
it does not do anything but to free up some internal memory and give you more to run other apps..removing non needed crap that runs does do something....Drm apk..cmstats...setup...and many more items that are loaded that are not needed gives a healthy dose of memory back and general CPU efficiency
Jiggity Janx said:
Many times in life there is more than one correct answer. This is one of those times. Please keep that in mind the next time you choose to provide input.
Click to expand...
Click to collapse
The correct answer for one person may not be correct for another...you were rather harsh on him...let me get this straight...I gotta turn on airplane mode every time I start my nook and turn it off versus just turning it on and playing with it? Does not seem very practical now....imh..but then I dont disagree with the idea...I mean why load a program when you don't really need it?
life64x said:
The correct answer for one person may not be correct for another...you were rather harsh on him...let me get this straight...I gotta turn on airplane mode every time I start my nook and turn it off versus just turning it on and playing with it? Does not seem very practical now....imh..but then I dont disagree with the idea...I mean why load a program when you don't really need it?
Click to expand...
Click to collapse
The app I posted it is something that can be turned on once and will set airplane mode for cell while allowing wifi and bluetooth to function as normal however you want them set, even on a reboot.
It has been proven that many times removing cell (or other main) features can affect the ability to use other applications. My solution was clean, simple, and would affect nothing negatively. BTW, I was using it to avoid the wifi dropping issues that some have seen periodically since CM was first put on the NC. So in my case, it has been providing more than one useful capability.
I feel that people should open up their mind and follow up on other ideas before narrowing their and others minds to only one solution....
photoassign said:
This is the correct answer.
Click to expand...
Click to collapse
The correct answer would be to learn ADB, install the drives and do it manually.
life64x said:
it does not do anything but to free up some internal memory and give you more to run other apps..removing non needed crap that runs does do something....Drm apk..cmstats...setup...and many more items that are loaded that are not needed gives a healthy dose of memory back and general CPU efficiency
Click to expand...
Click to collapse
I'd just like to ask folks not to remove CMStats. Its obviously your prerogative but it helps CM developers track usage. This isn't just for bragging rights. These numbers help us in talks with OEMs to quantify the importance of things like open bootloaders and such. We are starting to see OEMs cooperate with CM and I think tracking usage has helped.
CMStats is not invasive and doesn't hog memory or CPU cycles. It is open source so you can feel free to verify my claims.
I'm reasonably sure this isn't specific to the V20 but thought I'd start here.
I have a rooted H918. Some/most of the time when installing apps or updates, there is a long pause between the period of time that the download completes (reaches 100%) and when the app/update starts to install. I found a thread or two describing the same issue. The "solution" was to exit the Play Store application, close it, and then relaunch it. After relaunching, the app that was at 100% downloaded will then start to install. However, if there are several installs or updates queued, I have to do the same steps for each app. So, not much of a solution.
I've cleared the app cache, reverted to the base version of the Play Store and then updated to the latest version from APK Mirror. Same behavior continues. The strange thing is that it does not do this all of the time. Sometimes, things download and install right away.
Anyone else observe this behavior? Any suggestions of what to try?
Set your cpu governor to performance
---------- Post added at 04:47 AM ---------- Previous post was at 04:46 AM ----------
This is a performance issue, if your cpu is being used too much, it will have a delay
crimsonrommer said:
Set your cpu governor to performance
This is a performance issue, if your cpu is being used too much, it will have a delay
Click to expand...
Click to collapse
Is there a kernel editor you recommend?
i prefer kernel auditor, its much more simpler to use
SJMarty said:
I'm reasonably sure this isn't specific to the V20 but thought I'd start here.
I have a rooted H918. Some/most of the time when installing apps or updates, there is a long pause between the period of time that the download completes (reaches 100%) and when the app/update starts to install. I found a thread or two describing the same issue. The "solution" was to exit the Play Store application, close it, and then relaunch it. After relaunching, the app that was at 100% downloaded will then start to install. However, if there are several installs or updates queued, I have to do the same steps for each app. So, not much of a solution.
I've cleared the app cache, reverted to the base version of the Play Store and then updated to the latest version from APK Mirror. Same behavior continues. The strange thing is that it does not do this all of the time. Sometimes, things download and install right away.
Anyone else observe this behavior? Any suggestions of what to try?
Click to expand...
Click to collapse
Guys, you're like Don Quixote, fighting a windmills that do no harm. Just leave the Playmarket aside and it'll install apps.
You know that after a apk file is downloaded it begins to be compiled by ART/Dalvik, right? That causes the delay after apk is downloaded and begins to be installed. The process which does it is called dex2oat. When I install many apps that dex2oat runs high in battery statistics with 3-4% of battery. When apps are being compiled this process takes both much time AND battery. So, this cause a delay and you're fighting that what can't be fought. And if an app is huge like Chrome compiling takes much more time than if an app is tiny like some sort of Jota+ text editor hence different time between "Sometimes, things download and install right away"
Also, try to update apps when on charge since you loose 10%, 20% or more battery if install many apps in one try, hence you'll got "bad battery life"
Billy Madison said:
You know that after a apk file is downloaded it begins to be compiled by ART/Dalvik, right? That causes the delay after apk is downloaded and begins to be installed.
Click to expand...
Click to collapse
The delay that I am seeing is significant. If I just leave the phone alone, it can be as long as 10-15 minutes between the time that the download completes and the app starts to install.
Billy Madison said:
if an app is huge like Chrome compiling takes much more time than if an app is tiny like some sort of Jota+ text editor hence different time between "Sometimes, things download and install right away"
Click to expand...
Click to collapse
I should clarify that when I say there is a delay, there is a delay after every app install. For example, if I have five apps that need updates and I update all, there will be a long delay between each one of them completing the download and actually starting the install process. However, sometimes, I may have five apps that need updates and they will all install with no delays.
Billy Madison said:
Also, try to update apps when on charge since you loose 10%, 20% or more battery if install many apps in one try, hence you'll got "bad battery life"
Click to expand...
Click to collapse
I'm having no problems with battery life.
I went ahead and adjusted the CPU governor to "Performance" and noticed no difference in the behavior. I enabled the CPU monitoring in Developer Options and there is no spiking after the download is complete so I don't believe the compiling process is responsible for the delay.
What prompted me to post my question was that I have two V20s (mine and the wife's) and her phone is not doing this. Both are rooted and running the same ROM (10t).
I'm open to any other ideas...
SJMarty said:
What prompted me to post my question was that I have two V20s (mine and the wife's) and her phone is not doing this. Both are rooted and running the same ROM (10t).
I'm open to any other ideas...
Click to expand...
Click to collapse
Then I can only suggest you tweaked your phone somehow and those tweaks caused a delay. Of course 10-15 mins doesn't attend to compiling, I thought you meant like 15 sec a delay
Wipe to factory state your phone and see after that when and after what tweaks you'll get delays back