Related
Hi, I'm a noob to undervolting here (just rooted and flashed Vanilla Froyo to my Defy a week ago, and I'm hoping to squeeze out as much battery life as I can); just some quick questions about undervolting that I haven't found answers to in other threads:
1) What exactly is "vsel" and how does it relate to the actual battery voltage? For example, even though I've changed the maximum voltage in setvsel and Milestone Overclock (down to about 45 vsel at 800 Mhz so far, haven't tried lower), the battery voltage reported by Spare Parts is still reading between 3800 mV and 4000 mV. Does this mean that setvsel/milestone aren't working or does a ~30% decrease in vsel *not* equal a 30% decrease in battery voltage?
2) If anyone else has undervolted their Defy, can they testify as to what kind of battery life improvements they've gotten? I've heard that custom ROMs are already fairly undervolted
If laptops are anything to go by.. laptops can be undervolted to make them run less hot, thereby extending their life. Though battery life is increased too, this increase is virtually negligible.
Since the limits of undervolting (and over/underclocking), are done on a per-cpu/gpu basis for computers, because they are not all exactly the same and may not work with the same non-default values, I think it's a bad idea to assume that phones will run without problems when using values only tested by people with a phone that is not yours.
If you want to undervolt/over- or underclock, test your device, find out the lowest/highest values and then inrease or decrease that value, to have a safety margin, do not copy someone elses' settings.
A common issue with undervolting on 2.1 (at least with me on 2.1) is that if the minimum clock speed is below 300 mhz, it takes around 3-5 sec to actually respond to incomming call on your defy when defy is on stand-by mode.
Undervolting + Ondemand made my battery work at 23ºC vs +29ºC
I did not wrote down numbers, but battery life increased AT LEAST in 8 hours.
My values
vsel 1; 18 -300
vsel 2; 33 - 600
vsel 3; 43 - 800
(-15 points each value VS factory values)
Removing bloatware, root apps, autostart at boot apps, widgets (they autostart too) etc. or freezing them with "antitek app manager"
Decreased phone memory ussage from 140Mib to 80Mib; Also decreased cpu ussage from 10%-15% average idle to just 1%-5%
Apps / Widgets / Many System preinstalled apps, are autoloaded when phone is turned on, and they run 24/7. waste of resources and app auto killers just aren't good enough, coz apps reload themselves, you have to remove them or freeze them.
fortunely modders are realeasing their custom roms with most of this optimizations
45 vsel
using milestone oc I got 1ghz @ 45vsel from the day I got it I have owned the device for 1 1/2 months now not one single problem but it depends from device to device I must have a bin'd cpu
Ok EVO nation!
Here's my scenario. I'm running a fresh flash of MikFroyo 4.5 and Netarchy's 4.2.2. cfs nohavs. With almost nothing else running on the phone.
So far I've seen a the stand-by battery drain hover around 100-180mA, with an occasional dip into the 50's. The CPU usage is always just below 10%.
I've seen references all over the forums about users claiming low 40's and idle CPU usage around 3% and I'm wondering WHY I'm not able to achieve the same thing.
Now I've done all of the standard battery tweaks, tried various kernels, and can remember a time last fall when one kernel I flashed seemed to give me incredible battery life.
So...Let's hear what your average stand-by battery drain and CPU usage is.
(And any thoughts you might have about my battery situation)
Get 4.3.2 with more havs. It'll drop the voltages nice and low. When I had mikfroyo with netarchy 4.3.2 with setcpu screen off at 128mhz I had about 30-40 idle drain.
Sent from my (insert daily ROM name here) Evo 4g
I wouldn't worry too much about your idle current draw unless you're having a battery drain problem. The issue with the current draw methodology is it's taking the current consumption that instant in time. Unfortunately, you can't monitor instantaneous current draw without affecting the reading itself.
If you idle for an hour or two (or 5), and your battery only goes down 0-1%, i'd say you're in good shape. Also, it helps if you specify what software you're using to monitor these values with? Mine is based on Battery Monitor Widget (bmw).
Edit: There's more to cpu tweaks than just kernels. Along with kernels, there are governors, and then there are governor parameters. Each will directly affect your battery consumption and cpu load.
I'm definitely having a battery drain problem. At idle, it's falling 3-4% per hour, according to the Battery Monitor Widget.
I've got SetCPU set to 128min/998 max with Conservative scaling, and I've one profile enabled for Screen off settings of 128min/128max.
I did notice that when I try to set the min cpu to 128, the clock speeds jump all over the place. But if I set the min cpu to 245 it quiets right down.
Perhaps I a have CPU that's become finicky?
fsmith3x said:
I'm definitely having a battery drain problem. At idle, it's falling 3-4% per hour, according to the Battery Monitor Widget.
I've got SetCPU set to 128min/998 max with Conservative scaling, and I've one profile enabled for Screen off settings of 128min/128max.
I did notice that when I try to set the min cpu to 128, the clock speeds jump all over the place. But if I set the min cpu to 245 it quiets right down.
Perhaps I a have CPU that's become finicky?
Click to expand...
Click to collapse
I had an issue similar to this where my battery would drain quicker than usual when the CPU min was set at 128 and having a screen off profile of 128/128. I think the problem stems from just setting the CPU way too low and having it use more power to bring the phone 'up to speed'. From my personal experience, I think you'll still be just as good setting your mins to 245, but by all means you're more than welcome to continue experimenting with 128
First off, you need to determine if you have a wake lock issue. Use "spare parts" to see. Look in the battery history, partial wake lock section. It will show you what programs are causing wake lock, and what amount of time they are in a state of wake lock.
Example, my phone was last off the charger 42 hours ago (awake time 7h36m), battery still at 32%, and should last the remainder of the day so long as I don't do too much data. My two biggest wake lock listings are Android system at 1h26m, and my email at 20m.
All it takes is 1 misbehaved program, or even a particular setting within a program to cause wake lock. If that is the cause, then regardless of what your sleep settings are, the phone will still draw the battery down quickly.
You can also look in "/sys/devices/system/cpu/cpu0/cpufreq/stats" at the time_in_state file using a text viewer/editor. It will show how much each cpu frequency is being utilized. I don't recall what unit it's in. But the point here is that if your 128/245 Mhz values are lower than your upper mhz values, something is not right.
The governor parameters will control how much cpu swing is occurring under various load. That is, if you're reading an email, there's little reason for the cpu to be pegged at 998mhz. These parameters control the thresholds (contingent upon which governor is used) at which the cpu scales up or down.
Edit: Each value in time_in_state represent 10ms, or .01seconds. So multiple each value below by .01 to get actual time in seconds. If you notice, the total time in us equal to my awake time of 7h36m, not total uptime.
Mine looks like this
Code:
Mhz cycles seconds
128000 1264017 12640
245000 201083 2011
384000 72728 727
422400 4 0
460800 133450 1335
499200 0 0
537600 72174 722
576000 53479 535
614400 78771 788
652800 38230 382
691200 0 0
729600 87258 873
768000 29579 296
806400 98273 983
844800 18476 185
883200 0 0
921600 599503 5995
960000 0 0
998400 2821 28
Total 2,749,846 27,498
27498seconds = 458min = 7.63h or 7h37m.
gpz1100 said:
Example, my phone was last off the charger 42 hours ago (awake time 7h36m), battery still at 32%, and should last the remainder of the day so long as I don't do too much data. My two biggest wake lock listings are Android system at 1h26m, and my email at 20m.
Click to expand...
Click to collapse
gpz1100, Please describe your setup and usage. I'm curious to know how you're getting that kind of battery life.
Anyway....
Good morning gang!
I gave this a couple of days for the fresh install to settle in, and hopefully let it learn how to use the battery more efficiently. But it's still a power hungry beast.
Yesterday I calculated it's use ate 3.9% an hour, based on battery % / time unplugged.
Mind you, I made 2 short phone calls yesterday, and checked my Exchange mail a few times throughout the day. No Angry birds while I'm trying to sort out batter life.
It's still using 100-150mA in standby, and it seems like the governor (SetCPU) is working like it should.
Right now the battery is at 97% and has been off the charger for 1.5 hours. That's 2% an hour. Which isn't bad, but I doubt the average will be that low by the end of the day.
For those of you who like numbers, here's some stats for you. Do you see anything that raises any red flags?
Looking at Spare Parts, in the wake lock section, I see these values.
Android System: 9m9s
UID 10020: 54s
Facebook: 39s
Voicemail: 30s
Mail: 14s
Maps: 11s
Tasker: 9s
WidgeLocker: 6s
Other Usage...
Running: 36.1%
Screen on: 16.7%
Phone on: .9%
Wifi On: 100%
Wifi Running: 100%
The values from my 'stats' file:
128000 0
245000 84095
384000 20371
422400 9
460800 0
499200 127
537600 4743
576000 100
614400 9
652800 75
691200 4238
729600 0
768000 23
806400 1358
844800 2439
883200 0
921600 0
960000 976
998400 18361
1036800 0
1075200 0
1113600 0
1152000 0
1190400 0
1228800 0
1267200 0
fsmith3x said:
gpz1100, Please describe your setup and usage. I'm curious to know how you're getting that kind of battery life.
Click to expand...
Click to collapse
My setup is as described in the sig. The only additions would include custom conservative governor settings of 80/55/10 % on the up/down/freq steps thresholds; min/max cpu of 128/921 Mhz respectively. I don't use setcpu, tasker, or anything similar. Background updates is on, but nothing is checked (no gmail, facebook, etc.). I used to have email push enabled (using k9 mail), but decided to turn off push altogether, and just poll the server manually when I need to check email when away - little reason to getting emails as they come in if I have access to a computer at the same time.
I have found that even with wifi, the quality of your voice signal drastically affects battery life. I'd say I have average signal, (3-4 bars most of the time) for voice. However, sprint provided an airave because data speed is terrible here. A byproduct of the airave is it provides excellent voice signal. So, just with that in place, consumption while the phone is sleeping/idling is reduced by a good 10-20% over connecting to the tower directly. I'd say most of my usage is voice, some texting/emailing, and on occasion, heavy browsing. No games or videos, no facebook/twitter. It's hard to quantify use, but I think that's the bulk of it.
Yesterday I calculated it's use ate 3.9% an hour, based on battery % / time unplugged.
Mind you, I made 2 short phone calls yesterday, and checked my Exchange mail a few times throughout the day. No Angry birds while I'm trying to sort out batter life.
It's still using 100-150mA in standby, and it seems like the governor (SetCPU) is working like it should.
Right now the battery is at 97% and has been off the charger for 1.5 hours. That's 2% an hour. Which isn't bad, but I doubt the average will be that low by the end of the day.
Click to expand...
Click to collapse
What you need to keep in mind, is that unless you're using an sbc kernel, your battery may or may not stay above 90% for too long after being removed from the charger. Unfortunately, battery consumption is not constant. Demand on the battery is changing depending on what the phone is doing. Also, 1.5 hrs really isn't a large enough time period to draw an accurate average from. Based on your cpu usage below, it indicates your device was actually on for 22 min.
Your wakelock numbers don't look bad, but the data is inconclusive. The question is, when these readings were taken, what was the up time, and what would you say was the time with the screen off (rough estimate is the diff between uptime and awake time). Leaving wifi on is a good idea, as it draws much less energy than using 3g.
One number that does seem surprising (assuming total run time of 1.5h's since removed from charger) is your running % of 36.1%. If the phone was not used during this time, that seems excessive. In fact, looking at the next value, screen on - 16.7%, would suggest that 20% of the awake time was when the screen was off.
I would start by disabling or uninstalling(if you use titanium backup, the FREEZE) tasker and widgetlocker. Running % - screen on % = % of time spent not sleeping even though the screen is off - things like receiving email, performing weather updates, etc...
For me, with Overclock.. it's EXCELLENT! I can have it in standby but still have background data going (push gmail, twitter apps, etc.) for days at a time and still have some juice left.
Just today with some admittedly light usage (but I did use it) I had battery use time of 12Hrs with over 70% left.
I'm using setvsel @
35 @ 400MHz
50 @ 800MHz
65 @ 1200MHz
CPU Icon is set to refresh every second and it's supposed to cap at Vsel 2 @ 10%. It's as stable as ever.. been running like this for weeks now. I'm taking note of how much I appreciate the excellent battery life I get because my Vibrant has been getting really bad lately.
Running Barebones 1.3 with
19 @ 300Mhz
35 @ 600MHz
52 @ 1000Mhz
Battery Life is excellent - more than 48h without recharging is no problem.
I get 2 days of standby with heavy texting,surfing over wifi,calling and some gaming. DEFY battery performance is one the best amongst all Android phones.
el*Loco said:
Running Barebones 1.3 with
19 @ 300Mhz
35 @ 600MHz
52 @ 1000Mhz
Battery Life is excellent - more than 48h without recharging is no problem.
Click to expand...
Click to collapse
Undervolting your cpu can harm your hardware real badly. I've had my defy stopped working and shut down completely in the past so i won't recommend you OC or UV
EDIT: tho i still undervolt but 19 vsel is too low for 300 mhz, raise it upto 26 or so
Yes, 19 vsel maybe too low, at least in my case. When I ran the stability test, anything less than 24 would hang the phone after some 10 minutes. 24 is fine in my case but I set it at 26 to give a little more juice.
LOL. Why the hell, should undervolting harm the cpu? Undervolting improves your cpu's lifetime, instead! Less voltage means less stress (heat) and less leak currents for the cpu.
Well, it's true that you might have some instability issues, when the voltage is too low. As soon as you experience so, you can raise the voltage a little, until you have a stable cpu. I've been using undervolting for my PC's CPUs for several years.
PS: I'm on [email protected], [email protected], [email protected]
Never had any problems with my settings, some in this forum use even lower voltages.
mine is
[email protected]
[email protected]
[email protected]
I use wifi quite a lot. But still the battery backup is ok compared to my previous phones!
Running on Pays 5.0
[email protected]
[email protected]
[email protected]
I have to charge every two days.
running on pay 3.1
setvsel:
350/22
700/38
1100/56
48h no problem, record is 80h on moderate use
The battery life on the Defy is absolutely amazing.
I can easily get between 2 and 3 days of normal usage and somewhere in the region of 4-5 if I use it very little.
I reckon if I switched off 3G, had the brightness down as low as possible and generally tried not to use the phone much, I could push a week.
Sadly, my Defy is 'in the shop' just now, damned earpiece.
What do you guys run on the background? I probably able to get 1.5 days on normal usage. Even after charging and no usage, I lose about 10 % after an hour or so.
lanfearxt said:
What do you guys run on the background? I probably able to get 1.5 days on normal usage. Even after charging and no usage, I lose about 10 % after an hour or so.
Click to expand...
Click to collapse
It is impossible to get 1.5 day if defy uses 10% for 1 hour standby. Defy rounds 95% to 100%, and 94% to 90%. So it is possible that an apparent 10% drop is actually a 1% drop. You may install Motocharge to see the battery in 1% increment.
I'm happy to hear everyone getting excellent battery life. The DEFY is a truly unique Android phone.. I'm just afraid that us stateside won't get devices like this because of AT&T... the Bravo is a step below the DEFY just because it doesn't share the same faux-rugged water resistant build. I'm glad T-Mobile picked this one up, overclocked it's only a bit slower than my Vibrant in most operations.
Well I did a Quadrant benchmark 'standoff' with a colleague of mine which has a Samsung Galaxy S [EU version of the Vibrant] and I beat him with over 250 points [the Galaxy S did 975, my Defy did 1334], both running Froyo and the Defy being non-overclocked.
I've also noticed that his Galaxy S tends to hang & stutter from time to time. Regarding battery life, he carries his charger with him at all times, I do not, 'nuff said.
I also get ~1.5days of battery life.
I'm able to squeeze more than 80 hours of usage on a single charge running PaYs 5.0. Light to moderate use of WiFi/Data/GPS/BT, no background syncs and most apps firewalled except through WiFi.
SetVsel:
18/300
32/700
58/1100
ABC_Universal said:
It is impossible to get 1.5 day if defy uses 10% for 1 hour standby. Defy rounds 95% to 100%, and 94% to 90%. So it is possible that an apparent 10% drop is actually a 1% drop. You may install Motocharge to see the battery in 1% increment.
Click to expand...
Click to collapse
i used circle battery widget and it does shows 1% increments. after 90%, it slows down in terms of usage.
i also forgot to mention that my defy sometime runs pretty hot at 35-38C, which i think accelerates the discharge
what about autobrightness? if is set it on, the battery drains much faster.
For me, with undervolt (800/46;600/30;300/18) I can use my phone to make calls, send sms, surf the web, run some apps, and run one a two games.
After 24h of that usage, I have 50% remaining.
a strange thing happened to me (sorry for my English):
Yesterday I installed the camera 360 that did not work it gave some error. Last night when I went to sleep (1-1.30) had 50% battery, in the morning (7.30-8) phone was dead. I put the phone to recharge, from 11 to 3 o'clock phone has reached 30% of battery so i put the phone to recharge again. Until 10 pm the phone has reached again 30% of battery so I decided to give him a factory reset. With 30% i did 100+ app backups with titanium pro and I gave factory reset, after the phone restore from factory reset surprise the battery show 60% ??? I did restore 100+ app and battery show 50%, I played about a half hour and still 50% battery??? what the hell happened??? 360 camera app has to do with rapid battery discharge???
- I use advance Task Manager droidwall, light <10%, original rom only rooted
- anyway Battery discharge I think is caused by the signal GSM of my operator's.
- anyway in the night i decided to kill the traffic and by that the battery shouldn't discharged hardly over night. right?
(Q) sometimes the touch screen it freezes in games so I have to put the phone in standby and come out of standby, and then the touch screen works again ... this happens to you to?
I know unrooted desire z devices always work at 800mhz. My device is set to 245mhz min and 1400mhz max (interactive or smartass governor). It sometimes causes my device to wake up a bit late. I wonder how long time my battery goes if I set my device at min 800 mhz and max 1200 or 1400 mhz... Did anyone try this clock speeds?
Deadly Sto(R)m said:
I know unrooted desire z devices always work at 800mhz. My device is set to 245mhz min and 1400mhz max (interactive or smartass governor). It sometimes causes my device to wake up a bit late. I wonder how long time my battery goes if I set my device at min 800 mhz and max 1200 or 1400 mhz... Did anyone try this clock speeds?
Click to expand...
Click to collapse
That's way too low of a min speed, just bump it up to the next (I think it's 386) and you should see noticable improvement.
I'd also suggest the ondemand gov; since it only ramps up to the top speed when needed, then drops it back down again, you should get a bit better battery life.
Sent from my HTC Vision using XDA App
OriginalGabriel said:
That's way too low of a min speed, just bump it up to the next (I think it's 386) and you should see noticable improvement.
I'd also suggest the ondemand gov; since it only ramps up to the top speed when needed, then drops it back down again, you should get a bit better battery life.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
i read ondemand and conservative governors are od, so using interactive or smartass are better then using others. I will try min 368 mhz but am not sure if it works...
What are you trying to accomplish by messing with the clock speed? Leave it alone at default. Performance difference is NEGLIGIBLE (bottleneck is elsewhere), and all you'll accomplish is eating the battery and burning it up with excessive heat caused by excessive clock.
dhkr234 said:
What are you trying to accomplish by messing with the clock speed? Leave it alone at default. Performance difference is NEGLIGIBLE (bottleneck is elsewhere), and all you'll accomplish is eating the battery and burning it up with excessive heat caused by excessive clock.
Click to expand...
Click to collapse
First of all, I would like to thank you for your comments.
People don't do anything to access root if they don't want to mess device. I am one of them and want to have a device which both has performance and visuality. You offered me to not to change clock speeds. But we know HTC Desire Z is scheduled to work at 800mhz everytime (default). My opinion is just to set minimum clock speed to 800 mhz or something like this. If my device was burn by this clock speed, it was already dead.
Today i tried this clock speed (min 614, max 1382) and during the day it didn't heat up. Moreover, 8 hours passed, i played NFS for about 1,5 hour, made some call and 30 percent of battery left. It seems this clockspeeds doesn't cause battery drain or i couldn't feel it...
EDIT: 13 hours passes, 16 percent battery left (I made minimum 30 minutes of call)
Hello,
i hope you can help me.
I'm using MildWild 4.3 based on Oxygen 2.3.2 with Thalamus kernel.
When my desire is on stand-by modus, it consumes 1 % per 45-55 minutes. Because of that i'm very glad.
But when i use my desire, p.e when iuse play store without anything downloading it consumes 1 % per 2-4 minutes.
My question is: is that normal? Or must i change any settings or an another kernel etc???
Can nobody help me?
I don't know why you don't reply? This is my second thread, and the first thread I've not recieved any answers either.
Well, it is 18 hours past after unplugging my phone and I have 71 %. But I'm used my phone 15 minutes after unplugging.
Is there all right?
it seems maybe a little high. screen should be the biggest consumer of battery once you start using your phone.
however i don't know your screen brightness and age of battery.
in standby seems ok, you can use something like 'betterbatterystats' to double check no app is keeping it in partial wakelock.
inbuilt kernel, or stock thalamus kernel (in my sig) should be fine. personally i use inbuilt cpu settings ondemand 245 - 998MHz, no other apps needed, and i think battery use is fine.
for what it's worth, here's another response to another battery use query...
Yes ,Its normal
eddiehk6 said:
it seems maybe a little high. screen should be the biggest consumer of battery once you start using your phone.
however i don't know your screen brightness and age of battery.
in standby seems ok, you can use something like 'betterbatterystats' to double check no app is keeping it in partial wakelock.
inbuilt kernel, or stock thalamus kernel (in my sig) should be fine. personally i use inbuilt cpu settings ondemand 245 - 998MHz, no other apps needed, and i think battery use is fine.
for what it's worth, here's another response to another battery use query...
Click to expand...
Click to collapse
hi
in the android phone its normal battery usage , but for better test u can change CPU governor to smartassv2.
don't forget battery Consumption mostly depend on kind of Battery and thats Amper
thanks for the answers,
I'm using thalamus kernel, 2.6.35.14_r-stable.
Screen brightness is automatic and i've bought my battery 1-1,5 years ago, original desire battery.
I also have Better Bacttery Stats, by partial wakelocks i have since unplugged:
Activity Manager-Launch with 2m 6s and 318 counts.
Alarm Manager with 1m 7s and 1244 counts.
wifi with 10s and 501 counts
sleep broadcoast with 8s and 460 counts
and other programs.
Since unplugged: 10 h
deep spleep: 8h 7m
Awake: 1h 54m
Screen on: 1h 43m
KWL: 8m 20s
PWL: 6m 9s
İs there all right, and I don't know which programs are these.
and under cpu governor I don't have smartassv2, i have powersave, ondemand, performance. Min CPU frequency 245 MHz, max CPU frequency 998 MHz, and what is smartassv2?
And can you please explain in a bit simple English?
My English isn't good.
Can you post a screenshot of your battery usage graph?
I'm my case, almost all the power consuption comes from the screen (Never under 50%).. I have to use very low brightness if I want the battery life to last.
Best regards.
http://s14.directupload.net/file/d/2944/dn53ux3u_png.htm
How i said, it drains by using my desire. On standby, its all right.
Sent from my HTC Desire using xda app-developers app
Lonely_Boz said:
thanks for the answers,
I'm using thalamus kernel, 2.6.35.14_r-stable.
Screen brightness is automatic and i've bought my battery 1-1,5 years ago, original desire battery.
I also have Better Bacttery Stats, by partial wakelocks i have since unplugged:
Activity Manager-Launch with 2m 6s and 318 counts.
Alarm Manager with 1m 7s and 1244 counts.
wifi with 10s and 501 counts
sleep broadcoast with 8s and 460 counts
and other programs.
Since unplugged: 10 h
deep spleep: 8h 7m
Awake: 1h 54m
Screen on: 1h 43m
KWL: 8m 20s
PWL: 6m 9s
İs there all right, and I don't know which programs are these.
and under cpu governor I don't have smartassv2, i have powersave, ondemand, performance. Min CPU frequency 245 MHz, max CPU frequency 998 MHz, and what is smartassv2?
And can you please explain in a bit simple English?
My English isn't good.
Click to expand...
Click to collapse
looks fine, you can see that there is no app keeping the phone awake for very long...max 2m 6s.
smartassV2 is another CPU governor. whether it is better than ondemand will require you to measure the drain for similar activities, though personally i don't think it's worth it.
screen is still meant to consume the most battery as long as you are using the phone, regardless of govenor. no change of rom/kernel/touch screen phone will change this fact.
i can suggest turning off auto brightness and using a lower manual one. have a widget to toggle between low and high when you need to (many in google play).
Thanks for the answer. It is possible, the Battery is defect or it doesn't function well because of his age? Is there an app which measure the battery if it is all right with the battery?
Sent from my HTC Desire using xda app-developers app
theres lots of battery apps in the market but they only really tell ya basic things, health, voltage, battery percent etc.
Sent from my HTC Desire
Well... I've seen things with the same rom, same kernel and different results... mainly due apps keeping the phone awake, but in your scenario is not that bad. I loose 3% overnight with CM 5 MW's version which is awesome, but once i start using my phone.. let me see. I've lost 10% with about 20 minutes of browsing and 20 minutes of gaming... I'm using ManU kernel which is pretty good with battery life, but not compatible with oxygen version of MildWild.
Do a Nandroid backup and try CM version, just to check the differences if you're up to it.
Also, flash ManU kernel afterwards
Let us know if you need help, you have a drain but not awfully bad. However 1% every couple of minutes seems a bit too much .
Well, i don't think that there is a ROM problem. Many people using this ROM have good results than me.
Nevertheless, i will try MW CM 5. After testing i will write here.
I think, there is a battery problem .
Even if it is, you're not spending money without ruling out software issues right?
MidnightDevil said:
Even if it is, you're not spending money without ruling out software issues right?
Click to expand...
Click to collapse
I'm sorry, but unfortunately i didn' understand you what you mean
Well, i tested a lot of ROM's (MW, ICS Nikez Sandvold Oxy) and i've notice that there isn't a kernel or ROM problem, it's just battery problem.
My battery is still working, but it doesn't work well. I've bought the battery 1,5 years ago, and this is my second battery (genuine HTC battery).
I've also problems with my first battery.
I don't know, should i buy a new battery? If yes, which battery do yu suggest, genuine or another?
And i don't have any good experiences with HTC batteries. Perhaps i didn't use the batteries well.