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

Search This thread

gelidd

New member
Apr 24, 2021
2
0
I'm trying to use t580 as a wifi dongle from time to time, but USB tethering does not seem to work. Does it work for anyone?
 

SupremeKing5810

Senior Member
Mar 20, 2021
80
51
Samsung Galaxy S III I9300
Can anyone please tell a good method for backing up your whole tablet? By that I mean, app data, images, videos, documents and all that stuff. I've checked out NeoBackup, but it requires root, which I haven't done yet, because I'm still running Stock Oreo and I'm planning to flash this ROM tomorrow. Also I don't have TWRP, as I have mentioned above, I'm still in stock ROM.

Thanks in advance:)
 

odoll

Senior Member
[...] whether I should use my 400GB SD card as tablet storage or portable storage [...]
Maybe both?! Dunno if that trick still works, but it's maybe worth a try.
[...]
OK, it's a bit more tricky than that. What I just did. I inserted a 64 (59) G(i)B SD and formatted it as internal tablet storage.
When you look at the SD's storage layout after that (I use diskpart on a W10 PC) you will notice two partitions
Code:
DISKPART> lis part

  Partition ###  Typ               Größe    Offset
  -------------  ----------------  -------  -------
  Partition 1    Unbekannt           16 MB  1024 KB
  Partition 2    Unbekannt           59 GB    17 MB
In a next step I cloned the SD to another 200 GB SD (either use e.g. dd - I used Winimage) and created a third partition - I just sized it 58 GB, because I still want to fit the whole thing onto an 120 GB SD in the end) and formatted that as exFAT, naming it portable. Thus I ended up with the following layout
Code:
DISKPART> lis part

  Partition ###  Typ               Größe    Offset
  -------------  ----------------  -------  -------
  Partition 1    Unbekannt           16 MB  1024 KB
  Partition 2    Unbekannt           59 GB    17 MB
  Partition 3    Primär              58 GB    59 GB
And voilà
Screenshot_20230201-200717_Einstellungen.png
PS: This SM-T580 comes with native 32 GB
 

jjcasti

Member
Jan 30, 2023
6
1
Good morning, I am a new user here, although I usually read your posts and I am grateful for it.
I use the transducer so I apologize.

My problem is the following: I have a sm-t585 gtaxlte (well, my brother) and he brings it to me because I installed lineage 19.1 and now the call and SMS icons and the Sims icon in settings appear in dark gray and do not react when clicked. when starting the tablet with the without inside it does not recognize it. After much reading in the forums I have not been able to solve anything, I have to say that it does have Imei.
If I install a stock rom something very curious happens, when it reboots it says insert the sim, I do it and the device reboots but it still doesn't detect it and it says no sim card only emergency calls, but in the right corner the signal bars appear,
With odin I have tried to install other modems but the signal bars disappear and it puts a crossed out circle,
The tablet has binary 7 since my brother told me that he had updated it, he didn't copy EFS or anything, so I don't know if the firmware I had was correct, and I don't know what else to do because I've been testing for a month things and nothing,,, I would be very grateful for a solution,, greetings
 

Uluru25

Senior Member
Nov 27, 2016
392
152
Samsung Galaxy S7
Samsung Galaxy A6
Good morning, I am a new user here, although I usually read your posts and I am grateful for it.
I use the transducer so I apologize.

My problem is the following: I have a sm-t585 gtaxlte (well, my brother) and he brings it to me because I installed lineage 19.1 and now the call and SMS icons and the Sims icon in settings appear in dark gray and do not react when clicked. when starting the tablet with the without inside it does not recognize it. After much reading in the forums I have not been able to solve anything, I have to say that it does have Imei.
If I install a stock rom something very curious happens, when it reboots it says insert the sim, I do it and the device reboots but it still doesn't detect it and it says no sim card only emergency calls, but in the right corner the signal bars appear,
With odin I have tried to install other modems but the signal bars disappear and it puts a crossed out circle,
The tablet has binary 7 since my brother told me that he had updated it, he didn't copy EFS or anything, so I don't know if the firmware I had was correct, and I don't know what else to do because I've been testing for a month things and nothing,,, I would be very grateful for a solution,, greetings
I am also not an expert for this, but from a different phone I remember similiar problems when flashing a not suitable firmware. Therefore I would recommend that you try to reflash the newest available stock rom (by doing so you will have the most recent firmware) and afterwards to switch to LOS19.1. See here.
 
Last edited:

jjcasti

Member
Jan 30, 2023
6
1
I am also not an expert for this, but from a different phone I remember similiar problems when flashing a not suitable firmware. Therefore I would recommend that you try to reflash the newest available stock rom (by doing so you will have the most recent firmware) and afterwards to switch to LOS19.1. See here.
Thanks for the answer, I had already returned to the stock rom SM-T585_1_20210927111006_35hw5j1clu_fac_T585XXS7CUI2_T585PHE7CUI2_T585XXS7CUI2_T585XXS7CUI2_PHE which is android 8.1, everything works fine except the mobile network, the signal bars appear, but it does not detect the sim. I have installed several different modems using odin, but the signal bars disappear, so I think it is not a problem with the custom rom modem. The problem is that the binary was uploaded to 7, and I no longer know which firmware to install because I don't know which one was the original. I have read and tried everything but I don't know what to do anymore. thank you very much for trying... By the way, the mobile network option does not appear in settings.
 

jjcasti

Member
Jan 30, 2023
6
1
Well I'm still investigating, it turns out that I opened the tablet and on the sticker inside the imei matches except that the termona sticker is /5 and when dialing *#06# on the screen it ends in /01.
Another thing that I have observed is that the serial number on the sticker and the one in settings / about the tablet do not match.
The more I investigate, the more strange things I see.
on the page https://imei.net
I discovered that I had the free Italian version with Android Android 6.0 Marshmallow but I think that because of the binaries it won't let me reinstall it
 

TALUAtXDA

Senior Member
Nov 8, 2018
494
1,222
Well I'm still investigating, it turns out that I opened the tablet and on the sticker inside the imei matches except that the termona sticker is /5 and when dialing *#06# on the screen it ends in /01.
Another thing that I have observed is that the serial number on the sticker and the one in settings / about the tablet do not match.
The more I investigate, the more strange things I see.
on the page https://imei.net
I discovered that I had the free Italian version with Android Android 6.0 Marshmallow but I think that because of the binaries it won't let me reinstall it
The /05 vs /01 difference doesn't matter. I'm pretty sure I've even seen similar on Samsung devices running Samsung's stock firmware(/ROM), though don't quote me on that. As long as the rest of it shows up fine, there shouldn't be any problems.

The different serial also isn't an issue. If I remember correctly, there's an "Android serial" and "Samsung serial". The one in "About tablet" is the "Android serial". Both are unique to your tablet. Not much use in getting the Samsung serial in place of the Android serial there, if possible, I don't think.

Also, as long as the latest firmware (bootloader + modem firmware) is installed, if nothing is wrong with your hardware, things should work fine. Messing with different modem firmwares is pretty dead-end, I'm using T585XXS7CUI2 modem firmware on my T585 with no issues. The latest is all I can support, anyway.

Since you're having similar problems on the latest stock firmware, there would definitely be a hardware issue.
The signal indicator while no SIM is inserted on the stock firmware is simply just there to show there is a signal, and useless unless making sure you can make emergency calls. I'm pretty sure it just isn't shown on newer Android versions with no SIM inserted.

Your problems might be caused by a bad SIM slot. I'm pretty sure it's connected via a ribbon cable and removable, so since you've opened your tablet up already, replacing it should be easy.
Otherwise, there's likely a chance there's something wrong on the main board, which is where things get too complicated.
 

jjcasti

Member
Jan 30, 2023
6
1
The /05 vs /01 difference doesn't matter. I'm pretty sure I've even seen similar on Samsung devices running Samsung's stock firmware(/ROM), though don't quote me on that. As long as the rest of it shows up fine, there shouldn't be any problems.

The different serial also isn't an issue. If I remember correctly, there's an "Android serial" and "Samsung serial". The one in "About tablet" is the "Android serial". Both are unique to your tablet. Not much use in getting the Samsung serial in place of the Android serial there, if possible, I don't think.

Also, as long as the latest firmware (bootloader + modem firmware) is installed, if nothing is wrong with your hardware, things should work fine. Messing with different modem firmwares is pretty dead-end, I'm using T585XXS7CUI2 modem firmware on my T585 with no issues. The latest is all I can support, anyway.

Since you're having similar problems on the latest stock firmware, there would definitely be a hardware issue.
The signal indicator while no SIM is inserted on the stock firmware is simply just there to show there is a signal, and useless unless making sure you can make emergency calls. I'm pretty sure it just isn't shown on newer Android versions with no SIM inserted.

Your problems might be caused by a bad SIM slot. I'm pretty sure it's connected via a ribbon cable and removable, so since you've opened your tablet up already, replacing it should be easy.
Otherwise, there's likely a chance there's something wrong on the main board, which is where things get too complicated.
THANKSSSSSSSSS The truth is, after a month of reading forums and looking for solutions, nothing worked and since you told me that it could be a hardware failure, I checked the Flex SIM Reader Module. I proceeded to disassemble and clean it and voilaaaaaa the network signal appeared again. It could be some accidental blow that disconnected it from the flex. I don't know how to thank you because my eyesight was already leaving me reading pages and more pages and the computer has 100 programs and roms downloaded. It worked with the custom rom and now I just installed lineageos 19.1 and it works fine. REALLY THANK YOU AND THE XDA FORUM, GUYS THE BEST OF THE BEST. PS sorry for the English I use the translator
 
Last edited:
  • Like
Reactions: zeb carter

alireza9082

Senior Member
Dec 10, 2022
69
9
I installed this rom;)
it's very smooth and I don't see any issue on this rom(y):)

thank you so much:love::love:
 

Attachments

  • photo_2023-02-05_22-26-33.jpg
    photo_2023-02-05_22-26-33.jpg
    40.7 KB · Views: 76
  • photo_2023-02-05_22-26-26.jpg
    photo_2023-02-05_22-26-26.jpg
    95.3 KB · Views: 65
  • photo_2023-02-05_22-26-27.jpg
    photo_2023-02-05_22-26-27.jpg
    102.2 KB · Views: 70
  • photo_2023-02-05_22-26-28.jpg
    photo_2023-02-05_22-26-28.jpg
    37.3 KB · Views: 76
  • Like
Reactions: hamed_forum

Top Liked Posts

  • There are no posts matching your filters.
  • 20
    Since I haven't posted anything for weeks now, I thought I'd give an update.

    With me being yet more busy, and things constantly changing, and health issues on top (though don't worry about me), I haven't had much time to work on this stuff much.

    Within my sources, I've fixed a bug, and applied kernel updates, but haven't had any real opportunities to release any new builds. I should be able to get around to getting new builds out in the next week or so.

    I don't really have time to reply to much of anything at the moment, so if there is anything to reply to, I'll be leaving replies for later.
    3
    SM-P585Y ...

    1. I can't turn on hotspot tethering. I tried the pull-down menu and settings, but none of them seemed to work. When I open Settings, it shows "error" text below the Wi-Fi hotspot.

    Is there any workaround to solve these problems? At least I want my device to be able to turn on hotspot tethering.
    I tried the WiFI hotspot on my SM-T585.
    Like you, I could not activate it through the settings menu. After touching the switch and after some time it returns to off and says "error".

    However, when I use the quick-settings button for "Hotspot", then switching-on works, and the WiFi hotspot can be used.
    3
    Since I haven't posted anything for weeks now, I thought I'd give an update.

    With me being yet more busy, and things constantly changing, and health issues on top (though don't worry about me), I haven't had much time to work on this stuff much.

    Within my sources, I've fixed a bug, and applied kernel updates, but haven't had any real opportunities to release any new builds. I should be able to get around to getting new builds out in the next week or so.

    I don't really have time to reply to much of anything at the moment, so if there is anything to reply to, I'll be leaving replies for later.
    Health above all! Take care
    2
    Bluetooth doesn't work for me at all, I can't even turn it on. I tried resetting the "Bluetooth" app from Package Manager as well as deleting data in settings, but that didn't make any difference.

    I'm using the SM-T580
    No known issues here either with both SM-P580 (using for file transfer) and SM-T580 (using with keyboard).
    2
    No, you do not have to flash the latest Samsung firmware beforehand. Just flash TWRP 3.7.0 with Odin and then format the data partition there.

    Before the whole thing you have to enable the flashing of the bootloader in the development settings and copy the LineageOS firmware and the GApps (Pico) to the SDCard, so you can install them from TWRP right away.

    GApps have to be installed before the first boot, otherwise it won't work to certify the device with Google. At least that was the case for me at the first attempt.

    I can't remember if you need the arm64 or arm GApps, so just copy both to the SDCard. One of them you can install, the other one throws an error ;-)

    open_gapps-arm64-12L-pico-20220705-UNOFFICIAL_MOD.zip
    open_gapps-arm-12L-pico-20220705-UNOFFICIAL_MOD.zip
    All done. Lineage OS installed with Gapps Pico 1.2 (ARM64), Magisk and LsPosed.
  • 55
    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.
    20
    Since I haven't posted anything for weeks now, I thought I'd give an update.

    With me being yet more busy, and things constantly changing, and health issues on top (though don't worry about me), I haven't had much time to work on this stuff much.

    Within my sources, I've fixed a bug, and applied kernel updates, but haven't had any real opportunities to release any new builds. I should be able to get around to getting new builds out in the next week or so.

    I don't really have time to reply to much of anything at the moment, so if there is anything to reply to, I'll be leaving replies for later.
    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
    19
    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.