[KERNEL] [blu_spark r219 unified OP5/5T] [A10 unified]

[Megaflop666]

Guess I found the error with bad " in bad place. I swear I checked several times :_(

Will try again now.

Make sure every little detail matches the example @eng.stk provided. All I did was take his example, follow the directions, and as you can see by the attached pics, it worked perfectly through a reboot. Every little detail counts and the slightest mistake creates a headache.

Glad you found it, lesson learned!

[emoji106]

Sent from my ONEPLUS A5000 using Tapatalk

 

[kaihansen2001]

@eng.stk Can you block wakelocks like NlpCollectorWakeLock or Nlpwakelock? Because I added them but checking now I still see them in betterbatterystats. In boeffla document I see you can add them.

Sent from my OnePlus5 using XDA Labs

 

[Zocker1304]

I underclocked the two clusters, set it to hexacore mode and blocked all the wakelocks.
But ex kernel manager says 8,73% per hour and 2,86 in standby. Better battery stats says 5,6 % per hour but I think that's combined. What's going on? Is ex kernel manager wrong?

 

[Bl1zZ87]

Short question. Is restoring Data in your twrpblu build possible without errors. In official twrp it will go into a bootloop

 

[eng.stk]

I underclocked the two clusters, set it to hexacore mode and blocked all the wakelocks.
But ex kernel manager says 8,73% per hour and 2,86 in standby. Better battery stats says 5,6 % per hour but I think that's combined. What's going on? Is ex kernel manager wrong?

I don't know, I'm not the developer of those tools.
You should ask them... but probably just 2 different algorithms to measure and calculate stuff.

Short question. Is restoring Data in your twrpblu build possible without errors. In official twrp it will go into a bootloop

Sure, everything is solid, I use it all the time.
Wouldn't release it if crap lik ethat was broken.

 

[Jsilver73]

I don't know, I'm not the developer of those tools.
You should ask them... but probably just 2 different algorithms to measure and calculate stuff.


Sure, everything is solid, I use it all the time.
Wouldn't release it if crap lik ethat was broken.

Is also the fastest to backup and restore data, seriously, takes me like literally 3 or 4 minutes to do full backup of boot system and data and restore different build boot, system and data! So fast, much faster than the other twrp builds in my experience at least :good:

Sent from my OnePlus5 using XDA Labs

 

[Megaflop666]

Is also the fastest to backup and restore data, seriously, takes me like literally 3 or 4 minutes to do full backup of boot system and data and restore different build boot, system and data! So fast, much faster than the other twrp builds in my experience at least :good:

Sent from my OnePlus5 using XDA Labs

+1

Sent from my ONEPLUS A5000 using Tapatalk

 

[dakotah2468]

Is the Los version based off the gzr source or the official Los source?

 

[kaihansen2001]

@eng.stk Can you block wakelocks like NlpCollectorWakeLock or Nlpwakelock? Because I added them but checking now I still see them in betterbatterystats. In boeffla document I see you can add them.

Anyone for my question please? Thanks.

Sent from my OnePlus5 using XDA Labs

 

[Megaflop666]

Anyone for my question please? Thanks.

Sent from my OnePlus5 using XDA Labs

There's no needs for double posts by quoting yourself.

I would take a wild guess most folks were ignoring your question as it's not related to the kernel, and if memory serves, the Deb says he would offer no assistance with the wakelock blocker. I might be mistaken, but I'm sure I read that.

To answer your question, yes, you can block the nlp wakelock(s). There's several wakelocks relating to the Google play services (which nlp falls into) and you have to track them all down and list them all in your script or one of them can and will wake the others. Something that may be simpler for you if your tracking down play services wakelocks would be to look at an app called autostarts; or use the built in script, but include every part correctly for the wakelocks BBS is showing you.

Sent from my ONEPLUS A5000 using Tapatalk

Edit: went and double checked, @eng.stk said no support for wakelock blocking. I'm new in this thread, but I read through it all, learned all about it; and found out this is pretty tough crowd that follows the OP's rules/comments.

Good luck with wakelocks, they're annoying!

 

[Sukhi]

I underclocked the two clusters, set it to hexacore mode and blocked all the wakelocks.
But ex kernel manager says 8,73% per hour and 2,86 in standby. Better battery stats says 5,6 % per hour but I think that's combined. What's going on? Is ex kernel manager wrong?

Turning of the cores has no real advantage on SD835 and moreover it needs custom hot plugging which is absent. If you’re looking forward to bring down your active drain, you need to tweak the kernel parameters as per your usage. This might sound stupid but underclocking also wont have significant difference. Race to Idle is the way to go (the kernel should be able to finish the task is least possible time and thus lesser battery drain)


Sent from my iPhone using Tapatalk Pro

 

[mystique47]

is there any way to make this kernel work on unencrypted (decrypted) custom roms?

 

[eng.stk]

Is the Los version based off the gzr source or the official Los source?

None, my own blu_spark source.
I add hw and other needed stuff were applicable (like gestures for instance, in which I follow LOS/OMNI patchset).

Anyone for my question please? Thanks.

Sent from my OnePlus5 using XDA Labs

Don't need to keep asking the same question. People will reply if they want to reply.
wakelocks are requested from userspace by services, daemons etc and mostly when they are hw related, kernel is asked by them to perform the wakelock.
In general, all kernel wakelocks (which appears in BetterBatteryStats Kernel Wakelocks section for instance) can be blocked, it's up to you to choose want you want/need. Like I said, becasue of potential issues, you're on your own if you choose to do this.
Any other type of wakelocks are not mangeable by the wakelock blocker, which is only for kernel type ones.

is there any way to make this kernel work on unencrypted (decrypted) custom roms?

By default kernel should run unencrypted on custom ROMs. If by any means it's not running, you can use an forced uncrypted zip and other workarounds, search the thread and other places for that kind of stuff.
I don't recommend and doesn't make sense to run anything unencrypted nowadays, there's plenty of ROMs that support latest FBEcrypto stuff used on stock OOS.

 

[kaihansen2001]

Don't need to keep asking the same question. People will reply if they want to reply.
wakelocks are requested from userspace by services, daemons etc and mostly when they are hw related, kernel is asked by them to perform the wakelock.
In general, all kernel wakelocks (which appears in BetterBatteryStats Kernel Wakelocks section for instance) can be blocked, it's up to you to choose want you want/need. Like I said, becasue of potential issues, you're on your own if you choose to do this.
Any other type of wakelocks are not mangeable by the wakelock blocker, which is only for kernel type ones.
.

Sorry for double posting. Ok, that is why I couldn't block those NLP google play services wakelocks but I thought we could because in Boeffla info link provided, he put that wakelock as an example to be blocked.

 

[dakotah2468]

None, my own blu_spark source.
I add hw and other needed stuff were applicable (like gestures for instance, in which I follow LOS/OMNI patchset).


So basically, it won't work for aicp. Thank you!

 

[DylanTheVillian]

None, my own blu_spark source.
I add hw and other needed stuff were applicable (like gestures for instance, in which I follow LOS/OMNI patchset).


So basically, it won't work for aicp. Thank you!

It works fine on AICP, you just have to flash the no verity zip after the kernel.

 

[dakotah2468]

It works fine on AICP, you just have to flash the no verity zip after the kernel.

Odd it didn't work when I tried..

 

[DylanTheVillian]

@eng.stk

This kernel kills the 'swap buttons' toggle in additional button settings on AICP. Any way to fix this? I don't see an option in any of the kernel tuner apps....

 

[MurdererFight]

@eng.stk
I noticed this while using logcat. Everytime i touch the screen or do something it says "Failed to apply optimization". It looks like something couldn't be read properly
Using blue_active with fastlane 1 and thredshold 35, tried to disable it but nothing happens
I'm on blue-spark oos r30, Official OOS 4.5.10 and Magisk V14
Haven't tried on stock one.

EDIT: Phone is encrypted, the app is MatLog

 

[mystique47]

It works fine on AICP, you just have to flash the no verity zip after the kernel.

Tried but doesnt work