[KERNEL] Bricked-Kernel Hammerhead | Sweep2wake | KnockKnock/Dt2w

Search This thread

DeepSleep85

Senior Member
Jul 11, 2013
81
66
0
Which kernel version, impressive though

Sent from my Nexus 5 using Tapatalk

I'm on the latest stable (3/26).
I'm running 2hr 30min SOT at 70% and expect to hit 7hrs SOT for the first time.
Haven't changed my usage patterns and my record was a little over 6 with heaving tweaking of franco kernel.
Definitely impressed with mostly default settings and the performance I am seeing as well as the battery life.
:good:

---------- Post added at 08:38 PM ---------- Previous post was at 08:23 PM ----------

Definetly disappointed in this kernel. Battery life essentially cut in half. Flash over stock last night. Nothing's changed with my usage. after a 12 hour day I'd get home with at least 30%. Today I barely get home with 5%. I used to not have to charge until late at night maybe 11p or midnight. Before I'm under 10%. Screen on time is now 2 hours. Down from almost 5. Only extras I've enabled is the dt2w. Nothing else. Unless dt2w is the culprit iono what is. But I guess I'm gonna go back to stock. Is there a break in period or something? Why would it be this much of a drop off if my usage has not changed at all. I actually used it less once I noticed by midday it was at 55%!

Please test turning dt2w off if you are going to compare this kernel to stock.

55258d1390503550t-son__i_am_disappoint_by_soniamdisappointplz.jpg
 
  • Like
Reactions: PetritH

Mo'HAWK

Senior Member
Feb 16, 2013
237
78
0
Dt2w never helps as it keeps the digitizer on to detect touches. Also you must have a bad signal or syncing apps that don't help you either.

Sent from my Nexus 5 using XDA Premium 4 mobile app
 

malibu_23

Senior Member
May 18, 2007
959
115
0
Chicago
Dt2w never helps as it keeps the digitizer on to detect touches. Also you must have a bad signal or syncing apps that don't help you either.

Sent from my Nexus 5 using XDA Premium 4 mobile app

I actually use my phone, bt, wifi, google now, games, Instagram. Like I said I hit 5h SOT on stock regularly. Tmobile so my signal is LTE 90% of the time. Just surprised at the first day on this new kernel. HARD TO BELIEIVE THE DROP OFF. I'm giving it another day. But without the dt2w there's no point for me.
 

Mo'HAWK

Senior Member
Feb 16, 2013
237
78
0
I actually use my phone, bt, wifi, google now, games, Instagram. Like I said I hit 5h SOT on stock regularly. Tmobile so my signal is LTE 90% of the time. Just surprised at the first day on this new kernel. HARD TO BELIEIVE THE DROP OFF. I'm giving it another day. But without the dt2w there's no point for me.

Got ya. Honestly you may need to tinker with some of the settings of the kernel to tune it to your usage as that can make a difference. Plus many devices react differently to different kernel and ROM combinations.

Hope this one works for you as the Dev is a great person along with this forum.

Sent from my Nexus 5 using XDA Premium 4 mobile app
 

DeepSleep85

Senior Member
Jul 11, 2013
81
66
0
I actually use my phone, bt, wifi, google now, games, Instagram. Like I said I hit 5h SOT on stock regularly. Tmobile so my signal is LTE 90% of the time. Just surprised at the first day on this new kernel. HARD TO BELIEIVE THE DROP OFF. I'm giving it another day. But without the dt2w there's no point for me.

Stock doesn't have dt2w. Why would you expect the same results for this kernel with it active? Again if you want to compare performance to stock, disable dt2w and see what your SOT is like with your usage.

Sent from my Nexus 5 using xda app-developers app
 
  • Like
Reactions: show-p1984

malibu_23

Senior Member
May 18, 2007
959
115
0
Chicago
Stock doesn't have dt2w. Why would you expect the same results for this kernel with it active? Again if you want to compare performance to stock, disable dt2w and see what your SOT is like with your usage.

Sent from my Nexus 5 using xda app-developers app

That's what I'm doing on day two. Just wasn't expecting that huge of a drop off. I understand that extra stuff shaves off some battery life. Just wasn't expecting it to shave off half. :p
 

ganeshp

Senior Member
Mar 15, 2012
5,499
3,262
253
Hyderabad
That's what I'm doing on day two. Just wasn't expecting that huge of a drop off. I understand that extra stuff shaves off some battery life. Just wasn't expecting it to shave off half. :p


That's the problem with dt2w and s2w features in n5. The digitizer need to be on for them to work all the time. As you want dt2w without loss of much battery I would advise you to try elementalx kernel (before anyone fires on me chill down guys I still use bricked and I'm only advising based on his requirements )

It has some nifty optimisations for the dt2w ..like using the power button to turn off the phone will disable the dt2w temporarily and once you wake it up the dt2w wake will be available again. Timeout for dt2w option ..like after 30 minutes dt2w will get automatically disabled ..this will help during nights where you not going to use the phone

Sent from my Nexus 7 using Tapatalk
 
  • Like
Reactions: hooliganx

hooliganx

Senior Member
May 22, 2008
2,685
2,483
193
Brasília
@ganeshp
I try elementalx for weeks... this features is really very nice and is a good kernel.
but I still have better SOT and battery life with Bricked!
@malibu_23
review your installation and try again...
I use my HH for work. lot of whatsapp, excel, email, sms, calls, wunderlist, music, 3G....
and use since 05h30 to 23h00!
and almost every day have more than 6h SOT.

and... use a lot s2w. ;)

N5*SlimKat.b3.8*bricked.exp-cf73f13*ART*TWRP.2.7*0.23
 

spr33

Senior Member
Jan 10, 2007
644
110
63
Staffordshire
@ganeshp
I try elementalx for weeks... this features is really very nice and is a good kernel.
but I still have better SOT and battery life with Bricked!
@malibu_23
review your installation and try again...
I use my HH for work. lot of whatsapp, excel, email, sms, calls, wunderlist, music, 3G....
and use since 05h30 to 23h00!
and almost every day have more than 6h SOT.

and... use a lot s2w. ;)

N5*SlimKat.b3.8*bricked.exp-cf73f13*ART*TWRP.2.7*0.23

Do you use any particular setup or do you leave kernel settings as default?

Sent from my Nexus 5 using Tapatalk
 

ralpheboyo

Senior Member
Nov 7, 2005
1,630
2,654
0
Planet Earth?
Dam... This kernel is something else especially with kcontrol... Getting splinters in my fingers from scratching my head with all the tweaks.. Will take some time... To perfect my tune Up.... (^o^)... Will not compare to my favourite kernel but this one just rocks as well...

Sent from my Nexus 5 using Tapatalk
 

Mo'HAWK

Senior Member
Feb 16, 2013
237
78
0
Dam... This kernel is something else especially with kcontrol... Getting splinters in my fingers from scratching my head with all the tweaks.. Will take some time... To perfect my tune Up.... (^o^)... Will not compare to my favourite kernel but this one just rocks as well...

Sent from my Nexus 5 using Tapatalk

What is your favorite as I have used Franco, faux, Trinity, elementalx etc. And I keep coming back to this one due to it's customizability. To me the custom kernel scene is pretty even as you might have little gains here and there but now I have started looking at the Devs personality and @show-p1984 is a stand up one to say the least.

Sent from my Nexus 5 using XDA Premium 4 mobile app
 
  • Like
Reactions: yogi217

tanjiajun_34

Senior Member
Aug 24, 2010
738
131
0
Sorry but where is the f2fs version of the kernel? I flashed the normal version and it just stuck on "Type password to decrypt storage"

I tried the bricked_hammerhead_20140331_050519 build.
 
Last edited:

PetritH

Senior Member
Mar 3, 2011
4,174
2,556
253
Somewhere
When I try to download it sends me to bricked. de homepage.. can someone upload latest stable for me, wanna flash it to my bro's n5

Sent from my Nexus 5 using Tapatalk
 

DeepSleep85

Senior Member
Jul 11, 2013
81
66
0

Attachments

  • Screenshot_2014-04-02-15-17-56.png
    Screenshot_2014-04-02-15-17-56.png
    205.4 KB · Views: 600
  • Screenshot_2014-04-02-15-17-59.png
    Screenshot_2014-04-02-15-17-59.png
    94.6 KB · Views: 608
  • Screenshot_2014-04-02-15-18-03.png
    Screenshot_2014-04-02-15-18-03.png
    117.6 KB · Views: 592

Top Liked Posts

  • There are no posts matching your filters.
  • 313



    Welcome to the most customizable N5 kernel on xda :)
    Bricked-Kernel Nexus 5 (hammerhead)

    Features:

    * Based upon Google's msm 3.4 source
    * Various fixes, improvements and optimizatios (look @ github)
    * Compiled with gcc4.7.2 toolchain (linaro 09.12)
    * -O3+ optimized
    * Snapdragon & CortexA15 optimizations
    * replaced qcom's hotplug binary with msm_mpdecision (IN-KERNEL, better battery life + performance)
    * Extensive sysfs interface for mpdecision with all the tuneables you want (/sys/kernel/msm_mpdecision/)
    * replaced qcom's thermal binary with my IN-KERNEL solution. (/sys/kernel/msm_thermal/)
    * export krait version to: /sys/kernel/debug/krait_variant
    * Allow OC up to 2,5Ghz
    * Allow UC to 96Mhz
    * Undervolting (faux123)
    * F2FS Support
    * Multirom Support
    * KCAL (savoca) & Gamma Control (faux123)
    * Sound Control (faux123)

    * Default clocks: 300 Mhz min & 2265,6 Mhz max

    Zip features:
    *** ON-THE-FLY-RAMDISK EDITS!
    *** THIS KERNEL USES YOUR RAMDISK, it will just modify it on the fly while flashing. These changes are not creating any incompatibilities with roms/other kernels.
    * removes min freq overrides from the ramdisk
    * removes governor overrides from the ramdisk
    * adds init.d support to your ramdisk (if not already supported)
    * modifies stock ondemand settings
    * add module insertion

    Check the compare links for the rest :)

    Where is tha Changelog???

    There will be no more changelogs.
    Instead the download pages were outfitted with compare links to github for each download.

    What is sweep2wake?

    Disabled as default, activate through an app like KControl or over sysfs: echo 1 > /sys/android_touch/sweep2wake

    What is doubletap2wake / knock knock?

    Disabled as default, activate through an app like KControl or over sysfs: echo 1 > /sys/android_touch/doubletap2wake

    How to install?

    Flash through recovery. #done.


    Where to complain about errors/bugs?

    Please use the Issuetracker for bugs/errors/feature wishes!
    Issuetracker @ https://github.com/showp1984/bricked-hammerhead/issues


    [email protected]
    IRC Chat: Freenode IRC #bricked

    Download:

    No Guarantees! If it kills your grandmother or your device, I am NOT responsible! If you understand this:
    (If you download, please hit Thanks below my post! Thank you!)

    >>> DOWNLOAD <<<



    Donation Hall-of-Fame:

    > Hall of fame <

    Thank you very much!


    Stock 4.4 Nexus5 boot.img - flash this if you come from another kernel coming with it's own ramdisk (eg: zip contains a *.img file) ONLY FLASH ON 4.4

    Source:


    65
    What is msm_thermal?

    Kernel based 3-phase thermal control!
    This replaces your /system/bin/thermal-engine-hh binary which is renamed by the installer to thermal-engine-hh_bck.
    It will throttle your cpu speed to keep it cool and unleash it if the cpu has cooled down enough. (3 phases: low, mid and high)

    Check /sys/kernel/msm_thermal/conf/ for the thermal configuration :)

    allowed_max_high = highest threshold (phase 3)
    allowed_max_low = remove the throttling if we cooled down to this (clr_thrshold)
    allowed_max_freq = max frequency if throttled (limit)

    [...]mid[...] = same as above, just for phase 2
    [...]low[...] = Lowest threshold (phase 1)

    check_interval_ms = how often shall we check? (sampling rate)

    shutdown_temp = if we reach this shut down the device!

    If you want to see msm_thermal doing it's job:
    Code:
    adb shell
    cat /proc/kmsg | grep 'thermal'
    What is msm_mpdecision?

    100% kernel based multi core decision! (should cpu1/2/3 be online or not?)
    This replaces your /system/bin/mpdecision binary which is renamed by the installer to mpdecision_bck.

    Check /sys/kernel/msm_mpdecision/conf/ for the configuration.

    startdelay = time until mpdecision starts doing it's magic (20000)
    delay = time between checks (130)
    pause = if something else plugs in the cpu, fall asleep for 10000ms (10 secs)
    scroff_single_core = if the screen is off, don't plug in cpu1/2/3. Additionally: Unplug all cpus except cpu0 when screen is turned off (1)
    enabled = enable(1) or disable(0) mpdecision. This does not affect scroff_single_core!
    min_cpus = min cpus to be online, cannot be < 1. Default: 1
    max_cpus = max cpus to be online, cannot be > 4. (if you set it to 2 and min_cpus to 1 you will basically have a dualcore) Default: 4
    idle_freq = a value against that will be checked if a core +/- is requested. (499200)
    If cpu0 is below that value and a core up of another cpu is requested, nothing will happen.
    If any other cpu is above that value and a core down of that cpu is requested, nothing will happen. (otherwise it would now put down that cpu even though it is still working, which isn't what we want)


    Hot plug thresholds (aka now it gets 'complicated')
    This small formula calculates which value will be used: (number_of_cpus_online - 1) * 2
    The result of this formula will be the nwns_threshold where a new cpu is hotplugged.
    The result of this formula + 1 will be the nwns_threshold where a cpu is unplugged.

    nwns_threshold_x = runqueue threshold, if this is reached cpuX will be hot/unplugged
    twts_threshold_x = time threshold, this amount of time must have passed for the related action to be taken (hot/unplug)

    Example:
    One cpu is online.
    (1 - 1) * 2 = 0 ergo:
    nwns_threshold_0 = cpu1 will be hotplugged at this value
    ((1 - 1) * 2) + 1 = 1
    nwns_threshold_1 = cpu0 will be unplugged at this value
    Since we can't unplug cpu0 this is '0'.

    Two cpus are online.
    (2 - 1) * 2 = 2 ergo:
    nwns_threshold_2 = cpu2 will be hotplugged at this value
    ((2 - 1) * 2) + 1 = 3
    nwns_threshold_3 = cpu1 will be unplugged at this value

    etc...

    Some values are:
    NwNs_Threshold: 12, 0, 25, 20, 32, 28, 0, 35
    TwTs_Threshold: 140, 0, 140, 190, 140, 190, 0, 190
    Where the position and function of the number equals the result of the above explained formula.

    (all times are in ms)
    If you want to see the mpdecision magic happening:
    Code:
    adb shell
    cat /proc/kmsg | grep 'MPDEC'
    mpdecision's input event boost, aka project butter :p

    This will boost your min cpu speed if you touch the screen or press a button and gives you full control.
    In those events the min cpu freq will be risen to a predefined value (look below) on every online cpu. This boosts overall reaction times and smoothness a lot. (works similar to the qcom mpdecision binary)
    Configuration files:
    [email protected]:/sys/kernel/msm_mpdecision/conf # ls | grep boost
    boost_enabled
    boost_freqs
    boost_time

    All of them work like the usual sysfs files, except one special case:
    boost_freqs will list all frequencies from cpu 0 to cpu x. Cpu 3 and any following cpu will share one frequency.
    To change those frequencies echo the cpu number + the frequency in khz.
    Example: To change the boost freq of cpu3 (and 4,5,6,7,8, etc) the echo would look as follows:
    Code:
    echo "3 960000" > /sys/kernel/msm_mpdecision/conf/boost_freqs
    for cpu0:
    Code:
    echo "0 960000" > /sys/kernel/msm_mpdecision/conf/boost_freqs

    Defaults:
    Code:
    cat /sys/kernel/msm_mpdecision/conf/boost_freqs
    960000
    960000
    729600
    576000
    Why do I have no WLAN?

    Due to this kernels very high optimization settings it is too big for our boot.img with WLAN included into the kernel, so it is built as a module. That means it needs to be inserted into the kernel upon boot up, which needs to be automated for maximum comfort.

    The zip adds module insertion to your ramdisk, if that fails for some reason the wlan module cannot be inserted.

    if
    Code:
    adb shell lsmod
    doesn't show this:
    Code:
    tun 14701 0 - Live 0x00000000
    cifs 275399 0 - Live 0x00000000
    bcmdhd 2964650 0 - Live 0x00000000 (C)
    Then something went horribly wrong.
    Chances are that I broke it and this should never happen.
    One post in the issue tracker will probably fix it with the next release :)

    You can restore wlan for your current bootup by executing:
    Code:
    adb shell
    su
    insmod /system/lib/modules/bcmdhd.ko
    Is there an app available to customize this pure bodacious and awesome kernel?

    Yes there is: KControl. It's in the Google Playstore.


    45
    New Kernel beta :)

    Download:
    http://bricked.de/index.php?action=kdownload&device=hammerhead&release=beta&type=aosp

    Changes:
    https://github.com/showp1984/bricked-hammerhead/compare/ca9faf4...9ef2634

    A small KControl backport is to follow, so that color control will be enabled on the Hammerhead. (Sound already is)


    -------------------------------------


    The source now contains a fully fledged one command compile script.

    Ubuntu dependencies:
    Code:
    sudo apt-get build-dep linux-image-$(uname -r)
    (This should install most of what is needed to build any kernel)
    Code:
    sudo apt-get install ccache xz-utils git
    (This installs the ccache, a compiler cache, xz compression utils & the version control system git)

    Downloading the source:
    Code:
    mkdir ~/WORK
    cd ~/WORK
    git clone -b exp https://github.com/showp1984/bricked-hammerhead.git

    Building the source:
    Code:
    cd ~/WORK/bricked-hammerhead
    . buildme.sh exp
    (currently only exp has the build script though, since it's still all beta over here. This will change soon, then you can choose between master = stable and exp = beta)
    This script will download the toolchain, prebuilts and kcontrol gpu module source used and generate a flash-able zip at the end of the compilation as well as check-sums.
    It will ask you if you want to create the out directory, if you say n or N here it will be disabled. If you say y or Y however you will find everything in ~/WORK/bricked-hammerhead/out after compilation has finished.

    So if you have a linux machine, have fun. If you don't, well, it's as good as a time as any to download a distribution and get cracking! :)
    40
    Has anyone actually demonstrated (scientifically or otherwise) anything wrong with the qcom mpdecision binary? Im not taking anything away from kernel developers who write their own mpdecision (especially those who also provides sources), but I am curious as to whether they are actually better than those provided by qcom. Surely they know more about the capabilities of their own cpus better than anyone no?

    It's not that complicated (there is no black voodoo magic), that's why bricked kernel was the first to introduce this feature back on the pyramid.
    CPUs need to be plugged in / unplugged based on load, there is nothing more qcom can know that we can't also see inside of the kernel.

    There is one HUGE thing that is wrong with qcom's mpdecision: It's closed. It's a black box. We don't have any idea what is going on in there. Literally, none. It's not even configurable. It could contain secret nsa code, or send dirty sms to your girlfriend (who might actually enjoy that, idk...)
    If we would have source, hell, awesome. I wouldn't have spent over a year (first commit: Date: Thu, 21 Jun 2012 06:06:47 +0200, see here) to get my msm_mpdecision solution to the point where it is a) awesome and b) a lot better than the binary. It can be configured in any way you might need to. It features statistics on how often and how long a cpu is hotplugged. It has the input event boost. It's the full package deal.

    If you compare my kernel with the stock kernel you will see huge performance improvements and battery savings on bricked. Those are not only because of my msm_mpdecision but certainly related. Furthermore: we can completely customize it, over sysfs, on a running kernel, without reflashing.
    That's what I would have expected from qcom in the first place.

    Another thing wrong with qcom's binary: It's static. Meaning: If you change your min freq on stock it will always reset back to defaults. Same with their thermal binary. That's just annoying.
    msm_mpdecision will notice it if you change your min frequency and dynamically work with that from there on. It will also prevent hotplug wars between apps and it: eg: an app plugs in cpus to grab some cpu data (like frequencies, etc. That is only available if the cpu is plugged in). Qcom's mpdecision would now raise hell to keep that cpu unplugged, my msm_mpdecision just sits back and chills for 10 seconds to avoid those wars. (again, even that delay is fully configurable)

    There are also a bunch of boring advantages as to why it is better to let something crucial to the system run in kernel space and not in user space, but that would most certainly explode the context of this thread by the factor of 4.

    My solution is not inferior to that binary in any way, in fact it has been vastly superior in my testing up until now, otherwise I would a) improve it or b) ditch it. I don't keep around bad stuff just for the point of having it or because I wrote it. If it sucks I will say that and act accordingly.
    36
    Showp is my favorite Kernel dev. Used his kernel on all my phones (Sensation and One S). Was using Bricked on N5 until the battery light stopped working with SlimKat. SlimKat's stock kernel has some commit by Showp, though, which is great.

    Have been waiting for update for a while, now.

    Not asking for ETA. And I know Showp has been dealing with some personal matters but I have a feeling that it might either take a long time before Showp's back, or maybe even never.

    Anyway, I wish Showp all the best. If he decides to come back, I will try his kernel in a heartbeat!
    ill-be-back-quote.png
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone