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

[ROM][UNOFFICIAL][11][EAS][SM-T820][SM-T825][2021-12-19] LineageOS 18.1 for Galaxy Tab S3

Search This thread
D

Deleted member 11883955

Guest
Try to erase play services and google play data, it doesn't matter too much if you chance the device fingerprint for another model
I erased play services, google play data and the cache and made a reboot.
Unfortunately the problem still persists
 
D

Deleted member 11883955

Guest
Try an older Playstore version from apk.mirror

Don't update it

unfortunately the problem persists.
no matter what I try, the safetynet check in magisk always shows ctsProfile not passed

I tried following Tests:

  1. TWRP Recovery - Format the whole system, data, cache partitions using the format menu.
  2. TWRP Recovery - Install LineageOS 18.1 for Galaxy Tab S3
  3. TWRP Recovery - Install GAPPS Pico for ARM64, Android 11 Version 20211109 (also Tried Versions: 20211005, 20211104, 20211103, 20211102, 20211008, 20210901
  4. TWRP Recovery - Install Magisk 23
  5. Reboot System
  6. Magisk - Activation of MagiskHide --> Safetynet Check --> ctsProfile not passed
  7. MagiskHide - Activation for Google Play Services --> Safetynet Check --> ctsProfile not passed
  8. MagiskHide - Activation for Google Play Store --> Safetynet Check --> ctsProfile not passed
  9. Magisk - Activation of Hide the Magisk App --> Safetynet Check --> ctsProfile not passed
  10. Magisk - Install Riru Version 26.1.3.
  11. Reboot System
  12. Magisk - Install Universal SafetyNet Fix from kdrag0n, Version 2.1.1.
  13. Reboot System
  14. Magisk --> Safetynet Check --> ctsProfile not passed
  15. Magisk - Install MagiskHide Props Config Version 6.1.2-v137
  16. Termux - 2 (Force BASIC key attestation) - d (pickup value from device list) - 26 (Samsung) -
    90 (Galaxy Tab S3 LTE - SM-T825) Because SM-T820 was not in List
  17. Reboot System
  18. Magisk --> Safetynet Check --> ctsProfile not passed

    Between every step from 6 to 17 i cleared Cache and Data from Play Services and Play Store.
I don't know why ctsProfile not passed is always displayed.
Do you have any ideas?
 
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.
 
Last edited:

LedgendaryEpics

Senior Member
Jun 14, 2018
96
22
god speed. hope we could get some support for this delicious tablet, I heard android 12l will focus on tablets so who knows...
 

Sage

Senior Member
Dec 12, 2005
1,523
347
AU
Xiaomi Mi 11
just wanted to say thank you! loving this rom so much faster than stock and for what i use it for it its perfectly stable!
 
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. 😀
 
Last edited:
@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 :)
 
  • Like
Reactions: bmwdroid
@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.
 
  • Like
Reactions: Awesometic

hugo.rila

New member
Dec 3, 2021
2
0
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.
First, I have to say thanks! It's amazing your job and effort with this device. Everything that I've tested worked well. I just had a problem with screen lock after plugging in the charger. No advice or stuff like that, only one black screen. I forced a reboot, and put again the charger.
Thank you! You're the man!
 

Eutono

Member
Mar 23, 2019
5
2
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 !!
 
.... I just had a problem with screen lock after plugging in the charger. No advice or stuff like that, only one black screen. I forced a reboot, and put again the charger.....
Just tested myself.
Screen stays black when plugged in as it did on previous ROMs.
Waking up is no problem after a minute.
After which period of time did you encounter this?
Testing longer time now.

Edit 1h later: still no problem.
Fingerprint sensor seems to be working better as well compared to previous ROM.
 
Last edited:

LedgendaryEpics

Senior Member
Jun 14, 2018
96
22
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
 
@Awesometic didn't find formating option for inserted USB stick. Just being curious. Wasn't necessary.
Is there one or only in TWRP?
Long pressing on any drive symbol just offers option to open in file manager.
Ejecting works normally.
 

Attachments

  • Screenshot_20211204-185248_Trebuchet.png
    Screenshot_20211204-185248_Trebuchet.png
    91.3 KB · Views: 28
  • Screenshot_20211204-190944_Trebuchet.png
    Screenshot_20211204-190944_Trebuchet.png
    170.2 KB · Views: 28

hugo.rila

New member
Dec 3, 2021
2
0
Just tested myself.
Screen stays black when plugged in as it did on previous ROMs.
Waking up is no problem after a minute.
After which period of time did you encounter this?
Testing longer time now.

Edit 1h later: still no problem.
Fingerprint sensor seems to be working better as well compared to previous ROM.
I installed the rom and used it within an hour. And it happened once, as I reported. Until now, no other things. The ROM is smooth and very responsive. It's been a great experience.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Had to create an account just to thank you for this! Managed to breathe new life into this old tablet of mine. Everything works smooth and all the lag is gone.

    I had some issues with OpenGApps in the beginning, as I got stuck into a "Checking Updates" -> "Getting Info" loop with the setup crashing all the time, but got past it by not connecting to a network at first and copying my account to the tablet from my phone. Then I had to update everything (Most importantly Android System WebView, which produced some errors at first) and after that it was smooth sailing. So no real errors from your work, really.

    Everything I need works now. So thank you for your work!
    1
    Just an idea I've been thinking about, but maybe it's possible to adapt the new vendor + kernel implementation into something similar/exact replica of valera's old broken treble. The implementation was 100% alright, it's just that the kernel and vendor sources were awful
    1
    How do i configure the s Pen Button? There was a menu in Stock rom, when i pressed the Button...
    Greetz Daniel
    Sorry mate, no chance as Samsung hides s-pen drivers from custom ROM developers.
    Button doesn't/won't work other than on stock.
    Nor does Notes and some other Samsung stuff.
    1
    Just an idea I've been thinking about, but maybe it's possible to adapt the new vendor + kernel implementation into something similar/exact replica of valera's old broken treble. The implementation was 100% alright, it's just that the kernel and vendor sources were awful

    Yeah, sounds interesting. It is worth giving it a try with the new vendor + kernel implementation. 🤔
    1
    Was this part of the new update?

    Yeah, That option is now available from the last release.
  • 31
    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
    • WiFi display
    • 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
    • Hotspot
    • SELinux permissive
    • Hardware encryption
    • 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 11 and 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
    • Fast-charging won't work properly, it sometimes works but most of the time it won't
    • Sometimes 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
    • The tablet rarely reboots with a GMS related error
    • Unlocking the lock screen can make tablets not usable sometimes (black screen)
    • CTS profile will not be fixed (excepts some distributions that have some fixes for CTS profile)
    • 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
    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.
    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. :)