yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Imoseyon:
I just checked - no 5.1 source yet. :(

Most likely not starting from scratch. But I merged a lot of upstream CAF commits in an effort to stabilize stock kernel so there will be a lot of conflicts I'll need to carefully work through.
[Nexus 6  Original Android Development] hellsgod:
Just FYI the 5.0.x kernel boots up on 5.1 (anykernel because the 5.0.x ramdisk will straight reboot after optimizing apps) but the camera doesn't work. The stock kernel was compiled on january 28th, so maybe there are not so much changes :)

hells
[Nexus 6  Original Android Development] cfrank38:
So releaae aosp 5.1 for nexus 6 don't include kernel or includes the boot image with kernel compiled ?
[Nexus 6  Original Android Development] wrongway213:
Doesn't include kernel source
[Nexus 6  Original Android Development] Franzie3:
Binaries and Factory images are posted now
[Nexus 6  Original Android Development] suku_patel_22:
And kernel sources too. Let the sorcery begin!!

Sent from TheSixthDimension
[Nexus 6  Original Android Development] szale9001:
Ahem.

*sourcery

You're welcome...
[Nexus 6  Original Android Development] garyd9:
Imoseyon is in the US. It's Sorcery. The "u" is only there for people outside the US due to bit errors in transmitting the text overseas.

(edit: yes, I missed the pun)
[Nexus 6  Original Android Development] cinnak:
Pretty sure it was a pun. Sourcery...
[Nexus 6  Original Android Development] jdavis7882:
I think it was a wordplay.. Source as in kernel source?
[Nexus 6  Original Android Development] szale9001:
An intentionally bad pun, yes. :p
[Nexus 6  Original Android Development] garyd9:
Damn. I missed that. Oh, well. Back to my paying job...
[Nexus 6  Original Android Development] cfrank38:
Kernel source is live forma nexus 6 :D lets see what changes google madre. 5.1 is vary smooth con nexus 6 https://plus.google.com/+FranciscoFranco1990/posts/KB6JYHDG5U8 a comment of franco is interesting
[Nexus 6  Original Android Development] Imoseyon:
Those of you brave enough to try a 5.1 test kernel. Try booting v2.0b1 attached?

If it doesn't boot, it's probably because of the CM sepolicy file from 5.0 I left in there. Let me know - I won't be able to test this until tonight at the earliest (possibly tomorrow). Thanks!

Edit: attachment removed - beta1 had selinux issues
[Nexus 6  Original Android Development] Iyyel:
I'll be flashing and see how it works.

Will report back with whatever I can.

Thanks for the extremely fast build!

---------- Post added at 10:24 PM ---------- Previous post was at 10:19 PM ----------

Boots fine. I'll test performance and see if I notice anything.

Thanks for the fast build mate!
[Nexus 6  Original Android Development] jdavis7882:
So it boots and runs fine but I can't adjust brightness at all
[Nexus 6  Original Android Development] Iyyel:
As in brightness slider? Works fine here.
[Nexus 6  Original Android Development] tw1tch175:
boots fine but LKconfig doesn't work at all. Ambient Display also isn't working, possibly something with the proximity sensor pocket mode?
[Nexus 6  Original Android Development] jdavis7882:
Should've elaborated yes and I've noticed it's only a problem with adaptive brightness on.
[Nexus 6  Original Android Development] Iyyel:
Agreed, brightness slider is not working WITH! adaptive brightness on. Mine was turned off.

Ambient Display doesn't work either for me, plus I am noticed it not being as smooth as stuck. When dismissing apps in recents the animation stutters,

also scrolling does in settings etc, slightly.
[Nexus 6  Original Android Development] Imoseyon:
Great keep the reports coming. I'll fix them all before the 2.0 release. Thanks
[Nexus 6  Original Android Development] sniperpriest42:
So this does or doesn't work for 5.1?
[Nexus 6  Original Android Development] Iyyel:
Maybe this is because of the new kernel source or something, as I saw Franco mentioning something about

4-core mode or something, but all cores are constantly online at 1497mhz, (right now 3 at 1497 one at 300???) it seems to be very random and strange.

Perhaps it's not much but I thought to let you know any way. This is what Kernel Adiutor is telling, btw.

Also way more battery drain than stuck, but I guess that's because of what's said above.
[Nexus 6  Original Android Development] franciscofranco:
Did you merge the new source on top of yours?
[Nexus 6  Original Android Development] semdoc:
Wonder the same thing...
[Nexus 6  Original Android Development] Imoseyon:
That's pretty much what I did + the latest 5.1 ramdisk. Surprisingly there were only about a dozen conflicts I had to resolve, as a lot of the CAF commits I cherry picked were present in the new source. But in the end I may still need to rebase which would delay the release.
[Nexus 6  Original Android Development] franciscofranco:
You're insane. Starting fresh after a rebase like this takes longer, but it's probably worth it on the long run.
[Nexus 6  Original Android Development] Imoseyon:
Nah actually 5.0 and 5.1 sources are surprisingly similar and compatible. If you merge 5.1 source on top of stock 5.0 source it applies cleanly without any conflict. (Any conflicts I ran into were due to my own changes) You'll see what I mean if you compare the commit logs from between the two branches.

Still, requires further testing...
[Nexus 6  Original Android Development] garyd9:
...and you aren't?
[Nexus 6  Original Android Development] knitler:
For those with Ambient display issues. I had problems with it also until I did a flash of the new Factory Image from Google. For me it was NOT related to LK.
[Nexus 6  Original Android Development] Imoseyon:
Was there an older build that people flashed?
[Nexus 6  Original Android Development] knitler:
Not sure, I just know that people who flashed the OTA seem to have some Ambient issues, like I did, but for myself after then flashing the full image it was resolved.

I'll be flashing your kernel when I get off work to test it out.

---------- Post added at 08:51 PM ---------- Previous post was at 08:43 PM ----------

Decided to screw waiting. It does seem the kernel indeed does Bork with brightness.
[Nexus 6  Original Android Development] wrongway213:
I feel like all crackflashers should keep leanKernel handy.... currently shaking lol massssssive bootlooping... found an LK on my sd... no more bootloops.

Edit: Spoke too soon... I hate bootloops so much
[Nexus 6  Original Android Development] manup456:
I flashed each part of the .img's no ota fully stock and brightness is shot.

Edit:Great start ?✋?
[Nexus 6  Original Android Development] darkjedi:
Strangely, when I flash 1.20 on 5.1, I lose all data signal. I have to reflash the ROM again until I can get connectivity. Also the boot time is super long.
[Nexus 6  Original Android Development] flyinj54:
V2.0b1?
[Nexus 6  Original Android Development] darkjedi:
Yup, sorry. Even went from stock kernel and couldn't get data to activate. I have the new bootloader and radio as well. Strange.
[Nexus 6  Original Android Development] Imoseyon:
Ok I finally got 5.1 going on my phone. I see some massive selinux issues on v2.0b1 probably because of CM stuff in ramdisk. Hang tight until I fix those in 2.0b2.

Edit: Yup that's the cause of all the reported problems so far. Brightness, lkconfig, etc. Rookie mistake in keeping the CM sepolicy stuff in there. I'm currently fixing cpu-boost related issue (cause of battery drain reported earlier) and once that's fixed I'll put up b2 for testing.
[Nexus 6  Original Android Development] Imoseyon:
beta 2!

This one should behave a lot better. Should address all of the issues reported in the past three pages or so.

Also, I disabled core control stuff for now until I have some more time to play with it. As you've heard before 5.1 force enables all cores.

Edit: b3 posted later
[Nexus 6  Original Android Development] Yank555:
Agreed, commits ran into mine clean, one conflict was the 'add indonesia to wifi' because of my 5GHz change ;)

The 5.1 kernel is based or an evolution of 5.0, not a complete rebase, making a rebase not really necessary imho.

That's the charm of getting a kernel update via git instead of lump dumps like almost all others do (hi Sammsung)...

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v1.0-beta1 kernel.
[Nexus 6  Original Android Development] Cheater912:
No problems so far on 2.0b2 :)
[Nexus 6  Original Android Development] ballaz:
Is encryption on by default?
[Nexus 6  Original Android Development] DebauchedSloth:
Seems to be.
[Nexus 6  Original Android Development] cr4ck3r4lif3:
Yes. Surprise! ;)
[Nexus 6  Original Android Development] Imoseyon:
Ah crap forgot to turn off force encryption. B3 coming!

Edit: B3 attached! Sorry about that guys.
[Nexus 6  Original Android Development] datajosh:
Well so far I hadn't even noticed so I might just stay encrypted :laugh:
[Nexus 6  Original Android Development] Smallsmx3:
You won't notice, boot time takes a little longer is about it
[Nexus 6  Original Android Development] darkjedi:
This build is much better now. Full LTE and no super slow boots!
[Nexus 6  Original Android Development] garyd9:
Has anything changed with the 5.1 kernel (stock) in regards to encryption? I haven't had time to go through the git log in details, but I did see some comments about turning on, and off, and back on hw encryption. (hw, not sw, encryption. Presumably, if they enabled hw encryption, they'd have the proper driver from qualcomm.)
[Nexus 6  Original Android Development] knitler:
Just improved performance with software encryption. HW encrypt is still off.
[Nexus 6  Original Android Development] Krunk83:
This is only for 5.1 right?

Nexus 6
[Nexus 6  Original Android Development] akellar:
HW encryption is still turned off.

Edit: already answered, I fail
[Nexus 6  Original Android Development] ballaz:
It's a test kernel, thus I am reporting so you can make it great. Thanks for your work.
[Nexus 6  Original Android Development] wrongway213:
Right, stick to 1.17 until on 5.1.
[Nexus 6  Original Android Development] old_fart:
Running your B3 on 5.1 - - Thank you, sir ( I am NOT encrypted . . . )

Wow, I thought it would be a week instead of 'hours' !

running antutu v5.6.1 now . . . Its so smooth, and it seems ( psychological placebo effect ? ) to be zipping faster.

Score is not around 51k like I thought it "would" be. Hmmm . . . Odd . . .

. . . . mult / runt / cpui / cpuf / sini / sinf / ramo / rams / 2Dgr / 3Dgr / stor / data

(STK) 48846 // 7234 / 4024 / 4030 / 4377 / 3027 / 2679 / 2248 / 2479 / 1632 / 14959 / 1467 / 690

(B.3) 46821 // 6758 / 242 / 4258 / 4506 / 3022 / 2702 / 2331 / 3139 / 1631 / 15560 / 2002 / 670

(2.0) 51028 // 7176 / 3979 / 4194 / 4500 / 3017 / 2682 / 2332 / 3187/ 1633 / 15778 / 1880 / 670

(?.?) 47739 // 6973 / 3844 / 4032 / 3727 / 2970 / 2640 / 2077 / 2963 / 1634 / 14049 / 2125 / 705

(*.*) 46375 // 6367 / 4080 / 4341 / 3121 / 3016 / 2708 / 2068 / 2766 / 1629 / 13761 / 1846 / 675

(DR4) 45102 // 6776 / 3899 / 2161 / 2351 / 2942 / 2679 / 1155 / 3147 / 1631 / 15521 / 2120 / 720

I suppose the storage i/o is more important that the rest at : 2002/1880

Can I install ( solder in ) some galaxy edge "6" memory replacements ?

.

running androbench for the i/o

seqr / seqw / ranr / ranw / sqli / sqlu / sqld / brow / mark / came / camc

(STK) 240 / 69.8 / 16.8 / 16.8 / 347 / 277 / 312 / 40.7 / 125 / 102 / 269

(B.3) 246 / 70.9 / 17.4 / 16.9 / 326 / 298 / 323 / 38.5 / 111 / 104 / 249

(2.0) 246 / 70.9 / 17.1 / 17.1 / 350 / 300 / 314 / 61.0 / 128 / 101 / 233

(?.?) 225 / 66.7 / 16.4 / 15.8 / 329 / 273 / 325 / 34.8 / 114 / 105 / 316

(*.*) 205 / 67.1 / 15.2 / 13.8 / 229 / 256 / 310 / 42.8 / 131 / 118 / 262

(DR4) 221 / 69.8 / 17.1 / 17.0 / 344 / 297 / 295 / 40.0 / 118 / 103 / 264

.

I looked up the andro of four months ago and it appears google did some ( non trivial ) tweaks under the hood. . Swapped the two barrel carb out for a four barrels ? . Took out the gerbil and put in a hamster . . .
[Nexus 6  Original Android Development] michmeister:
Do the sweep features work on newest kernel for 5.1. ? Setup in lkconfig but not working.
[Nexus 6  Original Android Development] magnum870:
Working fine here. I started from scratch when I went to 5.1 if it matters.
[Nexus 6  Original Android Development] old_fart:
I believe something is broken ( for me and my overly large plastic slab ) ! ! ! !

.

I just did a warm boot but it did not. Rather - it is still spinning its little color dots. It is hung. Ah, snap !

.

Holding power to do a cold boot . . . and it came up . . . and its optimizing all 149 apps . . .
[Nexus 6  Original Android Development] michmeister:
Reflashed and sweep gestures working :)
[Nexus 6  Original Android Development] nextelbuddy:
Will you be updating or adding the no force encrypt boot image for 5.1 in a zip format to your onedrive account?
[Nexus 6  Original Android Development] Imoseyon:
hmm that doesn't seem like the kernel. Let me know if it continues to happen though.

You mean for stock kernel? Yeah i'll get to that soon.
[Nexus 6  Original Android Development] nextelbuddy:
Yup you got it, I just like to have a stock option to fall back on. thanks so much!
[Nexus 6  Original Android Development] old_fart:
Umm, . ( just a thought ) . I used the app 'flashify' to backup my original before going to the beta lean.
[Nexus 6  Original Android Development] nextelbuddy:
thanks for the tip ill keep that as an option!
[Nexus 6  Original Android Development] Imoseyon:
Finally had a chance to compare the stock source between 5.0 and 5.1. Some highlights:

1) Most of the new CAF commits in 5.1 were already merged into leanKernel v1.x.

2) The biggest change I see is the move to NEON based instructions for sw encryption, which was also merged into early leanKernel v1.x.

3) Some touchscreen enhancements from motorola.

4) Some changes in charging logic (it should charge to battery full finally) - check to see if we're still having phones shutting down issue at 5% on 5.1?

5) I also see an interesting commit by Google to prevent camera lock-up.
[Nexus 6  Original Android Development] franciscofranco:
It was cool to see the cpu-workqueue patch reverted as well. I blame QC for that.

I know you don't use cpu-boost, but it was interesting to see they disabled the thread migration boost claiming that it causes a big power regression.

I was hoping to see work on VIDC. They worked a bit on the vibrator driver.
[Nexus 6  Original Android Development] Imoseyon:
Yup I had that reverted in leanKernel a few releases ago. :)
[Nexus 6  Original Android Development] eep2378:
I find it interesting that google put some work to improve(kernel and OS) and did quite a bit of bug fixing and smoothing out of the OS overall. But its odd that they shipped 5.1 with new play services that holds systemupdate service wakelock that disallows deep sleep. Unitl I disabled the system update service, now it sleeps like normal.
[Nexus 6  Original Android Development] dmeadows013:
What sort of battery have you guys noticed compared to the stock kernel?
[Nexus 6  Original Android Development] drawde40599:
, u can try this path ( prob won't work )

su

echo 0 > /sys/android_touch/doubletap2wake

Or try this app to disable http://xdaforums.com/nexus-6/themes-apps/doubletap-to-unlock-enabler-t2949218

Neither may work but worth a try .
[Nexus 6  Original Android Development] simms22:
about the same, around 6 hours sot.
[Nexus 6  Original Android Development] dmeadows013:
Hmm nice. Might give it a shot. Can't undervolt too much since my CPU is a 5, but I can do some.
[Nexus 6  Original Android Development] ryude:
I don't think the number effects your ability to undervolt, since the number just tells you what the voltage table is. A PVS 5 can probably undervolt to a PVS 7-8 table easily.
[Nexus 6  Original Android Development] wrinklefree:
I had the same issue with v4. I downgraded to v3 to see if the problem comes back.
[Nexus 6  Original Android Development] bradputt:
anyone with lightflow working on this kernel?

strange that it works on elemental and not on leankernel
[Nexus 6  Original Android Development] simms22:
im a 5 as well
[Nexus 6  Original Android Development] Xileforce:
Me too :( I've found I can UV 24 MV stable. I tried 36mv UV once too but it did end up rebooting after awhile. Hard to say if from the UV though. I keep the 2.9gjz option at normal voltage though.

---------- Post added at 01:14 AM ---------- Previous post was at 01:13 AM ----------

Light flow worked fine for me a few versions ago. Haven't tried it since though.
[Nexus 6  Original Android Development] hsj1906:
I'm having the same issue. I am on beta 4 and mpdecision is off in trickster. Every time I lower the min below 1.7 and apply the change, it jumps back up to 1.7. I didn't have this issue on beta 3. So may go back to b3 or wait for beta 5. [emoji1]

Overall, I am seeing improved battery life by lowering the screen off max. [emoji106]
[Nexus 6  Original Android Development] Pilz:
What's a good app to use for looking max/min frequencies.
[Nexus 6  Original Android Development] Johnny424:
i noticed that too but even though an app won't lock 300 mhz it is actually cycling down to 300 or 223mhz ..
[Nexus 6  Original Android Development] Mistertac:
I use the app System Monitor myself. There's a free version and paid version, I have the paid one but think you'd still be able to see what you want with free version.

You can have a widget that shows what your cpus are currently doing during various tasks and the widget stays on top of any open windows.

Although my current font I have makes it harder to see, you catch my drift right.. Now on to another font...
[Nexus 6  Original Android Development] Pilz:
I was using trickster, but my min freq 233mhz wasn't sticking for that long. I tried using elementalX but I have the same issue with frequencies not sticking. MPDecision is off in the elemental app.
[Nexus 6  Original Android Development] zephiK:
Light flow works perfectly fine here. Followed all of the instructions from the developer
[Nexus 6  Original Android Development] Mistertac:
Whenever I try to turn mpdecision off using Trickster my CPUs go completely wonky according to System Monitor. I've ended up just leaving it on, and by looking at Trickster and System monitor after a days use, I can still see that my Min/Max have stuck and I can also see that using the live Widget.

I'm not sure myself what is really going on. I have latest SuperSu beta and SeLinux is Permissive as well. Not sure if any of that matters.
[Nexus 6  Original Android Development] Pilz:
I'm having the same issue as you. I think/hope this will be fixed in the next kernel update. My min freq still does like to stick despite trying different things.
[Nexus 6  Original Android Development] Mistertac:
I'm sure what some of us are experiencing will be fixed along the way. It's still so new in the way of development for the Shamu.

As long as I can see that my min/max are actually sticking, I'm just fine. I'm not a Benchmarker and don't really care if mpdecision is on or off. Just that I'm getting great performance and battery life which I am.

I've never gotten better battery life than with this Kernel and on Slim. So I'm good!
[Nexus 6  Original Android Development] Pilz:
I just want better standby and battery life when possible. Its been slightly better for me, not a huge amount but enough to make it worth while. I will benchmark my phone for fun every now and then, but I keep my settings average for daily use.
[Nexus 6  Original Android Development] zephiK:
I was having the same problem but went to /system/bin/ and renamed (or deleted) mpdecision.. rebooted.. and then the freqs were playing nice with the settings i set in place.

Standby for me has been amazing even on stock kernel. Mpdecision is really bad when it comes to bumping CPU Frequencies to high frequencies when you're doing a simple task and sits on that frequency for a period of time which attributes to warmer temperatures and a waste of resources at that cpu frequency. Definitely a big tradeoff for the smooth animations/scrolling. Can't wait for mpdecision replacements to be implemented for N6.
[Nexus 6  Original Android Development] oak:
I no longer have the wakelock on 5.1.
[Nexus 6  Original Android Development] eep2378:
Hmm. Weird
[Nexus 6  Original Android Development] old_fart:
Same here.

I am doing a ratio of 86 percent "deep" sleep and 14 percent not . Hmmm, why is it NOT in the nineties ? ? ?

WLD says : Google play store and Google App ( hello ? ) and hangouts are keeping it awake .. .. .. ( for me )

.

When GSam Battery Monitor companion tried to reboot . . . it could not... and again and again ... not able. Android was tossing complaints too

---------- Post added at 10:33 AM ---------- Previous post was at 10:19 AM ----------

Mr [MENTION=3357040]Imoseyon[/MENTION], sir . . . I was going to go try/plug in Mr [MENTION=3292224]franciscofranco[/MENTION]'s R20 and compare. Do I need to fetch and run the kernel clean utility that you mad a couple months back to reset the other kernel's changes and ramdisk ? ? ?
[Nexus 6  Original Android Development] Franzie3:
Hey guys I think I'm in wakelock hell....any thoughts?? The phone is going to deep sleep but I can't pinpoint exactly what's going on...
[Nexus 6  Original Android Development] jnralp00:
I'm getting the same thing... Over and over. It'll go to optimize apps and reboot when it goes to start apps and keep doing it over and over. Has to restore backup.
[Nexus 6  Original Android Development] nextelbuddy:
OK So I flashed 5.1 no problem... also dflashed the stock no encrypt kernel as well. once I booted up clean then i rebooted into Recovery and installed the 1.17 OC/UC zip which was fine. Then i booted up and got the "android is upgrading" and it keeps looping through this.. it has rebooted 5 times after optimizing 186 apps. so annoying.

i booted into recovery and fixed permissions and cleared dalvik and cache and rebooted. ... same thing.. boot loop after optimizing 186 apps.

booted into recovery and flashed the stock no encrypt kernel and booted up device.. optimized 186 apps and then booted up no problem..

is there something wrong with 1.17 oc/uc?
[Nexus 6  Original Android Development] datajosh:
1.17 is not compatible with 5.1
[Nexus 6  Original Android Development] Imoseyon:
Oh man you guys. Do not flash leanKernel v1.x on Android 5.1. That's what v2.0b testbuilds are for. I'll try to release v2.0 tonight since I'm going away for the weekend.
[Nexus 6  Original Android Development] nextelbuddy:
man i feel really dumb... i coudl have sworn i saw somewhere in this thread that 1.17 was updated for 5.1 which is why i asked earlier when we were going to get 5.1 stock no encrypt kernel lol..

my bad guys. ill wait for the oc/uc builds.. i LOVE that build very much.
[Nexus 6  Original Android Development] GPS3:
Can't wait for a 2.0 uc/oc stable release :good:
[Nexus 6  Original Android Development] derekr44:
Sometimes being on the bleeding edge... really bleeds... :D
[Nexus 6  Original Android Development] owyheendn:
What would be better for getting the most out of my battery? The stable build or the Oc/Uc build??
[Nexus 6  Original Android Development] wrongway213:
Stable, undervolting is generally not necessary for an average user and OC is obviously not good for battery.
[Nexus 6  Original Android Development] owyheendn:
Thanx, yeah I'm not to Familiar with Tweaking Kernels
[Nexus 6  Original Android Development] Imoseyon:
v2.0 is up. Lollipop 5.1 (lmy47d) only!

Should be very close to v1.17 feature wise. Just merged in the android 5.1 source and made a bunch of tweaks/adjustments for full 5.1 compatibility. I removed lkconfig core control stuff for now (I may bring it back later), but added a simple option to enable/disable mpdecision.

Full changelog: https://github.com/imoseyon/leanKernel-shamu/wiki/Lollipop-ChangeLog

Oh, someone wanted stock lmy47d kernel too so I put that up as well.

(Hope no major bug is found - I'm gonna be out of town for the next two days. :))
[Nexus 6  Original Android Development] Mervingio:
Thank You Sir!
[Nexus 6  Original Android Development] smclaughlin3:
Hi imoseyon can you out the volte icon when the phone is on it I remember you doing that from my note 3 days