Database Users

delete please

thanks for helps

thanks for helps

thanks for helps

freemanquna said:
do any one know which radio is stable and consume less energy?
Click to expand...
Click to collapse
I'll leave it to others to give advice on which radio to use. It might be worth installing danielherrero's (one of our own developers) bandswitch application http://www.commmgrpro.com/ You could use this to limit phone to certain bands only with an easy interface. Would allow you to check out exactly what is causing the drain on battery.
Mike

thanks for helps

Sorry, got me stumped. So with no radios on the consumption is double that when wifi is on!!
Let's see if anyone else has any suggestions.
Mike

infinite loop perhaps??
What ROM/Radio versions are you running? EDIT:: seen the ROMs, perhaps try updating to a newer dopod ROM??
Also what 3rd party apps have you got installed??
(RESCO was a ***** for doing this to my TyTN)

the exact same thing happens to me. i've charged it completely, it obviously got really hot. usually at this point, i would take out the battery and let it cool off before turning the phone on, otherwise it would get even hotter and eat 300+ mA and drain the battery fast. this time i opened the wi-fi connection and immediately the battery status dropped from 332 mA to 130, and stayed down there. the phone even cooled down a bit. after i've turned off the wi-fi, it started draining and heating again. what can i do? is it a software or hardware problem? i'm using schaps 4.31, 1.47.30.10, have google maps, palringo, opera, tcpmp installed

I have the same behavior, too.
But not yesterday evening. After restarted it for the xxx time it staid at 28mA. This was so until I left the train in the morning. It went up to 347mA and I am not able to get it back to 28.
I am using the default HTC ROM "HTC_TyTN_GER_3.54.257.2_103_6275_1.47.00.10_108".
I also tried several other ROMS (Schaps, Pays ...) and different radio versions as "HERM_Radinly_1.16.00.00_CustomRUU", "HERM_Radinly_1.47.00.00_CustomRUU", "HERM_Radinly_1.47.00.10_CustomRUU", "HERM_Radinly_1.47.30.10_CustomRUU" and "HERM_Radinly_1.54.30.10_CustomRUU"
but none of them helped me out.
I also done the Exchange Server trick, deactivated 3G and even deactivated all GPRS or EDGE possibilities from provider side.
demichef

Phone gets hot
Hi,
I am not an expert but I had the same problem with my phone, I solved the problem by moving some software I had on my storage card to the internal memory, (in my case it was the encryption and additional language support software I had)
Another way is to look for the Power management tweak in this forum which helps to manage your storage cards power draining,
Sound strange but it worked for me.
Good luck

Hi,
the new battery has arrived.
There is no change in battery draining
What I recognized is, that if the battery is "cold" the power consumtion is around 28mA. But after a call it is getting warm and uses 10 time so much of power.
Please don't laugh now:
I put the battery inside my freezer for 5 minutes. Put it back inside the mobile ...
... 28mA.
If I keep it cold it stays fine for 3 days.
There must be any solution on that.
demichef

Possible soluition to fix 60mA: Enable GPS and wait for full sync

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 ?

(Q) Screen using way to much battery

Recently on every build i use the display is taking up about 80% of the overall battery use i use it moderately but it only lasts about 8-9 hours. I looked on my battery usage and over the 9 hours my screen had been on bout about 50 minutes but had used 80% I have it on lowest brightness and have set it to turn off after 15 secs. Anybody else having this issue or know of a way around this. Also use setcpu with screen off settings and current widget is showing around 3-6mah when in standby.

Nobody else experiancing this?

I've had this issue in the past. Check this thread out, its a POSSIBLE reason why the screen is draining the battery. Basically the proximity sensor keeps running constantly when it should only activate during phone calls. In winmo the proximity sensor behaves correctly and turns off once you've hanged up. I'm hoping devs notice this and can hopefully find a fix for it
http://forum.xda-developers.com/showthread.php?t=870149
P.S. try installing system panel lite, just in case a rogue app is draining cpu constantly in the background even when your screen is off

Hmm no I'm pretty sure it's got nothing to do with the proximity sensor, this is a way more serious battery drain.
I suggest trying another build, maybe you're using an outdated one? If not, try reformatting your SD card (full format, not the quick one), changing radio and changing WinMo. You don't have to do them all at once, it may very well work after just one or a couple of these steps.

StephanV said:
Hmm no I'm pretty sure it's got nothing to do with the proximity sensor, this is a way more serious battery drain.
I suggest trying another build, maybe you're using an outdated one? If not, try reformatting your SD card (full format, not the quick one), changing radio and changing WinMo. You don't have to do them all at once, it may very well work after just one or a couple of these steps.
Click to expand...
Click to collapse
Its strange as its doing it will all builds i have formatted my card several times i have tried several new builds also swapped radios, done task 29 and tried several wm roms bit confused by it as some people are saying they get a days use and i dont not even in aeroplane mode :/

Jammie_1989 said:
Its strange as its doing it will all builds i have formatted my card several times i have tried several new builds also swapped radios, done task 29 and tried several wm roms bit confused by it as some people are saying they get a days use and i dont not even in aeroplane mode :/
Click to expand...
Click to collapse
That pretty much leaves out one option: try another SD card. Not all cards are equally optimal for Android. Just borrow one from a friend, and check if it makes a difference.

Diagnose random shutdown?

Probably at least once a day I will pickup my phone and it is off...any way to diagnose what is killing it? Running stock Sense with 1.72 update (rooted however). No overclocking but SetCpu is running but think it happened before when I wasn't using. Thanks for any help.
Sent from my HTC Vision using XDA App

Is it just off, or is it the "sleep of death", where you have to pull the battery to bring it back? I had the latter problem, and it was solved by installing one of the pershoot kernels from ROM Manager, oddly enough. Someone replied to a similar question from me with a "Try using pershoot, works well for me", and I was going to write it off as a rather unhelpful response, since he didn't elaborate at all...but wouldn't ya know it. Installed it for the hell of it, and cleared up the issues immediately. Didn't chance anything else (overclocking, settings, etc...). Worth a shot!

Its actually 'off'. Hitting the power button restarts it just fine, but it takes a long time to boot as if I HAD pulled the battery (not the fast boot you get when you tell it to turn off and then turn it back on).
I saw the threads on sleep of death but my symptoms didn't seem to fit.
I have noticed though that I would get pictures missing from my album and a reboot or a dismount and remount of my sd card would get them to turn back up. So I have bought a new card and so far so good on that front, and also no more shutdowns...so thinking maybe it was the memory card...which makes sense as it wasn't happening to anyone else!
Is there a program that logs what processes where running? I was thinking that I would see what tried to run before it shut off - but hopefully not necessary now!
Thanks for the reply...

Incredible battery drain?

On my second nook due to battery drain, getting terrible usage, lost 11% in 6 hours of no use. I've tried with and without a nook account, tried forcing it to sleep and letting it sleep by itself. Got wifi turned off.
Any ideas?

Is it rooted? Install Button Savior, and use the its soft power button to put the device into sleep mode from either the Nook Reader, Nook Home, or Nook Library apps. Seems to help for me.
If not, try pushing and holding the 'n' key until it sleeps from one of those apps. If that doesn't help, try sleeping by tapping the power button on the back.

Nope not rooted, it's for someone who is a techno-phobe so rooting would just confuse and overwhelm them.

theronkinator said:
Nope not rooted, it's for someone who is a techno-phobe so rooting would just confuse and overwhelm them.
Click to expand...
Click to collapse
Use better battery stats and then see that which app drains your battery or wakes your phone..
sent from my phone using hands and brain...

dagger said:
Use better battery stats and then see that which app drains your battery or wakes your phone..
sent from my phone using hands and brain...
Click to expand...
Click to collapse
Did you miss the not rooted bit?

theronkinator said:
Did you miss the not rooted bit?
Click to expand...
Click to collapse
It uses root only for finding the raw kernel wakelock.
rest of the things could be seen without root also..

Except you can't get better battery stats on the nook without rooting.

If I get what you're saying right, you' bought a brand new nook and it's draining that much out of the box? Sounds like it's defective to me. Odd that it's happened to you twice, Try doing a factory reset and see if it's still a problem, you may need to take it back and get a third one.
The only other time I've heard of that type of problem with hardware is when someone I knew bought from a random cheaper website (I believe it was an older kindle, not a nook but still), turns out it was some knockoff that didn't use the same parts inside. I don't know if maybe this could be your issue, but these things shouldn't drain the battery that quickly even with use AND root.
sorry if I misunderstood your problem =D