yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Savant:
Looks like romtoolbox.https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox
[Samsung Galaxy Nexus] billouetaudrey:
Thx ! What's your sysctl conf plz ?

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] Savant:
That you would have to tinker by yourself and see what works for you. I know there is some posts in Francos thread and around xda. Search and see what can work for you.
[Samsung Galaxy Nexus] cmoG530:
I'm happy to report that I have no SOD's on v10, so far.
[Samsung Galaxy Nexus] BriVG:
On a 4.1 or a 4.2 rom?
[Samsung Galaxy Nexus] bradman117:
What ever u guys did on v9 was good! With keeping all default settings it manages to stay the coolest more than v10 and 11. Love your kernel guys good job! The v10 and 11 run great! Just prefer not as hott. +1!
[Samsung Galaxy Nexus] cmoG530:
4.2. Paranoid Rom.

d",b.Sent From My God Given G-Nexus.d,"b
[Samsung Galaxy Nexus] lordofcamster:
Bootloop with rasbeanjelly.... :sly:

:)
[Samsung Galaxy Nexus] billouetaudrey:
No problem here...

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] chevycam94:
AOSP 4.2.1_r1 (using 4.2 version of course, release v11), it kills the ability to connect Galaxy Nexus to LTE or CDMA. Only works on WIFI, but the data handoff doesnt occur. Not a ROM issue, as flashing another kernel fixes the problem.
[Samsung Galaxy Nexus] sajty:
Testing IntellidemandX and no SoD so far. I have tested InteractiveX, OndemandX, AdaptiveX and IntellidemandX - only interactivex gave me SoD.

By my experience and reports of other users it looks, that only interactive and interactivex governor is problematic. Or had someone SoD on different governor?
[Samsung Galaxy Nexus] lordofcamster:
Someone?

:)
[Samsung Galaxy Nexus] Bl4ck3urn:
No SoD problems with Interactive governor here.
[Samsung Galaxy Nexus] sajty:
So your are lucky :). I saw some reports on Rootz about interactive. But as I said, no problems with SoD for me now, I am happy user of Zen.
[Samsung Galaxy Nexus] JediDru:
Loving the kernel guys. I just had it set to Zen and adaptivex. Better battery stats is only reporting using the 384 and 576 clock states. This was over 8 hours. Now using fifo instead and appears to scaling all CPU states. Just reporting. Thanks again.
[Samsung Galaxy Nexus] albsat:
No problem here. Did you use another kernel before?

---------- Post added at 01:37 PM ---------- Previous post was at 01:34 PM ----------

This kernel has been sod free for me, using RasJB rom.

Using zen/ondemandX 386/1036 Mhz default settings.
[Samsung Galaxy Nexus] jjhiza:
I'm personally on Rasbean as well, and I've had zero issues. At the moment, I'm on the exact same kernel as you guys are... I'm not having any SoD problems or any other problems for that matter. My setup:

Rasbean (Toro)

Zen v11

Intellidemandx/bfq

1305-384 w/ max screen off @729

No pgm
[Samsung Galaxy Nexus] billouetaudrey:
since yesterday on intellidemandx ( 384 min 1230 max, 729 max screen off ) scheduler zen, pgm on , no sod ;) ( v11)

Envoyé depuis mon Transformer avec Tapatalk
[Samsung Galaxy Nexus] Lancez:
Dose zen kernel support latest AOKP?
[Samsung Galaxy Nexus] bioturbo:
Best kernel so far for pa2.99. On my nexus. No any issue with 230-1230' ondemandX. Super smooth great battery! Awesome!
[Samsung Galaxy Nexus] albsat:
I can say that the this kernel is stable and OK for me. Nothing exceptional but having a reliable kernel and about 3 hours of screen time it is very good on my account. Thanks for your work guys.
[Samsung Galaxy Nexus] Savant:
Does anyone know why the sods randomly occur because 4.2.1 has more problems then 2.3.
[Samsung Galaxy Nexus] Jose Viegas:
Great job guys!
[Samsung Galaxy Nexus] sajty:
Why should not? :)
[Samsung Galaxy Nexus] purian23:
Some of you that are experiencing SOD's, are you using WiFi with it occurs? I know most of the time when folks are at home they are on wifi and charge overnight that way.
[Samsung Galaxy Nexus] menhaha:
I experienced it both on 3g and wifi.

I get SOD when I have a notification awaiting for me. Donno if that is related, but whenever I had an SOD, the phone had a notification waiting to be checked.

Im on Liquid RC9 4.1.2 and V11 Zen Kernel.

Hope this help you get some kind of idea! :)
[Samsung Galaxy Nexus] adio201:
I was getting sod on every version of the ROM n I'm running jbsourcery for sprint Samsung galaxy nexus with zen kernel and all I did to stop getting sod was change my governor to intellademandx and scheduler bfq with min/384 max/1305 and I have not gotten any sod yet...I have charge my phone over night and had a text msg waiting and was able to unlock my phone with out any problem before it would frezz upon unlocking or sod
[Samsung Galaxy Nexus] differentstyles:
I'm using Xeylon 010 and Zen 11. Some minutes ago I've reached the 4h screen time for first time ever. I've never reached this with trinity and Franco. Thanks so much for this Kernel. I'm running 384-1036 with ondemandx. Now the battery is empty :)
[Samsung Galaxy Nexus] orihuri:
Im using xylon 010 and j have the sod problem as well.. Both on 3g and wifi.. I really love this kernel so ill stay with it sod or not. Hope the next version will fix it.
[Samsung Galaxy Nexus] sajty:
Guys,try to post as much informations about SoD as you can.Only this can helps devs to fix this annoying problem.

1) governor

2) scheduler

3) min/max/screen off max frequency

4) undervolted yes/no

5) was SoD during charging yes/no

6) Android version of your ROM

This should help more than "i had SoD today..." :)
[Samsung Galaxy Nexus] orihuri:
Sod

1-gov ondemand

2-scheduler zen

3-min/max 384-1230

4-Sod on wifi while charging, sod on 3g not charging

Rom xylon 010 android version 4.2.1
[Samsung Galaxy Nexus] ak:
Have you try to delete all scripts into init.d folder? :eek:

And clear and reboot
[Samsung Galaxy Nexus] bbedward:
1-request only.

PM me if you'd like to test a build for SoD issues. Preferably if you get them frequently. Also, this is the only time i'm ever going to ask because I don't want to get hounded with PMs :)

But in this case, it's ok. So shoot me a PM.

I have some other goodies I'm still working on as well. I added some parameters to interactiveX (unplug_load and hotplug_delay). Along with logic to hot plug CPUs based on the current cpu_load versus the current unplug_load. Hotplug_delay works similar to how min_sample_time works, where it won't check the hotplug load until after X times (if cpu_load hits > unplug_load and cpu #1 is off, it wont enable cpu #1 until after hotplug_delay).

eventually when we get to quad core devices I will add more unplug_load settings (UNPLUG_LOAD_CORE1/2/3) for quad-core devices where we probably want to plug in all of the cores separately.

Just wanted to share what i'm still working on :)

Oh, and the "active hotplugging" can be disabled by setting unplug_load = 0 either manually or via app, if they make it available.

*edit*

Didn't mean to quote you anarkia :P
[Samsung Galaxy Nexus] jurica_m:
After flashing this kernel, the colors are a bit darker.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kyokeun1234:
That is because they set the contrast to -24 where the stock kernel has contrast of 0. You can always change that back using apps like Trickster MOD
[Samsung Galaxy Nexus] nikulogical:
I'm getting considerably low benchmark scores compared to Franco. Any idea why?

..and I know benchmarks don't really matter blah blah blah
[Samsung Galaxy Nexus] kyokeun1234:
Did you set the kernel to 512 GPU? I think Zen kernel sets GPU to 384 default (Correct me if I'm wrong) while Franco sets his to 512. Good thing you can control GPU speed on Zen kernel ;) so for people who don't care can enjoy lower clock speed where heavy gamer can enjoy the over clocked goodness :)

PS. GPU and CPU speed can dramatically change the benchmark scores IMO. So if you're into those kind of stuff, overclock it a bit to get a higher benchmark
[Samsung Galaxy Nexus] nikulogical:
Yeah. The reason I'm trying this kernel out is because Franco doesn't offer 384 builds anymore. But yes i compared benchmarks with this kernels GPU running at 512.

I like running benchmarks at default settings for different kernels just to see performance differences. I don't care for ocing CPU to 1.8 to get a high benchmark score... Well not anymore at least.

Sent from my Paranoid Francoid
[Samsung Galaxy Nexus] kyokeun1234:
Haha OK
[Samsung Galaxy Nexus] GCbard:
This is the highest score I got with this kernel.

Antutu=9455

Quadrant=4059
[Samsung Galaxy Nexus] GCbard:
sorry. wrong forum. This was on ak kernel.
[Samsung Galaxy Nexus] bbedward:
By how much?

Disabling fsync is good for some marks too.
[Samsung Galaxy Nexus] nikulogical:
I did tests when fsync enabled on both.

By a good 300-400 points on antutu

Sent from my Paranoid Francoid
[Samsung Galaxy Nexus] bbedward:
Maybe due to the fact of a more aggressive ondemand based governor over interactive, or a higher thorough put disk scheduler, can't say for certain but 3-400 points is trivial ;)
[Samsung Galaxy Nexus] kinfolk248:
once and for all....will overclocking the gpu burn out the phone faster? i know OC'ing the cpu will...but what if i OC the gpu and overclock the cpu, hmmmmm......i wonder..???
[Samsung Galaxy Nexus] TheMorpheus:
It seems working good on CM10.1...Keep testing.

Thanks!!
[Samsung Galaxy Nexus] bbedward:
Yea, higher voltage means more heat :)

But by faster I can't tell you how much, probably a negligible-minimal reduction in life expectancy.

*edit*

I think I'm going to post a public test build later in the day to attempt SoD fixes, so stay tuned :)
[Samsung Galaxy Nexus] IT_Blackbelt:
Any plans on adding the lulzactive v2 governor?
[Samsung Galaxy Nexus] bbedward:
I have something a little more interesting.
[Samsung Galaxy Nexus] IT_Blackbelt:
Oh really, cant wait!
[Samsung Galaxy Nexus] bbedward:
https://github.com/AndroidDeveloper...mmit/3b334dc0ac9c69afef24358b43203b7025e721af

A "Live" hotplugging version of interactive :laugh:

Still testing it out, trying to find the ideal settings for hotplug_delay and unplug_freq_cpu1
[Samsung Galaxy Nexus] IT_Blackbelt:
NICE!!! cant not wait to give that a run! :D

Another question, is the Zen scheduler based off another scheduler or was it coded from scratch?
[Samsung Galaxy Nexus] bbedward:
The zen I/O scheduler is basically based off of no-op with some exceptions. It uses deadlines, prioritizes synchronous requests over asynchronous requests, and does no sorting or merging.

It's similar to SIO, but closer to no-op, whereas SIO is closer to deadline without sorting or merging (on SIO, writes can starve read requests/writes are prioritized over writes, it uses its own former/latter_request functions where zen just uses the elevator ones). I think dispatching is also slightly different on SIO, everything on zen is just back-inserted closer to FCFS (but still not pure FCFS like FIFO).

This new "zeneractive" governor is based on interactive. It handles frequency scaling the exact same as interactive and has the same tunables as interactive for frequency scaling.

However, on zeneractive all of the new hotplugging code thats in there is "from scratch." I wrote/came up with all of the logic for it, it probably works quite different from other governors that do "dynamic" cpu hotplugging (pegasusq, some variations of intellidemand and ondemand) simply because those are all ondemand-based governors, interactive is not an ondemand-based governor and handles scaling a bit differently, although still scales based on load.

There are new tunables here though, unplug_load_cpu1/2/3 (frequency we should plug in cores 2-4) and hotplug_delay (how long we should wait in between attempts to see if we should plug in cores 2-4).

Here's a snippet of the cpu-freq doc for more information: http://pastebin.com/hTeWvCpX

The zeneractive bits for hot plugging are quite simple IMO, so far they seem to work good but I'm sure there's room for improvement or more tunables that can be added to make the algorithm more precise.

---------- Post added at 07:14 PM ---------- Previous post was at 07:08 PM ----------

As promised, here's a v12 public test build.

This is to test the following:

- Sleep of death (have a few testers, one that experienced SoD said none overnight like usual, I set my max to 230 min to 192 overnight and didn't get it, but would like to get a more widespread confirmation)

- Zeneractive governor (it is set by default). It seems to work very well, the default hotplug_delay is 80000 uS, the default unplug_load_cpu1 is 15 (unplug_load2/3 don't matter of course). You can use an app such as trickster to verify that CPU 1 goes off/online while the phone is awake.

- Anything else, those are just the key ones

http://goo.im/devs/bbedward/v3.0.54-ZenSERIES_v12_RC1.zip

Thanks! Remember test builds are experimental.
[Samsung Galaxy Nexus] BriVG:
For 4.1 or 4.2?
[Samsung Galaxy Nexus] bbedward:
For 4.2, sorry forgot to specify.

It should work on 4.1 except for bluetooth.
[Samsung Galaxy Nexus] albsat:
Nice. What is the expected battery life? I am trying right now.
[Samsung Galaxy Nexus] bbedward:
Well, still testing, you'll have to tell me. The default unplug_load_cpu1 is very conservative (15% so it'll only remove the second core if cpu_load as calculated is < 15%)

The cores still shut down on suspend like before as well.
[Samsung Galaxy Nexus] sajty:
Please,tell me,that you will release v12 for 4.1.2 too:fingers-crossed:
[Samsung Galaxy Nexus] albsat:
Just curious. In which rom do you try your testing :)?
[Samsung Galaxy Nexus] bbedward:
Yes probably, not the test build though.

I'm rebasing again on the jb-mr1 tree, hoping it resolves some of the issues. (The current base is a hybrid of linux-stable-3.0.y branch of linux-stable, android-omap-3.0, and android-omap-tuna-3.0-jb-mr1).

So a V12 release will likely be after that :)

And I'm currently testing in a raspbean port for toroplus (I have a toroplus :P)
[Samsung Galaxy Nexus] 47th_Ronin:
Thanks for the info on your new governor.

I have a question;

Is zeneractive similar to sakuractive? I've had excellent experience with that one but it's not to popular it seems. Anyway, i was hoping you would add it eventually but if zeneractive is as good as sakura, I'll take it!

Thanks guys!
[Samsung Galaxy Nexus] TheMorpheus:
So far so good! Keep testing
[Samsung Galaxy Nexus] gianton:
Great work, excellent battery life on AOKP Dec 4th Roman build. Running rock stable and very smooth so far on stock settings. :good:
[Samsung Galaxy Nexus] sajty:
:( i want to test it too :banghead: . I must be strong and wait for release...
[Samsung Galaxy Nexus] bbedward:
Nope :) sakuractive hot plugs too though, think its based on hot plug/ondemand but I never really checked it out.
[Samsung Galaxy Nexus] albsat:
How about zenondemand?

Could such a governor Vince come soon or it doesn't make sense?
[Samsung Galaxy Nexus] sajty:
Modified interactive will be good enough i guess.Cannot wait to see.
[Samsung Galaxy Nexus] lippol94:
I have a report to do.

I've been testing your kernel for a few hours really deeply and in different situations.

As Interactive already is, zeninteractive is really smooth doing one thing at time, but it kinda stucks on multitasking operations. Let me explain.

It happened many times that switching between open apps, or pressing home button and then opening another app, my phone suffered from a huge delay that made my phone unusable for a few seconds.

Another thing I've seen is that the phone takes a while to wake up and work smoothly. I don't know if it's because of that hotplug, suspend or whatelse. Maybe you should tweak it in order to make scaling a little more aggressive.

I don't know pretty much anything of this stuff, but these are my little observations.

Thanks! :)
[Samsung Galaxy Nexus] bbedward:
Interactive may actually already scale more intensely than ondemand. In my experience, on wake up the interactives tend to ramp up to max frequency already (by design). I could certainly modify the wake code to use a higher frequency when the governor wakes up. Right now it wakes up at 729.6MHz or the next highest frequency if that one is unavailable. (It seems to wake up fast for me though ;))

Perhaps the jitter in the UI is due to the lower default min_sample_time (how long it spends at a frequency before reducing to a lower frequency). The interactive default is 80000 uS, the default I set on interactive+zeneractive is 30000 uS (more of a battery saving deal, to help it scale down faster).

The other thing is on wakeup it increases the frequency to the suspend frequency (729MHz+) before it wakes up the other cores. Perhaps if it does it the other way around it may make things a bit smoother for you.

I think the UI is quite fast and it scales quite well :), but I can certainly seek some improvements before the next release.

I may modify ondemandx to perform the "live hotplugging" similar to zeneractive - but that may be for a different day (we'll see). For now though, there are tons of ondemand-based governors out there (pegasusq, adaptive, intellidemand, sakuractive, hotplug, lazy, wheatley, etc.) that I'm not sure what else I can do to make a variant of ondemand :P. (Pegasusq, hotplug, sakuractive, and a variant of intellidemand perform hotplugging as well). But I will look into a "live hotpplugging" ondemandX that uses the same parameters as zeneractive (unplug_load_cpuX, hotplug_delay), if there's enough request for it or if I have the spare time :laugh:

*edit*

Not too fond of how aggressive zeneractive is removing the CPU. I'm removing the hotplug_delay tunable and replacing it in favor of a new unplug_delay.

unplug_delay is how long we have to be BELOW the unplug_freq[cpu] before we can remove the core. (e.g. if unplug_freq_cpu1 is equal to 15, CPU 1 has to be below 15% CPU usage for unplug_delay uSec before we remove it.)
[Samsung Galaxy Nexus] gianton:
Haven't noticed a lag with default settings and loosing 0,5% per hour in standby!
[Samsung Galaxy Nexus] lippol94:
If you can say that you're loosing 0,5% per hour in standby it means you're not using your phone. I tried to stress mine as much as I could to provide a valuable feedback :)
[Samsung Galaxy Nexus] gianton:
I stressed it alright since it's released and haven't noticed any lag with default settings. I just mentioned the battery drain in idle, usually I get 1% per hour.
[Samsung Galaxy Nexus] killersloth:
I got a sod on v11 and like someone else mentioned, I had a pending notification while charging overnight. ROM I used also has charging light. Sadly I wasn't able to pull any log, the girlfriend needed to get to work and I need my music when I drive :(

Has never happened before under the same exact circumstances. Guessing it's a ROM issue in my case.

Sent from my Galaxy Nexus using Bacon
[Samsung Galaxy Nexus] gm007:
Try v12
[Samsung Galaxy Nexus] Craxx:
V12 is really smooth and looks promising for battery life :)

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] TheMorpheus:
Not bad battery life ... It did it better yesterday with V11 but every day is different from another!!
[Samsung Galaxy Nexus] Craxx:
Great with flashing xylon11 and zen12 between;)

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] bbedward:
I'm doing a lot more work on v12, mostly the governor fixing some stuff up yet and re working some of the hot plug logic.
[Samsung Galaxy Nexus] TheMorpheus:
Eager to try it out!!
[Samsung Galaxy Nexus] kinfolk248:
anyone else have media eating up a lot of battery with v11 4.1.2???

someone told me it was caused by 'nomedia' file....is there no permanent fix?
[Samsung Galaxy Nexus] IT_Blackbelt:
The public test has been running great for me, cant wait to run the final product!
[Samsung Galaxy Nexus] kinfolk248:
this kernel is developing too fast, slow it down guys...
[Samsung Galaxy Nexus] albsat:
Please don't give unsupported advices. :)
[Samsung Galaxy Nexus] differentstyles:
I'm on xeylon beta 11. Since Wednesday the 12 rc1 kernel is working absolutely flawless. No sod's or whatever. I'm using the default settings but max 1036. Sorry forgot to make a screenshot. My screen on time with extended battery was ca.3.15 yesterday which is amazing for me. Trinity was my absolute number 1 kernel and i still love the colour but since I'm using the Zen kernel my screen time raised.
[Samsung Galaxy Nexus] sajty:
Another SoD.

- OndemandX/noop

- 384 min, 1036 max, 729 max screen off

- Android 4.1.2

- was not during charging
[Samsung Galaxy Nexus] parkson:
Try using a different scheduler. Noop crashes for me on xylon 10 and pa 2.99.7 both Toro

*edit* I'm referring to v12 beta
[Samsung Galaxy Nexus] sajty:
I hope,that v12 with fix will be soon...

---------- Post added at 01:07 PM ---------- Previous post was at 12:15 PM ----------

And SoD again (adaptiveX,sio).I have to change kernel :(.
[Samsung Galaxy Nexus] Rimher:
I had half-SoD: when receiving a call the phone would not light up. When the phone was finally dropped on the other hand everything returned to work correctly
[Samsung Galaxy Nexus] yosula:
my antutu test with v12 and xylon v11 beta 3
[Samsung Galaxy Nexus] kinfolk248:
damn dude, its sarcasm, take a joke...
[Samsung Galaxy Nexus] differentstyles:
Damn the 12 rc1 was working really good. Now within one hour 2x sod. The only thing I remember that before every sod a Gmail notification came in. Before it was working. After the notification there was the sod. Strange that it happened twice. For now I'll switch back to 11.
[Samsung Galaxy Nexus] Craxx:
Today with 12 i get my first sod ever on xylon 11b2.... But keep up the good work ;)

Battery Life is awesome :)

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] bbedward:
v12 final has some sizable improvements in store ;), on a rebased tree as well
[Samsung Galaxy Nexus] Craxx:
Ohhhh nice could you give me a link :D

I want to flash xylon b3 and want not to flash a old 12 kernel ;)

.... just a nice try...

... And what's your best saving battery settings in trickster?

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] bbedward:
v12 is not available yet ;) stay tuned as it should be very soon.

Some more zeneractive info, its ready for release and has been thoroughly improved since v12 RC1, with revamped hotplugging logic.

Tunables over interactive:

- unplug_load_cpu1/2/3 (we only care about unplug_load_cpu1 on the GNex)

- insert_delay (default: 30 milliseconds)

- unplug_delay (default: 5 seconds)

- suspend_frequency (default: 729.6MHz) - our frequency target when suspending. (wake frequency target is always hispeed_freq)

So the frequency scaling is exactly the same as interactive.

The hotplugging algo works like this:

work done on a realtime thread.

for any/every CPU, lets say CPU #1

- We compare CPU load to unplug_load_cpu1

- If CPU load is <= unplug_load_cpu1, we increment how long its been since the last time CPU load was <= unplug_load_cpu1, and we completely forget about the last time the CPU load was > unplug_load (reset that timer)

- If CPU load is > unplug_load_cpu1, we increment how long its been since the last time CPU load was > unplug_load_cpu1, and we completely forget about the last time the CPU load was <= unplug_load (reset the timer)

- When CPU load has been <= unplug_load_cpu1 for unplug_delay (5s by default), we will remove CPU 1 (if it is online)

- When CPU load has been > unplug_load_cpu1 for insert_delay (30ms by default), we will add CPU 1 (if it is offline)

- All auxillary CPUs are removed on suspend, and the hotplug thread does not perform any logic

- On wake, all CPUs are inserted and we attempt to ramp up every CPU to the hispeed_frequency.
[Samsung Galaxy Nexus] viscocesco:
Is it ready???

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] ak:
Please dont ask for eta ! :D
[Samsung Galaxy Nexus] vincentistan:
hey arnarkia do you also develop this kernel? i thought you do ak kernel
[Samsung Galaxy Nexus] Craxx:
Today 2. Sod... i need the new kernel ;)

Nvm take your time... :D

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] ak:
Hey simpaty fly down .... :eek: