[KERNEL] [blu_spark r152] [Marshmallow 6.0.1 / Nougat 7.1.*]

Search This thread
There are no major modifications (none, actually) related to the kernel in the last factory image. I didn't even boot once with the stock kernel. I flashed stock and system images, booted into recovery, flashed blu_spark, cleared Cache and Dalvik-Cache and I booted into it. We are also Stagefright free, I tested with the app from the researchers that discovered the Stagefright bug.
 

yerfenuj

Senior Member
May 28, 2014
140
10
Hi i dont have my rom, i only have my delta update for cataclysm thats why i cant dirty flash. Is there any way i can flash blu spark without dirty flashing?
 

Maibol

Senior Member
Jan 9, 2011
496
127
OnePlus 7 Pro
Google Pixel 7
Does anyone here use Xmod with COC with this kernel?? Because its not working for me with bluespark, hellscore kernels. But working with elementalx, uber kernels.!! I know the answer am gonna get is its not kernel related. But i wanna know whether anyone got this problem with this kernel. ? ✌

ne❌us 5 --> pure ne❌us --> ❌TREMEMusic --> L Speed

xmod is working well here bro check your rom
 

xeraphael

Senior Member
Feb 9, 2012
313
113
No, it's not franco version. Mine has a couple upstream patches and that's about it.
I only work in blu_active which is my choice above anything else.

@eng.stk,

#1. The version of conservative you have included is awesome, I like that sampling_rate can be changed (unlike tons of other kernels that have it hardcoded at 200000), and that freq_step and freq_down_step are separate tunables too. If you could keep it updated with upstream that'd be really cool.

#2. Could you do the same for the interactive governor as well? Just keep up to date with upstream patches? Currently the above_hispeed_delay tunable for interactive cannot be modified, which makes it somewhat less useful than it could be.

#3. For blu_active, what does the low_load_down_threshold tunable do? Also, is there a way to modify the duration of input_boost_freq, or disable it entirely?

#4. I think I'm a fan of what you've done with blu_active. It really behaves like a cross between interactive and ondemand, unlike a lot of other custom governors for the N5 which seem to act a lot more like ondemand and favor the max frequency way too much for my liking. Right now I'm using blu_active for a performance-biased governor, conservative for balanced, and hopefully interactive for battery, if you can update it.
 

Arstoien

Senior Member
Oct 31, 2012
1,438
1,508
@eng.stk,

#1. The version of conservative you have included is awesome, I like that sampling_rate can be changed (unlike tons of other kernels that have it hardcoded at 200000), and that freq_step and freq_down_step are separate tunables too. If you could keep it updated with upstream that'd be really cool.

#2. Could you do the same for the interactive governor as well? Just keep up to date with upstream patches? Currently the above_hispeed_delay tunable for interactive cannot be modified, which makes it somewhat less useful than it could be.

#3. For blu_active, what does the low_load_down_threshold tunable do? Also, is there a way to modify the duration of input_boost_freq, or disable it entirely?

#4. I think I'm a fan of what you've done with blu_active. It really behaves like a cross between interactive and ondemand, unlike a lot of other custom governors for the N5 which seem to act a lot more like ondemand and favor the max frequency way too much for my liking. Right now I'm using blu_active for a performance-biased governor, conservative for balanced, and hopefully interactive for battery, if you can update it.

For #3, use boostpulse_duration. That controls the length of the input_boost
 
  • Like
Reactions: xeraphael

BlazeForth

Senior Member
May 19, 2013
1,130
340
Ernakulam(Kochi)
@eng.stk hey bro, need your help. Is there anyway i could improve performance of the kernel. Using blue_active governer, and under heavy usage i feel a lot lag here and there when using multiple apps. I even changed thermal throttling temp to 90°C. But still i have lag. It happens only when heavy multitasking like fb, coc, whatsapp, hike, google+ etc....? ✌
 

Mrcactuseater

Senior Member
@eng.stk hey bro, need your help. Is there anyway i could improve performance of the kernel. Using blue_active governer, and under heavy usage i feel a lot lag here and there when using multiple apps. I even changed thermal throttling temp to 90°C. But still i have lag. It happens only when heavy multitasking like fb, coc, whatsapp, hike, google+ etc....? ✌
Have you tried clearly dalvik and cache?

Sent from my Nexus 5 using Tapatalk
 

pianistaPL

Senior Member
Feb 15, 2012
2,301
1,249
Poznań - Poland
@eng.stk hey bro, need your help. Is there anyway i could improve performance of the kernel. Using blue_active governer, and under heavy usage i feel a lot lag here and there when using multiple apps. I even changed thermal throttling temp to 90°C. But still i have lag. It happens only when heavy multitasking like fb, coc, whatsapp, hike, google+ etc....? ✌
Try to change blu_active settings like on the screenshot uploadfromtaptalk1442178390978.png
 
  • Like
Reactions: BlazeForth

republicano

Senior Member
Mar 11, 2010
998
248
@eng.stk hey bro, need your help. Is there anyway i could improve performance of the kernel. Using blue_active governer, and under heavy usage i feel a lot lag here and there when using multiple apps. I even changed thermal throttling temp to 90°C. But still i have lag. It happens only when heavy multitasking like fb, coc, whatsapp, hike, google+ etc....? ✌

I had the same problem, I changed the hispeed freq,input freq, high speed load in kernel adiutor, but underclocked to 1.7ghz,basically changed the settings to make it easier to reach a higher frequency without generating more heat.

I had lag when the cores were parked and frequency was low, when I multi tasked or pressed the home button there would be a long delay and lag when in the app draw,
 
  • Like
Reactions: BlazeForth

BlazeForth

Senior Member
May 19, 2013
1,130
340
Ernakulam(Kochi)
I had the same problem, I changed the hispeed freq,input freq, high speed load in kernel adiutor, but underclocked to 1.7ghz,basically changed the settings to make it easier to reach a higher frequency without generating more heat.

I had lag when the cores were parked and frequency was low, when I multi tasked or pressed the home button there would be a long delay and lag when in the app draw,
Thanx bro. ? ☺
Try to change blu_active settings like on the screenshot View attachment 3472741
Thanx bro, testing it now. ? ✌

ne❌us 5 --> pure ne❌us --> ❌TREMEMusic --> L Speed
 

eng.stk

Senior Member
Mar 29, 2011
7,357
61,790
Google Pixel 4a
OnePlus 9 Pro
@eng.stk,

#1. The version of conservative you have included is awesome, I like that sampling_rate can be changed (unlike tons of other kernels that have it hardcoded at 200000), and that freq_step and freq_down_step are separate tunables too. If you could keep it updated with upstream that'd be really cool.

#2. Could you do the same for the interactive governor as well? Just keep up to date with upstream patches? Currently the above_hispeed_delay tunable for interactive cannot be modified, which makes it somewhat less useful than it could be.

#3. For blu_active, what does the low_load_down_threshold tunable do? Also, is there a way to modify the duration of input_boost_freq, or disable it entirely?

#4. I think I'm a fan of what you've done with blu_active. It really behaves like a cross between interactive and ondemand, unlike a lot of other custom governors for the N5 which seem to act a lot more like ondemand and favor the max frequency way too much for my liking. Right now I'm using blu_active for a performance-biased governor, conservative for balanced, and hopefully interactive for battery, if you can update it.

low_load_down_threshold is a threshold in which under it , cpu doesn't scale: let's say it's 10, if load is under 10% cpu freq will not scale. Improves low freq jitter.
you can change the input boost duration chaqnging boostpulse_duration. You can disable input boost making input_boost_freq to 300000
 

eng.stk

Senior Member
Mar 29, 2011
7,357
61,790
Google Pixel 4a
OnePlus 9 Pro
blu_spark r25

All right crew!
New build is up, go get it!

  • msm: mdss: KCAL: Send a pp display commit when changes are made (thanks @savoca)
  • PM: Fix a bug in dpm_suspend_late()
  • lz4: fix system halt at boot kernel on x86_64
  • Makefile: sort list of defconfig targets in make help output
  • kbuild: remove warning about "make depend"
 

Top Liked Posts

  • There are no posts matching your filters.
  • 767
    DWHxIK

    Kernel features:
    • Build with custom toolchain blu_naro-7.2 (cortex-a15 neon-vfpv4 hard-float targeted, build with latest Crosstool-NG from developer snapshot Linaro GCC 7.2-2017.10)
    • Full -O3 support with device and target flags enhanced, linaro build improvements, etc
    • Less is more: stockish builds based on android-msm-hammerhead-3.4-marshmallow-mr3
    • Kernel compressed with XZ, custom tweaked RAMdisk with GZIP (faster boot times)
    • Removed some debug and logging options
    • Enhanced performance and battery patches
    • Several CPU Governors (blu_active own governor is default- fastlane mode available!)
    • Voltage Control UV_mV_table (UV down to 700mV possible)
    • Enhanced TCP methods (westwood is default), Network and Wifi tweaks
    • Several I/O control (added FIOPS and ZEN is default), tweaked filesystems (F2FS, ExFAT, NTFS & CIFS available)
    • Disabled stock mpdecision and thermald
    • blu_plug: Dynamic hotplug for hammerhead
    • msm_thermal simple driver (default 65º C threshold)
    • Optimized RWSEM, AES and SHA1 routines (with neon support)
    • Vibrator Strength tunable (60% default)
    • KGSL fixes and reworked GPU driver (removed doubled freqs, goes to idle @ 27MHz), Simple GPU Governor by default
    • Gamma Control and KCAL - Advanced color control for Qualcomm MDSS (RGB calibration and post-processing features)
    • Backlight dimmer ready (disabled by default, tuned min manual brightness - level 3)
    • Wakelock blockers available
    • USB automount (ROM must support it, otherwise use stickmount)
    • CDROM emulation added to mass_storage (Drive Droid compatible)
    • Kexec (multirom) full support
    • doubletap2wake available (0:disabled, 1:enabled, 2:enabled fullscreen), option to disable with power button or after wake_timeout
    • USB Fast Charge (USB mode up to 900mA with MTP, Increase battery charging current to use higher input current on AC mode, proprietary charger detection
    • init.d support (put your scripts in /system/su.d or /su.su.d [systemless SuperSU], /magisk/.core/post-fs-data.d [Magisk])
    • Compatible with Kernel Adiutor, Universal Kernel Manager and others

    DOWNLOAD KERNEL ZIP (no mirrors please)


    Warning: If you come from other kernel, you should dirty flash your ROM before flashing blu_sp★rk zip to avoid problems.
    Also uninstall or clean data of any kernel control app you're using.

    About bugs and troubleshoots: don't bother to post if a log isn't ready or without steps so the behavior can be replicated. Also, I only actively support stock ROM with NO mods whatsoever (apart from root).
    No support will be given to custom ROM including N stuff, so don't clutter the thread with it (specially):
    • No talking about WiFi and N issues.
    • No talking about ROM related and misc N issues.
    Save the SOT and battery stats/screenshots for general threads, here we deal with development, not personal tastes and results.
    Also no OT about OTAs, apps, ROM bugs and other userspace stuff. There's threads for it, use them.


    This kernel installer modifies your filesystem, backup your boot.img with TWRP if you want to go back to full stock (or you can fastboot boot.img or dirty flash your ROM also)


    If you want to use F2FS, do the following (backup your data before attempt this, it will erase all your Data)
    • Flash TWRP with f2fs support and flash latest blu_sp★rk zip
    • Go to Wipe -> Advanced Wipe -> Select only Data -> Repair/Format File system -> Change partition type to F2FS
    • Go to Wipe -> Advanced Wipe -> Select only Cache -> Repair/Format File system -> Change partition type to F2FS
    • Reboot and profit


    pp-acceptance-medium.png

    If you like my work, donations are always welcome (but not mandatory).
    Don't forget to hit thanks, it's free ;)


    XDA:DevDB Information
    blu_spark hammerhead, Kernel for the Google Nexus 5

    Contributors
    eng.stk
    Source Code: https://github.com/engstk/hammerhead

    Kernel Special Features: powered by sparky

    Version Information
    Status: Stable
    Current Stable Version: r152
    Stable Release Date: 2017-11-23
    Current Beta Version: r141
    Beta Release Date: 2017-09-13

    Created 2015-08-10
    Last Updated 2019-11-29
    137
    blu_spark r40

    All right crew!
    New build is up, enjoy :)

    • audit: Mute userspace and kernel audit logs (goodbye nasty task exit spam)
    • net: fix iterating over hashtable in tcp_nuke_addr()
    • Input: optimize events_per_packet count calculation
    • tcp_cubic: fix the range of delayed_ack
    • tcp: fix timing issue in CUBIC slope calculation
    • Reverted moto LMK merges

    Don't forget to hit thanks ;)
    133
    blu_spark r35

    All right crew!

    New build is up, enjoy :)

    • lowmemorykiller: squash task adj rbtree optimization from Motorola
    • input: Don't reset keys pressed at suspend time from Atlantis
    • tcp_cubic: do not set epoch_start in the future, better follow cubic curve after idle period
    • Improvements on RAMdisk and install routines

    Don't forget to hit thanks ;)
    131
    blu_sp★rk r51

    All right crew!

    New update is up, some nice goodies inside, go get it.

    • makefile: use blu_naro cortex-a15 neon-vfpv4 hard-float toolchain (build with latest Crosstool-NG from developer snapshot Linaro GCC 5.3-2015.12)
    • sched/rt: Reduce rq lock contention by eliminating locking of non-feasible target
    • sched/core: Fix an SMP ordering race in try_to_wake_up() vs. schedule()
    • sched: Fix RLIMIT_RTTIME when PI-boosting to RT, Queue RT tasks to head when prio drops, Fix race in idle_balance()
    • sched/fair: Stop searching for tasks in newidle balance if there are runnable tasks
    • msm: camera: sensor: Change wait func to wait_for_completion_timeout
    • proc: actually make proc_fd_permission() thread-friendly, make proc_fd_permission() thread-friendly
    • futexes: Increase hash table size for better performance
    • mm/slub: don't wait for high-order page allocation
    • fs/buffer.c: increase the buffer-head per-CPU LRU size
    • ASoC: pcm: If pmdown_time is zero then shut down DAPM immediately
    • net: wireless: bcmhd: Serialize wl_notify_escan_complete
    • ARM: msm: hammerhead: Check completion status on vote for resume, Ignore watchdog init if device is interactive
    • net: wireless: bcmdhd: Do not process partial resume on bus reset, Fix suspend failure due to wakelock/wakeunlock mismatch, Ensure watchdog thread isnt called on bus reset, fix for watch dog issue in wifi connect test
    • cpufreq: ondemand: even if it's not being used it spawns uninterruptible threads equal to the num
    • wakeup: Add the guard condition for len in pm_get_active_wakeup_sources
    • timer: Prevent overflow in apply_slack
    • bluetooth: Validate socket address length in sco_sock_bind().
    • net: add validation for the socket syscall protocol argument
    • md: use kzalloc() when bitmap is disabled
    • ipv6: addrconf: validate new MTU before applying it
    • pagemap: do not leak physical addresses to non-privileged userspace

    If you like my work, don't forget to hit thanks :good:
    123
    Code_Blue r923

    All right crew!

    Back to the heavyweight jam :angel:
    I decided to reopen the thread after some thinking and some nice talks I had with several people.
    I do this for fun, so behave and don't make me regret it.

    This is for Lollipop 5.1 ROMs only.

    The zip uses anykernel installer, this means it uses previously installed ROM kernel Ramdisk.
    If already have Code_Blue or ROM default kernel installed just flash over.
    If you come from other kernel dirty flash you ROM and flash Code_Blue after.

    Changelog: http://goo.gl/tyW8lf

    Keep it real, keep it true, keep it #Code_Blue