Development [KERNEL] [blu_spark r165 OP9/Pro] [A14 Custom]

[dkcats3]

I have 2 questions:

1) Coming from stock and even Omega, this kernel seems to scroll a lot quicker, fixing the "slow scrolling fling" people report. Have you done anything intentional to cause this?

2) I see the setting slider for haptic vibration intensity, with a default value of 30, but no matter how I adjust it (from 0 all the way to 100), the brightness slider has the exact same intensity of haptics. Am I doing this wrong, is that a bad example to test, or does it require reboot to take effect?

EDIT: Just wanted to share, I'm hitting 4h10m SOT with 44% battery to spare. Using Wifi, bluetooth, and FKM's 25% max CPU reduction, GPU set to powersave, and MSM touchboost disabled. I notice no impact to actual normal usage smoothness or snappiness.

Thanks

 

[infamousvincci]

People reported working on regular OP9, if that uses simialr OOS bins etc should work.
Keep in mind that I can only test in OP9 Pro (EU), so backup your stuff and procede with caution.
We'll never know what'sreally going on on that "special" models.

Heyyy yeah i can report its working perfectly fine on my op9 tmobile variant.

 

[Hot-Proton]

Gcam not work with this Kernel. Normal cam working.

 

[mattie_49]

There's not really much difference in IO schedulers for fast nand devices.
in 5.* kernels with MQ framework and assynchonous stuff like io_uring in place (don't know if android takes advantage from this), none is actually advised for nvme and fast ssd, device.
Controllers are robust enough and there's plenty of cache to manage requests, just remove the middle man.
For now I'll keep it like that for some more interactiveness and safeguard, it seems like some userspace crap pegs on IO stuff so there's that.

I will add nothing more on this regard.

One question. You know how we have to flash stock boot image back to take ota's? As long as I back-up stock kernel through ex-kernel manager to flash back when update arrives. I can just return to stock kernel through app and flash untouched boot img back & I shouldn't have any issues taking ota correct? I just wanna maintain data . Put much time into getting device the way I want. And I learned my lesson msm'ing every other day with my op8. Finally watching it brick and unable to restore by msm tool. Please and thank you beforehand.

 

[Shooter7889]

One question. You know how we have to flash stock boot image back to take ota's? As long as I back-up stock kernel through ex-kernel manager to flash back when update arrives. I can just return to stock kernel through app and flash untouched boot img back & I shouldn't have any issues taking ota correct? I just wanna maintain data . Put much time into getting device the way I want. And I learned my lesson msm'ing every other day with my op8. Finally watching it brick and unable to restore by msm tool. Please and thank you beforehand.

From my experience, I never flash back stock boot.img b4 taking OTA. the ota is writing each img(including new boot.img) over what the phone is currently on, so I've never saw the need to go back to stock boot.img b4 OTA and I've never had any problems. I have had plenty though forgetting to disable any substratum themes

 

[mattie_49]

From my experience, I never flash back stock boot.img b4 taking OTA. the ota is writing each img(including new boot.img) over what the phone is currently on, so I've never saw the need to go back to stock boot.img b4 OTA and I've never had any problems. I have had plenty though forgetting to disable any substratum themes

Bet as far as getting stock partitions back for google ota to work . Restoring stock kernel is all there is to do correct?

 

[osm0sis]

vendor_boot now too

 

[mattie_49]

vendor_boot now too

Answer I was seeking. Thank you.

 

[toolhas4degrees]

Gcam not work with this Kernel. Normal cam working.

Use the correct gcam and configs or lack of config

 

[eng.stk]

I have 2 questions:

1) Coming from stock and even Omega, this kernel seems to scroll a lot quicker, fixing the "slow scrolling fling" people report. Have you done anything intentional to cause this?

2) I see the setting slider for haptic vibration intensity, with a default value of 30, but no matter how I adjust it (from 0 all the way to 100), the brightness slider has the exact same intensity of haptics. Am I doing this wrong, is that a bad example to test, or does it require reboot to take effect?

EDIT: Just wanted to share, I'm hitting 4h10m SOT with 44% battery to spare. Using Wifi, bluetooth, and FKM's 25% max CPU reduction, GPU set to powersave, and MSM touchboost disabled. I notice no impact to actual normal usage smoothness or snappiness.

Thanks

1) Well, this is blu_spark And this device is wonky AF, probably I won't be able to do everything I would like
2) What brightness slider? That is for vibration strength, you can easily test level by sliding the tristate button on phone for instance. Works fine on my 9 Pro, I use level 10 because I feel the haptics to be too strong for my taste.

 

[eng.stk]

If some of you are having an unusual drain when using wifi, it's a damn app from OP
com.oneplus.accessory (Oneplus Link)
I just froze the little bugger, probably loops trying to find something form the OEM driver to which we don't have source.

Why you do dis OP?

 

[HessNL]

Didn't feel that much battery drain seems to work really good nothing has been changed in fkm but i saw that mq-deadline is on what is really great to have normally I needed to switch over in kernels but this one far the best

(Didn't benchmark it yet going to try it soon)

Thx again

 

[eng.stk]

Didn't feel that much battery drain seems to work really good nothing has been changed in fkm but i saw that mq-deadline is on what is really great to have normally I needed to switch over in kernels but this one far the best

(Didn't benchmark it yet going to try it soon)

Thx again

I was getting 1.8%/h, which for my use is unacceptable.
Don't know if it's connected, but I started noticing it around the time I used OP account to enter OP community app.

I just adb uninstall com.oneplus.accessory and com.oneplus.account.
No more infinite wakeups from those and cleaner setting smenu as a bonus

 

[PKkeys]

I was getting 1.8%/h, which for my use is unacceptable.
Don't know if it's connected, but I started noticing it around the time I used OP account to enter OP community app.

I just adb uninstall com.oneplus.accessory and com.oneplus.account.
No more infinite wakeups from those and cleaner setting smenu as a bonus

Is it safe to unintall com.oneplus.accessory and com.oneplus.account ? I know it's a silly question but can confirm?

 

[Flasher8]

I was getting 1.8%/h, which for my use is unacceptable.
Don't know if it's connected, but I started noticing it around the time I used OP account to enter OP community app.

I just adb uninstall com.oneplus.accessory and com.oneplus.account.
No more infinite wakeups from those and cleaner setting smenu as a bonus

Can have the adb command ?

 

[mattie_49]

If some of you are having an unusual drain when using wifi, it's a damn app from OP
com.oneplus.accessory (Oneplus Link)
I just froze the little bugger, probably loops trying to find something form the OEM driver to which we don't have source.

Why you do dis OP?

No I'll side effects freezing Op link . Fantastic

 

[mattie_49]

Can have the adb command ?

Freeze it with titanium. Or use the oneplus all in one tool . And run adb uninstall through this app.

Thread '[TOOL][OP8P] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)' https://xdaforums.com/t/tool-op8p-t...ck-twrp-factory-image-stock-recovery.4103509/

 

[osm0sis]

Can someone with a OnePlus 9 (i.e. NOT Pro) give me the output of `getprop ro.display.series` ?

 

[GuyInDogSuit]

Gcam not work with this Kernel. Normal cam working.

Mine works fine. Grab the "snap" variant from BSG's builds.
Grab the config file if you'd like, as well. Load it from the GCam app by double-tapping anywhere in the black space around the shutter button.

One question. You know how we have to flash stock boot image back to take ota's? As long as I back-up stock kernel through ex-kernel manager to flash back when update arrives. I can just return to stock kernel through app and flash untouched boot img back & I shouldn't have any issues taking ota correct? I just wanna maintain data . Put much time into getting device the way I want. And I learned my lesson msm'ing every other day with my op8. Finally watching it brick and unable to restore by msm tool. Please and thank you beforehand.

From my experience, and this device seems to fit into this rule as well, the only necessary thing is to disable Magisk if you're rooted (which you would be if you have a custom kernel, no?).

This is the process I used, prior to flashing BluSpark:

STOP! Make sure to disable automatic system updates (Settings -> Developer options) if this is your first time doing something like this.

Go into Magisk Manager and choose -> Uninstall -> Restore Images.

This will restore the boot to stock.

Do not reboot yet or you'll uninstall Magisk and will have a bad time.

Apply the OTA. Go into Settings -> System -> System Update. Or conversely, do this from Oxygen Updater.

Seriously, do not restart.

Now return to Magisk Manager and choose -> Install -> Install to Inactive Slot (After OTA).

After the installation is done, press the reboot button in Magisk Manager.

Profit!

Now keep in mind, this might need some additional steps, since the vendor files are now affected as well. My guess is that is ONLY necessary if you are returning to the stock kernel, however.

 

[mattie_49]

Mine works fine. Grab the "snap" variant from BSG's builds.
Grab the config file if you'd like, as well. Load it from the GCam app by double-tapping anywhere in the black space around the shutter button.



From my experience, and this device seems to fit into this rule as well, the only necessary thing is to disable Magisk if you're rooted (which you would be if you have a custom kernel, no?).

This is the process I used, prior to flashing BluSpark:



Now keep in mind, this might need some additional steps, since the vendor files are now affected as well. My guess is that is ONLY necessary if you are returning to the stock kernel, however.

So that's part of my question then. Since the 9 and 9pro use Google ota to update, all partitions have to be stock or it fails.Can someone take an update with blu_spark or does stock have to be restored prior and then what other files? I wanna flash kernel but I however don't wanna have a bunch of partitions after that to cause next ota to fail. They are coming religiously every month. And I do not wanna have to msm and loose data on device by factory reset.