Related
Hello all,
it seems there is more to complain about than this video driver nightmare. I'm adding two issues in separate threads. This one deals with the GPS module and resulting battery drain. I observed it right after installing the first GPS software and searched for help nearly everywhere, and I found some more hints pointing at short battery uptimes after GPS was used. Here's how it works:
- access the GPS port (GPS software, "OziExplorer" or the like)
- stop the access
- end all software tasks
- put device into standby
- Due to an additional current draw of approx. 50mA the battery will be empty within a day --- in standby. The GPS unit does _NOT_ return into a low power state, no matter how much time passed.
- Only a complete power-off or pressing the soft reset button ends this condition.
Installing a battery monitor software (BatteryStatus) confirmed an additional current draw of approx. 50mA after the mentioned GPS port access.
I found a promising registry entry HKLM/System/CurrentControlSet/GPS Intermediate Driver/Drivers/SleepOnNoData but again it does not seem to have the least of an effect (default is 1000).
HTC support claimed "they know of no issues in conjunction with the Kaiser" - well at that point I was not even able to put my question. Which somehow tells me how serious these guys take their customers .
BusterTyTN
One thing I forgot: knowing that the GPS does not turn off, I use to apply a soft reset whenever I used a GPS software. Voilá, several days runtime until I have to recharge!
this confirms my suspicion...
now and then it happend that the battery of my tytn was empty in the morning. I never really proved that it happend after using gps, and looked for a thread here....well, here it is...
Others must have made the same observation.....
Today I succeeded submitting a bug report to HTC, at last... built a test setup, made measurements with a digital scope, documented everything. The problem can always be reproduced. There is a smooth, steady state current consumption of nearly 50mA after the GPS has been used, without any software running in the background. Until you soft reset the device.
I will let you know as soon as I have news on this one. Whoever can reproduce this, please add a note to this thread. This power management issue is getting more and more interesting.
BusterTyTN
Hm i must check that in my klaaiser last days i was always instaling something so manu soft restes have been made i'll test it now.
I can confirm that GPS activation seems to drain battery more.
I have installed the latest dutty rom, and have not installed tom tom.
So far I have had the phone on for 28 hours, and still have 40% of the battery.
Previously battery would die after 12 hours.
I am not sure now I want to install Tomtom.... ;-)
But I know I will not be able to resist....
what should my kaisers power usage be at on average, mine seems very high at an average of 250mW?
Good idea. Let's take typical power measurements and state them here. I will come back with some more values later on. I do not have my scope measurements within reach, and I am going to complete the picture with the help of "BatteryStatus". Here's what comes right out of my memory:
In standby, no background software, no communications etc.: next to nothing, 0 to 1mA / 0..3mW
Active, still no software or communications, just the "today" screen, brightness at the second lowest setting: ~180mW
BusterTyTN
I'm using the Garmin software for gps, and I don't seem to have te battery drain problem. with Garmin xt running 220 - 280 ma. Once I shut down Garmin xt it slowly drops, taking from 3 to 5 minutes, back to a normal 60 -70 ma. (1 -3 ma in standby.)
Good luck sorting this out.
Typical power data
Nakel, negative proof is just as good as positive. Well possible that there is a dependency on the ROM type / branding / OEM configuration, so maybe you're so kind to add the brand / type / ROM # of your device. And perhaps you can try GPSTest and check the battery current in standby again - just to exclude nasty side effects.
My device is the "Vodafone VPA compact V", ROM Version 1.56.162.5, Radio 1.27.12.11. No updates so far. Here comes its power consumption data, taken using "BatteryStatus". I observed the power display for a few minutes in each situation and tried to catch the lowest readouts. The individual sections were activated one by one. Sorry I forgot to check the current increase at full brightness, but I think that is of secondary interest here.
1. Pstby = 0..3mW (reference for the following)
2. Pon = 155..180 mW (reference, set to lowest brightness, no task running, didnt touch screen nor buttons)
3. Pon+20mW = 175..200 mW GSM phone logged in, no calls
4. Pon+5..10mW = 160..190 mW BT on, no link
5. Pon+130..400mW = 280..560 mW WLAN, no data transfers
6. Pon+850mW = 1000 mW GPS on, SW running (OziExplorer or GPSTest), with & w/o GPS fix
7. Pon+200mW = 340 mW On, after GPS access. Same situation as 2. otherwise.
8. Pstby+180 mW = 180mW standby, after GPS access. Same situation as 1.
9. Pon+380mW = 540 mW Mediaplayer running, 0%Volume
10. Pon+530mW = 680 mW 5% volume, internal speaker
11. Pon+260mW = 410 mW, 5% volume, display completely off
Scope readouts show very little battery current ripple (clean DC) in situations 1. and 8. Significant ripple in all other modes.
BusterTyTN
I've used both Pocket Streets and Fugawi and found that, if I use the "stop" or "close" GPS option in those applications, the GPS shuts down and I have no battery drain issue.
I think you're looking at a problem with an anti-social application rather than a Kaiser issue.
I'm running the stock AT&T ROM, but have upgraded the radio to 1.27.12.17
You have to make sure you close the GPS application and not just minimize it. If you minimize the GPS app that you are running the GPS will continue to stay on, draining the battery.
BusterTyTN said:
Nakel, negative proof is just as good as positive. Well possible that there is a dependency on the ROM type / branding / OEM configuration, so maybe you're so kind to add the brand / type / ROM # of your device.
BusterTyTN
Click to expand...
Click to collapse
AT&T Tilt
I'm using the standard At&T ROM without the added AT&T bloatware.
R 127.12.11
G 22.45.88.07H
D 1.57.00.00
Hopefully that will help solve the problem. Wish I could be of more help...
ray6 said:
You have to make sure you close the GPS application and not just minimize it. If you minimize the GPS app that you are running the GPS will continue to stay on, draining the battery.
Click to expand...
Click to collapse
Both of the applications I mentioned have features that specifically start and stop the GPS. They do not have to be closed to avoid battery drain issues.
I'll go ahead and add my numbers:
Before GPS:
Standby: <1mA
On and Active: ~85mA
GPS turned on (GPS Utilities): ~250mA Steady (450mA peak)
After terminating GPS software:
On and Active: ~80mA
Standby: <1mA
Running Alex's WM6.1 Beta 1 ROM, AT&T Tilt
Well I already saw quite a number of complaints out there, regarding quickly drained batteries, in similar circumstances. The problem is definitely there, I only have to find out the prone devices and/or the affected versions.
So anybody who can reproduce these findings, please contribute here, and do not forget your version numbers.
Thank you all
BusterTyTN
Dead battery after 6 hours of minimal use, i am not sure if it's the GPS's fault but i will do further testing
R 1.27.12.11
G 22.45.88.07H
D 1.56.00.00
I think I already wrote that in another thread on the same subject...
any road,
I had battery drain issues just twice: those times the phone completely drained the battery in a few hours... possibly more or less the 6 hours even dhob187 experienced.
I just re-charged the phone and had no more problems. I dunno why that happened but as it is not a common behaviour I'm not that worried.
In my experience I had no problems with GPS-battery relationship.
Rom: 1.56.408.5
Radio: 1.27.12.11
Protocol: 22.45.88.07H
According to MSDN the intermediate driver 'counts' the number of open connections to it. After all programs have closed their connection the driver shuts the gps down. When an program 'forgets' to close it's connection the driver doesn't shut down the driver. Could be an good idea to write an little program to check the status of the driver (with IOCTL_SERVICE_STATUS?) and/or start and stop the driver (IOCTL_SERVICE_START / IOCTL_SERVICE_STOP)
All i can tell is that the new Dutty rom Wm6.1 Beta1 is the best for your Batt. live !!!!
It's the best so far...
See my sig
This thread refers to cases where the HTC Kaiser (and probably other HTC phone models with the same built-in GPS chip, such as Polaris) sucks the battery empty within a single day, particularly during standby, particularly if all features of the phone are DISABLED, or after low usage. Another symptom may be a phone which unexpectedly did not come back to life, but operated normally after recharging. Yet another symptom is unusually short battery life through normal use. Note, this thread is not about limited battery endurance due to heavy usage.
*** Battery drain FAQ ***
How can I see whether my Kaiser is affected?
- A large percentage of HTC phones with Qualcomm chipset and internal GPS seems to suffer from the bug described here, some appear to be robust enough, likely depending on chip revisions. If you never ever use GPS, you are probably out of risk. If you use GPS at least occasionally, you should have a look at your phone, and closely. It is possible that an otherwise normal to heavy use of the phone conceals a basic, added current consumption which is what we are talking about here. In such a situation you may have got used to a certain battery endurance, which may be much higher under normal circumstances. So far I observed currents between 28 and 78 mA, depending on DUT and OS. Some users reported currents in excess of 100mA. Note, this added current does nothing for you, except accelerate your battery drain!
How to check this?
- Check the true standby current (see the following description). That simple.
How to measure the standby current?
- Clean up: switch all phone features off (GPS, Phone, Bluetooth, Media Player, really everything). Terminate all applications, use Task Manager to verify this. Make sure no processor intensive background tasks are running (standard installations should meet this requirement). Do NOT soft reset at this point!
- Put the phone in standby, and wait approx. 10 seconds. The phone needs a while to complete entering the standby though it appears to be off immediately.
- Now measure the current. Best and fastest way of doing it would be to have a current meter connected between your battery and your phone which gives you realtime readouts. Second to that is a suitable battery tool, such as "BatteryStatus", but you have to get used to the delayed current display (see post #4 for details). Using the software battery gauge, you should wait an additional 20 seconds or so to allow for the current capture, then reactivate from standby and take the lowest possible current readout.
- If the phone is in a good condition, the standby current must be in the range 1..3 mA, roughly. If you see a repeatable current well in excess of 20mA, your phone is in the BAD condition !!
- Another simple method is to leave the cleaned up phone in standby overnight. Next morning, soft reset your phone because the phone may have lost track of the battery capacity. Check whether the capacity dropped dramatically. And also check whether the phone feels warm to the touch.
How to reproduce the problem?
- Activate GPS until you get a fix. Probably receiving the first NMEA strings is good enough, but I have not verified this. GPSTest, HTC's GPS Tool or any navigation software does the job.
- Deactivate GPS. Just to be safe, terminate the GPS software, too.
- Check the standby current.
- The fault does not pop up always, so you may have to repeat these steps several times until it appears. The phones I tested usually catch fever after only one or two tries, but it is possible that you need to cycle through this procedure 5 or 10 times. Which is in the nature of intermittent bugs.
How to reset this nasty condition?
- Fault recovery is possible by continued on/off cycling of the GPS unit, similar to what provoked this fault.
- Activating the cellphone unit does also seem to cause the phone to return to a low consumption, but maybe not in all cases.
- Try to soft reset your phone, or to cycle the power to the phone (long press of the power button).
- If you really cannot get rid of the problem, back up your phone data, then execute a hard reset. BEFORE restoring the phone, load a battery gauge software and see whether the consumption is gone. If yes, some application is likely to cause your headaches.
After performing one of the above steps you may repeat the described current measurement, to confirm that the standby current is back in the normal range.
***********************
Original text:
I have reason to believe that all Kaiser models are prone to the "excessive standby current consumption" problem. I tried it on two original "VPA compact V" by Vodafone (= HTC Kaiser), using the original WM6, ROM 1.56.162.5, Radio 1.27.12.11. I gave a **** on warranty now, stepped up through HardSPL to "Duttys_Official_WM6.1_Rom_5.2.19716_UC.zip", Radio 1.64.08.21. The results are all the same: an excessive current consumption which can vary between 25 and 75 mA. Interestingly, the current is always the same in a specific setup, but varies between phones and operating systems. In the latest case, the same phone took 28mA under WM6, went up to 78mA under WM61. Consequence being, the battery will be sucked empty within a day or so, without obvious reason. The only mitigation is a reset, or a complete switch-off.
There is no application which could cause the current consumption, at least none I installed. It does not even matter which GPS application you used. The only active processes are (according to TaskManager, latest WM6.1 version, ".exe" omitted for the sake of ease): filesys, device, biotouch, gwes, shell32, cprog, services, quickdial, connmgr, mediahubmini, taskmgr, htcactionscreen, sapsettings, aplauncher, quickmenu, nk. I repeat: ALL applications properly terminated, ALL internal units are OFF (WLAN, Bluetooth, Phone, GPRS, GPS, Camera, Media Player etc. - really NOTHING).
Before anybody prematurely states that these findings can not be reproduced: the problem is unlikely to appear if you switch on the GPS for a couple of NMEA strings, then off again (though it did already). If need be, you have to leave it on for a while, play a bit, walk around a bit and so on. Take your time testing it _thoroughly_, really. I cannot tell when the fault actually appears, and it may not come up immediately because it seems somewhat sporadic in nature - but take my word, it will, I observed this issue for a long enough time. I can only repeat myself: I am sure there is something wrong with the power management in the GPS driver.
Anybody, feel free to contribute, but PLEASE avoid funny statements like "you have to shut down all programs", "WLAN can take up lots of energy" and so on. And before you express doubts just because there are not quite many people out there who come to the same conclusions, think again. Without going into details, most users are simply not in the position to come to the correct conclusions.
BusterTyTN
OK, making it sticky; depending on the feedback, I (or other mods) may unstick it in the future.
How do you measure current while in standby? When it's running, I can see current usage in the battery monitor of AE Button plus. Just after wake up from standby, it shows 16ma. A few seconds later it jumps to 385ma and then settles at 140ma.
I'm using 3.02.DKv0.0 6.1 Lite Rom from akadonny.
@ Menneisyys: thanx!
@ tdusen:
there's two ways of doing it. First, I do not know whether "AE Button plus" works in a similar way, but "BatteryStatus" (also included in Dutty's newest WM61 release) has some seconds of a delay in the current display. I assume this is because of an averaging process running in the background which collects current samples over a certain period of time, or soemthing to this effect. Anyway; you have to keep your in standby for at least 10..20 seconds, then reactivate the PDA. If it's still showing a high current, tip on the current/power display a few times, in most cases this helps getting the low standby current. You simply have to try to catch the lowest reading, right after reactivation from standby. If everything is OK, you will get a current reading of a few mA, maximum (in most cases 1..3 mA), assuming you shut every feature of your phone off.
The other way is also the verification of the "BatteryStatus" method. I built a current shunt test probe and measured the battery current directly. Attached is a screenshot taken with my digital scope, which shows typical results (see above -- moved to post #1).
In your case - just to be safe, give your PDA a soft reset, and leave everything off. Check your current reading. If it's still at 16mA as you wrote, I wouldn't bother. Later you may fire up a GPS application like GPSTest, the HTC GPSTool, Tomtom, OziExplorerCE or whatever, and play with it for a while. Running a circle or two around your house should do it. Switch GPS off again, make sure all tasks have ended (if you want to make it perfect). Repeat checking the current as described above. It is also possible that you have to redo the test one or two times until the problem appears. You will see!
BusterTyTN
Addendum to the previous post: explanation of the screenshot.
The vertical center is zero current, discharge currents are going down. To the very left you see the PDA coming out of a soft reset, then I switched it into standby (the short flat line right before the 200sec division, ~0..1mA). Directly at the 200sec division I reactivated the phone, started GPSTest, waited until GPS was all up and running, stopped GPS and terminated the program. I also checked that no other applications were running at that time. After a little while the current settled to a discharge current of approx. 48 mA (the wide track in the center; the exact level can vary between devices). It continues drawing this amount of current until the battery is empty, or until you soft reset the device. I did the latter to the right of the screenshot, which shows another boot sequence followed by a standby, which in turn returned to a very low current consumption.
Also give a try to acbTaskMan - it's a very nice meter tool, see my related articles
I don't know anything about current measurement, but my kaiser usually lasts 2-3 days of intensive use (1-2 hours calls/day + some GPRS data + bluetooth always on + GPS once a week) and it seems quite OK for such device.
Rumcajs_tr said:
I don't know anything about current measurement, but my kaiser usually lasts 2-3 days of intensive use (1-2 hours calls/day + some GPRS data + bluetooth always on + GPS once a week) and it seems quite OK for such device.
Click to expand...
Click to collapse
Seriously thats gr8... What ROM / Radio are you using??
Rumcajs_tr said:
I don't know anything about current measurement, but my kaiser usually lasts 2-3 days of intensive use (1-2 hours calls/day + some GPRS data + bluetooth always on + GPS once a week) and it seems quite OK for such device.
Click to expand...
Click to collapse
That's intensive????????
How about 5-6 HOURS of calls a day
4-5 HOURS a day of HSDPA
checking emails every 15 minutes on 3 email accounts
sending emails 60-75 times a day
WI-FI 1-2 hours a day
150 SMS/Texts a day
10-20 MMS a day
and then a few misc. apps ran.
To me, my usage is not really intensive, but I do have to have a car charger and a couple of wall chargers because I can run a battery dead in about 5 hours.
i played doom for 30 minutes starting at 100% battery, and the battery was at 75% afterwards. i had to charge it for about 30+ minutes to get it back up.
On a daily basis, i will go to school, leave my phone in my pocket on standby, then by the end of school its at about 80%. i did nothing all day and it dropped 20%.
I would agree, 5-6 hours is probably the max i can get out of it.
BusterTyTN said:
...
I have reason to believe that all Kaiser models are prone to the "excessive standby current consumption" problem.
Click to expand...
Click to collapse
At least two devices work nicely as far as battey power is concerned.
I still enjoy more than 10 days standby with phone switched on.
http://forum.xda-developers.com/showthread.php?p=1652208#post1652208
I hope you'll find a solution.
Regards,
V
T-Mobile Germany
VARIO III rom 1.56.111.4
radio 1.27.12.11
When my phone is on, but not running any active apps, it consumes about 145 mA - 150 mA with nothing but my phone on and backlight lower 3rd bar.
I've read some others guys on the forum have a power consumption of about 100 mA with higher backlight settings.
indeed excessive consumption
I must confirm the OP's finding. Though I assume it is simply related to the Radio used (see comparison in another thread where est. time of usage went from 227 to +400 minutes)
When I used my stock rom with radio 1.27, I wouls still have 40-50% cap using all day Blutooth on, no 3G, still GPS enabled for 3 hours.
When I falshed to DCS 1.7 and changed radio to 1.64, power consumption doubled, draining the battery at incredible speed (full chare morning, less than 10% in late afternoon)
I had to disable BT radio and set backlight low to let me go through the end of the day.
Looking forward to read a solution here.
With stock orange radio and rom, my device would last circa 36 hrs with very light usage and about 6/7 hours with heavy usage.
With Dutty V3 and orange stock radio (1.27) I got very similar, maybe slightly faster drain.
I have today flashed dutty 6.1 and a 1.64 radio and will monitor battery usage tomorrow.
There's a lot of anecdotal information here...
To get this to baseline information I suggest the following starting point:
1. Device (Kaiser, tilt, etc)
2. Which battery are you using (brand, mAh rating, etc)
3. Which Rom and radio version
4. What application are you using to measure current draw? (Great spot for a recommendation or a .CAB file)
5. Provide typical usage description and corresponding battery life
6. At what point do you charge the battery (i.e. top off every night, charge whenever power's available, recharge only when battery hits low level (i.e. 10%)
To effectively analyze the data, there needs to be a consistent method of capture.
Be careful not to mix up the problems here!!!
1. I assume you will not be confronted with this problem when you never use GPS at all, though you should not treat this as a final statement - has to be investigated further. So far I have not found any increased standby consumption if I did not touch GPS (well, at least after the last soft reset).
2. I am not talking about short battery uptime under heavy use, either. For instance, if you have GPS permanently on, you can suck the battery empty within 4~5 hours, max.. However, it is well possible that a suspiciously short uptime is somewhat concealed by an overall heavy use of the phone. To figure this out, you simply have to check the standby current consumption of a suspicious phone, with all its features (temporarily) disabled, as described earlier.
3. Note, this problem is all about current consumption during standby !
@ Liquidsilver:
"anecdotal information", sure. Please read again, particularly the start of the thread which will answer most of your questions. Add the thread "TyTN II / Kaiser issue: GPS & battery drain" for the remaining ones.
Please try to understand. You can get the phone into a condition where it sucks the battery dead empty within 24 hours give or take, during standby, all features of the phone OFF. ZERO usage. PROVEN, some 10 times, on different Kaiser's, using different OS's.
@ Stay0Puft:
if your battery capacity does not drop much overnight, you may look at an issue other than the one described here.
I would like to add my observation to high battery drain. Normally on my stock Kaiser rom that I used for about 4 months, normal overnight drain is 4% with radio in standby and BT On, WiFi Off. I use GPS with iGuidance almost daily and seldom soft reset.
I have witnessed extremely high power drain only a few times and they were always involved somehow with WiFi. If I have WiFi On and forget to turn it off and just put the phone in standby or let it auto power off, I have found the phone hot to the touch and dead or close to dead in only a couple of hours. The phone is usually locked up and non responsive at this point, needing a soft reset. I haven't found what causes this, it's been at home on my wireless LAN but with no active application, WiFi was simply on. I make it a point to keep WiFi Off when not actively needed and never have issues in many months of use.
If you haven't checked this out, I'd be curious to see what the current meter would show. At some point I'll drag out the scope and make a shunt as well, just no time these days...
AT&T Tilt...
I used to get 2-3 days with mediocre usage when i first bought it... and now i'm lucky if it lasts an entire day... I cannot trust it with my morning alarm anymore... I dont think its the ROM, because i even tried flashing AT&T Tilt rom back on and even the minor update on HTC... but still no luck... I think i need like a calibrator program...
Hi, I just got my diamond 3 days ago and it seems to be having some battery problems, even when on standby it drains very fast, how long should the diamond last on a single charge (on standby, talk time, with wifi, or bluetooth) is there a benchmark to compare with.
the battery is just 900mha, like Nokia N95, so it is a bit underpowered, I suggest you to activate all energy saving tips through the program "Advance Config" and if you don't use/need UMTS & GPRS just fix your phone to don't discover automatically GPRS (always through Advance Config) and to GSM band (setting > phone > band), these reduce battery consumption.
bye,
davide
thanks, I'll try that, but even when not in use, the battery drains 20% to 30% per hr. tried it 3 time, same result, doesn't even reach 4 hrs of standby time
really strange... in any case your battery should go better after some cycles, wait at least 2/3 weeks before care
It's because the battery (like so many other aspects of this phone) sucks.
I got the new extended battery but that's useless too. It comes with a new cover for the phone but the battery itself is just twice as fat, so you end up with a 'sleek' phone that has a hunchback sticking out of it very awkwardly.
yep, I don't like the new battery, it makes a different phone
I have followed most of the battery saving advice that the usual programs can set up for you. I would say my phone, if its *just* standby can go 24 hours with just losing one "pin" on the battery meter. That means no calls, no peeking at the screen, no sms or otherwise communication. Since its hard to do this I have just tried 24 hours. If left on true standby I would say the battery would last for days.
I have a car charger and plug the Diamond into it while driving and in the office it sits in a cradle, at least I do not have to look for it under a pile of documents when it rings. Plus it serves as a fancy clock too!
The battery bar goes rarely below 70% while not plugged in.
3G and WiFi are extremly power hungry so do not expect hours of entertainment while they are on.
Fat battery is a bad road to take, I remember old Axim X51v (also HTC) with a 2.2Ah battery, it was like a brick. It is better to have a couple of small batteries rather than one big one obviously unless you want to play games on a transatlantic flight or go hiking for a long weekend.
One thing to remember is that your runtime grows faster than the battery capacity which is caused by the fact that at a slower rate of discharge the battery has a higher capacity, so if the 1350mAh battery is not too big it may be a worthwhile choice, I would expect the runtime to go up by between 75-100%. I just wonder how much longer will it take to charge and also you can say goodbye to most of the protective cases.
CD
Buy a solar panel for mini usb and glue on the back of the diamond, then you will have infite standby time when left in the sun
leemrvnt said:
Hi, I just got my diamond 3 days ago and it seems to be having some battery problems, even when on standby it drains very fast, how long should the diamond last on a single charge (on standby, talk time, with wifi, or bluetooth) is there a benchmark to compare with.
Click to expand...
Click to collapse
What rom do you have? maybe it needs updating?
I am using the Customised Comms manager and that's made a massive difference, basically 3G, Bluetooth and WiFi are off unless I need to use them.
I charged last night for the first time in 3 days, making calls and playing around in between
Utking said:
Buy a solar panel for mini usb and glue on the back of the diamond, then you will have infite standby time when left in the sun
Click to expand...
Click to collapse
that idea is awesome !!!
zetlaw said:
that idea is awesome !!!
Click to expand...
Click to collapse
want one!!!
i get about 1.5 days outta my battery....
only running on 2g with light sensing on 20 or more sms a day with maybe an hour of phone calls all up.
i'll copy-paste my answer from an another thread:
using yr phone in a place where the reception is not good will drain yr battery faster.
i can add (there is a relation) that the level of radiation that any phone is emitting it is also higher when reception it is not strong enough. i've seen it demonstrated yesterday. entering in yr car double the level of radiation, in an elevator the radiation increases 10 folds! yr phone tries to connect and that's energy consuming and radiation emitting (electromagnetic).
i guess that you bought yr phone not too long ago. i know it sounds strange but after a few cycles yr battery's life is going to improve and i am not the only one to observe it.
don't stop the charging when the battery icon is full. i learned using a wall charger with LED (red for charging, green for charged) that after diamond's icon said 100% the charging continues for at least 30 minutes more (the led was not fully green but was blinking red-green).
from my experience u can use all power management option from shap's advanced configuration without loosing yr connectivity. i can not tell u what those option are but after using all i can tell that diamond's battery life improved.
with only 2G and some e-mailing downloading and checking this forum a few times my battery last for 1.5 days. of course their is also 1-1.5 hours of phone calls.
don't expect yr battery to last if you are using yr diamond as an entertainment center (movies and mp3) or as a battery only powered GPS navigator. i am using my GPS in my car always connected to my car charger.
I'm thinking about buying something like that to solve the problem :
http://usb.brando.com.hk/prod_detail.php?prod_id=00333
Blazeitup123 said:
What rom do you have? maybe it needs updating?
Click to expand...
Click to collapse
Hi
Rom 1.37.707.1
Radio 1.00.25.03
I'm not yet sure what the problem was, but it has something to do with the sim card that I'm using, the sim stop receiving signal and I tried another sim. The battery life improved and now It last more than a day.
thanks,
battery life
leemrvnt said:
Hi, I just got my diamond 3 days ago and it seems to be having some battery problems, even when on standby it drains very fast, how long should the diamond last on a single charge (on standby, talk time, with wifi, or bluetooth) is there a benchmark to compare with.
Click to expand...
Click to collapse
Well what can I say about it..... I'm totally new on this forum but this site is greeeat!!!!! Anyway - I have Diamond about 3-4 days, I had the same problems as most of us: overheating, battery life, ActiveSync on every 5 mins.... I just couldn't stand thoughts that I spend £250 on such a crappy thing until I found this site
What I've done was: install HARDSPL, then changed Radio from 1.00.25.05 to 1.08.25.08 using CustomRUU and changed ROM 1.93 onto cooked ROM: [WM 6.1] NEW SWIFTBL WWE DIAMhttp://forum.xda-developers.com/newreply.php?do=newreply&p=2460083OND ROM V7.5 (FULL & LITE VERSIONS) - CE OS 5.2.20755 (Build 20755 AKU 1.4.0) - FULL VERSION, then installed Regedit as well, done some additionall tweaks like Better Power Management (changing registry HKLM) - basicly - adding all tweaks that u can find on the internet and..........my Diamond is a real Diamond now I've spend 3 hours listening to my mp3's, then running wifi at home, playing etc.. and my battery life went from 100% to about 80% - all during all day using ...
elmumiomarek said:
Well what can I say about it..... I'm totally new on this forum but this site is greeeat!!!!! Anyway - I have Diamond about 3-4 days, I had the same problems as most of us: overheating, battery life, ActiveSync on every 5 mins.... I just couldn't stand thoughts that I spend £250 on such a crappy thing until I found this site
What I've done was: install HARDSPL, then changed Radio from 1.00.25.05 to 1.08.25.08 using CustomRUU and changed ROM 1.93 onto cooked ROM: [WM 6.1] NEW SWIFTBL WWE DIAMhttp://forum.xda-developers.com/newreply.php?do=newreply&p=2460083OND ROM V7.5 (FULL & LITE VERSIONS) - CE OS 5.2.20755 (Build 20755 AKU 1.4.0) - FULL VERSION, then installed Regedit as well, done some additionall tweaks like Better Power Management (changing registry HKLM) - basicly - adding all tweaks that u can find on the internet and..........my Diamond is a real Diamond now I've spend 3 hours listening to my mp3's, then running wifi at home, playing etc.. and my battery life went from 100% to about 80% - all during all day using ...
Click to expand...
Click to collapse
could u explain more, with the links to the progs u used? i'd really use this info
thx
I am getting about 48 hours (I probably talk less than 30 minutes in that time). Using default x04ht rom on diamond with radio 1.00.25.05 (just flashed to 1.08.25.20 and getting about the same). Charge every day isn't bad, but every 1.5 to 2 days for a device like this; no complaints.
Hi,
I've got a very strange problem: After replacing the display of my Alpine the 2nd time, the display is just light and yellow when the battery is full.
As the battery level gets lower and lower, the problem disappears.
When the battery is 100% full, there is no way to get a screen (except reset). Everything is just white!
The more lower the battery, the more and quicker are the ways to get a screen: When I call the phone, the phenomen disappers or when I switch on wireless lan or bluetooth.
When battery is ca. at 60% level the display works normal. The phenomen is gone.
My obersvation is:
- The lower the battery, the more is the display working
- The more "power consuming" things (incoming call, activating camera, pressing buttons, wireless LAN, ...) I do, the faster I can get a working display.
First, I hope you can understand my observation and my description.
First question: What could this be in your opinion? It is no software problem as the problem persists over hardresets.
My assumption is: Maybe there's a voltage regulator or a capaciator broken. Or something similar. This means that the voltage level is maybe just a little bit higher than normal, say a few mV. For all other components this does not matter. Except the display.
Can this be true?
At the moment, I can work normally with the PDA iff I just load the battery up to 60%. But as you might guess this is no persistent solution.
In my opinion, I could do two things:
1.) Build something that draws exceptional high power for just a very small time and activate this thing when powering on the device. This would not solve the problem but make the PDA useable again. But: How could I do this?
2.) Better way: Repair. Does anybody have some insight of the hardware? Is there a regulator or something that would explain this phenomen? Where is it and how to replace/repair (Soldering SMD would be no problem).
Thank you very much in advance,
Niki
Anyone else experiencing huge battery drain in R2AA008 (Generic_UK)?
Updated few days ago and now X1 drains the batery in 6 hours.
- Same location (networks etc)
- Same config (ie. all power-savingoptions enabledin Advanced Config)
- Same Microsoft Push settings, same servers etc
Any ideas?
Maybe SE changed some hidden power management settings. They did fix the BT shutting off on its own automatically. Id bet that was some badly implemented power saving strategy.
I use my BT very rarely so it's turned off like 99% of time so that's not the issue. Just can't figure this one out. If all else fails I have to flash R1 back, situation now is just not working, can't use phone for a full workday :/
just set the backlight to 20~30%, then you'll have more battery life I always use this method.
You're comparing the R2AA008 with which firmware?
foxcheng said:
just set the backlight to 20~30%, then you'll have more battery life I always use this method.
Click to expand...
Click to collapse
I'm sure I read somewhere that disabling auto-backlight actually throttles back the CPU for some reason.
It's strange I know but I read it somewhere on XDA-Devs
I'm comparing to R1 generic UK, will try R2AA0010 and see what happens. Will also try auto backlight. (Strange, always had it on auto)
Does anybody encounter the following situation?
I have my X1 fully charged and put to sleep. After 8 hours and switch on X1 again, there were only 30% battery left.
I've updated my X1 ROM to R2AA008 too. But I got my phone stanby for four days and the battery still last about 20%-30%.
I think the only reason is your battery is not original or it's not OEM battery.
No problem here. My battery work for whole 2 days.
BT - 4-5 hours connected with my Jabra BT Car Speaker + 2 hours at home with laptop
WiFi - 2-3 hours
Voice - 1-2 hours
Still having fun with my X1 so I turn it on very often to check, change settings etc.
At the end of the 2nd day it has 10-20%
ROM R2AA008 UK
Backlight auto, nothing special
Power drain
I had a smilar problem. It was due to a third party case which had a small bump pressing on the screen. They seemed to draw power. Out of the case, it lasts a lot longer.
Been testin R2AA0010 for a few days, same thing. Looks like I have to confirm this by moving back to R1. Annoying at least, X1 doesn't survive for one day as it is.
I use up the entire battery with just 4 hours of web browsing through wifi/3g on the R2A10 rom.
The same behaviour for me as well with the new ROM.
I am using exactly the same settings, apps, tweaks as before the upgrade, and now I have to charge the battery every day. With the R1 ROM it was 2 days!
It seems the 3G is eating the battery power so much in the new R2 ROM.
I just disabled it, because I don't use the video call, and the ordinary email checking doesn't need HSDPA, a simple EDGE is enough.
So, I got back the 2 days uptime
Consumption of power is bigger i R2A10 imho comparing to R2A08 genUK.
1.5 day it's all I can survive
Have you thought about why the new R2 rom is much snappier? Perhaps the CPU core isn't being throttled anymore/as effectively as before. I'll trade the increased response for battery life though, just need a standby battery ready. Now, if only SE would release a decent charger for that...
Me personally, i haven't noticed any huge difference in power consumption. I believe most X1's come with batteries from China, the outlet I dealt with in Taipei (remember HTC is based here and makes phones here) reports some issues with the new batteries.