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
443
194
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
509
1,336
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
79
12
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: 82
  • photo_2023-02-05_22-26-26.jpg
    photo_2023-02-05_22-26-26.jpg
    95.3 KB · Views: 70
  • photo_2023-02-05_22-26-27.jpg
    photo_2023-02-05_22-26-27.jpg
    102.2 KB · Views: 76
  • photo_2023-02-05_22-26-28.jpg
    photo_2023-02-05_22-26-28.jpg
    37.3 KB · Views: 82
  • Like
Reactions: hamed_forum

Top Liked Posts

  • 3
    I may soon get some option for donations for those who'd like to donate.

    But before that, does anyone happen to know of a decent accessible alternative to PayPal for donations?

    I'm presuming not really, so I'm asking just in case.

    I don't like PayPal for its business practices, so I'd prefer not to use it. Could still use it if there isn't really any other decent option, though not great.


    Needing more RAM now; The initial stages of LineageOS 20 builds consume all my current 16GB and ZRAM set to a large size, and I'm even often close to running out during 12L builds while also doing other tasks, since upgrading to a much higher thread count CPU. So that's where donations would first go.

    That's a part of why I'm hesitant to start with LineageOS 20, apart from a lack of time and whatnot.

    I have to resort to a console to build 20 (for my newer main tablet, notably) and not go out-of-memory, no GUI, very uncomfortable.
    3
    I tested it on 7th revision tablet and TWRP Recovery is works good and we have touchscreen works
    but in Lineage OS 19.1 is not booted
    It still on lineage os logo loading but no boots
    (adb devices) cannot read this tablet on lineage OS booting
    so I take a logs from twrp recovery again and I take logs or last_kmsg and pstore folder from twrp file manager in ROM.zip I send it for you
    Thanks so much for the unofficial twrp builds and lineage os 19.1 and have a good luck for you ❤️🫡
    Hmm, okay, the pstore log is just good enough.

    Attached is a new boot image to try. Should definitely boot with it.
    2
    New builds for 20230603

    Downloads:

    [...]
    For gtanotexlwifi: https://drive.google.com/file/d/1MMhxvs1jNPHAgU5kDy4kaJ7AZ3MSXcLg/
    [...]
    Update without issues (not using GApps, Magisk or alike).
    New unofficial TWRP builds for all variants are up

    Downloads:

    [...]
    For gtanotexlwifi: Image here, tar for Odin here.
    [...]
    Also here no issues.

    Thank you! :)
    2
    Now I have a bug with headphone and speakers is working together
    so wait I will take logcat from matlog app and I will send it to you
    Hmm, weird. I specifically made changes to prevent such a problem, and I don't seem to have made any mistakes. Tricky.

    I'll leave this for later when I have time.
    When I do get time, I'll want you to get the output from a small program called "tinymix" while headphones are plugged in.

    (Also, by the way, just to make sure, that's completely normal with ringtones, and alarms (at least), so it's only a problem if you're trying to play media audio and not just testing ringtones and alarms.)

    ok
    just wait for me 🫡
    No information there for sensors. Log taken too late. Specifically need a log as soon as possible after booting, errors are only logged during boot as the sensors HAL starts up.

    I take that the accelerometer works fine.

    Also, try to keep as much as possible in one message, otherwise it looks a little spammy.
    1
    thx for keeping the tablet alive. Udate for the rom no problems and the new twrp also no problems
  • 13
    New builds for 20230603

    Downloads:
    For gtaxlwifi: https://drive.google.com/file/d/15f1R3z-pbBTxhix8d_fBzwI1NOPHN6Bl/
    For gtaxllte:
    https://drive.google.com/file/d/1Ba3whNROBXFn7vnpIHlWi9e9pkWR5BbA/
    For gtanotexlwifi: https://drive.google.com/file/d/1MMhxvs1jNPHAgU5kDy4kaJ7AZ3MSXcLg/
    For gtanotexllte: https://drive.google.com/file/d/1aDGexOX56dazYwAclICju977NAqYpAPH/

    Changelog:

    • Latest changes from LineageOS, including the 20230505 Android security updates.
    • (Untested) support for revision 7 gtaxllte devices, which were apparently exclusively for 2020 students in Egypt, has been added.
    Yep, that's about it for these builds. The major addition in these builds is just addition of support for revision 7 gtaxllte devices.
    Since there hasn't been any testing on a 7th revision device, I can't say for sure that everything works. Sensors and touch should work, can't be 100% sure about audio. (Those are the differences in hardware in revision 7 devices compared to the standard previous ones.)

    If anyone with a 7th revision device has any issues, do report them.
    (You'll have a 7th revision device if it didn't boot with previous builds and running getprop ro.boot.revision in a shell under Android returns 7, and of course got it as a student in 2020 in Egypt. No changes/improvements for all other devices here.)

    I'll release a new unofficial gtaxllte TWRP build, to support that 7th revision, as well as a gtaxlwifi build, and updated gtanotexl* builds, very soon (in the next day hopefully).
    Really no idea if I'll ever get around to taking over maintaining officially at this rate, but no big deal I suppose.

    Random thoughts:
    I really wonder why Samsung saw incentive to come up with a 7th revision for such a special purpose. I know there would've been an unavailability of some older chips used in older revisions, and so they've switched to newer chips in this new revision, but couldn't they have just pushed for a newer Samsung tablet to be used instead? These tablets got their last updates in 2020 anyway... Very odd and inconvenient.


    Still no kernel updates. Still the usual lack of time (and energy) + it looks all the more daunting to apply the hundreds of new patches now. Ugh.... I might look at applying only some security fixes when I actually get time, should be an okay compromise without using so much time backporting so many changes.

    Nevertheless, enjoy.
    9
    New unofficial TWRP builds for all variants are up

    Downloads:
    For gtaxlwifi:
    Image here, tar for Odin for AP slot is here.
    For gtaxllte: Image here, tar for Odin here.
    For gtanotexlwifi: Image here, tar for Odin here.
    For gtanotexllte: Image here, tar for Odin here.

    Of course, current official gtaxlwifi and gtaxllte TWRP builds will continue working fine, if not trying to use them on 7th revision gtaxllte devices.
    Still, these are newer (being built from newer sources and having a new kernel), so there's some benefit from that.
    6
    Okay, I'm going to bite. Because of my typical lack of time, I'll have to delay any responses to other posts needing ones until later.

    Since I'm getting email notifications for this thread, and looking out for posts on more important worse off issues, unproductive arguments serve as nothing more than aggravating distractions.

    You must not have been here when the search function was NOT so precise in filtering results. We have already solved that searching for "s-pen" is the exact term required for any results.
    First off: Far too harsh. Where do you expect to get with such harshness? Unwarranted response to a polite response. Entirely unproductive.

    I think where you've gone wrong is not trying "S-Pen" in the first place. It's the proper way to spell it, and the device name officially has it as S-Pen. So, logically, at least the majority of people are going to spell it that way and it's worth trying.

    I'd be surprised if it's your first experience with a search function requiring precise input, so much so that you couldn't think of that being a possibility, especially as the forum got switched to XenForo.

    Otherwise, we miss stuff, is there seriously any reason to get that mad?

    Quoting yourself repeatedly is just as unhelpful and a faux pas as blather about "a few eays ago."
    It would've undeniably been best if you would've looked at at least the last few pages of the thread to see any wide reports of issues, even without someone prompting you. Logically. It's even just common practice on forums, and gets active encouragement believe it or not.

    As the maintainer who has read every post in this thread, there haven't ever been any reports of the S-Pen not working at all. It isn't a matter of some people claiming that it works, and some not, it undoubtedly works for everyone, and there have been multiple times people have asked about the S-Pen with no reports of issues. I also do my best with the issues section in my original post.

    When CM came out for the P580 back around 2017, I tried it and ever since the spen has never worked on any non Samsung based roms. Hence why I am still on N! Many threads have claimed it was working, but invariably it would be someone spouting disinformation.
    Okay, bad experiences previously in different times with different situations, could let those go already?

    If people are saying that the S-Pen works, with no reports of it not working, and you ask if it does, and you think there's a possibility they're all wrong, what different result do you expect? Perhaps at that point, with no trust, it would just be better to backup your data and try for yourself?

    Your entitlement radiates through my monitor.

    Meanwhile, I'm surprised the P580 ever got cyanogenmod builds. I never knew. I also wouldn't have been surprised if they had a myriad of bugs. Times are different. Things are more mature.

    Now, in the meantime, no continuation of this argument, please.
    4
    my 2 cents? Just accept it and move on. 4 Posts just to let everyone know that the WEBSITE/FORUM search is incorrect is 4 posts too much. Sorry, but maybe we can get back to the important things here...

    @TALUAtXDA I will check again tonight and if nessessary I'll send the report :) Thanks for your reply and thanks for your hard work!
    4
    ok, problem solved. For some reason I had no ringtones on my tablet. I moved all tones from an older backup and now it workes just fine. Even the voice of my navigation is back. Happy now :)
    Odd for there to have been no ringtones at all, as well as navigation prompts to not have played. Not even the default ringtones? Anyway, glad it's fine now.

    Hi,
    just a few notes.
    ROM works great, no real issues so far. Really impressive!

    2 minor items :
    • I can not use the icon to change users on the lockscreen. It is there but when I click on it nothing really happens. If I slide over it I go to the unlock screen - but the way this should work is to allow user change on the locked tablet
    • The other one is related - I can see the functions that should be accessible from the lock screen (like the torch) by sliding from the top. But when I let go it just slides back and I can not enable anything. That behavior is more of an observation, the multi-user problem is slightly more annoying
    Maybe someone can confirm it works? It might very well also just be user error :)

    Best regards
    Glad to hear that.
    There's an option to switch users in the notification shade. It's one of the 4 options right below the quick settings tiles.
    I guess the user icon directly on the lock screen only really shows profile pictures now.

    The notification shade sliding back up after releasing it while in landscape specifically (with rotation on the lock screen enabled) is a real issue. It is an general AOSP issue, not device-specific, though, so outside of my scope.

    I just installed version 20230419. Clean install, no GApps or other packages.
    Previous version was LOS 17.1. Everything works fine, no trouble at all.

    Thank you so much for your work!!! You keep my 585 alive!

    Is there any chance of getting LTE Bluetooth calling to work some day?
    That`s the only thing i`m missing, especially while driving.
    Glad to know. You're very welcome.

    I've tried my best with getting Bluetooth calling working, but failed. I really have no further ideas for fixing it. Tried all the typical fixes for Samsung devices, nothing worked unfortunately. I suppose someone else would have to find a fix with that, only time will tell if someone will.
  • 59
    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 - All from 20230603 with security patch level 20230505
    For gtaxlwifi: https://drive.google.com/file/d/15f1R3z-pbBTxhix8d_fBzwI1NOPHN6Bl/
    For gtaxllte:
    https://drive.google.com/file/d/1Ba3whNROBXFn7vnpIHlWi9e9pkWR5BbA/
    For gtanotexlwifi: https://drive.google.com/file/d/1MMhxvs1jNPHAgU5kDy4kaJ7AZ3MSXcLg/
    For gtanotexllte: https://drive.google.com/file/d/1aDGexOX56dazYwAclICju977NAqYpAPH/


    Note: If you have a revision 7 gtaxllte device (which are apparently exclusively for 2020 students in Egypt), for the current gtaxllte build to boot, the boot image here is required. It won't be needed for future builds.
    For all other revisions, which are 99.9% of all devices (with the 7th revision having just that exclusive usage), the current gtaxllte build will work fine as-is.

    Recoveries to use
    Use my unofficial TWRP builds:
    For gtaxlwifi: Image here, tar for Odin for AP slot is here.
    For gtaxllte: Image here, tar for Odin here.
    For gtanotexlwifi: Image here, tar for Odin here.
    For gtanotexllte: Image here, tar for Odin here.

    Folders for builds
    Along with current builds, these contain text files with SHA256 checksums for builds, and folders containing few 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 20230603:
    • Latest changes from LineageOS, including the 20230505 Android security updates.
    • Support for revision 7 gtaxllte devices, which were apparently exclusively for 2020 students in Egypt, has been added. (Note: Boot image here required for a change needed to boot on the 7th revision for the 20200603 build, the change will be included in all future builds making it unnecessary for them.)
    Previous releases
    Builds for 20230419:
    • Latest changes from LineageOS, including the 20230405 Android security updates.
    • Linaro's new SLSI BSP (Board Support Package, containing sources for HWC and some other stuff) sources are now used - Much more up-to-date than the previously used sources, and there's possibly a small improvement in performance.
    • The OMX hardware video decoder and encoder libs are now built from the new Linaro BSP sources - With that, playback of HEVC videos is fixed in Chrome and other Chromium-based browsers.
    • Some updates from the 4.9 Android common kernel as of March have been applied to the kernel.
    • The wireguard kernel module has been added back - I silently removed it in the previous builds since it was unusable due to a now fixed device lockup bug that caused almost total unresponsiveness after enabling a wireguard VPN.
    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.
    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.
    27
    New builds for 20230419

    Downloads:
    For gtaxlwifi: https://drive.google.com/file/d/1HYynOu6aGNBjYQ4Xa2PgV3bfFV_MNkfX/
    For gtaxllte:
    https://drive.google.com/file/d/1KgsUF_S2mUKAz7_vlHc8-EriN0MeGIlT/
    For gtanotexlwifi: https://drive.google.com/file/d/1i-Ixj9H0CXqFOmgL4pArds2c2DtliDEI/
    For gtanotexllte: https://drive.google.com/file/d/1_JC0PrPNPWSjzuAbZHPYwBfQwNmm_G19/

    Changelog:

    • Latest changes from LineageOS, including the 20230405 Android security updates.
    • Linaro's new SLSI BSP (Board Support Package, containing sources for HWC and some other stuff) sources are now used - Much more up-to-date than the previously used sources, and there's possibly a small improvement in performance.
    • The OMX hardware video decoder and encoder libs are now built from the new Linaro BSP sources - With that, playback of HEVC videos is fixed in Chrome and other Chromium-based browsers.
    • Some updates from the 4.9 Android common kernel as of March have been applied to the kernel.
    • The wireguard kernel module has been added back - I silently removed it in the previous builds since it was unusable due to a now fixed device lockup bug that caused almost total unresponsiveness after enabling a wireguard VPN.
    Wow, I didn't notice how long I really left this stuff for.

    Anyway, some nice improvements in these builds.
    The kernel updates are behind by a month due to... yep, a lack of time and other previously mentioned reasons. As always, I'll try getting them in at some point later. I'm really hoping these don't become unsustainable, keeping up and trying to defy that the 3.18 kernel is no longer maintained upstream since a really long while is certainly becoming more difficult.

    In any case, enjoy.
    23
    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.
    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