yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] robertozombie:
yeah, I have the nexus rom, I'll install this lineage based rom and voilà, thanks!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rw_on_xda:
BIG Thanks for a new Release !!!

Updated/Upgraded via TWRP.

under CPU-Z I see

- Security Patch Level is 2020-09-01

- Bootloader remains on BTFN

under Settings => "About phone" => "Android version" I see:

- LineageOS version seems to be cutted after "...-UNOFFICIAL-"

- "Vendor security patch level is "unknown"

Is this known ?

---------- Post added at 20:30 ---------- Previous post was at 20:16 ----------

regarding your S10e (while searching for a new phone):

- is it an exynos or snapdragon ?

- would you recommend it ?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] robertozombie:
exynos, yeah I'm happy with it, nice size. here in Germany it was difficult to get the snapdragon (which is better).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Well, the underlying LOS system image has ro.build.version.security_patch=2020-11-05. Samsung leaves ro.vendor.build.security_patch blank, which explains the "unknown". The boot image for BTH4 reports OS version and patch level as 335544649, which decodes to 10.0 and 2020-09-01, respectively. And since I don't replace the bootloader, it's whatever was on your device before the flash...in this case, BTFN.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rw_on_xda:
so all on my device is as it should be.

Thanks

---------- Post added at 23:36 ---------- Previous post was at 23:31 ----------

yep, only S20 FE 5G is snapdragon too in Germany
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Andyk969:
thank you very much. I tried and it was the solution for me.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 4929york:
It causes me to lose USB file transfer ability but exFat is more important.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] El Mik@:
Hi!

Quick question: is there any problems with this Rom and how it's working in general? Planning to buy The device from black friday sales.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TheDevil259:
The only negatives I know of are:

- no storage encryption

- no exFAT support (workaround through Infinity Kernel)

- Bitwarden (a password manager) doesn't work

Otherwise everything seemed fine
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] El Mik@:
Thanks for quick reply!

Is there a real security threat in "no storage encryption"? Or does it mean simply that anyone can access the files on the sd-card and internal memory if they plug it to computer (photos, downloads etc.)?

How about the ROM itself? Does it feel faster / more responsive than stock rom?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TheDevil259:
It is as you say. Someone could access the data on your device without the need of authentication.

Some applications could also refuse to work if encryption is disabled but I'm not sure about this one (maybe that's why Bitwarden doesn't work?) .

The ROM itself definitely makes it feel more fluid than Samsung's bloated One UI (although One UI is a huge improvement over Touchwiz imo).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rw_on_xda:
*I* see no problems with the ROM.

Maintainer is very responsive.

He and the ROM is fast.

GPS is fast too.

Battery drain is ~3 % per day only (idle, wifi/BT off, ...)

you should go for an 3 GB RAM, 64 GB storage device, standard is 2/32 GB only.

got mine for 194 € ~2 month ago (no delivery fee and a not so bad case was included, it was a very special time limited offer )

[ 1 € is ~1,18 $ to compare]

price search engine/ rewiews (mostly in German):

https://www.heise.de/preisvergleich....html?plz=&t=v&va=b&vl=de&hloc=at&hloc=de&v=e
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] robertozombie:
hello all,

quick question, sorry if this has been answered before, couldn't find the answer.

what is the difference between this custom Lineage ROM and [MENTION=903232]Magendanz[/MENTION]'s other Nexus rom that is based on Lineage?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
The other one is based on AOSP and not LOS.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] robertozombie:
then what does this mean?

“* The system is based on [MENTION=4467696]AndyYan[/MENTION]'s LineageOS 17.1 GSI (LQ) or [MENTION=1915408]phhusson[/MENTION]'s AOSP 10.0 (AQ) with the latest Stock variant from OpenGApps.“
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
This custom ROM is pure LineageOS, while the Nexus Stock ROM (LQ) is based on LineageOS and then adds the Stock variant of OpenGApps, custom Google logo animation and wallpaper, and custom Pixel Launcher icon layouts. The goal with the Nexus Stock release is to be as close to a Nexus or Pixel user experience as possible, much like the PixelExperience custom ROMs.

There is also an AQ build of the Nexus Stock custom ROM, which is based on AOSP 10.0 instead of LOS 17.1. The differences in user experience are pretty subtle, though, and I originally built AQ only to work around some LOS bugs.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Zippy Dufus:
Flashed fine

Quick note, I just installed this and had one minor quirk.

When I tried to flash open_gapps-arm-10.0-pico-20201121.zip immediately after flashing the ROM, I got an error about not enough space in the system.

So I booted into the ROM and then rebooted back to recovery and it flashed OK.

Thanks for the updated ROM!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Yes, that's a feature of LineageOS. On first boot it will run a resize2fs to expand the system volume to fit the partition, freeing up space for you to install OpenGApps. You can do this manually in TWRP, but you'll need to run e2fsck -fy first to check the partition.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] :
Yesterday I flashed this rum relatively easy. Needed to diddle a bit with Magisk to get netflix working. Got it running.

I found one weird bug so far, in the brightness slider, if I turn it all the way down the screen is off, it's just dark. The first time I had to blindly swipe untill I got the brightness back up agian.

Keep up the good work.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rintinfinn:
Hi there. Just wanted to report I still got the issue with the device rebooting when I try to enable usb file sharing (november update of the rom).

Also @Magendanz, what would it take to bribe you into releasing this rom once a month so it would be up to date with the latest security patches? ;)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
Been reported several times. If you put the tablet in a bright light, or shine a flashlight on it, you can see the slider.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] sam240os:
1- AudioFX problem

This application works for a certain period then I guess It automatically gets terminated cause while I was listing to music on spotify(after one or two songs) I have to remove the headphone jack and again connect it to get the application working.

2-Network traffic monitor ( my internet speed is 700-900kbps while testing but it shows 3-5 mbps)

3- Music artwork on lockscreen(not stable )

4- Widgets position on home screen( Resizing )

5-Brightness(as mentioned earlier)

6-Usb file sharing (Don't work after I leave my device 10-15 minutes connected to my PC with Usb sharing enabled)

7-Warning message while reboot

8-No landscape mode on lock screen

plus what @TheDevil259 mentioned

@Magendanz Wanted to bring this to your attention
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
I think you'll find that the USB not connecting is a problem with the Infinity kernel and not the ROM. I've posted about it in the Infinity ROM thread, but the dev for the kernel hasn't been heard from in a while.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] sam240os:
Infinity Kernel 3.0 by @ibanezbass . This is the thread you are talking about right. If yes then I don't find any solution to this problem in that thread. Did you find any solution ? @lewmur
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
No. Like I said, we haven't heard from the Dev in over a month. But the choice is either this problem or using the kernel from the ROM and not having exFat support. I'd rather have exFat and use TWRP for USB or my Wifi Transfer Pro app to transfer files.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Warrenchild:
Thank you, very helpful information. I am going to try to remedy the situation right now. so I have the sk5 firmware that was installed on my device new. I am going to flash the ap bl and csc then make sure internet is connected during setup, and immediately enable debugging mode . then try to flash again. Am I understanding this correctly?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Yes, that's always worked for me.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
Developer mode. Of course you need that for debug, but dev is all you need.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Warrenchild:
You're the man! Thanks for your advice.

Danz got it figured out, thanks for your input.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Warrenchild:
testing lineage on my tablet I have found programs having a difficult time accessing storage. I tried to downloaded a file from chrome and it crashed, magisk was not able to download the file for patching, and magisk was not able to access the SDCARD to patch the boot image file. (files seems to work fine)

have you seen this or had experience with this issue? What would you like me to do to help trouble shoot this issue? I am at a loss. (it's part of the reason I went back to factory OS (which didn't work for my needs correctly))

Edit: Just used the Odin flash version you had posted, same thing try to download anything from browser and it crashes. Tablet restarts, as no issues installing apps I download from computer and transfer to SD card, knox lock is fine.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] samorgs:
I know this has been asked, but there has been no answer.

ROM installs fine, but when trying to install Gapps in TWRP Tablet reboots every time without installing them. Has anyone had any luck with this as I want to give this ROM a try.

I've tried both Open Gapps and BiTGapps and neither will install.

Cheers
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] andreasoz:
I tried it but when I try to flash it via twrp it just reboots into twrp like before. What version of twrp are you using? Any tips I can try to get it to work? Do you have magisk installed, and might that cause the issue for me?

---------- Post added at 05:03 PM ---------- Previous post was at 05:01 PM ----------

I've got the same issue, I've tried all of the gapps that exist with the same problem. Do you have magisk installed and what region is your tab? EU?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
As I mentioned earlier, this is due to a corrupt vendor partition image. Whenever TWRP attempts to write to it, the device will reboot.

My current builds don't seem to have the problem, and I'll be posting a new release soon (also with the cold charging fix).

UPDATE: New build (20200308) is posted!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] elwhiteboy01:
I'm trying to understand the process. Unlock bootloader, once you hit the power button to restart, hold down the volume buttons while tab is still plugged in to PC? That will make it possible to flash from Odin? I can't flash twrp or your 17.1 rom.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] henslayer:
I am running Lineage 17.1 on my Galaxy A70 phone and I like it a lot.

Just today I ordered a SM-T510 to replace an Asus Zen 10, which is stuck on Android 7.0 and will never get another update. The Galaxy Tab A will come with 9.0 Pie, but I am considering putting this ROM on it. My thinking is that I might as well do it right away before it is loaded up with stuff that will end up getting wiped and restored.

Any thoughts about how this compares to the stock ROM from those of you already running it? Mostly I'll be using it for streaming, reading e-books and general internet stuff. I'm not really into gaming.

Your input is appreciated. Thanks.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] FL0R1AN:
I Have the SM-T510 Tablet with 2 GB RAM and installed Nexus ROM from the same developer. I must say it is very smooth, does not lag like the original Samsung ROM and works like a charm. Check out the Nexus ROM thread from the same developer to see anything that does and does not work. In my personal humble opinion go for the Nexus ROM. Hope that helps you a bit in your decision.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
This LineageOS 17.1 build is basically just the GSI with a few patches to the kernel and config files to get it working better with the SM-T510. I also now copy over the lpm service and its dependencies to enable cold charging. Frankly, it's still got a few minor issues, but it's almost to the stability of the LineageOS 16.0 builds.

My personal preference right now is the latest Nexus Stock for the SM-T510, and there are versions based on both LOS 16 and LOS 17. You get all the benefits of LineageOS, plus Google apps and animations so that it's more like the PixelExperience custom ROM. Again, the LOS 17 builds still have a few stability issues, but that won't be true for long. I'll be updating the LQ (Lineage 17.1) build in a few days, but was just working out some resource tweaks for the Android One launcher so that we get a nice default layout with 7 columns of icons. The LP build (LineageOS 16.0) was just updated yesterday.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] henslayer:
Thanks to [MENTION=8475151]FL0R1AN[/MENTION] for the info and especially [MENTION=903232]Magendanz[/MENTION] for putting these together. I have read through the Nexus thread and that does look like it will be a better fit. Also, the tablet (3GB RAM model) should be here late tomorrow and I see that there is an updated Nexus ROM coming soon. So I think I'll wait for that and avoid an extra flash.

Your help and advice is much appreciated.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Okay, I found that img2simg was corrupting the vendor partition so badly that any attempt to write to it would cause a reboot in TWRP. Using the sparse conversion feature built into ImgExtractor seems to have worked around the problem, but it disturbs me that a mature Linux command like img2simg would have such a serious bug.

Stand by for a new release that will fix this problem and update to the 20200309 build of LineageOS 17.1 GSI.

UPDATE: It turns out that the sparse conversion in ImgExtractor had significant issues of its own. The best results I've had so far have actually been with the latest img2simg Ubuntu package (1:8.1.0+r23-5).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] jaladhjin:
Anybody have a flashable AOSP keyboard swipe fix or the libjni files?

I've tried a lot of versions like the 1st few results on a Google search & none seem to when.

I could just install another keyboard but truthfully I like the AOSP lib fix.

It's a small change & I can keep using AOSP as is :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
New release is posted...

Change Log:

20200314:

Fixed vendor image corruption issue from img2simg command.

Based on LineageOS 17.1 20200309 release from [MENTION=4467696]AndyYan[/MENTION].
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] henslayer:
Installed without issue along with open_gapps-arm-10.0-nano-20200311.zip, so that is solved. But still the same problem with SD card as the Nexus stock ROM.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Yeah, I'm afraid that it's a bug with the underlying LineageOS build. The OEM vendor partition hasn't changed.

UPDATE: If this SD card bug is a deal breaker for you, consider the latest Nexus Stock AQ build. It's based on AOSP 10.0 v214, and that seems to have fixed it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] DeathMD:
You don't have to flash or install anything. Swiping works on AOSP keyboard, maybe it's turned off in your settings but usually it's on by default. I'm also using this LineageOS build and it's working fine here. Check your AOSP keyboard settings.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] akira128:
can't flash image in odin

Can't flash the lineage-17.1-20200314-UNOFFICIAL-T510XXU2ASK5.tar.md5 image in odin

####

<ID:0/003> Odin engine v(ID:3.1303)..

<ID:0/003> File analysis..

<ID:0/003> Total Binary size: 2504 M

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> NAND Write Start!!

<ID:0/003> SingleDownload.

<ID:0/003> boot.img

<ID:0/003> product.img

<ID:0/003> recovery.img

<ID:0/003> system.img

<ID:0/003> vbmeta.img

<ID:0/003> vendor.img

<ID:0/003> RQT_CLOSE !!

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

<ID:0/003> Removed!!

######

Has anyone seen this before?

update:

I was finally able to successfully flash lineageos!!!

Here are the steps that worked for me:

1. make sure bootloader is fully unlocked

2. power off tablet, disconnect usb cable

3. hold down the vol up + vol down keys (don't touch the power button), insert usb cable (tablet should power on and will display the warning screen).

from here, hit vol up key to enter download mode)

4. Flash stock (T510XXU2ASK5) rom: from odin, flash stock BL, AP, and CSC files (uncheck auto-reboot option)

5. When flash is finished, unplug usb cable, hold power + vol down

as soon as the screen goes black, repeat step 3, and quickly hold down vol up + vol down keys and insert usb cable, once the warning screen appears, hit vol up.

6. Flash twrp: from odin flash twrp image in AP (uncheck auto-reboot option)

7. When flash is finished unplug usb cable, hold power + vol down keys, as soon as the screen goes black hold power + vol up to enter TWRP

8. Transfer multidisabler-t51x-1.41.zip and lineage-17.1-20200314-UNOFFICIAL-T510XXU2ASK5.zip to sdcard

9. Install multidisabler-t51x-1.41.zip

10. Wipe Data: Wipe --> Format Data

11. Install lineage-17.1-20200314-UNOFFICIAL-T510XXU2ASK5.zip

12. reboot
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] PMikeP:
Am unable to get Odin to flash the ROM. Update: Problem solved. (Doncha hate when this happens? I guess running thru the steps in a forum gets one thinking.) My solution below.

------------------------------------

After starting the process (running through the list of partitions), Odin gives me:

Complete (Write) operation failed.

All threads completed. (succeed 0/ failed 1.)

The gas gage on the tablet shows but has barely started.

My tablet is a "new" (open box) 2019 T510 from Best Buy.

It came factory reset with a May 2020 ROM.

I let it update twice, to the BTH4.

After that, I did a Factory Reset.

I did the Debug thing in Developer's, played the game of "change the date" to Allow OEM Unlock, and I unlocked the boot loader. (I get the warning from the OS.)

I entered the Download mode again.

At first, Odin wasn't even showing a COM connection for the tablet.

So I installed a fresh version of Win 10 20H2, let it update, and I installed SmartSwitch. Later I also downloaded USB drivers from Samsung.

Now Odin shows a connection. The later versions of Odin kind of indicate that it's trying to flash the ROM, as above.

(I tried the latest version, and intermediates, all the way down to 3.09.)

I presume, since others have been able to get it to work, that I am doing something subtly wrong.

But I don't know what. (I read that bad USB cables can cause this. I am using the OEM cable, as it's te only Type-C that I have.)

-------------------

Here's what I did that solved this problem: I did another Reset of the Tablet. The bootloader remained unlocked. I checked Developer Options. Still there. But the toggle to allow OEM Unlocking wasn't showing.

So I did the "change the date to a week in advance, and request a software update" thing. Rebooted and now Allow OEM Unlocking was showing in Developers, albeit grayed out.

After that - and I don't think that this part of the instructions are as clear as they should be - I told the tablet to restart, and, while leaving the USB cable plugged in, I held the Volume Up & Down buttons. (It jumps into Download mode immediately.) Then Oden 3.13 worked.

Now I'm waiting for TWRP to autostart - while I've been writing this, there's been a swoopy graphic (like the Niki swoosh), animating across my screen. (Am I supposed to gesture it?) How long do I wait? Am I in a boot loop?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] PMikeP:
Okay, thanks to a post by Zippy Dufus I realized that I was in a boot loop. (That is, TWRP didn't auto-start. A race condition somewhere? Does having an external SD card affect this?)

So then I had to read about how to "hard" reset a T510.

Vol Up + Pwr got me into TWRP. But it's been a long time since I've been in TWRP. What am I supposed to do with that screen that asks if I want to keep the System Partition Read Only? I haven't seen anyone give guidance on that yet.

So I wiped Data, and I installed Magisk. It booted into Lineage.

Now, will I always see the warning about my unlocked bootloader? Or is it okay to lock it now? (I ask because on another phone I have, if I lock it, it wipes all the data off the phone. (A Security thing, doncha know.)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] MiscDev:
I had the same issue. After flashing LineageOS the tablet wouldn't boot. It just showed the LineageOS loading animation. I used Power+VolDown to restart it. I figured out Power+VolUp boots to TWRP recovery. I formatted the Data Partition and wiped Cache. After that it booted fine.

@Magendanz Could you please add this to the instructions on the first page? I think it would be useful for newcomers.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] MiscDev:
Does anyone else have an issue with the time/date?

When I unlocked the bootloader in the stock ROM I set the clock back a few days to get past the 7 day OEM unlock requirement.

After flashing LineageOS every time my tablet reboots the date and time reset to that time.

I can set the time normally, but it is lost when I reboot.

Setting the time manually in Lineageos and TWRP or using 'date' from ADB does not permanently fix this problem.

My tablet is not always connected to a network so NTP doesn't help.

Does anyone have any ideas what could be wrong? Where is the wrong time being stored?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] PMikeP:
After I used an Uninstaller to uninstall a core application, I got into a boot loop.

I was able to do the Odin flash procedure again, so I was able to recover.

But since TWRP automatically started after three loops, it occurred to me that it would have been a lot easier to recover if I had made a TWRP Backup of the partitions.

I'm doing that now. And, since I don't know any better, I'm backing up ALL the partitions.

Could someone post some guidance in this Guide about which partitions are likely to change and need to be backed up?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] PMikeP:
BTW, I don't want to sound ungrateful. Despite the (self-induced?) problem that I had installing the ROM, I'm grateful to @Magendanz for providing it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rw_on_xda:
it is already, look at the 1st page

Instructions:

From OEM stock firmware:

Unlock bootloader <= this is a link to the guide !