Ok thanks. EX kernel worked, much better.Sounds like a busy box/set up issue. You could try using ex kernel manager or franco kernel manager, they do not require busy box and flash this kernel fine with no issues.
Ok thanks. EX kernel worked, much better.Sounds like a busy box/set up issue. You could try using ex kernel manager or franco kernel manager, they do not require busy box and flash this kernel fine with no issues.
My mistake. Yes I have the international version. Tmobile made their version dust and water resistant (if I remember correctly).Hmmm...says here that 2005 is the int'l variant and not TMO - https://www.reddit.com/r/OnePlus8T/comments/k02xen
For OOS android 11 only...Hi guys. I was using this great kernel on my Oneplus 8T with the Unofficial LineageOS ROM and everything was working fine. I updated the ROM and did the usual process to flash Magisk and the kernel: patched the boot.img for Magisk, then installed the kernel with EX Kernel Manager. But after flashing the kernel WiFi stops working, here's the logcat:
01-11 11:36:56.965 910 910 E [email protected]: Failed to open driver state control param: No such file or directory
01-11 11:36:56.966 910 910 E [email protected]: Failed to load WiFi driver
01-11 11:36:56.966 910 910 E [email protected]: Failed to initialize firmware mode controller
01-11 11:36:56.966 910 910 E [email protected]: Wifi HAL start failed
01-11 11:36:56.966 1417 1889 E HalDevMgr: Cannot start IWifi: 9 ()
01-11 11:36:56.966 1417 1889 E WifiVendorHal: Failed to start vendor HAL
01-11 11:36:56.966 1417 1889 E WifiNative: Failed to start vendor HAL
01-11 11:36:56.966 1417 1889 E WifiNative: Failed to start Hal
01-11 11:36:56.966 1417 1889 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle
It obviously has something to do with the updated ROM, but what could the problem be? Could it be because with the latest ROM update the developer changed the install procedure?
Before it was:
Now there's just a big .zip file to flash with fastboot update {filename}.zip, but there are a lot more .img files than before in the .zip:
- $ fastboot flash boot boot.img
- $ fastboot flash dtbo dtbo.img
- $ fastboot flash system system.img
- $ fastboot flash system_ext system_ext.img
- $ fastboot flash product product.img
- $ fastboot flash vbmeta vbmeta.img
- $ fastboot flash vbmeta_system vbmeta_system.img
boot.img, boot_debug.img,dtb.img, dtbo.img, odm.img, product.img, ramdisk.img, ramdisk-debug.img, ramdisk-recovery.img, recovery.img, super_empty.img, system.img, system_ext.img, userdata.img, vbmeta.img, vbmeta_system.img, vendor.img.
Flashing back LineageOS stock kernel makes WiFi work again, even with Magisk, but I miss this kernel.
I think there's some conflict with the img files, but I'm no expert. Could someone help me?
Thanks!
Damn, that sucks. It was working great before. Maybe I'll try asking in the ROM thread, thank you.For OOS android 11 only...
AOSP code for kernel has many changes. Something changed with WiFi which is why it doesn't work anymore. You were lucky it even worked before.
1. Sorry but no, no sound control available for any sm8250 kernels afaik@acuicultor
Sup bud, thanks for putting your project out there to all of us to enjoy!
I'm rolling with a rooted OP8, featuring A11 OB5 + xXx + Acc module. Using FKM to manage kernel options.
I'd like to ask if:
1. Does it have sound control? I'm looking forward to be able to improve my mic input volume, so ppl can hear me better.
2. Does it have battery idle? Device starts to draw power directly from the power outlet, once Acc does reach a given battery level, allowing you to let it connected to the charger all night long, reducing battery heat and stress.
Yes, although kernel sources aren't out yet but you're safe.Just updated system to 11.0.3.3.
Is it safe to flash the latest radioactive Kernel ?
You can, but it's recommended that you flash stock boot.img first to avoid issues.can i flash this over another custom kernel (Omega kernel)?
Fingerprints working perfectly on my device and for everyone elsePerfect kernel, but, enrolled fingerprints aren't recognised on 11.0.3.3. Damn!
After many hours, I found out that weirdly, it was kcal's fault.Fingerprints working perfectly on my device and for everyone else
wohoo finally!Hi folks, finally had the time for updating, added custom roms support, you must flash the correct zip, take a look at flash instructions in op, like always download links and detailed changelog in op.
Enjoy!!!!