yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Echo_2000:
Hi @TALUAtXDA and thanks for keeping this device alive.

I saw that you mention in OP that sooner or later a version for the LTE variant will come. I just wanna ask if this version will come anytime soon or if I should just flash the current build in the meantime.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
You're welcome. I'm planning to attempt to setup sources and build for the LTE variant in around more or less 1-2 months.

I think you should be able to install a build for the LTE variant over an installation originally from a build for the WiFi-only variant for whenever I have one ready, and with that, you can install my current build for the WiFi-only variant if you want to in the meantime, and you wouldn't need to start fresh whenever you install a build for the LTE variant.

Do note that I'm going to release a new build in a few hours from now, so I suggest waiting until then.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Echo_2000:
Thanks for your replay. I will wait for the new build to enjoy Android 11.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rambomhtri:
Oh, that's really interesting info. I never thought you had to select one existing model to bypass the ROM, or however it works.

So... basically, to Google Play Store, we have a Google Pixel C tablet, and it will show everything that would be shown in a Pixel C, correct?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dskiller:
Great rom but have problem with app called video downloader from inshot when used along with other webbrowers causes major system lag causing firefox and chrome to stop responding. Could be memory related as dev tools reports zero free memory when it happens
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Yes, correct (with a few exceptions, I think?).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] littlegreen:
EDIT: I just remembered I forgot to wipe (facepalm). Wiped and re-flashed and everything is now OK :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
New release for 20210617

Download:

lineage-18.1-20210617-UNOFFICIAL-gtaxlwifi.zip

drive.google.com

Changelog:

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

The WiFi and Bluetooth firmwares have been updated from Samsung's A720SKSU5CTL2 firmware.

The qcom_cfg.ini configuration file for WiFi has been imported from Samsung's A720SKSU5CTL2 firmware - A change within it appears to have made WiFi more reliable.

The sensors.universal7870.so library has been updated from Samsung's stock P580ZSS1CTI1 firmware.

The health HAL has been upgraded to version 2.1.

There are a few other small miscellaneous changes (mostly small cleanups).

There are many updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.

Some unnecessary drivers have been disabled in the kernel.

The sdfat driver in the kernel, which is used for exFAT filesystem support, has been updated to version 2.4.5.

A few changes have been imported to the MMC block device driver in the kernel from Samsung's M105GDXS6CUD4 kernel that fix extremely rare kernel panics that occurred when there was an error with a MMC device (mainly with SD cards).

The fix for an issue where the duration of videos that are taken is lengthened by the time spent in deep sleep/suspended that was previously used has been replaced with a better fix in the Exynos fimc-is2 driver in the kernel.

As usual, enjoy.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rambomhtri:
If we were in the latest ROM, after we flash the new ROM you just released, is it recommended to wipe anything?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Archaide:
Thank you very much for the effort to bring the latest android to this old device. Much appreciated. I've only registered to say this.

Btw: just flashed over the last rom. no wiping no nothing. Same thing for the last 2 roms. Works flawlessly everytime so far. Great job.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Demonpanda8:
small problem, how do i unpin apps?

i clicked the app logo from overview and it said that i need to press back button and home button and it isnt working. will i have to wipe everything and install the rom again?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] tennessee_titan:
Don;t you just hold the app button down and then tap remove when the pop up appears??
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Raggamuffin86:
Hey TALUAtXDA,

A couple of days ago I installed your Lineage OS 18.1 on my tablet. So far everything works just fine .....

....However I do have a question:

Ever since I set up my device with my Google account .... My Google account lists a new device that has logged into it: "Google Pixel C"

.... I don't own such a device ....

... To me it only makes sense that instead of "Galaxy Tab A (2016)" Google registered my tablet as "Google Pixel C" .... or worst case scenario, my account got hacked and it has nothing to do with the install of your ROM ...

Please note I'm a complete layman / idiot concerning everything you guys on here seem to be experts in. I just wanted to update my tablet and with the help of a YouTube tutorial I was lucky enough to be successful, despite having no idea about what I was doing ;) ... So, if it's okay could you respond to my question like you were talking to 3rd grader ? ;)

Cheers

Ragamuffin
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rambomhtri:
Yeah, it's simple, although this answer is not 100% correct, but gives you an idea: when you flash a custom, not original, not stock ROM, sometimes the name Google recognizes and alerts you is the name the device (in this case Pixel C tablet) this custom ROM is based on. So, AFAIK, the developer of this LOS 18.1 ROM took as a base/start the Pixel C ROM or structure or scheme, and adapted it to the Samsung Tab A6. That's why Google will recognize this tablet as Pixel C.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Alright, here goes. Something called the "build fingerprint" is set to an old one for the Google Pixel C tablet. This is so that we can bypass a check put in place by Google, called "safetynet", used by apps to tell if any system-level modifications have been made. "Safetynet" will pass with this fingerprint provided some other conditions are met. The build fingerprint is used to identify which device you have. As a result of this, your device will be shown as a Pixel C.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Raggamuffin86:
Great! Thank you for the quick response. So nothing to worry about ...what a relief! Thanks!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
By the way, that reply is technically not right. Look at my reply for the correct answer. We don't take anything from the Pixel C, except an older build fingerprint from an older version of its firmware.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rambomhtri:
I knew I wasn't right, I've edited my message warning it's not 100% correct. Thank you.

By the way... why not all ROM's that don't pass safetynet put PIXEL C in the fingerprint?

Although... I guess it's more complex than typing pixel C in the system file...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rambomhtri:
Hi, I have bought recently the LTE variant to be able to use WhatsApp. I've been using the original Samsung stock ROM and it was way worse than LOS 18.1, as I expected. Didn't like it at all. So...

I understand that until you release LOS 18.1 for the LTE variant, with this ROM version for the WiFi variant I won't be able to put the SIM card and be able to set up WhatsApp, right?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Yes. You won't have mobile networking functionality, so you can't recieve the text message with a verification code. However, you could probably install WhatsApp on your tablet running the build for the WiFi-only variant, and put the SIM card in some phone or another tablet with mobile networking functionality, and use it just to recieve the text message with the verification code.

Do note that I'm going to attempt to get building for the LTE variant. I can't promise that I'm going to be successful. I don't expect to fail, though.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rambomhtri:
Fantastic news. Then I will wait, you are awesome! THANKS!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] KenMacD:
I'm looking for something to run on an SM-P580 (gtanotexlwifi), but I couldn't get this build to work.

I saw some posts suggesting that SM-P580 devices were basically SM-T580 with added s-pen hardware, and that a T580 rom would work, just without pen support (which is fine). I haven't found this to be true though. Was I misled, or am I likely doing something wrong?

I patched the updater script and flashed it that way. I also tried decompressing the system.new.dat file and just using dd to overwrite the system partition.

I can get it as far as the LineageOS boot screen, but it hangs there.

Any suggestions?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
I think that if it's in a bootloop (stuck and looping on the boot animation and not getting anywhere further. I'm assuming you mean that instead, and don't mean that it's hung on one frame of the boot animation, and not doing anything at all besides that?), and not just not booting at all, it should work provided it's all setup and installed properly.

My only suggestion for now is to format data if you haven't already in TWRP (Wipe -> Format Data). Let me know if that works.

If that doesn't work, you'll need to get logs that would contain useful information that would help with figuring out what's causing the bootlooping. I'll give you instructions on how to do that.

By the way, if you do get it installed and working, there could be a small chance that you may encounter issues in relation to touch input (not s-pen-related). I'm completely unsure about that.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] KenMacD:
Correct.

I typically do, although I don't restart the recovery (if that's needed). I also have to use an unofficial twrp build as the official (newer) one has display issues

Okay. That would be great. First I'll start by reconfirming this is actually with 18.1. I've been switching between your 17.1 and 18.1 and flashing in any way I can think of to try to get something that boots.

Good to know. The twrp is a little fussy on the slides, so you might be right. I'd be happy to work on that from a base of a booting platform though.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] KenMacD:
Not sure if this helps, but here's a last_kmsg log from booting. It boots to the LineageOS looping-logo sometimes, and sometimes just restarts before the logo.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Bhaam:
Hi everyone!

just installed this rom, connected the device to the computer, the device was recognized but appeared empty, what can I do for the storage to be accessible from the PC like before?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
There should be a notification saying:

"Charging this device via USB

Tap for more options."

...while your device is connected. Tap on it and select "File transfer".
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
New release for 20210709

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

Changelog:

Latest updates from LineageOS.

Merges of the latest changes from AOSP for repositories forked by Lineage have been picked to skip the wait for them to be merged (repopick -t android-11.0.0_r39), and the rest of the repositories not forked by Lineage were additionally switched to the android-11.0.0_r39 tag, for the 20210705 Android security updates.

A patch to the PermissionController app has been applied that adds the FAKE_PACKAGE_SIGNATURE permission group to it - The signature spoofing permission can now be managed through the permission management interface at Settings -> Privacy -> Permission manager.

The audio outputted from the audio jack while playing media will now be noticeably louder, as the headset "DAC1 playback volume" for media has been increased to the maximum of 175 from 162.

There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.

A few patches have been applied to the qcacld-2.0 WiFi driver in the kernel, which are mainly vulnerability fixes.

Enjoy.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Lumito:
Updated just now. Works pretty fine :).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Wow, already? Excellent. :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] JimDandy68:
Just updated to this after failing with the last version. Bootlooped with both that and this one until I jogged my memory (reading a blog post) about how to update correctly. Sideloaded this version, then NikGapps latest, then Magisk (rebooting TWRP each time), and now all seems good.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rapidm:
Same here. All good, but sound from speakers still seems kinda low for me (compared with the original rom).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
In the "gain-media-speaker" path in the /system/vendor/etc/mixer_gains.xml file, there is a control named "Speaker Playback Volume": https://github.com/TALUAtGitHub/and...006ab6174ac/configs/audio/mixer_gains.xml#L11

The maximum that it can be set to is 39. In testing on my device, when I tried to set this higher, as well as making the audio from the speakers louder, it also caused extremely undesirable distortion, that of course got much worse as it was increased more and more, so that's not an option. The "DAC1 Playback Volume" is already set to the maximum value to 175 for that path. Standard note: If you want to experiment with this control yourself, I'm absolutely not responsible for any damage you cause to your hardware, including in the long term after using a higher value for a while if you are to.

I've barely ever used the stock firmware, so I don't know how loud the audio from the speakers would have been running it on my device, but I honestly doubt it would be any better. Almost all of the gains/volumes that are used are the exact same as they are in the stock firmware, and a version of Samsung's proprietary audio HAL (that appears to be heavily patched) is also used, so these issues that have also been reported before with the audio from the built-in speakers sounding quieter than as with with the stock firmware are especially puzzling.

Consider using external speakers or headphones. The speakers built into these devices aren't very good, anyway.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Archaide:
Thnx alot. As always smooth sailing. Download, boot into twrp, flashing, reboot, done.

The volume is much louder now.

Really good job.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rapidm:
Thanks for the reply. I prefer a working device than a loud one. I ll use bluetooth if needed :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rosco_pc:
mmm WHAT is the correct procedure? The last 3 updates I keep having a bootloop no matter how I update

Have installed LOS, NikGapps and Magisk.

My upgrade procedure is normally

reboot to TWRP

install new ROM

install magisk

reboot system

Tried adding NikGapps after the ROM the last time but still bootloop.

When I end up in a bootloop re-installing just the ROM will get me out of it.

This time I tried just installing the ROM, but ended up in a boot loop as well. re-installation did not work and had to start over again with a factory reset followed by installing ROM, NikGapps and Magisk
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Are you installing an up-to-date NikGapps package? If not, try one - https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-R/04-Jul-2021/

Edit: I've re-read your post. I've missed where you said that you have to do a factory reset, and it will boot with that same NikGapps package. Hmm... I'm not sure at all. I personally reinstall Nanodroid MicroG and Magisk after updating to a new build, and never have issues with bootlooping.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 12312:
Greetings! After not having flashed anything for a good amount of time, I was pleasantly surprised by the setup being the same.

One thing I did notice after flashing the latest build (20210709) is that the "Trust" app will warn on every boot that this build was signed using public keys.

Would I have to worry about this, or should it be (relatively) safe to continue?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
You can ignore and disable those warnings. Currently, I don't sign my builds using my own release-keys, and they're just signed using the publicly available test-keys, which is what the trust app warns about, although with little detail. I'm considering signing my future builds using my own release-keys.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rosco_pc:
I'll try with update newly downloaded Nikgaps next time 😄
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Pat33170:
Update done from 05/05 version today with NickGapps Core: It works perfectly.

Thanks again for your job and time.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Zeppelli:
To update i just need to flash it over? Just a single flash in twrp?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] gunatm:
Thank you ... I installed your custom rom including the flame gapps. It worked like a charme.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] skiwarz:
@TALUAtXDA

Do you have a kernel config that you used? I didn't see the actual config in your kernel sources on github... or am I looking in the wrong place?

I'm working on getting 18.1 onto a SM-P580.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
You would be looking in the wrong place.

It's here: https://github.com/TALUAtGitHub/and...rch/arm64/configs/lineage-gtaxlwifi_defconfig
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] skiwarz:
Mine is doing the same exact thing (P580). How did you get that kmsg log?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Belarios:
I just installed with the July 24 release of opengapps pico and it's working fine. Thanks for your work.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Bertonumber1:
Been using lineage 18.1 since it first became available and have updated it every month give or take since.

There is not a more stable rom for this device and I for one fkin love :cool: it!!!

Excellent work @TALUAtXDA

We really appreciate your work and time dedicated to this amazing tablet..
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Chris_0147:
thanks for all the moments you gave me in your ROMs for gtaxlwifi keep updating (my tablet is dead) thanks @TALUAtXDA
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Chris_0147:
Now I will use my Samsung s5 sm g900t (klte) thanks for everything
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Zeppelli:
Guys can you tell me if, vpn hotspot (root permission needed) works for you? I'm currently on on the LTE variant, and i don't know if the problem is that i'm on this specific variant. Thanks in advance
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Bertonumber1:
Hello I use UFO vpn Hotspot and it requires root.

Everything works perfectly.

Regards
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] gioxoid:
tried to install latest update, and now stucked in logo loop. I'm unable to enter recovery, only download mode. Is it possible to sideload the rom and gapps zip files? Or any different procdure to solve?

Thanks
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] quantumcog:
Flash Twrp via Odin

And try installing ROM again in Twrp

Try clean flash (it will wipe apps but not internal storage) --> Wipe Data, cache and system
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] gioxoid:
Yeap, it worked. Thanks! You save my weekend.

I have only one issue. The Skygo app (paytv app for streaming) says me that the device is rooted. I purposely not installed Magisk, but it smels something. What could be the problem?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] FBK2904:
You have unlocked OEM and Skygo recognizes that too:cry:.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] gioxoid:
Well, with a different A11 rom SkyGo worked.

Something changed in the app?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] quantumcog:
There are two things you could try

1. You could rename TWRP folder to something else

2. If the above don't work try rooting via magisk and enable magisk hide in settings it will hide bootloader status and will allow to pass safety net
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] gioxoid:
i can understand your suggestion, but i cant' understand why with a different rom (i.e. crDroid) and the same config (TWRP recovery), Skygo stopped working. I will conclude that something different between ROMs ?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] FBK2904:
I had tried this with several different custom ROMs as well.

The Skygo app can be opened, BUT no stream works (root error)!

Even with Magisk-Hide, I couldn't outsmart the app at the time.

My only solution to date (as reported in several Skygo-Threads here) is an original and "untouched" STOCK-ROM!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] gioxoid:
well, till yesterday i was using the Skygo app on crDroid ... In past weeks I had also used it with Magisk rooting, and hiding was working. So i guess a very recent update of the skygo app itself could be the culprit.

BTW i checked and the rom passes safetynet check. I'm very puzzled
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] quantumcog:
Maybe skygo is updated to check for safetynet test
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] gioxoid:
Oh yes could be, but the rom passed the test.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Kostareka:
I want to know what is the difference between private and public keys and what are their benefits. Do you have a link to an article that explains this?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
The main benefit to using my own release keys as I already explained in that post is that it gets rid of Trust's notifications about builds being signed using public [test] keys. This ends up making people think that there's something seriously wrong. I only started thinking about switching to release keys after someone reported the notifications from Trust a few posts back. Saves headaches I suppose. Also, I remember someone over in my old 17.1 thread thought it would be a good idea to have my builds with release keys, so I guess that was a further motivator.

Another benefit is listed in this article, which also contains more useful information: https://source.android.com/devices/tech/ota/sign_builds

...so, if an .apk file is replaced with a potentially malicious one signed using a different key to mine (such as the test key), the new app from that new .apk file won't be able to access the old data for whichever app it's replacing and do whatever it's supposed to do with it. That's only really effective with data encrypted, but it's a benefit nevertheless.

I think that's basically it in this context. There should be some way to also verify if a signed build actually comes from me, like with official LineageOS builds: https://wiki.lineageos.org/verifying-builds.html for ultra paranoid people who don't want to make their own builds, but I'm not sure about that.

Maybe these benefits aren't really all that significant, I'm not really sure.