Database Develop

[ROM/A1/Recovery][Wifi+3G+TMobile][4.4.4/2.8][Oct 27]Omni Based Rom and TWRP

Summarized Standard Disclaimer: use at your own risk. I use it at mine.
*Full wipe recommended if coming from another kitkat rom*
MAKE SURE TO HAVE A BROWSER APK. THERE IS NO MORE STOCK BROWSER. For firefox see below.
My personal build "Diamond Rom 4.4" is based on omnirom with the following additions:
CM Calculator (the newly redone one they're proud of)
CM File Manager
CM Wallpapers
Bash shell
Nano text editor
Powertop
Koush's full featured open source superuser (and it's INTEGRATED into settings :cyclops: )
Carbon rom blue balls wallpaper
Cyanogenmod port of 2 column settings adapted to Omni rom.
Omni floating window
I've added a few of my personal touches which include
Batter circle color changing: green 100%-51% yellow 50%-16% red 15%-0% This was my favorite I9000M framework-res mod that I've missed since switching to CM7.2 way back.
Killed lock screen music full screen (personal privacy thing when riding public transportation)
Disable android external storage management: messes with ext4 formatted hard drives or multi partitioned hard drives. Use the unix style mount command
Disable hardware keyboard on boot: disabled but not removed. You'll have to manually turn it on
Removed camera sounds
Disable SELinux at the kernel level. It's even disabled on my laptop/desktop at the kernel because it seems like it's more trouble than it's worth.
Put the dalvik cache in the cache partition. Don't waste the data partition for it. :cyclops:
And of course, comes bundled with my A1 kernel :cyclops:
Every thing I've tested: camera, youtube hd, sound, gps, usb otg(use manual mount command) etc work.
*Instructions*
First time flashing omni:
-Read second post FAQ and other important information.
-Flash TWRP (you can flash twrp over cwm from cwm if you're in that situation)
-Reboot into new recovery
-Make recovery backup (optional)
-Run Titanium Backup (highly recommended)
-Full wipe
-Format system partition
-Install ROM
-Install gapps
-Reboot :cyclops:
Subsequent flashes:
-Install ROM
Downloads
Mediafire Wifi download folder with md5sum file
Mediafire 3G download folder with md5sum file
Mediafire TMobile download folder with md5sum file
*Authorization to download is just a captcha. Simply enter the text in the picture or name the item being advertised in the picture.* Mediafire sure beats sh***y sites like uploaded.net or rapidgator
A1 Kernel (as its own download)
V1.9.2: Security fix made aware by cyanogenmod, specifically this. The commit message on my github has a copy and paste mistake. It should list both of those security flaws as patched instead of the same one twice. Oops :cyclops: Security fix comes with ALL roms June 28 and onwards.
3G/Wifi 6ff199d6c9037d222a70ec0c561c8028
TMobile a675fd353ad3ad7dbf8e6bf2109fa360
TWRP Recovery
2.7.1.0 Wifi 6c995325e749e7561893e398847b09a0
2.7.1.0 3G 8fa04be69d0faf3d9a134e829ddff680
2.7.1.0 Wifi July 8 a8d12c13aac7430a319369069d814e72
2.7.1.0 3G July 8 dc1c50622c29c621f29b95f4c53734ea
2.7.1.0 Wifi August 11 b2c21e8fd58dc38a9c8b7669031b84b1
2.7.1.0 3G August 11 9f48defe78391e63a9053cbd281f738f
2.7.1.0 TMobile August 11 87fb29c803a2e3a56d98a1475c5fce8f
2.8.0.0 Wifi cfdac70d0ccac34cf220887eab72f8b0
2.8.0.0 3G d7918eb397f54c484e04a6d5cb07945c
2.8.0.0 TMobile aaf7c6d2455ca32178ec846f5186c774
Newer versions of firefox explicitly disable flash on tegra2. Use my firefox mod which is just normal firefox with a hacked tegra2 blacklisting mechanism. Don't use the old firefox apk. It has unpatched security holes.
Changelog: omnirom gerrit
Sources: https://github.com/AAccount?tab=repositories Has my device trees as well as all the omni repos I forked with my additions.
Credits:
Kasper_h: helping to make 4.4 possible
pershoot: original device tree from CM10.1
Omni team: providing great starter rom and keeping it TF101 compatible
fred6681: original gapps package. I just removed the 4.4.2 check
Cyanogenmod team: rom extras like calculator, superuser, to fill in Omni's missing holes and 2 panel settings template.
XDA:DevDB Information
Omnirom+ 4.4 for Galaxy Tab 10.1, ROM for the Samsung Galaxy Tab 10.1
Contributors
AAccount
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.1.x
Based On: Omni
Version Information
Status: Stable
Created 2014-10-12
Last Updated 2014-10-11

Known Issues:
Wifi signal indicator and speed indicator don't show up
No list of 3G APN. Write down your settings first
Bluetooth audio issues
Recovery adb doesn't start automatically. In recovery, go to Advanced --> ADB Sideload and start it. You can then cancel it if you don't want to use that. It just starts the recovery adb and will continue to run until you reboot. fixed thanks to twa_priv
Use another recovery for TMobile. Apparently the twrps I make can't boot on TMobile hardware even though it boots on my Wifi only.
FAQ
How do I get multi window: Settings-->(second) More --> App circle bar (check box) && --> Included apps (choose what you want available in multi window)
Yes you can flash TWRP over CWM
Random flickering: Try Settings-->Developer options -->Disable HW Overlays.
Can't install a very large quantity of apps: fix
Can't mount ext4 media: kill the e2fsck process assuming you safely removed the media before sticking into the tablet.
(Below this is optional)
(Android device manager does have legitimate uses. However, please read and consider the following paranoid but realistic fantasy:)
Completely disable android device manager: By only going to Settings->Security->Device administrators and un checking "Android Device Manager" this doesn't completely remove the ability for google to send in commands to your device. Go to the google play store through a web browser, choose android device manager, and try "ringing" your device. To my horror, my tablet started to ring as if it got a phone call. I don't find it acceptable that gapps gives google a way to setup a remote command and control operation. In any other operating system this is considered a back door or virus.
To close this back door install Xprivacy. Enable system apps to be modified. Look for the entry (should be highlghted in red to indicate a system app) "Google Account Manager, Google Backup Transport... (lots of items here) ...Google Services Framework". Check mark Notifications and open its menu. Check mark the items in red. These are cloud to device (c2d) permissions which do exactly what you think. While not necessary, disable identification too for good measure. This disabled the ring feature on my tablet which means android device manager should no longer be able to send in commands. I don't have the guts to try the device wipe feature but it should work too. Do not disable location otherwise google maps won't be able to find you which means no gps car navigation.
See this post about building from source. I use a different, simpler trick for prebuilt chromium binaries. Fear not, they are source built but only when there are real source changes. They're just recycled in between to save 90mins/build of time.

Downloading now!! Thanks for your work!!
Enviado desde mi GT-I9195 mediante Tapatalk

Another 4.4.3 for the tab?
Thank you very much!

Hi AAccount,
thanks for your 4.4.3 ROM, sounds promising ... however, what about the graphical glitches on that vesion? I always went back to ROM version CM10.2/SGT7 as this seems to be the latest one without those glitches (last version I tried was Nameless ROM version 4.4.2 where they were still visible ... and annoying).
Thanks in advance,
mistersixt.

Great job!! Runs fast without bugs and glitches, only youtube HD...
The best kitkat rom!! Thanks !
Enviado desde mi GT-P7510 mediante Tapatalk

Best kitkat rom. I have some glitches. It is not as smooth as cm10.2 so i am going back to cm10.2.

What graphical glitches do you mean? I think ever since omni fixed the screenshot way back most graphical bugs have been ironed out. By youtube hd do you mean it doesn't play or can be laggy? If you mean laggy I read on wikipedia the GPU video decoding on the tegra2 sucks. That's a hardware problem.
3G build and new recovery coming later today. I cheated the chrome renderer build process by copying all the freshly done ones from the wifi only output folder.
My github is now fully up to date with all the appropriate omni repos forked with my personal touches whether it be the audio blob fixes or little things I like.
Sent from my GT-P7510

What are the flashing instructions? Is there a preferred gapps package?
Sent from my GT-P7510 using Tapatalk

AAccount said:
What graphical glitches do you mean?
Click to expand...
Click to collapse
With all ROMs starting with 4.3 it looks like if a flash of lightning goes from one corner to the other (my wife is saying it looks more like a scratch) for maybe 100 ms, this happens quite constantly though, every minute or something. Also, in some games like flappy bird the application gets stuck for maybe 100 to 200 ms completely (every 5 to 10 seconds maybe) before it continues, this makes playing games unpossible (temple run is another good example).
With 10.2/SGT7 this does not happen ... for whatever reason.
Regards, mistersixt.

lancem71 said:
What are the flashing instructions? Is there a preferred gapps package?
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
I added instructions. There's no really preferred gapps package. I just like that one because it's the smallest one that gets the job done. There are some gapps packages that are bigger than the rom which I consider bloated.
mistersixt said:
With all ROMs starting with 4.3 it looks like if a flash of lightning goes from one corner to the other (my wife is saying it looks more like a scratch) for maybe 100 ms, this happens quite constantly though, every minute or something. Also, in some games like flappy bird the application gets stuck for maybe 100 to 200 ms completely (every 5 to 10 seconds maybe) before it continues, this makes playing games unpossible (temple run is another good example).
With 10.2/SGT7 this does not happen ... for whatever reason.
Regards, mistersixt.
Click to expand...
Click to collapse
I get these randomly sometimes but not often enough that I would consider it an issue. In angry birds it's an issue but if you go to Settings-->Developer Options check mark "Force GPU rendering" and "Disable HW overlays". Then you can play angry birds at least without the lightning.
And now for an important question
I have a script that puts /data/dalvik-cache on /cache/dalvik-cache as it was way back in android 2.2 froyo. Even though our tablet shipped with android 3.0 and my I9300 S3 shipped with android 4.0, Samsung seems to have been very sloppy and left the /cache partition huge to accomodate the froyo standard. This is a waste of space that will never be used. The cache paritition is 0.5GB. Is it OK if I include this script as a boot script? Is 0.5GB/500MB enough for most peoples' dalvik-cache? This will free up that space and add it to the internal sd card.

Great room, thanks! Everything working OK during the first hour of use
Sent from my GT-P7500 using XDA Free mobile app

Thanks for posting this! Great ROM. Only problem I'm having is the APN settings are blank for my 3G tablet (P7500). I input them manually and everything works, but normally they are preset.

AAccount said:
I get these randomly sometimes but not often enough that I would consider it an issue. In angry birds it's an issue but if you go to Settings-->Developer Options check mark "Force GPU rendering" and "Disable HW overlays". Then you can play angry birds at least without the lightning.
And now for an important question
I have a script that puts /data/dalvik-cache on /cache/dalvik-cache as it was way back in android 2.2 froyo. Even though our tablet shipped with android 3.0 and my I9300 S3 shipped with android 4.0, Samsung seems to have been very sloppy and left the /cache partition huge to accomodate the froyo standard. This is a waste of space that will never be used. The cache paritition is 0.5GB. Is it OK if I include this script as a boot script? Is 0.5GB/500MB enough for most peoples' dalvik-cache? This will free up that space and add it to the internal sd card.
Click to expand...
Click to collapse
Many thanks for this!
"Disable HW overlays"- for some reason this setting does not stick between reboots (not your ROM problem- it happens in all devices that I've ever seen). Is there a way to apply it automatically during or after boot? Such as in a script, or init settings etc?
Regarding the Dalvik cache, is there a way to know how much space all my installed apps + system are currently using?

jaibar said:
Regarding the Dalvik cache, is there a way to know how much space all my installed apps + system are currently using?
Click to expand...
Click to collapse
Go to the CM File Manager --> Settings --> General Settings -> Compute folder statistics and check mark that box. Also in the same area be sure to set access mode to prompt user mode or root access mode. Then, go to /data and hold dalvik-cache folder until get a menu and choose properties. The size will show up under "Size: ". Mine is 208mb.

AAccount said:
Go to the CM File Manager --> Settings --> General Settings -> Compute folder statistics and check mark that box. Also in the same area be sure to set access mode to prompt user mode or root access mode. Then, go to /data and hold dalvik-cache folder until get a menu and choose properties. The size will show up under "Size: ". Mine is 208mb.
Click to expand...
Click to collapse
238MB here. Maybe a quick poll can help gather info on how much allocation must users are using?
Sent from my GT-P7510 using Tapatalk

jaibar said:
238MB here. Maybe a quick poll can help gather info on how much allocation must users are using?
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Same around 2xx mb. I'm fine with it, since the 400mb in /cache is wasted anyway.
Sent from my GT-P7500 using Tapatalk

223MB here

Is Netflix working on this ROM. Asking because there is problems on the Nameless ROM.
Sendt fra min GT-I9305 med Tapatalk

thra1982 said:
Is Netflix working on this ROM. Asking because there is problems on the Nameless ROM.
Click to expand...
Click to collapse
Every time somebody asks about Netflix... I fell I'm missing something big...

[UNOFFICIAL][ROM]BETA LineageOS 18.1 for SM-T710 - June 10, 2023

LineageOS 18.1 UNOFFICIAL for 2015 Samsung Galaxy Tab S2 SM-T710 ONLY​Model: SM-T710 (wifi) - gts28wifi - 8" screen, Exynos 5433 SoC, no LTE
This is the ONLY model that the ROM will work on.​
There is NO ROM for the T715 or T815 in this thread. Questions about T715 or T815 will be completely IGNORED.
You MUST READ posts 1-4 (about 10 minute read) before deciding to install this rom. If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
DISCLAIMER
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.
All involved in bringing this build to you are working voluntarily on it in very limited spare time, and their other life commitments have much higher priority. Don't expect a prompt, or even any, response to questions and bug reports.
Before attempting to install this ROM
1. Ask yourself: would bricking your device be a disaster for you? If yes, don't try this ROM! It can't be guaranteed stable and reliable enough to depend on for daily use.
2. BACKUP YOUR DATA AND EXISTING ROM. Be prepared for a complete restore if anything goes wrong.
3. RESEARCH adb, fastboot, Odin/heimdall, and TWRP and how to use them, if not already familiar with these.
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
9. DRM level 3 (SD definition)
10. deep sleep
What doesn't work
1. fingerprint. As I wrote in post 1891 at
https://forum.xda-developers.com/t/...t810-t815-t815y.3879302/page-95#post-85533725
I will not spend anymore time looking at fingerprint. If you need fingerpint to work, stay with stock Samsung rom.
2. DRM level 1 (no HD definition). There's more detail in post 1891 above. I will not be trying to achieve level 1 for HD definition. If you need HD definition for your $treaming media, stay with stock Samsung rom.
3. If you charge the device while it's powered off and then want to power it on, you MUST wait at least 30 seconds AFTER disconnecting the charger cable before pressing the power button otherwise you might run into strange boot problems such as the touch screen not working.
4. Possibly other features that I haven't tested or do not use.
Source Code
See FAQ 1 for links in post #2.
Thanks
1. LineageOS team for source code.
2. @retiredtab, @ananjaser1211, @lpedia, @Yogi555 and @CuckooPenguin for spending nearing 1 month fixing the 2 most biggest bugs in 17.1 that plagued users for nearly 10 months: the wifi instability and random reboots. These are discussed in detail at
https://forum.xda-developers.com/t/...rs-running-any-version-of-android-10.4308193/
https://forum.xda-developers.com/t/...rs-running-any-version-of-android-10.4308203/
3. All past contributors of the exynos5433 code.
4. @rINanDO for his lmkd spam fix in 18.1.
5. beta testers: lpedia, Yogi555 and CuckooPenguin
6. lpedia for building the public T710 monthly roms starting April 2022
7. lpedia for suggestions, proof reading and FAQ table format in post #2.

Frequently Asked Questions. You MUST READ this before posting any questions. Thank you.
QuestionAnswerQ1. Can I build this ROM for myself? Where are the source and kernel source files?A1. Yes, you can. The source files are listed below.
Kernel
https://github.com/retiredtab/android_kernel_samsung_universal5433-selinux
Device Tree
https://github.com/retiredtab/android_device_samsung_gts2-common-selinux
https://github.com/retiredtab/android_device_samsung_gts28wifi
Vendor
https://github.com/retiredtab/proprietary_vendor_samsung-selinux
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. The other patch required for tcp/ip is at https://github.com/DerpFest-11/pack...mmit/22fd53a977eeaf4e36be7bf6358ecf2c2737fa5eQ2. Is this ROM suitable as a daily driver?A2. It might be, depending on your requirements. You would need to try it yourself, with your preferred apps, to see if suits your purposes. I've been using it myself since mid August 2021 with no major issues.Q3. What do I do if my app xyz doesn't work?A3. I can't help diagnose problems with random apps I know nothing about. If the app is critically important to you and it doesn't work on this ROM, go back to a ROM where it did work.Q4. Why is this ROM laggy and/or buggy?A4. The device will be noticeably slower if you're using any Gapps package. Consider going gapps-free. A lot of apps will work without Google's services, or there exist alternatives that will. Check out F-Droid, Aurora Store, NewPipe, etc.Q5. What TWRP should I use?A5. You MUST use my unofficial TWRP 3.5.2_9. Get it from
https://sourceforge.net/projects/retiredtab/files/SM-T710/TWRP/Q6. Why should I use this ROM?A6. You don't have to! If you don't like it, go back to your old ROM.Q7. Will you offer monthly updates with security patches?A7. We plan to do so. lpedia will try to update the ROM with the monthly security patches after LineageOS has released them, free time permitting. Each monthly build will be tested to make sure all the "What's working" functionality listed in post #1 still works, before it's made available (which might in some cases delay the release).Q8. I'm a newbie. Can you provide step by step instructions?A8. We simply don't have the time to do this, but there are lots of tutorials, videos, etc online showing how to flash custom ROMs and how to deal with common problems. Newbie questions are also accepted in the XDA General Questions and Answers forum. Having said that, @pflyaz has kindly make a guide in post #37.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.
Provide an adb logcat of the problem, and if possible describe how to reproduce it. Note that I can't help if it involves downloading any app I don't already use that requires payment or creating a userid/password.
To get a logcat, open a terminal window on your PC, connect your device to it via USB, and do this:
Bash:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occurred,
# then stop trace by hitting ctrl-c then zip the problem.txt file
# before uploading it.
Q10. How long will you build 18.1 for this device?A10. For now, 18.1 will be built for all of 2022. After that, we will make a decision depending on a number of factors.Q11. Do I need to erase everything and format my data before installing this ROM for the first time?A11. Under most circumstances, yes.
If you're coming from stock Samsung Android, or an earlier version of LineageOS, or a different custom ROM, you MUST 'clean flash': boot to TWRP recovery, wipe system, data, dalvik/art cache, and cache partitions, then Format Data, then install this ROM.
If you don't do this you're likely to run into problems, such as getting stuck at the boot animation for more than 5 minutes.
The ONLY exception is that if you are coming from LOS 18.1 with the April 5 2022 security patch or later, you can dirty flash the latest security patch build.Q12. What Gapps should I use?A12. Your choice! There are several well-known Gapps packages, such as NikGapps, BiTGapps, OpenGapps, and MindTheGapps. OpenGapps is being removed as per post #11. Do your own research as to what is the most reliable gapps option for you.
I recommend installing the SMALLEST version of any of these, preferably with just the minimum Google services needed to access the Play Store and run apps that depend on Google services.
You could also consider Google alternatives, such as Aurora Store, which mirrors the Google Play Store apps but doesn't need any Google services itself. Many Play Store apps do not actually depend on Google services.
If you are going to install any Gapps package, follow the installation instructions given for that particular package.Q13. I'm having problems with Gapps. Can you tell me why it's not working?A13. I can't answer any questions about Gapps, because I don't use them. Ask your questions on the XDA thread for the Gapps package you're using.Q14. Why isn't my post answered?A14. There are several possible reasons: the question is answered in the FAQ (in which case it will be ignored completely); or it involves apps or operating systems that I don't use; or it's about Gapps, which I don't use; or I simply have not had time to answer any questions.Q15. What speed up/optimization tips do you suggest?A15. These steps can make a big difference to performance:
Turn off animations. Go to Settings > System > Developer options, scroll down to the Drawing section, and set Window, Transition and Animator scale all to "Animation off".
Don't install Gapps unless you depend on something that only Google is providing. Use Aurora Store to get your preferred Play Store apps - they will all be available on Aurora Store. You can choose to access this anonymously or use a Google account.
Don't run more than two apps at the same time. You can probably listen to music in the background and use a web browser at the same time.
Use a web browser with built-in adblock and privacy features, such as Brave.
Use NewPipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
Look for apps that are open source, ad-free and lightweight.
Q16. Does this ROM support Magisk so I can root my device?A16. Magisk works with this ROM as reported by beta testsers, but that could change with any revision and changes by Google. However I don't use it myself and can't help with any related issues. Direct any questions about Magisk to the XDA Magisk forum.Q17. Will this ROM ever become official?A17. Never. Official maintainers have onerous responsibilities, and I know my device trees, code organization and git commits will NOT meet LineageOS standards. I'm not able or willing to take on the responsibilities and commit the extra time to supporting an official build.Q18. What is the difference between this ROM and others?A18. This ROM tries to be pure LineageOS with little or no modification. Other ROMs may come with a different UI, different bundled apps, etc.Q19. Will there be any major 18.1 code modifications in the future?A19. 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 - getting the rom up and running, and fixing all the major bugs - has been done. This doesn't mean the code is perfect or well organized, but I won't be making any major changes.Q20. Why did you fork the trees?A20. I wanted my own private branch where I could make changes that would only affect my own personal builds.Q21. Can you build a variant of this device? For example, a LTE or S-pen version?A21. I cannot and will not try to build for a variant device if I don't physically have that device. I have to be able to boot and test it myself, and there's no guarantee that I can get those variant features working. So I will NEVER build T715, T810 and T815.Q22. Can I load this ROM on a variant device like LTE or S-pen version?A22. This ROM is for the device explicitly listed and will only work on that device. Do not try to install it on any other device.
ONLY if you are an advanced user and understand TWRP, adb, odin, heimdall, etc, you could try loading it on a LTE or S-pen variant by modifying the updater-script, but be warned: there are likely to be problems, including a bricked device, bootloops, or the ROM not being able to support the functionality of LTE/S-pen.Q23. Does this ROM have any wifi connection issues?A23. This ROM's wifi has been stable on the specified device ever since lpedia and I determined the root cause of the wifi problems back in July 2021 and re-installed the original S2 network 'blobs' with LOS 17.1.Q24. Is this ROM secure so I can do financial transactions?A24. Although Android monthly security patches do improve general security, this ROM's outdated kernel and old proprietary vendor blobs/drivers will NEVER get updates of any kind, and could have significant security holes.
In addition, although the ROM is SElinux enforcing, there's a good chance that the rules written (about 800+ lines of code) have some errors.
If the device is rooted, this would further weaken the security.
With this information, it's up to you to make an informed decision about whether you trust this ROM to be secure enough for your financial transactions.Q25. Okay, I understand the consequences and willing to take the risks outlined, now where can I find the BETA rom?A25. Downloads are at
https://sourceforge.net/projects/lpedia-sf/files/gts28wifi/

Monthly release notes
June 10, 2023 release notes
1. Incorporates June 5 as per https://review.lineageos.org/q/topic:R_asb_2023-06
May 8, 2023 release notes
1. Incorporates May 5 as per https://review.lineageos.org/q/topic:R_asb_2023-05
Apr 18, 2023 release notes
1. Incorporates Apr 5 as per https://review.lineageos.org/q/topic:R_asb_2023-04
March 19, 2023 release notes
1. Incorporates Feb 5 and Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-02 and https://review.lineageos.org/q/topic:R_asb_2023-03
Jan 8, 2023 release notes
1. Incorporates Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-01
Dec 12 release notes
1. Incorporates Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-12
Nov 12 release notes
1. Incorporates Nov 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-11
Oct 9 release notes
1. Incorporates Oct 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-10
Sept 11 release notes
1. Incorporates Sept 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-09
2. Fixes non working touchscreen and hardware buttons when powering up with power cable plugged in and device turned off. However, the recommendation is still to unplug your charger, wait 30 seconds before pressing power button when your device is turned off.
https://github.com/retiredtab/andro...mmit/7e0657629efedc7f06f6f6fb57199fca0b4e8ea6
https://github.com/retiredtab/andro...mmit/e17c44d2e282d67b243a1c99ce62127e83052c4f
3. Removed settings menu option for fast charging. S2 tablet devices do not support this.
https://github.com/retiredtab/andro...mmit/6db8e690141a98e5cf9e6952c3572c127c0cf8ea
Aug 10 release notes
1. Incorporates Aug 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-08
2. Fixes saving of color profile in live display during a reboot/shutdown.
https://github.com/retiredtab/andro...mmit/01b1ed6ba8c268a19762031415fde1b4e45d4ac3
3. Fixes offline battery charging by writing rules to allow charger to access certain files. This removes the previous workaround. Thanks to @simon-edwards for providing an adb logcat that showed the denials.
https://github.com/retiredtab/andro...mmit/041ae45960170e68410b059f4f709e9c14b79a99
July 23, 2022
1. Added argosd to improve wifi throughput as per https://github.com/retiredtab/andro...mmit/c181aa0c5192e46a5a03d4451e2648481a520c0f
2. Incorporates July 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-07
3. Incorporates a workaround for offline charging.
https://github.com/retiredtab/andro...mmit/9d019f0a3be789850a9add18d042990631f05b44
Previously, if the device was off and you plugged in a charger, it would show a battery icon and this would display indefinitely giving no sign of charging animation. With this workaround, the battery icon is displayed for a few seconds and then a white circle with a charge symbol inside it is shown to indicate it's charging.
After a few seconds, the screen will go blank and continue charging. The side effect of this workaround is that in order to turn on the device, you first must unplug the charger and then turn on your device. If you try to turn on the device with the charger cable plugged in, it won't turn on.
June 12, 2022
1. Removed vibrator code from gts2-common as wifi only models don't have vibrator motor (only LTE models).
https://github.com/retiredtab/andro...mmit/e54aee73a98e3cef6e74f96c1815cec9c82ff10d
https://github.com/retiredtab/andro...mmit/dd846b06378182398c55b57b2edc2537369bd509
2. Incorporates June 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-06
May 12, 2022
1. Added overlay for led capacitive led buttons as per https://github.com/retiredtab/andro...mmit/83551570e4627a0e353e358787f83aa65484b528
2. Incorporates May 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
April 11, 2022
1. YOU MUST read posts 1-4 if you haven't already
2. First public BETA release of selinux enforcing T710 build.
3. Incorporates April 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
4. BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA after as this is the first release of this build. You cannot dirty flash at all. See FAQ.

Reserved.

Initial public build called lineage-18.1-20220411-UNOFFICIAL-gts28wifi.zip. The sha256sum file is provided as well to ensure integrity of download.
lpedia has tested all the functionality as to what works as per post #1 before uploading the build. 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.
April 11, 2022
1. YOU MUST read posts 1-4 if you haven't already
2. First public BETA release of selinux enforcing T710 build.
3. Incorporates April 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
4. BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA after as this is the first release of this build. You cannot dirty flash at all. See FAQ Q11.

Congratulations on the awesome release!

New build called lineage-18.1-20220512-UNOFFICIAL-gts28wifi.zip
lpedia has tested all the functionality as to what works as per post #1 before uploading the build. 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.
May 12, 2022 release notes
1. YOU MUST read posts 1-4 if you haven't already
2. Added overlay for led capacitive led buttons as per https://github.com/retiredtab/andro...mmit/83551570e4627a0e353e358787f83aa65484b528
3. Incorporates May 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
4. If you are upgrading from the April 11 build, you may dirty flash the May 10 build. If you are NOT coming from the April 11th, 2022 build, you MUST BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA. You cannot dirty flash at all. See FAQ Q11.

Hi there, thanks for your ROM. I would like to report a bug with using it.
May 12, 2022 release "lineage-18.1-20220512-UNOFFICIAL-gts28wifi" with "open_gapps-arm-11.0-pico-20220503".
All factory resetted through TWRP, after flashing and booting the device it is stuck on "Just a sec..." when selecting set up offlie. If you try to set it up over wifi it is stuck on "Getting your tablet ready."
I've included my logcat, if you need more info or another reproduction please let me know.
Thanks!
Kim

kimrosebush said:
Hi there, thanks for your ROM. I would like to report a bug with using it.
May 12, 2022 release "lineage-18.1-20220512-UNOFFICIAL-gts28wifi" with "open_gapps-arm-11.0-pico-20220503".
All factory resetted through TWRP, after flashing and booting the device it is stuck on "Just a sec..." when selecting set up offlie. If you try to set it up over wifi it is stuck on "Getting your tablet ready."
I've included my logcat, if you need more info or another reproduction please let me know.
Thanks!
Kim
Click to expand...
Click to collapse
Hi, @kimrosebush. Thank you for sending a logcat.
This kind of problem is often because the gapps package isn't quite right for some reason. Google Setup needs the underlying Google Play services to be present and working properly. This line from your logcat suggests they are not:
Code:
05-12 22:29:54.077 4147 4225 W GooglePlayServicesUtil: com.google.android.setupwizard requires Google Play services, but they are missing.
A few questions about the process you followed:
1. What OS was on the T710 before you began? If it was stock Android, was it the latest version available?
2. Did you install the correct version of TWRP (see Q5 in the FAQ)?
3. When you say "All factory resetted through TWRP", what did you actually do?
4. When did you install the gapps package? Just after the ROM, before first boot?
Have you checked whether everything else is working? In particular, is wifi connecting and working properly? [Pressing the Home button should get you out of the stuck Google Setup.]

lpedia said:
Hi, @kimrosebush. Thank you for sending a logcat.
This kind of problem is often because the gapps package isn't quite right for some reason. Google Setup needs the underlying Google Play services to be present and working properly. This line from your logcat suggests they are not:
Code:
05-12 22:29:54.077 4147 4225 W GooglePlayServicesUtil: com.google.android.setupwizard requires Google Play services, but they are missing.
A few questions about the process you followed:
1. What OS was on the T710 before you began? If it was stock Android, was it the latest version available?
2. Did you install the correct version of TWRP (see Q5 in the FAQ)?
3. When you say "All factory resetted through TWRP", what did you actually do?
4. When did you install the gapps package? Just after the ROM, before first boot?
Have you checked whether everything else is working? In particular, is wifi connecting and working properly? [Pressing the Home button should get you out of the stuck Google Setup.]
Click to expand...
Click to collapse
Hey @lpedia thanks for the reply.
1. LineageOS 17.1 I believe was the build.
2. Yes I installed the provided version.
3. I formatted all partitions except SD, flashed the images and then formatted the SD to ensure a completely wiped device.
4. Just after the ROM.
I tried a few times further, then I decided to go for the 'full' OpenGApps package; once I used this one and attempted the offline setup again I was able to proceed further in configuring the tablet.
Thanks for the hint in the right direction. Am glad to be on Android 11 now.
Kind Regards,
Kim

I will be removing opengapps from the FAQ because for several months now (starting around Oct 2021), the opengapps project has been releasing UNTESTED builds that results in bootloops or non working gapps services. Despite numerous requests/posts from the community to slow down the releases and actually TEST THEM BEFORE release, the latest May 3, 2022 shows there is still room for improvement.
This thread in the opengapps forum is just the latest example. Details of UNTESTED builds are also in the same megathread below.
https://forum.xda-developers.com/t/...rsions-devices.3098071/page-367#post-86885091
It's also shown up in other roms like
https://forum.xda-developers.com/t/...7-1-04-30-2022.3937956/page-100#post-86885353
This would be a good time for user to do their own research on which gapps is best for them or use NONE at all. I use Aurora Store myself.
Just a reminder that the builds we release are TESTED and verified to have all the functionality as listed in post #1.

kimrosebush said:
Hey @lpedia thanks for the reply.
1. LineageOS 17.1 I believe was the build.
2. Yes I installed the provided version.
3. I formatted all partitions except SD, flashed the images and then formatted the SD to ensure a completely wiped device.
4. Just after the ROM.
I tried a few times further, then I decided to go for the 'full' OpenGApps package; once I used this one and attempted the offline setup again I was able to proceed further in configuring the tablet.
Thanks for the hint in the right direction. Am glad to be on Android 11 now.
Kind Regards,
Kim
Click to expand...
Click to collapse
Good to hear!
Note that you don't have to be quite so brutal about wiping absolutely everything for a 'clean' flash. I manually wipe Dalvik / ART Cache, Cache, and System, and then Format Data. I have never reformatted the SD.
If you have any further trouble, I suggest you try starting again with a clean flash and a different gapps package, or try doing without any gapps, as @retiredtab has recommended in the post above.
In my experience, some gapps packages, or sometimes just a particular version of a gapps package, don't work with some ROMs. I have not tried opengapps, but I can confirm that BiTGApps-arm-11.0.0-R45_signed.zip does work on my T710 with this particular ROM version.
I personally like BiTGapps because it installs only the bare minimum needed (Google services and Play Store; doesn't even automatically run Google Setup) and doesn't have to be installed before first boot. So it's possible to install LOS, boot the system, make sure everything's working, then go back into TWRP and install gapps. If any problems turn up, this approach also makes it easier to tell whether it's something to do with LOS or with gapps.
You could also try running LOS without any gapps, and if you decide you want gapps after all, install BiTGapps without having to clean-flash and start again.

I just installed this rom two days ago. It has been working great. Today, however, I noticed that Trust gave me a message about the build having public keys. Yesterday, I don't recall getting that message. Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted. Finally, my CRAVE (a Canadian streaming service) app won't play videos but gives a "device is rooted" message. Netflix works however.
Would you have any idea what is going on or how I should deal with this?
Thanks,
MC

Dr_MC said:
Today, however, I noticed that Trust gave me a message about the build having public keys. Yesterday, I don't recall getting that message.
Click to expand...
Click to collapse
On April 6, @lpedia and I had a PM discussion about signing builds.
lpedia wrote
Code:
"About signing builds ... an issue with just using the default test-keys signature is that someone can easily create
their own builds and pass them off as someone else's, possibly adding malicious or just plain bad code, and their
package would look just like the original."
I replied
Code:
"For our purposes, maybe we should just include the sha256sum and recommend that the users verify
them to ensure the file downloaded correctly and it wasn't modified?"
To get stop seeing that trust message, goto settings, privacy, trust, turn off build signature.
Dr_MC said:
Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted. Finally, my CRAVE (a Canadian streaming service) app won't play videos but gives a "device is rooted" message. Netflix works however.
Click to expand...
Click to collapse
I can't see the Crave app in Aurora Store. I use the app devcheck to check for root access and the screenshot clearly shows it's not rooted.
There's nothing in my code to enable root. In fact, I don't even want root on my devices.
For Crave, you can try using Magisk and it's hide root function to see if that will fool Crave into thinking the device is not rooted.

Dr_MC said:
Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted.
Click to expand...
Click to collapse
I did installed the above root checker app and got the same message. That is, the T710 rom, by default is NOT rooted. I don't know why Crave would say it's rooted.
I believe root checker's main function is to verify that your rom is "rooted" so when it says "root access is not properly installed.", it's trying to tell you that your attempt to use Magisk or similar type app to root the rom was unsuccessful.
BTW, you are better off using devcheck as it's an excellent ad-free utility that I use on a regular basis to help develop this rom vs the ad-infested root checker app. While devcheck isn't open source, it's written by flar2 who is a xda member here.

Dr_MC said:
Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted.
Click to expand...
Click to collapse
Root Checker Basic says "Sorry! Root access is not properly installed on this device" when asked to confirm root status on an unrooted device. So as far as that app's concerned, it just means "I can't confirm it's rooted". Which is to be expected if it isn't rooted and you haven't even tried to root it.
If that isn't the app you're using, see if you can find out what it means to your particular root-checker app.
Dr_MC said:
Finally, my CRAVE (a Canadian streaming service) app won't play videos but gives a "device is rooted" message. Netflix works however.
Click to expand...
Click to collapse
Did the CRAVE app work on this device when it had the stock Samsung ROM? Do you have to register devices to receive this service? If so, might it need to be re-registered? Because its device ID will have changed.

Thanks for suggesting devcheck. It says I'm unrooted. Perhaps Crave noticed the unlocked bootloader or the custom ROM.

It did work with stock. It was registered, twice in fact. I deleted both, registered it again. The ap still says I'm rooted. Oh well, that's ok, I can use crave through a browser.
BTW do you know where I can find the stock keyboard?
Thanks

Dr_MC said:
BTW do you know where I can find the stock keyboard?
Click to expand...
Click to collapse
If you mean the Samsung keyboard - sorry, no, I don't. I switched to a different keyboard years ago. Google's GBoard has similar functionality, I think. MS SwiftKey is OK, too - has the best (most relevant) suggested text of any of the keyboards I've tried.

ROM working fine for me after trial and error with various gapps. FWIW I ran into the "just a sec " with opengapps. I finally had some joy by flashing the rom, but not gapps. Boot the ROM and completely setup it up Lineage. Then I restarted and flashed open gapps. When I rebooted everything came uo fine and has been solid eversince. Kudos your you gentlemen for fixing the Wifi ! Its been nice to have it work stably.

[UNOFFICIAL][ROM]ALPHA LineageOS 19.1 for SM-T710 - June 12, 2023

LineageOS 19.1 UNOFFICIAL for 2015 Samsung Galaxy Tab S2 SM-T710 ONLY​Model: SM-T710 (wifi) - gts28wifi - 8" screen, Exynos 5433 SoC, no LTE
This is the ONLY model that the ROM will work on.​
There is NO ROM for the T715 or T815 in this thread. Questions about T715 or T815 will be completely IGNORED.
You MUST READ posts 1-4 (about 10 minute read) before deciding to install this rom. If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
DISCLAIMER
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.
All involved in bringing this build to you are working voluntarily on it in very limited spare time, and their other life commitments have much higher priority. Don't expect a prompt, or even any, response to questions and bug reports.
Before attempting to install this ROM
1. Ask yourself: would bricking your device be a disaster for you? If yes, don't try this ROM! It can't be guaranteed stable and reliable enough to depend on for daily use.
2. BACKUP YOUR DATA AND EXISTING ROM. Be prepared for a complete restore if anything goes wrong.
3. RESEARCH adb, fastboot, Odin/heimdall, and TWRP and how to use them, if not already familiar with these.
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
9. DRM level 3 (SD definition)
10. deep sleep
11. camera
1. fingerprint is completely removed in 19.1. When I tested it in March 2022, it wasn't compatible with keystore2 and as I wrote in post 1891 at
https://forum.xda-developers.com/t/...t810-t815-t815y.3879302/page-95#post-85533725
it never worked properly after deep sleep. If you need fingerpint to work, stay with stock Samsung rom.
2. DRM level 1 (no HD definition). There's more detail in post 1891 above. I will not be trying to achieve level 1 for HD definition. If you need HD definition for your $treaming media, stay with stock Samsung rom.
3. workaround to disable scoped storage. In 18.1 there was a workaround to disable scoped storage, but that no longer works in 19.1. So if you have a lot of apps or data on an external microsd, the performance may be severely degraded.
4. If you charge the device while it's powered off and then want to power it on, you MUST wait at least 30 seconds AFTER disconnecting the charger cable before pressing the power button otherwise you might run into strange boot problems.
5. keyboard bug workaround. When prompted to enter something like a Bluetooth pin or text based password, sometimes the keyboard is not shown on the screen or off screen. The workaround is to goto settings, system, languages & input, on-screen keyboard, Android Keyboard (AOSP), appearance & layout, theme and choose "Material - follow system settings".
This keyboard bug is a LineageOS bug as per
https://review.lineageos.org/c/LineageOS/android_packages_inputmethods_LatinIME/+/325438
6. Possibly other features that I haven't tested or do not use.
Source Code
See FAQ 1 for links in post #2.
Thanks
1. LineageOS team for source code.
2. In alphabetical order.
@ananjaser1211
- helping out with libGLES_mali problem when I couldn't figure out why T810, for 3 months, wasn't booting with graphics
- answering more 5433 related questions wrt to certain features.
@bluess57
- joining the team and helping fix some of the legacy code problems
- pending code commits to come in the future
@bmwdroid
- testing many pre ALPHA builds and reporting the results
@CuckooPenguin
- testing many pre ALPHA builds and reporting the results, but sadly his T810 was killed by a cat (true story)
exynos5420 team
- making suggestions regarding radare2 debugger/code analyzer when I couldn't figure out why T810, for 3 months, wasn't booting with graphics
Kyle Harrison
- giving me a clue on how to fix the binder/keystore2 problem with msm8916 which ultimately led me to fix the same problem on the exynos5433 devices
- sharing his code on his github repos where I could study his commits to help bring up 19.1
- making code commits on LineageOS wrt to legacy devices like ours
- sharing the repopicks necessary to bringup 19.1
@lpedia
- testing many pre ALPHA T710 builds starting in April 2022 and reporting the results
- verifying my build instructions work so that the technically inclined can build this from source
- building, maintaining and most importantly, testing the T710 18.1 builds before monthly security patches release
- volunteering to build, maintain and test T710 19.1 builds
@metterschling
- reaching out and joining our group to help with code and fix problems
- testing many pre ALPHA builds and reporting the results
- pending code commits to come in the future
@pflyaz
- testing many pre ALPHA builds and reporting the results
- writing install instructions for the newbies
@simon-edwards
- reaching out and joining our group to help with code and fix problems
- testing many pre ALPHA builds and reporting the results
@tarkzim
- helping me fix the gpsd crash problem because I was missing the libutils library in my Android.bp file
- sharing his code on his github repos where I could study his commits to help bring up 19.1 especially wrt to hal audio 2.0 and camera 1.0
@Yogi555
- testing many pre ALPHA builds and reporting the results
- building, maintaining and most importantly, testing the T810 18.1 builds before monthly security patches release
As you can see, it's truly a team worldwide effort in getting this ALPHA 19.1 build out.

Frequently Asked Questions. You MUST READ this before posting any questions. Thank you.
QuestionAnswerQ1. Can I build this ROM for myself? Where are the source and kernel source files?A1. Yes, you can. The source files are listed below.
Kernel
https://github.com/retiredtab/android_kernel_samsung_universal5433-selinux
Device Tree
https://github.com/retiredtab/android_device_samsung_gts2-common-selinux
https://github.com/retiredtab/android_device_samsung_gts28wifi
Vendor
https://github.com/retiredtab/proprietary_vendor_samsung-selinux
The build manifest and instructions on how to compile from source are at
https://github.com/retiredtab/LineageOS-build-manifests
The other patch required for tcp/ip is at https://github.com/DerpFest-11/pack...mmit/22fd53a977eeaf4e36be7bf6358ecf2c2737fa5eQ2. Is this ROM suitable as a daily driver?A2. It might be, depending on your requirements. You would need to try it yourself, with your preferred apps, to see if suits your purposes. I've been using it myself since mid April, 2022 with no major issues.Q3. What do I do if my app xyz doesn't work?A3. I can't help diagnose problems with random apps I know nothing about. If the app is critically important to you and it doesn't work on this ROM, go back to a ROM where it did work.Q4. Why is this ROM laggy and/or buggy?A4. The device will be noticeably slower if you're using any Gapps package. Consider going gapps-free. A lot of apps will work without Google's services, or there exist alternatives that will. Check out F-Droid, Aurora Store, NewPipe, etc.Q5. What TWRP should I use?A5. You MUST use TWRP 3.5.2_9. Get it from https://github.com/retiredtab/android_device_samsung_gts28wifiQ6. Why should I use this ROM?A6. You don't have to! If you don't like it, go back to your old ROM.Q7. Will you offer monthly updates with security patches?A7. We plan to do so. We will try to update the ROM with the monthly security patches after LineageOS has released them, free time permitting. Each monthly build will be tested to make sure all the "What works" functionality listed in post #1 still works, before it's made available (which might in some cases delay the release).Q8. I'm a newbie. Can you provide step by step instructions?A8. We simply don't have the time to do this, but there are lots of tutorials, videos, etc online showing how to flash custom ROMs and how to deal with common problems. Newbie questions are also accepted in the XDA General Questions and Answers forum.
Having said that pflyaz has kindly provided instructions in post #5.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.
Provide an adb logcat of the problem, and if possible describe how to reproduce it. Note that I can't help if it involves downloading any app I don't already use that requires payment or creating a userid/password.
To get a logcat, open a terminal window on your PC, connect your device to it via USB, and do this:
Bash:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occurred,
# then stop trace by hitting ctrl-c then zip the problem.txt file
# before uploading it.
Q10. How long will you build 19.1 for this device?A10. For now, 19.1 will be built for all of 2022. After that, we will make a decision depending on a number of factors.Q11. Do I need to erase everything and format my data before installing this ROM for the first time?A11. If you're coming from stock Samsung Android, or an earlier version of LineageOS, or a different custom ROM, you MUST 'clean flash': boot to TWRP recovery, wipe system, data, dalvik/art cache, and cache partitions, then Format Data, then install this ROM.
If you don't do this you're likely to run into problems, such as getting stuck at the boot animation for more than 5 minutes.Q12. What Gapps should I use?A12. Your choice! There are several well-known Gapps packages, such as NikGapps, BiTGapps, OpenGapps, and MindTheGapps. Do your own research as to what is the most reliable gapps option for you. As a courtesy to gapps users, I opened a thread at
https://forum.xda-developers.com/t/...on-for-19-1-roms-sm-t710-and-sm-t810.4480041/
for you to discuss gapps. Do not discuss gapps in this thread. Thank you.
You could also consider Google alternatives, such as Aurora Store, which mirrors the Google Play Store apps but doesn't need any Google services itself. Many Play Store apps do not actually depend on Google services.
If you are going to install any Gapps package, follow the installation instructions given for that particular package.Q13. I'm having problems with Gapps. Can you tell me why it's not working?A13. I can't answer any questions about Gapps, because I don't use them. Ask your questions on the XDA thread for the Gapps package you're using.Q14. Why isn't my post answered?A14. There are several possible reasons: the question is answered in the FAQ (in which case it will be ignored completely); or it involves apps or operating systems that I don't use; or it's about Gapps, which I don't use; or I simply have not had time to answer any questions.Q15. What speed up/optimization tips do you suggest?A15. These steps can make a big difference to performance:
Turn off animations. Go to Settings > System > Developer options, scroll down to the Drawing section, and set Window, Transition and Animator scale all to "Animation off".
Don't install Gapps unless you depend on something that only Google is providing. Use Aurora Store to get your preferred Play Store apps - they will all be available on Aurora Store. You can choose to access this anonymously or use a Google account.
Don't run more than two apps at the same time. You can probably listen to music in the background and use a web browser at the same time.
Use a web browser with built-in adblock and privacy features, such as Brave.
Use NewPipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
Look for apps that are open source, ad-free and lightweight.
Q16. Does this ROM support Magisk so I can root my device?A16. Magisk works with this ROM as reported by beta testsers, but that could change with any revision and changes by Google. However I don't use it myself and can't help with any related issues. Direct any questions about Magisk to the XDA Magisk forum.Q17. Will this ROM ever become official?A17. With 19.1, legacy devices like ours will NEVER be official due to lack of ebpf support. See https://lineageos.org/Changelog-26/Q18. What is the difference between this ROM and others?A18. This ROM tries to be pure LineageOS with little or no modification. Other ROMs may come with a different UI, different bundled apps, etc.Q19. Will there be any major 19.1 code modifications in the future?A19. There may be some major modifications along with some slight tweaking to the SEpolicy, small bug fixes and minor code cleanup, but all the hard work - getting the rom up and running, and fixing all the major bugs - has been done.Q20. Why did you fork the trees?A20. I wanted my own private branch where I could make changes that would only affect my own personal builds.Q21. Can you build a variant of this device? For example, a LTE or S-pen version?A21. I cannot and will not try to build for a variant device if I don't physically have that device. I have to be able to boot and test it myself, and there's no guarantee that I can get those variant features working.Q22. Can I load this ROM on a variant device like LTE or S-pen version?A22. This ROM is for the device explicitly listed and will only work on that device. Do not try to install it on any other device.
ONLY if you are an advanced user and understand TWRP, adb, odin, heimdall, etc, you could try loading it on a LTE or S-pen variant by modifying the updater-script, but be warned: there are likely to be problems, including a bricked device, bootloops, or the ROM not being able to support the functionality of LTE/S-pen.Q23. Does this ROM have any wifi connection issues?A23. This ROM's wifi has been stable on the specified device ever since lpedia and I determined the root cause of the wifi problems back in July 2021 and re-installed the original S2 network 'blobs' with LOS 17.1.Q24. Is this ROM secure so I can do financial transactions?A24. Although Android monthly security patches do improve general security, this ROM's outdated kernel and old proprietary vendor blobs/drivers will NEVER get updates of any kind, and could have significant security holes.
In addition, although the ROM is SElinux enforcing, there's a good chance that the rules written (about 800+ lines of code) have some errors.
If the device is rooted, this would further weaken the security.
With this information, it's up to you to make an informed decision about whether you trust this ROM to be secure enough for your financial transactions.Q25. How do I turn off the taskbar at the bottom of the screen?A25. Goto settings, system, buttons and disable taskbar.Q26. Okay, I understand the consequences and willing to take the risks outlined, now where can I find the ALPHA rom?A26. Downloads are at https://sourceforge.net/projects/lpedia-sf/files/gts28wifi-19.1/

NOTE: lpedia has personally tested each build on his 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 in TWRP. This is known has a clean install. Backup your data before a clean install.
June 12 , 2023 release notes
1. June 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-06
May 7 , 2023 release notes
1. May 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-05
Apr 18 , 2023 release notes
1. Apr 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-04
March 20 , 2023 release notes
1. Mar 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-03
Feb 12 , 2023 release notes
1. Feb 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-02
2. Use stock android.hardware.power for CPU/SoC management so little cores can go as low as 400Mhz. Previously, the minimum clock speed was 1200Mhz and this may have caused some overheating. See
https://github.com/retiredtab/andro...mmit/8480e024cb15d82b9d418c44efd9257db173b49e
Jan 8, 2023 release notes
1. Jan 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-01
Dec 12, 2022 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-12
Nov 11, 2022 release notes
1. Nov 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-11
Oct 10, 2022 release notes
1. Oct 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-10
Sept 11, 2022 release notes
1. Sept 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-09
2. Removed settings menu option for fast charging. S2 tablet devices do not support this.
https://github.com/retiredtab/andro...mmit/8068a4a66ae7c576973807b392e686110126150c
Aug 11, 2022 release notes
1. Aug 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-08
2. Initial ALPHA release to public.

Reserved.

Tab S2 T710 Upgrade Procedure for the LineageOS 19.1 ROM by retiredtab
These installation instructions work for both Tab S2 T710 and T810, starting from a device running stock Android 7.0. I have both devices and have tested the procedure on both. I am a Windows guy, so these instructions assume a Windows PC. I am a lifelong techie guy and an Android enthusiast. My current “production” devices are Samsung S22 Ultra and Samsung Tab S7, but I do love the size and performance of the Tab S2 T710 so am extremely happy that @retiredtab and @lpedia have been successful at making Lineage 19.1 run on the Tab S2. But I am not developer, so these instructions will work for any competent newbie who’s looking for LOS 19.1 on their Tab S2 tablet. I do realize there may be alternative approaches for those who have deeper Android tech knowledge than me, but this procedure does work every time.
Step 1 – Preparation
Update your Tab S2 to the latest stock software.
Install a micro-SD card into your Tab S2.
Enable Developer Options – tap Build Number seven times.
In Developer Options, turn on USB debugging.
Connect your Tab S2 to your PC via USB and download onto the micro-SD card three files:
Retiredtab’s latest Lineage 19.1 ROM from lpedia-sf - Browse /gts28wifi-19.1 at SourceForge.net (T710) or retiredtab - Browse /SM-T810/19.1 at SourceForge.net (T810)
NikGapps-core-arm64-12.1-20220709-signed.zip from https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-SL/
Magisk-v25.2.apk from https://github.com/topjohnwu/Magisk/releases
Magisk is optional if you want/like root.
Download to your PC TWRP_3.5.2_9_SM-T710_20210719_Unofficial.tar from retiredtab - Browse /SM-T710/TWRP at SourceForge.net (T710) or twrp-3.5.2_9-0-gts210wifi.img.tar from Download TWRP for gts210wifi (T810)
Download to your PC Odin, from https://technastic.com/wp-content/uploads/2020/02/Odin3_v3.14.4.zip, and extract the zip.
Step 2 – Install TWRP Recovery
Power off your Tab S2.
Launch Odin on your PC and press OK.
Power up your Tab S2 into Download mode by holding down Home+VolDown+Power.
Then at the Warning screen hit VolUp.
Connect your Tab S2 via USB to your PC, and you should see Added!! in Odin.
Click AP in Odin and select the downloaded TWRP.
In Odin Options, uncheck Auto Reboot.
Click Log tab again.
Click Start in Odin.
Installing TWRP only takes a couple of seconds.
You will see progress in the Log, and Pass at the top of Odin when done.
Step 3 – First boot into TWRP
This part is tricky!
Power down your Tab S2 by holding down VolDown+VolUp+Power.
IMMEDIATELY the screen goes blank, hold down Home+VolUp+Power.
Keep holding down until you see the TWRP home page.
If you end up booting into Android rather than TWRP then you will have to repeat Step 2 and Step 3 again.
Step 4 – Backup your stock ROM
In TWRP, select Backup, Select Storage to choose your micro-SD card, check all the partition boxes, and then swipe Backup.
Confirm your backup is good
In TWRP, select Wipe, then Advanced Wipe.
Select all partitions except Micro SD Card (and USB OTG).
Swipe to Wipe.
Back, Back again, then Format Data
Type yes, and tap check.
Back, Back, Back, and select Restore.
Select Micro SD card and your backup.
Restore all partitions and allow restore to complete.
Reboot to System, and confirm you are back to stock.
Step 5 – Install ROM and NikGApps
In TWRP, select Wipe, then Advanced Wipe.
Select all partitions except Micro SD Card (and USB OTG).
Swipe to Wipe.
Back, Back again, then Format Data
Type yes, and tap check.
Back, Back, Back, and select Install.
Select your micro-SD storage.
Select the Lineage-19.1 ROM.
Add more Zips, and select nikgapps.
Swipe to confirm Flash.
Install takes about 3 minutes.
Wipe Cache/Dalvik, and Swipe to Wipe.
Reboot System.
Step 6 – Build your Android 12 Tab S2
First boot into Lineage is less than a minute, and then the Lineage boot animation takes less than 1 minute before “Welcome to LineageOS” appears.
At the end of the initialization process, be sure not to choose the Replace Lineage Recovery option, otherwise TWRP goes away.
Set up your Android device per your preference. I am a mainstream Google/Google Play Apps user, and I have loads of Apps, so it takes me a long time to install my Apps and set the tablet up for daily use. If you are less of a pack-rat, it shouldn’t take long!
I have found that, by not installing Magisk initially, I can restore all my Apps, including the sensitive ones such as Peacock, Netflix, Disney+, etc. All Apps run normally, and when I check Google Play/Settings and scroll to the bottom, I see “Device is certified”.
I recommend leaving tablet completely alone during the initial Apps and Data restore process. When I get impatient and fiddle around as it’s copying I’ve seen crashes.
Once all copying is done, do your unique Android setup. My go-to Android settings are:
Nova Prime Launcher (actually, gets selected during the initialization process, but I load my layout from backup at this time)
Microsoft Swiftkey
Screen timeout 30 minutes, and screen saver Clock
Dark theme off
Disable taskbar.
Plain dark blue wallpaper
Touch, screen locking, and charging sounds off
Battery %age next to icon
Default USB = File Transfer
Developer Options enabled, and USB and Rooted debugging selected
Window/Transition/Animator Scale all set to Animation Off
FX File Explorer
Microsoft Edge as default browser (with AdBlock enabled and Google as search and sync to my PC)
Raindrop, for all my cross-platform/device bookmarks
Advanced restart menu (to allow reboot into TWRP).
Step 7 – Make Root – Optional
Restart Tab S2 into TWRP.
In TWRP, install Magisk-v25.2.apk.
Reboot System
In Android install Magisk-v25.2.apk.
Open Magisk and select zygisk in settings.
Restart again.
You now have root. I test by enabling root in FX File Explorer and granting root.
Step 8 – All done! Enjoy!
I do a final and full TWRP backup once the device is solid on Lineage 19.1.

On lineage-19.1-20220811-UNOFFICIAL-gts28wifi.zip I don't have an onscreen keyboard. I rebooted into TWRP and tried the GBoard Add On, but after that stil no onscreen keyboard. Installed it with NikGapps core and retried with full. If you use full, something from Google keeps crashing.
In system settings with full NikGapps, only keyboard available is Google speak option.
Both were Clean Installs.

djcasl said:
I don't have an onscreen keyboard.
Click to expand...
Click to collapse
We found another way to workaround the missing on screen keyboard. @lpedia tested with the Google login accounts and I tested it with Bluetooth numeric PIN. It's documented back in post 1 to say
=== begin ===
keyboard bug workaround. When prompted to enter something like a Bluetooth pin or text based password, sometimes the keyboard is not shown on the screen or off screen. The workaround is to goto settings, system, languages & input, on-screen keyboard, Android Keyboard (AOSP), appearance & layout, theme and choose "Material - follow system settings".
=== end ===

retiredtab said:
We found another way to workaround the missing on screen keyboard. @lpedia tested with the Google login accounts and I tested it with Bluetooth numeric PIN. It's documented back in post 1 to say
=== begin ===
keyboard bug workaround. When prompted to enter something like a Bluetooth pin or text based password, sometimes the keyboard is not shown on the screen or off screen. The workaround is to goto settings, system, languages & input, on-screen keyboard, Android Keyboard (AOSP), appearance & layout, theme and choose "Material - follow system settings".
=== end ===
Click to expand...
Click to collapse
I can try again. However, I went to languages and input and there was no keyboard option whatsoever. I tried manage keyboards, but could not activate one as well. To me it looked like there was no onscreen keyboard installed at all. So I couldn't use this workarround.
Update:
So I reinstalled, but one thing I didn't do is change initial language to Dutch. So now I am going see if I can restore my device, but so far it hasn't found my backup. Or asked to restore it. Don't know how I can reinitilaze that if not asked at setup.
Update 2: Reinstalled with NikGapps Omni this should have google setup and google restore. But didn't get question to add google account during setup. After adding account didn't get a question to restore data.

New build called lineage-19.1-20220911-UNOFFICIAL-gts28wifi.zip
NOTE: lpedia has personally tested each build on his 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 in TWRP. This is known has a clean install. Backup your data before a clean install.
Sept 11, 2022 release notes
1. YOU MUST read posts 1-4 if you haven't already.
2. Sept 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-09
3. Removed settings menu option for fast charging. S2 tablet devices do not support this.
https://github.com/retiredtab/andro...mmit/8068a4a66ae7c576973807b392e686110126150c

Error!

retiredtab said:
New build called lineage-19.1-20220911-UNOFFICIAL-gts28wifi.zip
NOTE: lpedia has been personally tested each build on his 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 in TWRP. This is known has a clean install. Backup your data before a clean install.
Sept 11, 2022 release notes
1. YOU MUST read posts 1-4 if you haven't already.
2. Sept 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-09
3. Removed settings menu option for fast charging. S2 tablet devices do not support this.
https://github.com/retiredtab/andro...mmit/8068a4a66ae7c576973807b392e686110126150c
Click to expand...
Click to collapse
Thanks for the charging fix. Now my tablet does not get hot while charging. That's great!
But the charge does not show more than 76%. I have left it for 2 days untouched but it does not go above 76%. It did this even before the 9/11/22 version. Unless I need to recalibrate battery??? Never had to do that before.

chappatti said:
But the charge does not show more than 76%. I have left it for 2 days untouched but it does not go above 76%. It did this even before the 9/11/22 version. Unless I need to recalibrate battery??? Never had to do that before.
Click to expand...
Click to collapse
I suggest the following:
1. boot into TWRP and see what the battery % is. If it's not 100%, let it charge to 100%.
2. After charged to 100%, boot into OS and see if it's at 100%.
3. If OS shows 100%, it's fixed. If not, repeat steps 1 and 2 at least 3 more times.

retiredtab said:
I suggest the following:
1. boot into TWRP and see what the battery % is. If it's not 100%, let it charge to 100%.
2. After charged to 100%, boot into OS and see if it's at 100%.
3. If OS shows 100%, it's fixed. If not, repeat steps 1 and 2 at least 3 more times.
Click to expand...
Click to collapse
ha! will try....

retiredtab said:
I suggest the following:
1. boot into TWRP and see what the battery % is. If it's not 100%, let it charge to 100%.
2. After charged to 100%, boot into OS and see if it's at 100%.
3. If OS shows 100%, it's fixed. If not, repeat steps 1 and 2 at least 3 more times.
Click to expand...
Click to collapse
Still does not charge to 100% outside Twrp.
OK. So in Twrp it goes to 100% and on reboot it says 100% . But then again when it discharge, it will not charge above 76%. I repeated the process, but outside Twrp it does not charge above 76%.
Any ideas??

chappatti said:
Still does not charge to 100% outside Twrp.
OK. So in Twrp it goes to 100% and on reboot it says 100% . But then again when it discharge, it will not charge above 76%. I repeated the process, but outside Twrp it does not charge above 76%.
Click to expand...
Click to collapse
I'll answer the above in the T810 thread since that's what you have, but @lpedia and I have been using the 19.1 T710 since mid April and we would have noticed if it stops charging at 76%. I'll let lpedia comment since he uses the 19.1 T710 as a daily driver more than I do.

New build called lineage-19.1-20221010-UNOFFICIAL-gts28wifi.zip
NOTE: lpedia has personally tested each build on his 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 in TWRP. This is known has a clean install. Backup your data before a clean install.
Oct 10, 2022 release notes
1. YOU MUST read posts 1-4 if you haven't already.
2. Oct 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-10

it charges just fine for me

haircut313 said:
it charges just fine for me
Click to expand...
Click to collapse
Just for reference, the charging weirdness was not a device or ROM issue. It was on a T810 (the report of the issue was posted to this thread by accident), and was discussed on the T810 LOS 19.1 thread. It turned out that the device had an app that was interfering with battery charging. Removing that app fixed the problem.

Its working so smooth I like it! The only problem I found is the audio when I play videos in VLC player, didn't play the audio. Can't hear anything. ah! And sometimes my tablet reboots

Kyrat said:
Its working so smooth I like it! The only problem I found is the audio when I play videos in VLC player, didn't play the audio. Can't hear anything. ah! And sometimes my tablet reboots
Click to expand...
Click to collapse
@Kyrat - does VLC audio work otherwise, eg to play music? If not, you probably have the same problem as I came across with some versions of VLC. There's no audio output at all with VLC's default audio output method, AudioTrack. Changing that to OpenSL ES fixed the problem for me.
That setting is in VLC Settings > Extra settings > Audio > Advanced > Audio output.

[UNOFFICIAL][ROM]BETA LineageOS 18.1 for SM-T813 - June 9, 2023

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.
This is ONLY for the T813. I do not have and will NOT build T713, T719 and T819. See post #2, FAQ 20. Any questions asking to build these will be ignored.
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
9. deep sleep
10 DRM level 3 (SD definition)
Known issues/What doesn't work/what's not tested
NOTE: If any following features are important to you, don't use this rom as I will not be fixing them because I
i. don't use/need that feature
ii. already tried fixing it and couldn't succeed and won't spend anymore time on it.
1. Stock camera doesn't work at all (reason i and ii). Opencamera version 1.51.1 works for taking pictures and videos BUT with a 10 to 15 second delay when switching between functions.
I have not tested any video conferencing apps so they may or may not work. If they don't work, revert back to old rom as I will not be spending anytime trying to fix/troubleshoot.
2. fingerprint (reason i). I never use it and I see it doesn't even load correctly in the logs.
3. ARM64 gapps (reason i). Some of you require gapps for whatever reason. I use Aurora Store for my purposes and thus have NO KNOWLEDGE of the current state of ARM64 gapps.
There are various gapps projects (at least 5 in 2023). Each has pros and cons. It's your job to do the research and find a suitable gapps project. I suggest you allocate at least a couple of hours/days doing your own research. My rom works by itself fine without gapps. DO NOT talk about gapps in this thread. As a courtesy to gapps users, I have opened a new thread at
https://forum.xda-developers.com/t/...o-use-discussion-for-18-1-rom-sm-t813.4540423
so you may discuss gapps. I will NOT be participating in that thread as I do NOT use gapps.
4. disk encryption (reason i). Never tested.
5. If you restart the device with the purpose to reboot it and the usb cable is plugged in, the device will not reboot and stay in charging mode. Simply unplug the usb cable, wait 15 seconds and restart the device.
Source code
All the source code including the kernel is provided in post #2 FAQ1.
Thanks
1. LineageOS team for source code.
The rest in alphabetical order.
2. @Deltadroid for updating the msm8976 kernel for branches 14.1 and 16.0 with bug and security fixes. I'm using his 16.0 branch.
3. @lifehackerhansol for suggesting that I kang the pm-* proprietary blobs from another rom and making suggestions for possible fixes to the camera.
4. Team Infusion Developers github.

FAQ - I spent hundreds of hours building this rom. 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
https://github.com/syphyr/android_kernel_samsung_msm8976/tree/lineage-16.0
The device tree files are at
https://github.com/retiredtab/android_device_samsung_msm8976-common
https://github.com/retiredtab/android_device_samsung_gts210vewifi
The vendor tree files are at
https://github.com/retiredtab/proprietary_vendor_samsung_msm8976
The manifest.xml (or roomservice.xml) and build instructions for 18.1 are at
https://github.com/retiredtab/LineageOS-build-manifests/tree/main/18.1
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 Oct 2022 with no major issues. I suggest you do a clean install, see FAQ 11, and flash this ROM BY ITSELF (no gapps, magisk, etc) and see if you like it.
Q3. What if my app, xyz, doesn't work?
A3. If your app doesn't work, then go back to your old rom.
Q4. Your rom is laggy and buggy.
A4. If you find the above, then go back to your old rom. Your tablet will also run slower when you use gapps. 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.6.2_9-0. Do not use any other version for these reasons.
https://forum.xda-developers.com/t/...or-sm-t810-jan-11-2023.4430349/#post-86745013
https://dl.twrp.me/gts210vewifi/
I will not answer questions if you don't use this exact TWRP version.
Q6. Why should I use this rom?
A6. If you don't like this rom, then don't use it.
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. I don't have the time to help newbies, so please 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. In addition, I don't run Windows OS at all.
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
# attach the problem.txt ZIPPED as text files don't seem to get attached properly
Q10. Will you build 19.1 and higher for this device?
A10. Any questions on higher Android versions will be completely ignored. I do this in my free/spare time and will not be subject to any ETAs or demands. If you want a higher version, the source code is freely available as per FAQ #1 and you can build it yourself.
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.
You MUST FORMAT DATA in TWRP so backup your files first to some external storage (external microsd or PC).
NOTE: After you do the above, first boot (without gapps, magisk, etc) will take about 90 seconds. It may pop with a message saying "System UI isn't responding". Hit close app and then reboot the tablet again.
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.
Let me by crystal clear. YOU NEED TO DO YOUR OWN HOMEWORK selecting between the various ARM64 gapps offered. There are 5: opengapps, nikgapps, mindthegapps, flamegapps and bitgapps. Each one will have it's own installation instructions. The only recommendation I will offer to use the SMALLEST version of gapps.
Don't be surprised that whatever gapps you use might have problems like "Just a sec", voice not working, updating google play store please wait, etc. These are NOT problems of the OS as the OS will run fine without gapps. These are gapps problems and you must ask in the gapps forum why it doesn't work.
In addition, some of the gapps may not install properly when using TWRP and say "cannot /mnt/system".
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. Android does not depend on gapps in order to work.
Questions about gapps, for your courtesy, should be asked in the thread below.
https://forum.xda-developers.com/t/...-use-discussion-for-18-1-rom-sm-t813.4540423/
Q14. Why isn't my post answered or ignored?
A14. Questions already answered in the FAQ will be completely ignored. Again, I do not use Windows OS or gapps.
Q15. What speed up/optimization tips do you suggest?
A15.
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. Use a web browser like Brave that has built in adblock and privacy features.
4. Use newpipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
5. Look for apps that are open source, ad free and lightweight.
Q16. Does this rom support Magisk for root?
A16. I don't use Magisk. Magisk is always being updated to fool Google's certification process which may or may not work.
Q17. Will this rom ever become official?
A17. Never. I don't want the responsibilities that come with being an official maintainer.
Q18. What is the difference between this rom and others?
A18. This rom tries to be pure LineageOS with little to no modifications.
Q19. Will there be any major 18.1 code modifications in the future?
A19. I don't anticipate any major modifications. There may be some 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 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.
Q20. Can you build a variant of this device? For example, a LTE or S-pen version.
A20. 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. To be clear, I will NOT build T713, T719 and T819.
Q21. Can I load this rom on a variant devivce like LTE or S-pen version?
A21. 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!
Q22. Does this rom support OTA updates?
A22. No and I have no plans to add that functionality.
Q23. 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?
A23. You can download it from
https://sourceforge.net/projects/retiredtab/files/SM-T813/18.1/

Release Notes
I have personally tested all the functionality as to what works as per post #1 before uploading the build. 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 9, 2023 release notes
1. Incorporates June 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-06
2. Whatever LineageOS changed since May 5th patches (about 5,600 files had to be recompiled).
May 7, 2023 release notes
1. Incorporates May 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-05
2. Whatever LineageOS changed since Apr 5th patches (about 6,600 files had to be recompiled).
Apr 15, 2023 release notes
1. Incorporates Apr 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-04
2. Whatever LineageOS changed since Mar 5th patches (about 4,500 files had to be recompiled).
3. Updated aptX code so that it works and stops crashing (broken in 17.1) as per https://github.com/retiredtab/propr...mmit/3f6bd0d979ae25e3ba23e2c214fa7207c81f6b32
March 17, 2023 release notes
1. Incorporates Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-03
2. Whatever LineageOS changed since Feb 5th patches (about 24,000 files had to be recompiled).
3. Added overlay to control capactive key light buttons to enable/disable or change duration as per
https://github.com/retiredtab/andro...mmit/5a2649a040adfb879fd03076f97dd5321c5e27e6
Feb 13, 2023 release notes
1. Incorporates Feb 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-02
2. Whatever LineageOS changed since Jan 5th patches (about 13,000 files had to be recompiled).
3. Updated DRM code so that Disney+ works. See
https://github.com/retiredtab/andro...mmit/6c41d16cf1a8b2e8c436b3bef922a47e606381ee
https://github.com/retiredtab/propr...mmit/fed0f34d48330908165f78051066127b0e1870d8
Jan 7, 2023 release notes
1. Initial release of 18.1
2. Incorporates Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-01
3. If you are upgrading from a custom rom, stock or any older versions of LineageOS (like 14.1, 16.0 or 17.1) YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA in TWRP. You cannot dirty flash at all. Backup your data first.

Reserved #4

I have personally tested all the functionality as to what works as per post #1 before uploading the build. 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 has been my daily driver since Oct 2022.
Jan 7, 2023 release notes
1. YOU MUST read posts 1-4 if you haven't already.
2. Incorporates Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-01
3. If you are upgrading from a custom rom, stock or any older versions of LineageOS (like 14.1, 16.0 or 17.1) YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA in TWRP. You cannot dirty flash at all. Backup your data first.

Thanks for all your efforts. I never thought anything above Android 10 would see the light of days on the T813 model, since it was highly neglected here in my opinion. I will definitly try it out

THANK YOU "RETIREDTAB" this is awesome!
I will try it out on my T813 and report back here if there are any problems, Thanks a lot for this rom!!!

@retiredtab, many, many thanks for this rom. Have done a full clean install, the backup of the previous 17.1 took longer. So far everything I need to use is working perfectly. I mainly read the news, pick up emails and buy too much stuff from amazon.
went with the opengapps pico set, and all my google stuff is working, and it restored my apps from the previous backup. Did have some odd issues giving permissions to to the various google apps but once that was sorted it ran.
keep up the good work, and will keep testing

Further update after a weekend of use, the screen off battery drain seems to be minimal(may be Greenify helping) but appears to be better than I had on the previous 17.1 rom. No other issues found as yet.

will the camera issue be adressed or it will stay like that?

Ferchurito said:
will the camera issue be adressed or it will stay like that?
Click to expand...
Click to collapse
I'd say its unlikely to change, far as I know its never been fixed in the previous 17.1 rom either. As retiredtab mentions in point 1, camera use is not a big need or he has alrady tried to fix it and not been able to.

I did everything wrong with a working result:
-My Starting point: LineageOS 17.1 (ripee) installed
- Backup of User Data @ Android System (copy to MicroSD)
- Updated the TWRP version to the recommended in TWRP (coming from ripee version for 17.1)
- Boot to System to ensure it's still working
- Backup everything in TWRP
In one batch without booting in between:
- I dirty flashed "lineageOS 18.1" over "lineageOS 17.1 (from ripee)"
- Flashed the Arm64 version for Android 11 of "mindTheGapps" over existing "OpenGapps (for Android 10)"
- Flashed Magisk *.zip
- Deleted Cache and Dalvik
Boot to system and it's working perfectly so far
FYI.: Camera App "ProcamX" is working as well.
FYI.: Especially for lineageOS 17.1 users: I can confirm GPS is working (GPS Test Plus)
For sure I wouldn't recommend this procedure and maybe I will do a clean install later to gain smoothness and to make it stable in general but so far it's super nice, no bootloop, random restarts (BUT it's based on a few hour usage only) or whatever and a big thank you to ritiredtab

I have Magisk and safetynet pass flashed. I can download Netflix from Playstore but it doesn't play any content. It seems that Widevine / DRM is not part of the ROM at all as the App "DRM Info" doesn't show any Widevine information. In consequence Netflix doesn't play and stuck in "loading". Anyway it seems to enable some old DRM blobs can fix the issue like at least for L3 which is SD playback. Something like here needs to be added I think....:
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/339185
Didn't dig deeper into the topic so far. Just want to share the info.

Renzke said:
It seems that Widevine / DRM is not part of the ROM at all as the App "DRM Info" doesn't show any Widevine information.
Click to expand...
Click to collapse
As I listed in post #1, DRM L3 works as I check/test/verify ALL my public xda builds for the functionality in post #1 before uploading.
Here's the results of checking DRM with 4 different programs. Devcheck by flar2 is what I use to check all my ROMS for a variety of values and widevine DRM L3 (along with clearkey) is clearly shown. Device Info HW and DRM Check also show widevine properly.
DRM Info by Android Fung is the only one that cannot show the widevine information which may be due to a bug in this program or it's poorly written and being denied by selinux enforcing.
DevCheck and Device Info HW are both ad free while DRM Check and DRM Info are infested with ads. The latter 2 are programs I will never use again.
In addition, DRM Info by Android Fung shows this in the logcat
Code:
GooglePlayServicesUtil: com.androidfung.drminfo requires the Google Play Store, but it is missing.
As I mentioned several times, I do NOT and will NOT install any gapps.
Your link to gerrit regarding DRM is already in my code (done a bit differently, but works as clearly shown by Devcheck).
https://github.com/retiredtab/propr...mmit/92ecf0f7615a291281e4b39da6be956e92e66d82
https://github.com/retiredtab/andro...mmit/5a91ac3d5d14510b335f8d6ec650b254edcdb2dc

@retiredtab Thanks for the detailed reply. You are right. I See Widevine L3 in other Apps as well. Shame on me '-'. Even Netflix itself gives this Info... Anyway... Playback is not starting while preview videos are working. Tried already a couple of versions without success and checked the permissions. As I'm customized with Magisk the rootcause could be on my side for sure. Prime Video is working by the way. Would be nice to know if a clean install has the same behaviour.

Renzke said:
@retiredtab I See Widevine L3 in other Apps as well.
Click to expand...
Click to collapse
There's a reason why I always recommend clean installs. When you don't do it, it leads to unexplained problems. If Prime is working, that suggests DRM L3 is working.
If a clean install doesn't work with Netflix, then see FAQ 9 and send me the logs (zipped). There's no guarantee that it will show anything wrong or if I can fix it. I don't have/use Netflix or any other $treaming service.
Having said that, I do build other roms like the T810 (S2 2015 exynos model) and others have commented that they do not need Magisk hide, root, etc to get Netflix shown in the playstore because my T810, like this T813, is selinux enforcing. They report that the T810 shows up as "device is certified".
Again, since I don't use gapps, I cannot confirm if "device is certified" is true for T813, but if it is, then Netflix should show up without Magisk/hide, root, etc. If it does show up, it's a bonus. If the T813 shows up as "device not certified", I have no plans to fix this as I don't use gapps.

@retiredtab I'm not sure if I will do a clean install as the system is working quite well expect Netflix and at the end of the day it's not super important for me. In case I do a clean install I will provide a log and be thankfull for the offer to fix things
The chances to have an indication is maybe low in the logs as Netflix loops in the loading screen without an error at all. Anyway I don't want to waste your time with this topic currently as I cleary didn't follow your instructions by doing a dirty flash and so on. And again... Super nice to have this rom which gives my tablet a 2nd life. Thanks a lot.

Renzke said:
@retiredtab I'm not sure if I will do a clean install as the system is working quite well expect Netflix and at the end of the day it's not super important for me. In case I do a clean install I will provide a log and be thankfull for the offer to fix things
The chances to have an indication is maybe low in the logs as Netflix loops in the loading screen without an error at all. Anyway I don't want to waste your time with this topic currently as I cleary didn't follow your instructions by doing a dirty flash and so on. And again... Super nice to have this rom which gives my tablet a 2nd life. Thanks a lot.
Click to expand...
Click to collapse
I don't really care about using Netflix on this device, but figured I'd let you know that I'm having the same issues after a clean flash. Will try and grab a log later.

I have this strange problem
I have two tablets SM-T813 and SM-T819.
I installed Lineage os 18.1 on SM-T813 and SM-T819 (I modified the installer). On the T813 it booted without any problems. On the T819, on the other hand, it stands in bootloop. I went into recovery and there were no files in INTERNAL STORAGE, it was empty. To T819 I need to install some file or something so that it can start reading Memory and come out of bootloop?

K-BOX2022 said:
On the T819, on the other hand, it stands in bootloop.
Click to expand...
Click to collapse
As I mentioned in the FAQ, there's nothing I can do without the T819 physically in my hands. If the T813 worked on T819, then it's a bonus. If not, it was worth a try.

[UNOFFICIAL][ROM]ALPHA LineageOS 20 for SM-T813 - June 23, 2023

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.
This is ONLY for the T813. I do not have and will NOT build T713, T719 and T819. See post #2, FAQ 20. Any questions asking to build these will be ignored.
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 ,boot loop, complete loss of data 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
9. deep sleep
10 DRM level 3 (SD definition)
Known issues/What doesn't work/what's not tested
NOTE: If any following features are important to you, don't use this rom as I will not be fixing them because I
i. don't use/need that feature
ii. already tried fixing it and couldn't succeed and won't spend anymore time on it.
1. Stock camera doesn't work at all (reason i and ii). Starting with LineageOS 19.1 and higher, camera API functionality (pictures and videos) isn't even recognized by the OS.
2. fingerprint (reason i). I never use it and I see it doesn't even load correctly in the logs.
3. ARM64 gapps (reason i). Some of you require gapps for whatever reason. I use Aurora Store for my purposes and thus have NO KNOWLEDGE of the current state of ARM64 gapps.
There are various gapps projects (at least 5 in 2023). Each has pros and cons. It's your job to do the research and find a suitable gapps project. I suggest you allocate at least a couple of hours/days doing your own research. My rom works by itself fine without gapps. DO NOT talk about gapps in this thread.
4. full disk encryption has been deprecated in Android 13 (LineageOS 20).
5. If you restart the device with the purpose to reboot it and the usb cable is plugged in, the device will not reboot and stay in charging mode. Simply unplug the usb cable, wait 15 seconds and restart the device.
Source code
The kernel source code is at
https://github.com/syphyr/android_kernel_samsung_msm8976/tree/lineage-16.0
All the source code including the kernel, device trees, manifest and build instructions are provided in post #2 FAQ1.
Thanks
1. LineageOS team for source code.
2. LineageOS-UL team for merging, maintaining the legacy patches needed for old devices into one common reposistory so everyone can benefit.
https://github.com/orgs/LineageOS-UL/people
3. @Deltadroid for updating the msm8976 kernel for branches 14.1 and 16.0 with bug and security fixes. I'm using his 16.0 kernel branch for my 20 builds.

Frequently Asked Questions. You MUST READ this before posting any questions. If you think this is unreasonable, then find another rom. Thank you.
Q1. Where are the source and kernel source files?
A1. The kernel source files are at
https://github.com/syphyr/android_kernel_samsung_msm8976/tree/lineage-16.0
The device tree files are at
https://github.com/retiredtab/msm8976-common/tree/lineage-20
https://github.com/retiredtab/gts210vewifi/tree/lineage-20
The vendor tree files are at
https://github.com/retiredtab/proprietary_vendor_samsung_msm8976
The manifest.xml (or roomservice.xml) and build instructions for LineageOS 20 are at
https://github.com/retiredtab/LineageOS-build-manifests/tree/main/20/msm8976
Q2. Is this ALPHA 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 Jan 2023 with no major issues. I suggest you do a clean install, see FAQ 11, and flash this ROM BY ITSELF (no gapps, magisk, etc) and see if you like it.
Q3. What if my app, xyz, doesn't work?
A3. If your app doesn't work, then go back to your old rom.
Q4. Your rom is laggy and buggy.
A4. If you find the above, then go back to your old rom. Your tablet will also run slower when you use gapps. 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.6.2_9-0. Do not use any other version including the "latest".
https://dl.twrp.me/gts210vewifi/
I will not answer questions if you don't use this exact TWRP version.
Q6. Why should I use this rom?
A6. If you don't like this rom, then don't use it.
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. I don't have the time to help newbies, so please 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. In addition, I don't run Windows OS at all.
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
# attach the problem.txt ZIPPED as text files don't seem to get attached properly
Q10. Will you build Android 14 and higher for this device?
A10. Any questions on higher Android versions will be completely ignored. I do this in my free/spare time and will not be subject to any ETAs or demands. If you want a higher version, the source code is freely available as per FAQ #1 and you can build it yourself.
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 20 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.
You MUST FORMAT DATA in TWRP so backup your files first to some external storage (external microsd or PC).
NOTE: After you do the above, first boot (without gapps, magisk, etc) will take about 90 seconds. It may pop with a message saying "System UI isn't responding". Hit close app and then reboot the tablet again.
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.
Let me by crystal clear. YOU NEED TO DO YOUR OWN HOMEWORK selecting between the various ARM64 gapps offered. There are 5: opengapps, nikgapps, mindthegapps, flamegapps and bitgapps. Each one will have it's own installation instructions. The only recommendation I will offer to use the SMALLEST version of gapps.
Don't be surprised that whatever gapps you use might have problems like "Just a sec", voice not working, updating google play store please wait, etc. These are NOT problems of the OS as the OS will run fine without gapps. These are gapps problems and you must ask in the gapps forum why it doesn't work.
In addition, some of the gapps may not install properly when using TWRP and say "cannot /mnt/system".
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. Android does not depend on gapps in order to work.
Q14. Why isn't my post answered or ignored?
A14. Questions already answered in the FAQ will be completely ignored. Again, I do not use Windows OS or gapps.
Q15. What speed up/optimization tips do you suggest?
A15.
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. Use a web browser like Brave that has built in adblock and privacy features.
4. Use newpipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
5. Look for apps that are open source, ad free and lightweight.
Q16. Does this rom support Magisk for root?
A16. I don't use Magisk. Magisk is always being updated to fool Google's certification process which may or may not work.
Q17. Will this rom ever become official?
A17. With 19.1 and up, legacy devices like ours will NEVER be official due to lack of ebpf support. See https://lineageos.org/Changelog-26/
Q18. What is the difference between this rom and others?
A18. This rom tries to be pure LineageOS with little to no modifications.
Q19. Will there be any major 20 code modifications in the future?
A19. I don't anticipate any major modifications. There may be some 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 completed. This doesn't mean the code is perfect or well organized, but I won't be doing any major changes now that 20 is working.
Q20. Can you build a variant of this device? For example, a LTE or S-pen version.
A20. 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. To be clear, I will NOT build T713, T719 and T819.
Q21. Can I load this rom on a variant devivce like LTE or S-pen version?
A21. 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!
Q22. Does this rom support OTA updates?
A22. No and I have no plans to add that functionality.
Q23. Why is there no LineageOS 19.1 build?
A23. I actually had a private 19.1 build back in Dec 2022, but stock camera didn't work at all so I decided to try build 20 to see if stock camera works in 20 (it does not either). Since I'm the sole builder for 18.1 and 20, I don't want to build, maintain and test 3 roms each month. Since 19.1 and 20 are very similar, I decided to just do 20 and drop 19.1 altogether. For those that need stock camera to work, use 18.1 (with caveats) or another rom where it works properly.
Q24. Okay, I understand the consequences and that this is ALPHA rom and willing to take the risks outlined, now where can I find the rom?
A24. You can download it from
https://sourceforge.net/projects/retiredtab/files/SM-T813/20/

Release notes
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 in TWRP. This is known has a clean install. Backup your data before a clean install.
June 23, 2023
1. Initial 20 ALPHA public release.
2. Incorporates June 5th security patches as per https://review.lineageos.org/q/topic:"T_asb_2023-06"
3. If you are coming from stock rom or an older LineageOS version (example, 18.1), you MUST format your data in TWRP. Remember to backup your data and verify that restore data works before upgrading to 20.

Reserved.