yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Tomoms:
New version available!

Download here: https://www.androidfilehost.com/?fid=962339331458997047

This kernel features some kernel source updates, and the DCACHE_WORD_ACCESS optimization is now enabled.
[ONE Original Android Development] MaurixMystic:
Add support Alucard governor please

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] Tomoms:
Nope, sorry, there won't be any new version of this kernel for Nougat. I'll start working on Oreo next week, and if I manage to release my builds, they'll feature this kernel (in this case, development of this kernel will continue but new versions will only support my Oreo ROM).
[ONE Original Android Development] Lisko:
Will you consider franco's thermal driver which is less aggressive in future?
[ONE Original Android Development] Tomoms:
I'll analyze both thermal drivers and take a decision. As of now, I have no idea what changes between the two. As I've already said, I'm still quite a beginner in the OPO world.
[ONE Original Android Development] borzowsky:
What kind of options do you raccomand to keep the phone fluid for messaging, music, web browsing and improving battery life? Right now I barely have 2 hrs screen on time because the battery is old.
[ONE Original Android Development] Mr.Ak:
Then you should consider changing your battery.

No changes can do magic to take your old battery's 2hr sot to 4hr sot.
[ONE Original Android Development] Tomoms:
I agree, you should consider changing battery. A kernel is a kernel, it cannot do miracles. There are no recommended settings as the phone already works very well with the default kernel, the goal of this custom kernel is to let you use some features (such as sound control and sdcardfs) and provide some overall optimizations to make your phone really fly. I only suggest to disable mpdecision and use AutoSMP instead, according to my experience it helps saving a little power without affecting performance at all. Concerning everything else, do whatever you prefer.
[ONE Original Android Development] borzowsky:
Already ordered it but I'm not sure it will solve it.
[ONE Original Android Development] pankspoo:
Update?
[ONE Original Android Development] Tomoms:
Have you ever heard about that XDA rule that states that you shall not ask for ETAs? A new update will be released when it's ready. I can only tell you that you won't have to wait too much.
[ONE Original Android Development] Mr.Ak:
It should,if you order a battery which is recommended on battery thread.

---------- Post added at 02:11 PM ---------- Previous post was at 02:10 PM ----------

Can you suggest some settings to optimize this kernel for gaming?
[ONE Original Android Development] Tomoms:
Set the CPU governor to ondemand and maybe bump the minimum GPU frequency to the second lowest value.
[ONE Original Android Development] Tomoms:
New update released! The changelog is in the first post, on github you can find every single commit.

Download link: Neon v2
[ONE Original Android Development] moneyvirus:
I'm gonna give it a try

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] zalamandra:
Does it support undervolting?
[ONE Original Android Development] moneyvirus:
Nope I don't see it

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] Tomoms:
Not yet, but I'm working on it.
[ONE Original Android Development] Tomoms:
I've released another update! Download it from here, and check the 2nd post of the thread for some useful info.
[ONE Original Android Development] hkjr:
Truly enjoying your work
[ONE Original Android Development] Бахрам Байрамза:
Hmmm... Camera not working on the PA 7.2.1!
[ONE Original Android Development] SaurabhMumbaiOneS:
Corrupt File

Hey, I am getting Flash Failed, Corrupt File error in TWRP. I saw it coming, since file I downloaded from AFH is 5.57MB. Will wait for the update.

EDIT: Re-downloaded file flashes smoothly.
[ONE Original Android Development] Tomoms:
The downloaded file is smaller because the kernel now is compressed with XZ rather than with Gzip. So I invite you to re-download and re-flash.
[ONE Original Android Development] Tomoms:
If the ROM doesn't use Sultan's camera HAL, it won't work.
[ONE Original Android Development] Tomoms:
v3.1 is available here: AndroidFileHost

It contains all the latest updates Sultanxda included in his latest LOS build, and I've also added the "impulse" CPU governor.
[ONE Original Android Development] bigtastie:
The battery charging limiter you put in your kernel is limited to your own Neon kernel right? How much current can the OPO safely draw? The SD801 supports QC2.0 (3 A), but when I charge my OPO I rarely get anything more than 1 A.
[ONE Original Android Development] Tomoms:
On our 3.10 kernel, max speed reportedly is 3 A, on LOS/CAF based kernels the maximum should be 2 A. Keep in mind that the charging speed is automatically scaled during the charging process; anyway I always get more than 1,5 A when charging my OPO.
[ONE Original Android Development] geokilla:
Any F2FS support?
[ONE Original Android Development] Tomoms:
F2FS is supported indeed. I'm using it on my OPO for cache and data.
[ONE Original Android Development] moneyvirus:
Testing 3.1

first cycle with sdcardfs and impulse gov and I have to say I'm impressed with the sot with my light usage

Will test end tweak a bit further

But its really smooth

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] CooperBrick:
Is it possible to add a temperature threshold for the throttling that can be set in kernel adiutor?
[ONE Original Android Development] Fatsodonkey:
One wish. 2700mhz step for cpu. :)

For gzdoom. ;)
[ONE Original Android Development] pankspoo:
Then its

become frying pan for omlet Anywhere......

No need of that
[ONE Original Android Development] Tomoms:
The parameters are configurable, but not in Kernel Adiutor. You have to browse to /sys/kernel/msm_thermal and there you'll find some files called "zone0/zone1/zone2...zone7". These correspond to 8 different throttling levels. The information is stored in this way: <frequency> <throttle_temperature> <unthrottle_temperature>. Frequency = the frequency the thermal driver sets as maximum when the temperature goes above throttle_temperature. If the temperature decreases below unthrottle_temperature, then the max frequency will be increased to the frequency written in the zone* file with a lower final number than the one containing the frequency that is set at that moment.
[ONE Original Android Development] Fatsodonkey:
Gzdoom uses single core or maybe two. I have never fried my phone with 2700mhz with uv. With 3 cores max active i think that 2700mhz is the best balance for rapid single core performance, good multi and good temps as well as good battery life.

2800mhz is too much.

There can also be profiles set with tasker etc.

Sorry for OT, but i like options that can't hurt, because there is temp limit for the phone.

There is a reason why manufacturers use high frequensies altough those throttle after long use. One is marketing, but it also helps to bump the speed up for a small period of time if the user only uses the phone as a phone and not as a life replacement. :P

Sorry for the OT. I will be quiet from now on. :)
[ONE Original Android Development] Tomoms:
Doable, but it's definitely not my priority right now.

Anyway, there's a new release that brings loads of kernel updates, fixes, enhancements and improvements.
[ONE Original Android Development] JyoNoOB:
Hi,

I just flashed this rom on Sultan-ized RR and my phone is not going into deep sleep when I turn off the screen. It stays at 300 mhz.

This was not the case with the previous kernel or another one that I had installed before this. I am also using naptime by franco to force doze but it's not working.

Can someone help me out?

Thanks
[ONE Original Android Development] yijinsa:
Deep sleep like baby here
[ONE Original Android Development] JyoNoOB:
Have you undervolted? What rom are you using?

Edit :- Problem solved.
[ONE Original Android Development] moneyvirus:
With version 4 my WiFi slowed down did you change something with the version bump maybe. Overall its a great ride with your kernel

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] Tomoms:
Thanks for your feedback! I'll check if there's something wrong in WiFi as soon as possible. If you have more details to share, post them. I'll keep you informed.

EDIT: [MENTION=4980751]moneyvirus[/MENTION] there seems to be nothing wrong with WiFi for me. I tested three different connections and on each of them I reached the maximum speed.

Could you share with us how you solved your problem? It might be useful for others, too.
[ONE Original Android Development] JyoNoOB:
I was running an older version of Sultanrom. An update fixed the issue for me.
[ONE Original Android Development] moneyvirus:
OK thanks for the heads up. Could be my crowded neighborhood will test with different bands

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] JyoNoOB:
I am getting this problem whenever I try to use this kernel (even if I make no changes in Kernel Adiutor - Settings won't open. It just shows a black screen and needs a reboot to fix it.

I am running on latest Sultanrom

I have tried clean flashing the ROM and reinstalling the kernel but the issue still persists.

The ROM works fine with stock Kernel and another Kernel I am using.

Can anyone help me?
[ONE Original Android Development] Zieloo:
Hi,

First off I wanted to thank you for a kernel with so many ways of customization. But with all these tweaking I've done, after reboot everything goes back to stock even though I have selected the "Apply on boot" option in every tab that I've made changes to in Kernel Adiutor. It is really a bummer and I'm not sure whether it's supposed to be so or it's just me having trouble.

[MENTION=309187]edit[/MENTION]

Also I cannot install anything from playstore whether I'm undervolted/on different governor or not ;/
[ONE Original Android Development] JyoNoOB:
What's the matter does the app download stop at 100% doesn't proceed with the installation. If you're getting an error what's the error?
[ONE Original Android Development] Tomoms:
It happened to me once or twice but after a few minutes the app that wasn't starting correctly suddenly restarted working properly, so I thought it had been an occasional glitch. Now that you report the same behavior, I'll look into it and try to fix this issue in the next release.

Uninstall KA, reboot, reinstall it, apply your settings and enable the Apply on boot flag. It's only you facing this issue I guess. About the Play Store issue, it's not kernel-related. I install and update my apps every day without a single problem.
[ONE Original Android Development] Zieloo:
Yeah the downloading jumps from 0 to 100% in an instant and then goes nowhere from here ;/

KA started working properly when I installed other kernel to check whether the instalation thing is kernel related, and yes it is, as the guy above also mentioned, and coming back to ur kernel KA works fine now. I don't wanna be rude but the only thing that i change is kernel and suddenly apps don't want to install anymore so my guess is that it's kernel related ;P
[ONE Original Android Development] Tomoms:
Please attempt an app installation, let it stall at 100%, open a terminal emulator on your phone and run

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

Then send me the kernel.log file you'll find in the internal storage of your device. Thank you.
[ONE Original Android Development] Zieloo:
Literally 90% of terminal apps that are available on play store are just blank when I open them on your kernel and I cannot input anything, and the one that I found to be working says there is no such file or directory lol
[ONE Original Android Development] Tomoms:
You wrote scard instead of sdcard.

BTW I'm working to fix all these issues, expect a new release tomorrow.
[ONE Original Android Development] Zieloo:
Yeah lol I'm brainless i guess. I think it's just me being stupid and my stupidity stopping me from doing anything, now I installed your kernel and tried to replicate the bug, the first app installed without any hiccup so yeah I thought maybe it will work out this time, then I wanted to update Greenify which got stuck at 61%, so I cancelled it and moved onto random app from play store and yeah it got stuck at 100%. Here is your log file.
[ONE Original Android Development] alma23:
Hi guys!First of all I wanted to thank [MENTION=5727088]Tomoms[/MENTION] for this wonderful kernel and wanted to ask for advice: in order to save some more battery you think I should enable Multicore power save? If yes, in which mode? If it can help I'm using impulse governor, AutoSMP and I undervolted for all frequencies.

Thank you :)
[ONE Original Android Development] Inferillum:
Any plans on implementing a kexec-hardboot patch? To support MultiROMs.
[ONE Original Android Development] Tomoms:
It might be useful, yes. I have always set it to "Enabled"; "Aggressive" will save even more power but it might also have a (small) negative impact on performance (actually, I have never tried it).

I will implement it. Not in the release I'll upload today, but in the following one.
[ONE Original Android Development] Inferillum:
Amazing. Really looking forward to it.
[ONE Original Android Development] alma23:
Extremely clear! Thanks again :)
[ONE Original Android Development] Tomoms:
The new release fixes the bugs reported by [MENTION=8352547]JyoNoOB[/MENTION] and [MENTION=6587525]Zieloo[/MENTION]

They were most likely caused by some mistakes I made while merging the kernel updates from the upstream 3.4.y code. Thus, now the kernel base version is 3.4.27 (as in Neon v3.1) but in this release there are some new features and improvements too, as reported in the changelog.
[ONE Original Android Development] geokilla:
Is there a way to change the kernel settings using UKM and Synapse? I flashed UKM and installed Synapse but it would give me the UCI error.
[ONE Original Android Development] Inferillum:
Amazing. Thanks for the hard work. Really looking forward to the next release that will have kexec-hardboot (for Multirom support) implemented! Thanks in advance.
[ONE Original Android Development] Zieloo:
Thanks for the update, can confirm everything is working properly so far. Btw I have the kernel adiutor mod and here the top battery charging current which can be applied is 2190 mA, do you think it's due to using sultan's rom cause I remember you mentioning that it could top out at 3A.
[ONE Original Android Development] Fatsodonkey:
Can someone help a noob with the msm_thermal zone editing?

I have changed tge values with terminal and with file manager. The values reset aftet boot.

Just asking how can i make the changes persistent?
[ONE Original Android Development] DerRomtester:
Sure they do. The values are set in the ramdisk and get loaded every boot.
[ONE Original Android Development] yijinsa:
V5 break gesture settings, aospextend rom
[ONE Original Android Development] Tomoms:
As [MENTION=4804871]DerRomtester[/MENTION] said, the default values are loaded at boot, so the only way to change them is to use an init.d shell script, but unfortunately certain ROMs don't support init.d, for example Sultan's Lineage doesn't. Adding init.d support is something I'll do soon, so eventually you'll be able to edit the thermal zones' parameters.

Only our 3.10 kernel supports 3 A charging. This kernel supports 2,2 A charging at maximum. It is possible that 3 A support is really easy to implement, but I've never looked at it. If you're interested, I'll see what I can do.

Touchscreen gestures work fine on Sultan's Lineage with this kernel. I have no idea what's the problem with AOSPExtended.
[ONE Original Android Development] Stylez Ray.:
Ah okay, so it's the kernels fault :eek:

I'm having the same problem on AEX but I wasn't sure what the problem caused. I have too much stuff customizing my phone, could be anything, so I never thought about making the kernel the culprit, didn't want to be disrespectful posting about this problem.

First I thought it was a rom related problem and then I was pretty sure it could be a problem with some substratum themes...

Really wonder how a kernel could cause this bug?! :confused:
[ONE Original Android Development] shuini:
If you can customize the voltage even better。

thank you。
[ONE Original Android Development] Tomoms:
Just a quick update: Sultan has released a new build of his LineageOS. In the next few hours I'll upload a new Neon kernel release with all the latest kernel patches he added to his LineageOS build. Sultan has also removed f2fs support from his build, however I'm not going to remove it from my kernel, because it might still be useful for users of other "sultanized" ROMs.
[ONE Original Android Development] Zieloo:
Nah, I'm fine. I think my charger and cable tops at 2.4A anyways, just asking out of curiosity ;P We all really appreciate your hard work and the line of communication that you keep with us.
[ONE Original Android Development] Inferillum:
Thanks for the quick update. Can we expect to have MultiROM support next build, or it'll get postponed to reflect the last Sultans changes?

Thanks!
[ONE Original Android Development] Tomoms:
My charger tops at 2,4 A too :)

Before reading your answer, I read a bit of documentation on our charging driver and took the decision of enabling support to charging at 2,5 A. This feature will be present in Neon v6 but will be disabled by default, because some users (including me) might not want to have it enabled out of the box (in fact I prefer charging at 1,4 or 1,5 A, especially in summer). So the default charging speed will be 2 A as usual.

The kexec-hardboot patch will be present (although not tested)!
[ONE Original Android Development] Inferillum:
YES! I will test it out and post results. Thanks!
[ONE Original Android Development] Tomoms:
Here's the new release!

https://www.androidfilehost.com/?fid=745425885120758340
[ONE Original Android Development] Inferillum:
Thanks for the update! Unfortunately, the indicator for kexec-hardboot patch via MultiROM app still shows that there's no kexec-hardboot patch present. I will try flashing a secondary ROM regardless to see maybe it's just the indicator.

Edit:

No, it does not work :(
[ONE Original Android Development] Tomoms:
Too bad! I don't have the faintest idea what to do to fix it, but I'll come up with something eventually.
[ONE Original Android Development] Inferillum:
Take a look at this source, it's a patch I applied to a normal LineageOS kernel (not CAF). which worked:

https://github.com/Inferillum/android_kernel_bacon_lineageos/commit/2c0e9edcf5a74c0e9fc0162757b6e53f24e74ff4

The problem is, that CAF kernels are way too different for this patch to apply. It's not about conflicts only, literally many files just aren't there. Too much implementation I think :(
[ONE Original Android Development] CooperBrick:
Request: would you consider to add a thermal throttle threshold that can be set in kernel adiutor? Sultan's one is very aggressive and phone gets very laggy sometimes. You can look to lightning kernel and private kernel source for that
[ONE Original Android Development] Bladehawkz:
In the ramdisk folder of the kernel zip, create a folder named "sbin", then create a file in that named "render-post_boot.sh"

Insert the following:

(sleep 5;
BB=/sbin/bb/busybox

# Thermal Settings
echo 1 > /sys/kernel/msm_thermal/enabled;
echo "2457600 48 47" > /sys/kernel/msm_thermal/zone0;
echo "2265600 50 49" > /sys/kernel/msm_thermal/zone1;
echo "1728000 52 51" > /sys/kernel/msm_thermal/zone2;
echo "1497600 55 54" > /sys/kernel/msm_thermal/zone3;
echo "1190400 58 57" > /sys/kernel/msm_thermal/zone5;
echo "652800 60 58" > /sys/kernel/msm_thermal/zone7;)&

You can change the frequency throttle steps if you want, it goes by <frequency> <turn on throttle at this temp> <turn off throttle at this temp>
[ONE Original Android Development] geokilla:
Bump
[ONE Original Android Development] Tomoms:
If you're using Magisk, you could try to use the Magisk module that should enable UKM support (I'm not sure that it will work). Otherwise you have to wait until I manually add support for that app!
[ONE Original Android Development] CooperBrick:
Thanks, will try
[ONE Original Android Development] bigtastie:
Anybody tried both this kernel and the Private kernel? I have really great battery life on Private kernel, but this kernel has both undervolt and fastcharging
[ONE Original Android Development] Zieloo:
Ye, I tried both and for me the battery life was about the same, but I've also tried various other roms and kernel combos and on each one I have huge battery drain(like 3% per hour) when my mobile data is turned on, and when its off the drain is like 10 times smaller ;/ Tried different firmware versions and the problem stays persistent..
[ONE Original Android Development] Stylez Ray.:
That's a common problem on all sultanized roms unfortunately...when this could get fixed we would have a solid rom base
[ONE Original Android Development] Tomoms:
As far as I can tell it's not a problem only on "sultanized" ROMs. I face it since months, if not years, on my older device (running official LineageOS), and on the OPO I've faced it on idprophecy's LineageOS too.
[ONE Original Android Development] geokilla:
Oh wow I just learned Sultan's ROMs completely blocks installation if using F2FS on /data and /cache. I thought he just removed support so it wouldn't boot. If that's the case, then there's no point in keeping F2FS support on Neon I think? Unless we can find a workaround on this.
[ONE Original Android Development] Tomoms:
No. I'm building my own version of Sultan's Lineage and I won't remove f2fs support from it. I'm already running the first build I made and I'll share the next one on XDA if I reckon I'll be able to give continuity to this project. For this reason, I'll never remove f2fs support from Neon kernel.
[ONE Original Android Development] geokilla:
I use Resurrection Remix so I'm hoping romilparh will consider doing the same, but it doesn't seem like it.
[ONE Original Android Development] Tomoms:
Theoretically f2fs support could be restored by adding a command in the AnyKernel installer that readds a couple of entries in the fstab file, but Sultan has also added a filesystem check in the installation scripts of the ROM so that the ROM won't install on f2fs filesystems, and this can't be removed or patched with an AnyKernel command, so the whole thing can't be accomplished anymore.
[ONE Original Android Development] Zieloo:
Yeah, as I mentioned I tried different builds, not only sultanized ones. For me it happened over night on some iteration of lollipop or mashmallow, and I went from 5-6h sot to 2-3h sot and charging twice a day. I know battery degrades over time etc., but back then before all the bugs appeared I have constantly had 5-6h sot w/o using any UV, different governors, or any battery saving apps. I'm wondering if clean flashing kit kat could just wipe all the battery draining services out of the phone and bring back at least some of those glorious days when you could get 8h sot easily on OPO :D
[ONE Original Android Development] #utkarsh:
I'm using dirty unicorns ROM on OPO. Will this help my device to improve it's battery life? Battery backup on this ROM is too bad
[ONE Original Android Development] Stylez Ray.:
This kernel doesn't work on the rom you're using because it's CAF based. Watch out for sultanized version of roms in this forum for roms you could couple this kernel with.
[ONE Original Android Development] Tomoms:
EDIT: not needed anymore.
[ONE Original Android Development] murti52:
Hi.. can you tell me if sdcardfs can be used on all roms or only on caf based roms?
[ONE Original Android Development] Tomoms:
sdcardfs can be used on all ROMs, but keep in mind that this kernel works only on "sultanized" ROMs.
[ONE Original Android Development] murti52:
Okay, thanks for clearing it. :)