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....
I'm currently running the XM6r3 ROM, and my battery life is less than half of what it was with WM5. Anyone else notice this? I'm thinking it might be related to the weather panel app.
First, did you flash an official rom before you upgraded to XM6r3? If you have a corrupted Extended ROM, this has been shown to cause battery life that goes down very quickly.
Second, Yes, other apps you put on that are constantly accessing the network and such can cause battery life to go down faster. Did you have WeatherPanel on WM5? DO you do Push email (and how often is it setup to check / push)? Are you running BatteryStatus and overclocking? That definetly pulls more on the battery.
What Radio are you using on your phone? Newer radios (2.47, 2.61, and 2.69) all pull more on the battery (IMO) than the stock 2.25 radios from T-Mobile and Cingular. I think 2.19 is probably the most efficient (but also doesn't have as good of reception for some, but seems to work well for me).
When I first started messing with custom roms here, first AKU 3.3 (so WM5) and then WM6 roms, I would gripe about less battery life. Then it hit me, I'm using my phone WAY more than I was when I was on stock WM5 as it was so unreliable for me on the official roms, and now the phone does so much more. I do WAY more with my phone now with these custom roms. So yeah, battery life is going to go down faster as the phone is now being used all the time.
Also, I do think most of the custom WM6 roms do use more battery, but look at how much more they are doing by default.
If you really want to do a comparison, then build a WM6 rom that looks just like an official WM5 and don't use the phone anymore than you did with WM5 (same apps, etc). I think you will find the battery life is much closer in that case (but you won't be happy since its not overclocked, missing great apps you are now used to, etc)...
I'm experiencing the same issues...with only 2 or 3 days of the iphone theme, with Slide2Unlock and WisBar, my battery barely makes it 18 hours.
I'm going to try the suggestion of flashing it back to original and them just the latest WM6 (screw the iphone stuff).
I do take into effect that I use it more than I did before. I did not have weather panel with wm5, and I also use battery status. I only recently started overclocking it. I also use direct push with our exchange server.
I flashed it with the T-Mobile rom before upgrading. The radio is 2.25.11.
I guess it just comes with the territory I'm going to have get in the habit of charging it more often, because I like it WAY more than WM5.
mfrazzz said:
First, did you flash an official rom before you upgraded to XM6r3? If you have a corrupted Extended ROM, this has been shown to cause battery life that goes down very quickly.
Second, Yes, other apps you put on that are constantly accessing the network and such can cause battery life to go down faster. Did you have WeatherPanel on WM5? DO you do Push email (and how often is it setup to check / push)? Are you running BatteryStatus and overclocking? That definetly pulls more on the battery.
What Radio are you using on your phone? Newer radios (2.47, 2.61, and 2.69) all pull more on the battery (IMO) than the stock 2.25 radios from T-Mobile and Cingular. I think 2.19 is probably the most efficient (but also doesn't have as good of reception for some, but seems to work well for me).
When I first started messing with custom roms here, first AKU 3.3 (so WM5) and then WM6 roms, I would gripe about less battery life. Then it hit me, I'm using my phone WAY more than I was when I was on stock WM5 as it was so unreliable for me on the official roms, and now the phone does so much more. I do WAY more with my phone now with these custom roms. So yeah, battery life is going to go down faster as the phone is now being used all the time.
Also, I do think most of the custom WM6 roms do use more battery, but look at how much more they are doing by default.
If you really want to do a comparison, then build a WM6 rom that looks just like an official WM5 and don't use the phone anymore than you did with WM5 (same apps, etc). I think you will find the battery life is much closer in that case (but you won't be happy since its not overclocked, missing great apps you are now used to, etc)...
Click to expand...
Click to collapse
Very hypothetical and analytical description of the Battery consumption problem being faced,cudn't be explained more elaborately .
Stock wm5 Roms never had any such applications as new wm6 custom Roms offer.
secondly over clocking will definitely effect the battery power.
I noticed too. Probably the file connmrg.exe is taking all the CPU power, that's why the battery's life is so worse. Batterystatus gives a constantly 100% CPU usage display...
IF you see battery status showing 100% cpu usage you have some other issue. Mine is only at 100% when I start an app or doing heavy work on it. Otherwise it idles back under 195Mhz most of the time with CPUscalar for me. Also depends on what ROM you are running and what apps you have added.
No Problem with battery
I have been using this rom since it was released and have had no problems at all with the battery life.
Is it possible to damage the battery by installing a new ROM
Is it possible to damage the battery by installing a new ROM? My 8125 battery was fine on old wm6 ROM, but after I installed XM6r3 (and yes, I did install t-mobile os before to clean it), my battery level goes through the floor.
I managed to charge it to over 50% and installed stock cingular rom, and with no extra applications installed, just the virgin cingular software, BT/wifi not enabled, just gsm radio I still see a drop of few % a minute! So basically, my phone is effectively cannot be detached from charger or my battery will drain very fast and loose ability to start os and begin charging again in the phone.
I can see (using wizard service tool) some cingular customization stuff on the hidden extended rom, does this mean extended rom is not a cause of this? Should I use format ROM tool in WST? (sorry for probably stupid questions)
Is there any way to check that it is indeed the battery being shot and not some obscure software issue? I find it hard to believe that good battery can go bad exactly at the same time as OS upgrade, I am hoping I am missing some obvious software fix
I believe its something else because my girlfriend calls me every morning and I take it out of the charger. I talk to her for a couple minutes 5 minutes tops and I hang up I look at batterystatus and it says 79% left tops. This is OD crazy I don't know if its the rom or the battery. I don't feel like paying 40 bux for a battery and same thing happens. I am currently installing a new rom I am gonna try this for acouple days and see what happens. I only noticed it for one rom but that rom I used for two to three weeks straight I didn't notice with the other roms because I never kept them for more then a day.
Strange enough (Battery life)
Strange enough before reading this post I thought that my phone's battery is dying. But know I can say that its definitely this XM6r3 ROM has some problem. To be precise there is definitely some application that eats the battery. As sometime my battery works fine and other time it just drain. If anyone can work on what application is eating the battery would be appreciated.
Rest the ROM is great.
Harwant
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 also saw faster battery drain on my Qtek 9000 after I installed TOMAL V8, so decided to check the actual current drain on the ROMs.
I used BatteryStatusExt.1.05.CAB to show the current in mA. I installed a ROM, reset, then installed the BatteryStatus app and set it to show power consumption as a Today plugin, with 1 second refresh. Then I waited for the backlight to turn off and the number (mA) to settle. I did the test with a 4Gb card inserted, with a SIM card in a GSM network. All other radio was off: BT, WLAN, IR. I used radio 1.10.3 (incorrectly labeled 1.09 on xda-dev's FTP!).
I didn't check standby figures - they can be seen by checking the number immediately after getting out of standby, as the BatteryStatus plugin takes a while to refresh
rdosti v11
140-160mA but in 3G mode !!! I couldn't get it to switch to GSM
TOMAL v8
~120mA
SHIVAM310
80-100mA
minhanhtran (ROM UNI G3 OS 5.2.20270) :
~128 mAh
So there is a difference! And that's with no additional apps but BatteryStatus, and with backlight off.
With 120mA, a 1600 mAh battery will drain to 0% in 1600mAh/120mAh = 13.3 hours, with 80mA it will go to 0% in 20 hours....
So with my oldish battery I will wait for rdosti to fix the "Notes not working" bug on his SHIVAM release
I think the difference could be noticed also with applications running, but it is harder to test.
With Ranju 7.7 and 3G my battery drains in just a few hours, never lasted a whole day. 13-odd hours - I should be so lucky. New battery, BTW.
Confused
I used batter status and show my drain is 642mA but my battery last for about a day (4-6) Hours of actual using.
Battery 1600 mA
Rom Tomal 8
Radio 1.15
enigma1nz said:
With Ranju 7.7 and 3G my battery drains in just a few hours, never lasted a whole day. 13-odd hours - I should be so lucky. New battery, BTW.
Click to expand...
Click to collapse
I'd check the drain in mA and compare it with another ROM - SHIVAM310 for example (comparing a clean install of both ROMs + BatteryStatus + waiting for a few minutes with backlight off). Backup the entire system to a card first, of course.
Also, try a task manager to see if a process is keeping the CPU busy.
No with all versions
I´m using v7.6 and my battery, which is the original since aug 05, last me aprox. 24-30 hrs. Using wifi and surfing 1 h, gprs, 4 h, bluetooth 2 h and ocasionall music.
I must say that tested v.7.7 and noticed a faster drain of my battery and return to 7.6!
And is the perfect combination of stability (Performance) and speed
Congrats Tomal! so far the best ROM
Cheers to all
I have tried several 6.1 ROMS all flashes done with battery at 100% and tested with several ROMS that was the same whichever battery I tried. For example tomals 7.7 would eat 18% of a 1600ma battery with it closed and idling overnight for 8 hours, this reduced to 14% if cache was disabled and the performance application options removed. This compares to the best battery consumption I got from Shivam 310 with office, SPB shell and voice command added that lost 3-4% in the 8 hours overnight. Needless to say I am sticking with the latter as it is more in line with the quoted life in the manual for all activities.
blazzr said:
140-160mA but in 3G mode !!! I couldn't get it to switch to GSM
TOMAL v8
~120mA
SHIVAM310
80-100mA
minhanhtran (ROM UNI G3 OS 5.2.20270) :
~128 mAh
Click to expand...
Click to collapse
I've installed BatteryStatusExt.1.05.CAB to test the current ROM I'm using (minhanhtran ) but I alway get 181mA, this is independent of the configuration e.g. GSM on or off, WiFi on or off and so on, so there is something I'm missing or what the hell is happening... any hints?
Marco.
Jmp_3f8h said:
I've installed BatteryStatusExt.1.05.CAB to test the current ROM I'm using (minhanhtran ) but I alway get 181mA, this is independent of the configuration e.g. GSM on or off, WiFi on or off and so on, so there is something I'm missing or what the hell is happening... any hints?
Marco.
Click to expand...
Click to collapse
Same here only 181 and sometime 642
radio version for power consumption it's important
rod555 said:
radio version for power consumption it's important
Click to expand...
Click to collapse
You make a very important point here
Would be good if some knowledge member of this forum adivise us which radio has better battery performance
Cheers
pls use different radio version
anybody had tried different radio version for battery consumption ?
I don't have the meters but, 1.09 last my battery longer than 1.11
I tried 1.04 1.09 1.15 and 1.18 with the T 7.7 rom and it didnt make any real difference to battery at all I also tried 1.09 and 1.15 with shivam 310 and both gave me 3 times the battery life of tomals rom with the same radio so i am of the opinion the key thing is the right rom flashed while the battery is at 100%
I´m using 1.08 and my battery (the original since 2005) lasts 24-30 hour
I can´t ask more of my old battery so I suppose this radio is a good one
I 've the Tomal's one. With a normal use my SPV M5000 is up for 3-4 days.
Every time a cooker distrubutes a new rom there is someone yelling for an abnormal power consumption.
Real!
With new Rom the battery goes down very fast... cause the owner is testing everything, install all utilities & inutilities, and after 4-6 hours the battery line is down. After some days, with normal use, the Universal is going good again.
my consumation is about 180mA in batterystatusext105
I tried nev pdaviet 20273 rom and original 20270. It is nearly same. I have brightness on 2 degree and 128 MB ram. I think, ram is more depend on power consumation
The reason Tomal's ROMs seem to use more battery power, is because they come with the CPU overclocking option enabled to 624Mhz by default, and some of the power saving options in Schaps advanced config are disabled.
If you reverse the above, they should be the same as the other ROMs in terms of battery consumption, if not even better.
Hi,
I had a strange problem today.
I went to sleep with 50% battery left on my Touch Pro. About 7 hours later the alarm didn't go off and I found out that the battery was dead. Something seems to be draining it. Any ideas what?
PS. I downgraded to latest official radio ROM yesterday cause the one in my signature had problems with GPS.
aerozolic said:
Hi,
I had a strange problem today.
I went to sleep with 50% battery left on my Touch Pro. About 7 hours later the alarm didn't go off and I found out that the battery was dead. Something seems to be draining it. Any ideas what?
PS. I downgraded to latest official radio ROM yesterday cause the one in my signature had problems with GPS.
Click to expand...
Click to collapse
check to make sure no programs are running, do you got any apps you installed running in the background? also do you have a lock screen app like S2U2? thats known for battery leaks, and how about ur screen sleep settings? make sure to have Beam Connections unchecked and oh one thing, were you connected to data connections?
XERO_Racer said:
check to make sure no programs are running, do you got any apps you installed running in the background? also do you have a lock screen app like S2U2? thats known for battery leaks, and how about ur screen sleep settings? make sure to have Beam Connections unchecked and oh one thing, were you connected to data connections?
Click to expand...
Click to collapse
Nope, I didn't have any programs running at the time. I had G-Alarm configured to wake me. Haven't had any problems with G-Alarm before. I have the default screen sleep settings. I don't have S2U2 or anything like it. I'm not sure if I had data connection going at that time but I've never had problem like this before. 50% of battery going to 0% in about 7 hours in standby mode The battery used to last at least 5 days before.
Is it possible that with my custom rom (Gen.Y) the original radio ROM (1.11) might cause the drain?
I see that you're using the latest official radio with 1.14.25.05 rilphone.dll. I'm doing to try the same radio out. Do you have experiences 1.17.25.09 with 1.14.25.35 rilphone.dll?
aerozolic said:
Nope, I didn't have any programs running at the time. I had G-Alarm configured to wake me. Haven't had any problems with G-Alarm before. I have the default screen sleep settings. I don't have S2U2 or anything like it. I'm not sure if I had data connection going at that time but I've never had problem like this before. 50% of battery going to 0% in about 7 hours in standby mode The battery used to last at least 5 days before.
Is it possible that with my custom rom (Gen.Y) the original radio ROM (1.11) might cause the drain?
I see that you're using the latest official radio with 1.14.25.05 rilphone.dll. I'm doing to try the same radio out. Do you have experiences 1.17.25.09 with 1.14.25.35 rilphone.dll?
Click to expand...
Click to collapse
well g-alarm do had issues of battery leaks from what all of the posts im reading on and well try flashing the latest radio or 1.14.25.05 and for ur question regarding the 1.14.25.35 rilphone.dll i havent tried it yet i still have to try it but i have to say is that 1.14.25.05 dll are relatively close to 1.14.25.35 dll
XERO_Racer said:
well g-alarm do had issues of battery leaks from what all of the posts im reading on and well try flashing the latest radio or 1.14.25.05 and for ur question regarding the 1.14.25.35 rilphone.dll i havent tried it yet i still have to try it but i have to say is that 1.14.25.05 dll are relatively close to 1.14.25.35 dll
Click to expand...
Click to collapse
I think that the drain occured because i didn't have the right rilphone.dll installed for the 1.11 radio.
Tonight: 8 hours in standby mode took about 10% of battery. Maybe it's ok, but it still seems a bit too much for just standby. Or not?
aerozolic said:
I think that the drain occured because i didn't have the right rilphone.dll installed for the 1.11 radio.
Tonight: 8 hours in standby mode took about 10% of battery. Maybe it's ok, but it still seems a bit too much for just standby. Or not?
Click to expand...
Click to collapse
Well, let me try to help you. I have the latest official HTC ROM (30.8.2009.) with radio 1.14.25.05 and Manila 2.1 installed. When I go to sleep, I put my phone in flight mode. Eight ours later I have about the same battery level, sometimes decreased by 1%, not more.