[KERNEL] [blu_spark r63] [A11]

IntenseColor

Senior Member
Jan 18, 2012
113
31
58
I don't know why this morning I flashed r28 using json import with fkm and my device bootlooped ? (runing stock latest sunfish) should I try flashing latest kernel with fastboot ?
I flashed r28 the same way and had no problems. I expect that the bootloop will be gone after flashing the stock kernel via fastboot.
 

krotin

Senior Member
Jan 5, 2015
108
39
48
Clermont Ferrand
I flashed r28 the same way and had no problems. I expect that the bootloop will be gone after flashing the stock kernel via fastboot.
Where is the stock kernel ?
should i fastboot flash boot factoryboot ?
i looked through all factory image files and I can't see one called kernel.
Is kernel nested in boot img in factory image ?

While waiting I sideloaded latest factory image and rooted again.
I then flashed r28 again through json import in fkm no worries this time.

Could it be because I wasnt on latest factory image ?
 

IntenseColor

Senior Member
Jan 18, 2012
113
31
58
Where is the stock kernel ?
should i fastboot flash boot factoryboot ?
i looked through all factory image files and I can't see one called kernel.
Is kernel nested in boot img in factory image ?

While waiting I sideloaded latest factory image and rooted again.
I then flashed r28 again through json import in fkm no worries this time.

Could it be because I wasnt on latest factory image ?
The stock kernel is contained in the file called boot.img. You can find it in every factory image but the version might be different of course. You can flash it with the command 'fastboot flash boot boot.img'.
I don't have enough info to tell you why you got the bootloop.
 
  • Like
Reactions: gvsukids

jmtjr278

Senior Member
Mar 8, 2012
1,005
549
143
Where is the stock kernel ?

should i fastboot flash boot factoryboot ?

i looked through all factory image files and I can't see one called kernel.

Is kernel nested in boot img in factory image ?



While waiting I sideloaded latest factory image and rooted again.

I then flashed r28 again through json import in fkm no worries this time.



Could it be because I wasnt on latest factory image ?
I would suspect it was because you weren't on the latest factory image. When the new security update comes out you need to update to newest or problems can arise if there were kernel changes between builds. This is why you had bootloop issues.

Sent from my Nexus 5 using Tapatalk
 

krotin

Senior Member
Jan 5, 2015
108
39
48
Clermont Ferrand
I would suspect it was because you weren't on the latest factory image. When the new security update comes out you need to update to newest or problems can arise if there were kernel changes between builds. This is why you had bootloop issues.
Yes I'm inclined to believe that was it.
The thing is : I'm running stock with magisk only and though I have been able to ota previous update I didn't have any notification about latest build.
I only learned it once I was crashed this morning.
Thank you for your time. Love this community.
Running well since then.
Thank you eng.
 

jmtjr278

Senior Member
Mar 8, 2012
1,005
549
143
I noticed the latest release says R28 on the link but only offers R24 for download. Am I missing something?
The link posted in the release post does indeed link to r24. However, if you go to the op and hit the link to download it will direct you to r28

Sent from my Nexus 5 using Tapatalk
 

eng.stk

Senior Member
Mar 29, 2011
6,696
58,001
263
blu_spark r12 release (A11)

New build is up!

You can use FKM download kernel feature, just import the link bellow in the app :highfive:


blu_spark_r35 release
FKM download config: HERE
  • input: fpc1020: we don't inline here
  • makefile: cleanup
  • defconfig: disable cc_error
  • arm64: __ashlti3 __ashrti3 and __lshrti3 fixes
  • Some further build improvements
  • treewide: Suppress overly verbose log spam
  • Latest Magisk v21.1 or later mandatory for root in A11 (beta atm)

Keep in mind: I will give no active support for custom ROMs (including stock based ones).
I am mostly interested on debugging stuff in stock ROM (with logs and reproducible steps to replicate the issue).


No mirrors please
If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free :)
 

Chaplan

Senior Member
Jan 8, 2008
1,331
2,242
153
No Place
And we meet again yet on a Goggle device.
Feels like the good old days of the former nexus 5.
Kernel is top notch, full of goodies.
Wasn't expecting this mind blowing battery usage on such a device to be honest, really good.
Snappiness just went wild with blu_spark.
Nothing new there but worth of notice still.

Keep up, it's blu time. :)
 
Last edited:

eng.stk

Senior Member
Mar 29, 2011
6,696
58,001
263
And we meet again yet on a Goggle device.
Feels like the good old days of the former nexus 5.
Kernel is top notch, full of goodies.
Wasn't expecting this mind blowing battery usage on such a device to be honest, really good.
Snappiness just went wild with blu_spark.
Nothing new there but worth of notice still.

Keep up, it's blu time. :)
blu_crew baby :highfive:
 

eng.stk

Senior Member
Mar 29, 2011
6,696
58,001
263
blu_spark_r51 release (A11)

New build is up!

You can use FKM download kernel feature, just import the link bellow in the app :highfive:
FKM download config: HERE


Changelog:
  • Build with Google Clang 11.0.5 + LLD linker
  • Rebase main tree and subtrees to android-msm-sunfish-4.14-android11-qpr1 (Google 2020.12)
  • r35+ cleanup
  • printk: fix invalid-free on devkmsg_write(), use buffer from the stack space
  • arm64: dts: sdmmagpie: Remove display ramdump memory region, Remove useless 40 MiB memory dump region
  • treewide: Suppress overly verbose log spam
  • defconfig: remove some cruft
  • Latest Magisk v21.1 mandatory for root in A11 (beta atm)

Keep in mind: I will give no active support for custom ROMs (including stock based ones).
I am mostly interested on debugging stuff in stock ROM (with logs and reproducible steps to replicate the issue).


No mirrors please
If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free :)
 
Last edited:

jawz101

Senior Member
Jun 4, 2009
1,540
765
143
It's been a few years since I've taken a look at kernels. It would be nice if some of the features had descriptions and a brief history. example:

adrenoboost, KLAPSE, KCAL, KGSL, ZRAM Swap (LZ4) and with swap file disabled, FS fsync toggle on/off

The fsync one I've heard of but I read mixed feelings about the benefit/risk. The rest I don't know if they are things random Android kernel modders invented or if they are latent features in the Linux kernel or Qualcomm chips-- I dunno. And when and who came up with making them "a thing we want."

It's been like a decade and I don't know how relevant or if there is empirical evidence they have benefits-- it's just a mystery to me these days.
 

bobbarker2

Senior Member
Aug 30, 2013
1,485
503
133
blu_spark_r51 release (A11)

New build is up!

You can use FKM download kernel feature, just import the link bellow in the app :highfive:
FKM download config: HERE


Changelog:



Keep in mind:
I will give no active support for custom ROMs (including stock based ones).
I am mostly interested on debugging stuff in stock ROM (with logs and reproducible steps to replicate the issue).


No mirrors please
If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free :)

Is there any way you or someone else could provide an .img of your kernel? I had it installed prior to updating to December and now the magisk (canary) generated boot.img won't boot for me. DIsabled all modules and such before hand.. did the same procedure I've done every time when updating on 11.

I watch the logcat using monitor.bat on my computer of the device booting and it keeps getting stuck in a loop where its looking to set sound related settings. So taking a shot in the dark and seeing if someone can make an .img of the December build of this kernel and see if it will solve my problem.

Edit: Nevermind, fixed it. Apparently 1 module wasn't disabled and I was able to get rid of it during boot.

Thanks for the release!
 
Last edited:
  • Like
Reactions: eng.stk

rignfool

Senior Member
Dec 8, 2010
5,009
2,729
253
The Poconos
It's been a few years since I've taken a look at kernels. It would be nice if some of the features had descriptions and a brief history. example:

adrenoboost, KLAPSE, KCAL, KGSL, ZRAM Swap (LZ4) and with swap file disabled, FS fsync toggle on/off

The fsync one I've heard of but I read mixed feelings about the benefit/risk. The rest I don't know if they are things random Android kernel modders invented or if they are latent features in the Linux kernel or Qualcomm chips-- I dunno. And when and who came up with making them "a thing we want."

It's been like a decade and I don't know how relevant or if there is empirical evidence they have benefits-- it's just a mystery to me these days.
Adrenoboost boosts the gpu frequency...

KLAPSE is a display driver that auto darkens and adds an amber or red tint to the screen to "reduce eye strain"...

KCAL is color calibration...

KGSL is the trustzone environment for display (IIRC)...

ZRAM is compressed pages is RAM...

Swap is physical disk space masquerading as RAM...
 
  • Like
Reactions: jawz101

eng.stk

Senior Member
Mar 29, 2011
6,696
58,001
263
welp i tried and it didnt work it said uncompatible device
do on terminal or adb shell and post the output:
getprop ro.product.device
getprop ro.build.product
getprop ro.product.vendor.device
getprop ro.vendor.product.device
 
Last edited: