I was trying *#0228# secret code and Phone INFO ★SAM★ app without success.
Here is the output of the dumpsys battery command:
Code:
Current Battery Service state:
AC powered: false
USB powered: true
Wireless powered: false
Max charging current: 0
Max charging voltage: 0
Charge counter: 7300000
status: 2
health: 2
present: true
level: 52
scale: 100
voltage: 3890
temperature: 232
technology: Li-ion
batteryMiscEvent: 0
batteryCurrentEvent: 0
mSecPlugTypeSummary: 2
LED Charging: true
LED Low Battery: true
current now: 293
charge counter: 7300000
Adaptive Fast Charging Settings: true
Super Fast Charging Settings: false
USE_FAKE_BATTERY: false
FEATURE_WIRELESS_FAST_CHARGER_CONTROL: false
mWasUsedWirelessFastChargerPreviously: false
mWirelessFastChargingSettingsEnable: true
LLB CAL:
LLB MAN:
FEATURE_HICCUP_CONTROL: true
FEATURE_SUPPORTED_DAILY_BOARD: true
SEC_FEATURE_USE_WIRELESS_POWER_SHARING: false
BatteryInfoBackUp
mSavedBatteryAsoc: -1
mSavedBatteryMaxTemp: 522
mSavedBatteryMaxCurrent: 2811
mSavedBatteryUsage: 4013
FEATURE_SAVE_BATTERY_CYCLE: true
SEC_FEATURE_PREVENT_SWELLING: true
Do you know what mSavedBatteryUsage is?
Related
Friends,
Is there any way to build a battery driver which calculate battery percentage according to battery voltage.
I my defy battery level indicates full when it reaches 4184 mv and shows 99% / 4130 mv after disconnecting the charger. Phone shutdown itself when it reaches around 3600 mv. So the voltage variation is 530mv.
If we give 4130 mv and above as 100% and every 5.3mv decrease in voltage will reduce 1% battery level.
Ex:- 4130mv = 100%, 4125mv= 99%, 4120mv = 98% ..........4000mv = 75%,............3600mv = 1%.
I am not a developer, so i am just presenting this idea in this forum. Don't know if it work or not.
But if it works i hope the battery drops will reduce.
Thanks for reading this topic and sorry for my bad English
Sent from my MB525 using Tapatalk 2
AW: Battery driver modification
pradeeppk said:
Friends,
Is there any way to build a battery driver which calculate battery percentage according to battery voltage.
I my defy battery level indicates full when it reaches 4184 mv and shows 99% / 4130 mv after disconnecting the charger. Phone shutdown itself when it reaches around 3600 mv. So the voltage variation is 530mv.
If we give 4130 mv and above as 100% and every 5.3mv decrease in voltage will reduce 1% battery level.
Ex:- 4130mv = 100%, 4125mv= 99%, 4120mv = 98% ..........4000mv = 75%,............3600mv = 1%.
I am not a developer, so i am just presenting this idea in this forum. Don't know if it work or not.
But if it works i hope the battery drops will reduce.
Thanks for reading this topic and sorry for my bad English
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
if u look in quarx github he had a custom battd demon which calculate with extra files a better result. but battery drops are a combination of damage battery and a bad sensor for the batterylevel in the defy... thanks moto... in the newest CM10 builds the demon is integrated.
I just flashed a CM nightly. When it rebooted, it powered off and now the notification light just blinks 5 times when I try to boot into ANYTHING.
EDIT: Sorry, I guess I just freaked out. The 5 blinks, from what I can tell, mean that the device doesn't have enough power to boot safely. It's a feature
happened same to me tonight
when battery is tooootally 0 , White led blinks if u try to turn on
and also it need something like 3-5 mins to be rebootable after u plugin
this is true the device does have a safety feature that blinks the white led 5 times. I had issues with the charger/USB port, thought it was the battery so i ordered a new one and it booted with no issues. I then begun testing the USB/Charger port to find that 2 of the connections were lifted slightly i heated them with a soldering iron and got them reconnected had to use a table magnifying glass to see what i was doing. then i put the original battery in after i had verified that the connector was all good. after the switch I find the device blinking 5 white times i left it charge for like 15 minutes and it booted right up.
Yeah mine died one night and the next morning it wouldn't turn on. I didn't have time to charge it before leaving for work so I threw it in my bag with a portable battery pack that I keep in there for emergencies. By the time I got on this bus (10-15 minutes later) it was charged enough to turn on.
I just bought a Nexus 7 (2013), its a present for someone. I wanted to test it first and had just this problem, 5 blinks and not powering on straight out of the box new.
I eventually got the battery symbol after following a guide to quickly hold power and vol down when connecting the charger, and its now powered up and charging. But my question is, would it be a good idea to get it replaced since the battery has been left at zero charge for some unknown time before getting it? Or once its charged up will it be 'good as new'?
Strange, I also had the same issues yesterday. Altho when it did finally come back on the battery stats showed that it dropped from about 40% to 0 and then there was a gap and then it jumped back up to 40% and started charging.
After a prolonged analysis using the charge, voltage, and temperature graphs provided by the BatteryHD app, I conclude that there is a design error in a significant number of the Nexus 7 (2013) units.
According to a Google engineer, the charging system contains a charging rate governor which is controlled by firmware. It was included in the design to enable them to diminish the charging rate as the battery nears being full. Apparently the charging system sets the charging rate randomly -- sometimes even discharging the unit while it is plugged into the charger. Once the charging rate is set, it stays set to the same rate for some time. I have failed in all efforts to find what program, app, or sequence of operations changes the charging rate. Sometimes it seems impossible to get it to charge faster (or at all), and sometimes if I just breathe on it (click ON/OFF (0/1) once to see the flashing battery symbol), it will change the rate.
JB_Tipton said:
After a prolonged analysis using the charge, voltage, and temperature graphs provided by the BatteryHD app, I conclude that there is a design error in a significant number of the Nexus 7 (2013) units.
According to a Google engineer, the charging system contains a charging rate governor which is controlled by firmware. It was included in the design to enable them to diminish the charging rate as the battery nears being full. Apparently the charging system sets the charging rate randomly -- sometimes even discharging the unit while it is plugged into the charger. Once the charging rate is set, it stays set to the same rate for some time. I have failed in all efforts to find what program, app, or sequence of operations changes the charging rate. Sometimes it seems impossible to get it to charge faster (or at all), and sometimes if I just breathe on it (click ON/OFF (0/1) once to see the flashing battery symbol), it will change the rate.
Click to expand...
Click to collapse
These are interesting observations but if you are responding specifically to the "5 blinks..." topic then your battery is old, unreliable, near-dead, and the charging rate conclusions are unfounded because your battery has limited capacity . Furthermore, charging rate measured on a running OS is heavily depended on app/OS activities. It is much better to boot TWRP3 and observe charge/discharge current directly from bq27541 Battery Fuel Gauge, eg:
Code:
[3.135253] bq27541_get_psp status: Not charging ret= 0x0201
[3.140960] bq27541_get_psp voltage_now= 4106000 uV
[3.145843] bq27541_get_capacity = 100% ret= 100
[3.150390] bq27541_get_psp temperature= 220 (0.1˘XC)
[3.155548] bq27541_get_psp current_now = -462 mA
[3.160186] bq27541_get_psp charge_now (compensated) = 3155000 uAh
[3.166473] bq27541_get_psp charge_avg (uncompensated) = 3438000 uAh
[3.172790] bq27541_get_psp charge_full = 3155000 uAh
[3.177886] bq27541_get_psp charge_design = 4030000 uAh
[3.183074] bq27541_get_psp energy_now = 11142000 uWh
[3.188171] bq27541_get_psp charge_counter = -5000 uWh
[3.193267] bq27541_get_psp power_now = -1897000 uW
[3.198181] bq27541_get_psp cycle count = 89
[198.729858] bq27541_get_psp status: Not charging ret= 0x0201
[198.735565] bq27541_get_psp voltage_now= 4138000 uV
[198.740325] bq27541_get_capacity = 100% ret= 100
[198.745025] bq27541_get_psp temperature= 232 (0.1˘XC)
[198.749999] bq27541_get_psp current_now = -186 mA
[198.754699] bq27541_get_psp charge_now (compensated) = 3276000 uAh
[198.760894] bq27541_get_psp charge_avg (uncompensated) = 3414000 uAh
[198.767242] bq27541_get_psp charge_full = 3300000 uAh
[198.772216] bq27541_get_psp charge_design = 4030000 uAh
[198.777435] bq27541_get_psp energy_now = 12086000 uWh
[198.782501] bq27541_get_psp charge_counter = 20000 uWh
[198.787597] bq27541_get_psp power_now = -770000 uW
[198.792388] bq27541_get_psp cycle count = 89
[427.908111] bq27541_get_psp status: Full ret= 0x0200
[427.923492] bq27541_get_psp voltage_now= 4222000 uV
[427.927978] bq27541_get_capacity = 100% ret= 99
[427.932434] bq27541_get_psp temperature= 229 (0.1˘XC)
[427.937499] bq27541_get_psp current_now = 152 mA
[427.942138] bq27541_get_psp charge_now (compensated) = 3120000 uAh
[427.948272] bq27541_get_psp charge_avg (uncompensated) = 3402000 uAh
[427.954650] bq27541_get_psp charge_full = 3167000 uAh
[427.959594] bq27541_get_psp charge_design = 4030000 uAh
[427.964874] bq27541_get_psp energy_now = 11010000 uWh
[427.969848] bq27541_get_psp charge_counter = 32000 uWh
[427.975036] bq27541_get_psp power_now = 642000 uW
[427.979644] bq27541_get_psp cycle count = 89
Guys im on pure nexus rom with elementalx rom... Im using deb lte version.
Currently im only getting 4.5hrs of screen on time.. Can anyone suggest mea rom has good SOT?
Sent from my Nexus 7 using XDA-Developers mobile app
1Ishara said:
Guys im on pure nexus rom with elementalx rom
Click to expand...
Click to collapse
The ROM and kernel are already battery-efficient. Let's check your battery, run adb shell dmesg > dmesg and attach dmesg here or copy from it the following lines:
Code:
bq27541_get_psp charge_full = ...?
bq27541_get_psp charge_design = ...?
bq27541_get_psp cycle count = ...?
k23m said:
The ROM and kernel are already battery-efficient. Let's check your battery, run adb shell dmesg > dmesg and attach dmesg here or copy from it the following lines:
Code:
bq27541_get_psp charge_full = ...?
bq27541_get_psp charge_design = ...?
bq27541_get_psp cycle count = ...?
Click to expand...
Click to collapse
I didn't post this thread, but could you look at my values?
My Nexus 7 (2013) can boot to fastboot/recovery while plugged into USB or unplugged, but can only boot to Android when plugged into AC. I've tried the current 6.0.1 and 4.4.4 factory images, same with both. I used TWRP to get access to ADB. Unless it's plugged into AC it just shows 'Google' and sometimes the beginning of the boot animation and then shuts off when trying to boot to system. Leaving it plugged into AC boots fine.
Code:
~ # dmesg | grep bq27541_get_psp
<5>[ 1.327697] bq27541_get_psp status: Not charging ret= 0x0200
<5>[ 1.328796] bq27541_get_psp voltage_now= 4228000 uV
<5>[ 1.330841] bq27541_get_psp temperature= 278 (0.1óXC)
<5>[ 1.331817] bq27541_get_psp current_now = -21 mA
<5>[ 1.332794] bq27541_get_psp charge_now (compensated) = 3441000 uAh
<5>[ 1.333862] bq27541_get_psp charge_avg (uncompensated) = 3516000 uAh
[B]<5>[ 1.334869] bq27541_get_psp charge_full = 3441000 uAh
<5>[ 1.335906] bq27541_get_psp charge_design = 3830000 uAh[/B]
<5>[ 1.336914] bq27541_get_psp energy_now = 12998000 uWh
<5>[ 1.338073] bq27541_get_psp charge_counter = -8000 uWh
<5>[ 1.339080] bq27541_get_psp power_now = -89000 uW
[B]<5>[ 1.340148] bq27541_get_psp cycle count = 7[/B]
[.....]
<5>[ 3.681732] bq27541_get_psp status: Full ret= 0x0200
<5>[ 3.682739] bq27541_get_psp voltage_now= 4023000 uV
<5>[ 3.686248] bq27541_get_psp current_now = 0 mA
<5>[ 3.687255] bq27541_get_psp charge_now (compensated) = 3441000 uAh
<5>[ 3.688079] bq27541_get_psp temperature= 278 (0.1óXC)
<5>[ 3.689086] bq27541_get_psp charge_avg (uncompensated) = 3516000 uAh
<5>[ 3.689941] bq27541_get_psp charge_full = 3441000 uAh
<5>[ 3.690917] bq27541_get_psp charge_design = 3830000 uAh
<5>[ 3.691772] bq27541_get_psp status: Full ret= 0x0200
<5>[ 3.692749] bq27541_get_psp energy_now = 12998000 uWh
<5>[ 3.693603] bq27541_get_psp charge_counter = -8000 uWh
<5>[ 3.694580] bq27541_get_psp power_now = 0 uW
<5>[ 3.695404] bq27541_get_psp cycle count = 7
I'm not seeing anything there that looks wrong... but I don't know why it doesn't run without AC.
Thanks
Oishikatta said:
I didn't post this thread, but could you look at my values?
Click to expand...
Click to collapse
I hope the OP does not mind.
fully recharge
boot Android with AC on
disconnect AC
keep display on - turn off sleep
What is SOT on your N7?
From the looks of it tour charger isn't providing enough current while your nexus is using more then the charger can provide so ultimately your battery keeps on falling. Try using a new USB cable and look the the charger adapter that it should be 1.5A to 2A.
htb2050 said:
From the looks of it tour charger isn't providing enough current while your nexus is using more then the charger can provide so ultimately your battery keeps on falling. Try using a new USB cable and look the the charger adapter that it should be 1.5A to 2A.
Click to expand...
Click to collapse
Is it because of the near-zero "current_now"? But this can indicate a PC-USB2 port delivering typical <500mA, and indeed the user logged it on ADB from a PC.
Also, the user reports "leaving it plugged into AC boots fine" so the charger/cable can definitely supply 1A+ required during boot up.
Finally, considering "cycle count = 7" there are 3 options:
brand new tablet
old but hardly used
always AC connected
I'd say #3 because "it doesn't run without AC" and even the worst charger/cable can over time eventually fully recharge it.
I intended to comment on the logs when also SOT is provided but I have already concluded that the battery is finished. Note the incredible 4.2V to 4.0V drop within 2 seconds at the same current!
k23m said:
Is it because of the near-zero "current_now"? But this can indicate a PC-USB2 port delivering typical <500mA, and indeed the user logged it on ADB from a PC.
Also, the user reports "leaving it plugged into AC boots fine" so the charger/cable can definitely supply 1A+ required during boot up.
Finally, considering "cycle count = 7" there are 3 options:
brand new tablet
old but hardly used
always AC connected
I'd say #3 because "it doesn't run without AC" and even the worst charger/cable can over time eventually fully recharge it.
I intended to comment on the logs when also SOT is provided but I have already concluded that the battery is finished. Note the incredible 4.2V to 4.0V drop within 2 seconds at the same current!
Click to expand...
Click to collapse
SOT after leaving it charging for a while is about 65 seconds. If I plug it back into AC and boot it's still showing 100%, but only lasts ~1.5s after unplugging again.
I got it in 2014 but didn't use it much.
So looks like nothing to do for it then but replace the battery?
Thanks for the help.
So I charged my Note 7 (N930F Exynos) up to 100% and used an app called GSam Battery Monitor to read the voltage. It read 4.37v. I'm not a battery expert but unless it's one of those HV cells it should be around 4.2v correct?
If the reading is just inaccurate it should swing above and below 4.2v between devices when charged to full capacity, right?
So... Would anyone like to download the app and post their voltage reading and phone model after charging to 100%? It would be interesting to see the results... And get an average.
If anyone knows any better or thinks this is stupid for whatever reason let me know.
azzicles said:
So I charged my Note 7 (N930F Exynos) up to 100% and used an app called GSam Battery Monitor to read the voltage. It read 4.37v. I'm not a battery expert but unless it's one of those HV cells it should be around 4.2v correct?
If the reading is just inaccurate it should swing above and below 4.2v between devices when charged to full capacity, right?
So... Would anyone like to download the app and post their voltage reading and phone model after charging to 100%? It would be interesting to see the results... And get an average.
If anyone knows any better or thinks this is stupid for whatever reason let me know.
Click to expand...
Click to collapse
Some Lithium Ion batteries can be safely charged to 4.35v. Samsung and LG both make such cells.
Chippy_boy said:
Some Lithium Ion batteries can be safely charged to 4.35v. LG make such cells.
Click to expand...
Click to collapse
Fixed it for you.....
Okay so I found an image of the Note 7 battery. (iFixit)
Nominal Voltage: 3.85v
Charge Voltage: 4.4v
So it's supposed to charge to 4.4v. So 3.85v (And I guess 4.37v) is normal under load? Does that mean my readings are normal?
Thought I was on to something.
56K said:
Fixed it for you.....
Click to expand...
Click to collapse
Fixed it for you....
http://www.orbtronic.com/batteries-...pacity-li-ion-rechargeable-18650-battery-cell
Description
Samsung Li-ion 3000mAh (3Ah) 18650 high capacity cell.
This battery rechargeable cell can be charged to 4.35V
Flat top.
Nominal Capacity 3,000mAh
Nominal Voltage 3.78V
Charge Method Constant Current / Constant Voltage
Max. Charge Voltage level (V) 4.35V
Charge Current (C) 0.5C (1.5A)
Min. Discharge Voltage level (V) 2.75V
Model: ICR-18650-30B (Newest Rev. B)
Dimension (mm) 18mm x 65mm
Max Weight (g) 48g
Built-in (internal) Safety Functional Layer
New! Latest (Rev. B) production release is in stock
Made by Samsung
Chippy_boy said:
Fixed it for you....
http://www.orbtronic.com/batteries-...pacity-li-ion-rechargeable-18650-battery-cell
Description
Samsung Li-ion 3000mAh (3Ah) 18650 high capacity cell.
This battery rechargeable cell can be charged to 4.35V
Flat top.
Nominal Capacity 3,000mAh
Nominal Voltage 3.78V
Charge Method Constant Current / Constant Voltage
Max. Charge Voltage level (V) 4.35V
Charge Current (C) 0.5C (1.5A)
Min. Discharge Voltage level (V) 2.75V
Model: ICR-18650-30B (Newest Rev. B)
Dimension (mm) 18mm x 65mm
Max Weight (g) 48g
Built-in (internal) Safety Functional Layer
New! Latest (Rev. B) production release is in stock
Made by Samsung
Click to expand...
Click to collapse
It was a joke.
56K said:
It was a joke.
Click to expand...
Click to collapse
Went over my head, clearly!
Hi all,
My dear HTC One M8 took an unfortunate dive into water recently, I got it out pretty quickly (it was submerged) and shook it dry as fast as I could, then tore the unit down to get the battery disconnected as fast as I could (Screen jumped on, and vibrate motor was on constantly).
After getting the battery disconnected, stripping it down and drying it out, cleaning, etc.
I ordered a new battery and USB charge board as knew those would be most likely culprits.
Anyway, left existing USB and battery in, and after a few days of ensuring dry, etc, connected battery up and usb to charge, phone screen lit up and showed battery with electrical lightning symbol, a few seconds later then the battery with red exclamation mark (point) on screen.
Using my USB voltage/current meter I saw that battery charge current went to around 0.2amps but stayed constant, so I left it to do it's thing.
Powered it on and it's working! All good, touch working, all functions. However battery has an exclamation mark inside it when booted, and if connected to charger whilst phone is on charge current goes up when screen is on, etc (As though the phone is pulling current from the charger) but when idle the charge current drops to 0.
So it won't charge whilst turned on.
I then changed the battery and usb charge port. SAME, no difference. I've even tried a 3rd battery to be sure and it's the same, so I don't think it's the battery or the
usb charge port itself.
So debugging it, using "Ampere" app to see battery state. It says Unknown and often has unusual temperature values (- values or very low). Battery status is UNKNOWN.
I've connected up on adb to take a look and several things are odd, if I pull the battery stats:
Code:
130|[email protected]_m8:/ $ dumpsys battery
Current Battery Service state:
AC powered: false
USB powered: true
Wireless powered: false
Overload: false
USB overheat: false
Extension: 0
PowerJacketExist: false
PowerJacketStatus: 0
PowerJacketLevel: 0
PluginStatus: true
Unsupport Charger: false
status: 1
health: 2
present: true
level: 87
scale: 100
voltage: 4120
temperature: 288
technology: Li-poly
[email protected]_m8:/ $ dumpsys batteryproperties
ac: 0 usb: 1 wireless: 0
status: 1 health: 2 present: 1
level: 87 voltage: 4187 temp: 287
[email protected]_m8:/ $
So the status is 1 = Unknown.
Does anyone know how I can 'influence' this, even by forcing it using dumpsys to set a variable?
I've tried all the usual tricks, power off, hold all buttons, power on holding for 2-3 minutes to reset battery, delete the batterystats.bin under recovery, etc.
Any ideas?
By means of an update, it seems I can charge the phone, BUT it has to be turned off. When turned off, plug the charger in you get the charge symbol which then goes to the battery with red exclamation mark in it, but it continues to pull around 0.5amps and charges fully.
When the phone is turned on and booted up, plug the charger in and the battery exclamation mark appears, charge goes on 0.3amps then drops to 0.01amps and sits there so doesn't pull charge.
So that takes me over to something else, what is it in the o/s that's controlling charge rate?
andyb2000 said:
So that takes me over to something else, what is it in the o/s that's controlling charge rate?
Click to expand...
Click to collapse
I'm not really a "hardware" guy. But just throwing out what I can, hoping it helps in some way.
It's something on the phone (exactly what, I don't know) in conjunction with a "smart" chip on the battery itself. So it's possible you just have a bad battery (pretty common for a water damaged phone, from what I've heard). In which case, a malfunctioning battery is not something to trifle with. An overcharged battery can lead to fire or explosion! And I'm not sure how far you want to go replacing the battery on a phone that is over 4 years old; when it might not completely fix the problem (may also be a short or other damage to the phone's board, etc.).
Hi,
Thanks for the information, yep I do a lot of electronics and dealt with Li-Ion batteries for some time.
I have replaced the battery with two other alternatives as I also suspected the Li-ion control circuitry being the source of the issue, but alas it isn't. Voltage on the li-ion cells is fine, and the charge circuitry is responding correctly with voltage and level cutoffs in the correct ranges.
I also replaced the USB charge port which handles the charge regulation technology for the phone also, but to no avail.
My current focus is on the main circuit board, as I believe there is a temperature sensor used to monitor the battery temperature and this is giving me unusual readings which I'd suspect the O/S is controlling charge due to that.
Cheers for the input though!