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
-
There are no posts matching your filters.
-
4
I did have two mentions of google app packages, some custom opengapps packages and nikgapps. A while ago, I saw posts from someone related to issues with those packages, implying that the mentions were seen as recommendations, rather than just useful mentions in a specific context. All the while it seemed like I might've got partial blame for the issues, just with the mere mentions since I've been taken to having recommended packages.
Meanwhile, I don't use google apps and so can't support them, and google app package-related issues seem to be common.
So I simply gave up and removed the mentions. So IDK.3
Of course? I haven't disappeared.
Updated forked repos again.
In the future, use these commands to update forks from Lineage's repositories locally:
Git:cd frameworks/base git remote add lineage https://github.com/LineageOS/android_frameworks_base git fetch lineage lineage-19.1 git rebase lineage/lineage-19.1 cd frameworks/native git remote add lineage https://github.com/LineageOS/android_frameworks_native git fetch lineage lineage-19.1 git rebase lineage/lineage-19.1 cd packages/modules/Permission git remote add lineage https://github.com/LineageOS/android_packages_modules_Permission git fetch lineage lineage-19.1 git rebase lineage/lineage-19.1
Shouldn't be trying to make updated builds without pulling in all the updates while intending to get the latest security patches anyway.3As the questions "where can I find XYZ GApps" or "which GApps should I use" are popping up lately every other day, I tried to summarize and to gather options from this thread. If anyone has practical experience with additional options, please share here or send a PM - I will try to keep the post up to date.
Do I need GApps?
- Well, it depends ... consider also that you can run the tablet without GApps (freeing up resources) by using e. g. F-Droid (https://f-droid.org/) and accessing Google Play Store e. g. thru Aurora Store available thru F-Droid.
- As it depends on many variables, there can't be a clear statement for what you need GApps or not. Don't ask - try yourself!
- Credits to @netra3441 for the reminder.
- Remember, you need GApps for Android 12L (sometimes also referred to as Android SL; base of LineageOS 19(.1)) and ARM64.
- As stated in the OP, use as light as possible since the hardware is old and was never cutting edge!
- OpenGApps (https://opengapps.org/)
- NikGApps (https://nikgapps.com/)
- Files can be found here - you need to go for "releases" and "NikGapps-SL". "Core" is the lightest flavor - matching the "as light as possible" recommendation.
- My personal preference lately as they are light and well maintained.
- LiteGapps (https://litegapps.site/)
- No own experience and not mentioned in this thread but mentioned here and there in context of light GApps for older hardware.
- MindTheGapps (https://mindthegapps.com/)
- The only "officially" recommended (not supported!) GApps by LineageOS - linked on the official wiki page related to GApps.
- Apparently, there is an issue installing MindTheGapps via TWRP - multiple mentions can be found.
- As there is only one flavor incl. a few more apps, they don't match the "as light as possible" recommendation.
Disclaimer: This overview post is not implying support for any of the referenced GApps. Everything is on your own risk.3Well folks...
for me this discussion with *Gapps looks like with the flys, who dont want to move from the candy (I dont wanted to write "sh*t").
And to be honest: at the beginning of my "career" with LineageOS I also was a user, who thought, that *Gapps always must be.
But since a year now I run my to Samsung Galaxy S7 and my Samsung Galaxy Tablet SM-580 WITHOUT *Gapps, what means, that I do not have that Google mess (GSF, Pay and more) on my units.
Here at XDA there were good people who convinced me, that any *Gapps and so all that Google Systems Framework mess is really not neccessary.
Reason: over 90% of all the apps, and especially neary 99% of all that games in Google Play Store are not only just crap, they are also fullfilled with all kind of spyware, trackers and other mess, nobody needs. Google has lost the control of its play store, and the coders of bad apps, of viruses, spyware and other mess to rule there now...
I still use the Google Playstore to download just a few apps with Aurora, I got from there and use since years. But by rethinking I got convinced to use Fdroid store, where very good apps are, and none of them has trackers or other mess.
And, most important: mostly a direct contact with the coders of these apps allows me to pay them without fee for Google, and the coders like that.
So folks: forget *Gapps. Forget Google. Use your units without that mess. Its better, believe me!3
Regarding the lock screen rotation issue, it's essential for all of us to remember that when posting about problems, the more details we provide initially, the better the community can assist. In your original post, it would have been helpful for you to provide additional details for clarity. It otherwise might not be very reasonable to claim a misunderstanding on my end.
Now, let's address the orientation problem. This would appear to be an issue with LineageOS itself. Issues like this often require adjustments or modifications by developers. As a maintainer, creating changes to address the issue is outside my capabilities.
Regarding the desire for both hardware and on-screen buttons, I understand that some users may have unique preferences, but it's essential to acknowledge that the behavior of hardware and on-screen buttons is designed to be mutually exclusive. Enabling both simultaneously could lead to usability issues, and furthermore, creating changes to cater to such a specific request may be complex, and once again, outside my capabilities as a maintainer.
It's essential to highlight that after someone has been prompted the need to use English, with the aid of translation services if necessary, specifically highlighting it as a requirement according to forum rules only serves to emphasize the nature of the need as a requirement.
(Transparency note - Used an LLM generative text AI thing to generate the majority of these responses, lacking time and energy, with checking from me. But for anyone who knows, the really, really funnily cheesy/corporate-type tones should give it away.) -
70This 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
Some useful information for devices from China (SM-P583, SM-T585C, SM-P588C, and SM-T580 on the CHN CSC) - 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 of it should be easy to find.
As was the case with LineageOS 18.1, I've taken over maintaining 19.1 for gtaxlwifi from @followmsi, and my 19.1 builds continue on from his 19.1 builds that were intended for use by users. To update from his builds, my builds can simply be installed on top of an existing install from his builds without doing anything further (or "dirty flashed").
For those running 18.1 or 17.1, upgrading to 19.1 is possible through the procedure I've explained before here and here (except with 19.1/Android 12 and 18.1 rather than 18.1/Android 11 and 17.1 for that second post). 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.
For those who used WiFi-only variant builds on an LTE variant device, installation of a proper LTE variant build on top of an installation from a WiFi-only variant build is possible, except for a small issue you may encounter after doing so. See issue 3 in the "known workarounds and issues" section below for it.
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 20230824, all with security patch level 20230805
For gtaxlwifi: https://drive.google.com/file/d/1zY_6gJFjpcqbW2Upo8ZcFCpOIebcmlQh/
For gtaxllte: https://drive.google.com/file/d/1tlUO_x1MdIqUw_IMck6U6kU1WZEX6T7b/
For gtanotexlwifi: https://drive.google.com/file/d/1N34dR5QtcuPVbJQ88o2XIXhTdL1nR6Ju/
For gtanotexllte: https://drive.google.com/file/d/1AiP5P8855PWPtSCRybyDNJrQTP8dlNG-/
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.
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 fixes to various issues and other improvements, for useful information, and for 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 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.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.
