[UNOFFICIAL][ROM]BETA LineageOS 18.1 for SM-T710 - June 12, 2022

Search This thread

Dr_MC

Member
Aug 16, 2011
22
0
Samsung Galaxy Tab S2
ROM is working well so far except for the charging when powered off bug, which had been reported about the previous 18.1 from 2021. When charging with power off , the tablet gets stuck with the charge icon. Restarting requires power,, vol down, and home to clear icon. Is this still a known bug or should I return to stock and then reinstall?

Thanks,

MC
 

retiredtab

Senior Member
Nov 16, 2017
1,113
675
ROM is working well so far except for the charging when powered off bug, which had been reported about the previous 18.1 from 2021. When charging with power off , the tablet gets stuck with the charge icon. Restarting requires power,, vol down, and home to clear icon. Is this still a known bug or should I return to stock and then reinstall?
Our group focuses on uptime, reliability and stability testing so we rarely reboot unless we have to. We typically try for at least 100+ hours and sometimes can get 28+ days before rebooting to make the new monthly security patch. So when we need to charge our device, we never turn it physically off.

If this is a bug, I'll have a look, but no promises if this can be fixed or not. In addition, I won't be looking at this until the next time I have to purposely reboot or shutdown my T710 as it's doing uptime testing right now.
 

cammykool

Senior Member
Sep 6, 2011
1,492
371
25
Colorado
Samsung Galaxy Tab S2
Google Pixel 6
Had some issues getting recovery running. Got it booted and flashed the most recent build! I found this tablet 16 hours ago at an Arc Thrift store untested for $9. Thank you for making this tablet modern and usable!
 

Attachments

  • Screenshot_20220522-121047_Pixel_Launcher.png
    Screenshot_20220522-121047_Pixel_Launcher.png
    3.1 MB · Views: 15
  • Like
Reactions: lpedia

Dr_MC

Member
Aug 16, 2011
22
0
Samsung Galaxy Tab S2
This release is great! Thank you. I owe you a coffee :) . I have a question about power consumption though: Is it normal that when I am using the tablet, power consumption seems much greater than when on Samsung's stock Android 7? The battery does not drain when the tablet is idle, but when the screen is on AccuBattery says that I am using about 850 mA/h. Mostly I am just browsing the web or reading using Libby.

I have the original battery in it, which AccuBattery rates as at 85% capacity (3400 mA/h). Would there be much advantage in replacing it?

Thanks again,

MC
 

retiredtab

Senior Member
Nov 16, 2017
1,113
675
I have a question about power consumption though: Is it normal that when I am using the tablet, power consumption seems much greater than when on Samsung's stock Android 7? The battery does not drain when the tablet is idle, but when the screen is on AccuBattery says that I am using about 850 mA/h. Mostly I am just browsing the web or reading using Libby.
I bought my used T710 in Nov 2020, not for $9, and promptly deleted stock so I have don't have any reference.

With my display set at 46% brightness, airplane mode on (wifi on, bluetooth off, gps off), devcheck shows my battery discharging at around -218mA. At 87% display brightness, devcheck says -367mA.

I wouldn't replace the battery until it doesn't hold a charge properly. For example, for testing purposes, I have run my T710 down to 1% to make sure the OS is stable and still running. On another used tablet that I purchased, once the battery charge gets to 25%, it starts to crash and reboot itself indicating that the OEM battery can't provide enough amps.
 
  • Like
Reactions: Dr_MC

Dr_MC

Member
Aug 16, 2011
22
0
Samsung Galaxy Tab S2
I bought my used T710 in Nov 2020, not for $9, and promptly deleted stock so I have don't have any reference.

With my display set at 46% brightness, airplane mode on (wifi on, bluetooth off, gps off), devcheck shows my battery discharging at around -218mA. At 87% display brightness, devcheck says -367mA.

I wouldn't replace the battery until it doesn't hold a charge properly. For example, for testing purposes, I have run my T710 down to 1% to make sure the OS is stable and still running. On another used tablet that I purchased, once the battery charge gets to 25%, it starts to crash and reboot itself indicating that the OEM battery can't provide enough amps.

Thanks for this. By turning on airplane mode and tweaking things, I got my consumption down to what you have. Do you also toggle the battery saver? Also, I upgraded to the pro version of dev check. Do you know of a way to display the consumption rate in the status bar (or as an overlay) so that I can correlate activity and settings with consumption in real-time?

Thanks
 

retiredtab

Senior Member
Nov 16, 2017
1,113
675
Do you also toggle the battery saver?
Sometimes I do manually when my battery gets around 25% and I'm not close to a charger anytime soon.
Also, I upgraded to the pro version of dev check. Do you know of a way to display the consumption rate in the status bar (or as an overlay) so that I can correlate activity and settings with consumption in real-time?
flar2, the Canadian developer, for devcheck has his own thread at

https://forum.xda-developers.com/t/app-devcheck-1-19-system-information.3171427/

You can ask him directly in that thread.
 

retiredtab

Senior Member
Nov 16, 2017
1,113
675
Do you know of a way to display the consumption rate in the status bar (or as an overlay) so that I can correlate activity and settings with consumption in real-time?
While working on another problem with another device using adb logcat (microusb cable connected), I noticed the logcat displays the battery info. So then that led me to think about using adb logcat via wifi.

So I setup my device to do adb wirelessly and if I do this command

Bash:
adb logcat -C | nl | grep sec_bat_get_battery_info

I get this output
Code:
    12  05-25 20:16:20.272     0     0 I         : [1:   kworker/u8:7: 2473] sec-battery battery.76: sec_bat_get_battery_info:Vnow(3882mV),Inow(-330mA),Imax(450mA),SOC(61%),Tbat(259),Tchg(0),is_hc_usb(0)
   326  05-25 20:16:50.316     0     0 I         : [2:   kworker/u8:7: 2473] sec-battery battery.76: sec_bat_get_battery_info:Vnow(3895mV),Inow(-258mA),Imax(450mA),SOC(61%),Tbat(259),Tchg(0),is_hc_usb(0)
   366  05-25 20:17:20.353     0     0 I         : [2:   kworker/u8:5: 2206] sec-battery battery.76: sec_bat_get_battery_info:Vnow(3894mV),Inow(-281mA),Imax(450mA),SOC(61%),Tbat(259),Tchg(0),is_hc_usb(0)
   566  05-25 20:17:50.400     0     0 I         : [3:   kworker/u8:2:   45] sec-battery battery.76: sec_bat_get_battery_info:Vnow(3911mV),Inow(-78mA),Imax(450mA),SOC(61%),Tbat(259),Tchg(0),is_hc_usb(0)
   896  05-25 20:18:20.446     0     0 I         : [1:   kworker/u8:7: 2473] sec-battery battery.76: sec_bat_get_battery_info:Vnow(3915mV),Inow(-94mA),Imax(450mA),SOC(61%),Tbat(258),Tchg(0),is_hc_usb(0)
   916  05-25 20:18:50.487     0     0 I         : [3:   kworker/u8:7: 2473] sec-battery battery.76: sec_bat_get_battery_info:Vnow(3914mV),Inow(-96mA),Imax(450mA),SOC(61%),Tbat(258),Tchg(0),is_hc_usb(0)

So Inow is your current draw. As you can see in the timestamps, it doesn't update that often, but at least you get an idea of what is happening.

https://www.makeuseof.com/use-adb-over-wifi-android/
 

metterschling

Senior Member
Sep 29, 2013
163
108
Nexus 7
Samsung Galaxy Tab S2
Does haptic feedback work on this ROM? In "Settings->Sounds->Advanced->Other Sounds and Vibration" is there a separate entry/toggle for display touch vibration? On my 18.1 experimental builds for gts28ltexx that option is not present. I wonder if I missed something or if this is a known regression compared to 17.1.
 

metterschling

Senior Member
Sep 29, 2013
163
108
Nexus 7
Samsung Galaxy Tab S2
Does haptic feedback work on this ROM? In "Settings->Sounds->Advanced->Other Sounds and Vibration" is there a separate entry/toggle for display touch vibration? On my 18.1 experimental builds for gts28ltexx that option is not present. I wonder if I missed something or if this is a known regression compared to 17.1.
Nevermind, found the solution myself. After adding the following lines to the gts2-common device manifest haptic feedback started working:
Code:
    <hal format="hidl">
        <name>android.hardware.vibrator</name>
        <transport arch="32">passthrough</transport>
        <version>1.0</version>
        <interface>
            <name>IVibrator</name>
            <instance>default</instance>
        </interface>
    </hal>

@retiredtab - you might want to check.
 
  • Like
Reactions: lpedia

retiredtab

Senior Member
Nov 16, 2017
1,113
675
Nevermind, found the solution myself. After adding the following lines to the gts2-common device manifest haptic feedback started working:
Code:
    <hal format="hidl">
        <name>android.hardware.vibrator</name>
        <transport arch="32">passthrough</transport>
        <version>1.0</version>
        <interface>
            <name>IVibrator</name>
            <instance>default</instance>
        </interface>
    </hal>

@retiredtab - you might want to check.
It is incorporated into my device tree so when the June 5th security patches are released, it will be in that build. Thanks. I gave you credit in the commit notes at

https://github.com/retiredtab/andro...mmit/f5efa4c06d610d22bd6075696d370cc2947b389c

I did test it and "touch vibration" now shows up in settings, sound, advanced at the very bottom and haptic works when I use AOSP keyboard.
 
  • Like
Reactions: lpedia
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.
 
  • Like
Reactions: lpedia
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:
  • Like
Reactions: lpedia

retiredtab

Senior Member
Nov 16, 2017
1,113
675
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.
If you have random reboots, please follow the instructions in post #1 at

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

If we get enough data points, we may be able to narrow down the problem. You can send me the tombstones (zipped) via PM and I can take a look at them. If they are app related, there's nothing I can do other than suggesting you use a different app that does the same functionality.
 
If you have random reboots, please follow the instructions in post #1 at

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

If we get enough data points, we may be able to narrow down the problem. You can send me the tombstones (zipped) via PM and I can take a look at them. If they are app related, there's nothing I can do other than suggesting you use a different app that does the same functionality.
Understood, and will do.
 

retiredtab

Senior Member
Nov 16, 2017
1,113
675
A quick way of looking at your own tombstones is

Bash:
adb root
adb shell
cd /data/tombstones
head -n20 tombs* | more

When we solved the "random" reboots/dead battery/device on endless boot animation that was plaguing 17.1 users for 10 months, the majority of the tombstones pointed to gnss. Then it took another 25 days of trying different things, testing, etc before we found the 1 line solution at

https://github.com/retiredtab/andro...mmit/1bbb341259f6aee071d88e4abdce42190fd620a7
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    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_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/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 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 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 #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/
    3
    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.
    3
    Congratulations on the awesome release!
    2

    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. 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.
    2
    Monthly release notes

    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.