Database Users

My Nook has insomnia!

My Nook has insomnia, it won't sleep.
The battery drain speed has been bad for a while. I can't seem to narrow it down. I've killed a ton of apps and services and still it drains.
I was trying to measure the current out of the battery but I'd really need to get some tiny mating connectors to do it correctly.
Since I can't do that without messing up the wiring, I put a milliampmeter in line with a charger. When the Nook is fully charged it will give you some indication of current drain.
Right now my Nook is drawing about 65 mA. It's in what should be the sleep mode, I tapped the power button and the display has the saver on it.
But here's the kicker. It looks dead, WiFi is off, USB host mode is off, but if I skeedaddle my finger over the screen the current rises to 75 mA. Obviously, it's on.
I looked at dumpsys power, there are no WakeLocks.
Any clues?

Have you tried getting back to stock, so you can be sure it's not a hardware issue?

Stock? What's that?

Renate NST said:
Stock? What's that?
Click to expand...
Click to collapse
Stock means going back to the software like it was provided by the manufacturer. (Actually I'm not sure if you are joking )

Renate NST said:
[...] The battery drain speed has been bad for a while. I can't seem to narrow it down. I've killed a ton of apps and services and still it drains. [...] I looked at dumpsys power, there are no WakeLocks.
Click to expand...
Click to collapse
I've found comparing battery life on the NST is difficult, as it generally is better than a typical Android device, even in the worst case, and so much varies between user configurations.
Not sure if you're after an engineering explanation, or user-level troubleshooting. For comparison, here are some rough numbers based on my usage over the last couple of months:
1% per hour with wifi on and system idle.
1% per 6 hours with wifi off and system idle.
3-5% per hour with wifi on and active use.
You're not seeing wakelock usage, which is good. Is wifi on or off? Just how "bad" is bad?
If you can't narrow it down, you might seriously consider running stock for a couple of days to develop a baseline for your hardware. Then you can compare your custom configuration to that baseline and get more meaningful numbers.
Interesting about the sleeping screen noticing finger touches.

I'm losing about 30-40% charge overnight.
The point of trying to measure current was to get a more immediate sense without any long time trials.
In /data/data/com.android.providers.settings/databases/settings.db
I do have 12|stay_on_while_plugged_in|0
It should not be on while plugged in.
I went and tried the oldest uImage I have from noogie. It still acts the same.
Of course the WiFi is off, but if I leave the WiFi on I can still ADB right into it when it is supposed to be off. Has anybody tested this?

30-40% overnight definitely is high, especially with wifi off. My settings.db shows:
12:stay_on_while_plugged_in:3
Did you register the unit? I've read a few reports of unregistered units hammering the battery as they try to phone home or other such nonsense in the background. Not sure how valid they are.

Yes, it's been registered.
It has been doing this for a while.
I just gutted all the BN cloud stuff. ET can't phone home.
Moreover, logcat is quiet.

I figured out that the nook sleeping while plugged in is pretty much hit-or-miss even if you tell it in settings.db
Now for more fun!
Get yourself an IR detector diode from Radio Shack:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://www.radioshack.com/product/index.jsp?productId=2049723
Use the bluish one, connect the short leg to the tip of a 1/8" stereo cable, the long leg to the shield. Wrap it up in tape. Plug this into the mic input of a PC and crank the volume and the "mic boost" if it has one.
Aim the diode pointing downward at the lower left hand corner of the inside frame of the nook display. See diagram.
When the display is just idling, only the LED in the lower left side fires and the speakers should play a fast ticking. Touch the screen somewhere and it goes into a faster buzz. Turn off the Nook and a few seconds after the screen goes blank all buzzing will stop.

Do you mean you're seeing this amount of battery consumption while the unit is plugged in?
Less scientific, but if I press my ear to the NST when it's asleep, I hear nothing. If I press the 'n' button to get the unlock screen, I hear a high pitched noise. Interestingly (perhaps), it varies between two NSTs. One one, it sounds like an old 56K modem. On the other, it's a much higher frequency sound.
All interesting stuff, but unless you compare it to a stock baseline, I'm not sure how to figure out what your underlying problem is with battery consumption.

As far a high pitch sounds go, there's a number of DC converters in the Nook.
The screen uses +/- 15V to drive it.
Well, I don't have to go back to stock really.
I know how the power consumption is supposed to work.
I do know that USB host mode is a power hog, and it's not through supplying current to external devices. Even with a powered hub it uses a lot.
I think that I might have fixed it.
Before, I was having it connect on ADB over WiFi when it was supposedly asleep.

Renate NST said:
I do know that USB host mode is a power hog, and it's not through supplying current to external devices. Even with a powered hub it uses a lot.
Click to expand...
Click to collapse
I was under impression, with USB host mode enabled it drains battery a lot without any USB slave device connected…
Am I wrong about it?
Renate NST said:
I think that I might have fixed it.
Before, I was having it connect on ADB over WiFi when it was supposedly asleep.
Click to expand...
Click to collapse
What have you found?
---------- Post added at 05:29 AM ---------- Previous post was at 05:25 AM ----------
Renate,
Since you have milliammeter connected, could you tell what the consumption is with USB host mode enabled and disabled (without any USB slaves)?

Here's some numbers that I've collected.
Measuring current at the micro USB can be difficult until the battery is fully charged.
Even then, the charging circuit will try to "top up" with pulses for a while.
Power consumption:
Full power off: 9 mA (This is not what would be consumed if the charger were not connected.)
On and idle: 65 mA
Booting up: 160 mA (100% CPU)
Host mode: 160 mA (nothing attached)
Power drain:
USB keyboard: 5 mA (no LEDs on)
USB thumb drive: 65 mA (but still not working connected directly)
So the touch screen not shutting down is the worst scenario and you lose about 30% overnight.
Last night the touch screen did shut down, but I lost about 10% anyway.

Could you measure couple more, please:
Sleeping mode and WiFi (idle, no transfers)
Since you measuring between charger and nook, not between battery and nook, can we use something like P3
Just need to subtract AC 110v to DC 5v conversion loses, right?
Renate NST said:
So the touch screen not shutting down is the worst scenario and you lose about 30% overnight.
Last night the touch screen did shut down, but I lost about 10% anyway.
Click to expand...
Click to collapse
You wrote early – you’ve found the cause and fit it, right?
Or was it something related to “Host mode: 160 mA (nothing attached)”?
Still where those 160 mA goes?
Is it simply maxing CPU out by polling something?

ApokrifX said:
Still where those 160 mA goes?
Click to expand...
Click to collapse
After a lot of screwing around with this I've determined that measuring input current on the USB connector is too unreliable.
The problem is that the charging circuit switches in and out even when it says that it is disabled.
It is going through the charging circuit because the current settings modify it correctly and even turn it off completely.
This is similar to the problems with USB host mode. We can't get any straight info out of the driver.
It shows "await_vrise" quite often, even when it is in host mode.
Also, await_vrise should have a timeout in fractions of a second and should never be a steady state.
So, it looks like host mode is not using significant CPU time in any case.
Back to the original problem, I have seen how the touch screen does not shut off sometimes.
Rebooting it in full gets it back on track.
I've not seen what causes it to get in the non-shutdown mode.

Renate NST said:
I've not seen what causes it to get in the non-shutdown mode.
Click to expand...
Click to collapse
If you can get logcat logs when nook does and does not shutdown properly and compare, it might give you a clue.
At least the IR detector diode you have let you see right away if screen didn’t shutdown properly.
Is there a way to send nook to sleep from command line?

So USB host mode without anything plugged in is causing some drain. Has anyone an idea of how much roughly?

I may have stumbled on something that MIGHT help here. I have always put my Nook to sleep by pressing the power button and after a year for heavy use, it is starting to sound and feel like it might be ready to break. So, I started looking for another way to make my Nook sleep. I found that the bottom button (looks like a power button icon) in button savoir will put my Nook to sleep if button savoir has Superuser permissions. So this is the method I have begun to use (for the last week or so). I have noticed that occasionally, even before I rooted my Nook, that pressing the power button would bring up the screen saver, but not actually put the device to sleep. Since I have been using button savoir to put my Nook to sleep, this has not happened once. Perhaps this procedure might help someone with this problem.

David0226 said:
I found that the bottom button (looks like a power button icon) in button savoir will put my Nook to sleep if button savoir has Superuser permissions. So this is the method I have begun to use (for the last week or so).
Click to expand...
Click to collapse
David: When I try that, my Nook (ST) responds with "Feature not supported on your device. Requires 2.2 and above." How is this working for you?

wilo108 said:
David: When I try that, my Nook (ST) responds with "Feature not supported on your device. Requires 2.2 and above." How is this working for you?
Click to expand...
Click to collapse
Hmmmm.
Good question. Unfortunately, I don't have a good answer. I will say that the first time I try it after a reboot, it writes a message to the screen that button savior has been granted superuser privileges. Then the next time and every time until I power off the device it works. I initially rooted using tinynoot, then tried MininalTouch without unrooting. So perhaps I have gotten my device into some weird state where this works. I wish I knew a lot more about android ....
Sorry.

Nexus S ICS 4.0.4 - Reboots every minute!

My phone is a rooted Nexus S ICS - 4.0.4
It reboots now whenever it goes into sleep mode (when the LCD turns off). This is like 1 reboot every 1.5 minutes. It is really crazy and I have tried disabling apps like Gmail and Google+ but with no results. I have also disabled Wifi Sleep policy to "Never", no results either.
The phone has the stock 4.0.3 ROM upgraded via ClockWorkMod to 4.0.4 using Google latest OTA update zip. It was working fine for the past 10 days, but this thing started happening today.
I had experienced random reboot like this one month ago on 4.0.3 . That happened again whenever the phone went into the sleep mode.
These reboots do not happen when the phone is plugged into USB for debugging or when it is charging.
UPDATES:
-------
Full Factory Reset/ Dalvik cache wipe/ Battery stat wipe --> The phone Still reboots each 5-6 minutes in sleep mode.
BATTERY INDICATOR ISSUE:
When the phone is turned off and it is charging, unhooking the phone from the battery charger has no effect on the Charing indicator and it keeps charging !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I pull in the charger, then pull out but no effects!
Only a full battery remove would make the charging indicator go away.
Could these random reboots be related to the battery indicator issue?
UPDATE:
The charging indicator malfunction, as displayed above, is the cause of these reboots while the phone is in sleep mode and not connected to a charger. I have played a little bit with the USB port of my phone, cleaned it and raised the lower edge and the indicator went away.
Meanwhile the phone has not rebooted for almost 4 hours.
-----------
Update: ISSUE RESOLVED
I changed the charger to a new stock Samsung charger and bought a new battery. No restarts in the last two weeks!
This was not a software bug.

download a custom rom + custom kernel and do a full wipe, then flash the combo.
all issues gone

thegtfusion said:
download a custom rom + custom kernel and do a full wipe, then flash the combo.
all issues gone
Click to expand...
Click to collapse
Are there any easier choices?

Regular rebooting is a fairly serious issue, so you should really consider a serious solution i.e. custom rom/kernel. You could also try reflashing stock 4.0.4 and this might fix things for you.
Since you're already rooted, you've already done the hard part and you can do a full nandroid backup, so worst case scenario you can always revert to your rebooting stock rom
Sent from my Nexus S using xda premium

heccubusxda said:
Regular rebooting is a fairly serious issue, so you should really consider a serious solution i.e. custom rom/kernel. You could also try reflashing stock 4.0.4 and this might fix things for you.
Since you're already rooted, you've already done the hard part and you can do a full nandroid backup, so worst case scenario you can always revert to your rebooting stock rom
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
UPDATES:
-------
Full Factory Reset/ Dalvik cache wipe/ Battery stat wipe --> The phone Still reboots each 5-6 minutes in sleep mode.
BATTERY INDICATOR ISSUE:
When the phone is turned off and it is charging, unhooking the phone from the battery charger has no effect on the Charing indicator and it keeps charging !
I pull in the charger, then pull out but no effects!
Only a full battery remove would make the charging indicator go away.
Could these random reboots be related to the battery indicator issue?

If you're REALLY attached to stock rom I would suggest flashing a custom kernel. No data wipe, just cache and dalvik.
It would take you like 10 minutes and it MIGHT solve the problem.
Nothing to lose and a working device to gain
If that doesn't work, do a full backup and flash a rom (stock or custom lots of choices).
Sent from my Nexus S using xda premium

heccubusxda said:
If you're REALLY attached to stock rom I would suggest flashing a custom kernel. No data wipe, just cache and dalvik.
It would take you like 10 minutes and it MIGHT solve the problem.
Nothing to lose and a working device to gain
If that doesn't work, do a full backup and flash a rom (stock or custom lots of choices).
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Is the battery charging indicator while the phone is off also a part of the currently installed ROM? I mean 4.0.4 or 2.3.6 or Cyanogenmod?

heccubusxda said:
If you're REALLY attached to stock rom I would suggest flashing a custom kernel. No data wipe, just cache and dalvik.
It would take you like 10 minutes and it MIGHT solve the problem.
Nothing to lose and a working device to gain
If that doesn't work, do a full backup and flash a rom (stock or custom lots of choices).
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I did a full ROM installation (ZD3PyN0t.zip) and the same thing happened.
Crazy the charging indicator shows when the phone is off and not connected to ANY charger!

If you've done a FULL wipe (system, boot, data) and installed the stock 4.0.4 ROM without a custom kernel and without restoring any data or apps from backups and you're still getting reboots then you've got a hardware problem. If not then you did something wrong with your previous install.
Sent from my Nexus S 4G using Tapatalk 2

that sounds like symptoms of too much undervolting for your phone(reboots when the screen is off). but from what ive read here, youre not undervolting it. are you messing with your cpu speed or using any screen-off profiles?

jesusice said:
If you've done a FULL wipe (system, boot, data) and installed the stock 4.0.4 ROM without a custom kernel and without restoring any data or apps from backups and you're still getting reboots then you've got a hardware problem. If not then you did something wrong with your previous install.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Well I guess if it were a hardware issue then these reboots would occur even when the phone was plugged in a USB charger. The phone never reboots while charging, even in the sleep mode.

simms22 said:
that sounds like symptoms of too much undervolting for your phone(reboots when the screen is off). but from what ive read here, youre not undervolting it. are you messing with your cpu speed or using any screen-off profiles?
Click to expand...
Click to collapse
I think you are right. I left the phone in the charger while turned off, so it became fully charged. Now, so far, haven't seen any reboots even in the sleep mode without the charger; it has been 25 minutes, good, but the phone is not reliable at all for me.
UPDATE: The phone rebooted after 31 minutes. The battery has gone to 80%. This is crazy!
I have not noticed any missing cpu speed. But screen repaints on the lower left parts of my phone's LCD are a little choppy and sluggish when swiping home screen or sliding a view. It is like that part of the screen has troubles in smoothly updating itself.
I have noticed that sometime the "charging indicator" shows the phone is being charged when the phone is off and not connected to any chargers!
This is crazy! The only way to remove the charging indicator is to remove the batteries.
Also there were times when the phone turned off completely (while battery was 30% or lower) and didn't even reboot or turn on by pressing the power button. A battery removal would resolve the issue, but then random reboots would come in.
Do you think these symptoms are related to the reboot issues?

Have you tried a new battery?

I second Harrbs response. My friend had a G2 that did the same exact thing. He bought a new battery and the issues completely went away.

chronophase1 said:
I second Harrbs response. My friend had a G2 that did the same exact thing. He bought a new battery and the issues completely went away.
Click to expand...
Click to collapse
Please read my update in the original post. The USB port was the culprit. And the reboots were linked to a malfunctioning charging indicator.
And I guess a bad battery could also create the same behavior.

Reboots came back
chronophase1 said:
I second Harrbs response. My friend had a G2 that did the same exact thing. He bought a new battery and the issues completely went away.
Click to expand...
Click to collapse
Well after fully charging the phone last night with the wall charger, while the phone was turned off, this behavior came back and also the reboots. Now I think I should go for charging the batteries to see what happens next.
This happens with the wall charger I guess. I am using a Nokia Wall charger btw. It has the same voltage and usb specification as the stock Samsung charger. Could this the culprit?

Just about anything could be the culprit so try different chargers/usb cables, a different battery and observe the 3 pins that connects to the battery and make sure they're clean (as well as the 3 slots on the battery itself) to cover all bases.
A full wipe and reflash of Stock 4.0.4 (fastboot images would be perfect) would be recommended, any number of hard to diagnose random problems can tag along without one. Remember to do a backup beforehand, as always.

Flash everything. The latest Boot loader, a new radio, a new rom , kernel.. etc.
All the best!
Sent from my Nexus S using Tapatalk 2

Running a STOCK Google Nexus S 4g ICS 4.04 and I was having the same issue after going to ICS, as soon as I put my phone in sleep mode it would reboot and do this a few times in a row. Also my battery was draining like crazy one of the main things draining it was media at about 35%, i wasn't even running any music or video services. I searched everywhere for an answer and nothing so before rooting I decided to do a complete factory reset SD card and all. I transferred all my SD card info to my computer then did the reset. Low and behold not one reboot its been about 24 hours now. Also the battery drain issue gone media isnt even on the list of battery use. Before reset about 3.5 hours on battery to 30% now first run through about 68% at 3.5 hours. Also the battery showing its charging when its unplugged take very small piece of plastic and easily lift the small piece inside the charging port on the phone up GENTLY lift it up a hair and I bet the charging problem goes away. Hope this helps people.

hmdz said:
Well after fully charging the phone last night with the wall charger, while the phone was turned off, this behavior came back and also the reboots. Now I think I should go for charging the batteries to see what happens next.
This happens with the wall charger I guess. I am using a Nokia Wall charger btw. It has the same voltage and usb specification as the stock Samsung charger. Could this the culprit?
Click to expand...
Click to collapse
I've used an aftermarket charger providing 1A instead of 750mA in the past and it made my screen act all funky. Worked right as soon as I unplugged it, so make sure the amperage is the same.

Phone will not charge

Hey guys I have a bit of a dilemma. I have a verizon note 3 that has the bootloader unlocked by me. It's rooted with Temasek's CM13 Rom. My only issue is that I am having problems charging my phone whether it is turned on or off. I have replaced the battery recently in hopes to troubleshoot and solve my problem but came to no avail. When turned on and plugged in it shows the icon in the top right with the lightning bolt to indicate it is charging however it seems to drain still and will eventually turn itself off. If I try to charge it when it is turned off it just vibrates every 1-2 seconds repeatedly. I have replaced the charger cable and block with a brand new one from the store as well. Any help is appreciated.

Try the following and report your results.
1) Pull the battery with nothing plugged in to the USB port. Put the new battery into the phone. While watching the screen carefully, plug the ORIGINAL charger and ORIGINAL cable in to the phone.
Do you see:
(A) Nothing at all
(B) A battery charging animation, or
(C) A static battery icon graphic followed by a brief appearance of the Knox message "Knox Warranty: kernel"
Hopefully the answer is (A) or (B). If not you might have a chicken-vs-egg problem getting your battery to charge.
Answer these questions:
2) Is the original charger the OEM (Samsung) 2A Wall-wart charger, or something else?
3) Perchance was the new charger identified as "Apple Compatible" or "For iPhone", or similar?
4) Are you able to use both cables (old & new) for data connections to a PC (testing with some other devices that can exchange data)
5) What are the rated charging capacities of the old & new chargers? 2 Amps?
The business about Apple compatible chargers is that Apple intentionally violated parts of the USB specification (to suit it's own needs) that detail how devices are supposed to interpret signals on the 4 wires of a USB 2.0 connector during initialization. So a lot of "Apple compatible" chargers produce out-of-spec signals during initialization, and many Android devices will conclude that those chargers can only provide 500 mA of current. So even if they are rated at 2A, the charge controller in the device won't pull anything more than 500 mA.
Similarly, there's all sorts of counterfeit junk being sold, even USB cables. I bought a "USB 3.0" cable in a box that appeared to be Samsung's from Fry's electronics. Despite it having blue connector inserts, it didn't even have any D+ or D- connections. It was neither USB 3.0 nor even a data cable - it couldn't even be used for charging beyond 500mA (because of the missing D+/D- connections). If you can use the cable for communication, at least you know that all four wires are present.
The amount of current that gets pushed into a handset battery during charging is typically controlled by a charge controller chip that sits either on the motherboard or on the (replaceable) USB connector daughterboard and the battery, and also watches transitions taking place on the D+/D- lines shortly after plug-in. (The external charger is just a dumb power supply rated to provide 5v up to whatever it's maximum current draw is before the voltage collapses... unless it is an Apple charger, and then it wiggles the D+/D- lines around inappropriately, confusing any device you plug them into that actually follows the USB spec, aka all Android devices)
Were it not for some certain odd behaviors that the Samsung bootloader engages in when there is an unsigned boot image flashed to the device, the scenario I'd be most likely to suspect is the following:
That you have a bad charge controller chip and you need to replace the USB connector interface. (IIRC, I think the charge controller chip might be on the connector module behind a flex connector, but I can't remember).
Sorry for all the questions - just trying to eliminate possibilities which could be interfering with your debugging.
https://www.ifixit.com/Teardown/Samsung+Galaxy+Note+3+Teardown/19209

1: Nothing at all.
2: The original charger is a verizon 2.1A micro-usb charger that I bought from a direct verizon store.
3: No it is a Samsung usb3.0 charger directly made for the galaxy note 3 from verizon. Guy pulled it out of the box for a old note 3 he had sold out of the store and the customer already had a charger.
4: Yes I can use both on a galaxy s5. The old charger is a micro-usb and the new is a usb3.0. They charge and transfer data through both cables to the S5.
5: Old charger: 2.1A New charger: 5.3v=2.0A
I have replaced the charging port before on this same phone because my charger would only work being held a certain position and that fixed my issue. However now it won't charge hardly at all. Some time I can get lucky if I leave it overnight but not always. It's temperamental. But I honestly thought it would be a software issue considering it doesn't do anything. When it does do something the battery logo will come up but will not animate, it will remain static and then disappear forcing the phone to turn on and will slowly charge.

Captain Skeet said:
1: Nothing at all.
2: The original charger is a verizon 2.1A micro-usb charger that I bought from a direct verizon store.
3: No it is a Samsung usb3.0 charger directly made for the galaxy note 3 from verizon. Guy pulled it out of the box for a old note 3 he had sold out of the store and the customer already had a charger.
4: Yes I can use both on a galaxy s5. The old charger is a micro-usb and the new is a usb3.0. They charge and transfer data through both cables to the S5.
5: Old charger: 2.1A New charger: 5.3v=2.0A
I have replaced the charging port before on this same phone because my charger would only work being held a certain position and that fixed my issue. However now it won't charge hardly at all. Some time I can get lucky if I leave it overnight but not always. It's temperamental.
But I honestly thought it would be a software issue considering it doesn't do anything. When it does do something the battery logo will come up but will not animate, it will remain static and then disappear forcing the phone to turn on and will slowly charge.
Click to expand...
Click to collapse
TL;DR Maybe it is a software issue.
There is something subtle that happens when an unsigned boot image is in the boot partition. This is going to sound kind of strange, but it appears that in some conditions where you would expect the phone to be off, when the bootloader detects an unsigned boot image, it will start the kernel up in some kind of software prison where the kernel is actually running, but unable to complete the normal boot. (See this thread, posts #483-#494 where @Zzim posted a very similar set of observations to yours - again with CM13.)
Just now I repeated this experiment - flashed a unsigned image into boot and observed what happens plugging to either a charger or a PC, and then flashing a signed image into boot, and observing what happens in the same circumstance (in each case plugging done after a battery pull & replacement)
Unsigned boot image: Pull battery, replace battery. Plug an active device such as a PC or a dumb charger into the phone. A STATIC battery icon image appears - not an animation - and then a few seconds later you'll see "Set Warranty Bit: kernel" appear momentarily on the screen. If it's a PC you are plugged into, 15-16 seconds later the USB device port changes to a VID/PID device which is exactly the same as the device ID used during a normal boot. But the screen stays dark - the boot never completes! (I don't know if many minutes or hours later the USB device disappears.) That 15-16 second interval is also exactly the amount of time it normally takes for the boot process to be reaching the spot where it is setting up the USB port.
Signed boot image:: Same as above - Pull battery, replace battery, Plug in PC. A battery ANIMATION appears, no Knox message (expected) but also this: with a PC you are plugged into, no USB activity.
It seems a little weird, but its almost as if the bootloader is executing the kernel, but in a way that it's ramdisk has been spoofed or something so that init() never does anything meaningful. Rather suprising but maybe the kernel actually needs to be alive to control the charge control chip? Or produce a battery animation? That sure seems extreme.
Anyway, my experience is that the temasek/CM13 kernel eats through a lot of battery compared to stock kernels. If this phenomenon is still taking place when you plug to a charger and the charge controller isn't working very well, I suppose that could prevent you from gaining any charge on the battery. But I wouldn't expect even that to be chewing through 2A* ~3v ( = 6W) of power in that state, so there must be something else going on. OTOH, if the non-stock kernel messes with the charge controller somehow, then this mechanism potentially *could* interfere with charging.
I tried booting my phone plugged in to the USB charger but with no battery present, thinking, "well, maybe as an experiment he could restore a stock kernel termporarily using a custom recovery". But no joy, phone does nothing.
If both your batteries are so completely discharged that the phone isn't going to do anything, it would seem you are going to need to figure out how to get one of those batteries charged with enough juice so you could boot TWRP and put a stock boot.img in the boot partition. Seems like you need a friend with a Note 3 or a battery store that can juice up your battery enough to flash a stock ROM. Or there's this: boot into TWRP instead of your ROM (& temasek's kernel) and see if it starts gaining charge more rapidly than if temasek/CM13 was booted.
I've only had some older versions of (temasek) CM13 on my phone, so I can't vouch for recent stuff, but I will say that even though it ate up battery, it never caused me to lose charge while the ROM was up and running and the phone was plugged in to a 2A Samsung OEM wall-wart. (I would think that also your phone would get really HOT if it was really getting 2A of current and still could not keep the battery charged)
Which exact version of CM13 were you one when this started happening? I sort of remember someone over there reporting "massive" battery usage for a recent build.
.

Honestly it has done this since I can remember being on Temasek's CM13. But I have been using it since it was released. I never noticed it until recently because my old battery I've had since the note 3 was released did have some major drain issues. But my new battery on the updated build (OTA) has been pretty decent battery life....just won't charge when plugged in. CM13 is the only rom I use and is on my only phone unfortunately but If I have to start from square one I won't hesitate to if does solve my charge issues. I can usually get my phone to boot to download mode after 15-20 tries. And it usually won't turn off in download mode. So if you have a theory/hypothesis you would like to test that won't brick my phone then i will be more than happy to try/test. Maybe if others have the same issue then we can resolve it for others before they throw their phone in a lake because it won't charge lol.

Captain Skeet said:
Honestly it has done this since I can remember being on Temasek's CM13. But I have been using it since it was released. I never noticed it until recently because my old battery I've had since the note 3 was released did have some major drain issues. But my new battery on the updated build (OTA) has been pretty decent battery life....just won't charge when plugged in. CM13 is the only rom I use and is on my only phone unfortunately but If I have to start from square one I won't hesitate to if does solve my charge issues. I can usually get my phone to boot to download mode after 15-20 tries. And it usually won't turn off in download mode. So if you have a theory/hypothesis you would like to test that won't brick my phone then i will be more than happy to try/test. Maybe if others have the same issue then we can resolve it for others before they throw their phone in a lake because it won't charge lol.
Click to expand...
Click to collapse
I wouldn't risk flashing anything with a poorly charged battery, even if you can get to the Odin screen.
I'd figure out some way to get both of your batteries charged about 25% or so - got a friend with a different Note 3? I suppose you could even take your battery in to a VZW retail store, give them a sob story about how you are not sure if your phone is dead or not, could you please charge this for me just a little bit so I can find out if it's my phone or my charger? Or something like that - get creative.
If you are comfortable with electronics, a 5v supply and two 1/4 watt 22 ohm resistors in parallel ( == 1/2 watt 11 ohm resistor) would safely add charge to a discharged NiMH battery at about 180 mA while not exceeding the thermal rating of the resistors, or creating a dangerous situation by charging with too much current. (When discharged, NiMH batteries are about 3v. So: (5v-3v)/(11ohms) = 0.18 amp. P = I^2*R = (0.18)^2 * 11 = 0.36 Watts). Or you could use a different phone with a similar battery size and get creative by insulating the battery terminals of the battery that fits, tape two wires to your battery, and stick the other ends of those two wires in the little spring contacts of the other phone. Obviously you need to be absolutely sure you are observing the correct polarity here and making sure that nothing is going to come loose and create a short. (A battery meter/DMM helps here making sure you are not doing something stupid)
Then stick a partially charged battery in your phone, boot to TWRP, put it on the charger, and see if the charge % is going up or down. That's a different kernel, so if the fault is with the temasek/CM13 kernel, presumably you will get more rapid charging when TWRP is running. I think it displays battery percentage right on the main screen. Or if you wanted you could restore a stock ROM. (Not the whole thing including bootloader! Just boot, system, and cache. Remember that with an unlocked bootloader you can flash whatver ROM components you want in Odin in the AP slots)
When I ran the charger tests just now, I made a TWRP backup of my boot partition (only), and manually flashed an older sprint kernel into my boot partition
Code:
dd of=/dev/block/mmcblk0p14 if=/sdcard/bkup/0407-hltespr.img
and then ran my testing experiments making sure to avoid accidentally booting up the main ROM (so that the mis-matched kernel couldn't bollux anything in /data up). When done testing, I just restored the TWRP backup that only had the boot paritition in it.
Anyway, you get the idea. If it really is temasek/CM13 that is causing the problem, then temporarily putting a stock boot.img into your boot partition will give a different charging result.
But at the moment you have a chicken-vs-egg problem: you can't get the temasek/CM13 boot image off the phone (even temporarily) until you get a little charge on a battery first. I think that means you need to get one battery charged a little bit using some other device.
.

I managed to get a charge on my device somehow; (55% so far) . It seems that with CM13 Build for Hlte has changed the "Offline charging" images to be modified. I searched the rom thread and seen your theory about the device not fully turning off and being in a weird state. It seems users are having similar effects and it is different per user. What I have found (may not be 100%) is if you take the battery out, unplug it and put the battery back in, then go to download mode as if you were going to flash something through odin then press and hold the power button - it turns the my phone off and then shows static image with "Set Warranty Bit: kernel" on top then disappears. Supposedly (guess) that means it is charging offline (turned off). However I wish I could change it so it would pulse the top light or show an animation when the home button is pressed or something.
Just seen where you were the one explaining the process happening in the CM13 thread..It is exactly the same issue.

Captain Skeet said:
I managed to get a charge on my device somehow; (55% so far) . It seems that with CM13 Build for Hlte has changed the "Offline charging" images to be modified. I searched the rom thread and seen your theory about the device not fully turning off and being in a weird state. It seems users are having similar effects and it is different per user. What I have found (may not be 100%) is if you take the battery out, unplug it and put the battery back in, then go to download mode as if you were going to flash something through odin then press and hold the power button - it turns the my phone off and then shows static image with "Set Warranty Bit: kernel" on top then disappears. Supposedly (guess) that means it is charging offline (turned off). However I wish I could change it so it would pulse the top light or show an animation when the home button is pressed or something.
Just seen where you were the one explaining the process happening in the CM13 thread..It is exactly the same issue.
Click to expand...
Click to collapse
When you see that "Set Warranty Bit: kernel" message, that means that the Bootloader is very likely starting the kernel up (especially likely when you notice USB activity 15-20 seconds later). On my phone - which has a much much older MJ7 bootloader, every time you unplug the charger and then re-plug that charger, that "Set Warranty Bit: kernel" message re-appears. Even though the phone is supposedly "off"
I suppose it is possible that the Signed, stock kernels get started up in exactly the same fashion. You don't see any warning message on the screen because the stock kernel is signed, so the screen just stays dark and it appears that nothing is happening other than maybe a brief battery charging animation. OTOH, it's a little odd that there is no USB activity after a delay in that case.
It's pretty counter-intuitive. You would want the phone to charge as fast as possible when it is "off", so using the minimum amount of power would help that. And there's no way that a modern Linux kernel with several million lines of code is needed to paint a simple animation on a screen or charge a battery - the bootloader is more than capable of that. (The Code Aurora LK "LittleKernel" bootloader from which a lot of these vendors have derived their proprietary bootloaders is actually a tiny operating system capable of running multiple threads simultaneously as separate "apps".)
These phones appear as if there is always something going on even when they are "off". I built one of those UART jigs to be able to see kernel messages before init() even is launched. If I yank the battery, replace the battery, and then plug that thing in to the USB port.... the phone boots immediately without me touching anything else.
You are not on 10.4 are you? There was a user over there that was saying that the battery usage was quite high...

Yes I'm on 10.4. My battery drain isn't really high surprisingly it just doesn't charge usually when the battery is below 20%. If I plug it up to the wall it has the lightning bolt and says it's charging however if I leave it alone and come back then it has a lower percentage on the battery than when I plugged it up. And I just checked your twrp method and it seems to charge my phone when not in the rom as well. The rom thread OP posted another kernel version of the one that comes with the rom in the thread. Original is v1.86 and new version is v2.05. Maybe it has some changes that might help?
http://temasek.rajasthanautoworks.in/Samsung Galaxy Note 3 - HLTE/CM13.0/Kernel/

My girlfriends note 3 is gOing through these same exact issues, she needs something stable so I'm going to put her back on Alliance, I will try a fresh restore and flash alliance.
Currently going from 10.4 to alliance battery drain is still present.

VJmac15 said:
My girlfriends note 3 is gOing through these same exact issues, she needs something stable so I'm going to put her back on Alliance, I will try a fresh restore and flash alliance.
Currently going from 10.4 to alliance battery drain is still present.
Click to expand...
Click to collapse
It seems to be a current issue after being unlocked. Either put the phone in download mode then press the power button it should restart the phone in the off status and should charge. Or put it in recovery mode in twrp and it should charge that way as well.

Captain Skeet said:
Yes I'm on 10.4. My battery drain isn't really high surprisingly it just doesn't charge usually when the battery is below 20%. If I plug it up to the wall it has the lightning bolt and says it's charging however if I leave it alone and come back then it has a lower percentage on the battery than when I plugged it up. And I just checked your twrp method and it seems to charge my phone when not in the rom as well. The rom thread OP posted another kernel version of the one that comes with the rom in the thread. Original is v1.86 and new version is v2.05. Maybe it has some changes that might help?
http://temasek.rajasthanautoworks.in/Samsung Galaxy Note 3 - HLTE/CM13.0/Kernel/
Click to expand...
Click to collapse
Dunno but your test of the TWRP kernel vs. the temasek kernel seems like a smoking gun, so it's probably worthwhile to investigate. I thought I remembered someone saying they swapped kernels for lean kernel but I couldn't find that post, so I'm not sure what I remembered.
Trying to run a simple test over here (unpack and repack a stock kernel to break the Sammy signature - see if the observable behavior has nothing to do with signing and is all about the kernel) but I'm mucking it up... need sleep.
lates

Better Information About Battery Charge Animation on unlocked Phones
@Zzim @VJmac15 @Captain Skeet
I have some unambiguous clarifying information now about the "battery charge animation" when the phone is supposedly in an "off" state but plugged to a charger. Read on.
I took a stock (MJ7) boot image and unpacked it, and then simply repacked it, and flashed it to the boot partition in my (MJ7-firmware) SM-N900V.
Because there are very slight differences in "cpio" and libgz from linux release to release, this has the effect of making very tiny differences in the re-packed ramdisk image - enough that the Samsung signature is now broken, but likely nothing different at all from a functional perspective with the stock kernel or ramdisk (The kernel itself and it's device tree are bit-for-bit identical).
So what do it observe when I turn the device "off" and then plug to a dumb charger? The exact same stock "battery charge animation" that you would see on a retail device with a locked bootloader - plus one additional detail: that "Warranty bit set: kernel" message on the screen. After the battery animation runs for a while, the screen goes dark and the LED lights up according to charging state (red=charging, blue=charged, etc).
So the implication here is quite clear: the "off state" charging behavior you get depends on the kernel you have installed, and there is no difference in animations between signed and unsigned versions of the same stock kernel+ramdisk. An unlocked bootloader gives the same animations and LED illuminations as pure stock - so long as you are using a stock kernel.
Before I thought this was the bootloader running the (battery animation) show; but now I am beginning to believe that the bootloader fires up the kernel in some sort of jail when you plug power to the device. So if you are using a kernel that defaults to using a lot of power in it's idle state, (especially if it uses "init" to tweak into place battery savings) it's not going to charge as well as a less hungry kernel does - even when the device is supposed to be "off". It's even possible that the kernel could use more power when in this curious "off " state than when the ROM was running! (For instance, if the kernel developer decided "I'm gonna make this thing boot fast by setting the governor to performance; I'll reset it back to "interactive" with init in the late boot")
I watched the stock boot (MJ7) carefully, and realized that I couldn't conclude anything from USB behavior, as the MJ7 stock boot doesn't do anything with USB until well after init() has started running. I guess that the "jail" the bootloader creates for the kernel is probably a dummy ramdisk, perhaps including a very thin "init" program. That would explain why USB activity is seen with CM13 in this case, but not with the stock kernel. In the stock ROM that happens late in the boot after init has begun running, whereas the CM13 kernel fiddles with the USB interface before init is started.
Based on the evidence we have, I think this suggests that even with 100% stock retail devices & locked bootloaders, the same thing is going on - it's just not easily noticed because there is no on-screen activity other than that battery charge animation.. (It could be detected perhaps with an EMI sniffer or something)
So anyway - are the missing animations the fault of the kernel? Yeah, looks that way. Is it possible that the charging rate you get when the device is supposed to be "off" depends on the boot image kernel? Yeah, sure looks that way.
cheers

Amazing. Thank you for your investigation work detective. lol At least now we know it has nothing to do with signed or unsigned but more rather what kernel you have. Thanks for all your help man. If you ever need help with mimicking an issue you have shoot me a pm and I'll be more than happy to use my device to troubleshoot the same issue.

bftb0 said:
@Zzim @VJmac15 @Captain Skeet
I have some unambiguous clarifying information now about the "battery charge animation" when the phone is supposedly in an "off" state but plugged to a charger. Read on.
I took a stock (MJ7) boot image and unpacked it, and then simply repacked it, and flashed it to the boot partition in my (MJ7-firmware) SM-N900V.
Because there are very slight differences in "cpio" and libgz from linux release to release, this has the effect of making very tiny differences in the re-packed ramdisk image - enough that the Samsung signature is now broken, but likely nothing different at all from a functional perspective with the stock kernel or ramdisk (The kernel itself and it's device tree are bit-for-bit identical).
So what do it observe when I turn the device "off" and then plug to a dumb charger? The exact same stock "battery charge animation" that you would see on a retail device with a locked bootloader - plus one additional detail: that "Warranty bit set: kernel" message on the screen. After the battery animation runs for a while, the screen goes dark and the LED lights up according to charging state (red=charging, blue=charged, etc).
So the implication here is quite clear: the "off state" charging behavior you get depends on the kernel you have installed, and there is no difference in animations between signed and unsigned versions of the same stock kernel+ramdisk. An unlocked bootloader gives the same animations and LED illuminations as pure stock - so long as you are using a stock kernel.
Before I thought this was the bootloader running the (battery animation) show; but now I am beginning to believe that the bootloader fires up the kernel in some sort of jail when you plug power to the device. So if you are using a kernel that defaults to using a lot of power in it's idle state, (especially if it uses "init" to tweak into place battery savings) it's not going to charge as well as a less hungry kernel does - even when the device is supposed to be "off". It's even possible that the kernel could use more power when in this curious "off " state than when the ROM was running! (For instance, if the kernel developer decided "I'm gonna make this thing boot fast by setting the governor to performance; I'll reset it back to "interactive" with init in the late boot")
I watched the stock boot (MJ7) carefully, and realized that I couldn't conclude anything from USB behavior, as the MJ7 stock boot doesn't do anything with USB until well after init() has started running. I guess that the "jail" the bootloader creates for the kernel is probably a dummy ramdisk, perhaps including a very thin "init" program. That would explain why USB activity is seen with CM13 in this case, but not with the stock kernel. In the stock ROM that happens late in the boot after init has begun running, whereas the CM13 kernel fiddles with the USB interface before init is started.
Based on the evidence we have, I think this suggests that even with 100% stock retail devices & locked bootloaders, the same thing is going on - it's just not easily noticed because there is no on-screen activity other than that battery charge animation.. (It could be detected perhaps with an EMI sniffer or something)
So anyway - are the missing animations the fault of the kernel? Yeah, looks that way. Is it possible that the charging rate you get when the device is supposed to be "off" depends on the boot image kernel? Yeah, sure looks that way.
cheers
Click to expand...
Click to collapse
My gf reports that the Rom change is perfect for her, said she was on her phone all day and only lost about 7% feels like a new phone. Booting into download mode then restarting seemingly fixed the issue as suggested. Thank you for your replies!
---------- Post added at 02:47 PM ---------- Previous post was at 02:46 PM ----------
Captain Skeet said:
Amazing. Thank you for your investigation work detective. lol At least now we know it has nothing to do with signed or unsigned but more rather what kernel you have. Thanks for all your help man. If you ever need help with mimicking an issue you have shoot me a pm and I'll be more than happy to use my device to troubleshoot the same issue.
Click to expand...
Click to collapse
Yeah that 10.4 kernel must've wrecked phones!

Phone not charging, stuck at 1% after factory reset

Hi everyone,
My Axon 7 is not charging at all after I did a factory reset. The phone is almost 2 years old and battery was degrading a lot so I went and decided to do a factory reset. It was at 50% and charging fine before I hit reset, but once I reset and came to the setup screen, I noticed the battery showed 1% which was weird. I then unplugged the charger and it immediately died. Turning it on without charger will automatically turn off.
The phone does show the red led light and charging icon but no matter what it will stay at 1%.
Here's what I've tried so far:
-Change cable/charger
-Left overnight charging with phone on
-Left overnight charging with phone off
-Reset phone/wipe cache many times
I have always been on stock A2017U and wondering if flashing another ROM may help?
If anyone have tips on how I can revive my Axon 7 that would be appreciated. I really don't want to retire it yet.

Two years? Consider replacing the battery? The degradation on this thing is horrendous.

Hamburgle4 said:
Two years? Consider replacing the battery? The degradation on this thing is horrendous.
Click to expand...
Click to collapse
Uh no.Even with degraded battery,it should not stick to 1%.
---------- Post added at 01:07 PM ---------- Previous post was at 01:04 PM ----------
krazemonkey said:
Hi everyone,
My Axon 7 is not charging at all after I did a factory reset. The phone is almost 2 years old and battery was degrading a lot so I went and decided to do a factory reset. It was at 50% and charging fine before I hit reset, but once I reset and came to the setup screen, I noticed the battery showed 1% which was weird. I then unplugged the charger and it immediately died. Turning it on without charger will automatically turn off.
The phone does show the red led light and charging icon but no matter what it will stay at 1%.
Here's what I've tried so far:
-Change cable/charger
-Left overnight charging with phone on
-Left overnight charging with phone off
-Reset phone/wipe cache many times
I have always been on stock A2017U and wondering if flashing another ROM may help?
If anyone have tips on how I can revive my Axon 7 that would be appreciated. I really don't want to retire it yet.
Click to expand...
Click to collapse
If i were you,i should flash twrp,boot in twrp,wipe all partitions,boot in twrp.See battery now and flash custom ROM maybe

krazemonkey said:
Hi everyone,
My Axon 7 is not charging at all after I did a factory reset. The phone is almost 2 years old and battery was degrading a lot so I went and decided to do a factory reset. It was at 50% and charging fine before I hit reset, but once I reset and came to the setup screen, I noticed the battery showed 1% which was weird. I then unplugged the charger and it immediately died. Turning it on without charger will automatically turn off.
The phone does show the red led light and charging icon but no matter what it will stay at 1%.
Here's what I've tried so far:
-Change cable/charger
-Left overnight charging with phone on
-Left overnight charging with phone off
-Reset phone/wipe cache many times
I have always been on stock A2017U and wondering if flashing another ROM may help?
If anyone have tips on how I can revive my Axon 7 that would be appreciated. I really don't want to retire it yet.
Click to expand...
Click to collapse
if i were you, i'd ignore this predatorhaze guy...
Whatever you do, I'd say go for it, buy a new battery. It won't be for nothing.
But on the matter at hand: This comes down to charging mechanics. Your battery will charge with a set voltage (usually 4.4V) after the fastest stretch which is constant-current fast charge. If your phone stays on, you should check a couple of things to be sure that the phone is trying to charge at least.
First of all download Ampere, it'll show you the charge rate and battery voltage. You should leave it charging for a minute with the app open, and check how much current goes through. The battery voltage should be reported below as well. Then disconnect the charger, and see if you can see what the voltage says. If it is below 3.3 V then BCL (Software that controls some battery-related functions, one of which is this brown-out protection that turns the phone off after a certain voltage) will shut down the phone. Degraded batteries have certain physical properties that make them heat more and have serious voltage dips when a sizable current is demanded, something which Predatorhaze here doesn't seem to understand.
Now, you could try to disable BCL completely by simply adding root to the mix and running some commands that Infy_AsiX posted in the BCL degradation thread, this is obviously temporary if your battery is past the point of charging but it's possible. no need to switch ROMs although that might not be as bad.

This happens to me too, sometimes. Shockingly enough, once I charge it via USB cable from my laptop (I have an ASUS ROG G750JS, if that matters) , the charging picks up. Moment it crosses 36%, I can now charge it via the wall charger again; I'm careful now not to let my phone die down anymore.
I should change the battery, but I'm planning on selling this thing by February anyway and want to give the buyer a new battery altogether, by then.

Choose an username... said:
if i were you, i'd ignore this predatorhaze guy...
Whatever you do, I'd say go for it, buy a new battery. It won't be for nothing.
But on the matter at hand: This comes down to charging mechanics. Your battery will charge with a set voltage (usually 4.4V) after the fastest stretch which is constant-current fast charge. If your phone stays on, you should check a couple of things to be sure that the phone is trying to charge at least.
First of all download Ampere, it'll show you the charge rate and battery voltage. You should leave it charging for a minute with the app open, and check how much current goes through. The battery voltage should be reported below as well. Then disconnect the charger, and see if you can see what the voltage says. If it is below 3.3 V then BCL (Software that controls some battery-related functions, one of which is this brown-out protection that turns the phone off after a certain voltage) will shut down the phone. Degraded batteries have certain physical properties that make them heat more and have serious voltage dips when a sizable current is demanded, something which Predatorhaze here doesn't seem to understand.
Now, you could try to disable BCL completely by simply adding root to the mix and running some commands that Infy_AsiX posted in the BCL degradation thread, this is obviously temporary if your battery is past the point of charging but it's possible. no need to switch ROMs although that might not be as bad.
Click to expand...
Click to collapse
Here's readout from Ampere at 4.4v but the mA is very low. I couldn't get a proper readout after unplugging the phone as it dies immediately before it could measure.
Thanks for the post, will try to root and perform the BCL methods, if doesn't work ill try to flash LOS.
Just wanted to exhaust my options before replacing battery, seems tough to do and could be the motherboard or something else at fault.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
KwesiJnr said:
This happens to me too, sometimes. Shockingly enough, once I charge it via USB cable from my laptop (I have an ASUS ROG G750JS, if that matters) , the charging picks up. Moment it crosses 36%, I can now charge it via the wall charger again; I'm careful now not to let my phone die down anymore.
I should change the battery, but I'm planning on selling this thing by February anyway and want to give the buyer a new battery altogether, by then.
Click to expand...
Click to collapse
Unfortunately this doesn't work for me either, I left it for a whole day while at work charging through pc, same symptoms

krazemonkey said:
Here's readout from Ampere at 4.4v but the mA is very low. I couldn't get a proper readout after unplugging the phone as it dies immediately before it could measure.
Thanks for the post, will try to root and perform the BCL methods, if doesn't work ill try to flash LOS.
Just wanted to exhaust my options before replacing battery, seems tough to do and could be the motherboard or something else at fault.
Unfortunately this doesn't work for me either, I left it for a whole day while at work charging through pc, same symptoms
Click to expand...
Click to collapse
well, if anything, the battery swap is extremely easy on this phone
You don't even need to use heat on the grilles, just use something very sharp like a craft knife on the right corners of the grilles, pry upwards, then very carefully use a flat screwdriver or something like that. if you have the gold one, the grilles are very flexible, unlikely that you'll do any damage. If you have the gray model you'll need to be extremely careful with the top grille where you have the hole because it'll probably snap there.
Then take the screws off (6), open just slightly, take the fp cable sensor off carefully, take one more screw off, pry the battery, insert new one
You can watch JerryRigEverything's disassembly video to know every step of the process, it's useful for that

Finally I've managed to get the phone charging.
Flashed LOS but didn't remediate the issue, although TWRP does show 73%, phone dies after booting up.
So I attempted to go back to stock again. Voila this time turning on the phone, battery started to go up, unplugging holds.
However, issue remain is that charging now is significantly slower even though it is showing fast charging, and once it hits 75% it takes roughly an hour and a half to 2 hours to get to 100%.
I guess I will see how it goes for the next week or so and if battery performs poorly I will go ahead and buy a replacement battery.

Battery charging problem

Hi there,
I have a Leeco Le Pro 3 x720 running Lineage OS 17.1 (last version) . I was very happy with it but recently it is giving me a good headache due to the next battery charging problem.
This is a description on how the phone behaves depending on the situation:
* if the phone is powered off -> it just charges fine .
Once the phone is charging at this stage, if it boots while charging, it keeps charging until it is unplugged. This is perfectly right.
* But if the phone is already powered on, with no charging cable plugged, there are two behaviors depending on the charger:
** chargers that only can charge if they are plugged when the phone is powered off: if the phone boots connected to this kind of chargers, it charges and works as usual until they are unplugged. But they won't charge at all If they are plugged once the phone is on. I have no idea about what is happening in this case
** chargers that can charge anyway: if these chargers are plugged once the phone is on, the battery charging logo doesn't show the battery logo charging ray that means the phone is charging, but the phone is actually charging. The battery logo won't update the battery level shown, it will just stay at the last battery level, the battery level won't rise at all. In example, the battery level shown stays at 50%, and when the battery drops from that level, it goes down as usual, but it never shows a higher battery level, it is not going to show a 51% battery level. Only if the phone is rebooted, the battery level logo will show the right battery level. Looks like the phone is not detecting it is charging, although it is actually charging.
This behavior don't depend on the battery charger watts:
- I have some 10 Watts and 24 Watts battery chargers made by Amazon, Leeco, Samsung, that work in the first way described (they only work if they are plugged at boot time), and
- I have a 10 Watts battery charger made by Aukru that works the second way described, (it charges anyway).
I have tried wiping and reinstalling the Lineage ROM using TWRP but this didn't fix the problem.
At the beginning I thought it was a software issue but now I have no idea.
EDIT: I noticed that each time a system update was applied, the next time the phone boots, the charging worked without any problem. Charging whenever it was plugged to the battery charger. After that, the next time the system reboots it works in the way described above.
Questions:
- is this a software issue or a hardware issue?
- Could you explain what is happening?
- How could I fix it?
Thanks in advance.
Regards!

I have a quite similar situation.
Mi Le Pro 3 stopped charging, just charges when the battery completely drains and the phone turns off.
Once I turn the phone on it keeps charging but if it´s unplugged it stops charging until the battery is completely drained again.
I´ll reinstall LOS 17.1 again, if it doesn´t work I´ll try with 18.1.
I´ll let you know any update.

I've had the same/similiar problem it seems since I've had the phone almost. I got the phone in July of 2018, and within a week of getting it a dropped it in the toilet (feel free to laugh). Let it dry, and it's still worked ever since. I just don't know if that could cause issues down the road or not. I figured when it comes to water, it's either screwed, or not, but I don't know enuff about how that works. Anyways, I used the phone for a little less than a year and got another phone, and rarely used it since. Started using it again recently, and there's the usual problem with some cords or chargers not working for it. And then there's the phone either reading the battery information wrong, or it's getting fed the wrong information, regarding battery level as well as charge time left. Like, it's said 2% charging, 2 min left till full ha. Almost the phone likes to randomly shut off, but i'm thinking now that it's not randomly shutting off, but it's because the battery is actually dead even though it's reading say, 52%. And then sometimes when the phone shuts down and I'm charging it, when i hit the power button to see the charge level, I instead get a battery icon with a ? in the center of it!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what it shows now, which looks correct.

Ok, a bit more info now that i've been trying to watch for any patterns on this issue. So, if the phone is off and i put it on a charger, any charger that it recognizes and does so with an led light coming on, hitting the power button to check the charge level displays this fun little icon:
Annoyances aside, I find this (never seen it before) quite comical, just in the fact of me visualizing a conversation between me and my phone, and the phone gets an attitude and throws up a question mark symbol in response to any question i have for it lol...
But yeah, so not all chargers will charge the thing, even tho it acts like it's charging. Turning it on while on one of these chargers will make the phone shut back off during boot, no matter how long u leave it plugged in to charge. There's only a few chargers i have that will actually charge it.
Another thing I noticed is I have Battery Saver set to pop on at 30%, but i dont see any indication that it is on, and the buutton that says "TURN ON NOW" can never be clicked, no matter what.

GWARslave119 said:
I've had the same/similiar problem it seems since I've had the phone almost. I got the phone in July of 2018, and within a week of getting it a dropped it in the toilet (feel free to laugh). Let it dry, and it's still worked ever since. I just don't know if that could cause issues down the road or not. I figured when it comes to water, it's either screwed, or not, but I don't know enuff about how that works. Anyways, I used the phone for a little less than a year and got another phone, and rarely used it since. Started using it again recently, and there's the usual problem with some cords or chargers not working for it. And then there's the phone either reading the battery information wrong, or it's getting fed the wrong information, regarding battery level as well as charge time left. Like, it's said 2% charging, 2 min left till full ha. Almost the phone likes to randomly shut off, but i'm thinking now that it's not randomly shutting off, but it's because the battery is actually dead even though it's reading say, 52%. And then sometimes when the phone shuts down and I'm charging it, when i hit the power button to see the charge level, I instead get a battery icon with a ? in the center of it!
Click to expand...
Click to collapse
Lol that's weird. I've got my X722 since Feb 2018 and used it for all these years every single day (no signs of replacing it until it dies...probably), and in contrast I've taken quite some care with it: Never ever using the original charger and cable (just throw them away as these were the cause of many burnt ports back then) and using QC3 only when I actually need it (mainly because the phone gets pretty warm when charging this way, especially during summer, Lithium cells don't like extreme heat too much). It doesn't even have any noticeable scratches (a couple super small ones that are pretty hard to even notice).
I've gone through every single Android revision and currently in 10 (AICP) and experienced some of those issues a couple of times:
- The phone would, quite literally, randomly shutdown without any warnings (nothing to do with the battery, as it would turn on like normal after a hard reset). Maybe like 10 times since I've got it. Sometimes I just noticed it's actually turned off or it dies in my hands while doing anything. I've got no clue why this might happen, but it's so rare (like once every couple of months) that it doesn't bother me.
- The phone would not charge AT ALL when using some particular chargers (nothing to do with the cables as I've tested).
So far: Huawei and Samsung original chargers would only turn on the charging LED indicator for it to turn off like 2 seconds later (no charging whatsoever); and crap quality bootleg chargers (like those fake Samsung ones from Aliexpress) or those ****ty $1 chargers that you can buy everywhere would trigger charging but at unreasonably low speed (like 15mA charging current, basically not charging at all).
My Tronsmart 2 port charger (one with and one without QC3) coupled with the same 2 cables I've bought with it still works like a charm (been using it ever since I've got this phone). Only the port on the cable I use for normal (non QC3) charging is slightly loose (because that's the one I use the most) and the phone still holds quite a charge even though I charge it almost everyday (too much Youtube...).
Apart from this one, all the Xiaomi chargers I've tried also works fine (although none of the QC capable ones actually charge with QC3, I've only get this to work with my Tronsmart one). And the Nokia charger from my sister's phone also works fine.