yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] r80ies:
I have had this issue since 2.4. I thought it was a hotspot issue. I sent my logs and have since updated to 2.5. Then is morning had another lost signal and subsequent hotboot. I am trying 2.5.5 right now. I checked my lowest and I have fatal signal error 11.
[Nexus 6  Original Android Development] jkc120:
Method for testing chopiness

Figured I'd post my method I used to get [MENTION=3357040]Imoseyon[/MENTION] objective numbers to compare v2.0 -> v2.5 and stock that I sent to him:

I really appreciate [MENTION=3357040]Imoseyon[/MENTION] taking the time to debug this stuff and work directly with people to address the issues. It's why I was stoked when I saw LeanKernel was happening for the N6 and why I'm sticking with LK (well, maybe v2.1 for now :p).

Thanks again!
[Nexus 6  Original Android Development] Imoseyon:
Yup we'll track this down. thanks
[Nexus 6  Original Android Development] jodvova:
I've moved to r26 from Franco, all with default settings on stock 5.1 with no additional mods. It feels way much fluid than 2.5. (BTW I did configure not to increase low freq and not decrease high freq, and performance mode in lkconfig)

I'm not sure why is that.
[Nexus 6  Original Android Development] franciscofranco:
Isn't it obvious? Franco > Imoseyon!!!
[Nexus 6  Original Android Development] old_fart:
Ha Ha Ha Ha . . . . Once more you prove that ( at your core ) you're a REALLY funny guy ! ! !

Creator of 'honest' chuckles . . .
[Nexus 6  Original Android Development] Imoseyon:
That's exactly why. You lost performance when you told lkconfig not to raise minfreq. I think [MENTION=2934020]jkc120[/MENTION] 's testing also confirmed that.
[Nexus 6  Original Android Development] Imoseyon:
So thanks to [MENTION=2934020]jkc120[/MENTION]'s testing we figured out why some people had performance regression starting with v2.2. It only affected those of you that opted to "prevent raising of minfreq" via lkconfig.

Apparently the way I implemented the mitigation code is not efficient. For now, re-enable that option if you have it disabled (instead disable mpdecision via another means). I will have this fixed in v2.6.

Again, this only affected folks who chose to mitigate raising of minfreq via lkconfig
[Nexus 6  Original Android Development] SilkyJohnson:
I like how you pushbullet, boy ?

(Django)
[Nexus 6  Original Android Development] jodvova:
Can you elaborate? In sys mon I've seen CPU freq going up to 2.6ghz on all 4 cores, its not like they were all stuck at 300.
[Nexus 6  Original Android Development] bluntman420:
Imoseyon, I have tested the ocuc 2.5 build for frequency mitigation and it does work correctly but it defaults to stock frequencies of 2649 at 40% battery instead of the oc frequency of 2880. Not sure about the GPU? Could u please look into this if you have a chance? Thank you.
[Nexus 6  Original Android Development] neobuddy89:
Probably this commit:

https://github.com/imoseyon/leanKernel-shamu/commit/ed44b7f85677e63f23c616119d1490979b27231b
[Nexus 6  Original Android Development] Imoseyon:
Ah you are looking at maxfreq. The setting in lkconfig was to specifically prevent mpdecision from raising the minimum frequency. Either way this is being fixed.

That is correct. This will be fixed in v2.6 as well.
[Nexus 6  Original Android Development] epagib:
Just want to say thanks, Imoseyon. Gotta say you're amongst the most responsive (not to mention patient...given all the requests and questions) developers. Much appreciated.
[Nexus 6  Original Android Development] wera750:
Hope you don't mind me sharing this [MENTION=3357040]Imoseyon[/MENTION], this is an init.d script to enable sweep2sleep with haptic. You can edit the values to your liking, just put this in the /etc/init.d, set permissions, reboot and profit. https://www.dropbox.com/s/niq8fvd8awdiold/sweep2sleep?dl=0
[Nexus 6  Original Android Development] mjohnson4580:
does this kernel have frandom enabled if not how can i enable it
[Nexus 6  Original Android Development] JohnCorleone:
Holy crap, I can't wait for my Nexus 6 to get here next week! I lived on the Lean Kernel on my Galaxy Nexus. I have been hearing that its living up to its legendary status from my friends:thumbup:

Edit...I probably should have read the OP more thoroughly but...is there a Leantweaks script like in the GNex days or an app that I need to purchase that I can directly download new builds from? Thanks

Sent from my HTC One using Xparent Gray Tapatalk 2
[Nexus 6  Original Android Development] wietse1988:
On the latest test version 2.5.8a6 my phone turned into a 3core phone. Performance feels better though than on 2.5.

Edit: Did flash the rom again, and then the kernel. Now everything is looking good! I'm ready for the 2.6 ocuc version! ;)

Edit again: I think it has to do with thermal throttling, when it is above 40*C it goes to 3 cores. Was charging the phone and playing clash of clans, phone can get quit hot then.
[Nexus 6  Original Android Development] djcsurf:
Currently also working well, as expected 2.5.8a6 on AICP.
[Nexus 6  Original Android Development] rauschkugl:
I think you have to turn on mpdecision for the phone to hotplug correctly again.

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] magnum870:
Terminal emulator -> su -> lkconfig

That will be the config script method (been a while since my GNex, but I think it was similar)

No app to download the latest version, but Imoseyon has just recently started using/testing Pushbullet to announce releases. Just subscribe to channel "imoseyon"
[Nexus 6  Original Android Development] JohnCorleone:
Thank you good sir! My friend is getting 2 days off of a single full charge (with sync, GPS, etc on) using this kernel. I don't know what kind of magic Imoseyon works but my devices have always been super stable with great battery life using Lean kernel. This is going to be the longest week while I wait for my phone:banghead:

Sent from my HTC One using Xparent Gray Tapatalk 2
[Nexus 6  Original Android Development] Imoseyon:
v2.6 status

Been quite busy at work so I haven't had too much time. Three things I'm working on:

1) AICP compatibility. I got it to work but it apparently breaks root on Euphora. In the end, this may become too much of an exercise to make ramdisk compatible with all ROMs.

2) Handle prevention of minfreq change differently to fix performance regressions.

3) Folks on ocuc version will have noticed that at 40% the max freq is set to 2.6ghz - i'll have a fix for this.

I'm targetting maybe wed for the release.
[Nexus 6  Original Android Development] adame09:
Would it be easier to have an anykernel setup rather than replacing the whole boot image?
[Nexus 6  Original Android Development] Imoseyon:
anykernel is always an option but then you'd lose lkconfig and other goodies in my ramdisks. :(
[Nexus 6  Original Android Development] neobuddy89:
Simply setting OC freq in msm_thermal for both version of yours should do.

msm_thermal originally sets UINT_MAX which is quite out of range.
[Nexus 6  Original Android Development] Imoseyon:
yup already fixed in my test branch, but that's essentially what i'm doing. Oftentimes simpler is better. :)
[Nexus 6  Original Android Development] smclaughlin3:
Is 2.5.8a7 the latest what changes are in it?
[Nexus 6  Original Android Development] Imoseyon:
Ah a7 was my attempt to make a universal ramdisk for all ROMS (aicp, euphora, cm, etc.). Unfortunately this has proven to be pretty difficult especially on a single device.
[Nexus 6  Original Android Development] franciscofranco:
You know, I'm really radical towards the changes those guys do on their roms. I often wonder, do they really need those changes or they just pick everything from everywhere and stuff it all up in the same package without even wondering wtf they are doing. This has been going on for years, it's pretty annoying.
[Nexus 6  Original Android Development] Imoseyon:
I took this on because it's a challenge, and I like challenges. But it turned out to be too much of a challenge! LOL I got it to work mostly but not quite all the way - probably spent too much time on it.
[Nexus 6  Original Android Development] brymaster5000:
Have you tried an anykernel2 installer?
[Nexus 6  Original Android Development] akellar:
Exactly 6 posts ago...
[Nexus 6  Original Android Development] brymaster5000:
He mentioned any kernel, but not anykernel2. Very different things.
[Nexus 6  Original Android Development] Zorachus:
How is this kernel with Chroma ROM ?
[Nexus 6  Original Android Development] Smallsmx3:
Amazing.
[Nexus 6  Original Android Development] Imoseyon:
I don't know anything about anykernel2 - how is it different?
[Nexus 6  Original Android Development] adame09:
https://github.com/osm0sis/AnyKernel2
[Nexus 6  Original Android Development] wietse1988:
Latest test version is performing very well (2.5.12 ocuc)! Speed is very good, back were it used to be ;)! and battery life looks very good as well. Haven't found any bugs. Keep up the good work imoseyon!
[Nexus 6  Original Android Development] brymaster5000:
http://xdaforums.com/showthread.php?t=2670512

It injects ram disk edits into an existing boot.img, then packages up the zimage into the boot. Best of both worlds.
[Nexus 6  Original Android Development] djcsurf:
So there is hope for best kernel on AICP if imoseyon decides to go this route / fingers crossed
[Nexus 6  Original Android Development] Imoseyon:
I took a look at anykernel2. While I commend the effort put into this, I don't think it's quite robust enough to support what I want to do. There will undoubtedly be some edge cases and will require a ton of effort to get things to work still.

I will come back to it (anykernel2 & aicp) again at some point, but for now I commit to supporting CM/Euphora and stock. I'd imagine it will continue to work on most ROMs....
[Nexus 6  Original Android Development] M@XLOL:
Sorry for off topic but I don't know what application to use to adjust color profile. Thank you in advance.
[Nexus 6  Original Android Development] whalechan:
You can just use the lkconfig from a terminal app and select the advanced rgb/picture control.
[Nexus 6  Original Android Development] Chochiwpg:
Either terminal or you can use any kernel app that allows colour adjustment. For example I am using Franco Kernel app to control Lean Kernel and it's working great. Even has built in colour profiles to try out if you don't want to manually adjust. But you can manually adjust as well if you like.
[Nexus 6  Original Android Development] M@XLOL:
Got it worked out. The profile in the original post is amazing in my humble opinion. Thanks all.
[Nexus 6  Original Android Development] r80ies:
Sorry, another subject change but is anyone experiencing a super heated phone when charging. An example I have is when I'm charging and playing music the phone will jump to 119°F. Any thoughts are appreciated.
[Nexus 6  Original Android Development] Imoseyon:
v2.6 is up. It's not a big update, but not due to my lack of effort. :) I ended up spending way too much time trying to track down a couple of issues.

Notable changes:

1) ocuc builds should now stay at 2.9ghz when battery drops below 40% (and not revert to 2.6ghz) if you have this configured in lkconfig.

2) There is a change in there that is designed to reduce sluggishness and app launch latency by optimizing how the lowmemorykiller works. Likely to be subtle, as are almost all kernel optimizations. :)

3) more mem leak fixes and other minor updates.

As for the performance regression that was talked about for users who were preventing mpdecision's minfreq changes (via lkconfig), based on many tests I've found that that's the price you pay when you don't allow mpdecision to boost your minimum frequency during touch events. And my kernel space implementation for this was no less efficient than simply disabling mpdecision. I recommend that you leave this alone (keep the behavior stock) if you're sensitive to perceived performance during touch events.

Full changelog: https://github.com/imoseyon/leanKernel-shamu/wiki/Lollipop-ChangeLog
[Nexus 6  Original Android Development] Danvdh:
thanks a ton for your work, seriously...

running great so far, but I'm one of your easier users, I just grab the stable build, change the vib intensity and enable double tap to wake and im good to go, no other modifications
[Nexus 6  Original Android Development] garyd9:
2.6 stock.. Something odd with the turbo charge... With led set to flash while charging, the flashing stops w/ screen off. (Via sysfs)

Can't investigate more right now, but should be easy to repeat.
[Nexus 6  Original Android Development] franciscofranco:
Can you push 2.6 to github? You merged a patch according to your change-log that interests me! Thanks! :)
[Nexus 6  Original Android Development] Imoseyon:
Damn this could be due to selinux permission changes in ramdisk - i will investigate.

Sorry about that I forgot earlier - it's pushed.
[Nexus 6  Original Android Development] Efrenjr15:
Hey buddy is 2.6 ok to flash now with AICP?
[Nexus 6  Original Android Development] :
I tried LK 2.6 on unofficial Aicp 4-14 build and today's 4-15 from Aicp site and couldn't get it to boot.
[Nexus 6  Original Android Development] f-castrillo:
Has anyone successfullly used LK with the leaked LVY47H ROM? I'm nervous to try
[Nexus 6  Original Android Development] grisha1:
Not sure whether I get it all right (the sysfs-part), but for me charging led works well while charging with screen off
[Nexus 6  Original Android Development] mbegel:
Works fine.
[Nexus 6  Original Android Development] garyd9:
On boot, I run this:

echo battery-charging-blink-full-solid > /sys/class/leds/red/trigger

Typically (with stock kernel and everything <=2.5lk,) when using the quick charger or turbo charger (or whatever the damn thing is called), that causes the red LED to flash while charging. A particular oddity with the quick charger (as opposed to normal USB chargers) is that the LED flashes in a strange pattern: Every 5th blink is different. (It's strange - it kind of flutters, or stays lit longer - or something.. but only while it's quick charging.. not while charging at normal speed.) It does this if the phone is screen on or screen off.

With the 2.6lk kernel, the LED blinking is all different only when the screen is off. (When the screen is on, it performs as described above.) Sometimes it doesn't blink, sometimes it comes on and stays on, etc. It's almost as if the device is going into deep sleep while charging - and not waking up to change the LED state. (I'm not saying that this is the problem - I'm only describing what it appears to be similar to.)
[Nexus 6  Original Android Development] inzaghi75:
Does this kernel work with Blisspop?
[Nexus 6  Original Android Development] Imoseyon:
Yeah I'm hoping that AICP will stay in sync with CM-12.1. I will make sure that the kernel boots on CM-12.1.

This is a mystery. The only change in ramdisk I see in 2.6 is this:

imoseyon@leankernel:/lk2/shamu$ git show 200cd8e | grep leds
chown system system /sys/class/leds/keyboard-backlight/brightness
chown system system /sys/class/leds/lcd-backlight/brightness
+ chown system system /sys/class/leds/torch-light/brightness
chown system system /sys/class/leds/button-backlight/brightness
chown system system /sys/class/leds/jogball-backlight/brightness
chown system system /sys/class/leds/red/brightness
+ chown system system /sys/class/leds/charging/brightness
+ chown system system /sys/class/leds/charging/max_brightness
+ chmod 664 /sys/class/leds/red/brightness
+ chmod 664 /sys/class/leds/green/brightness
+ chmod 664 /sys/class/leds/blue/brightness

Potential file ownership change. But that doesn't explain the intermittent failure.
[Nexus 6  Original Android Development] garyd9:
are you at least able to reproduce the issue? I don't think it'd be a ramdisk issue. Ramdisk changes shouldn't make things wonky only with screen off...
[Nexus 6  Original Android Development] Imoseyon:
not yet but I will tonight when i get off work. Hopefully I'll be able to track it down quickly...
[Nexus 6  Original Android Development] Imoseyon:
Ok! I took a look at this. I can only reproduce your symptoms if I have the smb135x wakelock disabled. Do you by any chance have that wakelock disabled?
[Nexus 6  Original Android Development] garyd9:
No. Here are my current settings. (2.5lk). I didn't change them going back and forth between 2.5 and 2.6.
[Nexus 6  Original Android Development] galaxys:
1st time taking this for a spin, V2.6 very smooth with Chroma! Kudos
[Nexus 6  Original Android Development] Imoseyon:
That is bizarre. I see the exact same behavior you describe when I disable smb135x wakelock, but not at all when it's enabled. Do me a favor and toggle that setting back and forth to see if anything changes for you?
[Nexus 6  Original Android Development] petkyrk:
I'm really sorry for my "stupid" questions, but after a search I did in google and a small search in this thread, I could not find what exactly do the choices : wake sources 1) smb135x, 2)sensor_ind, 3)wlan_rx, 4)msm_hsic . I have no clue what these choices do and differ from each other.

thank you in advance
[Nexus 6  Original Android Development] garyd9:
So... Reinstalled 2.6 again and now I can't repeat it (and haven't changed any lk settings.) That's annoying.
[Nexus 6  Original Android Development] Imoseyon:
haha man that's just weird. Let me know if you encounter it again.

[MENTION=5871338]petkyrk[/MENTION], those are various wakelocks that prevent your phone from going to sleep (for good reasons most of the time). You can see them if you use apps like BBS, etc.
[Nexus 6  Original Android Development] old_fart:
I noticed that when I am at work ( where I have cell transmitters literally sitting feet / yards away from my head . . . ) the battery drain slope is a little bit 'steeper' than at home . . It's the "NlpWakeLock and/or NlpCollectorWakeLock" . . . So they're acting more aggressive at work ? Why ? I am using 'battery saving' selection in location, in settings because I read that it was the one to use . . . for the least amount of current . . . to track me . . . Could you please add these wakelocks to your kernel control ( throttle back ) group ? ? ?

.

Is it the play store who wants to keep tight track on me -or is it 'really' the NSA ?
[Nexus 6  Original Android Development] bigant262:
What vibration settings does everyone use? I mean what number?
[Nexus 6  Original Android Development] supercluver:
limiting NlpWakeLock and NlpCollectorWakeLock was the main goal of the Amplify exposed module... which no longer works on 5.1. It would be great if those wakelocks could be limited [MENTION=3357040]Imoseyon[/MENTION] as when I was using Amplify prior to 5.1 dropping I was seeing the best battery life I've ever seen.
[Nexus 6  Original Android Development] ahmarchi:
What app do you guys use to control kernel alongside lk config?
[Nexus 6  Original Android Development] Krunk83:
Franco Kernel Updater.

Nexus 6
[Nexus 6  Original Android Development] G1031L:
can't increase CPU min/max

I have tried everything.... 5 different kernels 7 different applications disabled mpdecision even got another replacement phone... Anything I modify in the kernel it gets instantly reverted back...... Somebody please help!
[Nexus 6  Original Android Development] BennyJr:
Kernel adiutor
[Nexus 6  Original Android Development] lainemac:
Is your battery below 40%?
[Nexus 6  Original Android Development] coldconfession13:
Wasn't able to get past boot animation on official nightly 12.1 . this is after running it on stock kernel then rebooting to install lk
[Nexus 6  Original Android Development] G1031L:
Yes it was, its working fine now at 100...

How do I prevent that throttle?
[Nexus 6  Original Android Development] epagib:
Terminal emulator

- su

- lkconfig or just lk
[Nexus 6  Original Android Development] G1031L:
can't increase CPU min/max

Option 1 to change frequency's?
[Nexus 6  Original Android Development] :
What app or process are you using to change frequencies, and are you sure that you installed the kernel correctly?
[Nexus 6  Original Android Development] G1031L:
kernal problems

Kernel adiutor, trickstermod franco and others... I even used fku to flash the kernel. Twrp with cache wipe to install the others

My uncles lg g3 almost doubles my quadrant scores (antutu and Quadrant Standard)

---------- Post added at 02:47 PM ---------- Previous post was at 02:30 PM ----------

Just at the same time
[Nexus 6  Original Android Development] Imoseyon:
Added this to FAQ (post #2):

Will this decrypt my phone?

If you're already encrypted, then it will stay encrypted after flashing kernel, *until* you wipe data. Once you wipe you will stay decrypted until you decide to encrypt again (see below).

What do I do to encrypt again?

There are several ways to do this. One way (easiest for me at least) is to adb in (or in terminal emulator):

root@shamu:/ # start encrypt

You will see the phone hot boot and once it comes up you will be encrypted again.
[Nexus 6  Original Android Development] freddienux:
Where is rastapop?
[Nexus 6  Original Android Development] digweed4me:
Google stock kernel had min CPU =1497 so that explains the battery draining I changed min CPU =300 through trickster mod on this kernel let's see how it goes
[Nexus 6  Original Android Development] pathtologos:
So you're not talking about a simple factory reset, but a full wipe like when u unlock the bootloader, correct? And this is AFTER u flash your kernel? U wipe data in twrp by going to advance, then selecting wipe data?

Thanks again!

You don't buy a Mustang for the gas mileage.
[Nexus 6  Original Android Development] digweed4me:
Yup that's what happen to me hot reebot and encrypted again but it was not encrypted as soon as flashed your kernel when it first booted.
[Nexus 6  Original Android Development] Imoseyon:
Ah that's your good old input boost built into android since JB:

init.shamu.power.rc: write /sys/module/cpu_boost/parameters/input_boost_freq 1497600

My kernel does not mess with that. When you launch an app like Trickster it captures the min frequency at the time of the launch which was boosted by the above parameter. In other words, what you see is normal and 1497 is not the true low frequency (ie. the app is lying to you).
[Nexus 6  Original Android Development] hackahero:
Let's be clear here. I'm running stock rooted and decrypted. If I flash this it will not encrypt my phone correct?
[Nexus 6  Original Android Development] Imoseyon:
To be clear, we're talking about the "userdata" (aka /data) partition. Either using fastboot erase or wiping data in recovery will achieve that goal. Before or after flashing my kernel - shouldn't matter. That is if your goal is to decrypt.
[Nexus 6  Original Android Development] simms22:
go to the advanced wipe, wipe system and data. dont wipe your storage.
[Nexus 6  Original Android Development] Imoseyon:
Correct, leanKernel will not force encrypt automatically if you're already decrypted.
[Nexus 6  Original Android Development] hackahero:
Sweet ty. Thank you for kernel as well.
[Nexus 6  Original Android Development] simms22:
its not ready for a thread yet, but itll be here in original development when its ready. here is a n6 rastapop version 0 http://goo.gl/V1riEk and [MENTION=2915683]BaNkS[/MENTION] gapps http://fitsnugly.euroskank.com/?rom=banks&device=gapps

now, considering that this is [MENTION=3357040]Imoseyon[/MENTION]s thread for his kernel, that was the first and last post like this that ill do here :)
[Nexus 6  Original Android Development] kingston73:
question about this encrypt/no encrypt thing: I understand wiping data part, but are all my app backups in titanium backup now useless? No using titanium to restore apps after wiping data and rebooting?
[Nexus 6  Original Android Development] freddienux:
Sorry also thanks
[Nexus 6  Original Android Development] simms22:
oh, warning.. youll get a force close right at boot up, then itll go away. also, when you open settings, youll get 3 force closes, then itll stop.