LineageOS 17.1 for SM-T580 (gtaxlwifi)

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

 

[TALUAtXDA]

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

I'm not sure myself as I don't use any video conferencing apps.
Has anyone else tested any on a recent build?

 

[Chris_0147]

@TALUAtXDA I will trust your rom because it is the most complete

 

[Jamess27]

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

I use microsoft meet and zoom, they work fine

 

[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?

 

[LifelessDead]

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?

Yes, works fine on 5GHz. Just pick your correct 5GHz network from the wifi list, and "forget" the 2.4GHz one.

 

[bnwgraaf]

Yes, works fine on 5GHz. Just pick your correct 5GHz network from the wifi list, and "forget" the 2.4GHz one.

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

 

[TALUAtXDA]

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

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.

 

[bnwgraaf]

I have no idea why it doesn't use 5GHz on one network with both 2.4GHz and 5GHz.....

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!

 

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

 

[fs1023]

Hi, what open gapps file to use? Error installing arm64 android 9 stock with rom? Do I use android 8.1 instead?

 

[TALUAtXDA]

Hi, what open gapps file to use? Error installing arm64 android 9 stock with rom? Do I use android 8.1 instead?

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.

 

[fs1023]

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.

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.

 

[Chris_0147]

Deleted

 

[TALUAtXDA]

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.

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.

 

[fs1023]

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.

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.

 

[TALUAtXDA]

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.

 

[soaringowl2145]

Hmm... That's strange. The latest build was working fine for me, and I assume it is for (most) others as well, and I made few changes in the latest build compared from the previous build (basically as in the changelog, nothing more). I'm not sure what exactly you mean by "zip signature". The MD5 checksum (which I never put anywhere, but probably should) for the latest build is 2e90f6dbc4af4cea9cb9d578f5b8a6d5.

You're going to need to get a log from logcat using a working installation of ADB on a computer for me to try to look into your issue. To do this, ADB has to be enabled on boot and secure ADB needs to be disabled. First of all, download this file named "default.prop", which has changes to do that: https://drive.google.com/file/d/10Lrva4gZIP0IKNqQKrEQVz1D3t7sg4S8/ Boot your device into TWRP, connect it to your computer, mount the system partition, and push the new default.prop file to /system_root/ using ADB so that it replaces the existing default.prop file by running this in a shell/command prompt, assuming that the default.prop file is in the same directory as the one you're in (use "cd <path>" to change directories):

adb push default.prop /system_root/

You can also copy it to your internal storage and copy it to /system_root/ using TWRP's file manager, although you'll need to use ADB to get the log anyway.
Once you've done that, reboot. While it's bootlooping, run the following in a shell/command prompt to get a log from logcat:

adb logcat > logcat.txt

The log will be in the new file named "logcat.txt". You can replace that filename with whichever you prefer. Upload it in a new post.

By the way, by any chance, did you install or upgrade any packages in addition to upgrading to that build? Perhaps that's the cause of your bootlooping?

I've also made an entirely clean new build earlier today, which can be downloaded from here: https://drive.google.com/file/d/1JeXvc3NVQaUUksfvtpEgWeUd25DSmChx/
I've tested it myself, and it works fine here. You could try it before trying to get a log, although I'm not expecting it to not bootloop if that build did.

Same issue with the March build. When doing adb it says waiting for device and the logcat never works

 

[TALUAtXDA]

Same issue with the March build. When doing adb it says waiting for device and the logcat never works

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.

 

[soaringowl2145]

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 conpletely wrong (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.

When I put the file in a new folder named /system_root

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.

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?