[UNOFFICIAL][ROM]BETA LineageOS 18.1 for Galaxy Tab A [SM-T550] June 12, 2022

Search This thread

magicmellon

New member
May 15, 2018
4
0
Hi there,

I am amazed to find an up-to-date linage ROM for my old tablet. Mad props @retiredtab for maintaining this - Thank you <3.

I was wondering if youd be able to tell me about OTG charging on this ROM. I have been looking for a kernel for my SM-T550 which has is Accessory charging adaptor enabled (Outlined here)

I have just had a look at the MSM8916 Git-library which you linked on page 1, but it doesnt appear to have a OTG folder in "drivers\usb\otg\msm_otg.c". Does that suggest this build has no OTG drivers at all?
 

retiredtab

Senior Member
Nov 16, 2017
1,114
677
I am amazed to find an up-to-date linage ROM for my old tablet. Mad props @retiredtab for maintaining this - Thank you <3.
The April 11 build has the April 5th security patches. It will be posted after I answer this.
I have just had a look at the MSM8916 Git-library which you linked on page 1, but it doesnt appear to have a OTG folder in "drivers\usb\otg\msm_otg.c". Does that suggest this build has no OTG drivers at all?
The file msm_otg.c doesn't exist at all in my kernel directory only the documentation for it. I checked another device that also uses msm8916 kernel code and that file doesn't exist either. So without that file, I'm going to say there's no support.

Bash:
$ find | grep msm_otg.*
./Documentation/usb/msm_otg.txt
 

retiredtab

Senior Member
Nov 16, 2017
1,114
677
New build called lineage-18.1-20220411-UNOFFICIAL-gt510wifi.zip. The sha256sum is

Code:
$ sha256sum lineage-18.1-20220411-UNOFFICIAL-gt510wifi.zip
b0063ab1f43b6775e39302ebdc5956fb8621ee4722f4b359dd458076a32f49c4  lineage-18.1-20220411-UNOFFICIAL-gt510wifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

18.1 continues to be my daily driver since March 2021.

April 11, 2022 release notes
1. April 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
2. Whatever LiineageOS changed since last January release (about 11,000 files had to be recompiled).
 

magicmellon

New member
May 15, 2018
4
0
The April 11 build has the April 5th security patches. It will be posted after I answer this.

The file msm_otg.c doesn't exist at all in my kernel directory only the documentation for it. I checked another device that also uses msm8916 kernel code and that file doesn't exist either. So without that file, I'm going to say there's no support.

Bash:
$ find | grep msm_otg.*
./Documentation/usb/msm_otg.txt
Thanks for the confirmation. Appreciate it :)
 

skills14

Member
Nov 13, 2014
8
1
@maserati2011
If it helps, I ran into the same issue that you originally had - but then went through it one more time and got it to work. The first time when it didn't work - I formatted first then wiped - instead of wiping everything (except my micro sd card) and then formatting. (I didn't know the order mattered, but apparently it does - thanks to @retiredtab for that clarification).

Once I saw the Widevine with L3 - I rebooted back into TWRP - and then just selected the Feb package and ran the installer without wiping or formatting. Then I wiped both caches and data, and rebooted.
All the packages were still installed, SELinux was back to enforcing, and Widevine still showed L3 and Netflix installed and ran without any issues.

Hope that helps.
This worked for me, thanks alot
 

retiredtab

Senior Member
Nov 16, 2017
1,114
677
New build called lineage-18.1-20220507-UNOFFICIAL-gt510wifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

18.1 continues to be my daily driver since March 2021.

May 7, 2022 release notes
1. May 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
2. Whatever LiineageOS changed since last April release (about 4,100 files had to be recompiled).
 
Sep 4, 2021
11
2
How does one get chrome to install via Aurora store?
These airline apps require chrome browser to play their ridiculous DRM and chrome-based doesn't appear to work (tried edge).
Tablet plays Netflix on its own - so its not the usual widevine issues.

When I click install after download, nothing happens. I suspect its related to not having any gaps apps, but didn't know.
Or has anyone gotten this to play any of the shows while flying american or united?
Thanks!

(running latest May 18.1 image on sm-t550)
 

joke19

Senior Member
Feb 23, 2012
1,324
203
Xiaomi Redmi Note 7
Xiaomi Mi Note 10
How does one get chrome to install via Aurora store?
These airline apps require chrome browser to play their ridiculous DRM and chrome-based doesn't appear to work (tried edge).
Tablet plays Netflix on its own - so its not the usual widevine issues.

When I click install after download, nothing happens. I suspect its related to not having any gaps apps, but didn't know.
Or has anyone gotten this to play any of the shows while flying american or united?
Thanks!
Test chromium
 
  • Like
Reactions: XDA_username00

retiredtab

Senior Member
Nov 16, 2017
1,114
677
How does one get chrome to install via Aurora store?
I don't use chrome, but I do use Brave which is based on the open source chromium and Brave adds privacy and ad blocking features.

Even if chrome installs using Aurora store (which I haven't tried or tested), chrome, itself might check for the presence of the underlying gapps framework. If that's missing, then chrome won't start.

You can check for yourself by viewing the adb logcat.

Bash:
# clear the log using little c
adb logcat -c
# start a new log and show the messages with color (big C)
adb logcat -C
# start chrome app
# look at messages, it might say something like "google play store required but not installed"

Aurora Store downloads the exact same apps from the actual Google play store, but doesn't come with the underlying gapps frameworks that some apps may require.
 
Sep 4, 2021
11
2
Yeah, I think the lack of gsf framework/gapps is what the issue is. I'd prefer not to use any chrome at all - but for whatever reason these airline apps have made it a requirement.
Interesting note: apparently Firefox 51 is supported, but nothing higher. *sigh

well, at this point all I can do is preload a bunch of different browsers and see if anything works. It's a shame there's no external site that can verify drm since the commercials and everything else plays just fine. It's when you are locked into non-internet local wifi mode on the plane that the error appears and to try and fix requires switching to a mobile hotspot with internet and then try to troubleshoot.
 
Sep 4, 2021
11
2
You might want to research microg.

https://microg.org/

edit: I have no plans to support or add signature spoofing to my builds. It's a potential headache that I don't want to be supporting.
I wouldn't even remotely suggest that, specifically because it could break other stuff. If I come across a solution, I'll share - but sometimes just knowing what won't work helps manage expectations.
 
Sep 4, 2021
11
2
Test chromium
That worked! The only adjustment I had to make was to use the browser to connect directly to the url instead of allowing the airline app to launch it. I did get a pop-up about not having the Google Play store something or other when I first launched - but that didn't affect it.

So to be specific - being able to play United Airlines content - was possible using the Bromite Chromium (armeabi-v7a) (direct link to 101.0.4951-69), setting it to the default browser, and navigating to http://unitedprivatescreening.com.

I suspect American will be similar and will update any issues the next time I fly with them.
 

chironfr

Senior Member
Feb 14, 2016
87
28
Chassieu
Thanks a lot. I've installed it on my T-550. It perfectly suits my needs (ebooks + press).
I've installed pico gapps because I need a paid app on the google playstore.
Everything runs smoothly, no bugs so far.

Thanks again! :)
 

retiredtab

Senior Member
Nov 16, 2017
1,114
677
New build called lineage-18.1-20220612-UNOFFICIAL-gt510wifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

June 12, 2022 release notes
1. June 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-06
2. Whatever LineageOS changed since last May release (about 9,000 files had to be recompiled).
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    New build called lineage-18.1-20220612-UNOFFICIAL-gt510wifi.zip

    NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

    June 12, 2022 release notes
    1. June 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-06
    2. Whatever LineageOS changed since last May release (about 9,000 files had to be recompiled).
  • 9
    PLEASE BEFORE YOU decide to try this rom, you MUST read all of post 1, 2, 3 and 4 (about 10 minute read). If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.

    I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.

    BACKUP YOUR DATA AND OLD rom BEFORE trying my rom.

    If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT use this rom. You must know how to use these tools to revert back to your old rom.

    If you are new to flashing custom roms, do NOT attempt this.

    If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.

    What works

    1. bluetooth
    2. wifi
    3. brightness
    4. external audio
    5. GPS
    6. audio through headphone jack
    7. audio over bluetooth
    8. selinux enforcing

    Thanks
    1. LineageOS team for source code.
    2. Pre alpha testers for the Samsung Tab A/E roms who provided valuable feedback: lpedia, Schaagi, katochwa, Henrick Grimler
    3. Huge thanks to Henrick Grimler https://github.com/Grimler91 for helping me reproduce a major bug in 18.1 which led me to find a solution. Henrick also helped fine tune some of the sepolicy as well.
    4. Sebastiano Barezzi https://github.com/SebaUbuntu for giving the msm8916 repo some 18.1 code updates in March 2021.
    5. Exynos5420 team for sharing it's knowledge in building roms.
    6. msm8916 team for their repos.
    7. aala27 for the device trees. He was nice enough to share his work so my build is based on his 17.1 with some minor changes.
    5
    FAQ - I spent hundreds of hours building this rom. It was frustrating process from Nov 2020 to March 2021 running into bug after bug. The least you can do is spend a few minutes reading everything before posting.

    Q1. Where are the source and kernel source files?
    A1. The kernel source files are at


    The device tree files are at


    The vendor tree files are at

    In addition, there is a repo diff file for device specific tweaks needed to work and a roomservice.xml (local manifest file) file so you can build this rom yourself.

    Q2. Is this BETA rom suitable as a daily driver?
    A2. It can be depending on your requirements. I can't test every app so you try it yourself to see if it's suitable. I've been using this rom myself since mid March 2021 with no major issues.

    Q3. What if my app, xyz, doesn't work?
    A3. I won't answer questions regarding why your app doesn't work. If your app, whatever it is, doesn't work, then go back to your old rom. It's difficult enough building and maintaining these roms. Remember, I'm an unpaid volunteer making a rom for free for your benefit.

    Q4. Your rom is laggy and buggy.
    A4. If you find the above, then go back to your old rom. There's only so much software can do on a 2015 budget level tablet. Remember a budget tablet will have the slower SoC/CPU and less DRAM than a top of the line model. Your tablet will also run slower when you use gapps (google apps). You can run a lot of software without using gapps. Research fdroid, newpipe, Aurora store etc.

    Q5. What TWRP should I use?
    A5. You MUST use TWRP 3.5.2_9-0. Get it at.


    Q6. Why should I use this rom?
    A6. You don't. If you don't like this rom, then don't use it. Yes, it's that simple.

    Q7. Will you offer monthly updates with security patches?
    A7. I will try to offer monthly security patches, but that all depends on if I continue to have high speed Internet in the future.

    Q8. Can you help me? I'm a newbie. Can you provide step by step instructions?
    A8. Do your own research. There are lots of tutorials, videos, etc on how to flash roms. Newbie questions must be posted in the Questions and Answers forum, not here.

    Q9. Can I report a bug with respect to the rom?
    A9. Yes, but you need to supply the following information. If you don't, I won't look at it.

    You must provide an adb logcat of the problem and tell me how to reproduce it. Note I will not be downloading any apps that require money or an userid/password. For example, if you have problems with Netflix, I cannot help you since I don't have a paid subscription. If you use some app that requires an userid/password, I cannot help you as I'm not willing to create another userid/password even if it's free.

    To get a logcat, open up a terminal window.
    Code:
    # clear the logcat first
    adb logcat -c
    # start logcat trace
    adb logcat > problem.txt
    # reproduce problem
    # wait until problem has occured, then stop trace by hitting ctrl-c

    Q10. Will you still build 17.1 for this device?
    A10. Yes, for now, but I will probably discontinue building 17.1 at the end of 2021. I will likely be trying to build 19.0 once it's released so I don't want to maintain 3 releases.

    Q11. Do I need to erase everything and format my data?
    A11. Yes, you MUST erase all the partitions (system, data, dalvik/art cache, cache) using TWRP and MUST format your data before installing 18.1 when you are coming from stock or an earlier version of LineageOS or from another custom rom. If you get stuck at the boot animation for more than 5 minutes, it's likely because you didn't follow the instructions I just wrote. Dirty flashes from stock, other custom roms or older LineageOS versions are not supported and not likely to work.

    Q12. What gapps should I use?
    A12. I don't use gapps anymore. I use Aurora Store. As of Nov 6, 2021, I no longer make recommendations on which gapps to use as your mileage may vary. It's reported that opengapps does no testing on their daily builds and some version results in bootloops, bitgapps may run out of disk space will installing apps and Mindthegapps as causing overall slowdown of the system.

    The only recommendation I can make is to use the SMALLEST version of gapps which is PICO or equivalent naming convention. DO NOT use anything other than PICO. That is, do not use nano, mini, stock, etc.

    If you are going to install gapps, flash the rom first, reboot into system/OS, reboot to recovery, flash gapps, reboot into system/OS. That is, do not flash/install the rom and gapps at the same time.

    Q13. I'm having problems with gapps, can you answer why it's not working?
    A13. I will not answer any questions regarding gapps. This thread is about the rom, not gapps and I don't use gapps so I cannot help you. Android does not depend on gapps in order to work.

    Q14. Why isn't my post answered?
    A14. It's probably because it's answered in the FAQ or not relevant to the rom. Again, I do not run Windows OS or use gapps. Questions already answered in the FAQ will be completely ignored.

    Q15. Can I turn off the on screen navigation keys?
    A15. To turn off on screen navigation, go to settings, system, advanced, gestures, system navigation, gesture navigation. It's enabled by default because I find it useful. If you don't like it, you only need to disable once and your preference will be remembered. If you want to invert the onscreen keys, goto settings, system, buttons and enable invert layout

    Q16. What speed up/optimization tips do you suggest?
    A16.

    1. Turn off animations. Go into developer settings, scroll down to the drawing section, and set window, transition and animator scale all to "off".
    2. If you don't have a google account, don't install gapps. Use Aurora Store to get your apps as you can get all the same apps from the play store using an anonymous login.
    3. Dont' run more than 2 apps at the same time. You can probably listen to music in the background and use a web browser at the same time, but don't expect great performance from a 2015 entry level tablet.
    4. Use a web browser like Brave that has built in adblock and privacy features.
    5. Use newpipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
    6. Look for apps that are open source, ad free and lightweight.

    Q17. Does this rom support Magisk?
    A17. I don't use Magisk myself so I don't know and Magisk is always being updated to fool Google's certification process. Others have reported Magisk as working, but I won't answer any questions regarding it.

    Q18. Will this rom ever become official?
    A18. Never. I don't want the responsibilities that come with being an official maintainer. In addition, I know my device trees, code organization and git commits will NOT meet LineageOS standards. Remember, I'm an unpaid volunteer doing this in my free time and sharing my work with you for free so you can get hundreds of hours of enjoyment from this tablet.

    Q19. What is the difference between this rom and others?
    A19. This rom tries to be pure LineageOS with little to no modifications. Other roms may have different UI, different bundled apps, etc. Use whatever meets your requirements.

    Q20. Will there be any major 18.1 code modifications in the future?
    A20. I don't anticipate any major modifications. There may be some slight tweaking to the sepolicy, small bug fixes and minor code cleanup, but all the hard work in getting the rom up and running and fixing all the major bugs have been done completed. This doesn't mean the code is perfect or well organized, but I won't be doing any major changes now that 18.1 is working. Any major changes will be done in 19.0.

    Q21. Why did you fork the device and vendor trees for 18.1?
    A21. The msm8916 repos seem geared towards phones and sometimes do not work or cause boot animation loops for tablets so I decided to fork their repos. In other words, what's deemed as msm8916-common code isn't common to all devices.

    In addition, since I'm building SM-T350, SM-T550, SM-P550 and SM-T560NU (all use the same msm8916 code), it seems easier to maintain all of them if I can control my own code repos and not worry if my changes affects the phones or not. I still have not figured out the best way to manage all my repos and it's a work in progress.

    Q22. Can you build a variant of this device? For example, a LTE or S-pen version.
    A22. If I don't physically have the device, I cannot and will not build it unless I can boot and test it myself. Even then, there's no guarantee that I can get those variant features working.

    Q23. Can I load this rom on a variant devivce like LTE or S-pen version?
    A23. The rom is built for the device explicitly listed. If you are an advanced user and understand TWRP, adb, odin, heimdall, you can try loading it on a LTE or S-pen variant by modifying the updater-script, but it may cause a bricked device, bootloops or non functionality of LTE/S-pen. You have been informed and warned!

    Q24. Will this run on the SM-T555?
    A24. No. Someone has tried and it will result in a bootloop.

    Q25. Why are you releasing a ROM for a tablet that you do not own?
    A25. I don't own the SM-T550, but have the SM-P550. I also build roms for the SM-T350 and SM-T560NU. All these platforms use the same msm8916 code base. As such, all my work from the SM-T350, SM-T560NU and SM-P550 could possibly benefit SM-T550 users. For one P550 owner, there are probably twenty T550 owners.

    The T550 rom does boot and run on my P550, but the x-axis is mapped backwards.

    Q26. Okay, I understand the consequences and that this is BETA rom and willing to take the risks outlined, now where can I find the rom?
    A26. Downloads are at

    5
    New build called lineage-18.1-20211211-UNOFFICIAL-gt510wifi.zip

    NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

    18.1 continues to be my daily driver since March 2021.

    Dec 11 release notes
    1. Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2021-12
    2. Whatever LiineageOS changed since last November release (about 11,000 files had to be recompiled).
    4
    New build called lineage-18.1-20210909-UNOFFICIAL-gt510wifi.zip

    NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

    18.1 continues to be my daily driver since March 2021.

    Sept 9 release notes
    1. Reverted the patch to https://github.com/retiredtab/andro...mmit/a32c7a0bed536281d20b7c1cf8d41c84a268cc80
    Removing systemUI from pinner services causes a 4 to 6 delay in bringing up the home screen. This is seen when loading or playing a game for about 20 minutes and then either hitting the recents or home button. By reverting this commit, pressing recents or home button brings up the systemUI right away.
    2. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/315661
    3. Whatever LiineageOS changed since last August release (about 7,000 files had to be recompiled).
    4
    That's fair enough. I did see the FAQ 18 section you quoted, but didn't really understand it.... The links you provided pretty much add the context behind this - and I get where you're coming from now.
    If you want monthly security patches, Google releases them on the 5th of every month. Then it takes a few days for LineageOS to merge these patches into their code. Then it takes a few more days to get them tested and verified before the official merge happens.

    So if you check on the 15th of every month, it's likely that I will have a 18.1 security patch made, tested and available for download. Sometimes it's earlier, sometimes it can be later. Alternatively, you can subscribe to this thread and eventually one of my posts will be announcing the Jan 5, 2022 security patch. Same goes for Feb 5, March 5, etc.

    I plan to provide monthly 18.1 security patches for all of 2022. I will likely make a decision sometime September or October 2022 if 18.1 security patches will continue in 2023. That all depends on if I can get 19.0 up and running and how well it works compared to 18.1. If 19.0 runs well, then I will likely discontinue with security patches for 18.1 in 2023. Then I would make monthly security patches for 19.0 for all of 2023.