yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III General] keiith:
I am also experiencing massive battery loss with my AT&Tilt.

I had the phone at:

DUTTY'S OFFICIAL WM6.1 - 5.2.19199

1.64.06.04 RADIO

No programs running in HTC task manager.

BatteryStatus 0.05 showing approx 150ma usage +

Thought it may be either the rom/radio.

So downgraded back to stock 1.27.12.11 using:

"RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship"

Hard Reset.

Downloaded/Ran BatteryStatus 0.05 cab.

Still showing approx 150ma usage! What is going on?! =(

Have tried on two batteries (other is a Cameron Sino Technology 1600mah battery) without any success.

Can anyone suggest anything so I can get a better battery life on this phone.
[Tilt, TyTN II, MDA Vario III General] BusterTyTN:
Hi there,

I'm back. Had some time for more testing, with interesting results. I will add them to the first post.

@ Jay2TheRescue: Are you really sure that you switched your phone completely off during your tests? I found that the high standby consumption does not appear if the cellphone unit is left on (i.e. you're out of "airplane mode"). I even succeeded resetting the phone to a normal consumption by activating the cellphone. Thanks...

@ zagan: I already wrote something about this effect in an earlier message. 1% capacity drop every 30secs ~ 1min points tells you that your battery discharged during standby for at least some hours. You are not looking at a "realtime" capacity drop, it's rather that the battery gauge does not catch up fast enough, due to an averaging process or something. If you soft reset your device, the gauge will be reset to a more or less correct state.

@ pietrucci: Impossible. If your phone would draw 730 mA, you would not get it to last 8 hours. The current readings must be wrong.

@ keiith: sounds like your phone is damaged. After all your battery changes, ROM updates and hard resets it should have come back to a normal consumption, at some point. One last try; did you verify the consumption reading, by comparing it with the actual capacity drop?

Buster
[Tilt, TyTN II, MDA Vario III General] leopold54:
I tried downloading PowerGuard but the link did not work for me. Has anyone else experienced a similar problem?
[Tilt, TyTN II, MDA Vario III General] BusterTyTN:
The link on this page seems OK to me.
[Tilt, TyTN II, MDA Vario III General] BusterTyTN:
@ any Mod:

I believe this bug has been sufficiently investigated and correctly identified. I think we can unsticky this thread, but may I suggest that we leave something like a reference to it in a list of "known bugs" (which I miss anyway). The "Kaiser Wiki" appears to be a great place for a bug list. We could do the same with other threads, like,

Known issues and bugs

- missing video drivers <thread reference>

- unresolved Tilt issues <thread reference>

- abnormal battery drainage in standby <thread reference)

and so on. Of course we could also keep this thread sticky and expand its meaning to "known bugs", if you prefer - I'd be glad to take care of a cleanup. All comments welcome.

Thanks, Buster

http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser
[Tilt, TyTN II, MDA Vario III General] myteematt:
Strangely Familiar

Is it just me or does this remind you of how mostly all the Windows operating systems need to be regularly restarted almost daily to get best performance and battery life. This applies to laptops moreso than desktops however. From my experiences with Windows XP and 2000 for example programs would never fully release the memory or close open threads after being closed, which will not only affect performance and memory availability but also affect battery life.
[Tilt, TyTN II, MDA Vario III General] BusterTyTN:
There's some truth behind it. Though I see even larger problems when it comes to maintenance or repair. Just remembering several hard disk failures where I had to retrieve my data with the help of Linux-on-CD (Murphy's law also states that the last backup is always too outdated). You can't even access your own data with this stupid "rescue CD" stuff, whether or not you're the one and only admin on the machine. Try to get assistance from the suckers @ Microsoft in such a situation and you'll learn what white hot rage is. Unfortunately I have so many tools running on a pretty large installation that I can't get away without f... Windows. But I swear, I will keep this thing alive for the Windows specific applications only, and set up my next machine based on Linux.

Regarding WM, this rather reminds me of the need to kill some tasks which do not end automatically (or which don't sport an "exit" menu entry), like "Internet Explorer", which can eat up quite a serious amount of memory, depending on the site you looked at. This is even worse compared to desktop versions of Windows.

Finally - just to be fair - I am not sure whether this problem is related to WM, or to some driver proprietary to HTC. We'll see.

Buster
[Tilt, TyTN II, MDA Vario III General] hsanghavi:
http://xdaforums.com/showthread.php?p=2044130#post2044130

This forum grants a solution I think to most of you.
[Tilt, TyTN II, MDA Vario III General] 4yunweb:
i'm pretty convinced that it's the GPS' problem.

i've tried many rom/radio combinations, and found they're almost all the same.

here're the standby current figures (following pressing the power button).

after running GPS:

-----------------

phone on (3G with push email): 56 mA

flight mode: 54 mA

after running GPS, then soft-reset:

---------------------------------

phone on (3G with push email): 4 mA

flight mode: 2 mA
[Tilt, TyTN II, MDA Vario III General] johnny13oi:
My ATT TILT with the original HTC Windows Mobile 6.1 firmware shows a current draw of 10ma after waking up after using GPS. It sometimes shows 7ma.
[Tilt, TyTN II, MDA Vario III General] 4yunweb:
Polaris Radio 1.58.25.14 on Kaiser: PROBLEM SOLVED?

here're the standby current figures at suspension with Polaris Radio 1.58.21.23 on Kaiser:

after running GPS:

-----------------

phone on (3G with push email): 56 mA

flight mode: 54 mA

after running GPS, then soft-reset:

---------------------------------

phone on (3G with push email): 4 mA

flight mode: 2 mA

GPS fix (i.e., 3-D): 1 minute

standby current at suspension with Polaris Radio 1.58.25.14 on Kaiser:

after running GPS:

-----------------

phone on (3G with push email): 5 mA

flight mode: 1 mA

after running GPS, then soft-reset:

---------------------------------

phone on (3G with push email): 4 mA

flight mode: 1 mA

GPS fix (i.e., 3-D): 3 minutes
[Tilt, TyTN II, MDA Vario III General] BusterTyTN:
@4yunweb: you should try cycling the GPS a couple of times, after updating to the new 1.58.25.14 radio. The problem does not pop up always. Very interesting to see that these ~55mA persist with an active phone.

@johnny13oi: so far I've learned about abnormal standby currents between 28 and 100 mA. Well possible that 10mA marks a new lower end. But did you really come out of flight mode? If you left the phone on, there may be no "GPS-related" increased current consumption (in contrast to what 4yunweb found).

@hsanghavi: I've looked at it. Is a different issue.
[Tilt, TyTN II, MDA Vario III General] 4yunweb:
Polaris Radio 1.58.25.14 on Kaiser: PROBLEM SOLVED!

BusterTyTN: how would you know i hadn't repeat the experiement several times before posting?

i'm a researcher. i know what i'm talking about.

the figures i posted were MEAN numbers on several tests, but each was pretty consistent, including trials fresh after both soft and hard resets, followed by TomTom or GPStest etc. i even tried enabling and disabling power management features a few times.

i believe the results are conclusive. the unsuspended but backlight-off current has also gone down from some 100 mA to 50! More so, with other radios, sometime you observe a current well over 1000 mA with GPS on, but now it's some 500~600 mA, if i remember correctly.

my figures are consistently repeatable to me. it'd be interesting to see soemone else's results of using Polaris Radio 1.58.25.14
[Tilt, TyTN II, MDA Vario III General] johnny13oi:
So would you consider 10ma the lower end of abnormal standby current or normal standby current. I don't ever use flight mode (turning off regular GSM service I'm guessing). I don't think I have 3G or anything like that on though and no bluetooth or Wifi on. Just the phone in standby gives me about 7-10ma current draw.
[Tilt, TyTN II, MDA Vario III General] fusi:
ive checked this on my phone a number of times trying different settings and states, managed to get 0ma with phone on (all stock here)! couldnt get mine to reproduce this gps bug, i might not be trying hard enough though :p
[Tilt, TyTN II, MDA Vario III General] 4yunweb:
lukcy you! guess what, i couldn't either, now!

the funny thing is, i had now got back to both radio 1.58.21.23 and 1.64.08.21, and couldn't reproduce the GPS bug any more that sucked my power before!!!:mad:

no wonder my wife never had this problem on her Polaris - i just checked her radio; guess what, it's 1.58.25.14!

don't know what happened when i first flashed to 1.58.25.14 - something must have!:rolleyes:

the only thing that i can recall is that i deleted the TomTom local city maps from the main memory, and start to use the entire UK map from the microSD. But i doubt this was the cure. :eek:
[Tilt, TyTN II, MDA Vario III General] BusterTyTN:
Hey, you are not under attack. In your position you should know how careful problem descriptions are to be taken. Worse, this issue is more guessing and suspecting than knowing - just look at the last post of yours. Regarding GPS consumption; you sure that you are talking about mA, not mW? My phone needs ~250mA if GPS is on.

@fusi: yes, it looks some phones are unaffected, and maybe you are in luck. Since you wrote something about "trying different settings and states"... did you put the phone in airplane mode before cycling the GPS?

@johnny13oi: As said, well possible that 10mA is at the lower end of the abnormal current, but you need to find out more. It is a bit high if nothing is on. Look at the Comm Manager after switching GSM off. If it says "airplane mode", then you're in good shape. Soft reset the phone, stay in airplane mode and recheck the current. If it's still 10mA, it may be worth looking at all active applications and services.

Buster
[Tilt, TyTN II, MDA Vario III General] 4yunweb:
no worries, buster, i know.

i didn't record anything for GPS being on, that's why i said "if i remember", as the issue you originally prompted was just the standby power comsuption after GPS gate opening.

further tried to put map (and zip, voice) back onto main memory - guess what, the standby current after GPS went straight back to 55 mA! so hopefully, my problem is now sorted (by keeping these files on SD card).

don't know if this or another radio would be helpful to you, but hope you get yours sorted soon too...

interested to know though... good luck:p
[Tilt, TyTN II, MDA Vario III General] Autourdupc:
Want to do the tests

Dear all,

Can you please give me the link to the software used to control the current consumption ?

I would like to do the test on my Kaiser...

Best regards to all,

Laurent.
[Tilt, TyTN II, MDA Vario III General] 4yunweb:
the one i use most is attached below. it doesn't control though; just monitors
[Tilt, TyTN II, MDA Vario III General] jgpd:
Another variation of abnormal battery drainage in standby

Hi to all,

two weeks ago I experienced the famous RLOD on my TyTn II Device.

The last operation I did was replacing the micro SD card and then I connected my device to the power supply for overnight reloading.

On the next day i saw the red light on my device :(

I was not able to boot my device and therefore I sent it back to my supplier for maintenance.

I got it back last week and the report says: Software replaced, Power Test OK.

But now I have an abnormal battery drainage. The device consumes ~ 150mA in standby, even if everything is disabled.

A full charge holds now 6-8 hours before I have to reload.

Before "maintenance" I was able to use the device 2-3 days without reloading and I had 1-3 mA power consumption in standby (with the lowest light settings).

The rom and radio versions are the same as before (1.27.12.11, 22.45.88.07H, 1.56.407.3) and the device and the battery are definitely my old ones.

I returned my device again back to my supplier and I will let you know what happens.

(Please excuse my whacky english, its not my native language).

Regards

Juergen
[Tilt, TyTN II, MDA Vario III General] mugsee:
I'm in the exact same position and have the same problem as jgpd except I didn't return mine.

Mine constantly consumes ~170mA in standby with everything turned off. I have very little icons in my today screen and I've tried all the different variations in radio and roms out there, including official releases as well as cooked roms (including lite roms). I've applied both battery saving patches but they only give a very small decrease in battery consumption. Lastly, I've also turned off all communication servies in the phone (wifi, bluetooth, phone, data, etc.) and nothing seems to want to turn down the phones battery consumption. :(

I'm beginning to think that the problem is hardware related because everything that I've tried just isn't doing anything.

Any ideas?
[Tilt, TyTN II, MDA Vario III General] Autourdupc:
Battery drainage and SD cards

Dear all,

Can we imaging that the drainage can be different with different SD cards ?

Maybe some of them could consume more current than others...

Did someone made some tests ?

I think it would be a good idea to collect some data about SD consumption.

Regards,

Laurent.
[Tilt, TyTN II, MDA Vario III General] BusterTyTN:
If I remember correctly, the SD card may be another problem field which causes current problems. Simple enough to try: remove it then soft reset. Just search for suitable keywords if you want to know more. There's also numerous reports about phones which never come down from consumptions between 50 and 150 mA or so. If this is a non-destructive latch-up (which I doubt), you should be able to recover from this by removing the battery for a short while. Most latch-ups are irreversible which makes them kinda dangerous. Possible as well that this is some sort of hardware bug leading to certain idle consumptions, which self reset below a specific current of ~20mA, can't be reset above ~100mA, and can be reset manually if the current range is somewhere in between. At least I am pretty sure that the current flow is not caused by system activity because of the very smooth & steady current flow (as shown in the screenshot in the first post). It rather looks to me like something leaves the lights on in the GPS corner of the device. While I'm still searching for an explanation for the varying standby currents.

Buster
[Tilt, TyTN II, MDA Vario III General] satiros:
my thoughts thoughts totaly

i have been using my tytnii and noticed severe drainage with gps use the latest incident was i was using dutty's rtm ver and niki radio had used it for several days with very good results also tested the gps and was very good

four days ago i opened the destinator 7 once more and after that i noticed severe drainage .

My thoughts was it had something to do with the new kingston 4gb sdhc i have just installed fuc that i ll remove the microsd the drainage although i removed continued i reseted a few times , powered off i was once more angry with my stupid selection of tytnii a very expensive not worthy machine.

today i installed a new rom dutty's latest with a new radio the problem dissapeared due to erase of setting zeroing values i suppose but the problem for every engineer stands as for every scientist the procedure must be reporduced i think that in that problem we have a random problem with no hinds why is happening of course it has its roots in the gps but where and why i dont know the drainage i faced could clean up my battery in eight hours easy without use when before that i had in cases of inacativity 36-40 hours

my guess is selling that **** will do the job and the only thing i will miss is xda forum and all the people that helped here

thanks

satiros

greece
[Tilt, TyTN II, MDA Vario III General] BusterTyTN:
@ DrXDA: Hey thanks for the positive feedback. Adding to what you wrote about the opened ports: somewhere within this thread I mentioned some experiments with GPSGate which proved that this can't be an "application count" issue. A complete port disconnect (through "External GPS") did not help, either. I considered writing a small tool to diagnose the GPS unit at chip level, but without the least bit of information it would be a waste of time. I already searched for details about these chips, to no avail. Qualcomm sucks...

@satiros: I can tell you, I understand your frustration. Thats the reason why I opened up this thread, rather than raise the white flag. This is definitely the right place to sort things out.
[Tilt, TyTN II, MDA Vario III General] DrXDA:
It sucks indeed... I tried to find the datasheet for the QUALCOMM MSM7200 chip but it wasn't up on their site, supposedly for some legal reasons or whatever.

Quick 'n' dirty idea: I'm wondering if rapidly turning on/off the GPS module a few times in succession would consistently remove this latch-up condition or whatever is happening. Perhaps someone could try writing a small s/w to test this and post results here. Anyway, this is not a proper solution, perhaps HTC could release a patch for the GPS driver (I seriously doubt it will happen though).

DrXDA
[Tilt, TyTN II, MDA Vario III General] BusterTyTN:
Perhaps? They definitely could, no doubt about it! I am even sure they would do something, if only the right developers at HTC were aware of this issue. But how to get through to them, if not by pressure from people like us? Another reason why this thread exists. When I find some time I will get in touch with Qualcomm and try to dig up some datasheets. I'd really like to debug the GPS chip, snapshot its status at fault time, or something. This should pinpoint the problem. I don't think rapid switching of the GPS module does do much of a good. We already have a basic understanding of how it reacts to this type of cycling: sometimes it comes back intact, sometimes not. Or do you want to "shake" it until power consumption is back to normal?

Buster
[Tilt, TyTN II, MDA Vario III General] DrXDA:
I was just hoping that maybe 5-10 very rapid (done in s/w) on/offs would bring it back to normal... Or one could go closed-loop and cycle the GPS, measure consumption and repeat if unsuccessful. But all of this is a really bad ad-hoc approach... Better target the root cause as you say. Let's hope HTC's engineers read this thread.
[Tilt, TyTN II, MDA Vario III General] jgpd:
Is it really a "GPS" problem ?

I am not sure if the GPS part is involved on my device.

As I described earlier. I had the RLOD problem, sent back the device for maintenance and got it back with "SW replaced" (same rom versions as before) and have now the abnormal battery drainage problem.

!! Since I got my device back I did not installed any GPS related software !!

@Autourdupc: I have a 8GB SanDisk micro SD hc class 4 card in my device but it makes no difference when I remove the card. The device consumes ~150mA anyway.

Regards

Juergen
[Tilt, TyTN II, MDA Vario III General] BusterTyTN:
If you can't fix it (did you try the "countermeasures" as mentioned in the first post?), you should replace it once more. As said, there are some phones which never come back to normal. The problem is that service people do usually check all features of the returned phones, but not abstract parameters like power consumption. Since they don't see a problem on their checklist they rate it all intact, send it back to a different customer, with the known results. So actually, by replacing your phone you may have worsened things. You simply got a used one which came out of another customer complaint. I can tell you a number of very similar stories about this, such as the "IBM Deskstar hard disk failure problem" which was a badly constructed board to board connection. I found it out, but IBM kept silent, probably because they would have risked a costly product recall.

Coming back to your phone. Maybe you should point out the very issue to your dealer / provider, add references to discussions like this, ask them to shift in gear and get HTC busy on this darned issue, after all this annoyance.

Buster
[Tilt, TyTN II, MDA Vario III General] jgpd:
Yes, I read your first post and I tried all measure methods. I had the phone for 5 days and checked various things before I sent it back. But whatever I did, the power consupmtion was 10-20 times higher as before.

No, I got back my old phone for sure (I always place a small mark on a device to make sure if I get back the same or another device). They just reflashed it. I spoke with one of the service guys and he told me, that they alway reflash the device. And when the device works properly after the reflash it will be send back to the customer.

In fact, it is amazing, that my phone worked properly for 3 months, suddenly died with a RLOD and now, after a reflash does not work a before anymore.

By the way, I never reflashed my phone myself. I always had the original HTC softweare in use.

Yes, I clearly announced, that I want a phone with the promised standby time. Let us see, what happens. I think I will get back my phone next week.

Anyway, thanks for your response. :)

Regards

Juergen
[Tilt, TyTN II, MDA Vario III General] BusterTyTN:
OK, thanks. These details may be helpful, who knows. Hope you will get back an intact phone, this time. Sounds to me like something was damaged at the time of the RLOD. Don't see why flashing the ROM should cause this.

Buster
[Tilt, TyTN II, MDA Vario III General] DrXDA:
Kaiser overheating <--> GPS problem (?)

Let me add another idea to the discussion. I don't know if it's just a coincidence or is related to the GPS problem, but a few days prior to discovering the GPS problem I noticed that the Kaiser got really hot while charging via the USB port. This happened only once. I don't think it has ever gotten that hot in the past. So I wonder whether the excessive heat generated internally while charging has anything to do with damaging the GPS module somehow... I know it sounds very far-fetched, but the GPS problem appeared right after the Kaiser overheated. Coincidence? Probably, but I thought I'd mention it.

Also, lately I'm noticing some weird behaviour in the phone module. I keep getting "No Service" messages very often, with the [!] icon appearing. At other times, although the phone signal is 4/4 bars, the incoming calls get transferred to VoiceMail, as if the phone is off! Really nasty! Again, this behaviour started happening right after the Kaiser overheated. Not sure if all of these problems are somehow related... In any case, I'm beginning to doubt HTC quality control... Not good! :mad: