This phone is becoming a joke, it seems that with every update Google or Samsung are crippling this phone.
N9005XXUFNF4 was supposed to improve battery life on the Note 3, so why is my battery drain worse?
I bought the Note 3 to do away with netbooks and tablets, but now I am being forced to use them again.
When I use the internet, browsing on the Note 3 itself, my battery can lose 50% in under 30 minutes. I am then forced to switch off data out of fear that the phone will not last the day.
However, when I tether a notebook or a tablet to the Note 3, it will give me about 8 hours of internet usage before it needs charging.
So what is the point of the Note 3 now? It is quickly becoming just an expensive modem.
Are u using fully stock ? Root it, delete bloat apps and install a custom kernel. I just did these and hardcore debloated now I'm getting perfect battery/performance.
And this is why I am happily sticking to NB7 for the forseeable future.
-6%, 1.30h screen-on time, wifi on, tapatalk, firefox and gmail.... (at -60% brightness though(lux).) No root, full stock.
If it isn't broken, don't fix it.
Tried a full factory reset yet?
Sent from my SM-N9005 using Tapatalk 2
terry1000 said:
This phone is becoming a joke, it seems that with every update Google or Samsung are crippling this phone.
N9005XXUFNF4 was supposed to improve battery life on the Note 3, so why is my battery drain worse?
I bought the Note 3 to do away with netbooks and tablets, but now I am being forced to use them again.
When I use the internet, browsing on the Note 3 itself, my battery can lose 50% in under 30 minutes. I am then forced to switch off data out of fear that the phone will not last the day.
However, when I tether a notebook or a tablet to the Note 3, it will give me about 8 hours of internet usage before it needs charging.
So what is the point of the Note 3 now? It is quickly becoming just an expensive modem.
Click to expand...
Click to collapse
it is all because you need to do a full wipe my friend.
I guess after update, you haven't do a full wipe. NF4 comes with new bootloader, and though a same KK, but different base version from NE or any older one. A full wipe from stock recovery will make it better.
But don't forget, backup your internal sd card first, as any factory reset from stock recovery will do a full wiping on your internal SD. All will be gone. ...
Stock firmware has never given me that type of worst battery usage. especially in 30 minutes ? wow....
FYI, I always like to do a clean install, especially jump up firmware.
antique_sonic said:
it is all because you need to do a full wipe my friend.
I guess after update, you haven't do a full wipe. NF4 comes with new bootloader, and though a same KK, but different base version from NE or any older one. A full wipe from stock recovery will make it better.
But don't forget, backup your internal sd card first, as any factory reset from stock recovery will do a full wiping on your internal SD. All will be gone. ...
Stock firmware has never given me that type of worst battery usage. especially in 30 minutes ? wow....
FYI, I always like to do a clean install, especially jump up firmware.
Click to expand...
Click to collapse
Thanks,
A full wipe and reinstall everytime this phone updates will drive me crazy.
You would think that Samsung would warn users about this.
terry1000 said:
Thanks,
A full wipe and reinstall everytime this phone updates will drive me crazy.
You would think that Samsung would warn users about this.
Click to expand...
Click to collapse
You'd think Samsung would come up with an app+data backup software.
terry1000 said:
Thanks,
A full wipe and reinstall everytime this phone updates will drive me crazy.
You would think that Samsung would warn users about this.
Click to expand...
Click to collapse
yeah... few first try you will feel crazy.. after that you will get use to it already.
It will take me at most 1 hour to resetup everything. But I will be able to enjoy the upgrade to the fullest, without any non sense things.
to the thread starter, is is already solved according to the posters?
this is also my new problem when I update. before update, for one day, I charge to the maximum of 4 hours (not continuosly) full battery. today, my percentage of charging is 12 hours. this is crazy. I think I might root my phone now in order to solve this problem.
Wow, on 4.3rom, i saw 10 hours screen time playing hd movies, and 7 hours screen time with 2 days.
T his is something I have been dealing with for 3 months and I'm fed up...
About once every week or two, I turn off my device for a few hours to give it a rest. However, every... single... time I power on or reboot my device, my phone greats me with SIGNIFICANT amounts of lag just after boot.
Eventually in a few hours everything runs smooth, but when I boot or reboot my device will lag behind nearly 500 to 3000 milliseconds.
Just now I pressed my power key and it took my phone nearly 10 whole seconds to turn off or react to any hardware keys. And I'm just coming off smart switch so I have no installed apps. So I'm as clean as stock, but I've still had issues like this since day1
Does anyone hear have any earthly idea why my s7 lags for hours if I reboot/boot?
What kind of SD card do you have? I used an old one when I got the S7 and it lagged horribly, overheated etc. As soon as I took it out it was better.
Sent from my KFFOWI using Tapatalk
Chocolina said:
T his is something I have been dealing with for 3 months and I'm fed up...
About once every week or two, I turn off my device for a few hours to give it a rest. However, every... single... time I power on or reboot my device, my phone greats me with SIGNIFICANT amounts of lag just after boot.
Eventually in a few hours everything runs smooth, but when I boot or reboot my device will lag behind nearly 500 to 3000 milliseconds.
Just now I pressed my power key and it took my phone nearly 10 whole seconds to turn off or react to any hardware keys. And I'm just coming off smart switch so I have no installed apps. So I'm as clean as stock, but I've still had issues like this since day1
Does anyone hear have any earthly idea why my s7 lags for hours if I reboot/boot?
Click to expand...
Click to collapse
Have you tried cleaning the cache via recovery? LJ
erick161 said:
What kind of SD card do you have? I used an old one when I got the S7 and it lagged horribly, overheated etc. As soon as I took it out it was better.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Samsung Evo 64GB, Read 30MB/s, write 18MB/s. Its nothing fancy but it is just a tier above standard Class 10 speed. It shouldn't be a hindrance to my performance.
Try clearing the system cache?
The cache thing may work. It also has to do with how many apps run at startup and how much ram those apps use. In my experience, that has the biggest effect.
I've stock Axon 7 and nothing is modified or unlocked. After Noughut update last week my phone is have number of issues
1) Bluetooth seems to be unreliable and it sometimes works and something wont
2) Cannot play audio on any of FB or youtube videos for some reason.
3) Phone hangs from time to time while using Whatsapp and speicifically if I try to take a picture when inside Whatsapp it makes whole phone freeze.
4) Overall performance of phone seems to be slower compared to how it was prior to update.
I've 15GB of remaining space on my internal memory and more than 70GB of space on my Sandsik microSD card. So not sure why phone is behaving bit odd.
Anyone else having similar issues after latest update on their Axon 7 ?
TIA
check out the zte forums. Lots of complaints over there.
lafester said:
check out the zte forums. Lots of complaints over there.
Click to expand...
Click to collapse
Maybe the next update will be more favorable. Brave souls to install a major OS update. I'm still unsure what to run on mine. For now, might just stick to MM for the next few months until things stabilize with 7.
I would say to backup your internal storage to the SD card and factory reset your phone. Not fun to do but I bet it will help.
RUNNERX said:
I would say to backup your internal storage to the SD card and factory reset your phone. Not fun to do but I bet it will help.
Click to expand...
Click to collapse
I was having some issues, so I copied what I could (I am stock not rooted) to the SD card and did a factory reset. So far, so good. It is a pain, but probably good to start with a clean slate...
I'm same as op, stock unrooted or modified. I did nothing except apply the n update but have none of the problems he experienced. Bluetooth is solid, audio plays perfectly, I took and sent pics in whatsapp to see if anything happened, all good. If anything my phone is faster, and battery seems to be running about the same as it was on mm-around 6.5 hours sot. Very strange how some phones react completely different to the update.
Sent from my ZTE A2017U using Tapatalk
After a couple of days, I notice a slowing down and lag in responsiveness. I boot into twrp and wipe cache and delvik. That does the trick for a couple of more days until it starts slowing again. Heard this can be done in stock recovery too.
azpatterson3 said:
After a couple of days, I notice a slowing down and lag in responsiveness. I boot into twrp and wipe cache and delvik. That does the trick for a couple of more days until it starts slowing again. Heard this can be done in stock recovery too.
Click to expand...
Click to collapse
Did you try reinserting your sdcard while using the phone? I heard it helps.
bornlivedie said:
Did you try reinserting your sdcard while using the phone? I heard it helps.
Click to expand...
Click to collapse
I have not. I will try that. Thanks!
My battery has definitely taken a hit. Less than an hour of SOT for 28%.. That's noticeably worse than MM.
I went over 6 hrs sot my first full Nougat charge. I factory reset after upgrading to get the Verizon sim to work.
Sent from my ZTE A2017U using XDA-Developers Legacy app
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.