MSFP Push Email - HeartbeatMin - Palm Treo 750

Digging on leaked ATT WM6 CapPackage.PXP noticed that a file called MSFPHeartbeat.prov.xml the parameter HeartbeatMin is set to 360.
Looking on MSFP Best practices, they suggest a HeartbeatMin set to 480 (8min). because a lower value could decrease battery life.
http://www.microsoft.com/technet/so...c27-8793-4343-b4a0-61f5ab9e946a.mspx?mfr=true
Found minHeartbeat key at \\HKCU\Software\Microsoft\Activesync with value of 360. I proceed to change it to 480 as MS recommends to see what happens.
I was wondering if changing this parameter to what Microsoft recommendations, can improve battery live on WM6.
Does anyone had worked with this before?
Let you know my results later.
UPDATE 11-13-07
No noticeable improvement.

There's not much difference between what MS recommends and what ATT set, unless your data connection stays iffy for a while, then the ping frequency starts its march downward to the minimum set in the reg. If you are in an area with a marginal signal for a long period of time you'd see an impact on your battery - but that's also caused by the radio itself upping its power as it trys to maintain a connection to the tower.
ariele said:
Digging on leaked ATT WM6 CapPackage.PXP noticed that a file called MSFPHeartbeat.prov.xml the parameter HeartbeatMin is set to 360.
Looking on MSFP Best practices, they suggest a HeartbeatMin set to 480 (8min). because a lower value could decrease battery life.
http://www.microsoft.com/technet/so...c27-8793-4343-b4a0-61f5ab9e946a.mspx?mfr=true
Found minHeartbeat key at \\HKCU\Software\Microsoft\Activesync with value of 360. I proceed to change it to 480 as MS recommends to see what happens.
I was wondering if changing this parameter to what Microsoft recommendations, can improve battery live on WM6.
Does anyone had worked with this before?
Let you know my results later.
UPDATE 11-13-07
No noticeable improvement.
Click to expand...
Click to collapse

thanks, summiter

Related

Limiting 3G/GSM Connection Time

Hello all,
I've noticed that once you initiate a data connection, whether it be for email or web browsing, when your done with that activity the data connection stay connected. The problem with this scenario is that I forget to terminate the connection and it drains the battery rather quickly. So, is there a way to set a time-out for the connection that will disconnect automatically after a preset period of in-activity?
Looking forward to your responses.
Regards,
idyllic
Try BandSwitch or PhoneAlarm. I use PhoneAlarm and love it.
iKelvin said:
Try BandSwitch or PhoneAlarm. I use PhoneAlarm and love it.
Click to expand...
Click to collapse
thank you iKelvin for the suggestions of BandSwitch & PhoneAlarm! Unfortunately this is not a good option for me as the only function I'd be using from the programs is the data time-out setting. The program installs are not worth it as they would wastes more memory than they would provide functionality.
What I'm looking for is some registry setting or utility that address this specific issue.
On a more positive note my wife loves the PhoneAlarm for all her appointments
Cheers,
idyllic
I have created a shortcut to the Phone Service settings and assigned it to the PTT button. At least gets me to the Band Selection option in a minimum of clicks.
Code:
22#ctlpnl PLMOCPL.cpl,0,1?\Windows\cplmain.cpl,-7140
I suppose someone good at mortscript (I haven't played with mortscripting yet or I'd offer) could create a simple batch type file to do this for you.
There is a registry hack, where you delete something, then re-add it and change the time out from some really large number to 60sec.
This works well.
Found it.
http://forum.xda-developers.com/showpost.php?p=1725927&postcount=62
This worked for me, use at your own risk
http://forum.xda-developers.com/showthread.php?t=349481&page=7
Full Thread
FSB said:
There is a registry hack, where you delete something, then re-add it and change the time out from some really large number to 60sec.
This works well.
Found it.
http://forum.xda-developers.com/showpost.php?p=1725927&postcount=62
This worked for me, use at your own risk
http://forum.xda-developers.com/showthread.php?t=349481&page=7
Full Thread
Click to expand...
Click to collapse
EXCELLENT!!!! That did the trick!!!! Thank you, thank you. Cheers all
Interesting find. I have Good MM so am "perpetually" online, need a data connection full time so prefer to "dumb-down" to EDGE to save resources (caveat is that I sometimes miss calls ). But this will work nicely for those without a need to keep a data connection 100%.
Bear in mind the cachetime is in ms, so 600 milliseconds = 0.6 seconds. And you may very well use more battery resources if you are constantly reconnecting over keeping a static data connection.
tmknight said:
Bear in mind the cachetime is in ms, so 600 milliseconds = 0.6 seconds. And you may very well use more battery resources if you are constantly reconnecting over keeping a static data connection.
Click to expand...
Click to collapse
Hmmm, when I tested the connection time-out, the initial test lasted exactly 60 seconds. When I changed the time-out to 120, the connection lasted two minutes. I'm not trying to start an aguement, but this is the way it has worked for me.
Regardless of actual time-outs, this little mod has helped save battery when not near a power source.
Regards,
idyllic

Is there a Signal Strength Logger?

I have an unlocked GSM WinMobile phone that I want to use to track the signal strength of the two major carriers in my area prior to settling with one. Does there exist a program for logging the signal strength that the phone has (i.e. number of bars) over a period of time. No GPS info required, just something that can do real time polling of the signal strength every few seconds/minutes and log it for later viewing.
Here's the scenario.... I start the program, drive bteween two locations, then look at the log to see if there were any "drop outs" along the way.
Looks like I'll have to make one myself.
I read that this registry key holds the GSM signal strength: HKLM\System\State\Phone\Signal Strength (DWORD value)
It shouldn't be so hard to make an application that checks the registry every set number of seconds and logs it.
BTW, Am I the only one who thinks this would be useful? It's something like wardriving for WiFi signals, but looking for GSM signal instead.
List of registry entries/tweaks here ( Windows_Mobile_5_Registry_Tweaks ). Is there a similar list for WM6?
Due to my Fuze having horrible signal strength (esp. compared to the Kaiser), I am looking for a program that does this. Did you ever write one?
Thanks,
-Mc
Yeah, I wrote a fairly basic one that checked the registry for signal strength every set interval (30 seconds), and wrote it to a text file with a time stamp. I wrote it in Visual Basic 2003 using the WM5 SDK and OpenNetCF, but it works in WM6.1. I'll see if I can dig it up and post it.
The downside is that the only point of reference is the time stamp, so if you see 0% in the log, you would need to remember where you were at that time. I added a sound file to play when the signal dropped below a set level so it would notify you if you are in a dead zone when running the program. It served my purpose for letting me know there was only one potential dead zone for my commute route, which lasted less than 1 minute (at 60 mph, that roughly 1 mile < 10%.)
An ideal program would log the GPS coordinates with the time stamp, but unfortunately thats beyond my skills.
There is a tool out there, I've seen it but can't remember the name. Try to find it at pdagold or pocketpcfreeware.net. Records a graph and a file if I remember correctly.
@nonpaq:
It would be great if You could post it!
Thank You!
Can't find my version off hand. Only found an early version that had no menu controls. I will post when I find the final version . (I have to dig up my old HTC StrTrk and pull it off there.)
In the meantime, I searched the web and found a great app called PhoneToday that does the signal strength logging and more. Its a Today plugin that displays network info, missed calls, sms, etc, and the logging is more precise than mine.
It is a commercial application, and for WM pro phones only, but has a 14 day trial www.burroak.on.ca . Site says registration only $5.50 with PayPal.
(My app was designed for smartphone, but worked fine on wm pro phone.)
Attached is the CAB for the trial version.
Sample PhoneToday log:
11/19/08 1:14:04 PM (1947806): Received signal acquired radio event
11/19/08 1:14:19 PM (1962636): signal strength: 61%
11/19/08 1:14:19 PM (1962675): Operator: T-Mobile
11/19/08 1:15:24 PM (2028175): signal strength: 61%
11/19/08 1:15:24 PM (2028210): Operator: T-Mobile
11/19/08 1:16:29 PM (2093292): signal strength: 61%
11/19/08 1:16:29 PM (2093338): Operator: T-Mobile
Sample log from mine:
Started -
11/18/08 - 11:19:57 = T-Mobile (90)
11/18/08 - 11:20:52 = T-Mobile (60)
11/18/08 - 11:27:49 = T-Mobile (60)
Thank You.
Important for me is the ability to get alerts, when the signal is poor - as Your own software does!
I've been playing with PhoneToday, and I have to admit is is far better and complete than what I wrote. It gives alerts, logs, displays as today plugin, andhas a companion scheduler application to automatically turn on and off the phone radio at set times, extending batterylife. I would have to say use it and forget mine. I dont know if the progammer is sill supporting it, but it looslike it is worth the $6 fee to register.
If you can still find your version, I'd like to give it a try. Since I'm using Manilla, the today plugin is useless. All I need is the functionality that yours does (and I only need it a couple rare times).
Thanks,
-Mc
OK. I will post it once I find it (I misplaced my old HTC StrTrk, where it was installed.) I may have to just recreate it.
hell, if you're not using the StarTrk, I'd consider buying it off of you, with the program on it. Always liked that phone but just never picked one up.
I'm holding on to the StrTrk as a spare phone (I have a Wing now -aka HTC Herald - and my wife has a Dash - aka Excalibur.) I actually liked this phone while I used it. Its a shame the StrTrk2 never came out, and Win Mo flip phones are dead. A WM6 (or 7) flip phone with a keyboard like the new flip blackberry pearl (or the tmo shadow) would be great. Add a touch screen...whoa. (Why not a touch screen flip phone?) I'll let you know if I ever get rid of it. You have quite a collection of WM phones.
BTW. I cant find the original logger application. I'm rewriting it in Visual Studio 2005. A simple Signal Strength logger. No bells or whistles (ie. no plug-in). Its actually easier in VS2005 than it was in VS2003 due to native code for WM5 and WM6. I just have to add the actual writing to a text file, and it will be done. It is currently capturing the signal strength (not precise.. only a 5 "bar" scale), and the carrier name. I probably will add battery level. I don't know how to do gps, so I cant add that. It will need WinCE CF2 or higher installed.
Oh, and alerts.... I just re-read you liked that feature.
My apologies for digging this thread up, but I'm looking for a signal strength to GPS location logging tool for mapping coverage a bit more accurately than the telco provided maps.
nonpaq said:
I don't know how to do gps, so I cant add that.
Click to expand...
Click to collapse
Is this still the case? It would pretty much just need to save what comes in from the serial port the GPS lives on, wouldn't it?
P3kit does the job
I managed to find this with a serial gen.
seeing as the developer no longer is around it may be OK to provide the gen?
I did not scan the files so use at your own risk.
Works fine on my HD2
[highlight]MOD Edit: No warez allowed on XDA. This is your first and last warning.[/highlight]
Have a look at post number #2 in here. I posted it last week.
It logs Latitude,Longitude,Signal Strength,Mobile Country Code, Mobile Network Code,Location Area Code, and CellID
http://forum.xda-developers.com/showthread.php?t=725568
Nice one - I ended up writing my own, but never got it beyond a first test run where I discovered it needed some work. I also lost my need for it too, so it's just a curiosity thing now.

TURBO GPS fix on Touch Pro

TURBO GPS fix on Touch Pro
(contrary to many of the GPS fixes offered on the net)
I read a lot of fixes on how to make the Touch Pro lock on to GPS faster. Being an ex-owner of toshiba G810, which is the fastest GPS PPC i tried ever before, and noting that it uses the same GPS chip as in the Touch Pro. I tried to emulate the settings in the registry, and i got an excellent result, so would like to share that with you.
1) Many of the fixes on the net talk about turning off the A-GPS , i think this is "wrong" thing, cos when A-GPS is turned off, it would not be able to use the valuable satellite data downloaded from QuickGPS. Therefore, i use Advanced Configuration Tool to turn it back on (ENABLED).
2) I changed the HKLM\SYSTEM\CurrentControlSet\GPS Intermediate Driver\Drivers\GpsOneDevice\PollInterval -> 500 (default is 1000),
which is the same figure as in my Toshiba G810 before.
3) keep the log files untouched, i.e., DO NOT delete:
\windows\GPSLogFile.txt and \windows\GPSLogFileBack.txt
(if you have deleted those 2 files before, just create 2 blank .txt files with those filenames and put them back in \windows. When new GPS data comes in, it will append to the blank files, older data get deleted once reached the 32K limit set below.)
4) keep maximum size of logfile to the default which is 32K
Voila, now my Touch Pro always get 4 to 5 BLUE bars on my mapking (which mean dead lock on!!!) And it it wont fluctutate lock on and off intermittently.
Really urge you to try it, and let me know if you get the same results~~
Cheers everyone!
(For those who dont like tweaking with registries manually, krish_nank has been kind enough to make it into a .cab which i attach here.)
nice experience, i'll try it
hoangtuvn said:
nice experience, i'll try it
Click to expand...
Click to collapse
Please write back to see if it works welll for you. And make sure you use QuickGPS once afterwards to get the satellite data before you start GPS.
I don't have any kind of data connection with my network so AGPS is useless for me, however I did try changing the polling from 1000 to 500 and I managed to get a lock with GPS test within a few minutes inside my own house! Can't remember getting the same results before.
I can only agree that
1 - touching log files is BAD.
2 - reducing poll interval will improve the GPS lag slightly
3 - keeping A-GPS up - in my country there is no A-GPS data available since thats the data provided by the provider over the local network cells. I dont think it has anything to do with the data from Quick GPS. But i might be wrong. Anyway, Quick GPS is your friend.
4 - if you have fix problems its usually either not having Quick gps data or trying to get a fix in a bad area or under a shielded windscreen.
overtweaked?
I changed the pollig interval to 100... is it milliseconds?
I haven't tried it yet but would it be a battery drainer like this (100)?
Actually I was hoping to reduce the delay of map in garmin or oziexplorer (which are my favourites) in higher driving speeds. I tried garmin while driving over 200 km/h and there was a damn nasty delay on the map. Of course it was a stupid risk to watch the screen during these speeds
I tried 1000 (default), 250, 125, and 64 Pollinginterval and none of them were as fast as 500.
well it would be slower because you are polling to often then. best thing to do for your gps speed is update your radio to 1.12.25.19. it doesnt take long to do. then make sure agps is enabled and update your quickgps data. increasing polling from 1000 to 500 might help but i havent tried yet.
ok i changed the polling and with my radio and quickgps i got a lock in under 2 seconds. i havent seen any gps device that could do that.
The Jack of Clubs said:
ok i changed the polling and with my radio and quickgps i got a lock in under 2 seconds. i havent seen any gps device that could do that.
Click to expand...
Click to collapse
Thanks for your testing.
It seems that Toshiba G810 polling setting (i.e. 500) really works for a lot of us.
I was originally so amazed at how G810 could do it, and was so sad to see how bad my Touch Pro (which costs twice compared to the G810) is performing.
I'm glad at least now i can make my Touch Pro just as fast.
hkwildboy said:
TURBO GPS fix on Touch Pro
(contrary to many of the GPS fixes offered on the net)
I read a lot of fixes on how to make the Touch Pro lock on to GPS faster. Being an ex-owner of toshiba G810, which is the fastest GPS PPC i tried ever before, and noting that it uses the same GPS chip as in the Touch Pro. I tried to emulate the settings in the registry, and i got an excellent result, so would like to share that with you.
1) Many of the fixes on the net talk about turning off the A-GPS , i think this is "wrong" thing, cos when A-GPS is turned off, it would not be able to use the valuable satellite data downloaded from QuickGPS. Therefore, i use Advanced Configuration Tool to turn it back on (ENABLED).
2) I changed the HKLM\SYSTEM\CurrentControlSet\GPS Intermediate Driver\Drivers\GpsOneDevice\PollInterval -> 500 (default is 1000),
which is the same figure as in my Toshiba G810 before.
3) keep the log files untouched, i.e., DO NOT delete:
\windows\GPSLogFile.txt and \windows\GPSLogFileBack.txt
4) keep maximum size of logfile to the default which is 32K
Voila, now my Touch Pro always get 4 to 5 BLUE bars on my mapking (which mean dead lock on!!!) And it it wont fluctutate lock on and off intermittently.
Really urge you to try it, and let me know if you get the same results~~
Cheers everyone!
Click to expand...
Click to collapse
I have not had issues with mine with warm or hot starts (most was 30 seconds). What I need to know is from a cold start, how long it takes to perform a fix (you can verify using the HTC GPS tool).
To do a cold start, reset the unit with the button near the USB connector or if you have StartXP, use that.
I think wildboy did do a soft reset, it's kind of standard on XDA.
ok i changed the polling and with my radio and quickgps i got a lock in under 2 seconds. i havent seen any gps device that could do that.
Click to expand...
Click to collapse
Without AGPS? Or is quickGPS similar... can't remember I forget now
agps needs to be enabled for quickgps. agps hindered gps on older radios. the newest radio works really well with agps and quickgps.
Agent Blair said:
I think wildboy did do a soft reset, it's kind of standard on XDA.
Click to expand...
Click to collapse
I kinda figured as much, but I just want to be sure. Mainly because with my current settings I am getting the same performance, except when I have a cold start. I am trying to figure out a way to get better cold start performance.
Thanks a million .. your tweak is working great. now i can get my GPS locked in 7 seconds
Once again thank you.
omg, this worked for me indoors
I never played with the Log file....
I do not have a GPS*.txt file in my windows folder, using EnergyROM 2.0 4.12.09...
Will those/can those files be generated by a program other then quick gps or visualgpsce?
BBM-Lee said:
I never played with the Log file....
I do not have a GPS*.txt file in my windows folder, using EnergyROM 2.0 4.12.09...
Will those/can those files be generated by a program other then quick gps or visualgpsce?
Click to expand...
Click to collapse
Just install AdvancedConfig, this will allow you to edit the buffer size of the log files and verify their are log files in that ROM. Then you just need a Registry Editor to adjust the polling time.
Pretty strange but I haven't modified mine at all and it locks on in about 10-15 seconds which I think is pretty good, or isn't it?
TriAxisFL said:
Just install AdvancedConfig, this will allow you to edit the buffer size of the log files and verify their are log files in that ROM. Then you just need a Registry Editor to adjust the polling time.
Click to expand...
Click to collapse
Sorry, slight miscommunication..
I'm using EnergyROM 2, and i'm familiar with Adv. Config & Registry editing..
Default setting was no logging, and I can't point adv. config to the log file that doesn't exist.
If i just make ablank log/text file, and point it, will that work? Or do the log files need to have certain information in them in order to not screw up?

Altering 3G MTU on Android, how ?

Hello,
I have noticed that a lot of sapphire roms (even the original one) have some problems on H3G and some other networks here (i.e. Vodafone Italy in my case), on my 32A magic.
Download stalls on 2G, uploads may be very slow on 3G. This is because mtu path discovery seems not working very well or maybe some servers block fragmentation request packets, etc etc.
I am wondering if it's enough to issue a "ifconfig rmnet0 mtu XXXX" as root to modify the MTU in android, and how to make this a permanent change in the system, so that it won't lose it for each bootup/interface up&down .
I have investigated this problem for weeks, thinking in the first place it was a problem with the build.prop kernel ril.parameters. Indeed setting this parameters to more conservative values fix that (ie gprs class 10 and not 12, hep disabled, etc), but it doesn't seem to be the main issue.
As I want to conduct some further testing I am wondering if someone knows how to set MTU in a permanent way on android for the remote (GPRS/3G) interfaces.
thanks a lot.
I would also like to know this, I have 3G and it does stall alot. While downloading from market it will go up to 99% then freeze
ziokendo said:
Hello,
I have noticed that a lot of sapphire roms (even the original one) have some problems on H3G and some other networks here (i.e. Vodafone Italy in my case), on my 32A magic.
Download stalls on 2G, uploads may be very slow on 3G. This is because mtu path discovery seems not working very well or maybe some servers block fragmentation request packets, etc etc.
I am wondering if it's enough to issue a "ifconfig rmnet0 mtu XXXX" as root to modify the MTU in android, and how to make this a permanent change in the system, so that it won't lose it for each bootup/interface up&down .
I have investigated this problem for weeks, thinking in the first place it was a problem with the build.prop kernel ril.parameters. Indeed setting this parameters to more conservative values fix that (ie gprs class 10 and not 12, hep disabled, etc), but it doesn't seem to be the main issue.
As I want to conduct some further testing I am wondering if someone knows how to set MTU in a permanent way on android for the remote (GPRS/3G) interfaces.
thanks a lot.
Click to expand...
Click to collapse
theres some method to use bettercut to lock the phone to only be in 3g not to connect to gprs or edge connections
lemme search for it and ill post the link
Zarboz said:
theres some method to use bettercut to lock the phone to only be in 3g not to connect to gprs or edge connections
Click to expand...
Click to collapse
In htc based roms there's the check "3G Only".
But I am just interested to know how to lower the mtu, because here in my flat I have only 2G coverage.
There's a paid app on the market that does exactly that if you're root (lowering the mtu), is called something like "3UK Fixer", so there should be a way.
(it's not like i don't want to pay 1£ btw for that app, is just that is for 3UK and installs a different APN.. i am just interested in applying the MTU fix)

4G LTE Rapid Power Burn Issue

High Level Symptoms:
- I notice battery has drained very quickly in a short time even when I have not been using phone (i.e. idle with display off)
- Phone feels noticeably warm/hot even when I have not been using phone (e.g. like it does while charging)
- Issue only seems to happen when running in 4G LTE mode
- I have gathered detailed usage statistics and do not believe there are any miss-behaving apps or system processes responsible
- I have noticed issue start most often near my office (in midtown NYC)
Note: This is where I use the phone on battery the most, so it may just be sampling bias
- I can temporarily stop the rapid power burn by switching out of 4G LTE mode (i.e. to 3G mode, or disabling radio)
- I have not found a way to stop the issue in 4G LTE mode once it starts except by restarting phone
(things I tried without success: toggling airplane mode, switching to 3G and back to 4G, radio off/on, and moving to different location/tower; rapid burn starts back up again as soon as 4G LTE mode is re-enabled)
Power Burn Rate:
- Data captured using Battery Monitor Widget which I have set to sample/log battery available % and usage every minute (this is a great app!)
- Available % dropping at a rate of about 20% / hour while phone is idle w/ screen off (my normal is about 5% / hour)
- Usage shows a very flat baseline of about 1000 mW / 250 mA (normal baseline is more like 100 mW / 40 mA)
(by baseline I mean many samples are equal to that baseline value with the rest being spikes up to greater values; no observed values are less than the baseline)
Background Info:
- My phone is unrooted and running stock firmware w/ the Verizon OTA upgrade (installed ~2011-05-19)
- I have noticed this issue many times since first getting the phone (~2011-04-12), and this issue is still present even with the newest LTE radio FW in the OTA update
- I am new to Android (~2 months in) but I am diving in deep with all the amazing tools both built-in and via add-on apps; I have collected a range of data/observations from numerous sources that are detailed in this post
My hypothesis is that the LTE radio hardware is responsible for this power burn. Most likely due to a software/firmware bug, but I'm not sure how to confirm that.
I wonder how common this issue is. I remember reading other posts on the forum that sound like the same thing. For example: http://forum.xda-developers.com/showthread.php?t=1008761
Can anyone else confirm they have seen this issue? If this issue is wide spread, I think it may be a contributing factor to the wide spread reports of 4G LTE a lot of battery.
I do not think this is the only factor that causes 4G LTE to use more power than 3G. I have read the reports, and personaly seen, higher 4G LTE power consumption when in low signal areas. However, I belive that to be independant from the burn issue I am describing here. The worst case power consumption I've seen that I think was "low LTE signal" related was only about 500 mW / 130 mA. The burn issue I'm refering too consumes power at about twice that rate and happened when I had strong signal. I had three to four of four possible bars. Also, I grabbed more detailed information:
----------
Phone info
reached using "LTE OnOff" app, "Network" app, or by dialing *#*#4636#*#* -> Phone information
Signal strength: -67 dBm to -80 dBm, 3 to 4 asu
Location: BID = 39b SID = 16 NID = 4
LAT = 7fffffff LONG = 7fffffff
Network Type: CDMA + LTE/EvDo auto
I believe this is good signal (e.g. issue not due to a low signal condition)
==================
Usage Data Capture
I briefly connected to power to reset the statistics after noticing the issue had started and and captured about an hours worth of data. My understanding of the data is that the display was off for almost all the time, and no apps or system processes are listed as using any significant amount of CPU/sensors in comparison to the hour data collection window.
-----------
Battery Use
reached using Settings -> About Phone -> Battery Use, or Battery Monitor Widget -> Usage
When last unplugged for 57m 12s
Display 30%
* Time on 1m 11s
* Auto Brightness
Cell Standby 21%
* Time on 57m 12s
Phone idle 19%
* Time on 56m 1s
Foursquare 11%
* CPU total 8s
* CPU foreground 6s
* GPS 26s
* Data sent 13.59 KB
* Data received 379.93 KB
Android System 7%
* CPU total 41s
* CPU foreground 2s
* Data sent 12.09 KB
* Data received 20.27 KB
Android OS 6%
* CPU total 39s
* Data sent 20.11 KB
* Data received 136.25 KB
Pandora 6%
* CPU total 35s
* Data sent 1.83 KB
* Data received 27.16 KB
---------------
Battery History
reached using Battery Monitor Widget -> Statistics, or by dialing *#*#4636#*#* -> Battery history
since last unplugged
CPU usage
* Android System (Total time:39s)
* Pandora (Total time:35s)
* suspend (Total time:31s)
* Foursquare (Total time:7s)
... (Note: more apps listed but with smaller total times)
Sensor usage
* Android System 29m 47s
* AccuWeather.com 28m 36s
(Note: after this capture I uninstalled AccuWeather.com app and retested. It wasn't listed anymore, but power drain behavior was unaltered)
Partial wake usage
* K-9 Mail 7m14s
* Android System 5m 4s
* Seesmic 9s
... (Note: more apps listed but with smaller times)
Other Usage
* Running (27.6%)
* Screen on (2.1%)
-------------------
CPU Spy v0.3.0 beta
Note: timers reset at begining of measurement interval
Time in state
1024 MHz 4:21 7%
768 MHz 0:54 1%
368 MHz 0:35 0%
245 MHz 12:11 20%
Deep Sleep 41:34 69%
This is a typical distribution I see when the phone is mostly idle (CPU sleeping for most of the time).
=================
Variation testing
After the data capture I systematicly tried several methods to see what it took to stop the abnormal drain in 4G LTE mode. In the end only rebooting the phone did it.
Set preferred network type: "CDMA auto (PRL)" (i.e. 3G mode) -> normal power usage (5:00pm-5:18pm)
Set preferred network type: "CDMA + LTE/EvDo auto" (i.e. 4G mode) -> abnormally high power usage (5:18pm to 5:43pm)
Set airplane mode (i.e. radio off) -> very low power usage (5:43pm to 6:54pm)
Turned off airplane mode (i.e. 4G mode) -> abnormally high power usage
Set preferred network type: "LTE mode" (i.e. ONLY 4G mode) -> abnormally high power usage
Set preferred network type: "CDMA + LTE/EvDo auto" (i.e. 4G mode) -> abnormally high power usage
Moved to a new place:
Signal strength: -65 dBm 4 asu
Location: BID = 23c SID = 16 NID = 4
LAT = 7fffffff LONG = 7fffffff
-> abnormally high power usage
Phone info "Turn off radio" button -> very low power usage
Phone info "Turn on radio" button -> abnormally high power usage
Restart phone -> normal power usage
I experience the same problem. My guess is that the radio firmware gets into a bad state when you are in an area with bad coverage.
I have been in a state where disabling data didn't stp the battery drain, only entering airplane mode would stop it.
crpalmer said:
I experience the same problem. My guess is that the radio firmware gets into a bad state when you are in an area with bad coverage.
I have been in a state where disabling data didn't stp the battery drain, only
entering airplane mode would stop it.
Click to expand...
Click to collapse
I originally thought the same thing about the issue starting while in poor coverage, but since I have seen it occur multiple times in a good coverage area I began to doubt that was the case. The extra power consumption I usually get while in poor coverage is less in magnitude, and varies much more, and goes away when I have good coverage again. This issue feels distinctly different to me.
When you say disabling data didn't stop the drain you experienced, do you mean turning off Settings -> Wireless & networks -> Mobile networks? I haven't tried playing with that option. I'll give it a try next time I see the issue too.
You said entering airplane mode would stop it. Did you have the same experience that when you turned airplane mode off that the drain started back up again until you restarted?
Thanks
Excellent post, I would venture a guess that your background is in one the sciences.
One thing I noticed you didn't try was connecting through wifi. I believe this will render the 4g radio on but not in use. If the issue persists, it could help narrow down the cause.
As far as attempting to fix it, you can factory reset it or go to verizon for a replacement.. but that doesn't do much for others with this problem.
I have been having the same issue, both on stock and BAMF 1.6. Thanks for looking so thoroughly at this problem. It appears not everyone is affected. Can someone confirm? If so, exchanging the could be the solution.
Sent from my ADR6400L using XDA App
To test your hypothesis, I'd recommend turning off LTE somehow. My suggestion for non-rooted phone:
Dial ##778#
Chose edit mode, password: 000000
You should be able to turn off LTE in Modem Settings->Preferred Mode
Please let us know your finding.
Nice work on the research!
The scenario you described happened to me yesterday.
I was in a building where I didn't get any reception at all. I noticed the phone started to warm up. By the time I got outside and the phone re-established a connection with the 4g network, it was extremely warm and the phone was at 7% life begging to be charged.
This has happened to me on two other occasions but I don't recall being in an area of zero to poor reception.
My bolt is also rooted running the BAMF Remix 1.6.
agdaniels said:
Excellent post, I would venture a guess that your background is in one the sciences.
One thing I noticed you didn't try was connecting through wifi. I believe this will render the 4g radio on but not in use. If the issue persists, it could help narrow down the cause.
As far as attempting to fix it, you can factory reset it or go to verizon for a replacement.. but that doesn't do much for others with this problem.
Click to expand...
Click to collapse
Thank you. Your guess is spot on; I did my Ph. D. in computer science.
I have not tried switching to WiFi. Next time I see the issue I will put that to the test. I find I haven't been using WiFi much with this phone since I have lower standby power consumption in 3G mode when I don't need the speed. When I do want more speed, I find here in NYC 4G LTE is actually significantly faster than either my home or work Internet connection (Cable and DSL respectively) (Crazy!). Also, here in NYC the 2.4 GHz band is VERY crowded so WiFi can slow down at times even on a good wired Internet connection. I wish this phone was 5 GHz WiFi capable to help avoid this particular issue.
My intuition is that this is a radio firmware issue so I have my doubts that a factory reset or even a replacement would fix anything. Factory reset would help if there were misbehaving apps or screwed up settings on my phone, but this seems unlikely. I'll probably need to root my phone so I can back it up before I try a factory reset. A replacement would only help if there was a hardware fault. Part of the purpose of this thread is to help gauge if many other people have this problem. The more that do, the less likely it is an abnormal HW fault with only my phone, and more likely a bug or other HW errata issue that hasn't been worked around correctly.
I think it is still too early in the game to make the call that it is not fixable in FW. I was aware that this LTE network/chipset is quite new and this phone was likely to have some rough spots at the start. Verizon/HTC/Qualcomm have only made one OTA release so far, and even that release has major bugs that were not present in the original stock FW (e.g. the frequent spontaneous rebooting when in 3G mode). Forums like this seem like great places for us users to publicly characterize issues we encounter. I hope it helps the engineers involved in making fixes and that we get updates not too far down the line.
cuguy said:
To test your hypothesis, I'd recommend turning off LTE somehow. My suggestion for non-rooted phone:
Dial ##778#
Chose edit mode, password: 000000
You should be able to turn off LTE in Modem Settings->Preferred Mode
Please let us know your finding.
Click to expand...
Click to collapse
Thanks for the suggestion.
If you look at the last part of my post under the "Variation Testing" heading, I believe I did try a number of configurations with LTE off. Each case where LTE was off I saw normal or low power consumption. This is why I grew to suspect the LTE radio in the first place.
The technique I used for switching between 3G and 4G modes was actually the "Set prefered network type" drop down on the "Phone info" menu that can be reached using "LTE OnOff" app, "Network" app, or by dialing *#*#4636#*#* and selecting "Phone Information".
I have used the dial ##778# to get the ESPT menu before, but that was to modify the "Rev. A" setting from "eHRPD" to "Enable" as a work around to re-enable 3G EVDO during the few days of nation wide 4G LTE & 3G SVDO outage we had a month or so ago. BTW, it looks like I had by phone set to the non-stock "Enable" setting rather than "eHRPD" for the original data capture. I switched this back to "eHRPD" and I'll report if I have the issue again. I was last playing with this setting to see if had any effect on the random reboots after the OTA while on 3G, but it did not.
In the ESPT -> Modem Settings -> Preferred Mode drop down I only see the options for:
- Automatic
- HDR Only
- Digital Only
- CDMA Only (selected by default)
- CDMA HDR Only
There is also a a Preferred Mode(9k) drop down that has these options:
- Automatic
- HDR Only
- LTE Only
- HDR LTE only (selected by default)
I believe that these are settings for the voice radio and the data radio respectively. See the third page of the excellent Anandtech review of the HTC Thunderbolt: <Sorry, I am a new xda-developers forum member so it won't let me post external links yet.>
Do you have suggestions on how to set these? I am unfamiliar with the HDR acronym and haven't turned up anything that seems relevant in my Google searches.
I had another instance of the 4G LTE power burn issue today. I tried a few of the above suggestions.
I enabled WiFi and logged on to an access point. This did not stop the abnormally high power burn. Instead it went up slightly; I assume this was the extra power for the WiFi radio.
I also tried turning off Settings -> Wireless & networks -> Mobile networks. That resulted in the 4G LTE icon going away but the signal bars were still showing. I couldn't use the Internet but a SMS came through in this mode. This mode did not stop the power burn either.
The burn stopped only when I rebooted.
The reboot happened when I dialed ##778# to get the ESPT menu and switched the "Rev. A" setting from "Enable" to "eHRPD" and this time remembered to commit the changes (forgot to when I posted above). Committing the changes auto-rebooted the phone, which returned me to normal power consumption. I will report if I have the problem again now that I have confirmed I am back in the stock eHRPD mode.
Most of today I was in very good signal conditions, judging by the time the drain started, I could have been out on a errand in the neighborhood. So I can't 100% guarantee that the 4G signal was high the whole time.
Does anyone know of an app that works on the Thunderbolt that can log signal strength over time and preferably graph it too (e.g. similar to Battery Monitor Widget). I have tried to download and use a few without success including: Open Signal Maps, Network Signal Info, RF Signal Tracker, and Signal Finder. Some of these apps didn't work at all (I suspect 4G signal is reported a bit differently and this confuses some of them). Some work in general but I can't seem to get the logging I'm looking for.
Thanks!
OdinGuru said:
I originally thought the same thing about the issue starting while in poor coverage, but since I have seen it occur multiple times in a good coverage area I began to doubt that was the case. The extra power consumption I usually get while in poor coverage is less in magnitude, and varies much more, and goes away when I have good coverage again. This issue feels distinctly different to me.
When you say disabling data didn't stop the drain you experienced, do you mean turning off Settings -> Wireless & networks -> Mobile networks? I haven't tried playing with that option. I'll give it a try next time I see the issue too.
You said entering airplane mode would stop it. Did you have the same experience that when you turned airplane mode off that the drain started back up again until you restarted?
Thanks
Click to expand...
Click to collapse
By disabling data, I was actually using the notification tools in most rooted roms. That should be equivalent to what you said.
Toggling airplane mode toggled the battery drain problem until it failed to enter airplane mode and I had to reboot.
I see the same thing
Where I live at home we only have 3G at work I have 4G. The phone will get itself into some kind of mode at work and burn through the battery in 4-5 hours. So I keep it charging on my desk all day. If I didn't, some days it wouldn't make it till lunch.
OdinGuru said:
Thank you. Your guess is spot on; I did my Ph. D. in computer science.
I have not tried switching to WiFi. Next time I see the issue I will put that to the test. I find I haven't been using WiFi much with this phone since I have lower standby power consumption in 3G mode when I don't need the speed. When I do want more speed, I find here in NYC 4G LTE is actually significantly faster than either my home or work Internet connection (Cable and DSL respectively) (Crazy!). Also, here in NYC the 2.4 GHz band is VERY crowded so WiFi can slow down at times even on a good wired Internet connection. I wish this phone was 5 GHz WiFi capable to help avoid this particular issue.
My intuition is that this is a radio firmware issue so I have my doubts that a factory reset or even a replacement would fix anything. Factory reset would help if there were misbehaving apps or screwed up settings on my phone, but this seems unlikely. I'll probably need to root my phone so I can back it up before I try a factory reset. A replacement would only help if there was a hardware fault. Part of the purpose of this thread is to help gauge if many other people have this problem. The more that do, the less likely it is an abnormal HW fault with only my phone, and more likely a bug or other HW errata issue that hasn't been worked around correctly.
I think it is still too early in the game to make the call that it is not fixable in FW. I was aware that this LTE network/chipset is quite new and this phone was likely to have some rough spots at the start. Verizon/HTC/Qualcomm have only made one OTA release so far, and even that release has major bugs that were not present in the original stock FW (e.g. the frequent spontaneous rebooting when in 3G mode). Forums like this seem like great places for us users to publicly characterize issues we encounter. I hope it helps the engineers involved in making fixes and that we get updates not too far down the line.
Click to expand...
Click to collapse
You are absolutely correct on all three points, my main focus with the two suggestions were background data for the factory reset and faulty hardware for the replacement.
If you have the ability to disable all background data syncing while on 4g- on the application side, sense ui side, and the android side you could completely rule out software being the cause. My thoughts with this are some background service is keeping the radio active, causing the burn.
The replacement device would help to narrow down whether the issue lies on the device side, or if its more related to the towers/the way lte functions. The latter is bad news for you. My thoughts on this are that some people report no issues running lte, while others are having similar problems as you have reported; I doubt that it is faulty phone hardware, but its possible.
I share your conclusion that this is a firmware(baseband) issue. Actually going in and manipulating it would require root, a considerable understanding of how the interaction between hardware and software works, and the abilty to make tweaks and test them. I will also contact some people more knowledgable then myself and see if they want to chime in on the matter.
crpalmer said:
By disabling data, I was actually using the notification tools in most rooted roms. That should be equivalent to what you said.
Toggling airplane mode toggled the battery drain problem until it failed to enter airplane mode and I had to reboot.
Click to expand...
Click to collapse
Excellent idea. I then I was able to execute the test you suggested yesterday when I re-encountered the issue. I saw the exact same behavior you reported: even though I disable applications data over LTE, the drain did not stop. This is strong supporting evidence that it is not an issue with some kind of rouge app / sync settings.
Drain toggling with airplane mode is the exactly consistent with my observations as well. Sounds like we have confirmed you having the exact same burn issue.
Thank you for the feedback and confirmation.
mcargil05 said:
Where I live at home we only have 3G at work I have 4G. The phone will get itself into some kind of mode at work and burn through the battery in 4-5 hours. So I keep it charging on my desk all day. If I didn't, some days it wouldn't make it till lunch.
Click to expand...
Click to collapse
This is consistent with my observations of the burn issue. The baseline power consumption I observed is about 20% of the battery per hour while phone is idle with screen off. That would correspond to the phone burning through a full charge in 5 hours even if you didn't use it at all. Add any extra actual usage on top of that and 4-5 hours of life sounds very plausible. That assumes you have the problem right away though (the worst case).
I typically see a variable amount of time of normal consumption before the issue starts. For instance, let's say I've been running normally for 3 hours and am at 80% before the issue starts. Then I'd quickly burn through the last 80% in 4 hours or less. In that case I'd get less than 7 hours of total battery life (e.g. not making it through the day). If my normal usage had continued, it should be more like 15 hours (e.g. more than enough for a long day and needs charging every night).
There is still the question if this issue is related or not to 4G signal levels. What do you normally see in the office? Number of bars is useful, and also the more detailed dBm number can be found in Settings -> About Phone -> Network.
Thank you for your report.
agdaniels said:
You are absolutely correct on all three points, my main focus with the two suggestions were background data for the factory reset and faulty hardware for the replacement.
If you have the ability to disable all background data syncing while on 4g- on the application side, sense ui side, and the android side you could completely rule out software being the cause. My thoughts with this are some background service is keeping the radio active, causing the burn.
The replacement device would help to narrow down whether the issue lies on the device side, or if its more related to the towers/the way lte functions. The latter is bad news for you. My thoughts on this are that some people report no issues running lte, while others are having similar problems as you have reported; I doubt that it is faulty phone hardware, but its possible.
I share your conclusion that this is a firmware(baseband) issue. Actually going in and manipulating it would require root, a considerable understanding of how the interaction between hardware and software works, and the abilty to make tweaks and test them. I will also contact some people more knowledgable then myself and see if they want to chime in on the matter.
Click to expand...
Click to collapse
In the most recent test I disabled "Mobile Networks" which effectively shutdown data service. I also tested switching to WiFi which should have redirected all data away from the 4G LTE radio. Neither one of these stopped the power burn. Do you agree this is sufficient enough to rule out apps/services?
I noticed on the Phone info screen there are some counters for number of bytes sent over the radio. Next time I have the issue perhaps I'll keep track of how those change when I'm having the issue vs not.
I agree that trying replacement HW would be a useful data point to help identify if the issue is inherent or tower related. I'm not quite ready to jump through all the hoops with Verizon to do it myself yet. I'd want to root first to create a backup of my current setup first to reduce the pain of the procedure. And I'll probably give them the benefit of the doubt and wait for the next OTA to give them another shot at fixing the issue with FW.
Part of our questions would be answered if there was indeed a user out there that runs 4G LTE and can document that they do not have this issue. Does anyone out there run Battery Monitor Widget or similar and can say they have never seen the tell-tail pattern of power burn I am talking about?
I really wish Android had a built in screen capture feature. I need to get adb installed and setup on my computer so I can post examples of what the graphs look like; I think that would help other users to identify the issue as it happens so they know when to re-boot to save what is left of their battery.
I agree there is very little we as users can do to fix the issue if it is in the radio FW. As you say, it would indeed take very detailed knowledge of the HW. Also, I think it would be impossible without the radio FW source code. Although I haven't looked through the HTC released code, I would be very surprised if this was included. It wouldn't be covered under the Android or Linux open source licenses as it likely originally came from Qualcomm and is considered proprietary. Without that, we can only hope that Qualcomm/HTC/Verizon work together to get it figured out. The good news is that they all have a good business case to do so. This LTE chipset is likely to be used in several phones so they need these issues resolved before it affects their whole lineup.
Anyone know if the new Samsung Droid Charge has this issue too?
After experiencing all the same issues myself, I have noticed that this seems to have been addressed in the leaked Gingerbread radio. Might be worthwhile to repeat testing using that radio and then somehow compare code.
Sent from my ADR6400L using XDA Premium App
I would have to agree you've sufficiently ruled out software, the point about the gingerbread build not having issues is worth noting though. Can someone confirm the 2.3 release has new radio firmware? It wouldn't be difficult at all to pull it out and flash it if it does
My thunderbolt will be in hand Monday, I don't have the phd you have in c.s (mines just a bs) but I've been in the business long enough to throw some graphs together. We'll compare notes then if we don't find resolution sooner.
I experience the same problem in North Phoenix when running 4GLTE in a weak 4g signal area. It doesn't happen too often if I'm in a heavily blanketed 4g area.
EDIT. I'm running rooted. OC to usually 1400 mhz. I'm constantly being synced with the Exchange Server. My phone gets super hot when running navigation plus 4GLTE. Temperature gets up to around 110 degrees Fahrenheit.
When I notice my phone heating up, I'll switch to CDMA prl and immediately my battery temperature starts dropping to normal levels, ie. 86 degrees Fahrenheit.
At the time I was running on different radio combinations. Such as, CDMA. 6 and lte. 7 radio combo. I have recently switched to Gingerbread so more testing is needed.
Had a spare minute to look up the radio, looks like its bricking certain devices after flashing. Not completely ruling it out, maybe you can flash it, test it, then flash it back, but there is some risk involved.
Whatever the case, its reassuring to know updates are coming eventually.
Here is a link for reference:
http://forum.xda-developers.com/showthread.php?t=1098363&page=70

Categories

Resources