Related
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....
*ORIGINAL TEXT EDITED AND UPDATED*
I have flashed at least half of the custom ROMs released for my G3 CID-unlocked MDA for the last 15 months. It has given me great respect for the efforts of kyphur, faria, molski, anchillus, and others. I have spent too much time, as well, following events here due to the 2 issues that leave my “Wizard” performing less than its best – the radio rom (stuck on 2.19.11 because of missed calls/messages) and battery life.
I do use a few add-on apps, but the main 3 I add to most ROMs that lack them are: batterystatus, todayagenda, and smartskey. I’ve tried placing the blame on battery life on overclocking (via batterystatus, I’ve run mine at all sorts of different speeds with and without cpuscaler, w/wo boost, w/wo extra indicators, etc.). I have updated, removed, reinstalled, backflashed (to ensure a extended rom was present, as many said this would fix the battery life issue) apps and ROMs and nothing has fixed the battery issue. Seemingly ever since WM6, I have been able to get about 24-36 hours out of my phone, about half of what I got before. Last night I went back to Molski’s Wm5 Aku 3.3 Crossbow ROM and over the course of several hours, battery life held firm. Then I added my push e-mail account and synced my mail for the first time (I have a lot of mail) which took like 10-15 minutes, and I dropped 10% of my charge (all levels reported per batterstatus, whatever the bias). Whoa, I thought. Well, I will chalk it up to a squirrelly initial indication of 100% because it sometimes seems to show that when it has just been unplugged from the charger, even if it soon resets to a more accurate value. Anyway, this morning the battery issue seemed to still be a problem. Could it be push e-mail, I thought?
So, I turned off the immediate send/receive, and my battery life improved a great deal. Wait, I thought, could it actually not be push e-mail (which would stink, because I NEED that), but the SD card access when it stores my attachments to SD causing the drain (this was suggested some time ago, but I couldn’t recreate at the time, because the CABs supplied didn’t resolve the issue)? I decided to check. I changed the push settings back to immediate (true push, not SMS triggered) and told the ROM to store attachments in main memory again. And guess what? My battery drain issue appears to be fixed!
I really hope this may be the case. It wouldn’t surprise me to learn that all the power users here are setting the option to store to SD card, or running apps off the SD card.
* MORE UPDATES*
I have been testing this theory for several days, and I can say with absolute certainty that the above fixed my battery issue. Some (WM6 and WM5) ROMs are better than others in this respect, but it is definitely fixed - life improved in all of them. I am currently using Business Edition v2 and it often shows 24mA consumption in BS. I am now seeing consumption under standby conditions of just a hair over 1% per hour, and excellent life even when I am working on it, using the phone, etc. And this is with bluetooth on, push e-mail, etc.
I admit I was surprised at the relatively limited response when I first posted, because this appears to be a gripe for a lot of people. Maybe I overestimated that....if it helps a post here would be nice, if only so others see it and can help themselves.
Thanks again to all the ROM cookers!
This could in fact improve the battery status for many people, and if so congrats on an awesome find.
However I do not have a data plan (being the poor college student that I am), therefore do not use push email. My battery life is similar to yours and I can stretch to maybe near 48hrs if there is very very little use of my wizard....
But I am glad we are on the right track
Zack
This might be it
I never thought of that. You just sparked something though. On both my HTC Wizard and my old MPx200, which has a full size SD card slot, I remember when I let the power completely drain out that one of the first things I couldn't access was the SD Card slot. I remember being surprised when I couldn't find it.
Nice Job! I'm willing to test with you but I will have to wait for two more weeks. I'm a freshman in high school and have final exams.
Good Looks
Good find, I went to do this and it turns out that I had it already set to that . Also, when not using your phone turn the screen off and while you are in call turn the screen off by pressing the power button up top. Also, changing the brightness of the screen has really helped my battery out and the fact that I had a bad extended rom. with all that said and your finding my battery has been great. and AHHH finals week here for me.. I feel for you guys.. Mine start tomorrow! BOOOO
You mean you ever made it more then 24 hours?
My Wizard needs charged every night. It's usually chirping by the time I get home from work
I do have push email set up though so I attributed that to Push.
Battery life is a bit of a bummer on these devices, but that's why I have a charger at home, in the car, and at my office, haha
Push definitely hurts battery life a bit, and that should be expected, but I have been using that for about a year and I really suspect that it is the combination of the original batteries getting "old" at 1 year and this SD card issue that is causing the accelerated decline. I am still optimistic, and my drain is still not too bad, so hopefully I can just learn to live with "fetching" my attachments to SD only when I need to see them (vs. having Messaging pull all of them automatically) to reclaim several hours to a day of battery life.
I can make it 24 hours. Usually at the end of the day say 10 or 11 my battery life is till about 50%. I tested it that night and didnt have to recharge till around 4pm the next day.
I'm sure that vettejock99 is on the right track for some users. My mail program (Xpress Mail) doesn't use the SD, so this wasn't an issue for me - only GPRS usage. When I use the card / applications that access the card, my consumption goes way up. I can see where an app that always runs in the bg and constantly reading/writing to the SD could have a huge effect on battery life, in addition to hardware that's left on - such as Wifi or beam.
-Matt
I don't know what u guys are talking about here. I use the Faria Vanilla ROM and my battery lasts for 96 hours, it's amazing! But when used other roms I never had my battery last less than 48 hours.
One more suggestion about the battry life: always close all active programs. They really drain the battery. I tested it luanching 15 applications at a time, and guess what happened? The battery lost 50% in 15 minutes. So, that might be one of the other factors...
Oh, and here is one last thing. The battery drain is also high when the phone network is unavailable. If u leave your phone somewhere where there is no network signal it will automatically try to search the network every n minutes. So, that also causes huge power drain.
I wonder if this little SD card thing affecting the battery drain isn't noticed when surfing the net. I set the temp folder on the sd card for IE...just a thought
anichillus said:
I wonder it this little SD card thing affecting the battery drain isn't noticed when surfing the net. I set the temp folder on the sd card for IE...just a thought
Click to expand...
Click to collapse
I dunno, maybe (as was speculated some time ago) the power management is turned on/off by one activity such as surfing w/cache to SD and handled differently when writing attachments......
By way of an update, I ALMOST added earlier today that my consumption was creeping back up again, though it still seemed to be about 20% lower (better) than before. I decided to uninstall TodayAgenda and BatteryStatus from the Molski ROM (the versions integrated into it), even though that would make it less desirable to use. The drain still seemed to be creeping up. I was troubled. Then I realized I had installed Today Commander earlier today to ensure I had an extended rom, which I did in fact have (check that box). Well, I installed it to the SD card - so I uninstalled it. And I removed my SD card. And once again, it appears that my consumption is back down. I have used 1% in the last hour, and that is something I have been unable to accomplish in some time. So.....I could be wrong, but I really think this SD card thing has something to do with it.
I remain hopeful this is it, and there is a way we can fix it, or that I can ultimately leave the SD card in at least, and install apps to memory (as there is plenty of room for my needs) and only pull attachments to SD as needed.
Anyone else looking into this?
last bump - updated OP
I thought I remembered seeing a registry hack, or something to that effect, which turned off the polling of the SD slot. I think it was supposed to dramatically improve battery drain times. I'll take a look around for the hack, maybe I'm just dreaming though.
Pastamancer said:
I thought I remembered seeing a registry hack, or something to that effect, which turned off the polling of the SD slot. I think it was supposed to dramatically improve battery drain times. I'll take a look around for the hack, maybe I'm just dreaming though.
Click to expand...
Click to collapse
You did, it's out there. Didn't help mine, though. I think that is because the polling does represent some drain, but it appears the actual writing/reading drain is the substantial part.
look here i think i solve this problem
http://forum.xda-developers.com/showthread.php?p=1259754#post1259754
increasing paging pool of the ROM causes the battery to roll down heavilly.. this was proven a long time ago in himalaya (xda II) section)..
but ofcourse this isnt only the problem..
-dOUbleOfour
i dnt know what my problem is. i charge my fone all night to 100% and take it out the charger only when am leaving for work. when i get on the train its a 40minute ride to work. i only listen to windows media player and by the time i get to work my battery is like 50% or less.
so i bought a new battery today. i will update tomorrow
boto said:
look here i think i solve this problem
http://forum.xda-developers.com/showthread.php?p=1259754#post1259754
Click to expand...
Click to collapse
That is a cause, but as I said, I had an extended rom, not corrupted, and still saw the drain, as have others. So folks need to ensure they have an uncorrupted extended rom, and they need to fix the SD issue in some way or they will likely have battery drain with many ROMs.
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
Hi guys, first post here. This place seems to be pretty informative when it comes to WM6 on these phones, so good job everyone on the guides and cookbooks and everything that has gone to it so far. I spent a lot of time searching over which ROM to load, and I ended up trying a XM6R3 version cookbook of WM6 (the basic less feature filled version). It seems pretty neat and my complaints are minor except for one thing, which I am wondering if it is my device specific, and that is battery life. When my Wiz (Cingular 8125) was running WM5 stock version, the battery life was incredible. I never have blue tooth enabled, and rarely enable wifi, but I used the internet all of the time and was constantly checking and sending email through the phone.
Now with WM6, I am lucky if it lasts 1/2 a day, and I have cut down my internet usage (so far I think it is related to that, but I am not sure yet). Today I pulled my phone off the charger at 8AM, and it was just about 100% dead by 10AM. This is a pretty new Wiz too (it was a warrantee replacement received maybe 2 months ago). I will admit that I emailed an attachment out twice this morning before it died that was 23k, but still it isn't THAT much and that battery life is pretty extreme... And of course even though it dies a heck of a lot faster, it still charges very slow. Charging through USB all day after dieing and it isn't to 50% yet...
Does anyone else have this problem? Again I have tried searching and haven't found anything out so far. Here are my version numbers:
IPL 3.08
SPL 3.08
Radio 2.69.11
OS 10.1.0.811
I also applied the Cingular Radio.cab fix that I saw on the site. I practicely leave no program running if at all possible. I really don't want to go back to WM5, and am willing to switch to a different WM6 if I need to. I love the features in WM6, as I said my complaints are really low. Thanks a lot guys. My email is [email protected] to contact me directly if you have a definite solution.
Jason
Did you flash back to the latest officiel release before flashing the WM6 Rom?
You might also want to reflash XM6 or try a different Rom (I've encountered no problem at all with NBD and TNT Roms, so...)
Cheers
Try to flash the empty extended rom.
Some users(including me) reported that a corrupt Extended Rom heavily affects the battery life. (You can check this easy by BatteryStatus; If the CPU stays at 20-30% all the time, then that's the cause)
Re-flash your OEM rom. My cpu was running at 25% at idle, I reflashed my OEM rom and then back to the WM6 rom and now the idle cpu is at 1 to 2%. I messed with my extended rom a while back and never should have touched it. Others have had their extended roms become corrupt on their own.
Jeff
edit: I use the same WM6 rom as you and feel it is probably the best overall WM6 rom out there. I use the full version though.
Your battery reaches end of life, to buy new one!
anichillus said:
Try to flash the empty extended rom.
Some users(including me) reported that a corrupt Extended Rom heavily affects the battery life. (You can check this easy by BatteryStatus; If the CPU stays at 20-30% all the time, then that's the cause)
Click to expand...
Click to collapse
How do you see this percentage in BS?
I'm using the last freeware version but can't seem to access that???
Edit: Is it the little icon on the left under the battery? If so, mine remains at a solid 100% and Handyswitcher, which also allows to see CPU usage says "idle process"=> 100%...
Do I have to flash a blank Ext Rom?
If so, can you please tell me how?
Thanks
Edit2: Maybe I should also mention that in idle mode, BS says 155mA as concerns the powerdrain...
To see cpu usage, open battery status and select options, select the indicator tab on the bottom and then check show more indicators. With pocket breeze, BS, and the backlight on my wizard draws ~100mA and the cpu is ~1-3% while at idle. I have seen the battery draw as low as 57mA but I never watch my battery draw as it seems to last two days now since fixing the extended rom issue vs 1/2 to 1 day.
I don't know about flashing a blank rom, I just did what everyone else said and flashed my OEM rom back which also flashes the extended rom back to OEM.
Well I also flashed back to the last official release before flashing tnt 1921, so I guess my ext Rom is OK...
Alright about to start the backup & reflash to the latest official rom. Thanks for all of the replies guys, and about the battery being bad I doubt it, or else it would have been bad back under WM5.
All your problem is the corrupted extended rom. Your battery drain goes back to normal when you flash an official rom because Official roms also have Extended rom , along with IPL, SPL , Radio and OS.
I suggested to flash only the empty extended rom, because that's the best way, being super fast (1-2 minutes) and you won't loose any of your data...and won't have to flash 2x times(the official rom and then the custom one) plus add your programs once again.
The extended rom should be either a simple nk.nbf(which you copy in the RUU and flash right away) or an *.nb(which you either convert to a nk.nbf or add it along with OS.nb into a OS+Extended Rom nk.nbf)
I have noticed that it changed my IPL & SPL versions. Do I need to change these again before going to WM6 again? I think I will go re-read the faq...
anichillus said:
The extended rom should be either a simple nk.nbf(which you copy in the RUU and flash right away) or an *.nb(which you either convert to a nk.nbf or add it along with OS.nb into a OS+Extended Rom nk.nbf)
Click to expand...
Click to collapse
What do you mean by copying it into the RUU? Do I just put it into the folder where the RUU program exists? Or do I have to rebuild the RUU with only the nk.nbf file?
I flashed back to the release WM5 rom, then flashed the T-Mo 2.26 rom, then flashed XM6r3aLite again, and I have the feeling that the issue is still there (my battery was 100% maybe 2 hours ago, however it is down to 70% now). In the past no matter what I was doing I could never drain it that fast except maybe playing MP3s. The only thing that I have done is sync'ed with my companies' Exchange server and copy some files from my storage card to the main memory.
Again, thanks a lot,
Jason
sweet JESUS...
my point of view.
procedure:
- choose normal(i mean good) rom,
- flash it,
- discharge battery to zero(or just near to zero),
- plug it into charger,
- load to full
- make soft reset.
these stupid bs mah paranoia is useless.
turn it OFF and STOP looking!
if you flash rom @ 70%, you will get 100% after, but it is 70-x(flash time) %.
machine is fooled and only thing you can do is learn it again by full discharge/recharge procedure.
and before someone will say: bull**** - i never had batt problem after using that procedure(3 days is minimum).
p.s. software may be reason too, sometimes.
few people had mainboard issues too(battery was gone fast without reason) - if so, replace mainboard(i hope you not need this).
extrom deletions/broken extrom may lead to drain too(almost always).
try to turn beam off(some roms have it on),
try to turn "today timeout" off(some believe that it "may" be something with it) in /menustart/settings/today.
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