yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] purian23:
Kernel Update!!!

Introducing along with AffinitySERIES ROM

On our Site, XDA & Rootz Forums

v3.0.51-ZenSERIES v4 Kernel

*Breaking Ground*

Fast, Smooth, Responsive & Battery Friendly

Unified Kernel for Toro/Toroplus/Maguro

3.0.51 is the latest Upstream Google Source

Built from 4.7.2 GCC Customized Zen ToolChain

[B]ZenSERIES_v4[/B]
- Breaking Ground *Serious Kernel Power*
- Built with a more vanilla crosstool-built gcc 4.7.2 instead of Linaro*
- Should solve affected Chrome users & any remaining boot issues*
- Fixed 384MHz Maximum GPU Frequency
- Updated to v3.0.51
- Adjusted CFLAGS
- Raised default vfs_cache_pressure from 20->30
- Re-added some incidentally removed PM updates
- Lowered fifo_batch to 1 on deadline/SIO/zen/V(R) as it may be most desirable for flash memory
- Set cpu transition latency back to 30ms
- Slightly increased voltages for 1.4-1.7~GHz frequencies
- Proprotional rate reduction for TCP
- Westwood as default TCP congestion scheduler
- Thalamus' updated target residencies
- Zen I/O scheduler is now default
- A couple cleanups to Zen I/O
- Adjusted default lowmemorykiller minfree, for min ~80Mb.
- 2048/3072/6144/15360/17920/20480

Here are your ZenSERIES Download Link:

ZenSERIES v4 Kernel

Main Support Thread

See OP for further information!

Thank you

Android Developer Alliance​
[Samsung Galaxy Nexus] purian23:
Kernel Update!!!

Introducing along with AffinitySERIES ROM

On our Site, XDA & Rootz Forums

v3.0.51-ZenSERIES v5 Kernel

*Breaking Ground*

Fast, Smooth, Responsive & Battery Friendly

Unified Kernel for Toro/Toroplus/Maguro

3.0.51 is the latest Upstream Google Source

Built from 4.7.2 GCC Customized Zen ToolChain

[B]ZenSERIES_v5[/B]
- Rebased Entire Kernel - Cleaned up all code in source
- More sysctl tweaks, min_free_kbytes is now at ~4Mb by default
- Added OndemandX Governor
- Added ZRAM Support
- Fixed OC issues for some users by enabling trim quirks
- Updated lowmemorykiller to latest from ~3.6
- Updated OPP driver to latest from ~3.6
- Adjusted intellidemand default settings to match our ondemand ones
- Some omap DSS fixes
- Reduced android logger ram usage (dorimanx)
- More accurate nohz load accounting (dorimanx)
- More tweaks by default
- Dirty_expired_centisecs -> 200, vm_dirty_background_ratio - >
- 60, sched_nr_latency -> 10, sched_min_granularity ->
- .4msec, sched_latency -> 3ms

Here are your ZenSERIES Download Link:

ZenSERIES v5 Kernel

Main Support Thread

See OP for further information!

Thank you

Android Developer Alliance​
[Samsung Galaxy Nexus] trini.s2k:
Good for you Jjhiza always thought you should be on a team congrats
[Samsung Galaxy Nexus] ArnieG:
Running fine with alien droid v1. Fast, smooth and good battery.
[Samsung Galaxy Nexus] trini.s2k:
one problem with kernel if you leave it to charge over night you wake up to a dead phone if I charge it an watch it till it full and unplug it its fine.
[Samsung Galaxy Nexus] ocman40:
+1
[Samsung Galaxy Nexus] fcisco13:
No dead phone here, alarm went of fine.

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] thenewguy821:
+1 My phone charged full, and rested on charger all night.
[Samsung Galaxy Nexus] trini.s2k:
Not sure dudes I try on sorcery clean install and now atom clean install the phone just dies and its on the charger and i dint install any apps clean just sitting there
[Samsung Galaxy Nexus] fcisco13:
Kernel that comes with rom? UV/OC?

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] trini.s2k:
This kernel on those ROMs not oc or uc just installed and left alone
[Samsung Galaxy Nexus] fcisco13:
You can try a different kernel, that might help. Zen is working very good here, faux is also a great kernel.

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] trini.s2k:
that sucks i like this kernel , popcorn kernel was stock on atom rom and was making the service hang wen it left wifi i would be in limbo it sucks, any one got a rom suggestion to rock with this kernel?
[Samsung Galaxy Nexus] purian23:
I have Zero problems on ZenSERIES with wifi. All the testings we've done we never incurred wifi issues. I'm not sure if something is trying to override on you, but rest assured v6 is coming and proving to be the best created yet from our team!
[Samsung Galaxy Nexus] fcisco13:
Did you say v6??? Me wants!!

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] trini.s2k:
your kernel is fine , only problem is when i leave it over night on the charger something happens and it kills the phone , i like your kernel when using daily what rom you using purian
[Samsung Galaxy Nexus] thenewguy821:
I'm running BAMF Paradigm, with v5 of this kernel, and am very impressed. Very snappy and great battery. No issues with leaving the phone plugged in overnight.
[Samsung Galaxy Nexus] purian23:
It's coming and going to be a game changer :)

I am using our teams rom, the ZenSERIES Kernel is the second part in our product lines, our Rom AffinitySERIES can be found here ;0)

Thank you sir, no issues here either, thanks for posting!
[Samsung Galaxy Nexus] purian23:
Kernel Update!!!

Introducing along with AffinitySERIES ROM

On our Site, XDA & Rootz Forums

v3.0.51-ZenSERIES v7 Kernel

*Ghost Protocol*

Fast, Smooth, Responsive & Battery Friendly

Unified Kernel for Toro/Toroplus/Maguro

One Build Compatible for 4.0/4.1/4.2 ROMS

3.0.51 is the latest Upstream Google Source

Built from 4.7.2 GCC Customized Zen ToolChain

[B]ZenSERIES_v7[/B]
- Now should be Compatible with 4.0/4.1/4.2 ROMS
- Merged in latest 4.2 Source tuna+omap updates
- Revert to using stock ramdisk for capability
- Pegasusq tweaks, some suggestions from EniGmA1987
- Set CPU_DOWN_FREQ to cpu frequency policy minimum on pegausq
- Set sysctl values via script, overrides anything set by ROMS Ramdisk initially
- To remove, rm /system/bin/set_zen_sysctl and /system/etc/init.d/99ZenKernel
- Deep Sleeping was more ROM Related vs Kernel - v7 has worked on our end
- Fixed Zram & CPU Sticking

[B]ZenSERIES_v6[/B]
- Added a New Custom Ramdisk Rewritten with Zen settings
- Ramdisk originally pulled and modified from leanKernel
- Sysctl settings won't be overridden by rom's default ramdisk now
- This should fix any lag/idle slowdowns that were minutely present
- Modified CPU scheduler settings
- Modified sysctl settings for the "Zen-Tune" branch settings
- Now matches what is set by the ramdisk just for easier reference
- More upstream lowmemorykiller updates
- Updated Interactive & InteractiveX using latest upstream from android common
- Added Brand New 4.2 Ramdisk by Google's Kernel Source *Testing Phase*

ZenSERIES v7 Kernel

Main Support Thread

See OP for further information!

Thank you

Android Developer Alliance​
[Samsung Galaxy Nexus] jayochs:
what clock widget is that? lol it's awesome
[Samsung Galaxy Nexus] purian23:
One More Clock Widget on the PlayStore :)
[Samsung Galaxy Nexus] jayochs:
looks differently themed than omc hmm.. cool!

---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------

how's you get that custom weather icon? and change the font size? all in omc? I never saw such customization options.
[Samsung Galaxy Nexus] iifuzz:
I just got a sleep of death on 4.2
[Samsung Galaxy Nexus] dcowboys2184:
That's what I was afraid of getting..
[Samsung Galaxy Nexus] Droid316:
No deep sleep on 4.2 mmuzzy clean wipe and all.
[Samsung Galaxy Nexus] purian23:
Thank you for reporting guys, we are getting a ton of mixed results. One thing to help minimize is clean flash everything, the transitions from 4.1 - 4.2 ROMS should always be clean flashed. Some kernels are using custom ramdisks overwriting some of the setting on the kernel end,. the ROM devs are hard working for good GPS and sleep issues on that end. Lots of thing in play at the moment. In the end what i'm saying, one person on the exact rom and kernel is reporting zero issues, sleeping well, while another on the same setup is not deep sleeping. Some of it has to be user definined, some rom/kernel defined. We are working on making sure it's not on our end and thank you all for reporting, using and supporting ZenSERIES.
[Samsung Galaxy Nexus] Android.Ninja:
Conclusive Independent Testing:

FYI on test results: Conclusive 12 hr test

ROM for testing: Jakeday Jelly Belly 10

Method: Clean install.

Devices Tested: Quantity 3 Galaxy Nexus.

GSM / CDMA: CDMA testing.

MD5's Verified: Yes on Kernels & ROM

Timed Test: 12 hr per 3 individual devices

Battery Percentage: @ Test Start 100%

Battery Used: 2 Factory & 1 Seidio 3800

Test #1

Zen Kernels

No deep sleep initiated in 12 hr period. GPS lock problematic. ROM very responsive when being utilized. Kernel well developed. Stepping excellent. Battery optimization better than estimated. Highly recommended kernel.

Test #2

Tiny Kernel

Deep sleep initiated in 12 hr period. GPS lock not problematic. ROM very responsive when being utilized. Kernel well developed. Stepping excellent. Battery optimization better than estimated. Highly recommended kernel.

Test #3

Stock Kernel

Deep sleep initiated in 12 hr period. GPS lock not problematic. ROM mildly responsive when being utilized. Kernel well developed. Stepping average. Battery optimization OK as estimated. Recommended kernel for stock purposes.

Test #4

Trinity Alpha 4

No deep sleep initiated in 12 hr period. GPS lock problematic. ROM very responsive when being utilized. Kernel well developed. Stepping excellent.

SOD on 2 events. Remove and replace battery to reinitialize required.

Battery optimization better than estimated. Highly recommended kernel.

----------------------------------------

Conclusive Recommendation:

Zen Kernel Best optimized performance.

Conclusive Suggestions:

1. Research & Resolve GPS lock issue.

2. Research & Resolve Deep Sleep issue.

All test were performed on 100% returned to stock devices / rooted / custom rom.

Hope this helps! ;)

Android.Ninja

If I've been a help to you, hit the Thanks button!

Edited to update names of each ROM utilized in testing.
[Samsung Galaxy Nexus] purian23:
Excellent testing sir! Thank you very much. We are certainly looking into every part of it!
[Samsung Galaxy Nexus] purian23:
Kernel Update!!!

Introducing along with AffinitySERIES ROM

On our Site, XDA & Rootz Forums

v3.0.52-ZenSERIES v8 Kernel

*The Wakening*

Fast, Smooth, Responsive & Battery Friendly

Unified Kernel for Toro/Toroplus/Maguro

Two Versions:

ZenSERIES_v8 4.2 Ongoing Support

ZenSERIES_v8 4.0/4.1 Final Version

3.0.52 is the latest Upstream Google Source

Built from 4.7.2 GCC Customized Zen ToolChain

[B]ZenSERIES_v8[/B]
- Two Versions
- Final ZenSERIES 4.1 build
- Ongoing support for ZenSERIES 4.2
- Updated Base to 3.0.52 Latest Upstream Google Source
- Fixed deep sleep on 4.2 ROMS
- More core build optimizations
- Updates from the android-3.0 tree
- More conservative default cache_pressure

ZenSERIES v8 4.2 Kernel

ZenSERIES v8 4.0/41 Final Kernel

Main Support Thread

Enjoy!

See OP for further information!

Thank you

Android Developer Alliance​
[Samsung Galaxy Nexus] LexusBrian400:
I keep getting a dead page via mobile. Tried 3 different browsers.
[Samsung Galaxy Nexus] purian23:
I am not sure, just tried the same link and working just fine :(

Try this directly again http://xdaforums.com/showthread.php?t=1958143
[Samsung Galaxy Nexus] taz1458:
Brand new to the nexus fold, will this kernel work with the latest aliendroid?
[Samsung Galaxy Nexus] fcisco13:
Download the correct one for your rom, check to see if your rom is 4.1 or 4.2

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] allan1313:
Is anyone else having problems getting oc to stick with system tuner??
[Samsung Galaxy Nexus] 47th_Ronin:
Uhh hell yeah!

I'll take one
[Samsung Galaxy Nexus] purian23:
Kernel Update!!!

Introducing along with AffinitySERIES ROM

On our Site, XDA & Rootz Forums

v3.0.53-ZenSERIES v9 Kernel

*Wide Awake*

Fast, Smooth, Responsive & Battery Friendly

Unified Kernel for Toro/Toroplus/Maguro

Two Versions:

ZenSERIES_v8 4.2 Ongoing Support

ZenSERIES_v8 4.0/4.1 Final Version

3.0.53 is the latest Upstream Google Source

Built from 4.7.2 GCC Customized Zen ToolChain

[B]ZenSERIES_v9[/B]
- Updated to v3.0.53 Latest Upstream Google Source
- Added in some additional omap-specific fixes
- Pulled in the core block layer from axboe/linux-block.git up to 3.3. Includes the following:
- http://git.kernel.org/?p=linux/kernel/git/axboe/linux-block.git;a=shortlog;h=refs/heads/for-3.1/core
- http://git.kernel.org/?p=linux/kernel/git/axboe/linux-block.git;a=shortlog;h=refs/heads/for-3.1/drivers
- http://git.kernel.org/?p=linux/kernel/git/axboe/linux-block.git;a=shortlog;h=refs/heads/for-3.2/core
- http://git.kernel.org/?p=linux/kernel/git/axboe/linux-block.git;a=shortlog;h=refs/heads/for-3.3/core
- Updated BFQ to for-3.3 version to reflect it
- SOD issues should now be fixed
- Added FIOPS v2 I/O scheduler
- Added logic to cpufreq_set_policy so it only sets policies with a valid min/max frequency*
- Vs any min/max frequency within the range*
- Adjusted Ondemand/OndemandX/Intellidemand/Pegasusq settings
- Updated wifi drivers to 3.4 ones
- Enabled frontswap and cleancache
- Added script to apply some fstab tweaks to current roms ramdisk (mount with noatime+disable barriers)
- Applied zRam updates
- Added ZRAM_FOR_ANDROID (Optimizes zram for android, adds bits to zram+lowmemorykiller)

ZenSERIES v9 4.2 Kernel

ZenSERIES v8 4.0/41 Final Kernel

Main Support Thread

Enjoy!

See OP for further information!

Thank you

Android Developer Alliance​

Thank you

Android Developer Alliance[/CENTER][/SIZE][/FONT]
[Samsung Galaxy Nexus] rlivin:
Had to go back to v8. Wireless tethering not working with v9 for me.

Ahh i see v10 that fixes that problem.
[Samsung Galaxy Nexus] jjhiza:
Check the Rootz thread... v10 is out with fixes for tethering. :)
[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

ZenSERIES Kernel v11 4.0/4.1

Main Support Thread

Enjoy!

See OP for further information!

Thank you

Android Developer Alliance​
[Samsung Galaxy Nexus] PatimusXPrime:
Okay I have to ask, what is the benefits of the Adaptive/X governor over default Interactive? Does it hotplug? Could we get an explanation? Thanks :)
[Samsung Galaxy Nexus] 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] thenewguy821:
Good description. For general use (occasional light games, music, text, web, etc.) Would you recommend adaptivex or intellidemandx? Looking for good battery, as well as smoothness.
[Samsung Galaxy Nexus] PatimusXPrime:
Thank you guys, I've been at this for a while but never knew that the "x" govs have hotplugging. I haven't used anything but interactive on my gnexus, used a lot of different ones on my Dinc2 but it only has 1 cpu core so :P

And for the last question, i'm just going to play around with a few. I need to do some serious cleaning on my phone but i'll report back with some results. Good luck and thanks again my dudes
[Samsung Galaxy Nexus] PatimusXPrime:
I've read a lot of guides for setting up PegasusQ for the GS3, I've applied those settings on the gnex and its snappy but I feel like I'm not getting such great battery life now. Has anybody tweaked pegasusq for the gnex?

The guides I've seen are for the Siyah kernel and it doesn't use a fee of the parameters that our device does use. I feel like if this is set up properly it could be a really nasty governor!

I'm on the Zen kernel running rasbean 4.2.1 12/29 build.

Let's try and figure this out together so we can hopefully enhance all of our experiences!

Here is the post that I used: http://xdaforums.com/show...03&postcount=3

Yeah with his recommended settings, it hot plugs nicely but I'm getting some bad battery drain when the screen is on, when I had the default Pegasusq settings it wasn't reap snappy but the battery didn't drain much.

Good luck everyone lol I'll be here

MY settings are:

sampling rate = 40000

up threshold = 75

sampling down factor = 2

ignore nice load = 0

io is busy = 1

down differential =8

freq step = 30

cpu up rate = 10

cpu down rate = 20

cpu up freq = 576000

cpu down freq = 384000

up nr cpus = 1

max cpu lock = 0

min cpu lock = 0

hotplug lock = 0

dvfs debug = 0

hotplug freq 1.1, 2.1, 3.1 = 576000

hotplug freq 2.0, 3.0, 4.0 = 384000

hotplug rq 1.1, 2.1, 3.1 = 250

hotplug rq 2.0, 3.0, 4.0 = 150

up threshold at min freq = 50

freq for responsiveness = 729000
[Samsung Galaxy Nexus] fordmanck:
I just started running this two days ago with Jellybro CM10.1 and I can't get over the battery life. I'm using the default kernel settings and its unreal the difference between this and any other kernel so far.
[Samsung Galaxy Nexus] PatimusXPrime:
You're using the default settings on pegasusq? I was using that but its sluggish, barely turns on when I hit the power button and everything is so slow lol you're saying you're not getting any of that? Hmm... I may have to fool around with default to see if its one specific setting that's doing that for me.. Thanks
[Samsung Galaxy Nexus] fordmanck:
No. Stock settings for me are intellidemandx. Performance is great as well as battery.

Edit - here are a couple screenshots from today. I never get more then 45 minutes of screen on time. I'm at 40 minutes right now.
[Samsung Galaxy Nexus] PatimusXPrime:
it's not bad at all, the way i have this phone tweaked is superb for battery lol i can get some great screen time.. when i was reading up on the pegasusq gov i had the screen on for like 20 min and only had about 10-15% drain, but it wasnt snappy. that was with default pegasusq settings. i want to try and find the magic numbers to even out that plane a bit. get good battery for screen on + hotplugging + performance. im not expecting perfection but to level that field i think would be GREAT for anyone using this kernel ya know?
[Samsung Galaxy Nexus] fordmanck:
All i can say is this kernel sleeps awesome. My phone has been used today and on WiFi, but I've been on my N7 most of the day. Either way it never lasts this long. Very impressed.

Sent from my Gnex
[Samsung Galaxy Nexus] maniaryan:
noop scheduler freezes for me on zenteractive v12 RC1! zen scheduler works awesome though!
[Samsung Galaxy Nexus] SomeGuyDude:
Got an SOD overnight using the zen I/O and zenteractive combo, 192/103600 min/max. On WiFi. RasBean Jelly.

I'll see if I get any more during the day.
[Samsung Galaxy Nexus] PatimusXPrime:
For me, anything but SIO scheduler causes severe lag and I don't like zeneractive too much, its giving me keyboard lag and app lag...

I may go back to the last version and just keep using interactivex which seemed to work better for me.. I feel like zen scheduler and zeneractive is so much better to use than what I am using but its not working for me! :(

I'm on rasbean by the way
[Samsung Galaxy Nexus] bbedward:
Experimental build :D

Current zeneractive is much adjusted and will not remove a CPU unless CPU load has been below unplug_load for unplug_delay. (defuault will be ~5-7s). Also there is no delay for inserting CPUs in the newest version, only for removing them.

And also, "echo 0 > /sys/devices/system/cpu/cpufreq/zeneractive/unplug_load_cpu1" will disable the "live" hotplugging and give you interactiveX behavior :D
[Samsung Galaxy Nexus] SomeGuyDude:
Aside from my overnight SOD I think v12 is running like a champ so far. Still using 192/103600 with the zenteractive/zen combo. Might not be QUITE as snappy as Intellidemand, but if battery is better that's A-OK.
[Samsung Galaxy Nexus] aperseghin:
hrm i see there is still an SOD issue.. luckily il off tomorrow :) so i dont need the alarm. hopefully that will be better by sunday night :):)
[Samsung Galaxy Nexus] PatimusXPrime:
Good to know! I just did a full wipe and tried JellyBelly and it seems to work a lot better with zeneractive and zen scheduler lol so maybe it was my flash of rasbean?
[Samsung Galaxy Nexus] nitsua98:
Ok, I really need help :( I can't figure this init.d script out!

Right now I have:

#!/system/xbin/busybox sh

echo "10000" > /sys/devices/system/cpu/cpufreq/zeneractive/min_sample_time

echo "729600" > /sys/devices/system/cpu/cpufreq/zeneractive/hispeed_freq

echo "100" > /sys/devices/system/cpu/cpufreq/zeneractive/go_hispeed_load

echo "50000" > /sys/devices/system/cpu/cpufreq/zeneractive/above_hispeed_delay

echo "50000" > /sys/devices/system/cpu/cpufreq/zeneractive/timer_rate

echo "0" > /sys/devices/system/cpu/cpufreq/zeneractive/unplug_delay

echo "100" > /sys/devices/system/cpu/cpufreq/zeneractive/insert_delay

echo "33" > /sys/devices/system/cpu/cpufreq/zeneractive/unplug_load_cpu1

Can anybody help?

Btw this is what comes up when I try to run it in script manager

exec /system/xbin/busybox sh '/etc/init.d/ZenKernel'

busybox sh '/etc/init.d/ZenKernel' <

: not found/ZenKernel: line 2:

/etc/init.d/ZenKernel: line 3: can't create /sys/device: nonexistent directoryneractive/min_sample_time

/etc/init.d/ZenKernel: line 4: can't create /sys/device: nonexistent directoryneractive/hispeed_freq

/etc/init.d/ZenKernel: line 5: can't create /sys/device: nonexistent directoryneractive/go_hispeed_load

/etc/init.d/ZenKernel: line 6: can't create /sys/device: nonexistent directoryneractive/above_hispeed_delay

/etc/init.d/ZenKernel: line 7: can't create /sys/device: nonexistent directoryneractive/timer_rate

/etc/init.d/ZenKernel: line 8: can't create /sys/device: nonexistent directoryneractive/unplug_delay

/etc/init.d/ZenKernel: line 9: can't create /sys/device: nonexistent directoryneractive/insert_delay

Getting "0" code
[Samsung Galaxy Nexus] jdec529:
V12 seems pretty stellar so far. No lag, and battery seems on point. Changed colors and governor to zeneractive. Everything else stock
[Samsung Galaxy Nexus] fordmanck:
I'm not getting a SOD but I'm getting to where my screen won't turn on. Not sure if it's kernel or ROM related. This morning my alarm was working and going off but I couldn't turn the screen on to turn it off. This was of course after using the volume keys 6 times to snooze....
[Samsung Galaxy Nexus] parkson:
That'd be SOD
[Samsung Galaxy Nexus] fordmanck:
Oh. Gracias.

Sent from my Gnex
[Samsung Galaxy Nexus] hotrodwinston:
I thought sod was when nothing at all would happen-

no alarm no ring no power screen will not turn on and have to pull battery to do anything
[Samsung Galaxy Nexus] parkson:
In my experience when SOD occurs, a battery pull is typically required. Because the phone/processes are still running normally, pulling the last_kmesg is useless because the phone never registers as off/rebooted. This is why SOD can be a pesky problem for devs to track down.

Anyone please correct me if this is incorrect as I am no dev.
[Samsung Galaxy Nexus] gchild320:
Getting more SOD's on .55 than I was on .53. Just FYI, wish I could find reasoning behind it.