yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] purian23:
Awesome thank you jjhiza, that's one thing I wanted to note as well. Notice how long your deep sleep and 384 has been in use, which is good, if the kernel is smooth, it simply doesn't have to scale up all the time. Example, I've had many hours of deep sleep and 384, but it shows 0% on some of my other steps above, two things to note on that. One, the percentages of use is gauged by the overall amount of hours your cpu spy is showing. Two: I said my higher steps are showing a 0% usage, but the time in use is displayed, so until that time outweighs my overall time in the lower slots, it'll continue to not display a bar for the higher slots. You can always reset your cpu spy when testing if you are doing so after a night of your phones deep sleeping. I hope that helps :)

Purian23
[Samsung Galaxy Nexus] shawnaye:
Subscribed to thread, anticipating results from current users regarding battery life.

Just a note to point out, i'm no expert or what, but during my Galaxy S2 days, the lesser Schedulers and Governors a kernel had, the better they were, less in this case was better. Case in example, franco's kernel only has a few options and he's isn't doing badly, haha.

Again, not an expert, just something i noticed from my previous phone's development.
[Samsung Galaxy Nexus] crixley:
I'm loving this kernel... Super smooth and I get 4 hours of screen on time on average. Running intellidemand/deadline 384/1230
[Samsung Galaxy Nexus] jjhiza:
I guess time will tell on this. I'm not sure

why the amount of governors/schedulers would make any difference in battery since, if they're not being used, they are just dormant code, and shouldn't have any effect on anything. It's an interesting point though...I'll keep an eye out for any variance now. As for battery results, the kernel was just released 2 days ago, so many people are still felling things out, and deciding on their optimal setup. I'm sure some benchmark and battery results will come flooding in eventually. :)

I plugged my phone in at 11% yesterday, because I needed to... bit prior to that, I had about 7 hours on battery, with roughly 3:15 screen on time. I'm using Intellidemand/cfq, and I've found it to be really nice. I'm at 230/1230 :)
[Samsung Galaxy Nexus] shawnaye:
Ah if only i could remember the reasons.

My best example is this, http://xdaforums.com/showthread.php?t=1576355

N.E.A.K kernel by simoene, it was one of the community's favourite kernel for a period of time, then soon gokhanmoral of siyah kernel just dominated everything due to the amount of tweaks he put in and dual-boot.

Hope that can provide some insight, especially with the author's main post.

edit: SpeedMod is an even better example, even lesser tunables and it was highly used back in the day.

http://xdaforums.com/showthread.php?t=1574218

i'm not saying tunable options are bad or anything, i love em. but i was thinking if a certain few options can be phased out, like eg. VR, or lazy gov, etc etc. those rarely used ones, and instead focus on those that are highly used.
[Samsung Galaxy Nexus] gm007:
First charge cycle and still have 34%,default setup.
[Samsung Galaxy Nexus] ak:
Every time I read the various threads I see people write "i have a sod" or "sod +1" and each time the sadness rises in my mind.

I can not understand what meaning can have this kind of statements in a thread, only serve to fuel the fear that you know the problems with the kernel when in fact there are none.

As those who invest the time to develop, those who use what is developed should contribute reports of serious and detailed. :good:
[Samsung Galaxy Nexus] differentstyles:
I'm using your Kernel since yesterday and it is working great. The whole time I had trouble with trinity and Franco and it's the first time now that I'm happy with 4.2. and 4.2.1. Thanks so much. It is working great with xeylon.
[Samsung Galaxy Nexus] sajty:
I think, that is clear, that main reason of sod is hotplugging. I tried stock interactivex and got sod during charging. Now I tried PegasusQ with raised screen off frequency to 700MHz and I survived without sod.

I know, that v10 is marked as last 4.1.2 build, but will be those issues fixed for 4.1.2 too? I would like to stay with Zen :thumbup:
[Samsung Galaxy Nexus] bigbear6708:
Put specifics in the rootz thread...will again. On 4.1.2, interactive gov. From what I have read it seems to be happening when charging overnight.
[Samsung Galaxy Nexus] NEtik:
Hi, i like this kernel and i have a question, both franco and zen, need for speed runs like "slow motion" (not lagged but slow). However with ak kernel runs smoothly. Is there any solution for this? thanks!
[Samsung Galaxy Nexus] bar_rodoy:
I have random sod. I am on stock rom 4.2 with default frequencies...
[Samsung Galaxy Nexus] bbedward:
SoDs i may have you resolved for v11, but more info please.

- ROM

- Key apps (franco/trinity/setcpu/PGM/etc.)

- Settings (governor/min/max/schedulers/governors)

- Previous kernel (if applicable), to determine what ramdisk you have.
[Samsung Galaxy Nexus] bigbear6708:
Using sourcery 4.1.2

Trickster app

Interactive

230-1280 , 576 screen off

Happened while charging overnight

Popcorn kernel was previous
[Samsung Galaxy Nexus] jjhiza:
You can always try a volume mod, guys. I use this one, and it works really well. :)

http://xdaforums.com/showthread.php?t=1748803
[Samsung Galaxy Nexus] gm007:
Try not to underclock, use min 3xx and try again.
[Samsung Galaxy Nexus] Sik-1:
Yes there is a fix and u need to find the modded need for speed app.

The reason it runs on ak is because its running the game at a predefined CPU speed which the game checks for and changes the graphics to suit the phone, the modded app gives you the ability to set the CPU speed that the game uses to check and your then able to run any kernel :D

Ill try and dig up the link for ya

---------- Post added at 12:29 PM ---------- Previous post was at 12:25 PM ----------
[Samsung Galaxy Nexus] sajty:
- LiquidSmooth RC9 (Android 4.1.2)

- Trickster Mod, PGM

- InteractiveX, sio or noop (not 100% sure), min 230, max 1036, screen off 576

- default of LiquidSmooth
[Samsung Galaxy Nexus] gm007:
Don't use 230 freq.
[Samsung Galaxy Nexus] bigbear6708:
Yeah... I've made that change as well as bumped the screen off up.. won't know till tomorrow though.:D
[Samsung Galaxy Nexus] RobBull69:
- AOSP R7 Jelly Bean 4.2.1 JOP40D + Kernel v3.0.53 Linaro

- Franco App

- Stock governors, as set by the kernel

- stock kernel JOP40D kernel (not the linaro kernel that came with the ROM)

It was charging overnight and I received an email ovrenight, so the LED was blinking, but the phone would not wake.Had to do a battery pull. The only tweaks I had in the Franco app were color setting and Wi-Fi Fast.

Edit: Since updating the max screen off to 729 and my phone is absolutely purring. I've been trying to re-create the same situation that gave me the SOD and it's been running rock solid.
[Samsung Galaxy Nexus] sajty:
230MHz will not be the problem i guess.I used 230MHz with Lean and Air Kernel with no problems.Or at least shouldnt be.
[Samsung Galaxy Nexus] friedCELLS:
Wrong post. deleted..
[Samsung Galaxy Nexus] gm007:
I think you should try not using it and see if the sod is solved,like this the dev will be aware and fix the issue.
[Samsung Galaxy Nexus] NEtik:
thank you! the performance in max quality is perfect now! :)
[Samsung Galaxy Nexus] purian23:
We are looking to push a rocking v11 update for you all this evening. Many changes upon user feedback. Also a nice line of added Governors and now introducing all three 307/384/512 GPU's
[Samsung Galaxy Nexus] purian23:
Kernel Update!!!

Introducing along with AffinitySERIES ROM

On our Site, XDA & Rootz Forums

v3.0.53-ZenSERIES v11 Kernel

*The ProdigyX*

Fast, Smooth, Responsive & Battery Friendly

Unified Kernel for Toro/Toroplus/Maguro

Two Versions:

ZenSERIES Kernel v11 4.2

ZenSERIES Kernel v11 4.0/4.1

3.0.53 is the latest Upstream Google Source

Built from 4.7.2 GCC Customized Zen ToolChain

[B]ZenSERIES_v11[/B]
- Reverted some DSS+OPP & SR adjustments (May fix SoD some users are experiencing)
- Raised default screen_off_freq to 729.6MHz
- Added 512MHz GPU clock setting (512 in progress for some users)
- Available GPU options are 307/384/512 (384 still default)
- Re-did ondemandX (suspend/wake code + CPU hot plugging)
- Added adaptiveX governor, adaptive with suspend/wake code + CPU hot plugging
- Added intellidemandX governor, intellidemand with suspend/wake code + CPU hot plugging
- New list of governors with early suspend/wake/hotplugging*
- InteractiveX, pegasusq, adaptiveX, ondemandX, intellidemandX
- 4.0/4.1 kernels will progress maybe another few builds for stability

ZenSERIES Kernel v11 4.2

Main Download

ZenSERIES Kernel v11 4.0/4.1

Main Download

Enjoy!

See OP for further information!

Thank you

Android Developer Alliance​
[Samsung Galaxy Nexus] mitchell.23:
The updates are coming so fast lately. So far v11 with xylon0081 seems great!
[Samsung Galaxy Nexus] androidkid311:
You guys are crazy lol. (Y)
[Samsung Galaxy Nexus] harrybigs:
Great job on the kernel guys. Flashed v10 yesterday and got 2h of screen time with 49% of juice still left. No settings change.

Will wait to upgrade v11 as i want test v10 for another day :)

Edit: on Xylon v81
[Samsung Galaxy Nexus] BurnOne77:
I normally use another kernel but I have been completely unhappy with anything other than 4.1.2 on my phone. This kernel changed that ! Flashed v10 then v11, love the options paired with trickster everything one could ask for and feels very smooth with xylon 0082 rom. :good:
[Samsung Galaxy Nexus] Vladivid:
Thanks, man! However there is a question. Why your kernel isn't set over anarkia kernel? Bootloop. Any incompatibility?
[Samsung Galaxy Nexus] jjhiza:
Not really 100% sure what you're asking, but the two kernels are different. As such, we suggest wiping cache and dalvik prior to flashing, to avoid any problems. :)
[Samsung Galaxy Nexus] viscocesco:
Ada Kernel v11 + Xylon 008.2 are the best combination

Thank you for you great work! :thumbup:

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Vladivid:
Doesn't help. Only installation of other kernel (for example, franco) and then ada kernel. Or on pure ROM.
[Samsung Galaxy Nexus] differentstyles:
This kernel is amazing. in combo with xeylon it is so smooth and absolutely stable. Gosh.
[Samsung Galaxy Nexus] musashihatred:
Aospa b5 + zen v11:. Awesome :) i love the colors btw. Looks so sharp and accurate color :)
[Samsung Galaxy Nexus] gm007:
Because they have different ramdisk.
[Samsung Galaxy Nexus] Craxx:
Hy

is it only me or are there in zen11 only 2 tcp versions? I miss Westwood?

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] sajty:
Westwood was not in 8,9,10 either.
[Samsung Galaxy Nexus] Craxx:
Ohhh really?? But in version 10 there where much more to choose. So is cubic the best?

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] viscocesco:
what is the best governor for battery and performance?

there are too many governor!
[Samsung Galaxy Nexus] shinydesert:
I always end up using savagezen+zen for that.
[Samsung Galaxy Nexus] sajty:
Devs,you are simply sick!There is any problem with your kernel and you are immediately working on fix.Fuc*ing good job!

In dictionary,under word "support",there should be written "Zen devs work".
[Samsung Galaxy Nexus] Invicta:
Is this kernel recommended for use with the stock rom? Does it improve the user experience at all?
[Samsung Galaxy Nexus] bbedward:
Zen actually uses the existing ram disk on the device, and makes whatever changes and optimizations it needs to in the ram disk.

Its just incompatible when its repacked with ak's ramdisk, seems like that's the only one that doesn't work.
[Samsung Galaxy Nexus] ak:
My kernel use XZ compression, probably this is the problem :good: with universal ramdisk of zen kernel.

Ramdisk e Kernel are OK.
[Samsung Galaxy Nexus] bbedward:
Thanks :), good work on your stuff, nice to see you contributing here as well, I like OS collaboration :thumbup:
[Samsung Galaxy Nexus] ak:
nice, the same for me ... thanks a lot guy :good:
[Samsung Galaxy Nexus] kyokeun1234:
Hello, I've first tried v8 and v9 of this kernel and had great experience but suffered from SODs... So I've been using Franco kernel and I've been satisfied with it. Then I noticed that you guys had already released v11 so I knew I had to try it and man! I'm glad I did :D

Everything is smooth, battery life has increased by a lot, no minor lags to be found, and no SOD!!!

Thanks you guys for your hard work and hopefully you guys update one of my all time favorite ROM too, AffinitySERIES ROM :)
[Samsung Galaxy Nexus] djluis48:
Hi guys great work here! I would loke to know if there is a way to reset back to stock all the color settings that the kernel changed, now everything seems kind of blueish, reminds me of my old Sgs2. Is there a way to reset them? Thanks!
[Samsung Galaxy Nexus] bbedward:
Colors are stock, you can use trickster app/Franco/Trinity app to set contrast to 0 (which is the only change we make)
[Samsung Galaxy Nexus] ntorresla:
can you share the optimal settings for better battery? governers and things like clock speeds...

im curious
[Samsung Galaxy Nexus] sajty:
OndemandX should be great for battery. i/o schedulers are very close,not big difference. Frequencies for me - min 384MHz, max 1036MHz.
[Samsung Galaxy Nexus] ntorresla:
what about cpu speeds...

I just want to know what people use
[Samsung Galaxy Nexus] sajty:
As i wrote,384 min and 1036 max.Absolutely enough for common work.You can go lower than 384MHz as min freq,but battery effect is minimal and 384MHz looks more stable than 230MHz.
[Samsung Galaxy Nexus] bigbear6708:
I posted my kernel settings in the root wiki thread...very good battery life and performance with them
[Samsung Galaxy Nexus] Craxx:
Please can you post link:)

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] pelm:
can you post the link please i can't find it
[Samsung Galaxy Nexus] albsat:
I changed to SavagedZen but i didn't find it smooth at all. Back to interactiveX governor. I got a good battery life using Wi-Fi but i think every kernel suffers once you start using data connection.
[Samsung Galaxy Nexus] cmoG530:
Seems as if I'm the only one having SOD issues. I'll play around with the settings Lord willing and see what happens. Could it be due to pgm though?
[Samsung Galaxy Nexus] bbedward:
Not sure if there's a correlation between pgm or not, can you share your settings?
[Samsung Galaxy Nexus] bigbear6708:
Using these same settings on v11.... money so far... Thanks again for the great kernel

http://rootzwiki.com/index.php?/topic/35781-[KERNEL]-{ADA}-*4.1/4.2*-v3.0.53-ZenSERIES-v11-*The-ProdigyX*-{Jelly-Bean}-[KERNEL]#entry1039858

Bbedward stated you can change these parameters on interactive x as well.. I prefer interactive...
[Samsung Galaxy Nexus] Jose Viegas:
I'm using pgm and no sods with min freq 384, interactivex and zen here, great v11 btw!
[Samsung Galaxy Nexus] sajty:
So far no SoD with OndemandX,min freq 384.
[Samsung Galaxy Nexus] BurnOne77:
been running 192/1306, 384 max screen off for 2 days now and no SOD, working perfectly using ondemandx and zen.
[Samsung Galaxy Nexus] cmoG530:
Thanks and the voltages are stock.
[Samsung Galaxy Nexus] reaper000:
Have had problems with retaining Bluetooth connection with min setting of 192. Increasing min to 384 resolved it.
[Samsung Galaxy Nexus] bbedward:
You're a little far from stock. Dont don't 792.6 min, no reason to.

Also, don't set profiles for the governor when screen off, if you want to save battery pick an an X governor that hotplugs.
[Samsung Galaxy Nexus] GCbard:
very snappy kernel, but why does antutu crash at 12% when I run a benchmark with this kernel?
[Samsung Galaxy Nexus] jjhiza:
What do your settings look like? AnTuTu never crashes on me, unless I'm messing with voltages or something like that. :confused:
[Samsung Galaxy Nexus] GCbard:
with trickster

scheduler - sio with 2048 read ahead

governer - interactive stock settings

max cpu - 1612800fsync - off

gpu - 512
[Samsung Galaxy Nexus] billouetaudrey:
Maybe OC too much...

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] jjhiza:
Agreed... Your problem is probably the 1612 speed. While it may work fine fire normal use, AnTuTu really stains the CPU, and will occasionally cause hot reboots. Do you have similar issues at lower speeds?
[Samsung Galaxy Nexus] sajty:
Can somebody describe adaptive governor?Cannot find it even with Google.And if Google something cannot find,it doesnt exist :D.
[Samsung Galaxy Nexus] GCbard:
I got out to run. Thanks for your help!
[Samsung Galaxy Nexus] purian23:
Per bbedward;

All of the X governors are the same as their non-x counterpart except with suspend/wake + hot plugging support.

Pegasusq hot plugs as well.

So all of the governors with suspend/wake code and CPU hot plugging are: adaptiveX , interactivex, ondemandx, pegasusq, and intellidemandX.

Adaptive is essentially ondemand based, but focuses more on latency demanding and higher performance applications.
[Samsung Galaxy Nexus] nziria:
bootloop on xenon-HD(latest) for me, come back to AK kernel :(
[Samsung Galaxy Nexus] ak:
If you want to test zen after AK you have to flash stock kernel my ramdisk have ZX compression :eek:
[Samsung Galaxy Nexus] djluis48:
Which of the X governors hotplugs?
[Samsung Galaxy Nexus] rasa92re:
Great work devs. I have nevee had such great battry life. I have been on Zen since v7 (which unfortunately has been the most stable for me).

Here are my observations: I have had the SoD multiple times. I was primarily using interactivex. When I switched to pegasusq, I had an even higher rate of SoD. At this point, I was suspecting there was an issue with hot plunging or even worse, the suspend/sleep profiles of the governors. So, I tried ondemandx and again suffered SoD.

Something was telling me it had to be PGM2 though when I switched to the regular interactive governor and only suffered one SoD in twelve hours.

To be sure of the point, I went back to Trinity @1420 MHz cpy and 384 MHz gpu. I set my governor to interactive and surprisingly didn't have one SoD, which was within a 24 hour period. I set my governor to on demand and haven't had a SoD situation in about 36 hours, which was when I last switched governors.

For all of these test runs, I reenacted the scenarios under which the SoD occured: either over night while I slept or under mild multitasking (by going between Tapatalk, text messaging, app news, and occasionally a phone call). Sometimes, the phone would freeze on lock too. Unfortunately, I could only induce the SoD on Zen and not Trinity. This has lead me to suspect that PGM2 is not playing well with this superior kernel. I am no programmer so I can't be too technical but could the voltages have something to do with the issue? I just really want to go back on Zen.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gm007:
Read the first post in this page.
[Samsung Galaxy Nexus] cmoG530:
Thanks. From what I read, people were saying to keep the min at 700 and to not go any lower. This I read from multiple forums (I'm guessing it was rubbish in actuality.). I will try what you said. :) Thanks :D
[Samsung Galaxy Nexus] purian23:
Hello,

My post a few above should answer your question : )
[Samsung Galaxy Nexus] sajty:
Devs,any idea,what is causing SoD´s?There is more and more reports,on Rootz too.Strange,i thought,that main reason is hotplugging,but many reports about interactive governor too.I am a little bit happier in this way,only one SoD so far.
[Samsung Galaxy Nexus] killersloth:
I have run zen since they released it for us, and have never had sod. I run 192mhz -1132.8mhz with screen off 576mhz, interactiveX. Stock voltages, 2048 read ahead buffer, everything else stock.

Sent from my Galaxy Nexus using Bacon
[Samsung Galaxy Nexus] billouetaudrey:
Do you use pgm ?

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] Craxx:
I use pgm and have also NO SOD :)

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] bigbear6708:
Are these sleep o death happening on 4.1 or 4.2 mostly...Im on 4.1 and yet to have a sod...but as great as the weekend on this kernel was...I still need to wake up for work tomorrow....lol
[Samsung Galaxy Nexus] sajty:
SoD on both,4.1 and 4.2 too.At least by comments of other users.
[Samsung Galaxy Nexus] adio201:
I get sod and I'm on 4.1 using pgm2 also
[Samsung Galaxy Nexus] cmoG530:
Followed instructions and I still got SOD. I have no other choice, but to think that pgm really is the culprit. I'm on 4.2 by the way. I disabled it, so I will report back Lord willing for an update.

*update*

It's the kernel. I disabled pgm and still got it. Rolling back to v10 for testing.
[Samsung Galaxy Nexus] gm007:
I think the dev should release a test kernel for Sod problem with higher voltage.
[Samsung Galaxy Nexus] jjhiza:
We're always working to bring you guys the very best, and we'll continue to do so. None of these SoD issues were present until very recently (4.2). Rest assured, we'll address the issue, and get it sorted out for everyone.

In the meantime, you can raise the voltages yourself, and see what kind of results you get. Some feedback in that department could really be useful. :)
[Samsung Galaxy Nexus] gm007:
I don't have any sod and the kernel is awesome but for users who don't know how to play with voltages it's better to release a test kernel with higher voltage cause as you know not all the phones behave the same.
[Samsung Galaxy Nexus] jjhiza:
That's true... all phones do operate differently. We'll be back at it tomorrow, and see if we can hammer out these issues. We stick to a Monday-Friday schedule with releases, because everyone has families and/or other obligations to attend to over the weekend.

I'll contend though that anyone who is interested in flashing kernels should be able to adjust voltages at the very least. Now that we have kernel control apps (some free), the process couldn't be easier. If people aren't willing to learn a tiny bit about what they're putting on their devices, they probably shouldn't be rooted in the first place. I don't mean this as an insult to anybody at all... It's just a general observation of the Android ecosystem in general. On the whole, the majority of Zen and Affinity users are very knowledgeable, friendly, and helpful, which is a big reason why we can do what we do. :)

There are a lot of variables with the SoD issues though... flash method, voltage, pgm, CPU speed, hotplugging, etc, but like I said, we'll get back in the lab tomorrow, and see what we can do. Thank you for the feedback and suggestions... they're much appreciated. :thumbup:
[Samsung Galaxy Nexus] bigbear6708:
I had a sod on v10.... Yet to get one on v11. Using interactive 230/12xx, pretty heavy usage. All these reports have scared me...I rely on the phone for alarm m-f! Lol
[Samsung Galaxy Nexus] cmoG530:
None taken here. I personally just don't deal with voltages. I keep them however the kernel creator(s) put as default. Thank you for your time however, because not all developers take the time to care for the community.
[Samsung Galaxy Nexus] jjhiza:
Just wanted to say thanks to all of you guys for helping us push Zen and Affinity forward... You guys are awesome! Here's a small gift from me to you, in UCCW form. ;)

Get them here: http://xdaforums.com/showthread.php?p=34923764
[Samsung Galaxy Nexus] sajty:
My only SoD so far was with interactiveX governor. OndemandX and adaptiveX run with no problems for me. I hope, it will be so during night too, I must go to work tomorrow morning and my phone must wake me up :D
[Samsung Galaxy Nexus] bigbear6708:
Lol...same boat man, no sod yet, but reports gotz me running, had to nandroid back. Must.wake.up. was a great weekend tho
[Samsung Galaxy Nexus] jjhiza:
Back on the kernel topic for me... these are some of the governor values I've been using recently, and they've been great.

Intellidemandx/bfq

1305-384; 729 max screen off

... and my usual sysctl tweaks
[Samsung Galaxy Nexus] billouetaudrey:
What app do you use ?

Envoyé depuis mon Galaxy Nexus avec Tapatalk