Related
Well members,
I really want to know who has their battery percentage the same as in winmo. I know it has a issue with the battery driver, but still i am curious.
My battery.capacity=4462 Units.
Current percentage in Android 41% at the moment
Current Units in Dmesg 2988Units
After restart in Winmo it says 53%
If I calculate this, (2988/4462)*100= almost 67%
Someone knows what i am doing wrong?
PHP:
I will charge my battery again tonight, plug usb out, read units, change Units again in default.txt. Then I will keep for myself updates trough the day of the current data. Will post again tomorrow with updates.
Hope to hear what other people are experencing
Don't blame my poor english, Firefox English dictionary isn't downloaded/installed yet
battery
Yeah is really not understandable of how to calibrate the battery, iv been trying it for the past 2 weeks...and i still have not get it right! well..i got 4320
My battery reports completely wrong in android, to the point where it's 30-50% left then dies as it's really flat!
Hmm,
Code:
Try to use this line in default.txt if you don't got it yet
board-kaiser-battery.battery_capacity= ****
**** stands for the unit you get in with Dmesg in terminal of android after a full charge.
I can say that doesn't even is correct for me.
But I Tried another value. I read (translated) on japanese forum dat you have to put the mAh instead of units.
So I tried with 1350 (Of my Kaiser160).
Now my android shuts of when it's 15% instead of 59%. He also said something like, try to double the value. I am testing now with the value 2700
You guys should try :O
I've to say, after changed to 1350, i had a more realised idea how android does with the battery. I can say that android sucks more battery than winmo.
battery
assangflexx said:
Hmm,
Code:
Try to use this line in default.txt if you don't got it yet
board-kaiser-battery.battery_capacity= ****
**** stands for the unit you get in with Dmesg in terminal of android after a full charge.
I can say that doesn't even is correct for me.
But I Tried another value. I read (translated) on japanese forum dat you have to put the mAh instead of units.
So I tried with 1350 (Of my Kaiser160).
Now my android shuts of when it's 15% instead of 59%. He also said something like, try to double the value. I am testing now with the value 2700
You guys should try :O
I've to say, after changed to 1350, i had a more realised idea how android does with the battery. I can say that android sucks more battery than winmo.
Click to expand...
Click to collapse
Hi there, well iv tried the above instructions, but i found out something is strange, i deleted the batterystats.bin and then make sure that the board-kaiser-battery.battery_capacity= 1400 (my battery is 1400) i adb pushed it to my device....but strangely when i reboot....it changes back to 2700 automatically....i think this is the reason why we still cannot calibrate our battery for now...since as soon as my battery reaches down to 20% and suddenly 4% then shuts off...
Perhaps do you guys think that to keep our kaiser's stanbby time longer rather buy an external battery charger and make sure that battery is charged up fully.so that we can utilize the battery fully.
i think for now we should just try an carry our chargers with us say to work or school..and charge it over night....
Usually i wouldnt charge my phone for bout 2 days but it will last..but now i realieze its a must if ima use android..
Cheers
i never trust the battery status when charging.
if I am looking for a full charge I wait until dmesg reports a charge of less than approx 30mA. if it shows charge at 100/100 and it still is showing over 100mA then it is not done charging.
also if it is showing less than 30mA and a charge of less than 100/100 it really is done charging. don't wait for 100/100 if it is done charging.
as far as battery usage is concerned, one thing to not as far as a difference between winmo and android:
winmo shuts down many services when sleeping.
such as in winmo if you are playing music and it goes to sleep, music shuts off.
and same for wifi.
android doesn't seem to shut of anything except the screen.
maybe there is settings for what is to be run while sleeping.
I had a program in winmo that allowed you to turn on or of services during sleep.
mnjm9b said:
i never trust the battery status when charging.
if I am looking for a full charge I wait until dmesg reports a charge of less than approx 30mA. if it shows charge at 100/100 and it still is showing over 100mA then it is not done charging.
also if it is showing less than 30mA and a charge of less than 100/100 it really is done charging. don't wait for 100/100 if it is done charging.
as far as battery usage is concerned, one thing to not as far as a difference between winmo and android:
winmo shuts down many services when sleeping.
such as in winmo if you are playing music and it goes to sleep, music shuts off.
and same for wifi.
android doesn't seem to shut of anything except the screen.
maybe there is settings for what is to be run while sleeping.
I had a program in winmo that allowed you to turn on or of services during sleep.
Click to expand...
Click to collapse
yep...you are right....maybe we should just focus on dmesg for now...by the way, do you guys have the same problem as i have...20% then suddenly drops to 4% then shuts off?
twinklesam123 said:
yep...you are right....maybe we should just focus on dmesg for now...by the way, do you guys have the same problem as i have...20% then suddenly drops to 4% then shuts off?
Click to expand...
Click to collapse
i dont have that problem..however today, i charged to 100 percent and talk to my gf on the phone for about an hour..it went down to about 40 percent..i set it down and didnt touch it for about 20 minutes..and it went up to about 70 percent..very weird
Yes, i can tell you, in the settings under connection (i think, i have dutch android language) you can define a setting that wifi goes to sleep after your screen sleeps.
Code:
Also,best way to use android is that you have to
1. fully charge your phone in android and keep the powercable on it,
2. look in dmesg for the units. when te units aren't getting bigger, than that's the last one that is charged.
3. write down or do something with your mind :D
4. restart to winmo, KEEP POWERCABLE ON
5. change and/or put a line to your default.txt "board-kaiser-battery.battery_capacity= ****"
change **** to your units you have written down
6. after you changed units, start to android.
But still it doesn't is good yet. I experienced that 1350 value is the most effective one. When android said 15%, i tought lets restart and look what winmo says. winmo was at 1%.
Also, i was a little cocky and without 100% battery i started android. I can say, it took ages that 100% was changed to 99%. Also you never know when battery is going to die
Maybe someone can do something with this.
Battery
i think for now...we should just look at the charge in dmesg....which is the most accurate telling for now...
twinklesam123 said:
Hi there, well iv tried the above instructions, but i found out something is strange, i deleted the batterystats.bin and then make sure that the board-kaiser-battery.battery_capacity= 1400 (my battery is 1400) i adb pushed it to my device....but strangely when i reboot....it changes back to 2700 automatically....i think this is the reason why we still cannot calibrate our battery for now...since as soon as my battery reaches down to 20% and suddenly 4% then shuts off...
Perhaps do you guys think that to keep our kaiser's stanbby time longer rather buy an external battery charger and make sure that battery is charged up fully.so that we can utilize the battery fully.
Click to expand...
Click to collapse
try to put these lines in sysinit.rc:
#battery patch
chmod 777 /sys/module/board_kaiser_battery/parameters/battery_capacity
write /sys/module/board_kaiser_battery/parameters/battery_capacity 1400
I'v changed it to 1350. It was charged properly and drop to 4% from ~10%, so nearly ok. But when connected charger it's full in about 10 minutes????
Edit: After dischargine (5 minutes), it charges probably normally.
working...
tiagoclc said:
try to put these lines in sysinit.rc:
#battery patch
chmod 777 /sys/module/board_kaiser_battery/parameters/battery_capacity
write /sys/module/board_kaiser_battery/parameters/battery_capacity 1400
Click to expand...
Click to collapse
Thanks! i think it worked now!my battery now runs down normally...
How long everybody using your Kaiser battery? I can use 3 days in Winmo but it could not exceed 1,5 day in Android (NAND) :-(
I have the same as you.
But i stopped using Android on ma phone. I'am out with Winmo, don't want to use it anymore. And android dies just quickly.
Am using now en Nec N343i
Will try android again when new updates or new kernel arrives
yo ppl...now most of the time i can figure this type of stuff out....but this time im kinda lost....i edited the sysinit.rc file....also the battery_capacity file.....im running poly 2.1g on NAND but after i reboot the phone....does nothing.....any tips or site with a little more info...?? thanks in advanced for any help
Battery problems on polymod 2.1 gamma
tiagoclc said:
try to put these lines in sysinit.rc:
#battery patch
chmod 777 /sys/module/board_kaiser_battery/parameters/battery_capacity
write /sys/module/board_kaiser_battery/parameters/battery_capacity 1400
Click to expand...
Click to collapse
Hi,
I have polymod 2.1 gamma with all updates (UPDATE 15 Mar 2010, UPDATE 18 Mar 2010, UPDATE 23 Mar 2010) and the kernel from "ponack.net/poly/BT_Update/" installed on NAND (Tytn II). It runs really smooth, but I have a problem with my battery.
I have written the battery patch from tiagoclc in the sysinit.rc before I installed on Nand (but with value 1350 from my battery). But is this enough or do I have to delete a *.bin file from battery? I hope someone can help me with a description.
I have seen a fix for "Myn's Warm Donat" here:
forum.xda-developers.com/showpost.php?p=6243182&postcount=306
Is there also a fix for Eclair 2.1 available? Or does someone have a "complete" description for this battery problem? My Batterie is a few hours on 100% with this battery patch and I can not charge it. But this could not be true.
I hope someone can help me.
MT
Maybe kernel problem.
I'm experiencing the same problem as everyone.
Lately my battery suddenly drops from 100% to 4%.
When I put to charge, it reaches 100% very fast. Should reach only 5%
I think it can be a problem in the kernel.
Now, i'm trying to solve it. If I find something I'll share with you
I can not determine which kernel brought the problem...
23/04 - 16:16 (GMT-3 - Rio de Janeiro) - Trying an old kernel
23/04 - 17:00 - Nothing. But came to the conclusion that the problem is with the battery.
Battery really "thinks" its 100% charged, since it accepts flash a nbh without the need of the phone is charging. And this only happens when the battery is at least 50% charged...
(sorry about my english. I'm brazilian and still learning english)
Some threads and posts about battery:
http://forum.xda-developers.com/showthread.php?t=661588
http://forum.xda-developers.com/showthread.php?t=644453
http://forum.xda-developers.com/showpost.php?p=5599516&postcount=33
We must concentrate everything in one thread!!!
We have to use search
I have set 1350 in sysinit.rc and it seems to be ok, but before every charge I have to reboot to charge it fully. then it discharges nearly fine - there are some fluctuations beetween 2-3-4 percent.
For me, with Overclock.. it's EXCELLENT! I can have it in standby but still have background data going (push gmail, twitter apps, etc.) for days at a time and still have some juice left.
Just today with some admittedly light usage (but I did use it) I had battery use time of 12Hrs with over 70% left.
I'm using setvsel @
35 @ 400MHz
50 @ 800MHz
65 @ 1200MHz
CPU Icon is set to refresh every second and it's supposed to cap at Vsel 2 @ 10%. It's as stable as ever.. been running like this for weeks now. I'm taking note of how much I appreciate the excellent battery life I get because my Vibrant has been getting really bad lately.
Running Barebones 1.3 with
19 @ 300Mhz
35 @ 600MHz
52 @ 1000Mhz
Battery Life is excellent - more than 48h without recharging is no problem.
I get 2 days of standby with heavy texting,surfing over wifi,calling and some gaming. DEFY battery performance is one the best amongst all Android phones.
el*Loco said:
Running Barebones 1.3 with
19 @ 300Mhz
35 @ 600MHz
52 @ 1000Mhz
Battery Life is excellent - more than 48h without recharging is no problem.
Click to expand...
Click to collapse
Undervolting your cpu can harm your hardware real badly. I've had my defy stopped working and shut down completely in the past so i won't recommend you OC or UV
EDIT: tho i still undervolt but 19 vsel is too low for 300 mhz, raise it upto 26 or so
Yes, 19 vsel maybe too low, at least in my case. When I ran the stability test, anything less than 24 would hang the phone after some 10 minutes. 24 is fine in my case but I set it at 26 to give a little more juice.
LOL. Why the hell, should undervolting harm the cpu? Undervolting improves your cpu's lifetime, instead! Less voltage means less stress (heat) and less leak currents for the cpu.
Well, it's true that you might have some instability issues, when the voltage is too low. As soon as you experience so, you can raise the voltage a little, until you have a stable cpu. I've been using undervolting for my PC's CPUs for several years.
PS: I'm on [email protected], [email protected], [email protected]
Never had any problems with my settings, some in this forum use even lower voltages.
mine is
[email protected]
[email protected]
[email protected]
I use wifi quite a lot. But still the battery backup is ok compared to my previous phones!
Running on Pays 5.0
[email protected]
[email protected]
[email protected]
I have to charge every two days.
running on pay 3.1
setvsel:
350/22
700/38
1100/56
48h no problem, record is 80h on moderate use
The battery life on the Defy is absolutely amazing.
I can easily get between 2 and 3 days of normal usage and somewhere in the region of 4-5 if I use it very little.
I reckon if I switched off 3G, had the brightness down as low as possible and generally tried not to use the phone much, I could push a week.
Sadly, my Defy is 'in the shop' just now, damned earpiece.
What do you guys run on the background? I probably able to get 1.5 days on normal usage. Even after charging and no usage, I lose about 10 % after an hour or so.
lanfearxt said:
What do you guys run on the background? I probably able to get 1.5 days on normal usage. Even after charging and no usage, I lose about 10 % after an hour or so.
Click to expand...
Click to collapse
It is impossible to get 1.5 day if defy uses 10% for 1 hour standby. Defy rounds 95% to 100%, and 94% to 90%. So it is possible that an apparent 10% drop is actually a 1% drop. You may install Motocharge to see the battery in 1% increment.
I'm happy to hear everyone getting excellent battery life. The DEFY is a truly unique Android phone.. I'm just afraid that us stateside won't get devices like this because of AT&T... the Bravo is a step below the DEFY just because it doesn't share the same faux-rugged water resistant build. I'm glad T-Mobile picked this one up, overclocked it's only a bit slower than my Vibrant in most operations.
Well I did a Quadrant benchmark 'standoff' with a colleague of mine which has a Samsung Galaxy S [EU version of the Vibrant] and I beat him with over 250 points [the Galaxy S did 975, my Defy did 1334], both running Froyo and the Defy being non-overclocked.
I've also noticed that his Galaxy S tends to hang & stutter from time to time. Regarding battery life, he carries his charger with him at all times, I do not, 'nuff said.
I also get ~1.5days of battery life.
I'm able to squeeze more than 80 hours of usage on a single charge running PaYs 5.0. Light to moderate use of WiFi/Data/GPS/BT, no background syncs and most apps firewalled except through WiFi.
SetVsel:
18/300
32/700
58/1100
ABC_Universal said:
It is impossible to get 1.5 day if defy uses 10% for 1 hour standby. Defy rounds 95% to 100%, and 94% to 90%. So it is possible that an apparent 10% drop is actually a 1% drop. You may install Motocharge to see the battery in 1% increment.
Click to expand...
Click to collapse
i used circle battery widget and it does shows 1% increments. after 90%, it slows down in terms of usage.
i also forgot to mention that my defy sometime runs pretty hot at 35-38C, which i think accelerates the discharge
what about autobrightness? if is set it on, the battery drains much faster.
For me, with undervolt (800/46;600/30;300/18) I can use my phone to make calls, send sms, surf the web, run some apps, and run one a two games.
After 24h of that usage, I have 50% remaining.
a strange thing happened to me (sorry for my English):
Yesterday I installed the camera 360 that did not work it gave some error. Last night when I went to sleep (1-1.30) had 50% battery, in the morning (7.30-8) phone was dead. I put the phone to recharge, from 11 to 3 o'clock phone has reached 30% of battery so i put the phone to recharge again. Until 10 pm the phone has reached again 30% of battery so I decided to give him a factory reset. With 30% i did 100+ app backups with titanium pro and I gave factory reset, after the phone restore from factory reset surprise the battery show 60% ??? I did restore 100+ app and battery show 50%, I played about a half hour and still 50% battery??? what the hell happened??? 360 camera app has to do with rapid battery discharge???
- I use advance Task Manager droidwall, light <10%, original rom only rooted
- anyway Battery discharge I think is caused by the signal GSM of my operator's.
- anyway in the night i decided to kill the traffic and by that the battery shouldn't discharged hardly over night. right?
(Q) sometimes the touch screen it freezes in games so I have to put the phone in standby and come out of standby, and then the touch screen works again ... this happens to you to?
Greetings gents,hows it going?
I got a question,i managed to overclock my phone to stable [email protected]
But now im trying to push it to [email protected],and its working properly atm,30mins of Stability test and running good.
My only concern is...im watching the temperature and its at 43ºC atm..which isnt exactly "cold" .
My question is,which are the max secure temperatures this beast can go before getting in the risk of frying the CPU?
Thanks in advance ^
PS : I tried searching around but all i found is VSel's...im interested in temps rather than VSel's.
Respect
Is that your battery temp or the CPU temp?
If it's battery temp, I'd be starting to be concerned there. CPU's can handle way higher temps though, 80+C before I'd get worried at all.
But try it out in the sun, too.
dasbin said:
Is that your battery temp or the CPU temp?
If it's battery temp, I'd be starting to be concerned there. CPU's can handle way higher temps though, 80+C before I'd get worried at all.
But try it out in the sun, too.
Click to expand...
Click to collapse
Hmm tbh im not sure which temp it is,StabilityTest says "Temperature"p,now i got no idea tbh which of them it is XD
Time to try again
EDIT : Yep,those 43 - 44ºC are Battery Temps,so should i worry?o.o
80ºC, that's for laptops and desktops, even i start getting warnings in syslog at 85ºC in my core i5 laptop with fan running max speed, and we are talking about a phone processor encased with other chips in a very little space and with no heat dissipation at all... you could not hold it up at 80º though burning and melting on your hands.
There's a lot of info about batteries here http://en.wikipedia.org/wiki/Lithium_ion_battery
I dont think defy is able to drain enough energy to increase battery temperature to dangerous levels, but with temperatures above 40º chemistry inside battery is going to suffer,the higher the temps the less cycles of charge you are gonna get and you are risking a permanent loss of capacity.
The best way for a long life battery is small charges from 25% to 80%
Multiple charges between 80%-100% is the worst thing one can do.
anyway reaching 43º for battery during stress test is not for concern
Battery Monitor Widget is a very good program to keep an eye, and see graphs and stats of battery temps consumption projections and estimations of of juice left.. its simply amazing runs 24/7 and if you dont open it to play with it, it only takes about 10 seconds of total cpu power per day. i would recommend it. So it wont eat your battery when monitoring it, and the same goes for "process monitor" which is perfect to know total cpu power eaten by all apps trhough the day.
unrafa said:
80ºC, that's for laptops and desktops, even i start getting warnings in syslog at 85ºC in my core i5 laptop with fan running max speed, and we are talking about a phone processor encased with other chips in a very little space and with no heat dissipation at all... you could not hold it up at 80º though burning and melting on your hands.
There's a lot of info about batteries here http://en.wikipedia.org/wiki/Lithium_ion_battery
I dont think defy is able to drain enough energy to increase battery temperature to dangerous levels, but with temperatures above 40º chemistry inside battery is going to suffer,the higher the temps the less cycles of charge you are gonna get and you are risking a permanent loss of capacity.
The best way for a long life battery is small charges from 25% to 80%
Multiple charges between 80%-100% is the worst thing one can do.
anyway reaching 43º for battery during stress test is not for concern
Battery Monitor Widget is a very good program to keep an eye, and see graphs and stats of battery temps consumption projections and estimations of of juice left.. its simply amazing runs 24/7 and if you dont open it to play with it, it only takes about 10 seconds of total cpu power per day. i would recommend it. So it wont eat your battery when monitoring it, and the same goes for "process monitor" which is perfect to know total cpu power eaten by all apps trhough the day.
Click to expand...
Click to collapse
Oh Right,
Yeh its true that the best would be from totally discharged to totally charged for its life.
And good to know 43ºC isnt panic-able yet cause the phone runs very well on 1.3GHz/65 and a score of 2700 of Quadrant (Impressive aint it).
Anyways,thanks for all the info =)
Respect
Running 1400MHz/87vsel i have reached 48C in a few minutes. Oc over 1200MHz is not good for battery.
Hi
It seems that the stock Battery as a very low max temp limit before stopping charge.
I've made some test and it becomes pretty clear that at 45°C, the battery stop charging.
The problem is that when you're using the Defy for Car navigation this 45°C can be reach very easily.. so instead of maintain the charge, the Defy start to discharge quickly! But at this time the phone still indicate "charging in progress"
BTW, I'm looking after the Mugen 1700mAh battery:
http://www.mugen-power-batteries.com/review/product/list/id/681/category/413/
So I would like to know if someone can say or test the max temp of this battery. In general Li-io can reach up to 50°C, the 45°C seems a little bit low here. Maybe the Mugen Battery can do better than stock one ?
Thanks
have you tried undervolting your device? (less voltage = lower temperature) the defy is way overvolted and underclocked by default. the max vsel/frequency is 58vsel/800MHz, and i could run it stable with 42vsel...
I've allready undervolt my Defy. It run at 1000/48 at this time.
But the CPU Vsel is not the only source: GPS+3G+Screen on = battery drain = heat
I have my Defy placed in front of the AC blower as work around
Rule 1: If you haven't taken these steps, you haven't done a thing in the way of actually optimizing your battery life, and please do not complain that your battery is bad if you haven't at least done steps 1 and 2!
Step 1: Use BetterBatteryStats: http://forum.xda-developers.com/showthread.php?t=1179809
This will diagnose battery drain issues. If you have apps that are sucking battery in the background, this will show it. Google the ones that have high partial wakelock, and usually you will get a diagnosis. It is also sometimes very easy to figure out what is sucking battery just by looking at the application that is holding wakelocks or having many alarm wakeups.
Step 2: Sync settings, make sure that all of them are either at push or as high as you're personally willing to allow between sync checkups. Any sync settings that happen too often will trash battery life.
Step 3: Radio based drain is a very big part of battery life! As such, if you do not need constant sync, you can turn off mobile data on your own when you do not need it, or go to the Mobile Network settings and disable always on mobile data. This can greatly increase battery life, but at the expense of sync not working when mobile data is off.
Step 4: Display brightness can greatly affect the power drain of the battery! You can either manually control the brightness, download Lux autobrightness to make your own autobrightness settings, or flash a custom autobrightness setting in the ROM in order to achieve this. It also can have the side effect of making the display of the right brightness when in the sun and in the dark, so it is always at ideal brightness to preserve battery.
Step 5: Make sure that the battery is calibrated. This is not very complicated. Download currentwidget from the market, put it on a homescreen. Charge the device until currentwidget indicates 0 mA charge. Use the phone until the phone shuts off. You might want to then go to hboot and drain the battery until it shuts off again, and then do a full charge again. Only do this once every 2-3 months, because this is bad for the battery.
Step 6: Adblocking! One big cause of battery drain and unnecessary network usage is downloading ads. If rooted, use Adaway and Adblock to block ads from ever being downloaded, and use Adaway's adware feature to detect and remove apps with adware!
Step 7: A radical step is to use Core Control or something similar to either underclock, undervolt, or just shut off cores. Undervolting is always highly suggested, as it will help reduce heat and give the phone a longer lifetime, but underclocking and shutting off cores will reduce performance!
Step 8: Custom ROMs and kernel experimentation might yield just a bit more in the way of battery life, and also give much more customization and features.
After this, you have likely topped out all that can be reasonably done to extend battery life. If you find that your battery drain is still poor, perhaps you have a defective battery, or maybe even a defective device (Highly unlikely, but who knows...). It is also possible that you simply have a use case that is much more than the phone can accomplish, in which case you can either use a battery case, or an external battery to charge the phone on the go.
Hunt3r.j2 said:
Step 5: Make sure that the battery is calibrated. This is not very complicated. Download currentwidget from the market, put it on a homescreen. Charge the device until currentwidget indicates 0 mA charge. Use the phone until the phone shuts off. You might want to then go to hboot and drain the battery until it shuts off again, and then do a full charge again. Only do this once every 2-3 months, because this is bad for the battery..
Click to expand...
Click to collapse
Weird, I've tried this many times, and can't get the indicator show exactly 0 mA...
the lowest for me around 3-5 mA... :|
what do you mean by undervolt because i dont understand..what are the consequences ?
nemer12 said:
what do you mean by undervolt because i dont understand..what are the consequences ?
Click to expand...
Click to collapse
if too much undervolting the phone freezes/ reboot ....so the best value for undervolting is between 50 and 100mv ....in some cases undervolting increases battery life and makes the phone cooler but not much ...
Under volting is when you tell the battery to provide a little less power than usual.
Which is why the battery life usually increases, as less battery is being used than previously.
But as stated, too much can cause the battery to not provide ENOUGH power, therefor crashes and cannot boot properly etc.
One-X-master said:
if too much undervolting the phone freezes/ reboot ....so the best value for undervolting is between 50 and 100mv ....in some cases undervolting increases battery life and makes the phone cooler but not much ...
Click to expand...
Click to collapse
Pretty much, I would say. Drastic increase of battery in games: phone won't get hot => battery will last longer without overheating and, what is much more important, it will stay healthier in long run.
Even on wall charger while playing, my HOX won't overheat with - 100mv UV.
This is the main feature I miss on JB Sense without custom kernels
Sent from my HTC One X using xda app-developers app
THANK YOU
MysteryE said:
Weird, I've tried this many times, and can't get the indicator show exactly 0 mA...
the lowest for me around 3-5 mA... :|
Click to expand...
Click to collapse
Same here. On both my old HTC Sensation, and my HOX. Never saw the mA reach 0. Even after leaving on the charger for a couple of days.
DarkManHaze said:
Same here. On both my old HTC Sensation, and my HOX. Never saw the mA reach 0. Even after leaving on the charger for a couple of days.
Click to expand...
Click to collapse
The problem is, the phone cannot get the same amount of energy, it consume (in fact, it is the millisecond, where the phone is fully charged, than it discharges for some minutes, than it will be charged again for three minutes and so on periodically). So, what I mean, you will almost never see 0 ma on one X or other modern phones. You can only see that, if device can disable battery while it is fully charge and use wall charger like a main supply. And the last device with such behavior was Huawei s7 back to 2010
So, 3-5ma is pretty ok.
Sent from my HTC One X using xda app-developers app