Banner

Banner

Mittwoch, 9. Dezember 2015

N6: b12-M

-added a couple of patches for several memory leaks
-fixes here and there (sorry i'm to lazy)
-updated to 6.0.1 source
-check git for all commits


Explanation of the different builds:

hC-b12-M: Selinux enforcing, marshmallow wi-fi driver
hC-b12-M-old_wi-fi: Selinux enforcing, lollipop wi-fi driver
hC-b12-M-permissive: Selinux permissive, marshmallow wi-fi driver
hC-b12-M-permissive-old_wi-fi: Selinux permissive, lollipop wi-fi driver


Selinux mode:

I compiled two different selinux modes. Some custom roms out there don't use the patched sepolicy from chainfire, this means these roms need a permissive kernel for root. If you try to boot an enforcing kernel on this roms, you'll end in a boot loop. Don't ask me what you need, since I can't track all roms and I don't know which one of them boot with an enforcing selinux mode. This kernel works with chainfires latest systemless root!


Wi-fi driver:


Its known some networks don't like the new marshmallow wi-fi driver. People reporting disconnects, not able to connect at all, or an instable connection in general. If you suffer from this, switch from the marshmallow driver to the lollipop one.


BUG-REPORT:

If you encounter an issue, please provide more information than just "phone reboots" or something like that. If your phone crashes, you can find crash logs in: /sys/fs/pstore - Just upload them and link me to them. Thank you!


DOWNLOADS:

renderserver


Have fun!

hells

Samstag, 7. November 2015

N6: b11-M

-reverted a few patches, which caused a non-working mic on calls for some
-compiled with latest ubertc


Explanation of the different builds:

hC-b11-M: Selinux enforcing, marshmallow wi-fi driver
hC-b11-M-old_wi-fi: Selinux enforcing, lollipop wi-fi driver
hC-b11-M-permissive: Selinux permissive, marshmallow wi-fi driver
hC-b11-M-permissive-old_wi-fi: Selinux permissive, lollipop wi-fi driver


Selinux mode:

I compiled two different selinux modes. Some custom roms out there don't use the patched sepolicy from chainfire, this means these roms need a permissive kernel for root. If you try to boot an enforcing kernel on this roms, you'll end in a boot loop. Don't ask me what you need, since I can't track all roms and I don't know which one of them boot with an enforcing selinux mode. If you'd like to make sure the enforcing kernel boots, you need to flash chainfires modified boot.img from here first and flash my kernel after it: boot.img


Wi-fi driver:

Its known some networks don't like the new marshmallow wi-fi driver. People reporting disconnects, not able to connect at all, or an instable connection in general. If you suffer from this, switch from the marshmallow driver to the lollipop one.


BUG-REPORT:

If you encounter an issue, please provide more information than just "phone reboots" or something like that. If your phone crashes, you can find crash logs in: /sys/fs/pstore - Just upload them and link me to them. Thank you!


DOWNLOADS:

renderserver

devkeep


Have fun!

hells

Sonntag, 1. November 2015

N5: b15-M / b26-L

-added hellsactive back
-hellsactive: added cpufreq_notify_utilization to work with mako_hotplug
-compiled with latest ubertc built by me


DOWNLOADS:

renderserver

devkeep


Have fun! (=

hells

N4: b87-M / b83.5-L

-enabled hellsactive
-hellsactive: added cpufreq_notify_utilization to work with mako_hotplug
-compiled with latest ubertc built by me


DOWNLOADS

renderserver

devkeep


Have fun! (=

hells

Mittwoch, 28. Oktober 2015

N6: b11-t1-M


-Revert "msm: mdss: accquire pipe before overlay start in pan display" - to fix the freeze by charging on power off.
-compiled with self built UBERTC-5.2 optimized for cortex-a15 - You can find the toolchain here, if you'd like to compile my kernel, or just use it for your own: https://bitbucket.org/hellsgod/uber-arm-eabi-5.2-cortex-a15


Explanation of the different builds:

hC-b11-t1-M: Selinux enforcing, marshmallow wi-fi driver
hC-b11-t1-M-old_wi-fi: Selinux enforcing, lollipop wi-fi driver
hC-b11-t1-M-permissive: Selinux permissive, marshmallow wi-fi driver
hC-b11-t1-M-permissive-old_wi-fi: Selinux permissive, lollipop wi-fi driver


Selinux mode:

I compiled two different selinux modes. Some custom roms out there don't use the patched sepolicy from chainfire, this means these roms need a permissive kernel for root. If you try to boot an enforcing kernel on this roms, you'll end in a boot loop. Don't ask me what you need, since I can't track all roms and I don't know which one of them boot with an enforcing selinux mode. If you'd like to make sure the enforcing kernel boots, you need to flash chainfires modified boot.img from here first and flash my kernel after it: boot.img


Wi-fi driver:

Its known some networks don't like the new marshmallow wi-fi driver. People reporting disconnects, not able to connect at all, or an instable connection in general. If you suffer from this, switch from the marshmallow driver to the lollipop one.


BUG-REPORT:

If you encounter an issue, please provide more information than just "phone reboots" or something like that. If your phone crashes, you can find crash logs in: /sys/fs/pstore - Just upload them and link me to them. Thank you!

DOWNLOADS:

renderserver

devkeep


Have fun!


hells

Dienstag, 27. Oktober 2015

N6: b10-M

-merged kernel patch needed for cataclysm rom
-merged a lot of patches for several subsystems (mdss/slimbus/net/vidc/etc)
-tuned cfq and bfq for flash memory
-f2fs is now supported
-merged some memory management related stuff and other fixes here and there
-merged a patch for better colors on low brightness (less reddish)
-compiled with UBERTC 5.2

Explanation of the different builds:

hC-b10-M: Selinux enforcing, marshmallow wi-fi driver
hC-b10-M-old_wi-fi: Selinux enforcing, lollipop wi-fi driver
hC-b10-M-permissive: Selinux permissive, marshmallow wi-fi driver
hC-b10-M-permissive-old_wi-fi: Selinux permissive, lollipop wi-fi driver

Selinux mode:

I compiled two different selinux modes. Some custom roms out there don't use the patched sepolicy from chainfire, this means these roms need a permissive kernel for root. If you try to boot an enforcing kernel on this roms, you'll end in a boot loop. Don't ask me what you need, since I can't track all roms and I don't know which one of them boot with an enforcing selinux mode. If you'd like to make sure the enforcing kernel boots, you need to flash chainfires modified boot.img from here first and flash my kernel after it: boot.img


Wi-fi driver:

Its known some networks don't like the new marshmallow wi-fi driver. People reporting disconnects, not able to connect at all, or an unstable connection in general. If you suffer from this, switch from the marshmallow driver to the lollipop one.


DOWNLOADS:



Have fun!

hells

Freitag, 23. Oktober 2015

N5: b13-M

-merged commit needed for cataclysm rom
-cfq/bfq: set slice idle to 0 for better flash memory performance
-sched: upstream fix


DOWNLOADS:

renderserver

devkeep

Dienstag, 20. Oktober 2015

N6: b9-M / b13-L

-rebased on top of latest google source for marshmallow
-back to cfs cpu scheduler
-cfs is now tweakable for performance, or battery life in kernel adiutor (performance default)
-cleaned source a little
-compiled with latest sabermod 5.2 toolchain


Explanation of the different builds:

hC-b9-M: Selinux enforcing, marshmallow wi-fi driver
hC-b9-M-old_wi-fi: Selinux enforcing, lollipop wi-fi driver
hC-b9-M-permissive: Selinux permissive, marshmallow wi-fi driver
hC-b9-M-permissive-old_wi-fi: Selinux permissive, lollipop wi-fi driver
hC-b13-L: Selinux enforcing, lollipop wi-fi driver, last lollipop build


Selinux mode:

I compiled two different selinux modes. Some custom roms out there don't use the patched sepolicy from chainfire, this means these roms need a permissive kernel for root. If you try to boot an enforcing kernel on this roms, you'll end in a boot loop. Don't ask me what you need, since I can't track all roms and I don't know which one of them boot with an enforcing selinux mode. If you'd like to make sure the enforcing kernel boots, you need to flash chainfires modified boot.img from here: boot.img


Wi-fi driver:

Its known some networks don't like the new marshmallow wi-fi driver. People reporting disconnects, not able to connect at all, or an instable connection in general. If you suffer from this, switch from the marshmallow driver to the lollipop one.


DOWNLOADS

renderserver

devkeep

If you like my work, you can donate me a coffee for my night sessions on the kernel: Coffee - Thank you (=

Donnerstag, 15. Oktober 2015

N4: b84-M - ONLY FOR MARSHMALLOW!!!

-merged source from CallmeAldy to have a working marshmallow base

Download

Mirror

Have fun with marshmallow on your device!

hells

Mittwoch, 14. Oktober 2015

N6: b8-M / b8-M-old_wi-fi

I know some of you suffer from reboots, thats why I cleaned the source again. I got a few logs, but nothing I could read from what exactly could be the problem. I'm sorry if you had such problem in the past. If it still happens, just upload the logs from /sys/fs/pstore and link me to it. Priority is to nail down this stability issues finally now! :) Oh and I also have a build with the lollipop wi-fi drivers!

-cleaned up
-compiled with latest sabermod toolchain

Download

Mirror

Have fun!

hells

Samstag, 10. Oktober 2015

N6: b8-t2-M

stability update:

-Revert "PM / Wakeup: Use rcu callbacks for better performance"

SuperSU 2.50 and chainfire boot.img is required! Have a look here: http://hc-kernel.blogspot.ch/2015/10/android-m-how-to-gain-root.html

Download

Mirror

Have fun!

hells

Mittwoch, 7. Oktober 2015

N4: b83 / -CM

-compiled with latest available sabermod 4.9 toolchain
-no changes in code

Download

Mirror

Have fun!

hells

Android M: How to gain Root!

SuperSU 2.50 allows ROOT in selinux enforcing mode, so the permissive hack is not needed anymore. You need to flash one of these modified stock boot.imgs for your device: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

-Flash boot.img via fastboot / TWRP (unzip it and push the boot.img to your device, chose image to install - boot partition)
-Boot into recovery
-flash SuperSU
-flash latest hC: N5 and N6

This boot.img also disables security warning on bootup!

hells

N6: b8-t1-M

SuperSU 2.50 allows root without selinux permissive, so I reverted the previous selinux hack.

Please read this short guide for gain root access: HOW TO GAIN ROOT WITH SUPERSU 2.50

-reverted selinux hack

Download

Mirror

Have fun!

hells

N5: b11-M

SuperSU 2.50 allows root without selinux permissive, so I reverted the previous selinux hack.

Please read this short guide for gain root access: HOW TO GAIN ROOT WITH SUPERSU 2.50

-reverted selinux hack

Download

Mirror

Have fun!

hells

Montag, 5. Oktober 2015

N5: b10-M / M ONLY!!

-merged m source
-reverted a pm/wakeup commit

Download: http://renderserver.net/?dir=devs/hellsgod/hells-Core-N5

Mirror: http://devkeep.de/7~f

Have fun!

hells

N6: b7-M / M ONLY!!

-merged m final source
-gained write access to /system

Download: http://renderserver.net/?dir=devs/hellsgod/hells-Core-N6

Mirror: http://devkeep.de/8~f

Have fun!

hells

N6: b12.2 / b6.2-M3

-compiled with latest sabermod
-reverted a couple of problematic commits
-Final lollipop and m-preview build
-m-build boots on official release. its up to you if you wait for the m kernel based on release source drop.

Download: http://renderserver.net/?dir=devs/hellsgod/hells-Core-N6/

Mirror: https://www.dropbox.com/sh/1v8f9nlf3mh35bi/AAAC-7_79zEweIZbsgCwoZ9Wa?dl=0

Have fun!

Samstag, 26. September 2015

N6: b12.1 / b6.1-M3

-Revert: "PM: Enable asynchronous noirq resume threads to save the resuming time"

Let me know if the wakeup problem some of you had are fixed. If you encounter a freeze, lag and the phone comes back to life after a few seconds, please do a dmesg and link me to if. You can do it with syslog from the play store (kernel log is what I need), right after the issue appeared. If the phone rebooted, please attach the /sys/fs/pstore/ files. I'd like to nail down the last issues to have a stable start on M.

Download: http://renderserver.net/?dir=devs/hellsgod/hells-Core-N6/

Mirror: https://www.dropbox.com/sh/1v8f9nlf3mh35bi/AAAC-7_79zEweIZbsgCwoZ9Wa?dl=0

Have fun (=

hells

Donnerstag, 24. September 2015

N5: b24 / b9-M

-mutex/rtmutex update
-fixes here and there (please refer to git)

Final build before M drops :)

Download: http://renderserver.net/?dir=devs/hellsgod/hells-Core-N5

Mirror: https://www.dropbox.com/sh/5ct4pwjubn1h360/AAAriS-SdPQkkSe47oVlxn7ba?dl=0

Have fun :)

hells

N6: b12 / b6-M3

-cleaned source
-fixed a bug in bfs

Let me know if this kernel fixes the issue some of you had in the last few versions (lags/freeze/reboots) If all is running well I'll take this as reference for the M kernel, when the final source drops sometime after the 29th.

Download: http://renderserver.net/?dir=devs/hellsgod/hells-Core-N6

Mirror: https://www.dropbox.com/sh/1v8f9nlf3mh35bi/AAAC-7_79zEweIZbsgCwoZ9Wa?dl=0

Have fun :)

hells

Samstag, 19. September 2015

N6: b12-t2 / b6-t2-M3

New test kernel! Let me know if the freezing issue some of you had are fixed in this build. I sent it to a tester and he haven't had a freeze in more than 24 hours.

-merged rcu updates
-merged rtmutex/mutex updates
-various other small improvements (check git)

Download: http://renderserver.net/?dir=devs/hellsgod/hells-Core-N6

Mirror: https://www.dropbox.com/sh/1v8f9nlf3mh35bi/AAAC-7_79zEweIZbsgCwoZ9Wa?dl=0

Have fun! (=

hells

Samstag, 12. September 2015

N5: b23 / -b8-M

I released b22 / -b7-M a few hours ago. I forgot to set the right min frequency - such things happens if you don't have the device anymore ;-) So here's b23! (changelog also mentions the stuff from b22)

-rebased upon latest m-source
-mako_hotplug
-cleaned out some stuff
-compiled with latest sabermod 5.2
-fixed min_freq

Download: http://renderserver.net/?dir=devs/hellsgod/hells-Core-N5

Mirror: https://www.dropbox.com/sh/5ct4pwjubn1h360/AAAriS-SdPQkkSe47oVlxn7ba?dl=0

Have fun!

hells



N4: b82 / -CM

-rebased upon latest google source
-msm_mpdecision replaced with mako_hotplug
-interactive and hellsactive temporarly deisabled, because of problems with them
-compiled with sabermod 5.2
-some things I may forgot

Download: http://renderserver.net/?dir=devs/hellsgod/hells-Core-N4

Mirror: https://www.dropbox.com/sh/p26kzvjrne9j7nm/AACK0ExVeS7rlCu-Bbr6Tms6a?dl=0

Have fun!

hells


N6: b11 / b5-M

-rebased on top of m3 source
-mako and ZEN in one kernel (boots with ZEN)
-in-kernel thermal - begins to throttle at 70°C to 2265mhz, 1728mhz, 1267mhz, 960mhz
-old_wi-fi build for the ones who had wi-fi probs in the past
-compiled with sabermod 5.2

Download here: http://renderserver.net/?dir=devs/hellsgod/hells-Core-N6

If you can't access the page, wait a few mins and try it again, or use my mirror here: https://www.dropbox.com/sh/1v8f9nlf3mh35bi/AAAC-7_79zEweIZbsgCwoZ9Wa?dl=0

Have fun!

hells

Donnerstag, 13. August 2015

Nexus 6: b10-t3 / b4-t3-M2

I've played around with some commits to improve the already good base we have. This time I merged a lot of gpu stuff and block/filesystem things. I reverted some of the wi-fi patches, because some users experienced disconnects/unstable wi-fi.

Changelog:
-kgsl patches from caf
-ext4 from upstream
-blk-throttle from mainline
-mmc/block srtuff from caf
-reverted wi-fi driver to a more stable state

hC-b4-t3-M2

hC-b4-t3-M2-mako

hC-b10-t3-ZEN

hC-b10-t3-mako

Have fun! (=

hells

Montag, 27. Juli 2015

Nexus 6: b9 / b3-M2

I rebased my kernel on top of the latest m-preview source. Lollipop and M kernel are both based upon that source. The only difference is, the M kernel runs permissive, because that's the only way to have working root on M. I removed some cruft in the rebase and changed some little things. I set the touch boost duration from 500ms up to 1s. That was a config I was using on b1. So if you think your screen on time is worse with this release, set it back to 500ms.

Changelog:
-rebased on m-preview 2 source
-removed some unneeded stuff
-higher touch boost duration to 1 second
-wi-fi updates from google repo

hC-b3-M2

hC-b3-M2-mako

hC-b9-ZEN

hC-b9-mako

Have fun! (=

hells

Samstag, 18. Juli 2015

Nexus 5: b19-L

BUGFIX: The same commit which made troubles on shamu also made troubles on hammerhead. But on shamu the problem was on M, here its on Lollipop. I'm talking about video recording.

Changelog:
-reverted vidc commits to have a working video recording on lollipop

hC-b19-L

Have fun! (=

hells

Nexus 6: b9-t4 / b3-t4-M

BUGFIX: Video recording did not work on the M-preview, but was working fine on lollipop. I've reverted the two vidc commits, which were added into the source and its working fine again on M. It was no issue on lollipop, but to keep track of the commits, I decided to revert them there also.

Changelog:
-reverted vidc changes which caused a non working video recording on M

hC-b3-t4-M

hC-b3-t4-mako-M

hC-b9-t4-ZEN

hC-b9-t4-mako

Have fun! (=

hells

Nexus 4: b81

It's been awhile since the last N4 build. But to be honest this kernel almost has everything needed and only one issue left: The wakup delay on calls. I have to think about some ways to get rid of it in the future. I've lowered the temperature threshold to 70°C and added a few commits from the N5 m-branch. Its also built with an updated toolchain.

Changelog:
-temp threshold set to 70°C
-few commits from M
-updated toolchain

hC-b81-L

hC-b81-CM

Have fun! (=

hells

Nexus 6: b9-t3 / b3-t3-M

I've merged a lot wi-fi stuff from the google repo, added some mainline updates for nohz and finally merged the m-preview 2 source. Toolchain also got updated.

Changelog:
-wi-fi updates
-nohz updates
-m-prev2 source
-toolchain updated

Refer to -t4

Have fun! (=

hells

Nexus 5: b4-M

I merged the m-preview source in both releases and the toolchain got updated.

Changelog:
-m source update
-toolchain update

hC-b4-M

b18 was removed, head over here

Have fun! (=

hells

Sonntag, 5. Juli 2015

Nexus 6: b8 / b2-M

I didn't change much on this release. I fixed a mistake I made in adreno idler and reverted a commit, which could cause random reboots on a few devices. So its more a bugfix release :)

Changelog:
-fixed a mistake in adreno idler
-reenabled tablet and joystick support
-reverted a commit which cause rr on a few devices
-changed the wi-fi wakelock divisor*

*I've found a way to deal with some huge wakelock issues on wi-fi. But now you can't tweak the wi-fi wakelock divisor in Kernel Adiutor anymore, thats why I made a script, where the wi-fi wakelocks will be disabled. You can tweak the divisor to another value if you like, I just disabled the wakelock at all in the script.

hC-b2-M

hC-b2-mako-M

hC-b8-ZEN

hC-b8-mako

Wi-Fi-wakelock-disabler

Have fun! (=

hells

Mittwoch, 24. Juni 2015

Nexus 6: b7 / b1-M

It's been a while since the last shamu update. I did builds for the other devices and tested some things for shamu in the mean time. There's always something to do on one of the devices ;-)

Changelog:
-updated BFQ
-merged some ext4 patches from linux upstream
-merged some caf kgsl patches
-merged various other patches for several subsystems to improve battery life and efficiency
-added adreno idler
-prevent bcl driver to kick out cores in some cases

hC-b1-M

hC-b1-mako-M

hC-b7-ZEN

hC-b7-mako

Have fun! (=

hells

Dienstag, 23. Juni 2015

Nexus 5: b17-L / b3-M

You may've seen I've pushed a build for mako where I've fixed the chrome freezing / hang issue. I've reverted the same gpu patches here on hammerhead, so lets see if its better now here, too.

Changelog:
-reverted some gpu patches to fix the chrome issues

hC-b17-L

hC-b3-M

Have fun! (=

hells

Samstag, 20. Juni 2015

Nexus 4: b80

Some people mentioned scrolling issues on chrome. I've investigated it a little and the whole thing seems very contradictory to me. Anyway, I looked around and saw a dev reverting some gpu patches to fix this issue, so I did the same. Please let me know if its better now.

Changelog:
-updated BFQ
-reverted gpu patches to fix chrome issues (need feedback on that one!)
-some little fs fixes
-hellsCode from @Maxr1998

AOSP

CM

Have fun! (=

hells

Sonntag, 14. Juni 2015

Nexus 5: b16-L / b2-M

Since M-preview sources on shamu were also working on Lollipop and improved idle drain and snappiness, I've also tried to merge the M-preview stuff into our Lollipop kernel. The kernel runs more than 24 hours on several devices and seems to run quite well. I've updated BFQ I/O sched and merged some little fixes for other subsystems on both releases (-L and -M). I still do two builds, since the -M kernel needs Selinux to be disabled to allow root, and the Lollipop kernel doesn't need that.

Changelog:
Lollipop:
-merged M-preview source
-updated BFQ
-merged little fixes here and there
M-preview:
-updated BFQ
-merged little fixes here and there

hC-b16-L

hC-b2-M

Have fun! (=

hells

Donnerstag, 11. Juni 2015

Nexus 6: ZEN or mako?

It seems to be the question of the week. I'll try to explain the differences in this post and how they can affect battery life.

ZEN uses zen decision hotplug. ZEN only onlines all cores on screen on, it also takes thermal events into account and wont online any core back, if you're under 15% battery, or currently have a thermal event, because of heat. So in the end it isn't a "real" hotplug driver, because it doesnt have any code for active hot plugging in it. That means you cant change its behavior.

mako uses mako hotplug. The mako kernel also comes with an all cores online setup, but you can change it to dual core on light tasks and quadcore for heavy tasks, if you higher the "load_threshold" from "0" to "80" for example.

So does that mean ZEN is for performance and mako for battery? There's no "real" answer to this question. You have to think about some points here:
Every time a core gets kicked in, there have some calculations to be made, which needs battery. Onlining a core also needs some battery every time. You're using your device and cores are getting kicked in and out, because you have some more idle phase and some more heavy load phase. It can also happen that the hotplug thinks its an idle phase right now, offlines cores and the governor has to higher the frequencies of the left cores to handle the load. After some time all cores are coming back and the frequency falls again. In the end it would've been more efficient to have all cores online during that period, because the load could've been handled with lower frequencies between all cores. Remember: All four cores online on a lower frequency is always better than having two cores online in high frequencies.

Remember also that even if all cores are online, it doesnt mean a core cant enter a battery saving idle state if it doesnt have anything to do. Online doesnt mean the core is active the whole time, it just doesnt get kicked out, which in the end is best for low latencies. The higher the idle state, the more time it needs to get active again. But its always faster than getting kicked out.

There's much misinformation about that setup in general. All cores online all the time can save some battery, because there are no calculations and onlining/offlining, which is a battery draining factor. In the end it depends on your usage, which setup is better for you. In some cases active hotplugging is the better choice, in some cases its better to run all cores without any active hotplug. YOU have to test, which suits YOU better.

UPDATE 09/12/15

Since I rebased my kernel, we are now able to switch between mako and ZEN in one kernel, by disabling the one and enabling the other.

Dienstag, 9. Juni 2015

Nexus 6: b7-t2 (Lollipop)

I've played around with some "M-preview" stuff and saw a nice improvement in interactivity and idle drain, so I decided to use the whole "M-preview" sources for Lollipop now. This release is basically b1-t2-M, without the SELinux hack to get root working on "M" and a little change in the anykernel template to use the correct offsets for the generated boot.img. I did a little idle test during the night and here's what I got:


Not bad, huh? ;) No airplane mode cheat or other tricks were used to achieve that. I'm using an unofficial SlimLP build by fraz14.

Changelog:
-based upon the rebased M-preview-sources test kernel
-reverted the SELinux hack to get root working on M
-added mako_hotplug build



Have fun! (=

hells

Montag, 8. Juni 2015

Nexus 6: b1-t2-M

I've played around with the M sources and added some little fixes for it. I've also made an "M" build with mako_hotplug.

Changelog:
-added some fixes for several subsystems (audio, video, gpu and mdss)
-added a mako_hotplug build

hC-b1-t2-M

hC-b1-t2-mako-M

Have fun! (=

hells

Nexus 4: b79

I didn't make anything new for mako for quite some time now. It seems b78 was as stable as the stable ones before. The problems I had between b73 and b78 were not related to the kernel as it seems. I don't blame anyone for thinking it could be a kernel related problem, because most of the time a SOD happens, its the kernel. I've added francos input listener and francos conservative back, because some people like it more than the conservative we had before. And with francos input listener the min_freq doesn't get changed, so no more "why my min freq is changing" questions anymore, yaaay ;)

Changelog:
-added back francos input listener
-added back francos conservative
-added input boost logic to hellsactive

hC-b79-L

hC-b79-CM

Have fun! (=

hells

Nexus 6: b1-t1-M

I did a complete rebase upon the Android "M" sources. I had to remove a few commits to boot without issues, but it shouldn't affect the kernel and user experience in any way :) Since I trained rebases a lot in the past, it was not that time consuming like it was in the beginning. This "M" kernel currently only has zen-decision without active hotplugging. I have plans to make a mako_hotplug "M" release in the next few days.

Changelog:
-rebased upon Android "M" sources

hC-b1-t1-M

Have fun! (=

hells

Nexus 6: b6

I've added some more mainline and upstream fixes for several subsystems. I'm very happy with the performance, idle drain and screen on drain on this kernel version. I got some reports about bad battery life, but I think it depends on the configuration and usage. I never stated I make a kernel for everybody. If it suits your need I'm more than happy, if it doesn't run nice, or causes battery drain you may need to look for a kernel that suits you better :)

Short explanation about the two kernel:

hC-b6 is shipped with mako_hotplug from franco and runs quadcore mode per default. You can change that behavior, if you higher the "load threshold" from "0" to "80" for example.

hC-b6-ZEN is shipped with zen-decision from bbedward. Its runs quadcore mode per default and doesn't give you the ability to change that behavior.

Changelog:
-compiled with UBERTC 5.1.1
-bcmdhd: wifi: updates from google bcmdhd repo
-suspend/power/wakeup commits from google common 3.10 repo
-various sched, cgroup, mm, und workqueue patches from upstream / Linux 4.0
-writeback fixes von Linux Mainline
-power efficient workqueues - Some non performance oriented tasks will choose an active core  instead waking up and idle core.
-slub/slab allocators synced with Linux 3.18
-merged lollipop 5.1.1 kernel sourcen
-some anykernel specific changes, simplyfied and fixed a thermal issue.

hC-b6

hC-b6-ZEN

Have fun! (=

hells

Nexus 5: b1-M

I merged the "M" sources and made a quick build. Its runs since a few days and seems to be stable.

Changelog:
-merged "M" sourcen

hC-b1-M

Have fun! (=

hells

Nexus 5: b15

I merged the 5.1.1 sources and added the input boost logic to hellsactive to work with the input listener. I think we're on a very good base for hammerhead.

Changelog:
-merged 5.1.1 sources
-added boost ability to hellsactive

b15-L

Have fun! (=

hells

Nexus 4: b78

I tested a lot of things between the last official build and b78 to get rid of the sleep of death issues. The funny part about this is the fact, it wasn't the fault of my kernel.

Changelog:
-Tested some things to fix stability issues

b78-L

b78-CM

Have fun! (=

hells

Sonntag, 7. Juni 2015

Welcome to my blog!

Hi guys,

Since there are many places where you can follow me, but none of them are really overseenable (or what do you call it, when people are asking me where to download the kernel IN the download section in my G+ community?) for some reasons.

So lets try it with a little blog for my work (=

hells