yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Archaide:
Hi taluatxda.

This time it was not so smooth. :)

After flashing switch-to-release-keys.zip the tablet rebootet automatically. I guess i had activated that in twrp. My bad.

After the device booted i landed on a empty homescreen and the message that the settings app was aborted several times. Or what ever the english translation of the message is. :)

After roundabout 30 seconds the homescreen appeared. Wlan was off and planemode was on. I did not checked any further.

Booted in twrp, flashed the new rom and rebooted. wlan off, planemode on and Aosp keyboard activ and not the custom keyboard i used for years. This never happened before. Newpipe is not working anymore and so is newpipe legacy. That's all i experienced until now.

Nevertheless thank you for keeping this device up to date.

I guess it was all my fault by letting twrp boot automatically after flashing. Maybe my experience will help someone else.

Edit: After rebooting again NewPipe is working.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Yeah, that would've happened because you had TWRP automatically reboot.

I'm actually thinking that it would now be best to take down this latest build, and make a new build switching back to test keys and a package to switch back to test keys for those who have upgraded to the latest one. I'd rather not have any risk of any worse issues occurring, and I don't think having release keys has much benefits besides having Trust not nag about the build being signed with the public test keys, anyway. I'm hoping that wouldn't create more issues. :( I don't think I've had a more stressful day for a very, very long while than today.....

Finally, you're very welcome.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
I've now made a second build for today. This one is simply signed with test-keys again. It can be downloaded from here: https://drive.google.com/file/d/12LXvcV9koMMV7tGXlcbfd0cUfAJ1-Agr/

For those who had installed the first build I released earlier today and have now taken down (with the filename "lineage-18.1-20210810-UNOFFICIAL-gtaxlwifi.zip" without "-R2-Test-keys"), to install and boot this build on an existing installation as well as future builds that are going to be continued to be signed using test-keys, you must install the package which can be downloaded here in TWRP recovery: https://drive.google.com/file/d/1gYVI71QEtfMafGssPfWW-6UAH2dLd3wO/ Otherwise, you will encounter issues. Make sure data is mounted in TWRP, and that the "Reboot after installation is complete" option is disabled in both TWRP settings and when installing that package before doing so, or you will also encounter issues when it boots up.

I would also suggest before doing anything to make a TWRP backup of data if possible, just in case.

For those who didn't install the first build I released today, and are still on an older build, you can simply upgrade straight to this build without doing anything further, and ignore all of this.

I've decided to go back to signing with test-keys as is standard to avoid any possible unforeseen issues with existing installations, and because signing builds with release-keys causes some undesirable complications that I overlooked and actually does not seem to bring many benefits, especially with an unlocked bootloader, except for getting rid of Trust's urgent-looking notifications about my builds being signed with public [test] keys, which can be disabled.

I apologise for this awful mess that I created with the release-key stuff. I don't think I'll be touching anything related to signing anytime soon...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rambomhtri:
Thanks a lot. Just curious: LTE verision is on the way, right?

Whenever it's ready, could you post a message here?

Thanks for everything man!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
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.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rambomhtri:
Unfortunately the LTE tab is my aunt's, and I can't help you test a build :(

I'm happy to hear you are working on it in a few days, whatever it takes and whenever you can, it's always fine, you've already revived the WiFi version.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Kostareka:
Good news, I'm ready to test build on my t585

Contact me on Telegram any time you like

@Mohamed2003T
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Archaide:
Flashing back to the test keys build worked like a charm. :-) Looks like everything is up and running. As always: good Job. Thnx alot.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Lumito:
I don't think so. I've ran the switch_to_signed.sh script, then rebooted into TWRP (not the main OS), installed the ROM, cleared cache and rebooted out of TWRP. Everything works fine for me with the release keys.

Maybe the installable package is broken idk.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
I see, that's understandable.

Alright. :)

Okay, excellent. I'll keep you in mind for whenever I get a build ready for testing.

"not the main OS" - That would be why you didn't get any issues. If you rebooted (either accidentally, or by having TWRP's "Reboot after installation is complete" option enabled) to the main OS, not recovery, after installing the package or running the script without installing the build signed with my own release-keys I had released, then you'd encounter issues.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Echo_2000:
I also volunteer as a tester for the LTE variant
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] LifelessDead:
Even with switching release keys, dirty flashing both August versions went fine.

Flash, wipe dalvik/cache -> boot

Thanks 👍
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] BlackDoma:
I'd like to be a tester for the SM-T585 builds.

Feel free to message me on telegram: @BlackDoma
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dovedescent7:
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...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
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://xdaforums.com/t/rom-sm-t580-sm-t585-unofficial-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://xdaforums.com/t/rom-sm-t580-sm-t585-unofficial-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:

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.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dovedescent7:
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?

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?

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.

Lastly, does this rom allow for overclocking the CPU?

Thanks op/dev! And yall
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Zeppelli:
Can you link the app in the post? I'm not able to find it in the google play store @_@
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Zeppelli:
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
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Uluru25:
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!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bswinburne:
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.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] gamerth:
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.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
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.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Uluru25:
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?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vstrecker:
is there any shedule for the 585?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rambomhtri:
It will come soon, just wait.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] LaPesteO_o:
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
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
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.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Uluru25:
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).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
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.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Uluru25:
Thx for yourdetailed and precious support!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
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://xdaforums.com/t/recovery-twrp-3-3-1-0-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.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Uluru25:
Regarding issue 2: does this only affects pictures / vids taken with the tablet's camera or even videos streamed via internet (e.g. movies etc.)?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
It's the former (only affects pictures and videos taken with the camera). Nothing else is affected by aspect ratio-related issues.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] novice1988:
I have installed this and my tab volume is really low, please help. I checked mixed_path.xml but there is no "speaker" and value. So please help. My tab is T580.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
See my previous post on that here: https://xdaforums.com/t/lineageos-1...d-for-sm-p580-available.4274293/post-85306295
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] novice1988:
Thank you but how to edit using quick edit. As I have edited it than again the value becomes 31. And the another editor cannot edit it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Rawwrius01:
Never thought this would happen lol. Thanks very much I will definitely try it today. I gave you developing for this device, because for a total beginner, handling all the bugs wasn't so easy.

I formatted data, flashed ROM, open Gapps, magisk and dfe but I stuck on bootloop. Any p580 user who got it working?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
I was hoping that wouldn't be the case. :( I'd like some more information to try to find possible causes for the bootlooping.

First of all, could you describe how it bootloops? By that, I'd specifically like to know if the LineageOS boot animation appears a few seconds after trying to boot your tablet up with that build (if this is the case, there's progress), or if it stays on a black screen for a short while before the LineageOS boot animation potentially appears (or something similar to that), or something else.

After having it in that bootlooping state for around 1-2 minutes (if it doesn't crash and reboot on its own), hard resetting your tablet (hold down the power key and volume down key for around 7 seconds), and booting into TWRP by holding the key combination for recovery mode as soon as your tablet reboots, could you please get a log from /proc/last_kmsg? To do so, you can just copy that file either to your internal storage (/sdcard) or SD card if you have one (/external_sd) using TWRP's built-in file manager, and transfer it from your tablet using USB and MTP, as usual.

If it doesn't stay on a black screen for a short while before the LineageOS boot animation potentially appears (or again, something similar to that), could you try formatting the system partition, installing the build without opengapps or magisk, and see if it bootloops then?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Rawwrius01:
Thanks for the answer. I will take a log and upload it later. The tablet stuck at the lineage Bootanimation the Samsung logo appears, them the lineage animation. Over and over again, I tested it for about an hour. Without Gapps I got the same result. I will try formating system and flashing only the ROM. Btw it was. The latest canary version of magisk.

edit: Wiping system and flash only the rom gave the same result. heres the log.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Uluru25:
Which dfe did you flash?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Rawwrius01:
https://xdaforums.com/t/universal-dm-verity-forceencrypt-disk-quota-disabler-11-2-2020.3817389/

This one
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Thanks for the information. Your log gives me the exact reason for why it would be bootlooping. It's filled with this one SELinux denial:

<36>[ 6.524706] type=1400 audit(1630007648.149:62): avc: denied { read } for comm="android.hardwar" name="type" dev="sysfs" ino=19607 scontext=u:r:hal_health_default:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=0

I've attached an AnyKernel3 package to be installed in TWRP. It will replace the kernel with one I've just built that has SELinux set to permissive on the cmdline, so that SELinux denials are only logged and not enforced. Please install it, and see if it will boot.

If it does boot, which I think it should, straight after quickly completing the initial setup, reboot into TWRP (to do so easily, enable advanced restart in Settings -> System -> Gestures -> Power menu -> Advanced restart, and you'll be able to reboot to recovery from the "Restart" menu in the power options screen you get when holding the power key) and grab another last_kmsg log, and send it here, so that I can get the SELinux denials that I have to address/fix, so that SELinux can be set to enforcing for better security.

You can alternatively get a log from the dmesg command using ADB shell and rooted debugging, but a last_kmsg log is easier to get, unless you already have a working installation of ADB on a computer, and is sufficient.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
That package isn't necessary at all, by the way. DM verity isn't a thing here, and forced encryption/forceencrypt isn't enabled. Even if forced encryption would be enabled, I don't think it would be a problem since TWRP supports decryption.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Uluru25:
Some years ago I used this: https://xdaforums.com/t/newbie-friendly-twrp-and-root-for-tab-a-tablets-2016-10-1.3552509/

See 1st post, step 1f
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Rawwrius01:
A few years ago a made a Kernel for this tablet, I got problems with no working wifi and I wasn't able to fix it so I stopped. The thread is maybe still live. I think there were also problem's with selinux. I will try it and report.

Edit: its booting