• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

OPEN BETA for 17.1 UNOFFICIAL LineageOS T550 rom

Search This thread
Hi, firstly thanks for this ROM, it's working well for me so far.

I did want to turn off the softkeys but for some reason all I've got under Gestures is Jump to Camera and Prevent Ringing.

When I first click on Gestures I can see some other menu items but they flick up and then disappear immediately. Don't know if it's something I've done? Also, my recents button doesn't work. If I remap it to open Google Assistant for example, it works. Set it back to Recent Apps and nothing! Maybe I just need to reinstall.

S'all good. I wiped System and reinstalled the ROM. Working now.
 

retiredtab

Senior Member
Nov 16, 2017
827
398
Well I have the February security patch update built, but have problems uploading it to sourceforge the last couple of days. Will try again over the next few days.

On the audio over bluetooth problem, I setup my linux computer with a blue tooth usb dongle and turned it into a bluetooth sink so it acts like a speaker (see instructions below) and I'm able to replicate the problem. However, I spent a few days trying to fix it and so far, I'm unable to. I will look at it again when/if I have time. I may not be able to fix though.

.
 

retiredtab

Senior Member
Nov 16, 2017
827
398
Audio over bluetooth is now fixed. The fix will be added to the March security patches. The problem was that it needs [email protected] hal/hidl and didn't work with [email protected] for whatever reason.

If you cannot wait until the March security patch for this fix, you can download this file called

lineage-17.1-20210221-UNOFFICIAL-gt510wifi-working-bt.zip

If you don't use audio over bluetooth, there's no need for you to download the above file.

https://sourceforge.net/projects/retiredtab/files/SM-T550/17.1/
 
Last edited:
  • Like
Reactions: cdza1971 and Adakin

cdza1971

Member
Sep 1, 2020
8
0
Audio over bluetooth is now fixed. The fix will be added to the March security patches. The problem was that it needs [email protected] hal/hidl and didn't work with [email protected] for whatever reason.

If you cannot wait until the March security patch for this fix, you can download this file called

lineage-17.1-20210221-UNOFFICIAL-gt510wifi-working-bt.zip

If you don't use audio over bluetooth, there's no need for you to download the above file.

https://sourceforge.net/projects/retiredtab/files/SM-T550/17.1/
Thank you @retiredtab for all your work on the T550 . The bluetoooth audio is working perfectly.
 

Schaagi

Member
Jun 30, 2015
27
2
Switzerland
New image called lineage-17.1-20210307-UNOFFICIAL-gt510wifi.zip

March 7, 2021 release notes
1. Mar 5 security patches.
2. Whatever LiineageOS changed since last February release.
3. audio over bluetooth fix incorporated. I had to use the [email protected] hal.
Thank you so much for your valuable work. Since today I use the tablet every day without any issues. (y)
Regards
Schaagi
 

retiredtab

Senior Member
Nov 16, 2017
827
398
Thank you so much for your valuable work. Since today I use the tablet every day without any issues. (y)
The T550 rom is #1 out of all my builds with 258 downloads since Jan 1 and the #2 is the T560NU with 247. So T550, which I don't even own, is used by a lot of people. USA #1 with 57 users and Germany #2 with 56. Users from 37 different countries use this rom.
 
  • Like
Reactions: cdza1971

dstars33

Senior Member
Jul 6, 2012
87
18
New Jersey
Does anyone else notice when they use the volume rocker, the tablet goes to sleep after a few seconds? A minor annoyance.
Edit: It also occurs when setting the volume using the volume panel in quick settings. It doesn't happen when setting the media volume using Settings.
 
Last edited:

retiredtab

Senior Member
Nov 16, 2017
827
398
Does anyone else notice when they use the volume rocker, the tablet goes to sleep after a few seconds?
What was your previous rom? Did you do a clean flash and format data?

If you can make this happen consistently, take a logcat.

Code:
# hookup microusb cable to tablet and usb to computer
# clear out logcat
adb logcat -c 
# now start logcat and send to file
adb logcat > volume.txt
# use volume rocker up, wait 10 seconds, rocker down, wait 10 seconds.
hit Ctrl-C to stop logcat
#upload here
 

dstars33

Senior Member
Jul 6, 2012
87
18
New Jersey
And what rom image are you running? I have released monthly patches so I have no idea which one you are running.
Your latest ROM and yes, a clean flash. I always update when you release update. I'll try to get you a
What was your previous rom? Did you do a clean flash and format data?

If you can make this happen consistently, take a logcat.

Code:
# hookup microusb cable to tablet and usb to computer
# clear out logcat
adb logcat -c
# now start logcat and send to file
adb logcat > volume.txt
# use volume rocker up, wait 10 seconds, rocker down, wait 10 seconds.
hit Ctrl-C to stop logcat
#upload here
I'm using 2/15. I am updating to latest now. I originally clean flashed your first one and dirty flash the updates. If the issue persists after the update, I will try to get you a logcat. Thanks.
 

dstars33

Senior Member
Jul 6, 2012
87
18
New Jersey
What was your previous rom? Did you do a clean flash and format data?

If you can make this happen consistently, take a logcat.

Code:
# hookup microusb cable to tablet and usb to computer
# clear out logcat
adb logcat -c
# now start logcat and send to file
adb logcat > volume.txt
# use volume rocker up, wait 10 seconds, rocker down, wait 10 seconds.
hit Ctrl-C to stop logcat
#upload here
Updated and still
Happening. Logcat attached.
Edit: I guess I can't attach a file.

--------- beginning of system
W/WindowManager( 682): removeWindowToken: Attempted to remove non-existing token: [email protected]
D/AndroidRuntime(21973): Shutting down VM
D/StatusBar(21827): disable<e i a s b h r c s > disable2<q i n >
W/Adreno-EGL(21827): <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
W/NotificationService( 682): Toast already killed. pkg=rs.pedjaapps.alogcatroot.app [email protected]
W/Adreno-EGL(21138): <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
I/RenderThread(21164): type=1400 audit(0.0:4922): avc: denied { ioctl } for path="/dev/kgsl-3d0" dev="tmpfs" ino=8359 ioctlcmd=93d scontext=u:r:untrusted_app:s0:c175,c256,c512,c768 tcontext=u:eek:bject_r:device:s0 tclass=chr_file permissive=1 app=com.topjohnwu.magisk
W/WindowManager( 682): removeWindowToken: Attempted to remove non-existing token: [email protected]
D/MediaSessionService( 682): Adjusting null by 0. flags=1, suggestedStream=-2147483648, preferSuggestedStream=false
I/vol.Events(21827): writeEvent active_stream_changed STREAM_MUSIC
I/vol.Events(21827): writeEvent show_dialog volume_changed keyguard=false
I/Sensors ( 682): AccelerometerSensor(0) setDelay : 20000000(ns)
I/Sensors ( 682): SensorBase::flush handle(0)
I/Authzen (12904): [DeviceStateSyncManager] The server is in sync with current state. Nothing to do
I/RenderThread(21867): type=1400 audit(0.0:4923): avc: denied { ioctl } for path="/dev/kgsl-3d0" dev="tmpfs" ino=8359 ioctlcmd=93d scontext=u:r:platform_app:s0:c512,c768 tcontext=u:eek:bject_r:device:s0 tclass=chr_file permissive=1 app=com.android.systemui
I/RenderThread(21867): type=1400 audit(0.0:4924): avc: denied { read write } for path="/dev/kgsl-3d0" dev="tmpfs" ino=8359 scontext=u:r:platform_app:s0:c512,c768 tcontext=u:eek:bject_r:device:s0 tclass=chr_file permissive=1 app=com.android.systemui
W/Adreno-EGL(21827): <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
W/NotificationService( 682): Toast already killed. pkg=com.topjohnwu.magisk [email protected]
I/vol.Events(21827): writeEvent touch_level_changed STREAM_MUSIC 22
I/vol.Events(21827): writeEvent touch_level_changed STREAM_MUSIC 25
I/vol.Events(21827): writeEvent touch_level_changed STREAM_MUSIC 28
I/vol.Events(21827): writeEvent level_changed STREAM_MUSIC 22
I/vol.Events(21827): writeEvent touch_level_changed STREAM_MUSIC 30
I/vol.Events(21827): writeEvent level_changed STREAM_MUSIC 25
I/vol.Events(21827): writeEvent level_changed STREAM_MUSIC 28
I/vol.Events(21827): writeEvent level_changed STREAM_MUSIC 25
I/vol.Events(21827): writeEvent level_changed STREAM_MUSIC 30
I/vol.Events(21827): writeEvent level_changed STREAM_MUSIC 28
I/vol.Events(21827): writeEvent level_changed STREAM_MUSIC 30
I/vol.Events(21827): writeEvent touch_level_done STREAM_MUSIC 30
V/SettingsProvider( 682): Notifying for 0: content://settings/system/volume_music_speaker
W/WindowManager( 682): removeWindowToken: Attempted to remove non-existing token: [email protected]
W/WindowManager( 682): Unable to start animation, surface is null or no children.
I/Sensors ( 682): AccelerometerSensor(0) setDelay : 66667000(ns)
W/WindowManager( 682): Unable to start animation, surface is null or no children.
W/AppOps ( 682): Noting op not finished: uid 10056 pkg com.google.android.gms code 79 time=1615439708038 duration=-1615427342494
I/TrustAgent( 1369): TAG: TrustAgent. [PhonePositionTracker] Received AR result: DetectedActivity [type=9, confidence=0] at 1615439726601 [CONTEXT service_id=84 ]
W/WindowManager( 682): removeWindowToken: Attempted to remove non-existing token: [email protected]
I/vol.Events(21827): writeEvent dismiss_dialog timeout
D/AndroidRuntime(21827): Shutting down VM
--------- beginning of crash
E/AndroidRuntime(21827): FATAL EXCEPTION: main
E/AndroidRuntime(21827): Process: com.android.systemui, PID: 21827
E/AndroidRuntime(21827): java.lang.NullPointerException: Attempt to read from field 'android.view.View com.android.systemui.volume.VolumeDialogImpl$VolumeRow.view' on a null object reference
E/AndroidRuntime(21827): at com.android.systemui.volume.VolumeDialogImpl$VolumeRow.access$500(VolumeDialogImpl.java:1662)
E/AndroidRuntime(21827): at com.android.systemui.volume.VolumeDialogImpl.setVisOrGone(VolumeDialogImpl.java:564)
E/AndroidRuntime(21827): at com.android.systemui.volume.VolumeDialogImpl.updateExpandedRows(VolumeDialogImpl.java:575)
E/AndroidRuntime(21827): at com.android.systemui.volume.VolumeDialogImpl.lambda$dismissH$14$VolumeDialogImpl(VolumeDialogImpl.java:971)
E/AndroidRuntime(21827): at com.android.systemui.volume.-$$Lambda$VolumeDialogImpl$WbM2lW0NZgKTAgzmFyEl97bfbio.run(Unknown Source:2)
E/AndroidRuntime(21827): at android.os.Handler.handleCallback(Handler.java:883)
E/AndroidRuntime(21827): at android.os.Handler.dispatchMessage(Handler.java:100)
E/AndroidRuntime(21827): at android.os.Looper.loop(Looper.java:214)
E/AndroidRuntime(21827): at android.app.ActivityThread.main(ActivityThread.java:7356)
E/AndroidRuntime(21827): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(21827): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
E/AndroidRuntime(21827): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)
W/RescueParty( 682): Noticed 2 events for UID 10109 in last 24 sec
W/ActivityManager( 682): Process com.android.systemui has crashed too many times: killing!
I/DropBoxManagerService( 682): add tag=system_app_crash isTagEnabled=true flags=0x2
I/Process (21827): Sending signal. PID: 21827 SIG: 9
W/BroadcastQueue( 682): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
W/BroadcastQueue( 682): Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
W/AS.AudioService( 682): SCO client died
I/StatusBarManagerService( 682): binder died for pkg=com.android.systemui
D/WifiExternalCallbackTracker( 682): Binder died [email protected]
D/ConnectivityService( 682): ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ LISTEN id=154, [] ], [email protected])
D/WifiExternalCallbackTracker( 682): Remove external callback on death 140075805
D/ConnectivityService( 682): ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ LISTEN id=152, [ Transports: WIFI Capabilities: NOT_VPN] ], [email protected])
I/WindowManager( 682): WIN DEATH: Window{80fbc66 u0 com.android.systemui.ImageWallpaper}
D/ConnectivityService( 682): ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ TRACK_DEFAULT id=153, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10109] ], [email protected])
D/NotificationListeners( 682): Removing active service ComponentInfo{com.android.systemui/com.android.systemui.statusbar.NotificationListener}
W/AS.AudioService( 682): Current remote volume controller died, unregistering
W/VolumeController( 682): Error calling dismiss
W/VolumeController( 682): android.os.DeadObjectException
W/VolumeController( 682): at android.os.BinderProxy.transactNative(Native Method)
W/VolumeController( 682): at android.os.BinderProxy.transact(BinderProxy.java:511)
W/VolumeController( 682): at android.media.IVolumeController$Stub$Proxy.dismiss(IVolumeController.java:260)
W/VolumeController( 682): at com.android.server.audio.AudioService$VolumeController.postDismiss(AudioService.java:6749)
W/VolumeController( 682): at com.android.server.audio.AudioService.setVolumeController(AudioService.java:6597)
W/VolumeController( 682): at com.android.server.audio.AudioService$4.binderDied(AudioService.java:6606)
W/VolumeController( 682): at android.os.BinderProxy.sendDeathNotice(BinderProxy.java:621)
D/ConnectivityService( 682): ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ LISTEN id=155, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 10109] ], [email protected])
D/WifiExternalCallbackTracker( 682): Binder died [email protected]
D/ConnectivityService( 682): releasing NetworkRequest [ TRACK_DEFAULT id=153, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10109] ] (release request)
I/ActivityManager( 682): Process com.android.systemui (pid 21827) has died: pers PERU
D/WifiExternalCallbackTracker( 682): Remove external callback on death 204722768
W/WallpaperManagerService( 682): Wallpaper service gone: ComponentInfo{com.android.systemui/com.android.systemui.ImageWallpaper}
W/WallpaperManagerService( 682): Wallpaper service gone: ComponentInfo{com.android.systemui/com.android.systemui.ImageWallpaper}
I/WindowManager( 682): WIN DEATH: Window{f28c33 u0 StatusBar}
 
Last edited:

steje

Senior Member
Dec 23, 2010
261
23
Niedersachsen
Hello,

my TM 550 was very slow so I search for a ROM an found this here.

Now, I rooted my Tab, flash recovery and your Rom.

Works perfect for the first try. Any chance to turn off the navigations buttons?

Thank you so much.

Greetings from Germany
Jens
 

retiredtab

Senior Member
Nov 16, 2017
827
398
Updated and still
Happening. Logcat attached.
Your logcat shows magisk installed. Since no one else has reported this and I have never seen it happen on my own tablets, I suggest you do a completely fresh install. Wipe everything and format data. Then, just install the rom with nothing else (no gapps, no magisk). Then test volume rocker and see if device pauses. If it doesn't, then it's one of your apps causing the problem.

If it does pause with just the rom, try another rom to see if it happens. From these 2 tests, you should be able to determine if you have a hardware problem or it's the rom.
 

dstars33

Senior Member
Jul 6, 2012
87
18
New Jersey
Your logcat shows magisk installed. Since no one else has reported this and I have never seen it happen on my own tablets, I suggest you do a completely fresh install. Wipe everything and format data. Then, just install the rom with nothing else (no gapps, no magisk). Then test volume rocker and see if device pauses. If it doesn't, then it's one of your apps causing the problem.

If it does pause with just the rom, try another rom to see if it happens. From these 2 tests, you should be able to determine if you have a hardware problem or it's the rom.
Did a fresh install (formatted system, data, cache). No Magisk installed. Immediately tried the volume rocker and same issue. It appears using the rocker or quick settings volume panel causes a system ui crash. Oh well. Thanks for looking into this. I can live with it. The rest of the ROM is great.
 
Last edited:
Mar 31, 2021
14
8
Dear @retiredtab,

thank you so much for your incredible work!
I read everything you wrote regarding the T555 and I am trying to create a T555 build on top of your work here.

Of course I tried simply using your builds, but the screen stays black and it freezes (as expected).
Using your repos and aala27's repos I managed to build a config that resulted in a buildable LineageOS that I could install and that shows the Lineage boot animation but crashes/reboots after a while.
I know that you do not provide support for this, I am trying to most humbly ask for a few pointers to where I might look.

- What is your current local_manifest/roomservice? I could not locate this in your Github and used one posted by aala27 in a different thread, but it might be "off".
- Did you extract the required proprietary files by hand from stock ROMs or is there an automated way? I have "SM-T555_1_20190103084053_we4a668guy_fac" with T555XXU1CQHA/T555XXU1CRG1 that I know works on my T555.
- The repo "vendor-samsung-gt5note10wifi" in your Github only contains a branch for Lineage 18.1, is that intentional?

Fyi, my forks for the GT510LTE (SM-T555) I currently maintain here: https://github.com/blizzard4591?tab=repositories

I am willing to put in some time and effort to make this work, but I just do not know enough to do it efficiently.
If you can spare the time for a few hints, I believe I can make some progress!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    New build called lineage-17.1-20210917-UNOFFICIAL-gt510wifi.zip

    Sept 17, 2021 release notes
    1. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/316083
    2. Whatever LiineageOS changed since last August release (about 49,500 files had to be recompiled).

    NOTE: 18.1 continues to be my daily driver. I will likely stop making 17.1 monthly builds in 2022. That is, Dec 5, 2021 security patches will likely be the last 17.1 build.
  • 12
    BEFORE YOU decide to try this rom, please read all of post 1 and 2.

    The UNOFFICIAL LineageOS 17.1 T550 ROM

    BACKUP YOUR DATA AND OLD ROM BEFORE trying my rom.

    Let me be clear, I have the SM-P550, NOT the SM-T550.

    So I built a SM-P550 rom which is almost the same as the SM-T550 except the "P" stands for Pen.

    I believe my P550 rom with minor modifications will work on the T550, but I have no T550 to test it on. I believe it will work because I have used virsys T550 rom on my P550 and it works, but the X-axis touch is inverted.

    So I built SM-P550 with code to fix the X-axis touch inverted problem and it's one of line code. If I leave that one line of code out, then the X-axis will be correct for the T550. I have tested my 17.1 T550 rom on my P550 and it works, but again with the X-axis inverted. Just remember I don't have a T550 to test it on so you may run into bootloops, stuck at boot animation, etc.

    If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT attempt this ROM. You must know how to use these tools to revert back to your old rom. I'm not a Windows user so do not expect any help from me. My main OS is Lubuntu 20.04 LTS and all my roms are built on this platform.

    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.


    Again, the T550 rom that I built does boot and function on my P550, but I have no T550 to verify.

    BACKUP YOUR DATA AND OLD ROM BEFORE trying my rom.

    The rom has the latest monthly 2021 security patches.

    What works

    1. bluetooth
    2. wifi
    3. brightness
    4. external audio
    5. GPS
    6. audio through headphone jack
    7. camera
    8. touchscreen X-axis works properly
    9. Google play store - use pico apps
    10. flip flap smart cover
    11. audio over bluetooth

    What doesn't work

    1. LineageOS FM Radio app does not work. The P550 and T550 don't have the LTE chipset for it to work.

    2. The stock Jelly browser crashes a lot. Use a different browser. There's lots of better options that are more stable and reliable than the built in Jelly browser.

    3. Home screen text may look fuzzy.

    Text on home screen looks funny/fuzzy. This only seems to affect the home screen and nowhere else. I have seen the same problem on the SM-T350, SM-T560NU, SM-P550 and Nexus 7 2013.

    Problem is with stock trebuchet launcher and/or its fonts. I tried rootless pixel launcher from fdroid as a quick and simple test and see no problems with home screen text. Rootless pixel uses a different font though. A future LineageOS update could resolve the problem?
    5
    @Schaagi, thanks for the feedback on the BETA image.

    I will likely make another January 2021 T550 BETA image once the January security patches are released and open it to everyone after I do some initial testing of my own on the P550. This is assuming there are no problems with the 2021 January security patches and all the changes that go along with it. More on this later.

    Just to give you an idea of my own build and test process as not everyone does the same for the roms they release. It's a long read, but something I will probably add to every FAQ in my rom builds in 2021 so people can understand and appreciate what it takes.

    1. I test and verify each of my posted builds for basic functionality such as wifi, GPS, external audio, deep sleep, etc. For each working build that I post publicly, I probably have 30 builds that failed and will never share. They fail because of stuck at boot animation, boot loops, or some major functionality that doesn't work. Usually these problems occur when moving from one major Android release to another like 9 to 10. And yes, I'm having problems building Android 11 despite my efforts for the last 3 months with stuck at boot animation and boot loops.

    Each build takes a minimum of 15 minutes if I'm lucky and sometimes a clean build takes around 10 hours. Most of the time, it's somewhere in between depending on what I need to change.

    2. After I get an image that functionally works, I use that build for a couple days to make sure there are no random reboots or crashes. However, while it functionally works, I cannot test stability and reliability.

    An example of stability is, I might use wifi for 2 hours with no problems, but someone else using wifi for 24x7 might run into memory leaks which causes the tablet to lockup or reboot.

    An example of reliability is, I might use GPS once in my car for 20 minutes with no problems, but a food delivery person might use GPS 20 time a day and GPS might fail on the 21st time.

    Stability and reliability are virtually impossible for me to test. This is where the BETA testers can help. Even then, my builds will never be bug free when you consider the scope and scale as I write below.

    3. Monthly security builds include refreshing over 1,500 repositories, 70,000 files and probably over 1 million lines of code. Most of the time, the monthly build goes well and before I post a public image, I test each build for the same basic functionality. Again, I can't test stability and reliability.

    For the P550, I was only able to make 2 public posted 16.0 builds because something changed in one of the 1,500 repositories, 70,000 files and probably over 1 million lines of code that caused the build to not boot properly. I tried troubleshooting for several weeks, but I gave up and luckily found another source where I can get a working 16.0 and 17.1 P550 build. So I spent a few weeks really testing my P550 before I felt comfortable to even begin asking for T550 BETA testers. For the P550 build, I probably made over 100+ failed builds.

    Obviously, I can't test features that I never use or have access to. And there will always be someone who is going to be unhappy no matter what so that's why in all my FAQs I state that if you are unhappy with this rom, go back to the old one. Or they can build their own version as all the code I use is open source and all my fixes are documented, open source and free for everyone to use.
    4
    FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.

    Q1) Why are you releasing a ROM for a tablet that you do not own?
    A1) 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.

    Q2) What if my app, xyz, doesn't work?
    A2) 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, not mine as I don't even have the T550.

    Q3) Your rom is laggy and buggy.
    A3) 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 newpipe, microg, youtube vanced, aurora store etc.

    Q4) What TWRP should I use?
    A4) Use 3.4.0.0. Get it at


    Q5) Why should I use this rom?
    A5) You don't. I only offer it because I have built the SM-P550 and it was an easy change to make a SM-T550 rom. If you don't like this rom, then don't use it. Yes, it's that simple.

    Q6) Can you build SM-T555 (LTE) or a crDroid version of the SM-T550?
    A6) No. All the source code is open source and my changes are in the repo diff file. You can use these two with the roomservice.xml to build your own rom.

    Q7) Will you offer monthly updates with security patches?
    A7) That all depends on if I continue to have high speed Internet and on the reaction of the posts in this thread. If people are going to complain, then I have NO incentive to make an update. Remember, I don't have the T550 so I get zero benefit from making this rom for myself.

    Q8) Can you help me? I'm a newbie. Can you provide step by step instructions?
    A8) There are lots of tutorials, videos, etc on how to flash roms. Do your own research.

    Q9) Can I report a bug with respect to the rom?
    A9) Yes, but you need to supply a) how to recreate it b) a logcat c) a github commit showing how it was fixed. Even then, if I don't have the means to recreate it, I won't be working on it.

    Q10) Can I build this rom? Where are the source and kernel source files?
    A10) Yes. The kernel source files are at



    Q11) 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?
    A11) Downloads are at

    4
    New January 2021 build at


    Release notes for Jan 15, 2021
    1. Jan 5 security patches.
    2. Whatever LineageOS changed since last Dec 2020 update.
    4
    New build called lineage-17.1-20210215-UNOFFICIAL-gt510wifi.zip. It's at


    Feb 15, 2021 release notes.
    1. Feb 5 security patches
    2. Whatever LiineageOS changed since last January release.