yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Original Android Development] johnbelloh:
Lineage 16.0 updates failing on Samsung devices

All nightly builds on Samsung devices since 8/9/19 are having trust failures when trying to update either with the updater or manual update with TWRP. All my devices are running the latest bootloaders. I believe this change from the change log of 08/09/19 is causing the problem:

Changes included in lineage-16.0-20190809-nightly-gts210vewifi-signed.zip

msm8976-common: Add TZ.BF.3.0.3-00077 to trustzone assert android_device_samsung_msm8976-common.
[Galaxy Tab S2 Original Android Development] OhioYJ:
Nice! Odin is much easier in my opinion. I would assume it's also OK to strip out whatever you don't want flashed from the full file and place it in the AP slot without issue?

This is been being discussed the last couple pages. See this post. There was new firmware released this year believe it or not (I was surprised actually). Are you sure you are on the latest? This is most likely what you are referencing. It's caught a lot of people off guard.

See these posts:

[Guide]Update Firmware using Heimdall - T813

Updating Using Odin.
[Galaxy Tab S2 Original Android Development] Max-82:
I have been one of those people who installed the newest German build without the sec.dat file before updating to the newest Lineage build, which went without any noticable problems. So what exactly is the function of this sec.dat file and is it essential in any way since I thus have not installed it on my device? Is it somehow related to the Qualcomm Secure Booting or to the Secure Mode in Download mode, since I found that download mode doesn't work and recognize my device as it had in the past? Thanks in advance for an answer and big thanks and appreciation to the developers of this absolutely great ROM!
[Galaxy Tab S2 Original Android Development] netbuzz:
Yes, you can do that. You'll need to create a tar file for what you want to flash from the full Samsung image file. The AP slot only accepts tar files.
[Galaxy Tab S2 Original Android Development] Deltadroid:
I have compared sec.dat in all of Samsung's Nougat firmware updates for T813 and sec.dat has never changed, so, I don' think that is the reason for your issue.
[Galaxy Tab S2 Original Android Development] Max-82:
Thanks for the reply. Well, it turned out I was able to get Download Mode working after all, was too quick to jump to conclusions. So I flashed sec.dat through Odin from the Canadian build just to be certain there won't be issues in the future because of not flashing that file and everything is working as expected now.
[Galaxy Tab S2 Original Android Development] kida182001:
I'm currently still on RR ROM because I read that Lineage 16 has battery drain issue and the user would have to put the tablet on airplane mode during sleep to remedy it. Has this been addressed in the latest updates? TIA
[Galaxy Tab S2 Original Android Development] CarlosCalderon:
Without Naptime (killing wifi while screen is off) standby battery time is pretty bad - build is from 08/09.

With Naptime is OK. But the refreshing time you need after waking it up, it's a bit underwhelming.

Gesendet von meinem Pixel XL mit Tapatalk
[Galaxy Tab S2 Original Android Development] no_means_no:
Thank you very much. It's updating again. Odin is super easy to use.

I guess I'm speaking for a lot of people here: THANK YOU!!!
[Galaxy Tab S2 Original Android Development] Spielmops:
No Wifi after clean install today

What is your LineageOS version: 16.o from2019/08/15

LineageOS Download url: download.lineageos.org

Gapps version: n. a.

Did you wipe:

- clean install from stock-Nougat to LineageOS via TWRP 3.3.3(latest) without any error-messages, format data, delete cache and dalvik, reboot to system

restore with titanium backup: was new

reboot after having the issue: a dozen times

Are you using--

a task killer: no

a non-stock kernel: no

other modifications: addonSU

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

The first thing after initial start of LineageOS was "connect to my wifi", but the wifi connection-setup alternates between "connecting" and "saved". I tried it with 3 Networks and both bands and my networks are good.

Seems to my like a "wrong firmware-error", but I read nowhere about any firmware-update.

Any advice? (hint: this is not the first device, on which I installed LineageOS)

Spielmops
[Galaxy Tab S2 Original Android Development] Deltadroid:
Try turning the tablet off and back on, not just a restart.
[Galaxy Tab S2 Original Android Development] Spielmops:
That's always the first thing I do ...

Spielmops
[Galaxy Tab S2 Original Android Development] Deltadroid:
Can you give more details about your wifi setup?
[Galaxy Tab S2 Original Android Development] davidnw:
I have a T813 and T819 tablet using this ROM. On the T819 the GPS is not working. Does anyone have the GPS working on the T819?
[Galaxy Tab S2 Original Android Development] Thomas_BA:
Also thanks from me.

That did the trick. For some reason i had to shorten the name of the tar file as otherwise flashing won´t work.
[Galaxy Tab S2 Original Android Development] Spielmops:
My wifi-setup? What do you mean?

If your are questing about my networks: I can asure you that they are good since years. I have more than one wireless device.

If you are talking about the S2: I goto setting/networks/wifi, switch wifi on, wait for the network-names, tap on one of my wifi-network-names, type my password and wait. Tha tablet is switching the following message between "connecting" and "saved".

Spielmops
[Galaxy Tab S2 Original Android Development] OhioYJ:
You are responding to the person who will likely be fixing something if its broken, so I would recommend giving lots of details or logs. Even if they don't seems relevant to you. Just my opinion though, my WiFi works fine on the three T813s in my house. Everyone is just trying to help, and this device needs more attention not less, as there aren't really any other tablet options out there with LOS support.
[Galaxy Tab S2 Original Android Development] Spielmops:
So, what is your opinion I should do?

Spielmops

BTW: I have Tabs working with LineageOS:

Samsung Galaxy Tab 3 8.0 (SM-T310) with 14.1 from 2019/04/05

Huawei Mediapad T2 Pro 10 with 15.1 from 2019/07/05

Google - HTC Nexus 9 with 14.1 from 2019/05/07
[Galaxy Tab S2 Original Android Development] OhioYJ:
Yeah, but those are older versions of LOS. Do you have the same SSID names for the 2.4 and 5 GHz bands. Have you tried just one band of the other? Is your SSID hidden? This a WPA2. Going to have to start narrowing down exactly what doesn't work. A log maybe helpful as well too, never know.
[Galaxy Tab S2 Original Android Development] cwm9:
I'm unable to get Minecraft working on my son's tablet. I don't know if it's the LOS 16 or some other conflict. Could someone test Minecraft and see if it's working on their system?
[Galaxy Tab S2 Original Android Development] Spielmops:
Yes. No. No. No. Yes. Read my Post. Log is 2.2MByte small ...

You can forget this. I needed a few hours to read about Stock-firmware and where to get and needed a lot of time to get the tablet to work with the newest stock-rom. I tried wifi and it doesn't work. It must be a hardware-failure ... I'll send it back.

Spielmops
[Galaxy Tab S2 Original Android Development] buffaloquinn:
I cannot get my tablet recognized by the USB driver to be able to use Odin. And I have tried cleaning the port, & other fixes like that. It's there any I other way to install the firmware update without connecting through the micro USB port? Mine barely works as a charging port.
[Galaxy Tab S2 Original Android Development] T_I:
I'm getting errors updating from 7 aug version to 17 aug version.

Warning: no file_contexts
Comparing TZ version TZ.BF.3.0.3-0064 to TZ.BF.3.0.3-0054
Comparing TZ version TZ.BF.3.0.3-0067 to TZ.BF.3.0.3-0054
Comparing TZ version TZ.BF.3.0.3-0071 to TZ.BF.3.0.3-0054
Comparing TZ version TZ.BF.3.0.3-0074 to TZ.BF.3.0.3-0054
Comparing TZ version TZ.BF.3.0.3-0077 to TZ.BF.3.0.3-0054
assert failed: samsung.verify_trustzone("TZ.BF.3.0.3-0064",...,"TZ.BF.3.0.3-0077") == "1"

Edit: Hmmm, never mind, found the solution. I hope this will help with wifi issues as well.

Edit 2: No go with the command and SG1 files I could find in this topic:

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
Heimdall v1.4.1

Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...

Does anybody have a build prior to august for me? (and a method to update the bootloader so I can install all images after 8-8?)

Edit 3: Found it, heimdall on Debian is to old as well. Build from source worked...

It would be wise if the index page would be updated with this info (Heimdall update procedure, flash of images) so it can be found easier when people want to flash newer images.
[Galaxy Tab S2 Original Android Development] gremly:
I am running release from 31.07.2019 and when I try to update, I do have the same TZ error. The downloads at https://download.lineageos.org/gts210vewifi are newer then 13.08.2019 and have the same error.

Currently, I wait for new releases.
[Galaxy Tab S2 Original Android Development] davidnw:
You need to install the latest firmware update to be compatible with the latest ROM release (see previous posts on how to do this). The TZ requirement is not an error. The error is your firmware is too old. Waiting will not solve this.
[Galaxy Tab S2 Original Android Development] Entodoays:
1. I'm encountering an issue with wi-fi direct. I use Total Commander with the Wifi transfer plugin. Also I tried connecting to a wireless display through wi-fi direct. Whenever a device tries connecting to the tablet through Wi-Fi direct Android restarts. Does anyone else have the issue?

2. Another issue is with the home button remaining responsive even when the magnetic cover turns off the screen. With Samsung stock, if the home button is pressed through the cover, nothing happens, but with LOS16 it turns the screen on. This should not happen in my opinion.
[Galaxy Tab S2 Original Android Development] rogers11:
I've transferred some files from the tablet to my Nexus 5x via TotalCommamder's WiFi transfer some minutes ago without any problems.

The tablet runs extremely well with this ROM.
[Galaxy Tab S2 Original Android Development] Entodoays:
Wifi transfer works if you connect to an external wifi network. If you are not connected you're asked to either connect to a network or use wi-fi direct. When you choose this latter option, the wifi network is created, but when you try to connect to it from another device Android soft restarts.
[Galaxy Tab S2 Original Android Development] Deltadroid:
[MENTION=7701270]BRDigung[/MENTION] [MENTION=6940829]Entodoays[/MENTION]

I have been looking into fixing wifi direct and miracast (ie; streaming to firetv), but I don't have any way of testing it. Please try this and let me know if it helps.

1) Edit vendor/etc/wifi/p2p_supplicant_overlay.conf and remove the following line

p2p_no_group_iface=1

2) Reboot

Edit:

Also, if the change above does not work, there are currently more changes under review to fix wifi-direct and miracast for Pie:

https://review.lineageos.org/q/topic:"pie-aosp-wfd"+(status:open%20OR%20status:merged). Perhaps it will work when this gets merged.
[Galaxy Tab S2 Original Android Development] Entodoays:
Can I do that without being rooted?
[Galaxy Tab S2 Original Android Development] Deltadroid:
Yes, in recovery with adb shell
[Galaxy Tab S2 Original Android Development] Entodoays:
Is it possible to do it directly in TWRP without adb? Because I'm away from my PC for the coming weeks.
[Galaxy Tab S2 Original Android Development] Deltadroid:
It is possible to use the console that is built into TWRP, but I would recommend waiting until you have a pc available.
[Galaxy Tab S2 Original Android Development] Entodoays:
OK I'll do that. In the mean time I discovered another bug that maybe it would be good to report on Gerrit.

Keyboard - Notification drawer issue

I use Gboard as my prefered keyboard, but the issue is there even with AOSP Keyboard. When you split the screen between two apps and have the keyboard showing, if you open the quick settings/notifications drawer, touching the screen responds to the keyboard and not the overlaying notifications you try to tap. Can anybody confirm this on their devices?

Testing Wi-Fi direct

Also about testing wi-fi direct, you don't need to have any special device to do so, just one other device that can connect to the wi-fi.

On the tablet install total commander and the wi-fi transfer plugin.

Disconnect from the wifi network.

In Total Commander select a folder and tap the copy/move icon below.

Choose Create Wi-fi direct server.

From any device with wi-fi connectivity try connecting to the newly created wi-fi network.

At the moment step 5 triggers a reboot.
[Galaxy Tab S2 Original Android Development] ZakHH:
Play Store stopped working, nothing helps

I see others reported issues with the Play Store earlier on (app updates not loading), but were able to fix them using simple measures.

Well, I have the same problems now, and I cannot get it fixed at all.

Long story:

I used a July build until recently, couldn't get it updated to a later build due to the Error 7 problem.

The July build worked fine, until a few days ago, when suddenly, Play Store would show app updates, but they wouldn't start downloading, no matter what I tried.

When clearing the app cache for Play Store and Play Services didn't help, I wiped all data for both, and that's when my T813 stopped working entirely. Froze every other second and seemed to do a soft reboot. Couldn't get it fixed.

So I wiped the device (via Twrp, wiping all that can be wiped), flashed the latest firmware using Odin, wiped the device again, and installed the latest LOS build (20 August).

I flashed the latest GApps (Pico version) right after flashing the ROM, as well as the latest Magisk.

Everything worked. Setup was easy, Google Play Store worked, I installed all apps I needed on the tablet, and was happy with my clean install.

Until after 24 hours, Play Store updates stopped working again.

The Play Store shows there is an app update available (for Dropbox, in this case), and when I hit "update", it shows "Update pending", and won't start downloading, no matter how long I wait.

The same goes for trying to install new apps.

Here's what I tried so far, to no avail:

- Force-stopping the Play Store app, wiping cache

- Same as above, but wiping Play Services cache as well

- Same as above, plus removing the Google account and reinstalling it

- Updating the Play Store to the latest version from APKMirror

- Disabling firewall (AFWall+) and ad blocker (AdAway), to make sure they don't block anything vital

- Trying other wifis with signals from different ISPs (mobile, cable, glass fibre)

- Trying a VPN

Nothing helped, and now I'm running out of ideas.

When I go into the detailed app view and hit the "update" button there, the message says "waiting for wifi", so it seems as if somehow Play Store doesn't realize the device is connected. I also tried the other available Play Store settings ("via a network", "ask every time"). That changes the message to "waiting for download", but the download still won't start.

What could possibly cause this?

EDIT: Ha! Result! I found the culprit, literally seconds after I posted this. I'll still keep the post up, in case somebody else encounters the same problem.

The solution:

Went into wifi settings, and there into the settings for the wifi I was connected to (clicking the gear wheel icon next to it), then clicking "Advanced" and then on the "Metered" setting, which is set to "Detect automatically" by default. Changed that to "Unmetered", and voilà! Google Play Store loads updates again.

Seems some processes struggle with detecting the "metered/umetered" status of a wifi. I never encountered that problem on any other device (running LOS on 3 other devices as well), so this may be device related.
[Galaxy Tab S2 Original Android Development] andyvdsteen:
Thanks for sharing the solution!

I have this issue as well now and then on tablet and OnePlus One (both LineageOS).

I changed this setting on both tablet and OnePlus One.

I am not sure yet if this really is the solution, since I never have this issue on my OnePlus 6, which also has automatic metering.
[Galaxy Tab S2 Original Android Development] gremly:
I was busy in the last days and tried today with success. Thanks for the reply.
[Galaxy Tab S2 Original Android Development] moloko01:
Build 20190824 is broken. Boot loop after update. Better wait for next build.
[Galaxy Tab S2 Original Android Development] AL_IRAQI:
[MENTION=5227588]Deltadroid[/MENTION] is there any way to increace charging speed ?, its painfully slow for me with stock charger

it doesnt go any higher than 800mAh
[Galaxy Tab S2 Original Android Development] Deltadroid:
This seems to be a Samsung specific issue with AOSP since Nougat. I have not yet found any other newer Samsung devices that charge at normal speed with custom ROMs.

Edit: [MENTION=4648515]AL_IRAQI[/MENTION] Take a look at this https://review.lineageos.org/c/LineageOS/android_device_samsung_apq8084-common/+/232035
[Galaxy Tab S2 Original Android Development] moloko01:
20190825 has same problems. My last working update is 20190823. Anyone else got this problem?

Same on my second device sm-t713.
[Galaxy Tab S2 Original Android Development] rogers11:
No problem with the build from today. Did not try the one from yesterday.
[Galaxy Tab S2 Original Android Development] Deltadroid:
Did you add something to /system/priv-app/ ? There are new restrictions to applications in priv-app.
[Galaxy Tab S2 Original Android Development] moloko01:
No, I don't think so. Both devices are rooted with magisk. Could this be the problem?

Edit:

Solved that problem by disabling modules (Substratum + Dolby) in magisk before updating. Thanks for the tipp.
[Galaxy Tab S2 Original Android Development] Deltadroid:
Good to hear. The way to properly fix things like this from now on is to add permissions to /system/etc/permissions. File a bug report.
[Galaxy Tab S2 Original Android Development] moloko01:
Don't know how to do that, sry.
[Galaxy Tab S2 Original Android Development] davidnw:
Ask google.

https://wiki.lineageos.org/bugreport-howto.html
[Galaxy Tab S2 Original Android Development] dead90:
Error 7. How to solve?

Inviato dal mio SM-T813 utilizzando Tapatalk
[Galaxy Tab S2 Original Android Development] ripee:
Update your TWRP to the latest official version (3.3.1-0).
[Galaxy Tab S2 Original Android Development] dead90:
Already done, and it doesn t solve the problem. I had to remove the assets in the zip

Inviato dal mio GM1913 utilizzando Tapatalk
[Galaxy Tab S2 Original Android Development] supachris:
Update Samsung Bootloader and modem. Link to the zip is some postings above.
[Galaxy Tab S2 Original Android Development] OhioYJ:
Does 3.3.1.0 work for you? Are you encrypted? 3.3.0.0 wouldn't decrypt data for me. 3.3.1.0 doesn't even ask for a password. No version past 3.2.3.0 has worked on any of my T813s. TWRP Thread post.

Starting on Page 11, there is some discussion on this.
[Galaxy Tab S2 Original Android Development] Entodoays:
I never did anything like that so please bear with me and explain. I entered TWRP, connected to PC with cable, tried

adb shell

and

ls

Got a vendor folder, but there wasn't any etc folder in it when I tried to ls again.

I then rebooted normally and searched the file root for the p2p_supplicant_overlay.conf file and I got two matches. One in system/vendor/etc/wifi/ and another in vendor/etc/wifi/. I'm confused :confused:.
[Galaxy Tab S2 Original Android Development] Deltadroid:
When you open an adb shell in recovery, mount /system partition first.
[Galaxy Tab S2 Original Android Development] Entodoays:
So I did that and tried creating a wi-fi server through Total Commander and the system rebooted as soon as I tried connecting to it as before. This modification doesn't solve the issue I'm afraid.
[Galaxy Tab S2 Original Android Development] Akipe:
Hey, I made an update of TWRP which adds the support of the decryption with version 3.3.1 (+ with more change).

If you're interested I need testers to check that everything works, before integrating the changes into the official repository.

Link to the flash image and sources : https://xdaforums.com/showpost.php?p=80167078&postcount=119
[Galaxy Tab S2 Original Android Development] Deltadroid:
Thanks for checking. It appears that Google has removed native wifi-direct support for this device in Android Pie. Wifi-direct support will need to be added back to lineage-16.0 frameworks to fix the issue. There is a topic still under review on Lineage's Gerrit regarding wifi-direct on Android Pie for older devices.
[Galaxy Tab S2 Original Android Development] dead90:
Best kernel with this release?

Inviato dal mio SM-T813 utilizzando Tapatalk
[Galaxy Tab S2 Original Android Development] OhioYJ:
I'm not aware of any kernels available for our device. WhitePug kernel is the only one that used to be available, but it hasn't been in development in a long time, and is no longer compatible with new builds.

I use NapTime by Francisco Franco to turn off Wifi, BT, GPS, whenever the screen is off on my tablet. This has helped my battery life considerably.
[Galaxy Tab S2 Original Android Development] churchner420:
Can I change the offline charging animation? It's shown horizontaly like on a horizontal tablet and I don't like that. Is there a zip I can flash to get another animation maybe with percentages?
[Galaxy Tab S2 Original Android Development] rogers11:
Good morning, I've tried to encrypt my Tab S2 today but after confirming the process it shows a green android for a short time and then I'm at the lockscreen again. What do I miss?
[Galaxy Tab S2 Original Android Development] supachris:
What is the version of the TWRP you firstly formatted the data partition? The 3.3.0 does not format correctly, you have to use 3.2.3 for this. You can backup data, format data (NOT only wipe) with 3.2.3 and restore. Afterwards you should be able to encrypt. You have to save pictures, music, downloads and so on manually. 3.3.0 does not preserve the small amount of data needed to store the encryption key.
[Galaxy Tab S2 Original Android Development] rogers11:
OK, I've used 3.3.x before but cannot remember if I formated /data before. I will try to format with 3.2.3 later. Thanks for your help.
[Galaxy Tab S2 Original Android Development] rogers11:
Thanks a lot. After formatting with 3.2.3 I was able to encrypt the device.
[Galaxy Tab S2 Original Android Development] almahix:
Netbuzz, Thank you very much for your guidance. I am not all that savvy about this stuff but your directions and your links provided what I needed to get my tablet to load the latest LOS. I really appreciate your contributions. :highfive: