Database Users

[Discussion] Ava V10 battery life - Phone Specs

First off, this might be a topic for the general forum, but since is pertains directly to development, i thought i would put it here... Mods.. please move if you feel this is inappropriate.
There seems to be some HUGE differences with Ava v10 and battery life and i wanted to try and narrow down what the differences are to see what is up!
What i am curious about and would like you to post is the following:
Hardware Version
Screen
Kernel you are using
battery life / Usage
If we are seeing a pattern here then we should be able to determine the problem and hopefully yield some good data for devs to use. If it is still very random.. then its got to be an app that is causing the issues.

I will start
Hardware 003
Epson
Stock Kernel
8 - 9 hours MAX on moderate - use (lots of texting, some calls, and a little web browsing) Was getting WAY better on v9 before 3.30 update (v9a)

It is apparent the 3.30.2/3 has drastically ****ed battery life. There has been way too many posts about it to ignore it now.
It isn't HTC kernel 17 related like someone said earlier either. It goes deeper than that because I never run HTC kernels, not even for 5 minutes after installing a rom and I notice it very much. It appears that the current during idle isn't affected. And it isn't a rogue program PR anything keeping the CPU from idling. I dunno what it is. But it really is very noticeable.
I wish more dev's would realize it and make updated 3.29s with some of the new stuff built-in like the pnotification pulldown switch thing, and stuff like that.
Thanks azrael so far for not ignoring the situation. Lol. I'm sure HTC will put out a version 3.40.00 or whatever that has ackrite for all hardware versions. And then it will be easier on the devs

skydeaner said:
It is apparent the 3.30.2/3 has drastically ****ed battery life. There has been way too many posts about it to ignore it now.
It isn't HTC kernel 17 related like someone said earlier either. It goes deeper than that because I never run HTC kernels, not even for 5 minutes after installing a rom and I notice it very much. It appears that the current during idle isn't affected. And it isn't a rogue program PR anything keeping the CPU from idling. I dunno what it is. But it really is very noticeable.
I wish more dev's would realize it and make updated 3.29s with some of the new stuff built-in like the pnotification pulldown switch thing, and stuff like that.
Thanks azrael so far for not ignoring the situation. Lol. I'm sure HTC will put out a version 3.40.00 or whatever that has ackrite for all hardware versions. And then it will be easier on the devs
Click to expand...
Click to collapse
It seems only hardware version 0004 is mostly unaffected by the new frame software and I know the only difference is camera hardware but that may be it
Sent from my EVO at the edge of hell

Hardware: 003
Screen: not sure how to tell I am a newbie
stock kernel that comes with AVA V10
Right now I am home and not on the road working so my useage is lighter but I did go to bed last night with >50% life remaining and the phone had been off charger >15 hours
4-5 calls none were more than 5 min long
a little texting, couple emails (with polling every 30 min from 8-8), FB and Twitter updating at a regular interval (about every 30 min)
Bluetooth on for around 2 hrs, wifi on most of the day as I was at home using my home network so it was connected and not scanning.
Went to mall for about an hour and that has notoriously bad Sprint signal inside most places.

I ran the following:
hardware 002
Novatek screen
kernel: HTC 10, HTC 11, HTC 17, Kings #10 & #11 (both variants), Netarchy 4.1.9.1 & 4.2.1 beta (havs, no havs, bfs, cfs, smartass)
Some web browsing, facebook, texts, maybe 10-20 min of calls per day if that.
I'd get MAX 6-8 hours from fully charged to completely dead.
Went back to MIUI 11.19 and am consistently getting 15+ hours with moderate to heavy use.
If I try and run any ROM with the 3.30 file system, my battery totally sucks no matter which kernel I use.

Evo hardware version: 003
Screen Type: unknown (don't know how to tell)
3.30-ROMs tested: Ava V10, EViO 2
Kernels: various, in text
When I first switched to the first 3.30-based ROM, I noticed a big reduction in battery life. I tried another and ran into the same thing.
After one day on Ava V10, on a recommendation I tried the EViO 2 v1.6, along with the "netarchy-toastmod-4.2.1-bfs-bfq-nohavs-smartass-universal (No HAVS)" kernel, and with extremely light usage (1 short call, and few texts) after 19-hours I was showing an 89% charge. With this kernel the phone slept very well. The problem was that with that same kernel, even moderate usage sucked the battery very quickly.
So, based on things that I read I switched to the "netarchy-toastmod-4.2.1-bfs-bfq-havs-more-smartass-universal (More Aggressive Undervolting)". Using this combo, sitting on my desk with zero usage for 11-hours it was displaying 89% charge, so sleeping did not appear to be as efficient. However through the day, normal usage (moderate) seemed to provide a bit more time per charge. It did not appear to be a drastic difference.
On another recommendation, I then tried the netarchy-toastmod-4.1.9.1-cfs-NoHAVS-universal kernel. Overnight, no usage, after 9-hours I was again at 89% charge. Normal usage netted slightly worse time than the netarchy-toastmod-4.2.1-bfs-bfq-nohavs-smartass-universal (No HAVS) kernel provided.
Behavioral observation: The 4.2.1 No HAVS kernel produced slightly higher Quadrant scores than the 4.1.9.1 kernel did, but overall in normal operation, the phone was more sluggish and draggy on the 4.2.1 kernel, while being snappier and feeling faster overall using the 4.1.9.1 kernel.
Also, please note that the best battery time I ever got on any 3.30-based ROM pales in comparison to my experience earlier in the year with DC3.5 and an older Toastmod DC-compatible kernel. Once, after almost 21-hours off the charger, light usage throughout the night and at the very end of a 3+ hour phone call, I got the charge warning that I was at 15%. I don't know why I changed.
At this point I made an inquiry through a friend and was told that the difference between the 3.29-build and the 3.30-build was that the 3.30-build has a few small changes made to support hardware changes on version 004 Evo's only. I was also told that 3.30-build ROMs were not going to run well on 001-003 Evo's. I'm sure that is not absolute and they can be made to, but it may take some work.
Sorry for the novella, and I hope that it helps. Thank you for your time.

Hardware Version: 0003
Screen: EPSON
Kernel you are using: STOCK
battery life / Usage: MOD to HEAVY USAGE - OVER 25 HOURS on FIRST FULL CHARGE of battery!
NOTE: I also had AUTOKILLER set to STRICT during this entire time, and not to AGGRESSIVE.
Detailed post with pic showing my over 20 hour mark still in the GREEN:
HERE!!!
I'm now in the process of trying out Net-TM 4.2.1 CFS-HAVS-LESS AGG with V10.

bender1077 said:
Hardware Version: 0003
Screen: EPSON
Kernel you are using: STOCK
battery life / Usage: MOD to HEAVY USAGE - OVER 25 HOURS on FIRST FULL CHARGE of battery!
NOTE: I also had AUTOKILLER set to STRICT during this entire time, and not to AGGRESSIVE.
Detailed post with pic showing my over 20 hour mark still in the GREEN:
HERE!!!
I'm now in the process of trying out Net-TM 4.2.1 CFS-HAVS-LESS AGG with V10.
Click to expand...
Click to collapse
what was your "awake" time with this? This will be the tell.

When i ran ava 10 i got like 10 hours max. Alot of the 3.30 roms sucked my battery life. Fresh 3.3 rom gave me best battery life and i upgraded to his 3.4 and my bat sucked. Now im running airbourne rc4 and i think im getting the best battery I've ever had and its 3.30 based. It does have the sense launcher removed but all other sense is still there that could be the problem.
Novatek and 003

I decided to reload v10 and only restore a few essential apps and see where i was at. i did this, and had a full charge late last night.
This was with ALL settings defaulted to what is in v10 and no setcpu. The ONLY thing that i changed was the autokiller settings to "optimum"
It has now been 14.5 hours since i unplugged it (7 was me sleeping)
and "awake time" has only been 2.5 hours
It has been a pretty light day for usage - couple phone calls, mostly texts and emails and i am at 50%
This is MUCH better, but i really have not used my phone like i normally do. And this is with only a few apps installed.

frettfreak said:
what was your "awake" time with this? This will be the tell.
Click to expand...
Click to collapse
I think was a little over 5 hours. I'll have to remember to get a pic of that next time

bender1077 said:
I think was a little over 5 hours. I'll have to remember to get a pic of that next time
Click to expand...
Click to collapse
huh.. thats pretty good! lol... hmm..

a little off topic......how do you tell who made the screen on your EVO?

skydeaner said:
It is apparent the 3.30.2/3 has drastically ****ed battery life. There has been way too many posts about it to ignore it now.
It isn't HTC kernel 17 related like someone said earlier either. It goes deeper than that because I never run HTC kernels, not even for 5 minutes after installing a rom and I notice it very much. It appears that the current during idle isn't affected. And it isn't a rogue program PR anything keeping the CPU from idling. I dunno what it is. But it really is very noticeable.
I wish more dev's would realize it and make updated 3.29s with some of the new stuff built-in like the pnotification pulldown switch thing, and stuff like that.
Thanks azrael so far for not ignoring the situation. Lol. I'm sure HTC will put out a version 3.40.00 or whatever that has ackrite for all hardware versions. And then it will be easier on the devs
Click to expand...
Click to collapse
nYdGeo said:
...
At this point I made an inquiry through a friend and was told that the difference between the 3.29-build and the 3.30-build was that the 3.30-build has a few small changes made to support hardware changes on version 004 Evo's only. I was also told that 3.30-build ROMs were not going to run well on 001-003 Evo's. I'm sure that is not absolute and they can be made to, but it may take some work.
Sorry for the novella, and I hope that it helps. Thank you for your time.
Click to expand...
Click to collapse
So dont remember where I got this from (someone in another topic), but it completely confirms everything that we have been talking about...
NO 3.30 rom is made for hardware 001-003 period.. directly from sprint.
http://community.sprint.com/baw/com.../blog/2010/11/05/htc-evo-maintenance-releases
so the problem now is devs are either going to have to split their roms in to 2 branches (one for pre-004 hardware and one for 004 hardware) OR... sprint need to come out with a unified release. SO... hopefully devs will read this and make changes accordingly

Battery Life Testing - Kernel + Rom Combo's

Iv always considered battery life a very important factor in my purchasing of a phone and was one of the big reasons i moved from my Desire HD to the Nexus S (amongst many others). However having been on the android scene for a while im used to tinkering with kernels and roms etc and due to the new battery graph in gingerbread im now able to make direct comparisons rom by rom and kernel by kernel to see how they all differ. This is all shown + explained below.
First id like to explain my method;
I install the rom and kernel with the same apps I always use and charge the phone fully until i am about to go to sleep. I then unplug the phone and leave it in the exactly the same place on my desk with exactly the same settings (sync intervals etc) and i kill all apps before i leave it just to make sure the test is fair.
In the morning i then take a screen shot of the battery life over the period of usually 8 hours and will upload this for you to see. I then look at the over-night battery drain as a comparison on how good battery life is on specific roms and kernels.
Justification - Many of you may be thinking who cares about standby battery life? I care about the battery when im using it!?
Well although that's valid there are many reasons i have taken this approach;
1. It is completely fair i.e. no individual differences such as 'im a heavy user' but we all have different definitions of a 'heavy user'. This is eliminated by the fact the phone is not used and thus the same every time (no individual differences)
2. If a phone has severe battery drain during sleep general knowledge should dictate that battery drain should increase when the screen is on, cpu is working and your syncing your facebook wall, thus a direct correlation with sleep battery drain and usage drain should be apparent.
Therefore i have decided over the next few days/weeks etc i will upload on a regular basis a screenshot of the battery drain over night, along with the battery use details and screen on time etc etc. In addition to the rom and kernel info and i hope that over time this proves to be a very useful thread.
I have been doing this over the last few days on a less strict system and there have been some VERY interesting results which i will upload over the next few days.
(Just a final note iv never really done anything like this on xda before so if its a stupid idea then please tell me now so i dont waste my time doing it, however if people are really interested please let me know and il make sure i do my best!!)
Thanks for reading my extremely long post!
Bratfink
SCREENSHOT 1: This was using modacos custom rom r10 and the kernel that comes with it, i had quite a short sleep (about 6 hours) but the curve pretty much shows what the point im trying to make is. The battery life is great!!
SCREENSHOT 2: This is CM7 Nightly build 27# with Netarchy's latest 1.2.1 kernel and although i didnt use the screen once of charge for a few minutes as you can see once the screen was off battery life barely decreased and was over a long period of time.
If anyone wants me to test specific combos please let me know.

I'm actually looking forward to reading your results.
Sent from my Nexus S using XDA App

Yep, this would actually be pretty useful. Good luck and good work!

i'm a sucker for these types of tests, always love doing them and seeing the results. post soon!

I like others will be keeping an interested eye on your findings.

Uploading pictures of modaco r10 with it's own original kernel today. Its an interesting result!
Sent from my Nexus S using XDA App
Uploaded to OP

I'm interested too.

Can u try modaco r10 with Netarchy 1.2.1 kernel.
bratfink said:
Iv always considered battery life a very important factor in my purchasing of a phone and was one of the big reasons i moved from my Desire HD to the Nexus S (amongst many others). However having been on the android scene for a while im used to tinkering with kernels and roms etc and due to the new battery graph in gingerbread im now able to make direct comparisons rom by rom and kernel by kernel to see how they all differ. This is all shown + explained below.
First id like to explain my method;
I install the rom and kernel with the same apps I always use and charge the phone fully until i am about to go to sleep. I then unplug the phone and leave it in the exactly the same place on my desk with exactly the same settings (sync intervals etc) and i kill all apps before i leave it just to make sure the test is fair.
In the morning i then take a screen shot of the battery life over the period of usually 8 hours and will upload this for you to see. I then look at the over-night battery drain as a comparison on how good battery life is on specific roms and kernels.
Justification - Many of you may be thinking who cares about standby battery life? I care about the battery when im using it!?
Well although that's valid there are many reasons i have taken this approach;
1. It is completely fair i.e. no individual differences such as 'im a heavy user' but we all have different definitions of a 'heavy user'. This is eliminated by the fact the phone is not used and thus the same every time (no individual differences)
2. If a phone has severe battery drain during sleep general knowledge should dictate that battery drain should increase when the screen is on, cpu is working and your syncing your facebook wall, thus a direct correlation with sleep battery drain and usage drain should be apparent.
Therefore i have decided over the next few days/weeks etc i will upload on a regular basis a screenshot of the battery drain over night, along with the battery use details and screen on time etc etc. In addition to the rom and kernel info and i hope that over time this proves to be a very useful thread.
I have been doing this over the last few days on a less strict system and there have been some VERY interesting results which i will upload over the next few days.
(Just a final note iv never really done anything like this on xda before so if its a stupid idea then please tell me now so i dont waste my time doing it, however if people are really interested please let me know and il make sure i do my best!!)
Thanks for reading my extremely long post!
Bratfink
SCREENSHOT 1: This was using modacos custom rom r10 and the kernel that comes with it, i had quite a short sleep (about 6 hours) but the curve pretty much shows what the point im trying to make is. The battery life is great!!
If anyone wants me to test specific combos please let me know.
Click to expand...
Click to collapse
Sent from my Dell Streak using XDA App

I'd be interested in seeing CM7, just whatever nightly build you manage to catch.

I don't think that result will give you precise result.
I found that statistic is wrong sometimes.
It is better to measure using "play video loop".
So, find a movie, set to the same brightness and play in loop?

gogol said:
I don't think that result will give you precise result.
I found that statistic is wrong sometimes.
It is better to measure using "play video loop".
So, find a movie, set to the same brightness and play in loop?
Click to expand...
Click to collapse
Unfortunately that will not give you how well the rom does while it is idle.

I'm really looking forward to your results. My only issue with this phone is the battery life is terrible. I ordered an extended battery off Ebay 3 weeks ago and have yet to receive it. Never ordering anything from Hong Kong again!

Fuse8499 said:
I'm really looking forward to your results. My only issue with this phone is the battery life is terrible. I ordered an extended battery off Ebay 3 weeks ago and have yet to receive it. Never ordering anything from Hong Kong again!
Click to expand...
Click to collapse
What were you using before that you consider this phone to have bad battery life? By far this phone has the best battery life of any Android device I've owned. If you want bad battery life, get an Evo. That is horrific battery life.

bratfink said:
Uploading pictures of modaco r10 with it's own original kernel today. Its an interesting result!
Sent from my Nexus S using XDA App
Uploaded to OP
Click to expand...
Click to collapse
I am looking forward to the rest of these, however just a quick question. What was your battery use like in that situation with the stock ROM? Just for reference, because I'm thinking I might switch to modaco soon. Thanks!

More soon
Iv got a few more screenies but it seems i may have to end this thread prematurely. Its the SNS or 2.3 but idle battery usage for me is pretty much identical no matter what the kernel or rom (il upload a CM7 + Netarchy 1.2.1 shot top op). This was unexpected on my behalf because with my DHD kernels and roms had a big impact on idle battery consumption. I have noticed however that without a full wipe when changing some kernels such as with M r10 idle battery life can increase drastically. I will continue for the next few days and if i dont see any big changes i may move method to a video loop or something of the sort.

Interesting find
I found out something today that may interest may of you. I was messing around with the sleep profiles on SetCpu with netarchys kernel and i found that its better to leave the range from 100-800 than 100-400 or less. This i believe is because when the phone is asleep and carries out a process it will be forced to clock to the maximum of 400mhz and then stay at that speed for 10 seconds, instead of say going up to 800mhz for 1-2 seconds to complete the same process. So a tip to you would be set your profile to 100-800mhz conservative and see what you get!

bratfink said:
I found out something today that may interest may of you. I was messing around with the sleep profiles on SetCpu with netarchys kernel and i found that its better to leave the range from 100-800 than 100-400 or less. This i believe is because when the phone is asleep and carries out a process it will be forced to clock to the maximum of 400mhz and then stay at that speed for 10 seconds, instead of say going up to 800mhz for 1-2 seconds to complete the same process. So a tip to you would be set your profile to 100-800mhz conservative and see what you get!
Click to expand...
Click to collapse
This kinda enforces the point that SetCPU is useless for the NS unless you really want to overclock...
Any battery saving tactics used buy lowering screen off profiles are counteracted by the system process;( So i think in the context of battery life you are probably better to not use SetCPU
JD

bratfink said:
Iv got a few more screenies but it seems i may have to end this thread prematurely. Its the SNS or 2.3 but idle battery usage for me is pretty much identical no matter what the kernel or rom (il upload a CM7 + Netarchy 1.2.1 shot top op). This was unexpected on my behalf because with my DHD kernels and roms had a big impact on idle battery consumption. I have noticed however that without a full wipe when changing some kernels such as with M r10 idle battery life can increase drastically. I will continue for the next few days and if i dont see any big changes i may move method to a video loop or something of the sort.
Click to expand...
Click to collapse
I would definitely move to a video loop or some other 'heavy use' task because when you think about it, not too much can really be changed when almost no power is being used in the first place.
You could also just mention your general feeling for the battery life of each rom, because quite often that is what I go by as my usage varies depending on a range of things (school day or weekend etc) .
Sent from my Nexus S using XDA App

Could you please test modaco r10 with Netarchy's latest 1.2.1 kernel ?
I would love to see the difference between modaco's default kernel vs netarchy's kernel.

On CM nightly 13, I just went 11 hours and I'm at 90%. That's 1/2% an hour. Not bad. That is with stock kernel.
Sent from my Nexus S using Tapatalk

Sleep of Death (SOD's) - CM9 / Paranoid ROM - Mission to find a fix...

Hi All,
I am currently running the Paranoid v0.1 Tablet / Hybrid ROM which is based on CM9 and am one of the unlucky people who have been experiencing SOD's since flashing. I flashed the ROM 2 days ago and have experienced 5 SOD's since.
I want to be of help to those of you who may be experiencing these SOD's as well be it on a CM9 Nightly (I had MANY SOD's when I was running a straight CM9 nightly a couple weeks ago) or on the Paranoid or even any AOSP/AOKP ROM and thats why I started this thread.
What I have done thus far to try and fix this is...
- Flashed the newest Modem - LR1 which did not stop the SOD's
- Increased my minimum CPU Frequency from the default 200Mhz to 500Mhz (I was having similar issues running an AOKP ROM on my Galaxy Nexus and if I remember correctly, this was how I got them to stop) Since doing this I have not yet had another SOD and I will post my progress accordingly.
I hope that this thread will be of help to people so please post your own experiences and thoughts and possible solutions and lets find a fix (even a TEMP one) for this annoying little bug.

Brief update...
It has now been 3 hours since I changed my minimum cpu frequency from 200Mhz to 500Mhz and I have not yet suffered another SOD. I will continually update here on this...
Keep your fingers crossed...

LoL @ 500Mhz mini... Start buying spare batteries

Didn't help for me. As far as I can tell there is an error on which a specific finalizer class isn't included in the project. I saw it a while back on another thread in some user's log, but can't find it anymore.

luminouche said:
LoL @ 500Mhz mini... Start buying spare batteries
Click to expand...
Click to collapse
Actually... I have been using the phone under some mid to heavy usage since I switched the minimum cpu frequency (emails, texts, facebook, etc) and I have not noticed much difference in the battery life... I was at about 85% when I changed it which was approx. 4 hours ago and I am now at 77%... Not too bad I dont think...
Besides... Id much rather trade off a bit of battery if I can keep the device from SOD'ing.

alex3305 said:
Didn't help for me. As far as I can tell there is an error on which a specific finalizer class isn't included in the project. I saw it a while back on another thread in some user's log, but can't find it anymore.
Click to expand...
Click to collapse
Hmmmm... Well I have never heard anything quite like that and everyone I have heard from is telling me that these SOD's are just a very RANDOM occurrence and that there really is no known reason they happen. Apparently they happen to some people but not to others.
My reasoning behind increasing the minimum cpu frequency is based on what I have read others write about CM9, Paranoid, AOKP, etc NOT entering into "deep sleep". Again... This seems to happen for some people but not for others and I am assuming that perhaps me (and others experiencing these SOD's) have devices that ARE entering into "deep sleep" mode and that they are sleeping TOO deeply which is why they wont wake up where perhaps the people who are NOT experiencing the SOD's have devices that do not enter "deep sleep" mode at all.
I'm no technical genius or developer or anything but this just makes sense to me and for myself... I have still NOT had another SOD since I increased the minimum cpu speed. (KNOCK ON WOOD)!!!

I don't want to duplicate posts, but I posted in ParanoidAndroid because I got my first SOD today just a few minutes ago when I got home. Here is the post:
http://forum.xda-developers.com/showpost.php?p=26525255&postcount=1327
I uploaded the last_kmsg file to xda as well.

andreww88 said:
I don't want to duplicate posts, but I posted in ParanoidAndroid because I got my first SOD today just a few minutes ago when I got home. Here is the post:
http://forum.xda-developers.com/showpost.php?p=26525255&postcount=1327
I uploaded the last_kmsg file to xda as well.
Click to expand...
Click to collapse
****ty to hear you got an SOD my friend. My SOD's have happened while on Network data AND only once on wifi so I really don't think that the wifi has much to do with it but I may be wrong.
Unfortunately I have no idea what to look for in the last_kmsg file so I hope that someone who knows what it means will be able to understand and give us some insight.
On a brighter note I have still not had an SOD since increasing my min. CPU frequency to 500 MHz... Perhaps give it a whirl yourself if you start getting frequent SOD's starting now...
Sent from my GT-N7000 using xda premium

yiannisthegreek said:
****ty to hear you got an SOD my friend. My SOD's have happened while on Network data AND only once on wifi so I really don't think that the wifi has much to do with it but I may be wrong.
Unfortunately I have no idea what to look for in the last_kmsg file so I hope that someone who knows what it means will be able to understand and give us some insight.
On a brighter note I have still not had an SOD since increasing my min. CPU frequency to 500 MHz... Perhaps give it a whirl yourself if you start getting frequent SOD's starting now...
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I might give it a whirl if I do have more than one SOD. But, I turned my wifi back off and on data and no SODs right now. Maybe it was just a rare bird lol. I might try turning on wifi in a few and see if it will duplicate.

andreww88 said:
I might give it a whirl if I do have more than one SOD. But, I turned my wifi back off and on data and no SODs right now. Maybe it was just a rare bird lol. I might try turning on wifi in a few and see if it will duplicate.
Click to expand...
Click to collapse
Keep me and the thread posted man. Lets see if we can get rid of this bug...

I use to get many SOD's while on CM9, and the only thing that permanently stopped it was using an app called wakelock. It basically didnt let the phone go into deep sleep mode, avoiding the problem entirely. Also battey life was not badly effected. Standby used almost double battery but my phone lasted the entire day regardless.
However, since I do believe its a kernel problem, I think we should get a fix in the near future since the iCS kernel sources have been released by samsung. So maybe some dev will be able to build a proper kernel for these roms which is not effected by the bug.

Well, I have been on data all night and not a single SOD......
The only time I got it was when I turned on the wifi. I haven't tried turning wifi back on now.

I've been using various updates of CM9 since v7, and have had at most 5 SODs in the past few weeks. Only 1 happened while I was using the phone. The only consistent thing about those experiences was that none of them were while the phone was charging.

Setting to 500 min didnt help me.
My phone has been perfect all night running from mains electricity. Within 2 hours of running on battery SOD.
Last KMSG
My List of installed APPS

I don't think it's ROM related. I've had SOD's on most ICS ROMs. Some get it, some don't. So it has to be the way some setup their device and choice of software installed.
Some suggested tests:
1. Uninstall any type of battery optimizer or WIFI switcher
2. Factory reset, and run the ROM for a day without any additional software to see if you get SODs
3, Disable WIFI for a day and see if you get SODs
4. Set WIFI to be on all the time and see if it helps.
5. If all SOD sufferers can dump the list of installed software and see what stuff is in common.
In my case, it was Green Power (other battery optimizers gave the same results) to control WIFI/Data, Once removed over a month ago, SOD's stopped.
Hope this helps.

tamarian said:
I don't think it's ROM related. I've had SOD's on most ICS ROMs. Some get it, some don't. So it has to be the way some setup their device and choice of software installed.
Some suggested tests:
1. Uninstall any type of battery optimizer or WIFI switcher
2. Factory reset, and run the ROM for a day without any additional software to see if you get SODs
3, Disable WIFI for a day and see if you get SODs
4. Set WIFI to be on all the time and see if it helps.
5. If all SOD sufferers can dump the list of installed software and see what stuff is in common.
In my case, it was Green Power (other battery optimizers gave the same results) to control WIFI/Data, Once removed over a month ago, SOD's stopped.
Hope this helps.
Click to expand...
Click to collapse
Not true. I tested a clean CM9 install with 0 apps installed. All I did was link it to my google account. Still had SOD. Wifi turned off all the time. Data connection H+ acticated all the time. As stated before I had exactly the same SOD on imilkas LP1 kernel. When he moved source to LP5 kernel the SODs vanished. So a change in those kernels fixed the SOD.
I have now enabled the smartassv2 CPU gov in CM9. Lets see what happens now. I aint got nothing to lose
Oh and I set a digit password to unlock my phone. Wonder if that has anything to do with it as I have never tested CM9 without a password.

From this morning. Running 24 Nightly with loud speaker fix

Flashing ZCLP1 solved this issue on PA 0.1
I flashed ZCLP1 modem version and I am not getting any SOD's.

off topic
ahh
since you are on CM9 you can always go back to Stock GB
would not that solve the problem ... ?

ahmad zuman said:
ahh
since you are on CM9 you can always go back to Stock GB
would not that solve the problem ... ?
Click to expand...
Click to collapse
I suppose, but that's not worth the price...

Curious observation in battery life on ICS LQ3

I have noticed accidentally yesterday that after I had my stock headphones pluggeed in the Note, the typical curve of the battery drain became much flatter and the different wakes during screen off have almost disappeared. The moment I unplugged the headphones, the battery drain went back to the usual 2-3% per hour on standby.
I am running stock LQ3 and stock kernel. I am rooted, as I have flashed it through Mobile ODIN, over stock, rooted LPY.
I have quite a lot sync-accounts - twitter, facebook, gmail, email, weather widget etc. so I am quite used to relatively short battery life but the trick with the headphones came as quite a surprise.
Before writing this post I decided to test it today as well and it is the same.
So, could someone test this and report? I think that if this proves to be true and common, the devs could easily track what's happening exactly and sort things out, so that battery can live longer without the headphones plugged in.

boboev said:
Before writing this post I decided to test it today as well and it is the same.
Click to expand...
Click to collapse
Maybe before writing this post you should also have asked yourself, Did I develop something here or am I asking a question?
http://forum.xda-developers.com/showthread.php?t=1365099

Wrong section
Ugh...I am terribly sorry, this was meant for the General Discussion. Please, admin, move it there.

I've noticed that same if the SAR of the last samsung mobile is very low, the reception is quite good compared to other phones.
Do you notice also an improvement of the signal reception? Because if it is the case, it is that your headphones are used as a secondary antenna, giving the phone a stronger reception and less power consumption (better signal = less need of power usage for processing the signal)
This is just a theory...

After some ICS ROMs I went back to Gingerbread, mainly due to poor battery life.
When Litening ROM 2.0 was published I flashed that one. I liked the GB version a lot. The battery life was remarkable, a lot better than previous ICS ROMs. Because Litening is not much supported I tried Alba, also LQ3. A surprise because battery life was the same. I think I'll stick to ICS this time.

Opperhoofd said:
I tried Alba, also LQ3. A surprise because battery life was the same.
Click to expand...
Click to collapse
Alba often uses LB2 modem (from GB) in his ROMs - maybe it is the reason. I myself observed huge batterey drain on latest ICS ROMs while connected to Wi-Fi at my workplace. Fixed it by flashing ZCLP5 modem (from early "LP5 leak" ROM).

kitsune44fr said:
I've noticed that same if the SAR of the last samsung mobile is very low, the reception is quite good compared to other phones.
Do you notice also an improvement of the signal reception? Because if it is the case, it is that your headphones are used as a secondary antenna, giving the phone a stronger reception and less power consumption (better signal = less need of power usage for processing the signal)
This is just a theory...
Click to expand...
Click to collapse
Hm, that is an interesting theory. I am not sure, however, that the headphones' cable really improves GSM radio reception. I think it is only for FM reception. Of course I have no knowledge behind that, just thinking.
I have frozen lots or apps in Titanuim Backup like:
- the whole range of SNS's
- Social Hub
- Wi-fi sharing manager
- the infamous wssyncmlnps
- software update service, etc
Also I have stopped a bunch of receivers, using Autorun Manager Pro, and disabled a lot of processes from Autostarts.
This should mean that I have opted out the most common battery drainers. I have tried to disable auto-sync for the time being, but that does not seem to be much of a drainer, so maybe the real problem comes somewhere from the modem.

dimcus said:
Alba often uses LB2 modem (from GB) in his ROMs - maybe it is the reason. I myself observed huge batterey drain on latest ICS ROMs while connected to Wi-Fi at my workplace. Fixed it by flashing ZCLP5 modem (from early "LP5 leak" ROM).
Click to expand...
Click to collapse
Hey dimcus, i've been having this WiFi vs battery issues with some routers(including the one at home), weird enough it doesn't happen on some of them. I did read somewhere about flashing te Modem file, what leads me to a couple of questions ir you don't mind. Are you on ICS? Do i need to be root to flash the Modem file? If not, any risks involved? I'm on stock ICS LPY DBT.
Thanks in advance,
VR

I flashed the ZCLP6 modem earlier today, guessing that it would be better than ZCLP5.
It is too early to judge but first impressions are that maybe there is a slight improvement in battery on 3G but not something worth it over the stock XXLPT that I used to have and generally battery drain on wifi seems as bad as it has been ever since I flashed ICS.
I have read that some people dared to wipe their Notes and after that most of the problems had disappeared but I don't want to risk getting some brick.
I will try several other popular modems and will report back.
Sent from my GT-N7000 using Tapatalk 2

boboev said:
I flashed the ZCLP6 modem earlier today, guessing that it would be better than ZCLP5.
It is too early to judge but first impressions are that maybe there is a slight improvement in battery on 3G but not something worth it over the stock XXLPT that I used to have and generally battery drain on wifi seems as bad as it has been ever since I flashed ICS.
I have read that some people dared to wipe their Notes and after that most of the problems had disappeared but I don't want to risk getting some brick.
I will try several other popular modems and will report back.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Hey, did you have the same issues? The orange arrow(th download ONE) keeps going on and off all the time, happened in most routers i've tried. So any help will be more than welcome...
Cheers,
VR

boboev said:
I flashed the ZCLP6 modem earlier today, guessing that it would be better than ZCLP5.
It is too early to judge but first impressions are that maybe there is a slight improvement in battery on 3G but not something worth it over the stock XXLPT that I used to have and generally battery drain on wifi seems as bad as it has been ever since I flashed ICS.
I have read that some people dared to wipe their Notes and after that most of the problems had disappeared but I don't want to risk getting some brick.
I will try several other popular modems and will report back.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Please let us know how you get on with them. Currently on LR1 modem and noticing a few strange wakelocks.

I have been with LR1 modem for about 40 hours now. What is better than the ones before is the much better behaviour on wi-fi. Other than that it is hard to tell any differences. So far 7 hours since unplugged, 1 h screen-on, half time wifi, half time 3g - battery is at 75%
Sent from my GT-N7000 using Tapatalk 2

boboev said:
I have been with LR1 modem for about 40 hours now. What is better than the ones before is the much better behaviour on wi-fi. Other than that it is hard to tell any differences. So far 7 hours since unplugged, 1 h screen-on, half time wifi, half time 3g - battery is at 75%
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
wow.. that;s great.. i upgraded to ICS 5 days ago.. super poor battery..
then I heard to go with speedmod kernel, which I did.
no change..
Can you'se tell HOW TO change the modem?? I need to do something... mine just dont last worth a crap.. half day..
should I try a modem? and can you please say how to do just the modem??.
my baseband is N7000XXLPT
and build # is IML74K.XXLPY
thank you!

Unfortunately after several different ICS Roms (From Stock LPY to Cleanote 2.20) with several different Kernels (Stock, SpeedMod, Goku and more) and few modems (XXLPT, ZCLP5) I had to go back to Ginger due to extremely poor battery life. With all roms /kernels/modems combination the behavior was very similar. The phone was going into deep sleep pretty easily when idle with very low battery drain. On the other hand when using the phone I was getting about 10% drain each 20 minutes (A little less with data wifi and all sync off). I was also getting overheating with temp most of the times over 40 deg C. This drain was almost the same even with system energy savings on. I could not understand the reason for this strange behavior considering that many other users are having great battery life on ICS with their devices. Anyone is experiencing this situation ? NB now with Ginger the battery life is ok.

^ I experience same behaviors...

vessk0 said:
^ I experience same behaviors...
Click to expand...
Click to collapse
Hi
Do you by any chance have a German Note ? Mine is German and I was wondering if all the German notes had the same behaviour ..
Thanks

Battery drain with cm10 paranoid android
I am facing a huge battery drain issue. Used the phone for downloading and playing games and general usage yesterday and battery only lasted 3.5 Hours. Need to continuously watch the battery as it drops about 10-20% on idle. Checked the wakelocks and mainly wifi related, the phone is going into deep sleep just fine. HELP PLEASE!!!

lol continuously watching means you're the wake lock.
btw phone only has 3-3.5 hour screen on time. When playing games its usually less.
All do some reading into analyzing battery life betterbatterystats and cpu spy
Sent with L0VE

[Q] Strange battery behavior following software update

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.