Database Users

Process "0" using network

I have realized that sometimes there is a process named 0 which takes a lot of network usage, even when APN in off and no network usage should be made. I realize this process takes up a huge amount of battery.
Does anyone have idea what the hell is this 0 thing?
I have cyanogen rom so battery usage displays all apps with its names, jfyi

/bump
any ideas? Anything to do with kernel? This process decides randomly to drain huge amounts of battery some days... don't know why :-/

nilart said:
/bump
any ideas? Anything to do with kernel? This process decides randomly to drain huge amounts of battery some days... don't know why :-/
Click to expand...
Click to collapse
I have this same issue. I can't figure out what is starting it... it is causing 100% wake time too... I have formatted and flashed from scratch to Damage Control 2.07.2 (obviously a 2.1 rom). if I try to click on the process it force closes spare parts.
Could really use this help.

/bump
still having this problem with Froyo and I'm using ARHD 3.5 now. this problem has been with me since version 2.1 and it is still force closed when trying to check it out. any ideas?

Android System Battery use!!!!

Under battery use it says 87%..is that normal??

In my experience of owning a G1 and an Evo (Both Android Devices) I have never seen the percentage be that high before. I just checked my Evo and my Android System is 27%. Im not sure if any harm in it being that high but it doesn't look normal to me.

i just checked again and it's now 91%

Do you have all of the bells and whistles running? Constant updates via Facebook/Twitter/Flickr/Weather/Gmail/etc? Something's got to be running in the background if Android system is that high up.

Also check you google syncing.
I dont ever use calendar, so disabling it from syncing was a good way to go.

i have all syncing off..i pretty much have everything off to save battery

I just looked at mine...pretty much all the syncing on and live wallpaper...Android System 10%.

Definitely sounds like there is an app keeping the phone awake. Also there is the chance an app could have a memory leak.

I don't like that HTC Function test program that's running. It's the GSD.Apk or something like that in /system/app. Back on the hero this app was a big battery burner. Gotta find a way to get rid of it.

great..i just checked and it's up too 95% now..i have no idea what to do..

Turn the phone off, and turn it back on...that will probably clear up the problem...

The moderator over at android central had this to say
" That means that 91% of the things that have used your battery are part of Android and not third party apps. Not that Android System is running 91% of the time. The higher the number for Android System, the better"
So i guess that explains it since i haven't been using third party apps yet..

How soon after unplugging your phone are you looking at this percentage? This number resets every time you unplug your phone. If you have just unplugged your phone and haven't done much with it than the android system percentage will naturally be high.

No Real Solution but helped me quite a bit
Sooo... I believe i was having the same problem. It was accompanied by an extremely high temperature (processor (140F) and chip (120F) ). ((I scaled the processor down to 600mhz and that only marginally decreased the temperature 5-10*)). I saw someone mention a memory leak... well my widget says that i still have a healthy 383MB of ram available and it seems to be stable at around that same figure. I also noticed that in the status bar the data (up) (down) arrows (underneath the H+) showed a download flash 4x then showed a constant arrow like i was downloading something (down arrow, 2 sec, down arrow, 2 sec, down arrow, 2 sec, down arrow, 2 sec, then a constant arrow down). My Network traffic widget showed that I was downloading at intervals of 1sec at a rate of 1kbs. This continued until my battery died or I turned on the wifi and connected to a network.
My solution that yielded a (checking now) 24% battery drain from Android System (from a previous 70-85%).
I deleted a great few apps (most recent first of course) but the thing that showed the most benefit was to change my gmail password on a computer and dissallow my android to log-in to gmail.
I believe it was/is a syncing error and a bug in the android system itsself.
also facebook has been blamed for increasing Android system battery usage.
I went the extra mile and deleted linked in, facebook, and twitter. as well as deleted my moto-blur accounts. As i said im only down to 24% which is still very high for this process (from my experience).
I hope my trials, findings and long-windedness helps someone and sorry this is such a long post.
I still have no real solution. I'm here looking for answers too!
thanks in advance

SRY android dev probably just fed you some BS
I'm no mod, but when the operating system uses all your resources thats NOT a good operating system.
a smooth running and new android device should use only a small percentage on Android System, like were talking 5% or less. not 90%
that "mod" told you that the operating system was doing all your phone could do without any 3rd party apps.... ERRONIOUS!
Again no disrespect if im wrong (im no DEV)
But durn that sounds fishy

jayv1717 said:
Under battery use it says 87%..is that normal??
Click to expand...
Click to collapse
I'm assuming your running an aosp gingerbread rom? There's really nothing you can do about it
Sent from my HTC Evo 4G

The only thing that helped my batterydrain

I installed Spare Parts and saw that my phone was never sleeping, even though it was on standby all the time.
This was caused by the location by antenna feature.
Ever since i unchecked that feature i've had around 50-60 hours of uptime, with a few calls and a lot of texts.
hope this helps alot others

With the new firmware the problem of battery dissapears completely

There is a known issue with network location detection in android 1.6. I had the same issue with my galaxy and it was solved. Now that we have root, we can hopefully do the same.
Also, br aware that I have found spare parts to actually stop the phone from sleeping, as well as tapatalk. I suggest rebooting after using either program.
-------------------------------------
Sent via the XDA Tapatalk App

adrianoftyriel said:
There is a known issue with network location detection in android 1.6. I had the same issue with my galaxy and it was solved. Now that we have root, we can hopefully do the same.
Also, br aware that I have found spare parts to actually stop the phone from sleeping, as well as tapatalk. I suggest rebooting after using either program.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Actually that issue is fixed in the latest update so it's already fixed without needing root.

Which firmware? I know I'm still experiencing it.

RBA020 solved the battery issues for me.

Where in spare parts does it show you if your phone has been sleeping?

you don't need spare parts. Just dial *#*#4636#*#* and click battery history and then the running bar.
Sent from my X10a using XDA App

Inebriatef said:
This was caused by the location by antenna feature.
Click to expand...
Click to collapse
I hope this means that under Location, you had Wireless Networks and Assisted GPS enabled.
One question tho... how did you isolate this feature as the one that was keeping the system awake?
I just found that my phone has been running most of the time, I see Running at 100% under Battery History. Then I select Partial Wake usage and see Android System has the largest share. But what part of Android System? how does one get to know?

I know from having a Samsung galaxy and being part of the androidforums community that was going nuts until Simone found a bug report with Google saying that network location was stopping devices from sleeping. We had root so a Dev applied a patch to services.odex and voila! Phones were napping again.
Sent from my X10a using XDA App

adrianoftyriel said:
I know from having a Samsung galaxy and being part of the androidforums community that was going nuts until Simone found a bug report with Google saying that network location was stopping devices from sleeping. We had root so a Dev applied a patch to services.odex and voila! Phones were napping again.
Sent from my X10a using XDA App
Click to expand...
Click to collapse
Hmm... time to give this a try... so is it just Wireless Network or also AGPS that causes this problem?
I hope I can still leave GPS turned on?
EDIT:
adrianoftyriel said:
Sent from my X10a using XDA App
Click to expand...
Click to collapse
Didn't know that there was an XDA App till I saw your sig. Looks like its worth a try since its free!!

Update after turning location off completely
Well first run with all location methods disabled (I can still enable GPS quickly via a widget when I need to use it)... the battery performance is up phenomenally!!
I charged fully before going to bed last night, then kept the phone unplugged... woke up and found the battery was at 97%. This has never happened to me.
Ok, one thing tho, I use Juice Defender with night time schedule, so my wifi and 3G were off during most of the night. Anyways, its been around 3 hours since I woke up, and I've been using the phone on and off to do some browsing.
The battery is now at 93%.
I do not use any other aid other than Juice Defender... no task killers, no startup editors. Will update on how the rest of the day progresses.
EDIT: my thanks to Inebriatef and adrianoftyriel for pointing this out.

j4mm3r said:
I hope this means that under Location, you had Wireless Networks and Assisted GPS enabled.
One question tho... how did you isolate this feature as the one that was keeping the system awake?
I just found that my phone has been running most of the time, I see Running at 100% under Battery History. Then I select Partial Wake usage and see Android System has the largest share. But what part of Android System? how does one get to know?
Click to expand...
Click to collapse
I too would like to hear a bit more. Could the OP please elaborate?
I'm running the latest FW and although my battery life increased exponentially, I find that it's not going to sleep anymore! I had close to 50 hours battery life and now I repeat everything to get just under 20 hours.
I don't use task killers and crap anymore, just before I put my phone away. If I don't, I have a trillion programs running with like 40mb of RAM free. Although I understand this is Linux based, these programs are RUNNING and not idle. All my **** is draining the battery again after a clean reinstall of everything. What a bummer.

bongd said:
I too would like to hear a bit more. Could the OP please elaborate?
I'm running the latest FW and although my battery life increased exponentially, I find that it's not going to sleep anymore! I had close to 50 hours battery life and now I repeat everything to get just under 20 hours.
I don't use task killers and crap anymore, just before I put my phone away. If I don't, I have a trillion programs running with like 40mb of RAM free. Although I understand this is Linux based, these programs are RUNNING and not idle. All my **** is draining the battery again after a clean reinstall of everything. What a bummer.
Click to expand...
Click to collapse
@bongd, by latest FW, do you mean the R2BA020? If yes, then you shouldn't be affected by the problem being reported here. I'm still on R1FB001, which apparently has this Android 1.6 bug related to location.
As in my case, simply by disabling location settings (even though this reports that network location is the culprit, I disabled them all), the phone is now able to suspend itself and basically consume very little battery in standby.
Personally, I dont see any issue with lot of applications running and having little RAM left because I trust the Android system to manage it efficiently. Furthermore, the RAM on these phones is not as fast as what you would see typically on desktop systems, so it actually helps having things around in memory rather than aggressively cleaning it out. Checkout this link to understand a bit more about Android task management features: http://android-developers.blogspot.com/2010/04/multitasking-android-way.html
I suggest you use Spare Parts to isolate your battery drain, there might be some app that is misbehaving and hogging systems resources. Also turning off very frequent updates/refresh intervals in some applications is the way forward.

I found through trial and error that fancy widgets keeps my phone from sleeping.sad cause I really want to use it.
Sent from my X10a using XDA App

j4mm3r said:
@bongd, by latest FW, do you mean the R2BA020? If yes, then you shouldn't be affected by the problem being reported here. I'm still on R1FB001, which apparently has this Android 1.6 bug related to location.
As in my case, simply by disabling location settings (even though this reports that network location is the culprit, I disabled them all), the phone is now able to suspend itself and basically consume very little battery in standby.
Personally, I dont see any issue with lot of applications running and having little RAM left because I trust the Android system to manage it efficiently. Furthermore, the RAM on these phones is not as fast as what you would see typically on desktop systems, so it actually helps having things around in memory rather than aggressively cleaning it out. Checkout this link to understand a bit more about Android task management features: http://android-developers.blogspot.com/2010/04/multitasking-android-way.html
I suggest you use Spare Parts to isolate your battery drain, there might be some app that is misbehaving and hogging systems resources. Also turning off very frequent updates/refresh intervals in some applications is the way forward.
Click to expand...
Click to collapse
Thanks, j4mm3r. I am using R2BA020. It looks like I have some diagnostic troubleshooting to do when I get home.
Sitting here at work charging my phone, it isn't loading craploads of programs anymore. And it seems to be sleeping okay. I'll play around when I have some free time.

Fixed my problem big time
Hey guys,
I just wanted to throw my two cents into the pot.
OK – so after experimenting with Task Killers, Task Managers, Spare Parts, Juice Defender, etc. I came to the conclusion that they (for the most part) did more bad than good. It was getting to the point that I was just starting to accept that “The X10 just has ****ty battery life” end of story.
I also read in a Google released post on the web, that there are a number of reasons that Task Killers, etc. are actually not required to end tasks. Android actually has a fairly intelligent and systematic approach to killing tasks that are not being used. I haven’t used any sort of proprietary battery saver, task ender, startup cleaner, etc. and I’ve been having the best phone performance since I got the headset.
The time now (Eastern Standard) is 3:30pm on Monday. The last time I charged my phone was Saturday evening at 6pm, and currently I am showing 24% battery remaining. Let those numbers do the talking!
My settings are:
Wi-Fi always off unless I am going to be actively using it (browsing)
Using Phone info, I change WCDMA Preferred to GSM Only (enables 2g instead of 3g without disabling data altogether)
GPS always off
Screen settings, brightness, etc. I believe have a much smaller effect than people tend to believe. The SINGLE BIGGEST factors for me, and noticing this huge increase in battery life are:
Settings -> About Phone -> Software Update -> UNCHECK Automatic Search (this constantly searches the market, etc. for app updates and what not)
Cycle power immediately after charging. Once my phone completes its charge, I turn off and then on again.
I hope that some people can enjoy moderately extended battery life as I have. I am SO ecstatic to be at HOUR 43 and still at 20%+
Worth mentioning also that I am on Rogers (Canada) and have not received any updates, so this extended battery life is not a result of a firmware update.

How I Fixed My Batter Life Problem
My Incredible would run dead in about 4 hrs doing nothing. I finally dug into several "task killer" programs and found that about 20 - 30 apps were invisibily running in the background constantly. As soon as I permanently killed them, my battery life went to normal. I can now get about 2 days of normal use on 1 charge. Even a day of pretty heavy use will last almost all day.
So for me, it was all the new apps I installed when I first got the phone that were running in the background. The free "task killer" program was not showing them. I finally found the app called "System Panel." It was the ONLY app that would show me all the "invisible" apps that were still running invisibly in the background and let me kill them. Once I killed them with System Panel, they stayed dead and the free "task killer" program could auto-kill them from them on.
Not sure why the free programs could not see the rogue apps, but my battery life is GREAT now.

Inebriatef said:
I installed Spare Parts and saw that my phone was never sleeping, even though it was on standby all the time.
This was caused by the location by antenna feature.
Ever since i unchecked that feature i've had around 50-60 hours of uptime, with a few calls and a lot of texts.
hope this helps alot others
Click to expand...
Click to collapse
What do you mean caused by the location of the antenna feature?
Where is this option to uncheck this feature.
Thanks dear.
Vatis

I'm running R2BA023 and I am struggling to get a full day from the phone at the moment. It normally lasts around 12 hours and then its flat.
However, I ran the Telenor R2BA020 update and I manage to get a full day with ease.
I have just done a clean install of R2BA023 Generic UK "root" edtion and going to see how I get on. What I did notice before is that the phone was not returning to a idle state.

Network usage Process '0' draining my battery

hey guys, under *#*#4636#*#*
network usage
a wierd process '0' shows up, draining my battery
i havnt found anything about that issue anywhere..
help pls

SammyGalax said:
hey guys, under *#*#4636#*#*
network usage
a wierd process '0' shows up, draining my battery
i havnt found anything about that issue anywhere..
help pls
Click to expand...
Click to collapse
Try uninstall '0' app

SammyGalax said:
hey guys, under *#*#4636#*#*
network usage
a wierd process '0' shows up, draining my battery
i havnt found anything about that issue anywhere..
help pls
Click to expand...
Click to collapse
You are not the only one.. I have it too.. Seems like android flue
that 0 must be some service in the background !

Same here... cant find any solution ANYWHERE !!!

stevekainth said:
You are not the only one.. I have it too.. Seems like android flue
that 0 must be some service in the background !
Click to expand...
Click to collapse
Help i have the same problem here!!!!
Sent from my GT-I9000 using XDA App

I keep my wifi and apn disconnected all the time.. only turns on when it is required..
what is this 0 that keeps eating battery??

Could be the backup of the system? Do you have it activated in privacy menu?
Sent from my GT-I9000 using Tapatalk

The process ID 0 is root on Linux and (I suppose) also on Android.
Now ask the question: is your process 0 behaving different from that on other phones?
I have no idea what connections would originate in process 0, but I can imagine things like a reply to a ping fall under this.

I have just done a factory reset. The process 0 usage under network usage had gone.I'm now going to add my apis back on one at a time to see what sets the process 0 bug off. My guess is its got to be something that we all use like facebook our something stupid like that.
Il keep you posted
Drew

What is the *#*#code for battery usage?

Tehpriest said:
What is the *#*#code for battery usage?
Click to expand...
Click to collapse
It is *#*#4636#*#*
I also have this process showing and would be interested in finding out what it is. If it is indeed 'root' then why is it a full blue bar?

Tehpriest said:
What is the *#*#code for battery usage?
Click to expand...
Click to collapse
*#0228#
*#*#4636#*#*
Pick one for your intent.
[[]]

Well I didn't actually get round to adding apps before the infamous process "0" appeared. Dunno what the hell it is but its draining my battery. I lost 60% in 2 hours! what's going on!?
Drew

well my drain isnt quite as severe.

Here is what my network use looks like.

dont think that is the issue mine is exactly the same and i get 36 hours per battery or so. depending on the battery

drew071 said:
Here is what my network use looks like.
Click to expand...
Click to collapse
This is almost exactly how mine looks!

lgkahn said:
dont think that is the issue mine is exactly the same and i get 36 hours per battery or so. depending on the battery
Click to expand...
Click to collapse
What do you reckon it is? I done a factory reset and it still draining away.

I think its the facebook app that hammering my battery. I put apps back on the phone one at a time and when I installed facebook I turned off the update interval and closed the application. After a few hours I pulled my phone out my pocket to find it really really hot and my battery was nearly dead after having 50% prior to installing. I uninstalled the app and now my phone is consuming at a rate of approx 5% an hour, still higher than 2.1 but better than it was. I still have the process 0 network usage issue though. I noticed that if you do a firmware recovery and re flash the firmware into the phone, the process 0 usage does not start unroll the phone has been restarted. I used my phone after flashingfor a few hours with no process 0 in the iterate statistics. as soon as I restarted it came back.
andy

drew071 said:
I have just done a factory reset. The process 0 usage under network usage had gone.I'm now going to add my apis back on one at a time to see what sets the process 0 bug off. My guess is its got to be something that we all use like facebook our something stupid like that.
Il keep you posted
Drew
Click to expand...
Click to collapse
Apparently the '0' proccess belongs to rooting.

I don't get how people have battery drain.

Like I honestly don't understand it. They are obviously doing something wrong. I am running NAND with the SD card for applications (Stock 16GB) with gauner1986's HD-FI 0.3 with 2.15.50.14 and I have only 2-5ma battery drain on standby. But here's what I noticed:
Certain applications from Market increases battery drainage. If you install an app, begin to experience high battery drain, uninstall it.
It's a 3G phone for godsakes. Why disable the speed of it by going 2G?
Disable WiFi/Bluetooth/GPS when not needed.
Don't disable AutoSync or Background Sync. I've noticed no increase with both of them except when it pushes email, updates
Keep the brightness UP to 100 percent. I saw no difference upon lowering it.
Don't disable APN either. This isn't your dumbphone, it's meant to have internet. Internet won't drain your battery life if it isn't active.
SetCPU is pointless. I don't even touch it as the risk to damage your phone using it is great. There has been no solid evidence this helps your battery life other then to SLOW down your phone.
Don't use a TaskKiller - Common sense, it eats battery. Android is programmed to kill apps.
On standby, it can last for freaking days even under light/medium usage. Constant heavy usage will make you last at-least a day.
Seriously. If you get drain, you have the wrong radio or application. I even tried uninstalling stock applications like Calender and removing widgets and they had no effect on my system. If you have to disable MAIN smartphone features, you might as well go back to:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I agree with most of what you say here but not this
Keep the brightness UP to 100 percent. I saw no difference upon lowering it.
Click to expand...
Click to collapse
Personally i think your better off keeping the brightness as low as possible as i did experience battery drain when i had it up to 100%.

I have a taskkiller and I don't notice any difference at all. Having the brightness to 100 does drain your battery that's just common sense.

have no probs with batt drain, i dont use appkillers, brightness on about 45%, play music most of the day, internet on all day with updates, txt and call daily, still on 75% now, not a problem

FirefighterDown said:
[*]Certain applications from Market increases battery drainage. If you install an app, begin to experience high battery drain, uninstall it.
Click to expand...
Click to collapse
True.
[*]It's a 3G phone for godsakes. Why disable the speed of it by going 2G?
Click to expand...
Click to collapse
Because it really is a battery consumer. Actually, surfing on 3G is more power consuming than on WiFi, and Edge is fast enough for a fair amount of uses. Having a 2G/3G toggle widget is probably best, indeed no need to dumb down your phone too much.
[*]Disable WiFi/Bluetooth/GPS when not needed.
Click to expand...
Click to collapse
WiFi & BT are obviously true, GPS is bullocks. As long as there's no GPS app running (i.e. there's no GPS icon in the status bar), your GPS is not active and is drawing zero current. It's just a setting.
[*]Don't disable AutoSync or Background Sync. I've noticed no increase with both of them except when it pushes email, updates
Click to expand...
Click to collapse
For some people, with certain apps behaving in a certain way (for example business people getting emails every minute), this can really be a serious battery hug. Again no need to dumb down your phone too much, but it if you really need to squeeze out those extra hours of juice this is a valid option.
[*]Keep the brightness UP to 100 percent. I saw no difference upon lowering it.
Click to expand...
Click to collapse
That's plain rubbish. More brightness = more emitted light = more emitted energy. Read a physics book someday, this really makes no sense. Display is one of the biggest battery hogs, especially when actively using your phone. Leaving it on a low brightness level sure helps heaps.
[*]Don't disable APN either. This isn't your dumbphone, it's meant to have internet. Internet won't drain your battery life if it isn't active.
Click to expand...
Click to collapse
First part is true, enjoy the features your phone has. It does drain your battery though, even when inactive. There's no such thing as a free meal. Disabling mobile data won't double your battery life, but is a very valid option when you really need your phone to last just that little bit longer.
[*]SetCPU is pointless. I don't even touch it as the risk to damage your phone using it is great. There has been no solid evidence this helps your battery life other then to SLOW down your phone.
Click to expand...
Click to collapse
Bullocks again. First of all, underclocking cannot damage your phone in any way. Obviously no scientist has done research (actually, someone probably has but I don't feel like googling any right now) to provide solid evidence on the matter of cpu clocking affecting battery life, but any tech-guy with some experience will disagree with you. No need to clock down your CPU to 245Mhz obviously, but a 900Mhz clock speed will still more than suffice for most users. Again this won't significantly boost battery performance, but all the small bits help.
[*]Don't use a TaskKiller - Common sense, it eats battery. Android is programmed to kill apps.
Click to expand...
Click to collapse
Probably the most valuable information in this thread - spot on!
Constant heavy usage will make you last at-least a day.
Click to expand...
Click to collapse
Define heavy usage. How about playing Angry Birds at 100% brightness, while listening to Pandora with your Bluetooth headset/headphones, through a 3G connection obviously. Not a very far-fetched setup eh!
I'll buy you a cookie if you last more than, say, 6 hours. You probably won't last 4 hours either but I really don't feel like buying you a cookie.

FirefighterDown said:
Constant heavy usage (without playing games or watching movies) will make you last at-least a day.
[/IMG]
Click to expand...
Click to collapse
fixed
ten char

FirefighterDown said:
[*]Keep the brightness UP to 100 percent. I saw no difference upon lowering it]
Click to expand...
Click to collapse
As other posters have said that is nonsense mate. You can easily see with current widget that the consumption is higher with higher brightness.

Bluetooth battery drain is the only issue
Coming from Windows 6.5 -as we all do- we all discuss the battery drainage.
All reasons for battery drainage given in this thread are true (bright screen sucks battery, 3G does etc etc.).
BUT WHY DOES THIS HD2 on ANDROID SUCK MORE BATTERY THAN THE SAME HD2 ON WINMO?
The bluetooth drivers obviously are not the right ones. On Winmo there was no significantly higher battery drainage with bluetooth on than with bluetooth off.
In all Android Roms that I have tried (and I tried them all), bluetooth empties the battery with about 60mA.
Who knows a rom that does not have this bluetooth problem?

jonny68 said:
I agree with most of what you say here but not this
Personally i think your better off keeping the brightness as low as possible as i did experience battery drain when i had it up to 100%.
Click to expand...
Click to collapse
I work outside in direct sunlight, where low settings makes it not viewable. I have it to max and even at home at 40 percent, I see no changes. Probably because of my usage pattern.
Sent from my HTC HD2 using XDA App

hello00 said:
I have a taskkiller and I don't notice any difference at all. Having the brightness to 100 does drain your battery that's just common sense.
Click to expand...
Click to collapse
Taskkillers have been proven to drain your battery. Google themselves have said it and admitted it in complex details. There's a thread on it that Ill pull up later at home. Like I said I see no differences in my battery report.
Sent from my HTC HD2 using XDA App

StephanV said:
You probably won't last 4 hours either but I really don't feel like buying you a cookie.
Click to expand...
Click to collapse
Sorry for this post.... but this made me laugh hard.....

StephanV said:
Probably the most valuable information in this thread - spot on!
Click to expand...
Click to collapse
So why when I run a task killer I get over a dozen apps running in list and when I close them my free RAM goes up, surley if they are using ram they are using energy?
Also surely the energy that these apps are using is MORE then the energy of the task killer itself?
There is ****loads of apps that just seem to run themselves in background and have no need to, I set my killer to kill every 30 mins or whenever screen is off aswell as manually when I choose to.
Can you provide any evidence that the task killer uses more energy then all the apps running in background combined as I seem to get much better battery with it then without it.

TheATHEiST said:
So why when I run a task killer I get over a dozen apps running in list and when I close them my free RAM goes up, surley if they are using ram they are using energy?
Also surely the energy that these apps are using is MORE then the energy of the task killer itself?
There is ****loads of apps that just seem to run themselves in background and have no need to, I set my killer to kill every 30 mins or whenever screen is off aswell as manually when I choose to.
Can you provide any evidence that the task killer uses more energy then all the apps running in background combined as I seem to get much better battery with it then without it.
Click to expand...
Click to collapse
No, just being in RAM memory does not (or maybe very little) use energy. When idle, they're just stored there. A lot of apps simply restart soon after you kill them, consuming a lot more power than just leaving them be, and on top of that you may experience bad app behaviour.
Well, if those apps do stuff they shouldn't be doing, they're badly developed and should be removed or updated, simple as that. Chances are though that those apps really need to be running (and their battery consumption doesn't necessarily have to be high), in which case killing them is even worse.
A lot of well known devs have very clearly pointed this out multiple times (Cyanogen for example is one of them), even Google twittered about it. Do some research, there's plenty of info on it.

It was good to know that info, i never knew that app killers could do more damage and use more power than none at all.

TheATHEiST said:
So why when I run a task killer I get over a dozen apps running in list and when I close them my free RAM goes up, surley if they are using ram they are using energy?
Click to expand...
Click to collapse
No. Android kills applications to free up RAM usage when i needs them.
Also surely the energy that these apps are using is MORE then the energy of the task killer itself?
Click to expand...
Click to collapse
Also incorrect, most applications are killed upon exit/back key hit. Or put into a suspended mode that eats no battery (Android Browser, Facebook etc)
There is ****loads of apps that just seem to run themselves in background and have no need to, I set my killer to kill every 30 mins or whenever screen is off aswell as manually when I choose to.
Click to expand...
Click to collapse
If only that was true. Killing applications will restart them which uses RAM to restart them which can also slow down your system. Applications don't run unless they are continuously fetching/streaming data or providing a service.
Can you provide any evidence that the task killer uses more energy then all the apps running in background combined as I seem to get much better battery with it then without it.
Click to expand...
Click to collapse
Ha, I don't believe you.
tl;dr version at the bottom.
Originally Posted by Google
By default, every application runs in its own Linux process. Android starts the process when any of the application's code needs to be executed, and shuts down the process when it's no longer needed and system resources are required by other applications. A content provider is active only while it's responding to a request from a ContentResolver. And a broadcast receiver is active only while it's responding to a broadcast message. So there's no need to explicitly shut down these components.
Activities, on the other hand, provide the user interface. They're in a long-running conversation with the user and may remain active, even when idle, as long as the conversation continues. Similarly, services may also remain running for a long time. So Android has methods to shut down activities and services in an orderly way:
- An activity can be shut down by calling its finish() method. One activity can shut down another activity (one it started with startActivityForResult()) by calling finishActivity().
- A service can be stopped by calling its stopSelf() method, or by calling Context.stopService().
- Components might also be shut down by the system when they are no longer being used or when Android must reclaim memory for more active components.
If the user leaves a task for a long time, the system clears the task of all activities except the root activity. When the user returns to the task again, it's as the user left it, except that only the initial activity is present. The idea is that, after a time, users will likely have abandoned what they were doing before and are returning to the task to begin something new.
Click to expand...
Click to collapse
Originally Posted by Google
Activity lifecycle
An activity has essentially three states:
- It is active or running when it is in the foreground of the screen (at the top of the activity stack for the current task). This is the activity that is the focus for the user's actions.
- It is paused if it has lost focus but is still visible to the user. That is, another activity lies on top of it and that activity either is transparent or doesn't cover the full screen, so some of the paused activity can show through. A paused activity is completely alive (it maintains all state and member information and remains attached to the window manager), but can be killed by the system in extreme low memory situations.
- It is stopped if it is completely obscured by another activity. It still retains all state and member information. However, it is no longer visible to the user so its window is hidden and it will often be killed by the system when memory is needed elsewhere.
- If an activity is paused or stopped, the system can drop it from memory either by asking it to finish (calling its finish() method), or simply killing its process. When it is displayed again to the user, it must be completely restarted and restored to its previous state.
- The foreground lifetime of an activity happens between a call to onResume() until a corresponding call to onPause(). During this time, the activity is in front of all other activities on screen and is interacting with the user. An activity can frequently transition between the resumed and paused states - for example, onPause() is called when the device goes to sleep or when a new activity is started, onResume() is called when an activity result or a new intent is delivered. Therefore, the code in these two methods should be fairly lightweight.
Click to expand...
Click to collapse
The following diagram illustrates these loops and the paths an activity may take between states. The colored ovals are major states the activity can be in. The square rectangles represent the callback methods you can implement to perform operations when the activity transitions between states.
tl;dr version
- Android is hard coded to automatically kill a task when more memory is needed.
- Android is hard coded to automatically kill a task when it's done doing what it needs to do.
- Android is hard coded to automatically kill a task when you haven't returned to it in a long time.
- Most services (while possibly running in the background) use very little memory when not actively doing something.
- A content provider is only doing something when there is a notification for it to give. Otherwise it uses very little memory.
- Killing a process when it isn't ready only causes it to have to reload itself and start from scratch when it's needed again.
- Because a task is likely running in the background for a reason, killing it will only cause it to re-spawn as soon as the activity that was using it looks for it again. And it will just have to start over again.
- Killing certain processes can have undesirable side effects. Not receiving text messages, alarms not going off, and force closes just to name a few.
- The only true way to prevent something from running at all on your phone would be to uninstall the .apk.
- Most applications will exit themselves if you get out of it by hitting "back" until it closes rather than hitting the "home" button. But even with hitting home, Android will eventually kill it once it's been in the background for a while.

StephanV said:
For some people, with certain apps behaving in a certain way (for example business people getting emails every minute), this can really be a serious battery hug. Again no need to dumb down your phone too much, but it if you really need to squeeze out those extra hours of juice this is a valid option.
Click to expand...
Click to collapse
Obviously you don't have push email setup. Nobody buys the HD2 for that, they buy a Blackberry. Even syncing every hour isn't going to harm your battery other then a few moments versus turning it off altogether. No noticeable differences.
That's plain rubbish. More brightness = more emitted light = more emitted energy. Read a physics book someday, this really makes no sense. Display is one of the biggest battery hogs, especially when actively using your phone. Leaving it on a low brightness level sure helps heaps.
Click to expand...
Click to collapse
Like I said above, has no affects on me. On a laptop, sure. Because those are 15 inch screens, not on a 4.3.
Bullocks again. First of all, underclocking cannot damage your phone in any way. Obviously no scientist has done research (actually, someone probably has but I don't feel like googling any right now) to provide solid evidence on the matter of cpu clocking affecting battery life, but any tech-guy with some experience will disagree with you. No need to clock down your CPU to 245Mhz obviously, but a 900Mhz clock speed will still more than suffice for most users. Again this won't significantly boost battery performance, but all the small bits help.
Click to expand...
Click to collapse
Are you serious? Overclocking and under-clocking has already been proven to harm Intel and AMD processors on main computers in long term situations. Phones run processors just like your laptop/desktop PC does. There's been nothing to prove it helps save battery. I have never used SetCpu and think it's stupid and my phone still outlasts a buddy who runs SetCPU to underclock the CPU. Speed doesn't affect battery or you'd understand that slower CPU would take longer time to run applications, further reducing the battery.
Define heavy usage. How about playing Angry Birds at 100% brightness, while listening to Pandora with your Bluetooth headset/headphones, through a 3G connection obviously. Not a very far-fetched setup eh!is so
I'll buy you a cookie if you last more than, say, 6 hours. You probably won't last 4 hours either but I really don't feel like buying you a cookie.
Click to expand...
Click to collapse
Lets use some basic mathematical skills here. Indeed I just tested this for an hour straight and the drain was 150-200ma constantly. The HD2 battery is something like 1200, 1300ma whatever in total. Lets say its 1200 (too lazy to check) that divided by 200ma drain equals six. Six hours so your logic goes out the door.
Click to expand...
Click to collapse

FirefighterDown said:
Obviously you don't have push email setup. Nobody buys the HD2 for that, they buy a Blackberry. Even syncing every hour isn't going to harm your battery other then a few moments versus turning it off altogether. No noticeable differences.
Click to expand...
Click to collapse
I'm not sure I'm with you here. I do have push email enabled, and it's one of the things I like about Android. What does Blackberry have to do with this? Missing your point.
Well, in your case, it may not be a noticeable difference. It does for people who get a lot of emails. Exactly like I said in my previous posts. What is your point?
Like I said above, has no affects on me. On a laptop, sure. Because those are 15 inch screens, not on a 4.3.
Click to expand...
Click to collapse
Well, I'm 100% sure it affects you too. You can't just create energy out of nothing. Upping the intensity from lowest to highest easily adds in an extra 80mA, and that's just a rough and probably too low estimate.
Have you ever compared you HD2's battery with a laptop battery? Not quite in the same league of size now is it. Moar size = moar powers (well, kind of). Dumb laptop comparison, sorry to put it like this.
You can go ahead and try to reinvent battery usage all you want, but a 4,3" screen is and always will be one of the major battery hogs on a phone like this.
Are you serious? Overclocking and under-clocking has already been proven to harm Intel and AMD processors on main computers in long term situations. Phones run processors just like your laptop/desktop PC does. There's been nothing to prove it helps save battery. I have never used SetCpu and think it's stupid and my phone still outlasts a buddy who runs SetCPU to underclock the CPU. Speed doesn't affect battery or you'd understand that slower CPU would take longer time to run applications, further reducing the battery.
Click to expand...
Click to collapse
Are you? I haven't even used the word 'overclocking' in my entire post, of course that's bad for your hardware. Underclocking isn't gonna do **** though. I'll buy you another cookie if you find a valid source backing that statement up. But let me give you a hint: ain't gonna happen José. Just sayin'. (Disclaimer: I'm talking about realistic/plausible underclocking situations here, applicable to comparable hardware)
Uhm actually there has. Moar CPU = moar heat = moar power loss = moar battery loss. Again, conservation of energy, which could be found in the book I advised you earlier (well actually a thermodynamics book would be more appropriate).
Sounds like some very valid empirical proof you got right there. I'm sorry, but I could care less about your 1 comparison with that unknown phone of your unknown buddy, whom I have no clue about if he can even properly configure SetCPU or has a properly configured battery.
Lets use some basic mathematical skills here. Indeed I just tested this for an hour straight and the drain was 150-200ma constantly. The HD2 battery is something like 1200, 1300ma whatever in total. Lets say its 1200 (too lazy to check) that divided by 200ma drain equals six. Six hours so your logic goes out the door.
Click to expand...
Click to collapse
150-200mA while playing Angry Birds @ 100% Brightness, while listening internet radio through 3G and BT headphones? Sorry, that's just physically not possible, hardware-wise. Not ever ever ever ever gonna happen, so you are either lying your ass off or have no clue how to check your current usage properly.
I think I'm sounding like a major douchebag here, but I don't really get it how you feel like you know all about this stuff when very clearly your technical knowledge on this matter is really limited. I'm very happy for you that you're happy with your battery life, but don't try and preach this like t3h l33t battery solution, because put simply: it's not.

[*]Keep the brightness UP to 100 percent. I saw no difference upon lowering it.
actually this is so funny dude ..
more light NEEDS more power .. this is so simple.. like 1+1=2