YesWas editing the "supported version" line the only edit you had to make or was there more to it? I don't wanna miss anything here.
Thank you, kernel is working. Adrenoboost disappeared from kernel settings. Can you confirm?
A few features disappeared. Adreno boost, wakelock blocker, display color and advance colors, etcThank you, kernel is working. Adrenoboost disappeared from kernel settings. Can you confirm?
Yes!!Thank you, kernel is working. Adrenoboost disappeared from kernel settings. Can you confirm?
I'm also using Nameless ROM, but when I flash the kernel and reboot I get a message saying "There's an internal problem in your device.". The phone worked fine, but I went back to backed up Kernel. Does this message also show up for you? If so do you just ignore it? I'm pretty knew at flashing Kernels and I'm using FKMIf anyone's thinking about using this kernel with Nameless ROM, i just flashed it and phone is flying! Just noticed that haptics are a little bit stronger, but it's not an issue, it's a feature!@eng.stk do you have in your plans update kernel source to 4.19.4xx?
I don't get this message.I'm also using Nameless ROM, but when I flash the kernel and reboot I get a message saying "There's an internal problem in your device.". The phone worked fine, but I went back to backed up Kernel. Does this message also show up for you? If so do you just ignore it? I'm pretty knew at flashing Kernels and I'm using FKM
I also got this message. But phones workers perfectly fine. And I get that message every reboot.I'm also using Nameless ROM, but when I flash the kernel and reboot I get a message saying "There's an internal problem in your device.". The phone worked fine, but I went back to backed up Kernel. Does this message also show up for you? If so do you just ignore it? I'm pretty knew at flashing Kernels and I'm using FKM
This used to mean you're on the wrong base build for the ROM or your vendor img is not updated. Not sure this is still the issue now thoI also got this message. But phones workers perfectly fine. And I get that message every reboot.
I'm on the latest nameless build and the latest kernel. It's unnerving, but like I and another person said the phone works perfectly fine no issues so until I see something wrong I'm gonna stick with this kernel, seems to be pretty decentThis used to mean you're on the wrong base build for the ROM or your vendor img is not updated. Not sure this is still the issue now tho
Do you have to build kernel from source to do this or can you just edit this line and then zip the files back up?
Only edit lineDo you have to build kernel from source to do this or can you just edit this line and then zip the files back up?
Hi, can you help me how to change the file step by step please ?Thank you, kernel is working. Adrenoboost disappeared from kernel settings. Can you confirm?
I wouldn't recommend this kernel on evoX 7.1 because some features disappear like adrenoboost and the option to turn off fsync. But you are welcome to try it out anyways.Hi, can you help me how to change the file step by step please ?
I want to flash over EvolutionX 7.1.
Hi, can you help me how to change the file step by step please ?
You should MSMCan somebody please upload one plus 8 pro model 2023 qcn file. i deleted mistake qcn file and now i dont have signal my phone. sim card not recognize.
i need 2023 model qcn file
- Build with custom upstream LLVM 15.x (Clang 15.0.6 + LLD linker + IAS)
- Rebase and cleanup for lineage-20.0
- Merge lineage-20.0 from LineageOS/android_kernel_oneplus_sm8250
- defconfig: sync with lineage-20.0-20221231-nightly
- makefile: disable some clang spam
- drivers: additional build/linker fixes
- defconfig: adjust cmdline for faster boot
- AnyKernel3 updates (v20221201)
- For root, Magisk 25.2 or newer is mandatory
- Build with custom upstream LLVM 15.x (Clang 15.0.7 + LLD linker + IAS)
- Merge lineage-20.0 from LineageOS/android_kernel_oneplus_sm8250
- AnyKernel3 updates (v20230120)
- For root, Magisk 25.2 or newer is mandatory
- Build with custom upstream LLVM 15.x (Clang 15.0.7 + LLD linker + IAS)
- Merge lineage-20.0 from LineageOS/android_kernel_oneplus_sm8250
- defconfig: sync with lineage-20.0-20230112-nightly
- defconfig: disable KALLSYMS_ALL
- AnyKernel3 updates (v20230110)
- For root, Magisk 25.2 or newer is mandatory
- Build with Google Clang 12.0.7 + LLD linker
- Add some build improvements
- Silence a couple logging and debug
- wireguard updates (v1.0.20210606)
- AnyKernel3 updates sync
- For root, Magisk v23.0 or newer is mandatory
- Synchronize codes for OnePlus 8T Oxygen OS 11.0.12.12.KB05AA and OnePlus 8 Oxygen OS 11.0.9.9.IN21AA and OnePlus 8 Pro Oxygen OS 11.0.9.9.IN11AA
- AnyKernel3 updates (v20211215)
- For root, Magisk v23.0 or newer is mandatory
- Build with Google Clang 12.0.7 + LLD linker (updated)
- hwtracing: Add entries from kona-coresight (tentative less idle draw)
- defconfig: enable ld deadcode elimination
- arm64: Allow LD_DEAD_CODE_DATA_ELIMINATION to be selected
- arm64: Keep alternative-instruction sections
- AnyKernel3 updates (v20210721)
- For root, Magisk v23.0 or newer is mandatory
- Revert "fs: exfat: sync with v5.8-1arter97"
- defconfig: disable IKHEADERS
- Remove some logspam and debug
- net/wireguard: merge v1.0.20210424
- AnyKernel3 updates sync
- For root, Magisk v22.1 or newer is mandatory