yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] elmexicanoalto:
Sorry about that. I have removed the link from the post.

Sent from a cloud of smoke
[Samsung Galaxy Nexus] Wh1t3Rose:
How's battery life on this can anyone give a general idea. I usually just use my phone for texts YouTube, and TPTK. 2-3 hours screen on when I'm home on WiFi. Will this give me 12-15 hours?

Oh and if I don't do any Gaming I should be fine with a 307 GPU right?
[Samsung Galaxy Nexus] kinfolk248:
zen is GREEAAAATTTTT as tony the tiger would say....im still on 4.1.2 btw w/ v11
[Samsung Galaxy Nexus] cms5423:
bbedward: if it would make you feel better, you could create a subdirectory on goo.im and just name it "test builds"?
[Samsung Galaxy Nexus] Wh1t3Rose:
I'm gonna go ahead and flash. Can't wait to see how battery holds up!

Edit: does this support fast charge?
[Samsung Galaxy Nexus] purian23:
These are only temporary at the moment. We are using goo.im until our sites facelift is complete :) Those of you on 13 or preview 14 now are in for a final version treat!
[Samsung Galaxy Nexus] cmoG530:
Yeuh! Lol In all honesty, this kernel is the only kernel that I anticipate coming out. I haven't had that since Trinity 67.

>-Sent From Something That's From Somewhere-<
[Samsung Galaxy Nexus] -freedroid-:
Thx for the quick reply.

I can't change the colors in Trinity Toolbox so they are very "yellowish". Is there a solution for that issue?

Sent with Galaxy Nexus
[Samsung Galaxy Nexus] cmoG530:
Trickster mid in the play store. TT seems to not play well with other kernels sometimes.

>-Sent From Something That's From Somewhere-<
[Samsung Galaxy Nexus] ak:
Trickster app works very well for all kernels ... the problem isn't his :good:
[Samsung Galaxy Nexus] Valaran:
Flashed over slimbean 3.1 (kernel AK, 4.1.2, maguro)

bootloop on "google" screen =(

Flashed two times with wipe cache/dalvik, same issue.

Flashed back "ak kernel" and boot ok.
[Samsung Galaxy Nexus] psxsnake:
was a surprise this kernel... flashed on XYLON

battery life amazing...
[Samsung Galaxy Nexus] ak:
Check back into thread .... ak ramdisk have ZX compression ... zen universal ramdisk = bootloop

Flash stock and then zen :good:
[Samsung Galaxy Nexus] -freedroid-:
Trickster doesn't run well on my Nexus. I had various SOD when using Trickster. I don't get SOD on the other kernel tools so imo Trickster is causing a problem.

Sent with Galaxy Nexus
[Samsung Galaxy Nexus] ak:
i dont think this ... post last_kmsg ....! please ....
[Samsung Galaxy Nexus] bbedward:
Cool :) I think v14 will be a pretty special release in comparison to the last couple.

Yes, v14 is taking a more performance-oriented stance with the new ZenX (zeneractive v2). The default settings were brought back a bit, but I still expect battery life to be solid ;) ZenX also hotplugs significantly more efficiently than zeneractive in my opinion, which may save battery on its own ;)
[Samsung Galaxy Nexus] -freedroid-:
Ok I'll try Trickster again and post kmsg if I have SOD.

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] billouetaudrey:
One reboot with Zenx and zen sheduler...

No issue for the moment with Zenx and bfq...

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] Valaran:
Thanks for the tip ! I try this right now :)

EDIT: Works fine ! Great kernel ! Really smooth !
[Samsung Galaxy Nexus] purian23:
Would anyone like a stellar update to this kernel already? :)
[Samsung Galaxy Nexus] f100cleveland:
I'll take one! This kernel runs great, so I can only imagine the update.
[Samsung Galaxy Nexus] odin13:
Stellar sounds interesting :D

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] musashiken:
Pretty please.
[Samsung Galaxy Nexus] WoodroweBones:
Hopefully the new version will fix my browser issues. Going to reinstall Chrome as well because its getting very frustrating. As an example I went to go download the new kernel and currently my phone is sitting here unresponsive stuck looking at the top page of this thread. It should come back in 3-5 minutes at which point I'll try again and hope it goes through

---------- Post added at 10:35 PM ---------- Previous post was at 10:04 PM ----------

Just an update on my issue. 2.0 seems to have made my issue worse. Here is what I did:

- Downloaded the 2.0 Kernel (had a "freeze-up" and had to wait a few minutes to get it)

- Completely uninstalled Chrome

- Rebooted to Recovery and wiped Cache/Dalvik 3 times each

- Flashed 2.0 Kernel

- Wiped Cache/Dalvik 3 times each

- Booted phone

- Went into Chrome, on the home page it shows what tabs I have open on my other computers. I clicked on this thread which was open on my laptop and the blue loading bar shows up about 1/10th of the way finished. Phone completely freezes to where I cant scroll or hit any buttons, etc. Eventually the screen goes off but if I keep hitting the power button i can feel the odd vibration (power menu coming up even though I'm not holding it?) and the screen will blink every so often. After about 5 minutes I get the screen to stay on and the FC box is up saying "Chrome isnt responding. Do you want to close it?" I have to repeatedly tap "ok" until it finally lets me select it. Once Chrome is closed the phone goes back to working normally.

Now clearly I must be pretty much the only one experiencing this as I'm sure most people use Chrome. What steps (if any) can I take to find out what the problem is? The browser works fine with Franco's and with Lean kernel. I am on Factory Rom 2.2 using Travp's inverted apps

Update: it seems my scheduler setting was causing it. I changed from deadline to cfq and all was good. Now even if I go back to deadline it's working
[Samsung Galaxy Nexus] kamykowsky:
On codename still not booting.

Wysyłane z mojego Galaxy Nexus za pomocą Tapatalk 2
[Samsung Galaxy Nexus] ak:
Linaro toolchain seems broke chrome browser!
[Samsung Galaxy Nexus] wwwpuntoit:
hello guys,

i'm currently on Franco's

on OP i read contrast temp control, does it mean you can actually tweak all color setting like with Franco's kernel ?

time ago i saw a video that stated that linaro would be muuuuch more performing than others, is this what this kernel is based on ?

sorry if i made some confusion
[Samsung Galaxy Nexus] Luigi_2:
Cant see the option to set max screen-off freq?
[Samsung Galaxy Nexus] purian23:
Woodrow, first again thank you for reporting. Secondly we hate to see you having these issues, but sadly they are none that I am able to re-produce. I am a full time Chrome user myself, the install options you have described wiping and installing seems correct. The only way to really tackle it further is to install your rom and go for it after a clean stock flash without mods, if it works, that should help you break down it's one of you modifications conflicting. If it still persists, try another ROM even to test if you could.

It is very strange since franco and lean does seem to work for you. But this is really the only way to debug the issues unless you can pull a logcat "watch "dmesg | tail -f"" to see what kind of activity you are showing when your troubles start.

Thank you for reporting, we are looking at another version to test for another release. That is the only ROM we've heard yet that cannot boot the kernel at the moment. As long as you wiped your cache & dalvik, that's all you can do for now.

Shouldn't be the case since 100% of our team uses Chrome just fine :(

Correct, example, cleanly install our kernel, then use say the franco app if you want and you will have full color control. To you last question, yes this kernel is built off a similar toolchain from that video :)

You are correct, by mistake this got excluded in this build and will be corrected for the next.

Thank you guys,

Purian23
[Samsung Galaxy Nexus] ntorresla:
I currently trying this kernel and everything runs smooth... I'm using it with Trinity app and it's fine.

Good job!
[Samsung Galaxy Nexus] WoodroweBones:
Yep i figured it out! This may stem back to a different issue I experienced or the method in which I tried to do it. I will try and explain here just for reference. I no longer have any issues and the kernel is running great! In fact now that I fixed the issue I swear my phone is running faster than ever especially in Chrome!

Back when I first flashed 1.0 I had an odd issue where I couldnt change the IO Scheduler. I was using Franco's app and I could click to choose my scheduler but no matter what I picked it was stuck on SIO (was trying to choose deadline). The next day I was using Chrome when I first experienced my issues. At first I chalked it up to your one-time issue type thing and then it happened again in Camera when trying to take a picture (the freeze-up thing). At this point I switched back to Franco's and all was well. I noticed that on Franco's kernel the scheduler was already at Deadline. I didnt use Franco's for very long when a user in this thread suggested I try to reflash but do a good cache/dalvik wipe before I flash it. So I went ahead and did that and reflashed this kernel. Upon booting up the scheduler was already on Deadline again so I didnt change anything and still had the same issues.

So then 2.0 came out and I flashed it nice and clean and to my chagrin the issue was still present!!! It seemed to be something that was either pinning the resources of the phone causing it to "freeze" or it wasnt processing instructions correctly. So I changed my scheduler from deadline to cfq as a test and everything worked. I then changed it back to deadline and thats where I have it now with everything still working perfectly! So somewhere in there my scheduler setting must have gotten screwed up (likely when it wasnt changing for me) and the fix was to simply toggle it to something else and then back again.

Long story short... a very weird one-time issue that others are not likely to experience!
[Samsung Galaxy Nexus] ntorresla:
clear caches
[Samsung Galaxy Nexus] WoodroweBones:
Yes I had several times. However what fixed it was just the act of changing my scheduler
[Samsung Galaxy Nexus] purian23:
I'm glad to hear you're all set dude!
[Samsung Galaxy Nexus] lordofcamster:
V2.0 don't boot on CM 10 Nightly.

No problem with V1.0

Wiped Cache and Dalvik and tried kernel change script

Sent from my C64 using a wonder
[Samsung Galaxy Nexus] ntorresla:
Take a look at the governors

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

I will try some
[Samsung Galaxy Nexus] obtained:
Aokp b5 won't boot. Just keeps rebooting at boot logo.
[Samsung Galaxy Nexus] iifuzz:
holy **** this kernel is flying.... Iv been considering switching to ota rom because of the odd lag with custom roms... This kernel seems to fix any kind of lag issues I was having with franco and leankernel... This is my new fav..

InteractiveX + deadline
[Samsung Galaxy Nexus] bbedward:
You're confusing me now :P you mean zeneractive?
[Samsung Galaxy Nexus] shawnaye:
wonder when is v14 coming out, gonna sleep soon :(
[Samsung Galaxy Nexus] purian23:
Kernel Update!

Introducing

v3.0.56-ZenSERIES v14 Kernel

*ZenX Rises*

Fast, Smooth & Battery Friendly

Unified Kernel for Toro/Toroplus/Maguro

- ZenSERIES_v14
- Multiple misc. wifi fixes
- Some other misc. fixes, a couple scheduler fixes backported to v3.0 by faux
- Some more adjustments to the lower-end voltages/margins. One of the mid-higher range voltage steps was wrong
- Several improvements in the kernel config.
- Fix some scripting issues, typo in sysctl.conf, don't rely on the sysctl binary to set sysctl values*
- Many roms don't have it, helps with permissions for min/max/governor, and other misc*
- Deprecated zeneractive
- Added ZenX (zeneractive v2)
- Fixed rare SoD (phone alive & accessible, but perm. suspended state) bug that was present on zeneractive
- 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
- XXX Quirk! If you are on pegasusq/hotplug/ZenX and you change governor to a non-X gov including*
- Ondemand/interactive/intellidemand/performance/adaptive/conservative* _while your second core is OFF_, it will never re-enable itself
- This only applies if you change your governor while the core is removed
- Workaround: I added a helper script, so, as root, you can just run "set_core_online" to manually re-up your CPU (you only have to do this once)
- This is a pretty rare case, and if your governor is set on boot - this won't affect you anyway!

ZenSERIES Kernel v14 4.2

ZenSERIES Kernel v14 4.1

Main Download

Enjoy!

See OP for further information!

Thank you

Android Developer Alliance
[Samsung Galaxy Nexus] bbedward:
These v14 builds are fresh, not the same as the unofficial ones some people got their hands on yesterday :good:
[Samsung Galaxy Nexus] elmexicanoalto:
Didn't see your post right after. Awesome. Flashing right now!
[Samsung Galaxy Nexus] bbedward:
Yes ^^

https://github.com/AndroidDeveloper...mmit/d5ba8641662629ce25adcde12cee952d0f75f443

https://github.com/AndroidDeveloper...mmit/bf177e2d77398bc9f42eb71506372752c87cd7d2
[Samsung Galaxy Nexus] billouetaudrey:
No no Zenx ;) i was download this morning v14 (dropbox url)...

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] Wh1t3Rose:
This kernel is amazing. I'm @ 90% after 3.5 hours. 30 minutes of Pandora. Battery at the end of the day is gonna be insane!
[Samsung Galaxy Nexus] anthonyp326:
What r ur configuration?
[Samsung Galaxy Nexus] Wh1t3Rose:
Everything is pretty much stock. I just flashed last night. This os my first discharge. Using IntellidemandX
[Samsung Galaxy Nexus] TheMorpheus:
SOD just after a call... I give up, I'll stay with stock CyanogenMod kernel for a while!

Thanks anyway
[Samsung Galaxy Nexus] JY02800190:
sod too
[Samsung Galaxy Nexus] nikulogical:
Franco has not been giving sods to anyone.

Sent from my Paranoid Francoid
[Samsung Galaxy Nexus] anthonyp326:
I just Dont know how to install IMG?
[Samsung Galaxy Nexus] gm007:
Fastboot flash boot xxxxxxxx.img
[Samsung Galaxy Nexus] mpokwsths:
Yes, but Franco is busy now developing for the Nexus 4.

So, I prefer an ongoing project full of features and a great variety of options than Franco...

ZenSERIES is great. Never had any problems...
[Samsung Galaxy Nexus] bbedward:
Here's some hot fixed v14.1 builds I'm testing.

http://goo.im/devs/bbedward/v3.0.56-ZenSERIES_v14.1.zip

http://goo.im/devs/bbedward/v3.0.56-ZenSERIES_v14.1_android41.zip

Had some last minute changes go into v14 before it was released, seemed harmless but seems they may have caused some issues, temp reverted in these builds.

---

Oh, and there's a lot of aftermarket kernel options for the GNex. I don't have anything against any one of them and i think they're all fine :) However, probably should keep affairs/issues with them in their sections. Don't want to cause any problems :)
[Samsung Galaxy Nexus] anthonyp326:
what issues are you specially talking about
[Samsung Galaxy Nexus] dre1187:
So just installed v14 this morning and had 2 SODs...after the second SOD i changed governor from Zen to interactive and it seems to be working just fine...would you recommend installing v14.1? I really love your kernel its just a tad frustrating trying to turn my phone on and have to pull the battery in order for it to work lol again thanks for all your hard work!!
[Samsung Galaxy Nexus] bbedward:
...very very frequent "sod" (phone active, screen wont turn on)

I missed it on v14, managed to get 3 within an hour though. 14.1 is the same as the build I ran all day/night yesterday (a few reverts), no issues on it.

Still confirming, but seems good so far. Getting to purian soon to update the threads :)
[Samsung Galaxy Nexus] tommy0823:
Everyone getting the sod, raise your voltages in increments on 10 or 15. Seems to help.
[Samsung Galaxy Nexus] bbedward:
In this case, it's a bbedward-induced bug. Go back a page to see the fixed build :)
[Samsung Galaxy Nexus] anthonyp326:
I'm assuming first link is for 4.2 and second is for 4.1 ?
[Samsung Galaxy Nexus] bbedward:
Right
[Samsung Galaxy Nexus] anthonyp326:
Will there being a problem lowering max screen off to 384?
[Samsung Galaxy Nexus] sajty:
Why you want to this?0 battery save,only problems can brings this.
[Samsung Galaxy Nexus] anthonyp326:
Okay thank u
[Samsung Galaxy Nexus] bbedward:
Probably not, you may get some issues (lag, slowness) if a process is using intensive CPU.

In my experience, you might as well keep the screen off google/samsung recommend (~700MHz). Likely your phone won't really exceed the minimum frequency much anyway while idle. But if maybe a phone call or background service causes a spike in CPU usage (ondemand/interactive based governors scale based on load), I'd prefer to let my governor scale up to a frequency higher than 384MHz, that way my device won't have any major lag or backups in the CPU pipeline :good:
[Samsung Galaxy Nexus] dehein:
I just had an sod on 14.1
[Samsung Galaxy Nexus] purian23:
What settings/gov where you using?
[Samsung Galaxy Nexus] purian23:
ZenSERIES Kernel v14.1

Hotfix release for ZenX Governor

Our forums have been updated with the links.

Download

Thank you,
[Samsung Galaxy Nexus] anthonyp326:
Is this the same as previous link
[Samsung Galaxy Nexus] purian23:
These are the same as Bbedward put out for v14.1

I updated the small hotfix logs and the updated builds on our Site/XDA/Rootz Forums :)
[Samsung Galaxy Nexus] sk8oldschool74:
What is dead line for????
[Samsung Galaxy Nexus] bbedward:
Its a disk scheduler that imposes deadlines on requests to prohibit any from getting starved.

It also provides other features like sorting/merging/etc.

A lot of the schedulers use deadlines, including zen, sio, and vr (probably cfq/bfq/fiops in their own way, never looked into the deep workings of those)
[Samsung Galaxy Nexus] justibasa:
Had an sod changing earlier with 14.1. Running Jelly bro cm10.1. Zenx at 1036 384. Zen scheduler

Don't like me........BITE ME!!!
[Samsung Galaxy Nexus] cmoG530:
Loving 14.1. No SOD, with PGM enabled. All around, smooth performance.

>-Sent From Something That's From Somewhere-<
[Samsung Galaxy Nexus] elmexicanoalto:
Is anybody else's Max Screen Off value always tend to revert back to 57600 if selected a different value? My values stick for like 5 mins then when I go back into Trickster Mod it reverts back to 57600. I always double tap the check mark and have set to boot.

Sent from a cloud of smoke
[Samsung Galaxy Nexus] nitsua98:
Happens to me too
[Samsung Galaxy Nexus] cmoG530:
Using SetCPU it doesn't. Trickster keeps everything the way it's set up on SetCPU. There are free alternative apps like that around though. SetCPU is just reliable.

>-Sent From Something That's From Somewhere-<
[Samsung Galaxy Nexus] Wh1t3Rose:
My FIRST discharge. Only at 50%. I did use 4G today.
[Samsung Galaxy Nexus] shawnaye:
Been using v14 since release. Absolutely no problems so far on stock settings.
[Samsung Galaxy Nexus] thoiloidainhan:
are u using trickster and setcpu at the same time??? Will they interfere with each other?? I've got a feeling that my profiles set by setcpu are not applied but I dont know how to check if this is the case
[Samsung Galaxy Nexus] cmoG530:
No, I don't touch frequencies and stuff like that in Trickster. I just use it for the mods and colors. Just set whatever you want on SetCPU and trickster will copy (lack of a better word) it.

>-Sent From Something That's From Somewhere-<
[Samsung Galaxy Nexus] kamykowsky:
During the night my phone get SoD. When I get up I have to remove battery and put it again then phone start. I'm using v14.1 version.

Wysłane z mojego Galaxy Nexus
[Samsung Galaxy Nexus] billouetaudrey:
Governor ? Freq ? Sheduler ?

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] kamykowsky:
Gov ZenX, Freq stock, Sheduler Zen.
[Samsung Galaxy Nexus] Cobra78:
I had a sort of sod with every governor that had hotplug: when i make a call the screen goes black, soft button remains on, the call start but after some seconds the phone reboot. Even with 192 - 1228, even with stock frequencies and even with other kernels, the problemis the hotplug itself.

As an example: the first time i've had this problem was on 4.1, with lean kernel, which had stock frequencies.

Everything works fine with governor without hotplug.
[Samsung Galaxy Nexus] teniente_dan:
Sod during night at charge (zeneractive+zen)

Now im testing intellidemanx + noop

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] allgsmnetwork:
kernel very bad !!!

kernel very bad !!! franco kernel the best in xda :cool:
[Samsung Galaxy Nexus] sajty:
LOL,you poor little baby.Flash franco and go away,nobody is interested in your stupid and pointless comments.
[Samsung Galaxy Nexus] sago62:
There are many kernel on the square! choose what you like, but do not make stupid comments ...
[Samsung Galaxy Nexus] vincentistan:
just had a sod in the middle of the day with v14.1, rom is 'unofficial nexus something' by flappjax, kernel zen, governor zen x, no values changed, no pgm
[Samsung Galaxy Nexus] sago62:
I find this kernel instead of the best ... with build 14.1, xylon flies ...
[Samsung Galaxy Nexus] billouetaudrey:
No sods since yesterday

ZenX, Zen, Stock value
[Samsung Galaxy Nexus] ak:
This isn't Franco thread :thumbup:
[Samsung Galaxy Nexus] mixtapes08:
No one needs your opinion ahole and please change your profile picture it doesn't fit in your stupid attitude.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rzgomba:
Same thing happened to me.
[Samsung Galaxy Nexus] vampire_god:
Got SOD using 14.1 for 4.1

ZenX, Zen, Stock value, android Color Profile.
[Samsung Galaxy Nexus] billouetaudrey:
Sod are very randomly... No sod for me since Last night...

Chance or rom ?

Xylon v12 + Zenseries v14.1

All by Default...

No Pgm

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] mpokwsths:
You very idiot...

:D

To our matter: ZenX and IntellidemandX work great. Conservative also. But ... Interactive (which should be the priority of every kernel as it is Google's choice) has problems. Not all clock speeds are populated. When I set (using trickster mod) max speed greater that hi_speed_freq the max is ignored and the hi_speed is used as max and other problems. Please fix interactive.
[Samsung Galaxy Nexus] lippol94:
Come on guys :)

First forums rule:

Don't feed the troll

:cowboy:

If you keep quoting him you'll follow his game. A single post which gets no quotations dies alone :)
[Samsung Galaxy Nexus] Frank_9.5:
Do I have to wipe cache/dalvik every time I install a new version of the kernel?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Master94ga:
Work with Cm 10.1?
[Samsung Galaxy Nexus] kamykowsky:
Next SoD after phone get fully charged.

Wysłane z mojego Galaxy Nexus
[Samsung Galaxy Nexus] bbedward:
These SoDs blow my mind still :-p

I wish I could get them, I use 192 min and can't seem to get a SoD.

Maybe if I go back to v14 and watch dmesg until sod it'll tell me something ;)
[Samsung Galaxy Nexus] vincentistan:
i think it has something to do with the hotplugging, i usually get sod when i havent touched my phone for a while (so its probably deep sleeping) then i suddenly get a message notification but the screen wont turn on :P i changed the governor to on demand now and havent had any sod
[Samsung Galaxy Nexus] bbedward:
I'm wondering if maybe the hot plugging thread is getting called by CPU 1 sometimes, maybe need to ensure it only runs on CPU 0.

Maybe hot plugging and sr don't get along for some people :-p, but the hot plugging itself should be pretty reliable.
[Samsung Galaxy Nexus] sago62:
I also had sod .... to restart the battery had gone from 40% to 100% :confused: ... I use the stock kernel, only max freq. to 1300MHz ...