yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] freddienux:
gotcha

and flash it like normal rom? cant wait to flash wit lean kernel

---------- Post added at 04:42 PM ---------- Previous post was at 04:40 PM ----------

just notice your in brooklyn? thats where i, from lol. was there yesterday. im a jersey and brooklyn boy lol
[Nexus 6  Original Android Development] sn0warmy:
OP, I didn't see it posted in the "features" list... Does this kernel allow for display color tweaking (such as ARGB and Gamma)?
[Nexus 6  Original Android Development] wrinklefree:
Does not appear so
[Nexus 6  Original Android Development] Imoseyon:
Not yet. I have color control code in all of my samsung device kernels, but shamu is very different. This may take me a while.
[Nexus 6  Original Android Development] zephiK:
Flashed over the stock unencrypted kernel, going to give this a try. I had to flash SuperSU after flashing the kernel since su binary disappeared.
[Nexus 6  Original Android Development] freddienux:
the last test build is working great wit stock rom
[Nexus 6  Original Android Development] simms22:
yup. and with rastapop and frankened aosp as well(both officially unreleased right now) :)
[Nexus 6  Original Android Development] old_fart:
I understand, thanks ! . . . Hmmm, it's my ( fossil ) brain telling me the device should do its natural thing of auto sweeping down through all the freqs possible. . but to MAX your bench score, then temporarily place it in a ( bogus ) freq state . . . I guess there is a bench number and a max_max_bogus bench number and they're both right. I was ( trying to be helpful ) and telling the kernel cooker about the way the freqs laid out. . .

.

My lastest score with normal beta 5 is : 49986 . . . and the trickster says it was mostly staying at 2649 mhz and not folding back too much . . . fwiw.

.

and another fwiw . . . Androbench ( which jumps around - surprise, surprise ), ran seven times, so these are low high

239 - 254 , 67.7 - 85.5 , 22.5 - 24.9 , 7.54 - 8.45 , 271 - 333 , 324 - 359 , 327 - 369 , 16.5 - 21.2 , 37.2 - 41.7 , 27.0 - 30.5 , 62.7 - 67.7

( greenify is being ran in between "all" the runs )

.

3D Mark - Ice Storm Unlimited : 23767 . . Seriously, what the hell ? . The apple 6+ is only 17851, so we're thirty three percent better than the best yuppie ( entitlement ) device ? ? ?

Epic Citadel average fps : 58.6 . . . at res. 2516x X 1440.
[Nexus 6  Original Android Development] simms22:
yup, it happens. the first i used antutu on my n6, i watched the cpu speed as it was going through(with perfmon), and it rarely went to 2649, only around the first few tests and at 31%. besides that, it spent a lot of time under 2ghz.
[Nexus 6  Original Android Development] ryude:
I'm using ondemand, but adjusted the up_threshold to 65 from 95. It helped ramp up the clocks during benchmarks and other tasks. The default threshold of 95 is way too high.
[Nexus 6  Original Android Development] simms22:
i use 98, specially for the performance impact, always have :angel:
[Nexus 6  Original Android Development] ryude:
Here is my clockstates, as you can see it doesn't go very high even with 65 up_threshold.

Here is my battery life, I rebooted the phone a few times and flashed stuff.
[Nexus 6  Original Android Development] clothednblack:
Update: I went into Google play services, opened up change permissions and toggled off the location toggle, let the phone sit for about 30 minutes and now the "stuck gps icon" is finally gone.

Edit: sorry, wrong thread, but I'll leave it here Incase someone else has the stuck icon

Posted from a Nexus 6 running Slim Rom
[Nexus 6  Original Android Development] ryude:
I haven't had any problems with the icon sticking, but that's good to know if it does.

:good:
[Nexus 6  Original Android Development] simms22:
right, wonderful battery life. the difference is how we use the phone, and our habits. im a very heavy user, and like the phone at maximum performance at all times. this way, it ramps up, and ramps down, much quicker. oh, and i get the same battery as you, about 6 hours sot to about 7 hours 15 min sot(less if im testing/benchmarking at 2880/2880). but i only last about 12-15 hours usually.
[Nexus 6  Original Android Development] ryude:
You misunderstand.

Up_threshold is the load at which it steps up to the next clock speed.

98 would mean 98% load. That would actually mean the phone stays at low frequencies more often and hurts performance.
[Nexus 6  Original Android Development] simms22:
maybe i said it wrong? i think i said it right. this is from what you yourself quoted above..

and this is exactly what i want. when i want performance, i get it right away. it doesnt waste time stopping at other cpu speeds. and when i dont need it, it stays low. because it doesnt waste time at other cpu speeds, and is faster. in theory its saving battery, and giving me the performance i want :)
[Nexus 6  Original Android Development] cheami:
If it is at 98, then it will not speed up the clock until at 98% load. As in you made it more difficult for the CPU to clock at max frequency, from default of 95.
[Nexus 6  Original Android Development] simms22:
it wont bump up until its needed. at that point it bumps up asap. again, look at my cpu stats right above your post. if it behaved like both of you are trying to explain that it does, my cpu speeds would be everywhere but at the max cpu speed(more lower than higher).
[Nexus 6  Original Android Development] Nal Rodriguez:
Im trying to flash the kernel on my nex , I do everything but when i check the kernel name its still the same stock one. Yes its unlocked, yes it has a custom recovery and is decrypted. Any ideas ?
[Nexus 6  Original Android Development] simms22:
look in /proc/version/ with a root file explorer. whats it say?
[Nexus 6  Original Android Development] nalrodriguez:
the google kernel if I'm not wrong
[Nexus 6  Original Android Development] simms22:
it is. what recovery are you using? twrp i assume, as i know no other for the n6. have you tried redownloading it, then reflashing?
[Nexus 6  Original Android Development] nalrodriguez:
Yes , ive tried Stock-mpdecision, and no-minfreq-mpdecision. I havent tried any of the beta ones.

Edit: going to flash the real kernels now, haha thanks
[Nexus 6  Original Android Development] akellar:
Those aren't kernels
[Nexus 6  Original Android Development] lainemac:
Hey imo, have you ever thought about adding BFS to your kernel? I've tried zen which incorporates this and it's very smooth.
[Nexus 6  Original Android Development] bradld:
I wasn't able to get past it either....is there a fix?
[Nexus 6  Original Android Development] TCMuffin:
I wasn't able to boot past the animation with the official CM12.1 either :(
[Nexus 6  Original Android Development] LostSol:
Same here.
[Nexus 6  Original Android Development] rignfool:
OK... The is by no means fact... Just my experience/usage...

When I am on WiFi... The NLP wakelocks trigger less... My assumption... I can only go so far from WiFi... So if I'm connected... You know where I am...

When I am on mobile data... The NLP wakelocks trigger once a minute... For like 10 seconds... To make sure it really knows where I am...
[Nexus 6  Original Android Development] Imoseyon:
I'll be working on this tonight/tomorrow! Don't worry guys - it will be fixed.
[Nexus 6  Original Android Development] elkay:
I'm not on this kernel yet, but really want to be. Just the wakelocks making me twitch a little. I was the dev that worked on the msm_hsic wakelocks on the DNA way back in the day. I know the pain. I tossed you a donation of a few beers.
[Nexus 6  Original Android Development] Imoseyon:
Those of you on official CM12.1 nightly, try v2.6.1 here: http://renderserver.net/devs/imoseyon/shamu/testbuilds/lk_shamu_lp-v2.6.1.zip

Let me know how it goes!
[Nexus 6  Original Android Development] Steady Hawkin:
I agree, BFS scheduler is absolutely worth a look. Would love to have it on lk :D
[Nexus 6  Original Android Development] coldconfession13:
2.6.1 booted up for me
[Nexus 6  Original Android Development] TCMuffin:
Thank you :) I'll try now...sorry in out of "Thanks", but will thank you tomorrow :good:

---------- Post added at 09:03 AM ---------- Previous post was at 08:41 AM ----------

Thank you...v2.6.1 boots with cm-12.1-20150420-NIGHTLY-shamu.zip :good:
[Nexus 6  Original Android Development] old_fart:
Thanks for sharing, yikes ! ( re: "once a minute" ) , so it just 'does what it does' and there is no way to dial it back and tell it to not be so aggressive ? Hmmm, so it know when you're walking over to the copier machine to send a fax and when you're going over to the head to take a leak . . .
[Nexus 6  Original Android Development] supercluver:
The Xposed module Amplify allowed you to control the frequency. Default setting was 240 seconds instead of 60, but you had full control. Unfortunately Amplify doesn't work with 5.1 (and still requires Xposed which some people aren't okay with installing).
[Nexus 6  Original Android Development] rignfool:
The other alternative is a ROM with the wake lock blocker... And just block that...

Also... If you revoke the google services location thing... Or... If you switch your location thingy to device only...

EDIT: people have reported better battery life by using GPS and forced intervals
[Nexus 6  Original Android Development] xtzz:
2.6.2 working fine on cm12.1-nightlies.
[Nexus 6  Original Android Development] jkc120:
Working great on stock rooted as well. Feels snappier than 2.6 as well, though that could be placebo. :)
[Nexus 6  Original Android Development] mjohnson4580:
What changed from 2.6.1 to 2.6.2?
[Nexus 6  Original Android Development] lainemac:
+1
[Nexus 6  Original Android Development] BennyJr:
Vtec kicked in
[Nexus 6  Original Android Development] Pedro Peguero Jr.:
Hey All,

I'm planning on picking up an N6 in two weeks. I heard the screen is a bit warm (possibly pinkish). Can a kernel like this fix that issue? Like screen profiles and tweaks, etc? Or is it mainly hardware.
[Nexus 6  Original Android Development] ac3theone:
Yes
[Nexus 6  Original Android Development] Pedro Peguero Jr.:
So it does fix the pink issues? I thought it was hardware :o
[Nexus 6  Original Android Development] ac3theone:
It does, this and many other kernel's allow you yo change the screen color to your liking
[Nexus 6  Original Android Development] jkc120:
If you're referring to the pink tint at low brightness levels, that is normal and only happens with adaptive brightness enabled.
[Nexus 6  Original Android Development] M@XLOL:
Edit. Disregard.
[Nexus 6  Original Android Development] :
LK v2.6.2 + AICP 4-21 + Viper= :sly::thumbup: Tks imo !!
[Nexus 6  Original Android Development] Imoseyon:
v2.6.2 is a test build, so I don't really have an official changelog, but it's essentially 2.6.1 + linux and interactive updates.
[Nexus 6  Original Android Development] Steady Hawkin:
Just got your message on Pushbullet in regards to the BFS CPU scheduler (thanks for the inquiry). While there is probably very little I could do personally to sway your opinion, I'll at least give you my $.02. For starters, [MENTION=2632235]bbedward[/MENTION] has allot of very useful information about it posted in the OP of his zen kernel thread, which includes details on his specific implementation of it. Since his initial release, more than a few Nexus 6 kernels have decided to jump on the BFS bandwagon. Is it possible it's a Placebo effect? Sure. However, from my own personal user experience, it's absolutely worth the price of admission. If I remember correctly, in the past you have said that most kernel changes will only equate to small, subtle, end-user differences (horrible paraphrase), but this one feels pretty big. Both you and bbedward like to keep things pretty close to stock, and from my own experience, something about it feels noticeably different. Anyway, sorry for the rant, I've been following you long enough to trust your judgement, I just really think it's worth a look :D
[Nexus 6  Original Android Development] :
Just updated rom I'm currently using (AICP) from 4/21----> 4/23 and its now Android 5.1.1, dirty flashed with LK 2.6.2 and all systems go. [MENTION=3863530]Steady Hawkin[/MENTION] Haven't seen you in ages on here!! Cool deal man!! Gunslinger days!! \m/
[Nexus 6  Original Android Development] akellar:
No idea if BFS is good or not but this is a terrible reason to add something to a rom or kernel. There are way too many "devs" that just add everything they can find without knowing what they do or the benefits of them. That doesn't make the kernel or rom better necessarily. /rant
[Nexus 6  Original Android Development] Imoseyon:
BFS, in my experience with other devices/kernels in the past, have not made a significant difference one way or another. Is there something unique about shamu that is a lot more friendly to BFS? Perhaps but I kinda doubt it.

I think what's more likely is that I (or CAF or Google) may have potentially introduced a change to CFS that possibly could have contributed to a different kind of user experience which becomes noticeable when you go to a different scheduler. If there's anyone that can reproduce this at all - I wouldn't mind reverting a few recent commits to see if there's a difference. There's really no reason why CFS can't match the performance of BFS.
[Nexus 6  Original Android Development] goila:
Hello. I really like your kernel. could you be an up-to-date build make on 5.0.2? many thanks
[Nexus 6  Original Android Development] Steady Hawkin:
Going to ping [MENTION=2632235]bbedward[/MENTION] since he's much better versed than myself.
[Nexus 6  Original Android Development] purian23:
5.1.1 AOSP Source is out haha. What's holding you back? It really was a great upgrade going to 5.1 alone.
[Nexus 6  Original Android Development] goila:
xposed...
[Nexus 6  Original Android Development] purian23:
Is holding you back :) No it's cool, I was curious. Looks like it'll take some time to make Xposed up to par on 5.1.1
[Nexus 6  Original Android Development] lainemac:
I personally have tried both zen and lean and it seems the UI is more constantly smooth with zen. I don't know if it's directly because of BFS because I'm not a kernel and dev and wouldn't know how to differentiate anything else. But yeah, to me BFS seems more buttery.
[Nexus 6  Original Android Development] Xileforce:
Good to know you're not a kernel, that would have worried me. :)
[Nexus 6  Original Android Development] Imoseyon:
This is more likely due to governor changes than cpu scheduler change. Keep in mind that interactiveX is not optimized for speed by default. Do me a favor and try this test:

1) On BFS kernel, set both min and max freq to same (ie. 2.2ghz). Do the same for GPU if you can. Run it for a while.

2) On leanKernel, do the same as above. See if you notice any UI speed difference.
[Nexus 6  Original Android Development] rignfool:
Fwiw:

I ran your kernel for a long time... In a similar fashion to the way I am running hellscore (it uses BFS instead of CFS)

The biggest difference I see... Is that I can run the processor at a much lower speed without ui degradation...

I'm only running a 1.7 max where with your kernel I ran it at 2.2 because any lower would cause stuttering in thing like Tapatalk when it came to scrolling

Again... No scientific evidence... Just my user experience
[Nexus 6  Original Android Development] Imoseyon:
Ah that sounds like it's either the governor or mpdecision, and not cpu scheduler. You probably had minfreq raise disabled via lkconfig (or mpdecision)? Again, the best way to take governor and mpdecision out of equation is to set both min/max the same. Then you can judge better whether the cpu scheduler is making a difference or not.
[Nexus 6  Original Android Development] BlueHarford:
Disabling the gov and mp will not tell you if it's the scheduler. The scheduler effects both of those. Set the same govs and same min and max and use different schedulers that's how u can see the difference.

I've ran both kernels in question and francos. Zen just run s better and not because I'm friends with bbedward. It's just because that's how it is. It's very very apparent the differences. With that said if lk doesn't want to use it who cares, use both.. Which ever once feels better to you.. Use that one. It would suck if all kernels were the same. No one would have choices. We'd just be picking based on the name that shows up in the status menu
[Nexus 6  Original Android Development] knitler:
Your logic is flawed. If you disable mp and give and still have an issue then it must be the scheduler. If there is no issue the its the gov, mp, or the schedulers effect on one of them. He's using process of elimination. You know, good troubleshooting.
[Nexus 6  Original Android Development] vspike915:
Question regarding "ideal" settings

Hey guys, sorry to be so "noobish" with this question but its been a while since i've poked around these types of things (better part of a year with an iPhone *shudders*) But awesome work on this kernel! I'm running Chroma ROM in conjunction with this kernel and battery life after a few days hasn't really seen an improvement. I'm a heavy user with alot of SOT and I used Trickster to Under volt -50 but that hasn't really helped much. Are there any quick tips or tricks for this kernel to prolong battery life as a whole? Thanks guys, can't wait to donate when my paycheck comes through next week you guys are awesome!!!!
[Nexus 6  Original Android Development] Xileforce:
Check your wakelocks, if you have one causing issues and its one of the ones lean allows disabling you can disable it or reduce it to save batt :) you could also try different governors and tweak your max CPU frequency.
[Nexus 6  Original Android Development] vspike915:
I just installed Greenify, seemingly Play Music, FaceBook & Showbox we're some big culprits. Do yuu have any personal recommendation on a certain governor/max CPU?
[Nexus 6  Original Android Development] Imoseyon:
Yup that's all it is. You want to make the conditions the same between kernels to determine where the difference is. Once you eliminate governor and mpdecision, then you can somewhat conclude that cpu scheduler could possibly be the next one in line. It's not completely conclusive but it's closer. You want apples to apples comparison, and not oranges to apples.
[Nexus 6  Original Android Development] Xileforce:
Personally I run default frequencies, but I've gone as low as like 800mhz before without getting lag. So if you want battery maybe 1.7 max could be a good compromise. Can always raise it if u hit lag.
[Nexus 6  Original Android Development] Chochiwpg:
If I wanted to flash back to the stock factory image kernel can i just flash the boot.img from the factory image in fastboot or do I have to flash anything else?

Usually I think it's just boot.img but just wanted to know if system or anything else needs to be flashed thanks.
[Nexus 6  Original Android Development] Smallsmx3:
Boot.IMG will do it

---------- Post added at 11:19 AM ---------- Previous post was at 11:16 AM ----------

So if your a heavy use and you get a lot of SOT then your pob getting pretty good battery life. I don't think you'll squeeze anything more substantial. It doesn't matter what set up I use on any nexus device. I top out at about 3 hours SOT. The idle on this phone is pretty good so I don't worry about running out of juice.
[Nexus 6  Original Android Development] jkc120:
Does A2DP/AVRCP 1.3 work for others? I just noticed today in a Chevy Traverse that on BT audio with google play music it doesn't show the track / artist name nor the time for the song. I'm not sure it's a LK issue, it could be the same way on stock but something I noticed.
[Nexus 6  Original Android Development] akellar:
Definitely not kernel related but it works fine with pandora in my mazda
[Nexus 6  Original Android Development] jkc120:
Just tried with Pandora in my 2013 Chevy Traverse and it didn't work with that either. I went to the BT settings for that pairing and it just shows phone audio, media audio and contact sharing all of which are checked. The HUD shows the batter and signal levels, too on the car. But no metadata :/
[Nexus 6  Original Android Development] iifuzz:
Will this kernel boost my in call audio? So hard to hear ppl
[Nexus 6  Original Android Development] rignfool:
You should look in your dialer settings for hearing aid compatibility or something like that... That will boost volume
[Nexus 6  Original Android Development] iifuzz:
If that works,I will sex you up
[Nexus 6  Original Android Development] rignfool:
Is this where I respond with...

Doesn't matter... Had sex...

?
[Nexus 6  Original Android Development] Vanhoud:
Is it normal that core 1,2,3 stay pegged at max freq?
[Nexus 6  Original Android Development] jkc120:
I doubt it. Post your lk settings and usage/relevant info.
[Nexus 6  Original Android Development] Franzie3:
hey [MENTION=3357040]Imoseyon[/MENTION]. I'm running Chroma with the included franco kernel on my last build and before that I always flashed over LK. I am seeing an issue while using FK that I never saw when using LK. Want to pass it by you and get your opinion. Every so often I get the half frozen screen issue where within an app or anywhere half the screen freezes solid (right side) and the other side (left side) stutters to scroll and when going home the frozen part of the screen remains drawn. Normally a lock and unlock of the phone resolves it but if it happens one to many times I end up rebooting. When that happens the reboot fails and i'm stuck in the boot animation. Another hard reboot and it boots fine but it now is going through the App Optimization again.

My question is if there might be a commit somewhere that you have that franco may not (i'm sure there are multiple). The only difference i can really tell is that the governor you use is interactiveX vs the one included in chroma uses franco and conservative. Could the governor be part of the issue? Just curious.
[Nexus 6  Original Android Development] moopile:
[MENTION=3357040]Imoseyon[/MENTION]

+1 Same here. When running Chroma with Franco I get constant 1/2 screen freezes (several times per hour of use). With LK I rarely get them. I know in the past Franco has said it was either a Motorola or Google problem with the graphic drivers (iirc) and would require a fix from them. I use your kernel because it seems to really help with the problem. I know I ran Terminus for a couple of weeks and I think he uses stock kernel and I rarely got them while using his rom, but when I was on Stock 5.0 I got them several times per day.

Keep up the great work !!!!!
[Nexus 6  Original Android Development] crzycrkr:
Yeah, Chroma is unusable for me with Franco. I'm using Hydra right now, but going to try out LK soon. Are you both changing DPI? Seems to be where the issue is most noticeable
[Nexus 6  Original Android Development] Franzie3:
I had it changed but switched back. i usually only see it in the mornings when im closer to 100% battery or coming right off the charger, i dont see it much, if at all, during the day
[Nexus 6  Original Android Development] crzycrkr:
I see it more in certain apps, especially when scrolling. Time of day doesn't seem to affect me
[Nexus 6  Original Android Development] waqar.qu:
+1
[Nexus 6  Original Android Development] moopile:
Stock dpi for me.
[Nexus 6  Original Android Development] Imoseyon:
I have heard that somehow my kernel fixes the half screen freezes that the others suffer from. Honestly I'm not sure which one of my commits fixes it - it could be a needle in a haystack at this point. Trust me, if I knew it I would tell others - I definitely don't mind sharing. :)
[Nexus 6  Original Android Development] numerouknow:
needless to say. :)

people who've been around for a while and have seen you and franco exchange views will know better.
[Nexus 6  Original Android Development] akellar:
To be fair it doesn't really fix it, just makes it occur less often than on other kernels. I would almost lean on it being something the others include that you don't but idk.