yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] alma23:
Thanks for your answer, if I can help you in any way just ask :D

Anyway, now that I know that there is a ROM based on sultan's and made by you I think I'll try that and let you know.

EDIT: Tried your ROM with no luck (your latest ROM and kernel dirty flashed over latest sultan, Magisk V14).
[ONE Original Android Development] solar666:
Sorry not being clear enough. I meant kernel v13 and not magisk.
[ONE Original Android Development] alma23:
Ops, thank you!
[ONE Original Android Development] solar666:
I never said magisk v13. I always talked about the kernel version. So for me kernels v13 is working and starting with kernel v14 it breaks installing magisk modules at least for some of us like reported in this and your rom thread.

I assume an incompatibility of updates, like security or whatever with magisk way of installing modules.
[ONE Original Android Development] Tomoms:
I meant Neon v13 + Magisk v14.5 + my ROM xD Got confused somehow.

Anyway, if you could try to install some module, then send me: a logcat, taken while installing the module; and a dmesg, taken after installing the module, it could be helpful.

To send me the dmesg just open a terminal emulator app and run

su -c 'dmesg > /sdcard/kernel.log'

and kernel.log will be the name of the file I need.
[ONE Original Android Development] solar666:
Thanks for your feedback.

Will try to do so on the weekend.
[ONE Original Android Development] areallytinydot:
I'm curious why most aren't using the Oreo roms. Did you guys try them out and didn't like it?
[ONE Original Android Development] Tomoms:
I personally don't like AOSP ROMs, I prefer LineageOS, thus, since LineageOS 15(.1) isn't ready yet, I'd rather wait till it's complete, with all the features I usually use, than use a partially incomplete OS. I have decided to wait until there is a deeper division between LineageOS and AOSP, thus choosing the former would actually make more sense.
[ONE Original Android Development] xlollomanx:
Me too prefere wait until los 15 was complete. I need perfectly working device.

Sent from Oneplus One
[ONE Original Android Development] Tomoms:
Neon v15 is available! Download it from here.

It mainly brings some security fixes, improved memory compaction routines and some patches by Nvidia to improve power usage, so you might get slightly better battery life after flashing this new kernel. Let me know your opinions :)
[ONE Original Android Development] murti52:
Is this included in your latest build? Or will have to flash it separately?
[ONE Original Android Development] Tomoms:
In the changelog of my latest LineageOS build you can read it's included. Please, next time, read all the available info before asking a question.
[ONE Original Android Development] murti52:
Sorry, will do it next time :good:
[ONE Original Android Development] solar666:
So, did the tests.

Started with a clean flash of your current ROM + Neon v13 + Magisk v14.5

Modules can be installed and are showing up as installed after a reboot.

Made a logcat and dmesg as requested. Please find both with "good" in their names attached.

Furthermore flashed just Neon v15 on top of the previous installation.

Previous modules were still there but I was not able to install new modules persistently, which means they are gone again after reboot.

Made a logcat and dmesg as well in this config. Please find both with "bad" in their names attached.

Hope this helps to get a step further.

From a brief scanning I can see an I/O Error with v15 which is not there with v13.

Just to prove that the kernel is the issue I went on and installed again Neon v13 again on the same installation and modules can be installed persistently again ...

Edit: had to put together a zip since the logs where exceeding the max upload size.
[ONE Original Android Development] AKA#1:
[MENTION=5727088]Tomoms[/MENTION] I'm getting this error when running youtube-dl from Termux

"Fatal Python error: failed to get random numbers to initialize Python"

BTW I'm getting the same error on V14 and V13 versions of the kernel. Is it something related to the backported random number generator?
[ONE Original Android Development] Tomoms:
It might be related. Try to open Kernel Adiutor and in the Entropy tab set Read = 256 and Write = 512. Is youtube-dl working now?
[ONE Original Android Development] AKA#1:
I did as you asked, Set to Boot and rebooted. Getting the same error. Any clue?? ?
[ONE Original Android Development] Tomoms:
I made some researchs and it seems that this could be related to a bug that was fixed in upstream python in February, however the bug was fixed on python 3.5, 3.6 and 3.7 if I recall correctly, so if the python environment you are using was built before the bug was fixed, or you're using a different version (3.4? 2.7?), the bug is still present. I'll try to revert the random number generator updates and rebuild the kernel, then you should test it and let me know if the issue is fixed.
[ONE Original Android Development] solar666:
[MENTION=5727088]Tomoms[/MENTION]; Did you find time to check the logs? Do you need me to get more logs on the issue to better understand?
[ONE Original Android Development] Tomoms:
Unfortunately, the logs aren't really helpful because they don't show any error... I took some logs while installing Magisk modules on my phone and my logs aren't very different from yours... I'll double-check them when I have some time.

I've also released v16, that is a kernel featuring lots of source updates and backports for important parts of Linux. There are also minor adjustments that might improve device responsiveness a little bit. I've also updated the AutoSMP hotplug and now it should be more reliable than ever. Enjoy this new release, and let me know your opinions about it :)
[ONE Original Android Development] solar666:
Thanks for your answer.

What about the I/O Error present in the logs with v15?

They are not there with v13.
[ONE Original Android Development] AKA#1:
I reinstalled python package "python/stable,now 3.6.4 arm [installed]", but the error persists.
[ONE Original Android Development] Tomoms:
Try this kernel, please: https://drive.google.com/open?id=1rtlfgHT6vFMNKaOWoahTfJ5NjZEtIhPU
[ONE Original Android Development] AKA#1:
Sorry , but Python's giving the same error even after installing the modified kernel.
[ONE Original Android Development] Tomoms:
What a pity! I'll send you a new kernel to try soon.
[ONE Original Android Development] Tomoms:
I've released a minor update! This kernel mainly fixes the problems someone faced when installing Magisk modules, and brings some useful improvements and optimizations: general performance might be slightly better. Let me know what are your opinions :)
[ONE Original Android Development] f41lbl0g:
I just installed this kernel on RR sultanized, but its lagging a lot. When I opened it up in kernel adiutor, it only goes up to a max of 1.5 ghz clockspeed even if I click higher frequencies. Is there any way to increase this?
[ONE Original Android Development] dudas89:
All the past releases had the same problem on my phone. I don't know if it is related, but I cleaned the Kernel Adiutor-Mod data, rebooted, flashed the kernel, wiped the Cache and the Dalvik Cache, and it turned much smoother. Try it! ;)
[ONE Original Android Development] wangyouCN:
When I used muilrom to install Ubports, the recovery hint kernel did not support setting swap. Although the final hint of success, but can not start, and swap have a relationship?

Bother you…:highfive:
[ONE Original Android Development] Tomoms:
I can enable swap support, but nonetheless I can't guarantee that the kernel will work properly with Ubports, then.
[ONE Original Android Development] wangyouCN:
No matter how thank you for doing all this,。I will experiment。 thank you！！！
[ONE Original Android Development] Tomoms:
Ok, so I've released v16.2. It's a very small update that brings some source updates, adds swap support and improves power consumption by disabling the automatic memory compaction that I added in the past releases of the kernel. Enjoy!

Here's the new kernel: https://androidfilehost.com/?fid=817906626617954941
[ONE Original Android Development] nthacks:
Is the latest release compatible with Oreo roms? (Aosp 8.1 or los15.1)
[ONE Original Android Development] Tomoms:
No, it's not, as there's a small change (required for Oreo compatibility) that's still missing. What's more, you'd better keep in mind that this kernel is made for "sultanized" ROMs, and not all the ROMs that feature Sultan's camera HAL (such as AOSP 8.1, if I recall correctly) are "sultanized". For now, there are no "sultanized" Oreo ROMs. Having said this,

in the future

you could also try to flash this kernel on AOSP 8.1, probably most things would work, however I wouldn't be able to provide any help in case of issues.
[ONE Original Android Development] borzowsky:
what about different blobs for camera? Did you have any chance to experiment with that?
[ONE Original Android Development] Tomoms:
I gave a look at the OOSv3 camera kernel driver, but I haven't had enough time to tinker with it yet. Sooner or later I'll try to implement it, and I'll let you know if it's doable or not.
[ONE Original Android Development] Inferillum:
Hey, have you thought about supporting Kali NetHunter? There are only 2 patches that need to be applied (I can supply those).
[ONE Original Android Development] Tomoms:
I have thought about many things, but I've never had enough time to learn about them & try them all. Soon I'll give a look at the Kali Nethunter patches :) Currently I'm working on other parts of the kernel. Anyway, I'll keep you informed! If you have already applied them to the kernel souce and tested them, please provide them to me, it'll ease & speed up the whole process :)
[ONE Original Android Development] Inferillum:
I did, but not on CAF sources and it might have few mismatches...
[ONE Original Android Development] prinz3nroll3:
hello,

thanks for the kernel.

i ve try the kernel with lineageos, but i cant use the camera and the flashlight icon is disabled.

some hints for me?

thx
[ONE Original Android Development] Tomoms:
You're using the wrong kernel. This kernel, as the title and the first post of the thread say, is compatible with CAF ROMs, i.e. those built from Sultanxda's sources.
[ONE Original Android Development] Tomoms:
A new kernel (v17) is available! It brings several source updates, in particular you might be interested in the updated f2fs driver (backported from Linux 3.10) and in the random number generator stack, that is backported from Linux 4.1. There are some memory management updates and tweaks that might improve battery life, and I've also enabled ZRAM, zsmalloc (both backported from Linux 3.17) and zcache (backported from Linux 3.18), so if someone wants to use them for whatever reason, they can. I've added a new TCP congestion control algorithm called "ascarex", that merges the best parts of westwood and reno; ascarex is enabled out-of-the-box. The other changes are minor and are mostly related to the ARM architecture or to our SoC.
[ONE Original Android Development] fabio_mcz123:
I can not find file available for download
[ONE Original Android Development] Tomoms:
Fixed. The file is now present.
[ONE Original Android Development] vicky2131:
[MENTION=5727088]Tomoms[/MENTION] Hello there, Just wanted to ask you some things before flashing this kernel. I'm using sultan's 14.1

Is your kernel- flash and forget(like franco's or needs tuning using kernel auditor) ? I'm asking because i'm not so good at tuning kernels for battery management. My main priority was battery before trying sultan's rom but now i'm using it for few weeks and it gives me really good camera clicks and ui experience. So i wanted to ask about your kernel before trying out.

Thank you in advance!

PS: I was using lineage OS and franco kernel and battery life on it was really amazing.
[ONE Original Android Development] Tomoms:
No, my kernel is not completely flash-and-forget. Or, to be more precise, there are some default settings that are fine-tuned by me, but other tweaks must be applied by hand. However, if you flash it and let it work as is, the experience shouldn't be bad, it'll be quite similar to using Sultan's default kernel without tweaks. So my advice is to try it, and if you want a simple yet effective tweak to get better battery life, open Kernel Adiutor and in the CPU Hotplug tab disable MPDecision and enable AutoSMP. That's it. If you're not satisfied, reverting to Sultan's default kernel is easy, you just need to reflash the ROM.
[ONE Original Android Development] vicky2131:
Thank you so much for explaining about the extra tweaks too! Will try this weekend and let you know.
[ONE Original Android Development] Tomoms:
[MENTION=5218735]AKA#1[/MENTION] the new v17.1 fixes the problems you encountered when using python in Termux. I've tried it myself, youtube-dl works fine!
[ONE Original Android Development] AKA#1:
It really works, man. Thank You so much.:D
[ONE Original Android Development] Tomoms:
I've uploaded a new release. It brings hundreds of "invisible" yet important updates and fixes. It's also slightly more optimized and contains a small fix that might help saving a little more battery life when the device is suspended. Please read post #3 because I've noticed there's something wrong with the CPU governors and hotplugs in my kernel. I'll look into these problems as soon as possible; in that post I give a suggestion about which hotplug and governor to use.
[ONE Original Android Development] Tomoms:
New kernel available! It's a minor update but it fixes some nasty bugs with the impulse & blu_active cpufreq governors (such as core 1 being kind of stuck at the maximum frequency), now I'm using impulse and the frequencies are scaled correctly. The /data partition will be mounted with the latemount mount option after flashing v18.1, thus reducing the time spent showing the kernel splashscreen when booting the phone. Last but not least, I've applied the zen-tune tweaks to the task scheduler.
[ONE Original Android Development] Berth666:
thanks for your work and for the new kernel.

With v18.1 my phone has some problems, it restarts while using tomtom navigation after some minutes.

tried different governors but all the same - no problems with v18.0
[ONE Original Android Development] Tomoms:
Provide some logs, please (after the next reboot happens, wait for the phone to boot up again and send me last_kmsg file, located in /proc).
[ONE Original Android Development] Berth666:
ok, I'll send you the last_kmsg after next time it happened ;)
[ONE Original Android Development] Tomoms:
I've released a new minor update! It features a couple of fixes for sdcardfs and some updates that improve the power efficiency of the interactive and impulse cpufreq governors.
[ONE Original Android Development] Berth666:
thanks a lot!

Do you found something in my last_kmsg?
[ONE Original Android Development] Tomoms:
Yes but didn't even try to fix the issue. I'll do it in the next days.
[ONE Original Android Development] :
Hey there!

I haven't updated to 18.2 yet, but here's a report of (I think) 2 of three reboots I experienced a few minutes ago. The first one happened while I was browsing on chrome, second when I was reading the log and third right after the first unlock I did once the phone rebooted.. hope it helps!
[ONE Original Android Development] Tomoms:
You faced the same problem [MENTION=654648]Motocross-FrEaK[/MENTION] faced. Something GPU-related. I'll look into it as soon as possible.
[ONE Original Android Development] Tomoms:
[MENTION=654648]Motocross-FrEaK[/MENTION] [MENTION=5047631]Nello96[/MENTION]

Neon v18.3 should fix the crashes you faced. Please confirm whether the problem is solved or not.
[ONE Original Android Development] Berth666:
for me it's working....thanks a lot!
[ONE Original Android Development] :
No luck ?
[ONE Original Android Development] Tomoms:
Your log doesn't show any error at all. The crash that caused the reboot left no traces in the kernel log, so I cannot know what happened and why. The log however shows a large amount of kernel messages printed by the battery gauge driver, and if I recall correctly I've also experienced a reboot, once or twice, that left similar messages in the log. However, it happened so rarely (twice in more than half a year, maybe) that I've never looked into the actual issue.
[ONE Original Android Development] :
I can confirm that after that reboot the phone kept working properly for the whole day ?
[ONE Original Android Development] Tomoms:
I've uploaded a new minor update. It brings a couple of fixes & improvements.
[ONE Original Android Development] Tomoms:
I have released v18.5, a minor release with only some security fixes.
[ONE Original Android Development] oscarmalo:
for me is a **** kernel... very laggy, a lot of reboots, etc.
[ONE Original Android Development] xlollomanx:
Then don't use it and move on. This kind of reply is very rude and not necessary, especially toward the developer and its work.
[ONE Original Android Development] Kéno40:
For me that kernel is very good.

But on the last version, I have some little vertical lines appearing. I too start to have reboot from time to time. Before jan, I never had.

Maybe I have to change settings to force GPU processing?

Anyone else have problems like that?

I'll jump to an other kernel to see if it's the same.
[ONE Original Android Development] Tomoms:
Hi everybody! After two months of inactivity, I've released a new kernel. It was pretty obvious that there was something wrong with Neon kernel, since many users reported instabilities and performance issues. I myself was aware that there were some problems, especially with graphics performance, however I tried to overlook them for some time. Then, a few weeks ago, I decided to restart the whole thing from scratch, and now here's the first release of the "new" Neon kernel. Many features, many updates are lacking, and I'll do my best to re-add them one by one, without affecting performance or stability. So read carefully the changelog in the first post, and keep in mind that if a feature from the older Neon versions isn't listed, it means it's not present yet.

The new kernel is compatible with Sultan's LineageOS, my LineageOS (btw, new build incoming) and it should be compatible with all the Nougat ROMs built with Sultan's device & kernel trees.

Download link: Neon v19

I'm here, ready to answer to any question and hoping to receive some feedback!
[ONE Original Android Development] JJohnson1988:
Welcome back, and thanks for the update. :)
[ONE Original Android Development] :
Can you compile kernel for Oreo?
[ONE Original Android Development] solar666:
:good:

[MENTION=5727088]Tomoms[/MENTION]; Would really like to see too an additional custom Kernel for Oreo!
[ONE Original Android Development] Tomoms:
Actually, this kernel is 99% compatible with Oreo. Only one minor change is needed to get it to boot any of the newer Oreo ROMs. Since this kernel is only made for Sultanized ROMs, however, I'm afraid it won't be a good idea to use it on any ROM that uses Sultan's camera HAL (e. g. AOSP 8.1, if I recall correctly); in fact, it'd be better suited for Sultan's LineageOS 15.1, which may or may not come in the future. Anyway, I have no plans to start working on a Oreo kernel based on LineageOS's trees.

Long story short: I can make an experimental build with Oreo support in the next days, however I do not guarantee it'll work flawlessly. If any of you guys is using an Oreo ROM that implements Sultan's camera HAL and would like to try it out (just for the sake of testing something new - and it'd be very useful for me to know that the kernel, at least, boots), just drop me a PM.
[ONE Original Android Development] Бахрам Байрамза:
This kernel supports Nethunter patches?
[ONE Original Android Development] Tomoms:
Not as of now, but I might consider adding them in the future.
[ONE Original Android Development] Бахрам Байрамза:
Thanks. Sound control engine added to the this kernel?
[ONE Original Android Development] Tomoms:
Not yet. Please check out the changelog, it lists all the features that are available in v19.
[ONE Original Android Development] Tomoms:
I've uploaded a new release!

Download link: Neon v20

It brings quite a lot of optimizations, improvements, fixes and tweaks, so I suggest you to flash it soon :)

You can check Github if you wish to know what features and patches I have added to the kernel.
[ONE Original Android Development] prerakr:
I noticed that the new releases don't have the kexec hardboot patch anymore. Are you planning on adding it again anytime soon?
[ONE Original Android Development] Tomoms:
Sure. Give me a couple of days and you'll have it back :)
[ONE Original Android Development] dudas89:
Tomoms, thank you for your work! I am a Lightning Kernel user for a very long time, but I've been trying your kernel releases and, for the first time, this v20 is not laggy anymore :) I did want to use your kernel as a daily driver, but it has been impossible. It was very laggy, even on stock settings, but this v20 appears to be fine on Sultan's ROM. Thank you!

However, I do miss some options and features, such as CPU governors, hotplugs, I/O schedulers and CPU undervoltage. Impulse and AutoSMP give me good battery life, for example, and I miss the option to undervoltage (-75 mV in my case). Other thing I miss is the option to set the maximum charging current. In you kernel the charging speed is very low (400/500 mA), while in Lightning's I can set the charging current to 1200 mA and it charges at this rate, using the exact same wall charger and cable.

Thank you once again for updating! :)
[ONE Original Android Development] Tomoms:
Hello!

The next release will bring the charging speed interface, CPU UV, the impulse CPU governor, sound control and kexec-hardboot support.
[ONE Original Android Development] dudas89:
And AutoSMP, if you may :P

Thank you so much! :laugh:
[ONE Original Android Development] Tomoms:
No, I won't implement AutoSMP in the next version. I need to look at it because I'm afraid it needs a little code cleanup. Most probably it'll be present in the following release.
[ONE Original Android Development] Tomoms:
Neon v21 is available! It brings many features so check out the changelog in the first post. More details on the commits I've implemented can be found on GitHub.
[ONE Original Android Development] Tomoms:
Hello! I've uploaded a new minor update: v21.1 is just a small update which fixes a regression in the kgsl driver that could cause poor performance in certain scenarios.
[ONE Original Android Development] Berth666:
thanks a lot for the new relases!
[ONE Original Android Development] Tomoms:
Hello! I've released a new update :) [MENTION=5703024]dudas89[/MENTION] AutoSMP is now included in the kernel :)
[ONE Original Android Development] dudas89:
Many thanks!
[ONE Original Android Development] MaurixMystic:
full compatible with last build 14 may sultan 7.1 rom ?
[ONE Original Android Development] Бахрам Байрамза:
Yes
[ONE Original Android Development] olygopoly:
does this kernel works with oreo 8. 1 rom such as tugapower ?
[ONE Original Android Development] Tomoms:
No, it's only for CAF Nougat ROMs, at the moment.
[ONE Original Android Development] herz.AG:
Hi,

sorry for asking nearly the same question: Is your kernel compartible with AOSPExtended (oreo v5.5)? And how do I recognize a CAF and a non-CAF kernel/rom when not stated in the headline?

Kind regads,

herz.AG
[ONE Original Android Development] Tomoms:
No, as you can see from the thread's title, this kernel is compatible with Android 7.1 ROMs. CAF ROMs are ROMs built using Sultanxda's sources, not only for the camera HAL, but for all the other components he has provided alternate sources. As of now, there are no Oreo CAF ROMs. Sooner or later I'll try to build one, but I'm not very confident it'll work well, due to my lack of skills and experience in this field. Anyway, if any other dev or I succeed at building a CAF Oreo ROM, this kernel will be almost immediately compatible with it. Otherwise, this kernel will be kind of dead.