yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] usmani:
How do you find performance on sultans cm compared to cm nightlies? I clean flash sultan's cm used for 3 4 days then went back to cos 13. The only upside I found on sultan's was the camera, Way better than cm. For me, Performance on cos 13 is a lot better than sultan, even more so than nightlies. What does your experience say? I guess I'm the only person having stuttery performance on his rom considering the number of users his rom has. (I tried with your kernel too)
[ONE Original Android Development] DerRomtester:
In terms of performance the cm nightlys feel snappier. This is related to the way sultan designed his kernel.

* underclocked by default

* a different cpu boost driver

* the interactive governor is tuned different

* thermal driver is a bit more aggressive

=>less performance => more battery life

Theoretically the battery life should be better at sultans rom but i get around the same or even better on the nightlys with my new custom kernel that i am currently testing. Yeah the camara is awesome. Also i like the stability of sultans rom. Currently running nightlys and did not notice something strange.
[ONE Original Android Development] usmani:
Yeah I'm having a similar experience. I actually get better standby time on cm.
[ONE Original Android Development] saiamrock:
I'm on latest brokenos rom but once i flash this kernel i get camera not working

Does anybody that use brokenos facing a same issue?
[ONE Original Android Development] parvesh:
IIRC with latest version Broken has mooved away from Sultan kernel and using new one so that might be reason for your issue as this kernel follow Sultan :)
[ONE Original Android Development] PivotMasterNM:
still not tempted? ;)

it's one hell of a phone :D
[ONE Original Android Development] PlusOne3k:
Just a feedback. Updated Kernel works like an charm. Compiled today with my own config and yes, it's quite stable - thanks again. I am interested in PMC, anyone got an version which is compileable. Damn, got an black screen picture with the camera, ehm I am Sultan Rom - can i ask for help :)

* Deleted App Settings, camera works.
[ONE Original Android Development] DerRomtester:
No sry. I got no money an if i had the money i would keep it. :) It looks decent but i think i wont buy oneplus again. Only if they cooperate with cyanogenmod again.

Yep stability and simplicity are my rules. :)
[ONE Original Android Development] PlusOne3k:
That's why we love you.
[ONE Original Android Development] PivotMasterNM:
by the way, the GPU govenor simple_ondemand used to be in sultans kernel like a long time ago, and he removed it for some reason (does anyone know why again?).

I kind of liked it because I felt that it gave the same performance as the msm-adreno-tz, while being a bit more battery friendly. Is this true and if yes, is it hard to implement? :)
[ONE Original Android Development] DerRomtester:
No its not hard to implement. He removed it because of instability problems.
[ONE Original Android Development] wszebor:
There's a new version of Sultans Rom ;)

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Original Android Development] Metacloud:
Can't wait new version of this great kernel! :)
[ONE Original Android Development] KaZo58:
r16 works fine on sultans latest :)
[ONE Original Android Development] DerRomtester:
It took a while cause i am busy these days.

Her it is (:

Yeah and if you dont need adaptive lmk you can stay on r16 or you give release 17 a try. :)
[ONE Original Android Development] SergioPC92:
Hi,

This kernel fix the LG screen problem?

Thanks for your work mate
[ONE Original Android Development] DerRomtester:
What problem?
[ONE Original Android Development] molonad:
Hello why can not be this kernel installed on secondary rom and all other caf kernel does not have this problem? Thank you for your answer.
[ONE Original Android Development] DerRomtester:
I dont support multirom because it breaks encryption.

What other kernels have this feature + encryption working ?
[ONE Original Android Development] venky716:
Multirom does not require kexec boot patch any more.

But private kernel fails to flash on a secondary rom, I think it has to do with the installation script. Rest i don't think you've to do anything different to make it MultiROM compatible.
[ONE Original Android Development] DerRomtester:
If it is the primary kernel than kexec is required of course. If it is the secondary than not. I am using the latest version of anykernel ramdisk and there is no updater script anymore just an updater-binary. Multirom searches for the updater script and than it fails because it cant find it. I won't go back to an older anykernel ramdisk version just to support multirom. I am sure it can be fixed on multirom side.
[ONE Original Android Development] venky716:
Ah ok.

Your kernel can still be used for the primary rom, since multirom uses non kexec patch method now for kernels without kexec.
[ONE Original Android Development] itsdacj:
Does anyone think this would work on AOSPA? Since that's CAF?
[ONE Original Android Development] LPW00:
Cam does not work because pa uses blobs which aren't supported by any custom kernels. But they may change it soon.

Is it normal that all options reset to default after reboot?
[ONE Original Android Development] itsdacj:
Do you use Kernel Adiutor?
[ONE Original Android Development] LPW00:
I use kernel adiutor mod (v14 I think).
[ONE Original Android Development] itsdacj:
Did you tap the switch at the top that says apply at boot?
[ONE Original Android Development] LPW00:
Yes, I'm not that retarded
[ONE Original Android Development] itsdacj:
No need to be so rude
[ONE Original Android Development] CooperBrick:
Getting this on darkobas, what to do? Snapdragon Camera
[ONE Original Android Development] DerRomtester:
Maybe dont use darkobas. That fixes your problem. No just a joke. Darkobas is not supported because he is using different camera drivers blobs and a kernel that does not match sultans kernel anymore. So i cant give any support for darkobas.
[ONE Original Android Development] CooperBrick:
Will this work with coloros camera?
[ONE Original Android Development] DerRomtester:
It is not a camera thing. So no.
[ONE Original Android Development] LPW00:
Sry I don't meant to be...
[ONE Original Android Development] iTalisman:
Using v17 on RR CAF. Solid kernel with a solid battery life. Thanks a bunch :)
[ONE Original Android Development] sohansonu:
Can I use this kernel with Dirty Unicorns?
[ONE Original Android Development] JJohnson1988:
No. Meant only for ROMs based off SultanXDA's work.
[ONE Original Android Development] bertozzi243:
nope

from first post

"Only for roms with sultans CAF kernel!"
[ONE Original Android Development] CooperBrick:
How to remove this kernel? I already flashed again sultan latest build
[ONE Original Android Development] JJohnson1988:
Sultan's kernel is being used again if you re-flashed his ROM.

Therefore, you shouldn't have to do anything more.
[ONE Original Android Development] marco2012:
Awesome Kernel!

Does kernel r17 work on older sultan rom?

I'm on sultan 03 Jun. Can I use the latest version of Private Kernel (r17) or should I use an older version, like r15?

Thanks!
[ONE Original Android Development] Bladehawkz:
Difficult to search for information on this; what's the main difference between mpdecision and cpuquiet?

Other than being imported from tegra chipsets, how do the hotplugs operate, and under what conditions are the other CPU cores turned on?

(also might wanna change the first post, still says autosmp hotplug)

Edit: Another question: Does underclocking actually help battery life (not talking about heat produced) given the aggressive nature of smartmax in throttling the clock rate? Giving the theory that under higher clock rates, while the CPU needs extra voltage the decrease in task time balances it out?
[ONE Original Android Development] JJohnson1988:
These are all good questions. This was the most useful information I could find on CPUQuiet:

https://www.linuxplumbersconf.org/2012/wp-content/uploads/2012/08/cpuquiet.pdf
[ONE Original Android Development] MrVoshel:
New sultan build is up :D
[ONE Original Android Development] DerRomtester:
Lets vote for a seconds place ( i am note sure if i add any of these)

http://strawpoll.me/6661302
[ONE Original Android Development] wingedpanther:
Again :rolleyes::eek:
[ONE Original Android Development] DerRomtester:
r2 Changelog:

* added voltage Control

* added Smartmax governor

* cleaned up smartmax governor

* removed boosting function from smartmax governor because we are using cpu_input_boost for that

* removed the redundant iowait check adapted for smartmax

"Iowait_time check is redundant and it would lead to heavy load
due to miscaluculation of idle time. Hence remove this check
as iowait will considered based on io_busy flag."

Maybe i need to tune it further. Lemme know how smartmax works.
[ONE Original Android Development] D_black84:
4 cores online

just flashed this kernel I have all 4 cores online, I thought it was supposed to be 2 cores right? please see the screenshot below . by the way, this kernel is smooth
[ONE Original Android Development] DerRomtester:
Your CPU load seems to be quite high so the hotplug kicked in all cores.
[ONE Original Android Development] madsponge26:
Looks promising.. Downloading!
[ONE Original Android Development] slamdunksaliby:
Hi, thanks for making this kernel! Just have two questions:

1. Does the kernel work on Sultan's stable 5.1.1 ROM?

2. Are you able to downclock using an app such as kernel adiutor?

Thanks!
[ONE Original Android Development] DerRomtester:
1. I dont know. But it should work

2. Yes, that is possible of course like on every kernel.
[ONE Original Android Development] slamdunksaliby:
Awesome thanks so much I can confirm it works! I love this kernel because its super smooth like stock and the underclock settings stick to save battery and of course smartmax :)
[ONE Original Android Development] Zeus20:
Have you thought of adding this to a second post and create a changelog second post.
[ONE Original Android Development] DerRomtester:
Nice idea but i was lazy this time :)

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] wingedpanther:
Flashed it ... so far everything seems good especially idle drain reduced (only 1% dropped during 8 hrs sleep. )

CPU Gov.: Smartmax

UV: -45
[ONE Original Android Development] DerRomtester:
Sleeps like a baby :)

Also the problem could be related because of the incompatibility to this rom. I know that sultan was using a different kernel tree for omni rom and maybe the darkobas developer is using this kernel tree for his rom (i am using the tree sultan designed for cm) and this could lead to your problem. Also the problem could be rom related. That means my kernel isnt compatible with that special rom and you get that problem. Also the problem could be related to my kernel (i dont get any wakelocks and also the user above i have quoted). Also i did not make any changes at all that affect wifi. Wifi drivers are excatly the same like on sultans rom.

But i found something interesting that may solve that problem but i cant guarantee that. The problem with that fix is that notifications may be recieved delayed and i dont like that. But i can give it a try but i cant promise anyhting.

Edit:

I just checked his source code and it is quite different from sultans kernel source code, so there could be compatibility problems. I dont suggest to use my kernel on darkobas.

* he i using an different prima driver, maybe he also changed some config files on rom side that cause problems with my kernel

* he isnt inline with sultans kernel so i dont give support for that specific rom,

so he isnt using latest stock kernel provided by sultan!
[ONE Original Android Development] Pradhan_89:
[MENTION=4804871]DerRomtester[/MENTION]: No CM version coming? Love your work. :)
[ONE Original Android Development] skyrmion:
V1 works great on tipsy rom last few days. Trying v2 now
[ONE Original Android Development] molonad:
Hello does your kernel have some other optimization like o3? Thank you

Also does your kernel have already zzmove governor with zzmove native which ended good in your vote challenge?

And does your kernel have added some frequencies or stock? (i think too many frequencies can lead to worse performance) thank you.

Odesláno z mého A0001 pomocí Tapatalk
[ONE Original Android Development] usmani:
+1
[ONE Original Android Development] DerRomtester:
Hmm i dont know yet. I dont want to make a kernel for something that i dont use anymore.

What optimizations are you looking for ? Can you proof that these optimizations do improve performance on android ? Aren't they just placebo ?

I said that i am not sure that i am gonna add them. And i dont add them. Why ? All respect to zanezams work but zzmoove and elemental x are just too experimental in my opinion.

You need frequnecies for what ? I use the suggest cpu frequency table suggested by Qualcom.
[ONE Original Android Development] DerRomtester:
Pushed r18

* totally untested

* synced with sultanxda
[ONE Original Android Development] JJohnson1988:
I shall test it for you, then. ;)

And so far, so good.
[ONE Original Android Development] mysteres:
I'm using latest without problem
[ONE Original Android Development] luytent:
Also using it. No problems so far :good:
[ONE Original Android Development] nfin1te:
R18 works like a charm with latest sultan. :)
[ONE Original Android Development] svil3:
Using R18 since yesterday and everything's fine so far, thanks a lot [MENTION=4804871]DerRomtester[/MENTION]
[ONE Original Android Development] PlusOne3k:
Same here, running without problems.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] hb17:
No problems running on Tesla!
[ONE Original Android Development] Bladehawkz:
Reading some other threads; rather interested in why in some kernels (not this one though) we are able to go down to a minimum CPU frequency 268mhz (though I understand why we don't have the option of overclocking).
[ONE Original Android Development] DerRomtester:
Our CPU supports that step but it isnt enabled by default like many other cpu frequencies. There must be a good reason why cm or google deciced to take some frequencies and some not. We are using the suggested cpu frequency table by qualcom without the 268mhz step. I dont see any difference in my observations so we use the 300mhz step like google or cm or oneplus and other companies.
[ONE Original Android Development] luytent:
I have noticed some difficulties connecting to the internet.

It happens using Wifi and mobile data connection.

Don't know if it's the kernel or the rom.
[ONE Original Android Development] Bladehawkz:
RQ affinity.

Multicore Power Saving

Both disabled in Kernel Adiutor MOD on default, are there any benefits in using them (and related sacrifices ofc)? Once again, difficult to find information on these.

Edit: RQ affinity is default set to 1 actually, not disabled (0). My mistake.

As far as I've searched, Multicore Power saving does what the description says, but on some devices, it leads to performance issues and stability issues.

RQ affinity makes it so i/o tasks are finished on the same core/core cluster that they started, and since they don't pass through different areas, less CPU cycles are required to finish the task. Same issues as above, but can also increase performance in some cases.

Can anyone correct me if these are wrong? Also, are these recommended for usage on the OPO? (smartmax, fiops)
[ONE Original Android Development] DerRomtester:
Yep this is absolutely correct. I suggest using bfq because it performs incredibly well even on flash devices (a developer on youtube found that out and made some benchmarks also cm made it to default) . Smartmax and Interactive are my favorites.
[ONE Original Android Development] Bladehawkz:
Thanks for the input! Do you have any suggestions for whether I should change the values of RQ Affinity/Multicore Power Saving or should i just leave them on 1 and 0 respectively?

Also, I'm not so sure about BFQ. While it does perform pretty decently in benchmarks, its fundamental strength is in multitasking and proper balancing of i/o tasks, especially in continuing to run apps in the background. However, wouldn't schedulers like ROW be better for some users (those who don't use a lot of apps), since prioritizing read at the cost of write to increase UI fluidity and app launch speed could be an acceptable (even favorable) tradeoff for worse multitask and write performance?

BFQ looks more like a great all-rounder, which is awesome for widely used settings (like in default CM), but I think that /just maybe/ (speculation), some other schedulers are better since a slight increase in one area may be worth a massive sacrifice in other areas.
[ONE Original Android Development] DerRomtester:
I have to admint that i dont know which values you should set for rq affinity or multicore powersaving. If i dont know what a values does i google it or leave it by default to avoid any problems or missbehavior. Or sometimes i test with trial and error. I actually dont have much information about that.

I still prefer bfq.

I am sure it will soon replace the cfq scheduler in the linux mainline kernel. And i am great fan of bfq because it gets updates also on our old 3.4 kernel. The last update of row or fiops was a long time ago and many things have changed since that time.
[ONE Original Android Development] LPW00:
Noop seems to be good, I use it..
[ONE Original Android Development] Bladehawkz:
OK, so I've compiled more information about some things.

Multicore Power Saving is actually a pretty useless option. The reason for this is that fundamentally, this is the job of hotplugging, and having this enabled basically enables another form of hotplugging. Unless you're not using cpuquiet/mpdecision, I would definitely recommend just keeping it at disabled. (information sourced from boeffla kernel's FAQ : http://www.boeffla.de/non-joomla/en/bc-settings.html, and from logical deduction of what hotplugging does and what the multicore power saving option aims to do).

Read-ahead Buffer: I see many, many sources of increasing read-ahead buffer to increase performance. Unfortunately, these increases are often done through COMPUTER benchmarks, where the downsides are extremely difficult to see. First of all, an overall global performance decrease. This can be seen more in multitasking, where LOCAL tasks (current UI you're interfacing on) most likely feels better, but the increased i/o tasks required to fill the read-ahead buffer cache decreases the performance of background tasks. This is probably what the "global performance regression" in "When your device is under high memory pression high read ahead values cause a global performance regression according to this commit https://github.com/MotorolaMobilityL...commit/aa87390. " (Quoted from DerRomtester) refers to.

Along with this, you're battery life is also slightly worse (extremely difficult to perceive though). This is because for each file read operation, you are reading an EXTRA <insert cache size> kb of data, of which is not always used. While the battery loss is quite low, so is the performance increase.

TL;DR

Don't use Multicore Power Saving if you're using a hotplug

The tradeoff of higher Read-Ahead Buffer Cache values is slightly better foreground performance, at the slightly cost of worse background performance and a loss of a bit of battery life.
[ONE Original Android Development] gamal001:
[MENTION=4804871]DerRomtester[/MENTION] , can you issue same kernel for working with CM.
[ONE Original Android Development] DerRomtester:
Not excatly the same but i am working on something.
[ONE Original Android Development] gamal001:
I'm used your kernel with candysix and like it too much. but when I try use kernel on du rom it's working okay but the camera broken. if we get same kernel without effective on camera it will be wonderful.

but I'll wait your magic. [emoji106] [emoji106] [emoji106]
[ONE Original Android Development] DerRomtester:
DU and its kernel are cm based right ?
[ONE Original Android Development] gamal001:
yes i know, but your kernel work with all rom caf, cm, aosp .

but camera working only with sultanxda rom and candysix
[ONE Original Android Development] DerRomtester:
Maybe it works but i dont suggest using it because of compatibility problems. Its not only the camera.
[ONE Original Android Development] Bladehawkz:
Hmm, mind if you upload a zip to unlock the other frequencies? While the 268mhz frequency may be quite useless (i suspect it's due to the equal 775mV as the other frequencies), and the other frequencies potentially unstable, I feel like tinkering with them might be fun.

At my own risk of course.

And yes, I have an over obsession with tinkering with my device ever since I got it. Sorry :(

Edit: Wow looking at other CAF kernel's arch/arm/boot/dts/msm8974.dtsi, there are a LOT more frequencies, many in-between the ones we have currently. Interesting. Unfortunately I'm not good enough at C and/or any form of linux usage to compile my own kernel.
[ONE Original Android Development] joefso:
[MENTION=4804871]DerRomtester[/MENTION]

can you add ondemand again? It seems to be stable - default on omni
[ONE Original Android Development] nfin1te:
Sultan released an update (Aug 6) - eagerly waiting for yours :)

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] JJohnson1988:
Looks like Sultan may release another update with fixes, so there's no rush for a new kernel. :)
[ONE Original Android Development] gamal001:
[MENTION=4804871]DerRomtester[/MENTION] in v.20 did you change anything about input frequency, because before was in 1190 and now if change max frequency to any value it will change also input frequency automatically with same frequency but not more 1479. I used smart max with cpuquiet.
[ONE Original Android Development] LPW00:
v.20? What about v.19? Did I miss something?
[ONE Original Android Development] gamal001:
see download section and first page. 19 passed with the changes 06/08
[ONE Original Android Development] LPW00:
Nothing to see in download section. But I don't need r19 anyways, I just thought it's called r20 by mistake...
[ONE Original Android Development] DerRomtester:
I just changed the cpu boost driver to boost to 1497600mhz for a more fluid experience nothing more.

I removed v19 because sultan said that there were random reboots.

I was to fast an removed v19 :)

No it was no mistake i removed it because of instability problems.
[ONE Original Android Development] Bladehawkz:
Hey, what's the relevant commit to achieve this?

Trying to compile my own kernel starting from your branch of sultan's kernel, but unable to see where the assignment of the input_boost_freq value is.

Thanks for the awesome kernel work though :).
[ONE Original Android Development] Bladehawkz:
Woops double post, was meant to be an edit.

Turns out you can edit the input boost value on the device itself, under sys\kernel\cpu_input_boost\ib_freqs

Edit again: Turns out this doesn't stick after a reboot. :(

Edit again 2 (lmao): If you want it to stick, reflash the zip except change the relevant values in the file inside \ramdisk\ within the kernel zip.
[ONE Original Android Development] JJohnson1988:
You can also put a shell script inside the init.d directory. Probably easier and safer than modifying the kernel itself on every new version.
[ONE Original Android Development] DerRomtester:
This value is inside my anykernel ramdisk. The file is called render_post_Boot.sh. There you can change the values. Just extract it from my kernel. My anykernel repo isnt up to date.

Than reflash the kernel with the new anykernel ramdisk.