yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Or may be because of the new kernel source code merged by LOS team... who knows? Anyway, it shouldn't be my credit:p Either LOS Team or Google or Samsung:)

Seriously, one more hotplug:confused:
[Samsung Galaxy S 5 Unified Development] Blackburn119:
Some of already existing hotplug are not necessary and intelliplug is one of the most widely used hotplug in any other custom kernel
[Samsung Galaxy S 5 Unified Development] Cirra92:
Intelliplug has been performing consistently great on my previous SD801 device (Z3 compact) with various interactive governor tweaks. Here I get occasional lags and stutters even with default interactive tweaks and with my own adapted tweaks no matter what Hotplug I use (except MSM which I use now and it's acceptable). My suggestion would be to remove Mako and Zen hotplugs, and add Intelliplug, but hey it's your kernel so it's your decision in the end :)

One more thing: Did you remove some GPU tweaks? GPU freq is not staying at minimum value, which is now 200mhz and it was 27mhz in previous releases.

Anyway the kernel is really great, it has all essential stuff without bloat, so just keep it up :D
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
plz tell me about one such kernel (to check the code)?

hi, thanks for the suggestions. Let me check the possibilities to implement intelliplug... Btw, l haven't added the 27 mhz step after the a rebase (couple of weeks ago) since I decided to stay with stock LOS... and is everything fine with MSM hotplug? I haven't tested that much...
[Samsung Galaxy S 5 Unified Development] Cirra92:
Are you planning to add 27mhz step and some tweak to keep it at 27 mhz as much as possible? I think that was how it worked before you did a rebase, now it's mostly at 266mhz even though 200mhz is minimum.

Anyway, MSM has been doing good so far, it's quick to turn off all but one core when there is no touch input, and quick to enable another extra core if needed, my feeling is that maybe it's how Intelliplug has been on my Z3C, however it's not quite same device as S5 so I can't just compare them like that :)
[Samsung Galaxy S 5 Unified Development] vd69:
Very nice job thank you.How can i change gharging usb rates up to 1600 .I mean more than 890 that is possible thru the aduitor mod app.

Thanks
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
the 27 mhz step is again added (thanks to Lord Boeffla:p) and should be available in the next build (though I never uses and even don't know the benefits). But, I'm not sure abt intelli_plug (is it intelli_plug or intelli_hotplug?). My attempts to add that hotplug was not successful yet. Further, I can't find intelli_plug on any nougat/marshmallow custom kernels for msm8974 platform. So, might take more time... anyweay, thanks for the suggetions.

I think it is not possible to change the current in KA app (atleast not easy). The charging values are currently (Custom AC level : 2100mA/h; Custom USB level : 1000mA/h; Custom Wireless level : 650mA/h).
[Samsung Galaxy S 5 Unified Development] Cirra92:
You can add 100mhz as well, just if lags occur to prevent them :) That lower freq *should* help lower the battery usage. Well I think that they label it as Intelliplug, it's a hotplug just as MSM or Zen.

Ok, I've been digging in Z3Compact forums since I've used it and have this, hopefully it will help you, both of these have Intelliplug, but for MM.

https://github.com/someone755/android_kernel_sony_msm8974_stock

https://github.com/panzerox123/darkkernel_kernel_sony_msm8974

Cheers :)
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Done...

Okay... Job done (ofc after several modifications). Will test for a day before public release... Screen shot is available here... Btw, thanks for the links...
[Samsung Galaxy S 5 Unified Development] londonbabs:
Wondering if anyone could enlighten me, since we're on the hotplug topic. I'm enjoying zzmoove cpu governor lately (top kernel by the way [MENTION=7060205]sunilpaulmathew[/MENTION], running on G900V with latest resurrection remix, tried on LOS 14.1 previously and was so happy with my renewed battery life and ice cold running phone, thank you so much!), and understood it has its own in-built hotplug, would that be correct, or would you say I could go ahead and activate another one (the above sounds interesting)?

Also, I wanted to report constant device crash when trying to activate simple_ondemand GPU governor (regardless of the ROM or different settings in adiutor). Not a huge deal for me, but I thought if you could use a report or any more details, it'd be happy to share. Would need a couple of advice though maybe, I've never had to create a report before. I'm sure I could manage to find how to with Google, however, should I create the report immediately following the crash and reboot (I assume yes)?

In any case, if I can help with anything, it'd be my pleasure. Once again, thank you so much for the hard work and for such a polished creation!
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Hi, thanks for testing and comments. The situation of zzmoove is bit complicated than many other govs (according to many experts, zzmoove is something more than a simple cpu gov). In my opinion, if you decided to use zzmoove, better disable all other hotplugs including mpdecission (since zzmoove has its own hotplug profiles and it likely creates issues with other hotplugs).

Regarding simple_ondemand, I assume that you are using an old build (isn't it?) of my kernel. The issues with simple_ondemand has been already reported by some users and after several (failed) attempts to fix, I removed that feature itself.
[Samsung Galaxy S 5 Unified Development] londonbabs:
Ah, my bad, I could have sworn I read through the whole thread. I must have missed this bit.

Actually, I try to stay up to date with your latest builds and flashed klte_20170627, which I am running now (dirty flash, would it matter though?)

In any case, no worries, as I said, I just don't activate it ;)

And thanks for confirming about zzmoove, I did run it a bit with another hotplug once (not yet knowing it'd be better advised not to) and didn't notice much issues. Better not take the risk though, I guess. I'll keep trying to read up on it, it's an interesting one I find.

Again, thanks for your awesome work, can't wait for your next cook up!
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
New builds are uploaded...

Stable release: v8

Changes: Linux kernel version is updated to 3.4.113. Few more updates to the sound control (credits: franciscofranco). Activated additional 27 MHz gpu frequency step (credits: Lord Boeffla). New cpu hotplug: intelliplug (credits: Faux123).

I don't know whether all the additions are working properly on all the devices (only tested on my kltekor) and honestly not aware (and don't care personally) about the benefits of features like additional 27 MHz gpu frequency steps added as per the suggestion of [MENTION=5070317]Cirra92[/MENTION]. [MENTION=7860020]Blackburn119[/MENTION] and [MENTION=5070317]Cirra92[/MENTION] plz test intelli plug too since I made some modifications to make it compatible (though everything seems fine in my device). Now it is your turn to test and report about issues if any. So, waiting...

Download links are here...

/* Downloads */

[B][COLOR="red"]Always remember to download the latest build (dated 20170706) for your device.[/COLOR][/B]

kltekor

klte

klteduos

kltedv

kltespr​
[Samsung Galaxy S 5 Unified Development] londonbabs:
Everything smooth this side of klte using G900V.

Switched to alucard CPU gov to test intelliplug, I'll keep these settings for a few days and try to play around, see how it holds. But, so far, all looks absolutely fine.

Only slight weirdness is CPU temp in overall now showing 0.04°C/0.05°C/etc, but still fluctuating. Not the end of the world, and still gives an idea of the actual temperature. [edit] Never mind that, looks like it may be an adiutor issue actually. [edit 2] Thanks [MENTION=7860020]Blackburn119[/MENTION] for confirming the aforementioned :highfive:

I'll send logs if anything blows. Thanks again!
[Samsung Galaxy S 5 Unified Development] Blackburn119:
It's actually kernel auditor display bug, everyone got it too after getting new update from play store.

So far intelliplug is a well running hotplug that keeps my overall CPU frequency at between 300mhz to 960mhz without sacrificing performance.
[Samsung Galaxy S 5 Unified Development] Cirra92:
Thanks for the update and your quick reaction towards suggestions :)

I quite like what I see with Intelliplug now, previously the most used freqs would be 1574 mhz, 1728 mhz and 1958 mhz, it is now 960mhz and it is still very smooth! Higher freqs are rarely used, since I don't do gaming. I am rather using Facebook app, Instagram and instant messaging apps like WA and Viber, bit of browsing through Chrome Canary and even with those apps freqs are now more stable as opposed to contantly jumping to max or just below max with previous update. Finfers croosed that it will stay like this.

Thanks again! :victory:
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Nice to know that it worked.. .thanks for testing and comments... cheers...:good:
[Samsung Galaxy S 5 Unified Development] Saber:
[MENTION=7060205]sunilpaulmathew[/MENTION]

Thanks for your awesome work. Default kernel settings were quite laggy throughout the whole android UI but after playing around with some governors and hotplugs, all is very smooth and buttery. Right now I'm using Nightmare + Alucard hotplug (IMO one of the best combinations since the s2 days) and getting awesome battery life.

It has been a while since I've comfortably settled on a custom kernel for daily driver (despite being a former kernel maintainer myself).

Edit: Also played around with intelliplug and I found it very stable and quite battery friendly.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Thank you very much [MENTION=5811506]Saber[/MENTION] for spending time for testing and also for sharing your settings that u found smooth and buttery. Really nice to know that you are comfortably settled :p

Btw, there is no default settings in my kernel except TCP cong algo (westwood) and iosched (sio). The rest are simply stock and I leave the rest to users...

A request to all... Hopefully, u all have your own fav settings. It will be really nice if you share ur fav settings... It will be really useful for others... for me it is,

CPU gov: Nigtmare; CPU hotplug: intelliplug; CPU untervolting: upto -50; Intelli thermal, sound control, Fast charge, Dynamic Fsync etc all active and the rest are default...
[Samsung Galaxy S 5 Unified Development] Cirra92:
Alright so atm I'm using this setup, although it may get changed in a couple of days to my preferred one from Z3 Compact, however this is also good enough for me.

CPU gov: interactive (screenshot attached)

CPU hotplug: IntelliPlug

Voltage: -50mV on all steps

Thermal: Intelli-thermal

Internal I/O scheduler: row read-ahead 1024

External I/O scheduler: bfq read-ahead 4096

LMK: my own settings (screenshot attached)

I'm using L Speed app with Governor tuner set at Battery setting (it changed governor settings itself, see screenshot), however as noted, I may set them to my personal ones, but so far this is doing okay.
[Samsung Galaxy S 5 Unified Development] mgp53:
What effect do the sound tweaks have on the volume levels? If I increase above 0, sound is muted entirely. No notification or phone. :confused:

Sent from my SM-G900T
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Thanks for the quick action... :)

Sorry, I forget to mention that (even very late to noticed), you need to set atleast '1' (the value '0' sometimes makes issues like you said). from values '1' to '20', it reasonably increase the speaker and headset volumes (but sadly with little noise).
[Samsung Galaxy S 5 Unified Development] :
My setup is almost the same as yours except I underclocked to 1728 and undervolted by 100.
[Samsung Galaxy S 5 Unified Development] snk3:
This kernel is compatible with G900M and the last release of resurrection remix?
[Samsung Galaxy S 5 Unified Development] dan13l3:
During a phone-call if i switch in vivavoice microphone doesn't work anymore. I can ear people talking but he doesn't ear me :eek:

Any help?

Edit: after a check in audio section in Kernel Adiutor finally I figured it what did you mean :cyclops:

Than, solved! ;) Sorry for this stupid post :p
[Samsung Galaxy S 5 Unified Development] londonbabs:
I'm using the klte build on the latest resurrection without any problem, and someone mentioned they successfully installed the same build on their G900M, I suppose it should work?

Go with a backup in TWRP first, you should be safe :)
[Samsung Galaxy S 5 Unified Development] LHR:
Anyone experiencing any problem with intelliplug? For example, my statusbar clock does not update hahahahah
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
See the Lineage OS supported variant list for kltexxx.

[OFFICIAL] klte - SM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8, SM-S902L
[OFFICIAL] klteduos - SM-G900FD, SM-G900MD
[OFFICIAL] kltedv - SM-G900I
[OFFICIAL] kltekor - SM-G900K, SM-G900L, SM-G900S
[OFFICIAL] kltespr - SM-G900P

Your device is a part of klte. So, you can safely flash the klte build of my kernel. However, as [MENTION=6042110]londonbabs[/MENTION] said, backup first.

Great. you did it...:good:

Not yet... will wait for that bug.. :laugh: ha ha ha
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Guys, I'm planning to pre-set some values to sound control to avoid some issues (no sound when Speaker Gain is "0"). Any suggestions? Which will be the best values to get best sound with minimum noise and less echo... My current configuration is here. waiting for your comments... Thanks in advance...
[Samsung Galaxy S 5 Unified Development] investinwaffles:
Flashed both the light and full versions of this Kernel and now I have zero microphone on my KLTESPR

Not via Bluetooth, not via a hardwired headset, and of course not via the built-in microphone

Tried all gains and settings but no dice.

Going to flash the LOS kernel back on, it at least worked at a laughably low volume :(

Love the battery and stability of this kernel otherwise

Tired of the microphone issues with LOS to be honest, this used to fix them to where I didn't have to scream into my phone in public but no more...

EDIT:

Flashed the LOS kernel and reset my Kernel Auditor settings, then flashed back to SmartPack Lite and on the default settings it seems that the mic is working (but sounds like I am 20ft away from the phone which I was expecting), and if I change the gain to anything other than 0, my microphone stops working on all inputs. With it at 0, I can use my wired headset but not my bluetooth one...

grr
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Hi, I had the mentioned issue and it goes when I set all the gains (speaker, microphone and volume) into atlest "1". Any number below or equal to "0" might make issues. I'm personally using speaker gain "3" and other two gains "10" without issues (see the screenshot in my previous post).

Edit: Bluetooth is a different issue in which Kernel has very little role to control... My kernel only have control over the inbuilt speaker as well as wired headsets...
[Samsung Galaxy S 5 Unified Development] dan13l3:
Every time I changed volume settings I have to save new settings than is necessary to reboot phone.

Only after reboot settings works :silly:

I have all valume gain set to 1 (0 is equal to "off" for me).

All other step over 1 are too much high and cause noise and distortion
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Hi, thanks for the information. So, everything is fine if all the values are set into "1", right?

Btw, instead if setting the values after every reboot, just check 'Apply on boot" in the Kernel Auditor (see the screenshot in one of my previous post) so that it will apply the values automatically :p
[Samsung Galaxy S 5 Unified Development] dan13l3:
Yes, "1" is the right set for me :good:

I just flag it but without reboot changes doesn't works for me :eek:
[Samsung Galaxy S 5 Unified Development] cfsr4:
With this kernel does vipermod work?
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Honestly, I have no idea. sorry. May be someone else can help...
[Samsung Galaxy S 5 Unified Development] dan13l3:
If you mean ViPER4Android yes, it works fine
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
New builds...

Stable release: v8_r1

All the commits in the LOS kernel source till date... Sound control (my fav values) and Fast charge features are now enabled by default. Now it is your responsibility to disable (fast charge) or change the gain values (sound control) according to your choice :p

Advised to flash over the latest LOS build (there are so many changes in the LOS source code)... Download links are here... Enjoy...

/* Downloads */

[B][COLOR="red"]Always remember to download the latest build (dated 20170713) for your device.[/COLOR][/B]

kltekor

klte

klteduos

kltedv

kltespr​
[Samsung Galaxy S 5 Unified Development] GZeromskas:
Hi

Speakerphone not work talking:crying:
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
I pre-set some gain values in the sound control. That might make some conflicts especially if you guys are already applied some other values to the sound control. To solve that, just remove the check mark on "Apply on Boot" in the Kernel Auditor --> Sound and restart. After restart, you can see the new deafault gain values in Kernel Auditor --> Sound tab (ofc, u can change if you wish to do so). Can you guys try and check if it solves? Thanks...
[Samsung Galaxy S 5 Unified Development] dan13l3:
In addition to this i have to uncheck mark on apply on boot on menu profile's choice (see the attached below), otherwise microphone doesn't works :rolleyes:

I don't know if this is a kernel's issue or a bug of Kernel Adiutor app
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
May not be an issue of both... simply the conflict btw the pre-setted gain values and individual values selected by individual users.

And yes, you need to do the necessary changes if you are using a profile...

Edit: you can edit and uncheck the sound tab from the profile...
[Samsung Galaxy S 5 Unified Development] dan13l3:
Infact now I have unchecked all switch's Apply on boot, but to set kernel how I wish, I have to load profile manually.
[Samsung Galaxy S 5 Unified Development] GZeromskas:
Thank you. What is the Known CPU Frequency:confused: Will it work

[IMG="CPU"]https://dl.xda-developers.com/4/2/1/1/2/6/5/Screenshot_20170714-101142.png?key=eI4LEfxgeckhG-uULzR9hQ&ts=1500020107[/IMG]

[IMG="Boot"]https://dl.xda-developers.com/4/2/1/1/2/6/6/Screenshot_20170714-101217.png?key=I_syzaQZqdreqUy0ITIT9w&ts=1500020176[/IMG]
[Samsung Galaxy S 5 Unified Development] Blackburn119:
It is because of this kernel or lineage ROM itself? My Korea S5 running 07122017 build just got a random reboot while using Facebook app.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Sorry. I can't get you clearly...

What you mean?

Not sure... I'm also using Facebook app a lot on my kltekor and is so far stable. In the main LOS thread, many users reported that the phone gets rebooted while using camera apps (both snap and 3rd party). But, so far, no complaints abt Facebook in LOS as well as this thread...
[Samsung Galaxy S 5 Unified Development] Blackburn119:
Maybe I got the same issue like them, before I open FB app I also did open camera to take a selfie.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
New builds...

Maintenance update: v8_r2

All the commits in the LOS kernel source till date... Download links are here... Enjoy...

/* Downloads */

[B][COLOR="red"]Always remember to download the latest build (dated 20170720) for your device.[/COLOR][/B]

kltekor

klte

klteduos

kltedv

kltespr​
[Samsung Galaxy S 5 Unified Development] mgp53:
The last commits messed up the camera. Go back to release 8.
[Samsung Galaxy S 5 Unified Development] ariel5zal:
Are the v8 r2 stable ..or v8
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Both are actually stable. However, due to some recent commits in stock kernel source, v8_r2 might makes some issues like camera error on some device variants (though I don't have such issues on kltekor).

So, in my opinion, try the latest first and then go back to v8 only if you have issues...
[Samsung Galaxy S 5 Unified Development] ariel5zal:
Okey I will give a try..thanks
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
New builds...

Minor update: v8_r3

This is just a minor update. You can even avoid this. The only change is that zzmove cpufreq gov is updated to the latest version (credits: zanezam)... If anyone interested, plz test zzmove (preferably after disabling other hotplug) and share your comments. In my personal use for a week, it is reasonably good. And hope it will not kill the Camera :p Download links are here... Cheers...

/* Downloads */

[B][COLOR="red"]Always remember to download the latest build (dated 20170727) for your device.[/COLOR][/B]

kltekor

klte

klteduos

kltedv

kltespr​
[Samsung Galaxy S 5 Unified Development] Blackburn119:
Hello please kindly update your boeffla unofficial kernel, 12072017 version came with camera bug.
[Samsung Galaxy S 5 Unified Development] cfsr4:
What the best configuration for daily use ?

---------- Post added at 02:57 PM ---------- Previous post was at 01:59 PM ----------

How to organize as information as in your prin. Here they stay like this.
[Samsung Galaxy S 5 Unified Development] brickhayabusa:
my microphone won't work on calls or audios

using synapse-.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
How you got synapse working. Because, I haven't add support to synapse. and is the sound controller is accessible in synapse. If so, revert everything you done on the sound tab and reboot. It will hopefully work.
[Samsung Galaxy S 5 Unified Development] brickhayabusa:
nope, didn't make any change to the sound tab, but thnx for reply.
[Samsung Galaxy S 5 Unified Development] heshan_1010:
Is it just me or does the fast charge only work when it is disabled in kernel auditor?
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
mm... your observation is probably correct. I think I recently did some stupid mistakes in the fastcharge code. Don't worry, I will revert it. So, it will be fixed in the next build.

A quick question to all. Is anyone still using klteduos, kltedv and kltespr builds of my kernels (both SmartPack & Smartpack-Lite)? If yes, plz let me know. Otherwise, I shall stop building for those devices (only if no one using). Removing each build will save significant amount of work load to my build system (my 5 yr old laptop:p) as well as my time. looking forward to your replies...
[Samsung Galaxy S 5 Unified Development] s3v3ngal:
Hi mate I'm using the kltedv build running awesomely on crdroid for now =p would appreciate if you could continue if I'm the only one I understand if u can't
[Samsung Galaxy S 5 Unified Development] Panzerknakker:
Using klteduos with SP, sometimes SP Lite.
[Samsung Galaxy S 5 Unified Development] LHR:
keep klteduos build alive!
[Samsung Galaxy S 5 Unified Development] zahin5542:
Use klteduos and loving your works ....this is so far better kernel source for klteduos....thanx , please keep alive this section
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Ok guys, I have no reasons to stop building for any device as long as it is useful for someone. So, I won't stop any of my builds of SmartPack and SmartPack-Lite... cheers...
[Samsung Galaxy S 5 Unified Development] montecarlo5:
Still using kltespr here. Thank for still building!
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
New builds...

Stable release: v9

Changes: All the commits in the LOS source code till date. Some recent commits in the fastcharge feature (that makes the feature enabled by default) are reverted (Now you need to manually enable the feature in Kernel Auditor).

Cheers...

/* Downloads */

kltekor

klte

klteduos

kltedv

kltespr