yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] jay661972:
so far so good running the latest xenon. only issue i have is fc when using the performance settings to oc/uv, same with trinity app. i guess i need to find an app that works with this kernel. suggestion?
[Samsung Galaxy Nexus] Vangelis13:
Trickster Mod works
[Samsung Galaxy Nexus] jjhiza:
TKT setting will stick, despite the FC when backing out of the Tuneables tab. I switched from TKT to Franco's app though, in part because of that FC, and because Francisco has updated the app to include scheduler changes. I'm sure Trickster Mod works as well...I've just never had any luck with it. I was never able to get settings to persist through a reboot, and I don't feel like setting my tweaks up every time I reboot my phone (about once a week). :)
[Samsung Galaxy Nexus] ommadawn-xda:
I can assure you that it worked on my crespo... by the way, an update to PA was just issued (2.51) and I will stick to the default kernel for now
[Samsung Galaxy Nexus] jay661972:
Switch to franco app and all good. Been trinity kernel user for so long, need to change.
[Samsung Galaxy Nexus] purian23:
Thank you and do let us know. I couldn't even get the stock kernel to deep sleep on my end either. That's why it points to something in the 4.2 ROMS we are flashing that is not correct at this time. I'm sure devs will tirelessly get these issues resolved.
[Samsung Galaxy Nexus] Jose Viegas:
The funny thing is that I had DS this morning, after flashing 4.2 for the first time with stock kernel. Then, I started playing with kernels and I never had DS again, even with reinstalled 4.2 stock.
[Samsung Galaxy Nexus] gm007:
That's weird,i am on stock kernel and i have deep sleep.

I did full factory reset after flashing 4.2.
[Samsung Galaxy Nexus] Jose Viegas:
Out of curiosity, do you have that new Daydream feature enabled or disabled?
[Samsung Galaxy Nexus] dyepnoodle:
mine sleeps better when daydream is turned off. i also had an issue with deepsleep on stock kernel. i resolved it by reseting timer, restore timer on cpu spy. did it lot of times before phone went into deepsleep.
[Samsung Galaxy Nexus] purian23:
Very cool, thank you for pointing it out. I do believe it just depends on what ROM the users are on at this time. Hopefully it gets cleaned up on all ends very soon.
[Samsung Galaxy Nexus] gianton:
4.2 kernel sources are out.
[Samsung Galaxy Nexus] jozef710i:
What is the name of clock widget Thank u
[Samsung Galaxy Nexus] gm007:
It's disabled,and everything stock without rooting just to test the battery with everything intact and it seems the battery is doing well
[Samsung Galaxy Nexus] bbedward:
Thanks, looks like theres only some minimal changes versus what I have. Some wifi, bluetooth, and touchscreen related.

Already merged them to my git repository, was sort of hoping we'd get bumped to 3.4 :(

*edit*

Going to go back to using the stock ramdisk (existing ramdisk on whatever rom you use). And using an init script to ensure all the settings get set.

It'll make things easier with all these 4.1/4.2 discrepencies. Also pulled in the latest omap source today to the zen git, so we'll probably have a minor update to v7, but hopefully one that gets us back on track and settles any kernel/rom discrepencies with 4.2 :)

Thanks again for your support guys, everyone has been great on this side of the site.
[Samsung Galaxy Nexus] kara mustafa:
My phone is now 10x faster with this rom but it wont go deep sleep unfortunately
[Samsung Galaxy Nexus] purian23:
At this point for alot of 4.2 ROMS we don't believe it to be kernel related. However check this originally posted by WillyJay on Rootz.

>Appears deep sleep was an issue with Google Network Location Services in 4.2....see this think for an apparent fix.

http://rootzwiki.com...10#entry1023486
[Samsung Galaxy Nexus] ak:
I can confirm that with new merge of source into kernel, deep sleep works.
[Samsung Galaxy Nexus] Ruggerxpunk:
Can you please fix that link? :)

Could you please explain what this means? Is there a download for this 'new' kernel?

Thank you both!
[Samsung Galaxy Nexus] dandroid13:
Check his thread here: http://xdaforums.com/showthread.php?t=1883298
[Samsung Galaxy Nexus] Lochman79:
Deep sleep works fine with the stock kernel, but once I flash this kernel, it does not. Flashing back to the stock kernel fixes deep sleep. At last these are my findings using bixies Rom.
[Samsung Galaxy Nexus] Braneless:
First day with v6 and JBSourcery resulted in outstanding battery life and performance:
[Samsung Galaxy Nexus] WoodroweBones:
Thats actually exactly what I was running as well for my earlier post about battery life (well v5 instead of v6)
[Samsung Galaxy Nexus] Dattack:
I have been using this kernel since yesterday and I get deep sleep with a 4.2 ota rom.
[Samsung Galaxy Nexus] an430:
bigxie's

---------- Post added at 11:26 AM ---------- Previous post was at 11:24 AM ----------

bigxie's rom with this v6 4.2 kernel

deep sleep no problem

but sudden screen on happen.
[Samsung Galaxy Nexus] purian23:
Thank you sir, we really appreciate it :)

To all, v7 should land with a bang, it'll be yet another first in the kernel world with the compiling toolchain that is being used. Again this with be a hybrid from here on out that is backwards and forward compatible with 4.xx/4.2 ROMs. Stay tuned!!

Purian23
[Samsung Galaxy Nexus] kara mustafa:
I hope it will be out before my running session and trip to home:) I need a great battery life.
[Samsung Galaxy Nexus] lsv-1:
Don't forget zram, wasn't working on v6 thank you!

Sent from my Nexus Prime JB 4.1.2
[Samsung Galaxy Nexus] jzero88:
Kernel is working beautifully! Trickster mod for Trinity colors. Loving it
[Samsung Galaxy Nexus] giorgis91:
Will v7 be available today? Just to know, I know that it's not a fast and easy work and I appreciate everything you're doing for us ;)
[Samsung Galaxy Nexus] bigbear6708:
What's the consensus on gov/schedule?! Just flash and forget...or is everyone using something different or tweaked to their liking? Care to share? I would love to be more intimate with my kernel!!!
[Samsung Galaxy Nexus] jzero88:
I believe pegasusq turns off one core when not used. Correct me if in wrong
[Samsung Galaxy Nexus] gm007:
Little search will be great ;)

http://xdaforums.com/showthread.php?t=1989824
[Samsung Galaxy Nexus] bigbear6708:
Thanks , have not seen that reference yet :beer:
[Samsung Galaxy Nexus] bbedward:
V7 update here:

Going back to a stock ramdisk, using an init script to set my sysctl settings (with a delay to ensure the ramdisk doesn't override them)

Pulled in latest omap source, and also fixed zram (I was dumb and didn't enable swap support).

So stay tuned, it'll be any ROM compatible again, probably 4.0-4.2.
[Samsung Galaxy Nexus] giorgis91:
Can't wait!
[Samsung Galaxy Nexus] viscocesco:
Can't wait for new version!

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] cmoG530:
Me 3! This is seriously my favorite kernel.:D
[Samsung Galaxy Nexus] bradman117:
I agree! Its my favorite too!!
[Samsung Galaxy Nexus] nickfromfresno:
Is the new 4.2 version of this kernel for the gsm nexus? Because the download file says tuna...

(Edit) never mind I see it's unified kernel, sorry for this post. If I knew how to delete it I would...
[Samsung Galaxy Nexus] bbedward:
Tuna is for galaxy nexus :)

Toro/Toroplus are the CDMA versions and Maguro is the GSM version ;)
[Samsung Galaxy Nexus] jzero88:
I don't know if it's the ROM or this kernel but I get a consistent battery drain and I know it's not a rouge app because I do the same apps on other Roms. anyone else getting a consistent battery drain?
[Samsung Galaxy Nexus] WoodroweBones:
get Gsam Battery Monitor so you can get a detailed list of your battery usage
[Samsung Galaxy Nexus] purian23:
Hey guys, just wanted to touch base with you all and put out an update on v7. I discovered a very minor issue on my end while testing that needs patched up. We would love to release, but it's not ADA's style to put out something we aren't 100% sold on yet. We go on quality vs quantity! Look forward to tomorrow even though we don't officially put out ETAs, no false promises to be made by ADA to never disappoint :)

Thank you

Purian23
[Samsung Galaxy Nexus] montbazon:
Can you alter Pegasusq's parameter?

As you know, ondemand has defect which is delayed reaction.

io_is_busy is to improve response so much.

I think turning on io_is_busy makes zen kernel more perfect.

And you'd better delete intellidemand.

it is same with ondemand in fixed GPU clock.

Thanks.
[Samsung Galaxy Nexus] WoodroweBones:
And why should they delete Intellidemand?
[Samsung Galaxy Nexus] bbedward:
I made some tweaks to pegasusq based on an email I received, sounds like it may have been you ;)

io_is_busy is enabled by default now.
[Samsung Galaxy Nexus] bigbear6708:
I think from the way his post read that intellidemand behaves similar to ondemand because the way GPU is clocked.
[Samsung Galaxy Nexus] montbazon:
CPU freq in intellidemand governor is depends on active GPU clock.

512mhz, 307mhz... so on

For example, GPU clock rises 512mhz. CPU also get high freq mode.
[Samsung Galaxy Nexus] purian23:
Per bbedward our ZenSERIES Kernel dev:

Stay tuned for a v7 update soon, finally got all the minor kinks worked out.

Went back to using a stock ramdisk, but I used some init magic to load in a custom sysctl.conf with a delay so it overrides all ramdisk values (I found that in most roms the ramdisk sets some sysctl's, and cause a bad user experience because the settings it doesn't override don't mesh well with the settings it does override)

But now it is rom independent. It will also add init.d support to your rom, only if it isn't already there.

Just had to spend some extra time getting things situated, to ensure that the user experience is consistent for everybody on all roms (4.0-4.2), without the requirement for a custom ramdisk.

I did ensure that the experience is consistent in V6, and IMO it's a good experience - but I wanted to work on getting the same consistency on the stock ramdisk, so there are no more rom version limitations and we don't change any features or mess with compatibility.

Also other things to look forward to in V7, merged in the latest omap source, fixed zram, and tweaked out pegasusq. Slightly modified some sysctl settings, but nothing major.

The major thing in V7 is just getting back to a build that uses the stock ramdisk to keep 4.0-.4.2 compatibility within 1 zip. And unlike, V1->V5 we should see consistency across all roms as far as a lot of the kernel tunables go.
[Samsung Galaxy Nexus] Savant:
Can't wait for it.
[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

ZenSERIES v7 Kernel

Main Download

See OP for further information!

Thank you

Android Developer Alliance​
[Samsung Galaxy Nexus] Savant:
Appreciate it and can't wait to use the kernel.
[Samsung Galaxy Nexus] gm007:
The phone doesn't go in deep sleep, V7 with stock rom.
[Samsung Galaxy Nexus] jjhiza:
Which "stock ROM" are you running?
[Samsung Galaxy Nexus] kyokeun1234:
+1 I just started to use this kernel so I can't tell much about the battery life but would this affect a lot on battery life?

Other then that, awesome kernel you got there!
[Samsung Galaxy Nexus] gm007:
Takju 4.1.2 updated to 4.2 via ota.
[Samsung Galaxy Nexus] jjhiza:
OK guys, I think this will simplify things a bit... If you're having issues with the kernel, please post the following:

ROM build and number

Dirty our clean flash... and be honest

Recovery used to flash

If you guys can do that, we may be able to isolate the problems. I'm running Jelly Belly 10.0 with v7, flashed through TWRP, and I haven't had an issue yet. Like I said, be honest guys, otherwise, we can't help you. We're trying fro get this right for 4.2 and your feedback had been a big party of it... Let's keep it going. :)
[Samsung Galaxy Nexus] dandroid13:
Flashed with latest CWM, running stock odexed by teshxx is a no go, bootloops in the Google logo.

Enviado do meu Galaxy Nexus
[Samsung Galaxy Nexus] bradman117:
Mine worked great
[Samsung Galaxy Nexus] adio201:
Kernel works like a charm I got toroplus jbsourcery ROM flash with twrp 2.2 which I believed is and out date version but what the heck lol..also I would say dirty flash just wipe cache and dalvic cache and no boot loop
[Samsung Galaxy Nexus] jjhiza:
Is the ROM 4.1.x or 4.2? Dirty it clean flash?
[Samsung Galaxy Nexus] Dattack:
I am running AOSP by KALO 4.2.

It looks like I do get deep sleep.

Going to wait and see a little longer.
[Samsung Galaxy Nexus] jjhiza:
I'm not familiar with that ROM, do you have a link? As a matter of interest, why are you running an odexed ROM? What cwm version are you running, and had it been updated to support 4.2?
[Samsung Galaxy Nexus] kara mustafa:
I flash with last trwp, Kalo 4.2 and no deep sleep. it was a flash with a full factory reset and flashing factory image before.
[Samsung Galaxy Nexus] kindred7:
-Also on Kalo v5 JOP40C w/ baseband UGLH1

-I did a cache wipe + dalvick wipe

-Flashed with TWRP 2.3.2.1

-No deep sleep

Gonna try full wipe after back up
[Samsung Galaxy Nexus] kara mustafa:
Kernel is blazing fast but with no deep sleep battery life is terrible...
[Samsung Galaxy Nexus] Dattack:
I did a full wipe and deep sleep does workon Kalo 4.2
[Samsung Galaxy Nexus] kindred7:
Yea, no worries I'm sure it'll be solved soon.

So...

-I did a full wipe and all the fancy stuff.

-Installed KALO v5 with TWRP as a stated before and booted. Installed trickster mod to check cpu state. Got deep sleep on stock.

-Rebooted and cleared cache etc and installed zen v7, booted and no deep sleep. Figured I should try removing trickster and use cpu spy instead. Still no deep sleep.

So I basically had Kalo (didnt change baseband) and the zen v7 all flashed with TWRP. Not sure what else I could check.

Interesting... v5? What did you flash it with? Also did you change any kernel settings (scheduler/gov)
[Samsung Galaxy Nexus] Dattack:
I did full wipe, install Kalo, install v7, then reboot. Nothing fancy. I was using twrp version 2.3.2.0

I used the default governers/scheduler
[Samsung Galaxy Nexus] kindred7:
By fancy I meant the usual wiping.

-Wiped and flashed Kalo v5 and zen v7 at the same time with twrp 2.3.2.1

-booted and in and checked deep sleep with cpu spy.

Confirmed, deep sleep works on v7. I'm gonna try and break it now.
[Samsung Galaxy Nexus] viscocesco:
Flashed on Cyanogen, deep sleep works well (wipe cache e dalvik before flash).
[Samsung Galaxy Nexus] kara mustafa:
I think the is something wrong with trickster mod... I did the same steps as you but there is no deep sleep when I use trickster mod

Wysyłane z mojego Nexus 7 za pomocą Tapatalk 2
[Samsung Galaxy Nexus] kindred7:
I agree with you, just installed trickster after confirming deep sleep and I lost it. Even after removing it I still have no deep sleep.
[Samsung Galaxy Nexus] viscocesco:
I use Trickster Mod on latest CM build without problem, I think that the problem is with new base 4.2
[Samsung Galaxy Nexus] Dattack:
Alright. I loss my deep sleep now too. Not sure what I did.
[Samsung Galaxy Nexus] giorgis91:
Bootloop form me :( I wiped cache and dalvik before flash but didn't boot

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] in1400:
V7 with JBSourcery 3.2, everything is OK. No bootloop, DeepSleep works well. I have done only Cache Wipe (both) and fixing permissions.
[Samsung Galaxy Nexus] jex77er:
No deep sleep for me either, shame because the kernel is fast.

I'm running stock 4.2 with super su and rooted.

Left it an hour with the screen off, deep sleep was unused in cpu spy. I'm not using any kernel tweaking tools, eg trickster mod.

Hope its fixed soon :)

Edit- flashed over the exiting rom, no wipe of data, but did wipe both caches. Didn't try fixing perms.
[Samsung Galaxy Nexus] kizaros2g:
no deep sleep for me too. :(

ROM: 4.2 Cataclysm
[Samsung Galaxy Nexus] Cobra78:
No deep sleep for me too.

Stock odexed/rooted/busybox 4.2 Rom

With original kernel deep sleep is working.
[Samsung Galaxy Nexus] ak:
Bloutooth service probably block deep sleep state :rolleyes:
[Samsung Galaxy Nexus] dandroid13:
Seriously? http://xdaforums.com/showthread.php?t=1989930

It was a clean install because it's 4.2, isn't it kinda obvious?? I'm using CWM 6.0.1.5 which was working with v6. I use odex because I don't care about mods...

Enviado do meu Galaxy Nexus
[Samsung Galaxy Nexus] jjhiza:
That's fair enough. I asked for a link because it was like 2am here, and I just wanted to be able to help quickly. While I am responsible for PR, I still own an LTE Nexus, and I'm not familiar with the GSM ROMs. I asked about a clean install because apparently it's not that obvious to many people (I don't know why), that moving from 4.1.x to 4.2, requires a clean flash. As for the question about the odexed ROM...It was just an honest question; most/all of the CDMA ROMs are deodexed, so I was mainly wondering if there was any special enhancement to performance as a result of running odexed.

Overall, the snark isn't needed though.. I'm trying to help, and don't have the time to read every ROM thread in the GSM forum. :o
[Samsung Galaxy Nexus] kyokeun1234:
Because of the problem with deep sleep,I guess I'll use stock for now, but since I had great experience with this kernel, I will keep this thread subscribed :)
[Samsung Galaxy Nexus] jjhiza:
Have those of you with deep sleep issues tried opening Maps and letting it lock on your location? Starting up Google Now has also seemed to work for some people. From all the feedback we've gotten, this deep sleep problem is ROM related, not kernel related, but there's no uniform consensus yet. Try opening Maps though, and see if that helps at all. :)
[Samsung Galaxy Nexus] kyokeun1234:
OK I just flashed boot image from the stock deodexed 4.2 and I still don't have deep sleep... Odd...
[Samsung Galaxy Nexus] gm007:
I don't have maps app installed, not even google now.

All the other kernels have deep sleep only this one not.

Sure it's not rom problem cause i am on a clean stock rom.
[Samsung Galaxy Nexus] dandroid13:
I've been flashing kernels for a long time and never experienced this... It's just weird.

Enviado do meu Galaxy Nexus
[Samsung Galaxy Nexus] kyokeun1234:
This is really weird... I have restored from my old backup (stock 4.2 with stock kernel) and still no deep sleep. I swear to God I had this before... What am I doing wrong?
[Samsung Galaxy Nexus] adio201:
Why the heck is everyone complaining about no deep sleep you must have done something wrong or forgot to wipe my phone sleeps like a baby
[Samsung Galaxy Nexus] kyokeun1234:
Are you on android 4.2 or 4.1.x? We have problem on 4.2 not 4.1
[Samsung Galaxy Nexus] adio201:
4.1.2
[Samsung Galaxy Nexus] billouetaudrey:
No Deep Sleep is for 4.2...

Envoyé depuis mon Transformer avec Tapatalk
[Samsung Galaxy Nexus] kyokeun1234:
So you have deep sleep because you're not on 4.2. Problem occurs when we have 4.2 android.

BTW, I've posted some posts saying that even in stock kernel deep sleep doesn't work. Well it seems to work now so I'll be waiting for you guys fix this issue :)
[Samsung Galaxy Nexus] jjhiza:
I do have to say guys, that at the moment, it appears that the majority of the issues are being reported by our GSM users. It may just be a coincidence, but rest assured, we're working to isolate the source of the problem(s), and find a fix, if one is indeed needed. :)
[Samsung Galaxy Nexus] modstorm:
Deep sleep was working perfectly until I installed Trickster Mod. Maybe it's a problem when restoring Trickster from Titanium Backup ?
[Samsung Galaxy Nexus] kyokeun1234:
I do have trickster too and that could be the problem but odd that only this kernel doesn't have deep sleep...
[Samsung Galaxy Nexus] jjhiza:
Hmm, I'm not sure. Have you uninstalled it and reinstalled it clean from the Play Store? I restored about 85 apps with TiBu (including Franco's app and ROM Toolbox), and didn't have any issues. I do know that TiBu got an update late last night to support 4.2 a bit better, so there may be an issue with older versions of the app. Idk though... Just thinking out loud. You are the second or third person to mention a potential Trickster conflict though, so I'll try to test it out on my end.
[Samsung Galaxy Nexus] billouetaudrey:
For me, ZenSeries v7 no deep sleep, last Arnakia DeepSleep OK...

Envoyé depuis mon Transformer avec Tapatalk
[Samsung Galaxy Nexus] ak:
The problem isn't trickster app! :D
[Samsung Galaxy Nexus] GerManiac:
Hi does your kernel support PGM?
[Samsung Galaxy Nexus] modstorm:
After flashing I installed it from Play Store and deep sleep was working. After wards I recovered it using Titanium and rebooted right after and after that deep sleep stopped working. Now I reflashed the rom and installed Trickster from Play Store so I will report back if deep sleep is working :)
[Samsung Galaxy Nexus] kindred7:
After installing trickster just reboot. Deep sleep stops.
[Samsung Galaxy Nexus] billouetaudrey:
If you talk about anarkia, yes

Envoyé depuis mon Transformer avec Tapatalk
[Samsung Galaxy Nexus] purian23:
Thank you for reporting guys, we are getting a ton of mixed results. As its been said, our kernel aside when transitioning from 4.1 - 4.2 ROMS or even one Devs 4.2 to another's, you should always be clean flashing for now. Some kernels are using custom ramdisks overwriting some of the settings on the custom kernels. The ROM devs are hard working for good GPS and sleep issues on their end as are we on the kernel end, lots of things are in play.

Simply stated, one person on the exact rom and kernel is reporting zero issues, sleeping just fine, while another on the same setup is not deep sleeping. Some of it has to be user defined, some rom/kernel defined. We are working diligently as jjhiza stated on making sure it's not on our end to the best of our knowledge.

Thank you all for reporting, using and supporting ZenSERIES

Purian23
[Samsung Galaxy Nexus] GerManiac:
I mean Ponury Gesture Mod (slide2wake)

Not sure if we are talking about the same thing ;)
[Samsung Galaxy Nexus] bradman117:
Kernel is working great for me :) :thumbup:
[Samsung Galaxy Nexus] kindred7:
So far from the replies this is what I gather...

Cyanogenmod+trickster+4.2 has no deep sleep issues

Stock/AOSP+Trickster+4.2 has deep sleep issues, noted by me and several others after a reboot. For poops and giggles Trickster hasn't been updated since Nov 10th and 4.2 came out 13th.

Since it is after a reboot and anarkia1976 (kernel dev?) stated it isn't Trickster it maybe a simple reboot that's the issue. I tried this idea with a fresh install factory reset and indeed after installing kalo v5+zen v7 I had deep sleep. I rebooted without installing trickster and deep sleep is gone. Previously I didn't check deep sleep between rebooting and installing trickster.

Can anyone on stock/AOSP freshly installed confirm that after a reboot with zen v7 installed deep sleep stops? I want to be sure it's not that I just didnt wait long enough (waited for about 45 seconds 5 times, this was with a clean install.).

Also if the kernel is working great mention what build and any kernel modding apps installed might help the zen-team.

I really like this kernel and want dat deep sleep :good: