yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] elmexicanoalto:
I had about 3 SODs with V12. Flashed V13 and haven't had one issue.. Have a feeling I'll have my first SOD shortly after this lol
[Samsung Galaxy Nexus] teniente_dan:
V13 has higher voltages In comparison with v12 final.

Are the same from v12 beta? Because those were ok for me

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] billouetaudrey:
OK I try it After next sod...

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] 32bit:
It's very promising idea, imho, but I have a problem with zeneractive: after a some time of using it the second core became more and more lazy to wake up. After a day it's never wakes up finally and I've got virtually a single core CPU. :)

So I've been forced to change this governor to another one (PegasusQ, intellidemand or something else).
[Samsung Galaxy Nexus] ak:
Have you try with ondemand or ondemandx?
[Samsung Galaxy Nexus] billouetaudrey:
No sod on V13 since 3h...

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] TheMorpheus:
After my first SOD I've set the screen of speed to 576 and I haven't had a problem since then!

Keep testing!
[Samsung Galaxy Nexus] grey.ghost:
The new governor is working extremely well even on a Rom with memory leak.
[Samsung Galaxy Nexus] bbedward:
This is certainly winner for weirdest bug of the day ;)

I have not experienced this myself and cannot think of exactly what could cause it, but I'll check it out and see if I can find anything.

Anyone else experience this?

None of the other governors work like zeneractive :) closest ones as far as hotplugging would be pegasusq or hotplug.
[Samsung Galaxy Nexus] Craxx:
Perhaps this is the reason for many sods here with pgm. Now i disabled pgm and see...

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] shivasrage:
Hi, at all

I would like to try this kernel and now I would ask...

Is there any app recommended to change the values of the kernel...

Thanks in advance...

S.R....
[Samsung Galaxy Nexus] gm007:
You can use trickster mod apk from playstore.
[Samsung Galaxy Nexus] TheMorpheus:
Another SOD, pulled the battery and flashed V13 beta... Let's see how it works
[Samsung Galaxy Nexus] billouetaudrey:
Sod with V13 too...

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] ak:
Have you used min freq 192 or 230?
[Samsung Galaxy Nexus] billouetaudrey:
Nop, all Default...

But yesterday I have restore all backup with twrp after testing an other rom... Maybe that...?

Not have sod after a night... One sod after SMS received (Light flow work again) and after endcall...

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] reaper000:
SOD last night (seems to occur when I charge it for the night).

V12

Cpu: min 384 max 1612 idle 538

No changes to volting

Zeneractive gov

Will try V13b tonight
[Samsung Galaxy Nexus] barbac666:
Back to interactive, zeneractive cause SOD.

3 SOD in 24h.

384/1230

Zeneractive/zen

No UV, GPU 384

Xylon v11 rom

depuis mon nExUs pRiMe
[Samsung Galaxy Nexus] BurnOne77:
I got 2 SOD but both seemed to be as the fan was charging and reached full charge on Zen 12.

I set 576/1305 and Only had 4% battery drain in 7 hours and no SOD while it was charging. Using Xylon v11, I like it :good:
[Samsung Galaxy Nexus] bbedward:
Still feeling that SoDs are because of some users voltages on 4.2 roms. Something must have changed there.

Stock voltages for reference:

350MHz: 1025mV

700MHz: 1200mV

920MHz: 1325mV

1200MHz: 1388mV

So not unlikely some of my combinations of new frequencies, smartreflex margins, undervolting are causing some issues for some users :good:

There's also several other factors, but I'm very doubtful that zeneractive is causing SoD either.

I'm working all of these issues out, seems like the kernels with limited to no SoD are the ones that don't undervolt at all. Still odd to me, because there were no issues with this on 4.1
[Samsung Galaxy Nexus] Braneless:
No v13 SOD since turning off PGM last night.
[Samsung Galaxy Nexus] jdec529:
Its really amazing how each phone acts so different also. I'm running v12 under voted 20 to each slot. 190-1305, zenractive on rasbean and havent had a single SOD or lag or anything. Its running stellar on my end.

Gnex with Rasbean and Zen.
[Samsung Galaxy Nexus] gianton:
Do you have PGM installed and enabled?
[Samsung Galaxy Nexus] jdec529:
Not at the moment. I disabled it when i first started getting SOD with a kernel from another dev.

Gnex with Rasbean and Zen.
[Samsung Galaxy Nexus] billouetaudrey:
I try change voltage and frequencies... Wait and see...

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] Craxx:
Since i disabled pgm no more problems..

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] billouetaudrey:
My 3 SODs this morning are without pgm...

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] lsv-1:
Just for the record, I've been using lean kernel since I started having SoDs with version 12 and these are the voltage values (No SoDs)

Sent from my Nexus Prime JB 4.2
[Samsung Galaxy Nexus] reaper000:
Update: flashed zen13b, and enabled Juice Defender. Immediately got three SODs. Have since reverted to Zen11 which plays nice with JD. Note that the overnight SOD on z12 was without JD
[Samsung Galaxy Nexus] sajty:
I doubt, that SoDs are caused by PGM. Air Kernel is running great with PGM, not even one SoD. I still think, that main problem is voltage.
[Samsung Galaxy Nexus] cmoG530:
So...are these SOD in the minority or majority?
[Samsung Galaxy Nexus] anthonyp326:
Running v12 stock...384 1400 384 no other changes no sod or reboots running it for days
[Samsung Galaxy Nexus] IT_Blackbelt:
minority, I've used this kernel on my rom, flashed at the same time, no sods for me, but I dont use the PGM or juice defender people are talking about. Right now while im updating and testing my rom, I leave all the kernel values at default.
[Samsung Galaxy Nexus] justibasa:
Anyway someone can pm me v11. I think I deleted it. Thanks.

Don't like me........BITE ME!!!
[Samsung Galaxy Nexus] purian23:
Kernel Update!!!

Introducing

v3.0.56-ZenSERIES v13 Kernel

*Zeneractive Lives*

Fast, Smooth & Battery Friendly

Unified Kernel for Toro/Toroplus/Maguro

- ZenSERIES_v13
- Updated to v3.0.56 upstream
- SoD work, Adjusted SR margins and voltages
- Replaced glados' color control with the CM/voodoo color control port
- Re-added some SR updates that were lost in v12
- Added some misc. updates/some from android-3.4
- Interactive upstream updates
- Decreased 512MHz GPU voltage slightly
- Zeneractive: upstream updates, also added tracing, boost, and boostpulse
- Zeneractive: Re-introduce set_speed_mutex*
- Prevents hotplugging from occuring while frequency scaling occurs*

ZenSERIES Kernel v13 4.2

ZenSERIES Kernel v13 4.1

Main Download

Enjoy!

See OP for further information!

Thank you

Android Developer Alliance
[Samsung Galaxy Nexus] TheMorpheus:
Thanks...Flashing now, I'll report back!

---------- Post added at 02:25 AM ---------- Previous post was at 01:29 AM ----------

Nope.... SOD just while I was starting to enjoy it!
[Samsung Galaxy Nexus] Braneless:
Turned off PGM: no sod for 24 hrs...turned it back on and had a sod within an hour. This is with v13.
[Samsung Galaxy Nexus] bbedward:
Raise the mpu voltages.
[Samsung Galaxy Nexus] jdec529:
V13 seems very smooth so far, but monitoring the cores with zeneractive governor it seems to spend much more time with one core off. Should it be??

Gnex with Rasbean and Zen.
[Samsung Galaxy Nexus] bbedward:
When load is low enough ;)
[Samsung Galaxy Nexus] jdec529:
Its seems to be smoother though. Should improve battery life in theory.

Gnex with Rasbean and Zen.

---------- Post added at 03:31 AM ---------- Previous post was at 02:59 AM ----------

Might have spoke to soon . my phone started lagging really bad so i rebooted and started bring voltage down in increments and couldnt get it to stabilize. Also with any notification my sound was very distorted. Back to v12 for me for now, which ran really good with my phone. Thanks anyways and will try v13 in am when i have a little more time to mess with voltages.

Gnex with Rasbean and Zen.
[Samsung Galaxy Nexus] crossen0:
Please don't hurt me if this has already been addressed but is color control not in v13 for a reason? I'm on the 4.1.2 variant.
[Samsung Galaxy Nexus] PandaKen:
V13 seems very smooth so far, but monitoring the cores with zeneractive governor it seems to spend much more time with one core offline?
[Samsung Galaxy Nexus] killersloth:
That's a good thing. :)

Sent from my Galaxy Nexus using Bacon
[Samsung Galaxy Nexus] kinfolk248:
Good news Zen team, Im back!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

And since youre back on an odd number, i'll give this a go...
[Samsung Galaxy Nexus] allgsmnetwork:
not stable and low perfermance !!!

at a 1.2 ghz on quadrant 24xx with franco kernel 342 over 3500 the best franco kernel have high performance
[Samsung Galaxy Nexus] afraaa:
how can we control GPU clock !!!? and what about those motrola shape widgets ?

---------- Post added at 02:22 PM ---------- Previous post was at 01:43 PM ----------

faux 123 kernel force close on GPU screen !! low performance io have but good battery life .
[Samsung Galaxy Nexus] ak:
quadrant is fck benchmarks ... use cf-bench by chainfire! :cowboy:

---------- Post added at 11:59 AM ---------- Previous post was at 11:58 AM ----------

You can use trickster app from market ... unistall faux app before. :good:
[Samsung Galaxy Nexus] afraaa:
thanks going to try ..

u are awesome thanks alot .. couldnt find it that easy .
[Samsung Galaxy Nexus] alizafar:
I don't know if u guys are experiencing this but after flashing v13

My second core is offline,switching back to 007 for a while before an fix is out ..
[Samsung Galaxy Nexus] barbac666:
If you use zeneractive, the second core is disable when is not use.

This is the hotpluging......

depuis mon nExUs pRiMe
[Samsung Galaxy Nexus] SahilC:
Just wondering, wouldn't that make it lag, with all of that moving around and turning cores on/off?
[Samsung Galaxy Nexus] alizafar:
Yep it causes serious lags :(
[Samsung Galaxy Nexus] bbedward:
Color control is there, it's a slightly different implementation (CM/voodoo one). I can't speak for other apps, but I only use trickster really and it's there. I'm kinda surprised some of the apps don't support the CM implementation :-O

apples to oranges really. If you change governors you may notice that extra few points. I still seem to get quadrant 2700-2800 though with fsync on.

The core will go an and offline based on load, not particularly abnormal. There is a bug, however, that I need to address. (When changing governor, if CPU 1 is offline the other governor won't bring it back online. I noticed hotplug does the same thing. I should just need to add a bit to enable all CPUs when the governor stops.

You tell me :P . To me, there is no system lag.The other core will go online pretty quickly when the CPU load justifies it.

As far as I can tell, system "smoothness" is not really impacted at all that I can notice, and benchmarks are about the same as interactive. I only released the governor because the hotplugging system seems to work well :cool:
[Samsung Galaxy Nexus] afraaa:
Low cpu performance .. Compared with franco and trinity .. Very good and powerful on gpu .. But poor on cpu . realracing on champion 4 and mc4 . lags too much even with 1.5 cpu .

I have game running smooth on previous trinity and franco kernels .thanks for trying .
[Samsung Galaxy Nexus] ak:
Have you implemented cpu hotplug also for interactive?

I have saw with my tests that the problem diappear when you do this. :good:
[Samsung Galaxy Nexus] in1400:
I think, there is no DeepSleep with "zeneractive" on in the Kernel!? :(
[Samsung Galaxy Nexus] bbedward:
There is, did you flash the wrong kernel by mistake? (4.1 version?)

I could resolve it by having the cpufreq driver itself bring all CPUs online when governor is changed or by having the other governors bring all CPUs online when they start, but I'd prefer to keep it contained inside zeneractive :)

Calling cpu_up on offline CPUs on GOV_EXIT should do the job, but testing it out :good:
[Samsung Galaxy Nexus] ak:
good ... very good .... guy. :good:
[Samsung Galaxy Nexus] in1400:
I don't think so, it's the "v3.0.56-ZenSERIES_v13.zip" :confused:

EDIT says:

After a re-wipe of cache and dalvik and Fix Permissions everything runs fine!

Thanks to bbedward!! :cowboy:
[Samsung Galaxy Nexus] dehein:
Does WiFi direct, Bluetooth and tethering work with this kernel. Or do i need an alternative?
[Samsung Galaxy Nexus] bbedward:
Yes to all 3.
[Samsung Galaxy Nexus] anthonyp326:
V13 is running on 1 core tried all setting ...and used same settings in v12 and had 2 cores running on v12
[Samsung Galaxy Nexus] bbedward:
Assuming you changed your governor while the second CPU is off. Working on a fix for it, swapping to an X governor and toggling your screen on/off will turn your other CPU back on. The non-hotplugging governors won't do it.
[Samsung Galaxy Nexus] anthonyp326:
Is zenx not running both cores on v13
[Samsung Galaxy Nexus] bbedward:
ZenX in v13 removes the second core after CPU load has been <= 35% for 5 seconds. It re-enables the core after CPU load has been > 35% for 0.1 seconds.

Is that the behavior you're seeing or is there a bug otherwise (permanent CPU 1 off) ?
[Samsung Galaxy Nexus] anthonyp326:
I switch governers to x...on 13 couldn't get the second to turn on..anyone else...

---------- Post added at 11:00 AM ---------- Previous post was at 10:44 AM ----------

Okay both are on after reboot..only thing I see that I don't understand is that I'm over clocked to 14200 but don't see it hit that number..using trick mod and cpuspy and is monitor to validate

---------- Post added at 11:04 AM ---------- Previous post was at 11:00 AM ----------

Also confirmed that it gets lazy and to turns back on when lock and unlock of screen
[Samsung Galaxy Nexus] Craxx:
Hy bbedward with 12 Bluetooth disconnect when screen is off. After flashing air kernel all works fine. Just a info.

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] anthonyp326:
What is ur max mhz when screen is off
[Samsung Galaxy Nexus] Craxx:
With air kernel 598 and with zen it was 576 i think. I also have no problems now with pgm with air kernel :D

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] bunnahabhain:
I am using this kernel since today (V13) and it is very smooth... battery is a bit on the worse side compared to franco r300! I got a soft reboot while turning screen on/off on zeneractive, so i decided to use interactive again. All in all really a great cutting edge kernel!

I would appreciate a couple of more releases for 4.1 ROMs to enhance stability! Really great work though. And bbedward doesn't get tired to provide some information about the progress of his efforts - i like that! :D
[Samsung Galaxy Nexus] reaper000:
Update #2: flashed Zen13 (non-beta) last night with JD aboard. Same settings as previously, but this time, no SODs at all!

Thanks for whatever changes were made.
[Samsung Galaxy Nexus] purian23:
Thank you all for these reports, of course we are driving insane in every which way to fix these SoD's from occurring that seems to be the plague to some of the kernels out there and mostly related to 4.2. Either way we truly appreciate all feedback though, good and bad. From your reports it just helps us grow and make a better kernel. Definately something we'll work out and be able to call our kernel one the best of the best to date. The kernel is currently packed with some real custom one of a kind work from our hard working developer bbedward, for this reason we'll not let it fall to the wasteside. Please stay tuned for the upcoming releases.

Purian23
[Samsung Galaxy Nexus] kinfolk248:
MIssion Debriefing...

-installed v13 4.1 on JBS 3.2 last night

-230mhz / 576mhz / 1.1ghz / zenX gov

-zen/cubic/384gpu - 512 still flakes out the screen, trick color scheme

-pros - nothing to complain about yet

-cons- nothing to complain about yet lol
[Samsung Galaxy Nexus] rzgomba:
experiencing SOD on V13 4.1

I have CNA 3.8.0

No OC

Zeneractive

Min 384

Max 1228

Tried cache & Dalvik wipe and fix permissions but no difference.

Otherwise gone back to V12

Please help.
[Samsung Galaxy Nexus] teniente_dan:
Same kind of sods, all during charge at night

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] dre1187:
I've been running your kernels since the beginning and have had nothing but great experiences with each kernel. No SODs at all. I installed v13 this morning and got my first SOD. I was running it with stock settings when it occurred. When i booted the phone back up i changed c the v governor to interactive instead of zen and all seems to be working great again! Any logs i can pull to help out?

Thanks again for all the great work!!
[Samsung Galaxy Nexus] Braneless:
Are you running PGM? I disabled it and have not experienced an sod since.
[Samsung Galaxy Nexus] dre1187:
Nope i don't believe so unless it's enabled by default. Was running it on fresh kernel install when it occurred
[Samsung Galaxy Nexus] rzgomba:
What is PGM.
[Samsung Galaxy Nexus] Savant:
An application that allows you to turn your screen on and off by gestures.https://play.google.com/store/apps/details?id=net.ponury.pgm2free
[Samsung Galaxy Nexus] bbedward:
I'm aware of quite a few things that need to be fixed from v13 :-O

Working them out though ;)

I realized some flaws in the zeneractive hot plug thread and will be working them out by tomorrow hopefully :)
[Samsung Galaxy Nexus] rzgomba:
Hey through mistakes comes greatness. Keep up the good work.
[Samsung Galaxy Nexus] WoodroweBones:
Hey guys I just wanted to clarify what a SoD was.

I believe my phone is experiencing SoDs using v13 as well though while the screen doesnt turn on the phone actually runs in the background. For example my alarm will still go off, I will still hear messages come in, etc. but the screen will just not turn on.

If thats an SoD then I have them regularily on v13. Went back to v11 and its been working great!
[Samsung Galaxy Nexus] iifuzz:
sooo does this work for 4.2.1 or just 4.2 ? :x

All i see is talk about SOD!
[Samsung Galaxy Nexus] Sik-1:
It works on both, SOD is the issue with 4.2.x
[Samsung Galaxy Nexus] gln003:
Installed the new kernel yesterday and changed governor to interactive. Using paranoid android 2.99 BetaSeven. No SODs since one week (there using ZenSERIES 12) and good performance.

Nice kernel and thnx for the good work!
[Samsung Galaxy Nexus] aleve1983:
It s not true, i have regular sod in 4.1.2, in all version of this kernel 11, 12, 13. I use pgm and my governor is interactive. Todey after sod i restart my phone open trickerst mod and i see that core 2 is offline with governor incterattive

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] alizafar:
As far as I can tell, system "smoothness" is not really impacted at all that I can notice, and benchmarks are about the same as interactive. I only released the governor because the hotplugging system seems to work well :cool:[/QUOTE]

Yah that's the trouble.. At the moment i noticed the core state, i was listening to music and the experience was VERY LAGGY with the first core on full load! So tried switching the governor and the io but there was no luck..
[Samsung Galaxy Nexus] billouetaudrey:
Hi sod this morning with V13 zeneractive... Snif snif

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] WoodroweBones:
Whats not true? Just because you experience something doesnt mean everyone else does.

v11 is what I reverted back to simply because it works perfectly. No SoDs at all
[Samsung Galaxy Nexus] giorgis91:
I'm on v13 and I noticed that when I used the phone when it's plugged in charge, it become a bit warmer on the upper side. This didn't happen with pervious versions.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] bbedward:
No worries guys, just put some work in :D

Zeneractive got the axe, renamed to ZenX.

Differences:

- The hackiness of total_below/above_unplug_time arrays got the axe. Now we actually set and use the data set on each CPU as we should have all along.

- Ditto last_time_above/below_unplug_time

- We now calculate the average load across _all_ ONLINE CPUs instead of using the potentially incorrect current CPU load.

- On device wakeup, all cores are forced to wake up

Changes for those curious in diff form:

http://pastebin.com/Jz2vWp4z

Commit:

https://github.com/AndroidDeveloper...mmit/2c7e1914031cf2983826808b9d9dee7c713d2113

Only thing I'm still working out is getting the governor to insert all offline CPUs when it stops :D. Otherwise, when switching to a non-hotplugging governor if the auxillary CPU is off, that core will never be re-enabled unless a hotplugging governor is activated again.

Have a bunch of other fixes and cool things in v14, which will all be in the changelog when its released.
[Samsung Galaxy Nexus] ak:
Very clear! :thumbup:
[Samsung Galaxy Nexus] -freedroid-:
Is it possible to change back to glados' color control? IMHO the color was better before.
[Samsung Galaxy Nexus] cms5423:
Use trickster app to choose the color profile that you like best. The color control implementation shouldn't effect that too much at all. I'm definitely fine with CM color control method
[Samsung Galaxy Nexus] bbedward:
The default colors actually haven't changed. Changing the colors should work the same as before, I just prefer the CM implementation because it seems a bit cleaner and seems to be more actively maintained :good:
[Samsung Galaxy Nexus] ianandamy:
V11 is super stable and fast for me too 12 and 13 are bad news sod quiet a bit
[Samsung Galaxy Nexus] gln003:
Mine too...
[Samsung Galaxy Nexus] cmoG530:
Reporting in. I've been using v13 for almost a day. No SOD's, PGM on and using Zenactive (sp?). Feels real solid and smooth. Thank you guys. :thumbup::)

>-Sent From Something That's From Somewhere-<
[Samsung Galaxy Nexus] bbedward:
Some of you have jumped the gun since v14 build is public on my goo.im :rolleyes:

Planning on tomorrow early release everything seems extremely solid so far.

So you're more than welcome to those v14 builds, just be careful anything I put on there that isn't announced may be risky ;)

*edit

The builds on there were updated around 4:30 EST, if you jumped the gun yesterday you may have several issues ;)
[Samsung Galaxy Nexus] kinfolk248:
soooooooo v14 is a go or what lol?
[Samsung Galaxy Nexus] elmexicanoalto:
*link removed*
[Samsung Galaxy Nexus] bbedward:
:(, if I wanted to post the link I would have, I only mentioned it because I noticed people have already downloaded it.
[Samsung Galaxy Nexus] kinfolk248:
ha so im guessing its a no then, so lets take finger off download button lol lol
[Samsung Galaxy Nexus] bbedward:
Its not a no, its a probably I just prefer to test and release on my own schedule
[Samsung Galaxy Nexus] kinfolk248:
damnit bb, idk what to do lol, you say it went public prematurely but got an update then someone posts a link then you rag them about it then you say its not a no just bothersome. you screwing with me, i got kobe and carmelo going at each other tonight, i gotta headache and a bone bruise in my shin, im gonna just wonder whats so impressive about 4.2 and if i need/want to upgrade... im just shot out smh lol smh lol...
[Samsung Galaxy Nexus] bbedward:
I post builds on goo. sometimes before they're released and what not. I noticed people have been downloading them so wanted to post a disclaimer, nothing wrong if you use them.

Im just wary now because I don't want anything I upload unannounced posted as if its a stable release. It may be or may not be.

Anyway, anyone who wants to is free to flash those v14 builds now anyway :-p, but they aren't official or supported or necessarily final yet.
[Samsung Galaxy Nexus] kinfolk248:
ya know i was messing with you, trying to project some of my annoy to someone else lol. you good player!!!!!!!!!!!!!!!! we cool, you cant upset me, im zen. hahahahaha, get it....im zen - im chill and the kernel is zen, i crack myself up lmao