yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] :
Latest exp 4.2/5.2 exp 230 is a win as always!:cool: Tks Imoseyon!!

Sent from my toroplus (Skank & Lean)
[Samsung Galaxy Nexus] ajf64:
5.2 is now out

gnex_jb42_v5.2exp1-180

gnex_jb42_v5.2exp1-230

5.2 Stable

gnex_jb42_v5.2

stable think should be fixed in main post sorry the site has been taking ages to load for me lately and half the time just wont work its getting harder and harder to post lately
[Samsung Galaxy Nexus] cgrimes5:
Apps update

when trying to update paid for apps i'm getting couldn't install on USB storage or SD Card. Has anyone else had this issue.
[Samsung Galaxy Nexus] :
All good on my end. I'd try wiping playstore data, maybe reboot after and try again and see if it still happens..

Sent from my toroplus (Skank & Lean)
[Samsung Galaxy Nexus] cgrimes5:
I will try that Thanks!
[Samsung Galaxy Nexus] :
From what I've been reading people are having issues downloading apps from play due to a prob on Googles end. May be what your experiencing...

Sent from my toroplus (Skank & Lean)
[Samsung Galaxy Nexus] cgrimes5:
Yes that could be it. I did what you suggested and no go. Look into it more after work.
[Samsung Galaxy Nexus] :
Pretty good battery life I'd say. :) Using latest 5.2/exp 230 @1350/230 interactive X, sio, screen off 230-350. (Round 2)

Sent from my Galaxy Nexus (Rasbean & Lean kernel )
[Samsung Galaxy Nexus] jeffreynothing43:
My phone never uses 180 or 230...am I doing something wrong in settings?
[Samsung Galaxy Nexus] :
I know some phones just can't use certain frequencies that others can, Its strange but true. I used to own 2 Gnex phones and witnessed this .. One was able to run certain freq while other had sods. Its really strange but true.

Sent from my toroplus (Rasbean & Lean kernel)
[Samsung Galaxy Nexus] evandena:
Anyone else getting permission denied when trying to change vmin option with lkconfig? Even in a su terminal.

Version 1.1 on Beans build 6.
[Samsung Galaxy Nexus] blankit:
How's the GPS on the latest kernel I never get good GPS on lean kernel
[Samsung Galaxy Nexus] Lento10:
The new 5.3 kernel is out.
[Samsung Galaxy Nexus] noregretzzzz:
Not entirely sure what all is entailed inside a kernel, but it seems ram management is vastly improved with this kernel :thumbup:
[Samsung Galaxy Nexus] keebler021:
Dang. Is that with stock battery?

Edit: Also, which ROM?
[Samsung Galaxy Nexus] :
Yes, stock battery & Rasbean w/ a real good signal, location off... I was home that day and have an airave..:cool:
[Samsung Galaxy Nexus] ajf64:
5.3 is now out

gnex_jb42_v5.3exp1-230

gnex_jb42_v5.3exp1-180
[Samsung Galaxy Nexus] Col. Sanders:
Thanks for posting the updates. I usually leave the settings as is, just looking to make a good phone better with that said which version do you recommend?

Nvm going to try 230 for a bit and then 180. Been having a weird issue on previous build if I silence a phone call sometimes the screen stays frozen or will soft boot and lose wifi. l have to then reboot, I left all settings stock and am using Maddogiins ROM.
[Samsung Galaxy Nexus] ddaley88:
Anybody using this kernel with cm 10.1?
[Samsung Galaxy Nexus] MizzouBrent:
I am right now.
[Samsung Galaxy Nexus] ajf64:
kernel should work with all 4.2 roms
[Samsung Galaxy Nexus] ddaley88:
How's it going so far?
[Samsung Galaxy Nexus] MizzouBrent:
It didn't seem as snappy as other releases. Flashed zen and it seemed better but I got a random reboot and my system started crawling another time and I ended up having to pull the battery. So now I'm on Franco.
[Samsung Galaxy Nexus] NYYFan325:
I switched from this to Zen for a few releases and while Zen is a great kernel I had quite a few SODs, some freezes and once or twice the system slowed to a crawl. Back on lean and keeping my fingers crossed :)
[Samsung Galaxy Nexus] bearsblack:
U have to change the min frequency on boot. It boots at 350-1200
[Samsung Galaxy Nexus] bigrushdog:
All issues with eos and installing paid apps is fixed. I'm running 5.3.1 and it feels great. I'm interested in distributing eos with lean kernel as I don't have time to maintain kernels atm. What are the protocols?
[Samsung Galaxy Nexus] ajf64:
just give credit to imoseyon and let me know if you want to use packaged kernel or take from git and cherry pick ur own

what i would like to see is kernel controls implemented in EOS if you could possibly do that
[Samsung Galaxy Nexus] bigrushdog:
We compile inline so i'd just mirror his git stable branch. Also, i'll grab any boot image resources he's using. Naturally, Imoseyon gets a huge shoutout in the OP as LeanKernel is just epic and he is a killer kernel dev.

I've debated this thing with kernel controls. It would take a dev's full attention just to maintain that one feature. If you look at apps like Trickster or Franco's app, those apps are simply bad ass. Even now, I have the performance settings in our control panel. But i'm considering removing it all together for everything but xoom and tf101. It's just not up to par for modern 3 series kernels, and i don't have time to maintain it.
[Samsung Galaxy Nexus] krazyfiend:
Is anyone else getting an issue w trying to update Franco Kernel Updater (paid) or SetCPU on EOS 4 b73 and the newest experimental Lean Kernel 230?

'Couldn't install to internal storage or SD card'

I've read this is kernel related.. Would a logcat of the event be useful.. Prob should be asking imoseyon over on RW
[Samsung Galaxy Nexus] ajf64:
plz dont remove the performance controls i use them all the time i just never been much of a fan of the other aps and i was big fan or the performance controls just wish they where extended a bit but i see what ur saying it is up to you but if you do happen to add it i will love you long time :)

Ps: i spoke with Imoseyon you are good to go
[Samsung Galaxy Nexus] bigrushdog:
Update your eos build. It had been fixed and is not the fault of lean kernel or any kernel. It was a problem related to a bug in my vold source code. The only reason I even mentioned it in this thread is because at the time I was uncertain as to the root of the problem
[Samsung Galaxy Nexus] bigrushdog:
Fair enough. I'll see if I can get around to putting some polish on it. But I'm telling you. Trickster is sweet.
[Samsung Galaxy Nexus] krazyfiend:
Thanks.. I realized I flashed 70 after Goo app told me rom update avail.. Didn't pay enough attention. All is well w 73..aside from Handcent fc'ing. (pretty sure it's their team) Gosms works just fine and has grown on me.

Sorry to go OT

Lean rocks!
[Samsung Galaxy Nexus] ajf64:
agreed trickster is every thing i want in kernel control i just don't like its interface i hate having to have an app to adjust system settings i love the eos ui because it makes it feel as if its part of the phone clean simple ui. That and its just one more thing to install every time i update the rom
[Samsung Galaxy Nexus] bigrushdog:
I agree. But Ivelearned something since I got in the aosp game. When developing features, the focus shoud be on doing things that can't be done via user apps. That often means harnassing the fact that we can manipulate parts of android that require signature level permissions. like the CDMATools app. What that app does can not be done via user apps. I'm not entirely opposed to features that can be duplicated by user apps. i think my point is we don't want to reinvent the wheel. But I think we can squeeze in some cleaner system controls.
[Samsung Galaxy Nexus] ajf64:
I totally agree with you i think because trickster is not in the app store and can be a pain to reinstall via recovery every time you update the rom its tends to get annoying for me so i just don't use it but i totally agree with what ur saying any thing you can do would be a + and greatly appreciated i know any thing you do i will love.
[Samsung Galaxy Nexus] davidstjohn1:
Trickster is in the market though
[Samsung Galaxy Nexus] ajf64:
Shows how long it has been since i used it lol that works ty before it wasn't in app store you had to install through recovery lol ty for letting me know this im trying it now
[Samsung Galaxy Nexus] davidstjohn1:
That's okay no problem I'm just glad I could help have a great day.
[Samsung Galaxy Nexus] bigrushdog:
I was gonna say the Trickster interface is sick clean. I know ALOT of work was put into those layouts .
[Samsung Galaxy Nexus] Imoseyon:
Thanks for keeping the thread up to date, ajf64!
[Samsung Galaxy Nexus] ajf64:
before it wasn't like this you had to install the script from recovery and it was kinda lack luster this is much nicer now works for me:) I stoped using cuz i had to reinstall so much
[Samsung Galaxy Nexus] bigrushdog:
Thanks for cooking a killer kernel! I have a huge project to maintain and don't have time to maintain a kernel. I wish I did. But lean kernel has been my go-to kernel for a while nowAnd it's smoother than a baby's butt! And thanks for permitting me to use lk in my project. A lot of Eos fans love lean kernel. When I get lean kernel online proper credit love and respect will be shown.
[Samsung Galaxy Nexus] bigrushdog:
Just a heads up, the Toro thread needs updating.
[Samsung Galaxy Nexus] ajf64:
v5.4 is released: http://revision.io/e...leanKernel-tuna

I replaced SIO I/O scheduler with BFQ v5, and made Deadline default again. Deadline and SIO were both very very close in their performance characteristics so I felt they were redundant. BFQ brings a whole new option - its sequential reads are supposedly better than Deadline/SIO by a large margin.

5.4 Stable

Exp

v5.4exp1-180

v5.4exp1-230

sorry for delay busy day
[Samsung Galaxy Nexus] bigrushdog:
ajf64 ok Eos is up and running. Check my toroplus and toro OP's to make sure everything is cool. Also, if Imoseyon has a donate link, post it up
[Samsung Galaxy Nexus] TheOneChristo:
I know it varies by phone, but is there a suggested governor? Or is it interactive and that's why it's the default?

Thanks :)
[Samsung Galaxy Nexus] Acvice:
Kernel devs tend to stick with interactive as its googles preferred governor. Personally, I feel interactivex works a bit better for me.
[Samsung Galaxy Nexus] ajf64:
i would suggest interactiveX it seems to have best performance and battery life
[Samsung Galaxy Nexus] unimatrixzer0:
Please excuse my incompetence but can someone dumb this down for me please. What is the built-in "oc" script for the GPU overclock?
[Samsung Galaxy Nexus] ajf64:
Just use Trickster Mod from the app store you can adjust the gpu oc directly from the app its much easier then using the terminal commands or new users. I just allows you to boost the speed of ur gpu for better gaming results though its not that much a improvement and not really needed some people find it helps for some games that lag a bit.
[Samsung Galaxy Nexus] Braneless:
Trickster Mod app also works pretty well with this kernel.
[Samsung Galaxy Nexus] ajf64:
Lol edited post that is what i ment thanks braneless
[Samsung Galaxy Nexus] JohnCorleone:
5.4exp2 is out now.

Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2
[Samsung Galaxy Nexus] seezar:
yes

http://rootzwiki.com/topic/13092-le...3100-jb-420-72312/page__st__12460#entry839282
[Samsung Galaxy Nexus] paullueders223:
MMS Issues with Kernel

I seem to get issues with MMS while using this kernel. I flashed your kernel a couple days ago and I suddenly couldn't receive MMS messages. I tried wiping and reflashing my rom (CM10 Nightly Kang) and flashing lowrider MMS fix/gapps, but still didn't allow me to receive. However if I just flash my rom without flashing this kernel, MMS works fine. Can anyone confirm this issue?
[Samsung Galaxy Nexus] ajf64:
CM10 is still in pre alpha build and the kernel has not been updated as fast as cm has unfortunately. So some things might provide issues when using the kernel with a pre alpha build of a rom i can tell that mms dose work in many other JB roms and we will try to have this fixed in upcoming kernels. If any one else has more feed back on this id be happy to hear it, so we can better pin point if this is a one time issue or if more people are experiencing it i can say however that CM10 has been giving quite a few issues with kernels.
[Samsung Galaxy Nexus] v3rk:
I can't get mms to send, haven't tested receiving
[Samsung Galaxy Nexus] ajf64:
what rom you using this kernel with and what kernel version are you using plz
[Samsung Galaxy Nexus] v3rk:
Sorry I should have given that in the first place. I'm using jb stable with purely aosp rom
[Samsung Galaxy Nexus] budde2:
I'm running maddoggins JB modded ROM with the stable vs and its smooth and the battery is OK to if that helps not to jump in on the conversation
[Samsung Galaxy Nexus] ajf64:
Have you tested the stock kernel to make sure it is in fact working in the rom i have not had any one with this issue on the rom you mention so i am going to need a little more info to figure this out. CM10 is known to have some issues but usually asop roms work with no issues. Also when you installed the kernel did you wipe you cach and dalvik.

What version of the kernel are you using if you are using the stable you can always try the experimental 180 and 230 builds for better battery life.
[Samsung Galaxy Nexus] v3rk:
i'm not sure what happened but mms is working now. i flashed cm10 on recommendation of a friend, didn't like it and restored my nand. saw your post and decided to try again and now mms both sends and receives.

this kernel is amazing thanks for sharing it here :)
[Samsung Galaxy Nexus] FL0OD:
Sprint has been having issues with mms nation wide. Over the past two months people have been having off and on problems with sending not receiving and vice versa. You may see this pop back up and it's very spotty. It has nothing to do with the roms or kernels for the most part. It also seems to effect different devices differently. We have a gnex, a gs3, a ns4g, and a hero and it will effect some devices and not others. It has something to do with the way the "backbone" in your area is processing your mms' as the network infrastructure grows, changes, and is being upgraded. Hopefully it will become less and less of an issue as Sprint rolls out its new network.

†††
[Samsung Galaxy Nexus] ajf64:
any time man im not sure what version of the kernel you are running but i would suggest you run the 230 under volt version in the experimental builds link for jb it will give you the most unbelievable battery life while still preserving the fluid responsiveness of what you come to expect from the nexus and jb.
[Samsung Galaxy Nexus] toomuchgame441:
Had to come back and say what an awesome ROM, super smooth, it even has better connectivity with the network, I maintained a solid 4G signal at home this morning. Nice
[Samsung Galaxy Nexus] Zeinzu:
Kernel.

Sent from my AOSP Android 4.1.1 Galaxy Nexus
[Samsung Galaxy Nexus] rjwriter78:
Bluetooth Malfunction

I tried your experimental kernel of the 230 under volt version and my Bluetooth didn't connect at all. I switched back to your "stable" version and i was actually able to connect. The thing about the stable kernel is that you could only go up to 2 feet, by then you lose a connection with the phone. I weighed out the possibility of why i would want to be so far from my phone anyway but, i would like to go more of a distance than 2 feet. The connection starts to go into static before eventually disconnecting. Bluetooth's in general allow you to go up to 15/30 feet away. Anyway, i hope you can include a longer distance to integrate into the kernel coding. Im fine with the stable version for now. Great kernel by the way!
[Samsung Galaxy Nexus] MichaelMcEntire:
Strange, my Bluetooth works flawlessly on the 180 and 230 experimental.
[Samsung Galaxy Nexus] ajf64:
weird i have had no issues with exp 230 and blue tooth and i use it pretty regularly may i ask what rom your using. If its CM10 it is most likely the rom it still has some bugs with non CM kernels
[Samsung Galaxy Nexus] rjwriter78:
EOS Rom nightly .. eh, maybe it is the Rom. Thanks guys!
[Samsung Galaxy Nexus] dna_d:
Battery still @ 100%?

not sure, but I don't think my battery should still be at 100% after being unplugged for 10hrs.....thoughts?

Edit: RUJellin' Milestone 2, only modification is the invisible/persistent menu button...
[Samsung Galaxy Nexus] FL0OD:
This made me chuckle :D

†††
[Samsung Galaxy Nexus] ajf64:
that is really wierd that is same rom i use and i have no issues at all do you have any other mods running on the rom so we can try to pinpoint what might be causing this i would advise a full wipe and reinstall of the rom and kernel.
[Samsung Galaxy Nexus] ajf64:
5.4.2 Is now out Get it fast

v5.4exp2-230

v5.4exp2-180
[Samsung Galaxy Nexus] jeffreynothing43:
Anyone notice the color being off on the newest exp build? What should it be set at in Trickster?
[Samsung Galaxy Nexus] neo4uo:
I noticed the same thing. I am running sorcery 4.2 and tried the older kernel and noticed the color being gosh awful. Glad I wasn't the only one, but haven't tried the newest kernel from 1/3.
[Samsung Galaxy Nexus] Imoseyon:
That should be fixed in 5.5. There were tons of changes in 5.5 so if things are severely broken for you, report it here and go back to 5.4. Testers didn't have any issues.

1) interactive completely modernized to android-3.4 (tons of updates)

2) interactiveX re-written and received the same update as above.

3) interactiveX is now compatible with butter

4) Linaro toolchain updated to 2012.12

5) morfic's trinity contrast

6) fixed possible crash within display code

7) random entropy tweak to read from nonblocking pool
[Samsung Galaxy Nexus] neo4uo:
I am running Sorcery 4.2 and using trickster to contol the kernel and used same screen settings with stock kernel on lean and still real dull faded color. Could it possible be because I need to use franco to contol the kernel?

Thanks
[Samsung Galaxy Nexus] ajf64:
5.5 is up now. There were tons of changes in this one so if things are severely broken for you, report it here and go back to 5.4. Testers didn't have any issues.

1) interactive completely modernized to android-3.4 (tons of updates)

2) interactiveX re-written and received the same update as above.

3) interactiveX is now compatible with butter

4) Linaro toolchain updated to 2012.12

5) morfic's trinity contrast

6) fixed possible crash within display code

7) random entropy tweak to read from nonblocking pool

Stable

Exp

v5.5exp1-180

v5.5exp1-230
[Samsung Galaxy Nexus] stevie13.xo:
I didn't even wanna flash a different kernel on jbsourcery but over clocking this slows it down on this ROM and inarguably the fastest and smoothest thing (not oc'ed) that ive tried on this phone and haven't had any problems whatsoever within the last hour..
[Samsung Galaxy Nexus] davidstjohn1:
I'm not sure if it was mentioned a GPS broken on this kernel 5.5 I went back to 5.3 GPS works perfect just wanted to chime in and let you know. Love the kernel... Thanks for all the hard work much appreciated.
[Samsung Galaxy Nexus] bigrushdog:
I'm running 5.5.1 230 and locked in 7 seconds. Seems normal to me. This version is just wicked. This is why my build come with LK!
[Samsung Galaxy Nexus] davidstjohn1:
I guess I will download this 1 and give it a try then...
[Samsung Galaxy Nexus] ajf64:
i also have fast lock on gps try full wipe
[Samsung Galaxy Nexus] ajf64:
Ok guys 5.6.2 is now out

Feature leanKernel v5.6

Feature block/defconfig: replace BFQ with ROW, make ROW default

Feature row: Add support for urgent request handling More

This patch add support for handling urgent requests. ROW queue can be marked as "urgent". If an urgent queue was un-served in a previous dispatch cycle and a request was added to it - it will trigger issuing urgent request to the device driver.

Signed-off-by: Tatyana Brokhman tlinder@codeaurora.org

Feature block: add ROW scheduler v4 More

This patch adds the implementation of a new scheduling algorithm - ROW. The policy of this algorithm is to prioritize READ requests over WRITE as much as possible without starving the WRITE requests. The requests are kept in queues according to their priority. The dispatch is done in a Round Robin manner with a different slice for each queue. READ request queues get bigger dispatch quantum than the write requests.

Signed-off-by: Tatyana Brokhman tlinder@codeaurora.org

Improvement cpufreq: interactive(x): don't remove sysfs nodes (Fixes boostpulse errors)

Improvement ramdisk: this should fix OTG

Improvement Input: Send events one packet at a time More

Stable 5.6

EXP Builds

v5.6exp2-180

v5.6exp2-230
[Samsung Galaxy Nexus] bigrushdog:
Taking it for a spin now. Let's try some Row action! Imoseyon is killingg it.

Update: this kernel is freaking blazing! Nenamark2 is off the charts. I hate benchmarks but was curious. This is going in my nightlys for sure.
[Samsung Galaxy Nexus] ajf64:
are you adding stable to eos or exp 230?
[Samsung Galaxy Nexus] bigrushdog:
Since you suggested it, I'm running with 230. But I haven't built a nighty since we discussed it. But their going out tonight so I'll commit this beast before I do.
[Samsung Galaxy Nexus] ajf64:
ur the man every one will like the undervolt
[Samsung Galaxy Nexus] Col. Sanders:
Running ver. 5.6 on Maddoggs Rom and all seems to be good. Had a tiny SOD this morning but cannot be totally sure. Some times my Gnex takes a second to wake up when you press the power button from standby. Gonna give it a few days to be sure but it looks like we have a winner thanks guys.
[Samsung Galaxy Nexus] ajf64:
Thanks man glad ur happy if ur problem persists plz let me know so we can try to get to the bottom of what is causing it.
[Samsung Galaxy Nexus] BaileyJ205:
Flashed v5.6exp2-230

Showing SD card removed, had to go back to earlier version.
[Samsung Galaxy Nexus] TheOneChristo:
I also had an SOD on 5.6 with Rasbeanjelly.
[Samsung Galaxy Nexus] ajf64:
i would try a full wipe i have never heard of this error it dosnt seem to be common let me know if full wipe works
[Samsung Galaxy Nexus] Rimmir:
This thing is fast, like ROLLERCOASTERDIPOMGAAAAAAAH fast.

Running Maddoggin's 1/05 jb 4.2 build.

Nice work to imoseyon and the OP of this thread :)
[Samsung Galaxy Nexus] ajf64:
We are happy ur happy :)
[Samsung Galaxy Nexus] ajf64:
5.7 Is now out

v5.7exp1-230

v5.7exp1-180

Stable 5.7
[Samsung Galaxy Nexus] bigrushdog:
Don't know how we can beat 5.6exp2 but I'm taking it for a spin. Feels smooth so far.
[Samsung Galaxy Nexus] Col. Sanders:
What changes were made in 5.7, minor things? Most of the settings in 5.6 I left stock.

I was getting the SOD sometimes when the screen went blank during a phone call. I would either have to pull the battery or just wait it out for the phone to wake back up. I increased the voltage of the screen off by like 25 so now it's at 975 and not 950. Gotta give it a few days to see if it fixed the issue.

GO SEAHAWKS.
[Samsung Galaxy Nexus] matthew0776:
Running 5-7 on Maddog 1-5 wow... Super fast haven't had it long enough to know how battery will be, but so smooth and fast. Nice work.

---------- Post added at 08:12 PM ---------- Previous post was at 08:03 PM ----------

Do you have auto brightness on...? Had same problem turned off auto brightness and hasn't happened since. Worth a shot
[Samsung Galaxy Nexus] Disgustoid:
I love the kernel as it seems to give me the best battery life out of the ones I've tried.

I have to be missing something but is there anything going from 5.4exp1-230 to 5.6 and 5.7 that would cause my phone to not pick up a 4g signal as well as in the earlier version? Fully charged phone, same ROM (EOS nightly 78) with me sitting in the same spot with 4g (two bars, -86dBm) flashing the different versions over a one hour period (wiping the two caches each time), with all other settings the same. My phone automatically goes into 4g mode on 5.4 but 5.6 and 5.7 won't even register the 4g signal, showing 3g only.

This is all happening indoors so I suspect the weak signal has something to do with it but it'd be nice to get 4g at home again seeing as Sprint's 3g here is beyond terrible (averages 50-200k AT BEST downloads).
[Samsung Galaxy Nexus] matthew0776:
On 5.7 i do not get 4g either...on stock i do. The speed is very impressive. But would also like the 4g to pick up.