yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ianmacd:
First off, disable all of those modules and try again. Put Magisk in core-only mode if you wish. Then, regardless of whether or not this fixes your problem, consider not re-enabling some of your modules. You really don't need the so-called RAM Management Fixes, because nothing is broken. Doze for GMS and Sysconfig Patcher aren't needed, either. Leave power management to the OS, which will do a much better job on an advanced machine like the Tab S4 than these hacks. I'm also doubtful about the usefulness of the Magic Charge Switch. Don't overmanage your system: You can introduce more issues than you fix.

As for commands not being found in the terminal, there's really nothing the kernel can do to alter your $PATH in the shell. Kernel space and userland are separate worlds, with no bridge between them in this case. For whatever reason, the command you are typing is not found in any of the directories defined by your $PATH variable, but it has nothing to do with the kernel.

Lastly, upgrade the kernel to the newly released 0.99.7. It's possible that some of your issues stem from a subtle mismatch between the firmware and the kernel you're running.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] N1NJATH3ORY:
Ok doc, i have updated to latest Kernel v0.99.7 (2018-10-30) only thing i was using Magic Charge Switch for. i had it set to don't charge over 90% lock it there. i Just launched terminal, i Su first, then inputted MCS HELP it worked flawlessly command came back :D your update has fixed it :D

i'll not install what you advise, will report back in a few days. Thanks
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ianmacd:
I think disabling the other modules is probably what did it for you, because at least one other T835 user reported the previous kernel working without issue on his device. That said, it's always good to have a properly matched kernel and firmware installation. The only reason we haven't had that until today is that Samsung hadn't released up-to-date kernel sources until yesterday evening.

Whatever fixed it, I'm happy that it's fixed. Enjoy your device!
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] dr460nf1r3:
Concerning magic charge switch, terminal enter su, then for example 90 88 works for me.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] N1NJATH3ORY:
Just a update it's running beautifully, I have faced no issues it's smooth and fast :D The previous kernel was driving me mad random reboots wifi connected but internet not available and 40 meg file would take over 2 mins to download when I am on fiber plus so many other issues!

But since installing this update everything is working as it should.. 1% battery gets used fo 10+ hours standby.. All I can say I'm super happy:D
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] N1NJATH3ORY:
Today i switched off the Tab S4 around 7am, then turned it back on 16:00 ish it booted up. But then locked up then went into the dim SAMSUNG logo.

it did it 3 times, before i managed to get it boot up but as i would enter pin to unlock, it would lock up..

i have also noticed this KERNAL does not like any type of modification apps. For example little tweaks like customizing battery icon or showing data usage top right corner. it simply does not want to boot it locks up

At the moment the only apps i have got installed is MTweaks, and EX Kernel Manager but the thing is they are only installed i have made no changes to them. They are on stock setting both apps oh also XPrivacy Installer is installed haven’t made any changes to apps or to privacy settings..

I can’t think of anything else, maybe Good Lock 2018 could be causing the issue? As I have customized the drop down bar, and other little stuff.

Is there any way I can get you a log? So you can take a look? Thanks
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] dr460nf1r3:
Generally speaking its not good to Install 2 different kernel managers since the settings may interfer
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] N1NJATH3ORY:
i see thanks man I’ll uninstall one of them.. Thanks
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ianmacd:
This sounds like an incompatible Magisk or Xposed module again. I probably reboot my T830 5 to 10 times a day to test new kernels, and I literally never experience a lock-up like this when I log in.

That's not something the kernel cares about or is even capable of caring about. SystemUI is typically the component that can have a bad reaction to such mods, but it all depends on the mechanism employed to achieve the goal.

FWIW, I have GravityBox showing network traffic on the status bar via Xposed, and that works like a charm.

I also have both of these on mine. Just having them installed is not an issue.

I assume you mean XPrivacy Lua, not the original. I have had problems with the new Lua version on another device, even after just installing it without performing any configuration, so I abandoned it. I haven't tried it on this device, but I would treat it with caution.

It's possible. I haven't tried Good Lock on this device. There could be some subtle incompatibility with SystemUI or some other system component on this device.

Are you also theming the device using Swift, Substratum or a Samsung theme? That's something else to watch out for: mixing and matching theme components from multiple sources. That's a recipe for conflicts.

In summary, I'm confident none of your issues are kernel-related. This kernel doesn't have a lot of users, but no-one else has reported the behaviour you're seeing. The intermittent nature of your problems also points in the direction of a user configuration issue. Revisit your list of Magisk and Xposed modules. The more invasive the module, the more likely it is to cause a problem, particularly if it wasn't specifically developed for a Samsung device.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ianmacd:
Version 0.99.8 released.

This version incorporates a lot of fixes, not just the considerable number from upstream Linux 4.4..163, but also more than 100 from the android-4.4 and android-4.4-o branches of AOSP.

In addition, I found that Samsung had left enabled many debugging and tracing features that really have no place in a release kernel. These features are present and active even in the stock kernel that Samsung supplies pre-installed and in its firmware releases. These unnecessary features have now been disabled, resulting in a smaller kernel with possibly marginally better performance.

All users are encouraged to upgrade to 0.99.8.

I hope this will be the final version of Modesty built for the ARH5 firmware. A few days ago, Samsung granted my request to release the ARJ3 kernel source code, and I already have it merged and waiting to go.

The fly in the ointment with the ARJ3 firmware is that it comes with an updated bootloader, denoted by U2 in the firmware's file name. Users have reported that the ARJ3 upgrade relocks the tablet's bootloader and, in at least some cases, triggers RMM protection, which removes the OEM Unlock option from the Developer Options menu, thereby making it impossible to re-unlock the bootloader. Bye bye root and the ability to flash a custom recovery or TWRP.

Needless to say, before I can continue kernel development with the newly released source code, I need to figure out how to get my own T830 safely up and running on the ARJ3 firmware without sacrificing root. To this end, I have created a modified system image with RMM protection disabled, but before I apply it, I'm waiting to hear from others whether TWRP will still run under the new bootloader. It seems no-one has tried this yet.

Change log

v0.99.8 (2018-11-10)

Updated to Linux 4.4.163.

More than 100 fixes applied from upstream AOSP android-4.4 and android 4.4-o branches.

Lots of tracing and debug logging disabled:

CONFIG_IPC_LOGGING (debug logging for IPC drivers)

CONFIG_QCOM_RTB (register tracing)

CONFIG_TRACER_PKT (for tracing IPC protocols)

CONFIG_FTRACE (kernel tracing infrastructure)

CONFIG_CPU_FREQ_SWITCH_PROFILER (CPU frequency switch profiler)

CONFIG_TRACING_EVENTS_GPIO (traces GPIO subsystem)

Fixes to allow kernel to build when above logging and tracing options are disabled.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ianmacd:
Version 0.99.9 released.

I finally plucked up the courage yesterday to upgrade my T830 to the ARJ3 firmware. In doing this piecemeal in an effort to avoid potential problems with the U2 bootloader (namely the triggering of RMM prenormal state and the consequent loss of OEM Unlock), I probably ended up causing myself a much bigger headache than I would have incurred with a simple straightforward flash. You live and learn.

Anyway, I got there in the end and my Tab S4 is now happily purring away on ARJ3, including the bootloader, and with OEM Unlock still visible and enabled.

So, this release merges the recently released Samsung ARJ3 kernel source code, compiling a kernel to match the latest firmware. Finally, Modesty's base is in sync with the latest firmware for our device.

All users who have upgraded their machine to ARJ3 firmware are encouraged to upgrade.

Change log

Rebased on ARJ3 kernel source code.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] N1NJATH3ORY:
That’s the thing dude i don’t have any Xposed mods installed, all i got in Magisk is YouTube Vanced, YouTube Vanced black theme, Xposed framework, Xposed framework (SDK) 27, and magic charging switch.

Xposed all i had installed is disable convert from sms to mms, i have updated to the v0.99.9 (2018-11-13)This coming thursday i'll find out when I switch it off for 7am and turn it back on 4pm, if it locks up or dim Samsung logo flashing away pops up..

Also on mine when I would turn it on 4 pm I would not input my pin, as I was doing other so few mins for pass before I got a chance to input my pin. But It would just boot to the dim Samsung logo it did about 7 odd times.

Also dude I don’t have any custom apps like GravityBox, all I got for customizing is good lock 2018 and one hand operation by Samsung. That’s it, can you please try these apps you can get them from the Galaxy App store to see if they interfere with your Tab S4? Thanks

No dude i have not got any of these installed (Swift, Substratum or a Samsung theme)

Also i have deleted XPrivacy Lua, i'm not sure if it was the Lua one as i updated to the v0.99.9 (2018-11-13) Kernel i never got round to fully instaling it's gone anyway that wont be a issue from now on.. Thanks
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ianmacd:
If you really have 2 Xposed frameworks installed, remove one of them. And disable that Magic Charging Switch, too. See whether you still experience the lock-ups then.

In the TWRP thread, I saw that you asked how to update your firmware to ARJ3. If you haven't done that yet, why are you already running the ARJ3 Modesty kernel? That's not a supported configuration and may add to your problems.

That sounds like a soft SystemUI restart.

Are you sure you're running full stock firmware? Please post the versions of your bootloader, PDA/AP, CSC and baseband.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] dr460nf1r3:
Would you be so kind to provide me the boot img of your kernel for T835? Id like to include it in my rom if you dont mind but dont know how to extract the clean bootimg from those bsdiff files. If you could tell me how id also do it by myself.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] z31k:
Just to clarify, you are encouraging to update to ARJ3 first. And then flash TWRP and then the kernel flash?
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ianmacd:
I'm not necessarily encouraging people to do the ARJ3 firmware upgrade itself, because some users have had their bootloader relocked and lost root as a result. This is a very clear case of YMMV.

I am, however, encouraging anyone already running ARJ3 to also upgrade their kernel to version 0.99.9, since an earlier version will likely have problems with the new firmware. With 0.99.8, for example, I can no longer log onto my ARJ3 machine after rebooting (which is odd, because it did work the very first time after upgrading: possibly some post-installation step was performed on first boot).
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] z31k:
Thank you for the response. I'm still on the fence. I want to root but I'm afraid to lose anything. I think I'll just root my ARG8 firmware and then just flash updated kernels as they are released... Can anyone confirm this method would be the best course of action?
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ianmacd:
At the very least, you should be able to safely move to ARH* firmware. My device came with ARGH and there was an OTA available for it as soon as I installed the device.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] N1NJATH3ORY:
XDA The message you have entered is too short. Please lengthen your message to at least 2 characters??? <---- I keep getting this mgs when trying to quote you [MENTION=7187684]ianmacd[/MENTION] ? XDA is crashing dude..
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ianmacd:
Trust me: This has nothing to do with the kernel.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] N1NJATH3ORY:
Yep i believe you something is playing up on XDA!
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ashyx:
It only says that if you post less than 3 characters. Quotes don't count.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] N1NJATH3ORY:
Yes but i typed out a few paragraphs answering ianmacd and i still was getting that msg..

Ahh I think where I was going wrong, I was typing within ianmacd post not underneath it,

And I think XDA would not recognize, that I have entered a response. Thanks
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ianmacd:
Version 0.99.10 released.

The 0.99.10 release brings the inclusion of the KCAL advanced colour/gamma control driver. Amongst other things, [MENTION=631273]Chainfire[/MENTION]'s CF.lumen can make good use of this to efficiently apply a blue light filter to your screen. Android Oreo has a built-in blue light filter, of course, but in my opinion it leaves much to be desired. There is no gradual transition to night mode and when active, colours appear oversaturated. If, like me, you had abandoned CF.lumen on Oreo, you may wish to revisit that decision.

The number of tracing and logging features has also been further reduced in this release. Such features really have no place outside an internal engineering build and cause the kernel's footprint to be unnecessarily large, both on disk and when loaded into memory. Pretty much only logging features I have left enabled are those that are actually useful, plus those whose removal causes recurring messages to be emitted to the system log.

Disabling some of these logging features caused a spurious and rather grave-sounding Android System warning to appear on boot, the solution to which was to have the kernel falsely report a stock config to user land when queried via /proc/config.gz. Please be aware, therefore, that this is no longer a reliable mechanism. GitHub is the definitive source of the configuration actually used to build the kernel.

Finally, Linux 4.4.164 appeared as I was preparing 0.99.10 for release, so this has also been merged.

All users on ARJ3 firmware are encouraged to upgrade.

Here's a comparison of the memory used by Modesty 0.99.10 vs. 0.99.9 (and 0.99.9 was already much improved over the stock kernel):

0.99.9: Memory: 3169928K/3856128K available (19582K kernel code, 2183K rwdata, 10888K rodata, 7424K init, 8001K bss, 501880K reserved, 184320K cma-reserved)
0.99.10: Memory: 3172276K/3856128K available (19390K kernel code, 2151K rwdata, 9740K rodata, 5952K init, 7669K bss, 499532K reserved, 184320K cma-reserved)

Change log

Updated to Linux 4.4.164.

Added KCAL advanced colour/gamma control driver. (Configure with MTweaks or EX Kernel Manager.)

Lots of tracing and debug logging disabled, further reducing kernel size.

CONFIG_DISPLAY_USE_INFO

CONFIG_SEC_DISPLAYPORT_LOGGER

CONFIG_FB_MSM_MDSS_XLOG_DEBUG

CONFIG_SEC_FILE_LEAK_DEBUG

CONFIG_SEC_DEBUG_USER

CONFIG_SEC_DEBUG_SUMMARY

CONFIG_SCSI_UFSHCD_CMD_LOGGING

CONFIG_MSM_SMEM_LOGGING

CONFIG_PROFILING

CONFIG_DEBUG_INFO

CONFIG_SCHED_DEBUG

CONFIG_SEC_PM_DEBUG

CONFIG_CORESIGHT

Built as monolithic kernel (i.e. without CONFIG_MODULES).

Built as relocatable code (CONFIG_RELOCATABLE_KERNEL).

Assembler symbols stripped (CONFIG_STRIP_ASM_SYMS set).

Embedded kernel config (reported via /proc/config.gz) now falsely reports stock settings to allow disabling of superfluous kernel features that otherwise cause grave Android System warning on boot.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] vvqboy:
T835N( For Korea) or T835C ( For China), can use this?
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ianmacd:
I don't know. Back up your existing boot partition and give it a try.

There's a chance the installer reject the device, depending on how strictly I'm detecting the model. From memory, though, I think I'm doing it loosely enough that it will work.

If it flashes, you'll soon find out whether the kernel works and to which extent. I wouldn't be surprised if these models at least differed in their DTBs, if nothing else. And the Samsung open source site has a separate download for what looks like a Chinese model.

So, it's untested. Be sure to report back if you give it a try.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ianmacd:
A fix for: "E propClient: PropClient failed to load"

If, like me, you are irritated by your Tab S4's system log being constantly hammered with messages similar to this one:

11-19 19:35:29.600 12835 12835 E propClient: PropClient failed to load

you may me interested in this Magisk module that offers a quick and easy way to silence them. The module is available via the official Magisk Module Repo, so it can be directly installed from Magisk Manager on your device.

Note that the messages in question are not caused by running a custom kernel. They also occur on a fully stock device. I'm simply posting about the problem here, because people with a rooted Tab S4 are in a position to circumvent these messages.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] dr460nf1r3:
Saw this one in the download section just a few hours ago thanks for doing so much for our tabs ?
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ianmacd:
Version 0.99.11 released.

In this release, [MENTION=4684315]flar2[/MENTION]'s sound control driver has been adapted for the WCD9341 DAC and added to the kernel. This offers headphone and microphone gain via the usual avenues of MTweaks or EX Kernel

Manager. Do note, however, that the latest versions of both apps currently use a hard-coded range of values that is too restrictive for this DAC: -40 to +20 dB. This should be -84 dB to +40 dB. So, if you want to configure values outside the restricted range, you will need to do so manually for the time being. The relevant sysfs entries can be found at

/sys/kernel/sound_control/{micro,head}phone_gain.

I have contacted the author of MTweaks and a fix is in the works for that app.

Also bear in mind that this driver will be overridden by ViPER4Android (and possibly other mods) if installed and enabled.

The KCAL driver has been optimised. It is now smaller and perhaps microscopically more efficient.

The latest Linux kernel has also been merged into this release.

Change log

Updated to Linux 4.4.165.

KCAL advanced colour/gamma control driver optimisation.

Added [MENTION=4684315]flar2[/MENTION]'s sound control driver for controlling headphone and microphone gain. (Configure with MTweaks or EX Kernel Manager).
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ianmacd:
Version 0.99.12 released.

Change log

Updated to Linux 4.4.166.

Realtek USB Ethernet driver upgraded from v2.08.0 to v2.10.00.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] MrPhilo:
I can see your first post about overclocking, but just curious would this ever be implemented?
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ianmacd:
It's certainly possible. I'm not sure the demand is there, though. This kernel doesn't have many users and it's not a feature I'm inclined to implement for myself.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] MrPhilo:
No problem. Just annoyed with samsung using last gen, so wanted to squeeze just a bit more performance out of it if I could
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ianmacd:
It's relatively easy for Samsung to throw together a device like this. It's basically an oversized Adreno S8, so they can reuse all of their existing code.

Of course, that means that pre-existing patches aren't too much work to shoehorn onto this device, either, so there's also an upside.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] MrPhilo:
Understandable, I know this ain't relevant but the kernel, how is the RAM management? Only asking as when I had an S8 plus it was terrible and i can't see how Samsung would improve it. Does the kernel manage ram better?
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ianmacd:
I'd first have to know what you consider wrong with memory management on the S8. I never had any issues with that device and haven't had any with this device, either.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] MrPhilo:
Coming from OnePlus, I've always had apps in memory a lot of the time. But with Samsung they don't keep it in memory as much, like maybe 6-8 apps depending on the size of the app, with my 6T now I'm able to keep more than 16 on average. I always like going into app instantly without refreshing. That's one reason why I got rid of my Pixel XL2 as well.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] dr460nf1r3:
Install ram fixes via magisk
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] Peter KIKI:
Hi i am a developer from Samsung s8（835），G9550，may i request you for some guide of modifying the kernel ，i have my own rom and kernel

Here is my form：

https://xdaforums.com/galaxy-s8/sam...g9550-g9500-phoenixo9-crf2-everytime-t3819774

at last my i have your contact please for work to together to improve our 835 version of Samsung devices
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ianmacd:
Version 0.99.13 released.

Time to scratch that OCD itch.

Change log

Updated to Linux 4.4.167.

Merged selected BACKPORT and UPSTREAM commits from android-4.4 kernel branch.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] geargeek:
I would like to be another tester/user of your Modesty Kernel...

From reading the TWRP thread , I know that you were instrumental in getting TWRP up and running for the Tab S4.

I just bought the Tab S4 (T830). It came with the full ARJ3 Firmware and Bootloader (M1AJQ.T830XXU2ARJ3) XAR, October 1 2018 Security patch, and Oreo 8.1.0. I enabled Developer Options and OEM Unlock is present and available. I have read the entire [RECOVERY][ROOT]TWRP 3.2.3-1 Galaxy Tab S4 - T830/T835 thread on installing TWRP and rooting this device. The second step in this thread involves flashing a custom patched kernel (T830XXU1ARH8_dmverity_patched_boot_permissive) via ODIN in order to disable dm-verity. My question is, since the Modesty kernel is based on ARJ3 would it be better to flash it instead of a kernel based on ARH8? Also, does the Modesty kernel disable dm-verity?

What I'm hoping for is that I can:

1. Flash the required TWRP via ODIN (force reboot to Recovery)

2. Flash the TabS4_oreo_forced_encryption_disabler (in order to have full functionality in TWRP)

3. FORMAT Data (reboot to recovery)

4. Flash Magisk v18

5. Flash Modesty Kernel

Any assistance/info you can provide will be greatly appreciated.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] ianmacd:
If you reverse steps 4 and 5, you'll be fine. Otherwise, you'll blow away the Magisk-patched kernel you just created. dm-verity will also be taken care of by the above sequence.

There's no need to flash a separate disabler.
[Samsung Galaxy Tab S4 ROMs, Kernels, Recoveries, &] EmRav:
Any chance of a version with a permissive selinux kernel? Thanks for your hard work!