Very fast battery drain on Cyanogenmod 11 on Galaxy S4

Soldato
Joined
11 Oct 2011
Posts
3,335
Location
UK
Hi all,

Recently flashed Cyanogenmod 11 to my Galaxy S4, first time I've done anything like this, and the battery is draining VERY fast.

I lost around 10% in about 15 minutes with no apps open in the app switcher.

At this point in the day, with stock rom, I'm usually on around 60%, now I was on 26%

Anyone have any ideas on what is causing this please?

I've attached some screenshots if they'd help

Hope someone can help :)

FnPe3Ojl.png.jpg

heJzNWjl.png.jpg
 
Hi all,

Recently flashed Cyanogenmod 11 to my Galaxy S4, first time I've done anything like this, and the battery is draining VERY fast.

I lost around 10% in about 15 minutes with no apps open in the app switcher.

At this point in the day, with stock rom, I'm usually on around 60%, now I was on 26%

Anyone have any ideas on what is causing this please?

I've attached some screenshots if they'd help

Hope someone can help :)

FnPe3Ojl.png.jpg

heJzNWjl.png.jpg

its the kernel.

try a different kernel such as ktoon or alucard
 
Sorry, for someone new to ROMs and modding, can you please explain...

How do I go about changing the kernel?

EDIT: I've read something about battery calibration apps, like the one below, I assume that won't help?

https://play.google.com/store/apps/details?id=com.nema.batterycalibration

The kernel manages the hardware of your device, such as speed etc.

you need to download a kernel. then flash it like you flashed your rom.

you flash the zip file. you can then tweak the kernel settings using the programs usually built in such as ktweaker or stweaks.

although i wouldn't recommend tweaking anything and just leaving it as default until you have read up abit
 
Thanks all :)

I will get a different kernel later on after work then and flash it

I assume the kernel is like flashing the gapps package, it doesn't replace cyanogen, it only replaces any other kernel? As in cyanogen wont need reinstalling after?
 
Think of the kernel as how the ROM communicates with the hardware, and vice versa (I guess like a BIOS). Flashing the kernel will not require you to reflash your ROM.
 
That's good :)

I will try ktoon or alucard later on and hope it fixes the issue :)

Without actually waiting for the battery drain to happen, is there any quick method of checking it? Like an app? Just wondering as I really need my phone tomorrow and won't be near a charger, so I may backup cyanogen, go back to stock ROM tonight and sort it out after tomorrow
 
Seems a bit odd that the stock CM11 kernel would be released with a problem like that?

Very odd, the reason I went with CM is because it is so popular and I assumed it would be stable

I downloaded a 'snapshot' version which from what I read, should be fairly stable. I couldn't see any marked as 'stable' on their website for the i9505 GS4
 
Just to check

http://download.cyanogenmod.org/?device=jflte

That is where I downloaded my CM from, I have the GT i9505, is that correct? Just odd that there isn't any 'stable' ones in that list, there is stable ones for the 'international' GS4 but I don't want to flash that and brick the phone

Go to Settings > About phone.

If its a UK based one then it should be International. Which is GT-I9500. Oh I see the I9505 is also international. I hate Samsung with there 10,0000000000 different variants >_<

Might also be worth clearing the cache/data for Google play services.

This is the correct thread for your version http://forum.xda-developers.com/showthread.php?t=2559336
 
Last edited:
Correct mine is the i9505

I'm thinking it might be best to go with something other than cyanogenmod maybe since they don't have a stable release for the i9505

I will also try the cache clear first :)

Matteysan/anyone recommend anything stable for the i9505?
 
Correct mine is the i9505

I'm thinking it might be best to go with something other than cyanogenmod maybe since they don't have a stable release for the i9505

I will also try the cache clear first :)

Matteysan/anyone recommend anything stable for the i9505?

word of warning, make sure you flash kernel for asop
 
Correct mine is the i9505

I'm thinking it might be best to go with something other than cyanogenmod maybe since they don't have a stable release for the i9505

I will also try the cache clear first :)

Matteysan/anyone recommend anything stable for the i9505?

Stock rooted with x-posed module & mavity box.

Near enough all Custom Roms will be using CM's device tree/have the same bugs.
 
word of warning, make sure you flash kernel for asop

Is that for CM? Or if I go with anything other than CM?

Stock rooted with x-posed module & mavity box.

Near enough all Custom Roms will be using CM's device tree/have the same bugs.

Hmm okay

I've also been told to look at paranoid android which is supposed to be good

Will look into the above also, what's the advantages of that module and mavity box? In short
 
Is that for CM? Or if I go with anything other than CM?



Hmm okay

I've also been told to look at paranoid android which is supposed to be good

Will look into the above also, what's the advantages of that module and mavity box? In short

PA is a very good ROM but with it being on a Samsung phone they use the CM device tree to get it working so will encounter the same kind of bugs as CM.

Advantage of the module & mavity box is they can apply the same kind of methods/custom stuff as custom roms but not on a level like custom roms. Plus you get to keep stock without any problems.

He means by that theres two different types of kernels. Stock uses normal Samsung trees & aosp is for custom roms such as CM, PA, AOKP.
 
Last edited:
PA is a very good ROM but with it being on a Samsung phone they use the CM device tree to get it working so will encounter the same kind of bugs as CM.

Advantage of the module & mavity box is they can apply the same kind of methods/custom stuff as custom roms but not on a level like custom roms. Plus you get to keep stock without any problems.

He means by that theres two different types of kernels. Stock uses normal Samsung trees & aosp is for custom roms such as CM, PA, AOKP.

Yeah a lot seem to be based on CM.

Ahh right that makes sense :)

Will wipe cache etc to see first, this whole thing might just be a small bug that can be fixed by something like that maybe. Like you say I may be stuck with this battery bug then if CM has it, and they're all based off that

I might be best with Google Edition or stock with the above packages and modules you mentioned

Thanks for all the help :)
 
One issue is google play services, it has a 'keep awake' time that is just constantly going up, even though the app is not running?

EDIT: It seems to have stopped after 27 minutes
 
Last edited:
Back
Top Bottom