[UNOFFICIAL][ROM]ALPHA LineageOS 19.1 for SM-T710 - Sept 16, 2023

Search This thread

lpedia

Senior Member
Sep 18, 2020
348
1
173
Samsung Galaxy Tab S2
HTC 10
New build called lineage-19.1-20230213-UNOFFICIAL-gts28wifi.zip

For those who use or want to use gapps: I found that NikGapps-core-arm64-12.1-20220709-signed.zip continues to work well with this ROM on my device. I have not been able to get a later version to work correctly with it. Although it would appear to install correctly, on reboot there'd be no Play Store.

Note that if you're dirty-flashing an update on top of existing NikGapps, you will need to reflash NikGapps just after flashing the ROM. I do not know if this applies to other gapps packages as well.
 
  • Like
Reactions: Dr_MC

zed011

Senior Member
Jan 18, 2011
545
110
The fix is working well, my tablet is noticeably cooler and I can see it at 400Mhz often
 
  • Like
Reactions: Kyrat

Dr_MC

Member
Aug 16, 2011
32
2
Samsung Galaxy Tab S2
The fix is working well, my tablet is noticeably cooler and I can see it at 400Mhz often
Curiously, my T710 was very well behaved with the January update, but after dirty flashing the Feb update I started having random reboots, occasional overheating, and the "cannot provide internet" problem. The three problems seem correlated, and usually disappeared after a restart or a power+home+vol down reset. Should I return to stock and flash the Feb update, or wait until the March update (and then should I return to stock before flashing)?
 

lpedia

Senior Member
Sep 18, 2020
348
1
173
Samsung Galaxy Tab S2
HTC 10
Curiously, my T710 was very well behaved with the January update, but after dirty flashing the Feb update I started having random reboots, occasional overheating, and the "cannot provide internet" problem. The three problems seem correlated, and usually disappeared after a restart or a power+home+vol down reset. Should I return to stock and flash the Feb update, or wait until the March update (and then should I return to stock before flashing)?

I'd suggest clean-flashing the Feb update and see if that behaves. No need to go right back to stock.

Dirty-flashing updates usually works, but as a general rule try a clean flash if there are any glitches.
 

Dr_MC

Member
Aug 16, 2011
32
2
Samsung Galaxy Tab S2
I'd suggest clean-flashing the Feb update and see if that behaves. No need to go right back to stock.

Dirty-flashing updates usually works, but as a general rule try a clean flash if there are any glitches.
I'd suggest clean-flashing the Feb update and see if that behaves. No need to go right back to stock.

Dirty-flashing updates usually works, but as a general rule try a clean flash if there are any glitches.



Could you please point me to instructions for clean flashing from twrp? Thanks.

 

lpedia

Senior Member
Sep 18, 2020
348
1
173
Samsung Galaxy Tab S2
HTC 10
@Dr_MC - this is how I'd do a clean flash with TWRP:
  1. In TWRP, select Wipe > Advanced Wipe.
  2. Tick Dalvik / ART Cache, Data, Cache, System, then swipe Swipe to Wipe.
  3. Touch the Back button and select Format Data. Type yes when prompted.
  4. Touch the Home button and select Install.
  5. Select the ROM zip and any addons (such as gapps), then swipe Swipe to confirm flash.
https://forum.xda-developers.com/t/...know-before-toying-with-your-android.4286651/ is a good introduction to XDA terminology and processes like clean and dirty flashing.
 

retiredtab

Senior Member
Nov 16, 2017
1,657
1,474
New build called lineage-19.1-20230320-UNOFFICIAL-gts28wifi.zip

NOTE: lpedia has built the rom and pflyaz personally tested the 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.

March 20 , 2023 release notes
1. YOU MUST read posts 1-4 if you haven't already.

2. Mar 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-03
 
  • Like
Reactions: zed011

zed011

Senior Member
Jan 18, 2011
545
110
Just wondering if anyone's been having issues with instagram. I started using it again, tried deleting and reinstalling the app but eventually the feed is a few days behind and images refuse to load. I haven't seen this issue happen on any other device but this S2. Can grab some logs later. Also videos are extremely low quality on instagram too. I only found 1 other person who commented the same but on lineage 18
 

retiredtab

Senior Member
Nov 16, 2017
1,657
1,474
Just wondering if anyone's been having issues with instagram. I started using it again, tried deleting and reinstalling the app but eventually the feed is a few days behind and images refuse to load. I haven't seen this issue happen on any other device but this S2. Can grab some logs later. Also videos are extremely low quality on instagram too.
I don't use Instagram and never will so I don't know why your feed is late or refuses to load.

For Instagram and low quality videos, I only know this because @ananjaser1211 mentioned this to me sometime in past year or two?

This commit

https://github.com/universal5433/pr...mmit/10a2ac9ff23a0a2c589df5c4ba1c21e4fd539d91

says it fixes

"This fixes Apps that rely on encoder (Live message and many others)
And fixes quality (decoder) in apps like instagram , twitter and so on"

Later on, the blobs were updated again in this commit.

https://github.com/universal5433/pr...mmit/c105d6037c7ad74a030101a946a53a2faf587e3d

* Previous OMX was "too new" and had many unsupported formats
* Also its AVC.Encoder is not supported on our phone
* This OMX solves all those issues
* Apply patch

sed -i "s|system/lib|vendor/lib|g" $BLOB_ROOT/vendor/lib/libExynosOMX_Core.so

So download these 2 files

https://github.com/universal5433/pr...m/vendor/lib/omx/libOMX.Exynos.AVC.Decoder.so
https://github.com/universal5433/pr...m/vendor/lib/omx/libOMX.Exynos.AVC.Encoder.so

Bash:
$ sha256sum libOMX*
8de9c97fcf6af9f5e96e93bd9be1d54b1a19180571129f4535b8384d3b5a6358  libOMX.Exynos.AVC.Decoder.so
622f23a8dc367d0b2296bd2337c7ef2e3d87241f7ec3479ab22f9e6296441e5c  libOMX.Exynos.AVC.Encoder.so

$ ls -al libOMX*
-rw-rw-r-- 1 l l 237496 Mar 28 16:42 libOMX.Exynos.AVC.Decoder.so
-rw-rw-r-- 1 l l 245704 Mar 28 16:42 libOMX.Exynos.AVC.Encoder.so

On my existing 19.1 build, I see

Bash:
gts210wifi:/system # ls -al ./lib/omx/libOMX*                                                                                                             
-rw-r--r-- 1 root root 164044 2008-12-31 17:00 ./lib/omx/libOMX.Exynos.AVC.Decoder.so
-rw-r--r-- 1 root root 169744 2008-12-31 17:00 ./lib/omx/libOMX.Exynos.AVC.Encoder.so
so they are earlier versions.

To update, follow these steps and see if Instagram video playback is better.

UPDATED/EDIT: See post #94 instead.

1. Save your device data.
2. Download newer versions of the libOMX encoder/decoder onto your PC.
3. Boot into TWRP.
4. Touch mount system
5. # cd into the directory where you downloaded the 2 files
6. adb push libOMX.Exynos.AVC.Decoder.so /system/lib/omx
7. adb push libOMX.Exynos.AVC.Encoder.so /system/lib/omx
8. # verify file sizes are correct
9. adb shell ls -al /system/lib/omx
10. reboot into OS and test Instagram

I only found 1 other person who commented the same but on lineage 18
I have no idea if that person is running my 18.1 rom or another.
 
Last edited:

retiredtab

Senior Member
Nov 16, 2017
1,657
1,474
The above post changing of the OMX breaks stock camera video recording. Anan suggested something else which I will post in the next thread once I test it out.
 

retiredtab

Senior Member
Nov 16, 2017
1,657
1,474
@ananjaser1211 suggested that the low quality video is due to the open source OMX drivers not supporting adaptive-playback. He suggested removing all instances of that parameter from the media_codecs.xml file which I have done and attached as zip.

@zed011, try this

1. Save your device data.
2. Download media_codecs.zip and unzip it.
3. Boot into TWRP.
4. Touch mount system
5. # cd into the directory where you downloaded the file.
6. adb push media_codecs.xml /system/vendor/etc/media_codecs.xml
7. reboot into OS and test Instagram
 

Attachments

  • media_codecs.zip
    2.4 KB · Views: 2
Last edited:

zed011

Senior Member
Jan 18, 2011
545
110
@ananjaser1211 suggested that the low quality video is due to the open source OMX drivers not supporting adaptive-playback. He suggested removing all instances of that parameter from the media_codecs.xml file which I have done and attached as zip.

@zed011, try this

1. Save your device data.
2. Download media_codecs.zip and unzip it.
3. Boot into TWRP.
4. Touch mount system
5. # cd into the directory where you downloaded the file.
6. adb push media_codecs.xml /system/vendor/etc/media_codecs.xml
7. reboot into OS and test Instagram

I tried the file, looks like now videos aren't playing at all for instagram, reddit and youtube. Here's a log I captured for youtube.

Code:
03-29 02:57:06.797  7459  7459 E YouTube : Encountered unknown or invalid card
03-29 02:57:06.821  3674 16997 I GenericSource: start
03-29 02:57:06.828  3674 17002 E NuPlayerDecoder: Failed to create video/mp4v-es decoder
03-29 02:57:06.832  3674 17002 W NuPlayerDecoder: onSetParameters called before codec is created.
03-29 02:57:06.834  3674 16997 E NuPlayer: received error(0x80000000) from video decoder, flushing(0), now shutting down03-29 02:57:06.835  3674 17004 E NuPlayerDecoder: Failed to create audio/mp4a-latm decoder
03-29 02:57:06.836  7459 13802 W MediaPlayerNative: info/warning (805, -2147483648)
03-29 02:57:06.837  3674 16997 E NuPlayer: received error(0x80000000) from audio decoder, flushing(0), now shutting down03-29 02:57:06.844  7459 13802 E MediaPlayerNative: error (1, -2147483648)
03-29 02:57:06.847  7459  8000 E MediaPlayer: Error (1,-2147483648)
03-29 02:57:06.854  7459  8000 E YouTube : AndroidFwPlayer: error [prepared=true, what=1, extra=-2147483648]
03-29 02:57:06.858  7459  7459 W YouTube : Missing Vss3Config
03-29 02:57:06.859  7459  7459 W YouTube : Warning: unexpected playback play 0 suppressed
 

Attachments

  • youtube_logcat.txt
    71.8 KB · Views: 6

retiredtab

Senior Member
Nov 16, 2017
1,657
1,474
New build called lineage-19.1-20230418-UNOFFICIAL-gts28wifi.zip

NOTE: lpedia has built the rom and pflyaz personally tested the 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.

Apr 18 , 2023 release notes
1. YOU MUST read posts 1-4 if you haven't already.

2. Apr 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-04
 

schnoeselmeier

Senior Member
Mar 19, 2016
246
40
Chiang Mai
I tried a few things but couldn't pass safety net. Is there a way to do it? Not really important because I won't use banking apps on such an old device anyway. The rom is superb. Feels like a completely new device.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4

    LineageOS 19.1 UNOFFICIAL for 2015 Samsung Galaxy Tab S2 SM-T710 ONLY​

    Model: SM-T710 (wifi) - gts28wifi - 8" screen, Exynos 5433 SoC, no LTE
    This is the ONLY model that the ROM will work on.

    There is NO ROM for the T715 or T815 in this thread. Questions about T715 or T815 will be completely IGNORED.

    You MUST READ posts 1-4 (about 10 minute read) before deciding to install this rom. If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.

    DISCLAIMER


    I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.

    All involved in bringing this build to you are working voluntarily on it in very limited spare time, and their other life commitments have much higher priority. Don't expect a prompt, or even any, response to questions and bug reports.

    Before attempting to install this ROM

    1. Ask yourself: would bricking your device be a disaster for you? If yes, don't try this ROM! It can't be guaranteed stable and reliable enough to depend on for daily use.
    2. BACKUP YOUR DATA AND EXISTING ROM. Be prepared for a complete restore if anything goes wrong.
    3. RESEARCH adb, fastboot, Odin/heimdall, and TWRP and how to use them, if not already familiar with these.

    What works

    1. bluetooth
    2. wifi
    3. brightness
    4. external audio
    5. GPS
    6. audio through headphone jack
    7. audio over bluetooth
    8. selinux enforcing
    9. DRM level 3 (SD definition)
    10. deep sleep
    11. camera

    1. fingerprint is completely removed in 19.1. When I tested it in March 2022, it wasn't compatible with keystore2 and as I wrote in post 1891 at

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

    it never worked properly after deep sleep. If you need fingerpint to work, stay with stock Samsung rom.

    2. DRM level 1 (no HD definition). There's more detail in post 1891 above. I will not be trying to achieve level 1 for HD definition. If you need HD definition for your $treaming media, stay with stock Samsung rom.

    3. workaround to disable scoped storage. In 18.1 there was a workaround to disable scoped storage, but that no longer works in 19.1. So if you have a lot of apps or data on an external microsd, the performance may be severely degraded.

    4. If you charge the device while it's powered off and then want to power it on, you MUST wait at least 30 seconds AFTER disconnecting the charger cable before pressing the power button otherwise you might run into strange boot problems.

    5. keyboard bug workaround. When prompted to enter something like a Bluetooth pin or text based password, sometimes the keyboard is not shown on the screen or off screen. The workaround is to goto settings, system, languages & input, on-screen keyboard, Android Keyboard (AOSP), appearance & layout, theme and choose "Material - follow system settings".

    This keyboard bug is a LineageOS bug as per

    https://review.lineageos.org/c/LineageOS/android_packages_inputmethods_LatinIME/+/325438

    6. There has no been no fix for the “Connected to device. Can’t provide internet” (CPI). However, pflyaz found a workaround for CPI. Goto Settings, Network & internet, Internet. In the upper right hand corner there is a small wrench with reversed arrow. Touch that and it will reset your wifi and you should be reconnected.

    NOTE: Airplane mode has to be disabled in order to see this icon.

    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.
    3
    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:
    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.
    2
    I am a happy user of retiredtab's Lineage 18.1 for T710. Are there any advantages to moving to 19.1? I am not a power user, although I sometimes look for specific files though myfiles types of apps and copy or move them.
    If you're happy with 18.1, just stay with that unless you need a feature that's only in Android 13.
    2
    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.
    2
    New build called lineage-19.1-20221111-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.

    Nov 11, 2022 release notes
    1. YOU MUST read posts 1-4 if you haven't already.

    2. Nov 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-11