• 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
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. 😀
 

xpil

Senior Member
Nov 14, 2016
89
7
First of all I would like to thank Awesometic for the excellent job. I have installed the previous to the last rom and my t825 works continuously for 1 month without any problems at all. Two things I had to change were to follow a procedure I found on the internet for otg to work properly ,and a procedure I found (using magisk) to make the t825 pass safetynet tests. Now my tablet is certified and fully functional.

I need though your help PLEASE. I want to update the tablet with the latest ROM. The one with the new kernel. I saw that I have to wipe system and cashes. Do I have to reinstall and gapps because of this? Is the tablet going to be certified after the installation? Or I have to repeat the procedure to recertify t825?
Thanks in advance...
 
... saw that I have to wipe system and cashes. Do I have to reinstall and gapps because of this? Is the tablet going to be certified after the installation? Or I have to repeat the procedure to recertify t825?
Thanks in advance...
At least I did flash them together with the ROM.
You could try without of course.
I don't care about "safety net" so idk.
 

am2013

Member
Dec 27, 2012
27
2
@Awesometic : I still have the same issues with the secondary/non admin user as described in my post https://forum.xda-developers.com/t/...-18-1-for-galaxy-tab-s3.4293069/post-85588047

Will you be able to fix this issue somehow. It looks like a permission issue for non primary users as the system shows that there is unsufficient space. As a hint which may help to localize the issue. When trying to start amaze file manager as a secondary user it will instantly crash with a file I/O exception. Please have a look. I can provide additional information if needed.

BTW, with the last version the WIFI MAC was changed. Not sure if this is on purpose or not.
 

xpil

Senior Member
Nov 14, 2016
89
7
Awesometic, Could you please suggest how to flash your latest ROM over the previous one??
Thanks again for your dedication and the excellent job!
 
@Awesometic : I still have the same issues with the secondary/non admin user as described in my post https://forum.xda-developers.com/t/...-18-1-for-galaxy-tab-s3.4293069/post-85588047

Will you be able to fix this issue somehow. It looks like a permission issue for non primary users as the system shows that there is unsufficient space. As a hint which may help to localize the issue. When trying to start amaze file manager as a secondary user it will instantly crash with a file I/O exception. Please have a look. I can provide additional information if needed.

BTW, with the last version the WIFI MAC was changed. Not sure if this is on purpose or not.
Ah okay, will reproduce that issue on my device too.
But for now I'm focusing on the kernel upgrades for battery improvement and better UI experience. Through that work, I might fix the Android OS side issues too. So please test again later with the upcoming kernel versions. :)
 
Last edited:
Sorry but I could not find how to update in the post you sent neither in the posts close to it.

Is there some set of instructions? I really want to update mine.
Awesometic, Could you please suggest how to flash your latest ROM over the previous one??
Thanks again for your dedication and the excellent job!

Dirty flashing will work. This means, just flash the new version using TWRP, and wipe caches.
But moving to F2FS requires you to format the current data partition. So please be aware of that before continuing. Currently, F2FS is an option that has better I/O performance but a little bit unstable than EXT4, very relatively.

Quoted here what "dirty flashing" means from a Reddit post.
A "dirty flash" refers to the process of flashing a new version of your ROM over the top of the one you have, without using the "Wipe Data/Factory Reset" option in recovery. Even if you intend to dirty flash the update, you should always wipe cache and dalvik cache.

  1. Wipe Data/Factory Reset: This option erases all data on the device. Every application, and all data generated by those applications, will be erased. If you do not wipe data, all the data files generated by every app on the system will persist through an upgrade. This includes the data files generated by core system apps, like the phone dialer, the Android UI, its option menus and core features. Remember, everything you do on Android is an application that generates data! NOTE:The storage you see when you connect to USB will not be erased.
  2. Wipe Cache: Every application on the system, even those that run things like your UI and the options menus, generates cache files. These cache files are more or less unique to the current installation of Android you are using, and are generated dynamically. These cache files help Android load and run faster. When changing ROMs or updating to a new version of a ROM, you should always wipe the cache partition, or you're gonna have a bad time: Force closes, boot loops and sluggish performance are just some of the perils that await you.
  3. Wipe Dalvik Cache: Android executes programs inside of software system called the "Dalvik Virtual Machine." The DVM interprets and runs APK files for Android. Dalvik maintains its own cache to again improve performance for your device by offering faster app loading and execution. The Dalvik Cache is again unique to the current installation you are running, and it should always be wiped whether you're installing a new ROM or simply updating versions.
 
  • Like
Reactions: namitutonka

xpil

Senior Member
Nov 14, 2016
89
7
Dirty flashing will work. This means, just flash the new version using TWRP, and wipe caches.
But moving to F2FS requires you to format the current data partition. So please be aware of that before continuing. Currently, F2FS is an option that has better I/O performance but a little bit unstable than EXT4, very relatively.

Quoted here what "dirty flashing" means from a Reddit post.
Performed dirty flash but kept EXT4. Everything works fine till now.
Thank you very much for the perfect ROM and your help
 

UberMorgott

New member
Dec 9, 2021
2
0
Great job. All 4 working speakers have brought life to this tablet.
Found something else that doesn't work:
The cover is a book. The screen does not go out and does not light up when opening and closing the lid.
 
Great job. All 4 working speakers have brought life to this tablet.
Found something else that doesn't work:
The cover is a book. The screen does not go out and does not light up when opening and closing the lid.
Yeah, while I was upgrading the kernel to merge the upstream patches seems like I broke that feature. I'm using a flip cover case too, so that is quite an annoying bug :confused:

I found which function handles that flip cover flips, and checked that function does listen to the status (opened and covered), but the screen is not actually responded by that function. I'd like to fix this issue too.
 
  • Like
Reactions: Anderleanderle

UberMorgott

New member
Dec 9, 2021
2
0
Yeah, while I was upgrading the kernel to merge the upstream patches seems like I broke that feature. I'm using a flip cover case too, so that is quite an annoying bug :confused:

I found which function handles that flip cover flips, and checked that function does listen to the status (opened and covered), but the screen is not actually responded by that function. I'd like to fix this issue too.
Thank you for the answer, we are all following your progress!)
 

franzli

Senior Member
Mar 15, 2010
288
61
Hi, this sounds like a great ROM!

I've got one question regarding Wifi Display/Miracast. The changelog mentions Wifi Display was removed in v. 2021.8.13. Is this a temporary state of affairs or is it a general restriction (maybe due to Google pulling support for Miracast in stock Android)?
I'm asking because I rely on Miracast when using my tablet for teaching, so if this feature is permanently disabled, unfortunately I won't be able to use this ROM. But if there's a chance the feature comes back at some point, I'd love to try it out!

It's so annoying that Google decided to abandon Miracast claiming that "it's not widely used" and that one should use their stupid Chromecast instead, when the Chromecast clearly doesn't allow you to do what Miracast can do, namely connect to any Miracast enabled device (or use the Wireless Display dongle) and directly cast to it without the need for internet access. Sorry for ranting, but I just want preempt suggestions of Chromecast as an alternative - I got one of those and it doesn't work without connecting it to some sort of network first, which makes it largely useless in most mobile teaching environments. Using a phone as a hotspot is, to my mind, no alternative - why should I burn through battery (and data?) on an extra device when there should be no need for internet access in order to project local data to a local device in the first place? (Imagine an HDMI cable that only works as long as it can access the google servers :p )
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    Hello.

    I uploaded the new LineageOS 18.1 release with lots of improvements.

    Now we're using the EAS kernel, so I changed the default CPU governor to schedutil.
    And I fixed flip cover working, and fixed aptX/aptX HD codec on Bluetooth media playback, and also fixed WiFi display.

    But there may be some existing issues still remain like the camera preview issue on Zoom app, supporting the PS4 controller, and so on. 😅

    Enjoy, and let me know if there's an issue. :)
    3
    How is the EAS Kernel compared to your custom one? I noticed very fast performance is it worth updating?
    The other Kernel made my tablet almost as fast as my phone! I was surely impressed.
    Despite the issues after using it for a few days I fell in love.

    I can't say that how much better it is in number.
    But I'm satisfied with the current smoothness. :)
    The updated kernel involves not only EAS but also some optimizations including memory performance than before.
    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
    Do I need an SD card to install or will it work with internal memory? My SD card slot doesnt work…

    You can install a custom ROM using ADB sideload in TWRP. SD card is not necessary.

    Turn on the ADB sideload mode in TWRP then enter `adb sideload rom_name.zip` command to flash.
  • 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. :)