yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Tenaya43:
Thanks for the information.

After posting my question, I've learned a bit more about my new (to me) SM-T350. The code name for my tablet seems to be "gt58wifi" (gt58wifixx?) and TeamWIN does not list an OFFICIAL version of TWRP for it.

FYI, "a8hplte" is the code name for the SM-A800i, which is a phone, not a tablet.

I did, however, find an UN-OFFICIAL image of TWRP, version 3.2.1, but I don't know if that can be substituted for the 3.5.0 listed in the Q&A at the beginning of this thread.

I am massively reluctant to attempt to install any TWRP image that doesn't at least say it's for gt58wifi models. I'm hoping someone (retiredtab?) here can provide a link to the correct TWRP image, in ODIN compatible format.

Tenaya

For clarity: I am most certainly a noob, but I like to think I'm not a complete noob. I have successfully used ODIN and TWRP to install LineageOS 18.1 on my Galaxy S5 phone (SM-G900T aka KLTE) and am VERY happy with the results. I guess that makes me a user. -T
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lpedia:
Hi, @Tenaya43.

Yes, the T350 is gt58wifi. One way to be sure of the codename of a device is to install the DevCheck app (from Google Play) and look at its System tab. It should show the model name as "Model" (GT-T350) and codename as "Device" (gt58wifi). [DevCheck's a very handy tool - I recommend installing it anyway, especially if you continue using custom ROMs.]

Here's a screenshot from one of my T350s:

In the FAQ on the first page of this thread, retiredtab has given a link to another XDA thread where you can find his recommended TWRP for the device, which is TWRP_3.5.2_9_SM-T350_20210726_Unofficial.img. I can confirm that this version of TWRP works: I have it on two SM-T350s, both of which have retiredtab's LineageOS 18.1 ROMs installed and working well.

TWRP versions will not be 'official' and available from twrp.me unless someone has committed to maintaining them. 'Unofficial' TWRPs recommended by ROM developers are not untrustworthy. If you're prepared to trust the dev far enough to install his ROM, you can probably trust his TWRP recommendation as well. :)

Note: Odin requires images to be in tar format, but the recovery tar file is just a recovery.img file compressed with 'tar'. You can install any TWRP.img with Odin by renaming it to 'recovery.img' and using any Windows or Linux or Mac app that can create tar archives to create the .tar file.

I hope that helps.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lpedia:
Hi, @jj26meu.

It sounds like you have a BOE panel. There's a known issue in which the BOE panel backlight doesn't come on and the screen stays blank in TWRP. There's a fix for this: see Q25 of retiredtab's FAQ on the first page of this thread.

Once you've applied the workaround, you should use TWRP_3.5.2_9_SM-T350_20210726_Unofficial.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Tenaya43:
That's good to know, I'm always up for a good utility and will install DevCheck once I get LOS 18 installed.

Thanks, I was over cautious and was looking for 3.5.0_9. (That's me being a non-complete noob - I still stumble over little things.)

I downloaded that TWRP file and will install it later this evening.

Tenaya
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New build called lineage-18.1-20211107-UNOFFICIAL-gt58wifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

Nov 7 release notes

1. Nov 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/318560

2. I enabled zram swap with size 512MB. I noticed that the last couple of months that Clash Royale would crash/close and logs showed

10-28 14:26:01.412 0 0 I [2: kswapd0: 91] lowmemorykiller: Killing 'ell.clashroyale' (6730), adj 0,

Hopefully, by enabling zram, that will stop Clash Royale from crashing/closing.

Zswap is enabled on stock Nougat SM-T350 (part of the Samsung Tab A/E family that uses same msm8916 kernel code)

https://github.com/retiredtab/andro...mmit/2a6bf385e6dfe6073fe328b7b1c563ccd60a5ede

https://github.com/retiredtab/andro...mmit/438d5d3ad20cbc98f0f8c18eb610b6268de19395

This code uses the in kernel low memory killer (lmk). I tried using the Android OS lmk, but it doesn't work very well and shows this in the log.

E lowmemorykiller: /proc/zoneinfo parse error
E lowmemorykiller: Failed to get free memory!

3. Whatever LineageOS changed since last Oct release (about 7,200 files had to be recompiled). One of these changes has removed the built in terminal program from LineageOS as AOSP deprecated this app as per

https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/304043
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Wikdclown:
Been using this as daily driver for awhile now and sometimes when you turn the screen on it just has a blue bar at top and the rest of screen black, it will not do anything so I have to reboot using download and then it goes back to being fine again. Just seems to randomly happen sometimes. Other than that the ROM runs great performance wise.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I have been using 18.1 since late March 2021 and I have never seen this behaviour ever.

If/when it happens again, hookup the device to a computer and do the following:

adb logcat > hung.txt

Zip the hung.txt and either attach it here in the forum or send the zipped file to me via PM. In addition, can you send me the tombstone files (zipped) via PM?

adb root
adb pull /data/tombstones
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
@lpedia , have you seen this before?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lpedia:
No, I haven't seen this, and the two family members who use our two T350s haven't mentioned seeing it.

@Wikdclown - which build/s have you seen this with?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Wikdclown:
I am using lineage-18.1-20211107-UNOFFICIAL-gt58wifi. I have had it to happen turning it on from home key and power key. It shows a blue box at the top of screen with time and date then the rest of the screen is black the tablet will do nothing other than turn screen on and off, cannot reboot normally or anything.

There is one thing though that I found out, if I just leave it on that screen and let it go back to sleep it will eventually after a couple tries go back to working normally.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
@Wikdclown, Okay, now with the above description, I have seen that before on a Samsung phone running 16.0 a couple of years ago. Upgrading to a later version of 16.0 resolved that problem. There were no changes to the device tree suggesting that the problem was with LineageOS itself.

I think the blue box is related to the smart cover which I have enabled on the SM-T350 as I have one. It's enabled here

https://github.com/retiredtab/device_samsung_gt58wifi/blob/lineage-18.1/device.mk#L122

So I use the flip cover to put my SM-T350 to sleep and wake.

If your workaround doesn't work, then get the logs so I can see if there's anything obviously wrong.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
@Wikdclown, here's the thread about the phone stuck on lockscreen with blue tile.

https://xdaforums.com/t/phone-gets-stuck-on-lockscreen-with-clock-on-blue-tile.3561878/

On another SM-T350 that I have with no smart cover, smart cover functionality is enabled by default. Try disabling it by going into settings, connected devices, connection preferences, smartcover and disable it. This setting should be saved now for future 18.1 OS upgrades. That is, the Dec 5th security patches should not overwrite this setting.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Wikdclown:
Apparently this was the issue. Thanks for the solution.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New build called lineage-18.1-20211210-UNOFFICIAL-gt58wifi.zip.

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

18.1 continues to be my daily driver since March 2021.

Dec 10 release notes

1. Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2021-12

2. Whatever LiineageOS changed since last November release (about 11,000 files had to be recompiled).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] John007778:
Just installed it on mine that I had laying around, took me a few days because I have only custom rom phones and not tablets but successfully installed 18.1 Go
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
@John007778, you have a BOE panel as per FAQ 25. With BOE, you must be running the correct bootloader found in stock Android 6. There's tons of detail of BOE.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] gyurza2021:
when i can find LineageOS ROM for SM-T355?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lpedia:
Not via this thread. See post #2 (FAQ) - q22 and q24. You could search XDA Forums to see if someone else is working on it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] NicBOMB:
I installed the ROM and followed your recommendations. I was able to install magisk and the microg services too. This was my first time installing a custom ROM (and yes I read all the disclaimers and FAQ like a good noob). Are android work profiles disabled for this ROM? Is this a difference between full and GO builds? Searching settings for 'work' finds multiple of the options I was expecting, but none of them are accessible.

Spoiler content hidden.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Thank you. Reading and respecting the FAQ greatly increases the chance of a response from me. Lately, in my T550 thread, the last few posters ask things which clearly tells me they have not read the FAQ.

I didn't know what work profiles are so I looked it up. Are you talking about central IT creating a work profile like

https://developer.android.com/work/managed-profiles

If yes, I have no idea if work profiles are disabled or not since I have no way of testing it. I tried this program called test DPC, but it says I'm not an admin and everything is greyed out.

https://play.google.com/store/apps/details?id=com.afwsamples.testdpc

If no, please explain or provide a link to what you mean by work profile.

Yes. It's documented here and I don't see any reference to profiles.

https://www.xda-developers.com/android-oreo-android-go-low-ram-patcher/

"Note that a number of on-device features will be affected. These include many UI changes including a flat recents menu and other changes like high-end graphics disabled, multi-window disabled, notification icon changes, log sizes, no app notification access, zen access, VR listener access, or picture-in-picture access."
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] NicBOMB:
I get the same greyed out options. I was trying to install a copy of an app and isolate/sandbox some apps with it in the profile. I tried https://f-droid.org/packages/net.typeblog.shelter/ but it failed to create a work profile. Since it explicitly claims compatibility with lineage os, it probably requires something this build isn't allowing by default or omitted. I haven't encountered any showstoppers though. Really good ROM.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I tried the above since it's FOSS and I don't require any ids, but it failed to work on my GO build.

You can try crDroid or evevolv. They both have SM-T350 builds that are NOT GO. If it works on either or both of them, let me know and I can do a bit more investigation.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
@NicBOMB Okay, I think I figured it out. One of the properties that the GO build sets is

ro.config.low_ram = true

While set to true, when I run shelter, it says "setup failed". If I set it to false, shelter says "Let's setup your work profile".

If you want to change this property, you can do this via TWRP by

1. Boot into TWRP, click mount, choose system so it has a checkmark beside it.

2. Goto PC, open a terminal.

3. Get build.prop file onto local PC.

adb pull /system/build.prop

4. Use a text editor and search for

ro.config.low_ram=true

change that to

ro.config.low_ram=false

5. Save file.

6. Push file back to tablet.

adb push build.prop /system/build.prop

7. Make sure file was updated.

adb shell cat /system/build.prop | grep low_ram

8. Reboot back to system and test shelter app again.

NOTE: This change will be required everytime you flash an updated rom from me since the default setting in the GO build is ro.config.low_ram=true.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] NicBOMB:
Thanks for the instructions! I'll try it out shortly. I don't mind additional steps for updating the ROM. I already used https://xdaforums.com/t/signature-spoofing-on-unsuported-android-11-r-roms.4214143/ to signature spoof for microg since magisk+riru+LSPosed+fakegapps module wasn't working. I'll update, then use a script to apply magisk, spoofing, and this customization. Unless you add signature spoofing patches for microg, or build "lineage for microg", or the app based LSPosed spoofing starts working, adding a few more lines to the update steps/script I already use is trivial. Keep doing what you're doing. People who want big brother alphabet can choose opengapps thanks to this ROM too. Either way, your ROM will likely be on both my SM-T350's at this rate.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] NicBOMB:
That was perfect! Thanks for the help and a great ROM.

Spoiler content hidden.

Spoiler content hidden.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I updated the FAQ Q26/A26 to reflect what features are removed with the GO build and how to edit the build.prop file for users who want/need these features.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] G_Bot:
Nice i tried this rom. its working great. 👍
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New build called lineage-18.1-20220120-UNOFFICIAL-gt58wifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

18.1 continues to be my daily driver since March 2021.

Jan 20, 2022 release notes

1. Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-01

2. Whatever LiineageOS changed since last December release (about 10,000 files had to be recompiled).

Note: The Jan 5 security patches were originally uploaded on Jan 6, but the "bump security string" was only submitted today Jan 19 and not yet officially merged. Nonetheless, I went ahead and made the build Jan 5 security patches build. I'm not sure why there was such a delay.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] glockmane88:
@retiredtab

Are you going to do a Lineage 19 build? Thank you :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ahoslc:
Ignore fixed
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New build called lineage-18.1-20220212-UNOFFICIAL-gt58wifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

18.1 continues to be my daily driver since March 2021.

Feb 12, 2022 release notes

1. Feb 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-02

2. Whatever LiineageOS changed since last January release (about 34,500 files had to be recompiled).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Viking8:
WOW! This rom is by far THE best I've used on my Tab A. It is actually usable now....for the first time! My thanks for your hard work on this, I greatly appreciate it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New build called lineage-18.1-20220312-UNOFFICIAL-gt58wifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

18.1 continues to be my daily driver since March 2021.

Mar 12, 2022 release notes

1. Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-03

2. Whatever LiineageOS changed since last January release (about 5.700 files had to be recompiled).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen:
Hey retiredtab, what does your local manifest xml look like? I tried building but it keeps failing, so before I spend forever debugging I just wanted to make sure I had everything 😅
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
It's in post #2. There is the manifest.xml and the diff file that you will need to apply to the source code.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen:
Oh, thank you! I didn't see the attached files.

They appear on my phone but not my computer.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] John007778:
So far, this latest update has been quite good for being this tablet with entey level specs
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New build called lineage-18.1-20220410-UNOFFICIAL-gt58wifi.zip. The sha256sum is

$ sha256sum lineage-18.1-20220410-UNOFFICIAL-gt58wifi.zip
e226511927b5b1f2796349e5c8d718dcfde492d8050e2c0a408925f73f0ca437 lineage-18.1-20220410-UNOFFICIAL-gt58wifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

18.1 continues to be my daily driver since March 2021.

April 10, 2022 release notes

1. Arpil 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04

2. Whatever LiineageOS changed since last January release (about 11,000 files had to be recompiled).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Wikdclown:
Does Spotify work correctly for anyone else? It loads fine but will not load tracks into any playlist. It's not a new thing that I know of because I didn't have Spotify on this device before.

I thought it might be something I had done so I flashed a clean ROM and still same problem.

I tried with gplay services installed still same issue.

My Spotify works fine on same account on other devices and PC.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen:
Enable adb, and grab a logcat of the issue. Run "adb logcat" in a command prompt (or in termux or a terminal emulator with su) then try loading a track. Copy whatever it spits out, or just send the whole log (you can put it in a file with "adb logcat > log.txt" )
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
In addition to FAQ 9 that lividhen already mentioned, did this work in my 17.1 build? The 2 biggest differences between 17.1 and 18.1 is that 17.1 is NOT a GO build and 18.1 has selinux enforcing.

With a GO build, some features are removed as per post #46 and #49. Perhaps Spotify needs something that is disabled by GO?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Wikdclown:
Here is a log.

--------- beginning of main04-14 19:39:22.113 22610 22622 E cessService0:1: fa - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
You have to zip it. I can't see or download any .txt attachments for some reason.

edit: Okay, I see your pastebin now.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I will look at your log in more detail sometime tomorrow. I have to things that I need to get done tonight.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
My best guess after looking at the logs is that it might be related to go the 18.1 GO build. You can try and set ro.config.low_ram = true to ro.config.low_ram=false as per post #49 and retest your Spotify.

I don't think it's selinux enforcing related as I don't see the messages in the log.

Also, did you try Spotify with my 17.1 SM-T350 build?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Wikdclown:
Thank for looking. I tried the low ram option didn't work. I'll go try the 17.1.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Wikdclown:
Oki tried your 17.1 build and Spotify works fine.

Edit:

Nevermind can't use 17.1 because no audio goes to Bluetooth headphones.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Hmm, 17.1 audio over bluetooth definitely works. I spend a lot of time working/fixing that and verified it worked in my last 17.1 Dec 5th 2021 security patch.

For 18.1, even though the log that you provided don't show any selinux denials, I wonder if the denial is way earlier in the log.

Try this.

1. Backup all your data.

2. Download kernel-permissive-patcher.zip from

https://xdaforums.com/t/mod-kernel-permissive-patcher-for-android.3506338/

3. Boot into TWRP. 3. Install by flashing kernel-permissive-patcher.zip using TWRP. This will put the rom into selinux permissive mode (not enforcing).

4. Boot into OS.

5. Try spotify again.

6. If it works, boot into TWRP again. Reflash the April 5th security patch rom. This will put it back to selinux enforcing mode.

7. Boot into OS and try spotify again. Report your results.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
PS. I know in 18.1 audio over bluetooth works since day 1 and every build I have ever uploaded.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Wikdclown:
Installed with TWRP still same thing.

Surely someone else that uses this ROM has Spotify and if it works or not ? lol

If its just a me thing ill figure it out eventually but itd be nice to know if someone else has this issue.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
"Same thing" meaning the playlist doesn't work or the audio over bluetooth doesn't work? Or both?

Send @G_Bot a PM and see if he willing to try 18.1 with his spotify and audio over bluetooth setup.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Wikdclown:
I may have muddied the waters some so let me clarify. In the 18.1 build audio over Bluetooth works perfect. It was the 17 build that I had Bluetooth issues. I flashed the kennel permissive on 18 but Spotify will still not load the content of any playlists. On the 17 build Spotify worked fine.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] uOySsElNu:
Will you build a 64-bit Android version lineageos for t350 in the future？(///▽///)