yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] WhoIsJohnGalt1979:
Don't wish to reply out of turn, but i will take the risk, hehe, I have been using APGK since day 1 of release, just use it default, I use exkm only to enable swipe to wake. I have abused this kernel across all forms of usage. I use dev base which is 100% stock, I don't debloat any app or system app. With default apgk, sync on, 2 sims on 100% lte (no wireless) auto brightness on, AOD on, wqhd+, no black theme, no greenify, you can easily get 5:30 hrs SOT in 24 hours run time with 45 minutes of Real Racing 3. I use around 10 social networking apps, just turn background activity off and turn off background activity of Android system. Also put all apps except the messaging apps under always sleep in device maintenance. Trust you me the user experience out of this kernel is the best.

Some stats that you can check to see if your Rom setup is consistent - the idle drain with AOD on with auto brightness is 1% per hour with mobile data on...and the active battery spend is around 3% an hour from 100 to 5%.

Regards,

Samit
[Samsung Galaxy S9 & S9+ Cross Device Development] iampatricktan:
I really appreciate your reply bro, btw I'm using Soldier's ROM, stock but it has few tweaks, also updated regularly.
[Samsung Galaxy S9 & S9+ Cross Device Development] WhoIsJohnGalt1979:
Sure the extended drawl was intended to assure you that irrespective of your Rom setup you would get the best out of box experience using the stock settings of the kernel hehe..cheers
[Samsung Galaxy S9 & S9+ Cross Device Development] iampatricktan:
So you mean i don't need to change anything from Ex Kernel Manger whe using APGK kernel while on Soldier's rom?
[Samsung Galaxy S9 & S9+ Cross Device Development] WhoIsJohnGalt1979:
That is correct my friend, flash and enjoy the kernel.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
The only things I use the EX app for are enabling sweep-to-wake and double-tap-to-wake.

I don't adjust any timings. Unless you have a very unusual workload, the default kernel settings are fine.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.25 released.

Change log

Updated to upstream Linux 4.9.132.

Minor changes to custom LED fader timings implementation.

Updated WireGuard to v0.0.20181007.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.26 released.

When APGK manages to drop to single-line change logs (as is the case here), it will be approaching readiness for a v1.0 release. It would have been there already, but a couple of tiny features were recently added (Magisk chaining and user-defined LED fader timings) and these needed to pan out into their final form.

I'm loath to add anything new at this point, and wouldn't really know what to add, anyway. APGK has always had a fairly conservative remit, and regular downstreaming of the Linux kernel and updates to WireGuard ensure as much volatility as I care to contend with. The motto was, is and will continue to be Stability above all else.

Change log

Updated to upstream Linux 4.9.133.
[Samsung Galaxy S9 & S9+ Cross Device Development] iampatricktan:
Thanks bro
[Samsung Galaxy S9 & S9+ Cross Device Development] Sora94:
Thanks again for your great work, it's always a bliss to read your changelogs and thought process on what's actually changed, I will try the overclocked variant, though once BRJ3 sources are out as it seems there are some camera changes on stock kernel which cause some minor problems.
[Samsung Galaxy S9 & S9+ Cross Device Development] Eamo5:
Great to see you've announced the overclocking and underclocking options! Congratulations and thanks for all your hard work yet again Ian
[Samsung Galaxy S9 & S9+ Cross Device Development] aedificavit:
Just tested 0.99.27 in interactive mode with underclock and no Magisk (I installed soldier's Magisk right after kernel) and my G960F didn't boot! blocked at S9 first logo (Samsung blink logo didn't appear).

Interactive with standard mode worked fine.

Any clue?

Thx for your great work!
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Bah! A one byte typo in the installer is the cause of this problem. I will fix it and upload a new archive.

In the meantime, you can run the following script on your phone, either in Android or TWRP, passing the path to the APGK ZIP file as a parameter. It will patch your ZIP file to fix the problem. Alternatively, you can run it on any device running Linux.

#!/bin/sh

zipfile=$1
zipdir=${zipfile%/*}
zipfile=${zipfile##*/}
bindir=META-INF/com/google/android
binary=update-binary

[ ! -f /tmp/$zipfile ] && cp $zipdir/$zipfile /tmp

mkdir -p /tmp/$bindir
cd /tmp
unzip -p $zipfile $bindir/$binary | sed -e '220s/g965/g960/' > /tmp/$bindir/$binary
zip -f $zipfile $bindir/$binary
cp $zipfile $zipdir/$zipfile
rm -rf /tmp/META-INF
rm /tmp/$zipfile

Paste that into a file called, for example, fix_apgk, make it executable and run it on the APGK file. For example:

# chmod 755 fix_apgk
# ./fix_apgk <path to the ZIP file>/APGK-0.99.27-1.zip

You can verify that the patch was applied correctly as follows:

# unzip -p <path to the ZIP file>/APGK-0.99.27-1.zip META-INF/com/google/android/update-binary | sed -ne 220p

g960_img=/tmp/boot-$kname-$lversion-$kversion-$build-g960.img # <--- Output should match this!

I'm attaching the script to this posting for your convenience. Download it to your phone, make it executable and run it as described above. Note that I have to give the file a .txt extension to work around XDA's daft restrictions on attachments.

UPDATE:

I have uploaded a fixed archive of v0.99.27. Anyone who has a G960 device and wishes to use either the underclocking or overclocking kernel variants should download the fixed archive. Anyone else needn't bother, as the original archive will work for other permutations.

[MENTION=4268804]aedificavit[/MENTION], can you please verify that this fixes your problem?
[Samsung Galaxy S9 & S9+ Cross Device Development] aedificavit:
Confirmed: Installed with fixed file it works now.

Thx a lot!
[Samsung Galaxy S9 & S9+ Cross Device Development] massaquah:
Am I correct that the current version won't work with Soldier 9.0 due to firmware changes in BRJ3?
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
0.99.27 will cause problems on any device running BRJ3.

0.99.28 will fix this. I am currently testing a build of it on my own BRJ3 device.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.28 released.

This release brings the kernel into line with Samsung's latest firmware. If you have already upgraded your device to BRJ3-based firmware, this release is for you.

Change log

Rebased to Samsung's BRJ3 kernel source code and boot images.
[Samsung Galaxy S9 & S9+ Cross Device Development] iampatricktan:
Thanks bro. Running your latest release now.
[Samsung Galaxy S9 & S9+ Cross Device Development] WhoIsJohnGalt1979:
The interactive feature works very well as per design. Thank you Ian.
[Samsung Galaxy S9 & S9+ Cross Device Development] pixelmatt:
Hi, since your newest release of Apgk the magisk chaining seems not to work anymore.

I don't change anything on my filestructure regarding magisk.

May you have a look at it?

For me this feature is so great to have and I love it:)

Thanks, as always.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
It seems you missed this line from the change log of 0.99.27:

* Trigger file to request Magisk chaining is now .apgk_magisk (formerly .magisk).

So, just rename the file and it will work as before.

The name change was to make it obvious which files control APGK behaviour and which are unrelated.
[Samsung Galaxy S9 & S9+ Cross Device Development] pixelmatt:
Oooops, missed that totally. Thank you for pointing that out :good:
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
ELS is my immediate upstream, so APGK will get .134 downstreamed¹ when ELS does; probably in the next 24 hours, but I didn't want to delay the rebase to BRJ3 for it.

¹ = This is a pet peeve of mine. Merging changes from an upstream kernel is correctly referred to as downstreaming, because the direction of flow is downstream from the source, just like a river. I have no idea why the Android community commonly refers to this process as upstreaming.

Upstreaming is actually the process of submitting changes (usually bug fixes) in the downstream fork back upstream to the source for the benefit of others who use either that source itself or a fork of it (in which case, they will receive the changes when their fork downstreams them).

The Android community is uniquely peculiar in its persistent confusion of these terms, and I'm recalcitrant about pandering to the practice.
[Samsung Galaxy S9 & S9+ Cross Device Development] pixelmatt:
So, now I read your changelog of v0.99.27 and get the point 'interactive'. I skipped this version, cause of the existence of the BRJ3 Rom on my device at this point. But I tried the installation process just now and it works well, at least for me:svetius::)
[Samsung Galaxy S9 & S9+ Cross Device Development] kangshoo:
can i use APGK 0.99.28 on bri4? or this kernel only for brj3

thank you
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.29 released.

I would normally sit on this for a while longer, just to avoid issuing two releases mere hours apart, but I'm travelling abroad tomorrow and may otherwise not get to it within a timely fashion.

Hopefully, this will be last release for today.

Change log

Updated to upstream Linux 4.9.134.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Try it.

People often try a custom kernel compiled for older firmware on newer firmware, but rarely the other way around. A kernel compiled for BRI is known to have issues on BRJ firmware, but the opposite isn't necessarily true. The easiest way to find out is to try. If you have a problem, either revert to the kernel you're already running, or install 0.99.27, which was the final version to be based on BRI source code.
[Samsung Galaxy S9 & S9+ Cross Device Development] kangshoo:
thank you bro

I just flashed it on my bri4 ,everything goes well. front cam works,it seems nothing wrong.
[Samsung Galaxy S9 & S9+ Cross Device Development] xruisz91:
Competition apgk and endurance kernel ? Lol

Ps : can you add fsync
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
If you mean the ability to disable fsync(), then no, sorry, that's a really bad idea; especially on a battery-powered device. It's also totally unnecessary on a device with very light I/O and fast storage access, such as a phone.
[Samsung Galaxy S9 & S9+ Cross Device Development] Eamo5:
Competition? Never. Cooperation and constructive criticism is what we thrive off :)
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.30 released.

Change log

Updated to upstream Linux 4.9.135.
[Samsung Galaxy S9 & S9+ Cross Device Development] icke:
No matter what ROM or kernel me is flashing...not able to over/under clock or undervolt. Me not stupid and was searching for that without luck. So please can someone here point me to a totarial? :confused:
[Samsung Galaxy S9 & S9+ Cross Device Development] kangshoo:
just rename the filename,add "_overcolock"
[Samsung Galaxy S9 & S9+ Cross Device Development] icke:
Haaa...yeah...what folder?
[Samsung Galaxy S9 & S9+ Cross Device Development] kangshoo:
anywhere,put the kernel where you can find it :)
[Samsung Galaxy S9 & S9+ Cross Device Development] Sora94:
Faro and IAN are on fire with those releases, I like how we get different kernel flavors.

APGK personal favorite stable kernel.
[Samsung Galaxy S9 & S9+ Cross Device Development] aedificavit:
+1
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.31 released.

As we move ever closer to a 1.0 release, this build disables a large number of debugging and logging features that are arguably unnecessary and undesirable in a release (i.e. non-engineering) kernel. This not only results in a less noisy kernel, but one with reduced on-disk and in-memory footprints.

The overclocking kernel has had its PELT timing further reduced to 8 ms to maximise the responsiveness of that variant. The difference will be small and will probably incur a further small battery consumption penalty, but users of that kernel are assumed to find this trade-off acceptable/desirable. I haven't run any performance-measuring tests on 8 ms PELT vs. 16 ms, so determining the precise effect of this change (if any) is left as an exercise for the user.

Change log

v0.99.31 (2018-11-22)

Many debugging and logging features disabled.

CONFIG_DISPLAY_USE_INFO

CONFIG_SEC_DISPLAYPORT_LOGGER

CONFIG_LOCKUP_DETECTOR (and all dependencies)

CONFIG_DETECT_HUNG_TASK

CONFIG_TIMER_STATS

CONFIG_DEBUG_ATOMIC_SLEEP

CONFIG_DEBUG_LIST

CONFIG_DEBUG_NOTIFIERS_PRINT_ELAPSED_TIME

CONFIG_DEBUG_EXCEPTION_STACK

CONFIG_PROFILING

CONFIG_MODULES (and dependencies)

CONFIG_SEC_PM_DEBUG

CONFIG_DEBUG_INFO (and dependencies)

CONFIG_SCHED_DEBUG

Strip assembler symbols (CONFIG_STRIP_ASM_SYMS).

Overclocking kernel variant now uses 8 ms PELT (Per Entity Load Tracking).

Updated WireGuard to v0.0.20181119.
[Samsung Galaxy S9 & S9+ Cross Device Development] Sora94:
[MENTION=7187684]ianmacd[/MENTION] back in action, great!
[Samsung Galaxy S9 & S9+ Cross Device Development] aedificavit:
Sorry for newbie question... How to use Wireguard with this kernel? Searched on Google but not clear to me.

Thx for your great work. Your Kernel is great!
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Download the WireGuard app and sign up with a VPN provider that supports the protocol. See WireGuard's own thread for more information.
[Samsung Galaxy S9 & S9+ Cross Device Development] oulouloul:
Is there any free provider on wireguard? Or all of theme are pre-paid?
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
The question is off-topic here and has already been asked and answered in the WireGuard thread.
[Samsung Galaxy S9 & S9+ Cross Device Development] iampatricktan:
Thanks for the update. Btw not based on .138? Also BRJ8?
[Samsung Galaxy S9 & S9+ Cross Device Development] tomiga:
Works just fine on BRJ8.
[Samsung Galaxy S9 & S9+ Cross Device Development] iampatricktan:
Alright. But not based on .138 right?
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
BRJ3 is the latest version for which Samsung has released kernel source, but this kernel will run fine on BRJ8, too.

The android-4.9-o maintainers haven't merged Linux past 4.9.135 yet, so the maintainer of ELS has nothing to downstream into his repo and I therefore have nothing to pull from him into APGK.

As soon as android-4.9-o is updated with the latest Linux, it will quickly flow downstream to the rest of us.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.32 released.

This release sees APGK fast-forwarded to the latest upstream Linux kernel, merging versions 4.9.136 to 4.9.141.

APGK has also been rebased on Samsung's latest BRJ6 kernel source code, with boot images sourced from stock BRJ6 firmware.

Change log

Updated to upstream Linux 4.9.141.

Rebased on Samsung's BRJ6 kernel source code and boot images.

Many more debugging and logging features disabled:

CONFIG_TRACE and its dependencies:

CONFIG_SEC_DEBUG

CONFIG_SEC_DEBUG_RESET_REASON

CONFIG_SEC_DEBUG_EXTRA_INFO

CONFIG_SEC_DEBUG_HW_PARAM

CONFIG_SEC_DEBUG_UPLOAD

CONFIG_SEC_PARAM

CONFIG_CM_OFFSET

CONFIG_SEC_DEBUG_AUTO_SUMMARY

CONFIG_SEC_UPLOAD

CONFIG_SEC_DEBUG_LAST_KMSG

CONFIG_SEC_DEBUG_PPMPU

CONFIG_EXYNOS_SDM

CONFIG_EXYNOS_SNAPSHOT_LOGGING_SMC_CALL

CONFIG_EXYNOS_ITMON

CONFIG_EXYNOS_SNAPSHOT

CONFIG_EXYNOS_SNAPSHOT_CALLSTACK

CONFIG_EXYNOS_SNAPSHOT_IRQ_EXIT

CONFIG_EXYNOS_SNAPSHOT_IRQ_EXIT_THRESHOLD

CONFIG_EXYNOS_SNAPSHOT_CLK

CONFIG_EXYNOS_SNAPSHOT_PMU

CONFIG_EXYNOS_SNAPSHOT_FREQ

CONFIG_EXYNOS_SNAPSHOT_DM

CONFIG_EXYNOS_SNAPSHOT_HRTIMER

CONFIG_EXYNOS_SNAPSHOT_REGULATOR

CONFIG_EXYNOS_SNAPSHOT_ACPM

CONFIG_EXYNOS_SNAPSHOT_THERMAL

CONFIG_EXYNOS_SNAPSHOT_I2C

CONFIG_EXYNOS_SNAPSHOT_SPI

CONFIG_EXYNOS_SNAPSHOT_PANIC_REBOOT

CONFIG_EXYNOS_SNAPSHOT_WATCHDOG_RESET

CONFIG_EXYNOS_SNAPSHOT_CRASH_KEY

CONFIG_EXYNOS_CORESIGHT

CONFIG_EXYNOS_CORESIGHT_PC_INFO

CONFIG_PC_ITERATION

CONFIG_EXYNOS_CONSOLE_DEBUGGER

CONFIG_EXYNOS_CONSOLE_DEBUGGER_INTERFACE

CONFIG_USB_DEBUG_DETAILED_LOG

CONFIG_MMC_DW_DEBUG

CONFIG_SEC_DEBUG_TSP_LOG

CONFIG_SDFAT_DBG_MSG

CONFIG_SDFAT_DEBUG

CONFIG_PHY_EXYNOS_DP_DEBUGFS

CONFIG_PHY_EXYNOS_DEBUGFS is not set

CONFIG_CGROUP_DEBUG

CONFIG_CMUCAL_DEBUG

CONFIG_SEC_BOOTSTAT

CONFIG_SEC_DUMP_SUMMARY

If anyone needs any of these features, I am open to reinstating them.
[Samsung Galaxy S9 & S9+ Cross Device Development] aedificavit:
Work in Pie Beta

Hi!

Does this kernel work on Pie Beta?

Thx
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.33 released.

Another maintenance update.

Apart from merging the latest Linux kernel, this also reverts a recent downgrade of the Realtek USB Ethernet driver imposed by upstream ELS in APGK 0.99.32 and upgrades it to the latest available version.

Change log

Updated to upstream Linux 4.9.142.

Realtek RTL8152 driver upgraded to latest version (v2.10.00) (after having been downgraded in APGK 0.99.32 by a change in upstream ELS).
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.34 released.

It's maintenance time.

Change log

Updated to upstream Linux 4.9.144.

Sundry kernel options re-enabled, mostly to bring back CONFIG_SEC_DEBUG_LAST_KMSG:

CONFIG_TRACE

CONFIG_SEC_DEBUG

CONFIG_SEC_DEBUG_RESET_REASON

CONFIG_SEC_DEBUG_EXTRA_INFO

CONFIG_SEC_DEBUG_HW_PARAM

CONFIG_SEC_DEBUG_AUTO_SUMMARY

CONFIG_SEC_DEBUG_LAST_KMSG

CONFIG_SEC_PARAM

CONFIG_CM_OFFSET=7340596

CONFIG_EXYNOS_SNAPSHOT

CONFIG_EXYNOS_SNAPSHOT_CALLSTACK=4

CONFIG_EXYNOS_SDM
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.35 released.

Flash. Reboot. Enjoy.

Change log

Updated to upstream Linux 4.9.145.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.36 released.

This release removes 4 commits accidentally included in v0.99.35. With apologies.

Change log

Reverted 4 accidental commits.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.37 released.

If no further issues are raised in the next couple of weeks, either this or an incremental update with a newer Linux kernel will probably become APGK v1.0.0 before the end of 2018.

Change log

Updated to upstream Linux 4.9.146.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.38 released.

Here's your festive stocking-stuffer.

Change log

Updated to upstream Linux 4.9.147.

Updated WireGuard to v0.0.20181218.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.39 released.

This is very likely to be the final release of APGK before v1.0.0.

If Samsung release BRK or BRL kernel sources before the end of the year, I will rebase APGK on the newer source. Otherwise, the current BRJ6 sources have been proven to yield a kernel that functions without any obvious issue on the final releases of the Android 8 firmware.

Samsung has released production Android 9 (Pie) firmware for the S9/S9+ over the last week. Although no-one has yet asked whether I intend to rebase APGK on Android 9 source code, just in case anyone is wondering or making an assumption one way or the other, I feel I should provide clarity and state that APGK will not be transitioned to Pie kernel source for the foreseeable future.

The primary reason for this is that I do not possess a device running Android 9 and have no intention of updating any, so I am currently unable to test kernels built for this version of the operating system.

Change log

Updated to upstream Linux 4.9.148.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
You're not making it easy for me, but that's as it should be. Thanks for your input.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Stable version 1.0.0 released.

After 6 months, innumerable internal builds and almost 40 public beta releases, a stable release of APGK finally sees the light of day; and just in time for its own obsolescence, too, if the dwindling download figures are anything to go by.

If your device is still on Android 8 (Oreo) and likely to stay that way, rest assured that APGK will continue to be updated for the foreseeable future with downstream merges of the 4.9 Linux kernel. Assuming Samsung eventually get around to granting my request for their final Oreo kernel source code (BRK3 or BRL3), this, too, will be merged in due course.

If you have already updated your device to Android 9 (Pie), I can offer you no assurances regarding APGK at this point in time. Whilst it's possible that APGK will target Android 9 in the future, it's at least as likely that this won't come to pass. Your only recourse for now is Samsung's own Pie kernel. Rebased versions of other custom kernels for the S9/S9+ will doubtless appear in due course, but for one reason or another, there isn't any that I feel I can recommend. In that scenario, too, I would suggest sticking with Samsung's kernel.

Now might be an opportune moment to remind everyone that this kernel is released under version 2 of the GNU General Public Licence, which is a roundabout way of saying that I am not the only person who can do the work to make this kernel run on Android 9. The future development of APGK need not — and should not — be tied to my own personal needs and whims. If this appears to be the case, it is merely because I am currently the sole contributor to this project.

Thank you to everyone for the kind words and support shown so far.

Change log

Updated version to 1.0.0.
[Samsung Galaxy S9 & S9+ Cross Device Development] ramone01:
I need to selinux permissive for viper4android only. Can i use v4a without permissive mode ?
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Yes. Just install the Magisk module implementation of Viper. I use it myself.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.1 released.

Samsung have finally granted my request for BRK3 kernel source code, so this first release of 2019 is built with these changes merged.

There was one further release of Android 8 firmware after this, namely BRL3, but this received minimal distribution and it's entirely possible that the kernel from that version remains unchanged from BRK3. I still have a request for the release of the BRL3 kernel source code pending with Samsung, however, so we should know before long.

Change log

Rebased to Samsung's BRK3 kernel source code and boot images.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.2 released.

This maintenance release brings us up to date with the latest and greatest Linux source.

I must say, the download figures for the last couple of 1.0.x releases have surprised me. Clearly, quite a few of you have not updated your devices to Android 9 for one reason or another.

5 users or 5000, however, APGK has never been about the numbers. APGK will continue to be updated even if its user base dwindles towards zero in the coming months.

Change log

Updated to upstream Linux 4.9.149.
[Samsung Galaxy S9 & S9+ Cross Device Development] xiru2312:
thank you:svetius:
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.3 released.

Change log

Updated to upstream Linux 4.9.150.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.4 released.

Change log

Updated to upstream Linux 4.9.151.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.5 released.

This release merges Samsung's final kernel source code targeting Android 8.0.

The BRL3 firmware received only minimal distribution, released only for devices with the DBT CSC. I had to pester Samsung for the code, filing half a dozen separate requests with them until they finally obliged.

It turns out that only one file has been modified from BRK3 to BRL3, fs/sdcardfs/inode.c for the trivia buffs.

Change log

Rebased to Samsung's BRL3 kernel source code and boot images.