I tried not installing gapps and the ROM booted. I'll try to use a different gapps package. For the time being I'm using Aurora store but I would prefer using proper gapps.
[ROM][UNOFFICIAL][10] LineageOS 17.1 [T713][T719][T813][T819]
- Thread starter ripee
- Start date
I tried not installing gapps and the ROM booted. I'll try to use a different gapps package. For the time being I'm using Aurora store but I would prefer using proper gapps.
I managed to install LOS16 and Open gapps, but not with the links in the original post but with the downloads from opengapps.org
Thank you so much for maintaining these LineageOS versions alive for our Tab S2!
I have v.17 now on a Tab S2 10" and just installed it on a Tab S2 8" that was still on original A7.0. Used MindTheGapps from the repository mentioned on the installation instructions page.
Always the little bug that doesn't let you finalise the google onfiguration setup (jumps back to security code/fingerprint stage after google voice search stage). Once you upgrade the google play services from the play store, it all works as expected and you can finalise the setup. It's a "MindTheGapps" bug anyway, so nothing to do with lineage.
You can't install Netflix directly from the play store, but I guess I can sideload it.
These "old" Galaxy Tabs are just great, with just enough RAM and memory, 3.5mm audio jack, etc. no need to have anything more recent for most of my/our needs, as long as there is someone keeping us updated with the OS as you do here. So Thanks again for your great work!
I have v.17 now on a Tab S2 10" and just installed it on a Tab S2 8" that was still on original A7.0. Used MindTheGapps from the repository mentioned on the installation instructions page.
Always the little bug that doesn't let you finalise the google onfiguration setup (jumps back to security code/fingerprint stage after google voice search stage). Once you upgrade the google play services from the play store, it all works as expected and you can finalise the setup. It's a "MindTheGapps" bug anyway, so nothing to do with lineage.
You can't install Netflix directly from the play store, but I guess I can sideload it.
These "old" Galaxy Tabs are just great, with just enough RAM and memory, 3.5mm audio jack, etc. no need to have anything more recent for most of my/our needs, as long as there is someone keeping us updated with the OS as you do here. So Thanks again for your great work!
Now that I have a working tablet again, I can confirm that the USB port is working only for charging but not for data transfer.
Hi,
I installed the LOS 17.1 ROM on my SM-T713 a few weeks ago (my first ever custom ROM install) and it's been running great aside from a few issues previously mentioned by others like the camera being slow to start and the GPS not working. However, I noticed that both CPU-Z and AIDA64 now report the platform/board as MSM8952 (which has a different SoC) instead of MSM8976. I'm wondering if this could be the cause of some of these problems with the ROM, or is it purely a cosmetic bug? Can anyone confirm this?
I installed the LOS 17.1 ROM on my SM-T713 a few weeks ago (my first ever custom ROM install) and it's been running great aside from a few issues previously mentioned by others like the camera being slow to start and the GPS not working. However, I noticed that both CPU-Z and AIDA64 now report the platform/board as MSM8952 (which has a different SoC) instead of MSM8976. I'm wondering if this could be the cause of some of these problems with the ROM, or is it purely a cosmetic bug? Can anyone confirm this?
I tried joining the Telegram channel but some admin blocking me.
It happened three times already.
Hey, No camera currently Not fixed in The Release of 3. March 2023.
It worked until a few months ago and was then patched broken. I wish I hadn't made an update
i gave up with the 719lte...i changed to 715lte installed android 11 and everything seems to be working great...you must use speaker for calls and takes few seconds before you hear the other person but i can put up with that for android 11.....whatsapp is working fine and camera.... https://forum.xda-developers.com/t/...os-18-1-for-sm-t715-february-18-2023.4509345/
The bootloop happened again but I have a solution!
I was adding quick panel buttons in the notifications panel (like location, sound, immersive mode, etc), and as soon as I tried to drag the icon for "One Handed Operation +" into the top part, SystemUI crashed and would not restart. Reboot went to TWRP. Safe Mode didn't work either, could not get past the broken lock screen, SystemUI would not start.
But the solution was easy. I found the package name for this app on my phone (which also has the app, I looked at TitaniumBackup to easily find the package name), suspecting it as the problem. The package name is:
`com.samsung.android.sidegesturepad-...`
... of course is a random strong of characters, not important. The folder beginning with that is what you want.
In TWRP on my tablet, I went to:
Advanced > File Manager
In file manager, I went to /data/app
In this folder, you will find the folder: `com.samsung.android.sidegesturepad-...`
Click on that folder,
Click the icon in the bottom right,
And either Delete or Move the folder. Personally, I moved the folder to my /sdcard/DCIM folder, but it's not important where you move it, as long as it's no longer in the /data/app folder.
This will effectively uninstall the app.
It can also be done over the TWRP terminal or ADB, but that's harder because you have to manually type that long strong of characters for the folder name.
Anyway, after doing the above and rebooting, tablet is working again!
Wanted to report this major bug so others know, and if it happens, how to fix it.
If there is another app causing a problem, you can do the same thing in TWRP to remove the problematic app. If you don't know which app, you could try uninstalling any suspect apps by moving the app folders out of /data/app until you find the problematic one. Would be way easier than reinstalling the whole system!
Hope it helps!
I was adding quick panel buttons in the notifications panel (like location, sound, immersive mode, etc), and as soon as I tried to drag the icon for "One Handed Operation +" into the top part, SystemUI crashed and would not restart. Reboot went to TWRP. Safe Mode didn't work either, could not get past the broken lock screen, SystemUI would not start.
But the solution was easy. I found the package name for this app on my phone (which also has the app, I looked at TitaniumBackup to easily find the package name), suspecting it as the problem. The package name is:
`com.samsung.android.sidegesturepad-...`
... of course is a random strong of characters, not important. The folder beginning with that is what you want.
In TWRP on my tablet, I went to:
Advanced > File Manager
In file manager, I went to /data/app
In this folder, you will find the folder: `com.samsung.android.sidegesturepad-...`
Click on that folder,
Click the icon in the bottom right,
And either Delete or Move the folder. Personally, I moved the folder to my /sdcard/DCIM folder, but it's not important where you move it, as long as it's no longer in the /data/app folder.
This will effectively uninstall the app.
It can also be done over the TWRP terminal or ADB, but that's harder because you have to manually type that long strong of characters for the folder name.
Anyway, after doing the above and rebooting, tablet is working again!
Wanted to report this major bug so others know, and if it happens, how to fix it.
If there is another app causing a problem, you can do the same thing in TWRP to remove the problematic app. If you don't know which app, you could try uninstalling any suspect apps by moving the app folders out of /data/app until you find the problematic one. Would be way easier than reinstalling the whole system!
Hope it helps!
Last edited:
Which version worked? Would be helpful for devs to find the problem. Can confirm camera does not work (T713), although I don't care about a camera on a tablet, I use this for reading.Hey, No camera currently Not fixed in The Release of 3. March 2023.
It worked until a few months ago and was then patched broken. I wish I hadn't made an update
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
Hey, No camera currently Not fixed in The Release of 3. March 2023.
It worked until a few months ago and was then patched broken. I wish I hadn't made an update -
71
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Code:* [B][U]Your warranty is now void.[/U][/B] I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or your getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at us for messing up your device, I will laugh at you.
FREQUENTLY ASKED QUESTIONSQ: The room is bootlooping the first time I attempt to boot into it after clean flashing. What should I do?[/COLOR]
(Please read them BEFORE posting anything in the thread!)
A: Force reboot using the Power and Volume Down buttons. The rom will boot properly the second time around. This is a known bug and it affects clean flashes only.
Q: Whenever I try flashing any lineage-17.1 build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: This error appears whenever you try to flash an Q-based rom within a version of TWRP older than 3.4. Simply flash the linked below version 3.4 or higher, reboot back into recovery, and flash the rom zip again.
Q: Will any of the variants ever receive official builds from LineageOS?
A: No.
Q: How often will new builds be released?
A: At least once per month: as soon as possible after each new Android security patch level is merged and whenever a new feature is added or a bug is fixed.
ROMs
pitrus-
- SM-T713: gts28vewifi
- SM-T719: gts28velte
- SM-T813: gts210vewifi
- SM-T819: gts210velte
Open GApps
Magisk
If your currently installed ROM is any version of either: stock Samsung TouchWiz, LineageOS, CyanogenMod, or any other custom ROM, you must perform a clean install of that LineageOS 17.1 variant, which corresponds to the model of your tablet!FULL WIPE (with external microsd card)
How to flash LineageOS and Open GApps
FULL WIPE (without external microsd card with NO Home PC access)
FULL WIPE (without external microsd card with Home PC access)
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your tablet and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the tablet.
* Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Bugs
- The rom bootloops only after clean flashing. Force rebooting allows it to boot properly the second time and every time afterwards. See the FAQ's above.
- The cameras work, but with a delayed response, so they are impractical to use.
- T719 & T819: RIL does not work at all.
- You tell us!
Changelog
All major features and bug fixes are discussed in detail by the developer in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.
Credits
- Luk1337 and every other open source developer and tester who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for the gts28velte, gts28vewifi, gts210velte, and gts210vewifi.
Sources
- LineageOS
- team-infusion-developers
XDA:DevDB Information
LineageOS 17.1, ROM for the Samsung Galaxy Tab S2
Contributors
pitrus-
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 10
Stable Release Date: 2020-03-25
Created 2020-03-21
Last Updated 2021-11-1029Reserved
TWRP 3.5.2_9-2
The official TWRP for all four variants is built by TeamWin's servers from the outdated android-6.0 branch. A major bug in this branch is that mtp is broken, so I ran my own builds from the android-7.1 branch. I fixed hw encryption, which is why I bumped the version number up to "-2":
twrp-3.5.2_9-2-gts210velte
twrp-3.5.2_9-2-gts210vewifi
twrp-3.5.2_9-2-gts28velte
twrp-3.5.2_9-2-gts28vewifi17Since all ROMs got deleted and it looks like there won't be any new ones I decided to do something about this.
My T719 is still in perfectly good shape and it would be a shame to dump it to the landfill.
So I spend the last two days digging through Repositories and recreated the build processes originating from ripee's original post, giving these devices a second life.
Download from my GDrive.13
Yes, I'm almost done reviewing my commits so far. Real life is busy lately.
