[UNOFFICIAL][ROM]ALPHA LineageOS 19.1 for SM-T710 - Mar 18, 2024

[retiredtab]

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://xdaforums.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. If you are repeatedly seeing “Connected to device. Can’t provide internet” (CPI), it's mandatory that you do a complete clean install including formatting data in TWRP and reinstalling all your apps. It's highly likely that CPI is because you did a dirty flash or one or more of your apps/configuration is messed up.

7. 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.

 

[retiredtab]

Frequently Asked Questions. You MUST READ this before posting any questions. Thank you.

Question	Answer
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 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/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 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_gts28wifi
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. 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: # 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://xdaforums.com/t/exynos5433-...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/

 

[retiredtab]

NOTE: Each build has been tested 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.

Mar 18 , 2024 release notes
1. Mar 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2024-03
2. The built in files, camera and music apps crash unless SElinux policy is updated. This is precisely WHY each build is tested before being uploaded. See
https://github.com/retiredtab/andro...mmit/519a249a5fd8105817fbc033b78fa10a82304acb
3. For 2024, going forward 19.1 will be built on March, June, September and December ONLY.

Feb 16, 2024 release notes
1. Feb 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2024-02

Jan 19, 2024 release notes
1. Jan 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2024-01

Dec 16, 2023 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-12

Nov 18, 2023 release notes
1. Nov 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-11

Oct 10, 2023 release notes
1. Oct 6 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-10

Sept 16, 2023 release notes
1. Sept 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-09

Aug 13, 2023 release notes
1. Aug 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-08

July 12, 2023 release notes
1. July 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-07

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.

 

[retiredtab]

Reserved.

 

[pflyaz]

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

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 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.
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.

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.
   • Installing TWRP only takes a couple of seconds.
10. 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 Step 2 and Step 3 again.

Step 4 – Backup your stock ROM

1. In TWRP, select Backup, Select Storage to choose your micro-SD card, check all the partition boxes, and then swipe Backup.
2. Confirm your backup is good

1. In TWRP, select Wipe, then Advanced Wipe.
2. Select all partitions except Micro SD Card (and USB OTG).
3. Swipe to Wipe.
4. Back, Back again, then Format Data
5. Type yes, and tap check.
6. Back, Back, Back, and select Restore.
7. Select Micro SD card and your backup.
8. Restore all partitions and allow restore to complete.
9. Reboot to System, and confirm you are back to stock.

Step 5 – Install ROM and NikGApps

1. In TWRP, select Wipe, then Advanced Wipe.
2. Select all partitions except Micro SD Card (and USB OTG).
3. Swipe to Wipe.
4. Back, Back again, then Format Data
5. Type yes, and tap check.
6. Back, Back, Back, and select Install.
7. Select your micro-SD storage.
8. Select the Lineage-19.1 ROM.
9. Add more Zips, and select nikgapps.
10. Swipe to confirm Flash.
11. Install takes about 3 minutes.
12. Wipe Cache/Dalvik, and Swipe to Wipe.
13. Reboot System.

Step 6 – Build your Android 12 Tab S2

1. 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.
2. At the end of the initialization process, be sure not to choose the Replace Lineage Recovery option, otherwise TWRP goes away.
3. 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!
4. 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”.
5. 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.
6. 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

1. Restart Tab S2 into TWRP.
2. In TWRP, install Magisk-v25.2.apk.
3. Reboot System
4. In Android install Magisk-v25.2.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! Enjoy!

1. I do a final and full TWRP backup once the device is solid on Lineage 19.1.

 

[djcasl]

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.

 

[retiredtab]

I don't have an onscreen keyboard.

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 ===

 

[djcasl]

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 ===

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.

 

[retiredtab]

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

 

[chappatti]

Error!

 

[chappatti]

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

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.

 

[retiredtab]

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.

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.

 

[chappatti]

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.

ha! will try....

 

[chappatti]

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.

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??

 

[retiredtab]

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%.

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.

 

[retiredtab]

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

 

[haircut313]

it charges just fine for me

 

[lpedia]

it charges just fine for me

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.

 

[Kyrat]

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

 

[lpedia]

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 - 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.