yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] :
The screen delay/no wake up is happening on v19 oreo.

TLTR: not kernel related.

I'm using Havoc OS at the moment.

When I get a chance i'll try First running stock again, then the previous versions of smartpack to see if its there too.

Its hard to find a cause, because it doesn't happen every time, and seems to be more usual when an app is left open and I hit home. I left Catlog running and it happened, but there was nothing I could see for warnings or errors except a few location update failures. I noticed today when my alarm went off, I had a hard time getting the screen to wake. Unless theres more reports, I'd still think my screen being faulty is a reason.

I will update when I get back home in a few hours.

Edit: i have dirty flashed the rom and cleaned data for the kernel manager, I'll see if I can make it happen again. If it does, then your kernel has nothing to do with it. Will update with more.

Edit2: i setup an alarm with a snooze of 5mins to let run since that seemed like a good way to reproduce it. Its been running for an hour, it keeps waking up, I keep snoozing and shutting the screen off. I'm going to try the stock setup for a few more hours, then I'll try another kernel version and go through this again. I should have looked into more when it happened last time, but i got flash happy and wanted to try all these wonderful projects :)

Edit3: so a few hours later it happened twice in 10 mins. I left my phone next to me as I watched tv, waking it every so often. And twice it failed to wake by button and hand wave. So with this I am going with the device screen being the problem. Which was what I suspected to begin with. It has happened on multiple roms as well, so unless it is Lineage specific, I'd wager that a failing to wake screen is signs of a failing device. I will at some point again flash the stock rom and run the same tests just for my own interest.

So I just wanted to confirm my suspicion, and I think I've done that. I originally reported the waking issue in responding to another users' same issue earlier in the thread, I kinda figured my screen is on its last leg.

Thanks again friend, I will keep testing as long as this device holds up :)
[Samsung Galaxy S 5 Unified Development] jackson_c:
Hello Sunilpaulmathew. Any chance of adding minimal backlight in the Display and Led menu, as there is already maximum backlight? I use that option in an xposed module to avoid flickering problem, common on amoled screens like our S5. It's the only reason I have xposed installed.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
I do not think that none of these problems related to SmartPack. Either ROM or from some recent changes from stock kernel because the only difference from last two kernels are only that.

Can you share a link to the module (source code, xda page etc). I have to find the sysfs to implement such a feature, either in Kernel or App.
[Samsung Galaxy S 5 Unified Development] :
Updated last post, 3rd edit.

I agree with you, thanks again :)
[Samsung Galaxy S 5 Unified Development] jackson_c:
Of course, it's the popular GravityBox module. I tested the Marshmallow version in stock and Oreo in LineageOS and this setting worked well. The setting is in Display tweaks > Brightness settings. In my case, I set Minimum brightness level to 15, so my 0%-100% brightness bar becomes 15-255, avoiding the flickering. Thanks for your attention, and I hope Google translator helped me well. :p

https://repo.xposed.info/module/com.ceco.oreo.gravitybox
[Samsung Galaxy S 5 Unified Development] :
I haven't used xposed in some time (had trouble with safetynet, and played pogo), I was using screen filter back then. I think I will go see what version I need and try. I don't play pokey anymore so I'd give up safetynet if I have to.

Thanks for the tip :)
[Samsung Galaxy S 5 Unified Development] ToCatchATiger:
This is interesting because I have been experiencing a few screen wake problems also, they are thankfully not very frequent though. I have been trying to track down the cause and thought maybe it was something to do with the proximity sensor since it usually happens after the screen turns off during a voice call... but I now wonder if it has something to do with the screen hardware itself, as I replaced the screen myself with one from a 900V (my phone is originally a 900T) I have a dead 900A that I keep around in case I ever crack another screen, I wonder if swapping for that would make any difference at all?
[Samsung Galaxy S 5 Unified Development] :
I figure its a sign of things to come. I've had flickering issues for a few years now, and lately the not waking up thing started. I initially thought that my screen is near done, and I still think that. It would cost more to fix than what the device is worth, so meh let it die lol.

I have a spare device, my wifes, that died. the power button and usb port stopped functioning but the screen had always worked. I'll likely make a last ditch effort to swap them. I don't expect success as I have shacky hands lol. It could work, but I suppose it depends on if its the screen itself, or what is controlling it (as in mainboard or logic board). I'm a certified pc tech, but my knowledge of Android hardware is limited.

Ultimately I can see two things helping with flickering, one is raising brightness to a level that it doesn't occur which is easy to achieve already with a number of apps. And secondly, would be changing the screen timeout dimming phase to a shorter or preferably non existent value to make it shut off without the dim. Regardless of animation settings there is 4-5 seconds of dimming before the screen shuts off. This part is something I've yet to find any way to achieve and is a power control function I believe. ( https://developer.android.com/reference/android/os/PowerManager )

Not to derail this thread any further, I'm not sure if our developing friends could achieve the second option, and must be done via the OS. I've grown accustomed to to watching to light show before the screen shuts off. It does the same on maximum brightness, so that dim phase is just brutal. :)

I should add that my screen never flickers while in use as long as its brightness is above 20. Letting it turn off is where it happens. So that dim brightness value is just too low.
[Samsung Galaxy S 5 Unified Development] jackson_c:
You can try this app too. It don't work so well, need to run in background, but only need root access.

https://xdaforums.com/android/apps-games/app-brightness-tweak-t3339579
[Samsung Galaxy S 5 Unified Development] :
Trying this now, I like how it locks your brightness slider to not go below your set value. So you can still use the slider without triggering the flickers.

Thanks.
[Samsung Galaxy S 5 Unified Development] Tech0308:
There's also a chance that doze is the culprit. It happens on my marshmallow device when aggressive doze is enabled. On Nougat+ it's enabled a lot more quickly.
[Samsung Galaxy S 5 Unified Development] jackson_c:
Hi, maybe the quick toggle of performance tweak has a bug. I can only switch between balanced / performance modes. battery mode does not.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Are you sure? because it is working fine for me. Can you tell me exactly what happened in your case?
[Samsung Galaxy S 5 Unified Development] jackson_c:
I don't know how explain in details, so...

https://drive.google.com/file/d/1y0ix1_HQPQ7DKEa0SbNnVC6mbEBzD9cS/view

Actually, looks like it is not changing the profiles at all.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Ahh, you are confused, I guess. The performance tweaks only do some changes in the Kernel level (more details here) and nothing related to the battery profiles in the system (that is a totally different thing). In short, if you activate the "Battery", it will mainly (but not limited to) change

1. Max CPU Freq to 1497

2. Lazy plug profile to Lazy

3. Max brightness to 100

4. Activate adreno_idler & dynamic Fsync

5. Reduce input boost duration to 150 ms

Can you please check those things are changed? I hope it will :)
[Samsung Galaxy S 5 Unified Development] jackson_c:
Yes, it changed. But, actually, I was referring to the quick toggle button (it change the performance tweak, right?). The video is quick. The toggle is the bottom right. Maybe I'm more confused of what I thought. :silly: or Google Translator
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
SmartPack-Kernel Manager v4.8

Hi friends,

A new version of SmartPack-Kernel Manager (v4.8) is now available.

For detailed change-logs, plz visit here.

Simply open the app and then follow the new pop-up notification. For the fresh installation, manually download from here.

Please note: I made some efforts to update new Kernels within few clicks (SmartPack page). I hope it will be useful. Enjoy...
[Samsung Galaxy S 5 Unified Development] fubo73:
Hi [MENTION=7060205]sunilpaulmathew[/MENTION], a tech question.

If I have LOS + SP kernel + Magisk, when a new LOS nightly is available I should not apply through OTA, but I should download, reboot TWRP and flash in same order. LOS supports addon.d to backup and restore files to survive an OTA. Currently Magisk supports this system, but kernel should be applied before it.

Could the kernel survive an OTA with addon.d system? Or am I wrong?

Thanks in advance.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
There should be some way to retain Kernel during LOS update (either by an addon.d script or with the help of Magisk. However, I'm not fully sure about making such a script. Magisk has it's own survival mechanism to survive ROM updates so that it will (and modules, if any) be retained. However, installing Kernel before Magisk is not advised by many devs (I do not know the reason). The best way to retain the kernel in my advice is to (i) simply avoid OTA and flash ROM and Kernel manually or (ii) flash kernel separately after OTA update.
[Samsung Galaxy S 5 Unified Development] fubo73:
Regarding kernel and magisk flashing sequence, I remember that magisk (like supersu) needs to change something in kernel image to be started before image. If you flash a kernel after, magisk should not be mounted, so sequence should be: new_image -> kernel -> magisk.

Magisk modules are retained because they are in systemless space in magisk virtual disk image, so what should survive is magisk itself. It uses addon.d to backup and restore some files needed to be applied to either system or kernel, I believe.
[Samsung Galaxy S 5 Unified Development] Many40:
Hi,

If I am not mistaken Magisk modifies ramdisk (part of the kernel/boot image). From other side, a kernel like Boeffla (probably the other modern custom kernels as well) doesn't replace a ramdisk with its own (what might cause losing root) but takes it from the already installed stock kernel (in our case with ramdisk still patched by Magisk as Magisk survived LOS OTA update).

So, in my case (LOS 15.1 + Magisk 16.7 + unofficial Boeffla kernel):

1. After applying OTA -> root untouched, stock kernel replaced Boeffla

2. After installing Boeffla -> root still untouched, Boeffla replaced stock kernel.

Regards
[Samsung Galaxy S 5 Unified Development] fubo73:
So in your case: magisk survives LOS OTA by using addon.d and repatching LOS stock ramdisk after update. But kernel is not applied, so you have to reinstall Boeffla that picks up ramdisk from LOS stock magisk-patched ramdisk and uses on its own.

In this case the proper correct sequence is flash LOS->magisk->kernel, instead of the one I pointed out.

One interesting approach would be using [MENTION=4544860]osm0sis[/MENTION] script 999-customkernel.sh addon.d here. Before OTA, it would save boot.img in a backup folder, and after magisk survive script it would reapply (already magisk-ed) saved boot.img.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
More detailed answer:

That is how anykernel based kernel's works, including SmartPack & Boeflla. It will simply replace the kernel zImage and device tree blob (dtb), and did minimum changes in the ramdisk (or leave as such). In the case of SmartPack, it will

1) add a line of code into "init.rc" (for Spectrum support),

2) removed one line from the same file (disable mpdecission) and

3) add a number of supporting files to achieve Spectrum support.

None of these changes will NOT touch the changes made by Magisk inside Ramdisk, so you won't lose Root after a Kernel Update.

However, each LOS update will replace the entire magisk modified "boot.img" with Stock "boot.img" which is later patched again by magisk with the help of its survival script. So, you won't lose Root after OTA update, but definitely loose Custom Kernel.

Thanks for the link to the custom kernel script. Let me check and see how we can apply it in our case.
[Samsung Galaxy S 5 Unified Development] osm0sis:
Better off using my FlashAfterUpdate addon.d and putting the kernel zip in /sdcard/FlashAfterUpdate, that way you keep any changes the OTA made to the boot.img. :good:
[Samsung Galaxy S 5 Unified Development] HippoMan:
Flashing order when Magisk is involved.

Just for clarity, if I'm doing a clean flash of a new ROM which also involves Magisk, and if I want to flash this kernel, what is the recommended flashing order (after a factory reset)? Is it this? ...

1. Flash the ROM

2. Flash the gapps

3. Flash Magisk

4. Flash this kernel

Or should I switch #3 and #4? ... or is there maybe even a different recommended flashing order?

Thank you in advance.

.​
[Samsung Galaxy S 5 Unified Development] fubo73:
This sequence is ok because Smartpack kernel has capability to inherit ramdisk from stock kernel that is the part modified by magisk to work. Not all kernels are ok with it.
[Samsung Galaxy S 5 Unified Development] HippoMan:
Thank you. I'm glad this sequence is OK. But if the kernel couldn't inherit ramdisk for some reason, what would then be the preferred sequence?

.​
[Samsung Galaxy S 5 Unified Development] CStadler:
Then it would be

1. ROM

2. Kernel

3. Magisk

Gapps should be flashed anywhere after the ROM, but preferably before the first boot.

Hope it makes sense

(Just shout if you want a clearer explanation)
[Samsung Galaxy S 5 Unified Development] HippoMan:
Now it's all clear, and I don't have any more to shout about. :)

Thank you very much.

.​
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
[MENTION=5034846]jackson_c[/MENTION]

for you :p
[Samsung Galaxy S 5 Unified Development] jackson_c:
Haha great! For me and for many users with the problem.

Already released? Can't wait to test! xD
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Kernel Manager (v4.9) is already released. However, to get that feature accessible, kernel supports is required, which will be available from the next version onwards.
[Samsung Galaxy S 5 Unified Development] silva_dump:
Sorry to say this but after installing v19 kernal i faced lot of lag in my rom

Can anyone suggest me good tweaks to use with smartkernal manager for smoother performance with a very good battery life

I don't need to play games or anything

But i don't like lagging

I just needed the smoother experience i had with stock kernal before falshing this kernal but with good battery life

Thanks :)
[Samsung Galaxy S 5 Unified Development] Tech0308:
Set one of the profiles available in the smartpack kernel
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
SmartPack-Kernel beta-v20

Hi all,

After a while, a new update (beta-v20) for Oreo ROMs are now available.

Please note:

This version includes control over minimum backlight of your display so that you can avoid the screen become too dark in certain conditions. The feature can be accessible in SmartPack-Kernel Manager (latest version) or from a root shell (or adb) by sending echo x > /sys/module/mdss_fb/parameters/backlight_min (replace x with desired value, range: 0 - 255).​

As usual, the download links for all the supported variants along with change-logs can be found at the below links as well as in SmartpPack-Kernel Manage. Enjoy...

https://sunilpaulmathew.github.io/sgs5/
[Samsung Galaxy S 5 Unified Development] StefanV3:
Hi,

could you add OC values for GPU like Unofficial Boeffla Venom Kernel from The_Skater_87 has?

Thanks

StefanV3

Gesendet von meinem SM-G900F mit Tapatalk
[Samsung Galaxy S 5 Unified Development] jackson_c:
The new brightness function is working wonderfully well. I already uninstalled Xposed. Thank you very much for your response. :D
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Sorry, I think it is dangerous and useless for most of the people. So, NO

;)
[Samsung Galaxy S 5 Unified Development] Quimicax:
I Have A Problem When Installed The ROM Works Super Fluid When I Install The Kernel Goes Slow The Interfaces

Havon Rom + SmarkPack V20
[Samsung Galaxy S 5 Unified Development] Ranniel:
+1
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Install SmartPack-Kernel Manager and switch to Performance profile, or manually increase Input Boost Duration & Frequency (CPU page). It will hopefully make the things more smooth.
[Samsung Galaxy S 5 Unified Development] Quimicax:
Thx :highfive: & Try With Clean Install, Other Question Dev... Adreno Drivers They Make A Difference?
[Samsung Galaxy S 5 Unified Development] flyingsaucer75:
[MENTION=7060205]sunilpaulmathew[/MENTION]

Samsung s5 klteduos stock MM 6.0.1, twrp 3.2.0 with magisk root v17.1, USB otg not working..

I've tried also SmartPack-Kernel-TW-klteduos-final-v11-20180811.zip USB otg not working.. very strange.

Sorry to bother you.

While latest kernel for lineage and Oreo has no issue.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
You don't need any script for that. Just flash another kernel... like stock kernel...:p
[Samsung Galaxy S 5 Unified Development] culiacanazo:
Just for the possible future reference, do you require yours to be flashed on top of stock kernel, like others do?

If what he meant was a cleaner to clean yours...
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Thanks for clarification. and sorry for my funny answer. :D

Since this kernel uses Anykernel concept, and I'm not interested in touching ramdisk, flashing this kernel only replaces the zImage from your present boot.img. That is your ramdisk and other stuffs remains intact. So, in most cases, you can flash this kernel over any ROM/Kernel without any pre-cleaning. However, if your previous kernel has any app/profiles/settings installed, that will also remains. You might need to remove such stuffs manually.

Btw, thanks to both of you for your interest in my kernel...
[Samsung Galaxy S 5 Unified Development] culiacanazo:
Thank you for providing it! :)
[Samsung Galaxy S 5 Unified Development] raisey:
no problem buddy :highfive:
[Samsung Galaxy S 5 Unified Development] SuperSandro2000:
Boeffla has a kernel cleaner script. There should be a zip for the cleaner on his website http://Boeffla.de
[Samsung Galaxy S 5 Unified Development] culiacanazo:
This tea, tho
[Samsung Galaxy S 5 Unified Development] SuperSandro2000:
Edited the post to better reflect what I wanted to say. He has a cleaner script to clean kernel settings etc. It was not my intention to advert his kernel. Thanks for the heads up
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Never mind guys... I really don't care if you guys discuss abt Boeffla kernel since I'm also a big fan of Lord Boeffla (and I'm sure that most of the devs including me shamelessly copied a lot of codes from his repos:p).

Btw, as I understand, his cleaner script is basically aimed to remove scripts related with synapse and ktweaks since he recommended to use his own app for kernel tweaking. I don't have any issue if you guys use synapse or ktweak or any app to tweak my kernel if it works fine...:)
[Samsung Galaxy S 5 Unified Development] HatchetEgg:
[MENTION=7060205]sunilpaulmathew[/MENTION]

I noticed that the Bluetooth stopped functioning with the latest kernel, so I have had to revert back. Im currently using a g900f with cosmicos
[Samsung Galaxy S 5 Unified Development] e-bert:
Hi. Has this kernel support for sdcardfs? It would be nice, given this:

https://xdaforums.com/apps/magisk/module-enable-sdcardfs-t3603375
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Not sure abt cosmic os, I personally don't have any issue in LOS latest build (kltekor). Btw, plz wait a bit. I'll upload new builds later today. Plz check and report (with logs) if the issue persists. Thanks in advance.

Thanks for the good suggestion. I'll try to include this in future builds. Btw, this is a magisk module and you guys can add this over my kernel anytime (if u are using magisk).
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
New builds...

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

/* [COLOR="blue"][B]Downloads[/B][/COLOR] */
[INDENT][URL="https://www.androidfilehost.com/?w=files&flid=177749"]kltekor[/URL]
[URL="https://www.androidfilehost.com/?w=files&flid=177748"]klte[/URL]
[URL="https://www.androidfilehost.com/?w=files&flid=177753"]klteduos[/URL]
[URL="https://www.androidfilehost.com/?w=files&flid=177757"]kltedv[/URL]
[URL="https://www.androidfilehost.com/?w=files&flid=177756"]kltespr[/URL][/INDENT]
[Samsung Galaxy S 5 Unified Development] XdaGiedrius:
Hello. Maximum and minimum CPU not work.[emoji29]

https://drive.google.com/file/d/0B1MG7ehNnOfjV2wyWmJQWXRYc00/view

Išsiųsta naudojantis SM-G900F Tapatalk 4 Lt
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
I don't have that issue in my kltekor (and I'm using Kernel auditor mod). Btw, can you test with a different cpu freq gov like nightmare or lion-heart. Someone previously reported similar issues in kltevzw and the issue was made by alucard gov.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
New builds are uploaded...

Changes includes the addition of new cpu hotplugs (Alucard and Zen decision) as well as the recent LOS commits. Download links are here...

/* Downloads */

Please make sure to download the latest build

[URL="https://www.androidfilehost.com/?w=files&flid=177749"]kltekor[/URL]
[URL="https://www.androidfilehost.com/?w=files&flid=177748"]klte[/URL]
[URL="https://www.androidfilehost.com/?w=files&flid=177753"]klteduos[/URL]
[URL="https://www.androidfilehost.com/?w=files&flid=177757"]kltedv[/URL]
[URL="https://www.androidfilehost.com/?w=files&flid=177756"]kltespr[/URL]
[Samsung Galaxy S 5 Unified Development] Vlin.Wang:
Hello, Can you build it for kltekdi variants,I can help you to make test.:rolleyes:
[Samsung Galaxy S 5 Unified Development] culiacanazo:
Señor, does your kernel get along with multirom, or does it even matter?

In Mexico, where I'm from and you're welcome to visit, they say (I'll try to be faithful to the real meaning when translating):

"It's more desirable to come across as stupid for a few minutes" (by asking a potentially dumb question), "than being one for the ages..." (by not knowing due to fear of asking).

Thank you!
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Okay... I'll build for kltekdi as soon as I'll get free time... Plz wait a bit...

Edit: My test building wasn't successful. It might take more time to solve all the issues and provide a test build for you (or even may not work... who knows :().

Thanks for the nice words. and I really don't know abt multirom. But, if your stock kernel is compatible, this kernel should also work...
[Samsung Galaxy S 5 Unified Development] culiacanazo:
Ok, thanks for the clear answer.

Regarding the proverb, let me rephrase it so we have zero misunderstandings.

My prior question could very well have been one that, had it been overly obvious, would have made me look stupid for not knowing such stuff already. But, since i don't wanna be a fool forever, I rather ask (and hopefully, learn)!

:highfive:
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Sorry friends, that project (TW Kernel) is already dead (and added an EOL tag to the title as well as on OP long back). So, please do not expect any further updates. Thanks for the understanding...