Yesterday this showed up as my second battery user under battery.. With over 3 hours of Wakelock? Why? Anyone have the same problem?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Oh yes, you're not alone.
I've been having this problem on all 4.3 builds, JWR and JSS regardless of the vendor (CM, AOKP, Carbon...)
I tried many 4.3 roms, I always get this Android System battery drain. CM10.1.3 works perfectly for me though.
My brother, who also has a Nexus 4, has this problem on his CM10.1.3 installation.
It's not kernel related, I tried different kernels on the same rom and still had the drain. It's not JSS related, JWR has this too.
I wonder if stock 4.3 has this problem too. It's starting to infuriate me; I'm stuck on 4.2.2 when CM is already on it's first 4.3 M release.
This thread discusses this issue
http://forum.xda-developers.com/showthread.php?t=2392155&page=6
but doesn't provide an answer.
They're saying radio 0.84 might be the culprit, but I'm not sure.
I hope 4.4 builds won't have this.
Related
Over in the Omega thread for the I9505, I've been having a discussion with a few people regarding why the wifi breaks when you flash say an MF4 based rom from an older base (like if you're on stock MEA or something) however all I got in response was to flash an MF4 modem package and wifi will start working.
Wifi, as we all know, is handled by the kernel and not the modem, so why does wifi start working when you flash the modem for the base you're on if you're using a stock kernel? Are the stock kernels dependent of a certain modem? Because when I flashed Wanam's Adam kernel (source-built) straight over Omega 6 (MF4), wifi started working.
Why is it like this, you think?
http://forum.xda-developers.com/showpost.php?p=42806026&postcount=4104
Theshawty said:
Over in the Omega thread for the I9505, I've been having a discussion with a few people regarding why the wifi breaks when you flash say an MF4 based rom from an older base (like if you're on stock MEA or something) however all I got in response was to flash an MF4 modem package and wifi will start working.
Wifi, as we all know, is handled by the kernel and not the modem, so why does wifi start working when you flash the modem for the base you're on if you're using a stock kernel? Are the stock kernels dependent of a certain modem? Because when I flashed Wanam's Adam kernel (source-built) straight over Omega 6 (MF4), wifi started working.
Why is it like this, you think?
Click to expand...
Click to collapse
Ya even though the WiFi module is in the kernel it would seem that Samsung have put some sort of dependency in there that relies on a particular modem. (Maybe it is just that particular modem and all other modems from the MF4 one on will work with whatever new kernel you use, it could just be something big they changed in MF4 compared to MEA)
Sent from my Nexus 7 using Tapatalk 4 Beta
nodstuff said:
Ya even though the WiFi module is in the kernel it would seem that Samsung have put some sort of dependency in there that relies on a particular modem. (Maybe it is just that particular modem and all other modems from the MF4 one on will work with whatever new kernel you use, it could just be something big they changed in MF4 compared to MEA)
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
From what I can gather, it's always been like this. Check this thread (last pages) and see that they are being highly ignorant. http://forum.xda-developers.com/showthread.php?t=2253528&page=410
It's basically this: "flash the latest modem or sod off" but used with kinder words. I refuse to flash the MF4 modem just to fix the wifi when I know that flashing a source-built kernel fixes it just as well. Besides, a newer modem doesn't mean a better modem. The problem needs to be fixed, not circumvented.
Don't forget that people do stupid things just because they have heard that's what to do, need I mention the 'calibrating' the battery situation! If you can get it working with a custom kernel built from source then that is the way it should be done as it isn't a modem issue, it is a kernel issue, obviously Sammy put something in there that changed how it works in the last code drop.
On the other hand, maybe they did that to force people to use only the new modem, maybe the old one uses too much power, has bugs etc. God only knows why they do what they do.
Sent from my Nexus 7 using Tapatalk 4 Beta
nodstuff said:
Don't forget that people do stupid things just because they have heard that's what to do, need I mention the 'calibrating' the battery situation! If you can get it working with a custom kernel built from source then that is the way it should be done as it isn't a modem issue, it is a kernel issue, obviously Sammy put something in there that changed how it works in the last code drop.
On the other hand, maybe they did that to force people to use only the new modem, maybe the old one uses too much power, has bugs etc. God only knows why they do what they do.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I think we'd need the help of some very experienced kernel devs. Maybe @AndreiLux can share his knowledge?
That's probably the best option, get a definitive answer from someone that understands this stuff better than we do.
Sent from my Nexus 7 using Tapatalk 4 Beta
nodstuff said:
That's probably the best option, get a definitive answer from someone that understands this stuff better than we do.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I bet Samsung has placed some sort of dependency in the kernel (like you said) that when it doesn't find the right modem, it crap out and destroys wifi.
Djembey had an interesting reply: http://forum.xda-developers.com/showpost.php?p=42806026&postcount=4104
Thread closed at OP's request.
I've been having this problem for a couple weeks now. There hasn't seemed to been any pattern, my nexus 4 decides to reboot and then the battery usually goes down to 0. I am on PA now but before it was stock everything. I restored but that didn't help, then a fried suggested a new kernel so I rooted and flash Franco. However nothing had helped so far. Any ideas? I'm not going to go into specifics about the exact versions because it'll be stated below. So I just need some suggestions, this appeared a couple weeks after I was prompted to update to 4.3. Weirdly I was on 4.3 already but just went through with the update and 2 weeks after I have this. I was thinking of possibly flashing a 4.2.2 based ROM and an older version of the Franco kernel. Will this help? Or is a new battery all together I more logical way to go. Do y'all think it's a software or hardware issue. If more info is needed I'll be happy to reply, thank you :thumbup: Also I know this has been posted before but I couldn't find an actual solution... So hopefully this isn't taken off... Thanks Everyone.
Sent From Nexus 4 Android: 4.3Paranoid Android 3.99-RC2Franco Kernel #190 (nightly)
HarryH987 said:
I've been having this problem for a couple weeks now. There hasn't seemed to been any pattern, my nexus 4 decides to reboot and then the battery usually goes down to 0. I am on PA now but before it was stock everything. I restored but that didn't help, then a fried suggested a new kernel so I rooted and flash Franco. However nothing had helped so far. Any ideas? I'm not going to go into specifics about the exact versions because it'll be stated below. So I just need some suggestions, this appeared a couple weeks after I was prompted to update to 4.3. Weirdly I was on 4.3 already but just went through with the update and 2 weeks after I have this. I was thinking of possibly flashing a 4.2.2 based ROM and an older version of the Franco kernel. Will this help? Or is a new battery all together I more logical way to go. Do y'all think it's a software or hardware issue. If more info is needed I'll be happy to reply, thank you :thumbup: Also I know this has been posted before but I couldn't find an actual solution... So hopefully this isn't taken off... Thanks Everyone.
Sent From Nexus 4 Android: 4.3Paranoid Android 3.99-RC2Franco Kernel #190 (nightly)
Click to expand...
Click to collapse
Most probably its a Software porblem.
My suggestion is you should try another rom as many PAusers have some or the other issue with the rom or the kernel they use with it.
GO for Slimbean heck lot of features and try any JWR kernel. Iwould go with franco or hellcore test5JWR.
Press thanks if I helped you. :good:
P.S : Please do a clean install,factory reset before flashing Slim
I'll try that, thanks.
Sent From Nexus 4 Android: 4.3Paranoid Android 3.99-RC2Franco Kernel #190
As I know Chrome beta had this issue...so if you got it install just remove it
I have sound on maludus 2.0.1 but none on aosp has anyone else reported this problem
Sent from my Nexus 5 using Tapatalk
spinninbsod said:
I have sound on maludus 2.0.1 but none on aosp has anyone else reported this problem
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
As far as I know, I have not come across any AOSP roms as of yet on the 24 baseband, that would be the issue. You should flash back to a 12b baseband to use an AOSP rom at this time.
Edit:
I stand corrected I have come across it seems one AOSP rom based off of the 24a baseband, but it seems the developer has left this project.
http://forum.xda-developers.com/showthread.php?t=2702958
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.
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