yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] LifelessDead:
Did the upgrade:

1. Update twrp from within twrp

2. Wipe system/cache/dalvik

3. Install 18.1

4. Install Nikgapps core

5. Restart - and everything still looks about the same ;-)

Works out of the box! Thanks
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] R!ffRaff:
could that also work for the update of lineageos 16?

I tried that with lineageos 17 and it got a boot loop ?!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
It could be possible to update to 18.1 from 16.0, but that hasn't been tested.

It seems that in a few (some?) cases, it does bootloop after upgrading, and I have no idea why.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] hsje333:
Im already rooted with bootimg having lat pie release. Is it possible to flash Android Q on pinnacle of last pie release and be rooted? Again I am rooted with magisk, no longer having twrp as you can read.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Binerf:
Hi all,

First of all: many thanks for this work and to allow my daughter to keep using her tablet !!

I've just updated from release 16 to lineage-17.1-20210413-UNOFFICIAL-gtaxlwifi.zip (and lost all previous data in the meantime due to error from my side I guess).

Anyway, there is an SD card inside the tablet which I used to configure as "extended storage" to allow application to be installed on.

It worked pretty well with Lineageos 16 but now, most (hard to find one working actually) of applications installed on this storage crash when starting. I can use this SD card in several applications (like Emby) to use this extra storage to store data.

Did I miss something during upgrade ? (hopefully not as I afraid to lost again data with reinstall...)

Thanks
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Issues with adoptable storage (or "extended storage") are known. As far as I know, these would be caused by SELinux denials. However, I don't have logs with the SELinux denials that I need to address, and I can't test adoptable storage.

Could you run this command to set SELinux to permissive temporarily in a shell with root access, and see if your issues no longer exist after doing so?

setenforce 0

You can get a shell with root access by using some form of terminal emulator (such as Termux) and running "su" if you have Magisk installed, or by using root access over ADB, which can be enabled in developer options, and running "adb root" and "adb shell" on a computer with a working installation of ADB with your tablet connected.

If your issues do indeed disappear after doing so, please get a log from dmesg still in a shell with root access right after doing something that would crash without SELinux set to permissive by running the following command:

dmesg > /sdcard/dmesg.txt

After that, upload "dmesg.txt" from your internal storage in a new post here.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] slipd83:
Hey guys,

Could someone link me to a working Gapps pack?

The ARM64 10.0 Stock ones caused my tab to hang...

Thanks!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Try using the pico opengapps package for arm64 and 10.0 from https://opengapps.org, instead of an (extremely large) stock package. If the opengapps pico package doesn't work, either, try NikGapps core from https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-Q/
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] slipd83:
Thank you so much! And install directly from TWRP?

Fantastic rom BTW, it's breed a whole new lease of life into the Tab 😉
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
You're welcome. Yes, of course, only after formatting system and re-installing.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] slipd83:
Perfect, thanks!

Just been messing around with the set up and is it me or does Factory Reset not work? Data a Settings reset appear to work but not Factory.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] [[EU]Tomas]:
Pretty awesome build. I think it's the smoothest ROM there is for T580 series, performance wise?

Thank you
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] anguzito:
Hi, I just tried the command and it didn't work for me, I just can't use an SD as adoptable storage, tried different SD cards, formatting on Win or Linux, formatting on Android when setting up the feature. The apps get installed into the SD card by default from the Play Store but any of them crash on opening, once you move back to internal storage they run fine. Then if you try to move back to the SD, every app is the same, it goes up to 80-90% of move, then the bar goes back to 0 (rolling back) and gives the error "Not enough storage space", using App2SD with root is the same, just gives a generic error 8 or 4 depending on the app.

Please find my dmesg here. Has anyone ever been able to make this work on Samsung tablets? It seems like Samsung devices don't really work with this feature.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
You're welcome. No idea. I've personally never tested factory resetting, and doubt very many people ever have. Just format data in TWRP if you ever need to do a factory reset.

Hmm, I see... Alright, looks like SELinux denials aren't the cause of issues with adoptable storage. Something else must be wrong, but I'm not sure what. Adoptable storage has always been a problem, at least with Android 10/LineageOS 17.1, and maybe (probably?) still with Android 11/LineageOS 18.1.

It appears that there is actually no file with a log from dmesg attached in your post. I think a log from logcat (with any personal information removed) would be more helpful in addition to a log from dmesg.

If I recall correctly, Samsung disables adoptable storage in their stock firmwares for performance reasons. Regardless, it should work with Lineage and other custom firmwares if everything (including things outside of the device-specific stuff, which I don't have much of an idea about) is setup correctly. I'm not sure about the state of adoptable storage with Lineage for any other devices. I might end up looking into disabling adoptable storage for now to prevent anyone from trying to use it only to encounter similar issues.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Chris_0147:
App to chance the selinux state

Not works on android 11
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Did you mean to say that things break when SELinux is set to enforcing, rather than the app not being able to set it to enforcing? That's a known issue, and I've told you that before over in the 18.1 thread.

SELinux will be enforcing in my next 18.1 release when I've finished with the SELinux rules. In the meantime, please stop trying to set it to enforcing with the current release - No matter what you try, you won't be able to set it to enforcing. The necessary SELinux rules won't suddenly automagically be there. :P
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Binerf:
Hello,

Sorry for the late reply, didn't get notice about your reply. BTW, thanks for taking time to reply.

I've tested with

setenforce 0

but problem persists.

Please find the dmesg file.

Thanks
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
It's alright. I've already concluded that SELinux denials wouldn't be the cause of the issues with adoptable storage as per @anguzito's report of results. Your log from dmesg doesn't seem to have any useful information. Could you please get a log from logcat straight after a crash instead? It would be a lot more useful. Let me know if you need any information on how to do so, although there should be good enough documentation for that out there elsewhere. Do go through and remove any personal information (such as email addresses) from it before sending it here.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] slipd83:
Thanks! So just formatting data in TWRP won't remove the Gapps, just deletes the user data?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
You're welcome. Yes, it indeed won't.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] slipd83:
Nice one! I'll finish 'playing' but for now, I know what to do when I want a fresh start. Thanks again!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TabAGuy:
I hope I can add additional information on the adoptable storage issue. First off, adoptable storage is the primary use case that I have for my SM-T580. Your images up to and including 20210207 all work fine with adoptable storage. The two images after this one, for me, will allow, configure, and use adoptable storage just fine. However, on the first reboot, the two latest images always show the SD card as corrupted. I've just been staying with the 20210207 image.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
I see.... That's interesting. People complained earlier about adoptable storage not working properly with builds even older than that. In fact, I think people reported similar issues to yours sometime earlier, but I don't remember much, including exactly when. I have no idea about what could be causing such issues, except maybe changes somewhere from Lineage from the past few months. A log from logcat taken straight after a reboot where the SD card is detected as corrupted might be useful for trying to find the cause of those issues.

By the way, according to user reports, there are no issues with adoptable storage on 18.1, so you have the option of upgrading to my 18.1 build and having working adoptable storage with it if you want to. I've moved onto 18.1 as well, so working on 17.1 is more difficult for me.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] LifelessDead:
I've seen the corruption message once or twice (also on older builds). It always resolved itself automatically with a bit of patience. Occasionally the home screen icon for a certain large app with ~6 GBs of data disappears after rebooting.

I think it takes some time for the sdcard to be indexed after rebooting, triggering some timeout if it takes too long. Maybe it has to do with the speed of the card (or my Tab likes the fact that I use a Samsung card). All in all, it does work fine for me on 17.1 and 18.1.

Device storage: 20.37 GB out of 80.00 GB in use
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] anguzito:
Thank you so much for the tip, the 20210207 worked perfectly. I tried installing the latest (Android 11) but had issues getting GApps installed and is not SafetyNet checked yet, so I'll just stick with 10. Since I'm only installing this custom fw to allow extra space for my son's tablet, mission accomplished.

Thanks once again all for the help.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
New release for 20210523

Download: https://drive.google.com/file/d/1tBEZ9YINqH1JEe3iWrBNcUaK993HjGZo

Changelog:

Latest updates from LineageOS, including the 20210505 Android security updates.

Some changes have been imported to libbt-vendor from https://github.com/LineageOS/android_hardware_qcom_bt on branch lineage-18.1-caf (same as branch lineage-17.1-caf).

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.

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).

As usual, enjoy.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Eriol:
20210523 causes boot loops with my tablet. Came from January release and tried "dirty" and "clean" flash. Returning to January release now for the moment.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Try using a newer google apps package if you’re using one.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
New release for 20210530

Download: https://drive.google.com/file/d/14ZCYYcT5b6E9zWiFNgwUP3Kxlvf-dyVn

Changelog:

Latest updates from LineageOS.

File-based encryption has been disabled after I left it enabled by mistake.

Today, I've only just found out that I had left a fstab with file-based encryption (FBE) enabled for EXT4 in the last few releases. I was testing file-based encryption out a while ago. I had a few issues with it, and decided to not use it for now. Unfortunately, I switched over to 18.1, and forgot to remove the local changes to the fstab which enabled file-based encryption in my sources, and as a result, the previous release (for 20210523) and the release before that release (for 20210413) have file-based encryption enabled. My 18.1 builds are not affected by this as the sources used for it don't have this mistake.

With file-based encryption, data is always encrypted on boot, without users having to manually enable encryption.

The only significant change in this release is that file-based encryption is disabled. Installations encrypted with file-based encryption will likely no longer work with this new release, and for that reason, everyone upgrading from the releases for 20210413 and 20210523 to this release should backup any files, format data to start with a clean install, and use the clean install after restoring the files. Unfortunately, there is no way to get around needing to go with a clean install (backups of data in TWRP will not work). Even if installations with file-based encryption do still happen to boot and work (which is up to others to test), I'd still suggest going for a clean install regardless to avoid any issues in the future.

Those with full-disk encryption (FDE) are completely unaffected by any of this. To check if an installation is encrypted with file-based encryption with either the build for 20210413 or 20210523 installed, go to Settings -> Security -> Encryption and credentials and check if the "Encrypt tablet" option is labelled with "Encrypted". If you have never went there yourself and enabled encryption and it's labelled as encrypted, your installation would be encrypted using file-based encryption. Moreover, if your installation is encrypted with file-based encryption, when booting TWRP, there will be a message in the logs accessible through the third button on the navigation bar about file-based encryption (referred to as FBE) not being supported, and data won't be accessible. If you did go there and enable encryption manually with a build previous to the build for 20210413, and there is no message about FBE not being supported when booting TWRP and a prompt for the PIN/password instead, you would have full-disk encryption, and therefore be completely unaffected. If you're using the F2FS filesystem, you're also completely unaffected.

I will probably return to this complicated subject of file-based encryption in the future. For now, I've decided to just continue using full-disk encryption.

I'm sorry for making this extremely bad mistake that I should not have overlooked. :(
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Eriol:
Thank you for the new 0530 release. It works fine on my tablet. My impression is that the overall reaction time of the tablet is laggy. It seems slower than with previous builds. But this is of course difficult to measure.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] GoodSoul:
I've got the same experience. Tablet has slowed done and bug appeared like entering setup (crash). Is that only me?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] GoodSoul:
Is it only me or seems that the development of this has come to an end?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] LifelessDead:
Check out the 18.1 thread: https://xdaforums.com/t/lineageos-18-1-for-sm-t580-gtaxlwifi-and-sm-p580-gtanotexlwifi.4274293/
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] andreas__:
Hi Talu,

thank you very much for your efforts!

With this release, I cannot use DRM video playback anymore (upgrade from 05-30). It looks like SELinux errors. This happens at least with Disney+ and Amazon Video. dmesg+logcat attached.

[182408.965785] type=1400 audit(1637526456.741:233): avc: denied { write } for comm="main" name="tasks" dev="tmpfs" ino=10495 scontext=u:r:zygote:s0 tcontext=u:object_r:device:s0 tclass=file permissive=0 app=com.android.providers.calendar duplicate messages suppressed
[182408.967226] type=1400 audit(1637526459.401:234): avc: denied { write } for comm="main" name="tasks" dev="tmpfs" ino=10496 scontext=u:r:zygote:s0 tcontext=u:object_r:device:s0 tclass=file permissive=0 app=com.disney.disneyplus
[182409.223767] type=1400 audit(1637526459.401:234): avc: denied { write } for comm="main" name="tasks" dev="tmpfs" ino=10496 scontext=u:r:zygote:s0 tcontext=u:object_r:device:s0 tclass=file permissive=0 app=com.disney.disneyplus
[182409.224968] type=1400 audit(1637526459.661:235): avc: denied { read } for comm="pool-3-thread-1" name="version" dev="proc" ino=4026534911 scontext=u:r:untrusted_app:s0:c205,c256,c512,c768 tcontext=u:object_r:proc_version:s0 tclass=file permissive=0 app=com.disney.disneyplus
[182409.554188] type=1400 audit(1637526459.661:235): avc: denied { read } for comm="pool-3-thread-1" name="version" dev="proc" ino=4026534911 scontext=u:r:untrusted_app:s0:c205,c256,c512,c768
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
You're very welcome.

Looking at your log from logcat, your problems are most likely related to the webview, and unlikely to DRM itself. Those SELinux denials are actually harmless.

For DRM, there are only these concerning log messages:

11-21 21:29:12.030 2787 32046 W MediaAnalyticsItem: Failed to record: [1:drm.vendor.Google.WidevineCDM:383:-1:com.disney.disneyplus:0:-1:1:0:0:] [forcenew=0]
11-21 21:29:12.030 2787 32046 E PluginMetricsReporting: selfrecord() returned false. sessioId 383

However, they wouldn't indicate an actual fatal problem.

For the webview, there's log messages of more concern in particular, including log messages about crashes. The most descriptive of the errors which would indicate an issue is this one:

11-21 21:30:09.241 32150 32150 E WebViewFactory: Caused by: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/system/product/app/webview/webview.apk"],nativeLibraryDirectories=[/system/product/app/webview/lib/arm64, /system/product/app/webview/webview.apk!/lib/arm64-v8a, /system/lib64, /system/product/lib64, /system/vendor/lib64, /system/lib64, /system/product/lib64, /system/vendor/lib64]]] couldn't find "libwebviewchromium.so"

...but weirdly, libwebviewchromium.so does exist in the webview APK file as I found after extracting it from my latest build as it should, so there shouldn't be any issues with it not being found.

I don't think any of the new changes could've broken DRM or the Webview. Although I don't remember much from the testing I did, I think I tested the webview through the default browser app and found it to work fine, and possibly checked DRM information as a quick check to make sure DRM would work, although unlikely, so I'm especially puzzled.

With all that, unfortunately, I don't have any ideas for any possible cause. :(
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] andreas__:
Hi,

Thank you for your analysis. it helped me a lot!

I tried another app that uses WebView too, and it also crashed, so not a DRM problem.

Then I pulled /system/product/app/webview/webview.apk and found the libwebviewchromium.so inside.

I then just installed that apk on top of the system, and now it's working again. :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Hi,

We suspect that the issue with clicking and popping sounds in sleep is caused by google apps. [MENTION=8017005]srgrusso[/MENTION] recommends using the pico opengapps package, not exactly sure if that will help you as I don't use google apps. I don't have such issue.

Yes, indeed installing the TWRP app causes bootloops. Even if there weren't bootloops after installing the TWRP app, it still shouldn't be used as it's known for collecting data in the background and TWRP updates don't happen often meaning there's limited use for such an app.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] BarnOwl:
That's an opinion........I doubt if TWRP collects more data then Google? And I think it is very useful for making backups, deleting, wiping etc. It has been on my devices ever since the start of it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
I'm talking about the TWRP app, not the recovery itself. Of course it's useful for those purposes but the app is, of course, not. The apps supposed purpose is simply to update TWRP. The issues I describe are known issues. For example, there's this: https://wiki.lineageos.org/devices/s3ve3gjv/install

Also, you shouldn't be comparing the huge amount of data collection Google does with anything else that collects data but in smaller amounts and think it's perfectly fine - collection of private data in any amount is bad. Most importantly, why should the TWRP app, with a supposed use of simply updating TWRP, need to collect private data?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] t123321:
Very good rom. No problem so far, thanks
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] funinagg:
thinking of trying out lineage-17.1-20200309-UNOFFICIAL-gtaxlwifi.zip. whats the md5 for it. want to make sure it matches. had some issue before. thanks for all the great work (:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Hi,

The MD5 checksum for that file is f912211bd7f831c2b26ac30a06d314d1. You're welcome.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] jonnybigodesPT:
Hello,

A newbie question... how much time at the first boot?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] t123321:
no more than 3-4 minutes
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] forceu:
Thank you so much for your hard work! I had it installed for two days now and it appears very stable :)

One thing though: By default ADB is active on the device, without any RSA verification. By enabling developer options it is possible to disable adb, however you can still connect with any device - is that an issue related to LineageOS?

/edit: One problem I also encoutered that the touchscreen did not respond anymore once I enabled the onscreen nav bar in the settings, after a reboot it worked again, however now the option is missing to disable the nav bar again
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] seandpa:
I'm trying to get microG set up but I can not get the UnifiedNlp registered in the system. Anyone help me?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Hi,

Have you rebooted since first installing microG, and do you have microG installed as a system app?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] jonnybigodesPT:
I was in a loop :laugh:

Thanks mate
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] seandpa:
I tried with nanodroid with microg and installed from twrp, all worked fine until I attempted to use Netflix and a local sports streaming app and they didnt work.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] jonnybigodesPT:
I have tried with MicroG and the system has failed , more propely, the launcher.

After 3 reboots install other launcher..all good for now.

I had other problem , google store won't download apps..all good for now as well.