Update without issues (not using GApps, Magisk or alike).
Also here no issues.
Thank you!
LineageOS 19.1(+) for SM-T580 (gtaxlwifi), SM-T585 (gtaxllte), SM-P580 (gtanotexlwifi), and SM-P585* (gtanotexllte)
- Thread starter K9100ii
- Start date
Thank you!
I tested it on 7th revision tablet and TWRP Recovery is works good and we have touchscreen works
but in Lineage OS 19.1 is not booted
It still on lineage os logo loading but no boots
(adb devices) cannot read this tablet on lineage OS booting
so I take a logs from twrp recovery again and I take logs or last_kmsg and pstore folder from twrp file manager in ROM.zip I send it for you
Thanks so much for the unofficial twrp builds and lineage os 19.1 and have a good luck for you
🫡Nevertheless, thank you very much
!!!I just installed 20230603 LTE, works as expected ;-).
Hmm, okay, the pstore log is just good enough.I tested it on 7th revision tablet and TWRP Recovery is works good and we have touchscreen works
but in Lineage OS 19.1 is not booted
It still on lineage os logo loading but no boots
(adb devices) cannot read this tablet on lineage OS booting
so I take a logs from twrp recovery again and I take logs or last_kmsg and pstore folder from twrp file manager in ROM.zip I send it for you
Thanks so much for the unofficial twrp builds and lineage os 19.1 and have a good luck for you
Attached is a new boot image to try. Should definitely boot with it.
That's excellent.Hey that's works now and Lineage OS 19.1 was booted
Thanks soooooo much bro
Does audio work fine?
That would mean the light sensor doesn't work. Does changing the orientation work (meaning the accelerometer works)?
Please get a log from logcat straight after booting.
Now I have a bug with headphone and speakers is working together
so wait I will take logcat from matlog app and I will send it to you
Hmm, weird. I specifically made changes to prevent such a problem, and I don't seem to have made any mistakes. Tricky.
I'll leave this for later when I have time.
When I do get time, I'll want you to get the output from a small program called "tinymix" while headphones are plugged in.
(Also, by the way, just to make sure, that's completely normal with ringtones, and alarms (at least), so it's only a problem if you're trying to play media audio and not just testing ringtones and alarms.)
No information there for sensors. Log taken too late. Specifically need a log as soon as possible after booting, errors are only logged during boot as the sensors HAL starts up.
I take that the accelerometer works fine.
Also, try to keep as much as possible in one message, otherwise it looks a little spammy.
I may soon get some option for donations for those who'd like to donate.
But before that, does anyone happen to know of a decent accessible alternative to PayPal for donations?
I'm presuming not really, so I'm asking just in case.
I don't like PayPal for its business practices, so I'd prefer not to use it. Could still use it if there isn't really any other decent option, though not great.
Needing more RAM now; The initial stages of LineageOS 20 builds consume all my current 16GB and ZRAM set to a large size, and I'm even often close to running out during 12L builds while also doing other tasks, since upgrading to a much higher thread count CPU. So that's where donations would first go.
That's a part of why I'm hesitant to start with LineageOS 20, apart from a lack of time and whatnot.
I have to resort to a console to build 20 (for my newer main tablet, notably) and not go out-of-memory, no GUI, very uncomfortable.
But before that, does anyone happen to know of a decent accessible alternative to PayPal for donations?
I'm presuming not really, so I'm asking just in case.
I don't like PayPal for its business practices, so I'd prefer not to use it. Could still use it if there isn't really any other decent option, though not great.
Needing more RAM now; The initial stages of LineageOS 20 builds consume all my current 16GB and ZRAM set to a large size, and I'm even often close to running out during 12L builds while also doing other tasks, since upgrading to a much higher thread count CPU. So that's where donations would first go.
That's a part of why I'm hesitant to start with LineageOS 20, apart from a lack of time and whatnot.
I have to resort to a console to build 20 (for my newer main tablet, notably) and not go out-of-memory, no GUI, very uncomfortable.
Last edited:
oh sorry
now I take logcat again but from PC adb logs so take look at it and tell me is that helps you to find this bugs or no
that's another logcat I hope it helped you to find a bugs of sensors
and I take a screenshot of Device Info HW app sensor test
and I take a screenshot of Device Info HW app sensor test
in games like brawl stars and PUBG mobile there is no sound
I don't know why but check logcats if you found this bug
I don't know why but check logcats if you found this bug
Similar threads
Top Liked Posts
-
1
I also tried that option at one point, and it still gave me the same problems. Anyway, thank you very much for your help. -
9I believe I've found, and have a fix for, the bug that causes random reboots with my LineageOS 20.0 builds.
I'm now testing, with my T580 playing a video on a loop as I type this, and will publish my fix later.
In short, the bug was a pretty bad one in our HWC1 sources due to an oversight by someone at Samsung. I imported those HWC1 sources, alongside other legacy stuff, from older Android 10 BSP sources to newer BSP sources intended for Android 13, which are in use for my 20.0 builds. In those same Android 13 sources, there are other huge external changes related to OMX hardware codecs. The huge HWC1 bug only became massively visible because of those huge OMX changes.
After I've tested and published my fix, I'll release new 20.0 builds hopefully within the next two days (if not today).
I will also apply the bug fix for my 19.1 builds - While the bug wasn't visible there, it should still improve stability in extreme usage. Technically also, there should be slightly better efficiency from my fix (whatever it could mean in the real world).4
Let's not get ahead of ourselves - Me suggesting that there might be performance issues is based on actual observations from different, newer lower end Exynos devices, where 20.0 was also fine (and yes, it is smoother on these devices indeed) but 21.0 turned out to be worse.
We cannot project results on better, more performant devices, like the S7's, to these much lower end devices (which also came out as low-to-mid-range devices at the time of the S7's). It could be that Google managed to somehow make it all perform better and look smoother at the cost of using more hardware resources, or something.
It is most wise to see that, on similar devices with environments more alike, there were issues, and there could be issues to an extent on these devices.
If it will actually be fine, with no or a small hit, nice, but it doesn't mean there's no good in speculating there could be some performance shaved off, based again on real observations, and that it remains to be seen by myself.
It's simply safer and better to be more careful with expectations.
Extras:
One set of devices that apparently had issues were Exynos 7904 devices. Apparently also, the performance issues went away after an upgrade of HWC2 sources. If there are issues here, we're stuck, since we're stranded with the same old HWC1 implementation, and might not have enough HW resources to bruteforce through slowness. But again, it's to be seen.
Meanwhile, I do know of some small HWC issue, where we've got 4 HWC layers but weirdly only 1 or 2 layers are typically used at any time. As far as I can tell, Android 14 makes more use of HWC layers, and depends more on the HWC implementation working properly - That could all make things a little worse off here.
I have no idea of the "many bugs" you speak of. I consider that, on most devices, 19.1 is "production ready".
I have no idea also about those WiFI crashes, unless there was some ultra weird Google apps issue or other modification messing with the system overall that isn't present anymore.
All I know is that there's an issue with the WiFi driver, independent from whichever version of Android, where, rarely, WiFi cannot be enabled on a first try. That's due to strange MMC-related errors, that appear in kernel logs. I've had it extremely rarely on 19.1, and also before on LineageOS 18.1.
No, and I wouldn't support any such kernels anyway.
The CPU is already safely overclocked from 1.586GHz stock to 1.69GHz. No overclock of something like a further 100MHz (as could only truly be feasible) could improve performance in any noticeable way.
Either, there actually are more ways you can lighten up your system (though I don't have suggestions, not knowing anything about your setup), or you've got a lot of intolerance for any slowness that shows up at all, which is normal if you're too used to other faster devices.
Either way though, we can only work within hardware limitations, and I think I've done my best.2
Yeah, indeed. I just left a video playing on a loop on my T580 and I got a soft reboot after a while. Though it looks to be stuck on the boot animation indefinitely, no signs of continuing at all.
Not sure at the moment. Might take me some time to figure it out.2
Yeah, exactly, because the very implementation of that charging control feature is as such, as I described. Of course it started when it was added and enabled.
I have no plans to disable it. It's useful and I'm glad personally to have no need for any external app anymore. It's also good for those without root access.
Mind you, I was using the same app you've mentioned, and there's a big advantage with Lineage's feature - It doesn't completely keep your device active without going to deep sleep, and cause battery drain before charging again, after it stops charging to monitor if the battery level drops below the lower boundary. That app did that, and the only way to avoid too much battery drain and cycling it between a few % over and over was to pick up on when it stops charging, disable it from its notification, and disconnect the charger.
You'd also have the same problem on any other device with Lineage installed and it enabled (which are quite a lot now). In any case, you should question if you have any real use for an external app. -
97This is LineageOS 19.1, which is based on Android 12L, for variants of the Samsung Galaxy Tab A 10.1" (2016), which have models and codenames as follows:
- SM-T580, with codename gtaxlwifi
- SM-T585, with codename gtaxllte, along with SM-T585N0, SM-T585C, and SM-T587 (not SM-T587P)
- SM-P580, with codename gtanotexlwifi, along with SM-P583
- SM-P585, with codename gtanotexllte, along with SM-P585M, SM-P585Y, SM-P585N0, and SM-P588C
For LineageOS 20.0 - Go here
Some useful information only for devices from China (Never any others!) (SM-P583, SM-T585C, SM-P588C, and SM-T580 on the CHN CSC code for China) - For unlocking the bootloader before installation, an app, "CROM Service", would need to be opened and the prompt from it accepted so that it can be unlocked, after enabling the "OEM unlock" setting in developer options. It should be available from the Galaxy Store, although I can't be 100% sure about it. In any case, an APK for it should be easy to find.
Also, for those running 18.1 or 17.1, upgrading to 19.1 is possible through the procedure I've explained before here and here. Mentioned Android/Lineage versions are different, but the steps still apply. I highly suggest backing up any important data before trying to upgrade. In the unlikely case the upgrade fails, and it doesn't boot, data would need to be formatted.
LineageOS 19.1/Android 12 usability fixes
For those wanting to disable the widely disliked taskbar (the grey bar at the bottom with the 3 navigation buttons and shortcuts for apps docked at the launcher): Instructions for doing so are in the first section of my post here.
For enabling lockscreen rotation: Instructions for doing so are in my post here.
For those needing Google apps: Do not use heavy Google apps packages, as otherwise, you WILL have severe performance issues. Instead, use the most minimal variant of your chosen package (core, pico...). Also, while mentioning that, make sure the package is 64-bit ARM (ARM64) and specifically, and only, for Android 12L.
You may look for Google app packages that others have had success using by searching the thread. Also worth considering is microG, which - if you can use and don't have anything depending strictly on having Google's own play services - will allow you to have additional resources (RAM mainly) that would otherwise be taken up by Google play services.
Build downloads - From 20240318, all with security patch level 20240305
For gtaxlwifi: https://drive.google.com/file/d/1-EDLBoeKl9UTx1ogcMl2QXD19d9KXItw
For gtaxllte: https://drive.google.com/file/d/1qQleL4pPhQKKYPoQs-XDIm_mfP3M91m-
For gtanotexlwifi: https://drive.google.com/file/d/16mVkIU4qWFO5DoqfehzwbCaRcL8AY7hD
For gtanotexllte: https://drive.google.com/file/d/1T13orMDGEsb_QKo9fGy653jWEuAzgUZL
Recoveries to use
Use my unofficial TWRP builds:
For gtaxlwifi: Image here, tar for Odin for AP slot is here.
For gtaxllte: Image here, tar for Odin here.
For gtanotexlwifi: Image here, tar for Odin here.
For gtanotexllte: Image here, tar for Odin here.
Official TWRP builds also work. Lineage recovery images within builds as "recovery.img" do work as well, but only for installing packages from a micro SD card.
Note that any other recoveries are completely unsupported and not recommended whatsoever.
Folders for builds
Along with current builds, these contain text files with SHA256 checksums for builds, and folders containing few previous builds.
For gtaxlwifi: https://drive.google.com/drive/folders/1S3NRiTP2jr9gRtSMKoKoaoMu75g_FJM4
For gtaxllte: https://drive.google.com/drive/folders/1ZFkGkVkIohsNFDi0jNF2-Yhz7Sbg5GT4
For gtanotexlwifi: https://drive.google.com/drive/folders/11pcp9NZf0ovelvT7oxfhoem6-utpSao8
For gtanotexllte: https://drive.google.com/drive/folders/1AICJ1UcnZ5a-slcgd-iGQ9mpk9J8Evmd
Changelogs
Known issues and workarounds/fixes (if any)
Sources
A manifest containing all of the necessary repositories to make builds for all of the variants is in the repository here on branch lineage-19.1.
Thanks to:
- @Valera1978 - for all of the previous work for the T580 and T585 long ago.
- @followmsi - for previously working with me on much of this stuff.
- Anyone who has previously tested anything new I've put up for testing, reported results, and provided information needed for me to get it working if it was necessary.
- The Lineage team - for the Android distribution itself.
- ...and everyone else who has worked on anything that is in use.
27New builds for 20230419
Downloads:
For gtaxlwifi: https://drive.google.com/file/d/1HYynOu6aGNBjYQ4Xa2PgV3bfFV_MNkfX/
For gtaxllte: https://drive.google.com/file/d/1KgsUF_S2mUKAz7_vlHc8-EriN0MeGIlT/
For gtanotexlwifi: https://drive.google.com/file/d/1i-Ixj9H0CXqFOmgL4pArds2c2DtliDEI/
For gtanotexllte: https://drive.google.com/file/d/1_JC0PrPNPWSjzuAbZHPYwBfQwNmm_G19/
Changelog:
- Latest changes from LineageOS, including the 20230405 Android security updates.
- Linaro's new SLSI BSP (Board Support Package, containing sources for HWC and some other stuff) sources are now used - Much more up-to-date than the previously used sources, and there's possibly a small improvement in performance.
- The OMX hardware video decoder and encoder libs are now built from the new Linaro BSP sources - With that, playback of HEVC videos is fixed in Chrome and other Chromium-based browsers.
- Some updates from the 4.14 Android common kernel as of March have been applied to the kernel.
- The wireguard kernel module has been added back - I silently removed it in the previous builds since it was unusable due to a now fixed device lockup bug that caused almost total unresponsiveness after enabling a wireguard VPN.
Anyway, some nice improvements in these builds.
The kernel updates are behind by a month due to... yep, a lack of time and other previously mentioned reasons. As always, I'll try getting them in at some point later. I'm really hoping these don't become unsustainable, keeping up and trying to defy that the 3.18 kernel is no longer maintained upstream since a really long while is certainly becoming more difficult.
In any case, enjoy.23Since I haven't posted anything for weeks now, I thought I'd give an update.
With me being yet more busy, and things constantly changing, and health issues on top (though don't worry about me), I haven't had much time to work on this stuff much.
Within my sources, I've fixed a bug, and applied kernel updates, but haven't had any real opportunities to release any new builds. I should be able to get around to getting new builds out in the next week or so.
I don't really have time to reply to much of anything at the moment, so if there is anything to reply to, I'll be leaving replies for later.20New builds for 20230720
Downloads:
For gtaxlwifi: https://drive.google.com/file/d/1lrTWHdZc8N3_QU5z9unqzdf8vwHfTs0r/
For gtaxllte: https://drive.google.com/file/d/1vI87QfvD4SiYZILrscebKzakM_eYbYlM/
For gtanotexlwifi: https://drive.google.com/file/d/19qlw6psNakFs2CQOXJvGwT1yrNhB9Vg7/
For gtanotexllte: https://drive.google.com/file/d/1usokOmctg3-OrXLjQvzhDJLwOaqXW_3f/
Changelog:
- Latest changes from LineageOS, including the 20230705 Android security updates.
- Call audio over Bluetooth has been fixed.
- On tablets with different models for different regions, the correct model number should now be set and displayed in "About tablet" in settings.
- [LTE variants only] RIL blobs have been updated from Samsung's A305GUBU8CWE3 firmware.
- Booting and sensors issues fixed for revision 7 gtaxllte devices (exclusive to 2020 students in Egypt) - Audio issues remain.
- Many updates from the 4.14 Android common kernel, up to v4.14.320, and a few other small updates, have been applied to the kernel.
Since the correct model numbers on devices with different ones for different regions should now be set, in case that doesn't happen for anyone, do report that.
Enjoy.20New builds for 20221127
Downloads:
For SM-T580/gtaxlwifi: https://drive.google.com/file/d/1jd9kC8SoJH3Jba2YT_7K3qEB7QG27MMR/
For SM-P580/gtanotexlwifi: https://drive.google.com/file/d/1V_lE-ehNIvD2q-B6bbz119pjwFq92fOk/
Changelog:
- Latest changes from LineageOS, including the 20221105 Android security updates.
As for LineageOS 20.0, I've still yet to get around to working on it.
While it certainly is possible, sadly, there most likely won't ever be any possibilities for getting network traffic monitoring (used specifically for data usage statistics, network download/upload speed monitoring...) working under Android 13. (For 12.1, support for the old, non-eBPF method for it was removed, however, we have changes to revert the removal and bring it back since our old 3.18 kernel only supports it and doesn't support eBPF. It certainly seems like we won't have changes to bring it back on 13, and unfortunately, it doesn't look like there will ever be eBPF backports for 3.18.)
Nevertheless, for the meantime, enjoy.
