yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] szucsgf:
You can probably do better. Try:

1. A slightly older version of ak. 256 gave some people higher than normal battery drain. I'm on 248 and battery is great.

2. Use bbs and Wakelock detector to see if there is anything draining your battery when it shouldn't be.

3. Share your kernel settings (if other than stock) and someone might offer alternative suggestions to try.
[Samsung Galaxy Nexus] bigbear6708:
Lol... going to admit...I saved that meme! Lmao
[Samsung Galaxy Nexus] adio201:
I have pgm install so maybe thats my wake lock
[Samsung Galaxy Nexus] szucsgf:
Those kernel settings are pretty decent. You might want to turn zram off and change max Screen Off to 525. Might make a bit of a difference.

Pgm takes some battery but not too much. Maybe an additional 0.3-0.4% per hour. I'd still try Wakelock detector / bbs and an older version of the kernel if I were you.
[Samsung Galaxy Nexus] jjhiza:
^Agreed. I've never found Zram to be useful in the Nexus, so disabling it may help. I'm almost willing to bet that there's some kind of Maps or GPS related wakelock going on.
[Samsung Galaxy Nexus] adio201:
What is bbs
[Samsung Galaxy Nexus] klobkelosh:
Better battery stats
[Samsung Galaxy Nexus] szucsgf:
https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats

https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector
[Samsung Galaxy Nexus] adio201:
This is screen wake lock and also CPU wake lock
[Samsung Galaxy Nexus] manardrs.jb:
Where can I find the 248 version thanks
[Samsung Galaxy Nexus] MBQ_:
http://d-h.st/wjF
[Samsung Galaxy Nexus] manardrs.jb:
Cool thanks a bunch
[Samsung Galaxy Nexus] L-ViZ:
batterylife is ok with 256

55min screentime (nearly full brightness, cuz sunny day)

uptime just 2h

but 80% left.

deleted nearly all bloat and stuff with autosynch. just whatsapp/hangouts/ 2 gmail accounts.

edit: sry, 2 times same screenshot :-\ cant change it in xda app.
[Samsung Galaxy Nexus] Sheetzie03:
Hey [MENTION=4783761]szucsgf[/MENTION] i recently seen this post of yours commenting on a members kernel settings.

http://xdaforums.com/showthread.php?p=42685021

Also, someone recommended v248 skl(not sure if it was you or not). Well i figured i was going to try 248 as well.

Anyway i was hoping you(or others) could give me their thoughts on if my settings were OK battery life wise, in your opinion.

Would appreciate very much :)

I will posts battery life results after a few days like others have to get feed back regarding that as well.

I just wanted to make sure settings were about where they should be before doing testing.

I thank anyone who offers feedback, it will be very very.much appreciated.

And of course thank you to Stefano for an amazing kernel.:thumbup:

♦ToroNex♦N7›Wifi♦DDless-Please [MENTION=4763201]mbq[/MENTION] bring the XY nightly goodness. My ToroNex has never been the same.
[Samsung Galaxy Nexus] Soundigy:
I've tested many kernels recently and I found that 248 serves me best, feel free to try my settings.

First cycle on [B]Slim 6.2[/B] + [B]AK SKL.248[/B]

(Stock battery, 2g, PGM on, [I]Lux Auto Brightness[/I])

[B][COLOR="#FF0000"]*[/COLOR][/B] On battery: [B]2d 11h 38min[/B]
[COLOR="#FF0000"][B]*[/B][/COLOR] OST: [B]2h 57min[/B]

Drain from 03am to 9am is amazing, [I]-0.1% /h[/I]

Trickster setup:

[HIDE][B]Cubic[/B]
[B]SIO[/B]
[B]Read Ahead Buffer[/B]: 512
[B]Interactive[/B] (hispeed_freq - 810000)
[B]Min[/B]: 180mhz
[B]Max[/B]: 1350mhz
[B]Max Screen Off[/B]: 350mhz
[B]Min Screen On[/B]: 180mhz

[B]WiFi High Performance[/B]: Off
[B]C.A.Brightness[/B]: Off
[B]Multicore Power Savings[/B]: 2
[B]Dynamic FSYNC[/B]: On
[B]Tempature Limit[/B]: 80
[B]Smartreflex[/B]: All On (MPU undervolted by -25)
[B]Core Min Calibrated Voltage[/B]: 800
[B]IVA Min Calibrated Voltage[/B]: 800
[B]MPU Min Calibrated Voltage[/B]: 800

All others are default.

** If you experience lockscreen lag, use 525mhz instead [B]Max Screen Off[/B] 350mhz [/HIDE]
[Samsung Galaxy Nexus] szucsgf:
Thanks for asking me! The first thing I would do is change max cpu. Because it runs at the same Voltage as 1200, 1350 will give slightly better performance while using no noticeable additional battery. Or, because it runs on a much lower Voltage than 1200, 1060 will give slightly less performance but noticeable extra battery. Take your pick.

Unless it results in instability (eg freezes / reboots), you can lower min cpu and min screen on to 180 and turn on content Adaptive Brightness. These might help a bit.

Also, you didn't post your governor control settings. If they're default, lower hispeed_freq to 810 or lower. That should help.
[Samsung Galaxy Nexus] TurboLed:
I did that, the first time. Nobody helped. Because my logs had nothing helpful in them, only a sudden reboot, without any related log message. There are several users complaining and nobody found a solution. Just doing a search with "Reboot" will show my log and what settings I tried to change to fix the problem.
[Samsung Galaxy Nexus] aamadorj:
bbs = Better Battery Stats. Look here: http://xdaforums.com/showthread.php?t=1179809
[Samsung Galaxy Nexus] szucsgf:
This is a relatively fast-moving forum. Please forgive if people forgot the context of your post.

I took a look at your recent posts. You posted problems exactly like the OP asks, and provided all the additional info needed. Thank you.

As you mentioned yourself, the bugreport didn't show any errors. The solutions you've attempted are very comprehensive. You've already done exactly what I would do to try to solve the issue.

I can only offer one unlikely idea: did you try to turn Content Adaptive Brightness off? CAB caused reboot issues for some people, depending on your ROM.

---------- Post added at 08:21 AM ---------- Previous post was at 08:18 AM ----------

Your wakelocks don't seem to be excessive to me. Thanks for posting.
[Samsung Galaxy Nexus] Sheetzie03:
Oh no problem, thank you foot your help!

I didn't know that about that about max CPU, glass i know now, thank you. Yes i week definitely either raise to 1350 or lower to 1060!

Also i l will lower both min cpu and min screen on to 180 and go from there.:)

And yeah, i didn't post gov control settings because they're at default. Ill try and lower high speed_freq. If i did uv 25, should i lower each one of the levels 25?( in the past i always one lowered the first 3 or 4 levels, never knew. enough about it. And if i do UV, should i still lower high speed_freq to 810 or lower?

I very much appreciate your help. Thank you!

♦ToroNex♦N7›Wifi♦DDless-Please [MENTION=4763201]mbq[/MENTION] bring the XY nightly goodness. My ToroNex has never been the same.
[Samsung Galaxy Nexus] szucsgf:
I just want to make sure since I can't tell from your screen shots: do you keep smartreflex on? I personally don't bother with undervolting. I just keep smartreflex on. You can read the guide "SmartReflex and Undervolting" in my signature if you'd like to see why.
[Samsung Galaxy Nexus] Sheetzie03:
I usually don't UV either, was just curious. Yeah Whatever is default. I don't touch smartflex....:)

♦ToroNex♦N7›Wifi♦DDless-Please [MENTION=4763201]mbq[/MENTION] bring the XY nightly goodness. My ToroNex has never been the same.
[Samsung Galaxy Nexus] KemikalElite:
I have to say that since I switch to AK back in January each percent allows me to do more with my phone and worry less about draining and charging all the time.

I feel bad for my friends who bought those high end overpriced Motorola portable chargers cause they're not on AK. This saves me from buying one of those since my phone lasts all day.
[Samsung Galaxy Nexus] aaron13:
After a flashing AK256 on my pa rom and gs2kernelwipe I saw in trickstermod that the scheduler was set on SIO instead of row.

Strange that it still holds old kernel settings.

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] mrgnex:
Where did the twrp themes go? I only could find 1.. They were in the first post but now they're gone.. Anyone who has links?
[Samsung Galaxy Nexus] MBQ_:
http://xdaforums.com/showthread.php?t=2329700 :)
[Samsung Galaxy Nexus] thegtfusion:
the wifi drops are gone with franco...

i think it has something to do with the 3.4 wifi drivers. it needs to be fixed though
[Samsung Galaxy Nexus] MBQ_:
How quaint

I've never had WiFi drops with v256
[Samsung Galaxy Nexus] venividivici87:
No, my gnex dropped also with FK 382, that also drained battery too fast. Returned with AK !

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] thegtfusion:
well, I had, some other people too. I mentioned it a couple of days ago. the versions before 256 had it too.
[Samsung Galaxy Nexus] ciprianruse88:
End of the world is coming.annuaky will return and punish us all. I hope google will be punished first due to their $hitty 4.2 update :cool:

Highfive bro :)

Sent from my Nexus 4
[Samsung Galaxy Nexus] Az Biker:
+1

Axiom + AK SKL Series = Bacon, Skittles & Skulls!
[Samsung Galaxy Nexus] ciprianruse88:
I don't believe in no wifi drops.I have them on nexus 4 also.

Sent from Inferno
[Samsung Galaxy Nexus] thegtfusion:
but it is frustrating that ak has them and franco not!!! i am stressing here
[Samsung Galaxy Nexus] cms5423:
Maybe you haven't used Franco long enough for one to occur, or another option is that franco built in a script that runs whenever a wifidrop occurs which auto toggles wifi to reestablish connection (this is what the fancy kernel dev did). Either way, I have not had any wifi drops on SKL256 (or maybe one a couple days ago) but that is at most 1 in over 2 weeks
[Samsung Galaxy Nexus] killersloth:
I now consider myself lucky to have no access to WiFi at home.

One less bug to worry about.

Although I must admit the WiFi on gnex is really bad compared to every other phone I've ever had.
[Samsung Galaxy Nexus] ChazzMatt:
You should know how it works by now with AK kernels. They can't admit anything is wrong, until AK comes back in and ANNOUNCES he's fixed the wi-fi drops! THEN, everyone can admit yes there WERE (past tense) wi-fi drops, now that you mention it. Oh, THOSE wi-fi drops...

And within 5 minutes of releasing a new kernel, six people will post battery stats claiming they had THREE freakin' days of phone life without charging -- on the new kernel. :rolleyes:

But until AK say says there was a problem (overheating, soft reboots, wi-fi drops, etc) which has now been fixed, the acolytes will push back and deny any problem. :silly:
[Samsung Galaxy Nexus] killersloth:
^^This guy has it down to a science.

256 provided me with random reboots on two different gnex, stock ak settings. Its an experimental kernel and sometimes there are problems, but yeah until the man comes in and clears it up-- long live 256 the flawless release :) :) :)
[Samsung Galaxy Nexus] jjhiza:
Can't admit something's wrong if nobody else can verify the problem man. It would be kinda like me coming to the SlimBean thread and claiming I had SystemUI crashes, but not posting any other details, logs, etc. You'd probably let me know that my post wasn't too useful, and that you can't help without more info. That doesn't mean you're slurping Neb's work...it just means you expect better quality bug reporting.

Essentially, that's what I understood [MENTION=4244313]MBQ_[/MENTION] to mean, when he said (tongue in cheek) "how quaint". He could have put the user on blast for not posting bugs properly, but he didn't...he just made a small joke at that user's expense, and moved on.
[Samsung Galaxy Nexus] Khizar:
you should know that every device works differently.. i have had ZERO issues with SKL 256, no reboots, no overheating.. i cant comment on wifi drops as i hardly use wifi but i remember stefano saying something about it being fixed, not 100% sure though..

hahaha please link me where a user has posted battery stat within 5 mins of the new kernel being released..

and as for your last point even if stefano confirms that the issues exist, i will continue saying they dont exist for me as i dont have them

PS- dont misunderstand me i know many users are having issues, but if they dont use the format that stefano has set in the OP then we cant help them

256 gave you random reboots but its still flawless lol :what:
[Samsung Galaxy Nexus] MBQ_:
Quaint also happens to be one of my current favorite words as well
[Samsung Galaxy Nexus] jjhiza:
Lmao! How very 19th century of you! :P
[Samsung Galaxy Nexus] jjhiza:
Hahahahaha! Lmao! Classic!!
[Samsung Galaxy Nexus] MBQ_:
:3
[Samsung Galaxy Nexus] MBQ_:
Try these colors out fellas. :)
[Samsung Galaxy Nexus] OMFGNuts:
Wow, really cool, my old and rusty gnex works fast now,really battery smooth,THX U REELE SMART ONE

Отправленные с моего Galaxy Nexus с помощью Tapatalk 4 Beta
[Samsung Galaxy Nexus] MBQ_:
Uh

Can't tell if that's sarcasm, or if you're actually thanking me. (I see English isn't your primary language so I don't want it to be an accidental miscommunication)
[Samsung Galaxy Nexus] mixtapes08:
Lol

-3StarsAndaSun
[Samsung Galaxy Nexus] Az Biker:
Actually, as hard as it may be for you to believe, admit, accept: I've never had a wi-fi drop, ever. As a matter of fact, when the whole 'WEP router wouldn't work' issue affected so many people, I was still able to use WEP when most couldn't. Just because you experience an issue with your phone or a specific kernel / rom, does not mean everyone else not experiencing the same thing is lying, or in denial.

Axiom + AK SKL Series = Bacon, Skittles & Skulls!
[Samsung Galaxy Nexus] MBQ_:
Straight up
[Samsung Galaxy Nexus] jjhiza:
Here are my custom color settings. I like things a little bit darker... Let me know what you guys think.
[Samsung Galaxy Nexus] msa1390:
My phone loved your color setting! So do I:D

thanks jjhiza:good:
[Samsung Galaxy Nexus] OMFGNuts:
Yeah, i was kinda sleepy, night shift, you know, and english is actually my 3rd language, it was a sarcasm btw :(
[Samsung Galaxy Nexus] ciprianruse88:
I have also made an awesome color profile for gnex.It is posted in the OP of my wallpaper thread but here is a screenshot of it:cool: ...true white and deep black :)

Sent from Inferno
[Samsung Galaxy Nexus] jjhiza:
Been farting around with a couple different kernels - Syarkissed, Franco, Trinity, and Fugu to be exact - in an attempt to get a feel for how different ones perform, as I attempt to build my own... After having serious signal and lag issues with all of them, I've come to the conclusion that AK kernels really are top of the heap for me.

I was surprised at the problems I had with Franco and Trinity, particularly because they've always run decently for me, but they're just not doing the trick this time around. I guess I'm going to be basing my kernel on Ezekeel's and Stefano's work moving forward. I'm thinking of trying a base of KUBO (for stability and reliability), mixed with some extra governors and schedulers from Ezekeel and ZenSERIES. I continue to be amazed by how well these kernels are built... I can only hope to do half as well.
[Samsung Galaxy Nexus] szucsgf:
I'd like to let the AK team know that I'm moving on to the Nexus 4. I want to thank everyone here for sharing their knowledge and experience, and especially Stefano for allowing us to benefit from his many hours of work. It feels like half of what I know about Android I learned from this thread. Crack flashing 5 beta kernels a day was one hell of a ride at times. I'm very happy I could be a small part of this project.
[Samsung Galaxy Nexus] TheMan0790:
Hmm...I too am trying out different kernels until a new AK release. Running Franco's latest right now, and I'm seeing no lag.

Sent from my Cyanogen-flavoured, AK-powered Galaxy Nexus
[Samsung Galaxy Nexus] nixholas:
Good luck in Nexus 4 :) Hope you'll see Anarkia there.

By the way, Anarkia, I know it may be OT, but in AK's boot logo, I feel that there's two images. Am I right?
[Samsung Galaxy Nexus] MBQ_:
Same, I tried one (wont say which one out of respect), and I had WiFi problems (Clean flash and everything too), as well as semi-quick battery drain. The performance was outstanding, but nothing can compete with Anarkia kernels in my opinion*
[Samsung Galaxy Nexus] tritonesub:
Check out these settings! They're a but closer to stock, but they still look nice and not yellowish. Also I've found that there's minimal burn-in for screens that are suspect to that.

Sent from my Mahjong Nexus
[Samsung Galaxy Nexus] MBQ_:
Fuuuuuu hahaahah
[Samsung Galaxy Nexus] klobkelosh:
I decided f**k the screen burn in, I need to be able to see my screen in the midday Arizona sun...

I have this matched with some very aggressive auto bright options. I like it, but the screen will probably be toast
[Samsung Galaxy Nexus] yaatzek:
Not necessarily, I think that cm default settings are higher and people didn't complain about screen burn out. I also prefer higher values, here is mine (in fact it's osmosis ;) ):
[Samsung Galaxy Nexus] ranasrule:
Im using CrossBreeder mod >>> http://xdaforums.com/showthread.php?t=2113150

I would like to enable Frandom support on SKL v256....can anyone provide a step by step guide on how to achieve this ? Thanks

Info from CrossBreeder thread about Frandom...

"Frandom support (Optional) - CrossBreeder now supports linking both your random devices to the extremely fast alternative - Frandom ( http://billauer.co.il/frandom.html ). This module is orders of magnitude (10-50 times) faster than the standard character devices ( Check this out - http://xdaforums.com/show...&postcount=134 ). The erandom character device also installed by Frandom doesn't use up system entropy at all on top of being fast. You will need to ask your ROM developer to develop the kernel module for you and then place it in /system/lib/modules. CrossBreeder will then try and load it and if successful, make all the necessary adjustments so that both /dev/random and /dev/urandom are pointing to /dev/frandom and /dev/erandom respectively. The speed benefits are to be seen to be believed. But since each ROM requires a unique kernel module, this option is left optional ( but auto detect ). Advanced users can even try and load the frandom module built for other kernels if they don't have one readily available for their own kernel version using the Punchmod utility. Read this: http://xdaforums.com/show...5#post41920265"
[Samsung Galaxy Nexus] chikimonke:
It's in the OP.
[Samsung Galaxy Nexus] Az Biker:
Best of luck with N4! I think I'm holding out for N5 or whatever is next big thing after N4. Your presence will be missed.

Axiom + AK SKL Series = Bacon, Skittles & Skulls!
[Samsung Galaxy Nexus] szucsgf:
Thank you az! And I'll be getting the Nexus 5 as well, whenever that happens. I look forward to seeing you there.
[Samsung Galaxy Nexus] MBQ_:
Make that one more. :)
[Samsung Galaxy Nexus] Khizar:
make that 2 more ;)
[Samsung Galaxy Nexus] jjhiza:
Count me in on the N5 action!
[Samsung Galaxy Nexus] xxSAKISxx:
I am getting the N5 to (i hope)
[Samsung Galaxy Nexus] yaatzek:
I want to buy n5, who's selling?
[Samsung Galaxy Nexus] TheMan0790:
Me!

Sent from my Cyanogen-flavoured, AK-powered Galaxy Nexus
[Samsung Galaxy Nexus] Seraz007:
most probably the N5 as u know it will turn out to be the Moto X

i hope im damn wrong :fingers-crossed:
[Samsung Galaxy Nexus] yaatzek:
Do you also have n6 for my wife :)
[Samsung Galaxy Nexus] TheMan0790:
Pffft, I've got a N....wait....there already is a Nexus7...carry on

Sent from my Cyanogen-flavoured, AK-powered Galaxy Nexus
[Samsung Galaxy Nexus] Seraz007:
i've got the N8

wait, that's a nokia :D:D

anyways lets just stop the offtopic guys(although i do love it xD)
[Samsung Galaxy Nexus] Sik-1:
I can't wait for a Nexus Desktop computer edition lol, big screens to the world lmfao
[Samsung Galaxy Nexus] musashihatred:
Have to say goodby as well to GNex and move on to N4 -__- got it really cheap so i cant resist.
[Samsung Galaxy Nexus] Az Biker:
Looks like a lot of the people I follow and have learned from are going to eventually be on the N5 or whatever comes after the N4 :D IF I can get a great CASH deal on an N4, I would take it. But I ain't using my upgrade until the N5 or better is available. In any case, it looks like I'll be in impressive company down the road!
[Samsung Galaxy Nexus] cuzzinz:
On axi0m with ak256.

No mater what I do, clean wipe or dirty flash I find after some time my phone just gets really slow. Almost as if the CPU is pegged at 100% or I am being throttled really bad. I am using stock settings when flashing. I only use trickstermod to change the screen color calibration. Any thoughts? I have even tried with and without cross breeders mod. Nothing helps.
[Samsung Galaxy Nexus] jjhiza:
I'd suggest trying KUBO 0.50. it was released at the same time as 256, but for me, it's been far more stable. Your phone may just hate 256... What was the last version of AK that you had success using? If KUBO doesn't work well for you, hit the AK ARKIVZ in my sig, and download whatever version you want... I have them all. :)
[Samsung Galaxy Nexus] cuzzinz:
Thanks man. Giving it a whirl
[Samsung Galaxy Nexus] MBQ_:
Are you gaming or running Facebook or something in the background?

And, which IO scheduler?
[Samsung Galaxy Nexus] cuzzinz:
Yes I am running Facebook. I don't have it update ever though. Only when I open it. I also have Facebook messenger. Hangouts and that is about it. I removed ALL games from my phone after the last clean flash. I am using stock messenger and don't have many additional apps installed. I even clear recent apps and the problem continues.

I am was on ak256 using the stock settings. Which I believe was 2048 sio and interactive scheduler.
[Samsung Galaxy Nexus] branedamig:
Enable Zram with Scriptmanager

Okay, I've searched all I can and still don't know if I've done this right. I'm running AK KUBO r50 and am trying to enable Zram via Scriptmanager (an app/process I've never used before). Here's what I did:

1. In Scriptmanager, navigated to root\data\ak\backup\zram

2. Typed zram_imoseyon.sh in the alias line

3. Selected "run"

4. Took me to a screen with a "shell" and "zram_imoseyon.sh" tab and below it said "swap 0 0 0"

5. Went to Terminal Emulator to check if it took and it gave me some buffer, etc. info and then also listed "swap 0 0 0"

After all that, I'm not sure if Zram has been enabled. The info in Terminal Emulator really didn't look that much different before and after I went through this Scriptmanager process. Maybe I'm screwing with stuff I don't know about but I'd really like to use KUBO and enable Zram. If someone, anyone can let me know what I'm doing, I'd greatly appreciate it. Thanks!
[Samsung Galaxy Nexus] jjhiza:
Zram is essentially (like your readout said) extra swap space... Making, it takes "x" amount of RAM out of your system, and stores it for more RAM-intesive tasks. In my opinion, the Galaxy Nexus, and newer phones, don't require additional swap space. As long as you have 150MB+ available, the device should run just fine. That's just my understanding though... Maybe I'm wrong. It seems like you've run the proper terminal commands to enable it though. :)

See here for a full explanation of swap space: http://www.centos.org/docs/5/html/5.1/Deployment_Guide/s1-swap-what-is.html
[Samsung Galaxy Nexus] Seraz007:
O_o ! i have 50mb free and no lags ;) :highfive:

well free ram is useless

unless the phone lags, no need to increase ram whatsoever ;)
[Samsung Galaxy Nexus] jjhiza:
Free RAM isn't useless actually... It helps to keep things running smoothly, and acts as a buffer when you need more RAM for tasks. 50MB free is a bit low in my estimation, unless you're running a ton of widgets. Here's my free RAM right now... 3 homescreens, two widgets, plus WidgetLocker, which is a resource hog.
[Samsung Galaxy Nexus] Seraz007:
ha u got that right

running uccw,zooper and some other ones at the same time

hangouts and gmail

well no problems with lag

just the battery drainin that's all ;)
[Samsung Galaxy Nexus] schnob:
I hope this isn't too off-topic, but what will you toro folks do if the Nexus 5 (Or whatever it will be) doesn't come to Verizon? I basically have to stick with big red because they're the only ones with good coverage in my area. Hopefully at least the X-Phone will come to Verizon, it seems like they always have a lot of Moto phones.