Fair enough...hope to see good battery results with this kernel... who knows if ill be able tell differences in anything between kernels...but it is fun!!

Battery stops charging with this kernel on RU Jellin latest milestone. It works fine for a few days, then it will stop charging my phone. I turn it off, the lightning bolt in the battery appears then shows the screen where its charging the battery. After the screen times out or w/e the lightning bolt pops up again, and then back to the charging battery. But when I turn it on, it isn't charging. Has happened twice. Lean kernel fixes it but I wanna use this kernel. Suggestions?

If the problem can be verified and reproduced you may want to find the devs irc and do some debugging. The usual flash/reflash wipe stuff may not be enough.

Originally Posted by DRatJr

Battery stops charging with this kernel on RU Jellin latest milestone. It works fine for a few days, then it will stop charging my phone. I turn it off, the lightning bolt in the battery appears then shows the screen where its charging the battery. After the screen times out or w/e the lightning bolt pops up again, and then back to the charging battery. But when I turn it on, it isn't charging. Has happened twice. Lean kernel fixes it but I wanna use this kernel. Suggestions?

I've been running the latest stable, 3??/13??, (Sorry, new to the gnex and don't rember the exact speeds lol) and have not had any charging issues. Are you sure you have fast charge disabled? Trinity has always been great for me on my nexus s, and now on my gnex. Hats off to morphic, you sir, are the man.

Sent from my Nexus S 4G using xda app-developers app

I've tried googling and looking on XDA to see if this is either a ROM issue or a kernel issue.. but I can't seem to find an answer.. right now I'm running cm10 with trinity 307/1344 stable.. I use cm's built in CPU control settings to over clock to 1344.. now the problem is, sometimes the max CPU speed will randomly revert back to 1200 but everything else will remain saved. Normally 1200 isn't even an option for trinity.. thanks for any help

Sent from my Galaxy Nexus

Originally Posted by s3v3nXDA

I've tried googling and looking on XDA to see if this is either a ROM issue or a kernel issue.. but I can't seem to find an answer.. right now I'm running cm10 with trinity 307/1344 stable.. I use cm's built in CPU control settings to over clock to 1344.. now the problem is, sometimes the max CPU speed will randomly revert back to 1200 but everything else will remain saved. Normally 1200 isn't even an option for trinity.. thanks for any help

Sent from my Galaxy Nexus

I think the best way to OC is to use Trinity Kernel Toolbox found in the Play Store. I think because you use the built in CPU controls of that ROM, the settings don't stick. I use it and it works perfectly. It also helps with changing other things like the colors.

Sent from my Galaxy Nexus using Tapatalk 2

That may be only an icon issue with a theme you have applied, check into it.

Sent from my Galaxy Nexus using Tapatalk 2

I've used cm10 and Trinity jb on my nexus s 4g with no problems.. this only happens on my galaxy nexus

Sent from my Galaxy Nexus

I do not need further feedback on alpha41, i know what it is, i knew the potential existed, i merely hoped a change to it would eliminate the issue.
I will add another fix, if this does not lead to stability, it will be a switchable item.
IF it works for you, use it, if not turn it off.

Originally Posted by s3v3nXDA

I've tried googling and looking on XDA to see if this is either a ROM issue or a kernel issue.. but I can't seem to find an answer.. right now I'm running cm10 with trinity 307/1344 stable.. I use cm's built in CPU control settings to over clock to 1344.. now the problem is, sometimes the max CPU speed will randomly revert back to 1200 but everything else will remain saved. Normally 1200 isn't even an option for trinity.. thanks for any help

Sent from my Galaxy Nexus

I guess your rom ships with hardcoded values instead of reading from the frequency table, not cool. PowerHAL introduced in JB switches the kernel to a lower max frequency on screen off, and back to "max" on screen on.
This is particularly retarded considering the stock kernel already does this, no need to duplicate the feature in the rom, especially if the kernel side of things is adjustable and the rom side is hard coded.

I saw someone mention No Frills cpu control can prevent other apps from changing cpu clock, you could utilize that if you do not have TKT to help you keep your max at whatever you set it at.