Related
When I upgrade to ICS, my tablet exhibited all issues everyone was complaining about.
1) Battery drain. - the culprit of this issue is GPS. The GPS was preventing tablet from going into deep sleep. I have disabled GPS but kept Google location service enabled and that fixed the deep sleep issue. Also there were some incomparable software which prevented deep sleep. XDA app was one of them.
2) Random reboots, shutdowns, and lag. - the culprit of these issues is software incompatible. All you have to do is perform full wipe and cold boot using recovery by pressing and holding power and volume down buttons. After reset, all issues are gone.
To troubleshoot use next tools.
1) CPUSpy - it will show of tablet goes into deep sleep.
2)Battery settings in the rom's system setting is helpful to see if the phone sleeps but will not show if it deep sleep.
3) BetterBatteryStates is very useful to see which process keeps tablet awake.
Sent from my SGH-T959 using XDA
If it were that easy Asus wouldn't be working on a fix to push out to us. They have already confirmed there are issues.
My tablet didn't exhibit any of the reboot issues up until a few days ago. Which means even though your "solution " has seemed to help so far it could end up happening again later on
Sent from my Transformer TF101 using xda premium
I have been running for 1d and 20 hours using tablet and still have 60% left. No reboots no lag runs smooth. Also there is an issue with GPS which keeps tablet from going into deep sleep and that is what Asus is working on. If you disable GPS and remove xda app that will solve your battery issue. Also xda might have fixed their app since then. Full wipe will fix other issues.
Sent from my SGH-T959 using XDA
I understand and believe you. I'm saying that the amount of time you have without any issues is not long enough to be 100% certain all issues are gone.
That is why I stated that's I had NONE of the issues for a couple weeks then out of nowhere they started.
Tho I hope your solution works in the long run and helps others as well
Sent from my Transformer TF101 using xda premium
I am just sharing my findings. I think GPS is the biggest contributed. Just disable it and see how the tablet runs.
Sent from my SGH-T959 using XDA
If a full wipe was the solution, then you will not find so many threads about the reboot or other issues.
it is just pure luck, some did all the steps of full wipe, full reset, go to stock HC then stock ICS, in all ways some keep getting issues and some do not have any.....
and as it has been already mentioned above, the issues have been confirmed by asus and they are already working on a solution.
mveksler said:
When I upgrade to ICS, my tablet exhibited all issues everyone was complaining about.
1) Battery drain. - the culprit of this issue is GPS. The GPS was preventing tablet from going into deep sleep. I have disabled GPS but kept Google location service enabled and that fixed the deep sleep issue. Also there were some incomparable software which prevented deep sleep. XDA app was one of them.
2) Random reboots, shutdowns, and lag. - the culprit of these issues is software incompatible. All you have to do is perform full wipe and cold boot using recovery by pressing and holding power and volume down buttons. After reset, all issues are gone.
To troubleshoot use next tools.
1) CPUSpy - it will show of tablet goes into deep sleep.
2)Battery settings in the rom's system setting is helpful to see if the phone sleeps but will not show if it deep sleep.
3) BetterBatteryStates is very useful to see which process keeps tablet awake.
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
My experience: I've done a full wipe, installed few apps from scratch (no restore), disabled GPS and installed autoairplane app. Everything seemed ok, two days and one night in deep sleep with 8% of battery drain per day. The following morning the tablet was switched off with 0% of battery
Great that you have resolved the issues for your TF101 and thanks for sharing the steps you took you to get that far.
It's only a limited set of devices though (1) and a limited amount of time.
I still believe most TF101 ICS issues are related to drivers. Just like it was initially with the first Asus HC release. Updates will improve stability.
the culprit of these issues is software incompatible.
Click to expand...
Click to collapse
I agree, this is just a poor choice of words..and with the title of the thread, you are really just ginning up controversy here now as a thread of this nature has already been closed because of someone insisting that a full wipe solves reboot issues..I would have phrased it more scientifically correct by saying 'the culprit seemed to be software incompatibility', you could even throw in the obligatory 'to me' lol. When you state things with such certainty in a development and electronics forum where terminology and phrasing is very important you are misleading people (noobs and lurkers) who are then going to complain and whine about being misled (and possibly mess up their device in some cases). Safer to state your 'findings' in less certain terms IMO.
And as I already pointed out in another thread, in order to say anything equivocally about a solution to a common problem like random reboots you need to have tested and confirmed the proposed solution on tens and hundreds of units, which very few of us have access to to test with any clarity of results. So anyone *should* take users' proposed solutions with a grain of salt barring they are employed with Asus or Best Buy and could have done such testing. Other users have proposed build.prop fixes for example, only to realize they had reboots and didn't even notice. 1 day is not long n this timeframe- I have one once a week tops..but I still have them..lol
The only problem i had was the apps disappearing from the launcher whenever i exited an app. I thought i solved this by installing a new launcher. But it returned after a few days. I did a full wipe and installed apps from scratch. since then my tablet has been running smooth and fast. no issues. May be it's the apps we install that are causing the problems.
Sent from my Transformer TF101 using Tapatalk
I think it is the graphics acceleration driver. Many games are not working to me, they just exist to launcher and in logcat i can see SIGSERVs because of openGL ( this is from memory, I don't have my tablet here right now).
We must wait until ASUS releases a fix.
I'll come in with another just wait and see like other folks have said. I did my ICS update with a full wipe and then only installed apps I felt comfortable with instead of just doing a full reinstall of everything. For days life seemed grand with everything working just right. Then I got a few reboots and now the constant media converter dying message. So be happy things are working well for you but be prepared for the errors to creep in.
Sent from my HTC Flyer P512 using Xparent Purple Tapatalk
I suffered from random reboots. Whenever my device went to deep sleep it could not come out of it. What I did to remedy this is to root and install set cpu. After installation, i changed my minimum freq to 312mhz and my max at 1ghz. So far, for about a week, i have not suffered any random reboots/freezes. Also, using cpu spy, it does go to deep sleep. I hope this helps.
mveksler said:
1) Battery drain. - the culprit of this issue is GPS. The GPS was preventing tablet from going into deep sleep. I have disabled GPS but kept Google location service enabled and that fixed the deep sleep issue. Also there were some incomparable software which prevented deep sleep. XDA app was one of them.
Click to expand...
Click to collapse
No idea if you're right, but I can't be bothered to try, because...
mveksler said:
2) Random reboots, shutdowns, and lag. - the culprit of these issues is software incompatible. All you have to do is perform full wipe and cold boot using recovery by pressing and holding power and volume down buttons. After reset, all issues are gone.
Click to expand...
Click to collapse
You are *definitely* wrong on this one. There are numerous documented accounts of people having this problem even on stock, unrooted TF101 tablets that have been wiped both before and after the ICS update was applied, and have nothing or next-to-nothing reinstalled. I'm one such person.
A full wipe most definitely does NOT fix or prevent these problems.
knoxploration said:
A full wipe most definitely does NOT fix or prevent these problems.
Click to expand...
Click to collapse
It did for the OP and a vast number of other users. Doesn't work for everyone but it is a viable solution.
I originally suffered from horrible battery life after updating to ICS, but I took a page from the book of the Gnex when it comes to sudden horrible battery life. One of the biggest problems on the GNex with sudden battery drain a lot of the times had to do with Google Maps. I used CPU Spy and Better Battery Stats and sure enough, Google Maps was constantly running in the background, putting the tablet into a wakelock and most likely running the GPS. The tablet wouldn't even last half the day WITH the dock. Went to apps, uninstalled updates and reinstalled the most recent version and since then the battery life has been PHENOMENAL! I've got the tablet with dock and it'll go most of the week, if not all week before the dock starts running low.
Hope this helps others. Can't guarantee it'll fix your problems but it fixed mine.
Speaker Issues after ICS update
Has anyone else had any speaker issues after the ICS update?
Jai1985 said:
Has anyone else had any speaker issues after the ICS update?
Click to expand...
Click to collapse
My volume is low, also been experienced by others. And it seems like left speaker is lower in volume, which I also read issues with. So yea. I have a couple little quirks. Good thing is I don't really use it for music or movies so not huge deal to me
Sent from my SGH-T959 using xda premium
ghost0001 said:
I suffered from random reboots. Whenever my device went to deep sleep it could not come out of it. What I did to remedy this is to root and install set cpu. After installation, i changed my minimum freq to 312mhz and my max at 1ghz. So far, for about a week, i have not suffered any random reboots/freezes. Also, using cpu spy, it does go to deep sleep. I hope this helps.
Click to expand...
Click to collapse
This has been my fix from the start and have only had one self-inflicted random reboot and (Horndroid here is a nod for you) another reboot after I updated Google+. I reverted back to previous G+ build and all is back that way it was before.
If you'd like to read more about the kernel issue and how I solved it for myself, see here.
I had a question regarding custom ROM's and shutting down/rebooting the tablet.
I've had two Android tablets in my life, and experience with about 5+ phone models. Both tablets were of easily modifiable types, one even getting a post-mortem Android 4.2 (as defined by manufacturing life mortality). Both, on stock ROM, the Acer Iconia a500 (RIP and may your new owner honor thy resilience) and the Nexus 10, would shut down or reboot instantaneously after pressing the button. You'd see "Shutting down" flash for a second at most.
On CM10.1, PA, AOKP, RootBox, RV, etc. when shut down or reboot is pressed, the device just... Sits there for 3-5 seconds (I've never timed it) before rebooting or turning off. I was curious as to why? Does anybody know? Its more of a "wanna know" than "I have an issue"
dibblebill said:
I had a question regarding custom ROM's and shutting down/rebooting the tablet.
I've had two Android tablets in my life, and experience with about 5+ phone models. Both tablets were of easily modifiable types, one even getting a post-mortem Android 4.2 (as defined by manufacturing life mortality). Both, on stock ROM, the Acer Iconia a500 (RIP and may your new owner honor thy resilience) and the Nexus 10, would shut down or reboot instantaneously after pressing the button. You'd see "Shutting down" flash for a second at most.
On CM10.1, PA, AOKP, RootBox, RV, etc. when shut down or reboot is pressed, the device just... Sits there for 3-5 seconds (I've never timed it) before rebooting or turning off. I was curious as to why? Does anybody know? Its more of a "wanna know" than "I have an issue"
Click to expand...
Click to collapse
how often do you charge do you let it go to like 10-14% before charging. Could be a battery calibration issue idk really I am just guessing here. Are you sure you are not holding it down.
shadowblade330 said:
how often do you charge do you let it go to like 10-14% before charging. Could be a battery calibration issue idk really I am just guessing here. Are you sure you are not holding it down.
Click to expand...
Click to collapse
Any time, any charge, any device. I am just curious, is all
Sent from my Nexus 10 using XDA Premium HD app
I jumped in and bought a K1 to replace my dying GPad GPE. After 3 days, this seems like a huge mistake.
The K1 is very laggy in basic apps like Play Store and Chrome, does not register touches very well and has terrible battery life. I even charged it overnight and didn't get a full charge. On top of that, I am constantly getting the screen overlay message any time I need to enable a permission.
What could be causing this? This tablet is so highly regarded I don't get it.
Sent from my SHIELD Tablet K1 using Tapatalk
For charging you need a 2 or 2,5 A charger. Then it will charge (if it's not faulty) in around 2 hours. The screen overlay message is coming from the quick launcher (or how it is called). So disable it or give it the right to draw over other apps.
I don't have problems with lags or touches. Are you on the latest updates?
PearlMikeJam said:
I jumped in and bought a K1 to replace my dying GPad GPE. After 3 days, this seems like a huge mistake.
The K1 is very laggy in basic apps like Play Store and Chrome, does not register touches very well and has terrible battery life. I even charged it overnight and didn't get a full charge. On top of that, I am constantly getting the screen overlay message any time I need to enable a permission.
What could be causing this? This tablet is so highly regarded I don't get it.
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
Its got a crappy Nvidia CPU in it, thats the issue. Like my N9, that too is crap, again, Nvidia inside.
edisso10018 said:
For charging you need a 2 or 2,5 A charger. Then it will charge (if it's not faulty) in around 2 hours. The screen overlay message is coming from the quick launcher (or how it is called). So disable it or give it the right to draw over other apps.
I don't have problems with lags or touches. Are you on the latest updates?
Click to expand...
Click to collapse
I am using the correct rated charger. This even happened when charging with the tablet off.
I am on the latest update. I waited to install my apps until after all updates were applied. The touch issues may be lag related. The back button almost always requires multiple touches. Keyboards often time register multiple touches or just freezes.
I am also noticing network issues. Apps report loss of connection when the wifi shows connected.
I hate to say it, but I am leaning towards returning this for a Samsung.
Sent from my SHIELD Tablet K1 using Tapatalk
PearlMikeJam said:
I jumped in and bought a K1 to replace my dying GPad GPE. After 3 days, this seems like a huge mistake.
The K1 is very laggy in basic apps like Play Store and Chrome, does not register touches very well and has terrible battery life. I even charged it overnight and didn't get a full charge. On top of that, I am constantly getting the screen overlay message any time I need to enable a permission.
What could be causing this? This tablet is so highly regarded I don't get it.
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
Also a recent owner of the k1. Running stock firmware (1.5) but with BitO-K kernel. The only thing I am experiencing is mediocre battery life, charges from 50-100% in under an hour using a 2.5A charger. The only thing that sucks, and this goes for android tablets in general, is the removal from 4.4 of the TabletUI. Seeing we're already at 7.1 and TabletUI is still dead, it looks like we'll have to fight to get it back again.
PearlMikeJam said:
I am using the correct rated charger. This even happened when charging with the tablet off.
I am on the latest update. I waited to install my apps until after all updates were applied. The touch issues may be lag related. The back button almost always requires multiple touches. Keyboards often time register multiple touches or just freezes.
I am also noticing network issues. Apps report loss of connection when the wifi shows connected.
I hate to say it, but I am leaning towards returning this for a Samsung.
Click to expand...
Click to collapse
That lag is not normal. And my tablet charges from around 10% to full in about 2 hours. Maybe you should try a factory reset. If that doesn't help I would return it.
I won't buy a Samsung tablet. I would try a replacement. I own the k1 for a year now and I'm still very satisfied with. And Nvidia updates it. Which Samsung usually doesn't.
Don't listen to Nvidia trolls... ⬆
Your experience does not sound typical. Perhaps it's a hardware issue, but I agree with @edisso10018 that the first step would be a factory reset.
Wish you luck!
The Nvidia CPU is pretty good shame it's not the X1, It performs better then some of my phones with QC chips, Do a factory reset and see if the lag is still there, Battery life is poor can agree on that
My k1 is over a year old it is still playing games with no trouble yes a agree with the battery life but mine charges with no problems a have noticed a little slow down but am not running bit os updated kernel yet but a still rate 10/10 best tablet a ever owned.
Tablet is laggy, no denying it.
Sent from my Pixel XL using Tapatalk
ctap001 said:
Also a recent owner of the k1. Running stock firmware (1.5) but with BitO-K kernel. The only thing I am experiencing is mediocre battery life, charges from 50-100% in under an hour using a 2.5A charger. The only thing that sucks, and this goes for android tablets in general, is the removal from 4.4 of the TabletUI. Seeing we're already at 7.1 and TabletUI is still dead, it looks like we'll have to fight to get it back again.
Click to expand...
Click to collapse
K1 here-- I don't run stock (DU 6.0.1), but I used BitOK for a while and realized its not very good. Switched back to stock kernel (from my ROM) and its more stable. You don't lose out on much anyway-- BitOK doesn't have features I want like voltage control. Examples of instability caued by BitOK: GPU was stuck at ~350mhz, would not ramp down fully to 72mhz. Also stock is smoother. You can still use adiutor to monitor and control a few things.
One more thing: be very careful when flashing blobs and other stuff in fastboot that it is for the K1 version and not OG shield! A lot of devs posting these things arent explicit as to which version. DTBs and Blobs are specific to the shield type-- one might work for the wrong tablet version, or it might brick it, or it might be unstable.
As for the Batery life I can tell you it does suck even on the best case scenario. There is no way around this as it is small and the large screen, as nice as it is, sucks a lot of juice. Lowering brightness helps somewhat but still I'll be lucky to get a couple hours of SOT out of it.
For the price its a great tablet, with a few small compromises, such as bat life, but thats the price you pay for great screen and sound at a cheap price. We are lucky to have at least a few devs still doing work with this device, and luckier still that nvidia is STILL supporting it with updates, even if slowly. They recently announced 7.1.1 will be forthcoming.
Mine was laggy too, I flashed stock firmware with my PC and now it's working perfectly.
Bought mine as a refurb and it works fine. I think you either have bad hardware, or a bad install. Try flashing stock and see if it improves.
Tbh my only complaint is with battery life, I switched to BitO to see if it got any better, the tablet is smoother with this kernel than stock but the battery is the same, I wish we had UV'ing, my favorite setting on any kernel, back on my N10 my battery could easily be improved 10-15% and the heat was reduced drastically, good binned ones could shave up to 200mV on some steps. K wish this was implemented
PearlMikeJam said:
I jumped in and bought a K1 to replace my dying GPad GPE. After 3 days, this seems like a huge mistake.
The K1 is very laggy in basic apps like Play Store and Chrome, does not register touches very well and has terrible battery life. I even charged it overnight and didn't get a full charge. On top of that, I am constantly getting the screen overlay message any time I need to enable a permission.
What could be causing this? This tablet is so highly regarded I don't get it.
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
I just bought a K1 (discount price 169€) and I don't have this problem at all. Even if I use only 1 core (settings performance) for basic app it's smooth smooth smooth.
And the battery life is huge !!
For gaming tho I switch back ofc the performance setting.
:good:
I bought a K1 three weeks ago to use as a display for my phantom 4 quadcopter. I am very impressed with its performance. I'm not experiencing any lag other than at startup. Once it's up and startup is finalized I dont have any problems. The battery life isn't great, I'll agree there but hopefully it gets better with Nougat.
Sent from my SM-G925P using XDA-Developers Legacy app
I bought a K1 last week to replace my aging Nexus 7, did a factory reset and still wasn't satisfied with it being laggy. Did my share of Google searching and finally stumbled upon a quick fix to try : disable Daydream. Since changing this one setting it has been very smooth since, no issue for lag or touch registrations.
Give it a try, might not help your charging but I did notice a much reduced battery drain while sleeping also.
My only other changes were to root, change the DPI to 240 and use the Google Now Launcher which compliments the display nicely.
I wasn't happy with it as well until I flashed cyanogenmod 13 and a custom kernel with overclock. Now it's a beast, battery is great, signal as well. And I also now have the option to OC the processor to 2.5 GHz before I play some more demanding games and then set it back to 2.2 or even lower if I won't need all the juice. Seriously, the stock marshmallow ROM sucks, I have only heard bad stuff about it. Also, the nougat update is about to come out so I'd give android N a chance, too.
About the battery life -- see which apps are using the most juice under settings/battery/. Some of them may be using more CPU cores, and have a higher frame rate than is needed. Go to settings/App optimisation/ and crank the numbers down. Next go to settings/Accounts and see the long list of things that want to autosync with you. Turn the autosync off for those you aren't using. Turning off wifi except when I am using it has made a significant difference for me as well.
grävling said:
About the battery life -- see which apps are using the most juice under settings/battery/. Some of them may be using more CPU cores, and have a higher frame rate than is needed. Go to settings/App optimisation/ and crank the numbers down. Next go to settings/Accounts and see the long list of things that want to autosync with you. Turn the autosync off for those you aren't using. Turning off wifi except when I am using it has made a significant difference for me as well.
Click to expand...
Click to collapse
Putting the CPU at 80 or 90% CPU speed in the performance settings will get you that reduced power consumption. You might not even notice the speed difference. These speed tiers also run at lower voltage.
Using the GPU frame rate limiter will dramatically extend gaming time too. I find 30 fps acceptable most of the time.
Of course it would be nice to run the thing unrestricted, but it's just not practical when you also want battery life. Look at what Nintendo is doing with the clock speeds of the X1 in the Switch.
I recently pulled the trigger on the MPHS25.200-23 official Android N software update for the Moto X Pure Edition. Aside from the concerns I listed among the release notes in the rollout discussion thread, I have been reasonably satisfied with the update. However, battery life absolutely plummeted after installing it. A hard reset was executed before (and after) the update and a cache/dalvik/art wipe was completed a couple days after getting everything set up.
Battery percentage drops at record speeds while the screen is on (although standby time is still okay). Using a Nexus 6 for reference, I compared results using Ampere and didn't notice any significant difference in power use (at least while idling with the screen on). Using the CPU usage monitor tool found under the debugging panel, nothing seems out of the ordinary here either (idling and light use shows a figure in the 9s, typically).
At this point, I figured misbehaving software could be ruled out, so I turned my attention to the battery. On my laptops, I can use either the OEM's power manager application or a Windows commandline tool (in Windows 8 and newer) to generate a battery health report, showing the "design capacity" and the actual "full charge capacity" in mah, which is a very good indicator of a battery's health. I struggled to find an equivalent to this on Android, but, after some digging, did find some promising leads
The trouble is that the results aren't consistent. On the Nexus 6, running "dumpsys batterystats | grep "Capacity"" shows a "Capacity" of 3220, which just happens to match the design capacity of the Nexus 6's internal battery. Running "dumpsys batteryproperties" shows "2910000" at the bottom next to "Full charge." Since the Nexus 6 is close to 3 years old now, it would make sense that the battery is only good for 2900 mah. Everything makes sense so far...
On the Moto X Pure Edition, however, "dumpsys batterystats | grep "Capacity"" yields a puzzling "Capacity: 1948." "dumpsys batteryproperties" yields "Full charge: 1948000". This makes no sense. If "Full charge" represents the design capacity, (not taking usage into account) why would it show as only 1948 on the Moto X?
Now, I'm opening this up to the community. What do you see when you run the first command?
Code:
dumpsys batterystats | grep "Capacity"
Do you see the expected design capacity of 3000 or do you also get a small (or smaller) number like I did?
Either way, I'd like to see people's results for the second command as well:
Code:
dumpsys batteryproperties
How close is the resulting "Full charge" value to the rated 3000?
The battery never was a 3000mah. That was a lie.
Have you done a factory reset since the update?
I get:
estimated battery capacity : 2996 mAh
and :
ac: 0 usb: 1 wireless: 0 current_max: 0 voltage_max: 0
status: 2 health: 2 present: 1
level: 96 voltage: 4411 temp: 267
current now: -182951
charge counter: 2905046
current now: -185
cycle count: 2
Full charge: 2730600
although my battery misbehaves big time ! from full charge to 80 in less than 10 minutes.
Thank you for the input
autosurgeon said:
The battery never was a 3000mah. That was a lie.
Have you done a factory reset since the update?
Click to expand...
Click to collapse
I figured as much, but not a value nearly half that! Definitely performed a hard reset, both before and after the update.
roozbeh101 said:
I get:
estimated battery capacity : 2996 mAh
and :
ac: 0 usb: 1 wireless: 0 current_max: 0 voltage_max: 0
status: 2 health: 2 present: 1
level: 96 voltage: 4411 temp: 267
current now: -182951
charge counter: 2905046
current now: -185
cycle count: 2
Full charge: 2730600
although my battery misbehaves big time ! from full charge to 80 in less than 10 minutes.
Click to expand...
Click to collapse
Interesting. This is more in line with what I was expecting to see on my own system, although it's surprising to hear that your phone still misbehaves as it does.
Bill720 said:
Interesting.
Click to expand...
Click to collapse
Bought February this year:
Going to try battery replacement
At this point, I'm going to chalk the issues up to a failing battery and simply consider this a coincidence. Does anybody who has done a battery replacement recently recommend any good brands or vendors who sell a decent battery that I won't have to bend to make fit? One eBay seller who I have contacted says that he normally sells the flat ones, but will provide a curved battery in its place if the customer specifically asks for it at checkout.
It may not be a bad battery, as I had the same issues and I recently replaced my battery with a battery the seller swears is brand new, and again it is behaving exactly like the old battery.
So I am at a loss as to what to try. How do you fool the system into thinking the battery is brand new?
I just decided to check the dumpsys batterystats and it shows absolutely nothing
dumpsys does not give me any information at all, is this a permission problem?
The plot thickens...
roadrun777 said:
It may not be a bad battery, as I had the same issues and I recently replaced my battery with a battery the seller swears is brand new, and again it is behaving exactly like the old battery.
Click to expand...
Click to collapse
Interesting. What time of runtime (screen-on time) are you seeing? Do you remember what seller/store you got the replacement from? Was the replacement flat or curved, like the original battery?
roadrun777 said:
I just decided to check the dumpsys batterystats and it shows absolutely nothing
dumpsys does not give me any information at all, is this a permission problem?
Click to expand...
Click to collapse
Don't try "dumpsys batterystats" without the "grep "Capacity"," else you'll get so much output that the device might freeze and then reboot.
The fact that you're getting no output with either command seems unusual though. I don't know if it'd make a difference for sure, but, out of curiosity, do you have busybox installed?
Yes I have busybox installed, let me go check version.
busybox 1.27.2
I thought maybe it was because I was plugged in but I installed a terminal app get root and check it internally without it being plugged in and nothing, there is absolutely no data.
So I am at a loss as how to fix this. Something is either hijacked the system and is hiding the data or there is no data and the processes that create it have not run correctly, which then means I will have to hunt down exactly what processes create the info.
Any help would be appreciated as I've been doing stuff like this without help for decades and it gets very time consuming to track down bugs for developers that are too busy driving around in their humvee's and flying to Europe to care.
Strange output; are you running the stock rom?
roadrun777 said:
Yes I have busybox installed, let me go check version.
busybox 1.27.2
I thought maybe it was because I was plugged in but I installed a terminal app get root and check it internally without it being plugged in and nothing, there is absolutely no data.
So I am at a loss as how to fix this. Something is either hijacked the system and is hiding the data or there is no data and the processes that create it have not run correctly, which then means I will have to hunt down exactly what processes create the info.
Any help would be appreciated as I've been doing stuff like this without help for decades and it gets very time consuming to track down bugs for developers that are too busy driving around in their humvee's and flying to Europe to care.
Click to expand...
Click to collapse
That's really weird that the command takes, but displays no output. My Samsung Epic (with a CyanogenMod build of Ice Cream Sandwich) simply scolds me when trying to put the commands in. The only time when I can achieve no output (on the Pure Edition or Nexus 6) is if I forget to go root before typing the commands. Are you on the stock rom?
No good, it seems
Well, I received the replacement battery today and installed it. To my surprise, however, there was almost no measurable change in runtime; I charged it up and burned down half a tank with only about 45 minutes of screen-on use! I ran those commands again, and this time, both values indicate a touch over 3000. I'll give it a few cycles to see if things return to normal, but if not, then I'm at a loss. Are there any negative consequences to "downgrading" to Marshmallow?
Unusually high power draw spotted, as reported by Ampere
Quick addendum: I tested again using a program called Ampere, and found that current draw is actually a bit on the high side. Comparing alongside the (nearly identically-configured) Nexus 6, using multi-window, I found that current draw is actually often doubled, and sometimes even tripled.
For example, when playing an HD YouTube video, the Nexus 6 maintained a draw of around 330, give or take a few dozen (fluctuating between around 300 and 430). However, the Pure Edition was between 800 and 1400, typically settling at around 1100 to 1300. Thinking that there may be some kind of software issue after all, I rebooted into "Safe Mode" and tried using the device that way, but saw no perceptible change (at least as best as I could tell without being able to run Ampere).
With that in mind, I'd like to pivot more to a discussion of what kind of power draw everybody is seeing in Ampere under light usage and video watching, regardless of what Rom or kernel you're running. Is anyone else seeing high power draw while doing relatively little?
200-22 was the ticket!
Well, this will be the second time that a weird, untraceable issue wound up being solved by flashing back to stock and upgrading. I installed that 200-22 factory image, took the new update, (October security level) and everything appears to be fine and dandy once again. Runtimes are much better and Ampere reports much lower power consumption (idling below 250ma and light use in the mid-to-low hundreds; which is much less than half of what I was seeing before).
Idle power draw (prior to restoring most of my apps) was holding steady at around 1.4% per hour, averaged over about 24 hours of non-use. And that's without any of the Amplify or Greenify tweaks.
I'll have to withhold final judgement until all of my data and software is restored, but things are looking really good so far. That "Sprint" factory image appears to have saved this Verizon-network-user's bacon.
Update...
Maybe that wasn't it after all. Battery life started tanking again within a couple of weeks after the operation, so there must be some software I'm installing that isn't playing nice somehow (even though Wakelock Detector shows no noteworthy periods of unrest). It's odd because I have almost the exact same software load on my backup phone (the Nexus 6) and can leave that thing in the backpack for days on end without it losing much charge at all, while the Pure Edition is managing to run down at a rate of about 4 percent per hour, screen-off and unused.
While the device is awake and running, Ampere shows an idle power draw of between 450 and 1000 mah, which, while (probably) not as bad as before, is still consistently higher than it should be.
The silver lining to this whole thing is that I now have so little time in the day to actually use the phone that it usually doesn't matter. If I get the chance again, I might switch back to the Nexus 6 temporarily again to troubleshoot the Pure Edition more carefully. There has to be something that I'm missing.
same issue here after updating to NPHS25.200-15-3, i have to charge the phone almost twice as before. looking at apps usage shows nothing unusual. i'm checking battery performance using accubattery
Power use figure?
hagi_mostafa said:
same issue here after updating to NPHS25.200-15-3, i have to charge the phone almost twice as before. looking at apps usage shows nothing unusual. i'm checking battery performance using accubattery
Click to expand...
Click to collapse
What's your idle power draw as measured by Ampere?
Bill720 said:
What's your idle power draw as measured by Ampere?
Click to expand...
Click to collapse
Check these two shots
Going to have to find the answer the hard way
hagi_mostafa said:
Check these two shots
Click to expand...
Click to collapse
Are you running stock rooted? At this point, I'm beginning to wonder if I got a bum replacement battery, since the whole thing just shut down spontaneously on me one day at around 20%. I'll try switching back to the Nexus 6 and start over with the Pure Edition again, this time installing things one-at-a-time (or in waves while making liberal use of backup images) to see what (if anything) is not sitting right with it. The most perplexing thing of all is that I have the Pure Edition configured almost identically to the Nexus 6 in terms of tweaks and software, and yet the Nexus lasts 2-4 times longer.
Even right now, I'm sitting at 4% with about 32 minutes of screen-on time and 36 minutes of background audio playback over about 12 hours. In contrast, the Nexus 6 is at 74% with just over 1 hour of screen-on time and 52 minutes of screen-off audio playback (and yes, I do have an active Sim card installed in it too, albeit on a different carrier). In essence, the Nexus managed to do twice as much with one quarter the power draw, so I know for a fact that something is wrong, either in hardware or in software, and my experiments over the course of the coming weeks will confirm, one way or another, which is the case.
This whole experience really has soured my whole opinion of this phone. I still believe that it's one of the best smartphones ever made, but there's no doubt that it has a serious problem, and I'm disappointed by both possible outcomes. If it ends up being software, then it'll be plain that Lenovo screwed up in a big way to make it so that I could duplicate the same weird bug twice in a row with a fairly common/minimal setup that should not cause any problems. On the other hand, if it ends up being hardware, then that'll be the end of the line for this phone, plain and simple, seeing as few of the available battery replacements don't completely suck. Honestly, I'd have replaced this phone sooner, given how much time it's cost me, but there's just nothing affordable I could go to that wouldn't be a compromise. I guess the dream of "decent smartphone" just wasn't meant to be for any longer than that first year .
Bill720 said:
Are you running stock rooted? At this point, I'm beginning to wonder if I got a bum replacement battery, since the whole thing just shut down spontaneously on me one day at around 20%. I'll try switching back to the Nexus 6 and start over with the Pure Edition again, this time installing things one-at-a-time (or in waves while making liberal use of backup images) to see what (if anything) is not sitting right with it. The most perplexing thing of all is that I have the Pure Edition configured almost identically to the Nexus 6 in terms of tweaks and software, and yet the Nexus lasts 2-4 times longer.
Even right now, I'm sitting at 4% with about 32 minutes of screen-on time and 36 minutes of background audio playback over about 12 hours. In contrast, the Nexus 6 is at 74% with just over 1 hour of screen-on time and 52 minutes of screen-off audio playback (and yes, I do have an active Sim card installed in it too, albeit on a different carrier). In essence, the Nexus managed to do twice as much with one quarter the power draw, so I know for a fact that something is wrong, either in hardware or in software, and my experiments over the course of the coming weeks will confirm, one way or another, which is the case.
This whole experience really has soured my whole opinion of this phone. I still believe that it's one of the best smartphones ever made, but there's no doubt that it has a serious problem, and I'm disappointed by both possible outcomes. If it ends up being software, then it'll be plain that Lenovo screwed up in a big way to make it so that I could duplicate the same weird bug twice in a row with a fairly common/minimal setup that should not cause any problems. On the other hand, if it ends up being hardware, then that'll be the end of the line for this phone, plain and simple, seeing as few of the available battery replacements don't completely suck. Honestly, I'd have replaced this phone sooner, given how much time it's cost me, but there's just nothing affordable I could go to that wouldn't be a compromise. I guess the dream of "decent smartphone" just wasn't meant to be for any longer than that first year .
Click to expand...
Click to collapse
after several cycles accubattery shows that a full battery just works no more than 3 hours. in some cases it even lasted for just one hour or less!
so of course there's something wrong here.
the issue has appeared exactly since i upgraded from 6.0.1 to version 7, both official xt1572 asia ds. just flashing boot and system files. no root custom recov or else.
so i really doubt that this could be of a hardware failure. also i'm using the same collection of apps as in rom 6.0.1 so this is not an app issue.
as accubattery shows battery health and power usage, battery health is 80% at 2580mah and power usage is high, something between 500 up to 700 mah.
the only possible cause resides in rom or flashing. i'm gonna try flashing us rom and if the problem continued, i'm gonna flashing latin ds with boot system and modems.
Gratitude for the information
hagi_mostafa said:
the issue has appeared exactly since i upgraded from 6.0.1 to version 7, both official xt1572 asia ds. just flashing boot and system files. no root custom recov or else.
Click to expand...
Click to collapse
Good to know. Mine is the North American XT1575 variant, but I'm in the same boat otherwise. The trouble seemed to start almost immediately after installing the new 7.0-based update, so there's a good chance that it's related to this in some way. Mine is rooted, (stock rom/kernel, however) but it's good to know that somebody running stock is seeing the same thing.
hagi_mostafa said:
so i really doubt that this could be of a hardware failure. also i'm using the same collection of apps as in rom 6.0.1 so this is not an app issue.
as accubattery shows battery health and power usage, battery health is 80% at 2580mah and power usage is high, something between 500 up to 700 mah.
the only possible cause resides in rom or flashing. i'm gonna try flashing us rom and if the problem continued, i'm gonna flashing latin ds with boot system and modems.
Click to expand...
Click to collapse
I don't think that it has anything to do with the software region. I'm on the standard North American build with the same problem, so the issue (if in software) must be a broader one. I'm going to try to switch back to the Nexus 6 today so that I can start the long process of starting over on the Pure Edition and getting to the bottom of just what causes things to crash & burn.
I have a Kindle FIre HD 10 (2017) that has been rooted. I recently noticed that my Kindle's batteries aren't lasting as long as they once did. I've looked at the apps I have installed and uninstalled most of the suspect battery draining apps, but I feel like maybe more can be done. Are there any tips and tricks for rooted Kindle Fire HD 10's that will improve battery performance?
I had some issues with system/amazon processes eating 15-20% CPU for a while. Even though I disabled most inessential Amazon apps..
Reflashing the rom and starting over helped, without registering the device, with Amazon.