Noted. Since I don't like arguing over semantics, I'll just move on.I just wanted to point out that your general statement "this kernel breaks bluetooth" is not true. There was and is no offense intended.
Noted. Since I don't like arguing over semantics, I'll just move on.I just wanted to point out that your general statement "this kernel breaks bluetooth" is not true. There was and is no offense intended.
Thanks for your work! Is this the only official channel for kernel updates? No Github releases or Telegram group?Affinity Kernel r22 is up!![]()
Can you try using other version or other kernel. The issue you mentioned happens if you keep flashing many kernel or keep dirty flashing. I had this same issue. I don't know the exact reason for this but clean flash solves stuck at 1+ logo for longer time. You can dirty flash and get back to stock kernel and check if it boots faster or no.22nd Boot speed becomes very slow,Staying on the first screen`s 1+ logo for a long time
Thanks for chiming in. So, any workaround for this besides using a different kernel?
r23 feels much faster, boot either .Affinity Kernel r23 is up!
Here's the changelog:
- Upstreamed to Linux 4.4.177
- Merged changes from OOS kernel beta branch
- Fixed PS4 Controller support
- RCU upstreams
- Reverted LMK to the msm common kernel state
- Minor Klapse fix
- Fixed HBM on OmniROM
- Deoneplusified devfreq driver
- More arm64 related optimizations
- Other stuff
I would like to try this kernel on CrDroid / Pie ... are there any problems?
Let me know how it works out if you decide to try it. I'd be interested to know if it helps with the 'Phone is Starting' bug. Have you ever had that?
Yes, too me.
CrDroid Pie
Everything would seem to work perfectly; no problem with "phone is starting" and no problem with bluetooth and wifi.
Let me know if anything changes or if 'Phone is Starting' happens again? It's way to early to say yet that it's 'fixed', unless you were getting it on every single boot and now it's stopped.
Let me know if anything changes or if 'Phone is Starting' happens again? It's way to early to say yet that it's 'fixed', unless you were getting it on every single boot and now it's stopped.
Nothing done. "... phone is starting" appeared again...
P.S.: and I don't use Magisk (no root).
Thanks for letting me know. I got it again myself last night. Got a logcat but don't know if it'll help.
Edit: Might be worth noting "Affinity Kernel is based on the official kernel source released by OnePlus" The crDroid maintainer for the 5T says "OnePlus kernel implementation" when asked why the issue might affect Oneplus phones only.
Perhaps a Kernel that doesn't use Oneplus sources might be better for this issue? Does one exist?
@mascian
This issue has occoured for me on LOS multiple times even on a stock kernel. Seems to be a ROM-side problem on LOS based ROMs but who knows.I think you're right; it is necessary to try another kernel that does not use the sources from Oneplus.
A lot of users have blamed the root (Magisk)... for example, I don't use any kind of root.
/*
* Your warranty is not void (Thank you OnePlus!).
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/