On Pure Nexus rom with EX kernel, my battery indicator drops 2% at a time.. Is there any fix for this?
I'm getting this too. Its annoying find any fix ?
I'm having this with PureNexus and Franco. So is it kernel or ROM related?
I'm not 100% sure but I think I heard about this in a different thread, try to dirty flash ROM + Kernel and wipe dalvik + cache before reboot.
Regards,
I'll give this a go and let you know
Not seeing this with Pure Nexus 2/3 build & Franco r9 kernel. Clean flashed tonight
Sent from my Nexus 6P using Tapatalk
I was having the same issue after flashing PureNexus + ElementalX Kernel, then I thought going back to stock (completely unrooted) would fix this issue entirely, but unfortunately the problem still persists. The fellows at Google suggested me to wipe the device cache which supposedly would fix it, will see how that goes.
I'm actually seeing this now and have tried wiping cache. Not really concerning for me since it's just a reporting issue (battery life isn't affected)
Sent from my Nexus 6P using Tapatalk
Bump this tread i have same useuses i factory rest the latest 6.0.1 and android N W firmware all stock same hapend first 100%-90% ok 1% drop the after that its 1% drop then in 5 seconds andother % drop i thoth its a N devoloper bug but its not have same on stable M build shood i wory about?
I also have this issue with the latest Pure Nexus and ElementalX. Battery life does not seem very good but perhaps it's just something wrong with the battery indicator?
nds850 said:
I also have this issue with the latest Pure Nexus and ElementalX. Battery life does not seem very good but perhaps it's just something wrong with the battery indicator?
Click to expand...
Click to collapse
does its was ok before i just bought used nexus 6p week ago so i very nevous about it i was thinking its N preview doing this but its not
Seems to be a Google bug that happens to some users. Haven't found a solution yet but we´re not alone.
Happening here too on stock latest 6.0.1 firmware
Enviado desde mi Nexus 6P mediante Tapatalk
It's a 6p bug
Sorry for necroposting. Same problem here with N5X all stock, MM 6.0.1
I'm having the same problem here, started while using stock then I tried to flash CM but it didn't fix it, flashed stock again today, still happening
But the problem here also is that it's greatly affecting my battery life
I have the same priblem Pure nexus EX kernel twice clean flashing and the same.
It had been reported many times
Its a 6p bug
Even i have faced it
Some users have claimed that N had fixed that
I'm still on DU and have this since day 1 i had this device
Cheers
I have this problem on my 5X too, like i said.
I have this issue but I take it I just a software issue, if it was fixed the battery life wouldnt be any different
It stays at a number for a long time then it drops by two
Related
Kernels no longer work for me. I was running _Motley's build 49 kernel and the stock ROM for a few months and never had any issues and had excellent battery life. Then I decided to flash PA and _Motley to give Halo a try and noticed my battery wasn't all too great. I then nandroid back to my previous setup and then my battery life went to ****. Android OS was my biggest drain so I reflashed my stock rooted ROM and kernel and still had the same issue.
Then I flashed Faux's reset kernel and was stuck in a boot loop but was unable to get past the Google logo. Flashed another reset kernel, can't remember who's, and everything was fine. Android OS wasn't an issue anymore but my battery life went back to being mediocre. So I tried flashing other kernels, _Motley's included, and Android OS would still be on top.
So for some reason, only the stock kernel is working for me. Any ideas why? I'm about to just restore the factory image and start over again. I heard PA uses a custom kernel from Franco so could that be why I'm having issues?
Edit: I also fully charged my battery and left it overnight unplugged last night and went from 100%-64% in 8 hours
Sent from my Nexus 4 using xda app-developers app
Hero_Guy said:
Kernels no longer work for me. I was running _Motley's build 49 kernel and the stock ROM for a few months and never had any issues and had excellent battery life. Then I decided to flash PA and _Motley to give Halo a try and noticed my battery wasn't all too great. I then nandroid back to my previous setup and then my battery life went to ****. Android OS was my biggest drain so I reflashed my stock rooted ROM and kernel and still had the same issue.
Then I flashed Faux's reset kernel and was stuck in a boot loop but was unable to get past the Google logo. Flashed another reset kernel, can't remember who's, and everything was fine. Android OS wasn't an issue anymore but my battery life went back to being mediocre. So I tried flashing other kernels, _Motley's included, and Android OS would still be on top.
So for some reason, only the stock kernel is working for me. Any ideas why? I'm about to just restore the factory image and start over again. I heard PA uses a custom kernel from Franco so could that be why I'm having issues?
I also fully charged my battery and left it overnight unplugged last night and went from 100%-64% in about 8 hours.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Here's a logcat
Hey, i just want to know your opinions about why is better CM11S or why is better the latest CM12 Bacon Nightly ( cm-12-20150128-NIGHTLY-bacon)
I'm not trying to be a spoiler, but seriously, when it's so easy to do a nandroid backup and flash CM12, why not just try it? The only slight hassle is having to flash the old firmware if you decide to go back, but even that's not hard if you know how to use fasboot / recovery / flash ROMs.
And to answer your question, it's better because it's Lollipop, a step forward.
Bottom line: there is only one way for you to know.
As the above post said try it but myself i went back to cm11 as i tried every cm12 rom plus different kernals and my device would still be awake in wakelock app went back to mahdi rom with ak kernal and all good. still early stages for cm12 and cant wait to go back but will wait for a while
pro4ever said:
As the above post said try it but myself i went back to cm11 as i tried every cm12 rom plus different kernals and my device would still be awake in wakelock app went back to mahdi rom with ak kernal and all good. still early stages for cm12 and cant wait to go back but will wait for a while
Click to expand...
Click to collapse
Your problems have nothing to do with the cm12 nightlies "early stage".
Using cm12 since unofficial builds in december. There were some problems,
but not the battery life. It is the same as on cm11 for me.
Thats good news for you but since going back to cm11 my device goes deep sleep im happy
AcmE85 said:
Your problems have nothing to do with the cm12 nightlies "early stage".
Using cm12 since unofficial builds in december. There were some problems,
but not the battery life. It is the same as on cm11 for me.
Click to expand...
Click to collapse
Agreed. I had some wakelock issues in a build back in December or early January, but none since.
May i ask you guys acme85 and cafekampuchia what cm12 rom they have been using and kernal plz
pro4ever said:
May i ask you guys acme85 and cafekampuchia what cm12 rom they have been using and kernal plz
Click to expand...
Click to collapse
I use official CM12 nightlies with stock kernel and no mods. I dirty flash, but clear cache / ART cache with every nightly.
pro4ever said:
May i ask you guys acme85 and cafekampuchia what cm12 rom they have been using and kernal plz
Click to expand...
Click to collapse
Official CM12 Nightlies with stock kernel.
If you ask me ALL kernels are overrated in terms of battery life, but that is just my opinion (after some testing).
It is funny though how some users with custom kernels are undervolting and underclocking their
devices and yet never achieve the same battery life I get with all stock.
Some even claim that there device is more fluid than stock with kernel x or y. :laugh:
If you are into multirom or perhaps display color calibration then sure, a custom kernel is the way to go.
btw, I don't use greenify, I don't block play services wake permissions, I don't use the facebook app.
AcmE85 said:
Official CM12 Nightlies with stock kernel.
If you ask me ALL kernels are overrated in terms of battery life, but that is just my opinion (after some testing).
It is funny though how some users with custom kernels are undervolting and underclocking their
devices and yet never achieve the same battery life I get with all stock.
Some even claim that there device is more fluid than stock with kernel x or y. :laugh:
If you are into multirom or perhaps display color calibration then sure, a custom kernel is the way to go.
btw, I don't use greenify, I don't block play services wake permissions, I don't use the facebook app.
Click to expand...
Click to collapse
Tnx for both your replys I've always used cm 12 with custom kernels. Will try with stock and see how it goes
I reverted back to stock 44S after trying CM12 in Nov, was too unstable back then. Seems people are getting stable experience from CM12 now, think I am gonna flashing it later today
Thanks all!
I've gone from 11s to 12 to 11 again. Cm12 is stable but does have a few annoying bugs. The one that annoyed me the most was the audio buzzing bug. Many say enable the phone to always have 2 cores on, but that never fixed my issue. Buzzing always happened. Then there was the proximity issue which van be fixed by flashing a new firmware and modem but my phone doesn't take the modem. Lost lte and signal kept dropping every 3 minutes. Also had an issue when I was in a call, I often was a unable to hear the person. Only had to enable speaker and then Disable it again. That was the icing on the cake so I went back to cm11s. Now here I can say that battery life is almost identical. Just ever so slightly better on lollipop for me. The system is not as smooth specially with scrolling. I have scroll lag on instagram and Facebook again (minimal but noticeable) system, for a stock rom, isn't really too stable. Had the phone crash on me and when I turned it back on, it asked me to re set up the device but data was still in tac. So yeah. That's pretty much it.
Sent from my A0001 using Tapatalk
Have tried CM12 nightly, and back to 44s because one game that I like didn't run smooth . I think ART cause this, been trying on CM12 unofficial builds also, same result. Maybe the game hasn't updated for lollipop yet.
I installed loillipop 5.1, from scratch using the factory image. All went smooth and the performance was much better than with 5.0.2 (which was my previous version), but I have random reboots unless I stay connected to the wall. This can be easily reproduced by putting the tablet to sleep (i.e., I pressing power button). Immediately my nexus reboots (99% of times).
I tried everything possible. Factory reset. Reistalled after formatting every possible partition. Reistalled starting from scratch without using my google backups. Nothing helps.
The only solution was to come back to 5.0.2 (again through the factory images, flashing and formatting everything).
Last test I am going to do is to use the OTA to go from 5.0.2 to 5.1 but I do not have much hope.
Anyone else experiencing similar problems?
It looks like an hardware issue put in evidence by the new kernel that is part of 5.1, but it could eb enything else.
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Thanks for the suggestion, I didn't know Franco had released a version of his kernel for 5.1. I tried latest M-Kernel but it is not working with 5.1. Now I am sideloading the OTA from a stable 5..0.2, just to see if going to 5.1 using OTA helps. Will report if I succeed and in case I didn't will try with FK (and report).
Meanwhile, any other suggestion is welcome
Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Current situation after some more tests:
5.0.2 from factory image (full wipe): works
5.0.2 -> 5.1 via OTA: reboot each time goes to sleep (unless wall powered or attached to PC USB)
5.1 from factory image (full wipe): same as above
rastapop 5.1 (full wipe): same as above
5.1 + franco kernel R82: same as above
I would try to increase CPU voltage: any suggestion how to do? Which kernel to use? Which app to adjust voltages? I am going to try with franco kernel and trickstermod (which I already bought) but I am not sure this combination will allow me to adjust voltages.
EDIT: no way to adjust voltages with FK for 5.1. Reverting back to 5.0.2 and waiting someone gives suggestions or has similar issues (or releases new kernels)
Sideload 5.1, same issue. Even worse than 5.0.2.
Sent from my Nexus 7 using XDA Free mobile app
killerfrank said:
Sideload 5.1, same issue. Even worse than 5.0.2.
Click to expand...
Click to collapse
Even in your case the device reboots just after entering sleep mode? Please confirm, I thought I was the only one, but if this happens to others then it must be a software issue, not hardware.
This does not happen at all to me(using stock 5.1 with Franco Kernel).
This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.
_Hobbz said:
This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.
Click to expand...
Click to collapse
It looks like a mixed hw/sw problem. It is indeed clear that 5.1 works on most N7, either being installed from factory images or after an OTA upgrade, but for some of us it results in rebooting when the machine goes to sleep.
I attached last_kmsg (/proc/last_kmsg) just after the problem manifested. This is exactly what happens every time I put the device to sleep (pressing the power button or leaving it alone for a couple of minutes) and it repeats always the same (with the same kmsg).
Anyone knows how to extract other information that could be useful to isolate the source of the problem? Notice that I cannot do a catlog since the device doesn't go to sleep if it is connected to a PC (so I cannot recreate the problem).
Your battery is dying, I've been getting the same problem until I replaced the battery today.
richarddwyer10 said:
Your battery is dying, I've been getting the same problem until I replaced the battery today.
Click to expand...
Click to collapse
A hardware problem related with the power unit of the device was also my first hypothesis, but under 5.0.2 i everything works perfectly and the battery has the original duration. Under 5.1 also everything works... until the device goes to sleep. Only then it reboots.
Was this the behavior in your case?
I've been getting the same issues on my N7 since updating.
regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....
ondoy1943 said:
regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....
Click to expand...
Click to collapse
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.
gianpaoloc said:
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.
Click to expand...
Click to collapse
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.
_Hobbz said:
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.
Click to expand...
Click to collapse
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks
I've given up on LP for the N7. I've gone back to KK. Stability is awesome, performance is great. LP was a disaster on the N7. Performance issues, lock ups, etc. No matter how many times I clean installed it, etc, it just wasn't good.
I'm now officially calling it Lollipoop (at least for the 2012 N7). But, it is an old device. I'm still waiting to see how it turns out on my LG G3 phone. I'm sticking with KK on that phone as well for now until I know for sure it runs well on it.
Stability over bleeding edge.
Hi
JFYI, I have just updated my 2 sons' N7 2012 (coming from Omnirom) to Lollipop 5.1 (with Nexus Root Toolkit v2.0.4, meaning following the same procedure)
- 1 of them fine
- 2nd one with the issue reported here; which is why I'm on this thread now
updated kernel to franco r82
the issue remains...
will keep checking this thread
thansk
beng
gianpaoloc said:
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks
Click to expand...
Click to collapse
So I can't post links yet because of my low number of forum posts but if you google 'nexus help after update to 5.1, it won't wake up after in sleep mode, please help' then it should be the first result that shows up.
Things were running fairly well for me with the slimkat 5.0.2 rom on F2FS so I'll likely switch back to that while this gets sorted out.
I've had my n7 for 2 years now, flashed all kinds of custom Roms, bricked it, fixed it, encrypted it, unencrypted it several times, and It has never ran as slow as it did on lollipop. I tried, 5.0, 5.0.2, and 5.1 I even reset kk to stock and let the ota's do the job and no matter what, LP is still not usable in my opinion. I feel sorry for the people that take the ota and do not know how to revert back to kk.
Sent from my Nexus 7 using Tapatalk
I'm planning to downgrade to MM due to the hideous Android OS and Android System battery draining. Getting hardly 2 hours of SOT with very light use. Anyway I know that I'll have to flash the factory image but there are a lot of model types and I don't know which to download. So how do I know the variant and is there a difference between them and is there a certain model famous for the battery drain bug while the others are working fine?
Ghand0ur said:
I'm planning to downgrade to MM due to the hideous Android OS and Android System battery draining. Getting hardly 2 hours of SOT with very light use. Anyway I know that I'll have to flash the factory image but there are a lot of model types and I don't know which to download. So how do I know the variant and is there a difference between them and is there a certain model famous for the battery drain bug while the others are working fine?
Click to expand...
Click to collapse
If you are going down to Marshmallow surely just go to the last version of MM
https://developers.google.com/android/images#angler
Grab - 6.0.1 (MTC20L)
I don't think battery drain was that much of an issue on MM but could be wrong, someone else may recommend a different build but i'd go with the last build. before nougat.
brichardson1991 said:
If you are going down to Marshmallow surely just go to the last version of MM
https://developers.google.com/android/images#angler
Grab - 6.0.1 (MTC20L)
I don't think battery drain was that much of an issue on MM but could be wrong, someone else may recommend a different build but i'd go with the last build. before nougat.
Click to expand...
Click to collapse
There have been rumors about a bricks while downgrading?
I am not rooted , no custom recovery, unlocked bootloader. So that should be okay right?
Can't see how bricking is possible. Unlock, flash, lock. Done a thousand times.
Skickat från min iPhone med Tapatalk
I downgraded using the listed build with no issues. Battery issues appear to be resolved too. Can't get over how poorly optimised 7.1.1 was.
Regards.
Sent from my Nexus 6P using Tapatalk
You will be fine use the instructions on the sticky by Heisenberg and just use the files from that zip of the build i mentioned.
Hey, guys.
I want to downgrade to MM too because of the same battery drain reason. I'm running the latest PureNexus 7.0
I was on RR before. I'm rooted, unlocked, latest TWRP. Can I just flash my old RR Rom and the MM vendor image?
Holy Hell... I come here periodically to check whether battery drain has been solved. One of the reasons I chose a Nexus for was to get timely security updates. Tying them to a sub-par version of the OS ends up negating the advantage for me. How can Google mess up battery so much, after all the talk about battery life improvements with Nougat?
gorman42 said:
Holy Hell... I come here periodically to check whether battery drain has been solved. One of the reasons I chose a Nexus for was to get timely security updates. Tying them to a sub-par version of the OS ends up negating the advantage for me. How can Google mess up battery so much, after all the talk about battery life improvements with Nougat?
Click to expand...
Click to collapse
They were to busy with the pixel to care about providing to Nexus owners.
On topic I used the above factory image to downgrade my completely stock, locked, and not rooted 6P without issues.
Sent from my Nexus 6P using Tapatalk
For the record, I just flashed the MM vendor image and RR rom via TWRP and everything booted just fine and is running smooth. Didn't have to flash the stock rom. I'll just leave this here in case there's someone else looking for a solution
Hello Community,
im from Germany, so don't judge me if my english skills are not that good.
So here is my problem.
I couldnt wait for the new nougat update. I decided to flash the beta 3 i guess with odin. Everything has gone right, the battery life was perfect, the performance great, everything was really smooth until i tried to get twrp on it. Ive got an endless bootloop. I flashed nougat again and everything was great. However now my battery life is the worst. I charged it to 70% it dropped down to 5% in like 3,5 hours ? I have nothing installed except whatsapp and the XDA App. I deactivated facebook, galaxy store and every bloatware.
It took about 2 hours to get from 5% to 32% with the fast charge enabled. When disabled it took longer.
i have wiped the cache section and nothing helped. I wiped all data and installed my backup from smart switch ive done befor i wiped everything.
Please i need help, im afraid that i broke my battery.
Samsung S7 Edge G935F Exynos
G935FXXU1ZPK1
Kernel
3.18.14-9658725
[email protected]#1
Fri Nov 4 19:48:33 KST 2016
Buildnumber
NRD90M.G935FXXU1ZPK4
SE for Android Status
Enforcing
SEPF-SECMOBILE_7.0_0002
Android Security Patch
1. October 2016
I dont think you have made it kapput. Flash the stock firmware back and see if the problem is solved. Beta versions of software usually come with bugs, sometimes many , some times a few. I remember when lollipop just came out, i installed on my droid rarz and i hard a simarly problem to you. I just flashed my stock ROM back and every returned to normal
Sent from my 404SC using Tapatalk
priesly said:
I dont think you have made it kapput. Flash the stock firmware back and see if the problem is solved. Beta versions of software usually come with bugs, sometimes many , some times a few. I remember when lollipop just came out, i installed on my droid rarz and i hard a simarly problem to you. I just flashed my stock ROM back and every returned to normal
Sent from my 404SC using Tapatalk
Click to expand...
Click to collapse
The Problem is, i did not have the problem when i flashed it first. But the second or third time ruined something i guess.
I dont want the stock marshmallow rom back to be honest.
Just try and see if the problem still persist. I think that's the only way you can find out if its the rom or u breaked your phone
Sent from my 404SC using Tapatalk
priesly said:
I dont think you have made it kapput. Flash the stock firmware back and see if the problem is solved. Beta versions of software usually come with bugs, sometimes many , some times a few. I remember when lollipop just came out, i installed on my droid rarz and i hard a simarly problem to you. I just flashed my stock ROM back and every returned to normal
Sent from my 404SC using Tapatalk
Click to expand...
Click to collapse
priesly said:
Just try and see if the problem still persist. I think that's the only way you can find out if its the rom or u breaked your phone
Sent from my 404SC using Tapatalk
Click to expand...
Click to collapse
Wait, yesterday i have done this, the battery drain was kinda normal, but now i see the "android system" is draining with like 30% of the total battery usage after the third nougat flash.
RisingCracks said:
Wait, yesterday i have done this, the battery drain was kinda normal, but now i see the "android system" is draining with like 30% of the total battery usage after the third nougat flash.
Click to expand...
Click to collapse
Well, you might just have brokened it. But still give what a told you a try
priesly said:
Well, you might just have brokened it. But still give what a told you a try
Click to expand...
Click to collapse
How could ive broken it ?
I tried it some hours ago i remember.
RisingCracks said:
How could ive broken it ?
I tried it some hours ago i remember.
Click to expand...
Click to collapse
There are quiet a few reasons why it might be broken. But again i still insist on trying out back the stock ROM
priesly said:
There are quiet a few reasons why it might be broken. But again i still insist on trying out back the stock ROM
Click to expand...
Click to collapse
i say it again, i did go back on the stock. And yes, the battery life was kinda better. And then i flashed nougat back. The problem is, why is the android system draining so much with 30% for the total battery consumption.
Ohhh.if it got besser that simply means there seem to be a lot of background activity with the nougat
Sent from my 404SC using Tapatalk
priesly said:
Ohhh.if it got besser that simply means there seem to be a lot of background activity with the nougat
Sent from my 404SC using Tapatalk
Click to expand...
Click to collapse
okay...
am i getting still software updates ?
I mean when nougat get released, am i getting an update pop up thing or not ?
You probably will get an option to update firmware
Sent from my 404SC using Tapatalk