yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Some useful Magisk modules

Sharing some of my favorite Magisk modes (all self made).

Samsung Health Service

Enables Heart rate and stress measurements in SHealth (should be installed from play-store)

Download

Should work ion Lineage-OS-14.1 and its derivatives (will not work in Lineage-15.1, not sure about cm-13)

OnePlus Camera

Download

Install Oneplus Camera as a system app. Should work on Lineage-OS-14.1/15.1

Navigation soft key enabler

Download

Enables navigation soft keys in Lineage-OS (13/14.1/15.1). Not sure about Samsung ROMs.
[Samsung Galaxy S 5 Unified Development] Jiimmy97:
I have problem with r/w system partition when try to make it from r/o to r/w it return back and can't make change sytsem apps how to make r/w permeant ??

Edit: oneplus camera front camera can't capture?? It's already system app and there is new update i have zip file of 2.5.7 version ??

Regards
[Samsung Galaxy S 5 Unified Development] Muhammad Tajy:
The one plus camera is better than stock but can't use flash
[Samsung Galaxy S 5 Unified Development] kenedielh:
Cannot use flash oneplus camera
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Sorry guys: haven't noticed that yet as I'm simply switched to HDR mode in the first use of the app.
[Samsung Galaxy S 5 Unified Development] Jiimmy97:
iam on los 14.1 and front doesn't open yet and the new app version doesn't install as update

Regards
[Samsung Galaxy S 5 Unified Development] Muhammad Tajy:
The front camera works fine for me on RR and the module is the latest version according to apkmirror
[Samsung Galaxy S 5 Unified Development] Jiimmy97:
Thanks for feedback . Did you do anything atfer flash this zip ??
[Samsung Galaxy S 5 Unified Development] Muhammad Tajy:
No
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
New (Oreo-beta-v1.1) builds...

Guys,

Here I'm adding a new version (Oreo-beta-v1.1) of my Oreo kernel for those who are already moved to LOS-15.1 (and to motivate others to move soon;)). These kernels should be compatible with the latest LOS builds released just today.

Changes: KSM (not uksm) is enabled and should be reflected in the memory management.

Crashing of simple_ondemand gpu governer will be fixed now (thanks to [MENTION=5811506]Saber[/MENTION] & [MENTION=5414005]GeTex[/MENTION] for the commits).

For detailed change-logs, plz visit here.

Before flashing...

Please remember that it is just a beta release. So, expect some issues in the worst case. Further, I really want to request a few things to all of you...

1.	Please do not report bugs/post logs in the main LOS thread while using this Kernel (they do not care about your logs if you installed a custom Kernel)

2.	Please do not pollute main LOS thread by making discussions about this kernel. You guys can use this thread instead.​

Download links can be found at the below link... enjoy...

Oreo test-builds

PS: I haven't added these kernels to the auto-updater app yet as I'm now trying to do the same thing using my modified kernel manager app instead.
[Samsung Galaxy S 5 Unified Development] Blackburn119:
Will this fixed coming to 7.1.2 kernel?
[Samsung Galaxy S 5 Unified Development] taylorhmatos:
Excellent launch for our beloved and warrior S5. To since since turned the year using android oreo on my cell phone and with your kernel will get even better. No problem, I warn you. Congratulations on the release.

ease.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Yes...

Thank you for the nice words friend... have a nice day...
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
SmartPack-Kernel Manager v2.2

A minor update to SmartPack-Kernel Manager (v2.2) is now available.

In this update, OTA (I mean real OTA) support to both Oreo and Nougat Kernels are re-implemented. As always, the new app can be found on the GitHub release page. To know more about accessing the updates, please see the attached screenshots. Enjoy...

Please note: Download links in the OTA page will usually expire in 2-3 days (not my issue, but AFH). However, you can always access to the download folder at anytime from the "About" menu of your Kernel page.

Screenshots

Edit: Please comment your thoughts about the better app for auto-update. This app or Auto Kernel updater?
[Samsung Galaxy S 5 Unified Development] Davidgostbo:
The latest kernel breaks android auto, my car can't recognize the device anymore. But when i go back to stock it can recognize it again?

im on nougat crdroid
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Hi friend,

The latest crDroid (crDroidAndroid-7.1.2-20171214-klte-v3.8.4) is more than one month old. My latest kernel includes a lot of new commit (more than 20) from the mainstream LOS kernel, that might break some stuff in your *old* ROM. So, please do not blame me (and my Kernel) after using the same on an *old* ROM.

Sidenote: I do not own a car and therefore no Idea about android auto. Therefore, I have no way to reproduce your issue. Now you tell me what can I do if you simply say "The latest kernel breaks android auto, my car can't recognize the device anymore"? ;)
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Testing a new governor (blu_active)... so far good... next build (tomorrow) will hopefully bring something useful... ;)
[Samsung Galaxy S 5 Unified Development] flyingsaucer75:
Maybe something bluetooth related... Anyway he needs to explain...
[Samsung Galaxy S 5 Unified Development] Keller0088:
Wow great! That's on Nougat, isn't it?
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Yes, and eventually added to OreO as well (since it working great)...
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Major update to (stable-v12)/Nougat

Hi guys,

New kernel version (Stable release: v12) for Nougat ROMs are now available to download.

This gonna be a big update as well as bit long write-up...

Changes:

1. Fixed simple_ondemand crashing.

2. Added blu_active cpufreq gov (credits: [MENTION=3873953]eng.stk[/MENTION]).

Please note: blu_active governer has a lot of patches from the mainstream Linux and will be a good deal for our device.

3. Properly enabled cpu_input_boost while booting. Please make sure to disable lazyplug touch boost to avoid any possible conflicts. If you want to disable cpu_input_boost, plz do it manually by using this custom control json file.

Big thanks to [MENTION=5811506]Saber[/MENTION] for bringing this topic (see posts 1 & 2).

4. Introduced *SmartPack* boot script into ramdisk, which will be used for the various purpose (for properly activating cpu_input_boost at this moment).

5. Some fine tunings to Nightmare cpufreq gov.

6. Increased default read ahead size & tcp output window.

7. Merged recent changes from osmosis anykernel repo.

8. Up-to-date with Linage-OS source code.

See this page or my GitHub commits for detailed change-logs.

Download links can be found in the below links. The links will hopefully appear on SmartPack-Kernel Manager (inside Tools ---> Update) as well.

Since it is a major update, expect improvements in both performance and battery and some issues in the worst case. I'm seriously looking for your comments.

Enjoy....

/* Downloads */

kltekor

klte

klteduos

kltespr

[B][COLOR="Red"]Please make sure to download the latest build dated 2018011[/COLOR][/B]

Further, the test build for kltekdi is here.
[Samsung Galaxy S 5 Unified Development] Blackburn119:
I don't think Blu_active is a battery friendly governor, it's based on interactive but boosting to performance and gamings.
[Samsung Galaxy S 5 Unified Development] wlgur313:
Really thank you for make korean version.

Thank you.
[Samsung Galaxy S 5 Unified Development] Henrea4:
Sounds good to me! lol
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Thank you ;)

Because I'm also using Korean S5... :good:
[Samsung Galaxy S 5 Unified Development] Keller0088:
Kernel works flawlessly :D well done Sunil! I m using Smartmax governor :D
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
New (Oreo-beta-v1.2) builds...

Guys,

A new version (Oreo-beta-v1.2) of Oreo kernels are now available.

For detailed change-logs, plz visit here.

Further, please note that while installing this kernel, the following features were activated by default, irrespective of your device is rooted/not-rooted, using official KA/my modified app etc.

---> It will enable cpu_input_boost by default. So, please make sure that touch_boost (CPU hotplug section) is turned off. Else, turn off cpu_input_boost (to avoid conflicts) in SmartPack-Kernel Manager after importing this json file (Custom Control section). For official KA (free version) users, you need to manually add a new controller for cpu_input_boost (since custom control import is not free) which is a bit complicated process (Plz read next post). As a quick workaround, you can put "echo 0 > /sys/kernel/cpu_input_boost/enabled" in the root terminal.

---> It will enable "adreno_idler" by default

---> It will disable thermal "core_control" and "vdd_restriction" and enable "inteli_thermal" by default.

---> It will enable "fast_charge" by default.

Please make sure that you are not making any conflicting actions in your favorite kernel manager.

again, before flashing...

Please remember that it is just a beta release. So, expect some issues in the worst case. Further, I really want to request a few things to all of you...

1.	Please do not report bugs/post logs in the main LOS thread while using this Kernel (they do not care about your logs if you installed a custom Kernel)

2.	Please do not pollute main LOS thread by making discussions about this kernel. You guys can use this thread instead.​

Download links can be found at the below link (and will be added to SmartPack-kernel manager soon)... enjoy...

Oreo test-builds

Please make sure to download the latest version (name should contain [B][COLOR="Red"]Oreo-beta-v1.2-20180119[/COLOR][/B])
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
CPU Input boost

How-to-create custom control for cpu input boost in KA

Go to KA ---> Custom Control --> Click the Plus sign ---> select Switch and fill various feilds with the following parameters

Title: CPU Input Boost

Description: Enable CPU Input Boost by Sultanxda

Enabled:

#!/system/bin/sh

if [ "$(cat /sys/kernel/cpu_input_boost/enabled)" -eq "1" ]; then

echo 1 #(Enabled);

else

echo 0 #(Disabled);

fi;

Applying:

#!/system/bin/sh

status=$1

#$status is either 1 or 0

echo $status > /sys/kernel/cpu_input_boost/enabled

echo "1190400 1497600" > /sys/kernel/cpu_input_boost/ib_freqs

echo "1400" > /sys/kernel/cpu_input_boost/ib_duration_ms
[Samsung Galaxy S 5 Unified Development] saif hussain:
What's happened with nethunter kernel
[Samsung Galaxy S 5 Unified Development] thaidroid:
Maybe I did not explain properly, First I'm on TWRP 3.1.0.

I never wipe anything before taking backup.

For trouble shooting I did complete wipe before restore but those failed with boot loop when rebooting system

So like this

Running Cosmos,

Wipe complete

Restore Lineage

Wipe Cache / Dalvik

Reboot

BootLoop

Same the other way around. Lineage -Cosmic.

Both cases

Restore backup-dirty install ROM and Smartpack-Wipe Dalvik / Cache - Reboot success
[Samsung Galaxy S 5 Unified Development] KazuDante:
so you did not wipe /data from what you wrote , that alone would cause problems since its coming from a whole different rom. now correct me if im wrong if when you wrote "Wipe Cache/Dalvik " you literally meant just cache /dalvik ( factory reset) i dont know if it does wipe /data or not , but having data from one rom and then having the device boot on a different rom with data that did not belong to that other system(rom) im pretty sure that you would face problems. idk maybe im not understanding it correctly, was trying to shed some light/help if i can. from what i already see devs say and from what i do i wipe dalvik-cache,cache,data,system,internal-storage before flashing new rom or restoring a backup just to avoid any king of issues.
[Samsung Galaxy S 5 Unified Development] thaidroid:
Not sure what you mean....Doing a TWRP Restore, Restores system and data. So after restor of couurse the only thing you wipe is cache and dalvik otherwise there is nothing of value to boot:D
[Samsung Galaxy S 5 Unified Development] KazuDante:
i mean if you are backing up , of course youl back up the boot,system,data,cache,efs partitions then back out to main menu then wipe-advance wipe dalvik,system,data,cache then flash rom ect.... leaving any leftovers from a different rom for the newly flashed rom to pick up will cause problems especially if its not the exact same one you flashed before. CosmicOS it not the same as lineage even tho its based of LineageOS. What im trying to say is that to avoid bootloops wipe it all before flashing new rom , all devs tend to always say that as well because leaving anything behind after a older rom and then flashing a new one and reporting to those devs that theres a bootloop or a bug just for the dev to find out it dint come from that rom that it was a mismatch from a bad wipe.

after restoring a backup you don't wipe anything not even dalvik-cache or cache. those 2 partitions were in use when you made the backup , so wiping it would cause issues.

So in general what i was trying to say is wipe it all when switching rom either from flashing or restoring ( except internal storage and Micro SDCard ,USB Storage...those 3 dont have to be wiped ) to avoid bug-bootloops. I flash and restore roms at least twice a day I even test 5.1.1 roms and yes i was using CosmicOS rom as well thats why Im trying to explain the wipe properly because that will cause bootloop if not properly wiped.

We are getting of topic since this is a Smartpack kernel thread and the kernel is definitely not the issue.
[Samsung Galaxy S 5 Unified Development] thaidroid:
Got you actually just tested again before I read this post. Tried restore Cosmic no Luck, Tride Resore Lineage no Luck

Wipe Factory Reset Advanced wipe Dalvic, System, Data, Cache. Restore Lineage

No Wipes of any kind after Restore just Re-Boot Lineage up and Running Very quickly.

Cosmic same procedure as above no Luck, Bootloop

I'm not backing up cache in TWRP will check to see if that makes a difference with Cosmic

---------- Post added at 03:05 PM ---------- Previous post was at 02:09 PM ----------

I fixed the Cosmic restore issue by also backing up cache, I think thats what did it.....not sure

Anyway

Factory Reset

Advanced Wipe, Dalvik, System, Data, Cache

Restore System Data Cache.

Wipe nothing Just reboot system and it's all good.
[Samsung Galaxy S 5 Unified Development] thaidroid:
There is something funny going on...

It does not matter how you wipe before you do a restore.

You can restore to the same ROM without problem but if you restore to another ROM then you get boot loop. To avoid Boot Loop Restore the other ROM (don't wipe or do anything else)and Dirtyflash Rom and Smartpack on top- Hit Reboot and it will work. Really not a big deal as long as you know that you have to do it.

Dont know if its twrp or kernel or what
[Samsung Galaxy S 5 Unified Development] thaidroid:
OK so I tried using TWRP -3.0.2-1-klteskt, No Difference backed up and restored both ROM's in 3.0.2, same result as 3.1.0

Restore to the same ROM no Problem Restore to different ROM Boot loop unless you do the procedure above.

So Ive never seen this before it must be something that is not getting wiped properly. Cosmic has the Modified Kernel Auditor maybe that has something to do with things?????

Anyhow I know the work around so I will leave it at that. Back on 3.1.0 TWRP;);)
[Samsung Galaxy S 5 Unified Development] thaidroid:
TWRP restore bootloop problem identified.

It has to do with Cosmic ROM(I dont know what or why maybe its their modified kernel auditor that leaves something on the phone that Lineage does not like and vice versa)

I just installed crDroid and Did a full TWRP backup on that and then immediately restored Lineage including Cache (no wipes nothing), hit Reboot and it was up like a Rocket.

The reason I went back to Lineage was that Skype app refused to open on crDroid, has anyone tried that? everything else seemed OK.

Actually Skype does not open on any Rom at the moment
[Samsung Galaxy S 5 Unified Development] :
Trying out Smartpack kernel and I got to say my S5 is running at much cooler temperatures. Performance and battery life have increased. Anyway, anyone have a kcal setup that makes blacks blacker, whites whiter and colors more vivid? :)
[Samsung Galaxy S 5 Unified Development] KazuDante:
red 230

green 232

blue 255

saturation 274

hue 0

display value 247

contrast 268
[Samsung Galaxy S 5 Unified Development] fbs:
installing this made my phone notably slower, I think touchboost isn't working at all. I even raised the input boost frequency and interval, but no luck

enabling mako hotplug makes it dual-core only

"adaptive" governor made it crash
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
which is your device model? I never noticed most of those issues on my device (mine is Korean variant). Are you sure that mako hotplug restrict ur device to dual core... In my case, it is true with some cpu freq govs like nightmare (and may be more)... but all the 4 cores are active when I switch my profile to performance and some others... Btw, ur correct... touchboost isn't working... since it is not implemented in to my kernel :laugh:
[Samsung Galaxy S 5 Unified Development] Mrcactuseater:
Love this kernel, running great on my klte! Just a wondering if you thought about using a different toolchain?
[Samsung Galaxy S 5 Unified Development] fbs:
klte, g900m

touchboost options are enabled on kernel adiutor (as Input Boost Frequency), and they work with the vanilla los/aosp kernel

It seems changing the governor will screw up the hotpluger. I just changed from Interactive to Yankactive and all cores are on, even though they're at 300mhz (almost no load..). I'm staring at them for some minutes and no one is being unplugged, they're steadly ON..

Even changing back to Interactive again won't fix this.. I have to reboot if I want hotplugging to be enabled again..

I don't know but adiutor itself may be causing this.. it seems it always enabled every core when you change the governor, then they won't be disabled again by mpdecision until you reboot

and I'm not using any other kernel tweaker/scripts/mods or anything..
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
I recently switched to Linaro toolchain. Any other options?

Thanks for the details.
[Samsung Galaxy S 5 Unified Development] :
There’s also UberTC and CAF.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
New builds are up...

[B]March 30, 2017[/B]
Stable release: v2
Nothing other than the latest LOS commits.

Recommended to use with the latest LOS builds since the official kernel source is largely modified (and consequently mine). Download links are here...

/* [COLOR="blue"][B]Downloads[/B][/COLOR] */
[INDENT][URL="https://xdaforums.com/devdb/project/dl/?id=23970"]kltekor[/URL]
[URL="https://xdaforums.com/devdb/project/dl/?id=23971"]klte[/URL]
[URL="https://xdaforums.com/devdb/project/dl/?id=23972"]kltevzw[/URL]
[URL="https://xdaforums.com/devdb/project/dl/?id=23969"]klteduos[/URL][/INDENT]
[Samsung Galaxy S 5 Unified Development] Blackburn119:
Your kernel is largely modified from stock it keeps killing my apps in background whenever​ I multitasking.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Ofcourse it is largely modified on the top of stock LOS kernel. However, I'm pretty sure that it will not kill apps in the background (at-least for me). Check this screenshot to see many recent apps in my case. In the Developer options, there are some options that allows force closing of recent apps immediately after leaving the screen. Make sure that those are not activated in your case. Also check with the stock LOS kernel... Anyway, thanks for testing my kernel...
[Samsung Galaxy S 5 Unified Development] Blackburn119:
Last time I checked those options was not activated and I tried​ to disable greenify but the problem still remains.

Edit: never mind now I just found out that Lineage's devs have been messing the virtual memory setting like zram and swap memory too much, I just changed it back to default ASOP setting.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Hi all,

Any suggestion about adding Boeffla charge_level to this Kernel?

Benefits: Which gives more flexibility in controlling AC, USB, and wireless charge.

Issues: KA, (consequently my modified app), is currently unable to control Boeffla charge_level natively.

Workaround:

1. Pre-define custom values while booting (easy way)

2. Make custom controller for charge level (see screenshot, partially success, work-in-progress)

Please let me know your suggestions...

Regards

Screenshot
[Samsung Galaxy S 5 Unified Development] vd69:
That would be great. Just please make them controllable with values until 2000 1600 1600 max like boefla.Thank you.That was only reason I wasnt using your kernel.
[Samsung Galaxy S 5 Unified Development] GeTex:
Wish you could include a kernel custom file in the ramdisk or place it in system and KA could poll it for adding lines without requiring end user intervention.

Talk to the KA Dev?
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Hi, thanks for the suggestion. But is it really safe to use the extreme high end values? I initially thought to predefine bit lower values like 1800, 1000, 1000 ....

Hi, I can't really understand what you mean. I recently added some scripts in the ramdisk to predefine some parameters while booting. But it doesn't add anything new that are not natively supported by KA. Plz share some more idea, if you have.

Thanks
[Samsung Galaxy S 5 Unified Development] GeTex:
Custom values like the charging circuit that aren't predfined should have a way to be define by the kernel via flashing or such.

The extreme values aren't very extreme, by default AC is chraging at 1800-1900, usb is 500 though and wireless is 1000 afaik
[Samsung Galaxy S 5 Unified Development] asdfghjkl200606:
Please update for kltechn.Thank you!;)

From China
[Samsung Galaxy S 5 Unified Development] Saber:
I'd say do both. Write to init the custom pre-defined values, then allow KA to override the values after finishing boot process.
[Samsung Galaxy S 5 Unified Development] vd69:
I am using this max 2000 1600 1600 values with no problem at all and the same (first) battery.
[Samsung Galaxy S 5 Unified Development] LeoJrC:
Idk if it just happens with me but when I flashed your nougat kernel, all of my system animations got laggy. I tried to change the governor and hotplug but the only thing that stopped it was reflashing the ROM in order to get rid of this lag. Them, yesterday, I flashed the Oreo version (I'm using blackjubbel's AICP 13.1) and got the same system animation lag. Idk if it's possible to get a logcat since every animation (System UI and apps. Scrolling my Facebook timeline is a pain) is lagging. I'm not complaining about anything but I didn't see anyone talking about it so I suppose I'm the only one with it. I'd like to know if I can do anything about it :/.
[Samsung Galaxy S 5 Unified Development] furkaan28:
Use nightmare
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
You are right. Seems like its possible. Trying to control fast_charge current levels. Work-in-progress. Some improvements in the Screenshot.

Extremely sorry to disappoint you. But I can't. However, you or anyone else can freely build from my source.

Agreed. That could be the ideal. However, the second part (making custom controls to allow KA to override values) seems more progress.... and of course testing...

Thanks. So, I will pre-define much more current...

Hi, My Noguat and Oreo Kernels works pretty well in LOS-14.1/15.1 respectively after some tunings. I'm using *Nightmare* / *Lazyplug* combo without touch boost. Regarding aicp, I do not know whether [MENTION=6647671]Blackjubel[/MENTION] using the same LOS-15.1 kernel. If not, I won't recommend using my Oreo kernel over aicp.