Guys, I'm on Oxygen OS 5.0.4 and I'm on HolyDragon Kernel. HolyDragon Kernel supports Spectrum, but in my case it's showing that it doesn't support my current kernel and I need to contact the Dev of HolyDragon. Why is it so?
Because ROM has to support it too, if I recall correctly
Related
Hi,
up until 7.1.2 I used to run 2-3 roms in multirom, six or nitro as primary purenexus as secondary. However six's newest Oreo rom, it would install new kernel (i think) with it which does not support kexec (don't quote me on it either). Where as before I always used Kexec supporting kenrels such as franco, elemental and b14ckb1rd. Now I understand things very basic not in depth. And I understand why custom kernels for N6 might not be out already (since google didnt push out official oreo update for N6). My question for devs is should there be kernels out there in near future that would support Oreo and multirom same way it used to be till 7.1.2? Not asking for when not asking why not yet just asking if in future will it happen? If so (this question is just to understand) would that kernel be based on kernel for N6P or N5x or Pixel?
I would greatly appreciate if anyone can explain me. If a kernel developer wants to explain in great technical details I would love to read up. Thanks.
BTW the reason I asked this, is because in my experience, current custom kernels would not boot Oreo beta rom. and I am assuming they would not boot any future 8.0 roms as support for 8.0 is not listed under them only support for until 7.1.2 is listed. I am noob so feel free to correct me wherever i was wrong.
nanunoran said:
BTW the reason I asked this, is because in my experience, current custom kernels would not boot Oreo beta rom. and I am assuming they would not boot any future 8.0 roms as support for 8.0 is not listed under them only support for until 7.1.2 is listed. I am noob so feel free to correct me wherever i was wrong.
Click to expand...
Click to collapse
Devs are working on making Oreo stable with it's core features and when that's done the kernel and feature development will start picking up. As of now you'll have to wait but by experience from seeing older phones with dropped official support that has received newer Android versions by custom roms, multirom has worked so I don't see any issue. Only time will tell. Right now getting all core features stable is prio number 1.
I recently purchased a OnePlus 3T phone. Which Oreo ROM and Kernel that supports EAS are you guys using?
AFAIK, most do. If you're unsure about it, you can check the Kernel Description in the Thread. It usually states the features.
I'm not sure about the included Kernel in most ROMs, but the Kernels here on XDA mostly do support it.
Hi all
I have problem in compiling kernel source for Moto G9 Plus. There are apparently 2 versions of kernel source for Moto G9 Plus. There is one source in this link that 's the stock kernel (company released kernel ver. 4.14.117) and the other source that 's released by the experts community in this link.
I can build the community released kernel source, easily through clang or gcc but I can build the stock kernel neither by clang nor gcc (aosp or my host ubuntu or gcc-linaro versions) and I face with different types of errors consecutively (related to compiler version or configuration and code syntax)!
The main question and ambiguity for me is that if it is possible for a company to release a source code, erroneous and buggy or it can be built with a special compiler config or version or under a specific condition?!
Thanks in advance
Sapper Morton said:
The latest tag is available here:
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QPAS30.19-Q3-32-50-5
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QPAS30.19-Q3-32-50-5
github.com
As for the compiling errors; audio drivers, wlan and etc, are not included in that repository, you should included yourself:
https://github.com/MotorolaMobilityLLC/vendor-qcom-opensource-audio-kernel
https://github.com/MotorolaMobilityLLC/vendor-qcom-opensource-wlan-qcacld-3.0
About the Toolchain, you got that right, usually OEMs will use the default compiler that's matching the release tag.
The custom tree you linked in has these and more resolved; not to blame Motorola or Lenovo, but CAF itself, so a learning curve is necessary.
Click to expand...
Click to collapse
Thanks for your help
but now another question is how can we understand which additional source (just like above two other sources you mentioned alongside the original source) is needed when we want to compile a kernel source?
hi
I have compiled stock kernel of Moto G9 Plus (odessa) based on the tutorial on this link successfully. when I replace the stock kernel (in boot.img) with the new compiled one (Image.gz), the phone has no problem in boot process but it's touch screen does not work and I can not login to the OS. can anyone help me to understand the issue and help to fix the problem?
note:
I know 3 commits (1, 2, 3) is needed to solve the issue about working the core kernel (kernel modules not compiled and not integrated with the core) correctly with kernel modules existing inside the OS from before (thanks @erfanoabdi for explanations and the commits!)
deheshjou said:
hi
I have compiled stock kernel of Moto G9 Plus (odessa) based on the tutorial on this link successfully. when I replace the stock kernel (in boot.img) with the new compiled one (Image.gz), the phone has no problem in boot process but it's touch screen does not work and I can not login to the OS. can anyone help me to understand the issue and help to fix the problem?
note:
I know 3 commits (1, 2, 3) is needed to solve the issue about working the core kernel (kernel modules not compiled and not integrated with the core) correctly with kernel modules existing inside the OS from before (thanks @erfanoabdi for explanations and the commits!)
Click to expand...
Click to collapse
Hi, just curious how your kernel worked out? Is there any chance you are planning on sharing your work? This device could really benefit from a good custom kernel for stock sdcardfs A11, and one for asop(A11&A12) roms.
I really just need a custom kernel for Android 13 that uses the wireguard kernel module. Anyone know if ANY custom kernels with wireguard support in them for Android 13?
I'm looking for an A13 ROM or Kernel for this device which has wireguard kernel module support baked in. AFAIK the last one I'd used was the fsociety tribute kernel for A12 but have since moved on. I feel like there has to be something? I was looking in to building the kernel from source and adding it in myself - but I currently don't have the hardware to achieve this task. Any help would be super.
Disregard unless you want to share your preferred option. Found Sleepy Kernel via the fsociety telegram channel. Works like a charm!