[ROM][UNOFFICIAL][T819][9] LineageOS 16.0

inbx · Oct 23, 2018 at 3:37 PM

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).

emuandco · Oct 23, 2018 at 8:03 PM

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.

linoux · Mar 31, 2016 13 1 3

inbx said:
Please correct me if I miss something, this is my current understanding:
- 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)?
.

It works with the last version of heimdall (1.4.2). You can install if from source (see gitlab.com/BenjaminDobell/Heimdall).

inbx · Oct 24, 2018 at 4:08 PM

linoux said:
It works with the last version of heimdall (1.4.2). You can install if from source (see gitlab.com/BenjaminDobell/Heimdall).

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?

linoux · Mar 31, 2016 13 1 3

inbx said:
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?

Yes, I did exactly what you wrote

stevenandree · Feb 1, 2014 4 0 0

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.

emuandco · Nov 16, 2018 at 7:59 AM

stevenandree said:
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.

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 ^^

FlCoura · Nov 28, 2018 3 0 0

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?

emuandco · Dec 3, 2018 at 8:53 AM

Nope ^^

Blubber120 · Dec 7, 2018

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.

Egor Duda · Jan 7, 2019 3 0 0

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!

LuK1337 · Jan 8, 2019 at 8:24 AM

Egor Duda said:
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!

If encryption breaks it then I'll try to find some motivation to fix it myself in the somewhat near future.

Flondy · Jan 12, 2019

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

Would be appriciate help

emuandco · Jan 10, 2019

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

ghostofhtc · Jan 11, 2019 at 8:35 AM

Thanks a lot @LuK1337 !

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).

Egor Duda · Jan 7, 2019 3 0 0

LuK1337 said:
If encryption breaks it then I'll try to find some motivation to fix it myself in the somewhat near future.

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

Code:

[email protected]:~# adb root
restarting adbd as root
[email protected]:~# 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 [email protected]/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 [email protected]/legacy/0 (v1.0) dumpState: ==
== Camera HAL device [email protected]/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 [email protected]/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.

LuK1337 · Jan 11, 2019 at 1:41 PM

Egor Duda said:

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

Code:

[email protected]:~# adb root
restarting adbd as root
[email protected]:~# 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 [email protected]/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 [email protected]/legacy/0 (v1.0) dumpState: ==
== Camera HAL device [email protected]/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 [email protected]/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.

Try that https://review.lineageos.org/c/LineageOS/android_device_samsung_msm8976-common/+/238720

Egor Duda · Jan 7, 2019 3 0 0

LuK1337 said:
Try that review.lineageos.org/c/LineageOS/android_device_samsung_msm8976-common/+/238720

Remounted /system read-write
Edited /system/vendor/etc/init/hw/init.qcom.rc
Remounted /system read-only
Rebooted

Everything works great now! Thanks!

Flondy · Jan 13, 2015 13 0 0

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 ----------

emuandco said:
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

Sorry my failure fixed ... it worked with new twrp version.

emuandco · Jan 18, 2019 at 8:08 AM

I never used a root addon. I prefer working SafetyNet and thus install Magisk for root. That works fine.

[ROM][UNOFFICIAL][T819][9] LineageOS 16.0

New member

Senior Member

Member

New member

Member

New member

Senior Member

New member

Senior Member

Senior Member

New member

Recognized Developer

Member

Senior Member

Member

New member

Recognized Developer

New member

Member

Senior Member