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.
Related
I've read some similar threads about this problem. Most of them keep it inconclusive or ends with "replace the battery". Unless one damaged the battery itself, I find this rather strange.
In my, and most of the other cases, the phone will shutdown immediately: no warnings, no 'Shutting down...' message, nothing. Just like if the battery was plugged out from the phone. Then it reboots and can't get through the second boot screen: it shows the [Google] screen then shutdowns again. And starts to reboot again, endless loop until the battery is totally drained (which will take some hours). If I plug in the power cable it will boot the phone normally.
There are some confirmed actions that trigger the shutdown (always not plugged in the power):
- turn on WiFi (100% of the times)
- turn on Cellular Data
- sometimes when making a telephone call
- sometimes only by using the phone anywhere
When plugged to the power, the phone won't ever shutdowns like that.
Another symptom is the Cellular Network. Seems like every X seconds (around 10) the phone loses the signal, then 5 secs later it comes back - this is even with the power plugged in. I found it when people tried to call me, they said they try around 5x to call me, 4 first times the phone can`t be reached, suddenly it can. When the call is made I can talk for hours, the call never shuts down or anything.
Any clues on that? Anything I can test in here? It's really a faulty battery?
Just for info:
- 3yr old Nexus 4 using Chroma (Android 6.0.1), rooted. Battery worked 100% before the LCD replacement.
- I've already wiped Dalvik+Cache dozens of times, no difference.
- Wiped batterystats.bin, no change.
- At TWRP Recovery, sometimes the battery indicator also behaves in a weird way.
Some screenshots showing some bizarre behavior while 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 suggest flashing back to a complete stock LP ROM, use it for a while and see if the problem continues to occur. If it does, and since the phone is 3 years old (assuming you're using the original battery) this leads me to conclude that the battery is the likely culprit.
Hi there!
I know it's strange, but it's battery related I'm sure because I'v been there too.
I replaced my lcd first. Everything were fine for at least 2-3 days after that I've recongized some issue with my phone. For example the drained battery. Those symptoms were the same as you described in your post. (no connection, drops connection, sim missing, draining from full, etc)
One thing, i knew i fck'd my battery when I replaced the lcd and I had to remove the sticky-hardglued battery from my phone. I knew I've damaged the foil of the battery. Smell your battery! (if it has a phys problem you will know it by smelling it, damaged battery smells sweet-like)
Then I've ordered a battery as well and replaced it, but it has problems too. Phone didn't get charged and I was like crazy. The problem was with screws on the battery cable which is connected to the motherboard. I had to remove the screws from it and with some adhesive tape it just works fine now.
Good luck bro! :fingers-crossed:
-duplicate-
bceeN said:
Hi there!
I know it's strange, but it's battery related I'm sure because I'v been there too.
I replaced my lcd first. Everything were fine for at least 2-3 days after that I've recongized some issue with my phone. For example the drained battery. Those symptoms were the same as you described in your post. (no connection, drops connection, sim missing, draining from full, etc)
One thing, i knew i fck'd my battery when I replaced the lcd and I had to remove the sticky-hardglued battery from my phone. I knew I've damaged the foil of the battery. Smell your battery! (if it has a phys problem you will know it by smelling it, damaged battery smells sweet-like)
Then I've ordered a battery as well and replaced it, but it has problems too. Phone didn't get charged and I was like crazy. The problem was with screws on the battery cable which is connected to the motherboard. I had to remove the screws from it and with some adhesive tape it just works fine now.
Good luck bro! :fingers-crossed:
Click to expand...
Click to collapse
Ok, you've practically described what happened with me when replacing my LCD too. That dreadful glue on the battery... I'm pretty sure I f*ed it up too. I was only after some confirmation, THANK YOU very much for telling your story. I'll replace the batt in here (and post the after story too, sure).
Thanks again! :good:
Similar issue - Stock 5.1.1 rooted
wirapuru said:
I've read some similar threads about this problem. Most of them keep it inconclusive or ends with "replace the battery". Unless one damaged the battery itself, I find this rather strange.
In my, and most of the other cases, the phone will shutdown immediately: no warnings, no 'Shutting down...' message, nothing. Just like if the battery was plugged out from the phone. Then it reboots and can't get through the second boot screen: it shows the [Google] screen then shutdowns again. And starts to reboot again, endless loop until the battery is totally drained (which will take some hours). If I plug in the power cable it will boot the phone normally.
There are some confirmed actions that trigger the shutdown (always not plugged in the power):
- turn on WiFi (100% of the times)
- turn on Cellular Data
- sometimes when making a telephone call
- sometimes only by using the phone anywhere
When plugged to the power, the phone won't ever shutdowns like that.
Another symptom is the Cellular Network. Seems like every X seconds (around 10) the phone loses the signal, then 5 secs later it comes back - this is even with the power plugged in. I found it when people tried to call me, they said they try around 5x to call me, 4 first times the phone can`t be reached, suddenly it can. When the call is made I can talk for hours, the call never shuts down or anything.
Any clues on that? Anything I can test in here? It's really a faulty battery?
Just for info:
- 3yr old Nexus 4 using Chroma (Android 6.0.1), rooted. Battery worked 100% before the LCD replacement.
- I've already wiped Dalvik+Cache dozens of times, no difference.
- Wiped batterystats.bin, no change.
- At TWRP Recovery, sometimes the battery indicator also behaves in a weird way.
Some screenshots showing some bizarre behavior while charging:
Click to expand...
Click to collapse
I have a similar issue:
1. Sudden battery drain, no particular pattern
2. Frequent Signal Loss (WiFi as well as Cellular) [My network provider usually displays a msg when I switch from Data to Wifi or Switch off Data, and I get around 1 such message every 2 minutes, even when I am connected to WiFi]
3. Excessive heating (No fixed pattern)
4. Yellowish marks towards bottom left on screen when Phone heats up
Skoche said:
I have a similar issue:
1. Sudden battery drain, no particular pattern
2. Frequent Signal Loss (WiFi as well as Cellular) [My network provider usually displays a msg when I switch from Data to Wifi or Switch off Data, and I get around 1 such message every 2 minutes, even when I am connected to WiFi]
3. Excessive heating (No fixed pattern)
4. Yellowish marks towards bottom left on screen when Phone heats up
Click to expand...
Click to collapse
Hi, first of all sorry - I said I would post some feedback here after the battery replacement and never did. Ended up being completely solved by the replacement indeed. In my case, like I said before, must have been while replacing the LCD and then I damaged the battery somehow. If I was you I'd save some headache and go for a new battery, I tried to find answers for this everywhere (at the time I was really short on $) before finally accepting it. Today my phone works normally again.
(Note: about 4. Yellowish marks towards bottom left on screen when Phone heats up I really never heard/read about it.)
The problem:
When my S8 is turned off and plugged in (yes, stock charger), the device won't charge. The charging icon show on the screen nor will the LED indicator light up. However, the device will still charge while it's ON (with the same charger).
This matter hasn't really been pressing because I rarely run out of battery. However, the few times I drain the battery completely, it's been extremely hard to turn the device on again. I'll have to trickle charge it and then turn the device on, hope the device doesn't die while turning on, and only then will the S8 start charging normally.
A ton more details:
Sometimes, I'll see a charging warning that there is water in the port. I think that this entire problem has arisen from the device thinking that there is water in the port, but I don't see why it would refuse to charge only when the device is turned off. My device has not been in water for 3-4 months.
This problem has been ongoing for 3-4 months
If turned off, the device will still charge WIRELESSLY
When I plug in the charger while the device is off, there's a small horizontal line on the screen that will light up every few seconds. I'm assuming that this is a boot loop due to charge failure.
I've been "trickle charging" the device by holding the power down and volume down button to start the bootloader. I'm unsure if this is a permanent solution, though, and it is not quite consistent.
Thanks in advance.
bump
bump 2
I have the same problem buddy.
I don't know how to fix that.
did you manage to fix it ?
p.s : I just bought this phone.
Sounds defective, I'd contact Samsung about a warranty repair.
Have the exact same issue. It will wireless charge when off, though.
Won't fast charge when on.
All the problems started when all of a sudden I got the old "moisture" in USB warning.
Got rid of that and downhill from there.
This started around 21 January, but the not charging when off, and slow charging seemed to have come on at a later stage.
Not impressed as I tend to baby my phones.
I have the same issue.
If i quickly press the power button while it's turned off and immediatly plug the charger, the phone shows the moisture warning and starts to vibrate.
The phone has never been exposed to moisture. I already tried to clean the usb and jack ports, and i also cleaned the usb app without success.
Any idea before a factory reset or rma?
I had exactly the same problem as Spike96.It seems it's a software problem from Samsung.I tried everything on the net to fix it,including talking to Samsung,nothing worked.I then systematically went through the entire usb programs and settings-FINALLY I found the problem,the USB audio routing when turned on,,causes the USB failure,go to developer options,disable USB audio routing,and your phone will charge as it should when powered off
12 hours later problem returned
U have to turn off " Varify apps via USB" in developers option, as well.
I had the same problem and just fixed it by clicking every option and found the luck.
Came here because I also have this problem now. Which unfortunately happened to start the DAY AFTER I pre-ordered the S10+ with my S8 included as part exchange.
If the phone is off, it says theres moisture in the port and wont charge. If I hold volume down and power, it resets and turns on like normal and charges like normal. Phone has been exposed to water in the past but not in the last few days. Strange that it says there's moisture when the phone is off.
Same issue over here. No quick charge and it won't charge when my phone is off. It also won't turn on with the charging cable is connected, I have to disconnect it before I'm able to turn on my phone.
Tried fully cleaning all my phone ports with a wooden toothpick and some alcohol, but without luck. (Had a charging issue before, with another phone, and this is what fixed it)
After reading this tread I changed the developer options, but I still have the problem.
I also recorded a bug report, but I got a really big file out of it and I can't find anything regarding the phone charging.
Are there any other suggestions for things I can try without having to factory reset my phone?
Any suggestion is welcome.
I've noticed that sometimes after i unplug the phone from the charger (obv i can charge only if it's on) the warning appears.
Do you think that a custom rom would solve the problem?
MrRanza said:
I've noticed that sometimes after i unplug the phone from the charger (obv i can charge only if it's on) the warning appears.
Do you think that a custom rom would solve the problem?
Click to expand...
Click to collapse
No. I have lineageos 16, but the problem is present.
Superweird problem. I always had this problem, when the phone was fully off it would not charge unless I powered it on first.
Disabling "USB audio routing" PLUS disabling "Verify apps via USB" in developer options like suggested fixed this for me!
I've got the same issue, and I have been dealing with this for over 2 years now. I initially thought my phone was gone for good because it wouldn't turn on at all, flash me a working screen, or vibrate like it usually does. So, I just kept it hidden in my cabinet for almost a year.
When I remembered I had this S8+ device, I decided to take one more look at it and it finally turned on!.. Well, the charging icon before actually being turned on did, at least. However, like @Spike96, @MrRanza, @AC5L4T3R, and @IkBenNietHier mentioned, the off charging screen showed a water-in-port warning below the charging icon and would vibrate non-stop — and not charge too, of course. Here's a picture of what the screen looks like on the device:
{
"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 later then found that either hard resetting the device or using a wireless charger would pretty much fix the issue, but again, like @Spike96 presumed, it isn't a permanent solution and isn't very consistent, because I've noticed that the longer I leave my S8+ uncharged and dead, the harder it is to get it starting again. I'm quite relieved, though, that a lot of other people are experiencing this predicament, as well, because I know I'm not alone with having this annoying issue anymore.
A couple of people in this thread suggested going to Developer Options > Debugging: disable Verify apps via USB + Media: Prevent USB audio routing, but my Verify apps via USB was always disabled (by default, unless I turn Debugging: USB debugging on), and doing the given steps did nothing for me. I appreciate the help a lot, though, but I'm still stuck with the same problem...
Actually, it's worse now — for some reason, after turning my phone off to see if it'll charge, it now won't react to any of the button combinations except for Odin mode (volume down + power key + Bixby key). I'll just try again some other time — this happens a lot, anyway...
I faced exactly similar issue with s9+ around a year back .... I tried cleaning the port etc and flashing custom rom ... Nothinh fixed the issue .... Wireless charging worked fine .... Finally i got the usb port changed and it fixed this issue ...
Hi all,
I'm sure a lot of you are in the same boat as me. We all love our Nexus 7s and aren't willing to let go.
However, after trying dozens of ROMS and Kernels, repartitioning the system etc to get the latest Android version, I have come to a conclusion that we need to stop force feeding this humble tablet with the latest versions and rather have a snappy tablet than a mere showcase of experiments.
I'm currently running CM13 (Android 6.0.1) and my tablet is barely usable.
It's painfully slow, to the point that pressing the home button and going back to the home screen takes around 1.5 to 2 seconds.
From pressing the search bar to the keyboard appearing takes 3 seconds, and forget about typing delays and launching apps. Jumping from apps to apps via the recent apps button is extremely painful and most apps are killed in the process.
I have tried many different ROMs and solutions posted here and there but no improvement.
I also tried to go back to stock but somehow even the stock had horrible performance, which I'm guessing is because of the repartitioning I had done much earlier for flashing newer ROMs.
I'd love to use my tablet regularly even if it is on an older version. Please help me get back to a normal and snappy ROM, such as stock, but without such lags. I'm not willing to let go of my N7 just yet!
Did you try AOSP based ROMs ? I had similar issues before. CM/Lineage OS based ROMs seemed laggy and slow. Then I installed pure AOSP 7.1.2 by nbhary (later moved to followmsi build). Now I'm in Unlegacy 8.1.0 and I can't say my Flo runs slow or lags (small ones happend from time to time)
I personally find the tablet works best as is. Whenever I even try to tweak the kernel it performs miserably.
When I swapped tablets in my car I played with them for awhile. The N7 is much better that the mediatek taets that have flooded the market.
---------- Post added at 04:59 PM ---------- Previous post was at 04:58 PM ----------
I personally find the tablet works best as is. Whenever I even try to tweak the kernel it performs miserably.
When I swapped tablets in my car I played with them for awhile. The N7 is much better that the mediatek taets that have flooded the market.
Have you tried a battery replacement? I recently replaced the battery in my Nexus 6p and saw a significant performance boost. According to AccuBattery, my Nexus 7 is at 75% health so I'm planning a replacement soon.
Currently running LOS15.1 with ElementalX with No Battery Mod on a car set-up, runs amazingly well.
I have OC the CPU to 1.9 and GPU to 489, but as other mention, check your battery health and if you have root , download "Trimmer" and check all 3 and start the trimming process. That also help by a lot.
DrakenFX said:
Currently running LOS15.1 with ElementalX with No Battery Mod on a car set-up, runs amazingly well.
I have OC the CPU to 1.9 and GPU to 489, but as other mention, check your battery health and if you have root , download "Trimmer" and check all 3 and start the trimming process. That also help by a lot.
Click to expand...
Click to collapse
Quick question
So the LOS updated kernel has the otg and everything need for the car install?
omariscal1019 said:
Quick question
So the LOS updated kernel has the otg and everything need for the car install?
Click to expand...
Click to collapse
It does (OTG + Charging) , including fast charging if you decide to keep the battery.
But in my case I have them Disable cuz I don't use them cuz the nobattery mod.
junooni said:
Hi all,
I'm sure a lot of you are in the same boat as me. We all love our Nexus 7s and aren't willing to let go.
However, after trying dozens of ROMS and Kernels, repartitioning the system etc to get the latest Android version, I have come to a conclusion that we need to stop force feeding this humble tablet with the latest versions and rather have a snappy tablet than a mere showcase of experiments.
I'm currently running CM13 (Android 6.0.1) and my tablet is barely usable.
It's painfully slow, to the point that pressing the home button and going back to the home screen takes around 1.5 to 2 seconds.
From pressing the search bar to the keyboard appearing takes 3 seconds, and forget about typing delays and launching apps. Jumping from apps to apps via the recent apps button is extremely painful and most apps are killed in the process.
I have tried many different ROMs and solutions posted here and there but no improvement.
I also tried to go back to stock but somehow even the stock had horrible performance, which I'm guessing is because of the repartitioning I had done much earlier for flashing newer ROMs.
I'd love to use my tablet regularly even if it is on an older version. Please help me get back to a normal and snappy ROM, such as stock, but without such lags. I'm not willing to let go of my N7 just yet!
Click to expand...
Click to collapse
Stop using Android. Use Sailfish OS. It has alien dalvik support so you can still use android 4.4 supported apps. Only issue is headphone jack is broken but besides that it is golden
https://forum.xda-developers.com/nexus-7-2013/development/sailfish-os-t3605791
Use this rootfs instead though: http://images.devaamo.fi/sfe/deb/sf...2/sailfishos-flo-release-2.1.1.26-STABLE2.zip -> 2.1.3.7 seems to have broken bluetooth audio rerouting, but everything in this image works! (besides headphone jack of course)
Thanks guys for this post, I was just wondering if I could also update my N7(2013). So if you could tell me where the tried and true stuff is . I'm a 50 yr new to rooting, just fixed my 6P currently on Nougat BLOD and plan to update it to Oreo.
Unlegacy is great! It is what stock 8.1 would have been. If you're looking to update this great hardware to a modern version of Android with current security patches, I highly recommend Unlegacy.
1. Try this kernel:
https://elementalx.org/devices/nexus-7-2013/
2. ROOT needed and a terminal app like 'material terminal':
run the following commands:
su
fstrim -v /data
(repeat command until '0 bytes trimmed')
fstrim -v /cache
(repeat command until '0 bytes trimmed')
fstrim -v /system
(repeat command until '0 bytes trimmed')
exit
(= for exit su)
exit
(= for closing terminal session)
close app and reboot
junooni said:
I'm currently running CM13 (Android 6.0.1) and my tablet is barely usable.
It's painfully slow, to the point that pressing the home button and going back to the home screen takes around 1.5 to 2 seconds.
From pressing the search bar to the keyboard appearing takes 3 seconds, and forget about typing delays and launching apps. Jumping from apps to apps via the recent apps button is extremely painful and most apps are killed in the process.
Click to expand...
Click to collapse
I am on latest LineageOS (with that dreadfull "1 april joke"). My Nexus 7 2013 works almost like new. I never had slowness near the point you describe. Are you sure you don't have a hardware issue (flash related perhaps)?
varunprime said:
Have you tried a battery replacement? I recently replaced the battery in my Nexus 6p and saw a significant performance boost. According to AccuBattery, my Nexus 7 is at 75% health so I'm planning a replacement soon.
Click to expand...
Click to collapse
Do you know a place that replaces them? Mines running pretty good as I did a reset and now limiting the amount of apps. But it needs a battery, as does an ipod classic that I have.
Sent from my SM-G955U using Tapatalk
Try this, it can help you.
https://play.google.com/store/apps/details?id=com.paget96.lspeed&hl=en
DrakenFX said:
Currently running LOS15.1 with ElementalX with No Battery Mod on a car set-up, runs amazingly well.
I have OC the CPU to 1.9 and GPU to 489, but as other mention, check your battery health and if you have root , download "Trimmer" and check all 3 and start the trimming process. That also help by a lot.
Click to expand...
Click to collapse
Which lineage LOS15.1 build are you using? I have a car setup build as well and am looking around for a good oreo rom... :fingers-crossed:
For anyone who wants to speed up the Nexus 7 in the car, I recommend this modification
https://forum.xda-developers.com/nexus-7-2013/general/guide-improve-nexus-7-2013-cooling-t3095895
I used only thermal pads - GELID GP-Extreme 12 W/mK (without thermal paste & pieces of metal), I also removed the copper foil (because with excess of heat she began to peel off), cleaned the metal surface and glued the heat sink
{
"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"
}
Now I can overclock the processor without the risk of throttling
Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
tinOFbeer said:
For anyone who wants to speed up the Nexus 7 in the car, I recommend this modification
https://forum.xda-developers.com/nexus-7-2013/general/guide-improve-nexus-7-2013-cooling-t3095895
I used only thermal pads - GELID GP-Extreme 12 W/mK (without thermal paste & pieces of metal), I also removed the copper foil (because with excess of heat she began to peel off), cleaned the metal surface and glued the heat sink
Now I can overclock the processor without the risk of throttling
Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
Click to expand...
Click to collapse
What are you using to power your no battery mod? I bought a Drok dc-dc 5A box of tricks. Hooked it all up. Left it running as a test for an hour (running Timurs kernel with power hooked up to the USB port via otg cable). All was good, decided to shut down, tweak voltage up (was at 3.9 and reporting 70% battery charge), but tablet refused to reboot. Instead the Drok CC light comes on. Plugged battery back up to Nexus 7, dead. Nothing. Have the battery 5 minutes of external kick start charge and tablet screen showed battery empty icon. Left on charge over night but tablet is totally dead this morning. Recon the charging circuit has somehow become fried
steuk said:
What are you using to power your no battery mod? I bought a Drok dc-dc 5A box of tricks. Hooked it all up. Left it running as a test for an hour (running Timurs kernel with power hooked up to the USB port via otg cable). All was good, decided to shut down, tweak voltage up (was at 3.9 and reporting 70% battery charge), but tablet refused to reboot. Instead the Drok CC light comes on. Plugged battery back up to Nexus 7, dead. Nothing. Have the battery 5 minutes of external kick start charge and tablet screen showed battery empty icon. Left on charge over night but tablet is totally dead this morning. Recon the charging circuit has somehow become fried
Click to expand...
Click to collapse
DC/DC XL4015 Step-Down 5A (set to 5.07v)
this module powers all my systems - the navigation opening and closing system, the active USB hub and the tablet. I inserted a 1N5401 rectifier diode into the tablet supply line (battery PCB) - about 4.3 is delivered to the battery PCB.
I did not buy an OTG cable, I made it myself - without a 100k resistor, I directly connected the 4 and 5 pins in the connector.
Battery mod: https://youtu.be/9N2Bh4fI8Bo
Edit: improved value of the tablet's power supply
Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
Figuring I have nothing to lose, I took out the battery and hooked back up the direct feed. It’s working again. Random! I noticed the fatter ribbon cable has two damaged ‘pins’. I removed the drift and flattened out what is left. So maybe that was the problem.
Interesting to see you feed such a high voltage to the tablet PCB. If I feed 3.8v I get 56% battery reported. If I feed 4.3 I get 100%. Guess it just has to be higher depending on the dc-dc unit used?
Apologies if I have missed you saying, but what kernel do you use? Does it have ‘usb power through your otg cable’ to ‘bring the tablet to full life/go into power save mode’ ? If so, where do you have diodes to restrict current back flow? I have seen talk of putting it on the 12v feed to the dc-dc, but surely it needs to go after the dc-dc on the ~3.8v line that feeds the tablet PCB? And also one on the usb connection side somewhere?
Last question, promise! Does your no battery mod have the extra negative wire from the feed plate to one of the black wires that connect to the plug (that clips onto the tablet PCB - as in the video) ? I did the mod without it first, and the tablet booted just fine testing on a 12v 5A power supply in the house. But refused to boot when hooked up to a 12v battery. So put the wire in and I’d worked.
steuk said:
Figuring I have nothing to lose, I took out the battery and hooked back up the direct feed. It’s working again. Random! I noticed the fatter ribbon cable has two damaged ‘pins’. I removed the drift and flattened out what is left. So maybe that was the problem.
Interesting to see you feed such a high voltage to the tablet PCB. If I feed 3.8v I get 56% battery reported. If I feed 4.3 I get 100%. Guess it just has to be higher depending on the dc-dc unit used?
Apologies if I have missed you saying, but what kernel do you use? Does it have ‘usb power through your otg cable’ to ‘bring the tablet to full life/go into power save mode’ ? If so, where do you have diodes to restrict current back flow? I have seen talk of putting it on the 12v feed to the dc-dc, but surely it needs to go after the dc-dc on the ~3.8v line that feeds the tablet PCB? And also one on the usb connection side somewhere?
Last question, promise! Does your no battery mod have the extra negative wire from the feed plate to one of the black wires that connect to the plug (that clips onto the tablet PCB - as in the video) ? I did the mod without it first, and the tablet booted just fine testing on a 12v 5A power supply in the house. But refused to boot when hooked up to a 12v battery. So put the wire in and I’d worked.
Click to expand...
Click to collapse
I'm sorry, my mistake. The voltage is 4.3V, the voltage drop in the diode is 0.7V.
Yes, I have extra negative wire.
Kernel: Timur
Set the voltage to 4.3V, you must also set a higher current. You see CC light because the value is too low.
Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
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.
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.