Related
UPDATE Dec 9:
ALL i did was use Autoboot (Exceller Multiple Build Loader) set at 3 seconds
Try this setup if all else fails
Rom: ChuckyRom Lite HERE
Radio: 2.15.50.14 HERE
Droid: HyperDroid 1.7 HERE
AutoBoot: Exceller Multiple Build Loader for Android/Ubuntu HERE (Comes preinstalled in ChuckyRom)
PLEASE KEEP LEAVING RESULTS AS I TRY THEM, AND CAN UPDATE THE FIRST POST
10/25:
I have been reading and in a recent post I read HAVE THE BUTTON LIGHTS ON WHEN U BOOT ANDROID and u will save battery and its true try this!
AGAIN, PRESS A BUTTON IN WM AND HAVE THE KEYPAD LIGHTS ON.
THEN AS QUICKLY AS POSSIBLE BOOT ANDROID.
I AM CURRENTLY GETTING 3MA WITH SETCPU
I had to try this twice before it worked but THE KEY IS TO BOOT ANDROID AS SOON AS THE KEYPAD LIGHYS TURN ON!
chrisizzle492 said:
I have been reading and in a recent post I read HAVE THE BUTTON LIGHTS ON WHEN U BOOT ANDROID and u will save battery and its true try this!
AGAIN, PRESS A BUTTON IN WM AND HAVE THE KEYPAD LIGHTS ON.
THEN AS QUICKLY AS POSSIBLE BOOT ANDROID.
I AM CURRENTLY GETTING 3MA WITH SETCPU
I had to try this twice before it worked but THE KEY IS TO BOOT ANDROID AS SOON AS THE KEYPAD LIGHYS TURN ON!
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
I just posted this in another battery thread but I think the real key is booting Android as quickly as possible and not really the lights so much as I have achieved similar results just using Exceller Multiple Build Loader app and not even touching the keys/lights. C/P from the other thread-->
Tried different techniques to get better battery and found that even on the same build with exact same setup would give varying results. Here's my setup that I would like others to try and post their results. SetCpu with screen off profile set to 245min/max 100 priority and whatever main profile you like; but use conservative preferably or interactive for best battery performance. Any task killer that auto kills all tasks with screen off (be sure to add SetCPU to ignore list). And here is the most important step, use an auto android booting app with minimum boot time setting. I have been doing some experiments with this and found that if you boot into Android as soon as possible, it seems to give better battery performance as opposed to playing around in WM then booting Android. Have tried this with several WM/Android combos. For the first time ever I'm able to get comparable battery performance out of Android as WM. I'm running a bare bones WM (but should work with and WM rom) and using Exceller Multiple Build Loader app set to 3 secs. Even running several sense builds I was able to achieve 3-7 mA draw during standby according to current widget. Took my phone off the charger at about 6:30 a.m. and it is now 11:15 and I still have 25% battery left after pretty heavy usage on standard battery. This is as good or better than what I usually get from WM! Hope this helps.
This was the one thing that was ruining my Android on HD2 experience. I finally got this step right after a few tries.
I've been using it for two days now, and getting consistent 5-8mA readings on standby. There's definitely something to either booting Android quickly and/or hitting the back button to turn on the LED backlight on the buttons.
I just checked my phone, and it's reading 5mA.
And I don't even have SetCPU on my phone. Should I try it out?
I think HTC winmo sense is the culprit. I disable the sense in winmo and get very low Android battery usage during standby. Sometimes around 3mA.
Sent from my HTC HD2 using XDA App
I also suggest to disable sense and put wmo in offline status.
Sent from my HTC HD2 using XDA App
leeyunfook said:
I think HTC winmo sense is the culprit. I disable the sense in winmo and get very low Android battery usage during standby. Sometimes around 3mA.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
why should turning off sense be good when it comes to battery usage under android? this would mean winmo and sense are running in the background of android...which is not the fact!
chrisizzle492 said:
I have been reading and in a recent post I read HAVE THE BUTTON LIGHTS ON WHEN U BOOT ANDROID and u will save battery and its true try this!
AGAIN, PRESS A BUTTON IN WM AND HAVE THE KEYPAD LIGHTS ON.
THEN AS QUICKLY AS POSSIBLE BOOT ANDROID.
I AM CURRENTLY GETTING 3MA WITH SETCPU
I had to try this twice before it worked but THE KEY IS TO BOOT ANDROID AS SOON AS THE KEYPAD LIGHYS TURN ON!
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
You had to try this 2 times before it worked yet you claim this is the final solution for battery drain problems?
i agree with you guys but let me just throw this observation into the mix here. i've read somrthing here in these forums regarding the sd card that came with the phone had something wrong with it ( don't really remember the exact issue ) and if you swapped it out for another sd card, there would be less SODs and a better battery as well.
i've tested this as i have a 4gb sd card and have had no problems whatsoever. everything runs smooth as silk. and, once again, the battery life is great.
NOTE: i do use the keypads lights on trick as well.
anap40 said:
You had to try this 2 times before it worked yet you claim this is the final solution for battery drain problems?
Click to expand...
Click to collapse
Please re-read the post. i updated
Most of us don't need to do keypad gymnastics to get those same results.
Just use the exceller boot loader and set it for 3 or 6 seconds. Having stuff turned off till you need it is a great way to preserve the battery.
apallohadas said:
Most of us don't need to do keypad gymnastics to get those same results.
Just use the exceller boot loader and set it for 3 or 6 seconds. Having stuff turned off till you need it is a great way to preserve the battery.
Click to expand...
Click to collapse
Ya thanks for the comment, i was doin this in between class so i didnt have time to just try the Excellor Boot Loader!!!
Updated the First Post Thanks!!!!
well now we hav almost 48 hrs of battery life on android... and moreover i info radio 2.14.xxx is better than 2.15.xxx in battery life...
Not working for me
Sorry thats all not working for me
i'm still having about 60 mA with VBNROM reloaded - 2.15.50.14/ Bangster 1.5 / Scandisk class 2 - 8 GB
I realley tryed everything and have read a lot of posts. I'm really distressed at the moment.
The best battery cosumption i ever experienced was with mccm 2.5 But that one was not stable for me.
Baltheruis said:
Sorry thats all not working for me
i'm still having about 60 mA with VBNROM reloaded - 2.15.50.14/ Bangster 1.5 / Scandisk class 2 - 8 GB
I realley tryed everything and have read a lot of posts. I'm really distressed at the moment.
The best battery cosumption i ever experienced was with mccm 2.5 But that one was not stable for me.
Click to expand...
Click to collapse
1. Are you using SetCPU with a 245 max screen off profile? 2. Are you disabling WiFi, data and GPS when not using it? 3. Are you using a auto task killer with only SetCPU and Current Widget in ignore list? Also, I don't have 3g in my area but if you do I guess it could account for increased battery drain. If you're in an area that is in/out of coverage, this will cause higher battery drain as well. I get spotty coverage where I work and the battery drain is terrible.
Try mdeejay sense rEVOlution 2.0 androind build with your vbn wom rom - works great !
Try this:
1. switch phone radio off in winmo
2. power off and charge until green light comes on
3. boot winwmo on vbn, then immediately click on EBL
4. boot into mdeejay sense rEVO 2.0
5. turn sense off and use LauncherPro
I get *very good* battery life now with avg 5-7mA draw as evidenced by currentwidget.
z
Baltheruis said:
Sorry thats all not working for me
i'm still having about 60 mA with VBNROM reloaded - 2.15.50.14/ Bangster 1.5 / Scandisk class 2 - 8 GB
I realley tryed everything and have read a lot of posts. I'm really distressed at the moment.
The best battery cosumption i ever experienced was with mccm 2.5 But that one was not stable for me.
Click to expand...
Click to collapse
try my complete setup
Baltheruis said:
Sorry thats all not working for me
i'm still having about 60 mA with VBNROM reloaded - 2.15.50.14/ Bangster 1.5 / Scandisk class 2 - 8 GB
I realley tryed everything and have read a lot of posts. I'm really distressed at the moment.
The best battery cosumption i ever experienced was with mccm 2.5 But that one was not stable for me.
Click to expand...
Click to collapse
a few things to try
1
boot into android as quick as possible, 3 or 6 seconds
disable gps location in android
activate the lights when haret is loading
disable wifi & 3g
disable hotspot
disable sync
running htc sense? try a build without it
and many more attempts
im finally at 3mA in airplane mode, 5mA on phone, 7mA with wifi, 20mA with wifi & 3g
chrisizzle492 said:
try my complete setup
Click to expand...
Click to collapse
I want to try that version of Android, but I don't want to mess with my good setup...
Baltheruis said:
Sorry thats all not working for me
i'm still having about 60 mA with VBNROM reloaded - 2.15.50.14/ Bangster 1.5 / Scandisk class 2 - 8 GB
I realley tryed everything and have read a lot of posts. I'm really distressed at the moment.
The best battery cosumption i ever experienced was with mccm 2.5 But that one was not stable for me.
Click to expand...
Click to collapse
no need for keypad gymnastics or other weird and wonderful combinations - before booting into Android, just use KeypadLedControl to force the keypad lights to stay on, then fire up Android using your loader of choice (I use Android Loader, modified to automatically call KeypadLedControl to turn on keypad lights, instead of just letting it run on WinMo startup).
Been rebooting 5-6 times now with consistent low 5-10ma standby current.
Link to KeypadLedControl for lazy people: http://forum.xda-developers.com/showthread.php?t=605731
The Solution....kind of ;-)
Thx for u'r replys.
I considered all u'r tips and sry dudes it didn't work for me I think the problem was related to the Bangster Build, even though i have been lonesome with my issues.
I changed the LED lib, and tryed to let the LEDs on while booting, set CPU is in condervativ mode/screen off 245min/245max 100% interactiv. And yep, GPS and Wifi where off. I even searched for any SD-Card related Problems in regestry. But Chucky did some great work i think. (i switched again concernig to faster boot)
At some time i think each Leo is different to the other. I changed to Hyperdroid 1.7 with 2.14 Radio and the results are definitely mind blasting.
12 hours on the road, did some surfing, some calls, 2 h musik.
Strange though i used the same kernel and same Radio. Something must have gone wrong by flashing Bangster or something.
Hi friends.
I found the following coincedence.
When I install new build aparently CurrentWindget shows 60mA in stand by and no way to fix it to 5-7mA as it should be.
The solution which helps me to fix it is the following:
- enable GPS module in settings
- open Maps and wait for it to find where you are located
- go back to homescreen and put phone to stand by
It should be fixed now to 5-7mA current.
Hope it will help everyone.
I can even leave GPS module on all the time after that - standby current stays at 5-7mA level.
hlvl said:
I can even leave GPS module on all the time after that - standby current stays at 5-7mA level.
Click to expand...
Click to collapse
Very strange, but very cool if it works for you! I will give it a shot next time I see high battery drain. Thanks for sharing, it will help at least one other person if it helps you.
I've also found that switching Bluetooth off, then back on again, fixes this 60mA drain !
Common misconception: leaving GPS enabled in settings doesn't leave the GPS chip on the whole time. It just means that an app can enable it when it needs to (e.g. when you open Maps). As long as there's no GPS icon in your status bar, it doesn't drain *any* battery.
OT: that trick would be way faster than rebooting! Gonna try if it works for me too.
Really strange solution for this issue. I have the same problem but for this moment have drain about 5mA after quick boot with dualbootloader (wait time 3sec for Android load). For this moment 5mA in standby mode - with any enabled comm modules (WiFi,Bluetooth,GPS).
My experince of fixing the problem(temporary) is not using taskkiller too often, but it not always works
Curarpikt said:
My experince of fixing the problem(temporary) is not using taskkiller too often, but it not always works
Click to expand...
Click to collapse
Don't ever use your task killer again, it only causes problems.
Tried the above however no sucess..........please check out my post and tell me what you think
http://forum.xda-developers.com/showthread.php?t=857606&highlight=battery+wifi
I'm getting better battery life with wifi on
StephanV said:
Don't ever use your task killer again, it only causes problems.
Click to expand...
Click to collapse
Why? I use it a lot...
To solve 60mA problem, each time you want to boot android:
1) when you are in windows mobile, lock the phone and turn the screen off by press end call button
2) wait few seconds and press it again to turn on screen
3) you see lock screen, unlock your phone
4) after that boot your android quickly within 10 seconds! (you can do it by creat shortcut of android on your home sceen)
I test it and solve problem for me on both mccm and mdeejay builds!
Phantoml337 said:
Why? I use it a lot...
Click to expand...
Click to collapse
It was discussed hunderd of times. You dont need to free up mem in android 2.x
It has already a memory management built inside.
The only reason to use a task killer is to close an app that hangs or not properly close itself.
If you continue to kill your processes and backround apps just to free up ram, you will definitively drain more battery becaouse some of that apps will just load again automatically from SD or, when you open again one of them, it needs to load again from SD.
rafpigna said:
It was discussed hunderd of times. You dont need to free up mem in android 2.x
It has already a memory management built inside.
The only reason to use a task killer is to close an app that hangs or not properly close itself.
If you continue to kill your processes and backround apps just to free up ram, you will definitively drain more battery becaouse some of that apps will just load again automatically from SD or, when you open again one of them, it needs to load again from SD.
Click to expand...
Click to collapse
Exactly. And apps not closing properly is still not an excuse for using it. If the app is bad uninstall it or mail the dev to fixit, but don't go around screwing stuff up with a task killer.
Phantoml337 said:
Why? I use it a lot...
Click to expand...
Click to collapse
Me to....i use 2!
Autokiller on agressive,and a taskkiller....never troubles with drain etc
Or everyone check my signiture for my thread on battery drain solution
I think the OP is really onto something here. I tried this trick & my drain has gone from a steady 55-65mA down to around 5. I'm impressed!
Just one question, those of you that having issues with battery drain what WM do u use? I've recently had a problem on my HD2 (no USB) and i installed a stock ROM. Before i had the VBN Droid Reloaded 2 and with Mdeejay kernel current widget never showed me values above 300mA (witch i believe i only saw that value 1 time). Usually i'd get from 1-2mA to 250mA tops. Now i'll never go below 60mA and i've seen the record of 600mA. Today it drain me from 95% to 35% in about 2 hours. A bit too much for my taste...
I always find if you boot Android with Win Mo fully booted, it's over 60mA, but if I use Exceller Dual Boot to boot Android before Win Mo has finished loading, then it's 5-6mA.
Yea man task_killer - problem
Everything is working for me fine, i am using futureShocks MIUI build, the only thing is when i switch on bluetooth, my battery drain is about 60-80 mAh without bluetooth i have 3-6 mAh... no task killer, no setcpu, with other builds like mdeejays sense roms this problem is not !?
Everyone an idea how to solve the problem ?
hey
1.
just use system panel to kill "ALL" processes include system process
then its will be back to normal mA
[well its better then restarting the phone no ?]
2.
Forgetting to disable bt or gps in winmobile
can cause that too
3.
remove with titanium backup CSPeopleSyncService [ thx to fruchtfliege ]
dont like apps that cant be controlled and do what they like
4. same apps make drain more in standby i think cos its not really full standby
5. unmount sdcard when u gonna "put ur phone to sleep"
[this one should help a lot but in testing for 8 hours gonna try it on nites]
that doesn't always work, if you don't isolate the cause then the app will re-open itself at times.
as i mentioned in some other threads, the 60ma bug is caused by the process "CSPeopleSyncService". you can kill this process as you wrote, or just disable syncing facebook and google contacts in options. at least i sync them once a day automatically (don't want to loose the sync feature), and the 60ma bug never came back...
fruchtfliege said:
as i mentioned in some other threads, the 60ma bug is caused by the process "CSPeopleSyncService". you can kill this process as you wrote, or just disable syncing facebook and google contacts in options. at least i sync them once a day automatically (don't want to loose the sync feature), and the 60ma bug never came back...
Click to expand...
Click to collapse
Might be a nOOb question but how do you kill that CSPeopleSyncService process?
I've been suffering from this 6mA for a couple of minutes and going to 60mA thing. Rebooting 'might' work but I don't want to monitor the consumption every hour.
If you don't feel like disabling sync, Quick Reboot (free in market) is a good alternative. Some builds have hot rebooting built-in, even easier.
Back in the game in less than 30 seconds, as opposed to the rather lengthy full reboot.
StephanV said:
If you don't feel like disabling sync, Quick Reboot (free in market) is a good alternative. Some builds have hot rebooting built-in, even easier.
Back in the game in less than 30 seconds, as opposed to the rather lengthy full reboot.
Click to expand...
Click to collapse
LoL just downloaded it. It really says what it does. Click it and the device reboots without a single warning.
lukesan said:
Might be a nOOb question but how do you kill that CSPeopleSyncService process?
I've been suffering from this 6mA for a couple of minutes and going to 60mA thing. Rebooting 'might' work but I don't want to monitor the consumption every hour.
Click to expand...
Click to collapse
the best way is a taskkiller. i'm using systempanel light (included in mdj hd builds), where you can add programs and processes to ignore list. but as i said, changing sync to once a day fixed my problem with 60ma in standby completely! i don't know why
StephanV said:
If you don't feel like disabling sync, Quick Reboot (free in market) is a good alternative.
Click to expand...
Click to collapse
lukesan said:
LoL just downloaded it. It really says what it does. Click it and the device reboots without a single warning.
Click to expand...
Click to collapse
I think he meant fast reboot. It just kills everything so it's as if you've just rebooted (sort of).
johncmolyneux said:
I think he meant fast reboot. It just kills everything so it's as if you've just rebooted (sort of).
Click to expand...
Click to collapse
No, I mean Quick Reboot. I'm still not convinced this battery drain is caused by certain processes, so Fast Reboot isn't an option imo.
StephanV said:
No, I mean Quick Reboot. I'm still not convinced this battery drain is caused by certain processes, so Fast Reboot isn't an option imo.
Click to expand...
Click to collapse
Fair enough. So you just mean reboot then. Ah well.
No, it's hot rebooting: basically only rebooting Android (it's a little more complex than that).
I used to do regular reboots but they take way longer.
im suffering from this in Desire HD build
wanna kill this permanently without quick reboot (since my ROM is not Deodex) completely.
disabling sync? its all "disabled"
You all might try a different SD card, had the 30ma bug, was 60. Changed micro SD card, re loaded android, now 3-7ma
Sent from my HTC Desire using XDA App
Just saying, I reboot using dev tools: bad behavior-> crash system server. Probably not the cleanest way to do it but it works.
fruchtfliege said:
as i mentioned in some other threads, the 60ma bug is caused by the process "CSPeopleSyncService". you can kill this process as you wrote, or just disable syncing facebook and google contacts in options. at least i sync them once a day automatically (don't want to loose the sync feature), and the 60ma bug never came back...
Click to expand...
Click to collapse
Where did 'find' this information?
Without background sync enabled and facebook not even installed it can draw up to 60mA.
I'm not sure it's that single process causing the drain to be honest.
(Please don't take this the wrong way )
For me I think it is after I turn on WiFi and then back off again. It never goes back to 7ish mA. It stays at around 65mA as if WiFi was still on.
I'm using darkstone SuperRAM FroYo v1.5.
strange?
I just found something interesting while using autokiller.
In the processes (i had the high drain again) there was twice the 'android system' mentioned.
I killed one of those entries, and the drain went back to 6mA.
Of course, can't be sure enough so i rebooted the phone, played with it a little and after 10 minutes of standby, i checked again. 54mA.
Again, Autokiller > processes and twice the android system. Killed 1 of them and back to 7mA.
I can't say why this happens, because in older builds (MDJ 2.4 Froyo clean w/ it's own kernel i don't have that issue).
I am no DEV or programmer, but maybe it's something others could test as well? I've been playing with this and trying to find out why this happens ever since the hastarin 8.6 kernel was released and I noticed it only happens with later kernels and mostly on RAM builds.
Just my 2 cents (or local currency my 2 bani )
I found this on other post
DarkStone1337 said:
Lets see how many people will ignore this...
To fix high power drain / usage in standby (60mA or 70mA) disable 'Use wireless networks' in Settings>Location menu. You will now get 7mA or less constantly. I discovered this as the main culprit last night. Also works in other builds.
Click to expand...
Click to collapse
For whatever its worth: On MDJ Froyo HD 4.6 (and earlier builds) I can get 3-6mA in standby but anytime I change the Kernel or framework-res.apk and reboot, standby consumption goes up to around 55 mA all the time. Doesn't matter how many times I reboot.
I've been correcting this by rebooting to WM and recopying all the files in the android folder (CLRCAD.exe, Haret.exe, initrd.gz, rootfs.img, startup.txt, system.etx2, ts-calibration) except zImage (because I'm using a different Kernel than came with the build) and data.img. When I boot back to Android, back to 3-7 mA. I don't know why this works, but it consistantly does. At least for me.
another tip by darkstone:
turn off the "use Wireless" in the Locations Settings help to solve the problem if you are having high drain when you got data/wifi
I can understand a PC takes a while to boot considering how many different devices it has to set up, but... a nook? It is so simple it should take less than a second to boot.
Any one knows where is most of the time spent during boot?
Thanks
bisbal said:
I can understand a PC takes a while to boot considering how many different devices it has to set up, but... a nook? It is so simple it should take less than a second to boot.
Click to expand...
Click to collapse
What Linux powered devices do you own that boots a cold, non-hibernated, system in less than a second?
In fact the boot sequence on the NST, or any other Android device for that matter, is more or less the same as on a PC, and the device count ain't that different.
The kernel still have to load storage, input, graphics, networking, usb and whatnot.
Hell, one second isn't even enough to finish the bootloader stage
Considering it is a flavor of Linux, probably running those never ending screens of things being started up. As the nook should be an optimized version, it should really go faster. But an unrooted version goes faster than a rooted one, that was one thing I noticed. Maybe running extra services and start up apps.
apeine said:
Considering it is a flavor of Linux, probably running those never ending screens of things being started up.
Click to expand...
Click to collapse
Well, it's running a Linux kernel and the kernel has to load like any other kernel
There's no console output to fb on boot, and even if there was it wouldn't make a dent in the start-up time.
apeine said:
As the nook should be an optimized version, it should really go faster.
Click to expand...
Click to collapse
Faster than what? A PC with 6 - 36 times the processing power?
In fact, the NST kernel loads faster on its puny 800MHz single-core ARM than the 3.0.0-13 kernel on my quad core 2.6GHz AMD.
What we don't see behind that nice boot animation screen is the system that's being loaded on top of the kernel, namely Android and it's Dalvik virtual machine.
If you go trough the logs you'll see that this is where a large portion of the start-up time is being spent
apeine said:
But an unrooted version goes faster than a rooted one, that was one thing I noticed. Maybe running extra services and start up apps.
Click to expand...
Click to collapse
Well simply rooting the NST enables a single tiny service (adbd) and there's no difference in start-up time booting with the stock ramdisk or the adbd enabled one.
I just tested this for the fun of it, and the start-up times are random variations in the order of milliseconds
Now, like you point out, most rooted devices aren't just rooted but have additional services and apps running, and naturally that increased workload would make the device run a little slower based on the amount of additional stuff, and the quality of it
Nice and complete answer, Roger.
Thanks for taking your time to answer that. Maybe the startup time of an unrooted nook was clearly due to extra overhead apps and services. It is quite noticeable, as I did the restore/reset/update/root/restart after fail several times.
Dalvik is the JVM on the android?
apeine said:
Dalvik is the JVM on the android?
Click to expand...
Click to collapse
That's correct
ros87 said:
What Linux powered devices do you own that boots a cold, non-hibernated, system in less than a second?
Click to expand...
Click to collapse
XPUD, boots in 3 seconds and I have a browser ready to use.
bisbal said:
XPUD, boots in 3 seconds and I have a browser ready to use.
Click to expand...
Click to collapse
3 seconds from you press the power button on your pc? Care to share a video of that?
My pc uses 10-12 seconds just to get to the bootloader menu..
Now, aside from that, I've already stated that a large part of the ~30s boot time is spent on loading Android, there's not much that can be done about that.
I have a dual booted HTC HD2 with WM 6.5 on it and Android running from an SD card. When I'm in Android everything runs fine other than it doesn't recognize the memory card and my main problem is power drain when it's off, or I guess when the screen is off. Is this a problem because of running Android from a memory card? I've turned everything off that I can and have it in airplane mode. I don't use it as my phone so I can do that. But there still is a big power drain when the screen is off so something must be running in the background.
Thanks for your help!
That Tuning Guy said:
I have a dual booted HTC HD2 with WM 6.5 on it and Android running from an SD card. When I'm in Android everything runs fine other than it doesn't recognize the memory card and my main problem is power drain when it's off, or I guess when the screen is off. Is this a problem because of running Android from a memory card? I've turned everything off that I can and have it in airplane mode. I don't use it as my phone so I can do that. But there still is a big power drain when the screen is off so something must be running in the background.
Thanks for your help!
Click to expand...
Click to collapse
Could you download CurrentWidget and post your battery drain in mA when screen is off? In airplane mode it should be at the very most 4mA, but I'm not too sure of this as you're on SD.
Yes, I've already installed that app and it's usually around 58mA. So, if you are correct, something is dramatically draining my battery even when I turn the screen off. Right now with it on it's at 123mA. I've noticed it really jumps around.
That Tuning Guy said:
Yes, I've already installed that app and it's usually around 58mA. So, if you are correct, something is dramatically draining my battery even when I turn the screen off. Right now with it on it's at 123mA. I've noticed it really jumps around.
Click to expand...
Click to collapse
First off all, make sure that you're killing running apps before turning the screen off. If this doesn't work, then at least you know it's not to do with an app. Try using this method to fix the drain and see if it works. When I used SD I had the same issue and this method fixed it, and clearly it has done for many others as well.
Just followed you instructions and so far it seems to have worked. It was just now registering 4mA! YOU ARE AWESOME...
Thanks Nigeldg, I just went through the process you prescribed (taking the battery out also) and now I'm reading 4mA. YOU ARE AWESOME!
Try to switch WinMo into airplane mode before booting Android. Normally that helps as well and is easier that taking out the SD card.
Regards
Achim
Hi Achim, That's what I've always done. I don't use this device as my phone so I always have it in airplane mode, and that's why it seemed so weird that it would be using power when the screen was off. By the way, if you're curious, it's main use is tuning pianos! The program I use is TuneLab.
Thanks for your advice though. It's nice to know there are plenty of helpful people out there!
Scott
That Tuning Guy said:
Thanks Nigeldg, I just went through the process you prescribed (taking the battery out also) and now I'm reading 4mA. YOU ARE AWESOME!
Click to expand...
Click to collapse
Haha glad I could help mate Annoyingly when I first had that issue I didn't manage to find that thread so I just fresh installed a new ROM. Also don't forget to thank the OP of that thread as well, all I did was provide a link
Sent from my NexusHD2