• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][UNOFFICIAL][11][SM-T820][SM-T825][BETA][2021-11-30] LineageOS 18.1 for Galaxy Tab S3

Search This thread
Code:
/*
* Your warranty will be VOID after installing a custom ROM.
*
* Get notified yourself that I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it!
* YOU are choosing to make these modifications,
* and if you point the finger at me for messing up your device,
* I will laugh at you.
*/


# LineageOS

LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.


# What's working
  • Display/Touchscreen
    • LiveDisplay
  • Audio playback
    • Quad speakers
    • Headphone/Headset
    • Bluetooth audio
  • Video playback
    • HDR
  • Camera
  • Microphone
  • Sensors
  • Fingerprint sensor
  • GPS
  • LTE (SM-T825)
  • WiFi
  • Bluetooth
  • DRM
    • Widevine L1
  • USB ADB/MTP/OTG
  • Samsung Doze
  • S-Pen
    • Palm rejection
  • SD Card
  • Power-off mode charging

# What's not working
  • Fast charging
  • WiFi display/hotspot
  • SELinux permissive
  • Hardware encryption
  • Lots of things I couldn't find
  • Please see the "Known issues" part of this post

# Downloads

## LineageOS 18.1

## Google Apps

## TWRP Recovery

# How to install
  1. Unlock the bootloader.
  2. Download TWRP and flash the recovery image via Odin.
  3. Download LineageOS 18.1 for Galaxy Tab S3.
    • Be aware of the board name.
  4. Download GAPPS for Android 11and the others you want to flash.
    • Only OpenGApps is tested. (open_gapps-arm64-11.0-pico-20210130-TEST.zip)
  5. Enter TWRP recovery.
    • The first boot to TWRP might be very slow because of the unmatched file systems.
  6. Format the whole system, data, cache partitions using the format menu.
    • You will type `yes` to do that.
  7. Flash the images.
    • If you're going to install GApps or something, you have to install the LineageOS first.
  8. Reboot the system.
  9. Done.

# Known issues
  • Settings app crashes for the first run
  • SD card may not be recognized for the file system, excepts VFAT (FAT32)
  • OTG drives may show nothing even if it mounted
  • The side button on S-Pen is working but you must use the proper application that can handle the button event
  • Enabling AudioFX may cause a short popping sound when playing a sound
  • Fast-charging won't work properly, it sometimes works but most of the time it won't
  • Turning on the flashlight via the quick panel doesn't work after using a camera app
  • Using a camera app may cause reducing the UI performance on a launcher app
  • Nightlight mode will not switch automatically with Sunrise/Sunset
  • The tablet rarely reboots with a GMS related error
  • Unlocking the lock screen can make tablets not usable sometimes
  • CTS profile will not be fixed
  • Thank all of you for the feedback

# Sources

# Telegram Groups
  • If you are interested in developing this potential machine, please tell me through PM then I will send you the invitation link.
  • If you need a general discussion channel for this potential machine or want to share the news of its Android projects from anyone to everyone, you can join our discussion group chat.

# Buy me a coffee

# Credits / Special thanks to
  • Android Open Source Project
  • LineageOS Team
  • @Valera1978 for his amazing previous work including his MSM8996 kernel
  • @supermike86 and @samsuffit for testing LineageOS 18.1 for T820, which is I don't have one
  • @bmwdroid and @cherepanov for confirming the LTE works
  • @sebmue for letting me know that the useful information for palm rejection, and @ghostwheel for sharing its working source codes on Android 9
  • @switchgott for helping me in the development discussion and creating Telegram groups
  • All from our Telegram discussion channel, @EonOfBlack , Sands, David Becker, ...
  • @LuK1337 for giving me a hint to fix the quad-speakers.
 

Attachments

  • gts3llte-lineageos18.1-2.png
    gts3llte-lineageos18.1-2.png
    89.9 KB · Views: 549
  • gts3llte-lineageos18.1-1.png
    gts3llte-lineageos18.1-1.png
    558.8 KB · Views: 538
  • gts3llte-lineageos18.1-3.png
    gts3llte-lineageos18.1-3.png
    46.6 KB · Views: 469
  • gts3llte-lineageos18.1-5.png
    gts3llte-lineageos18.1-5.png
    119.7 KB · Views: 485
  • gts3llte-lineageos18.1-6.png
    gts3llte-lineageos18.1-6.png
    288.1 KB · Views: 497
  • gts3llte-lineageos18.1-4.png
    gts3llte-lineageos18.1-4.png
    39.8 KB · Views: 552
Last edited:
## Changelogs
  • 2021. 11. 30
    • gts3l-common: Synced with the latest LIneageOS source
    • gts3l-common: Fixed Bluetooth input working including a Bluetooth keyboard
    • gts3l-common: Now it starts to use my custom kernel
      • Version: awesometic-kernel-v0.3
      • To get the detailed information, please see the third post of this thread
  • 2021. 11. 16
    • gts3l-common: Applied the new security patch, November 5, 2021
    • gts3l-common: Fixed the external keyboards' arrow keys working
  • 2021. 10. 29
    • gts3l-common: Applied the new security patch, October 5, 2021
  • 2021. 9. 22
    • gts3l-common: Applied the new security patch, September 5, 2021
    • gts3l-common: Fixed the power-off mode charging using the Samsung LPM binary
    • gts3l-common: Switched to QTI USB HAL, version 1.2
    • gts3l-common: Cleaned up the keyboard layouts and added the layouts from the latest firmware for Samsung products like the book cover keyboard
    • gts3l-common: Improved power management
  • 2021. 9. 1
    • gts3l-common: Fixed the camera working
    • gts3l-common: Resolved lots of SELinux warnings
    • gts3l-common: Added some props to optimize the video and media performance
    • gts3l-common: Added proper power profiles for better power management
    • gts3l-common: Added a proper thermal-engine config for better thermal management
    • gts3l-common: Change the hotspot location of the pointer arrow
  • 2021. 8. 13
    • gts3l-common: Applied the new security patch, August 5, 2021.
    • gts3l-common: Fixed the quad-speakers working.
    • gts3l-common: Disabled WiFi display feature.
    • gts3l-common: Added support for Adaptive Fast Charge.
    • gts3l-common: Added LiveDisplay HIDL to switch the screen modes.
    • gts3l-common: Added the button backlight control menu.
    • gts3l-common: Added the advanced reboot menu.
    • gts3l-common: Changed to the Light HIDL completely.
    • gts3l-common: Changed the stylus pointer icon to the smaller one.
  • 2021. 7. 29
    • gts3l-common: Fixed headphone jack working.
    • gts3l-common: Fixed Bluetooth audio playback working.
    • gts3l-common: Fixed microphone working.
    • gts3l-common: Fixed AudioFX working.
    • gts3l-common: Made hardware touch key, LCD, Touchscreen, S-Pen disabled when the screen turns off.
    • gts3l-common: Fixed DRM working.
    • gts3l-common: Disabled connecting to WPA3 WiFi.
    • gts3lwifi: Fixed Bluetooth working.
    • gts3lwifi: Fixed vibrator working.
  • 2021. 7. 14
    • gts3l-common: Applied the new security patch, July 5, 2021.
    • gts3l-common: Added support for palm rejection for S-Pen.
    • gts3l-common: Added support for the Freeform Window mode of AOSP.
    • gts3l-common: Removed the "Serial console enabled. Performance is impacted..." message.
  • 2021. 7. 4
    • gts3l-common: Changed the default DPI value to 320.
    • gts3l-common: Added new pointer arrow icon for S-Pen.
    • gts3l-common: Moved fingerprint sensor location when the preview screen that is before the actual enrollment a fingerprint.
    • gts3l-common: Enabled automatically brightness by default.
    • gts3l-common: Enabled adjusting haptic feedback intensity menu.
    • gts3llte: Fixed LTE working.
  • 2021. 6. 28
    • gts3l-common: Separated the device tree into 3 parts, common, LTE, and WiFi.
    • gts3l-common: Changed the default DPI value to 360.
    • gts3l-common: Fixed fingerprint sensor working.
    • gts3l-common: No more adsprpcd errors on the logcat.
    • gts3llte: Added missing RIL-related binaries, init scripts and could check the RIL initialized properly. But an error still repeated on the logcat so I think it won't work yet.
    • gts3lwifi: Added support for Galaxy Tab S3 WiFi variants.
  • 2021. 6. 17
    • Initial release
 
Last edited:
## About quad-speakers

I have lots of tries to make quad-speakers working and finally, I think I found a way we should ahead.

I think the important parts for working quad-speakers are in the Samsung SoundBooster libraries. We can check this on the logcat easily.

Code:
12-31 13:28:24.101   708   708 I SoundBooster_plus: Use HardCoding Values
12-31 13:28:24.101   708   708 I SoundBooster7: SetPar()-whole parameter
12-31 13:28:24.101   708   708 I SoundBooster_Inner: SetPar()-partial parameter
12-31 13:28:24.101   708   708 I SoundBooster7:SoundBooster_Multiplexer: [mInstanceID:0]SetPar()  SPK_0_OnOff : 1 , SPK_1_OnOff : 1 , SPK_2_OnOff : 1 , SPK_3_OnOff : 1
12-31 13:28:24.101   708   708 I SoundBooster_Inner: SetPar()-partial parameter
12-31 13:28:24.101   708   708 I SoundBooster7:SoundBooster_Multiplexer: [mInstanceID:1]SetPar()  SPK_0_OnOff : 1 , SPK_1_OnOff : 1 , SPK_2_OnOff : 1 , SPK_3_OnOff : 1
12-31 13:28:24.101   708   708 I SoundBooster7: SetVolumeTable()
12-31 13:28:24.101   708   708 I SoundBooster7: SetOrientation( 0 )
12-31 13:28:24.101   708   708 I SoundBooster_Inner: SetOrientation( 0 )
12-31 13:28:24.102   708   708 I SoundBooster7:SoundBooster_Multiplexer: [mInstanceID:0]SetOrientation(0)
12-31 13:28:24.102   708   708 I SoundBooster7:SoundBooster_Multiplexer: [mInstanceID:0]Set_Orientation_Update_Flag() flag : 1
12-31 13:28:24.102   708   708 I SoundBooster_Inner: SetOrientation( 0 )
12-31 13:28:24.102   708   708 I SoundBooster7:SoundBooster_Multiplexer: [mInstanceID:1]SetOrientation(0)
12-31 13:28:24.102   708   708 I SoundBooster7:SoundBooster_Multiplexer: [mInstanceID:1]Set_Orientation_Update_Flag() flag : 1

Yes, I cannot really sure it initializes quad-speakers, but the name like SPK_#_OnOFF looks really interesting.

So if it is the one who makes quad-speakers working, then it looks quite easy; Use SoundBooster libraries.
But it is not that easy to use that library, properly.

The libraries, the vendor binaries, in other words, have a lot of dependencies on other libraries, each other. It sounds like it can be so complicated and you are right, sometimes it becomes so complicated to use.

Each library contains a list of which library it must go together so it is easy to supplement them. But we don't know which configuration files and the other libraries called by hardcoded code are needed because it is a binary file. Even the directory structure can be a matter.

For this reason, I could call the SoundBooster libraries like the above messages by using the many many prebuilt libraries but could not get the quad-speakers working so far. In the logcat the audio stuff annoys me about the lack of backend entries and something but I don't know what I am missing.

Plus, maybe it isn't a good idea to cover errors using shims or something because we still don't know which part needs to get the quad-speakers working.

I really hope the fully working speakers on the custom ROMs but it may take time.

### Update on 2021. 7. 29

Finally, I can enable the vendor audio HAL that comes with that SoundBooster to work. But so far no good for the quad speakers.

Even though the quad-speakers do not work yet, I think that the SoundBooster library is needed anyway. Because I saw the speaker rotation codes for the quad-speakers in that library.

So maybe the speaker itself is ready now, but something doesn't seem to be filled.

I have no idea for now, so I will update this post as soon as I find something. :unsure:

### Update on 2021. 8. 13

Finally, I could get the quad-speakers working. :cool:

Actually, the answer was so close to me. The key factor is even I saw before but I didn't think that it is so important.

In short reports, the Samsung libraries do their work but somewhat partially. I could check how each speaker configured using tinymix tool and found that the upper speakers' I2S channel must be set manually in our case.

So we have to have the vendor libraries for audio anyway. It should work without them, but we have to find lots of configurations to fit into our devices. So, it may be best to keep the libraries.

Enjoy the quad-speakers. :)

## About the camera

## Why the camera doesn't work? It works on the previous LineageOS on this forum

Right, it does. I think it may be related to the vendor files. Before starting the development LOS 18.1, I have to update vendor files from the latest firmware. But after that, the previous definitions for the camera on `device.mk` began not to work.

So, I should start again from scratch. Have to find out how many files the vendor files require, or how can I build the camera binaries from the sources.

Before all, I won't fix that right now. Since I think the camera is not that important as the others like the audio or the kernel, in general. It is an old tablet, having a just-could-be-used camera. Sorry for who loves its camera. :)

### Update on 2021. 9. 1

Yeah, now we have the working camera too. :cool:

For now, our builds use the vendor's pre-built camera libraries so that it may not be optimized for a custom ROM. But in our use case it works really nice..... except for some bugs.

Maybe the default camera daemon has slightly different settings for the flashlight. If I use a camera at least once, maybe, the turning on the flashlight by the toggle button on the quick panel no longer works. It looks like a protocol problem between the Android SystemUI and the prebuilt camera daemon, so I don't know how to fix that neatly for now.

And sometimes using a camera app reduces the UI performance for a launcher app and the animation when pulling down the quick/notification panel. Also, I don't know why this behavior happens. The most strange thing is that this reducing performance only appears with the launcher app as far as I have seen.

So, anyway, for this reason we should build ours from the AOSP/LOS source codes someday.
But, I can say that it works like a charm now. It will be doing much better if you use Open Camera from PlayStore.
I'm not advertising it, just to share the experience. 😅

Code:
/*
 * All done. Enjoy the camera and audio!
 */

## About the kernel

### Update on 2021. 11. 30

Finally the first release including my custom kernel is published, as of December 3, 2021.
Now all the later releases will have my kernel. :)

This kernel is based on CTD1 firmware, and I have done the following jobs so far;
  • Merged android-linux-stable/msm-3.18, which is including up to Linux 3.14.140 patches
  • Merged LA.UM.7.6.r1-07800-89xx.0 CAF tag
  • Replaced the built-in WLAN driver into the CAF one from LA.UM.7.6.r1-07800-89xx.0 tag, which is the latest version
  • Disabled most of Samsung-specific flags including TIMA, KNOX, RESTRICT, ...
  • Enabled F2FS file system
  • Added AutoSMP CPU hotplug feature and enabled by default for better battery consumption
  • Added AdrenoBoost and enabled by default for better GPU performance
  • Added Anxiety I/O scheduler for better I/O performance
  • Enabled TCP Westwood congestion window control by default for better network stability
  • Set CONFIG_HZ to 300 which is recommended in Android devices and it improves overall interactivity and UX with no power cost
  • Now the S-Pen palm rejection is implemented in the kernel rather than the Android frameworks
  • Maybe more..?
But we have still some limitations.
  • It still uses the legacy camera driver from CTD1 firmware so unfortunately there are the same bugs on the camera as before
  • The screen on/off using a flip cover is broken for an unknown reason. The system recognizes how the flip cover status changed but actually not working
  • Cannot upgrade to the next CAF tag because of some old blobs we have, I believe
  • Maybe more..?
This is the first version of mine, so there might be some more upgrades on later.

I think the most meaningful thing about this job is now we can edit the kernel on the full Linux kernel commits.

Enjoy. 😀
 
Last edited:

elchmartin

Senior Member
Oct 17, 2014
166
50
Duesseldorf
Google Nexus 4
Nexus 7
Sweet!
Unfortunately my wife uses out tablet for work too so I can't really mess with it.
Plus ours is 820 (non-LTE), so I'm not sure if the alpha will work anyway.
But I am quite curious to try some time.... maybe I'll just get a more recent work-tab :)
 
  • Like
Reactions: MistCe
Sweet!
Unfortunately my wife uses out tablet for work too so I can't really mess with it.
Plus ours is 820 (non-LTE), so I'm not sure if the alpha will work anyway.
But I am quite curious to try some time.... maybe I'll just get a more recent work-tab :)

Thanks for your interest. :)

I believe I can create a WIfi version without the actual machine. It will be uploaded in a few days I think comes with implementing the common device tree.
 

Rhobb

Member
Jun 7, 2021
14
1
Code:
/*
* Your warranty will be VOID after installing a custom ROM.
*
* Get notified yourself that I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it!
* YOU are choosing to make these modifications,
* and if you point the finger at me for messing up your device,
* I will laugh at you.
*/

# LineageOS

LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.


# What's working
  • Display/Touchscreen
  • Audio playback (only bottom speakers)
  • Video playback including HDR
  • Sensors
  • GPS
  • WiFi
  • Bluetooth
  • USB ADB/MTP
  • Samsung Doze
  • S-Pen
  • SD Card

# What's not working
  • Audio (quad speakers)
  • Bluetooth audio playback
  • Microphone
  • Camera
  • LTE
  • DRM
  • SELinux permissive
  • Hardware encryption
  • Fingerprint sensor (recognized but enrollment failed)
  • Lots of things I couldn't find...

# Downloads

# How to install
  1. Unlock the bootloader.
  2. Download TWRP and flash the recovery image via Odin.
  3. Download LineageOS 18.1 for Galaxy Tab S3.
    • Be aware of the board name.
  4. Download GAPPS for Android 11and the others you want to flash.
    • Only OpenGApps is tested. (open_gapps-arm64-11.0-pico-20210130-TEST.zip)
  5. Enter TWRP recovery.
    • The first boot to TWRP might be very slow because of the unmatched file systems.
  6. Format the whole system, data, cache partitions using the format menu.
    • You will type `yes` to do that.
  7. Flash the images.
    • If you're going to install GApps or something, you have to install the LineageOS first.
  8. Reboot the system.
  9. Done.

# Notes [2021. 6. 17]
  • Some annoying messages are repeated on the logcat, which I think the tiny stutters may cause for this reason.
  • Fingerprint and some other minor things may be fixed soon but not sure about audio and camera.
  • For now, it may not be good for the daily driver. Please be aware that this is a test version yet. I have no responsibility for your data.
  • The device tree sources will be separated into two types of boards for better maintaining.

# Sources

# Buy me a coffee

# Credits / Special thanks to
  • Android Open Source Project
  • LineageOS Team
  • Valera1978 for his amazing previous work including his MSM8996 kernel
Thank You !
 
Will you also be working on the t820, because i see this id for t825?

Yes, I'm working on T820 now, actually, it's a little late because I tried some things including fixing the fingerprint working.

And I saw some interesting strings are in the audio.primary.msm8996 binary. I have tried using this but doesn't work so far.
If the quad-speaker can be enabled by that binary file, we should use that file on the fly.

But for now, it seems to take a lot of time, so I will upload the image for T820 before working on the quad-speaker.
 
Last edited:
  • Like
Reactions: sebmue and bmwdroid

supermike86

Member
Jul 19, 2016
9
2
35
Qualche volontario per testare LineageOS 18.1 per T820?
Potrebbe essere necessaria un'installazione pulita. Sarebbe qualcuno che può cancellare tutti i suoi dati.

Prova questa immagine e fammi sapere che funziona o meno. Se funziona aggiornerò il thread.
- https://drive.google.com/file/d/1yMq8wAsJKIXf5C6iBF5kZCK6lngkDPwN/view?usp=sharing

Proverò e ti farò sapere


Edit:
the installation was successful, even with the installation of the nano gapps. wifi is working properly. for other bugs among those mentioned I have not had the opportunity to test yet. but in my opinion the system is very good and fluid, great job. it would be great to have this rom for daily use! thank's for your job!
 
Last edited:
  • Like
Reactions: Awesometic

Luiggi Piumbu

New member
Aug 4, 2017
1
2
Any volunteer to test LineageOS 18.1 for T820?
It may need clean install. It'd be someone who can erase all of his data.

Please test this image and let me know it works or not. If it works, I will update the thread.
- https://drive.google.com/file/d/1yMq8wAsJKIXf5C6iBF5kZCK6lngkDPwN/view?usp=sharing
I installed it from the link in the first post with OpenGapps Nano (also from the first post), and so far so good.
This is really much much faster than the "Tweaked" ROM! It feels like a new tablet.
I don't use the camera, so for me it’s already very usable. I didn't notice any problem with audio. There is only sometimes a short popup appearing (a few milliseconds) and disappearing. Also, if you enable "Trust" it complains about SELinux and some stuff.
Anyway I will keep this fast ROM, great work, thank you!

EDIT: There is also a notification saying : "Serial console enabled. Performance is impacted. To disable, check bootloader" which i didn't understand the meaning...
 
Last edited:
Dec 7, 2016
14
6
Bavaria
You are so good! Thanks so much.
I do have 2 of the WiFi tablets and will test after my holiday.
The original firmware is really crap and so slow, hope that this is faster.
The only problem is I need it as daily driver, but will make a complete backup.
Greetings from Bavaria
 
  • Love
Reactions: MistCe

Top Liked Posts

  • 1
    is there any prospects for android 12? ... maybe an early look to see if its possible, my n8013 the dinosoar that it is already has an alpha build because only God wished it
    Sure, if I could.
    But as always, please don't expect too much 😅
    1
    I'm still getting the Google drive file from 11-30, not 12-3 when I click the OP link -- or does 11-30 include the new kernel you referred to in the 12.3.2021 update?

    Is everyone using the 20211130 ROM who's posting about it?
    Yeah, 20211130 is the latest version now. I'm sorry for the ambiguous titles.
    Will change them to the same date. 😀
  • 11
    Long time no see. :)

    I uploaded the new version that contains the November security patch and fixed arrow keys working on the keyboard inputs.
    Yeah, sorry for it isn't a big update, I know there're lots of bugs remaining. 😅

    Currently I have been investigating upgrading our kernel as I said before.

    I did start the Android kernel studying to know what CAF based kernel or AOSP based kernel means, and how the other people merge the latest tags from the official repositories to the vendor-providing kernel base.
    And now I think I'm managed to know the very small piece of that Android kernel world.

    First, I found that there is no problem with using the Bluetooth keyboard on the stock kernel for LOS, which hasn't any patch including the upstream Linux patches and/or any tunes.
    Yeah, this is interesting, it can be small evidence that the current kernel is somewhat broken at least for the Bluetooth.

    My first plan was to migrate Samsung codes to the LineageOS MSM8996 kernel. But after a few weeks, I realized that it isn't for humans. There are so many flags and tweaks they put in. Even some codes are not marked whether this code is from Samsung.

    So I changed my plan, to get CAF tags onto the top of the CTD1 kernel that is the latest kernel base of the T825 model. Fortunately, I could merge some modern CAF tags successfully. But in that progress the camera got broken. :unsure:

    Then, I tried to merge the AOSP tags for getting the proper upstream Android/Linux patches and security patches. I could merge until early 2020, that is also containing 3.18.140 upstream Linux patches. But I couldn't merge the latest patches like the one just published last month. It makes the tablet not boot.

    I think it is quite hard work on our tablet because Samsung puts various un-listed patches onto the top of the 3.18.115 kernel but they didn't apply the upstream Linux patches. So, for example, when I merge the 3.18.116 tag to the current 3.18.115 kernel, I couldn't accept all the incoming changes because some files in the current kernel base are much more modern files. o_O This makes me get frustrated.

    But it doesn't mean it is impossible. Some people out there are doing this job now so there will be something more I don't know yet about the Android kernel development. If someone has experience or knowledge of upgrading vendor kernel, please join our Telegram channel and let's discuss that.
    6
    Hello all.

    I uploaded the new LineageOS ROMs that comes with the new kernel.

    Probably the first seen noticeable change is the Bluetooth keyboard is fixed now. 😀
    And there are lots of improvements on that. I wrote the detailed information to the first post of this thread but firstly, I copied that contents here.

    ## About the kernel

    ### Update on 2021. 12. 3


    Finally the first release including my custom kernel is published, as of December 3, 2021.
    Now all the later releases will have my kernel. :)

    This kernel is based on CTD1 firmware, and I have done the following jobs so far;
    • Merged android-linux-stable/msm-3.18, which is including up to Linux 3.14.140 patches
    • Merged LA.UM.7.6.r1-07800-89xx.0 CAF tag
    • Replaced the built-in WLAN driver into the CAF one from LA.UM.7.6.r1-07800-89xx.0 tag, which is the latest version
    • Disabled most of Samsung-specific flags including TIMA, KNOX, RESTRICT, ...
    • Enabled F2FS file system
    • Added AutoSMP CPU hotplug feature and enabled by default for better battery consumption
    • Added AdrenoBoost and enabled by default for better GPU performance
    • Added Anxiety I/O scheduler for better I/O performance
    • Enabled TCP Westwood congestion window control by default for better network stability
    • Set CONFIG_HZ to 300 which is recommended in Android devices and it improves overall interactivity and UX with no power cost
    • Now the S-Pen palm rejection is implemented in the kernel rather than the Android frameworks
    • Maybe more..?
    But we have still some limitations.
    • It still uses the legacy camera driver from CTD1 firmware so unfortunately there are the same bugs on the camera as before
    • The screen on/off using a flip cover is broken for an unknown reason. The system recognizes how the flip cover status changed but actually not working
    • Cannot upgrade to the next CAF tag because of some old blobs we have, I believe
    • Maybe more..?
    This is the first version of mine, so there might be some more upgrades on later.

    I think the most meaningful thing about this job is now we can edit the kernel on the full Linux kernel commits.

    Enjoy. 😀
    1
    @Awesometic great news. Thx very much again.
    Just downloading.
    Any, to you known, disadvantages from f2fs to ext4?
    I've read that ext4 is more stable.
    What do you think?

    Yeah definitely, EXT4 is the most stable file system for Linux so even the modern Linux distributions use that as a default file system for the root partition.
    I think F2FS is also stable nowadays and it is enough to use on a mobile device. In fact, 3.18 kernel doesn't get the latest patches since 3 years ago but fortunately CAF and AOSP sometimes added some patches on that.
    Yeah, this depends on your choice. Between relatively unstable but faster one and the most stable but a little slower one :)
    1
    @Awesometic so being lazy I've just wiped System and Caches then flashed your new LOS which worked.
    As I undervolt (thought might reduce freezes) my device I don't think it's sense full to switch to a faster fs.
    I will use it like before to test if (probably GMS caused) random freezes still appear.
    If they don't I still can switch to f2fs.
    1
    Hello guys, first of all, this is the best custom rom ever for our tab s3. Many thanks to Awesometic and team !
    I'm trying to activate gestures navigation that i remember can be found at settings > system > gestures > system navigation. In this rom i do not see this option. Can the gestures be activated ? I could not figure out how ... Thanks in advance !!
  • 28
    Code:
    /*
    * Your warranty will be VOID after installing a custom ROM.
    *
    * Get notified yourself that I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed.
    * Please do some research if you have any concerns about features included in this ROM
    * before flashing it!
    * YOU are choosing to make these modifications,
    * and if you point the finger at me for messing up your device,
    * I will laugh at you.
    */


    # LineageOS

    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.


    # What's working
    • Display/Touchscreen
      • LiveDisplay
    • Audio playback
      • Quad speakers
      • Headphone/Headset
      • Bluetooth audio
    • Video playback
      • HDR
    • Camera
    • Microphone
    • Sensors
    • Fingerprint sensor
    • GPS
    • LTE (SM-T825)
    • WiFi
    • Bluetooth
    • DRM
      • Widevine L1
    • USB ADB/MTP/OTG
    • Samsung Doze
    • S-Pen
      • Palm rejection
    • SD Card
    • Power-off mode charging

    # What's not working
    • Fast charging
    • WiFi display/hotspot
    • SELinux permissive
    • Hardware encryption
    • Lots of things I couldn't find
    • Please see the "Known issues" part of this post

    # Downloads

    ## LineageOS 18.1

    ## Google Apps

    ## TWRP Recovery

    # How to install
    1. Unlock the bootloader.
    2. Download TWRP and flash the recovery image via Odin.
    3. Download LineageOS 18.1 for Galaxy Tab S3.
      • Be aware of the board name.
    4. Download GAPPS for Android 11and the others you want to flash.
      • Only OpenGApps is tested. (open_gapps-arm64-11.0-pico-20210130-TEST.zip)
    5. Enter TWRP recovery.
      • The first boot to TWRP might be very slow because of the unmatched file systems.
    6. Format the whole system, data, cache partitions using the format menu.
      • You will type `yes` to do that.
    7. Flash the images.
      • If you're going to install GApps or something, you have to install the LineageOS first.
    8. Reboot the system.
    9. Done.

    # Known issues
    • Settings app crashes for the first run
    • SD card may not be recognized for the file system, excepts VFAT (FAT32)
    • OTG drives may show nothing even if it mounted
    • The side button on S-Pen is working but you must use the proper application that can handle the button event
    • Enabling AudioFX may cause a short popping sound when playing a sound
    • Fast-charging won't work properly, it sometimes works but most of the time it won't
    • Turning on the flashlight via the quick panel doesn't work after using a camera app
    • Using a camera app may cause reducing the UI performance on a launcher app
    • Nightlight mode will not switch automatically with Sunrise/Sunset
    • The tablet rarely reboots with a GMS related error
    • Unlocking the lock screen can make tablets not usable sometimes
    • CTS profile will not be fixed
    • Thank all of you for the feedback

    # Sources

    # Telegram Groups
    • If you are interested in developing this potential machine, please tell me through PM then I will send you the invitation link.
    • If you need a general discussion channel for this potential machine or want to share the news of its Android projects from anyone to everyone, you can join our discussion group chat.

    # Buy me a coffee

    # Credits / Special thanks to
    • Android Open Source Project
    • LineageOS Team
    • @Valera1978 for his amazing previous work including his MSM8996 kernel
    • @supermike86 and @samsuffit for testing LineageOS 18.1 for T820, which is I don't have one
    • @bmwdroid and @cherepanov for confirming the LTE works
    • @sebmue for letting me know that the useful information for palm rejection, and @ghostwheel for sharing its working source codes on Android 9
    • @switchgott for helping me in the development discussion and creating Telegram groups
    • All from our Telegram discussion channel, @EonOfBlack , Sands, David Becker, ...
    • @LuK1337 for giving me a hint to fix the quad-speakers.
    12
    Hi all,

    Finally, I can take a picture with my Tab S3 :)

    But still, there are some annoying bugs about the picture resolution, a flashlight behavior, ... but yeah it is usable when I take something using slightly lower resolution without the flashlight.

    Also, for now, both the LOS camera app and Snap camera are not working well while Open Camera and Google Camera seem to be working well.

    For now, the major problem is that if I use a flashlight in the camera app at least once, the overall GUI animations slow down even I closed the camera app.

    So, when I publish the camera fixed version, at least I will fix this most bothering thing even though I can't fix it all for the camera.
    11
    Hello all.

    I uploaded the new version, including fixing the power-off mode charging.
    I'm using the LPM binary that is from Samsung for the power-off mode charging. When you plug in the charging cable while the tablet turns off, you can see the original charging screen you might see in the stock firmware. :)

    And I tried to fix the Bluetooth inputs and the OTG drives issues but I couldn't. I can reproduce these problems but I cannot find how to fix them for now. But I can confirm that the wired input devices are working such as a keyboard and a Playstation 4 controller.

    Please check out the first post of this thread. :)
    11
    Great news here. The next release will include the fully-working quad-speakers. :D
    And I also have implemented the audio rotation codes for the screen rotation.

    Actually, I already have used it for about 3 days, and I think it looks working flawlessly.
    And, for the alternatives of the Dolby Atmos, I have tested with the Dolby Digital Plus module with Magisk and I can say that it is awesome. :cool:

    The new release will be uploaded before this weekend. :)
    11
    Long time no see. :)

    I uploaded the new version that contains the November security patch and fixed arrow keys working on the keyboard inputs.
    Yeah, sorry for it isn't a big update, I know there're lots of bugs remaining. 😅

    Currently I have been investigating upgrading our kernel as I said before.

    I did start the Android kernel studying to know what CAF based kernel or AOSP based kernel means, and how the other people merge the latest tags from the official repositories to the vendor-providing kernel base.
    And now I think I'm managed to know the very small piece of that Android kernel world.

    First, I found that there is no problem with using the Bluetooth keyboard on the stock kernel for LOS, which hasn't any patch including the upstream Linux patches and/or any tunes.
    Yeah, this is interesting, it can be small evidence that the current kernel is somewhat broken at least for the Bluetooth.

    My first plan was to migrate Samsung codes to the LineageOS MSM8996 kernel. But after a few weeks, I realized that it isn't for humans. There are so many flags and tweaks they put in. Even some codes are not marked whether this code is from Samsung.

    So I changed my plan, to get CAF tags onto the top of the CTD1 kernel that is the latest kernel base of the T825 model. Fortunately, I could merge some modern CAF tags successfully. But in that progress the camera got broken. :unsure:

    Then, I tried to merge the AOSP tags for getting the proper upstream Android/Linux patches and security patches. I could merge until early 2020, that is also containing 3.18.140 upstream Linux patches. But I couldn't merge the latest patches like the one just published last month. It makes the tablet not boot.

    I think it is quite hard work on our tablet because Samsung puts various un-listed patches onto the top of the 3.18.115 kernel but they didn't apply the upstream Linux patches. So, for example, when I merge the 3.18.116 tag to the current 3.18.115 kernel, I couldn't accept all the incoming changes because some files in the current kernel base are much more modern files. o_O This makes me get frustrated.

    But it doesn't mean it is impossible. Some people out there are doing this job now so there will be something more I don't know yet about the Android kernel development. If someone has experience or knowledge of upgrading vendor kernel, please join our Telegram channel and let's discuss that.