yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] salahmed:
Do you use multi ROM?

Sent from my Nexus 5
[Nexus 5 Original Android Development] Berget:
no. but i just found out what i did wrong ;) i downloaded from the "stabel downloads" - so got the wrong kernel.

i have now downloaded the 1077 and it works fine :)

do this kernel improve battery life?
[Nexus 5 Original Android Development] Citizen_Snips:
eng.stk, thanks for the kernel! Extremely smooth on L developer preview. I think I remember you from the GNex forums back in the day too.
[Nexus 5 Original Android Development] simondva:
Color control

Hi guys, I'm thinking about flashing Android L on my nexus 5, but the main thing I can't stand about my phone is the washed out colors... On Kit Kat, I use Franco Kernel + Franco Kernel Updater (App) for changing the stock colors to Vomer Amoled.. Have any of you have been able to change the colors of the screen in L using this kernel with FKU or any other app? And how about the bugs? How stable is this developer preview? Thanks in advance, I can't wait to experience the material design!
[Nexus 5 Original Android Development] kevtrysmoddin:
I have been using L preview since it dropped and this kernel coupled with it is awesome check the android L bug thread for bugs there's not many and you can tweak the colours with fku or the display tester app myself I prefer trueRGB v7
[Nexus 5 Original Android Development] Berget:
is it only my phone who like overheats with this kernel?

i am running the Wifi tether router app and the phone is getting very hot (more then with the stock kernel) and then the cpu locks in at 1190400 (min ) and 147600 (max)

:(
[Nexus 5 Original Android Development] nman17:
Bug: Problem with Camera!

So, my camera app and every other camera crashes every time I take a picture, unless the picture is taken with the HDR mode in the Google camera app. I'm using the 1066 build, with Android L. Is this a known issue with this kernel, cause I remember that this didn't occur in the stock Android L. And if this is a common issue is there a solution for this?

P.s. your kernel made Android L ****ing smooth and so stable. I barely have any other bugs other than this camera one! Thanks for all the hard work!
[Nexus 5 Original Android Development] Tylog:
New Preview of AndroidL is available

LPV81C

https://plus.google.com/106886406279606937520/posts/jNpSPmjXWJG

Flashable zip, credtis go to Tasssadar

http://xdaforums.com/showpost.php?p=54678947&postcount=1593

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] llevo3:
will r1077-L work with LPV81C?
[Nexus 5 Original Android Development] paychex:
should... try it. I'm going to work in an hour so I'm not flashing it till tomorrow
[Nexus 5 Original Android Development] Tylog:
I have not look at the code of the new preview , i am not at home but i think yes. Do not think much has changed in the kernel.

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] eng.stk:
It's the same kernel, it works ;)

New Code_Blue build later this night or tomorrow.

Nice, but it seems no fixes found, it like Google says:

Android L is so nice. Now play with this broken builds lol
[Nexus 5 Original Android Development] eng.stk:
Code_Blue r1080-L

Hey guys!

Just pushed new release, perfect pair for today's L-preview release by Google.

Some good performance and battery tweaks, enjoy :highfive:

Get involved, test, play, donate, help, contribute.

You keep the spirit alive! ﻿

Changelog:

Keep it real, keep it true, keep it BLUE.﻿
[Nexus 5 Original Android Development] CriGio:
Great kernel!

P.S. Sorry for the intrusion, but the law is equal for everyone; you are occurred in the hottix's because he forgotten a simple thanks (credit) but I don' see your thanks to flar2, why? ;)

P.P.S: your message in the hottix's thread hasn't been deleted; I hope that my not be deleted, otherwise it would be really sad :( I would just like an explanation, thank you ...
[Nexus 5 Original Android Development] eng.stk:
Sure. You are welcome to talk here mate, I don't hide behind mods.

We are talking about different things: in OP I thank dev's that inspire me, helped me and people in general that are important to me.

On the other hand, you will see that any driver or code taken from other person is clearly stated (most wannabes in xda just put the feature like they invented the thing lol)

For last, any commit I use from flar2 (or any other dev), even if I can't use original one, I state clearly the original commiter and source.

That's the thing. The law for me is simple: I could never use somebody's else work and call it my own.

And by the way I didn't ask about credits in OP or he to praise me.

I just asked for him to make the commits with at least a comment to the original source.

Go in peace.
[Nexus 5 Original Android Development] marf28101995:
Wtf dude ?you're talking to a recognized XDA developer .. You're talking about hours of work and you talking like it was nothing

The developer of this kernel always give the credits to the one who deserve it unlike some other devs here at XDA that post like they are the creators

Think before post

Read before post
[Nexus 5 Original Android Development] Dragusdrake:
If help you

For me 1066 works better than 1077
[Nexus 5 Original Android Development] tomzefi:
What about 1080? Have you tried it? I think its better than both.
[Nexus 5 Original Android Development] ekowanz:
Latest kernel.. Theres no option on tcp.. Previous kernel is westwood rite? Now theres nothing

Im sorry.. Its there now, just have to restart it
[Nexus 5 Original Android Development] tomzefi:
Haha haha its cool. Running good here so far
[Nexus 5 Original Android Development] eng.stk:
No it isn't. What happens is that Trickster doesn't refresh frequency for 3 or 5 seconds and it seem slike it's stuck.

If you swipe right or left real quick it's going to show different min/max freqs, this is a Trickster issue.

This kernel has cpu-boost which spikes freqs for awhile in order to smooth things. All the freqs changed momentarily come back to normal after a few milliseconds.

You're probably using Trickter right? It needs to be updated. Faux sound seems to be working just like on KK, I don't use apps just scripts.

And I don't use faux sound alot so...

Let's not forget this beta stuff, most thing will be nneded to be updated for L, like always is ;)

Nope... upstream mainly patches x86 stuff and I want to keep kernel clean and close to stock as possible.

Even more now since this is beta stuff and will change for sure in future.

Nope.
[Nexus 5 Original Android Development] dialmformostyn:
Flashed earlier, runs very smooth and the phone stays noticeably cooler. Screen colours are lovely - only downside is that it makes my tablet look yellow in comparison.
[Nexus 5 Original Android Development] Koopa777:
I saw SOC Thermal is disabled, is there some type of custom Thermal enabled(Franco, your own, etc.)? Just wondering. Also, noticably smoother, Android L is now even more buttery. :good:
[Nexus 5 Original Android Development] eng.stk:
Well thermal is pure stock, I didn't change anything.

I'm debating about merging custom hotplug, and thermal because idk if it will do something to project volta and battery saving mode.

But I'm getting good bat life so...

More 400 dls in less than 4 hours, massive!

BTW guys don't forget to rate thread and tip xda, maybe I'll hit xda portal :victory:
[Nexus 5 Original Android Development] paychex:
Turn off thermal throttling and I bet it will stick. Stock throttling is low, but I would still suggest leaving it enabled

---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------

How can you not hit the portal with the first custom kernel on L? Thanks btw!!
[Nexus 5 Original Android Development] ChrisJ951:
Awesome, thanks for making an L-Preview Kernel.

I see it says:

Gamma Control by [MENTION=4152171]myfluxi[/MENTION], improved (apply without turning off screen, Piereligio_TrueRGBv6.6 profile by default)

Do you know of any apps to control the colors for other profiles? I tried Franco's Display control but it doesn't run correctly (it works with ElementalX but you lose the baseband when doing that)

EDIT:

So it seems it just took a few minutes for the colors to switch (screen refresh maybe?) The app doesn't work but it at least seems like the Piereligio_TrueRGBv6.6 profile is working.
[Nexus 5 Original Android Development] eng.stk:
Works fine for me, gamma is applied instantly...
[Nexus 5 Original Android Development] Angel0fDeath:
I'm gonna try this. Thanks for this awesome kernel!
[Nexus 5 Original Android Development] yoyoz808:
Does this work with multirom?
[Nexus 5 Original Android Development] dlsygaco:
Finally i can boot other kitkat roms! Finally. The best smoothest kernel now on L :D
[Nexus 5 Original Android Development] pbr2:
The feature list in OP mentions kexec support, so yes.
[Nexus 5 Original Android Development] chachin:
what does it mean dirty flash rom? just reflash it or what? cause I'm stuck on the google with the unlocked lock for a while now and nothing is happening
[Nexus 5 Original Android Development] KennyDumah:
How do i increase the speaker volume?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] dlsygaco:
Booting other roms doesnt work
[Nexus 5 Original Android Development] crookdbill:
Thanks! Flashing now.
[Nexus 5 Original Android Development] Kaemo:
Dirty flashing is when you flash a ROM on top of another one without wiping the system and factory resetting.
[Nexus 5 Original Android Development] Blaze420916:
Do you have a link to this app
[Nexus 5 Original Android Development] ONeVmaniac:
After couple hours of testing I have to say - superb job ! Works smoothly and fast .Phone sleeps well in 300mhz ,no problems at all. By the way i dont know how is it related but after flashing your kernel google now hotword detection works on every screen now finally;D Thank you man!
[Nexus 5 Original Android Development] CrashOverride1995:
Can anyone please provide a stock kernel of Android L as a flashable zip. Just in case someone wants to go back.
[Nexus 5 Original Android Development] rpmfc36:
Just reflash the stock ROM.

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 5 Original Android Development] ferro123:
flashed with fastboot, for now seems ok!
[Nexus 5 Original Android Development] nexusmaniac:
For some reason my CPU is pinned at 2265MHz with 1080 on the latest L update. :( I'll try a reflash but it wasn't immediate and there are no processes running that are hogging the CPU

Edit: Reboot fixed this problem...

Now there is a new one: I noticed that the cores become active/inactive very frequently, I was doing nothing except for looking at the system monitor and cores were coming online like crazy! Flicking between 300+ up to 2.3GHz :(

Not sure what the problem is but I've never seen this before 1080
[Nexus 5 Original Android Development] eng.stk:
MUst be something wrong there mate, can't reproduce for me it's normal.

Did you clean flashed?
[Nexus 5 Original Android Development] nexusmaniac:
After I clean flagged the new L ROM I flashed 1077 then when you pushed 1080 I just flashed the .zip with twrp.

I've done a reflash with a new download of 1080 and the problem 'seems' to have gone away but I'll keep an eye out, I don't know what went wrong there though :S
[Nexus 5 Original Android Development] Dragusdrake:
I would understand why eng.stk ignore my posts.

I ask for VM values, why new interactive drain less battery then bluactive, i post screenshot of my battery...and? And i got no answer ...

I would help

But not say "test help contribute", and then not considerer ideas
[Nexus 5 Original Android Development] marf28101995:
The default governor is bluactive and it will stay bluactive in the future

The best performance with the best battery life we can get..

So tell me why should him listen your idea if to us the kernel is already perfect
[Nexus 5 Original Android Development] eng.stk:
Mate I replied to several posts from you like 10 before this...

VM an dirty values you can read from kernel, the ones I use are meant to be the best...

Feel free to change them.

The interactive present now is google stock... if you got more battery life with it, use it.

You can use even conservative if it's better for your personal use.

If I was to follow every personal request, I would have to do hundreds of versions.
[Nexus 5 Original Android Development] nexusmaniac:
Hi eng.stk :) I don't know if you've experimented with Fransisco Franco's hotplug settings but they're great for battery life :) could be worth taking a look at for a later version? Ty
[Nexus 5 Original Android Development] Dragusdrake:
You don't say?

I not ask a personal version

By the way with new versions i can't use interactive stock because is not present...

For the VM values, i talk about because from 1066 to 1077 some values changes for example dirties and swappiness or cache pressure.

But if you say that is perfect, they will.

Regards
[Nexus 5 Original Android Development] eng.stk:
You mean using franco hotplug?

Sure, it's on my favorites, along with intelliplug and my favorite msm_hotplug.

But I prefer msm_hotlpug. Serves my purposes and wasn't available in AOSP kernels, I think I was the first to use it out of CAF kernels scene.

Lot's of this questions were debated during Code_Blue cycle of development on the main thread.

Here I just post/use results most of the time.

C'mon dude relax ;)

Those values aren't random, they were heavily tested in various situations and behave for the best on this kernel.

Like everything, it's subject of discussion. But we must give fundamented replies and test concepts so we can all benefit from it.

And of course interactive is present, checkscreen is the first one... I appreciate feedback, but rigorous, ok? ;)
[Nexus 5 Original Android Development] nexusmaniac:
Yeah :) I would love to see code blue with blueactive governor and Franco's hotplug :)
[Nexus 5 Original Android Development] eng.stk:
Not going to happen, sorry.

I'm working now on blu_hotplug based on dyn_hotplug, let's see how it goes ;)
[Nexus 5 Original Android Development] nexusmaniac:
Oh well :P

Nice, I look forward to seeing more blue! ;)
[Nexus 5 Original Android Development] gippy2:
Im sticking with blu .....So looking forward to what comes next....Great work by the way .....:good:

EDIT - Just posted in the wrong thread lol....
[Nexus 5 Original Android Development] myvijay:
Awesome kernel, its great that you have jumped into this when other devs are still waiting for full kernel source.

how do I revert to stock colors ? is there a color profile for that which works with FKU ? couldn't find anything with search on this thread.
[Nexus 5 Original Android Development] eluspo:
Looking for stock L colors as well.
[Nexus 5 Original Android Development] eng.stk:
You can use Color Display or FKU I guess, just check the files at http://192.227.135.147/N5_ColorProfiles/Individual/
[Nexus 5 Original Android Development] toxicbubble:
Hey, I just want to say I love this kernel, the last builds with blueactive have been amazing for me! It looks like it spends less time at 300MHz, but seems to balance out well with good use of the other lower freqs and less time at the top ones. Battery has been stellar, so keep on doing what you're doing, and thank you!!!

Really excited to see blu_hotplug. Got me wondering, can you or anyone else give a brief overview of the philosophies behind each of the hotplug drivers? I followed the Franco thread when he was developing his for the N4 (I think it was?), and as I understand it works on a load average, online a core once a certain threshold is reached and offline when dropping below another threshold.

Can anyone give me any info about how the others work, and how you're thinking of approaching blu_hotplug? I don't really know much about the others and I'm really curious as this interests me a lot.
[Nexus 5 Original Android Development] jrosero:
how did u get that battery percentage?
[Nexus 5 Original Android Development] Ben36:
https://play.google.com/store/apps/details?id=de.kroegerama.android4batpercent
[Nexus 5 Original Android Development] jrosero:
that's not it, if you look at the picture, his battery percent is shown even at 98%. the one in google play will only show up when ur battery becomes real low.

but thank you for your help.

:good::good::good:
[Nexus 5 Original Android Development] eng.stk:
The app is that Ben linked, only colors on L are diferent and level shows always correctly.

The app is in Nexus 5 app subforuim also, check it out :good:
[Nexus 5 Original Android Development] jrosero:
oh ok! thank you very much. :D
[Nexus 5 Original Android Development] yoyoz808:
Does anyone have their screen stay black after calls on L preview? I'm not sure if I'm only getting this or its known bug with the preview itself or something else.
[Nexus 5 Original Android Development] Ben36:
Nope
[Nexus 5 Original Android Development] jitin02:
ROM issue I guess coz I m on stock kernel and face the same
[Nexus 5 Original Android Development] kevtrysmoddin:
Do you have nuplayer checked in developer preview?
[Nexus 5 Original Android Development] eng.stk:
Code_Blue r1092-L

All right crew!

Here we go for another round!

I'm finally debuting dyn_hotplug: Dynamic hotplug driver for hammerhead (aka blu_hotplug), heavily based on stratosk amazing work on the mako.

This is a conservative yet powerful hotplug solution, performance is +/- the same, but temps will go down and battery will go up.

I'm using min 2 cores online (no hotplug touch boost, that's for cpu-boost), max 1 core screenoff. I'm sure you will like it.

Also, flar2 msm_sleeper is enabled to keep fret at 1190MHz on screenoff, powersuspend available on hybrid mode (autosleep and lcd hooks).

Lot's of other goodies and fixes, check changelog!

Get involved, test, play, donate, help, contribute.

You keep the spirit alive!﻿

Changelog:

Compressed with LZ4-r121

Fine tune freq tunables

dyn_hotplug: Introduce Dynamic hotplug driver for hammerhead (aka blu_hotplug), hammerhead fixes, powersuspend hooks, enabled by default (min 2 core online, max 1 core screenoff)

msm_sleeper: Max screen off frequency and shut down cores while screen is off, Change msm-sleeper to use lcd-notifier, Add sysfs entry for max screen off frequency, Change default max screen off frequency to 1190400

cpufreq: Create a helper function to get CPU utilization, Always allow update of user policy

msm_hotplug: Do not butcher boosted CPU

cpu-boost: Export cpu boost status

msm: thermal: make sure we actually want to go through with the policy adjust

powersuspend: new PM kernel driver for Android w/o early_suspend, remove userspace dependency from powersuspend, add back userpace control w/ default kernel control, default to userspace for now, LCD screen on/off hooks (Yank555.lu), cumulative update to version 1.5

ASoC: msm: Rampup volume on each start

ext4: Add support for FIDTRIM, a best-effort ioctl for deep discard trim

sched: Fix race between try_to_wake_up() and move_task(), Update documentation and comments, Fix __sched_period comment

sched/fair: Fix typo describing flags in enqueue_entity
[Nexus 5 Original Android Development] eluspo:
Hope this one will pump up our batt life ? thanks man!
[Nexus 5 Original Android Development] ekowanz:
With the new kernel i got 300mhz a lot, but all the cpu is online.
[Nexus 5 Original Android Development] iba21:
found a bug.. 3 and 4 core wont hotplug!

I runs stability test app, only core0 and core3 are on @ maxfreq, core1 and core2 are everytime offline

Maybe bugghed code?

to install the kernel i wiped system dalvik and cache, reinstall all zips, and reboot..
[Nexus 5 Original Android Development] nexusmaniac:
Although the changelog says min 2 cores online I'm looking at system monitor and there is only 1 core online :S the hotplug was behaving fine earlier :)
[Nexus 5 Original Android Development] iba21:
Yup.. i did some tests.. hotplug dont work..

If i modify the max_online cores boots as the number.. for ex, if i put 3, 3 is the number of cores witch are online..

after 10 (cicle -sampling rate?) down_timer_count cores hotunplugs..

If i put 1 into up_threshold and 1 in up timer count.. still wont hotplug even if the threadshold is low..

P.s. i putted 99 too in up_threshold to test if it's a negative value.. i'm meaning.. i found 25 as defoult.. it means.. 25 of idle time o 25 of cpu usage.. so.. i test it too

Still no hotplug..

Any idea?

If you need i'm here for other beta testing

EDIT: a screenshot of the activity

http://www.imgur.com/JHXTSaE.png

stability test is on.. and only 2 cores are on (the numbers in min_online)
[Nexus 5 Original Android Development] paychex:
When you change the min number of core online it goes back to normal until the cores drop out and they don't come back online. Turned off hotplugging for now
[Nexus 5 Original Android Development] iba21:
Exactly.. if you change the min_online kernel hotplugs cores at number chosed in max_online till the hotunplug..

So.. the unplug works.. the hotplug not

If you disable the module, all 4 cores are still on since there isn't the mpdecision script
[Nexus 5 Original Android Development] eng.stk:
Don't really know guys, maybe some issue with powersuspend.

The code is the same on kk and it works fine.

Altough I rebooted a couple of times and sometimes it works, sometimes not.

I will not loose too much time with L version, revert to previous version for the time being I will look into it later if I have the time.
[Nexus 5 Original Android Development] iba21:
No prob man.. great job
[Nexus 5 Original Android Development] :
Thanks for the info, reverted to 1080L with no issues :)
[Nexus 5 Original Android Development] ekowanz:
Me too.. Revert back and its rock again
[Nexus 5 Original Android Development] eng.stk:
Code_Blue r1097-L

All right crew!

Just pushed Milestone release.

For those that are not familiar with these, the idea is to push out a version that is very stable and stands out from the others.

Reverted back to msm_hotplug, I need to polish dyn_hotplug until is ready for the masses.

My aim is to use lcd_notify, but much work is needed. Also I'm testing autosmp which is also very nice, maybe I'll push out some betas so we can test it .

Meanwhile, maintenance build with some more nice commits.

Will be resting a few some days, so I will be away from xda and stuff, just wanted to leave you guys with something more stable.

Get involved, test, play, donate, help, contribute.

You keep the spirit alive!﻿

Changelog:

Milestone release

Bugfix release, back to msm_hotplug while polishing new hotplug

bluactive: don't scale beyond min if the load is low

Fine tune freq tunables

Removed powersuspend and msm_limiter (hotplug does it all)

Revert " cpufreq: Create a helper function to get CPU utilization"

mm: fix prctl_set_vma_anon_name

defconfig: use smp idle threads

RAMdisk fixes

perf/debug: disable some debug
[Nexus 5 Original Android Development] nexusmaniac:
Hmmm, now I can't decide between this build and 1092 :S I love the new hotplug, when it works it's brilliant for battery life! But when it doesn't it's about the same as before the new hotplug (still good but be hotplug is way better! :D )

But this milestone sounds pretty good with the extra improvements/fixes you've made :) can I run both at the same time? Hehe ;)
[Nexus 5 Original Android Development] iba21:
You can modify msm_hotplug parameters with min cores "2" and with a slow ramp up for other hotplugs

If you need help let me install it, i'll send you a modded script to put in init.d
[Nexus 5 Original Android Development] nexusmaniac:
Oh :) If you could help me with that, that would be great :) ty! I have never touched init.d haha
[Nexus 5 Original Android Development] paychex:
you know 1092 had broke hot plugging right?
[Nexus 5 Original Android Development] nexusmaniac:
Yes, it had 'sort of' broken hotplugging, as I said though; when it works it's great :)
[Nexus 5 Original Android Development] Bubble-be:
Have a beer on me :good:

27C28087L85734505
[Nexus 5 Original Android Development] eng.stk:
Share with others, thats what this thread is for :)

Thank you for the support, it really helps :good: