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

Search This thread

yagueitor

Member
Aug 6, 2022
11
0
Could you please try installing Nova Launcher first and set it as default launcher? I dont know but maybe that could help.
Yep, done that already, no changes. I've freezed pixel launcher with titanium backup and the bar is gone.... but recent apps button ha stopped working lol.
Yes, you can but you need the ff:
1. Magisk with zygist enabled
2. Universal safetynet fix installed (magisk module)
3. Magiskhide props config (magisk module). You will need a terminal emulator to configure magiskhide. In the config select Samsung Galaxy Tab S3 as your device.
4. Reboot afterwards. Give google play store a few hours (this is consistent in my case). Then later search Netflix in playstore you will find it there.
Done it yesterday, i just had to wait a few hours, it's working now hehe.
 

Stogie87

Senior Member
Oct 3, 2015
1,069
485
Berlin
Yes, you can but you need the ff:
1. Magisk with zygist enabled
2. Universal safetynet fix installed (magisk module)
3. Magiskhide props config (magisk module). You will need a terminal emulator to configure magiskhide. In the config select Samsung Galaxy Tab S3 as your device.
4. Reboot afterwards. Give google play store a few hours (this is consistent in my case). Then later search Netflix in playstore you will find it there.

Or you just install Aurora Store and install it from there. ;)
 
  • Like
Reactions: jtrakx

solemgar

Member
Jan 15, 2016
18
1
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 !
 

yagueitor

Member
Aug 6, 2022
11
0
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 !
Performance with this rom is like using a brand new tablet.
Stock android on this is bloody laggy.
 

solemgar

Member
Jan 15, 2016
18
1
T825:
Atmos idk as I don't hear any difference when turning on or off.
OTG works. (@Awesometic imho you can delete that on the "What's not working" list)

How did you test OTG? I still can't use it 🤔

@Awesometic changed them two lines (RX1+2 Mix Digital Volume) back to original values as I have the impression that when using speakers these are quite over amplified.

Ah okay, will not change the speaker volume (RXx Mix Digital Volume)
 

Attachments

  • IMG_20220809_115648.jpg
    IMG_20220809_115648.jpg
    155.4 KB · Views: 35

bradzand

New member
Jul 9, 2008
2
2
Samsung Galaxy Tab S3
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?
 

908070

Member
May 26, 2020
9
1
Hi,
TWRP does not run for me.
ODIN installs without errors, but the recovery remains stock.
Where could be the problem?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I have an SM-T820. Installed twrp-3.6.0_9-0 and flashed this rom. Magisk 25.2 (25200) app is installed but it's not rooted yet. Ramdisk shows Yes. Only option I have is to "select and patch a file". I tried extracting the boot.img from this ROM, patching it, then flashing in TWRP but that broke the kernal and resulted in a bootloop. ADB won't recognize the device in download mode. I've reflashed TWRP in Odin, then reflashed this ROM in TWRP, and it boots normal again.

    Can someone please explain how to get root with Magisk or point me to a guide that works?
    Install Magisk using TWRP. Just rename magisk.apk to magisk.zip. After reboot, the magisk will update to latest version and there will be an option to activate root. No need to use "select and patch a file."
  • 21
    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.
      • On webcam chat apps, there is a vertical green bar and the color is not properly displayed.
    • Audio bugs
      • No sound for the microphone and speaker in voice calls, such as the regular phone call or voice chat with a meeting app.
    • 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
    • LOS17.1) @Valera1978 for his amazing previous work including his MSM8996 kernel
    • LOS18.1) @supermike86 and @samsuffit for testing LineageOS 18.1 for T820, which is I don't have one
    • LOS18.1) @bmwdroid and @cherepanov for confirming the LTE works
    • LOS18.1) @sebmue for letting me know that the useful information for palm rejection, and @ghostwheel for sharing its working source codes on Android 9
    • General) @switchgott for helping me in the development discussion and creating Telegram groups
    • General) All from our Telegram discussion channel, @EonOfBlack , Sands, David Becker, ...
    • LOS18.1) @LuK1337 for giving me a hint to fix the quad-speakers
    • LOS19.1) @followmsi , @html6405 , @ThE_MarD for giving me a hint to bring up Android 12
    • LOS19.1) @masdaster for the fix of MDFPP Keystore on our device
    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. :)
    9
    ## Changelogs
    • 2022. 9. 23
      • Synced with the latest LineageOS 19.1 repositories
        • Security patch by September 5, 2022

    • 2022. 8. 15
      • Synced with the latest LineageOS 19.1 repositories
        • android-12.1.0_r22
        • Security patch by August 5, 2022
      • About Keystore, switch to use MDFPP skeymast files again.
        • This will break your lock screen. Please remove `/data/system/locksettings.db` file using TWRP, then lock screen will be fixed and your biometric information will be removed. Please reset your biometric lock method again. Sorry for the inconvenience.
        • Thank you for the idea and contribution for the proper use of our MDFPP Keystore, @masdaster :)
    • 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. :)