• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

dovedescent7

Senior Member
Jun 18, 2011
256
12
Note 2 for those who upgraded to the first build from 20210810, "signed with my own release keys (which doesn't have "-R2-Test-keys" in its filename): Before upgrading to a newer build, you must install this package to switch your installation back to test-keys with data mounted in TWRP recovery: https://drive.google.com/file/d/1gYVI71QEtfMafGssPfWW-6UAH2dLd3wO/ Otherwise, you will encounter issues! Make sure "Reboot after installation is complete" is disabled in both TWRP settings and when installing that package, or you will also encounter issues.


Thanks so much for the work!

I'm ready to install this but not familiar AT ALL with all this talk of Keys and Signed keys...

My t580 is on an official ( i think) lineageos like 16 or something.

Can i simply flash this rom over an official lineageos without worrying about all this "Key" stuff?

Our would i need to install one of your earlier builds of this THEN install your latest one from Page 7???

If not could you tell me the process of how to install this over something that WASNT one of your previous builds, but still using TWRP?


Thank you kindly...
 

TALUAtXDA

Senior Member
Nov 8, 2018
379
651
Thanks so much for the work!

I'm ready to install this but not familiar AT ALL with all this talk of Keys and Signed keys...

My t580 is on an official ( i think) lineageos like 16 or something.

Can i simply flash this rom over an official lineageos without worrying about all this "Key" stuff?

Our would i need to install one of your earlier builds of this THEN install your latest one from Page 7???

If not could you tell me the process of how to install this over something that WASNT one of your previous builds, but still using TWRP?


Thank you kindly...
That note is only for people who installed the build with filename "lineage-18.1-20210810-UNOFFICIAL-gtaxlwifi.zip", without "-R2-Test-keys" in it (which my latest build does have). Since you did not install that build, you can ignore that specific mess.

There was never official LineageOS for this tablet.

If you are currently on one of Valera1978's LineageOS 16.0 builds from this thread: https://forum.xda-developers.com/t/...ficial-lineageos-16-0-64bit-20191211.3845016/, you should be able to just upgrade to my latest build (without anything related to signing needed to be done). I think upgrading to 18.1 from 16.0 should work, although I can't be entirely certain.

If you are currently on one of Klaerchen's LineageOS 16.0 builds from this thread: https://forum.xda-developers.com/t/...l-lineageos-16-for-galaxy-tab-a-2016.4083157/, you need to run the script in the zip archive downloadable from here: https://androidfilehost.com/?fid=2188818919693800974 with the argument 'unofficial', like so:
Code:
sh /path/to/migration-achalmgucker.sh unofficial
...in recovery (using TWRP's terminal function or ADB shell) with data mounted or booted in Android in a shell with root access before installing my latest build.
If you struggle to run it, I can make a migration package that does the same thing as that script that you can install through TWRP before installing my latest build.

So, installation should basically go like this:
  • Run the script, only if you're on one of Klaerchen's LineageOS 16.0 builds. Don't reboot into Android after running it if you haven't installed my latest build!
  • Format system in TWRP.
  • Install my build.
  • Install any up-to-date versions of packages that you want that are compatible with Android 11 (such as a google apps package if you need one).
Before starting, I suggest backing up any important data in case anything goes wrong.
 
Last edited:
  • Like
Reactions: andreas__

dovedescent7

Senior Member
Jun 18, 2011
256
12
That note is only for people who installed the build with filename "lineage-18.1-20210810-UNOFFICIAL-gtaxlwifi.zip", without "-R2-Test-keys" in it (which my latest build does have). Since you did not install that build, you can ignore that specific mess.

There was never official LineageOS for this tablet.

If you are currently on one of Valera1978's LineageOS 16.0 builds from this thread: https://forum.xda-developers.com/t/...ficial-lineageos-16-0-64bit-20191211.3845016/, you should be able to just upgrade to my latest build (without anything related to signing needed to be done). I think upgrading to 18.1 from 16.0 should work, although I can't be entirely certain.

If you are currently on one of Klaerchen's LineageOS 16.0 builds from this thread: https://forum.xda-developers.com/t/...l-lineageos-16-for-galaxy-tab-a-2016.4083157/, you need to run the script in the zip archive downloadable from here: https://androidfilehost.com/?fid=2188818919693800974 with the argument 'unofficial', like so:
Code:
sh /path/to/migration-achalmgucker.sh unofficial
...in recovery (using TWRP's terminal function or ADB shell) with data mounted or booted in Android in a shell with root access before installing my latest build.
If you struggle to run it, I can make a migration package that does the same thing as that script that you can install through TWRP before installing my latest build.

So, installation should basically go like this:
  • Run the script, only if you're on one of Klaerchen's LineageOS 16.0 builds. Don't reboot into Android after running it if you haven't installed my latest build!
  • Format system in TWRP.
  • Install my build.
  • Install any up-to-date versions of packages that you want that are compatible with Android 11 (such as a google apps package if you need one).
Before starting, I suggest backing up any important data in case anything goes wrong.

Thank you for taking the time to write this up man! You are good people. Yes i realized that there's no official lineageos 16 for this after writing that.

But just to update: I went ahead and flashed your 18.1 in TWRP over the previous lineageos. It seemed to work flawlessly, with the exception of the first 10 minutes (while google was restoring apps etc) because the screen was very very unresponsive, UNTIL restoring everything was finished,, then it was fine..

If it helps anyone, I'm 85% certain that the rom I had on the device prior to flashing this was this:
"lineage-16.0-20201109-achalmgucker-gtaxlwifi-signed.zip" downloaded here at XDA as i have no other lineageos files on my PC., and i had just recently flashed that, the ver 16. Seems to be working ok.

May i bother the OP, or anyone else willing to help with a few more elementary questions regarding tweaking this Lineageos?
  1. I'd like to know if there's an easy way to keep Lineageos yet change the theme of the ENTIRE tablet software so it looks as if its stock Samsung one ui? Make it look almost exactly, or as much as possible, like a stock samsung tablet? Icons and all? Maybe a launcher that does this? Its because my 5yr old is used to all Samsung UI and doesn't like the icons, colors, she just wants it close to the regular Samsung UI. Is there a relatively easy fix/trick for this?
  2. Is there an option on this rom (like on my S10e) to increase Touch Sensitivity? In settings the s10e states "its to increase touch sensitivity for use with screen protectors" I'd LOVE to know where this setting is.
  3. Lastly, does this rom allow for overclocking the CPU?

Thanks op/dev! And yall
 

Zeppelli

Member
Jun 26, 2021
16
4
Yes, I'm planning to start attempting to work on it sometime in a few days. I'll release a new test build for the LTE variant if I get one ready, or make a post asking for testers if necessary (how I would organise a group of testers is still undecided, thinking about maybe setting up a Telegram group and possibly some alternative alongside, or something). I've started thinking about how I'd go about this already.

You're welcome.
That's just great, if you want I would be ready to test the build when it's ready.
You can reach me using telegram @Itcraft093
 

Uluru25

Senior Member
Nov 27, 2016
158
58
Samsung Galaxy A6
Redmi Note 8
Wonderful to have a LOS rom for this tablet - thanks!
Two questions:
1. I guess after installing this rom the data partition will be encrypted by default?

2. If so, can I easily flash the Disable_Dm-Verity_ForceEncrypt.zip before rebooting or is there something specific to keep in mind?

Thx again!
 

bswinburne

New member
Aug 20, 2021
1
0
Great work, I love the OS. Just one question though, is it correct that ANT+ does not work under LineageOS? Been trying to get Zwift to work with my ANT+ sensors under LOS and it does not want to find them.
 

TALUAtXDA

Senior Member
Nov 8, 2018
379
651
Wonderful to have a LOS rom for this tablet - thanks!
Two questions:
1. I guess after installing this rom the data partition will be encrypted by default?

2. If so, can I easily flash the Disable_Dm-Verity_ForceEncrypt.zip before rebooting or is there something specific to keep in mind?

Thx again!
You're welcome. Data is not encrypted by default. I don't know why you'd want to remove encryption if it was, anyway, since it has no impact on performance and decryption works in TWRP recovery.
Great work, I love the OS. Just one question though, is it correct that ANT+ does not work under LineageOS? Been trying to get Zwift to work with my ANT+ sensors under LOS and it does not want to find them.
I'm glad you love it. ANT+ isn't supported specifically under my LineageOS builds, and also never was under any other custom firmwares/ROMs for this device.

I'm totally unsure about it. I think to add support for ANT+, I'd need to add some proprietary stuff, which I would strongly prefer not to do. But it might not be as simple as that, though. Hmm...
Hello and thank you for all the work. I would like to know how to share the connection via usb? I tried but it doesn't work with lineage.
You're also welcome. Assuming that by "share the connection via USB" you mean share your tablets internet connection via USB with, for example, a computer to which your tablet is connected, you need to enable USB tethering at Settings -> Network and Internet -> Hotspot and tethering -> USB tethering if you haven't tried that already. I just tested it here, and it works fine.
 
Last edited:
  • Like
Reactions: Uluru25

Uluru25

Senior Member
Nov 27, 2016
158
58
Samsung Galaxy A6
Redmi Note 8
You're welcome. Data is not encrypted by default. I don't know why you'd want to remove encryption if it was, anyway, since it has no impact on performance and decryption works in TWRP recovery.

I'm glad you love it. ANT+ isn't supported specifically under my LineageOS builds, and also never was under any other custom firmwares/ROMs for this device.

I'm totally unsure about it. I think to add support for ANT+, I'd need to add some proprietary stuff, which I would strongly prefer not to do. But it might not be as simple as that, though. Hmm...

You're also welcome. Assuming that by "share the connection via USB" you mean share your tablets internet connection via USB with, for example, a computer to which your tablet is connected, you need to enable USB tethering at Settings -> Network and Internet -> Hotspot and tethering -> USB tethering if you haven't tried that already. I just tested it here, and it works fine.
Thx! I am also wondering if I have to update the firmware beforehand since I never made an ota update up to now with the stock rom? And if needed or recommended: how to do so? Where can I download the most up to date firmware?
 

LaPesteO_o

New member
Feb 5, 2012
1
0
Bologna
Hi. I have a simple question, mainly fueled by curiosity:
What's holding this work of yours back from becoming official? What are the official requirements that you can't meet with this work?
I'm not super familiar with this in general, so if you can use more than just 2 words per requirement, It'd be appreciated.

Thanks
 

TALUAtXDA

Senior Member
Nov 8, 2018
379
651
Thx! I am also wondering if I have to update the firmware beforehand since I never made an ota update up to now with the stock rom? And if needed or recommended: how to do so? Where can I download the most up to date firmware?
I would strongly recommend doing so, and it would be a necessity if you've got a particularly old version of the stock firmware.

Assuming you're still on an older version of the stock firmware (although it seems you're implying that you're not), to update, you can, of course, simply go ahead and use the built-in software updater for the first time to upgrade to the latest version of it without doing anything additionally. That would be the easiest way to go about it.

Alternatively, assuming you would do so using a computer running Windows, here are some basic instructions on how you would go about doing so:
You need two tools:
1. A tool called Frija. Use it to download a zip archive containing the latest firmware for your country. You need to specify a CSC for the firmware ("Consumer Software Customization"/"Country Specific Code") (You can find which CSC you need using an app like Devcheck (System -> Original CSC in it), or maybe it's somewhere in the "About tablet" section of settings in the stock firmware. There are also lists of CSC's you can search for that you can get the CSC for your country from.), which can be downloaded from here: https://forum.xda-developers.com/t/tool-frija-samsung-firmware-downloader-checker.3910594/.
2. Another tool called Odin to install it. I've got my copy of it from here: https://build.nethunter.com/samsung-tools/Odin_3.13.1.zip

After downloading those tools and the stock firmware using Frija, you should be able to go about installing it by basically doing the following:
  • Extract the downloaded zip archive containing the stock firmware.
  • Open Odin, and select the extracted .tar.md5 files for the corresponding slots - The one with the filename beginning with "AP_" to the AP slot, "BL_" to the BL slot, and "CSC_" to the CSC slot. Ignore the file with the filename beginning with "HOME_CSC_" - Using the one with the filename beginning with "CSC_" will get you a clean install with your data formatted, and using the one with the filename beginning with "HOME_CSC_" will not get your data formatted.
  • Connect your tablet to your computer while it's booted into download mode (Although I'm assuming you know how to, just for information, power it off, and hold Power + Volume Down + Home, and press the Volume Up button to confirm the warning. Just for even more information which might end up being useful, to get out of download mode for whatever reason after accepting the warning, you can hold down Power + Volume down for several seconds.)
  • Wait for Odin to detect your tablet (it should be nearly instant unless there are drivers to automatically install), and start the installation, making sure not to accidentally disconnect your device.
Note that when it reboots, if you were running the stock firmware and were signed into a Google account, you'd need to connect to a WiFi network and enter the credentials for it, unless you've disabled Factory Reset Protection by enabling the "OEM unlock" option in developer options.
If Odin doesn't detect your tablet while booted into download mode, you may need to install the drivers from here: https://developer.samsung.com/mobile/android-usb-driver.html
Let me know if you struggle with it if you go with this route.
 
Last edited:

TALUAtXDA

Senior Member
Nov 8, 2018
379
651
Hi. I have a simple question, mainly fueled by curiosity:
What's holding this work of yours back from becoming official? What are the official requirements that you can't meet with this work?
I'm not super familiar with this in general, so if you can use more than just 2 words per requirement, It'd be appreciated.

Thanks
There are several general reasons for why it's not possible to go official. Here are just a few:
  • Going official would require me to go about doing things that are incredibly difficult and time consuming. Apparently, my sources to build LineageOS would need to be completely redone, which would be an extremely extensive process.
  • There are still a few issues that haven't been fixed, and as it looks like won't be anytime soon. See the "Known issues and workarounds (if any)" section of my original post.
  • To go official, there are unfavourable restrictions that I'd need to conform to. As an example, there is an overclock to the CPU to 1.69GHz, and there are some voltage control interfaces in the kernel, which would need to be removed, as that type of stuff isn't allowed. That particular restriction is understandable due to stability concerns, but again, it's not favourable, and it's just one restriction.
You're welcome.
 
Last edited:

Uluru25

Senior Member
Nov 27, 2016
158
58
Samsung Galaxy A6
Redmi Note 8
I would strongly recommend doing so, and it would be a necessity if you've got a particularly old version of the stock firmware.

Assuming you're still on an older version of the stock firmware (although it seems you're implying that you're not), to update, you can, of course, simply go ahead and use the built-in software updater for the first time to upgrade to the latest version of it without doing anything additionally. That would be the easiest way to go about it.

Alternatively, assuming you would do so using a computer running Windows, here are some basic instructions on how you would go about doing so:
You need two tools:
1. A tool called Frija. Use it to download a zip archive containing the latest firmware for your country. You need to specify a CSC for the firmware ("Consumer Software Customization"/"Country Specific Code") (You can find which CSC you need using an app like Devcheck (System -> Original CSC in it), or maybe it's somewhere in the "About tablet" section of settings in the stock firmware. There are also lists of CSC's you can search for that you can get the CSC for your country from.), which can be downloaded from here: https://forum.xda-developers.com/t/tool-frija-samsung-firmware-downloader-checker.3910594/.
2. Another tool called Odin to install it. I've got my copy of it from here: https://build.nethunter.com/samsung-tools/Odin_3.13.1.zip

After downloading those tools and the stock firmware using Frija, you should be able to go about installing it by basically doing the following:
  • Extract the downloaded zip archive containing the stock firmware.
  • Open Odin, and select the extracted .tar.md5 files for the corresponding slots - The one with the filename beginning with "AP_" to the AP slot, "BL_" to the BL slot, and "CSC_" to the CSC slot. Ignore the file with the filename beginning with "HOME_CSC_" - Using the one with the filename beginning with "CSC_" will get you a clean install with your data formatted, and using the one with the filename beginning with "HOME_CSC_" will not get your data formatted.
  • Connect your tablet to your computer while it's booted into download mode (Although I'm assuming you know how to, just for information, power it off, and hold Power + Volume Down + Home, and press the Volume Up button to confirm the warning. Just for even more information which might end up being useful, to get out of download mode for whatever reason after accepting the warning, you can hold down Power + Volume down for several seconds.)
  • Wait for Odin to detect your tablet (it should be nearly instant unless there are drivers to automatically install), and start the installation, making sure not to accidentally disconnect your device.
Note that when it reboots, if you were running the stock firmware and were signed into a Google account, you'd need to connect to a WiFi network and enter the credentials for it, unless you've disabled Factory Reset Protection by enabling the "OEM unlock" option in developer options.
If Odin doesn't detect your tablet while booted into download mode, you may need to install the drivers from here: https://developer.samsung.com/mobile/android-usb-driver.html
Let me know if you struggle with it if you go with this route.
Since I am always rooted and running TWRP as recovery I would like to find a way to update the phone without loosing TWRP. Is there a hasslefree way you could recommend? If not, it seems I have to choose ota and then agai Odin for flashing TWRP (but if I do remember correctly it was a little painful).
 

TALUAtXDA

Senior Member
Nov 8, 2018
379
651
Since I am always rooted and running TWRP as recovery I would like to find a way to update the tablet without loosing TWRP. Is there a hasslefree way you could recommend? If not, it seems I have to choose ota and then again Odin for flashing TWRP (but if I do remember correctly it was a little painful).
Updating the stock firmware using the built-in software updater won't work since you've got root access and TWRP installed. The stock recovery is required to use it, and it would simply not allow you to update as you've got such modifications. With this, installation using Odin is your only option.

In relation purely to installing an up-to-date version of the stock firmware using Odin, keeping TWRP would probably cause issues, since some preparation stuff would need to be done with the stock recovery after your tablet automatically reboots after installation, although I don't think that the preparation stuff would be important since you're going to be installing my LineageOS build afterwards anyway.

If you can install the stock firmware using Odin, or otherwise have Odin working, It shouldn't actually be very difficult to reinstall/reflash TWRP after installing the latest version of the stock firmware. I suggest just going with this route to avoid any issues. To reinstall TWRP, you would need to download the latest .tar archive for TWRP for installation using Odin from here: https://dl.twrp.me/gtaxlwifi/, select it in Odin for the AP slot, boot your tablet into download mode, connect it to your computer, start the installation in Odin, and right before it reboots from download mode after finishing, hold the combination of buttons for recovery mode. It should then boot into TWRP.
 
Last edited:
  • Like
Reactions: Uluru25

Uluru25

Senior Member
Nov 27, 2016
158
58
Samsung Galaxy A6
Redmi Note 8
Updating the stock firmware using the built-in software updater won't work since you've got root access and TWRP installed. The stock recovery is required to use it, and it would simply not allow you to update as you've got such modifications. With this, installation using Odin is your only option.

In relation purely to installing an up-to-date version of the stock firmware using Odin, keeping TWRP would probably cause issues, since some preparation stuff would need to be done with the stock recovery after your tablet automatically reboots after installation, although I don't think that the preparation stuff would be important since you're going to be installing my LineageOS build afterwards anyway.

If you can install the stock firmware using Odin, or otherwise have Odin working, It shouldn't actually be very difficult to reinstall/reflash TWRP after installing the latest version of the stock firmware. I suggest just going with this route to avoid any issues. To reinstall TWRP, you would need to download the latest .tar archive for TWRP for installation using Odin from here: https://dl.twrp.me/gtaxlwifi/, select it in Odin for the AP slot, boot your tablet into download mode, connect it to your computer, start the installation in Odin, and right before it reboots from download mode after finishing, hold the combination of buttons for recovery mode. It should then boot into TWRP.
Thx for yourdetailed and precious support!
 
  • Like
Reactions: TALUAtXDA

TALUAtXDA

Senior Member
Nov 8, 2018
379
651
I've made a build for the WiFi-only variant of the Samsung Galaxy Tab A 10.1" (2016) with S-Pen, with model SM-P580 and codename gtanotexlwifi, which can be downloaded from here: https://drive.google.com/file/d/1Sw7pEuAEYB-tFtGM3t0AXSrlGrUQFnqK/

After seeing some posts from people searching for a custom firmware/ROM for that tablet (although it seems mostly for the LTE variant), someone having had reported that my builds for gtaxlwifi don't boot on it (after forcing installation) earlier in this thread, and seeing that there shouldn't be very many changes to make for a build for it when looking into it, I decided to go ahead and make the changes for it in a copy of my existing gtaxlwifi device tree, and make this build. The changes are mostly with the kernel and, most significantly, DT image in the boot image.

For installation, the TWRP build from here should be used: https://forum.xda-developers.com/t/...-for-p580-oreo-compatible-unofficial.4048671/ The official TWRP builds for gtanotexlwifi are reported to have severe graphical glitches, due to Samsung having made some change in their later bootloaders, and the kernel used in them being outdated. I plan to make an up-to-date TWRP build myself based on new sources later on.

Since I don't have a P580, this build is untested, so I can't be sure if it boots and works properly or not. However, I don't see any reason for it not to. The one thing I know for sure is that S-Pen functionality would definitely be missing.
For anyone who has tested this build, if it works, please report that it does, and I'll continue making builds for the P580.

Now, I'm going to be moving on to setting up sources for gtaxllte, as I've said I'd attempt for a long while now.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 14
    New releases for 20210922

    Downloads:
    For SM-T580/gtaxlwifi: https://drive.google.com/file/d/1LPxvLU-O8jpCBB-vaoI_lp7ZJROqh28b/
    For SM-P580/gtanotexlwifi:
    https://drive.google.com/file/d/1mCE78wpxFHoI-4IIyd3ZEQzXZrkOJ5P9/

    Changelog:
    • Latest updates from Lineage, including the 20210905 Android security updates.
    • The ZRAM size has been increased to 768MiB.
    • Even further miscellaneous cleanups have been done.
    • The 32-bit wcnss_filter binary, used for Bluetooth, that was used previously has been replaced with the 64-bit wcnss_filter binary from Samsung's A520FZTU4BRB1 firmware.
    • There are some updates from the 3.18 and 4.4 Android common kernels and Linux 4.4, a few changes backported from mainline Linux, and also a few other insignificant changes to the kernel.
    • An issue where there was additional extremely quiet high-pitched noise from the right speaker has been fixed. (Thanks to @Kostareka for reporting it!)
    Enjoy.
    5
    With that first proper release for the P580, I've made a new unofficial TWRP build for it from an updated device tree and with a kernel compiled from the same sources used for these LineageOS builds, which is, of course, untested, but should now be used if it works, as I fully expect it to. An image of it can be downloaded from here, and a tar archive containing it for installation via Odin in the AP slot can be downloaded from here. (Note: these download links have been changed for a second build, with a ramdisk compressed using LZMA compression, that should actually work. Edit: it does.)

    With this build, things that didn't work with the TWRP build that previously would've needed to be used from here would work. For example, the data partition would be formatted correctly with it so that encryption works, and data partitions formatted with the F2FS filesystem would be mountable.

    For anyone who tests it, please report if it works or not. If it does, as I expect it to, I can look at taking over maintainership over official TWRP builds for the P580 and P585, and pushing my changes for official TWRP builds.

    For those who want to use encryption, and already formatted the data partition with the old TWRP build, with this new TWRP build, going to Wipe -> Advanced Wipe, selecting Data, selecting "Repair or Change File System", selecting "Resize File System", and finally swiping to confirm should work to resize the filesystem that the data partition is formatted with so that encryption works. Otherwise, backing up all data from internal storage, making a TWRP backup to a SD card or a USB drive connected via USB-OTG, formatting the data filesystem, and then restoring the backups would also be a method of getting encryption to work.
    4
    Hello, first of all, I would like to congratulate you for this magnificent structure and the extraordinary achievement you have shown. As someone who uses SM-P580, thank you very much for both the "TWRP" and "LOS 18.1" build you made. I installed it today and it works flawlessly. ( The build I uploaded is the latest version ( 2021.09.22 ) . I would like to ask you to adapt the "CrDroid" structure for the SM-P580. CrDroid provides much more customization as well as better visual integrity, useful features ( Unlimited Google Photos Backup, 3 I have no doubt that you will move towards the official version with this build, thank you again and again for everything, I will be eagerly awaiting your CrDroid build.
    I'm not going to make any CrDroid builds for the P580. I don't have any time that I can invest to do so, interest in CrDroid, motivation, or disk space, much of which I'm reserving for other stuff, for CrDroid sources along with space for temporary files for the build process. Also, your statement that you "will be eagerly awaiting [my] CrDroid build" implies that you're expecting a build, even though you didn't have any confirmation that I would make one, which makes you look like you feel entitled to one.

    When I asked @followmsi, who makes the CrDroid builds in the thread here, which was also linked in @Uluru25's post, if he would make CrDroid builds for the P580 in the future, he told me that he understandably doesn't have any time for devices he doesn't own, and therefore wouldn't. With that, your only options are to make a build of CrDroid yourself, for which you can use my entirely freely available sources, or just use my LineageOS builds.

    I'm not sure how you can expect me to go through with making this official, especially with the few issues that I've conveniently listed in my "Known issues and workarounds (if any)" section of my original post (yeah, flawless is an exaggeration). If you also searched through my thread, you would probably have found my post here, in which I list a few reasons for why it's not possible to go official, which all remain relevant until now and the forseeable future.

    By the way, you shouldn't have also sent me a message with a complete copy of this same post. It's futile.
    Hey, im trying to compile the kernel with gcc12, using the Ares Kernel source. I'm getting this error and can't find a fix. It still persists, when I'm using the stock defconfig.
    Firstly, I can't provide support for any other kernel sources. Anything that you do that is not in relation to my very own sources is entirely up to you. I can only provide support for my own sources, which I actively maintain and know relatively well.

    Secondly, it would be a lot more beneficial to just stick with my kernel sources. I remember ares kernel sources being full of gimmicky and simply bad changes, and the sources that are publicly available are no longer updated. Meanwhile, I'm actively maintaining my kernel sources, and applying many changes, most of which are from Linux v4.4 and the Android 3.18 common kernel, to them, which, of course, include security updates that you won't have with a kernel compiled from ares sources. Also, I can think of a few likely reasons for why a kernel compiled from ares sources wouldn't even work with my builds, which would require additional changes to get around, so it's also best to just avoid the troubles with that.
    2
    Thank you for releasing another update for our old tab. Just flashed the rom without any problems over the previous rom. So far nothing to complain. (y)
    Only one very minor thing i noticed a few roms ago: the samsung splashscreen identifies the tab as "A6"
    Thank you so much for keeping this old but absolutly capable hardware alive and up–to-date.
    You're welcome, and excellent.
    The "A6" boot splashscreen you describe would actually be the completely stock and static splashscreen.

    Not asking for a release date but can we still expect SM-T585 build in the future? Meanwhile this is working fine :) Thanks!
    I don't think there should ever be any complete expectations for a build for the T585. As I've always said before in my previous posts, I'm only going to attempt to setup sources for the T585 to build for it, whenever I have the time to, which unfortunately I've still ended up not having much of. I can never be certain if I'm going to succeed.

    While I do think I have a decent enough chance at success (although I'm less confident than I was before after taking a better look at the previous sources that were used for the T585), the undeniable reality is that there can only possibly be full expectations for me to setup proper sources and get working builds if I have physical access to a T585, to freely test and "experiment" on. Builds for the T585 boot on the T580, just as builds for the T580 boot on the T585, so I can take advantage of that, however, it's a far from perfect compromise, because that can only be used for testing of fairly basic things.

    With that being said, what I have now is a vendor tree that I've converted for the T585 several days ago and am not very sure about for now here: https://github.com/TALUAtGitHub/android_vendor_samsung_gtaxllte I've mostly used the blobs that were previously used for the T585 for a safe starting point, although I would prefer to have more up-to-date blobs, which is something to potentially consider later. Now, the next big thing would be to setup a device tree. There wouldn't be very much to add to, or replace in, my device tree for the T580, to convert it for the T585, after all, it's just mobile networking/telephony, GPS, and vibration, however, it's not all about simply adding and replacing stuff, but also most importantly, of course, having everything setup such that it actually works, and this is where things get somewhat difficult and I have to make hard decisions that I'm not entirely certain about. Also, there's the sepolicy, containing all of the SELinux rules, to which new rules would need to be added for the additional functionality, which would be a relatively involved process. I'm hoping for eventual success with all of this stuff.

    I just flashed your TWRP and it... does not work. In fact, I can no longer boot to either recovery or the main OS. Each time I try it gets to the samsung logo screen and has red text at the top that says "Could not do normal boot. Invalid RAMDISK LENGTH!"
    I flashed it using the "third-party" TWRP you referred to earlier, as well as tried flashing in download mode using heimdall (I'm on linux so no odin).
    Hope that helps...
    Thanks for your report. Looking into this, I've found that the ramdisks for builds from my device trees for TWRP for the P580 and P585 are around 2MB larger than those for the T580 and T585, due to the inclusion of a few extra languages for the P580 and P585 that require some fonts that are quite large, and they end up being around 16MB. It seems that the bootloaders refuse to boot from recovery images with a ramdisk that is larger than 16MB.
    I've made another TWRP build for the P580, with the ramdisk compressed using LZMA compression, rather than the standard gzip compression with which the ramdisk in the first build was compressed, bringing the size of the ramdisk from that size of around 16MB down to around 11MB, and therefore, that error from the bootloader about an invalid ramdisk length should no longer occur with it, and it should work. The image of it can be downloaded from here. Could you please test that build out?
    2
    Concur. S-pen registers movements in portrait orientation, no matter the orientation of the screen. So, in landscape mode, moving the s-pen up causes the cursor to move right, etc.
    @TALUAtXDA , I don't have either the T580 or P580, but I ran into this on the P550 where S-pen only worked in portrait mode. The fix is really easy. See post #32 at

    https://forum.xda-developers.com/t/...ab-a-9-7-sm-p550.4160909/page-2#post-83712287

    For @skiwarz and @Acatzin, you can put the sec_e-pen.idc file into the system yourself using TWRP.
  • 32
    This is LineageOS 18.1, which is based on Android 11, for the WiFi-only variants of the Samsung Galaxy Tab A 10.1" (2016), with model SM-T580 and codename gtaxlwifi, and the Galaxy Tab A 10.1" (2016) with S-Pen, with model SM-P580 and codename gtanotexlwifi. LineageOS doesn't need much of an introduction - It's a well-known custom firmware/Android distribution.

    As was always planned, my LineageOS 18.1 builds are a continuation from @followmsi's LineageOS 18.1 builds that were intended for use by users. To update from his builds, my builds can simply be installed on top of his builds without doing anything further.

    Downloads:
    Note: While these builds are intended to be used on the WiFi-only variants of these devices, they can be installed and used on LTE variants if you can go without mobile networking (of course), GPS and vibration. I'm planning to try to setup sources to make builds for the LTE variants sometime in the future whenever I have the time to.

    For SM-T580/gtaxlwifi:

    Latest build from 20210922 (with security patch level 20210905): https://drive.google.com/file/d/1LPxvLU-O8jpCBB-vaoI_lp7ZJROqh28b/
    Folder for builds (which includes text files with MD5 and SHA256 checksums for builds, and another folder within it containing some previous builds): https://drive.google.com/drive/folders/1wuirD9cyoguv7CQdEO5ymZ911k2ASKKD

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

    For SM-P580/gtanotexlwifi:
    Latest build from 20210922 (with security patch level 20210905): https://drive.google.com/file/d/1mCE78wpxFHoI-4IIyd3ZEQzXZrkOJ5P9/
    Folder for builds (includes text files with MD5 and SHA256 checksums for builds, and another folder within it for previous builds (only contains a previous build I released that has been tested to work for now)): https://drive.google.com/drive/folders/1fVGx1xGUxAtTvE0rG-OidwbXLM_93om2

    For the P580, I've made an unofficial TWRP build from an updated device tree and with a kernel compiled from the same sources used for these LineageOS builds that must be used.
    Download link for an image of it: https://drive.google.com/file/d/1eNOn9IRCj98dpx7fCSnPBQu0FIOsKZrr/
    Download link for a tar archive containing it for installation via Odin in the AP slot: https://drive.google.com/file/d/1oTurdJuNSQpl2PrEJDZpNjKdCTMapokE/
    Note that this is a second build, that has a ramdisk compressed using LZMA compression, rather than using standard gzip compression as it was in my first build since it's too large with it.

    Changelogs:
    Releases for 20210922:
    • Latest updates from Lineage, including the 20210905 Android security updates.
    • The ZRAM size has been increased to 768MiB.
    • Even further miscellaneous cleanups have been done.
    • The 32-bit wcnss_filter binary, used for Bluetooth, that was used previously has been replaced with the 64-bit wcnss_filter binary from Samsung's A520FZTU4BRB1 firmware.
    • There are some updates from the 3.18 and 4.4 Android common kernels and Linux 4.4, a few changes backported from mainline Linux, and also a few other insignificant changes to the kernel.
    • An issue where there was additional extremely quiet high-pitched noise from the right speaker has been fixed. (Thanks to @Kostareka for reporting it!)
    • First proper release for the P580.
    Previous releases:

    Release for 20210810:
    • Latest updates from Lineage, including the 20210805 Android security updates.
    • This is my first build that is signed using my own release keys. This change was removed in the second build released for 20210810 (with "-R2-Test-keys" in the filename).
    • The BSP sources have been redone to closely match what has been done with the new exynos7880-specific part of Lineage's BSP sources, and with that, there are now more exynos7870-specific changes to the open source gralloc that is in use.
    • Some further small miscellaneous cleanups have been done.
    • There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel, and a few other insignificant changes.
    Release for 20210709:
    • Latest updates from LineageOS.
    • Merges of the latest changes from AOSP for repositories forked by Lineage have been picked to skip the wait for them to be merged (repopick -t android-11.0.0_r39), and the rest of the repositories not forked by Lineage were additionally switched to the android-11.0.0_r39 tag, for the 20210705 Android security updates.
    • A patch to the PermissionController app has been applied that adds the FAKE_PACKAGE_SIGNATURE permission group to it - The signature spoofing permission can now be managed through the permission management interface at Settings -> Privacy -> Permission manager.
    • The audio outputted from the audio jack while playing media will now be noticeably louder, as the headset "DAC1 playback volume" for media has been increased to the maximum of 175 from 162.
    • There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
    • A few patches have been applied to the qcacld-2.0 WiFi driver in the kernel, which are mainly vulnerability fixes.
    Release for 20210617:
    • Latest updates from LineageOS, including the 20210605 Android security updates.
    • The WiFi and Bluetooth firmwares have been updated from Samsung's A720SKSU5CTL2 firmware.
    • The qcom_cfg.ini configuration file for WiFi has been imported from Samsung's A720SKSU5CTL2 firmware - A change within it appears to have made WiFi more reliable.
    • The sensors.universal7870.so library has been updated from Samsung's stock P580ZSS1CTI1 firmware.
    • The health HAL has been upgraded to version 2.1.
    • There are a few other small miscellaneous changes (mostly small cleanups).
    • There are many updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
    • Some unnecessary drivers have been disabled in the kernel.
    • The sdfat driver in the kernel, which is used for exFAT filesystem support, has been updated to version 2.4.5.
    • A few changes have been imported to the MMC block device driver in the kernel from Samsung's M105GDXS6CUD4 kernel that fix extremely rare kernel panics that occurred when there was an error with a MMC device (mainly with SD cards).
    • The fix for an issue where the duration of videos that are taken is lengthened by the time spent in deep sleep/suspended that was previously used has been replaced with a better fix in the Exynos fimc-is2 driver in the kernel.
    Release for 20210508:
    • Latest updates from LineageOS, including the 20210505 Android security updates.
    • New SELinux denials with Android 11 have been addressed, and with that, SELinux is now set to enforcing by default, and the sepolicy, which contains the SELinux rules, has been rewritten almost entirely, and is now of much better quality.
    • Some changes have been imported to libbt-vendor from https://github.com/LineageOS/android_hardware_qcom_bt on branch lineage-18.1-caf.
    • BPF offloading for tethering has been disabled.
    • The audio HAL has been upgraded to version 6.0.
    • The rampatch_tlv_tf_1.1.tlv firmware for Bluetooth has been updated from Samsung's stock T585XXS6CTJ7 firmware.
    • There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
    • Some tcp_info-related patches have been applied to the kernel, and with that, a workaround, a patch titled "TcpSocketTracker: Opt-out for TCP info parsing on legacy kernels", is no longer used since it's no longer necessary.
    • A workaround that was used to get USB tethering and Bluetooth tethering to work is no longer used, and has been replaced with a proper fix (enabling CONFIG_NETFILTER_XT_TARGET_CT in the kernel).
    Release for 20210407 (My initial 18.1 build. This changelog continues on from @followmsi's last 18.1 build that was intended for use by users):
    • Latest changes from LineageOS. The crashes that occurred when setting a new wallpaper that were discussed earlier in this thread appear to have been fixed.
    • Merges of the latest changes from AOSP, including the 20210405 security updates, have been picked to skip the wait for them to be merged. (repopick -t android-11.0.0_r34)
    • The same workaround that was used on 17.1 to get USB tethering and Bluetooth internet access sharing to work has been forward-ported and applied.
    • vintf manifest override enforcement is now enabled.
    • The vendor/lib[64]/egl/libGLES_mali.so blobs are now symlinked to vendor/lib[64]/vulkan.exynos5.so, rather than copied to vendor/lib[64]/hw/vulkan.exynos5.so - This is a proper fix for Vulkan support.
    • RSA key verification for ADB is enabled again, and ADB isn't enabled by default and on boot anymore.
    • There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.



    Known issues and workarounds (if any):
    Issue 1: Occasionally, when trying to select tiles in the notification panel, it will crash to the lockscreen.
    I have no idea about this issue at the moment. It seems like generic systemui crashes. Todo: test LineageOS 18.1 on another device to see if the same issues occur.

    Issue 2: Images and videos that are taken using the camera in a resolution with an aspect ratio of 16:9 are actually stretched from 4:3.
    Somewhat of a workaround to issue 2: Use a resolution that has an aspect ratio of 4:3.

    Issue 3: the on-screen navigation bar feature that can be enabled with the option at Settings -> System -> Buttons -> "Enable on-screen nav bar" doesn't work properly.

    Issue 4: If the WiFi hotspot is enabled without first enabling and disabling WiFi, it will not work.
    Workaround to issue 4: Simply enable and disable WiFi before enabling the WiFi hotspot.
    This issue no longer seems to exist. I'm not able to reproduce it on my setup anymore. However, there is a similar issue I can reproduce - If the WiFi hotspot is enabled after booting with WiFi disabled beforehand, WiFi will fail to be enabled when attempting to enable it on the first try. It gets enabled successfully and works fine after attempting again with no further issues.

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


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

    Thanks to:
    @Valera1978 - for all of the previous work for these devices, and for providing his old BSP sources without which the open BSP sources wouldn't have been possible.
    @followmsi - for fixes to various issues and other improvements, for useful information, and for working with me on much of this stuff.
    The Lineage team - for the Android distribution itself.
    ...and everyone else who has worked on anything that is in use.
    14
    New releases for 20210922

    Downloads:
    For SM-T580/gtaxlwifi: https://drive.google.com/file/d/1LPxvLU-O8jpCBB-vaoI_lp7ZJROqh28b/
    For SM-P580/gtanotexlwifi:
    https://drive.google.com/file/d/1mCE78wpxFHoI-4IIyd3ZEQzXZrkOJ5P9/

    Changelog:
    • Latest updates from Lineage, including the 20210905 Android security updates.
    • The ZRAM size has been increased to 768MiB.
    • Even further miscellaneous cleanups have been done.
    • The 32-bit wcnss_filter binary, used for Bluetooth, that was used previously has been replaced with the 64-bit wcnss_filter binary from Samsung's A520FZTU4BRB1 firmware.
    • There are some updates from the 3.18 and 4.4 Android common kernels and Linux 4.4, a few changes backported from mainline Linux, and also a few other insignificant changes to the kernel.
    • An issue where there was additional extremely quiet high-pitched noise from the right speaker has been fixed. (Thanks to @Kostareka for reporting it!)
    Enjoy.
    12
    New release for 20210617

    Download:

    Changelog:
    • Latest updates from LineageOS, including the 20210605 Android security updates.
    • The WiFi and Bluetooth firmwares have been updated from Samsung's A720SKSU5CTL2 firmware.
    • The qcom_cfg.ini configuration file for WiFi has been imported from Samsung's A720SKSU5CTL2 firmware - A change within it appears to have made WiFi more reliable.
    • The sensors.universal7870.so library has been updated from Samsung's stock P580ZSS1CTI1 firmware.
    • The health HAL has been upgraded to version 2.1.
    • There are a few other small miscellaneous changes (mostly small cleanups).
    • There are many updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
    • Some unnecessary drivers have been disabled in the kernel.
    • The sdfat driver in the kernel, which is used for exFAT filesystem support, has been updated to version 2.4.5.
    • A few changes have been imported to the MMC block device driver in the kernel from Samsung's M105GDXS6CUD4 kernel that fix extremely rare kernel panics that occurred when there was an error with a MMC device (mainly with SD cards).
    • The fix for an issue where the duration of videos that are taken is lengthened by the time spent in deep sleep/suspended that was previously used has been replaced with a better fix in the Exynos fimc-is2 driver in the kernel.
    As usual, enjoy.
    10
    New release for 20210709

    Download:
    https://drive.google.com/file/d/1ej8JYTZzcdQzwHtJHiBFwVC-rm5ytBq1/

    Changelog:
    • Latest updates from LineageOS.
    • Merges of the latest changes from AOSP for repositories forked by Lineage have been picked to skip the wait for them to be merged (repopick -t android-11.0.0_r39), and the rest of the repositories not forked by Lineage were additionally switched to the android-11.0.0_r39 tag, for the 20210705 Android security updates.
    • A patch to the PermissionController app has been applied that adds the FAKE_PACKAGE_SIGNATURE permission group to it - The signature spoofing permission can now be managed through the permission management interface at Settings -> Privacy -> Permission manager.
    • The audio outputted from the audio jack while playing media will now be noticeably louder, as the headset "DAC1 playback volume" for media has been increased to the maximum of 175 from 162.
    • There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
    • A few patches have been applied to the qcacld-2.0 WiFi driver in the kernel, which are mainly vulnerability fixes.
    Enjoy.
    6
    I've made a build for the WiFi-only variant of the Samsung Galaxy Tab A 10.1" (2016) with S-Pen, with model SM-P580 and codename gtanotexlwifi, which can be downloaded from here: https://drive.google.com/file/d/1Sw7pEuAEYB-tFtGM3t0AXSrlGrUQFnqK/

    After seeing some posts from people searching for a custom firmware/ROM for that tablet (although it seems mostly for the LTE variant), someone having had reported that my builds for gtaxlwifi don't boot on it (after forcing installation) earlier in this thread, and seeing that there shouldn't be very many changes to make for a build for it when looking into it, I decided to go ahead and make the changes for it in a copy of my existing gtaxlwifi device tree, and make this build. The changes are mostly with the kernel and, most significantly, DT image in the boot image.

    For installation, the TWRP build from here should be used: https://forum.xda-developers.com/t/...-for-p580-oreo-compatible-unofficial.4048671/ The official TWRP builds for gtanotexlwifi are reported to have severe graphical glitches, due to Samsung having made some change in their later bootloaders, and the kernel used in them being outdated. I plan to make an up-to-date TWRP build myself based on new sources later on.

    Since I don't have a P580, this build is untested, so I can't be sure if it boots and works properly or not. However, I don't see any reason for it not to. The one thing I know for sure is that S-Pen functionality would definitely be missing.
    For anyone who has tested this build, if it works, please report that it does, and I'll continue making builds for the P580.

    Now, I'm going to be moving on to setting up sources for gtaxllte, as I've said I'd attempt for a long while now.