First off, I am rooted with the "unrevoked" method. I have notice that my alarm clock only goes off sometimes. I cant figure out what the pattern is. This is my 4th android phone, so I know how to navigate and set things up. I have it set for Mon-Fri @ 6:05am w/ a stock alarm tone (light).
I am back to using my regular house alarm clock with the blaring radio. Anybody else have this problem?
Do you use a task killer? If so, you should set it to ignore the clock. It will kill the clock and prevent it from going off.
Better yet, find a way to do things without a task killer, but that's my two cents. You can use a task killer if you so desire.
Thanks, I actually was using task killer. Why do you say not to use it?
I don't use an automatic task killer simply because it's not needed, at least not for me. I have plenty of RAM available at all times and this way I don't risk killing off something important. The only time you should need to kill a process is if it is misbehaving by using lots of data or CPU time or not properly going to sleep. Otherwise your phone will generally be faster with a lot of ram in "use" because it's being cached and can be used by other programs. For more information look up how Linux handles RAM.
Is there an app or something that actually tells me what is running I. The background? I'm currently using automatic task killer but I feel that it only kills somethings and not all.
Sent from my PC36100 using XDA App
try system panel. or taskiller
Why do you want to kill the apps? Android will stop them for you if it needs the memory. Hitting the back button at the bottom of your phone should exit you out of the app you're currently in.
What do you have running in the background that's killing your phone so bad?
Sent from my PC36100 using XDA App
Autostarts is a good paid app. Prevents certain apps from ever starting automatically.
Sent from my FROYO'D EVO using xda app
Love autostart.. cheap and on cm6 with stock root I hit 1903 on quad. Also I removed alot of stuff. Almost barebones then installed my 28 apps. Still get average 1800s. +1 for autostart.
Sent from my PC36100 using XDA App
atypical1 said:
Why do you want to kill the apps? Android will stop them for you if it needs the memory. Hitting the back button at the bottom of your phone should exit you out of the app you're currently in.
What do you have running in the background that's killing your phone so bad?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
You can back out to exit but doesn't shut down the app when you are done with it. Stays in the background. Developers need to start putting close or exit on apps to close and shut down the app instead of leaving it in background. There is 3 parts.. background..foreground.. and cached..
Sent from my PC36100 using XDA App
atypical1 said:
Why do you want to kill the apps? Android will stop them for you if it needs the memory. Hitting the back button at the bottom of your phone should exit you out of the app you're currently in.
What do you have running in the background that's killing your phone so bad?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The back button closing apps is a large myth for most apps. Some are coded that way but not all. As for the other post about AutoStarts, it is a great app for root users. Just be careful. However, 2.2 is great by itself about managing apps and resources on its own without a 3rd party task killer. I use AutoKiller to tweak Android's own task manager to kill off items sooner. Just because you see an app running does not mean it is using battery or hogging resources. Android is not a Windows device.
Sent from my iPhone with the bigger Gee Bees.
Well the reason I'm asking is because, I am rooted with 2.2 But I still get horrible battery consumption. I thought it might have been all the background apps still running or on standby. I used taskkiller myself but i really don't see a difference.
Sent from my PC36100 using XDA App
Good info on the back button. I always thought that worked for some applications. I don't see how force closing an application can be good for your phone though anymore than force closing a program is great for your computer. But I'm not totally familar with the OS on our phones.
But my understanding about the OS is that it will shut down apps on it's own in case it needs the memory right? And, to your points just having apps open won't necessarily drain the battery.
OP, how's your reception. It's also my understanding that having poor reception will drain your battery worse too. Are you running GPS, wireless, or services that use those resources?
Not at all, I don't even have Bluetooth on. And using system tools I can see that before killing any background apps the phone is using 63% memory when killing the apps its reduced to 42%
Sent from my PC36100 using XDA App
autostarts + system panel + juice defender
Take a little time to learn how they work, one you get them set up you'll be a happy camper.
nebenezer said:
autostarts + system panel + juice defender
Take a little time to learn how they work, one you get them set up you'll be a happy camper.
Click to expand...
Click to collapse
+1 for system panel. This will tell you not only what processes are running, but will also tell you how much battery and CPU they use (and have used over the past X hours). It's invaluable when trying to find the rogue process that's sapping up your battery.
Sent from my blah blah blah blah
I don't know why there should be any problem with killing an app or service through the app manager. I do it frequently. At first I did encounter unexpected results but these are less now as I become more familiar.
I wondered, though, is there a preferred order of stopping and clearing data/cache through the app manager (in 2.2)?
I didn't know there was background/forground/cache difference: in froyo, it appears to me that app manager shows all of those under "running"--is that correct? Also, you can look at services. If a service (calendar, talk, etc.) is running, for example, it could be an obvious thing to stop if you aren't using it. You will see if you log out of the service first, and then check the service list, that it might remain running.
I think when you re-start the device very little starts with it. You can use that as a baseline.
Playing games online realtime is probably the biggest power hog I've found. I sometimes cannot play for even 15 min.
Other days, the device holds juice for more than 24 hrs.
The signal strength seems to be the main variable in my experience. The phone signal strength makes a difference, so does 3G, and 4G even more. It's like there's a threshhold or a revolving time--sorry, I don't know the right term here--but the device goes round and round searching if it thinks some signal is out there or if you trigger an app that calls for it. OTOH, once the device really finds nothing at all it drops everything. It shuts down entirely and you get really great battery life
ok so....
1st question - is a task killer necessary with this phone. im happy with its battery life but, of course, the more the better. Does having loads of apps open actually use more battery life?
2nd question - every time i start up google maps, it starts up the gps. If i leave google maps - of course it runs in the background as 1 of the tasks, and therefore gps is left on.
so similar sort of question....if the answer to the 1st question is 'no'.....does having gps on permanently suck more battery life?
if the answer to the 2nd question is 'yes'....is there an app that will switch off gps when its not in use by google maps.
thanks.
Task killers are NOT needed and haven't been needed since.. 2.0?
GPS doesn't run unless you are using an app in the foreground that uses it. When you see the icon in your notification bar, that's when GPS is running.
The answer was no, but you can still use apps like Tasker to turn GPS on/off when not in Google Maps.
joshnichols189 said:
Task killers are NOT needed and haven't been needed since.. 2.0?
GPS doesn't run unless you are using an app in the foreground that uses it. When you see the icon in your notification bar, that's when GPS is running.
The answer was no, but you can still use apps like Tasker to turn GPS on/off when not in Google Maps.
Click to expand...
Click to collapse
You read my mind...
Don't use a killer. Leave GPS on.
Sent from my Galaxy Nexus using xda premium
I've not noticed any battery improvements from turning GPS off.
GPS is not running when you leave Google maps. The only time the GPS is ever running is when you see that icon at the top. Its unnecessary to manually turn GPS on and off.
Task killers don't help IMO. I use system panel to see what's going on as its by far the best task app on android.
What will disabling this effect? I installed wake lock detector and under wake triggers calendar storage has triggered my phone 51 times. This maybe one of the culprits as to why my battery life is so poor.
Sent from my SPH-L900 using xda app-developers app
I'll say probably not. Not enough to see at least. Try a task manager I use a ram/memory manager along with a task manager. To each their own though!
From what I read Greenify hibernates apps you're not using after you select a few. Supposedly when you go back to the hibernated app it takes a little longer to load, but it resumes your previous state hence the term "hibernate".
However, for me it always forgets the apps state, regardless of what app I use it with. Greenify, for me, basically does exactly what a taskkiller did for me. The app has to reboot after being hibernated. I also never had the issue of tasks restarting themselves after being killed.
I am rooted, is this normal behavior, and if so, what is the benefit of using greenify over an automatic task killer?
Sent from my Nexus 7 using xda app-developers app
Am i missing something because i don't even see the app under my apps. I see a widget for it and it shows as a downloaded app in my application manager so i'm not able to view it in apps. Some help?