LineageOS 19.1 for SM-T580 (gtaxlwifi), SM-T585 (gtaxllte), SM-P580 (gtanotexlwifi), and SM-P585 (gtanotexllte)

Search This thread

jcsdkx51

Member
Dec 26, 2010
15
0
Navarre
Sorry you're having this trouble. It took me ages to sort things out also.

I've just realised that I've glossed over the fact that you want to trade your device in, so are looking to re-create a plain vanilla stock installation.

This means you probably don't want to retain TWRP on the device.

If it were me, I'd be doing this - indeed I've done this before:
  • obtain the *exactly* correct stock ROM (got mine at samfw.com), paying attention to the bit (BINARY/U/SW REV.) number (mine is 5 - you can see this in the Odin Mode screen on your tablet)
  • using Odin3
    • Options tab – ticked:
      • auto reboot
      • Nand Erase
      • Re-Partition
      • F. Reset Time
    • Files to flash:
      • BL
      • AP
      • CSC (not home_csc – I wanted to wipe everything)
After successfully flashing these, the tablet rebooted into the stock ROM without further ado.

Hope that helps. :)
Thanks for the help! I tried that a few times and still got the bootloop. Even after getting into recovery and wiping the data and cache there a few times as well. i ended up using a coupon code for Android Reiboot, which I think is basically a script that runs the Odin, lol, but it was only $13 so I did it. Ran it several times on and was still getting the boot loop and finally one of them took and it booted to the stock welcome screen. As soon as it came up I submitted the trade at Amazon. Thanks again for the help, not sure what finally took or if it was the multiple partition/cache wipes, but I definitely appreciate you pointing in the right directions to get it resolved!
 

ithritin

New member
Nov 19, 2022
1
0
Hey there~ I just flashed from 17.1 to 19.1 and it all seemed to go well, however now I'm experiencing crashing issues. When trying to download any app from the Play store, it tells me I need to free up space (I have a freshly formatted 128gb sd card inserted) [edit: should add that I installed the GApps Pico linked to in this thread]

When I go to Settings > Storage it says 6% used, 136GB free

If I click on Storage, it crashes to desktop/home screen. Any ideas? Could this be an internal tablet issue?

SOLVED: Formatted Data/partition in TWRP and reinstalled everything. Working again. Sorry for the early freakout post!
 
Last edited:

rapidm

Senior Member
Dec 24, 2010
91
20
Thanks for all your hard work @TALUAtXDA
Really makes this tablet shine and makes it still perfectly usable (at least for me) to this day.
Not asking for ETA or anything but is android 13 be possible with this tablet? Or is it the end of the road here (in terms of time spend needed and hardware capabilities)?
 

TALUAtXDA

Senior Member
Nov 8, 2018
493
1,190
New builds for 20221127

Downloads:
For SM-T580/gtaxlwifi: https://drive.google.com/file/d/1jd9kC8SoJH3Jba2YT_7K3qEB7QG27MMR/
For SM-P580/gtanotexlwifi: https://drive.google.com/file/d/1V_lE-ehNIvD2q-B6bbz119pjwFq92fOk/

Changelog:

  • Latest changes from LineageOS, including the 20221105 Android security updates.
Being yet more busy than usual, and also conveniently having had a hardware failure to deal with, yep, quite late again with these builds, and unfortunately with no kernel updates. Should be able to bring them in for the next builds, though.

As for LineageOS 20.0, I've still yet to get around to working on it.
While it certainly is possible, sadly, there most likely won't ever be any possibilities for getting network traffic monitoring (used specifically for data usage statistics, network download/upload speed monitoring...) working under Android 13. (For 12.1, support for the old, non-eBPF method for it was removed, however, we have changes to revert the removal and bring it back since our old 3.18 kernel only supports it and doesn't support eBPF. It certainly seems like we won't have changes to bring it back on 13, and unfortunately, it doesn't look like there will ever be eBPF backports for 3.18.)

Nevertheless, for the meantime, enjoy.
 
Last edited:

shimn

Member
Aug 5, 2013
46
7
Pacific NW
I had an older version of 19.1 installed on my SM-T580 and someone else was using for about 4 months but they were done with it so I thought I would wipe it and install the latest version. Put the following on the portable SD card:

lineage-19.1-20221127-UNOFFICIAL-gtaxlwifi.zip
NikGapps-54b1d_lite-arm64-13-20221128-signed.zip
open_gapps-arm64-12L-pico-20220705-UNOFFICIAL_MOD.zip

Booted into TWRP 3.6.2_9-0 and wiped system , internal storage, and data. Then installed the Lineage zip and the NikGapps zip in succession. Rebooted into system and got to that bluish screen with "Hi there" but then it immediately restarted saying "Factory data reset":

IMG_20221129_102653349.jpg

So, did the same procedure and same result. Then did it with OpenGapps instead of Nik but same result.

Any ideas? Thanks.
 

shimn

Member
Aug 5, 2013
46
7
Pacific NW
I had an older version of 19.1 installed on my SM-T580 and someone else was using for about 4 months but they were done with it so I thought I would wipe it and install the latest version. Put the following on the portable SD card:

lineage-19.1-20221127-UNOFFICIAL-gtaxlwifi.zip
NikGapps-54b1d_lite-arm64-13-20221128-signed.zip
open_gapps-arm64-12L-pico-20220705-UNOFFICIAL_MOD.zip

Booted into TWRP 3.6.2_9-0 and wiped system , internal storage, and data. Then installed the Lineage zip and the NikGapps zip in succession. Rebooted into system and got to that bluish screen with "Hi there" but then it immediately restarted saying "Factory data reset":

View attachment 5773183

So, did the same procedure and same result. Then did it with OpenGapps instead of Nik but same result.

Any ideas? Thanks.
I did a system wipe and then tried loading only the Lineage 19.1 zip with no Gapps but still get the factory data reset reboot right away.
 

shimn

Member
Aug 5, 2013
46
7
Pacific NW
I did a system wipe and then tried loading only the Lineage 19.1 zip with no Gapps but still get the factory data reset reboot right away.
I upgraded TWRP to 3.7.0_9-0 from https://dl.twrp.me/gtaxlwifi/ but still getting that error. Also tried a previous version of the ROM lineage-19.1-20221020-UNOFFICIAL-gtaxlwifi.zip. Tried wiping everything: system, internal storage, data, cache, Dalvik cache. Still same problem. Gonna take a break from this to clear my head.
 

js-xda

Senior Member
Aug 20, 2018
362
157
Samsung Galaxy S4
i9100
New builds for 20221127

[...]

Different from my post last night (see below), I tried the same today with NikGApps (dirty flash on P580 with encrypted storage and with GApps from 20221020 to 20221127) on a second device and running into issues:
  1. As done on other devices, dirty flashing only the LOS 20221127 build. Running into boot loop (LOS start-up screen after PIN for decryption for 1-2 min and then reboot).
  2. Tried flashing LOS 20221127 build together with NikGapps-core-arm64-12.1-20220908-signed. Results in starting to system but Play Store not able to connect.
  3. Wiping system before flashing LOS 20221127 build together with NikGapps-core-arm64-12.1-20220908-signed. Results in starting to system but Play Store still not able to connect.
  4. I double-checked the checksum (LOS build on SD card) but that one is correct as well.
  5. Wiping system before flashing LOS 20221020 build together with NikGapps-core-arm64-12.1-20220908-signed as during initial installation. Results in a message that the encrypted data are corrupt.
  6. Wiping system before flashing again LOS 20221127 build together with NikGapps-core-arm64-12.1-20220908-signed. Results in starting to system (no complaint on decrypting data) but Play Store still not able to connect.
Anyone an idea? Just a glimpse, bad luck, something with the latest build, the NikGapps or could it be that the storage is broken? Probably asking for too much but maybe someone has by chance an idea - before I wipe completely and give it a clean try.

Dirty flash on P580 with encrypted storage and without GApps from 20221020 to 20221127 without any issues. Thank you! :)

LATER ADDITION: Issue with Play Store being offline resolved - but not clear why it happened in the first place. Issue was that the Play Store had network data access deactivated. I recall also that the device was in flight mode when starting to system in 2. of above list. And I know for sure it wasn't before starting the dirty flash. So, something is still quite odd about all of this - a. o. the boot loop mentioned in 1.
 
Last edited:

js-xda

Senior Member
Aug 20, 2018
362
157
Samsung Galaxy S4
i9100
I upgraded TWRP to 3.7.0_9-0 from https://dl.twrp.me/gtaxlwifi/ but still getting that error. Also tried a previous version of the ROM lineage-19.1-20221020-UNOFFICIAL-gtaxlwifi.zip. Tried wiping everything: system, internal storage, data, cache, Dalvik cache. Still same problem. Gonna take a break from this to clear my head.
As I am also never sure what the difference between wiping and formatting is (and which one includes the other): Have you tried also the format option? Similar errors during clean flash as you see are often related to file system errors.
 
Last edited:
  • Like
Reactions: shimn

shimn

Member
Aug 5, 2013
46
7
Pacific NW
  • Like
Reactions: js-xda

shimn

Member
Aug 5, 2013
46
7
Pacific NW
I did a Format Data and I think that did the trick. I can't recall ever doing that...usually just do a wipe but now will now remember to use format.
 
  • Like
Reactions: js-xda

Sage

Senior Member
Dec 12, 2005
1,746
416
AU
Xiaomi Mi 11
if you dont format data then sometimes the Recovery cannot read the data cause it's encrypted.. format clears encryption. (to be honest on these old devices i prefer to disable encryption if possible.. one less thing it has to work on)..
 
  • Like
Reactions: shimn

TigreMarino

New member
Jun 13, 2014
1
1
Hello!

I updated to this version after formatting and trying to figure out things, always got the "Factory data reset" and rebooting into Recovery.

On TWRP (the version recommended for 19.1) I found out an option of "fixing context" on the advanced settings, clicked on it, rebooted the tablet and has been working normal since then.

Maybe this will help people who cannot boot this ROM properly.
 
  • Like
Reactions: shimn

js-xda

Senior Member
Aug 20, 2018
362
157
Samsung Galaxy S4
i9100
Different from my post last night (see below), I tried the same today with NikGApps (dirty flash on P580 with encrypted storage and with GApps from 20221020 to 20221127) on a second device and running into issues:
  1. As done on other devices, dirty flashing only the LOS 20221127 build. Running into boot loop (LOS start-up screen after PIN for decryption for 1-2 min and then reboot).
  2. Tried flashing LOS 20221127 build together with NikGapps-core-arm64-12.1-20220908-signed. Results in starting to system but Play Store not able to connect.
  3. Wiping system before flashing LOS 20221127 build together with NikGapps-core-arm64-12.1-20220908-signed. Results in starting to system but Play Store still not able to connect.
  4. I double-checked the checksum (LOS build on SD card) but that one is correct as well.
  5. Wiping system before flashing LOS 20221020 build together with NikGapps-core-arm64-12.1-20220908-signed as during initial installation. Results in a message that the encrypted data are corrupt.
  6. Wiping system before flashing again LOS 20221127 build together with NikGapps-core-arm64-12.1-20220908-signed. Results in starting to system (no complaint on decrypting data) but Play Store still not able to connect.
Anyone an idea? Just a glimpse, bad luck, something with the latest build, the NikGapps or could it be that the storage is broken? Probably asking for too much but maybe someone has by chance an idea - before I wipe completely and give it a clean try.



LATER ADDITION: Issue with Play Store being offline resolved - but not clear why it happened in the first place. Issue was that the Play Store had network data access deactivated. I recall also that the device was in flight mode when starting to system in 2. of above list. And I know for sure it wasn't before starting the dirty flash. So, something is still quite odd about all of this - a. o. the boot loop mentioned in 1.
Building on this, I continued today and found something else which is odd (third bullet):
  • From TWRP recovery (the one provided in the OP), I formatted data first and wiped after reboot also Dalvik / ART Cache, System, Data and Internal Storage.
  • I flashed again LOS 20221020 build together with NikGapps-core-arm64-12.1-20220908-signed. Starting smoothly and I didn't encrypted storage for now.
  • Going back to TWRP recovery for testing update to 20221127 with a fresh, not encrypted installation, I noticed that I was asked again to confirm write permission for TWRP. I checked and found that there is no /data/media/0 but some folders (a. o. TWRP) in /data/media while /sdcard contained the regular folders one expects but not TWRP. So, it seems something is wrong with the symbolic link usually pointing from /sdcard to /data/media/0. Can't test on my other P580 as that one is encrypted (but also no TWRP folder visible when running LOS) but I compared to a Samsung Galaxy S4 at hand - confirming what I had remembered.
  • Format data resolved the missing link and now I see the TWRP folder on running LOS (flashed again LOS 20221020 build together with NikGapps-core-arm64-12.1-20220908-signed). Updating once without setting up Google account worked fine but I wanted to be super sure ... therefore ...
  • Back to TWRP, wiping first the four initially mentioned items, rebooting, formatting data and flashing once again LOS 20221020 build together with NikGapps-core-arm64-12.1-20220908-signed. Starting smoothly and I didn't encrypted storage for now. Logging into Google account, setting up a few things and reverting to TWRP. Flashing LOS 20221127, wiping Dalvik / ART Cache and reboot to system: Flawless! :)
  • For now, I keep the device with NikGApps not encrypted as well to be on the safe side - excluding it as possible cause but also allowing for backups via TWRP ...
Conclusion: Always "Format Data" as final step before starting a fresh installation in TWRP. (And a brief check in the file manager of TWRP doesn't harm either.)
 
  • Like
Reactions: shimn

Rosspapa

New member
Dec 12, 2022
1
0
I haven't found any solution for "double tap to wake" the screen. Is there any possibility to have this function?
 

0 George 0

Member
Jun 3, 2020
15
4
I cannot power off the tablet , continuous running , I left the battery going to zero after I put the power cable doing the same thing .
It's starts after I load the Odin3_v3.10.7 / twrp-3.0.2-0-gtaxlwifi.img
I do not have access to operator system, It's stuck black screen.
 

Attachments

  • εικόνα_Viber_2022-12-12_19-40-20-802.jpg
    εικόνα_Viber_2022-12-12_19-40-20-802.jpg
    120.5 KB · Views: 17
  • εικόνα_Viber_2022-12-12_19-40-25-592.jpg
    εικόνα_Viber_2022-12-12_19-40-25-592.jpg
    122 KB · Views: 15
  • εικόνα_Viber_2022-12-12_19-40-36-491.jpg
    εικόνα_Viber_2022-12-12_19-40-36-491.jpg
    113.7 KB · Views: 18
  • εικόνα_Viber_2022-12-12_19-45-14-974.jpg
    εικόνα_Viber_2022-12-12_19-45-14-974.jpg
    213.3 KB · Views: 19
Last edited:
Sep 15, 2017
25
2
I cannot power off the tablet , continuous running , I left the battery going to zero after I put the power cable doing the same thing .
It's starts after I load the Odin3_v3.10.7 / twrp-3.0.2-0-gtaxlwifi.img
I do not have access to operator system, It's stuck to black screen.
first of yall youre using the wrong twrp img use the one given under the guide based on the model you have... again read the guide before doing mistakes like that :)
 

0 George 0

Member
Jun 3, 2020
15
4
Yes correct , I use the wrong twrp .... Now I stuck in logo Samsung .... I cannot load twrp and I cannot power off the tablet again...
twrp-3.6.1_9-0-gtanotexlwifi-unofficial-newsources
 

Attachments

  • εικόνα_Viber_2022-12-12_21-00-12-893.jpg
    εικόνα_Viber_2022-12-12_21-00-12-893.jpg
    139.1 KB · Views: 8

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    New builds for 20230128

    Downloads:
    For gtaxlwifi
    For gtaxllte

    For gtanotexlwifi
    For gtanotexllte

    Changelog:

    • Latest changes from LineageOS, including the 20230105 Android security updates.
    • [LTE variant-specific] Issues with mobile networking not working have been fixed.
    • [gtanotexllte-specific] Additional issues with bootlooping and rebooting during the boot animation have been fixed.
    • Open source aptX encoder libraries, from sources adapted from Qualcomm's recently upstreamed to AOSP open source code, are now used.
    With yet more of a lack of time I'm expecting to continue, there isn't much to these builds.
    Again, no kernel updates, I'll try getting those in for the next builds. Going forward, since the 4.9 Linux kernel has been discontinued upstream, hopefully, taking updates from the 4.14 kernel won't be too difficult.

    The fixes for the LTE variants that I've brought up before are now included. There shouldn't be any issues with booting or totally non-functional mobile networking anymore on any devices.
    In case anyone is still having some other issues, do report them.

    Also, I'm going to look into getting call audio over Bluetooth to work later on, though it's not a priority.

    Enjoy.
    3
    If I recall Android 12 and this ROM had a problem on the 580 where the bottom navigation bar could not be disabled. Is this still true? I am using the LineageOS 18.1 ROM and would like to update if it is fixed. Thanks in advance!
    This is not true. You can disable the "application bar" at the bottom. Also it is possible bring back the classic navigation bar or alternative to use the gestures navigation. Tried all of these. All are working fine.
    2
    For who like write and read paper (pdf) do you suggest update tablet ?!
    Depends on what you need - I can't compare as I never used the Samsung apps. But you can test OneNote and alike (I use Quill for privacy reasons) before upgrading from Stock and decide based on that for writing. PDF is no issue for sure.
    2

    Hans_Werner, js-xda, thanks!​

    TALUAtXDA, I've been using your ROMs for the 580 for a long time and would like to thank you for the amazing work still bringing new life and features to the device. This ROM is simply AMAZING!​

    2
    I install Los on my gtanotexllte with out the 2 fixes and it boot and runs great
    something I want to know how can I disable the navbar ?
    ... just read carefully the very first post of the developer. He explained it and it works (and was already asked here several times). 😁
  • 46
    This is LineageOS 19.1, which is based on Android 12L, for variants of the Samsung Galaxy Tab A 10.1" (2016), which have models and codenames as follows:
    • SM-T580, with codename gtaxlwifi
    • SM-T585, with codename gtaxllte, along with SM-T585N0 and SM-T585C
    • SM-P580, with codename gtanotexlwifi, along with SM-P583
    • SM-P585, with codename gtanotexllte, along with SM-P585M, SM-P585Y, SM-P585N0, and SM-P588C
    LineageOS doesn't need much of an introduction - It's a well-known custom firmware/Android distribution.

    Some useful information for devices from China (SM-P583, SM-T585C, SM-P588C, and SM-T580 on the CHN CSC) - For unlocking the bootloader before installation, an app, "CROM Service", would need to be opened and the prompt from it accepted so that it can be unlocked, after enabling the "OEM unlock" setting in developer options. It should be available from the Galaxy Store, although I can't be 100% sure about it. In any case, an APK of it should be easy to find.

    As was the case with LineageOS 18.1, I've taken over maintaining 19.1 for gtaxlwifi 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 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.

    For those who used WiFi-only variant builds on an LTE variant device, installation of a proper LTE variant build on top of an installation from a WiFi-only variant build is possible, except for a small issue you may encounter after doing so. See issue 3 in the "known workarounds and issues" section below for it.

    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 OpenGapps (no longer maintained officially, with no Android 12L packages, so use @ipdev's latest unofficial build available here), that is the pico variant, and for NikGapps (note that it now seems to more often be problematic, probably better using something else), that is the core variant.

    Build downloads
    For gtaxlwifi - From 20230128 (with security patch level 20230105): https://drive.google.com/file/d/1jwtlk2QhpdmoK2aLeSoGmGC8riSfNOSY/
    For gtaxllte - From 20230128 (with security patch level 20230105):
    https://drive.google.com/file/d/1wqJ_5DAPhzh2s6N7YGi131-lcy_S4agp/
    For gtanotexlwifi - From 20230128 (with security patch level 20230105): https://drive.google.com/file/d/1SzVDR5ff-etrXzClVJ4DVO5njV9_UMJc/
    For gtanotexllte - From 20230128 (with security patch level 20230105): https://drive.google.com/file/d/1PuNt_gOpEcmWLdM0a9xLGTG-gFC6Xgq7/

    Recoveries to use
    For gtaxlwifi:
    The latest official TWRP build from here.
    For gtaxllte: The latest official TWRP build from here.
    For gtanotexlwifi: An unofficial TWRP build, that I built from newer TWRP sources and new kernel sources so that boots (unlike the current official gtanotexlwifi TWRP builds), must be used. Image can be downloaded from here, tar for installation via Odin in the AP slot can be downloaded from here.
    For gtanotexllte: As for gtanotexlwifi, only a different build. Image is here, tar for Odin is here.

    Folders for builds
    Along with current builds, these contain text files with SHA256 checksums for builds, and folders containing previous builds.
    For gtaxlwifi: https://drive.google.com/drive/folders/1S3NRiTP2jr9gRtSMKoKoaoMu75g_FJM4
    For gtaxllte: https://drive.google.com/drive/folders/1ZFkGkVkIohsNFDi0jNF2-Yhz7Sbg5GT4
    For gtanotexlwifi: https://drive.google.com/drive/folders/11pcp9NZf0ovelvT7oxfhoem6-utpSao8
    For gtanotexllte: https://drive.google.com/drive/folders/1AICJ1UcnZ5a-slcgd-iGQ9mpk9J8Evmd

    Changelogs
    Builds for 20230128:
    • Latest changes from LineageOS, including the 20230105 Android security updates.
    • [LTE variant-specific] Issues with mobile networking not working have been fixed.
    • [gtanotexllte-specific] Additional issues with bootlooping and rebooting during the boot animation have been fixed.
    • Open source aptX encoder libraries, from sources adapted from Qualcomm's recently upstreamed to AOSP open source code, are now used.
    Previous releases
    Builds for 20221231 and 20230101:
    • Latest changes from LineageOS, including the 20221205 Android security updates.
    • Some more miscellaneous cleanups have been done.
    • Initial builds for gtaxllte and gtanotexllte.
    • Many updates from the 4.9 Android common kernel have been applied to the kernel.
    Builds for 20221127:
    • Latest changes from LineageOS, including the 20221105 Android security updates.
    Builds for 20221020:
    • Latest changes from LineageOS, including the 20221005 Android security updates.
    • Performance of animations has been improved slightly further.
    • Configuration files for media codecs and profiles have been updated from Samsung's M105FDDS4CVG1 firmware, and audio codec support might be improved slightly (as the Codec 2.0 media codec framework has been fixed and is now used).
    • Some updates from the 4.9 Android common kernel have been applied to the kernel.
    Builds for 20220929:
    • Latest changes from LineageOS, including the 20220905 Android security updates.
    • The torch has been fixed.
    • Performance of animations and responsiveness has been improved slightly.
    • Some updates from the 4.9 Android common kernel have been applied to the kernel.
    • [SM-P580/gtanotexlwifi only, already fixed in T580 builds long ago] 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 a different bright light source on it), has been fixed.
    • The WiFi drivers RX wakelock feature has been disabled - Heavy battery drain that occurred in sleep when connected to certain WiFi networks due to "qcom_rx_wakelock" wakelocks has been fixed.
    Builds for 20220824:
    • Latest changes from LineageOS, including the 20220805 Android security updates, and a fix for "Intent Filter Verification Service" crashes that occurred in few/some cases with no Google apps or with MicroG.
    • Some things that appeared that are only relevant for devices with mobile networking (such as the baseband version and SIM status sections in About tablet in settings) no longer appear.
    • The ZRAM size has been increased to 2GiB, and the swappiness is now set to 100.
    • A higher frequency (1246MHz, was 902MHz previously) is now set for the interactive CPU governors "hispeed_freq" value - This improves responsiveness slightly.
    • The sepolicy containing device-specific SELinux rules has been improved slightly.
    • Yet more miscellaneous cleanups have been done.
    • Some updates from the 4.9 Android common kernel have been applied to the kernel.
    Builds 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.
    Builds 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.
    Builds 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 builds 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 a different bright light source on it), has been fixed.



    Known issues and workarounds/fixes (if any)
    Issue 1 - Squashed (rear) camera previews, and videos at some resolutions: 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: Use resolutions at which there are no issues with squashing from 16:9.

    Issue 2 - LTE variants - In-call echo: There may be echoing that can be heard by the person you're calling while using speakers.
    See my post here for more on this issue.

    (Temporary) Issue 3 - APN issues on LTE variant devices - after installation of a proper LTE variant build on top of an installation previously from a WiFi-only build: On an LTE variant device, after installing a proper LTE variant build on top of an existing installation from a WiFi-only build, when going to APN settings, at Settings -> Network and Internet -> SIMs -> Access point names, an error is displayed that APN settings cannot be changed by the current user (or something similar).
    Fix: Tap the 3-dot menu at the top right, and select "Reset to default", and then select the relevant APN.

    (Minor cosmetic) Issue 4 - Incorrect model displayed on devices with region-specific model numbers
    I'll take a look at fixing this issue up later on.

    Issue 5 - LTE variants - Bluetooth calling doesn't work: There isn't any call audio over Bluetooth audio devices. Any call audio with a Bluetooth audio device connected will be routed to the built-in speakers.

    Something notable is that with Android 12, encrypted data can't be decrypted in TWRP recovery. That problem can only be fixed within TWRP, but with the fixes only being in Android 12L TWRP sources, which we can't build our TWRP builds from due to issues, it continues to exist.

    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 builds for all of the variants is in the repository here on branch lineage-19.1.

    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 provided information needed 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.
    20
    New builds for 20221127

    Downloads:
    For SM-T580/gtaxlwifi: https://drive.google.com/file/d/1jd9kC8SoJH3Jba2YT_7K3qEB7QG27MMR/
    For SM-P580/gtanotexlwifi: https://drive.google.com/file/d/1V_lE-ehNIvD2q-B6bbz119pjwFq92fOk/

    Changelog:

    • Latest changes from LineageOS, including the 20221105 Android security updates.
    Being yet more busy than usual, and also conveniently having had a hardware failure to deal with, yep, quite late again with these builds, and unfortunately with no kernel updates. Should be able to bring them in for the next builds, though.

    As for LineageOS 20.0, I've still yet to get around to working on it.
    While it certainly is possible, sadly, there most likely won't ever be any possibilities for getting network traffic monitoring (used specifically for data usage statistics, network download/upload speed monitoring...) working under Android 13. (For 12.1, support for the old, non-eBPF method for it was removed, however, we have changes to revert the removal and bring it back since our old 3.18 kernel only supports it and doesn't support eBPF. It certainly seems like we won't have changes to bring it back on 13, and unfortunately, it doesn't look like there will ever be eBPF backports for 3.18.)

    Nevertheless, for the meantime, enjoy.
    19
    New builds for 20221231 for gtaxlwifi and gtaxllte

    Downloads

    For gtaxlwifi: https://drive.google.com/file/d/1V3B8ftxioY9jCVpDfInFMvDE1t9rbFEt/
    For gtaxllte: https://drive.google.com/file/d/1ch-OfzWtDy-tZw1M1blqBcmhKAWA9b6D/

    Changelog:

    • Latest changes from LineageOS, including the 20221205 Android security updates.
    • Some more miscellaneous cleanups have been done.
    • Initial build for gtaxllte.
    • Many updates from the 4.9 Android common kernel have been applied to the kernel.
    Yep, a gtaxllte build!
    Recently, I got a donation of a T585, which has made bringup for gtaxllte, and gtanotexllte as well, possible.

    Mobile networking (including calls, texts, and mobile data), GPS, and vibration all work perfectly.
    There's only the exception of issues with in-call echo, which I'll address in my next post.

    For those who installed a gtaxlwifi or gtanotexlwifi build on a gtaxllte or gtanotexllte device, installation of a build for gtaxllte or gtanotexllte on top of such existing installations is possible.
    There may, however, be an issue with APNs, where when going to APN settings at Settings -> Network and Internet -> SIMs -> Access point names, there's an error about APN settings not being changable by the current user (or something like that), and mobile data won't be usable. To fix it, tap the 3-dot menu at the top right, and select "Reset to default", and then select the relevant APN. A reboot may be needed, and then after that, everything should be perfectly fine.

    I'll put an updated gtanotexlwifi and a gtanotexllte build up tomorrow, along with updated TWRP builds.

    Happy new year
    16
    New releases for 20220824

    Downloads:
    For SM-T580/gtaxlwifi: https://drive.google.com/file/d/1TU9fFHwuxb8yB6HpfPXNP974Wu1dw0gQ/
    For SM-P580/gtanotexlwifi: https://drive.google.com/file/d/1kLy3M4h76L1JN0jX1C7piyPoS4Af78BS/

    Changelog:

    • Latest changes from LineageOS, including the 20220805 Android security updates, and a fix for "Intent Filter Verification Service" crashes that occurred in few/some cases with no Google apps or with MicroG.
    • Some things that appeared that are only relevant for devices with mobile networking (such as the baseband version and SIM status sections in About tablet in settings) no longer appear.
    • The ZRAM size has been increased to 2GiB, and the swappiness is now set to 100.
    • A higher frequency (1246MHz, was 902MHz previously) is now set for the interactive CPU governors "hispeed_freq" value - This improves responsiveness slightly.
    • The sepolicy containing device-specific SELinux rules has been improved slightly.
    • Yet more miscellaneous cleanups have been done.
    • Some updates from the 4.9 Android common kernel have been applied to the kernel.
    As always, enjoy.
    16
    New builds for 20220929

    Downloads:
    For SM-T580/gtaxlwifi: https://drive.google.com/file/d/15D5tDk91Xk1zS8GHhdW8tQ_qx8ndPrfE/
    For SM-P580/gtanotexlwifi: https://drive.google.com/file/d/1EwsZjA842T9otCInkxQYHADDkw7N8UTK/

    Changelog:

    • Latest changes from LineageOS, including the 20220905 Android security updates.
    • The torch has been fixed.
    • Performance of animations and responsiveness has been improved slightly.
    • Some updates from the 4.9 Android common kernel have been applied to the kernel.
    • [SM-P580/gtanotexlwifi only, already fixed in T580 builds long ago] 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 a different bright light source on it), has been fixed.
    • The WiFi drivers RX wakelock feature has been disabled - Heavy battery drain that occurred in sleep when connected to certain WiFi networks due to "qcom_rx_wakelock" wakelocks has been fixed.
    Later than usual with these builds due to yet more busyness. Will definitely try getting the next ones released earlier than usual.
    Nevertheless, just so managed to get several fixes into these, enjoy.