yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Original Android Development] markeees:
I can't find the switch to enable onscreen nav bar and disable HW buttons. Could someone tell me where this option is located in the settings ?
[Galaxy Tab S2 Original Android Development] Schuwarth:
How to install LineageOS on Stock Rom (with Windows 10)?

I need your help for installing LineageOS 16 on my T713. I followed the official wiki installation instruction for the T713 step by step, but it doesn't work. Heimdall seems to get no connection to the tab. Tests like "adb reboot" or "Heimdall version" worked but "Heimdall print-pit" failed. Then I read here in the forum, that Heimdall 1.4.0 for Windows is outdated and doesn't work. Is this right? Then the official wiki install instructions (for windows) are outdated as well and should by changed?

After that I flashed TWRP 3.3.1 with ODIN 3.12.3 successfully and booted into TWRP recovery. But I couldn't wipe anything especially /data . I flashed last LineageOS build, but as expected boot process stopped with an error.

Now I'am thankfully back on lastest stock rom via ODIN.

What was my fault?

Florian
[Galaxy Tab S2 Original Android Development] lmacmil:
I am on 16 but originally flashed 15. It failed the first time because a partition was encrypted but I didn't wipe it. Can't remember which partition it was. Not sure why TWRP wouldn't let you wipe anything. Maybe a real expert will jump in and help you out. This forum doesn't get much traffic lately.
[Galaxy Tab S2 Original Android Development] sliding_billy:
I did this with Windows 3+ months ago using LineageOS 16. TWRP was twrp-3.3.1-0-gts28vewifi.img installed with Odin3 v3.12.5. I don't recall which stock I was coming from (maybe XAR-T713XXU2BRB2_T713XAR2BRB2-20180206), but I did a full factory install with the same Odin and didn't touch it before flashing TWRP, LineageOS, Gapps, Magisk. etc. My install was around the beginning of August if you want to try to glean anything from my messages.
[Galaxy Tab S2 Original Android Development] Schuwarth:
TWRP 3.2.3-0 and 3.3.1 -0 can't wipe data partition: "Could not mount /data and unableto find crypto footer".

:confused: and now? Can a complete factory reset with the stock rom help?
[Galaxy Tab S2 Original Android Development] sliding_billy:
That is what I am thinking. Whatever partition work needs to be done as part of the Lineage install needs to be done on a clean install with the proper TWRP version.

---------- Post added at 03:09 PM ---------- Previous post was at 02:42 PM ----------

Also, I assume you are using the install instructions here. https://wiki.lineageos.org/devices/gts28vewifi/install Once you have twrp-3.3.1-0-gts28vewifion your device, it doesn't matter if you used Heimdall or Odin to get it there. Start with "Installing LineageOS from recovery." I am on open_gapps-arm64-9.0-nano-20190803. Root with Magisk, and ignore the addonsu. Make sure Magisk is set up for systemless hosts or don't use a PIN. It will loop if you do.
[Galaxy Tab S2 Original Android Development] Schuwarth:
It worked! After the Heimdall-Windows problems I forgot the wiki-step "Format Data", because I didn't have to do that on my other Lineage devices...
[Galaxy Tab S2 Original Android Development] sliding_billy:
That is great news. First and only LOS device for me unless you count old CM devices, so I wouldn't have even noticed that difference.
[Galaxy Tab S2 Original Android Development] dbuf7:
lineage-16.0-20191108 boots into recovery instead of LineageOS

twrp-3.3.1-0-gts28vewifi.img installed and appears to be working normally, except when I attempt to sideload LineageOS with adb I get

$ adb sideload lineage-16.0-20191108-nightly-gts28vewifi-signed.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found

So instead:

$ adb push lineage-16.0-20191108-nightly-gts28vewifi-signed.zip /sdcard/

and then use TWRP to flash the image from /sdcard/. Flashing produces no apparent errors in TWRP.

Thereafter, adb reboot or reboot from TWRP or powering off and then hitting the power button almost always has the same result: booting directly back into TWRP.

"Almost" because, just once, I saw the LineageOS logo for a couple minutes before going automatically to TWRP. (All the other times there is not even a LineageOS logo, and almost no delay, it just boots straight into TWRP.

Any suggestions?
[Galaxy Tab S2 Original Android Development] hamelg:
Hello,

I'm trying to build the rom with the instructions here :

https://wiki.lineageos.org/devices/gts28vewifi/build

The build fails early at the step "brunch gts28vewifi" with the error :

[331/1039] including frameworks/opt/net/lowpan/Android.mk ...
build/make/core/binary.mk:1476: error: frameworks/opt/net/lowpan/libandroid_net_lowpan/Android.mk: libandroid_net_lowpan: Unused source files: goinfre/android/lineage-16/frameworks/opt/net/lowpan/libandroid_net_lowpan.
16:34:12 ckati failed with: exit status 1

Before this error, i see a lot of warning of this kind :

build/make/core/java_common.mk:183: warning: frameworks/base/packages/SystemUI/shared/tests/Android.mk: SystemUISharedLibTests: Unused source files: /goinfre/android/lineage-16/frameworks/base/packages/SystemUI/shared/tests

by digging the makefiles, I find out it's the macro find-files-in-subdirs in the file build/make/core/definitions.mk which cause this error and the warnings.

define find-files-in-subdirs
$(sort $(patsubst ./%,%, \
$(shell cd $(1) ; \
find -L $(3) -name $(2) -and -not -name ".*") \
))
endef

If I replace it with

define find-files-in-subdirs
$(sort $(patsubst ./%,%, \
$(shell cd $(1) >/dev/null ; \
find -L $(3) -name $(2) -and -not -name ".*") \
))
endef

The error and warnings vanish, but it fails later with an other error :

[434/1039] including libcore/Android.mk ...
build/make/core/java_common.mk:118: error: FindEmulator: cd: libcore/goinfre/android/lineage-16/libcore: No such file or directory
00:00:57 ckati failed with: exit status 1

Any ideas ?

EDIT

SOLVED !

I found the culprit : I had the CDPATH variable defined in my environment. Unset it and the build works fine now :)
[Galaxy Tab S2 Original Android Development] eturk01:
Need help updating please

Haven't updated in months and when I just tried i get the error 7 in attached photo.

I'm on build:

lineageos gts28vewifi-userdebug 9 PQ3A.190605.003 3354fe3973
[Galaxy Tab S2 Original Android Development] @muja@:
Will this rom work on t819 mates...

Thanks in advance
[Galaxy Tab S2 Original Android Development] puddingoz:
Latest recovery? Twrp 3310
[Galaxy Tab S2 Original Android Development] sliding_billy:
Yes
[Galaxy Tab S2 Original Android Development] Limitscrw:
After updating the firmware, I was fighting with the Nov 14th nightly using TWRP 3.3.1-0: the LOS boot animation would loop and then reboot into TWRP.

I just went back to TWRP 3.2.3-0 and the nightly booted right away.

Hope that helps someone out there. :)
[Galaxy Tab S2 Original Android Development] eturk01:
yes v3.3.1

thank for reply!
[Galaxy Tab S2 Original Android Development] GmanGrout:
Can anyone help me please trying to install los16 with constant bootloop gone back to twrp 3.2.3 just end up in recovery each time. Thanks in advance
[Galaxy Tab S2 Original Android Development] sliding_billy:
I just updated to the Nov 18 nightly since it had been almost a week since any changes, and I had no issues using updater and 3310.
[Galaxy Tab S2 Original Android Development] dbuf7:
Thanks! I can confirm that TWRP 3.2.3 is the fix for a fresh install as well. On TWRP 3.3.1 after a fresh LineageOS install all reboots also ended in TWRP.

adb sideload is still broken in both versions of TWRP, but I was able to install no problem after pushing the LineageOS image to /sdcard/
[Galaxy Tab S2 Original Android Development] lmacmil:
I am on 3.3.1 also and have had no issues with the Lineage updater. Just updated to the 11/15 nightly.
[Galaxy Tab S2 Original Android Development] Deltadroid:
It depends on if you have encryption enabled or not. The new TWRP version is broken with encryption and does not format the data partition correctly.
[Galaxy Tab S2 Original Android Development] rholm:
How do you tell if encryption is enabled?

Thanks!

Cheers,

Rich
[Galaxy Tab S2 Original Android Development] dbuf7:
My device is dead at the moment so I can only say generally, look under Settings --> Security --> Encryption, where "Encrypt Phone" should clearly indicate the current state

---------- Post added at 09:08 AM ---------- Previous post was at 08:49 AM ----------

This is not working for me as well. This is what I have seen so far:

Installed (fresh over Samsung OS) twrp-3.3.1-0-gts28vewifi.img with heimdall, this works except all attempts to sideload LOS fail with "no devices/emulators found", pushed to /sdcard/ instead.

Installed lineage-16.0-20191108-nightly-gts28vewifi-signed.zip, flashing produces no apparent errors in TWRP.

Thereafter, adb reboot or reboot from TWRP or powering off and then hitting the power button almost always has the same result: booting directly back into TWRP.

Then I installed twrp-3.2.3-0-gts28vewifi.img (old version) and reinstalled lineage-16.0-20191108-nightly, this seemed to work! Booted into LOS and turned on encryption. This failed badly, back to every boot returning to TWRP, and LOS reinstalls did not fix this.

Then I installed a still older twrp-3.2.2-0-gts28vewifi.img, reinstalled lineage-16.0-20191108-nightly, turned on encryption, and this failed in the same way as twrp-3.2.3. I am going to call encryption dead in TWRP 3.2.

Then I (re-)upgraded to twrp-3.2.3-0, reinstalled lineage-16.0-20191108-nightly, passing on encryption. Then attempted to upgrade running LOS to lineage-16.0-20191119-nightly with the LOS updater. Broken again: all reboots go back to TWRP.

From where I sit, it looks like the current combination of TWRP/LOS images is quite broken. Has anyone recently done a new install and had success? Or is everyone updating devices that were setup a long time ago?
[Galaxy Tab S2 Original Android Development] sliding_billy:
I installed 'lineage-16.0-20190802-nightly-gts28vewifi-signed' and 'open_gapps-arm64-9.0-nano-20190803' using 'Odin3 v3.12.5' and 'twrp-3.3.1-0-gts28vewifi.img' at the beginning of August. I rooted with Magisk (not sure what version was stable then, but that is what I used).
[Galaxy Tab S2 Original Android Development] Deltadroid:
Because you have to format the data partition with twrp 3.2.3 to create a working encryption footer. You formatted with new broken twrp so it falls.

Edit: and don't install twrp's app or it will not boot
[Galaxy Tab S2 Original Android Development] Schuwarth:
strange behaviour of auto brightness

Is the auto brightness function working correctly? When I come form a dark environment into a bright environment auto brightness mostly switches to nearly maximum brightness. I know, under Pie it should be intelligent, but for me it's rather stupid... It doesn't learn.

And is there no more option to deactivate WLAN in standby?

Thanks!
[Galaxy Tab S2 Original Android Development] AlbSlopeSoar:
Bluetooth Issues

I've just found that I can't connect to bluetooth audio devices. They don't even turn up in the available list. Other devices are detected and pair (keyboard, mouse, phone, etc.), but neither of my speakers. I tried clearing the bluetooth app cache, and restarting, but it hasn't helped.

I'm currently running the Nov. 24 nightly, and had installed the latest stock ROM before wiping and installing Lineage OS 16 with OpenGaps 9.0.
[Galaxy Tab S2 Original Android Development] lmacmil:
I'm on the 11/15 nightly and have no problem connecting to my UE Boom Bluetooth speaker. I used Mind-the-Gapps when I first installed LOS 16 back in February. I've been updating about once every two months since then.
[Galaxy Tab S2 Original Android Development] AlbSlopeSoar:
All my fault, the audio devices were hiding in the Previously Connected Devices tab and not showing up in the Available Devices.
[Galaxy Tab S2 Original Android Development] Icmer:
Audio skips on Spotify and YouTube Vanced when switching between apps or opening home screen. Tried in core only mode, wired, and Bluetooth. On latest nightly 12/01 with Lawnchair v2

Edit: Someone in the T813 thread said using openGapps Pico instead of nano fixes it. Flashed pico after a clean install and no more skipping.
[Galaxy Tab S2 Original Android Development] eturk01:
Older builds?

Where can we find old builds?

I'm on July 4, 2019 build. Builds from Nov+ are not installable by the Updater. So want to try August+ build.
[Galaxy Tab S2 Original Android Development] getreal:
I have tab s2 9.7 inch. Lte version, model no T817, it is exynos not Snapdragon. Which file should I use for custom Rom?
[Galaxy Tab S2 Original Android Development] Dnorris55:
I'm on Dec 01 build, updated via the updater. No problems updating...
[Galaxy Tab S2 Original Android Development] dbuf7:
I, however, also have problems if updating JUST using the updater. I end up in a state where reboots always land in recovery, Android will not start. I am still poking at the thing, but this just worked:

* Download the new update with the updater

* reboot into recovery

* use recovery to flash the update manually

At this point I am, as described previously, stuck and cannot boot Android, only recovery.

* flash a different version of TWRP. (I am currently alternating between 3.1.1 and 3.2.2, others here have described 3.2.3 as somewhat "broken".)

* do NOT wipe anything, just

* boot Android.

Next time I am going to try just re-flashing the same version of TWRP.
[Galaxy Tab S2 Original Android Development] eturk01:
Looks like the updater requires at least build TZ.BF.3.0.3-00064

my July build is ...00054. Removing the requirement to force install makes the install unbootable to something changed in a major way. (see error message in pic)

Where can we find older builds?

esp. that ...00064 build
[Galaxy Tab S2 Original Android Development] Dnorris55:
I checked my sdcard, and I have a few of the older builds: July 29, Aug 05, Aug 07, Sept 07.

Here's a link to Aug 05:

https://drive.google.com/open?id=1ULVf4HHo4Dvb17OX9gvBMe5_MH15ViVg

and Sept 07:

https://drive.google.com/open?id=1qND8eBS-ZuXNVmeNSinqzYRVc6wh1YIl
[Galaxy Tab S2 Original Android Development] eturk01:
[MENTION=5604884]Dnorris55[/MENTION] thanks a bunch mate!

Aug update worked. Sept failed check of ...00064 also so something big changed between those two builds

Wonder how I can get it to update?
[Galaxy Tab S2 Original Android Development] EVOLw:
Who have error7 After august updates, Try this build https://drive.google.com/file/d/1tp1JZxy--b7ewpwyQbBgq7u8G71txq69/view?usp=drivesdk
[Galaxy Tab S2 Original Android Development] eturk01:
Thanks a bunch for providing that build, which I could install!!!!

Unfortunately, trying to install with the Updater still fails the trustzone assert.
[Galaxy Tab S2 Original Android Development] Deltadroid:
Just update your firmware from latest stock ROM with either heimdall or odin. Search this thread, there are instructions on several posts.
[Galaxy Tab S2 Original Android Development] eturk01:
thanks!!

So I need to reset to stock Samsung ROM then back to LineageOS?

They did some major update in August that required everyone to do this?
[Galaxy Tab S2 Original Android Development] Deltadroid:
you can download your latest stock rom from sammobile and extract it. Then only flash the partitions that do not overwrite lineage. This is the heimdall command to flash the required partitions and then you can just update lineage as usual. You won't need to factory reset or do anything else.

heimdall flash --SBL1 sbl1.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn --HYP hyp.mbn --SEC sec.dat --KEYMASTER keymaster.mbn --CMNLIB cmnlib.mbn --DSP adspso.bin --MODEM modem.bin --APNHLOS NON-HLOS.bin
[Galaxy Tab S2 Original Android Development] andreaschen:
Hello I am in kind of emergency to replace my current tablet. I saw Samsung Galaxy Tab S2 8.0 SM-T713 32GB Wi-Fi Nook Edition SM-T713NZKEXAR. Does this hardware allow me to flash this LOS 16 within reasonable amount of work? (not too much hacking what's so ever...) Thanks!
[Galaxy Tab S2 Original Android Development] lmacmil:
Any idea why battery drain varies so much from one build to the next? Some builds will only lose 1% overnight and others will lose 7-8%. I usually only update once a month to keep current on the monthly security patches but the 12/18 build was one of those high drain builds so I updated to the 12/23 today. We'll see how it goes.
[Galaxy Tab S2 Original Android Development] oswald-p:
I dream to have a 1% over night battery drain. What build did you use? How does the things goes with your new update?

Cheers.

O-p

Envoyé de mon SM-T713 en utilisant Tapatalk
[Galaxy Tab S2 Original Android Development] lmacmil:
I've had a couple builds with 1% overnight drain though that might have been in airplane mode. I lost 5 or 6% last night. I will put it in airplane tonight and see what happens.

Drain for 12 hours in airplane was 3% on the 12/23 build. According to AccuBattery it was in deep sleep 96% of the time.
[Galaxy Tab S2 Original Android Development] Techguy777:
Well ive been using this rom for a week now and im going to say very happy with it. I went back to oreo along time ago because I don't like bugs anymore so being on the latest version of android makes no sense unless you would get something the older versions cant do which nothing in the last few years. I do like UI upgrades but again stability and no bugs is more important. This rom here is running no bugs whatsoever except if I use edxposed which is edxposed because it causes the same bugs on all devices. Its just the only way to get your SDcard to allow you to save to it even if the app doesnt allow it. Id recommend the jump if your on 7 or 8 android this rom is rock solid and a little battery drain at night is solved with plugging it in. Very nicely done. Ive found 0 issues .
[Galaxy Tab S2 Original Android Development] Techguy777:
Sorry wrong thread im on T813 not this one. I was wondering why there was 5 different threads for the same rom. lol
[Galaxy Tab S2 Original Android Development] lmacmil:
Because the threads are device specific, not ROM specific.
[Galaxy Tab S2 Original Android Development] EvilWayz:
Whats the keypress to get into TWRP once its successfully installed? Ive flashed it three times with ODIN, and i get the pass and reset, but can't get to TWRP, just blue screen download or black screen recovery.
[Galaxy Tab S2 Original Android Development] tripLr:
Set up odin to not reboot

When you flash do not tick reboot

When you complete the flash in download mode

Do this.

Power +down volume + home to force reboot

Immediately when the screen goes black

Switch to

Power + UP volume + home

To boot to twrp for the first time.

Click Allow modifications.

That's it.

If it boots to the black screen , you have to start over

The twrp flash gets erased unless you do the above
[Galaxy Tab S2 Original Android Development] EvilWayz:
Tried it five times, the sixth time it factory reset my device.

Theres no way to reboot to bootloader without a keypress?? ADB sideload or something? My volume keys are on their last legs.

do i let go and repress power and home? or can i just let go of vol down and switch to vol up
[Galaxy Tab S2 Original Android Development] WagaJr:
You can use ADB to get into download mode and flash TWRP with fastboot. You have to make sure you have the right USB drivers because I was never able to flash using the ADB method. Fastboot didn't work for me for whatever reason. You can try to follow this.

https://www.xda-developers.com/how-to-install-twrp/
[Galaxy Tab S2 Original Android Development] EvilWayz:
thanks ill give this a try. I really hate Verizon right now.

---------- Post added at 03:50 PM ---------- Previous post was at 03:22 PM ----------

I don't think its rebooting into bootloader. I have tried hte way it said plus the way it says in the man pages, sdb reboot-bootloader.

Anyone have a screenshot of their tab in bootloader?
[Galaxy Tab S2 Original Android Development] tzinaski:
Hi

I just flashed LineageOs 16 and enabled root access from developer options. Now, can i install magisk manager and modules, or will i have some problem since i didnt root with magisk method?
[Galaxy Tab S2 Original Android Development] lmacmil:
Once or twice a day my tablet will freeze for 5 seconds or so. Doesn't seem to be related to any particular app. Once it "unfreezes" it works normally. Currently running the January 16th nightly but it did it on earlier builds also. Usually happens soon after it's been awakened from sleep mode. Anyone else seeing this?
[Galaxy Tab S2 Original Android Development] ripee:
My work on Q (no builds yet but the sources are coming along)
[Galaxy Tab S2 Original Android Development] Krystanos:
Hello,

I have just updated my version from july 2019 to latest version, after flashing the stock updates with Heimdall to avoid error 7, with cache and ART cache wipe.

And now I have a 45 minutes battery lifetime, tablet is hot as hell.

Am I the only one with this issue ?

EDIT: with another reboot, another cache wipe, everything is back to normal. Battery is spectacular with the new wifi drivers. Still not as good as stock, but far far better. My tablet is alive again. Great work!!!!
[Galaxy Tab S2 Original Android Development] Just Call Me Lucifer:
Anyone been able to use Expressvpn on this ROM? Whatever I try, I always end up with an 'unable to connect' error in the VPN-app.
[Galaxy Tab S2 Original Android Development] :
Same here. It's been this way for months.
[Galaxy Tab S2 Original Android Development] asphodeli:
Hi guys,

How do I get Widevine L1 on this device?
[Galaxy Tab S2 Original Android Development] usblaidas:
I've just installed this rom and so far its really great! However, on a hangouts call I've the other party has informed that they are able to hear themselves. Is it possible that audio echo cancelling is not working? Perhaps there's a setting that I'm missing? What are your thoughts on this?
[Galaxy Tab S2 Original Android Development] Deltadroid:
This is a known issue for this device on Pie. I'm not sure how to fix it. Nougat does not have this problem.
[Galaxy Tab S2 Original Android Development] fjason@iprimus.com.au:
cant get this rom working at first I was getting error 7 then i installed new firmware and now it boots into the boot sequence and then back into twrp not sure what els I can try can anyone give me some tips please

im using this firmware:T713ZCU2BSI3_T713CHN2BSI3_CHN because it's the newest

edit: got it working
[Galaxy Tab S2 Original Android Development] ripee:
Unless you bought your tablet in China, I would suggest using the latest non-ZC/ZH stock bootloader. For T713, that would be T713XXS2BSG1. Using a Chinese bootloader on a non-Chinese unit caused random reboots and the chip running very hot after playing videos, not to mention while playing them, as I found out on my old T810.
[Galaxy Tab S2 Original Android Development] fjason@iprimus.com.au:
thanks I got it working using my regular firmware
[Galaxy Tab S2 Original Android Development] pointbob:
dumb question but i'm not the brightest bulb at times.

I recently installed lineage os 16 working on my sm-t713. Looks good but if I want to download and try a nightly build do I have to re-install from scratch and lose my settings? if I can keep my settings/programs etc - how do i do that with the nightlys?

also - what is the best/easiest way to do a total backup of my tablet (with existing Lineage os) so it includes everything/settings/etc...can TWRP do that or?

thanks
[Galaxy Tab S2 Original Android Development] Turnilemikus:
If I'm understanding you correctly, just download the nightly via the Lineage update function in the settings. Your set up will be the same. If you rooted with Magisk, it'll still be rooted.

For backup entirely, it's as simple as loading TWRP and swiping backup. I'd recommend you keep it stored on an external SD card, if you have one.

Make a backup then try out the update. Both are super simple and you won't experience any snags.