yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] NeophyteGS2:
The boot.img with rom is permissive, and the previous release of this kernel (17/11) works fine
[Nexus 5 Original Android Development] HiGhDRo3o5:
Lost root again but sensors are working
[Nexus 5 Original Android Development] neobuddy89:
Which ROM? Flashed SuperSu?

What files you see under system/etc/init.d ?
[Nexus 5 Original Android Development] badtazm:
[MENTION=3795148]neobuddy89[/MENTION]

How to fix the broken sensors on stock? I have flashed the new zip with the removed bionic libs.
[Nexus 5 Original Android Development] neobuddy89:
Flash stock again (So that stock libs are back.)

Flash SuperSu

Flash latest nightly.
[Nexus 5 Original Android Development] badtazm:
Sorry if i don't get it but i installed stock with fastboot, should i flash the system.img or the boot.img? Thanks.
[Nexus 5 Original Android Development] neobuddy89:
Flash system.img

Boot in recovery

Flash last nightly
[Nexus 5 Original Android Development] sjknight413:
I lost root too, my init.d folder has disappeared!

Sent from my Android 5.0 Lollipop + ElementalX powered Nexus 5
[Nexus 5 Original Android Development] unknvvn:
Same issue on stock rom, SuperSu is flashed, there is nothing under /system/etc/init.d .
[Nexus 5 Original Android Development] neobuddy89:
I have an idea to fix this.

Seems to me root broke because of ramdisk update from CM12

This => https://github.com/neobuddy89/hammerhead_ramdisk/commit/f3fefbe6122146ff6638b92216836cc86745e126

We are no longer calling SuperSu's modified /system/bin/install-recovery.sh

I removed it because if you use stock's install-recovery by mistake, it can break your recovery.

Anyways, just give me couple min.. This should not take time for next build.
[Nexus 5 Original Android Development] ptr_hamilton:
I'm on aicp Lollipop alpha 0.1 using chain fire super super 2.25 and I have not long root with latest nightly. Let me reboot to double check..

Root even after reboot. No issues with latest version
[Nexus 5 Original Android Development] HiGhDRo3o5:
Same here
[Nexus 5 Original Android Development] neobuddy89:
[MENTION=535343]all[/MENTION], download newest nightly build -

Hybrid_v1.0-[11-21]-[02-32]

* Fix broken root with SuperSu (hopefully)
[Nexus 5 Original Android Development] unknvvn:
It works now, thanks a lot!
[Nexus 5 Original Android Development] pianistaPL:
Amazing and fast feedback by you, thank you, loving this kernel even more.

Please consider adding blu_active governor.
[Nexus 5 Original Android Development] Blueblob:
My LED turn on yellow while phone is charging.

I have light manager with this feature disabled. So kernel takes the lead on it.

How can I config it ? I don't find option in synapse. Or I'm missing something ?

Last build : all right here. Good work ?? Thank you neo

I think it's stuff of new battery saver mode. Red while you're under threshold, yellow while charging, maybe green when full battery.
[Nexus 5 Original Android Development] neobuddy89:
Yes, it's a feature.

Until now, I haven't been successful to find solution where user can control color of led on different stages since there is certain dependency in userspace (system partition.) With current implementation, charging led feature is ported from CM12 to all ROMs - I missed it on AOSP ROMs - but not any more..

We will revisit this sooner to make it better. :good:
[Nexus 5 Original Android Development] neobuddy89:
Thanks. I have checked blu_active governor.

It's same as bacon governor (interactive governor from CAF) with minor changes.
[Nexus 5 Original Android Development] NeophyteGS2:
Thanks for resolving the issues with root last night, its great having the charging lights back!!

One question, though, what benefits us now from using the CM12 ramdisk as opposed to the stock?
[Nexus 5 Original Android Development] vishal8492:
This feature makes my heart pound so hard on hammerhead (pun intended).Damn great feature(Charging lights) and my beloved root is back. Can you recommend under-volt if yes some standard settings(like vomer) ?
[Nexus 5 Original Android Development] neobuddy89:
It's not complete CM12. We have merged certain updates such that both works great.
[Nexus 5 Original Android Development] neobuddy89:
I have checked latest "hyped" CM12 ROM for benchmarks which are more or less same than that our kernel provides for ALL the roms. ;)

Moreover, benchmarks doesn't always reflect true picture. Let's not fall for that trap again.

Newer nightly with experimental test for hw encryption support (and more updates maybe) will be available soon.
[Nexus 5 Original Android Development] pajaSRB:
Excellent excellent kernel! Testing whole day yesterday with aosp N5X rom and I must say that is more then great. With Synapse app I boosted the sound plus sweep2sleep working flawless. TY so much for all hard work!
[Nexus 5 Original Android Development] pianistaPL:
Sorry, I forgot to ask - how can I modify ramdisk?
[Nexus 5 Original Android Development] unknvvn:
[MENTION=3795148]neobuddy89[/MENTION]

i think there is a bug with Synapse.

It seems that default values shown in synapse doesn't reflect what actually is set.

For example just after flashing the kernel in hotplug tab there is a setting "touch boosted cpus 2". However when touching the screen all 4 cores were boosted, until i removed the finger from the screen.

Then i changed touch boosted cpus to 1 and then again to 2, after that only 2 cpus got boosted then touching the screen.

Same happened to max cpu frequency, which is set to 2265, however cpu boosts to 2572. However again disabling and then enabling MSM limiter got my max cpu freq to what is actually set by slider.
[Nexus 5 Original Android Development] gengi:
Try to uninstall and install synapse again
[Nexus 5 Original Android Development] neobuddy89:
Not facing any such bug.

Also touch_boost by default is set to 2 cpus in kernel. There is no way 4 cpus will boost without setting the parameter.

You can check path /sys/kernel/msm_hotplug/touch_boosted_cpus whenever you face such glitch. This parameter will reflect the truth.

Gearing up for next update. Make sure all are using latest SuperSu for Lollipop

http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

We are changing to SELinux ENFORCING mode since LolliRoot is fixed by chainfire.
[Nexus 5 Original Android Development] 5echo2:
[MENTION=3795148]neobuddy89[/MENTION]

I think he means that you have to enable msm limiter in order to change the frequency

I have been getting a bug where the msm limiter doesn't change my cpu back from the suspend frequency 1.6 ghz to my normal frequency 2.6 ghz after i turn my screen on. It does it randomly.
[Nexus 5 Original Android Development] neobuddy89:
1. All controls for changing CPU freq which are defined under MSM Limiter tab will work only when MSM Limiter is enabled.

2. Max freq is manipulated by mpdecision hotplug (if active) as well as thermal driver (always)

3. When devices has reached some temp threshold, you will notice max freq is limited. However, it will sooner restore.

4. MSM Limiter should change back to resume freq in all cases since CPU0 is never offline. If you are finding any issue here, please send me dmesg log and a screenshot of max freq under CPU tab.

Alternatively, you may use suspend freq equal to the resume freq - hardly makes difference since we really don't operate device when screen is off and in very very very rare scenario (which I never faced) there may be nasty rogue process keeping CPU work hard at max freq.
[Nexus 5 Original Android Development] neobuddy89:
New nightly build!

Before installing this nightly build, please update your SuperSu to version 2.27 or later if you haven't already.

Hybrid_v1.0-[11-22]-[21-43]

* HW Encryption support

* SELinux changed to "Enforcing" mode

* Fixed broken QSEEComm driver

* Misc updates
[Nexus 5 Original Android Development] nirudha:
Do we need to do anything to enable hardware encryption?
[Nexus 5 Original Android Development] neobuddy89:
Nopes.
[Nexus 5 Original Android Development] procitysam:
Does this kernel have LED control support?

Sent from my Nexus 5 using the N5X LRX21T ROM
[Nexus 5 Original Android Development] neobuddy89:
LED Control support doesn't work for hammerhead yet due to some dependency in userspace.

However, we have always-on led while charging.
[Nexus 5 Original Android Development] procitysam:
Where would the setting for the charging light be located? I've been unsuccessful finding it.

Sent from my Nexus 5 using the N5X LRX21T ROM
[Nexus 5 Original Android Development] neobuddy89:
No control for it. It's activated. LED color changes as per your battery percentage.

Adapted feature from CM11/CM12.
[Nexus 5 Original Android Development] gengi:
[MENTION=3795148]neobuddy89[/MENTION] im having some problems with some synapse sliders. Do you think it migth have something to do with your kernel or the app? Thanks
[Nexus 5 Original Android Development] neobuddy89:
What problems?
[Nexus 5 Original Android Development] neobuddy89:
Thanks for PM. If this is bug, it will be fixed and new live monitor coming up....
[Nexus 5 Original Android Development] jeky82:
Just tried to install this amazing kernel on new Cataclysm ROM, but I was not able to flash it. The flash process ends with the following error:

symlink: some symlink failed
E: Error executing update binary in zip /sdcard/Download/Hybrid_v1.0-[11-22]-[21-43].zip

what can be the problem?
[Nexus 5 Original Android Development] neobuddy89:
Update your recovery.
[Nexus 5 Original Android Development] badtazm:
Is anyone here using a FIIO E18 DAC? There is a strange bug on android 5.0 that when you press the power button the phone freezes for a bit and pulls up a bugreport.
[Nexus 5 Original Android Development] nirudha:
The hardware crypto stuff seem to be working fine with password encryption. Haven't noticed any issues at least.
[Nexus 5 Original Android Development] neobuddy89:
Many thanks confirming.

[MENTION=5776992]fluther[/MENTION] Same fix would required on Chaos kernel. We have outdated qseecom blobs there.
[Nexus 5 Original Android Development] neobuddy89:
Which ROM? Is same behavior found on your ROM with it's stock kernel?

dmesg and log would be helpful.
[Nexus 5 Original Android Development] Chuck Bartowski:
HW Encryption doesn't make worse performance?
[Nexus 5 Original Android Development] Sc4ryB3ar:
Got this error when flashing this nightly. Twrp2.8.20, su2.27, Cataclysm Rom. Did a clean install of Rom, booted an did initial setup, went to recovery to flash hybrid kernel...
[Nexus 5 Original Android Development] pianistaPL:
Before install try to uncheck /system in "Mount" section in TWRP.
[Nexus 5 Original Android Development] EnginEAR:
Eargasm???

What's "eargasm"? Please share...
[Nexus 5 Original Android Development] Sc4ryB3ar:
Lmao! Its the lolliViper flashable. Its ViPER4Android. LOVE it! Best audio drivers/mod out there, IMHO.

---------- Post added at 10:37 AM ---------- Previous post was at 10:36 AM ----------

Will do, thank you
[Nexus 5 Original Android Development] EnginEAR:
If you work it out- let us know... I want an eargasm too... Thanks!
[Nexus 5 Original Android Development] Sc4ryB3ar:
Oh, Viper works fantastic on Lollipop! There's a couple of hoops to jump through, but absolutely fantastic. There's a N5 ViPER4Android discussion thread that'll get you all the info you need. I flashed that just before trying to flash the kernel, which is why you see it in the screenshot.
[Nexus 5 Original Android Development] badtazm:
I am on stock rom and i have attached a bugreport, last kmsg and dmesg. Thanks.
[Nexus 5 Original Android Development] phishfi:
Is there a simple set of instructions for editing the ramdisk on Android 5.0 or CM12?
[Nexus 5 Original Android Development] topgeardave:
Hey [MENTION=3795148]neobuddy89[/MENTION], I've been looking through your git but I haven't found any cm commits such as audio offloading, is it because it could conflict with aosp?
[Nexus 5 Original Android Development] neobuddy89:
Already merged.

https://github.com/neobuddy89/hammerhead/commits/lollipop/sound/soc/msm/qdsp6v2/

Maybe in General section. Please search in all N5 forums.

Will revisit F2FS later for auto mounting.

Please try newest nightly and let me know.

Hybrid_v1.0-[11-24]-[02-30]

* Rework MSM Limiter driver and bug fixes.

* Add live monitor for min-max-current frequencies in Synapse.

* USB Driver update from 3.4.y and CAF.
[Nexus 5 Original Android Development] topgeardave:
Thanks mate! Glad to be back on this kernel :) One other thing, this audio driver in this kernel supports manual poweramp control like it used to if you want to include it in synapse, I use fauxsound so I'm happy, just thought I'd give you a heads up :)
[Nexus 5 Original Android Development] badtazm:
Have the same issue again [MENTION=3795148]neobuddy89[/MENTION] I think this is the problem cause its the first thing that shows up in logcat and it's not a kernel issue. The E18 has 3 buttons (play,next,previous) and while they work maybe they are confusing the OS.

https://source.android.com/devices/tech/input/validate-keymaps.html https://source.android.com/devices/tech/input/input-device-configuration-files.html

I'll pass this on to FIIO maybe they can commit to AOSP so we can get this issue resolved. Thanks for looking into it though I appreciate it.
[Nexus 5 Original Android Development] xxjrkkrjxx:
Did this break root for anyone else or just me?
[Nexus 5 Original Android Development] neobuddy89:
Is this issue with AOSP stock kernel as well?

Install SuperSU 2.27.
[Nexus 5 Original Android Development] badtazm:
[MENTION=3795148]neobuddy89[/MENTION] Yes it is, the same issue was back to 4.4.x where CM11 would freeze with an ANR of the system ui and reboot sometimes when you opened quick settings or pressed the power button. Now it pulls up a bug report and I think it freezes because it's trying to make the bug report. I don't know what it is but FIIO said they are not planning a firmware update or any updates to the AOSP.Edit: I didn't email FIIO about the above (maybe)solution.
[Nexus 5 Original Android Development] xxjrkkrjxx:
Worked like a charm. Thank you for the prompt response.
[Nexus 5 Original Android Development] janres155:
Hi! I think there is a problem with the frequecy for CPU0, the min freq doesnt go down to 300 and only stay in 1497 even when the screen is not touched.

You can replicate by doing this.

1. set max cpu touchboost for cpu0 to 300

2. Touch the screen and touchboost will react setting min to 300 for a while

3. Observe that cpu0 will return to 1497 and will never go down if you dont touch the screen.
[Nexus 5 Original Android Development] neobuddy89:
That's because of "bacon" CPU governor.

If you change governor to "conservative" for example.. curr freq will fall to 300 if idle.

We need to tune bacon/interactive. Am open to suggestions though.
[Nexus 5 Original Android Development] janres155:
I see. Thanks for the clarification! Btw I don't know what should be done but I think that it should fall to 300 if idle, for better battery savings maybe. Just my opinion.

Thanks again!
[Nexus 5 Original Android Development] neobuddy89:
Yes, I know.

If we think other way round, your device is ready to handle any load and provide smoothest performance.

However, you are right ... better battery savings need idle freq to fall.

We need to find and tune governor and other settings. That's only part remaining for v1.0 to be released as final version.

Let me try some new settings after research, we will concentrate on battery savings for couple of next builds.

EDIT:

FYI for all, FAQ post created in the OP.
[Nexus 5 Original Android Development] janres155:
Okay. Thanks again! Btw good thing you made a kernel for AOSP roms. I really wanna try chaos before but I prefer using AOSP roms than CAF. Sorry for OT [emoji1]
[Nexus 5 Original Android Development] neobuddy89:
Will search and let you know if any solution can be made available.
[Nexus 5 Original Android Development] neobuddy89:
Welcome back. Manual Poweramp is not locked.

It tends to change when you use PowerAmp application or when you insert/remove headset.

It can be locked in-kernel... but will create further issues...

https://github.com/neobuddy89/hammerhead/commit/719f172f49c5ee5e1bb0db8bd7311d17d98130b5
[Nexus 5 Original Android Development] EnginEAR:
Clarification

Maybe I wasn't clear enough... If you looked at my signature you would realize I am using the latest Hybrid nightly and it works for me. I was suggesting that maybe the mix (Hybrid + ViPER) causes the problem and I hoped that if you figured out how to make them work together you would share so I could enjoy an eargasm as well.

Thanks in advance!!
[Nexus 5 Original Android Development] FunkyRasta:
Hmm looking for default governor ? Optimax does not compromise performance for me and is very good with battery if you set optimal max value on 1728000. It will go above only when load is heavy. Intellactive seems nice too.

And for battery eficiency great solution is hotplug MSM MPDecision by show-p1984. Intellidemand agressively turn off cores causing more battery drain because switching cores back on is expensive in terms of energy and heat.

It makes games smoother than any other too. And three phase thermal by show-p1984 is the most genius thermal I ve seen.
[Nexus 5 Original Android Development] neobuddy89:
@FunkyRasta

Which kernel is having latest Optimax governor?

I may like to give it a spin.

EDIT: fix typo.
[Nexus 5 Original Android Development] FunkyRasta:
Hmm did you mean 'kernel' ? ;) both Racer Kernel and Uber from Android Development have up to date Optimax. And in Racer it was introduced not too long ago.

And I really recommend giving bricked (show-p1984) hotplug and three phase thermal a spin too. I know hotplug is much more work than governor implementing but it is worth it in my opinion 100 percent

Sorry for not posting links, sitting here in my classes stealthy posting from under desk ;)
[Nexus 5 Original Android Development] neobuddy89:
Yeah. I meant 'kernel'.

I will cherry-pick and test Optimax. Hope it doesn't give jerky touch.

For bricked hotplug, really need to understand its hotplug logic and implementation as we have multi-hotplug coexisting in one kernel.

(too many users = too many choices)

If that's feasible and good enough, we will have it.
[Nexus 5 Original Android Development] defconoi:
yea I agree, I like the options we already have.
[Nexus 5 Original Android Development] Sc4ryB3ar:
Oh, whoops, didn't catch that...o_0... But yes I have the latest and greatest hybrid working...it appears that, for me at least, I have to wipe caches *before* installing the kernel, instead of after, like I was used to....and I'm happy to report that if you change it to 'permissive' in Synapse, ViPER works just fine!
[Nexus 5 Original Android Development] EnginEAR:
Is this for music mainly or would it also improve speech quality over the speaker? I ask because I use the speaker gain feature in Hybrid and although it is indeed louder- the quality is not so good IMHO...
[Nexus 5 Original Android Development] Sc4ryB3ar:
It's kinda odd the way that it works....you can tune it to whatever you want....for instance if you want speech quality, you can do that, but music will just sound 'eh, OK'. Or vise versa.... However....I've found that headohones....have much better audio out of them, for both....I tune headphones to sound great for watching movies, and boom, it sounds fantastic for voice annnddd music....
[Nexus 5 Original Android Development] tatoniss:
So I am really curious about the hardware encryption. Is it fully accelerated? Would someone more informed be able to explain how it works compared to the current software encryption?
[Nexus 5 Original Android Development] FunkyRasta:
Keeping thumbs up :) Racer kernel for eg. Saw tremendous leap in both performance and battery when coming from intelliplug to bricked hotplug. You should be positively surprised.

More options is always better , of course if they don't cause problems, stability FTW.
[Nexus 5 Original Android Development] unknvvn:
Anyone using CM12 unofficial with this kernel has "miscellaneous" in battery stats higher than "screen"?

With stock + this kernel "miscellaneous" wasn't showing up.

I am wondering if this is just battery stats issue or there is an actual battery drain. Any ideas?
[Nexus 5 Original Android Development] topgeardave:
Hey, I've been messing around with blu_active governor from code blu, as you say its based on bacon governor but it's no where near as aggressive as your bacon governor. I see the blu active governor doesn't use touch boost as freqs can be anywhere between 653mhz to 1.2ghz upon touch. You might want to look into it more deeply if you're after battery life without sacrificing performance :)
[Nexus 5 Original Android Development] mo976:
Neo would it be possible to add a toggle to the CPU governor control in synapsys for choosing per core or unified selection
[Nexus 5 Original Android Development] neobuddy89:
Will check and let you know.
[Nexus 5 Original Android Development] GragonV:
Keep it up :D

Good kernel with useful kernel manager ^^

Only miss the option to choose the direct of swipe action (for sleep and wake), overall is very satisfied ^^
[Nexus 5 Original Android Development] Meakii:
Battery settings

Firstly epic kernel. Loved your work with Chaos.

Interested to know if anybody's getting really sweet battery life with this kernel? If so what settings do you advise? Love trying my own things but there's so many options with synapse that some of it is overwhelming. TIA :good:
[Nexus 5 Original Android Development] JulianXhokaxhiu:
Just want to say that your kernel works amazing also with the ROM called Nexus Experience that is AOSP based too using the latest android-5.0.0_r7 tag!

Yay! :victory:
[Nexus 5 Original Android Development] HiGhDRo3o5:
Same here. Great combo.
[Nexus 5 Original Android Development] neobuddy89:
Ok, so I added a toggle in the kernel which synchronized governors across all CPUs.

However, in Synapse display.. user will have to tap on tick again to confirm.

This seemed very hacky (unless some Synapse expert can help us), so removed toggle. Let's keep it simple, we have 4 cores and not 32. :fingers-crossed:

I am really reluctant to mess with wake controls. If you have link to any N5 kernel which has this feature, let me know; I will have a look. :angel:

Seems good ROM. Using Terminus ROM at the moment, next will be Nexus Experience. :good:

Do we have any XDA thread for same?
[Nexus 5 Original Android Development] JulianXhokaxhiu:
Sure, that's where I discovered it :)

http://xdaforums.com/google-nexus-5/general/rom-android-5-0-aosp-gapps-t2932747

I think it's one of the best combo out there ( until CM12 will be out of course :P ).

Sorry for the Off-Topic btw :)
[Nexus 5 Original Android Development] janres155:
Hi,

Please can you give further explanation for zram max compression streams and the recommended value for it? Thanks!
[Nexus 5 Original Android Development] neobuddy89:
Compression backend may use up to max_comp_streams compression streams, thus allowing up to max_comp_streams concurrent compression operations.	By default, compression backend uses single compression stream.

Recommended value not greater than 2.
[Nexus 5 Original Android Development] crian:
[MENTION=3795148]neobuddy89[/MENTION] is it possible to disable battery charging LED?

Any updates about new Governors and hot plugs?
[Nexus 5 Original Android Development] gamerman123x:
to disable charging led is a rom thing
[Nexus 5 Original Android Development] neobuddy89:
New governors under testing: Intellimm, blu active.

Added Bricked hotplug and tuned it further!

Next build tonight (IST).
[Nexus 5 Original Android Development] dEris:
I'm using Lollerpop and it automounts my OTG. If I flash this, I will lose it?
[Nexus 5 Original Android Development] neobuddy89:
You wouldn't as we have kernel-side support same as CM12 for OTG auto mount.

Please flash, check and confirm.
[Nexus 5 Original Android Development] dEris:
Will do tomorrow and report back. Good night.
[Nexus 5 Original Android Development] Minfreak:
:o I'm on faux kernel with intellimm, it's awesome, will wait for you release (here it's night :)