yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Chang-logs

18. August 16, 2017

Stable release: v9_r1

Changes: The source is fully re-based (since LOS kernel source is re-based by the development team). Some of the commits suggested by [MENTION=5811506]Saber[/MENTION] is included...

17. August 02, 2017

Stable release: v9

Changes: All the commits in the LOS source code till date. zzmove cpufreq gov is now updated to the latest version (credits: zanezam). Some recent commits in the fastcharge feature are reverted...

16. July 19, 2017

Maintenance update: v8_r2

Changes: All the commits in the LOS kernel source till date...

15. July 13, 2017

Stable release: v8_r1

Changes: Intelli_plug is added as a replacement to Zen_Decision. Sound control (my fav values) and Fast charge features are now enabled by default. All the commits in the LOS kernel source till date...

14. July 6, 2017

Stable release: v8

Changes: Linux kernel version is updated to 3.4.113. Few more updates to sound control.

13. June 27, 2017

Stable release: v7

Changes: Source code is merged with Samsung's latest source (thanks to [MENTION=2693412]haggertk[/MENTION] and LOS team). Sound control is updated to fix some issues with speaker sound (now it seems fully working). Toolchain is switched to Google's latest arm-eabi-4.9 r15.

12. June 21, 2017

Maintenance update: v6-r1

Changes: Nothing other than the recent LOS commits till today...

11. June 14, 2017

Stable release: v6

Faux sound is replaced by sound control (credits: franciscofranco). Linux kernel version update to 3.4.113 is temporarily reverted (now its 3.4.111) due to some issues.

10. June 8, 2017

Stable release: v5

Linux Kernel version is updated to 3.4.113. All the recent commits in the LOS source code till date.

9. June 1, 2017

Stable release: v4-r3

Source is fully re-based. USB fast charge is back (replaced charge level). Recent commits on the LOS source code till date.

8. May 24, 2017

Stable release: v4-r2

Changes includes the replacement of Mako hotplug with msm zen decision as well as all the LOS commits till date.

7. May 18, 2017

Maintenance update: v4-r1

Nothing other than latest LOS commits.

6. May 10, 2017

Stable release: v4

Linux Kernel version is updated to 3.4.111. All the commits in the LOS kernel source code until now.

5. May 03, 2017

Stable release: v3

Fast charging feature is now replaced with charge level interface (credits: Lord Boeffla).

All the recent changes in the LOS source code are included.

4. April 19, 2017

Maintenance update: v2-r2

Nothing other than the latest LOS commits.

3. April 15, 2017

Maintenance update: v2-r1

Nothing other than the latest LOS commits.

Support to new devices: kltespr and kltedv

No more separate build for kltevzw since LOS officially merge kltevzw with klte.

2. March 31, 2017

Stable release: v2

Nothing changed other than the latest LOS commits

1. March 27, 2017

Stable release: v1
[Samsung Galaxy S 5 Unified Development] badassadism01:
Can this be flashed over the original smartpack kernel?
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Sure... It will work...
[Samsung Galaxy S 5 Unified Development] KazuDante:
to achieve a 100 undervolt : max cpu frequency should be set to 1958mhz and low to the users prefrence , the gov set to conservative , also idont know if you can use boeffla git and permission to add the options of determing the maximum amout of cores that can go online setting it to 3 cores max is perfect and reduce power since one of them wont be used , i dont think the rest affects it but what i will say is that the gpu needs a working gov and add 27mhz frequency so that it can idle at 27mhz with screen off.
[Samsung Galaxy S 5 Unified Development] marcioafoliveira:
working nice on new ressurection remix build :)
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
New builds are uploaded...

[B]March 31, 2017[/B]
Stable release: v2
Nothing changed other than the latest LOS commits.
[Samsung Galaxy S 5 Unified Development] HaRdC0r3:
For starters. THANK YOU! I dig this kernel....Second I have a few requests

1...Could you add MSM Hotplug from myfluxi

2...Could you add Maple and Zen to the IO Schedulers

The reason I ask if because I tune Mako to have all 4 active at all times as I feel it doesn't impact battery and it feels better with these settings for me...MSM it is more customization. Also I'd like to play with those schedulers. I know that you have Zen in the other kernel but I like the less is more approach to most things in my life....so this lite version suits me.
[Samsung Galaxy S 5 Unified Development] thaidroid:
[MENTION=268346]sunil[/MENTION],

Trying the Kernel now what will be the major power savings is it the kernel itself or other areas?
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
HI. I'll try to add those features to the full version of my kernel first and eventually here (depends on the success :p). Thanks for the suggestions...

A lot of things (they are cool stuffs, but not necessary) were actually removed from the original LOS Kernel. Further, minimal features are only implemented to reduce the kernel size as much as possible. So, the kernel itself will be the major power saving factor (I hope).
[Samsung Galaxy S 5 Unified Development] badassadism01:
Would you want to add arch power saving to this kernel?
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
any reference (xda thread, github etc) plz?
[Samsung Galaxy S 5 Unified Development] badassadism01:
I think crazygamer dev has implemented it in his kernel, tnough it's discontinued I think. https://github.com/CrazyGamerGR/CrazySuperKernel-CM14.1-KLTE-New-rebase
[Samsung Galaxy S 5 Unified Development] thaidroid:
[MENTION=268346]sunil[/MENTION],

When I try to use another ROM together with this Kernel or your "BIG" version, everything seems fine with one exception.

Skype app always crashes. Ive tried with KLTE 14.1 (You get a lot more network options on G900S with the klte rom) and also Cosmic and crDroid.

Same result in all of them. Could you test if you have some spare time?

Also when I restore after trying I still get the app crash, to fix I do a restore and then immediately install ROM and Kernel on top/wipe dalvik and cache/Reboot and all is fine
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
How abt this issue in stock kernel or any other custom kernel? Just to check the role of kernel in this issue...
[Samsung Galaxy S 5 Unified Development] thaidroid:
:D:DSunil I can't test those things with stock Kernel(G900S)that's the reason I'm using your excellent kernel. I have asked and looked in the threads but there are no Skype issues regarding this posted.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Okay... I understand the issue. I'm presently using LOS (kltekor version) without no skype issue. I will later test CRDroid and CosmicOS for skpye issue...
[Samsung Galaxy S 5 Unified Development] thaidroid:
Just dirtyflash LOS klte with your kernel and see if Skype will work (everything else should work...I think)? You can then Reflash kltekor again with your kernel to get everything back to normal.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Sorry to disappoint you... I tried LOS klte build as well as cRDroid klte buids. As you said, skype is crashed in the case of both ROMs after dirty flash... and works fine with kltekor build. Absolutely no idea to solve the issue. Even don't know it's a fault of my Kernel or not... :confused:
[Samsung Galaxy S 5 Unified Development] Blackburn119:
Why did you remove interactive governor?
[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... cu very soon with new builds... cheers...
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
New builds...

Stable release: v9

Changes: All the commits in the LOS source code till date. zzmove cpufreq gov is now updated to the latest version (credits: zanezam). 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). Download links are here...

Cheers...

/* Downloads */

kltekor

klte

klteduos

kltedv

kltespr
[Samsung Galaxy S 5 Unified Development] androidundies:
I've applied the v9 update and am no longer seeing the issue with the camera freezing on kltespr! Thanks again for all of your work on this great kernel.
[Samsung Galaxy S 5 Unified Development] j1gga84:
[MENTION=7060205]sunilpaulmathew[/MENTION]

are you still working on new builds my friend? :)

Edit:

I should maybe also read in your other thread: https://xdaforums.com/showpost.php?p=73346420&postcount=333

looking forward, saber really is a good guy, he continued kernel developing of an EOL kernel for the Samsung Galaxy S2 back in the days :)

regards
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Yes... I'll surely push new builds along with each LOS builds if there is something changed in the LOS source or my source.

I found that the LOS kernel source is totally re-based last day. So, I'm also forced to re-base everything (it will be more easy to re-base, rather picking thousands of commits from the LOS source). If everything goes well, I'll soon provide much better and fresh builds (hopefully along with the new LOS build)... stay tuned...
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Test builds...

Need testers... anyone plz...

Hi all... SmartPack-Lite is now fully re-based (since LOS kernel is largely modified). I also added some patches suggested by [MENTION=5811506]Saber[/MENTION] in my SmartPack kernel thread (Thanks a lot to Saber). Everything seems working great in my kltekor (see the battery stats). However, I like to get some comments from klte users. Here I'm posting two test builds (for klte and kltekor). If everything goes well, I'll push new builds along with new LOS release... Thanks in advance

Note to all testers: please test overall stability and smoothness of the kernel...

Test builds are here...

kltekor_testbuild

klte_testbuild

PS: My personnel settings are cpufreq gov (nightmare): CPU hotplug (Intelli_plug): CPU voltage (-50): IOSched (SIOPLUS): TCP (Westwood)
[Samsung Galaxy S 5 Unified Development] j1gga84:
I flashed the test kernel, booted up without no issues, camera (also video recording) is working.

I set the same settings except undervolting because I did not have much positive effects with that in the past ;)

When I set these settings 3 cores are normally offline when not touching the screen but in kernel adiutor the frequency of the first CPU core is at 652MHz and only for a few seconds at 300MHz, sometimes at 422MHz but most of the time at 652MHz, the load is between 40 and 50%, is that normal? I think 300MHz in Idle mode would be better.. !?

Or must I set something different at "Multicore Power Saving"? Currently it is disabled.

The CPU hotplug profile is set to balanced, touch boost activated, CPU treshold 722, read-ahead for phone memory 1024kB, for external storage 2048kB (because I have a 64GB SD card).

regards
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Perfect... Thanks for testing. I think the the cpu related stuff is just normal (or atleast not a big issue). Btw, have you activated touch boost in the cpu hotplug tag? If so, can you disable it and check again?
[Samsung Galaxy S 5 Unified Development] j1gga84:
I don't know how the behaviour is on stock kernel but what I can say is that on first sight the battery life is better than on V9 :good:

I will just check telephone calls during my work break but I think it will also work :)

For me, everything is stable for now.

What do you mean with disabling touch boost in cpu hotplug tag (yes, I have activated here)? You mean if it is relly disabled when disabling it?

Or if the performance decreases?

EDIT:

Telephone calls also work without no issues but I just had a random reboot when device was in deep sleep.. Never had that before.. I will see if it occurs again.

regards
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
I mean, in the Kernel Auditor ---> CPU hotplug tab (sorry, it is accidentally mentioned as tag in my previous comment), there is a TouchBoost option which is enabled by default. I suspect that it might be the cause of little high cpu idle freq (not sure though)... You may disable it and test... Btw, all other things including telephone calls should work (since I haven't made any change)...
[Samsung Galaxy S 5 Unified Development] j1gga84:
Okay I will check that.

Please see my post, I edited it.

I just had a random reboot out of nothing since ages :(

EDIT2: Second system freeze and reboot..

EDIT3: Okay, I maybe found the reason, MPDecision AND IntelliPlug was activated, alltough I have not activated MPDecision.

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Yup... That might be the reason. Btw, MPDecission will be activated unless you disabled it in the Kernel Auditor + tick "Apply on boot". Another possibility... Are you using zzmove? If so, it is better to disable all the hotplugs...
[Samsung Galaxy S 5 Unified Development] Prime Evil:
Hi!

I also test the new Kernel Version.

Found a problem:

Start the Camera App, in picture mode the screen remains black.

On video mode all is fine!
[Samsung Galaxy S 5 Unified Development] j1gga84:
Which camera do you use?

I read in the SmartPack "normal" thread that there seems to be an issue with open camera.

regards
[Samsung Galaxy S 5 Unified Development] Prime Evil:
The standard RR Rom camera.

When I use another Smartpack Lite Kernel, all is fine!
[Samsung Galaxy S 5 Unified Development] j1gga84:
Strange, I don't have this issues but I don't use official RR, maybe that is the reason.

Which RR build do you use?

regards
[Samsung Galaxy S 5 Unified Development] Prime Evil:
I use the inofficial Build from fessmm from 10.08.
[Samsung Galaxy S 5 Unified Development] j1gga84:
Strange..

I use the same build and everything is working on my side..

regards
[Samsung Galaxy S 5 Unified Development] j1gga84:
[MENTION=7060205]sunilpaulmathew[/MENTION]

I had the next strange behaviour with latest test build.

After a telephone call I was not able to unlock the phone (fingerprint)..

I will observe it further but for now the test build is not as stable as v9 on my side..

Edit:

Third reboot with the test kernel today.. I guess I will go back to latest final :(

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Samsung Galaxy S 5 Unified Development] Saber:
I know I'm a bit late but... Hotplug driver already handles which CPU core should online, thus enabling multicore power saving is not necessary.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
mm... okay... I'm now working again on Smartpack-lite and the new build (within one day) will hopefully work well with the next LOS/RR builds. not sure abt the ROMs released before Aug 14 (since the kernel is largely modified). Surprisingly, SmartPack (not Lite) seems pretty stable... :)
[Samsung Galaxy S 5 Unified Development] j1gga84:
okay, thanks for information, I appreciate your work very much :) :good:

I went back to v9 with the same settings and here the active CPU core 1 is mainly at 300MHz when not touching the display , sometimes there are short peaks to a higher frequency (when CPU load goes up) but normally it is at 300MHz.

This did not work with the test build, the minimum CPU frequency was higher and the peaks were much more.

regards
[Samsung Galaxy S 5 Unified Development] Blackburn119:
Disable all the hotplugs including mpdecision or keep it enable?
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Thanks for the nice words and also for the information...

The rule is simple... do not use more than one hotplug at the same time... and it is better to disable all the hotplugs while using zzmove (since zzmove uses its own hotplug profiles and it is pretty good)...
[Samsung Galaxy S 5 Unified Development] Blackburn119:
Ok now i can disable mpdecision with this new updated version of zzmove before it gave me a random reboot when i disabled mpdecision with zzmove.
[Samsung Galaxy S 5 Unified Development] koobie777:
I'm pretty new to the s5 coming from s3. Is the klte build safe on kltespr?
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
It will probably work. However, I'll soon update new builds which include a dedicated build for kltespr. So, its up to you to try now or wait for next build (in few hours)
[Samsung Galaxy S 5 Unified Development] koobie777:
Well I have used ROMs that were just klte but when it comes to a kernel I'll play it safe and wait. Thanks for the work your putting in btw. Any way you could add free lunch governor?
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
New builds...

Stable release: v9_r1

Changes: The source is fully re-based (since LOS kernel source is re-based by the development team). Some of the commits suggested by [MENTION=5811506]Saber[/MENTION] is included... Since the source is largely modified on Aug 14th, I suggest all of you to use this build with the new LOS builds (supposed to be out tonight) or an equivalently new ROM (preferably released within 2 day)... I hope this build with the latest ROMs will solve some of the annoying issues...

Special thanks to all the testers... :p

Download links are here... Enjoy...

/* Downloads */

[COLOR="Red"]Always remember to download the latest build for your device(dated 20170816)[/COLOR]

kltekor

klte

klteduos

kltedv

kltespr
[Samsung Galaxy S 5 Unified Development] j1gga84:
Many thanks for the update :good:

I will check it for a while and report back :)

I flashed todays RR 5.8.4 of [MENTION=6018432]furkaan28[/MENTION] and have no issues so far.

The only difference I observed between v9 and 9_r1 is that the minimum frequency when screen is on and device is idle was, as described before, at around 300 MHz in v9, in 9_r1 it is at about 652 MHz but I don't know what's the reason for that..

Maybe because the CPU load of one core is higher than in v9 :confused:

[MENTION=5811506]Saber[/MENTION] maybe you also have an idea?

Something different, in the logcat (Matlog for example), I have a lot of "QCOM PowerHAL - Failed to acquire lock" errors

On my Samsung Galaxy Tab S (Exynos processor) I also use an unofficial RR 5.8.4 but I don't have this error there.

Somebody told me, back in MM days, that this was an kernel related error.

Any ideas for that?

EDIT:

Again I had a reboot out of nothing when device was in deep sleep :(

I only see boot anymation but device does not boot anymore. I had to hold VOL Down, Power and Home to manually reboot to the system..

I did not have these issues on the v9 build from 02.08.2017..

Very strange

Regards
[Samsung Galaxy S 5 Unified Development] Triple [-] [-] [-]:
Hello j1gga84,

Do you use the latest Version of [MENTION=6018432]furkaan28[/MENTION] from 15.08.2017 ? I have 2 Reboots with the Version from 10.08.2017 and SPLK from 02.08.17,not in Deep Sleep but in the Settings Menu.(Freeze und anschliesend Neustart)

My Videos Recordings does not play at the first Time, after Reboot Playback works again.I fix this issue with the SPLK from 10.05.2017.

GreeTz!
[Samsung Galaxy S 5 Unified Development] j1gga84:
Yes, I use the latest build of furkaan28 from 15.08.2017.

With this build and the build from 10.08. I had absolutely no issues with SmartPack Lite from 02.08.2017, also not in the settings menu.

The issues start with the test build of SmartPack-Lite and yesterdays new final build.

These builds are based on the totally rebased stock LOS kernel and I guess that there is still something wrong.

Also furkaan28 went back to previous SmartPack Lite from 02.08.

regards
[Samsung Galaxy S 5 Unified Development] Blackburn119:
RR is not a standard Lineage based rom anymore. It's normal you would face some bugs after this re-based.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
[MENTION=4699854]j1gga84[/MENTION] [MENTION=5747397]Triple [-] [-] [-][/MENTION] [MENTION=7860020]Blackburn119[/MENTION]

Guys, I tested SmartPack and SmartPack-Lite with the latest as well as 20170809 LOS builds. I haven't encounter any serious issues yet as you guys reported in the case of unofficial RR builds. No random reboots (not even one). also see the freq stats.

Since my latest build is pretty stable on LOS and not on RR (and also considering the fact that my old builds are stable on RR), I'm seriously doubt about the update status of the unofficial RR build. I'm not talking about the build date. [MENTION=6018432]furkaan28[/MENTION] are you sure that the RR source is up-to-date with the LOS repo? Are you simply building using RR repo?

To confirm, you guys might test either latest LOS or another up-to-date ROM (probably crDroid or the newly released ViperOS)?
[Samsung Galaxy S 5 Unified Development] j1gga84:
I agree that even latest official RR is not up to date with latest LOS repo, I don't know if this is the case for the unofficial build of furkaan28 but if not that would explain the random reboots and unstable behaviour.

something else:

When I touch the screen I got the following error in the log:

QCOM PowerHAL (1007): Failed to acquire lock."

What could be the reason for that and is there any fix?

Is it kernel related?

I don't have this error on my galaxy tab S but it has an exynos processor..

EDIT:

the stock LOS kernel does not have this issue:

https://xdaforums.com/showpost.php?p=73435298&postcount=7800

regards
[Samsung Galaxy S 5 Unified Development] j1gga84:
I want to add that I also have issues with my camera now, but with SmartPack-Lite build from 02.08. :confused:

The display stays black after opening any camera app, also when I switch to video or front camera.

I have to reboot to get the camera working again.. Very strange, I did not have seen this issue before, maybe because I don't use the camera that much..

regards
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Thanks for reporting the issue though it is already known. I also faced that issue occasionally on Stock LOS (not sure abt RR) as well as both SmartPack kernels. See this post (a user reported that some camera apps worked). Still in a search for a solution. So far unsuccessful :crying:
[Samsung Galaxy S 5 Unified Development] culiacanazo:
Just a small thumbs up, camera still works, even though you can't see anything thru it. Both video and picture
[Samsung Galaxy S 5 Unified Development] furkaan28:
Lol
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Test builds...

Guys, it seems like the issue is fixed in kltekor.

Is someone willing to test in klte? If so, here I'm attaching test builds for klte and kltekor. Kindly let me know if the issues (especially Camera black screen) is solved or not... Since it is anykernel zip, you guys can flash this Kernel over any aosp nougat ROMs like LOS, RR, crDroid, ViperOS etc...

Waiting for your replies... and I'll push builds for other variants only after someone tested and confirmed that this build is fine...

Thanks in advance...

/* Download */

klte

kltekor
[Samsung Galaxy S 5 Unified Development] furkaan28:
Log for camera
[Samsung Galaxy S 5 Unified Development] Henrea4:
Hi. I have a Straighttalk variant of the S5 (SM-S902L) and I'm currently running the most recent klte build of RR and unfortunately I'm still experiencing black screen camera issues after flashing your patch.