Database Info

Battery

Greetings
I think so after flashing my fone in the last month for more than 50 times.
I see my battery is going wierd.
1. when i take out my battery it forgets the date and time.
2. It is showing weird difference, like at one time it is 88 and after reseting it goes to 90%.
Anybody know wats the problem.
Thanks

Yup.. even me have the same issue like you..
i dont know if its because of the crossbow rom but someone told me that even in wm5..

It is listed somewhere that the WM6 has problem tracking your battery life due to the change of ROM. I recall the thread mentioned that you ought to run your battery as low as possible before recharing it to full again and that ought to fix the battery indicator problem.
BTW, while I'm here, I'm just wondering, what software do you use to check the battery drainage? e.g. how do you check if your plugins / background software is eating your battery like mad.
UPDATE2:
Hmm... I seems to have found it
Just incase someone looking for it (difficult to google for such common words) BatteryStatus

I use battery status

Have the same problem
I've the same problem, but It stared eith me when I was using WM5

join the club...

yuppers. these battery problems are not confined to certain ROMS
It's making my phone unusable. I've tried every WM6 ROM out and none makes a lick of difference. My phone dies in 2-4 hours. Battery readings are unstable in all plug-ins (BatteryStatus) and even the OS % meter. Tried the drain to 0% and fully charge thing before and after a hard reset and it did nothing. I've been using Pocket Battery Analyzer to graph and record the discharge and it's insane. 20%-30%/hr or more. It's sky-high when using the phone or GPRS. And it'll often white-screen/lockup when the battery gets low (but not 0), which it never used to do (nor should it).
This all started after flashing a million different WM6 ROMS. Has one of these ROMs buggered something it shouldn't have? I wish I could remember exactly when the problem surfaced (sometime in the past two weeks) maybe we all used a common ROM that screwed our phones. I think the closest ROMS I used around the time it started were mUn's, MB, and that NTS one on rapidshare (I read somewhere it was an updated MB).
Anyone who knows what IPL/SPL does wanna chime in? Can corruption to that memory code conceivably cause this? Maybe I'll try reflashing that just to check.
Other than that I just don't know. I pray the flashing hasn't killed some hardware component. How many writes are these ROM chips supposed to handle in their lifetime? I know things like SD and USB memory get 10,000's-100,000s writes before failure. Maybe these chips aren't designed for repeated re-flashing. Just a thought...
fluxist

Believe it or not, but certain versions of Battery Status (that same today plug in you are using to monitor battery level) are actually known to deplete the battry quite quickly.
Two nights ago, I had my phone going from 70% to 0 (dead) while I was sleeping... Clearly the phone was not!
Removed battery status: my phone goes back to its true self.
Now, I have to find out which version of Battery Status work, and which one don't... as it has not been always like this.
Regards,
--eluth

fluxist said:
It's making my phone unusable. I've tried every WM6 ROM out and none makes a lick of difference. My phone dies in 2-4 hours. Battery readings are unstable in all plug-ins (BatteryStatus) and even the OS % meter. Tried the drain to 0% and fully charge thing before and after a hard reset and it did nothing. I've been using Pocket Battery Analyzer to graph and record the discharge and it's insane. 20%-30%/hr or more. It's sky-high when using the phone or GPRS. And it'll often white-screen/lockup when the battery gets low (but not 0), which it never used to do (nor should it).
This all started after flashing a million different WM6 ROMS. Has one of these ROMs buggered something it shouldn't have? I wish I could remember exactly when the problem surfaced (sometime in the past two weeks) maybe we all used a common ROM that screwed our phones. I think the closest ROMS I used around the time it started were mUn's, MB, and that NTS one on rapidshare (I read somewhere it was an updated MB).
Anyone who knows what IPL/SPL does wanna chime in? Can corruption to that memory code conceivably cause this? Maybe I'll try reflashing that just to check.
Other than that I just don't know. I pray the flashing hasn't killed some hardware component. How many writes are these ROM chips supposed to handle in their lifetime? I know things like SD and USB memory get 10,000's-100,000s writes before failure. Maybe these chips aren't designed for repeated re-flashing. Just a thought...
fluxist
Click to expand...
Click to collapse
May your problem come from hardware ? I mean it's not impossible...if you have an imperfect contact, that will also deplete your battery fast. What are temperature readings with batterystatus ?...do you feel your phone is warm ?

BatteryStatus
Yeah, I've read tons of posts suggesting batterystatus may be draining batteries but this condition persists even when newly flashed without installing batterystatus.
And regarding a short in the hardware, yeah thats surely possible. Ive dropped my phone enough times. But with all the hullabaloo in this forum about battery drain issues i'm more inclined to believe it's something else. And I only got this phone in June. I should hope these batteries last longer than 9 months before becoming unusable.
I just replaced the IPL/SPL using the T-Mobile 2.26 ROM. I'm not hopeful.
fluxist

fluxist said:
Yeah, I've read tons of posts suggesting batterystatus may be draining batteries but this condition persists even when newly flashed without installing batterystatus.
And regarding a short in the hardware, yeah thats surely possible. Ive dropped my phone enough times. But with all the hullabaloo in this forum about battery drain issues i'm more inclined to believe it's something else. And I only got this phone in June. I should hope these batteries last longer than 9 months before becoming unusable.
I just replaced the IPL/SPL using the T-Mobile 2.26 ROM. I'm not hopeful.
fluxist
Click to expand...
Click to collapse
do you have battery drain with any rom you use ? try orwell or ..how about a wm5 ... ? or try another battery

I have the same problem!
When i have put Orwell ROm everything was ok!
Then installed mUn rom and also everything was ok!
Both of them could use Omapscaler without any problem (overclock/underclock)
Then i tried the Xplore 1.0 which included the BatteryStatus.
After the BatteryStatus the Wizard changed!
The battery drain was big and when removed the BS and ckeck with Omapscaler the CPU is always 100%.
Then i put again the Mun but the same CPU 100% every time with OmapScaler nad battery drain.
Then i put the NBD ROM and the same with above.
Now using Xplore 1.1 and the problem remain.
My concern is that something changed!

I've noticed the time and date screw up when I'm taking the battery out as well, but other than that my phone acts pretty normal. no huge battery drain. I did not monitor it closely, but a couple days ago I installed Battery Status beta 3, and it seemed to me that the battery drains a litttle faster than previously, but can't tell for sure, as I had some spare time and I used pocket MS reader a lot.

No luck
Well I replaced the IPL/SPL (not that I really thought that that was the problem, but i'm trying to eliminate variables one by one).
And it did............... absolutely nothing. The power problems remain.
I have had BatteryStatusExt installed and maybe it is in fact the culprit (in which case they better get a good lawyer), but by what mechanism could any software cause a condition that persists through ROM flashes? Any ideas?
I would totally think my battery was at fault and buy a new one if this wasn't happening to others at the same time. These battery problem posts have only surfaced in the past few weeks, and at least in this thread, all the symptoms are the same. (That and cell batteries are expensive as hell and they don't allow returns)
So what the hell is going on here? I'm on Xplore now and the problem still remains. Next up I'll try going back to a WM5. However, other posters have reported the problem persists in WM5 as well.
I think I might try and analyze BatteryStatus. Perhaps the author employed some non-standard methods for accessing the battery.
Come to think of it, I used the original BatteryStatus (the one that had no overclocking capabilities) for ages back when everything was fine. Maybe the overclocking method the new version uses is leaving the OMAP chip in an unstable configuration? Really I'm appealing to the experts here. I'll try to look into it myself but more eyes are always better at finding bugs.
OK. Off to find the spec sheet for that chip...
fluxist

I'm also curious about the draining when flashing back to WM5. I'm considering going back, but i would like to read some experiences.
The draining is killing me. I'm on X-Plore and it gets worse every day.
I'm willing to pay for a good solution (;

same here
fluxist said:
It's making my phone unusable. I've tried every WM6 ROM out and none makes a lick of difference. My phone dies in 2-4 hours. Battery readings are unstable in all plug-ins (BatteryStatus) and even the OS % meter. Tried the drain to 0% and fully charge thing before and after a hard reset and it did nothing. I've been using Pocket Battery Analyzer to graph and record the discharge and it's insane. 20%-30%/hr or more. It's sky-high when using the phone or GPRS. And it'll often white-screen/lockup when the battery gets low (but not 0), which it never used to do (nor should it).
This all started after flashing a million different WM6 ROMS. Has one of these ROMs buggered something it shouldn't have? I wish I could remember exactly when the problem surfaced (sometime in the past two weeks) maybe we all used a common ROM that screwed our phones. I think the closest ROMS I used around the time it started were mUn's, MB, and that NTS one on rapidshare (I read somewhere it was an updated MB).
Anyone who knows what IPL/SPL does wanna chime in? Can corruption to that memory code conceivably cause this? Maybe I'll try reflashing that just to check.
Other than that I just don't know. I pray the flashing hasn't killed some hardware component. How many writes are these ROM chips supposed to handle in their lifetime? I know things like SD and USB memory get 10,000's-100,000s writes before failure. Maybe these chips aren't designed for repeated re-flashing. Just a thought...
fluxist
Click to expand...
Click to collapse
My phone also dies in a few hours. I'd charge it to 100% and see it goes down 1% every minute or so. After just a call or two it'd restart itself due to low battery. BS says it's using 200+ mA which seems high after reading others at low double digits. This had never happened before I upgraded to WM6. I've tried MBE and Faria's Real Thing and both are the same. I know the battery has overcharge protection. Could BS somehow messed up the battery with its probing?

hi,
i flashed to Faria and my Battery lost from 100 to 10 % during the last 12h.
i installed BatteryStatus and SPB Shell.
Cpuscaler at 156 mhz and it shows +198mA ...
Wat is wrong ?

Yeah from what it seems the BS leaves something behind or puts the CPU or battery in such a state that it, get drained faster I noticed that also. I dont think its the ROMs them selfs I think its the BS. Also we have to remmber that BS was not designed for the wizard, so the person that is developing it is not using the same hardware as we are....... THis is really sad I have 2 batteries and both basicly now do the same thing. I asked that X-Plore would not include BS in 1.1, and thats what I have running on my wizard now. The battery is not as crazy as other people, but still from 8am to 5 and 52% gone with about 13 calls and 3-4 email thru direct push and some browsing. SO I dont know, but it is sad hopefully T-Mo will release a new phone with in this month and I will upgrade

Battery issues
I'm not really having too much problem with my battery so far. I'm running battery status as well. However, I'm pretty moderate with my overclocking. I remember reading when omapclock first came out that some people would find that after a few weeks of overclocking, their wizards would start draining the battery very rapidly, even after cutting back the clock again. I wonder if heavy overclocking can sometimes damage some of the electronics in the wizard, causing persistent power loss?
Hope you guys get things back to normal..
Regards,

I have installed Xplore 1.1 ....without BS.... still huge draining.
40% in 4 houres. Great rom, but too fast out of power for me.
I'm going back to WM5....let you know if the draining consists....

WM6 KILLS the Battery... Help!!

I recently upgraded to WM6 ROM, "Jwrightmcps Crossbow ROM Update 2.02.02 WWE", and all went well.
But then at 40% battery my phone died... and this is very similar to a problem I used to had in WM5.
Can anyone tell me which WM6 ROM doesnt cause the battery problem?
For the record, I don't think either my phone or PDA is damaged. The last time I had this problem, I went back to the service center (several times I might add), and they replaced everything eventually (both PDA and Battery). Since then it has worked fine (for about 6mths+), until I flashed to the WM6 ROM.
**** man, I hope this has not damaged my device. Out of warranty already.

I had a similar problem and also initially didn't beleive it could be the battery, but guess what -- getting a new battery solved almost all problems I had including the phone dying at 40% or above. So it might be worth a try...

IT"S YOUR BATTERY
Just trust me
the battery 'dies' after like 6 to 12 months. It just goes bad in a week.
Mine went out on like 20%, then a week later on 54%
replacing it fixes it.

mine crashes over 20%.... the battery it's new

I had same problem with battery,then I buy new battery from ebay, and then the battery status was OK it goes from 100- 4% with warning and everything. But the problem was that battery last only a couple of hours, even aftzer a few days nothing change I must have charger with me all the time.
Then I search the forum and found someons solution, that works for me too.
Just charge the battery full take the cable out and put it in again a couple of times so the battery is realy full charged, the put the device in bootloader mode by pressing Power + Light + Reset, which brings up an un-backlit screen with "Serial" at the top, and "v0.XX" at the bottom. And then just put your device somewhere and dont touch it until it died that coul be the all day. Anyway next day I put the charger in and again didnt touc for all day. And my problems are gone, the battery since then last fortwo or three days if I dont use it much.
Hope that will help somebody

Dears,
i used to read about this issue in the forum again and again.....so i desided to wrote this post....everyone was claming the battery is the reason....OK do not belive this.....it is the rom.....i used the wm6 for sometime and i was facing the same problem....and when my carrier started the 3G i had to switch back to wm5.....and now my device never turns off before i get notified that my battery level is too low it about 10% of the battery....so if you do not belive me just do this test....switch back to wm5...i am using now Hilme 3.5 v1.3.1
regards

Mine dies at 35% with wm6 and wm5 and my old battery, but never dies with my new battery.

Use Radio 1.15
My battery life increased by 200% just by upgrading to this radio ROM.

same here
i m also sufrer of same problem. now after this forum i m confused

Here is the simple fact of the matter:
Batteries are EXTREMELY complicated pieces of equipment
They often give false readings because the chemical reaction that creates the electricity is easily affected by heat\age\use\etc. Also, the electronics that measure the temperature are based on the false assumption that the battery drains in a predictable way down to the same level.
Your battery draining quicker\slower and dying when it says it has charge may be because of the ROM. However, this is HIGHLY unlikely. What is most likely the cause is external factors (eg heat, number of programs running, etc) or that the battery has "died" or become unreliable.
Recommendation: Try different batteries, and remember that batteries have a chemical reaction, before posting here

I don't know... I started having problems as well just after a ROM upgrade... but it was an official ROM upgrade. I start thinking this has something to do with the upgrade process, like some setting being "wiped out" during the upgrade and the battery going "out of sync" with the device, reporting the wrong battery level...
But, more likely, this is just a psycological effect, you install the new rom and then start playing a lot with the device to find the improvements, and you begin noticing the problem for the first time!

My relatively new I-mate JasJar also started dying when the battery level reached 40% the day i flashed WM6.
i posted here, trying to explain that it was perfectly alright 2 days back, prior to WM6.. pointless to say, everyone still said it was the battery 100%
well.. i got a new battery.. and it did indeed solve the problem.
but guess what.
i flashed WM5 back, and both batteries work fine there.
not sure what the heck is going on here.. but i'm certain there are two fixes:
- flash WM5 back on.
- get a new battery and stay with WM6

astraman said:
Dears,
i used to read about this issue in the forum again and again.....so i desided to wrote this post....everyone was claming the battery is the reason....OK do not belive this.....it is the rom.....i used the wm6 for sometime and i was facing the same problem....and when my carrier started the 3G i had to switch back to wm5.....and now my device never turns off before i get notified that my battery level is too low it about 10% of the battery....so if you do not belive me just do this test....switch back to wm5...i am using now Hilme 3.5 v1.3.1
regards
Click to expand...
Click to collapse
I used to think like you, but now I beg to differ, my dead battery never usable under any OS.
It used to be always dead at some % starting from as low as 0 (good ones) and increase until now it is permanent dead at 100%. I have all your intermediate voltages before reaching 100%.
If your's still usable than your battery is not complete dead yet or half dead or maybe soon to be dead.
By the way, I am using helmi_c aku3.5 v1.3 (add on version) as compared to v1.3.1 (vanilla version).
One last thing, please do use big bold characters in forum, sounds like shouting. Thanks!

You cannot judge the battery is old or new by just months.
This older version of Universal battery, it counts by number of time charged I think, inserting in USB for a sync and remove would probably counted as 1 charge.
I now do not sync using those working condition battery, I change to my dead battery for sync purpose.
As I sync only contacts, now Dotfred has a tool and now I hardly use sync anymore.
By the way, there is one guy in this same forum start another thread without reading this (closest info) or all other previous threads.
People like this deserved to be flamed, but I didnt.

IMHO WM6 uses and drains the battery different then WM5
My experience is that everyone that has problems with their device dying just switched to WM6. It has nothing to do with the WM6 itself, it's just that WM6 is more 'sensitive' to a low battery output then WM5. So if you switch back to WM5 it looks like it might 'solve' your problem but in the end the battery will die, it'll just take a little bit longer before WM5 appears to have problems.
You'll postpone the problem for a little while but it's not a fix
Just my 2 cents

CWKJ said:
I used to think like you, but now I beg to differ, my dead battery never usable under any OS.
It used to be always dead at some % starting from as low as 0 (good ones) and increase until now it is permanent dead at 100%. I have all your intermediate voltages before reaching 100%.
If your's still usable than your battery is not complete dead yet or half dead or maybe soon to be dead.
By the way, I am using helmi_c aku3.5 v1.3 (add on version) as compared to v1.3.1 (vanilla version).
One last thing, please do use big bold characters in forum, sounds like shouting. Thanks!
Click to expand...
Click to collapse
Mine still working very good at WM5 as i told you.....just let the battery get off and recharge it till full....now mine is working great and keep working until 10% or less

The point is that WM6 treets the battery and power in different way then WM5. First when you upgrade to wm6 and start it first time it assumes that battery is full (the instruction says that you should charge your battery before uploding new ROM). If the battery was not fully charged then you have a problem. WM6 registers the point of current while starting first time and assumes that this level represents the fully charged batteryl. Then it is programmed for consumption of power according to processor cycles, so after such and such time of use of your device it should reach certain level of power. If your battery was not charged full at the start then it will always show false percantage.
The solution is to fully charge the battery (possibly using the way described in some post above) and then reload the ROM once more.
Of cource when you buy a new battery, WM6 registers this (each battery has unic number) and creats new pattern for this battery. That is way it is so importatnt to properly charge the new battery when you load it first time.
Hope this is helpful.

astraman said:
Mine still working very good at WM5 as i told you.....just let the battery get off and recharge it till full....now mine is working great and keep working until 10% or less
Click to expand...
Click to collapse
I have 3 original batteries.
In principle, good battery can goes to perfect 0%.
First battery started half dead (that is phone is dead 30%) after upgrade from WM5 AKU1 to WM5 AKU2 happen to be around 6 months after I start using the phone, I thought it was the problem with WM5 AKU2 ROM. My usage pattern of this battery is that I charge anytime I wish with Power charger and also during sync. This battery is still with me now after 1 year I have encounter the problem. The dead % grow (no change of ROM) until now it is around 100%, that is phone is dead just before it goes to 99%.
Second battery was bought the same time my first battery has problem, 1 year passed. Usage pattern are, never use this battery for sync or short connections to PC USB, never charge my battery until it is 0% (always possible) or less than 5%, never upgrade ROM using this battery. Always charge to LED turns GREEN & always sync & upgrade ROM with the dead stuck at 100% battery. 1 year has gone, the second is still able to reach 0% till now with battery last average 1 to 3 days, normally 2 days & sometimes 4 days depends on usage pattern.
Third battery, claim by vendor that some electronics is modified compared to the those bought last year. Charged this battery, use a few time to check if it is an ok battery, need to do this as I have ever bought brand new dead battery last year. After confirmed it is a good battery, I continue using the second battery and third battery always carry along as backup in case I used up the second battery.
Hope my usage pattern can help some of you to have optimal use of the battery and do not let the manufacturer earn extra money due to the problem in the old version of the battery. Anyway, this original battery will be discontinued soon due to end of life of this product. Guess I will have to look forward of getting imitations when my second & third battery is gone or maybe when my phone is gone too.

Tadeusz said:
The point is that WM6 treets the battery and power in different way then WM5. First when you upgrade to wm6 and start it first time it assumes that battery is full (the instruction says that you should charge your battery before uploding new ROM). If the battery was not fully charged then you have a problem. WM6 registers the point of current while starting first time and assumes that this level represents the fully charged batteryl. Then it is programmed for consumption of power according to processor cycles, so after such and such time of use of your device it should reach certain level of power. If your battery was not charged full at the start then it will always show false percantage.
The solution is to fully charge the battery (possibly using the way described in some post above) and then reload the ROM once more.
Of cource when you buy a new battery, WM6 registers this (each battery has unic number) and creats new pattern for this battery. That is way it is so importatnt to properly charge the new battery when you load it first time.
Hope this is helpful.
Click to expand...
Click to collapse
uhh...not true...
try to flash you phone at 50% charge...when you boot your battery will still be at 50%

astraman said:
Dears,
i used to read about this issue in the forum again and again.....so i desided to wrote this post....everyone was claming the battery is the reason....OK do not belive this.....it is the rom.....i used the wm6 for sometime and i was facing the same problem....and when my carrier started the 3G i had to switch back to wm5.....and now my device never turns off before i get notified that my battery level is too low it about 10% of the battery....so if you do not belive me just do this test....switch back to wm5...i am using now Hilme 3.5 v1.3.1
regards
Click to expand...
Click to collapse
Not so Dears
i have what the american will say as 20/20 and the rst of the world will say as 6\6 corrected vision.
i can read normal 12 pt text pretty well..
and apart from that what you claim is...well NOT TRUE

Battery Life..+ Micro SD slot dead? [yeap again]

Hello all i have seen those threads about battery life but i beleive i have the worst..!
My battery last from fully charged condition in about 10 minutes of reading rss news!
It is rubbish it is also this shi* after flash. . .
anyone has a nice solution? or knows why is this happening?
i am a bit afraid of bying a new battery, because this may continue.
I dont know why vox is draining so much.
Second problem is that i cant get any micro sd wo work on it...!
It is really awfull cause vox has very little flash memory...
Please Give as many advices as you can i would be really gratefull!
Friendly Akuma.
Edit: sometime it hard shut down and then gives me false baterry indicate...

I was experimenting with battery life since mine was quickly falling down from 100 to around 75-80% within 15-30 minutes without much using the phone. My observations are as under:
1) Radio 4.1.13.47 seems to be the best in terms of battery use and call quality.
2) while charging I noticed the progress bar under "Power management" menu in settings. What I found is it suddenly shot to 100% (full) from around 80-85 clearly indiacting false charge.
3) To combat this I used my vox for sometime and it quickly dropped below 80% and then I again put it to charge. This time it charged normally for say upto 90-95% and again jumped to 100%
4) I again used it to drop the charge below90% and recharged.
5) This was continued till actually the battery was charged to 100% in normal spped. The experiment took some time.
6) Now I observe that the battery is much much stable and doesn't drain quickly and behaves like a normal battery should do.
7) Regarding battery showing inflated level after hard shut down, I think this is a problem with vox (or windows mobile?) and I also suffer from this.
Anyway you can try my method for battery charging and report any improvement if you find.

many thanks i will do some testing and try this re-charging method and i'll post my results!

One more thing I observed - Operamini 4.1/4.2beta consumes huge power - almost 1% gone every 2-3 minutes. Better if ucweb is used. I have just downloaded ucweb 6.1 for smartphones (English ver) and testing. Hope Ucweb will help to conserve battery better.
If you wish to test, link below.
http://forum.ucweb.com/viewthread.php?tid=226&extra=page=1

and some other things are that if you have windiows update automatic it runs as a process and using your ram.
i found out that rss is too
anyway you can check out your processes and some disable automatic update for them to stop running.
i hard reset and it got better i will do some further testing with you battery trick.

Don't try Ucweb for smartphone. The device is freezing.

Fuze Pathetic Battery Life

I know this has been covered in many other threads but they seem to be fragmented into some suggestions for specific problems. Researching, following and applying the information, tips and software some have suggested I am still getting nowhere. My battery dies in a very short period of time - something like 4-6 hours.
I have installated, executed / implemented many of the suggestions and procedures here and on fuze-mobility to extend battery life. These are representative. I think there have been probably more but I cannot remember them.
HTC Power Management
SD Card Battery Saver
Taskmgr - to kill / stop Activiesync (replog.exec) from continuously cycling
Advanced Configuration Tool to turn on and off 3G
Registry Edit modifications on both the Fuze and associated laptop related to Activesync Update cycles
Activesync - added new server, made timing manual, deleted server.
Charging processes - Letting battery run all the way down to below 10%
Lowering brightness on my screen
I have ordered and am waiting for an extended battery for the Fuze.
The only thing I see is when viewing what is executing via the Taskmgr CPU Usage panel, I see that most of the time the Idle process is executing. (75+%). Although I have read some threads where folks have said this is good because nothing else is draining your power, just because the process says "idle" does not seem to me to be doing nothing..it is still cranking through and using cycles to go through its designated activities.
Is there a way to indicate the interval when the idle process cycles?
Anyone have this same situation? Any suggestions?

That sounds very bad. Most complaints are about it being less than a day, noy 4-6 hours.
Have you contacted HTC/your supplier to get a replacement battery?
Also, idle is not a process, it's the absence of a process...

I'm not an expert on the ARM architecture, but idle processes are processes that use the CPU when all other processes are waiting for something or when there are no other processes running. They don't necessarily do anything constructive (they essentially just 'mind' the CPU until another process needs it), but they often feed the CPU with power-saving instructions. In conclusion, ignore it - it's not causing any problems and there's no point in fiddling with it.
That sort of a battery life is absolutely ridiculous, and you've clearly had a good go at increasing it, so I my best guess would be that it's defective.

Thanks for the quick responses.
I would still like to investigate the "idle" process angle. As long as something accesses the CPU, cycles are being executed and power is being used. Depending on what the "idle" process is doing with the 75+% "time" it has control of the CPU lots of power could be being used / drained.
Not sure how to go about this yet but I'm sure there is a way to find out what is going on during the "idle" process time holding the CPU.
If anyone know please share.....

Wow, it seems like the battey life on these things just keeps getting worse and worse. I remember going from the Hermes to the Kaiser and thinking how much worse the battery life was on the Kaiser.
The features keep increasing and batteries are having a hard time keeping up, I think.

there is alot to blame here. the good news there is a fix for almost every culprit.
1st....touch flow 3d. this thing demands alot of battery life. Not too mention its always running. Att has also seem to have added a few things to the touch flo interface that may have had an impact on this as well.
2nd....the applications these days seem to be getting bigger and bigger every few months. its not uncommon to see an app eating up 7 to 10 mb of ram. jivetalk...opera...the new aim??? the thing about this....the more ram an app takes up, the more batt power is consumes.
by the way...this is not a problem native to windows mobile...take a look at Google's g1....the batt life on that phone is even worse than your stock fuze...and after i've been digging through the phone....i found out all the apps are over 5 mb....madness! Also, the iphone has had this problem....and still does. but the iphone doesn't allow for background processing....so large programs running in the background aren't really that much of an issue.
3rd...att! in a noble attempt to cram the fuze with everything under the hood and give it the title it truly deserve (a phone capable of doing everything) they've weighed the os down with crap ware.
4th...the att radio that ships with the phone....its horrid. you'd never belive how much better some of the other radios are vs. the shipped att radio. its almost ridiculous that att would ship the phone with such a poor radio.
5th....htc. The batt in the phone is no bigger than the one offered in the tilt. But lets keep in mind, the same size batt now has to power faster processor....more ram...and a brighter more high res screen. Why they didnt up the power of the batt? who the hell knows...i guess to keep the phone nice a small...but its def a trade off.
I want you to try a cooked rom....try romeos 1.4 or the new proven.....change your radio to the shipped orange....make sure you spl before doing both.
and post back. im sure you'll have a different experience.

wrjp said:
Thanks for the quick responses.
I would still like to investigate the "idle" process angle. As long as something accesses the CPU, cycles are being executed and power is being used. Depending on what the "idle" process is doing with the 75+% "time" it has control of the CPU lots of power could be being used / drained.
Not sure how to go about this yet but I'm sure there is a way to find out what is going on during the "idle" process time holding the CPU.
If anyone know please share.....
Click to expand...
Click to collapse
I'm going to save you a ton of wasted hours in your life....or at least give you something else to waste those hours on. Stop the witch hunt on the "Idle" process. Open up the task manager on your desktop/laptop and look for the Idle process on there. If you pay attention (and do a little guessing), you'll see that the idle process consumes the remaining percentage of the CPU after the other applications have had their cut, however if you look at the total usage, you'll see that it doesn't include the Idle process.
There's a reason for this. It's lying to you....
There is no "Idle" process, it's just a way for the operating system to indicate how much processing power is not being used by applications. There's certainly something going on during those empty cycles, but it's operations that the core of the operating system is doing. Another poster mentioned that one of the things it's doing is sending power-saving instructions, which is basically true (but it's more in the form of telling the processor that there's nothing to do and letting it decide to save power).
The idle process cannot go away, and the closer you get it to 100% the better (relatively speaking, as it means you're doing nothing with the phone and removed any cool features it had). As long as the phone is on there's going to be at least a trickle of power going through the processor so the core of the operating system (i.e. Kernel) can perform it's necessary actions...just like the brain or heart does in your own body, even at rest they are still working a little bit.
Truthfully, I think you're barking up the wrong tree with your battery issues. I've got a Fuze also, and the ONLY time that I saw the battery die in 6 hours was when I was talking on it for about 3 1/2 or 4 hours in one afternoon. Otherwise, that thing, even on the stock rom, has given me nothing like the trouble your describing. I've flashed NATF's rom onto it (didn't like ROMeOS that much, just felt a little too laggy for me) and the new Austrailian radio .20M1 and the battery life seems even better. I don't think you're doing something wrong, I think you've got a lemon phone. Return it to the store complaining about the battery life on it not matching that of any of the other Fuze's you've seen anybody else using, then get a new one and try that out.

4-6 hours? Consider yourself lucky. I can get that if I don't touch the phone and no one calls. If I use the phone as a normal person might, I can get 2 hours. I don't even consider it a mobile phone. It's stays plugged into something all day.

momojopoe said:
4-6 hours? Consider yourself lucky. I can get that if I don't touch the phone and no one calls. If I use the phone as a normal person might, I can get 2 hours. I don't even consider it a mobile phone. It's stays plugged into something all day.
Click to expand...
Click to collapse
You have a faulty battery or you don't know how to set up the phone. I'm also using HTC Raphael, and battery lasts 1,5 days with lots of usage. I think that you should search xda for battery tips&tricks, like lowering backlight, turning off WIFI, BT and other. Also, there might be a problem with the ROM and Radio you're using.

The battery was exchanged...twice...the poor battery life was present with nothing but stock apps and all the tips and tricks you suggest were tried, and then some...the problem is endemic with the fuze...I figure as much as I paid I shouldn't have to jump through all the hoops with 3rd party new roms etc. just to get my phone to work like it should...the battery is piece of crap

Hmmm, in that case it could be faulty device - there are plenty of people on Raphael subforum that are using Fuze and battery lasts for most of them 1-2 days.

Whos got Extended battery on there Att Fuze ?
Is it worth the bulk
& which one to get ?
18,00 / 2,000 diff kinds i see
with diff company

[Q] How can you make the battery last longer??

Is there a tweak out there that stops the stupid battery from guzzling? Im tired of charing it constantly and I swear it takes hours and hours to charge it back to full power. The thing cant last longer than a day without loosing power I cant stand it. Whats making it use all that power? I thought maybe if I switch wireless it would help but I didnt notice a difference.

I can get 2 days out of my battery.
I let it drain to 1% and then stick it on charge over night. When i get up the battery will be at 100% and then 30 minutes later down to 90% but it settles down after that.
I do not have wifi and bluetooth on all the time, just when I need to.

sORRY DOUBLE POST................

Archangel22 said:
Is there a tweak out there that stops the stupid battery from guzzling? Iam tired of charging it constantly and I swear it takes hours and hours to charge it back to full power. The thing cant last longer than a day without loosing power I cant stand it. Whats making it use all that power? I thought maybe if I switch wireless it would help but I didnt notice a difference.
Click to expand...
Click to collapse
I don't understand people telling battery lost for 2 days..... even if we keep phone idle it will lose power in 24 hrs i believe....try like this try to use ROM with out manila & with manila once you will know the difference other than that there is some tips to save battery in Energy ROM thread in 3 rd 0r 4th post ..

4 days normal usage.
Manila2, GSM
15 minutes call, 6~10 text message, sync exchange, 30 minute ebook reading per day

If I build rom myself from the kitchen. It usually runs for 2-3 days.
However, in most cases when I try decent cooked ROM, for example, Energy - battery drains in about 5 hours. That's been the case with other cooked roms as well.
I suspect that some popular configuration change done by cooks causes battery to drain in certain environments. Would be nice to find out which change is that.

Processes and services often place a strain on the life of the battery; add to the mix a buggy service or application that further shortens battery life and one has an unusable device.
Another habit that can shorten Li-ON battery life is full discharges - near 0%. One of the members put out a thread a while back on research he/she had done on batteries - worth the read if you haven't already.
Cheers,

alexnoalex said:
If I build rom myself from the kitchen. It usually runs for 2-3 days.
However, in most cases when I try decent cooked ROM, for example, Energy - battery drains in about 5 hours. That's been the case with other cooked roms as well.
I suspect that some popular configuration change done by cooks causes battery to drain in certain environments. Would be nice to find out which change is that.
Click to expand...
Click to collapse
I just had the same experience, cooked for the first time and my battery was better than it has ever been!
Since then I have flashed to RRE 21731 6.3 and it seems my battery has stayed the same (Brilliant, 2 Days no problem).
The only thing ive done differently is I have used the new UK Voda rom as my Stock Rom that i flash before flashing custom, and i believe this may have something to do with it...What, I don't Know.
I also believe changing the Radio After a flash can affect battery life, I always try to flash a new radio before a Custom rom.
I have wondered for some time wether the European Touch Pro is slightly different to the US Fuze in its hardware, Since most Cooked Roms are configured for the Fuze maybe that is what it is?
maybe we will find out..One Day

turn off 3G and you will get much better battery.

Get a Blackberry Bold. My phone has been on for 2 days, sent around 150 texts, got in 150, I'm at 85%

ukjock said:
I can get 2 days out of my battery.
I let it drain to 1% and then stick it on charge over night. When i get up the battery will be at 100% and then 30 minutes later down to 90% but it settles down after that.
I do not have wifi and bluetooth on all the time, just when I need to.
Click to expand...
Click to collapse
That will ****-up your battery, you should never let it drain to 1%, just charge it when you have the time, preferably before it drains to about 20%.

I guess it all depends on the eye of the beholder, I come from the Diamond part of XDA, and we are lucky to get 24 hours on the Diam.
I was happpyyyyy with my new TP battery life -compared to Diam that is-
But ya, turning of 3g and being picky about processes and back light helps.
Greets to all.

Search the development and Hacking thread for Windows Long Life/save your gonads. Chainfire is developing a neat application to automatically switch from 3G when not needed. I tried an early version and it seemed to significantly increase my battery life.

Check my sig....it tells you how to deal with Li-ion batteries...

battery stuff on my site
Check out chapter 17. I cover this pretty thoroughly.

Archangel22 said:
Is there a tweak out there that stops the stupid battery from guzzling? Im tired of charing it constantly and I swear it takes hours and hours to charge it back to full power. The thing cant last longer than a day without loosing power I cant stand it. Whats making it use all that power? I thought maybe if I switch wireless it would help but I didnt notice a difference.
Click to expand...
Click to collapse
An app that may help is Advanced Task manager, it has a widget to end all running processes/tasks which i tap before putting mine to sleep about 1000+ times a day it seems. go in and exclude ones you may want to exclude always and then its as simple as 1 click. as everyone else said, no gps,wifi,3g when not 100% necessary. also, get widget "toggle disply" from rounded labs and keep your screen completely dim (not like you can't see it...), being able to make it bright when you step outdoors. Also, toggle backlight app for root users keeps the pesky keyboard backlight off when you don't want it on (suggest making keyboard shortcut for quick toggle). last but not least because i'm sure theres plenty more, but yesterday i switched to cyanogen's newest stable ROM and it seems to be much more effective than any other i have tried in the means of saving battery life. had wifi on after a 98% charge for about an hour and a half (30mn usage) and it only went down to 91%... wow. "and that's all, i have to say, about tha-aat"- Forrest Gump

Firstly I don't think this is the right sub-forum for this question since it's not a specific ROM question.
Secondly, try nueDynamicClock, if you use the right settings, you'll extend your batt life by at least 1/2 a day if not more.

alexnoalex said:
If I build rom myself from the kitchen. It usually runs for 2-3 days.
However, in most cases when I try decent cooked ROM, for example, Energy - battery drains in about 5 hours. That's been the case with other cooked roms as well.
I suspect that some popular configuration change done by cooks causes battery to drain in certain environments. Would be nice to find out which change is that.
Click to expand...
Click to collapse
It's really very simple. Flash an awesome rom, and the battery burns and burns. Flash a rom you hate, and the battery lasts forever. Don't over-think it.

hi guys.
i was eager to start up this discussion and am glad to find it here itself.
even am really finiky about battery.
tried alot of thing but cudnt find any spcl tweaks.
though i came across some registries from advanced config and other wise also but they seem to be more worse.
;IMPROVE BATTERY PERFORMANCE
[HKEY_LOCAL_MACHINE\Comm\AsyncMac1\Parms]
“DisablePowerManagement”=dword:0
[HKEY_LOCAL_MACHINE\Comm\Irsir1\Parms]
“DisablePowerManagement”=dword:0
[HKEY_LOCAL_MACHINE\Comm\PPTP1\Parms]
“DisablePowerManagement”=dword:0
[HKEY_LOCAL_MACHINE\Comm\L2TP1\Parms]
“DisablePowerManagement”=dword:0
when i use these tweaks the power consumption of my rom reached to 4.112 volts(as per power detect) which otherwise without these tweaks is 3.992 at startup.
more power consumption i guess means less battery i guess.
and even if its not still these tweaks as per my usage show bad results.
why so?
and arnt there spcl application which can detect the packages which might consume more battery, as i have over 50 packages in my rom and it'll hell to check which eats more.

Some tweaks I do
I have also found for me that disabling these things in advanced config also helps.
Performances
> File System cache: Disabled
> File System filter cache: Disabled
> Glyph Cache: 32kb (advised) I'm not sure if disabling this one is a good idea. I like having a little bit of glyph cache on my device.
Light senor
> Light sensor polling: Disabled.
*Note: If you want to still have light sensor on (this means the auto backlight feature) I would set the:
> Light sensor polling interval: 2000. This will make it poll every 2 seconds instead of every .2 seconds. I would even try setting it to 5000.
The backlight will make a huge difference on how long you battery will last. The brighter it is the more the battery needs to light up that screen. If you turn off the polling all together it will make the battery last longer.
Also running fancy UI apps will also deplete the battery more. Just common sense really as another poster alluded to earlier. The more things you have running and sucking up memory the more battery it will consume. If you disable TF3D or other apps such as this you will get your battery to last longer. Given that these devices are meant to have these types of programs on them you will have to weigh the options of how much you really want to "tone down" your devices to get the most out of your battery.
Also different radios will cause you battery to last longer. I suggest to everybody that they try different radios to see which ones last longer. Also people who live on the edge of 3G and EDGE area will cause the battery to drain faster as it constantly switches in and out of 3G coverage.
WMLongLife is a great app if you don't need 3G while you phone is just sitting in you pocket. It works great for me and when I want to use 3G I simply launch opera and the program will automatically enable 3G once again.
There are many things that you can do to improve your battery life. I encourage everybody to find what is best for them given what they use there device for and try and test things out. The best way to tell which works best for you is to simply try it out for yourself.
**NOTE** I also set all ROMs that I flash with a page pool of 0. I don't know if this has any real effect on battery life but it does seem to make my battery last a little bit longer. Not sure if this is a placebo affect though.