LineageOS 19.1 for SM-T580 (gtaxlwifi) and SM-P580 (gtanotexlwifi)

Search This thread

Dasgandlaf

New member
Jul 2, 2022
3
0
I only had installed lineagoes19 (your build) when I was testing it out, no gapps, no magisk etc.
Hmmm. It seems like this is a hardware problem, because my tablet is really slow, that was also the reason why I wanted to test out a custom rom. I thought that samsung had maybe done some shady stuff with the stock rom to make it slower. I was ignoring the lags until now. I don't know what causes for it to be so slow.
Do you know maybe something which causes this? Cuz I have honestly no idea. (except maybe some broken hardware)

Edit: Ok, something is definitely wrong. I did a geekbench benchmark, with result of:
150 Single-Core Score
887 Mutli-Core Score
Yeah................ This is really slow lollllll
What causes this? Its weird.
 
Last edited:

TALUAtXDA

Senior Member
Nov 8, 2018
451
965
I only had installed lineagoes19 (your build) when I was testing it out, no gapps, no magisk etc.
Hmmm. It seems like this is a hardware problem, because my tablet is really slow, that was also the reason why I wanted to test out a custom rom. I thought that samsung had maybe done some shady stuff with the stock rom to make it slower. I was ignoring the lags until now. I don't know what causes for it to be so slow.
Do you know maybe something which causes this? Cuz I have honestly no idea. (except maybe some broken hardware)

Edit: Ok, something is definitely wrong. I did a geekbench benchmark, with result of:
150 Single-Core Score
887 Mutli-Core Score
Yeah................ This is really slow lollllll
What causes this? Its weird.
Hmm, I see.
For Geekbench 5 scores, unfortunately, I can't get scores for reference here. It seems that on 19.1, as Geekbench consumes too much RAM, it gets killed part way through tests.
I wouldn't expect to not have fairly low scores on any modern benchmark with our fairly low end (by todays standards) hardware, but yeah, I'm totally uncertain on what could be expected for any scores.

If it is indeed hardware at fault, my best guess for a possible cause is that the internal eMMC storage chip might be failing and performing badly. It might be worth running some read/write storage speed test app and seeing what it reports, although I don't have any suggestions for one. No other ideas apart from the eMMC storage for hardware.
 

Dasgandlaf

New member
Jul 2, 2022
3
0
Ok, gotchu. Thanks for your help, I'll look into that!
Also, just so I know, how is the performance of this rom for you?
 

dagbdagb

Member
Aug 30, 2010
19
7
Installed twrp, latest build and a custom opengapps package. Looks good. Only annoyance so far is that Android Setup insists on starting up, and for some reason is unable to detect that I am already connected to wifi.
I can force close and disable Android Setup of course. But is there a proper fix?

Ninja edit: Thank you, @TALUAtXDA and friends.
 

Pat33170

Member
Mar 19, 2021
17
2
Hello, once again new release working perfectly with NikGapps core. Issue on power off is solved and nav bar definetly removed with setup. Version 19.1 adopted to replace 18 one.
Thanks a lot @TALUAtXDA for giving us the possibility to have this tablet alive with last Android functionalities. You help us, you help the planet...
 

TALUAtXDA

Senior Member
Nov 8, 2018
451
965
Ok, gotchu. Thanks for your help, I'll look into that!
Also, just so I know, how is the performance of this rom for you?
Alright, you're very welcome.
On my own tablet (with MicroG), performance is quite good. Performance might suffer a little with fairly heavy tasks and more heavier multitasking, but it's still overall pretty good.
Installed twrp, latest build and a custom opengapps package. Looks good. Only annoyance so far is that Android Setup insists on starting up, and for some reason is unable to detect that I am already connected to wifi.
I can force close and disable Android Setup of course. But is there a proper fix?
Your opengapps package might've replaced the Android Setup package with its own variant, and that might cause your issue, although I'm totally uncertain. Other than that, I don't have any ideas. Any issues like that haven't ever been reported before and I haven't ever encountered anything like that, either, so there isn't any proper fix I'm aware of, unfortunately.
 
  • Like
Reactions: ipdev

ipdev

Recognized Contributor
Feb 14, 2016
1,861
1
3,292
Google Nexus 10
Nexus 7 (2013)
Installed twrp, latest build and a custom opengapps package. Looks good. Only annoyance so far is that Android Setup insists on starting up, and for some reason is unable to detect that I am already connected to wifi.
I can force close and disable Android Setup of course. But is there a proper fix?

Ninja edit: Thank you, @TALUAtXDA and friends.

Alright, you're very welcome.
On my own tablet (with MicroG), performance is quite good. Performance might suffer a little with fairly heavy tasks and more heavier multitasking, but it's still overall pretty good.

Your opengapps package might've replaced the Android Setup package with its own variant, and that might cause your issue, although I'm totally uncertain. Other than that, I don't have any ideas. Any issues like that haven't ever been reported before and I haven't ever encountered anything like that, either, so there isn't any proper fix I'm aware of, unfortunately.

OpenGApps does not replace lineage setup wizard but..
Google and Linage setup wizards become a bit intertwined.

I know there is some issues with the Google setup wizard so, it might be causing the issue.
Normally I skip though the initial setup and do it off-line.
Then after adjusting what I need to, connect to the internet and finish the setup.
On Android 12L (SDK32) Google setup wisard might hang on updating apps.
If so, just close and restart finnish setting up.​

Cheers. :cowboy:
 
  • Like
Reactions: TALUAtXDA

probasxose

New member
Jul 6, 2022
1
0
Hello first of all, thanks you, it is a great work

I have installed the ROM perfect, then I have installed flameGapps 12.1 It is Running perfect thanks very much!!!
 
Last edited:

pressor

New member
Jul 5, 2022
2
0
Hello ! I just tried your build and it work really great ! Thank you for your amazing job !

Only ANT+ is not working on my side, do you have any idea why ?
I tried with ANTtester which show "built-in ant detected : NO" when on the Samsung's official build it is working for information :).
I also tried to install plugin as "ANT radio plugin" but did not solved the issue...
Thank you !
 
Last edited:

alejim

Member
Sep 1, 2013
42
6
Hello. Once the latest version is installed, I have realized that when I turn on the tablet, the image stays in vertical and not in landscape. It does not rotate automatically despite being activated. What can be)
 

Uluru25

Senior Member
Nov 27, 2016
281
109
Samsung Galaxy S7
Samsung Galaxy A6
Help needed!
Just upgraded from 18.1 to 19 but when trying to re-root with Magisk v23 (I need this version to have EdExposed for XPrivacyLua) I always face a boot loop. I tried both methods (renaming the .apk to .zip and flashing via the recovery => bootloop as well as extracting the boot.img from the LOS19 rom, patching it via the Magisk app and then flashing the patched boot.img via the recovery => bootloop). Does it make a difference that I tried to flash the patched boot.img via recovery and not via fastboot commands? Any other hints or advice for me? Thx!
 

TALUAtXDA

Senior Member
Nov 8, 2018
451
965
Help needed!
Just upgraded from 18.1 to 19 but when trying to re-root with Magisk v23 (I need this version to have EdExposed for XPrivacyLua) I always face a boot loop. I tried both methods (renaming the .apk to .zip and flashing via the recovery => bootloop as well as extracting the boot.img from the LOS19 rom, patching it via the Magisk app and then flashing the patched boot.img via the recovery => bootloop). Does it make a difference that I tried to flash the patched boot.img via recovery and not via fastboot commands? Any other hints or advice for me? Thx!
Magisk v23 (if I remember correctly) wouldn't have any support for Android 12, and so it would certainly cause a bootloop. For 12, you must use the latest version of Magisk (downloadable from here as the only official source for reference).
Also, remember, we don't have fastboot, only Samsung's download mode.
 
Last edited:
  • Like
Reactions: Uluru25

Uluru25

Senior Member
Nov 27, 2016
281
109
Samsung Galaxy S7
Samsung Galaxy A6
Magisk v23 wouldn't have any support for Android 12, and so it would certainly cause a bootloop. For 12, you must use the latest version of Magisk (downloadable from here as the only official source for reference).
Also, remember, we don't have fastboot, only Samsung's download mode.
Thx for your kind remind, will try my luck tomorrow...

Edit: it worked! But i had to manually delete the previously installed magisk modules in /data/adb/modules as well as the edxposed folder in /data/adb.
 
Last edited:
  • Like
Reactions: TALUAtXDA

silas67

Member
Feb 24, 2017
19
2
Good Morning or evening (depending where you are in this world). I just installed this ROM last night. Finally put everything back to what I had before upgrading from lineage18. At first it was reeeeeally slow. I read another user had the same issue. After installing nikgapps and everything else I use. I reinstalled the ROM through TWRP recovery. That seems to have helped the lag a lot. Now my reason for this post is. Is there any way to get rid of the gray bar with the soft keys at the bottom? If I'm watching a video I full screen that gray bar is in the way or if I'm not in full screen that gray bar covers up choice buttons at the bottom that I can see anymore. So far Im enjoying this ROM. Thanks for your hard work.
 

BankiZ

New member
May 7, 2011
2
0
Hey there,

I just installed the ROM and I wanted to share my feedback.

First of all, thanks a millions for bringing this ROM to us in such an easy way! That's fantastic.
I decided to install it because the official stock ROM was super laggy and barely usable, despite the factory reset.

I ran into several issues while installing though.
I first installed it with NikGapps (the `latest` version you can get on sourceforge). While it booted and I was able to setup the tablet, the launcher never came up (the Google setup form crashed at some point near the end). I was able to access the settings via the notification bar and I saw several updates coming from the Play Store, but the launcher wasn't there at all. Impossible to use. I've tested it several times with the same issue.

I then tried installing only Lineage without NikGapps to test it out, and it worked, but it was super unstable. For example, the native browser wasn't able to access the storage when downloading stuff (Firefox, for example).

Finally, I did a last attempt by chosing a specific release of NikGapps (which is a bit confusing when you're a newbie :D), I chose the SL / stock and I was able to set up and use the tablet normally this time 👍
I got a few glitches, but definitely not important. It seems the tablet is faster, at least I can use it as I would want to use it :) but I didn't use it much yet.

Once again: thanks a lot, this is awesome.
 

MSgtTUSMC

New member
Sep 14, 2020
3
1
Alright, you're very welcome.
On my own tablet (with MicroG), performance is quite good. Performance might suffer a little with fairly heavy tasks and more heavier multitasking, but it's still overall pretty good.

Your opengapps package might've replaced the Android Setup package with its own variant, and that might cause your issue, although I'm totally uncertain. Other than that, I don't have any ideas. Any issues like that haven't ever been reported before and I haven't ever encountered anything like that, either, so there isn't any proper fix I'm aware of, unfortunately.
HI TALUAtXDA. You use MicroG. Where do you get it?. I'm using OpenGapps pico which works pretty good but I'm looking for the best performance. Thanks for all you have done! It's an awesome OS!
 

Top Liked Posts

  • 4
    Thanks for your reply. I have the service disabled until there is a proper fix available.
    Thank you for your efforts and this great ROM
    A proper fix (here on Lineage's gerrit) has now been applied from upstream AOSP to Lineage, and so it will be included in my next releases.
    You're very welcome.

    Indeed my performance problem was due to using too heavy gapps, I have reinstalled using the CORE gapps from nikgaps and the performance is tremendously superior. I think it should be specified in the main post to use minimum gapps. Great job and thanks for this rom @TALUAtXDA
    Excellent.
    I've added a note to use minimal variant gapps packages to the same usability fixes section. Again hoping it won't go unnoticed.
    You're welcome.

    something's wrong with latest build. Special apps detect rom rooted, maybe it's related to public keys and rom signature?
    Not much has changed in the latest build at all, so I'd say there can't be anything wrong like that that's new, unless something has suddenly been added somewhere else that does additional checks, which you'd need to bypass, and is completely out of scope for me.
    As for signing, unless something has been added that checks the build signature, that won't be the cause of any issues, as my builds have always been signed with the public test keys.

    My question is the internal updater not working? Nothing showed up as an update and I checked back here and saw the update so I manually installed it.
    OTA updates aren't setup, and I don't have/know of any place to statically store new builds so I can't set them up.

    Thank you for keeping this old tablet alive.I am facing connection problem in the latest version. The wifi randomly disconnects after sometime. I am using gtaxlwifi
    You're welcome. I don't have any ideas, again not much has changed in the latest build, there could be an external cause. You could send a PM with a log from logcat after a random disconnection for me to look at, and it could give away information for figuring out possible causes.

    Anyone know of an overclocking kernel that works with this? Would love to wake this tablet up a bit
    No, you'd need to make your own, and I wouldn't ever suggest using any published anywhere (if they were to exist).

    They'd get out-of-date quickly from my kernel sources if they're used (unless updates are regularly released), or not have necessary changes for certain things to work properly at all if some other sources are used as a base, as well as not having my updates/general changes.

    Also, most importantly, they could in general cause problems not reproducible with the standard kernels included with my builds (the very reason most other maintainers also discourage use of custom kernels).

    Your only option is undervolting for better battery life and less heat, which is much more worth it. Overclocking any further (since there's already an overclock from 1.586GHz to 1.69GHz) is simply not worth the effort for minimal gains. I'm sure I told you this a long while ago.

    Are there any plans to add LTE too? The tablet i finished today is a 585, but no SIM in it. The other one is a 585 too, but this one uses the SIM for a mobile connection
    Well, now, someone else who got a T585 is trying to bring builds up for it. Hopefully there will be success with it, although as usual, no guarantees for anything.
    The note in my original post on the LTE variant remains relevant for me.
  • 4
    New releases for 20220724

    Downloads:
    For SM-T580/gtaxlwifi: https://drive.google.com/file/d/1RU6xNosaBlS-VoOGoahpT3zvgiGH-iS9/
    For SM-P580/gtanotexlwifi: https://drive.google.com/file/d/1lh4ThE8TjESt9ru05V0IWlAOP50x-6hP/

    Changelog:

    • Latest changes from LineageOS, including the 20220705 Android security updates.
    • Some updates from the 4.9 Android common kernel have been applied to the kernel.
    Enjoy.
    4
    Thanks for your reply. I have the service disabled until there is a proper fix available.
    Thank you for your efforts and this great ROM
    A proper fix (here on Lineage's gerrit) has now been applied from upstream AOSP to Lineage, and so it will be included in my next releases.
    You're very welcome.

    Indeed my performance problem was due to using too heavy gapps, I have reinstalled using the CORE gapps from nikgaps and the performance is tremendously superior. I think it should be specified in the main post to use minimum gapps. Great job and thanks for this rom @TALUAtXDA
    Excellent.
    I've added a note to use minimal variant gapps packages to the same usability fixes section. Again hoping it won't go unnoticed.
    You're welcome.

    something's wrong with latest build. Special apps detect rom rooted, maybe it's related to public keys and rom signature?
    Not much has changed in the latest build at all, so I'd say there can't be anything wrong like that that's new, unless something has suddenly been added somewhere else that does additional checks, which you'd need to bypass, and is completely out of scope for me.
    As for signing, unless something has been added that checks the build signature, that won't be the cause of any issues, as my builds have always been signed with the public test keys.

    My question is the internal updater not working? Nothing showed up as an update and I checked back here and saw the update so I manually installed it.
    OTA updates aren't setup, and I don't have/know of any place to statically store new builds so I can't set them up.

    Thank you for keeping this old tablet alive.I am facing connection problem in the latest version. The wifi randomly disconnects after sometime. I am using gtaxlwifi
    You're welcome. I don't have any ideas, again not much has changed in the latest build, there could be an external cause. You could send a PM with a log from logcat after a random disconnection for me to look at, and it could give away information for figuring out possible causes.

    Anyone know of an overclocking kernel that works with this? Would love to wake this tablet up a bit
    No, you'd need to make your own, and I wouldn't ever suggest using any published anywhere (if they were to exist).

    They'd get out-of-date quickly from my kernel sources if they're used (unless updates are regularly released), or not have necessary changes for certain things to work properly at all if some other sources are used as a base, as well as not having my updates/general changes.

    Also, most importantly, they could in general cause problems not reproducible with the standard kernels included with my builds (the very reason most other maintainers also discourage use of custom kernels).

    Your only option is undervolting for better battery life and less heat, which is much more worth it. Overclocking any further (since there's already an overclock from 1.586GHz to 1.69GHz) is simply not worth the effort for minimal gains. I'm sure I told you this a long while ago.

    Are there any plans to add LTE too? The tablet i finished today is a 585, but no SIM in it. The other one is a 585 too, but this one uses the SIM for a mobile connection
    Well, now, someone else who got a T585 is trying to bring builds up for it. Hopefully there will be success with it, although as usual, no guarantees for anything.
    The note in my original post on the LTE variant remains relevant for me.
    3
    ¡This ROM is working perfect! But i have few questions:
    This is the new lockscreen of linage os 19.1? Or i install something wrong? And is not possible to have landscape lockscreen?
    See my post here for enabling lockscreen rotation.

    Edit: Just added a small section on 19.1 usability fixes in my original post, expanding from my existing note on disabling the taskbar, with a note referring to that post for enabling lockscreen rotation. Hoping it will be less likely to be missed.
    1
    Hmm, that does look far more clean, and much more minimal. I suppose I might start using it myself. Thanks for posting this recommendation.
    Thanks to Andreas and you for your replies! Much appreciated!
    1
    How do i install this ROM? (My tablet is currently on the stock ROM)
    I had the same situation sime months ago and asked for help in the 18.1 forum. See here: https://forum.xda-developers.com/t/...d-sm-p580-gtanotexlwifi.4274293/post-85518275 and here: https://forum.xda-developers.com/t/...d-sm-p580-gtanotexlwifi.4274293/post-85522719 and for rooting several years ago I followed this guide: https://forum.xda-developers.com/t/...and-root-for-tab-a-tablets-2016-10-1.3552509/
  • 24
    This is LineageOS 19.1, which is based on Android 12, for the WiFi-only variants of the Samsung Galaxy Tab A 10.1" (2016), with model SM-T580 and codename gtaxlwifi, and the Galaxy Tab A 10.1" (2016) with S-Pen, with model SM-P580 and codename gtanotexlwifi. LineageOS doesn't need much of an introduction - It's a well-known custom firmware/Android distribution.

    As was the case with LineageOS 18.1, I've taken over maintaining 19.1 from @followmsi, and my 19.1 builds continue on from his 19.1 builds that were intended for use by users. To update from his builds, my builds can simply be installed on top of an existing install from his builds without doing anything further (or "dirty flashed").

    For those running 18.1, or probably even 17.1, upgrading to 19.1 is possible through the procedure I've explained before here and here (except with 19.1/Android 12 and 18.1 rather than 18.1/Android 11 and 17.1 for that second post). I highly suggest backing up any important data before trying to upgrade. In the unlikely case the upgrade fails, and it doesn't boot, data would need to be formatted.

    LineageOS 19.1/Android 12 usability fixes:
    For those wanting to disable the widely disliked taskbar
    (the grey bar at the bottom with the 3 navigation buttons and shortcuts for apps docked at the launcher): Instructions for doing so are in the first section of my post here.
    For enabling lockscreen rotation: Instructions for doing so are in my post here.
    For those needing Google apps: Do not use heavy Google apps packages, as otherwise, you WILL have severe performance issues. Instead, use the most minimal variant of your chosen package. For example, for NikGapps, that is the core variant, and for OpenGapps, that is the pico variant.

    Downloads:
    Note: While these builds are mainly intended to be used on the WiFi-only variants of these devices, they can be installed and used on LTE variants if you can go without mobile networking (of course), GPS and vibration.
    I'm only going to try getting builds up for the LTE variants if I get one in the future. Trying to do so without direct access to an LTE variant device is very difficult and not really feasible (as I've realized after thinking in much more depth about it since thinking I'd be able to do so without an LTE variant device a long time ago).


    For SM-T580/gtaxlwifi:

    Latest build from 20220724 (with security patch level 20220705): https://drive.google.com/file/d/1RU6xNosaBlS-VoOGoahpT3zvgiGH-iS9/
    Folder for builds (which contains text files with MD5 and SHA256 checksums for the latest build, and a folder containing previous builds): https://drive.google.com/drive/folders/1S3NRiTP2jr9gRtSMKoKoaoMu75g_FJM4

    For the T580, the latest official TWRP build from here should be used. If installing a build for the T580 to the LTE variant, with model SM-T585 and codename gtaxllte, keeping in mind some functionality will of course be missing as described in my note, the latest official TWRP build for gtaxllte from here can also be used.

    For SM-P580/gtanotexlwifi:
    Latest build from 20220724 (with security patch level 20220705): https://drive.google.com/file/d/1lh4ThE8TjESt9ru05V0IWlAOP50x-6hP/
    Folder for builds (which contains text files with MD5 and SHA256 checksums for the latest build, and a folder containing previous builds): https://drive.google.com/drive/folders/11pcp9NZf0ovelvT7oxfhoem6-utpSao8

    For the P580, I've made unofficial TWRP builds from an updated device tree and the same kernel sources used for these LineageOS builds that must be used.
    Download link for an image of my latest TWRP build: https://drive.google.com/file/d/1TAFLVpxdYQNvfvUPS_BGKx3imphR1Wd2/
    Download link for a tar archive containing it for installation via Odin in the AP slot: https://drive.google.com/file/d/1Ay55ntZj7Uptzm--hiCaeG1C5lamQ1fG/

    Changelogs:
    Releases for 20220724:
    • Latest changes from LineageOS, including the 20220705 Android security updates.
    • Some updates from the 4.9 Android common kernel have been applied to the kernel.
    Previous releases:
    Releases for 20220620:
    • Latest changes from LineageOS, including the 20220605 Android security updates.
    • Network traffic monitoring now works (as some changes reverting the removal of the old, non-eBPF, method of doing it that the old 3.18 kernel only supports have been applied, thanks to @rINanDO for them!).
    • One of Lineage's changes to the default keyboard, likely to be causing a problem where the keyboard appears full screen with no keys in very few cases, has been reverted.
    • Many updates from the 4.9 Android common kernel, and some from a few other sources, have been applied to the kernel.
    • The issue where trying to power off, or reboot to recovery or download mode, would sometimes cause a normal reboot has been fixed.
    • A small fix to the kernel has been applied that fixes occasional soft reboots, that were caused by a change I made a very long time ago that had only started causing such soft rebooting problems with Android 12.
    Releases for 20220523:
    • Latest changes from LineageOS, including the 20220505 Android security updates and an option for disabling the taskbar.
    • The problem where enabling the "Enable on-screen nav bar" option at Settings -> System -> Buttons caused touchscreen input to be disabled has been fixed.
    • Native support for IPsec tunnels has been enabled.
    • Support for Vulkan compute is now declared.
    • A new custom version of the open source Samsung audio HAL from Lineage's android_hardware_samsung repository is now used, rather than the stock, heavily-patched, proprietary Samsung audio HAL, with some fixes for a problem that made it unusable before where occasionally, audio would get outputted from both the speakers and the headphone jack.
    • The playback and low-latency capture period sizes have been reduced to 128 in the open source audio HAL, which reduces audio latency.
    • Pro audio support is now declared, since with the reduced period sizes, as well as with the use of the open source audio HAL, round-trip audio latency has been reduced enough for it.
    • Many updates from the 4.9 Android common kernel have been applied to the kernel.
    • Several fixes to the Sony HID driver in the 4.9 Android common kernel have been ported over to the kernel - Sony DualShock 4 controllers should now work properly.
    Initial releases for 20220416 (This changelog continues on from @followmsi's last 19.1 build that was intended for use by users):
    • Latest changes from LineageOS.
    • SELinux is now set to be enforcing after having addressed new SELinux denials with 12.
    • Assisted GPS has been fixed.
    • ADB is no longer enabled by default or on boot.
    • The tablet product characteristic has been added back after being mistakenly removed - Places where the device was referred to as a phone (such as the "About phone" section in settings) will now refer to it as a tablet again.
    • The Widevine DRM blobs have been updated to 1.4 blobs from the latest stock firmware for the Google Pixel 3a XL.
    • A new wcnss_filter binary built from sources is now used to properly fix an issue where Bluetooth couldn't be re-enabled after enabling and disabling it once, and the old workaround for it has been removed.
    • Some other miscellaneous cleanups have been done.
    • There are a few updates from the 4.9 Android common kernel and Samsung's A600FNXXU9CVB1 kernel sources to the kernel.
    • An issue where the displays backlight would be turned off completely when setting very low brightnesses, causing nothing to be visible on the display (unless very faintly if you shine a torch or something on it), has been fixed.



    Known issues and workarounds (if any):
    Issue 1: Camera previews for images to be taken at resolutions with aspect ratios other than 16:9 using the rear camera are squashed from 16:9 (while final saved images at any resolution are unaffected by any squashing), and videos taken at some resolutions are affected by similar issues with squashing in previews, and, in a smaller set of resolutions, also in final saved video files. (Note that these issues don't affect the front-facing camera)
    Somewhat of a workaround to issue 1: Use resolutions at which there are no issues with squashing from 16:9.

    Something notable is that currently, with Android 12, encrypted data can't be decrypted in TWRP recovery. That problem can only be fixed within TWRP, so we'll need to wait for an update to TWRP which fixes it.

    To report further issues, get a log from logcat and dmesg. If you're unsure on how to get either, there's good documentation out there for how to do so.


    Sources:
    A manifest containing all of the necessary repositories to make a build for either the T580 or P580 is in this repository on branch lineage-19.1: https://github.com/TALUAtGitHub/gtaxlwifi-manifests

    Starting from my initial 19.1 build, a new common tree setup, with new gtaxl common device and vendor trees, along with new gtaxlwifi and gtanotexlwifi device and vendor trees to use with them, is used to create builds. Before, the gtaxlwifi device tree was a standalone tree, and the gtanotexlwifi device tree was a complete copy of it with changes for the P580 on top, meaning a lot of stuff was duplicated between them. With such new setup, that duplication no longer exists, and build times when building builds for both the T580 and P580, one after the other, are massively decreased.
    18.1 builds for 20220423 onwards are also built with that setup, only without changes for Android 12.

    Thanks to:
    @Valera1978 - for all of the previous work for the T580 (and T585) long ago.
    @followmsi - for fixes to various issues and other improvements, for useful information, and for working with me on much of this stuff.
    Anyone who has previously tested anything new I've put up for testing, reported results, and gave details for me to get it working if it was necessary.
    The Lineage team - for the Android distribution itself.
    ...and everyone else who has worked on anything that is in use.
    12
    New releases for 20220620

    Downloads:
    For SM-T580/gtaxlwifi: https://drive.google.com/file/d/1onRpEeNRkFpVrZqP4bFbZoDyf9N1GkVY/
    For SM-P580/gtanotexlwifi: https://drive.google.com/file/d/1WgT1ZCz5sqf7g41OECqCyULmCO-ss2X3/

    Changelog:

    • Latest changes from LineageOS, including the 20220605 Android security updates.
    • Network traffic monitoring now works (as some changes reverting the removal of the old, non-eBPF, method of doing it that the old 3.18 kernel only supports have been applied, thanks to @rINanDO for them!).
    • One of Lineage's changes to the default keyboard, likely to be causing a problem where the keyboard appears full screen with no keys in very few cases, has been reverted.
    • Many updates from the 4.9 Android common kernel, and some from a few other sources, have been applied to the kernel.
    • The issue where trying to power off, or reboot to recovery or download mode, would sometimes cause a normal reboot has been fixed.
    • A small fix to the kernel has been applied that fixes occasional soft reboots, that were caused by a change I made a very long time ago that had only started causing such soft rebooting problems with Android 12.
    As always, enjoy.
    9
    More detailed release notes for the builds for 20220523

    New option for disabling the taskbar


    A new option for disabling the widely disliked taskbar has been added by the Lineage team.
    Along with that, I've fixed the problem where enabling the "Enable on-screen nav bar" option at Settings -> System -> Buttons disabled touchscreen input entirely, which makes that new option for disabling the taskbar usable.

    Now, to disable the taskbar, it's unfortunately not very straightforward. The steps are as follows:
    • Go to the Settings app, and in it, go to System -> Buttons.
    • Enable the "Enable on-screen nav bar" option.
    • Go back to the System section, and go to the Buttons section again.
    • A new option, "Enable taskbar", should be there. Toggle it off. The taskbar should disappear and be replaced with an old-style navigation bar.
    From there, to use the hardware keys with no navigation bar or taskbar, simply disable the "Enable on-screen nav bar" option.
    Otherwise, that option can be kept enabled to have an "old-style" navbar, with input from touchkeys being ignored, and with no taskbar. Different methods of navigation can be selected at Settings -> System -> Gestures -> System navigation.

    Sony DualShock 4 controller support

    Several fixes to the Sony HID driver that are in the 4.9 Android common kernel have been ported to the Sony HID driver in our older 3.18 kernel, including fixes for DS4 controller support.

    With them, DS4 controllers should now work properly, along with probably a few other Sony controllers, too.

    Huge improvements in audio latency

    The audio HAL has been switched from the stock, heavily-patched, proprietary Samsung audio HAL to a custom version of the open source Samsung audio HAL from Lineage's android_hardware_samsung repository, with some fixes for a problem that made it unusable before where occasionally, audio would get outputted from both the speakers and the headphone jack.

    Within it, the playback and low-latency capture period sizes have been reduced to 128.

    With the use of the open source audio HAL and the smaller period sizes, round-trip audio latency has decreased from around 48 ms (if I remember correctly) with the proprietary Samsung audio HAL to 14-16 ms on my tablet, according to the Superpowered audio latency test app, with rough tests with just my headphones and the built-in microphone with the Dr. Rick O'Rang loopback app suggested in Android documentation for latency testing confirming.

    With that massive improvement in audio latency, support for pro audio is now declared (for which a round-trip audio latency of 20 ms or less is required). Any apps requiring it to be available in the Google Play Store will now show up, and if any apps check for if pro audio feature support is reported, they'll now run.

    If anyone comes across any new problems with the open source audio HAL, do report them.


    As always, enjoy.
    9
    New releases for 20220523

    Downloads:
    For SM-T580/gtaxlwifi: https://drive.google.com/file/d/17DJlZUaKd2u-zNxU2GojqM_HjZ1HOK0C/
    For SM-P580/gtanotexlwifi: https://drive.google.com/file/d/1EEFTw3glv6kbqdNodKWnIu5Jw1D47Hq4/

    Changelog:

    • Latest changes from LineageOS, including the 20220505 Android security updates and an option for disabling the taskbar.
    • The problem where enabling the "Enable on-screen nav bar" option at Settings -> System -> Buttons caused touchscreen input to be disabled has been fixed.
    • Native support for IPsec tunnels has been enabled.
    • Support for Vulkan compute is now declared.
    • A new custom version of the open source Samsung audio HAL from Lineage's android_hardware_samsung repository is now used, rather than the stock, heavily-patched, proprietary Samsung audio HAL, with some fixes for a problem that made it unusable before where occasionally, audio would get outputted from both the speakers and the headphone jack.
    • The playback and low-latency capture period sizes have been reduced to 128 in the open source audio HAL, which reduces audio latency.
    • Pro audio support is now declared, since with the reduced period sizes, as well as with the use of the open source audio HAL, round-trip audio latency has been reduced enough for it.
    • Many updates from the 4.9 Android common kernel have been applied to the kernel.
    • Several fixes to the Sony HID driver in the 4.9 Android common kernel have been ported over to the kernel - Sony DualShock 4 controllers should now work properly.
    7
    I think stock Android 6 on the tablet had Widevine L1. Didn't it? I don't know how it all works, but I do wonder what is missing. When you posted that you had used the Pixel 3a blobs, I had thought that was whatever blackbox did the widevine L1. I see I was wrong. I guess whatever blobs and whatnot from Android 6 aren't compatible with our LineageOS setups?

    If you could explain a bit more of the Widevine internals as it relates to L1 on these tablets, just to cure my ignorance, I'd appreciate it. I've been wondering about it for a while. I can program in assembly language and C, so don't pull any punches. :)
    It would also work on the Android 8.1 stock firmware.

    The Widevine DRM HAL, which is what I updated, is part of it. There's also a liboemcrypto.so blob, and Mobicore/the Trustonic TEE, along with relevant "trustlets" for it. WIth a working combination of the Widevine DRM HAL, liboemcrypto blob, Mobicore blobs, and "trustlets", it would be possible for the Widevine security level to be reported as L1. But, still, it would be dropped down to L3.

    The commit message for the commit here removing the liboemcrypto blob and also replacing two other DRM-related blobs for Exynos 7580 devices describes, in actuality, Samsung as disabling L1 on devices that are modified in any way. Who knows how that happens or where along the line it does, seeing as all low-level device-specific stuff is, of course, undocumented.

    I don't think it's worth continuing discussion on that topic. It's dead-end and I personally have a very poor understanding of it all, as I imagine almost everyone else does. There's no getting back the L1 security level.
    Good work. Upgrade from 18.1 worked flawlessly except for this that appeared and dont know how to remove it.
    What is this bottom bar?
    That's the new, pretty intrustive and seemingly also buggy, taskbar in Android 12L.
    The only way to somewhat get rid of it is to switch to gesture navigation. Oddly, there's no three buttons for navigation on your taskbar there, so I'm not sure if you have it enabled already, and just need to hold down on it to switch to a navigation "pill".
    That can most easily be done by running this command in an ADB shell or a shell with root access otherwise (run `su` in any other type of shell, such as one through an app, to get root access):
    Code:
    cmd overlay enable com.android.internal.systemui.navbar.gestural
    With it, a small white pill, along with some space around it, replaces the taskbar for navigation. Holding it down would switch back to a taskbar, and holding it down again would switch back to that pill. Note that as it's gesture navigation, you'd have to get used to either using the gestures or ignoring that they're there, especially since they interfere with some gestures in some apps.

    Unfortunately, at the moment, we don't have anything else besides switching to gesture navigation to get around it. This all came down from Google/AOSP (the Android Open Source Project) itself. Here's hoping Lineage makes improvements or improvements are made under AOSP to this navigation stuff.