yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] DrGEROH:
I tried installing this unoffical LOS 17.1 ROM (build 20210207) on my SM-T580 yesterday using TWRP 3.4.0.0, OpenGApps ARM64 (build 20210210) and a "clean" install with an initial wipe/format of Dalvik/ART, System, Data, and Cache.

LOS started OK, but the start-up process got stuck in a loop after I declined Google Assistant (the screen that asks someone to say "Hello Google"). Choosing "Skip" sent the process back a few screens repeatedly (grrr). I did complete installation from TWRP recovery a couple of times before giving up.

I've been using official LOS 17.1 on a spare Galaxy S5 (SM-G900T) for a while and have been pleased with its stability and efficiency (WRT performance & battery life).

This tablet isn't my "daily" (I replaced its system board recently after the original failed last month); the stock Android 8.1 ROM (T580UES5CTL1) works well enough for me, but I'm open to replacing it with a stable LOS 17.1. At this point, T580UES5CTL1 is flashed back on the tablet again.

I guess for now I'll wait for your next unofficial build and try this again...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
The problem would appear to be with gapps and not the ROM. You could also try not skipping the Google Assistant and then uninstalling it once the setup is complete.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] soaringowl2145:
I have successfully updated from the December build to the February build. I have the "Hey Google" turned off. January to February does not work but December to February does. I have not installed anything else since then.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TheYester:
Dirty flashed from the januari version to the latest version with no problem, flashed only the ROM not the gapps since they were allready there. Everything works here fine! Sometimes a small glitch but overall a very stable ROM. I use it as my daily driver
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Portoconnor:
Hi, for some reason the wifi is being automatically turned off when I reboot, and I have to manually turn it back on. Is that supposed to happen or is it a bug?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TheYester:
Hello, I don't experience the same thing on my sm-t580. Maybe a clean install?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Chris_0147:
@TALUAtXDA I have a question how is the experience in online classes in zoom (I ask you this question because my younger brother is going to start studying)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
I'm not sure myself as I don't use any video conferencing apps.

Has anyone else tested any on a recent build?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Chris_0147:
@TALUAtXDA I will trust your rom because it is the most complete
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Jamess27:
I use microsoft meet and zoom, they work fine
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bnwgraaf:
Finally my Samsung tablet has a newer Android! Thank you for this rom!

I have a question: my internet speed is not that great. I do have 5Ghz in my house, but the SM-T580 c9nnects to the 2,4Ghz band....

Is this device capable of connecting to 5Ghz and if yes, can I force that?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] LifelessDead:
Yes, works fine on 5GHz. Just pick your correct 5GHz network from the wifi list, and "forget" the 2.4GHz one.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bnwgraaf:
Thanks for your reply. My 2,4Ghz and 5Ghz networks do have the same SSID and my other devices (and this Samsung with the stock rom) do connect to the 5Ghz one automatically!

And I have seen that it should be possible to force it in the wifi settings, but I see it is connected to 2,4Ghz but I can not change it to 5Ghz...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
I have no idea why it doesn't use 5GHz on one network with both 2.4GHz and 5GHz, and I don't use one network with both, but as a workaround, you can setup 2 separate networks - one on the 2.4GHz band, and another on the 5GHz band - with different SSIDs, and connect to the WiFi network on the 5GHz band. Your routers settings/admin page should let you do so.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bnwgraaf:
I have a 2,4Ghz router and two 5Ghz wifipoints/extenders.

It turns out, the power of the wifi extenders was switched of for some reason. Now it works great!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] fs1023:
Hi, thanks for all your work with this project. Do you have a guide to install the ROM? Haven't flashed a ROM etc for a while and have forgotten the process.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] fs1023:
Hi, what open gapps file to use? Error installing arm64 android 9 stock with rom? Do I use android 8.1 instead?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Use the pico variant package for arm64 and Android 10 from https://opengapps.org/

Install any additional Google apps that you need from the play store.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] fs1023:
Thanks for your reply. Installed rom with your recommended gapps file and Magisk. Works fantastic, very fast and with sound. Just a couple of tiny issues

1. Can't get Samsung wearable gear app to work even though I have full root with SafetyNet pass and hidden app in Magisk.

2. On reboot Wifi does not auto connect but works fine after power off.

Once again thanks for your help and fantastic rom. Great to have this Tab with Google 10.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Chris_0147:
Deleted
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Excellent. For your issues:

1. That's a type of thing to be expected... Not really a "real" issue per se. The gear app is probably checking for something else, for example, the Knox warranty status. There is probably a modified version of the Gear app somewhere that you can try, with any of those types of checks removed. You can probably find one somewhere else on this forum.

2. I'm not aware of that exact issue. I'm only aware of an issue where WiFi is disabled after a reboot, and it needs to be enabled manually. Maybe that's just a better description of the issue you're having? Apparently, that issue only occurs when WiFi scanning at Settings -> Location -> Wi-Fi and Bluetooth scanning -> Wi-Fi scanning is enabled, and it was fixed in LineageOS 18.1/Android 11. Not sure why people care so much about that issue for usual usage, anyway... It takes one slide down on the notification bar and one tap to enable WiFi.

Finally, you're welcome.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] fs1023:
Again thanks for your reply. Point taken, they are not issues and I should have worded my comments better.

1. Thanks for the heads up, I will search for modded gears app.

2. You are correct, I meant as you have described, WiFi disabled after reboot and it is not a problem to manually enable.

I will try the LineageOS 18.1/Android 11 update in due course, just trying to get used to doing this stuff again:)

Again thanks for your help and work you put in to update T580.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
New release for 20210313

Changelog:

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

There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel, many changes to the rcu, locking and btrfs code from 4.4, and a few changes from Samsung's M105GDXU6CUA1 kernel to the kernel.

The exynos part of the BSP has a few changes from Lineage's 18.1 branch for HWC and memtrack.

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

Nothing more to this release. Enjoy.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] soaringowl2145:
Same issue with the March build. When doing adb it says waiting for device and the logcat never works
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
I think that either you didn't do as I described correctly, your installation of ADB isn't working (bad drivers?), your devices micro USB port or cable isn't working (were they working for data transfers before?), or something else is going completely wrong for some reason that prevents ADB from working (and I have no idea for what that could possibly be). I just tested ADB on boot on my installation (just edited default.prop and set persist.sys.usb.config to "adb" and ro.adb.secure to "0"), and it works fine, as with ADB after booting as well.

I have absolutely no idea for what your issue could be without any insight. I've made few changes since the January build (pretty much as in my changelogs), and only applied/made many changes to the kernel, and my latest build seems to boot for everyone else with good installations, as with the Febuary build as well, so assuming you just did a simple upgrade and nothing else on top, your issue is extremely baffling.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] soaringowl2145:
When I put the file in a new folder named /system_root

So I tried a normal upgrade again but this time I installed the rom and an updated version of opengapps and it worked successfully. Any idea on why that fixed it?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Jamess27:
Oh, you are a genius. I'll stick with your ROM, obviously.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] tennessee_titan:
Gee, another ROM you have to be a developer to use! What is there for the rest of us?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Jaaxx:
Buy a new tablet every 3 years and stick with stock ROM.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Jamess27:
Sorry to bother again, but it appears that wifi is not turning on after turning off the screen and (I think) the device going into deep sleep. Is there a solution to this?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
New release for 20200303

Changes:

wireless: add back Samsung's 'temporary' workaround due to qcacld-2.0 page allocation errors. Looks like this is actually necessary. Works around issues with WiFi not being possible to be enabled after some time again due to page allocation failures that still exist. (Commit: c41850b80a935b7a1052cbda07eb7f59ba75a6c9 in kernel repository)

Revert duplicate "signal/ptrace: Don't leak unitialized kernel memory with PTRACE_PEEK_SIGINFO". We already had this commit as in Linux v3.18, the content of this reverted commit are useless. (Commit: 2357085a279d24a7806483b9da45bfd557e1dfe1 in kernel repository)

Download: https://drive.google.com/open?id=1IMFBy5KhelBSWKlOK3YfFf9DKlKNjAED

This release isn't very significant, there have only been small changes to the kernel, including adding back Samsung's workaround (which I've removed before as I thought it was unnecessary as WiFi appeared to work fine initially) to the wireless configuration stack for page allocation failures for qcacld-2.0 (the WiFi driver) to workaround the issues where WiFi can't be enabled (due to page allocation failures that still exist) again after some time. Enjoy.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] marcelser:
If I understand correctly, things like fixing the sleep issue and set selinux to permissive are not permant changes and will be reverted after a reboot. Is there an easy way apart from exkm which I don't know to reapply them after boot?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
New release for 20200309

Changes:

Latest updates including 20200305 security patches

Upgrade android.hardware.keymaster to 4.0. (Commit: ab01d69c0c90f6de4769b9de6589d88e8d4fe1db in device tree)

trace: exynos-ss: use PTRACE_MODE_READ_FSCREDS. (Commit: 69e98c6717f5fb9f9d156e750b9ae680c9193387 in kernel repository)

lineage-gtaxlwifi_defconfig: disable CRYPTO_FIPS to get encryption partially working. (Commit: c170ecb847783a014b1ff449b025fb964ed71210 in kernel repository)

sdfat: update to version 2.3.0. (Commit: e33b2e83d9e111c74737f6d136470feddf29f12e in kernel repository)

Update the BFQ IO scheduler to v8r12 using a port. (Commits: e33b2e83d9e111c74737f6d136470feddf29f12e..bae3119b92642df8cecea4a6eedcbd130e7d8779 in kernel repository)

Download: https://drive.google.com/open?id=1QGL75MBZvih611TCNrLzln_8hPet86wL

In this release, I've tried to get encryption to work, and only got it partially working.

EDIT: it also looks like adoptable storage is now fixed.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ScottB59:
Hi. micro sd card causes reboot recycle. Workaround here:

Hi.

On my Tab A 2016 tablet, when i try to format the sd card, the r.o.m. shuts down and reboots, only to shut down again after i enter my password. I was able to reproduce this error, using the Bliss r.o.m. as well.

I found out that i can remove the sd card from the tablet and the reboot/recycle stops. Lucky. But the tablet will continue to reboot/recycle when the sd card is reinserted.

Workaround: If you have another android device with a micro sd card slot, you can format the sd card on that device and reinsert the formatted card into the tablet. The tablet will accept the card and use it normally.

I still haven't found the "Kosher" solution to this android bug, though.

Thanks; ScottB59
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] srgrusso:
You can also boot to twrp and format it
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Christian45:
Hi,

I tried to install the rom. I started mit TWRP, made the wipe, installed the rom zip and the gapps. After reboot the tab hangs at the moving circle directly after switching on. I tried it again with the same result. Do you know what I'm doing wrong or is there a fault in the image?

As alternative I tested the installation of the bliss rom and that works fine.

Can someone help me?

Thanks in advance

Christian
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] srgrusso:
I little more details would help. Were you on the stock ROM before flashing LOS? If you were, did you format data? That's the only thing I can think of without a little more information.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Christian45:
Hi, I solved the problem. I tried it some times. Reboot after wipe, reboot after installing and so on. Then I tried it without Installation of gapps and: the tab started as expected. Therefore I tried the bitGapps and was surprised, it works. I tried it sometimes with opengapps without success. Till now I'm verry happy with the rom, no errors.

Thanks a lot.

Christian
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] PK5ive:
I try to install it now. Thank you for your work and i will post again when i will have problems with it.

Thank you and followmsi thank you, too.

It seems that i have a problem: I wiped dalvik/cache, format data, wiped dalvik/cache again and installed the rom and gapps nano, ARM64 10.0 and nano. Now it is stuck in the boot procedure when the green curved line and the animated green circle is showing.

I am from LOS 16 from Valera, updated only because i want access to security patches. Now i bricked it i guess.

Thanks for help.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Christian45:
[MENTION=10419409]PK5ive[/MENTION]

I had exactly the same problem. Wipe and reboot before installing the gapps did not fix the problem. First try to install the rom without the gapps and then start it. When it starts, you will know if it is because of the gapps. I had the problem with the openapps pico and nano. Then I tried with the bitGapps and the tab starts normally. You can install the other Google Apps from the store.

Maybe the error occurs due to the rom, but can be bypassed.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] PK5ive:
Thanks for reply [MENTION=8437995]Christian45[/MENTION]. In my case it makes no difference between installing with or without GApps. I can let it load for an entire night and nothing happens. Ive read your problem Christian45 and i tried the same way you did but no success.

I had previous lineageos 16.0 installed. Now 3rd try with:

- 1. Format data

- 2. Wiping dalvik cache.

- 3. Wiping everything except of external sd card

- 4. Wiping dalvik cache

5. Installing rom

6. Wiping dalvik cache

7. Reboot system and let it boot

EDIT: doesnt work either
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] srgrusso:
Where you using your sdcard as adoptable storage in los 16.0. Maybe try removing your sdcard and see if it works.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] BarnOwl:
I have the same problem, stuck at LOS boot image.......cannot get it in TWRP again, so how did you go forth from the stuck logo?

EDIT: Fixed
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ChrisCologne:
This is the T580 version, but I have a T585 and donot use the LTE module.

Does it work on my T585 or the the Hardware too different?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ajax33:
Question on audio clicks while the tablet screen is off

I've noticed that my speakers click or pop when the screen is off. Anyone else noticing this, or ideas on this?

Also, for anyone having issues installing the ROM, in my experience make sure you don't let TWRP install the app as you reboot. For me that caused it to fail each time, but when I stopped doing that, it would install and boot fine.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Christian45:
[MENTION=218092]BarnOwl[/MENTION]

If you are in the bootloop, you can start into twrp as follows.

Press Power, Volume Down and Home for some seconds. The tab switches off. Once the screen is off, press power, volume up and the tablet starts in twrp. If you are too slow, it will start in the bootloop again.

[MENTION=4039691]ajax33[/MENTION]

Sometimes the speakers make noise in standby.

It would be nice if this could still be fixed.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Some change/update in Lineage might have broken your old opengapps package somehow, and the updated version has some fix. That's my only idea...

Anyway, I'm glad you've got it working now. :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Klaerchen:
Hi @TALUAtXDA

the DMESG shows a strange behavior of the shutting down/starting of the CPUs and the device shutdown/wake.

At a certain time the second CPU cluster is shut down:

And some 100ms later the power management / governor suspends some hardware components and even does shut down the non-boot CPUs of the first cluster and goes to sleep.

This part happend at about 09:27:15 (AM), and an alarm was set for 40s in the future (09:27:54).

But immediatley after entering sleep mode (the same time stamp), the device is woken up again:

And shortly after that also the second CPU cluster (CPU4 to CPU7) is booted.

This behavior (shutting down 7 of 8 CPUs, going to sleep and immediat wake up) can be seen quite frequently.

The wakeup reasons are recurring:

These wakeups come every 2 to 6 seconds.

Could some interrupt sources be routed to CPU0 (which is always booted) to avoid booting the rest of the clusters?

It never stays in sleep mode until the alarm is triggered.

Is this normal? Do you have an idea?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
This is entirely normal. When entering deep sleep, the Exynos CPU hotplugging driver at drivers/soc/samsung/exynos-cpu_hotplug.c in the kernel shuts down the 4 cores in the second cluster. After that, PM shuts down the non-boot cores in the first cluster (all cores in the first cluster except 0). When woken up, PM brings the non-boot cores in the first cluster back online, and the Exynos CPU hotplugging driver brings the cores in the second cluster back online (note that I'm unsure about the accuracy of this very last bit). This is all the usual behaviour of Samsung's kernels - I didn't change anything.

Looking at the time spent in deep sleep using certain apps (such as smartpack kernel manager) or the data from /sys/kernel/debug/sleep_time (if only I knew from where the apps get their much more precise data...) on my tablet, it spends most of the time I put it to sleep for in deep sleep, even with an alarm setup, so there appears to be no issues here. The time spent in deep sleep is not counted in the timestamps for kernel log messages in dmesg, so that cannot be used as a way to tell how much time is spent in deep sleep, which is what you're trying to do.

If we were to change the behaviour such that the cores are not brought online whenever such wakeups occur, we'd have to have a way to tell if a wakeup is caused by the user or not (for example, through the home or power buttons) - otherwise, if a wakeup is caused by the user, all of the cores except 0 would always be offline, which is of course no good, and we'd have to make modifications to the kernel that are not preferable. Also, as I said, this is all the usual behaviour of Samsung's stock kernels, and there are no real issues here, and I doubt hotplugging the cores wastes much power, anyway.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TabAGuy:
@TALUAtXDA One curious question, now that LineageOS 18.x is out, is there any possibility that you'll be creating a build for that?

With a quick google search, I did find this thread, which does give a thanks to you:

https://xdaforums.com/t/rom-sm-t580-unofficial-64-bit-lineageos-18-1-2021-03-16.4190313/

However, I've been so happy with what you've done, I was wondering if you were going to do your own LineageOS 18 build. Also, whatever your direction, I think there are others that are as happy with your work as I am (THANK YOU!) and will want to know this answer. Might want to sticky it, if that's an option you have in a thread.

Thanks in advance, regardless of the direction you choose.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
Yes, very, very, soon. Two days ago, I had installed a build of 18.1 on my tablet, and have started further work on it. There isn't much to do - most of what had to be done has already been done, and there are few issues. I'm thinking that I'm going to release one new untested 17.1 build, and then start releasing 18.1 builds, and maybe also a few more 17.1 builds before discontinuing 17.1 entirely. You're welcome. :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Klaerchen:
Thanks for your answer! I was not aware of the kernel's timestamps not counting during deep sleep! That explains the behavior perfectly.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Chris_0147:
hello I want to know if I can only have 4 cores turned on without playing and when I start playing the 8 cores will turn on when playing as the stock ROM is possible?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] StriKe_jk:
Should I use arm or arm64 gApps for this?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Chris_0147:
Arm 64 gapps I recommend that you use Nikgapps in the version go Android 10 so that you have more free ram tell me if you want me to pass the link to you
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
New release for 20210413

Download: https://drive.google.com/file/d/1m3RPFY-gJ4R8ZYKgMr_8ilJZzZtDsOyM

Note that as I've moved onto 18.1, I'm unable to test this release, and any future 17.1 builds. Nonetheless, it should boot and work perfectly fine. For anyone who hasn't seen it, I now have a new LineageOS 18.1 build here: https://xdaforums.com/t/rom-sm-t580...18-1-2021-04-07.4190313/page-13#post-84795467

Changelog:

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

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

That's all there is to this release. As usual, enjoy.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] blk14:
Is Factory reset mandatory when we upgrade from 17 to 18 ?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K9100ii:
No, it shouldn't be necessary. You should only need to format the system partition, install the 18.1 build, and install newer versions of any packages that are compatible with Android 11. I upgraded to 18.1 from 17.1 with encryption perfectly fine.

I highly suggest backing up all of your data before attempting to upgrade in case something goes wrong.