Database Develop

[Q] Maybe a clue to battery issues? 2 instances android.process.acore using 100% CPU

Let me start by saying Thank You VERY much DroidTheory (and everyone who has contributed to making this an excellent stable ROM).
I am on the 1.4 (wiped cache, dalvik, battery stats, formatted system) build and I've been having the battery issues that everyone is talking about since 1.2. I am in the forums constantly and I have read all of the posts and the fixes for them. I have wiped battery data from a full charge, I'm on 1.4 so OMA files are already gone, I'm in Portland Or and we have stong 4G no drops ever since I have had my phone. So it isn't the cycling 4G/3G issue.
So I know there are multiple "my battery is dying" threads but I had not seen this one mentioned in any and don't want to get buried.
So I am having a bit of an issue getting a screen shot of it everytime I try I just get a wierd distorted image. That is not the issue I came for but if anyone knows.
What I am noticing is when I use the "Android System Info" app in the processes if I sort by CPU% I see 2 instances of the same thing "android.process.acore" both reporting 100% CPU and 35.28MB RAM. My total CPU is reporting around 50% at most times. I have tried killing the processes to see what may happen and there are no negative effects but the processes just seem to come back eventually if I check an hour (not exact) later there they are again.
I assume it's impossible for 200% of CPU to be used right now but what I'm wondering is would 100% CPU on one process equal to 50% when considering that nothing uses both cores yet?
Any clues what these processes (android.process.acore) are and if there is anything I can do. If someone can suggest a good way to take screens I will be happy to post one as well.

Use Screenshot ER instead of AndroSS. Curious to your findings. Massive battery drain here. I dropped 10% in 45 minutes doing absolutely nothing. Nothing rogue in my battery stats...
Sent from my DROID BIONIC using xda premium

Now I did notice that both say com.fede.launcher. This seems to say to me it is launcher pro as the dev is Federico Carnales. Im really hoping the 2 aren't in compatible as I've been using this since it came out in my D1 and I am damn used to it. Anyways here is my screen shot.
{
"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"
}
Sent from my DROID BIONIC using XDA App

Also I should mention that when I kill one process it kills both at the same time. I am using 0 of the launcher pro widgets so it doesn't seem to be polling or syncing. And nothing acts any differently (that I can see) after the kill. No restart of launcher or anything.
Sent from my DROID BIONIC using XDA App

Proff3ss0r Farnsw0rth said:
Now I did notice that both say com.fede.launcher. This seems to say to me it is launcher pro as the dev is Federico Carnales.
Click to expand...
Click to collapse
Pretty sure Fed said LP/LP+ isn't tested to work on gingerbread yet
Maybe that'll be fixed once he's done w/ the rewrite?
Wish I could help ya tho...just another pointless reply here

Proff3ss0r Farnsw0rth said:
Also I should mention that when I kill one process it kills both at the same time. I am using 0 of the launcher pro widgets so it doesn't seem to be polling or syncing. And nothing acts any differently (that I can see) after the kill. No restart of launcher or anything.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
I see this, 100% CPU on 1 or more threads of a single process on multiprocessor linux boxes where that process has run away/spinning in code... on a 2 processor system the system would look always loaded 50% or more...

Hey that's news to me man. Honestly by the time I put GB on my D1 I couldn't tell a difference because my battery was suffering as is so it could have been doing it there too...
Mista Wolf are you running launcher pro as well?
Sent from my DROID BIONIC using XDA App

That was my guess on the cores was 100% of of what it has the ability to use right now is only 50% of available.
Sent from my DROID BIONIC using XDA App

I have launcher pro and those processes don't run at all on my phone.
Sent from my DROID BIONIC using XDA App

Proff3ss0r Farnsw0rth said:
Hey that's news to me man. Honestly by the time I put GB on my D1 I couldn't tell a difference because my battery was suffering as is so it could have been doing it there too...
Mista Wolf are you running launcher pro as well?
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
I am using the stock Blur launcher. My battery is just taking a beating...
I really want to figure this out because I love this ROM.

I swapped out to launcher ex I was pretty much able to duplicate my lp+ setup I'll see what happens I'm good so far no return. We'll see if this cures my battery issues.
Sent from my DROID BIONIC using XDA App

And its back... so I seem to be getting this no matter what launcher I use on top of stock. Can anyone else confirm this? Could someone that can dig deeper into this try to duplicate and find out why these processes seem to be taxing the cpu so much or are there any resources I can pull that could help me get this figured out?
Sent from my DROID BIONIC using XDA App

I get great battery life with launcher pro. It may not be optimized for gingerbread(or so it's said) but it runs great for me. I was getting a day and a half on Eclipse for the x2.
Sent from my DROID BIONIC using xda premium

I have been running zeam launcher, and have had absolutely amazing battery life, unplugged at 6:30, and will still be in the 70's with light use, or 60's with moderate use come quitting time.
Sent from my DROID BIONIC using xda premium

Proff3ss0r Farnsw0rth said:
And its back... so I seem to be getting this no matter what launcher I use on top of stock. Can anyone else confirm this? Could someone that can dig deeper into this try to duplicate and find out why these processes seem to be taxing the cpu so much or are there any resources I can pull that could help me get this figured out?
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
I installed Android System Info and checked that my android.process.acore was not using any cpu cycles (0%). I use the Go Launcher. I would suggest trying the dreaded "Factory Hard Reset". I know it's a pain and time consuming, but it cures a lot of random ills.
Good luck.

Yeah I am doing a reinstall with a rewipe at the moment (I know this isn't hard reset). I am a very process oriented person so I doubt I missed any of the wipe/formats needed for Unleashed but I'm going to give it another try.
After doing a bit of google searching for "android.process.acore" I find ALOT of people with the exact same issues (on different phones) all with non-stock launchers. I have found a few suggested fixes. Like removing widgets from stock browser and all other launchers (I have a few right now as I've been testing and trying to work around.
This does seem to be a widespread problem though for more than just us.
Geezer could you please keep checking on Android System Info for me randomly (this is not an all of the time thing) I can kill the process and it will stay dead for a seemingly random amount of time (haven't been able to notice a pattern yet) at seemingly random points(I'm not noticing any one action causing this). But from the other references I'm seeing to this problem all seem to revolve around updating but most for different things... I have been taking note of PID in Android System info and searching for the PID in CATLOG I am finding references to the PID but honestly I don't see any glaring problems but I'm no dev and I don't fully understand what it is telling me. If I provide LOGCAT of the process could someone translate for me?

Proff3ss0r Farnsw0rth said:
Geezer could you please keep checking on Android System Info for me randomly (this is not an all of the time thing) I can kill the process and it will stay dead for a seemingly random amount of time (haven't been able to notice a pattern yet) at seemingly random points(I'm not noticing any one action causing this). But from the other references I'm seeing to this problem all seem to revolve around updating but most for different things... I have been taking note of PID in Android System info and searching for the PID in CATLOG I am finding references to the PID but honestly I don't see any glaring problems but I'm no dev and I don't fully understand what it is telling me. If I provide LOGCAT of the process could someone translate for me?
Click to expand...
Click to collapse
Will do. I just checked and it's still at 0. I'll check throughout the day and let you know tonight.
Good luck.

ROB281 said:
I have been running zeam launcher, and have had absolutely amazing battery life, unplugged at 6:30, and will still be in the 70's with light use, or 60's with moderate use come quitting time.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
+1
Zeam launcher is awesome.

I checked out zeam but I just can't deal with how minimal it is don't get me wrong I run very minimal home screens (nearly 0 widgets but battery and clock and only 2 home screens. I just can't deal with the lack of options in zeam. I don't really have any further leads on this I've been fighting with it as I've had chances at work but still no luck. Does anyone here know how to actually read a logcat or will that even get me what I need?
Sent from my DROID BIONIC using XDA App

FWIW, I'm getting ABYSMAL battery life (7h4m from full charge to shutdown as of my last cycle just now), with only 8 minutes of phone calls, light surfing, light texting, email sysncs at 1/hour.
I'm running GoLauncher with UNL3EASH3D v4. I have yet to see the process you describe (and I've been checking it pretty frequently trying to track down my drain- in fact, without exception every time I check, Android System Info is the process using the highest cycles at about 10-13%). I also used Go with stock for a day or so and didn't have this level of drain. HOWEVER, I didn't duplicate my stock setup when i flashed unleashed, so it may well be unrelated to the ROM.
I AM seeing waaaaaay too much awake time on the stock battery stats screen.
I'm about to do a wipe and reinstall and run minimal for a few days to see if I can pinpoint anything. Trying to hold out for the update if I can... (Love the ROM, so really don't wanna go stock)

AOSP roms = possible problems

I have been following most of the AOSP threads fairly closely to see people's experiences and I have seen a disturbing amount of people report bricked phones. The odd thing about it is that these bricks didn't occur during the process of flashing a rom. They all happened (or most of them at least) while trying to power on the phone after it was turned off or in deep sleep. Here are links to posts by DIFFERENT AOSP rom users who all experienced similar issues (one of these posts contain links to 3 other posts):
http://forum.xda-developers.com/showpost.php?p=42682374&postcount=78
http://forum.xda-developers.com/showpost.php?p=42654173&postcount=434
http://forum.xda-developers.com/showpost.php?p=42681918&postcount=436
http://forum.xda-developers.com/showpost.php?p=42557657&postcount=417
I personally have run Slim's rom for a good 4-5 hours w/o problems. However, I went back to Sense shortly thereafter. I'm not trying to cause some kind of panic but on the same hand I don't want to see people sitting around with a $500 desk ornament. Bottom line is we are responsible for what we do with our phones and as a result we should do as much research as possible before flashing anything. Look before you leap!
Edit: Here is an additional means to record your brick experience:
smac7 said:
I made this to try to pinpoint the issue. This way we can collaborate with all one owners, not just sprint.
If you have this issue, please add your info.
Here is the form
https://docs.google.com/forms/d/17NmaM3zhWueTxI_y7f1U7N6Er6tprd22I8_f3aIYmCw/viewform
Here is the responses
https://docs.google.com/spreadsheet/ccc?key=0AkLYIbykddrAdF9TMXBXaXZjMFhEczlSYUhoVDNHU1E#gid=0
Let me know if i should add any other crucial questions. I encourage people to post this in other threads when relevant.
Edit: page is open for public sharing
Click to expand...
Click to collapse
Thanks goes out to the user who took the time to do this.

Yep just be careful guys the only warning I had to something strange happening was that my phone didn't charge at all when I turned it off (to try and charge it fast) it still charged while powered on however. But once it died that was it. Also no overclocking or system setting where really changed in my case.
Here's how I got a replacement went in and told them it wouldn't turn on and I myself at the time thought it was the battery so they said that could be it but again I wasnt to sure and neither where them. I ended up paying 50$ without tep
{
"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"
}
Sent from my HTCONE using Tapatalk 2

Alex1123 said:
Yep just be careful guys the only warning I had to something strange happening was that my phone didn't charge at all when I turned it off (to try and charge it fast) it still charged while powered on however. But once it died that was it. Also no overclocking or system setting where really changed in my case.
Here's how I got a replacement went in and told them it wouldn't turn on and I myself at the time thought it was the battery so they said that could be it but again I wasnt to sure and neither where them. I ended up paying 50$ without tep
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
That's some messed up stuff.... You shouldn't have had to pay since it was a "hardware" issue. It should've been covered under the manufacturers warranty.

Lol it was but I needed a phone fast and didn't go through HTC
Sent from my HTCONE using Tapatalk 2

Alex1123 said:
Lol it was but I needed a phone fast and didn't go through HTC
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
I know but whenever i've had a problem like that it's always been a free fix through sprint......

yeah I am in the same boat, I believe I was the first to report this. At first I thought it was just me and I passed it off as nothing. Since I've got my replacement I've watched people starting to trickle in with the same exact problem on AOSP I would definitely avoid flashing AOSP until the cause is narrowed down and solved if possible. As I said before it would be a damn shame not to run AOSP on this mighty device, but I have to stick with sense for now and hope that this problem is squashed soon.

Wow really? How upsetting. I'll have to keep an ear open. If there is any news regarding this issue please share
Sent from my HTCONE using xda app-developers app

Has anyone on a NON AOSP rom run their battery down and had it die? Did it charge? I know on a few other phones it was actually the recovery that had this issue. I would try it myself but as I have my phone through work, replacing it is a bit more complicated.

I work for sprint and had a guy come in who bricked his phone. A simple relock of the bootloader and an ruu flash and bam phone was up and working fine. Is that not working for aosp bricks? I've personally haven't had any problems out of aosp roms
Sent from my HTCONE using xda app-developers app

That makes sense. Thanks
Sent from my HTCONE using xda app-developers app

socalnative1 said:
I work for sprint and had a guy come in who bricked his phone. A simple relock of the bootloader and an ruu flash and bam phone was up and working fine. Is that not working for aosp bricks? I've personally haven't had any problems out of aosp roms
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
you are not able to relock the bootloader. we're talking total shut down, no power, no charge, no recovery, no bootloader, no fastboot adb devices, not a thing period point blank. i have the dead device still, and for the life of me cannot get it to do anything. I have been on my replacement for 2 weeks now running sense. hopefully the cause and solution are near.

Well... I was thinking of trying an AOSP ROM, but I guess I will hold of on that thought.
Sent from my HTCONE using Tapatalk 4 Beta

felacio said:
Well... I was thinking of trying an AOSP ROM, but I guess I will hold of on that thought.
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm with you on that

Until we get more kernel sources/reliable code out of HTC, playing with AOSP can be a dangerous game. And tbqh, it could well be OP's fault (not saying it is, but it can be). Flashing custom software of any kind is going to give your carrier/OEM an easy way out if anything goes wrong, which everyone really should keep in mind before making the jump.

What recovery are the "bricked" users running. TWRP or CWM?

Yeah I had my battery die completely on a sense Rom, but I was easily able to charge it and turn it back on 2 minutes later.
Sent from My Only "One"

Glad I'm doing a lot of reading before I make the jump back to HTC. Seems like the One is more of a pain in the ass to Develop (safely) for than the GS3. Looks like I'll be sticking to sense for a while.

For once in all of my android ownership, I'm not really pressed to switch to aosp so this isn't a huge deal for me. The phone is already blazing fast and I actually enjoy and use a lot of the features HTC has implemented into Sense 5. And HTC's browser is the smoothest I've ever used. I do hope someone figures out the problem though. Hate to see more people get bricked.
Sent from my HTCONE using xda premium

Kraizk said:
What recovery are the "bricked" users running. TWRP or CWM?
Click to expand...
Click to collapse
So far, only TWRP users have reported this issue.

I don't want to be Mr. Obvious but I'm assuming that you guys have already tried the trick of putting your phone under a bright light, etc etc

I am loosing my mind! Note eating battery and superslow

Hi!
My Note has for a quite long time now been slow, laggy and eating battery.
Didn't mind, had a car charger, suspected old battery and clogged storage.
About a week ago it came to a complete stop, taking 30 sec to open facebook.
And typing in Swiftkey an impossibillity, having keystrokes on a 5-10sec lag.
So finally i got a new battery, whiped the phone clean.
Flashed the phone with a fresh rom (Team Union JB XXLT4 V7)
Installed my apps manually, making shure no crap cache was brought.
Formatted internal storage and got a new 32Gb SanDisk Ultra card.
Fresh start, fast phone right? no.
Apps still unusably slow, typing on swiftkey impossible without lagging.
Battery from a full charge last about 6h with light usage.
Would like to stay on TW only for the MHL capability, but now i am open to anything.
Can't really afford a new phone, so if this can't get resolved ill switch to my old 3GS.
What do i do now?
What can i try?
{
"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"
}
The screenshots are from different days and scenarios, but changing governor or other settings gives me about the same result.
Just listened to som music, and some light surfing, thats about all. Battery blames is all on the screen and os about 33% & 33%.

YOu should try AOSP/AOKP Roms!!!

I think one of the apps you have is causing the problem.
When i had the same problem it turned out to be the podcasting app i had.
https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats&hl=en
Or go to the terminal and run top, see whats eating the cpu.

have you try to replace new battery ?!

NoteboyTech said:
YOu should try AOSP/AOKP Roms!!!
Click to expand...
Click to collapse
Thanks for the reply, but i am afraid ill have the same issues.
Azeazezar said:
I think one of the apps you have is causing the problem.
When i had the same problem it turned out to be the podcasting app i had.
https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats&hl=en
Or go to the terminal and run top, see whats eating the cpu.
Click to expand...
Click to collapse
Good suggestion, i'll run top once in a while, see i find anything.
nokia2002 said:
have you try to replace new battery ?!
Click to expand...
Click to collapse
Well, yeah couldn't find any original though, and don't want to wait weeks for a shipment, so got a copy brand "ENERGY" spacy logo and made here in Thailand. Only 2350mAh compared to the original 2500mAh.
Found that the new battery didn't really make any difference, about the same.
So worried i got new but crappy battery I'm now back on original, without any noticable change.
Considering getting a external charger and carrying the spare battery, that is not really a solution either.
Got get this phone working reliably soon, or i need to find a replacement.
Appreciate the tips, and ill try and make a study with "top" and get back to you guys.
Maybe i have a energy hog after all...

It's a pain in the butt, but it looks like the only way to resolve it is to do a clean wipe, then install each
app one by one, giving yourself a day or two of usage. Sucks, but it sure sounds like one app is
screwing up another one. Any chance you can (shudder) use a "memory cleaner/program closer"
after you use each app, to make sure it's closed as a test? Sounds like something sure is
interacting with something else.

USe Greenify and hibernate all apps!!!

Check your Google account settings. If you have sync Internet ticked disable it.
Sent from my GT-N7000 using XDA Premium 4 mobile app

You think you have it bad? I'm only getting 4.5 hours
Sent from my GT-N7000 using xda app-developers app

JellybeanSandwich said:
You think you have it bad? I'm only getting 4.5 hours
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Really?
I thought my battery life was bad. 7h15m with 45 min screen time after charging my battery is at 67%
That is with wifi and bluetooth (with music playing) on and connected.
GPU overclocked and lowest step 200mhz(from 133 and max 400) and cpu up to 1550 Mhz.(okay, i did reduce the voltages, sue me)
and google location service on.
On original battery (dec 2011), that is about to die (screen starts glitching around 30%)
Somehow you are doing it wrong.

You would be surprised at what a speed deference you will get and battery life with aosp roms I have used tw and aosp and always go back to aosp based when tw starts to get laggy. But as most have said most likely a app causing your problem you should try install new Rom with all wipes inclueding preload I think thats what its called and make sure that media scan is not always running
Sent from my GT-N7000 using XDA Premium 4 mobile app

I'm pretty dependant on my camera for my kids. From my readings of AOSP threads, the camera app has never really worked well? Or am I misinformed?
Sent from my GT-N7000 using xda app-developers app

I do not use the camera that much, but i have not had problems with it.
Focal does crash for me and makes me reboob my phone.

Azeazezar said:
Really?
I thought my battery life was bad. 7h15m with 45 min screen time after charging my battery is at 67%
Click to expand...
Click to collapse
With a new battery original OEM just purchased yesterday, I am at 4h10m with 55 minutes screen time at 64%
This is much better.
Sent from my GT-N7000 using xda app-developers app

Just an update everyone:
I'm currently at 7h15m with 2 hours screentime.
The battery is at 38%
I will have to chalk this up to a worn battery being replaced by a real Samsung battery and not a knockoff 3rd party battery.
Sent from my GT-N7000 using xda app-developers app

Batteries make a big difference and as for cm roms and the camera they work great
Sent from my GT-N7000 using XDA Premium 4 mobile app

How about tying to read or post on the battery thread in Q&A instead of posting new threads in the wrong section?

This didn't start out as a battery discussion
Sent from my GT-N7000 using xda app-developers app

AndroidSlave said:
How about tying to read or post on the battery thread in Q&A instead of posting new threads in the wrong section?
Click to expand...
Click to collapse
JellybeanSandwich said:
This didn't start out as a battery discussion
Click to expand...
Click to collapse
How about reading the first post AndroidSlave?
What's this snarkyness that's infected xda?
Shure wasn't around back in the WM days.
This is and or was a very "General" issue with my phone, as i am still not entierely shure is a plain software issue.
However i've made the switch to a or the PA-rom out of desperation.
Still too early too tell, as it is first day after flash, but feels smoother.
What is driving me mad on PA is the lack of lockscreen-homebutton-torch.
Also a bit dissapointed in "Screen Mode" dynamic mode missing.
Missning SPen->screenshot->notetaking is bugging me aswell, but i'm shure ill find some replacement thing for that.
EDIT:
You, know what.
I apoligise if i posted this in the wrong place.
And no bad intentions towards you AndroidSlave.
I just feel that it's the place of a MOD and not of a user to make these claims.
Please just use the report button in if you feel like this, instead of posting a retorical question.

I know, right? What's up with the uninformed snark?
Sent from my GT-N7000 using xda app-developers app

Crazy battery drain when Idle

Hey guys, I am having issues with battery drain and not sure what to do, my note wil lose about 30% battery overnight(about 7-8 hours) and last night it lost about 50%
At first it said that google app used alot of battery so I disabled the reccomanded things online(it's location and such), now it isn't draining as much.
Also my location doesn't use GPS, at night I always have maximum reception and yet I lose alot of battery to cell reception, also the other 2 you can see in the picture.
Hope someone can help, and thank you!
{
"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"
}

Nearly the same problem since MM. Sometimes 4%/hour when laying next to my bed during the night.
Tried everything like Wifi choices. Something also keeps my phone awake for at least an hour.
I hate factory resetting....
Huib

herpi said:
Nearly the same problem since MM. Sometimes 4%/hour when laying next to my bed during the night.
Tried everything like Wifi choices. Something also keeps my phone awake for at least an hour.
I hate factory resetting....
Huib
Click to expand...
Click to collapse
Factory reset is about 2h of work for much better performance. Just do it - use Google Photos, back up other stuff to google drive and sync, and you're done.

AB__CD said:
Factory reset is about 2h of work for much better performance. Just do it - use Google Photos, back up other stuff to google drive and sync, and you're done.
Click to expand...
Click to collapse
Factory reset only helped me for a couple days. Just the other day I lost almost 75% overnight with minimal apps installed and debloated. I've tried many combinations of WiFi on/off, HD/WiFi calling on/off, but the drain always comes back. Factory stats and gsam don't show anything out of the ordinary. It's been like this since Marshmallow.

Shooperman said:
Factory reset only helped me for a couple days. Just the other day I lost almost 75% overnight with minimal apps installed and debloated. I've tried many combinations of WiFi on/off, HD/WiFi calling on/off, but the drain always comes back. Factory stats and gsam don't show anything out of the ordinary. It's been like this since Marshmallow.
Click to expand...
Click to collapse
Ever rooted or anything?

Did anyone facing these issues have any packages disabled before the update?
Sent from my SM-N920G using Tapatalk

AB__CD said:
Ever rooted or anything?
Click to expand...
Click to collapse
Nope, I'm on Verizon.
swarup.siddharth said:
Did anyone facing these issues have any packages disabled before the update?
Sent from my SM-N920G using Tapatalk
Click to expand...
Click to collapse
Nope, all packages enabled before accepting the MM update. I forgot to enable them for this last small OTA just the other day, but I haven't noticed a change.

That's surprising. I've had better standby after mm. Hardly 3% in an 8 hour night. 5.5 hours consistent screen on with relatively heavy usage.
Sent from my SM-N920G using Tapatalk

Shooperman said:
Nope, I'm on Verizon.
Nope, all packages enabled before accepting the MM update. I forgot to enable them for this last small OTA just the other day, but I haven't noticed a change.
Click to expand...
Click to collapse
Just wondering: what happens if you dont enable packages before accepting OTA? I've never been given an answer on that.
Sent from my SM-G930F using Tapatalk

Shooperman said:
Nope, I'm on Verizon.
Nope, all packages enabled before accepting the MM update. I forgot to enable them for this last small OTA just the other day, but I haven't noticed a change.
Click to expand...
Click to collapse
The only app that messed it up was Opera max. Saved me ton of data but messed up battery life exponentially.
Sent from my SM-N920G using Tapatalk

I would've done a factory reset if I knew for a fact it would help, hope someone will have a solution for us

AB__CD said:
Just wondering: what happens if you dont enable packages before accepting OTA? I've never been given an answer on that.
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
I'm assuming the update will fail. I would guess the OTA has some sort of check before installing.

Shooperman said:
I'm assuming the update will fail. I would guess the OTA has some sort of check before installing.
Click to expand...
Click to collapse
Didnt you mention you didnt enable the packages before accepting the last OTA? If so, how did that go?

I did a factory reset, it did not help in the end :\

I have the impression that completely stopping Location services makes a difference, inclusive this option to Scan wifi.
I now have, on idle(!) 2.1 % per hr loss. Sync still on and also Wifi. But no automatic updates.
Pls feedback about this
Huib

AB__CD said:
Didnt you mention you didnt enable the packages before accepting the last OTA? If so, how did that go?
Click to expand...
Click to collapse
Correct, I forgot to enable the disabled packages for the latest OTA from Verizon. Everything went fine, as far as I can tell, but it wasn't a "major" update (still 6.0.1, no version change/update), just a few bug fixes.

herpi said:
I have the impression that completely stopping Location services makes a difference, inclusive this option to Scan wifi.
I now have, on idle(!) 2.1 % per hr loss. Sync still on and also Wifi. But no automatic updates.
Pls feedback about this
Huib
Click to expand...
Click to collapse
I have disabled GPS and location is there any other options ?
SM-N920C cihazımdan Tapatalk kullanılarak gönderildi

Ozgurce said:
I have disabled GPS and location is there any other options ?
SM-N920C cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
Nope, if they are off they are off, I think.
HUib
---------- Post added at 09:59 AM ---------- Previous post was at 09:31 AM ----------
swarup.siddharth said:
That's surprising. I've had better standby after mm. Hardly 3% in an 8 hour night. 5.5 hours consistent screen on with relatively heavy usage.
Sent from my SM-N920G using Tapatalk
Click to expand...
Click to collapse
That is amazing, 0,375% per hour. I never in my life succeeded in that. Ok, with first Nokia maybe.
I sometimes got a .7% per hour drain,but that is my absolute minimum.
Huib

Yeah. On lp it was an easy ten percent + every night. I think the combination of package disabler and the dose on mm got something right going on.

Greenify
Hi guys, i'm actually from over on the s6 edge plus part of xda and a lot of us are having the same issue with idle battery drain
I fixed this on my s6 edge plus by installing greenify and activating aggressive doze. It's by no means a permanent fix but it does the job. Since the note 5 is like the s6 edge plus's brother in terms of hardware and similar software give this a go and let me know if it helps
Have a look at the screenshot i uploaded if you are unsure

App crashes and reboots

Anyone had apps crash / close not responding or phone reboots ?
Installed stability patch that was released but still getting reboots of os and app crashes.
Sent from my TA-1012 using Tapatalk

Nokia 8 bud
Sent from my TA-1012 using Tapatalk

Nope no problems here, everything runs clean and smooth. Maybe you should hard reset?

No issues here

No issues...

Lorditler. I'm no troll buddy. Sadly my Nokia 8 is going back. Crashes, reboots, smart lock doesn't work period.
I'm pretty gutted about it not being 100% from the get go.
Sent from my XT1572 using Tapatalk

I've had the odd app crash and reboot, I've got one more week to decide if I'm keeping it. Only thing is, I'm not sure there's anything else around that's going to be pure android with these specs for the same price. Pixel 2 is interesting, but likely to be £700+...

Smudger40 said:
I've had the odd app crash and reboot, I've got one more week to decide if I'm keeping it. Only thing is, I'm not sure there's anything else around that's going to be pure android with these specs for the same price. Pixel 2 is interesting, but likely to be £700+...
Click to expand...
Click to collapse
You sound like your exactly where I'm at smudger40. My phone arrived last wed so under DSR I've got a fortnight. After a fortnight I'm stuck with it for the next 2 years.
I'm after a near stock / totally stock android phone which leaves the pixel.
But like you I'm watching what price it is released at and with the fruity firm releasing a £1150 handset, what's not to say the pixel 2 hasn't suddenly gone up even more.
Like yourself I suspect it's going to be around £750 ish.
Which makes the Nokia a real bargain. My Nokia is going back so I'm covered under DSR and im just going to sit on the fence and see what pixel 2 looks like come oct.
And at that point i maybe re-order the nokia and hope I get a better one than the one I'm returning.
As for the X phone... I think this will open the flood gates to 3 year phone contracts to make the phone contract affordable or people are going to have to put 300-400 towards the handset cost.
Sent from my XT1572 using Tapatalk

I've had random reboots. Also issues with phone app and alarm. Phone app is being silent and unresponsive, alarm is just silent.

No issues here at all. Maybe try a factory reset and run with bare minimum a day or 2.
If it still happens it could very well be issues specific to your phone and you should be able to return it and get it either replaced or repaired.
My phone version is... Read below ?
Sent from my TA-1004 using Tapatalk

swejuggalo said:
No issues here at all. Maybe try a factory reset and run with bare minimum a day or 2.
If it still happens it could very well be issues specific to your phone and you should be able to return it and get it either replaced or repaired.
My phone version is... Read below
Sent from my TA-1004 using Tapatalk
Click to expand...
Click to collapse
Running a flagship phone with bare minimum? That makes no sense.
I have random reboots, phone app crashes on incoming calls, apps lag heavily, phone gets stuck in landscape mode.
Even the original ZTE Blade had better software than this. This is my first Nokia phone in 17 years and I will probably never get another one.

nuggeo said:
Running a flagship phone with bare minimum? That makes no sense.
I have random reboots, phone app crashes on incoming calls, apps lag heavily, phone gets stuck in landscape mode.
Even the original ZTE Blade had better software than this. This is my first Nokia phone in 17 years and I will probably never get another one.
Click to expand...
Click to collapse
The very least you can do is to factory reset and some basic trial and error... If the service workshop factory reset it and can't find issues they basically end up claiming you caused the problems. Gathering some proof makes them look like the idiot instead.
It could very well be hardware related since mine works perfectly. **** happens. No brand has 100% flawless phones.
Avoid Nokia if you must... But then avoid Samsung due to Note 7 aka Firestarter, Sony due to random reboots on my Z5 premium (that they fixed later), Apple due to critically flawed updates... The list can go rather large if you really put some time on finding reasons to avoid something.
Sent from my TA-1004 using Tapatalk
---------- Post added at 12:10 PM ---------- Previous post was at 11:48 AM ----------
A interesting question... All with issues is that TA-1012? Mine is TA-1004. Only issue I've seen is that I had Data Saver function enabled a few times automatically.
Sent from my TA-1004 using Tapatalk

No, I'm on TA1012 with no problems.

swejuggalo said:
The very least you can do is to factory reset and some basic trial and error... If the service workshop factory reset it and can't find issues they basically end up claiming you caused the problems. Gathering some proof makes them look like the idiot instead.
It could very well be hardware related since mine works perfectly. **** happens. No brand has 100% flawless phones.
Avoid Nokia if you must... But then avoid Samsung due to Note 7 aka Firestarter, Sony due to random reboots on my Z5 premium (that they fixed later), Apple due to critically flawed updates... The list can go rather large if you really put some time on finding reasons to avoid something.
Sent from my TA-1004 using Tapatalk
---------- Post added at 12:10 PM ---------- Previous post was at 11:48 AM ----------
A interesting question... All with issues is that TA-1012? Mine is TA-1004. Only issue I've seen is that I had Data Saver function enabled a few times automatically.
Sent from my TA-1004 using Tapatalk
Click to expand...
Click to collapse
Already am avoiding all brands you mentioned.

I really like the Nokia 8. Just what I really wanted but, mines not been right from the first day. However, having seen pics that were leaked last night of the pixel 2, I think that looks a proper minger. Then there's leaks of the Nokia 9 appearing every where.
Sitting this one out till Nov when either I go Nokia 8/9 or minger phone (pixel 2 XL) depending on how stupidly it is priced
Sent from my XT1572 using Tapatalk

Janzerfaust said:
I've had random reboots. Also issues with phone app and alarm. Phone app is being silent and unresponsive, alarm is just silent.
Click to expand...
Click to collapse
I have exactly the same issues, with the phone app crashing and alarm is silent sometimes, have you found a solution to your problem?

As others have not had this issue I've returned my handset to carrier. Awaiting a replacement bud
Sent from my XT1572 using Tapatalk

cpu-z crashes for me all the time.....ayone can give that app a try and report back please?

Thorgoth said:
cpu-z crashes for me all the time.....ayone can give that app a try and report back please?
Click to expand...
Click to collapse
Works fine @.my end
{
"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"
}