[UNOFFICIAL][ROM]BETA LineageOS 18.1 for SM-T810 - June 11, 2022

Search This thread

retiredtab

Senior Member
Nov 16, 2017
1,113
674

LineageOS 18.1 UNOFFICIAL for 2015 Samsung Galaxy Tab S2 SM-T810 ONLY​

Model: SM-T810 (wifi) - gts210wifi - 9.7" 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. 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. Yogi555 for building the public T810 monthly roms starting April 2022
7. lpedia for suggestions, proof reading and FAQ table format in post #2.
 
Last edited:

retiredtab

Senior Member
Nov 16, 2017
1,113
674
Frequently Asked Questions. You MUST READ this before posting any questions. Thank you.

QuestionAnswer
Q1. 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_gts210wifi

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/22fd53a977eeaf4e36be7bf6358ecf2c2737fa5e
Q2. 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 TWRP 3.5.2_9. Get it from

https://dl.twrp.me/gts210wifi/
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. Yogi555 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 make a guide in in post #16.
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 May 5 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 #14. 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/retiredtab/files/SM-T810/18.1/
 

Attachments

  • gts.xml
    1.5 KB · Views: 10
Last edited:

retiredtab

Senior Member
Nov 16, 2017
1,113
674
Monthly release notes

June 11, 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 10, 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 10, 2022
1. YOU MUST read posts 1-4 if you haven't already

2. First public BETA release of selinux enforcing T810 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.
 
Last edited:

retiredtab

Senior Member
Nov 16, 2017
1,113
674
Initial public build called lineage-18.1-20220410-UNOFFICIAL-gts210wifi.zip. The sha256sum file is provided as well to ensure integrity of download.

Yogi555 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 10, 2022
1. YOU MUST read posts 1-4 if you haven't already

2. First public BETA release of selinux enforcing T810 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.
 
Last edited:

dcaffeine8d

Senior Member
Tried the beta build and everything seems to be working. I'll observe once it goes into deep sleep and see if WiFi will lose connection (usually 24 hours) on the other 18.1 build. Loaded all my paid apps without issues. Only gripe is the Netflix with DRM L3. Will look into another thread where they spoofed it.
 
  • Like
Reactions: CuckooPenguin
@retiredtab, @ananjaser1211, @lpedia, @Yogi555 and @CuckooPenguin thx very much for your work.
Until yesterday mine was on ripees build from 20211103 which was stable and working but didn't seem to get any further updates than 20211208.
Clean installation went well although I didn't follow "Q5" and used latest TWRP which is 3.6.1_9-0.
Flashed it with Magisk 23. (wanted to make sure that Gapps didn't interfere)
1st boot was fast, setting it all up.
Looking in settings for button backlight duration but didn't find it (using it in the night and want them to light up as short as possible).
Wifi connection there as soon as it wakes up.
So I gave BitGapps a go and flashed ARM64 which worked (isn't specified in "Q12" and as far as I remember only ARM worked on ripees build).
Fiddling around a bit installing paid apps and others.
Everything seems to be fine especially for a beta version.

For others who want to change from ripees version to this one:
On mine it worked to restore "Data" via TWRP (partition got wiped again before) what makes it much easier to switch.
Each app I use seems to be working under the new ROM without problems.

Fun fact: button backlight after restoring is as short as it was set in the prior ROM.
 
Last edited:

retiredtab

Senior Member
Nov 16, 2017
1,113
674
Clean installation went well although I didn't follow "Q5" and used latest TWRP which is 3.6.1_9-0.
The reason I write MUST is that not all TWRP from the official TWRP site work properly. For example, when I was initially building the 18.1 tree back in July/Aug 2021, I needed mtp and adbd to work in TWRP T710 for debugging purposes.

Despite the change log claiming both were fixed, not a single version worked wrt mtp and adbd. I knew this way back in Dec 2020 and you may have even seen my post #124 since you were post #122 and #126 in the same thread.

So in order to get 18.1 up and running, I fixed TWRP T710 myself as I explain at

https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-2_9-for-samsung-sm-t710.4430335/

So for T710 users, I know my TWRP build is rock solid as I have easily used it more than 150 times when making the 18.1 rom.

Another example. During the summer of 2020, I upgraded the OS on a Samsung S4 phone for my friend. I went to official TWRP website, downloaded the latest and much to my surprise, the touchscreen didn't work at all. I used an older TWRP version and it worked fine.

Bottom line: even though it's on the official TWRP website does not mean it's tested or working properly. In the case of the S4 TWRP with the non working touchscreen, it's obvious there was zero testing done.

That's why we will test ALL our 18.1 builds for the "what works" functionality in post #1 before uploading to the general public.
Looking in settings for button backlight duration but didn't find it (using it in the night and want them to light up as short as possible).

By sheer coincidence, I already had the above in my private build on March 27 as I wanted to test it to make sure it works before adding it into github. Yes, I test even 1 line of code change myself no matter how trivial.

The 1 line of code needed is documented at

https://review.lineageos.org/c/LineageOS/android_device_samsung_s3ve3g-common/+/292889

I will put this change into my github so that it gets built with the May 5 security patches.

Wifi connection there as soon as it wakes up.
My github repo has always had the S2 wifi blobs after @lpedia and I fixed it on Aug 7, 2021 as per

https://github.com/retiredtab/propr...mmit/3984c2ef6852794a939b8eda689fc477705d5c86

As you can see in my github history, that reversion back to S2 wifi has never changed since Aug 7, 2021.

Fun fact: button backlight after restoring is as short as it was set in the prior ROM.
Without looking through the 1000's lines of code or more, the above functionality exists probably in the hardware/samsung repo

https://github.com/LineageOS/android_hardware_samsung/tree/lineage-18.1/hidl/light

and the settings are probably saved in some directory, but the display menu for the button backlights isn't shown until I put in that one commit above. That is, the OS knows to use the saved settings, but without the menu overlay, it doesn't show the menu itself.
 
Last edited:
  • Like
Reactions: bmwdroid
The reason I write MUST is that not all TWRP from the official TWRP site work properly. For example, when I was initially building the 18.1 tree back in July/Aug 2021, I needed mtp and adbd to work in TWRP T710 for debugging purposes...

Despite the change log claiming both were fixed, not a single version worked wrt mtp and adbd. I knew this way back in Dec 2020 and you may have even seen my post #124 since you were post #122 and #126 in the same thread....
Well I gotta admit I didn't check adb and mtp in that TWRP.
I probably saw your post but might not have paid attention as they referred to T710 and as I own T810 I judged them as not relevant for me.
...
Bottom line: even though it's on the official TWRP website does not mean it's tested or working properly. ...
That's what I've noticed as well for T325.
..My github repo has always had the S2 wifi blobs after @lpedia and I fixed it on Aug 7, 2021 as per
https://github.com/retiredtab/propr...mmit/3984c2ef6852794a939b8eda689fc477705d5c86
As you can see in my github history, that reversion back to S2 wifi has never changed since Aug 7, 2021....
I just mentioned wifi functionallty for those users of T810 having problems with ripees ROM after version 20211103 and looking for a stable version regarding that feature.
 
......Without looking through the 1000's lines of code or more, the above functionality exists probably in the hardware/samsung repo

https://github.com/LineageOS/android_hardware_samsung/tree/lineage-18.1/hidl/light

and the settings are probably saved in some directory, but the display menu for the button backlights isn't shown until I put in that one commit above. That is, the OS knows to use the saved settings, but without the menu overlay, it doesn't show the menu itself.
The settings seem to be in the file /data_mirror/data_de/null/0/org.lineageos.lineagesettings/databases/lineagesettings.db

When opening in DB Browser I found:
In table "secure" the lines
46 "button_backlight_timeout" (value 1000 [probaly for milliseconds as I set it to 1s in ripees ROM]) and
47 "button_brightness" (value 1.0).

In table "system" the line
47 "button_backlight_only_when_pressed" (value 1).

Never worked with .db files myself before but for the knowing it might be interesting if they want to fiddle around a bit.
 

retiredtab

Senior Member
Nov 16, 2017
1,113
674
New build called lineage-18.1-20220510-UNOFFICIAL-gts210wifi.zip

Yogi555 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 10, 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 10 build, you may dirty flash the May 10 build. If you are NOT coming from the April 10th, 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.
 

retiredtab

Senior Member
Nov 16, 2017
1,113
674
Due to a post in the T710 regarding gapps, 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.

T710 thread post #8, #9 and #10.

https://forum.xda-developers.com/t/...neageos-18-1-for-sm-t710-may-12-2022.4430339/
 
Last edited:
I wanted to express my sincere thanks to @retiredtab and @Ipedia for your work on the ROMs for the T710 and T810. I have both devices and had previously used the @ripee versions in thread (2) [ROM][UNOFFICIAL][11] LineageOS 18.1 [T710][T715][T715Y][T810][T815][T815Y] | XDA Forums (xda-developers.com). But that 18.1 version had some noticeable bugs and wasn’t being maintained.

Thanks to @bmwdroid ’s April 15 post directing us to this forum, I have been experimenting with this ROM since then on both the T710 and the T810. Based on my pretty heavy usage, I can declare both to be excellent. Most notably, the WiFi is rock solid. The T810 and the T710 (especially) are outstanding hardware, and being able to run Android 11 is a huge boost in the device’s intrinsic value.

I have experienced a couple of random BSOD-equivalent crashes over the past month, but the tablet always immediately restarted. I am going to try and learn how to provide the necessary to the developers so, if it happens again, they can have the necessary evidence. Since I am a decent techie, but not a developer, I decided to write up the complete upgrade procedure I followed so others who come to this forum may benefit. See my next post.

PS: I put this post on both the T710 and the T810 threads since I have both devices.
 
Tab S2 T710 and T810 Upgrade Procedure Using LineageOS 18.1 ROM by retiredtab

These installation instructions work for both Tab S2 T710 and T810. I have both devices and have tested on both. I am a Windows guy, so these instructions assume a Windows PC. I am a lifelong techie guy and an Android enthusiast. But I am not developer, so these instructions should work for any competent newbie who is a decent techie, but I realize there may be alternative approaches for those who have deeper tech knowledge than me.

Step 1 – Preparation
  1. Update your Tab S2 to the latest stock software.
  2. Install a micro-SD card into your Tab S2.
  3. Enable Developer Options – tap Build Number seven times.
  4. In Developer Options, turn on USB debugging.
  5. Connect your TGab S2 to your PC via USB and download onto the micro-SD card three files:
    1. Retiredtab’s latest Lineage 18.1 ROM from lpedia-sf - Browse /gts28wifi at SourceForge.net (T710) or retiredtab - Browse /SM-T810/18.1 at SourceForge.net (T810)
    2. open_gapps-arm-11.0-pico-20220215.zip from The Open GApps Project
    3. Magisk-v24.3.apk from Release Magisk v24.3 · topjohnwu/Magisk · GitHub
  6. 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)
  7. Download to your PC Odin, from https://technastic.com/wp-content/uploads/2020/02/Odin3_v3.14.4.zip, and extract the zip.
Comments:
  • I saw retiredtab’s comments about OpenGApps quality. However, this version works well for me. I had previously tried the latest MindTheGapps (which hung) and BiTGapps (which doesn’t include the Google restore functionality that I use.)
  • Magisk is optional if you want/like root. I do!

Step 2 – Install TWRP Recovery
  1. Power off your Tab S2.
  2. Launch Odin on your PC and press OK.
  3. Power up your Tab S2 into Download mode by holding down Home+VolDown+Power.
  4. Then at the Warning screen hit VolUp.
  5. Connect your Tab S2 via USB to your PC, and you should see Added!! in Odin.
  6. Click AP in Odin and select the downloaded TWRP.
  7. In Odin Options, uncheck Auto Reboot.
  8. Click Log tab again.
  9. Click Start in Odin.
  10. Installed TWRP only takes a couple of seconds.
  11. You will see progress in the Log, and Pass at the top of Odin when done.

Step 3 – First boot into TWRP.
  1. This part is tricky!
  2. Power down your Tab S2 by holding down VolDown+VolUp+Power.
  3. IMMEDIATELY the screen goes blank, hold down Home+VolUp+Power.
  4. Keep holding down until you see the TWRP home page.
  5. If you end up booting into Android rather than TWRP then you will have to repeat steps 2 and 3 again.

Step 4 – Backup your stock ROM
  1. In TWRP, select Backup, Select Storage to choose your micro-SD card, check all the boxes, and then swipe Backup.

Step 5 – Install ROM and GApps.
  1. In TWRP, select Wipe, then Advanced Wipe.
  2. Select all partitions except Micro SD Card.
  3. Swipe to Wipe.
  4. Back, Back again, then Format Data
  5. Type yes, and hit check.
  6. Back, Back, Back, and select Install.
  7. Select your micro-SD storage.
  8. Select the Lineage-18.1 ROM.
  9. Add more Zips, and select open_gapps.
  10. Swipe to confirm Flash.
  11. Installation took about 3 minutes.
  12. Wipe Cache/Dalvik, and Swipe to Wipe
  13. Reboot System

Step 6 – Build your Android 11 Tab S2
  1. First boot into Lineage was less than a minute, and then the Lineage boot animation took less than 2 minutes before “Hello” appeared.
  2. On each build I’ve done I see “Speech services by Google keeps stopping” error once Hello appeared.
    • I assume this is one of the known OpenGApps bugs.
    • Clicking Close App makes it go away, and later Google replaces the module anyway.
  3. Set up your Android device per your preference. I have loads of Apps so it takes me a long time. If you are less of a pack-rat, it shouldn’t take long!
  4. At the end of the initialization process, be sure not to choose the Replace Lineage recovery option, otherwise TWRP goes away.
  5. I have found that, by not installing Magisk initially, Google restores all my Apps, including the sensitive ones such as Peacock, Netflix, Disney+, etc. And when I check Google Play/Settings and scroll to the bottom, I see “Device is certified”.
  6. I recommend leaving tablet completely alone until Google has finished its “Copy Apps and Data” from my other tablet. When I get impatient and fiddle around as it’s copying I’ve seen crashes.
  7. Once all copying is done, do your unique Android setup. My go-to Android settings are:
    • Nova Prime Launcher (actually, gets selected during the copy process, but I load my layout from backup at this time)
    • Microsoft Swiftkey
    • Default USB = File Transfer
    • Window/Transition/Animator Scale all set to Animation Off
    • Screen timeout 30 minutes, and screen saver Clock
    • Battery %age next to icon
    • FX File Explorer
    • Microsoft Edge as default browser (with AdBlock enabled and Google as search and sync to my PC)
    • Raindrop, for all my bookmarks
    • Advanced restart menu (to allow reboot into TWRP).

Step 7 – Make Root
  1. Restart Tab S2 into TWRP.
  2. In TWRP, Install Magisk-v24.3.apk.
  3. Reboot System
  4. In Android install Magisk-v24.3.apk.
  5. Open Magisk and select zygisk in settings.
  6. Restart again.
  7. You now have root. I test by enabling root in FX File Explorer and granting root.

Step 8 – All done!
  1. I do a final and full TWRP backup once the device is solid.

Note:
I found the fingerprint reader sometimes works to unlock the Tab S2. Per other discussions on this thread, looks like I got lucky!
 
Last edited:

lojelo

Member
Jan 21, 2022
11
1
Hi just a question regarding Q5

A5. You MUST use TWRP 3.5.2_9.

Is there a reason for this! I'm only asking because I have 3.6.0.9-0 installed so just wondered why its a must.

Edit - ignore the message above I didn't see post 9 when reading this on my tablet but do now I am on PC.
 
Last edited:

lojelo

Member
Jan 21, 2022
11
1
Had this running now for the last 5 hours, everything seems to be fine but I'm seeing very slow WiFi speeds. Coming straight from (lineage-18.1-20211103-UNOFFICIAL-gts210wifi) where I was getting a constant speed over 330mb I'm now only getting 110 dropping down to 70 at best.
 

metterschling

Senior Member
Sep 29, 2013
163
108
Nexus 7
Samsung Galaxy Tab S2
Had this running now for the last 5 hours, everything seems to be fine but I'm seeing very slow WiFi speeds. Coming straight from (lineage-18.1-20211103-UNOFFICIAL-gts210wifi) where I was getting a constant speed over 330mb I'm now only getting 110 dropping down to 70 at best.
@retiredtab Maybe just a wild guess, but might this commit be related? In my understanding argosd is a daemon that controls the CPU governor so that CPU performance can be adopted to network bandwith requirements. Shouldn't that be activated for Wifi models as well?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    4. If you are upgrading from the April 10 build or later, you may dirty flash the June 11 build.
    A warning: if you have BiTGapps installed and the BiTGapps recovery script says when you dirty-flash the ROM that BG will have to be re-installed, don't ignore that. Re-flash BiTGapps before booting the system.

    I say this from experience. My T710 went into an infinite bootanimation loop after I ignored that message and tried to reboot straight after dirty-flashing a ROM update. Once I forced it back into TWRP with "adb reboot recovery" and re-flashed BiTGapps, the reboot succeeded.

    A T810 might do the same thing.
    1
    @metterschling , thanks for spotting that. It certainly helps having another set of eyes looking at the code. Long winded answer, but I think it's important for everyone to know why changes were made and the rationale at that point in time even though 99% of the people reading this aren't coders/developers.

    begin backstory

    On Dec 29, 2020, in post 1588, I reported

    https://forum.xda-developers.com/t/...t810-t815-t815y.3879302/page-80#post-84192499

    the argos-daemon didn't work properly in 17.1 and was crashing every 5 seconds. @lpedia confirmed in post #1593.

    Then in post #1594, it was discovered by @ananjaser1211 that there was a line of code missing that made argos-daemon crash.

    Remember at that time in Dec 2020, 17.1 had serious wifi stability and reliability problems connecting after sleep or just dropping connections due to those builds using the S6 wifi blobs. The comment about making the "difference in wifi performance" wouldn't have mattered with the S6 wifi blobs.

    These wifi instability problems wouldn't be solved until lpedia and I found a solution and presented them on July 19, 2021 at

    https://forum.xda-developers.com/t/...rs-running-any-version-of-android-10.4308193/

    and then later incorporated into the 17.1 Aug 25 build. My 18.1 personal and now public builds have always had the S2 wifi blobs since day 1.

    end backstory

    The best performance I can get out of my current wifi router running OpenWrt 21.02.3 is 100Mbps using an Ipad 5 on 802.11AC. For me, that's plenty. On my T710, I get the same 100Mbps on 802.11AC. All are tested using

    https://fast.com

    to do my throughput testing. I get 300Mbps on gigabit ethernet using the same test so my wifi isn't being artifically limited to 100Mbps.

    I live in a wifi congested area and I only pay $5 for my used routers. I would rather have a bit slower wifi router and have up to date patched Openwrt software vs proprietary never updated OEM software. So if there's a performance drop between the 2 builds, I would have never noticed.

    As you can see in my Sept 3, 2021 commits, I made a number of them in order to get selinux enforcing up and going for the very first time.

    This is the message I got for argosd

    Code:
    E [c4] init: Could not start service 'argos-daemon' as part of class 'main': File /vendor/bin/argosd (labeled "u:object_r:vendor_file:s0") has
    incorrect label or no domain transition from u:r:init:s0 to another SELinux domain defined.
    Have you configured your service correctly? https://source.android.com/security/selinux/device-policy#label_new_services_and_address_denials

    I can't remember the exact details, but if I couldn't properly write a selinux rule for it and S2 wifi blobs were working properly for at least 2 months, then I would have removed argosd. As for the comment about "# Why do we need this on S2 wifi only devices? If needed for LTE, decommonize this code.", I'm not sure why I wrote that or where it came from. I made a number of changes that day and it could have been a cut and paste error or I just made a mistake thinking that it was for LTE?

    Anyway, I will try to make a 18.1 private build with argosd re-enabled and take a look to see if I can write a selinux policy to address the denial.

    If/once it works, I'll PM @lojelo and get him/her to test it. If it does work and throughput increases back to 330Mbps for lojelo, I will think about how to add this patch.

    For June 5th security patches, your vibrator patch is already queued up. For argosd, because it affects wifi, I might have people test it in a separate build and if it's stable, reliable and helps with throughput, then I will add it to the July 5 security patch build.
    1
    Hello mate! argosd most likely is responsible for low throughput, i dont fully remember how it worked but as far as i recall it adjusts cpu frequency, affinity, HMP values etc when detecting high internet load (for example speedtest). similar to things like input booster.
    Thanks for the explanation above. It helps me understand more how argosd works.
    if i remember correctly when i lacked argosd not only was my speed capped at around 100mbps, the phone would get extremally slow and unresponsive while the download was taking place. after fixing it my note 4 can saturate my entire ISP bandwidth at around 350~500MBPS on the 5GHz channel without it grinding to a halt.
    I'll give it a test if/once I get it running.
    i dont know anything about handling selinux denials, but argos kernel driver needs to have argosd functional and access to
    "/dev/network_throughput"

    you can find the entire policy here if needed. thanks to lineage team common samsung_sepolicy
    https://github.com/LineageOS/androi...mmit/b82b1934646d71da34464ffd4223c6ad10f2dea8
    Yes, I found it on github last night, but thanks for confirming that I'm looking at the correct one. Thanks again @ananjaser121, I always appreciate your input.
    1
    New build called lineage-18.1-20220611-UNOFFICIAL-gts210wifi.zip

    All the functionality as to what works as per post #1 has been tested 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 11, 2022 release notes

    1. YOU MUST read posts 1-4 if you haven't already

    2. 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
    3. Incorporates June 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-06
    4. If you are upgrading from the April 10 build or later, you may dirty flash the June 11 build. If you are NOT coming from the April 10th 2022 or later 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.
    1
    Sorry I haven't replied in here sooner I have been really busy.

    Since receiving the test build my download has been perfect a huge difference in-fact, this last couple of days I have had speedtest over 400mb. I have only lost connection on my device when I have been upstairs so I am not putting that down to the build that fault is with my ISP's router the Wi-Fi range on virginmedia's hubs aren't that good even with the pods.

    I noticed one problem on 1st reboot after installing the update my tablet was rather sluggish but after another reboot it worked fine, I am very happy with this build much appreciation to retiredtab for spending the time to fix this issue. I will carry on monitoring my tablet but for now this build has given it a new life.
  • 7

    LineageOS 18.1 UNOFFICIAL for 2015 Samsung Galaxy Tab S2 SM-T810 ONLY​

    Model: SM-T810 (wifi) - gts210wifi - 9.7" 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. 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. Yogi555 for building the public T810 monthly roms starting April 2022
    7. lpedia for suggestions, proof reading and FAQ table format in post #2.
    3
    @retiredtab, @ananjaser1211, @lpedia, @Yogi555 and @CuckooPenguin thx very much for your work.
    Until yesterday mine was on ripees build from 20211103 which was stable and working but didn't seem to get any further updates than 20211208.
    Clean installation went well although I didn't follow "Q5" and used latest TWRP which is 3.6.1_9-0.
    Flashed it with Magisk 23. (wanted to make sure that Gapps didn't interfere)
    1st boot was fast, setting it all up.
    Looking in settings for button backlight duration but didn't find it (using it in the night and want them to light up as short as possible).
    Wifi connection there as soon as it wakes up.
    So I gave BitGapps a go and flashed ARM64 which worked (isn't specified in "Q12" and as far as I remember only ARM worked on ripees build).
    Fiddling around a bit installing paid apps and others.
    Everything seems to be fine especially for a beta version.

    For others who want to change from ripees version to this one:
    On mine it worked to restore "Data" via TWRP (partition got wiped again before) what makes it much easier to switch.
    Each app I use seems to be working under the new ROM without problems.

    Fun fact: button backlight after restoring is as short as it was set in the prior ROM.
    2
    Frequently Asked Questions. You MUST READ this before posting any questions. Thank you.

    QuestionAnswer
    Q1. 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_gts210wifi

    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/22fd53a977eeaf4e36be7bf6358ecf2c2737fa5e
    Q2. 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 TWRP 3.5.2_9. Get it from

    https://dl.twrp.me/gts210wifi/
    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. Yogi555 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 make a guide in in post #16.
    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 May 5 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 #14. 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/retiredtab/files/SM-T810/18.1/
    2
    Monthly release notes

    June 11, 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 10, 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 10, 2022
    1. YOU MUST read posts 1-4 if you haven't already

    2. First public BETA release of selinux enforcing T810 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.
    2
    Initial public build called lineage-18.1-20220410-UNOFFICIAL-gts210wifi.zip. The sha256sum file is provided as well to ensure integrity of download.

    Yogi555 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 10, 2022
    1. YOU MUST read posts 1-4 if you haven't already

    2. First public BETA release of selinux enforcing T810 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.