[KERNEL] [blu_spark r92] [Lollipop 5.1.1]

[eng.stk]

Kernel features:

• Powered by Ubuntu 14.04.3 x86_64 (sparky VPS @ www.servercore.com.br - thanks @ChristianLetti)
• Build with toolchain SaberMod eabi-4.9-09272015 cortex-a53 targeted
• Full -O3 & graphite support with device and target flags enhanced, linaro build improvements, etc
• Less is more: stockish builds based on android_kernel_motorola_msm8916
• Kernel compressed with LZ4-r131, custom tweaked RAMdisk with GZIP (best size/efficiency ratio, faster boot, less CPU usage)
• Removed some debug and logging options
• ARM enhanced performance and battery patches
• Upstream and CAF fixes
• Several CPU Governors (blu_active own governor is default)
• Slight UV and both CPU and GPU OC available (boots with stock freqs)
• Enhanced TCP methods (westwood is default), Network and Wifi tweaks
• Several I/O control (FIOPS is default), tweaked filesystems (F2FS, ExFAT, NTFS & CIFS)
• blu_plug: Dynamic Hotplug for osprey
• msm_thermal simple driver (default 65º C threshold)
• Optimized RWSEM, AES and SHA1 routines (with NEON support)
• Vibrator Strength tunable (63 % default)
• KGSL fixes and reworked GPU driver
• KCAL - Advanced color control for Qualcomm MDSS v3 (RGB calibration and post-processing features)
• doubletap2wake available (0:disabled, 1:enabled, 2:enabled fullscreen), option to disable with power button
• USB Fast Charge (force max PMIC charge level available both in MTP/AC charger mode)
• Multimount fstab (you can use data and cache partitions as f2fs or ext4)
• USB & SD Card automount
• CDROM emulation added to mass_storage (full Drive Droid compatible)
• init.d support (busybox run-parts required)
• CM12.1 performance profiles compatibility
• Compatible with Kernel Adiutor, Universal Kernel Manage and others

DOWNLOAD KERNEL ZIP

I only support stock ROM on XT1541. Stock ROM for XT1540 and XT1542 should work nicely also.
Other than that, you're on your own
On CM based ROMs, I support all models original CM supports.


Warning: If you come from other kernel, you should dirty flash your ROM before flashing blu_spark zip to avoid problems.
Reflash ROM -> flash SuperSU -> Boot device and install busybox -> flash blu_spark.
Also uninstall or clean data of any kernel control app you're using.

The regular kernel zip is for all ROMs that have Wifi builtin (like CM).
The stock zip is for stock ROM on supported models or other ROMs that have wifi built as a module.
Ask your ROM developer to know what to choose from.


Thanks to @franciscofranco, @faux123, @LaboDJ @show-p1984, @flar2, @anarkia1976, @stratosk, @myfluxi, @Christopher83, @hellsgod, @savoca
Special thanks to @DariosF and @ciprianruse88, for the friendship, initial push, knowledge and webart.

XDA:DevDB Information
blu_spark osprey, Kernel for the Moto G 2015

Contributors
eng.stk
Source Code: https://goo.gl/dDXuqH

Kernel Special Features: Powered by sparky

Version Information
Status: Stable
Current Stable Version: r92
Stable Release Date: 2015-11-14

Created 2015-09-21
Last Updated 2015-11-13

 

[eng.stk]

Reserved

All right crew!

Some of you may know me from Nexus development in Code_Blue and blu_spark projects, I decided to release a kernel for the Little Moto G3.

So far is in beta stage but quite stable. I manage to do a nice base I think, keep in mind that more stuff will come in the future, be patience

I tested it good on the AOSP ROM by @Alberto97 and Paranoid-L by @scritch007.
CM 12.1 nightlies works nicely.
Other ROMs should work too, I use anykernel zip that uses ROM existing RAMdisk

Stock 5.1.1 ROM compatible also soon

Enjoy the blu_spark!

 

[nelsonw]

Great! All kernel have wifi issues due to different drivers. Seem better using CAF wifi drivers. I'll try this soon!

Sent from my MotoG3 using Tapatalk

 

[Carlos Arriaga]

Goob work thanks!

 

[squid2]

On CM 12.1 of 13-09 by @squid2, I encountered some issues.
Radio derps always on first run, on reboot is cool. But wifi doesn't work.
Now on the officials let's see how it goes, hope you guys can help out so we have some nice goodies for the osprey.

Stock 5.1.1 ROM boots also, most work, except wifi... but who wants stock right? ;p

The reason you encountered WiFi issues on the stock ROM and my CM builds is that they use a separate kernel module for WiFi instead of building it into the kernel. You can make two variants of your kernel, one with CONFIG_PRONTO_WLAN=y for ROMs where WiFi is built into the kernel, and one with CONFIG_PRONTO_WLAN=m for ROMs where WiFi is in a separate kernel module.

Also, just so everyone knows, the official CM builds will be using Alberto's stock-ish kernel with WiFi drivers built in. So the existing blu_spark build here will probably work on official CM. Also be aware that the official CM kernel will use stock Motorola WiFi drivers, and will not have any special features like hotplug or better I/O schedulers. Thus, performance and battery life will be a bit poorer with the official CM kernel, and Indian users may encounter WiFi issues. On official CM, flashing a custom kernel such as blu_spark should improve performance and battery life a bit. In the coming days, I will also be making my kernel (that I've been bundling with CM) available as a standalone flashable zip, so that people who were happy with the kernel my unofficial CM builds shipped with would continue to be able to use my kernel.

 

[arnabJ]

The reason you encountered WiFi issues on the stock ROM and my CM builds is that they use a separate kernel module for WiFi instead of building it into the kernel. You can make two variants of your kernel, one with CONFIG_PRONTO_WLAN=y for ROMs where WiFi is built into the kernel, and one with CONFIG_PRONTO_WLAN=m for ROMs where WiFi is in a separate kernel module.

Also, just so everyone knows, the official CM builds will be using Alberto's stock-ish kernel with WiFi drivers built in. So the existing blu_spark build here will probably work on official CM. Also be aware that the official CM kernel will use stock Motorola WiFi drivers, and will not have any special features like hotplug or better I/O schedulers. Thus, performance and battery life will be a bit poorer with the official CM kernel, and Indian users may encounter WiFi issues. On official CM, flashing a custom kernel such as blu_spark should improve performance and battery life a bit. In the coming days, I will also be making my kernel (that I've been bundling with CM) available as a standalone flashable zip, so that people who were happy with the kernel my unofficial CM builds shipped with would continue to be able to use my kernel.

"...and Indian users may encounter WiFi issues..."

I didn't got your point here.
Will the Official CM kernel cause the WiFi issue for we Indian users or this blu_spark kernel?

Sent from my SM-A800F using XDA Free mobile app

 

[nelsonw]

"...and Indian users may encounter WiFi issues..."

I didn't got your point here.
Will the Official CM kernel cause the WiFi issue for we Indian users or this blu_spark kernel?

Sent from my SM-A800F using XDA Free mobile app

Official CM won't work on Indian users without custom kernel

Sent from my MotoG3 using Tapatalk

 

[hp420]

Finally, a REAL custom kernel!!! Thank you!!

 

[HelpMeruth]

Nice work! im currently running cyanogenmod so i cant test it.

 

[hp420]

Synapse isn't working...stock x.44 rom on xt1540

 

[khartaras]

Running r25 plus the 22/09 official CM nightly on the 1GB model.
No glaring issues to report, everything works as far as I can tell. Battery life is comparable to stock, but note that most of the time I'm using the "performance" option for CM, whatever that does.
Performance is slightly disappointing, some stutters and lag is present, but that is to be expected, as I had run into these issues (worse, even) on the kernel used on the unofficial builds.

Overall, thanks for your excellent work, and I look forward to using this kernel after using Code_Blue for a very long time on my now-defunct Nexus 5.
If you happen to need testing or feedback, let me know, and I'll try my best to be of use to you.

 

[==vj==]

The reason you encountered WiFi issues on the stock ROM and my CM builds is that they use a separate kernel module for WiFi instead of building it into the kernel. You can make two variants of your kernel, one with CONFIG_PRONTO_WLAN=y for ROMs where WiFi is built into the kernel, and one with CONFIG_PRONTO_WLAN=m for ROMs where WiFi is in a separate kernel module.

Sadly for me, CONFIG_PRONTO_WLAN=m and CONFIG_PRONTO_WLAN=y both the methods didn't flick to get WiFi working on Stock ROM. Last time i had missed doing modules_install for the seperately compiled wlan module. Did that one as well, still WiFi is a no go.
BTW in Motorola kernel source, there are 2 defconfigs namely

msm8916_defconfig
msm8916-perf_defconfig

and 2 externel configs

debug-msm8916.config
lux.config

I had attempt building kernel by clubbing them as follows

[B]CASE 1 :[/B]
msm8916_defconfig + debug-msm8916.config + lux.config
[U]Result:[/U] Kernel works (All features except WiFi), WiFi module stripped be 3.4MB in size
[B]CASE 2:[/B]
msm8916-perf_defconfig + debug-msm8916.config + lux.config
[U]Result:[/U] Kernel works (All features except WiFi), WiFi module stripped be 4MB in size (This is the size same as of Stock's WiFi module).Yet no go with WiFi

Now do i have to club them together while building kernel,

msm8916-perf_defconfig + msm8916_defconfig + debug-msm8916.config + lux.config

To get Kernel and WiFi module matching each other..?

Stock 5.1.1 ROM boots also, most work, except wifi... but who wants stock right? ;p

Hi, is your kernel functioning WiFi fine on Stock ROM..? Stock for stability and good backup i'd say

 

[eng.stk]

Synapse isn't working...stock x.44 rom on xt1540

Nothing to do with kernel

Running r25 plus the 22/09 official CM nightly on the 1GB model.
No glaring issues to report, everything works as far as I can tell. Battery life is comparable to stock, but note that most of the time I'm using the "performance" option for CM, whatever that does.
Performance is slightly disappointing, some stutters and lag is present, but that is to be expected, as I had run into these issues (worse, even) on the kernel used on the unofficial builds.

Overall, thanks for your excellent work, and I look forward to using this kernel after using Code_Blue for a very long time on my now-defunct Nexus 5.
If you happen to need testing or feedback, let me know, and I'll try my best to be of use to you.

Yeah I'm cooking some stuff, but moto source is crap. I already miss nexus AOSP .

Sadly for me, CONFIG_PRONTO_WLAN=m and CONFIG_PRONTO_WLAN=y both the methods didn't flick to get WiFi working on Stock ROM. Last time i had missed doing modules_install for the seperately compiled wlan module. Did that one as well, still WiFi is a no go.
BTW in Motorola kernel source, there are 2 defconfigs namely

msm8916_defconfig
msm8916-perf_defconfig

and 2 externel configs

debug-msm8916.config
lux.config

I had attempt building kernel by clubbing them as follows

[B]CASE 1 :[/B]
msm8916_defconfig + debug-msm8916.config + lux.config
[U]Result:[/U] Kernel works (All features except WiFi), WiFi module stripped be 3.4MB in size
[B]CASE 2:[/B]
msm8916-perf_defconfig + debug-msm8916.config + lux.config
[U]Result:[/U] Kernel works (All features except WiFi), WiFi module stripped be 4MB in size (This is the size same as of Stock's WiFi module).Yet no go with WiFi

Now do i have to club them together while building kernel,

msm8916-perf_defconfig + msm8916_defconfig + debug-msm8916.config + lux.config

To get Kernel and WiFi module matching each other..?


Hi, is your kernel functioning WiFi fine on Stock ROM..? Stock for stability and good backup i'd say

Yeah I tried a bit of everything and didn't get it to work either. NOt going to bother :/

 

[hp420]

Stock 5.1.1 ROM boots also, most work, except wifi... but who wants stock right? ;p

I do!! If I want anything else I have a nexus for that.

Hotspot doesn't work for me. USB tether does

 

[eng.stk]

blu_spark r29

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

• Latest CAF wifi drivers and other network patches
• Build improvements and tracing disabled
• Filesystem and storage improvements
• Multimount fstab (you can use data and cache partitions as f2fs or ext4)
• Removed debug and cruft
• Crypto and Neon patches
• Scheduler improvements
• Lot's of ARM battery and performance fixes
• Memory management improvements
• CM12.1 performance profiles compatibility
• RAMdisk tweaks

 

[==vj==]

I was about to review by the time new release is already up.
I'd say this kernel is meeting my requirements and behaves to how I want it to be.
Thanks for not adding CPU boost. And the blue_plug is going good
Battery backup is close to Motorola's stock kernel. And happy to find WiFi turning on-off fine.

Will get on new release and check it out. Thank you for bringing kernel development alive for G3

ROM: CyanogenMod official nightly 24-Sept-2015

 

[==vj==]

The latest release is cool. Smoother and CPU temps are soo cooler. Honestly I always had higher temps on CM12.1 as compared to Motorola's stock kernel. This time its same as stock.

And I tried out INTERACTIVE governor with just 2 changes. The scaling goes awesome with blue_plug

timer_rate: 40000
hispeed_freq: 800000

The CPU load tasks looks accomplished within lower frequencies itself less rampage to higher freqs. And have set CPU min to 400MHz.

 

[Harry551]

Hello.. Anyone can tell me if the latest release work on stock rom?

 

[hp420]

I'm iffy on whether or not to keep this one yet, since I'm going away for the weekend, but I'll totally test it for today and see how battery life seems. the first build didn't like me underclocking, so I'm hoping this one responds better.

*edit*
i'm seeding for the next few hours for anyone who prefers torrent. Please re-seed!
*edit #2*
stock .44 build, moto xt1540, kernel b29
no wifi, no hotspot...cleared cache and dalvik. no dice

 

[khartaras]

Following the release of r29, updated CM12.1 nightly to 24/09 and flashed the newest release.

Performance is significantly improved over last iteration, on r25 and 22/09 I had massive, massive slowdowns where the phone ground to a halt quite often. I also experienced issues with Spotify closing while playing music (which is a mild annoyance) and frequent re-launching of the, well, launcher. Here, I've not had as much of that, but the phone takes a LONG time to wake up when someone is calling, as in 4-5 seconds just for the screen to show caller ID. Which may or may not be kernel-related, but if you could look into it, that'd be fantastic.

Thanks for the quality release again.