tickerguy
Android Enthusiast
To clear battery stats (again folks, use the source if you want to know how things work ;-))
1. Charge until at 100% and watch the charge CURRENT. It will eventually drop well into single-digits. Do not use anything that "estimates"; either use Battery Status widget set correctly or use adb shell and look at "dmesg" to see when you're in that state. Note that the Triumph goes into trickle mode at 90% and turns the LED green - this is good, not bad as it minimizes battery overheating and degradation of life risk.
2. Reboot into Clockwork and wipe the battery stats.
Now you're good and the readings should be accurate.
Be aware that the last 10% or so is really on the ragged edge. The BATTERY has a protective circuit in it and will cut off the current when it gets near an unsafe charge level. This is a requirement for all consumer LiION batteries because an overdischarged state can cause fires when the battery is subsequently recharged; the overdischarged state can result in internal shorts which in turn cause overheating and burst case when the charge current is later applied. Since lithium burns on exposure to moisture and there is always water vapor in the air, well, you can figure out what happens.
I'm moving to a T-Mobile plan that's $45/mo and is postpaid, but it's unlimited across the board with a 5Gb soft cap on data. It also includes roaming access (incidentally, T-Mobile's prepaid includes roaming access - they're the only carrier I know of that does.) It's an unbeatable deal; I've never gone over 5Gb on the data side in a month even when traveling and the unlimited voice and SMS appeals to me, plus the full-rate AMR codec on the voice side produces dramatically superior voice quality for calls. CDMA just plain sucks on the voice side guys; always has, always will, and AT&T's half-rate AMR codec blows donkey nuts too. I use my phone for business as well as personal purposes, so all this matters. I have to be a little "careful" with tethering with T-Mobile, but unlike Virgin where it's just flatly a TOS violation (and they can expel you for it if they catch you) I can buy the add-on with T-Mo (and on this plan it's both $10/month and can be turned on and off as desired); I don't need it often and when I do it's typically a VPN session and thus is an encrypted data stream anyway and is basically impossible to determine that I'm not using OpenVPN off the handset itself (which is perfectly legitimate.)
Anyway, that's the deal. I have b.07 in the pipe; what I'd like to fix before I drop it is the haptic problem but I'm not getting anywhere with it; what I thought might do it turned out to be a dead end. I've been running it for a week without incident but it has basically no change other than a calibration change in the light sensor at the kernel level and the corresponding mods to the base table in CM7 - other than that it's what you're running now as b.06.
1. Charge until at 100% and watch the charge CURRENT. It will eventually drop well into single-digits. Do not use anything that "estimates"; either use Battery Status widget set correctly or use adb shell and look at "dmesg" to see when you're in that state. Note that the Triumph goes into trickle mode at 90% and turns the LED green - this is good, not bad as it minimizes battery overheating and degradation of life risk.
2. Reboot into Clockwork and wipe the battery stats.
Now you're good and the readings should be accurate.
Be aware that the last 10% or so is really on the ragged edge. The BATTERY has a protective circuit in it and will cut off the current when it gets near an unsafe charge level. This is a requirement for all consumer LiION batteries because an overdischarged state can cause fires when the battery is subsequently recharged; the overdischarged state can result in internal shorts which in turn cause overheating and burst case when the charge current is later applied. Since lithium burns on exposure to moisture and there is always water vapor in the air, well, you can figure out what happens.
I'm moving to a T-Mobile plan that's $45/mo and is postpaid, but it's unlimited across the board with a 5Gb soft cap on data. It also includes roaming access (incidentally, T-Mobile's prepaid includes roaming access - they're the only carrier I know of that does.) It's an unbeatable deal; I've never gone over 5Gb on the data side in a month even when traveling and the unlimited voice and SMS appeals to me, plus the full-rate AMR codec on the voice side produces dramatically superior voice quality for calls. CDMA just plain sucks on the voice side guys; always has, always will, and AT&T's half-rate AMR codec blows donkey nuts too. I use my phone for business as well as personal purposes, so all this matters. I have to be a little "careful" with tethering with T-Mobile, but unlike Virgin where it's just flatly a TOS violation (and they can expel you for it if they catch you) I can buy the add-on with T-Mo (and on this plan it's both $10/month and can be turned on and off as desired); I don't need it often and when I do it's typically a VPN session and thus is an encrypted data stream anyway and is basically impossible to determine that I'm not using OpenVPN off the handset itself (which is perfectly legitimate.)
Anyway, that's the deal. I have b.07 in the pipe; what I'd like to fix before I drop it is the haptic problem but I'm not getting anywhere with it; what I thought might do it turned out to be a dead end. I've been running it for a week without incident but it has basically no change other than a calibration change in the light sensor at the kernel level and the corresponding mods to the base table in CM7 - other than that it's what you're running now as b.06.
