Flash whatever rom you are running again, that will restore the boot.img. Then flash root if needed and Blu_Spark. No need to factory reset, you will keep apps and data this way. I usually keep the boot.img from whatever rom I have handy in case I need to restore it for some reason.
Accidentally left my screen on last night and it was chilling in the morning!
blu_spark for life!!! [emoji109]
blu_spark for life!!! [emoji109]
Happy Holidays for the blu_crew!
https://www.xda-developers.com/com-interview-eng-stk-blu-spark-kernel-1/
https://www.xda-developers.com/interview-eng-stk-blu-spark-kernel-2/
Phunk me, I'm famous ;p
https://www.xda-developers.com/com-interview-eng-stk-blu-spark-kernel-1/
https://www.xda-developers.com/interview-eng-stk-blu-spark-kernel-2/
Phunk me, I'm famous ;p
Attachments
-
blu_tree.jpg
Great interviews, it has been really interesting to read them! And good work
Happy holidays to you too
Congrats for being interviewed. Interesting to read on! Anyways, your kernel really rocks!
Can I use this kernel with latest AOSPA 7.3.1? Its a CAF ROM.
Great interviews, it has been really interesting to read them! And good work
Happy holidays to you too
Thanks for being supportive guys, this keeps the spirit alive
Stock ROM and LOS 14.1 for testing.
Sent from my blu_spark'd OP5
Can i flash this kernel over resurrecting remix 5.8.5(Nougat 7.1.2) in my moto g ( falcon)
Nope, kernel is device dependent.
This is only for this device.
Sent from my blu_spark'd OP5
Settings still not applying after reboot. I always manually adjust kernel everytime I reboot.
And you should be doing some digging on your own since it applies just fine for everybody else.
Anyways:
1- What settings specifically are you talking about?
2- How are you setting them? App/script? If app, Apply on boot checked?
3- What ROM?
Apply on boot works as expected no matter how I set it up. KA, ExKM, scrypt.
Double check you process.
Last edited:
I'm running the latest LOS 14, and with stock kernel it is very smooth and works perfectly.
But as soon as I install BluSpark, the phone gets slower and slower of the next couple of hours, until even opening the app-drawer takes 5 seconds.
After a reboot, everything is back to normal. Until is gets slower again.
It doesn't matter what settings I choose - happens even with stock settings.
But as soon as I install BluSpark, the phone gets slower and slower of the next couple of hours, until even opening the app-drawer takes 5 seconds.
After a reboot, everything is back to normal. Until is gets slower again.
It doesn't matter what settings I choose - happens even with stock settings.
You're using a phone with 2GB of RAM, deal with it.
You can tune LMK to your own needs, it had been discussed several times.
Sent from my blu_spark'd OP5
Thank Eng, for giving a direction to look at.
I was just curious why there is no problem at all when using the stock LOS kernel.
Same problem for me, I have just do a clean flash to see if there was related to a specific app. I my case sometimes after getting slower and slower the phone reboots itself.
This did not happen with stock kernel or EucOs kernel.
This did not happen with stock kernel or EucOs kernel.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
767
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.
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
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-29123Code_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
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