yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] aviz1911:
I just change the color profile and Undervolt. Other that this, i'm on the stock settings that i upload the kernel. I always use interactive CPU governor(I guess it's the best balance between performance and battery) and sometimes use other governors for testing ;)
[Nexus 4 Android Development] jekkel:
how to start

Hi,

Could you please confirm if the following steps are OK to flash your kernel?

I'm on stock 5.0.1 and very-very disappointed with battery life. So I plan to do the following:

1. Flash TWRP

2. Root + Busybox

3. Flash your kernel

4. Flash UKM

5. Install Synapse

The "dirty flash your ROM" part in your description made me uncertain. Should I do something like that and if yes, how if I'm on stock?

Thanks for answering my noob questions in advance!
[Nexus 4 Android Development] aymnahmd:
I got 4 hrs SOT and still 23% remaining. with nash kernel v12 and SimpleAOSP. ElementalX governor. Super smooth experience.

I have one question : When i flash this kernel CM version on CM based roms it causes the disappearance of the home and recents button+disappearnce of lock screen.

This happened on Crdroid & Liquidsmooth roms.

I fix it by reflashing the rom and gapps.

Can anyone confirm this bug ?

Thanks
[Nexus 4 Android Development] tlongren:
Shouldn't you be using the AOSP kernel from nash instead of the CM version? I also use SimpleAOSP and use the AOSP nash kernel.
[Nexus 4 Android Development] aviz1911:
That's not my kernel issue. Ask it in the ROM thread.
[Nexus 4 Android Development] christopherrrg:
Coming from stock with your steps you'll be okay!

For peace of mind you can always wipe dalvik / cache after flashing to make sure everything is optimized correctly.

---------- Post added at 08:05 AM ---------- Previous post was at 08:01 AM ----------

I think he was saying he does use the setup like that (sAOSP with AOSP kernel) but wanted to try the CM version.
[Nexus 4 Android Development] kelvin99:
been using this kernel for weeks....and i love the battery.....please continue developing this kernel..
[Nexus 4 Android Development] m_harsh:
I wonder how many understood the last line in features list:p
[Nexus 4 Android Development] aviz1911:
SRK rocks ;)
[Nexus 4 Android Development] aviz1911:
I'll continue updating this kernel and I'm not having cancer [emoji14]
[Nexus 4 Android Development] christopherrrg:
I wasn't entirely aware, thanks!

I always thought it had something to do with compatibility.
[Nexus 4 Android Development] Rohit02:
Elemenatlx is freaking awesome.. Loving the battery backup.. Performance is good too.
[Nexus 4 Android Development] aviz1911:
hey, howz R12 going ??

We have 600+ downloads for R12 AOSP version :angel: and that is damn awesome.

I was quite busy these days, you know Job hunting and stuff ;) So, couldn't update the kernel.

But HEY, you will get a Christmas gift with some extra saucy Santa stuff.

Also, if anyone have any feature request, this is the right time to ask and i'll add(do my best) it.

Until then, beat the sh*t out of R12 :p

Thanks !!

CLICK TO SHOW CONTENT below :p
[Nexus 4 Android Development] txuki2005:
Happy christmas to you friend!! Awesome kernel!! Only if is possible.. Conservative for gpu.

Have a good day!
[Nexus 4 Android Development] aviz1911:
Is that better than Franco's interactive GPU governor ??
[Nexus 4 Android Development] yaymalaga:
Hey, that's so great, congratulations for your kernel, and could you pleasy try to add tap2unlock ( http://xdaforums.com/android/software-hacking/kernel-tap2unlock-tap2wake-feature-t2965344). Thanks your work, and merry christmast!
[Nexus 4 Android Development] vampire36:
Elementalx is freaking awesome :P

Wish can we get back 2 cpu min online and 1 when screen off :)

its more efficient than 1 cpu min online
[Nexus 4 Android Development] aviz1911:
Default screen off cores is 1, it's always like that in my kernel.

Lol changing the min online cores isn't a feature [emoji14]
[Nexus 4 Android Development] aviz1911:
Uhhhhh, this is a real battery drainer. I don't even like that extra 2-3% drain while using dt2w, but this tap2unlock drains even more battery than dt2w.

I'm sorry but I will not add it. Are there any kernels with this feature implemented? Howz the battery drain?
[Nexus 4 Android Development] yaymalaga:
I think there isn't any kernel for our nexus4 with this feature. Anyways It's not something important, I just thought it could be cool, but I didn't think about the battery impact, so never mind, thanks anyway.
[Nexus 4 Android Development] vampire36:
Well rest is perfect...its difficult to improve it :P

Btw did you ever test intellidemand...is it good ?

Recently saw AK add it...;)

If you wanna try something...:P
[Nexus 4 Android Development] jacomail95:
Thermal led indicator? Like in unleashed or semaphore kernel? But only if you want to, thanks :)

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Android Development] aviz1911:
I see no reason in enabling it(it's there, but disabled in my kernel) because Franco's interactive governor is far more optimized than intellidemand.

And also, having a list of 100+ governors is not my thing.
[Nexus 4 Android Development] vampire36:
True btw sorry for identity crisis :P

Btw bro is interactive actually better than elementalx....

That you speak so highly of...seems you have tested both well
[Nexus 4 Android Development] aviz1911:
It's more like a personal choice. I only flash Either Franco kernel or My kernel on my nexus 4. So, i'm heavily exposed to Franco's interactive governor and i really like it because it's stable, smooth, battery friendly and good performer when it comes to games. This is the main reason i implemented it into my kernel.

As far as elementalX, i added this because there is no n4 kernel with this governor :p(My mainstream governor is still franco's interactive). I did not test elementalX heavily, this governor is still living in my kernel because of user's positive feedback.

If users who flash my kernel say it's good - i'll keep it, if they say it's bad - i'll remove it ;)
[Nexus 4 Android Development] jacomail95:
Sorry for asking again, i think se can have also a good battery improvement using your kernel also implementing GPU voltages table as in AK kernel :) please, don't fire me from here ;)

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Android Development] aymnahmd:
Flashed. R12 AOSP on Euophoria 24-12 build + banks gapps ..... but the home and recents buttons have disappeared.

Also lockscreen has disappeared.

Can anyone confirm this?

I love this kernel and want to use it.

Thanks

Edit: this happened also onFranco kernel. But not franco-Sabermod.
[Nexus 4 Android Development] lonnieboy:
I have the exact same setup as you (Christmas eve Euphoria, R12, banks gapps) and I do not have that problem.

Maybe see the euphoria google plus to see if there is anything there.
[Nexus 4 Android Development] vampire36:
It happens...its more to do with kernel format....

You need to switch to some other kernel....

Semaphore, Hellscore, etc :)

Else switch to rom like SimpleRom to try this kernel :)
[Nexus 4 Android Development] aviz1911:
If that ROM dev's start messing all the things in the ROM, What should i do ??

This kernel works on Stock and on SimpleAOSP and on CM12. So, there is NO PROBLEM with the kernel. You should consider posting this on the rom thread and they will give you a FIX.
[Nexus 4 Android Development] aymnahmd:
That is strange .

I tried that multiple times even clean flash yet the same problem.

Other kernels work fine (except Franco too).

---------- Post added at 02:55 PM ---------- Previous post was at 02:54 PM ----------

I will switch to simpleAOSP anyway and use this kernel.

I love this kernel.

Thanks
[Nexus 4 Android Development] aviz1911:
Honestly, i don't understand what's the problem with the zip format ?? I'm using this format since kitkat and never experienced any issues and nobody reported one. So, what do we understand from this ??-Rom dev's ****ed up something at their side and they need to fix their ****.
[Nexus 4 Android Development] snak3ater:
It has nothing to do with kernel. Something is wrong in SystemUI. It looks like a bad flash to me. Flash rom again & then flash kernel. Also check the G+ comments & discuss your issue there.

PS: Can you tell us how you flashed Lollipop rom coming from kk..

What were the exact steps?
[Nexus 4 Android Development] skidaway:
It also works fine on SlimLP alpha (5.0.2).
[Nexus 4 Android Development] aviz1911:
Thanks.

I just mentioned the ROM's i tested the kernel ;)
[Nexus 4 Android Development] aymnahmd:
I am now on simpleAOSP + nash kernel and it's awesome.

When i came from KK on November, if flashed the stock google L image which wiped everything on the phone as if new.

I always clean flash Lollipop roms by TWRP (Factory reset + wipe system/cache/dalvic)

Thanks
[Nexus 4 Android Development] aviz1911:
LOL, you flashed SimpleAOSP ? I just made some changes in the ramdisk and testing it on mahdi rom to see if the nav bar issue is fixed ;)

Anyway, SAOSP is awesome tooo and i use that ROM all the time as a daily driver :D [MENTION=4770534]snak3ater[/MENTION] is the BOMB :p
[Nexus 4 Android Development] aymnahmd:
LOL.

If you would like me to test it, i can restore my Euphoria backup and test the new kernel version.

Please tell if then.

SAOSP and Euphoria are my daily drivers. I use them interchangeably.
[Nexus 4 Android Development] aviz1911:
Of course you can test it. I'll PM you the link when it's ready :)
[Nexus 4 Android Development] aymnahmd:
Awesome, with pleasure.

Thanks so much for your great work bro. :)
[Nexus 4 Android Development] vampire36:
[MENTION=4914494]aviz1911[/MENTION] : There has been some change in elementalx logic by flar2 in latest version 2.05...

Not sure but maybe you would like to take a look at it...

Seems he has made it simpler and efficient :P
[Nexus 4 Android Development] aviz1911:
Done.

Added all those latest changes :D R13 in a couple of hours
[Nexus 4 Android Development] vampire36:
Cool :)

Also hopefully would be upto date with all sabermod changes ;)
[Nexus 4 Android Development] aviz1911:
Nash kernel r13

hey everyone,

Uploaded R13 - Check OP for download links and 2nd post for Changelog.

As this version(R13) is different from our previous version zip layouts. I suggest you dirty flash the ROM first or the stock boot.img before flashing R13.

Also, i did not have enough time to test Thermal LED thing. So, don't report all those led not working properly now. I'll fix/test them when i get time. I added that because Some user requested it and i did not want to disappoint him on Christmas :cowboy:

Special thanks to [MENTION=4217103]zaclimon[/MENTION] - For the anykernel layout. You are truly a life saver ;)

Happy Christmas, i gave you guys what i promised and You should smack that "Download button" "Rate this thread button" and "Thanks button" REAL HARD :p
[Nexus 4 Android Development] aviz1911:
Actually, I moved away from Sabermod toolchain.
[Nexus 4 Android Development] zaclimon:
Lool I got a bit too excited with r215 and I actually forgot some elements while doing my anykernel patches. It shouldn't affect anything though looool.
[Nexus 4 Android Development] aviz1911:
A couple of small issues are better than missing navigation bar keys and weird things [emoji14]

I extracted the ramdisk from stock kernel image, did not touch any selinux stuff(maybe Franco did something fishy [emoji14]) but I don't know why its breaking some important things in the ROM.

I know you will fix it, you know I'll pick it [emoji14] ;)
[Nexus 4 Android Development] zaclimon:
I compared both ramdisk from when I was trying to debug that sdcard issue and there's no difference between the Franco ramdisk and stock ramdisk from an selinux perspective.

I don't know why it is breaking stuff as well, though the only thing I can say is that I prefer anykernel due to its flexibility. (even though that's a big hack)

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] camp70:
R12 runs great. Lets see R13. Thanks for the job!

trasteando...
[Nexus 4 Android Development] aymnahmd:
R13 runs greeeeaaaaat on Euphoria 24-12 .

Thanks so much for such spectacular kernel.
[Nexus 4 Android Development] aviz1911:
Thank god its not my fault then.

Until today when users say "your kernel is breaking stuff" I thought I messed up the ramdisk. But now Franco kernel breaks them too, so I'm proud of that ;)

Also, this is the case with only a few custom ROMs(I noticed only 1), and the rest are fine. I have no clue what's causing it so, switched to your any kernel format(legend says, yours doesn't break things [emoji14])
[Nexus 4 Android Development] Gu$houn*:
[MENTION=4914494]aviz1911[/MENTION] r13 working flawlessly with [MENTION=4770534]snak3ater[/MENTION]'s 25/12 simpleAOSP build, thanks a lot, buddy.

I know it's not a meant feature but after reboot my led makes a single slooooow red blink and it looks very cool. :good:

P.

[sntfrmnxs4]
[Nexus 4 Android Development] zaclimon:
Hmm I wouldn't say that Franco have problems because I never had encountered any ROM problems with Franco kernel period. That said I could say that maybe something lies in the kernel (optimizations, toolchains who knows)

Also go check your PM's. :p

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] aviz1911:
Lol, that's thermal led. It blinks according to the CPU temperature I guess. Low brightness - your CPU is so so cool, high brightness - your CPU is ready to get roasted [emoji14]
[Nexus 4 Android Development] aviz1911:
Nope, I'm not saying its Franco kernel that's causing it. His kernel is intended to work on stock ROM and yes, it does a great job in doing that.

But if he once look into the weird Nav bar disappear thing, he can solve it easily. That is what I'm hoping for :)
[Nexus 4 Android Development] Gu$houn*:
Thanks for your reply.

So my CPU is sooo cool after reboot, then heats up to become cold again, I don't use this feature it's just cool.

P.

[sntfrmnxs4]
[Nexus 4 Android Development] aviz1911:
No No, "SO SO cool" in the sense I meant to say not soo cool/hot LOL :p(thats what i pronounced while writing it So, So maybe :p, damn English is hard)
[Nexus 4 Android Development] xWolf13:
So weird. On any ROM I try this kernel on it won't work. It boots, but it's just a blank black screen. Did your steps too. Dirty flash ROM, then install the kernel and still a no go. I'm running on SimpleAOSP Build 7 at the moment.
[Nexus 4 Android Development] kelvin99:
I flash also R13 now I experience bootloop..going back in R12...runs perfectly and I don't know what' the problem

edit:

Sorry need to dirty flash the ROM and Its's running great.. you need to dirty flash ROM gapps and super SU then the r13
[Nexus 4 Android Development] snak3ater:
Delete [emoji1]
[Nexus 4 Android Development] aviz1911:
Please dirty flash the rom or fastboot stock boot.img, i changed to the any-kernel layout in R13(which fixes all those issues with euphoria rom) so that's what caused you the bootloop.

I'm on Saosp Christmas build with R13 and i don't think there are any major differences between this and build 7. So, the kernel should boot and work fine on build 7. What kernel you were on before flashing my kernel ?? I also changed the min freq to 384mhz to avoid all the possible issues with slow cpu bins.

You guys need not worry while flashing my kernel on SAOSP, i test all my kernels on that ROM and if my kernel breaks anything on that ROM, i'll fix them before you guys even notice it :D
[Nexus 4 Android Development] kelvin99:
It's fine now..I'm in R12..then flash R13...i'm stuck at bootloop..what I did i dirty Flash my ROM gapps and superSU and R13..and It's working great..
[Nexus 4 Android Development] aviz1911:
I stated clearly(with red color font) to dirty flash the rom before flashing R13 :confused:

Anyway it's working now. So, enjoy it and report if you find any bugs..
[Nexus 4 Android Development] xWolf13:
Excuse my idiotic mind :P. I was flashing the CM12 version on a AOSP based ROM.
[Nexus 4 Android Development] casmelad:
Having fc on playstore and red light led with r13 after hellscore, dirty flash, any clue?
[Nexus 4 Android Development] aviz1911:
PlayStore FC ? Check your gapps package.

Red-light is Thermal LED which was added in R13. It varies in brightness and completely turns off based on the device temperature. You can turn that off in synapse.
[Nexus 4 Android Development] maufega:
In my case, the problem with LED does not change values, always red in charging
[Nexus 4 Android Development] vampire36:
I used semaphore kernel manager...just set all thermal led indicators to none...

Done :)

Now charging lights are normal :)
[Nexus 4 Android Development] vampire36:
[MENTION=4914494]aviz1911[/MENTION] : The kernel is continuously outputting E/Powerhal(578): touch_boost: failed to send: No such file or directory error continuoulsy....

Maybe you should look at it :)

https://github.com/faux123/hardware_qcom_power/commit/31763b036130553d85232073e31288d94ae9d172

this may help not sure
[Nexus 4 Android Development] aviz1911:
Don't worry about that PowerHal, it's because the touch_boost goes through MPDecision which I've disabled.
[Nexus 4 Android Development] sykopompos:
I went through that with defconoi when we were figuring out everything with the L preview, there is another power hal file in lib/hw to delete with your install script that is then useless and causes that spamming if you disable mpdecision
[Nexus 4 Android Development] aviz1911:
Defconoi have some deadly stuff in his zip folder ;)

Searching his git is like jumping out of the titanic. Too hard but totally worth it. I'll see the end of this powerhal thing now.

Thanks for the info.
[Nexus 4 Android Development] sykopompos:
I had to dig through the old hangouts convo and was for the n5 but the power.msm-xxxx.so (CPU numbers for the xxxx) and the power.hammerhead.so had to be removed since they get replaced by the ones you are making to get rid of the touch boost spam
[Nexus 4 Android Development] maufega:
better R12 !!
[Nexus 4 Android Development] aviz1911:
LOL
[Nexus 4 Android Development] maufega:
Surprised, yes, yes, I knew I had not explain :D

Seriously, you have the best kernel to this day, but I was better before.

Thanks for your work and share.
[Nexus 4 Android Development] aviz1911:
Tune the kernel as you like.

Difference between R12 and R13 is Min online cores is set to 2 and Min cpu freq is set to 384mhz(You can change these using synapse).

And i don't think these would make a huge impact on the battery life or performance of the kernel :)
[Nexus 4 Android Development] maufega:
You win that that's their job, but the first thing I did was precisely that change.

And what of thermal or changing led synapse is solved. Thanks again.
[Nexus 4 Android Development] blusydays:
2 cores always online at 384 Mhz surely use more battery than 1 core online at 192 Mhz.
[Nexus 4 Android Development] aviz1911:
192mhz is still there(not all CPUs can handle low freq at boot). 384mhz is the stock frequency. So, you cant complain on that.

2 cores online is just a personal choice.

You can change both these using synapse to your liking. I don't force anyone to stick with the settings I push the kernel with ;)
[Nexus 4 Android Development] vampire36:
Can we have a build compiled with latest sabermod :)

Maybe placebo but just feel sabermod one was better :P
[Nexus 4 Android Development] aviz1911:
Sure. Next build :good:
[Nexus 4 Android Development] jacomail95:
Dear aviz, led things work fine here, thanks ;)

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Android Development] txuki2005:
All go fine here with SimpleAOPS... this kernel with sabermod feature will be impressive with SIMPLE :D
[Nexus 4 Android Development] aviz1911:
Already added Sabermod toolchain path in the Makefile ;)
[Nexus 4 Android Development] vampire36:
How far from we getting it :P
[Nexus 4 Android Development] ltjmax:
Is it normal that I can't see blu_active governor anymore? I don't see anything on the 13 changelog about it.
[Nexus 4 Android Development] aviz1911:
Disable blu_active(Sorry fanboys)

You can't see it in the Changelog ?? :confused:
[Nexus 4 Android Development] ltjmax:
Ha ha... Sorry, think I read to fast
[Nexus 4 Android Development] aviz1911:
Hey,

If anyone want a test build

https://www.androidfilehost.com/?fid=95864024717071977

Changelog:

Complete Rebase (I was bored and i did this :p)

Added sweep2dim, sweep2sleep, dt2w profiles, touch wake

Added SLIM GPU Governor, No interactive yet - i'll add it

Back to sabermod toolchain

Max screen off cores is set to 2 and Max screen off freq is set to 702mhz(Don't shout, Change these in synapse)

Back to my OLD KERNEL FORMAT(Fixed nav bar key issue though ;))

No thermal LED, No Mpdecision

Sync Ramdisk with Latest CM12 sources

And some other things, i don't remember correctly - Check GIT

Test it and report. Don't just flash it and Forget :p
[Nexus 4 Android Development] vampire36:
Cool test begins :P

Edit : Current setup

Governor elementalx

Min cores 2 max 4 screen on

Min core back to 1 screen off

Min Frequency 192

-50 UV....

Smoothass bro :)
[Nexus 4 Android Development] kelbaez:
oh man.. Im currently in the middle of a clean install of SimpleAOSP bould 8 since the R13 cause bootloops on SimpleAOSP build 6 and didnt want to dirty flash the ROM..

well never hurt to clean flash once in a while
[Nexus 4 Android Development] aviz1911:
Yeah i reverted from anykernel. Just dirty flash this test build if you are on R13, it should work fine.

You clean flashing broh ?? :p :p
[Nexus 4 Android Development] aviz1911:
Whats your CPU bin ??
[Nexus 4 Android Development] vampire36:
Faster PVS 4

Speed bin 0
[Nexus 4 Android Development] kelbaez:
too late for dirty flash.. when you posted I was all cleaned out :p
[Nexus 4 Android Development] maufega:
TEST SimpleAosp - Nash Test 29/12

Setup

Governor Elementalx

Min cores 2 max 4 screen on

Min core back to 1 screen off

Min Frequency 192 MHz.

Max Frequency 1458 MHz

CPU Volt: -130 mV

ACPU PVS: Fast

Speed BIN: 0

First impression; wonderful
[Nexus 4 Android Development] Gu$houn*:
Hey [MENTION=4914494]aviz1911[/MENTION],

the test version working flawlessly here with simpleAOSP build 8, I really love the sweep 2 sleep feature, finally I'm able to use smart lock feature how it's meant to be used. My power button is 100% ok but I like these gesture things and I don't like double tap to status bar because it's not really handy and my status bar is hidden on the home screen. And unfortunately all those screen off apps also lock screen so again, not as smooth as it could be but now it's perfect, s2s with Stratosk's dt2w, ou yeah, thanks a lot.;)

P.

[sntfrmnxs4]
[Nexus 4 Android Development] aviz1911:
Also try sweep2dim. This comes in handy while reading ebooks or surfing internet on your device at night times.
[Nexus 4 Android Development] Gu$houn*:
Yes, I tried it for a while but I'm using Lux app to control brightness set to setup brightness after screen wake up and I find out that it's /obviously?/ not possible to use sweep to dim and sweep to sleep at the same time, right? At least my Trickster Pro doesn't like it that way and sweep to sleep & wake too, even if dt2w is disabled. Nevermind, s2s & dt2w is cool combo.

P.

[sntfrmnxs4]
[Nexus 4 Android Development] syedtahir16:
Awesome

Currently running r13. Flawless so far.

Snappier than hells which I was using earlier. Thanks [MENTION=1229225]aviz[/MENTION]
[Nexus 4 Android Development] aviz1911:
Yup, using both s2d and s2s at the same time is not possible.

s2s and dt2w combo is the bomb :highfive:
[Nexus 4 Android Development] aviz1911:
Added UKM+SYNAPSE into the kernel, you know to make things easier to tweak it.

I'ts the STOCK UKM 3.6.1, so if you forget and re-flash the UKM zip after flashing my kernel, there will be no issues.

Also, bailed Franco's thermal and added Faux intelli thermal and tweaked the temperatures a bit.

I'm not sure to keep Thermal LED or Remove it. It's fighting with ROM led tunable values, and you need to disable it before ROM led values work. What do you guys say ??
[Nexus 4 Android Development] ltjmax:
I personnaly find thermal LED more annoying than anything