[ROM][UNOFFICIAL][10] LineageOS 17.1 [T713][T719][T813][T819]
- Thread starter ripee
- Start date
I installed Open Camera. Works fine. I installed december 23 TH, and opengapps pico. Rom and gapps from first post.
There is no 12/23 release in this location
LineageOS Downloads
Where did you find that release? What does Rupee mean in your signature ?
Also, the reason I need the regular camera to work is for another app. The Verizon messaging app won't verify my phone number without seeing a QR code that Verizon sends to the phone. If the native camera isn't working then the Verizon app view doesn't work.
There is for the T813 (which I use). Other versions some days older or newer. Native camera does not work on the T813. All mentioned in firs post. The OP is RipeeThere is no 12/23 release in this location
LineageOS Downloads
lineageos.wickenberg.nu
Where did you find that release? What does Rupee mean in your signature ?
Also, the reason I need the regular camera to work is for another app. The Verizon messaging app won't verify my phone number without seeing a QR code that Verizon sends to the phone. If the native camera isn't working then the Verizon app view doesn't work.
Thanks. One more question. I tried to reinstall from a backup of Lineage 17 and it did not work. Do you have trouble with using backups?
I just installed the exact same configuration.
Unfortunately, Open Camera doesn't work (the app shows front or back camera signal after some seconds but crashes when I try to take a photo).
Are you using a specific configuration for Open Camera?
Nope. Just install camera app and it runs fine.
EDIT: only works in landscape mode. Is reported earlier. Just discovered ;-)
Last edited:
THANKS grumpy man
Unfortunately same setup but camera not functional for taking pictures (video conferencing apps such as jitsi, zoom or skype which work without problems after the usual delayed loading).
Hi,
First of all, thanks for the hard work in this ROM. I have managed to bring to life again my old SM-T813 and it's working really well. However, the issue with the camera is a bit annoying and I was wondering if someone is still actively working on it and we may still have hope or if it's a lost cause and there are very little chances for this to be fixed.
Thanks
First of all, thanks for the hard work in this ROM. I have managed to bring to life again my old SM-T813 and it's working really well. However, the issue with the camera is a bit annoying and I was wondering if someone is still actively working on it and we may still have hope or if it's a lost cause and there are very little chances for this to be fixed.
Thanks
I was using LOS17 on my t813 but I decided to go back to LOS16. So I downloaded the rom and gapps, put them on a pen drive, rebooted my tablet in recovery mode (runnig latest TWRP), wiped everything (system, cache, dalvik, internal storage), connected pendrive through OTG cable but discovered that the ROM file was corrupt, so I downloaded it again but now my tablet is no longer recognising the OTG drive.
So I tried the adb sideload method, no luck device is not found.
MTP is enabled but PC is not seeing the device.
At this point I'm stuck. What could I do?
So I tried the adb sideload method, no luck device is not found.
MTP is enabled but PC is not seeing the device.
At this point I'm stuck. What could I do?
Last edited:
You couls try to start the device in Download Mode. If it's recognised by you PC, you could flash latest modem, recovery, ROM etc. through odin. Yu would have to go through a lot more trouble to go back to LOS but at least the device is not bricked.
Or maybe, if the device is recognised try to go from download to recovery and see if you can sideload. idk. looks like you will have some work coming you way
Where do I get latest modem, recovery, ROM? I tried sammobile.com but the ROM is archived and can only be accessed with a paid subscription.
I do have a TWRP backup that I had done before installing LOS. The zip contains 3 img files (boot, recovery, system). Don't know what to do with without twrp.
I do have a TWRP backup that I had done before installing LOS. The zip contains 3 img files (boot, recovery, system). Don't know what to do with without twrp.
I spoke too soon. Device is booting to Rom, after I force reboot, some 15 minutes later, the device boots to Rom gets stuck in the LOS boot animation and then reboots to recovery. Any idea?
Last edited:
I
Would also like to know if the camera is still being fixed, especially since it was still working in the summer release.
bmwdroid
Senior Member
- Mar 8, 2014
- 1,914
- 1
- 821
Perhaps it helps starting from scratch means flashing stock via odin.
At least it often helped on my devices.
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.
