yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Original Android Development] pitrus-:
Hi, and sorry for late reply. I haven't really gotten time to stick around XDA for the last two years, mostly due to family life, a now two almost three years old daughter who always wants to play with her father. :)

Anyways, as I'm home with sick leave I actually got some time to work on my buildbot, and as ripee has moved the manifest files for gts210/gts28 over to team-infusion I now got time to update the buildbot to use these. So hopefully we soon have monthly builds of both 16 and 17.1 up an running if all goes well.

I've also updated the URL:s to use my new rockhost domain, so the new download URL is https://los.rockhost.se and buildbot is reachable through https://buildbot.rockhost.se as well.
[Galaxy Tab S2 Original Android Development] fmc000:
First of all, thank you for your work.

Please note that it seems that your newer LOS16 builds break SIM detection on T*19 . The last known working if from November 2021.
[Galaxy Tab S2 Original Android Development] pitrus-:
Update your URL, the new page for downloads is https://los.rockhost.se. Shorter and simpler to remember. :)

Apparently many of the important gerrits/fixes for RIL are marked as abandoned and without perfect knowledge of how cherry picking works, I suspect they failed. I've mirrored the source tree and reapplied the patches manually and they will be reintegrated in next build (if it succeeds that is). https://review.lineageos.org/q/msm8976+branch:lineage-16.0

Here's the updated manifest file and the updated msm8976-common tree being used.

https://gitea.rockhost.se/Piteball/local_manifests/src/branch/lineage-16.0/gts210velte.xml

https://gitea.rockhost.se/Piteball/android_device_samsung_msm8976-common
[Galaxy Tab S2 Original Android Development] fmc000:
Hi,

Thanks for your efforts but unfortunately the build failed for gts28velte.
[Galaxy Tab S2 Original Android Development] nobbb:
...links to the gitea sources seem to be down. I get a download error trying to download the sources via repo sync, using the local_manifest of pitrus...

Greets
[Galaxy Tab S2 Original Android Development] pitrus-:
Maximum luck, Gitea accidentally pushed a wrong container tonight causing the gitea instance to fail due to database version missmatch. I'm restoring my Gitea database and will apply the temporary fix, then compilations should be successfull again.

Gitea issue

Docker :latest tag referred to 1.16.0-rc1, now it refers to 1.15.11 (downgrade) · Issue #18462 · go-gitea/gitea

Gitea Version 1.16.0-rc1 Git Version No response Operating System No response How are you running Gitea? docker via https://hub.docker.com/r/gitea/gitea Database MySQL Can you reproduce the bug on ...

github.com
[Galaxy Tab S2 Original Android Development] nobbb:
thanks for the info and take your time. I am still able to work with my own vendor directories. By the way, keep on going with your superb work. Appreciate....nobbb
[Galaxy Tab S2 Original Android Development] SirSeanM10Pro:
still on Aug security patch version of LOS 16, any reason to upgrade other than newer security patch? i always end up having to clean flash because a dirty flash breaks everything for me
[Galaxy Tab S2 Original Android Development] Houyhnhnm:
Is that the latest version with a functioning 4G LTE connectivity?

Just flashed the lineage-16.0-20220712 build and it's soo smooth =) Only issue is LTE doesn't work, only Edge.

Are older builds still available somewhere? The oldest I could find in there is from May. I'd really like to flash the newest one where LTE works 🙏
[Galaxy Tab S2 Original Android Development] Harv234:
LTE works for me. But I had this effect too. I only had to change the preferred Network Type back to LTE. ;)
[Galaxy Tab S2 Original Android Development] Houyhnhnm:
Oh why didn't I come up with that before whining around 🤦‍♂️

Thanks a lot for pointing me in the right direction!!!
[Galaxy Tab S2 Original Android Development] NikLas_2310:
Anyone here who can provide the newest build? 2019 is the newest in androiidfilehost... Thanks!
[Galaxy Tab S2 Original Android Development] solved:
2019, is also the latest build where LTE works .. after this build no more mobile data
[Galaxy Tab S2 Original Android Development] ismail demirbaş:
Does it work for SM-T818 (SM-T818 is one of the tablets produced specifically for the regions)
[Galaxy Tab S2 Original Android Development] ivanox1972:
I installed rom, reboot, no problem, back to recovery, install pico open gapps, reboot, no problem!

This procedure leads to no any fc or error...
[Galaxy Tab S2 Original Android Development] Cosha:
Mobile data not working. Everything else seems to work fine
[Galaxy Tab S2 Original Android Development] bersu_guyar:
Installed with opengapps and all was well. After install, enabled encryption. Now on startup, device says password was correct but decryption failed, you need to factory reset. However, there seems to be something running on a timer so that 30 seconds after OS startup, the device restarts into recovery no matter what I do, so I cannot even factory reset. I will just reinstall without encryption, I guess.

Edit: on the plus side, I can report that the abnormal battery drain I saw with 15.1 is gone in 16.
[Galaxy Tab S2 Original Android Development] cooling29:
I'm trying to install LineageOS on T819 with 3.2.3 TWRP Recovery but I had this issue:

Comparing TZ version TZ.BF.3.0.3-00064 to TZ.BF.3.0.3-00054

Comparing TZ version TZ.BF.3.0.3-00067 to TZ.BF.3.0.3-00054

assert failed: samsung.verify_trustzone ("TZ.BF.3.0.3-00064","TZ.BF.3.0.3-00067") == "1"

I think it's something related to bootloader...should I reinstall official stock ROM?
[Galaxy Tab S2 Original Android Development] LuK1337:
noted, wait for next build.
[Galaxy Tab S2 Original Android Development] caprihome:
When battery is lower, maybe under 50 %, I have often a reboot when I am using chrome or another browser. Under lineage 15.1 it was the same. In original Samsung firmware no problems.
[Galaxy Tab S2 Original Android Development] ecotrojan:
just wanna says thanks to Luk1337
[Galaxy Tab S2 Original Android Development] ronjan:
Cellular data is not working

Great ROM :), but I think you should mention this right upfront in the first post so that people get a clear picture of what they are getting into. Went back to Lineage 15.1 where my cellular data works perfectly. Will wait for it to start working on this one.

Did try all the clearing Cache, Dalvik etc. but the cellular data just doesn't work. There is always a small cross inside the right side of the signal bar.
[Galaxy Tab S2 Original Android Development] emuandco:
Seconded, installed recent version and I get my cellular data, but it says no connection even though I get a IP and stuff. Looking into it.
[Galaxy Tab S2 Original Android Development] PMShodan:
Same problem on T719. Hope you find the culprit soon! ?
[Galaxy Tab S2 Original Android Development] linoux:
Installation of lineage-16.0-20181002_090736-UNOFFICIAL-gts210velte.zip

I just updated (with clean install) from 15.1 to 16, no gapps.

- Mobil data don't work

- It is not possible to use the launcher on the main page (the keyboard doesn't appear)

One question : how to install root as there is no addonsu for lineageOS16?

Thanks for your job :)
[Galaxy Tab S2 Original Android Development] PMShodan:
Mobile data is not working on all the Android 9 based builds (T719, T819) at the moment.

As to your question regarding root: Magisk is the answer. Install the Magisk .zip file (17.1) in recovery and the Magisk .apk afterwards once your system has booted and ... voila, you're rooted.
[Galaxy Tab S2 Original Android Development] linoux:
Regarding root : Thanks PMShodan for your answer. I wiped caches (maybe not necesssary) and installed Magisk.zip 17.1 and ... voila now I am rooted:)

---------- Post added at 11:32 ---------- Previous post was at 10:45 ----------

I intend to install gmscore on LineageOS16 T819. For the signature spooking, on LineageOS15 I used to install xposed and fakegapps. Unfortunatly, xposed is not available (yet?) for Android9.

Any suggestion?

Thanks a lot :)
[Galaxy Tab S2 Original Android Development] RawRanger:
Incall audio

I really appreciate the incredible effort you put in these ROMs and I would love to try them, but my T819 is my only phone, so the Incall Audio is something I cannot do without. It must be a complicated aspect to fix as it carried over from 15.1. I know you've had the question several times before, but I still wonder if there's a chance it will work in 16.0? I really wanted to install 15.1 and now install 16.0 even more. Thanks!
[Galaxy Tab S2 Original Android Development] GNUDroid:
Thank you for the ROM!

I use the device as a pure tablet without sim. So I can deal with the bug. as a hint for others (had a battery drain in los 15): one can disable ril via build.prop.

One small bug for me: Rotation of the screen seems to stop working. Is it just me?
[Galaxy Tab S2 Original Android Development] emuandco:
Btw, recent builds should have fixed mobile data thx to jav and LuK1337. NO not incall audio ^^
[Galaxy Tab S2 Original Android Development] maxhux:
Sorry, i'm not sure if I really understand what you wrote...

You want to say that:

- mobile date is working and

-incall audio is also ok?

Thanks in advance...
[Galaxy Tab S2 Original Android Development] wetzer123:
No.

Moblie data is working, incall audio not.
[Galaxy Tab S2 Original Android Development] Chazy12:
Nothing for the T815?! ???
[Galaxy Tab S2 Original Android Development] emuandco:
Not in here, nope.
[Galaxy Tab S2 Original Android Development] inbx:
Summary on how to get LOS 16.0 onto the T819

Please correct me if I miss something, this is my current understanding:

- Enable developer mode

- Enabe USB debugging

- I tried heimdall but didn't get it to work with the latest bootloader I have on the T819. So it's most probably downloading and installing ODIN (//odindownload.com/download/Odin3_v3.13.1.zip)?

- Download latest suitable TWRP (//dl.twrp.me/gts210velte/twrp-3.2.3-0-gts210velte.img.html)

- Use ODIN to flash TWRP

- Transfer latest image (see beginning of this thread) onto SD-Card - is there any difference between androidfilehost and sourceforge? I would expect no, but on quick glance the size seems to differ

- Flash this image from within TWRP

Are these the sources you trust or are there better ones (especially for ODIN ,which looks like a total opaque code blob).
[Galaxy Tab S2 Original Android Development] emuandco:
You forgot to format /data in TWRP due to the fact it's encrypted in a non TWRP compatible way. For what you need the first two ones I am not sure. Else looks fine for me. Maybe some OpenGAPPS would be a good idea too. I recommend to read the few pages we have here and in the T719 thread to get some insight what to do with the gapps package if you have problems with SetupWizard and other stuff.
[Galaxy Tab S2 Original Android Development] linoux:
It works with the last version of heimdall (1.4.2). You can install if from source (see gitlab.com/BenjaminDobell/Heimdall).
[Galaxy Tab S2 Original Android Development] inbx:
Thanks, I will give it a try on Linux. So it's basically downloading the latest TWRP (twrp-3.2.3-0-gts210velte), install Heimdall 1.4.2 or master and run "heimdall flash --no-reboot --RECOVERY twrp-3.2.3-0-gts210velte.img", correct?
[Galaxy Tab S2 Original Android Development] linoux:
Yes, I did exactly what you wrote:o
[Galaxy Tab S2 Original Android Development] stevenandree:
Just wanted to say thanks and also for reference to those considering it in Australia.

Works great if you follow the instructions and helps if you have some knowledge of rooting/flashing. No problems experienced yet, the only note through the process is after installing TWRP to make sure that you don't let it reboot otherwise it overwrites bootloader. Disable auto reboot in Odin and then poweroff and reboot to bootloader.
[Galaxy Tab S2 Original Android Development] emuandco:
Well you can keep auto reboot on, but then you must be prepared to push the typical recovery boot button combination IMMEDIATELY after flashing is complete. Otherwise you are best set with switching off, yeah ^^
[Galaxy Tab S2 Original Android Development] FlCoura:
Some news about phone/ incall audio on t819????

---------- Post added at 09:22 PM ---------- Previous post was at 09:18 PM ----------

Some news about phone/ incall audio on t819?
[Galaxy Tab S2 Original Android Development] emuandco:
Nope ^^
[Galaxy Tab S2 Original Android Development] Blubber120:
What Bootloader do I have to use for this release? And where am I able to get it from? Thanx

TWRP even mentions that this file is for gts210velte weird. Is there any way to fix it.
[Galaxy Tab S2 Original Android Development] Egor Duda:
Camera stops working after tablet encryption

Hi, LuK1337!

First of all, thanks for great work!

I wonder if you can help me debug a problem with camera. Steps to reproduce:

Download latest ROM lineage-16.0-20181228_193344-UNOFFICIAL-gts210velte.zip

Download open_gapps-arm64-9.0-nano-20181229.zip from opengapps.org

Download addonsu-16.0-arm64.zip

Installed twrp-3.2.3-0-gts210velte.img

Flashed ROM, Gapps and root addon

Booted system, without configuring mobile data and wifi

Started Camera app (com.android.camera2), it works

Go to Settings->Security->Encryption&Credentials->Encrypt tablet

After rebooting tablet gets encrypted, started Camera app, it exits immediately

Here are links to dmesg and logcat: pasted.co/ 0d3df615 and pasted.co/ 19a265f6 after encryption and an attempt to start Camera app

(sorry for garbled links, this forum does not allow me to post links yet)

What can I do further to debug this problem?

Thanks a lot in advance!
[Galaxy Tab S2 Original Android Development] LuK1337:
If encryption breaks it then I'll try to find some motivation to fix it myself in the somewhat near future.
[Galaxy Tab S2 Original Android Development] Flondy:
This not 4 T819 ?!

Sorry if i missunderstood this but why ur writing "T819" in Title ?

I tried flashing this but twrp says me "This package is for device: gts210velte; this device is ."

So whats the difference ?

Both are Galaxy Tab S2 - LTE (2016) right ?

Under settings screen on my Device there is "T819 "

So whats the problem :(:confused:

Would be appriciate help :o:D
[Galaxy Tab S2 Original Android Development] emuandco:
T819 != T813

T819 = Galaxy Tab S2 - LTE (2016)

T813 = Galaxy Tab S2 - WIFI (2016)

If you have a T819 and get such an error.... which TWRP do you have in use? Sounds very ancient then... most recent stuff: See my sig
[Galaxy Tab S2 Original Android Development] ghostofhtc:
Thanks a lot [MENTION=5075128]LuK1337[/MENTION] !

Build lineage-16.0-20190109_043157-UNOFFICIAL-gts210velte works fine.

Since now everything is working except - as you wrote - incall audio. Tried to use it by bluetooth, but there is nothing in or out (micro+speaker).
[Galaxy Tab S2 Original Android Development] Egor Duda:
Thanks for prompt answer!

Ok, I've found a workaround -- restarting android.hardware.camera.provider process fixes the problem. I guess it starts before user have a chance to enter decryption password and tries to read something from /data or some other not yet mounted partition.

I'm not yet that proficient with android to find where this race condition plays out exactly, but hope this helps

root@fox:~# adb root
restarting adbd as root
root@fox:~# adb shell
gts210velte:/ # dumpsys media.camera

== Service global info: ==

Number of camera devices: 0
Number of normal camera devices: 0
Active Camera Clients:
[]
Allowed user IDs: 0

== Camera service events log (most recent at top): ==
01-11 15:27:39 : USER_SWITCH previous allowed user IDs: <None>, current allowed user IDs: 0

== Camera Provider HAL legacy/0 (v2.4, remote) static info: 0 devices: ==

== Vendor tags: ==

Dumping vendor tag descriptors for vendor with id 3854507339
Dumping configured vendor tag descriptors: None set

== Camera error traces (0): ==
No camera traces collected.
gts210velte:/ # pgrep -f android.hardware.camera.provider
406
gts210velte:/ # pkill -f android.hardware.camera.provider
gts210velte:/ # pgrep -f android.hardware.camera.provider
5604
gts210velte:/ # dumpsys media.camera

== Service global info: ==

Number of camera devices: 2
Number of normal camera devices: 2
Device 0 maps to "0"
Device 1 maps to "1"
Active Camera Clients:
[]
Allowed user IDs: 0

== Camera service events log (most recent at top): ==
01-11 15:29:31 : ADD device 0, reason: (Device added)
01-11 15:29:31 : ADD device 1, reason: (Device added)
01-11 15:27:39 : USER_SWITCH previous allowed user IDs: <None>, current allowed user IDs: 0

== Camera device 0 dynamic info: ==
Device 0 is closed, no client instance
== Camera device 1 dynamic info: ==
Device 1 is closed, no client instance
== Camera Provider HAL legacy/0 (v2.4, remote) static info: 2 devices: ==
== Camera HAL device device@1.0/legacy/0 (v1.0) static information: ==
Resource cost: 100
Conflicting devices: None
API1 info:
Has a flash unit: false
Facing: Back
Orientation: 90
API2 not directly supported
== Camera HAL device device@1.0/legacy/0 (v1.0) dumpState: ==
== Camera HAL device device@1.0/legacy/1 (v1.0) static information: ==
Resource cost: 100
Conflicting devices: None
API1 info:
Has a flash unit: false
Facing: Front
Orientation: 270
API2 not directly supported
== Camera HAL device device@1.0/legacy/1 (v1.0) dumpState: ==

== Vendor tags: ==

Dumping vendor tag descriptors for vendor with id 3854507339
Dumping configured vendor tag descriptors: None set

== Camera error traces (0): ==
No camera traces collected.
[Galaxy Tab S2 Original Android Development] LuK1337:
Try that https://review.lineageos.org/c/LineageOS/android_device_samsung_msm8976-common/+/238720
[Galaxy Tab S2 Original Android Development] Egor Duda:
Remounted /system read-write

Edited /system/vendor/etc/init/hw/init.qcom.rc

Remounted /system read-only

Rebooted

Everything works great now! Thanks!
[Galaxy Tab S2 Original Android Development] Flondy:
no root ?

Hi guys, i´ve activated Root for adb & apps under dev. options….

Galaxy Tabs S2 LTE

flashed the Lineage OS 16 ROM & Gapps & the ROOT ZIP File 4 OS 16 (Android 9)

But Root Checker says there is no Root ?

And every app which asked for granting Root says it even…

So whats wrong ?

Whyi can activate root under dev. options but don´t get root?

Do i need an Root Manager or is that included in the ROM?

---------- Post added at 09:44 AM ---------- Previous post was at 09:41 AM ----------

Sorry my failure fixed ... it worked with new twrp version.
[Galaxy Tab S2 Original Android Development] emuandco:
I never used a root addon. I prefer working SafetyNet and thus install Magisk for root. That works fine.
[Galaxy Tab S2 Original Android Development] dantibes:
Hi

I installed the ROM v. 16.01.2019, gapps pico and magisk 18.0, everything seems to work well, at least until now, thanks
[Galaxy Tab S2 Original Android Development] BakaNeko59:
Recent apps?

Sorry wrong thread
[Galaxy Tab S2 Original Android Development] Tarunalpha:
Hi, is this compatible with SM-T819Y ?
[Galaxy Tab S2 Original Android Development] dantibes:
warning!

I tried the last version of the rom: lineage-16.0-20190206_200057-UNOFFICIAL-gts210velte.zip

and the tablet after two days of testing had a strong overheating and then restarted often.

I had to restore another rom. I have not installed any new apps in the meantime
[Galaxy Tab S2 Original Android Development] LuK1337:
Thanks for 0 logs. You're amazing.
[Galaxy Tab S2 Original Android Development] dantibes:
I think you're referring to this file if I ask you to clarify what can serve you. Thank you for your understanding and think that I am a neophyte thanks
[Galaxy Tab S2 Original Android Development] LuK1337:
I want logcat from latest build running. last_kmsg isn't that important for me (especially last_kmsg that is showing your 'twrp running' and nothing else).
[Galaxy Tab S2 Original Android Development] dantibes:
Hi, if you tell me the file name and the path address of the folder where it is, I send you the file you need to understand the anomaly
[Galaxy Tab S2 Original Android Development] LuK1337:
adb logcat >> log.txt.

or adb logcat | tee log.txt if you're on normal OS (Loonix/MacOS)
[Galaxy Tab S2 Original Android Development] dantibes:
o.k.

as I told you I am currently using another rom, tomorrow i reinstall the lineage 16 from the last bkp I made of the last version and if the overheating occurs again I send the logcat with the adb command
[Galaxy Tab S2 Original Android Development] Tarunalpha:
Hi, I flashed this on T819Y successfully after editing updater_script file in the rom. Basically it just bypasses TZ. Will this create any trouble?
[Galaxy Tab S2 Original Android Development] LuK1337:
What TZ do you have?
[Galaxy Tab S2 Original Android Development] Tarunalpha:
TZ 74 I think
[Galaxy Tab S2 Original Android Development] Tarunalpha:
tz.bf.3.0.3-00074
[Galaxy Tab S2 Original Android Development] LuK1337:
I added it to board-info, will be included whenever I feel like rebuilding gts*velte.
[Galaxy Tab S2 Original Android Development] Tarunalpha:
Okies.

Thanks man
[Galaxy Tab S2 Original Android Development] thoreauwouldn'thaverooted:
hi, just got this tablet and will try los16 now. are there any disadvantages for not using any gapps package except for the obvious ones (no playstore comes to mind, anything else?)

thanks for making this possible LuK!
[Galaxy Tab S2 Original Android Development] DoggyStar:
Official linaegeos 16??

Will we get official linaegeos 16 some day??

I really like the unofficial version but official is allways better :)
[Galaxy Tab S2 Original Android Development] LuK1337:
If you fix incall audio then sure.
[Galaxy Tab S2 Original Android Development] DoggyStar:
I dont know anything for things like that. I only know how to flash rom and stuff :D
[Galaxy Tab S2 Original Android Development] LuK1337:
No official builds then.
[Galaxy Tab S2 Original Android Development] emuandco:
Some guy told me that the needed microphone and speaker for incall audio are simply not working at all. I still wonder if some T713/813 blob remnants are our problem, but I have not the skills to verify that... I am just happy with what I have right now after some experiments making things worse and not better ^^
[Galaxy Tab S2 Original Android Development] LuK1337:
Fixit.
[Galaxy Tab S2 Original Android Development] Montero7o:
Hello

Excuse me for my very bad translation, I'm French

Congratulations @ LuK1337 for this realization, there are several topics on XDA on the SM-T819 that I read in full, but this one seems to me the most detailed.

I have a tablet Galasy Tab S2 - SM-T819 LTE ​​Android 7 so here are the references:

- gts210velte

- Bootloader: T819XXU2BRI1

- PDA: T819XXU2BRI1

- Baseband: T819XXU2BRI1

- CSC: XEF

TWRP: twrp-3.2.3-0-gts210velte

Root: Magisk v18.1

Having discovered LineageOS 16 that I installed on an old Galaxy S5 SM-G900F, this one found a second youth despite the 2GB of RAM thanks to LineageOS 16

So now I want to install LineageOS 16 on my SM-T819 (LTE) tablet

I get the latest version lineage-16.0-20190308_141803-UNOFFICIAL-gts210velte.zip and the Gaps open_gapps-arm64-9.0-pico-20190307.

First question: does this version take into account the bootloader "T819XXU2BRI1"?

If I understood the procedure to install LineageOS it is necessary in TWRP:

- Menu Wipe / Advanced Wipe, then select "Wipe Cache + Wipe dalvik / ART cache + Wipe Data + Wipe System"

- Installed lineage-16.0-20190308_141803-UNOFFICIAL-gts210velte.zip, then open_gapps-arm64-9.0-pico-20190307

- Menu wipe Cache / Dalvik

- Restart in Recovery then install Magisk 18.1

I have an imperative: Having the 4G LTE connection active during my travels (APN: Bouygues Telecom), I know that phone calls are not operational.

Is this the right way to go?

Thank you for your answers