[ROM][UNOFFICIAL][12L][EAS][SM-T820][SM-T825][2022-07-15] LineageOS 19.1 for Galaxy Tab S3

Search This thread

MachineMasher

Member
Sep 8, 2021
24
12
OK, I got lineage-19.1-20220611-UNOFFICIAL-gts3lwifi.zip working on my SM-320 with a modified version of FlameGApps-12.1-basic-arm64-20220612.zip, and have the two column display in settings working too (@pooyab, you may be interested in this, because I'm hoping it solves the problem you raised before!)

The Camera is working perfect with the default camera app, but I have the same issue with the camera in Zoom as I had in the LineageOS 18.1 version at https://forum.xda-developers.com/t/...-18-1-for-galaxy-tab-s3.4293069/post-86517463, with a green bar being displayed on the left of the screen and the colour being distorted on the rest of the screen.

I also have the same same issue with transferring files I referenced at https://forum.xda-developers.com/t/...-19-1-for-galaxy-tab-s3.4418855/post-86778643, with all the USB options in the top pulldown menu being disabled. The workaround referenced in that post still works.

To make this work with FlameGApps-12.1-basic-arm64-20220612.zip with two column display working, I did the following:
1. Delete the following files from the ZIP file:
tar_gapps/AndroidMigrate.tar.xz
tar_gapps/GoogleBackupTransport.tar.xz
tar_gapps/GoogleRestore.tar.xz
tar_gapps/SetupWizard.tar.xz

2. Replace installer.sh in the ZIP file with the version at https://ufile.io/6rqcwk07 (do compare them first to see what's changed - this is the same installer.sh as was used by the modifed version of FlameGApps referenced by Awesometic in the first alpha). The link to this file will expire on July 13th 2022. Does anyone have a suggestion on how I can post the file in a longer lived location?

3. Wipe the device and clean flash both LineageOS and FlameGApps on a clean install WITHOUT doing a reboot between them.

EDITS: Added links to my previous posts about issues and updated the link to installer.sh because I was having trouble attaching the file.
 
Last edited:

wakka1

Member
Jul 8, 2011
9
0
Hello ,For a new user, is it recommended to install lineage 18.1 or 19.1 now? Also what is Selinux permissive and will some apps no longer work if it doesn't?
 
Hello ,For a new user, is it recommended to install lineage 18.1 or 19.1 now?
My T825 is on 19.1 and I'm quite satisfied.
Imho better than 18.1 anyway.
Also what is Selinux permissive
Amazing what you can find when searching, isn't it? 😉
and will some apps no longer work if it doesn't?
Might be although I never found one.
 

m18735714399

New member
Jun 23, 2022
1
0
thanku do it。now my t820 headphone jack audio is smaller than Samsungos 30%,how fix it
 
Last edited:

jtrakx

Member
Apr 22, 2013
29
1
Thank you for the report. I will increase headphone volume in the next update.



Is USB-C DAC working? I didn't know that :)
Thank you very much Awesometic for this very nice and stable ROM. I am so delighted to know from you that updates will be coming soon. Oh your so great!

I just observe that using headphone jack and turning off the Dolby ATMOS while a music player is running (e.g spotify, deezer, etc.) will significantly decrease the volume. Then turning it (Dolby) back on while the music player is still running will not restore to lost sound volume. I just set the Dolby ATMOS permanently to auto and not touching it so as not to affect the music volume. BTW my workaround is to install the AML + VIPER4Android. The sound volume and quality becomes very acceptable.

I would also like to mention the AOSP keyboard bug. When the theme is set to Material You, the AOSP keyboard will not display properly the number pad. This does not happen when other theme is selected. I hope this will be addressed in the coming update.

Thanks again to you!
 

jtrakx

Member
Apr 22, 2013
29
1
OK, I got lineage-19.1-20220611-UNOFFICIAL-gts3lwifi.zip working on my SM-320 with a modified version of FlameGApps-12.1-basic-arm64-20220612.zip, and have the two column display in settings working too (@pooyab, you may be interested in this, because I'm hoping it solves the problem you raised before!)

The Camera is working perfect with the default camera app, but I have the same issue with the camera in Zoom as I had in the LineageOS 18.1 version at https://forum.xda-developers.com/t/...-18-1-for-galaxy-tab-s3.4293069/post-86517463, with a green bar being displayed on the left of the screen and the colour being distorted on the rest of the screen.

I also have the same same issue with transferring files I referenced at https://forum.xda-developers.com/t/...-19-1-for-galaxy-tab-s3.4418855/post-86778643, with all the USB options in the top pulldown menu being disabled. The workaround referenced in that post still works.

To make this work with FlameGApps-12.1-basic-arm64-20220612.zip with two column display working, I did the following:
1. Delete the following files from the ZIP file:
tar_gapps/AndroidMigrate.tar.xz
tar_gapps/GoogleBackupTransport.tar.xz
tar_gapps/GoogleRestore.tar.xz
tar_gapps/SetupWizard.tar.xz

2. Replace installer.sh in the ZIP file with the version at https://ufile.io/6rqcwk07 (do compare them first to see what's changed - this is the same installer.sh as was used by the modifed version of FlameGApps referenced by Awesometic in the first alpha). The link to this file will expire on July 13th 2022. Does anyone have a suggestion on how I can post the file in a longer lived location?

3. Wipe the device and clean flash both LineageOS and FlameGApps on a clean install WITHOUT doing a reboot between them.

EDITS: Added links to my previous posts about issues and updated the link to installer.sh because I was having trouble attaching the file.
I just did what you have instructed, but still no two columns in the setting. Anyway, the installation went smooth and trouble free. clean install everything using F2FS. Two weeks in use and very stable so far.
Thanks!
 

am2013

Member
Dec 27, 2012
31
4
Hi all,

the ROM works really well for me. No issues so far. Many thanks to @Awesometic. I have one question concerning device encryption. Is it working? Can I just enable it? If it is ok to enable it, do I have to do it for admin and secondary users? Will only data be encrypted or also system?

Thank you and kind regards,

am
 

LedgendaryEpics

Senior Member
Jun 14, 2018
176
41
Anyway to implement Monet settings in wallpaper within the next couple updates, or are those settings closed sourced to pixel?
 

MachineMasher

Member
Sep 8, 2021
24
12
I just did what you have instructed, but still no two columns in the setting. Anyway, the installation went smooth and trouble free. clean install everything using F2FS. Two weeks in use and very stable so far.
Thanks!
That's really strange. The two column display in settings just happened for me any time I flashed LineageOS and FlameGApps without a reboot in between. I didn't have to do anything special to enable it.

When I installed WITH a reboot in between, the two column display didn't work.

So if you used the same version of FlameGApps as I mentioned and you didn't reboot between LineageOS and FlameGApps, I have no idea why you wouldn't get two column display. :(
 

wakka1

Member
Jul 8, 2011
9
0
Can someone help me please.i unlocked bootloader in developer option, flashed twrp using odin, tried to install lineageos rom, but it froze for 2 seconds before rebooting to twrp again..did the wipe and now my tablet is into infinite bootloop.
TWRP keeps giving me error 1 and error 8 when i do wipe now sometimes
 

wakka1

Member
Jul 8, 2011
9
0
Reinstall trwp with Odin not only wipe but format system and data, then install again. Worth doing 19.1 runs very smooth
I already tried reinstalling twrp multiple times, both 3.60 and 3.52 versions. i get errors when i try to do anything, Do i just need to unlock bootloader and nothing else? it feels like twrp can't access system files.
nvm, i got it working!
 
Last edited:

Top Liked Posts

  • 1
    I've had the same issue since installing the alpha, these instructions helped. Thanks!
    Thank you, finally the solution!
  • 7
    The new version is uploaded.

    With this version, I have added support for Sony DualShock 4 gamepad. I confirmed it's working, simply using the touchpad on it and the buttons and it is quite interesting.

    And I increased the headphone jack volume too. I think now it gets enough to listen to something but I need feedback from the users.

    Check out changelogs, and enjoy the new ROM.
    3
    Hi,
    a few days ago I managed to fixed hardware encryption. I've encrypted my own tab and it's performing well. Additionally I applied a patch regarding palm rejection. When using the pencil with a handwriting keyboard, sometimes the keyboard closes because the pencil was not close enough to the display to get recognized. This should be better now.

    My compiled version is based on the sources mentioned in the first post and on changes from these repos: https://gitlab.com/android229

    Here is the link to my cloud with the build: https://1drv.ms/u/s!AgBELbH5Ycnt0RKSPGXy2r0FXd_i?e=F4OVNL

    Of course all credits go to @Awesometic! He did a great job! For future builds we will merge our sources. But for now you can also use my build. The sources are mostly the same (based on Android 12 R11). So dirty flashing should be fine.
    3
    And, I will increase the speaker loudness by about 20~30%.
    @Awesometic , I don't have this device, but this should let users increase/decrease the volume themselves instead of you having to build new image.

    Code:
    # boot into TWRP
    # click on mount, touch system
    # on pc with usb cable plugged in, let's get mixer_paths_tasha.xml
    adb pull /system/vendor/etc/mixer_paths_tasha.xml
    # bring up text editor on PC and edit mixer_paths_tasha.xml
    # users should look at
    # https://github.com/awesometic/android_device_samsung_gts3l-common/commit/ae49ee8c3859d0f378688611a4f4ffbcb68fbdb7
    # to see what lines of code were modified and make modifications as desired to headphones
    # save file in PC
    # push back to tablet
    adb push mixer_paths_tasha.xml /system/vendor/etc/mixer_paths_tasha.xml
    # reboot back into OS

    For those who want to increase speaker loundess, you probably need to change

    "RX1 Mix Digital Volume"
    "RX2 Mix Digital Volume"

    from 76 say to 82.
    2
    I would like very much to try this rom as a daily driver (and since it supports encryption), but the lack of selinux enforcing worries me in terms of security . Is there any work towards having full selinux enforcing support? Thanks !

    I'm also interested in this question. Running with selinux=permissive is high risk, and it seems irresponsible that such a large proportion of unofficial ROMs disable selinux. LineageOS makes it mandatory to run selinux in enforcing mode in their official ROMs for good reason.

    With selinux disabled, it is trivial for malicious code in an app to permanently root the device and gain full control over it, giving malicious actors the ability to access and exploit your personal information that exists within your other apps or perform other malicious activity without the user knowing. Given that there is a PoC on github that shows how to do this, you can bet that this exploit is already out in the wild.

    @Awesometic, I appreciate and respect that you put a lot of your personal time and effort into this (it's a lot more than I do), but I think this concern is valid. Can you eli5 why you haven't set selinux=enforcing in your builds, and if it is possible, what it would take to achieve this?
    2
    1) Go to default apps and select the Pixel Launcher
    2) Long press the home screen and select Settings
    3) Go to Developer Options
    4) Disable "ENABLE_TASKBAR"
    5) Go back to your previous launcher


    Hope that helps.
    I've had the same issue since installing the alpha, these instructions helped. Thanks!
  • 20
    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
      • Dolby Atmos
      • Headphone/Headset
      • Quad speakers
    • Video playback
      • HDR
    • Camera
    • Microphone
    • Sensors
    • Fingerprint sensor
    • GPS
    • LTE (SM-T825)
    • Hotspot
    • WiFi
    • WiFi display
    • Bluetooth
    • DRM
      • Widevine L1
    • USB ADB/MTP
    • Samsung Doze
    • S-Pen
      • Palm rejection
    • Hardware Encryption
      • MDFPP
    • SD Card
    • Power-off mode charging
    # Untested
    • FBE for userdata
    # What's not working
    • USB OTG
    • SELinux permissive
    • Please see the "Known issues" part of this post

    # Downloads

    ## LineageOS 19.1

    ## Google Apps
    • NikGapps
    • The other Gapps will work too, but I only confirmed that NikGapps working

    ## TWRP Recovery

    # How to install
    1. Unlock the bootloader.
    2. Download TWRP and flash the recovery image via Odin.
    3. Download LineageOS 19.1 for Galaxy Tab S3.
      • Be aware of the board name.
    4. Download GAPPS for Android 12L and the others you want to flash.
    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
    • Camera somewhat buggy
      • The built-in camera application (Camera2) is not working well. You can use another camera application like OpenCamera.
      • Sometimes the camera doesn't work after booting. You can fix that back by just rebooting.
      • After using the camera application, the Torch tile on the quick settings not working. But you can use the camera anyway.
    • 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
    • @followmsi , @html6405 , @ThE_MarD for giving me a hint to bring up Android 12
    10
    Hello all,

    After numerous tries, I could fix the camera and the Bluetooth/Headphone jack audio working.

    The camera is back, but still has some bugs, unfortunately.
    First, we can't use the default camera app, Camera2. It takes a shot but the result is cracked. But we can use a third party app like OpenCamera.
    And, there is something weird on the Torch. After using the camera with the flashlight, sometimes the Torch tile on the quick settings is broken, it just said "camera in use". But we still can use the camera.
    Lastly, sometimes the camera doesn't work at all after rebooting. Fortunately, it is easily fixed by rebooting again. I don't know why it is well.

    Now our audio HAL is built from the source. Previously, we were using audio HAL version 4.0 which is for Android 9 but now we're using version 6.0 which is for Android 11. I can move on to version 7.0, yeah, which is for Android 12, but from this version the configurations have to be modified in many ways so I just pended it.
    I had to supplement some audio configurations because of the compatibility of each version, maybe some audio scenarios were broken compared to our LineageOS 18.1. But I confirmed for most used scenarios like the quad-speaker, Bluetooth audio, headphone jack, and wireless display audio, so in most cases it will work well.

    I think, we can deprecate our LineageOS 18.1 now because our LOS 19.1 has no fewer features than LOS 18.1. :)
    8
    ## Changelogs
    • 2022. 7. 15
      • Synced with the latest LineageOS 19.1 repositories
        • android-12.1.0_r11
        • Security patch by July 5, 2022
      • Added support for Sony DualShock 4 gamepad
      • Increased headphone jack volume by about 20%
      • Updated USB HAL to v1.3
    • 2022. 6. 11
    • 2022. 4. 16
      • Synced with the latest LineageOS 19.1 repositories
        • android-12.1.0_r4
      • Fixed the boot failure issue for some users
        • It is related to the Keystore of the Android system, I did a little compromise to make it work for all users
        • If you are using the first version (220320), you have to clean install to this version or you may fail to unlock the screen , you have to boot into TWRP and remove the file `locksettings.db` under `/data/system` directory. This will resolve the unlock failure issue after dirty-flashing it.
          • Thanks for this information, David Becker. :)
    • 2022. 3. 20
      • Initial release
    8
    ## Special Notes
    • You must do clean-install if you are willing to upgrade from another ROM such as an Android 11 based one
    • I have tested Magisk 24.3 working
      • You can fix SafetyNet using Magisk modules, SafetyNet Fix and PropsConfig
    • You can hide the soft nav buttons on the bottom bar. This is the workaround.
      • 1. Go to "System -> Buttons" and check "Enable on-screen nav bar" to enable soft nav bar temporarily
      • 2. Go to "System -> Gestures" and set "System navigation" to "Gesture navigation"
      • 3. Go back to "System -> Buttons" and check "Enable on-screen nav bar" again to disable soft nav bar and enable hardware key.
    • You can hide the bottom Taskbar. This is the workaround.
      • 1. Go to "System -> Buttons" and check "Enable on-screen nav bar" to enable soft nav bar temporarily
      • 2. Go back using navigation bar and go to the "Buttons" menu again
      • 3. Then we can see the "Enable taskbar" option that we couldn't see before. Disable that option.
      • 4. And disable "Enable on-screen nav bar" option again to use the hardware buttons back.
    8
    Finally I think I found which thing I should look into to fix the camera and the remaining audio things including Bluetooth audio, headphone jack and the audio when screen recording.

    Currently I managed to fix the camera working, which comes with some bugs yet but we can use it.
    But I couldn't fix the audio yet. I found the root cause but don't know how to fix that.

    So, the new one will come and I think it is not so far. If I can't fix the audio for a few days, then I will upload the new release including the working camera. :)