Related
hi there!
as mentionend by users in other threads, it seems that a high number of raphs have a draining battery issue - compareable to the bug in our kaisers about a year ago: batterystatus measures around 70/80 mA in sleepmode with all programs and tf3d closed - on a kaiser with custom rom was around 4mA (!!).
So please, dear chefs: Try to figure out how we can fix this one
Check out some kind of solution / a way to improve your battery uptime: http://forum.xda-developers.com/showpost.php?p=2770702&postcount=25
Update: Battery was sucked empty from 90% within 3-4 hours in the night (!!). No running programs. In the chart you can see the difference between loading with the 220V plug and the USB-cable (last part of the chart). Sometimes it looks as the device sucks more power than the usb loader can deliver -> battery will get empty even when plugged into the computer the whole day.
Looks as we really need a solution thus waiting for htc or cellproviders is useless :-(
licht77 said:
Update: Battery was sucked empty from 90% within 3-4 hours in the night (!!). No running programs. In the chart you can see the difference between loading with the 220V plug and the USB-cable (last part of the chart). Sometimes it looks as the device sucks more power than the usb loader can deliver -> battery will get empty even when plugged into the computer the whole day.
Looks as we really need a solution thus waiting for htc or cellproviders is useless :-(
Click to expand...
Click to collapse
Can you check this? Start->Settings->System->Power. Make sure that the "When device is turned on, do not charge the battery when connected to the PC" is unchecked.
programatix said:
Can you check this? Start->Settings->System->Power. Make sure that the "When device is turned on, do not charge the battery when connected to the PC" is unchecked.
Click to expand...
Click to collapse
Of course it is unchecked - but thanks for the hint!
I still need to get over the shock that it took just 3-4h to ground the battery in standby without running programs oO
for me it helped a lot to improve battery life to set the setting 18.4 (energy saving) in diamond tweak...
pensador said:
for me it helped a lot to improve battery life to set the setting 18.4 (energy saving) in diamond tweak...
Click to expand...
Click to collapse
I need to compare the tweaks but i enabled energysaving options with Advanced Config... - but I will give diamond tweak a try and even do a hardreset in order exclude 3rd party software for the power consumption...
ill report soon!
im having battery issues, too.
sometimes the phone gets unresponsive, really hot and battery drops 30-40% in ~1h minutes - without being used.
i love my touch pro, but ive got so many problems (crashes, hang ups, battery, broken screen thing, grey display with stripes, the list goes on and on...) that im considering to return it
So... small update of my findings:
My Raph(s):
R 1.02.25.19
G 52.23.25.1.7U
D 1.69.00.00
The power consumption usually never falls below 75mA. It goes up to usually 240mA, 700mA yes sometimes 1100mA. (Again: in standby!)
Comparison: on the kaiser it was around 4-12mA with Teijaks V5.
The following changes WONT affect this problem:
o disabling TF3D
o switching to GSM/GPRS only
o switching off persistent internet connection (e.g. exchange server) (!!!)
o kicking ALL not absolutely necessary backgroud processes step by step and measure between
Naively i thought that someone may be interested in that behaviour and called my provider t-mobile... ok, bad idea as they seem to have none knowledge about that devices at all.
But at least I got a number of their hardware-supporter / servicemen "Kapsch" who couldnt help me either but where kindly enough to pass me a number of HTC here in Europe.
The nice lady with basic knowledge about the devices as well as the language we were talking in came to the conclusion that the only solution would be to send the devices in via my provider.
Well, so they believe that exactly theese 3 raphaels here are the only ones to suffer from that power drain (hardresettet, blank installation, bla bla like above)... and sending them in (what means: dont see them again for a month or so and get them back in the same condition) would be THE solution.
Somehow i am pissed that i already sold the kaisers and wonder how it will be next week on a businesstravel with an unpowered TomTom outside the car and a phone which drains in a few hours in standby
(Sorry for whining around...)
Completely agree with some of your figures, however the highest i have ever seen is around 550mA. Usually after no data transfer i get it to drop to between 89 ~ 110mA. How are you measuring standby current? When in standby, how can the software measure the current? I only ask as like you, the lowest i have seen for current is 82mA, however this figure would give a max standbytime of around 16 hours. I have found that the TP in standby performs the same if not better then my old kaiser which, like you measured around 4mA in standby. From what i have seen, i can not measure a true standby current like i could on the kaiser.
I measured with CommMgrPro and batterystatus...
Measuring a "real" standby without changing the battery with an Ampere/Voltmeter is not easily possible i think... so i use CommMgrPro and accept its own usage as somekind of "Baseline".
Or - if you dont need a chart / history, i use the much smaller Batterystatus, disable TF3d to see the Homeplug and close all applications. With all apps closed i turn of the device, wait a minute or to be sure that it has gone sleeping, and wake it up. A few seconds after turning on the mW/mA measures will jump to the "standby" values due to its delay. Not 100% accurate but okay for comparison reasons...
Edit: Theese are my processes, the bold ones have been killed for testing purposes:
NK.EXE;0;0;\Windows\nk.exe;;2;FEFF002
filesys.exe;9760768;6286864;\Windows\filesys.exe;;14;FEEDCE6
device.exe;6602752;5714424;\Windows\device.exe;;218;FEB8F4A
cprog.exe;10567680;10227808;\Windows\cprog.exe;-n;12;2D93537A
SAPSettings.exe;114688;2944;\Windows\SAPSettings.exe;99;5;E9C7742
gwes.exe;4698112;4214840;\Windows\gwes.exe;30;35;E9B4566
shell32.exe;1724416;886584;\Windows\shell32.exe;50;21;CE70CBAA
services.exe;3035136;2127440;\Windows\services.exe;60;74;AEDD3EF2
connmgr.exe;409600;99152;\Windows\connmgr.exe;70;17;D8D06E6
Biotouch.exe;1024000;636792;\Windows\Biotouch.exe;;9;EF86C7DE
SDDaemon.exe;176128;28544;\Windows\SDDaemon.exe;;2;6DA68DBE
tmail.exe;352256;46256;\Windows\tmail.exe;-NoUI;6;ED2CCD36
OperaPreL.exe;24576;32;\Windows\OperaPreL.exe;;2;EC986A3E
Opera9.exe;159744;4256;\Windows\Opera9.exe;;1;C4FA06E
JBlendDaemon.exe;188416;65744;\Windows\JBlendDaemon.exe;;3;C595512
SIPGT_app.exe;1863680;1688032;\Windows\SIPGT_app.exe;;2;AC57D24E
My5MsgCenter.exe;180224;22016;\Windows\My5MsgCenter.exe;;5;C2CD412
myFavesService.exe;299008;132608;\Windows\myFavesService.exe;;2;AD8D0806
licht77 said:
I measured with CommMgrPro and batterystatus...
Measuring a "real" standby without changing the battery with an Ampere/Voltmeter is not easily possible i think... so i use CommMgrPro and accept its own usage as somekind of "Baseline".
Or - if you dont need a chart / history, i use the much smaller Batterystatus, disable TF3d to see the Homeplug and close all applications. With all apps closed i turn of the device, wait a minute or to be sure that it has gone sleeping, and wake it up. A few seconds after turning on the mW/mA measures will jump to the "standby" values due to its delay. Not 100% accurate but okay for comparison reasons...
Click to expand...
Click to collapse
OK, this i could do on the kaiser, but not on the touch pro. Each time i turn the phone on, i see at least 82mA, which would only give a stnadby of 16 hours - but i can achieve 3 days, so clearly this is not the standby current.
3 days.. i can only dream of that That would mean that you got around 19mA drain in standby... how do u measure?
licht77 said:
3 days.. i can only dream of that That would mean that you got around 19mA drain in standby... how do u measure?
Click to expand...
Click to collapse
Thats what i'm trying to say - i cant measure anything below 80mA when i turn the TP on, however it is obviously NOT the standby current as i can obtain 50mA with a dim backlight, plus get 3 days standby. When i state 3 days, thats with no usage!
I'm just trying to point out that what you think is the standby current, probably isn't and we all know that there are issues with the battery management on this phone.
Another example, i have had my phone of charge since 7am, made a couple of short calls, 5 mins of wap browsing, and its currently reporting 95%. If my standby current was 80mA, it would be down to 50% by now. However, assuming i continue to use the phone in this way, in theory i should get 160 hours, which indicates an average drain of 8mA.
I agree - of course you are right and measuring this way can - if anyhow - assist in relatively comparing two devices/ configs but not deliver absolut values of course.
With batterystatus it worked pretty well on the kaiser - and even on the raph i could see 3 or 4 times my beloved 4mA... but in 99% its around 80aH ind standby and around 300-400 in usage which seems plausible regarding my usage.
Nevertheless i had several times a "hardcore" drain where i must had (mathematically) around 400 during standby and maybe even more during worktime when plugged in via USB: It DISCHARGED what means that it used more power than USB could deliver
(usb charging settings correct)
If I dont get my callback from my provider today, then i will try an inofficial RadioRom this weekend...
In standby mode, all application should have been paused by the deviced, right? Then how can any application measure the power usage in standby mode?
some apps keep going. thats how you get messages
i can get 2days out of my phone with heavy usage
Brendo said:
some apps keep going. thats how you get messages
i can get 2days out of my phone with heavy usage
Click to expand...
Click to collapse
That is because the OS send out events when something happens, thus waking up the device and letting the apps run.
For SMS, sim card receive message, sim card inform OS, OS wakes device up, OS send out events, app capture the events.
For alarms, OS wakes device up when the schedule reached, then send out events or start apps depending on the alarm.
So, device must wakes up before apps can do anything.
Some apps intercept the standby button (power button) and instead of letting the device goes to standby when pressed, just turns off the display. For TP, HTC has modified something (or loaded some apps) to make sure that when you are playing the music or listening to the radio, the power button just turn off the display instead of going to standby mode. If the device goes to standby mode, the device could never play any music.
So, if the battery benchmarking app you are using is able to measure the power consumption when the device goes to standby, I doubt it. It actually just turn off the display.
I seem to have fixed or at least drastically improved my battery. I was suffering major drainage with moderate to heavy use, after about 5 hours the power would go down from 100% to 10%. I have WiFi on permanently and do a lot of emailing and texting.
I drained the battery to 0% and with the phone off (not in standby) I charged it using the AC adaptor. With it fully charged and the button light on (glows when charging, solid on when charged) I turned the phone on and first time it said 88% charged?!?! But it lasted the whole day and even had a good 30+% left at the end.
Did it again, ran loads of apps and switched everything on until 0% battery. Charged over night with the phone off. Next day it said it had 95% charge when I switched it on and again it lasted all day with quite heavy usage.
Discharged it again that night and plugged it in, today it says 100% and I'm pretty sure it will last even longer.
I've also found that after doing this, if I don't use the phone and the screen is off, I can leave it for 4 hours and the battery percentage doesn't even go down 1%.... which is a bit unbelievable but happens.
PLeased to say, now this last gripe seems to be fixed..... this is by far the best smartphone I've owned or used and on the market. Great step up from the TYTN II and iPhone (nice toy but useless for email and destructive with exchange servers).
Gav_ said:
I drained the battery to 0% and with the phone off (not in standby) I charged it using the AC adaptor. With it fully charged and the button light on (glows when charging, solid on when charged) I turned the phone on and first time it said 88% charged?!?! But it lasted the whole day and even had a good 30+% left at the end.
Did it again, ran loads of apps and switched everything on until 0% battery. Charged over night with the phone off. Next day it said it had 95% charge when I switched it on and again it lasted all day with quite heavy usage.
Discharged it again that night and plugged it in, today it says 100% and I'm pretty sure it will last even longer.
Click to expand...
Click to collapse
True. Draining the battery completely really helps. I've done it about 3 times and now my device can reach 2 days of heavy use with 1 charge. When I bought it drained very fast and charge indications were way of. (1 hour charges would just increase charge level with 5-10%).
What also adds battery life ia disabling activesync in the notification queue. Use memmaid or a similar program. Go to the notification queue and disable the entry for repplog.exe with the comment "system time changed". Activesync will function normally when connected to a PC. Not sure about OTA exchange syncs though...
Hope this helped
Scott
Hi,
I've found that the Raphael battery stops charging when it gets warmer than 48 degrees Celsius. I discovered this because I am using WMWifiRouter all day at the office, and noticed that although I have the Raph connected to a 2000mA wall charger, the battery drained and device got down to 10%.
The trick is that I have to put the device in "standby" mode py pressing the power button. The screen goes off, but the device is still running. This resulted in a lower device / battery temperature, and the battery remained at 100% after 8 hours of usage with WMWifiRouter and connected to the wall charger.
I can contrast this to with my Kaiser, which didn't stop chraging the battery until about 65 degrees Celsius!!
Maybe that helps too.
-Z
Maybe this depends on the batterys but mine was having that problem of going dead at higher and higher % it started at 10 than 30 then 50 and up to 70 I think.
I've tested all the solutions in the wiki (yes the freezer too ) but with no improvements, then I did the opposite, instead of draining the battery fast I drained the battery slowly and when the Universal shuted off I pluged it to the electricity until it boots ok and the cpu returned to 0/1%, then take it from electric power again and wait until it goes dead again and did this over and over again until I reached the minimum battery of 9% i think. Great improvement since I was already looking for battery replacements... Then I charged it over night.
Conclusion I have the Universal alive for 3 consecutive days (and nights) now at 52% waiting to check when it dies again
By draining the battery slowly I mean no light in the screen, no running programs and universal in closed state, flight mode and just one thing to check if it was alive or not, play some music in WMP in repeat mode, when it stoped playing it was time to have a litte more eletric juice until I could boot it up and start the music playing again.
When I have the final results -> when the universal goes down I will post the solution in the wiki
Again this may depend on the batterys but since there are so many people buying new ones you maybe want to try this solution too.
Oh and by the way I solved an "other" problem while trying to solve this...
Besides the tests on the battery like freezing it over night, taking the power level pin etc, I've started to think it was a problem from the rom so I cleaned the Universal doing that "task 28" thing and the result was solving the problem that I was having with the battery status (now home screen plus plus) it was not getting the cpu using percentage when in the past it did. Now with the cleaning reg whatever It is showing again the cpu using %
I don't know if you use this but it has a cool functionality, posting the cpu using % at the top bar of your universal can tell you how much the universal is working all the time, enabling you to notice when it is working when it shouldn't, normally some stupid background program that didn't go off...
hi there. I have two same unis, and three batteries. two standard, one big capacity 3200mAh (personally I dont believe it have such capacity, it is some china crap). but all three had that issue (uni shut down when capacity still showing more as 30% or more %). tried to deplete the battery completely (when it wont boot, I put device to bootloader mode and wait untill died completelly). now it show again 0% on all three batteries. I dont want to say, that your method is bad . no, I am just a lucky one, where the "wiki" methods worked correctly. and I think it is also important sometime charge the battery completelly, not only for couple of minutes, but until you see green light. when you deplete the battery completelly to zero (it is never zero, electronics integrated on the batter doesnt allow that) charging to full take much more time as before.
powerdetect
one more thing, you can test, how much capacity your battery have. it is simple utility called power detect. you can find it in THIS thread or as attached file. just copy to device and run. the test will suspend itself after one hour, so set all settings as needed. it will automatically create file, where you can find all important information. before you use it first time, charge your battery to full.
Thank you for the reply, My battery still dies at 30% but no more at 70% and 50% and it lasts 3 days/nights in a row.
I tried the boot loader mode but it seemed it had a timeout, instead of dying from battery losse it died from some kind of time out :/ because I was still capable of juicing some more battery if i went again to boot loader...
I will check that app, thnks again
wat i did..
well my battery used to shut off at 95 above present...wat i did was drain the battery with a 12 volt motor, took me a complete day for it to discharge, then i put it in the freezer, was suppose to put it for one night but i actually forgot bout me putting the battery in the freezer n i remembered after 2 days. then i charged it which also took around 18 hours to charge now my batter shouts itself at 70% n i can listen to music for 1.5 hours. which is a lot from a battery which was shutting at 95%
I have had quite bad battery drain issues for a while, and searched BBS dump files and forums for an answer, but the logs appear normal with no unusual wakelocks. In short, the battery consumption profile is OK but it just goes too fast. So I concluded I needed a new battery and was too cheap to buy Samsung original battery and instead got a noname type (same capacity, 1500 mAh).
But it didn't help. Still 12-16 hr standby with low use (<1 hr screen time at lowest brightness).
So I tested the health of the two batteries by draining them as fast as possible. I used the app "Battery Drain" (https://play.google.com/store/apps/details?id=com.fuzzyoneapps.BatteryDrain) and drained using full screen brigtness, wifi, bluetooth, gps, CPU but NOT the vibrate function.
The results are attached to this post. As observed, there's no big difference between the two batteries. And I don't know what to expect.
So now I'd like someone else to do the same test so that we can compare the results
Basically, just 1) Run the app with all the settings turned on except vibrate, 2) make note of battery percentage, 3) leave it for exactly one hour, and 4) check percentage again. Is ~45% per hour normal for the nexus s?
Thanks in advance
I mistakenly posted this in the wrong forum at first, so here it goes again:
I bought this Galaxy Tab 2 10.1 (GT-5110) about a year ago, it runs the original firmware with the recent Samsung update to 4.2.2.
Lately the battery life has become very short. This was not a gradual change, but something that seemingly happened over night. I charge the device with a travel adapter that claims to output up to 1 A. The battery monitor shows that charging works as expected and the device charges to 100 % .
In use the battery shows 100 % for a while, but after about 20 to 30 mins jumps to 4 % , giving me the low batter warning. I am travelling and the only change I can think of is, that mains power here in Canada is 110 V instead of the 220 V back home in Europe, not that I expect that to be a problem.
I don't notice the device getting warmer than usual, so I don't believe, that the battery really charges to 100 %. Is there anything on the software side I can do to investigate this further?
Thanks for any advice!
EDIT: I just noticed, it's actually not the battery, that is dying. It is a error in the measurement. The battery life is normal, however the charge measurement shows nonsensical behavior: It goes to below 10 % in less than half an hour and then goes back to full, repeating this in cycles, like a sawtooth wave. So I suspect either a hardware fault in the measurement circuit or a software problem.
Here's a screenshot of what the battery info looks like, mind you the device has not been on the charger the entire time:
imgur.com/i2HUQjN
krashik said:
I mistakenly posted this in the wrong forum at first, so here it goes again:
I bought this Galaxy Tab 2 10.1 (GT-5110) about a year ago, it runs the original firmware with the recent Samsung update to 4.2.2.
Lately the battery life has become very short. This was not a gradual change, but something that seemingly happened over night. I charge the device with a travel adapter that claims to output up to 1 A. The battery monitor shows that charging works as expected and the device charges to 100 % .
In use the battery shows 100 % for a while, but after about 20 to 30 mins jumps to 4 % , giving me the low batter warning. I am travelling and the only change I can think of is, that mains power here in Canada is 110 V instead of the 220 V back home in Europe, not that I expect that to be a problem.
I don't notice the device getting warmer than usual, so I don't believe, that the battery really charges to 100 %. Is there anything on the software side I can do to investigate this further?
Thanks for any advice!
Click to expand...
Click to collapse
i think the problem is with the charger
drain the battery of your tab completely and then charge it fully upto 100 % with stock original charger and see if you notice any difference
aditya rathee said:
i think the problem is with the charger
drain the battery of your tab completely and then charge it fully upto 100 % with stock original charger and see if you notice any difference
Click to expand...
Click to collapse
What makes you say that? I've been using that charger instead of the Samsung charger at home for a long while now.
For me it may be the hardware issue, because software doesn't consume battery in the background so rapidly.
#If you are not sure try this options
For Hardware issues:
*Make sure your charger is working properly (Completely drain your battery and then connect your charger and charge for few half n hour and then reboot your phone and check your battery status and use your tab normally for few minutes and keep an eye on the battery consumptions)
If your battery is gradually decreasing no fault to your charger.
If your charger doesn't charge then its the time to either change or repair your charger.
For Software issues:
"GO TO BATTERY SECTION IN SETTINGS AND CHECK WHICH APPLICATION REDUCES YOUR BATTERY OVERNIGHT RUNNING ITS SERVICES IN THE BACKGROUNG AND JUST DELETE IT"
*After using your tab normally go to SETTINGS>APLLICATION MANAGER> and then RUNNING SERVICES.
If you find unnecessary services running in background NY an app which is not required just uninstall those app.
*Try to check your Sync, WiFi, GPS etc. settings to ensure that any app is consuming continuous services and draining your battery.
*Remove recently installed app which are not necessary.
Hope they help.
Thanks so far, I just updated my original post to describe the problem more precisely.
a solution
krashik said:
I mistakenly posted this in the wrong forum at first, so here it goes again:
I bought this Galaxy Tab 2 10.1 (GT-5110) about a year ago, it runs the original firmware with the recent Samsung update to 4.2.2.
...
EDIT: I just noticed, it's actually not the battery, that is dying. It is a error in the measurement. The battery life is normal, however the charge measurement shows nonsensical behavior: It goes to below 10 % in less than half an hour and then goes back to full, repeating this in cycles, like a sawtooth wave. So I suspect either a hardware fault in the measurement circuit or a software problem.
Here's a screenshot of what the battery info looks like, mind you the device has not been on the charger the entire time:
imgur.com/i2HUQjN
Click to expand...
Click to collapse
I had this exact problem, down to the sawtooth battery status profile, tablet model and android version, and fixed it with the following procedure:
After a normal boot, press and hold the power button continuously.
The tablet will shutdown and reboot repeatedly.
Hold the button down for at least 4 complete shutdown/restart cycles, never releasing the button.
After that treatment the battery status shows a nice, normal discharge curve, starting from whatever random place the sawtooth pattern left you at. Run the tablet until it powers down by itself, and then recharge it.
The ugly sawtooth battery status first appeared on the tablet after running an intensely power-hungry application (the battery got hot after 20 or so minutes of running). After that, the discharge rate seemed to have a flipped sign, where if normal discharge rate per minute was positive, the altered, aberrant discharge rate was negative. CoPilot was the offending software; however, that may be a post hoc ergo propter hoc logic error on my part.
The messed-up discharge rate would prematurely terminate charging if the table was on, so the only way to get a full charge was to turn the tablet off and attach the charger.
Hello,
I followed the excellent guide linked below for help with calibration of a Samsung battery.
[GUIDE] Samsung Battery Calibration
Samsung Phone Battery Calibration Guide Description: This guide is for those who are experiencing battery issues (e.g., battery suddenly dying at percentages >1% or battery draining too fast or messed up battery readings after custom ROM...
forum.xda-developers.com
Unfortunately, it did not solve my problem. I was hoping someone here might be able to help.
My battery calibration issue is different to anything I've seen before. I had the usual battery problems and got a replacement battery fitted. My current problem is that the battery has more charge than the phone realises (which is the opposite of the usual problem one tends to see with a bad battery).
The battery level falls quickly from 100% down to 1% at a rate of about 10% per hour. But then it stays at 1% for AGES! Even if I leave a video running on YouTube on maximum brightness. A minimum of 30 minutes but possibly more. So there's plenty of milliamps in there, it's just that the phone doesn't realise this.
I tried following methods 1 and 3 from the guide linked to above but the problem is still there.
Any suggestions? Thanks in advance.
Thanks for your reply. I've tried this but unfortunately this hasn't fixed the issue. Any other suggestions?
Has the battery ever been replaced? This kind of behavior can happen with a failing battery.
FYI: If phone's battery health shows less than 80% then battery should get replaced.
xXx yYy said:
Has the battery ever been replaced? This kind of behavior can happen with a failing battery.
FYI: If phone's battery health shows less than 80% then battery should get replaced.
Click to expand...
Click to collapse
Yes the battery has been replaced recently. Within the last 6 months.
Where do I see the battery health from? It's a Galaxy S7.