OP meaning OnePlus, not "OP". He's not ****-talking Freak.
yea. this. ?
Would it be better to wait until next release to install? Or is the latest + op brain module enoughAbsolutely no need to apologize. I’m short on time and you’re helping out is a good thing!
Some people seem to expect this issue also on the stable OOS release.
The real problem here is OnePlus not pushing kernel changes for stable OOS since 10.0.1 (mid October) and no beta updates either for beta 7.
I have an update ready, but I want to not rely on more workarounds. I guess I’ll release it in the next days/week if One Plus pushes nothing new and I find time.
In the meantime use the fix kindly linked to by @ridobe
Would it be better to wait until next release to install? Or is the latest + op brain module enough
Holy dragon kernel has fixed the issues apparentlyI just installed the 10.3 update earlier today, and then immediately reinstalled the Kirasakura kernel v1.4 without issue. I held off on installing the OOS 10.3 AA update for a few days after it was released because of concerns regarding potential kernel issues, but I can say that so far everything seems to be working great. I have found zero kernel compatibility issues as of yet...granted it's only been the better part of one single day and it's very possible there could be something going on behind the scenes that I can't see, but yeah...things are looking good! I don't see any reason for you to be worried, and it looks like there are plenty of others here in this sub-forum who would tell you the same. It also looks like all of my mods/magisk modules are good as well.
I know Freak has mentioned he's got a test kernel that sounds like it's ready to go, but he/she (they? Whatever, sorry Freak!) have been holding off for the same reasons. Unfortunately we're at the mercy of OnePlus and their delays with releasing the kernel source code. Delays in releasing source means delays in releasing custom kennels that a developer can be confident in.
My module also contains the fix mentioned and more haha it has for weeks before this became an issue for everyone that's probably why you're not seeing an issue lolI just installed the 10.3 update earlier today, and then immediately reinstalled the Kirasakura kernel v1.4 without issue. I held off on installing the OOS 10.3 AA update for a few days after it was released because of concerns regarding potential kernel issues, but I can say that so far everything seems to be working great. I have found zero kernel compatibility issues as of yet...granted it's only been the better part of one single day and it's very possible there could be something going on behind the scenes that I can't see, but yeah...things are looking good! I don't see any reason for you to be worried, and it looks like there are plenty of others here in this sub-forum who would tell you the same. It also looks like all of my mods/magisk modules are good as well.
I know Freak has mentioned he's got a test kernel that sounds like it's ready to go, but he/she (they? Whatever, sorry Freak!) have been holding off for the same reasons. Unfortunately we're at the mercy of OnePlus and their delays with releasing the kernel source code. Delays in releasing source means delays in releasing custom kennels that a developer can be confident in.
Very likely. I hadn't thought of that. I was using 10.3 for maybe not even a full day before trying your mod. But I guess between you and Freak07 , I'm covered lol.My module also contains the fix mentioned and more haha it has for weeks before this became an issue for everyone that's probably why you're not seeing an issue lol
I hope you don't feel pressured to release an update without unreleased updated source... You do you!
Same issue here. No disrespect to @Freak07 but I'm going to link to another kernel thread/post; not because of the kernel, but for the explanation and temporary solution.
https://xdaforums.com/showpost.php?p=81225599&postcount=155
Hi,
I just installed the latest OB8 and switched again to kirisakura 1.4 from smurf. After installing the stop_brain_service magisk module I still had the prime core maxed for 5min+ and no change after rebooting twice.
After trying the terminal command posted earlier "stop oneplus_brain_service" it worked. My solution to make it stick with reboots is to create a script with that line in my kernel manager (I use SmartPack) and make it run on boot.
No idea why the module wouldn't work...
Thanks for this nice kernel, hope everything else works in OB8.
Hi,
I just installed the latest OB8 and switched again to kirisakura 1.4 from smurf. After installing the stop_brain_service magisk module I still had the prime core maxed for 5min+ and no change after rebooting twice.
After trying the terminal command posted earlier "stop oneplus_brain_service" it worked. My solution to make it stick with reboots is to create a script with that line in my kernel manager (I use SmartPack) and make it run on boot.
No idea why the module wouldn't work...
Thanks for this nice kernel, hope everything else works in OB8.
Excuse my lack of understanding, but why with every release after 10.03 does this stuck core exist, even running OOS stock? Is OnePlus messing up its own kernels?
I've never had issues on stock kernel. Only with custom kernels on 10.3 I had issues.
Me neither.
After a clean flash of stock rom to start clean the module didn't work anymore.
After trying several kernels i went back to stock.
Prime core doesn't stuck on max with stock oos, only on custom kernels. At least on my side.