Looking at the system log (using MatLog Libre), there's a repeated crash of /vendor/bin/pm-proxy with a stack corruption., looks like it's related to the modem (this is on a T713, which has only WiFi). I'm on the latest build from Sep. 20th.
[ROM][UNOFFICIAL][10] LineageOS 17.1 [T713][T719][T813][T819]
- Thread starter ripee
- Start date
Is there maybe a way to disable this rild for good? Have t819 and this problem with battery just stops me from flashing the rom
Sorry, I don't know. You may try flashing the t813 build, which is without the RIL software of course but I have no idea if it wiould work at all, sorry.
Just ran Geekbench5 on the latest build... I don't know what is happening, but there has been a noticeable drop in scores this year. In January, was getting single 355 and multi-core 1175. The worst score was in April, with 284/803. Today's score is 287/884. All on T713. Since I use mine mostly for reading news and books, does not have much practical input. Still, it's curious.
Am I the only one getting random reboots in the last builds (pitrus)?
I've just replaced the battery before anyone suggest it
I've just replaced the battery before anyone suggest it
No you are not the only one. Having the same problem and I also replaced my battery.Am I the only one getting random reboots in the last builds (pitrus)?
I've just replaced the battery before anyone suggest it
I have had random reboots with pretty much every build. I'm using the tablet a lot less these days so I haven't had one in a while.Am I the only one getting random reboots in the last builds (pitrus)?
I've just replaced the battery before anyone suggest it
I'm actually getting fewer reboots in the last couple of bills, but what I am getting are freezes where for a second or seconds the tablet becomes unresponsive.
I'm calling it on the GPS working in the pitrus builds. I have spent two days flashing all those builds I could find, as well as wiping re-
Flashing and trying 14 different gps.conf builds with no luck. Wondering if anyone saved the .conf file from the GPS from the stock ROM and I would try to tweak that to get it to work. Or if someone found a clear solution to that problem on the t713 it would be appreciated. Thanks for everyone's time.
If I want to revert to 16.0, can I just flash it over 17.1 with TWRP? I assume I have to wipe everything before flashing, right?
Ok, so now that I am on 17.1 bother lineage 16 and the stock firmware won't flash with either Odin or TWRP. I was trying to flash to copy the gps.conf to my SD and update. Now I am getting boxed in a corner. Any other suggestions at this point.
Finally got 16.1 flashed after a bunch of tries and low and behold the GPS works. Comparing 16.1 doesn't have the GPS_debug.conf file, could this addition be the hangup in 17.1?
I am going to stick with 16.1 for now since I use the tablet with aviation apps. This particular tablet has always been relatively slow on the update for space vehicles. I am including a config file that I can confirm has made the that time quicker with 16.1 on SM-T713 with the 28vewifi lineage 16.1. Just replace .text with .conf and replace existing gps.conf in system/etc. I will get back to 17.1 in little while.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
72
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.
