yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Original Android Development] JamesKinds:
Hi,

To use an analogy from the PC world.

Vendor Security Patch Level = Drivers/Firmware.

The Android Security Patch Level = Software/OS.

So put another way, our devices have the latest and most up to date software, but some of the deeper "drivers/firmware/bare metal" components have not been updated for over a year.

The relevance is that this leaves open a number of security and possibly performance issues that can't be addressed by updates to the "software" (LOS).

This may well be out of the devs control and could only be remedied by Samsung. I was just curious if anyone had seen a more up to date Vendor Security Patch Level or had an idea of how one could be hacked together (possibly by lifting the requisite components from a later device (assuming Samsung will not be issuing any further updates for the S2).

If nothing is available, c'est la vie, but I just thought that I would ask those with more knowledge than myself.

Thanks again,

JK
[Galaxy Tab S2 Original Android Development] CarlosCalderon:
Thx for your explanation.

Gesendet von meinem SM-T813 mit Tapatalk
[Galaxy Tab S2 Original Android Development] DeeXii:
How is the battery life on this?
[Galaxy Tab S2 Original Android Development] sebmue:
Good
[Galaxy Tab S2 Original Android Development] Atreya1:
Sorry I didn't leave the message I should have.

I had Vendor Security Patch 1 Jan 2019. After installing los 16 the Vendor Security Patch went backwards for some unknown reason and now have the 1 Jan 2018.

I checked this by reinstalling the Stock Rom, updated checked the patch date (Jan 2019). Reinstalled los 16 and back to Jan 2018.
[Galaxy Tab S2 Original Android Development] davidnw:
I think the the security patch date is set manually by the developers, so it could be a simple mistake rather any indication of the real patch level going backwards.
[Galaxy Tab S2 Original Android Development] JamesKinds:
Can you please tell me which stock ROM you used? All the ones I tried had the 1 Jan 2018 date. Thanks :)
[Galaxy Tab S2 Original Android Development] Atreya1:
I used a Stock Rom that on initial installation gave a Vendor Security Patch (Jan 2018). After installation I updated OTA from Samsung and the Vendor Security Patch updated to Jan 2019.

Initial thoughts yeah I have the latest Vendor Security Patch.

Installed LOS 16 and feeling confident that I'd have the 2019 Vendor Security Patch.

Checked and it had reverted back to the 2018 Vendor Security Patch :crying:
[Galaxy Tab S2 Original Android Development] Deltadroid:
I have updated the kernel in today's build with a new WiFi driver and several hundred cve. It should not be necessary to disable WiFi anymore while sleeping.
[Galaxy Tab S2 Original Android Development] supachris:
Thank you. But with this release the battery drain in sleep mode is more again. With the wake lock kernel fix made by Claymore1297 the "awake with screen off" time was much less. So I have to fo on using Nap Time and let this app disable all while in standby to have deep sleep all the time.
[Galaxy Tab S2 Original Android Development] Deltadroid:
Booting into safe mode might help determine if there is an installed application that is causing wake lock issues.
[Galaxy Tab S2 Original Android Development] buffaloquinn:
Updated to the new ROM from a March version. Battery is not good so far & Verizon Messages is completely broken. First time I've ever had significant issues with this ROM.
[Galaxy Tab S2 Original Android Development] BRDigung:
i try to stream the display to my firetv stick and the tab crashes, with my oneplus 3 (both official 16.0) it works fine.
[Galaxy Tab S2 Original Android Development] Deltadroid:
Without any logs, it is difficult for me to guess what would cause this. I also do not have a firetv stick to test with. Although, it would be interesting to know if the Nougat ROM I have posted for T813 also crashes when streaming to firetv, since it is using basically the same kernel as this ROM.
[Galaxy Tab S2 Original Android Development] BRDigung:
I downloaded Syslog, which log types do you need?
[Galaxy Tab S2 Original Android Development] Deltadroid:
just a logcat of the crash
[Galaxy Tab S2 Original Android Development] BRDigung:
hope this is right
[Galaxy Tab S2 Original Android Development] Deltadroid:
Yes, can you also post a "dmesg"
[Galaxy Tab S2 Original Android Development] BRDigung:
yes
[Galaxy Tab S2 Original Android Development] Deltadroid:
Is this a dmesg from when the crash occurs?
[Galaxy Tab S2 Original Android Development] Deltadroid:
OK, after looking at your logs, this seems to be a problem (but I cant guarantee this fixes the streaming issue because I don't have anything to test with).

08-02 21:34:02.990 E/wpa_supplicant( 1147): nl80211: Failed to open /proc/sys/net/ipv4/conf/p2p0/drop_unicast_in_l2_multicast: No such file or directory
08-02 21:34:02.990 E/wpa_supplicant( 1147): nl80211: Failed to set IPv4 unicast in multicast filter

I have added a fix to the kernel for review here:

https://review.lineageos.org/q/topic:"multicast_filter_msm8976"+(status:open%20OR %20status:merged)

It should be included in the the build soon. You can check merge status from the link above to know when its added.
[Galaxy Tab S2 Original Android Development] davidnw:
Could loop device support be be added ?

I have tried the Linux Deploy app, it works on my phone running DotOs, but the Tab S2 needs loop device support to mount the Linux image. The Loop checker app tells me loop device is not supported.
[Galaxy Tab S2 Original Android Development] Dastonie:
Tried twice the installation from the scratch with those Gapps. Fully wiped with TWRP. Both time the result is even worse. Those Gapps are crashing already and I do not even reach the homescreen.

But this shows to me, that the Gapps are obviously the root cause. :mad:

Update: modified my initial post with more details.
[Galaxy Tab S2 Original Android Development] Deltadroid:
The issue is probably with the new Google SetupWizard for Pie. There is an installation switch for this gapps package to not install Google's setupwizard.

touch /sdcard/.removesetupwizard

Format /system, /data, and /cache partitions, install lineage, then install gapps.
[Galaxy Tab S2 Original Android Development] Shyamani:
Try bitgapps.

https://downloadgapps.com/gapps/download-android-9-0-pie-gapps/
[Galaxy Tab S2 Original Android Development] Deltadroid:
Those gapps say they are for pie but they are actually using files from an oreo stock image.

platformBuildVersionCode="27" platformBuildVersionName="8.1.0"

I've updated the Pie Gapps to not install Google SetupWizard by default here
[Galaxy Tab S2 Original Android Development] Dastonie:
Thanks a lot for all hints/help.

After a full wipe and just installing the image I receive:

"Bluetooth keeps stopping"

Afterwards I installed the Gapps from deltadroid (build 0409) and I receive additional

"Google Play Services keeps stopping"

"android.process.media keeps stopping"

Looks like I'll better wait for another release and go back to LOS15.1 :D
[Galaxy Tab S2 Original Android Development] Dastonie:
Hi guys, todays build is great. So far everything works fine.

1. Wiped tablet fully

2. Reboot to recovery

3. lineage-16.0-20180910_003806-UNOFFICIAL-gts210vewifi.zip installed

4. Reboot to System -> Everything fine (no more bluetooth or othter system errors)

5. Reboot to Recovery

6. open_gapps-arm64-9.0-mini-20180910.zip installed (from open Gapps site)

7. Reboot -> All good
[Galaxy Tab S2 Original Android Development] eeter:
yes it works!!!!! Many thanks :)
[Galaxy Tab S2 Original Android Development] jahciple:
Recents looks blank.
[Galaxy Tab S2 Original Android Development] LuK1337:
known issue, Google broke it for hwrotation devices lol
[Galaxy Tab S2 Original Android Development] Lupin The Third:
This has matured quite a lot since the last time I tried.

Using it for a couple of hours and, besides the blank recents and exfat sd card format not supported, looking good! :)
[Galaxy Tab S2 Original Android Development] jahciple:
It's actually quite stable and battery drain seems to be normal like stock.
[Galaxy Tab S2 Original Android Development] Lupin The Third:
Battery life is not bad. I lost ~4% overnight. First night though. Keeping this for some time and test further. :)

P.S. do you have the Bluetooth-enabled icon on status bar?
[Galaxy Tab S2 Original Android Development] ikonline:
Installing pie for the first time on my T813 now, thanks for the rom !!! I rely appreciate your work!
[Galaxy Tab S2 Original Android Development] harise100:
When I try to install latest build 0915 I get an error that my Samsung Trust Zone Version is wrong.

Do I have to flash full Stock image?
[Galaxy Tab S2 Original Android Development] LuK1337:
What's your trustzone and bootloader version?
[Galaxy Tab S2 Original Android Development] harise100:
Bootloader: T813XXU2BQG4

Trust Zone: TZ-BF.3.0.3.00054
[Galaxy Tab S2 Original Android Development] LuK1337:
Thanks, added to the list.
[Galaxy Tab S2 Original Android Development] Dastonie:
Hi Luk,

great work, just updated from 10.09. Build to the actual 16.09.

So far everything looks fine. No issues at all (except the know issue)

Thanks a lot for your efforts!

Cheers
[Galaxy Tab S2 Original Android Development] Lupin The Third:
exFat support with today's build! Great! :)
[Galaxy Tab S2 Original Android Development] BRDigung:
i creat it with syslog after the crash. if that isn't right i need instructions what to do.
[Galaxy Tab S2 Original Android Development] Deltadroid:
It is fine. Try the next build and let me know how it goes.
[Galaxy Tab S2 Original Android Development] BRDigung:
it crashed again. here are the new logs.
[Galaxy Tab S2 Original Android Development] Deltadroid:
It looks like your build is not including the fix I added. You can verify the fix is included by looking at /proc. These should now exist below:

/proc/sys/net/ipv4/conf/wlan0/drop_unicast_in_l2_multicast

/proc/sys/net/ipv4/conf/wlan0/drop_gratuitous_arp

/proc/sys/net/ipv6/conf/wlan0/drop_unicast_in_l2_multicast

/proc/sys/net/ipv6/conf/wlan0/drop_unsolicited_na
[Galaxy Tab S2 Original Android Development] BRDigung:
I found these files. I used 'Total Commander' from PlayStore to check it. I'm running the latest build from today.
[Galaxy Tab S2 Original Android Development] Deltadroid:
Your logs still say:

08-03 18:26:31.128 E/wpa_supplicant( 1149): nl80211: Failed to open /proc/sys/net/ipv4/conf/wlan0/drop_unicast_in_l2_multicast: No such file or directory
08-03 18:26:31.128 E/wpa_supplicant( 1149): nl80211: Failed to set IPv4 unicast in multicast filter

I see that you have Magisk installed and it is very possible that Magisk is causing a permission problem. You should try without Magisk.

---------- Post added at 08:05 PM ---------- Previous post was at 07:31 PM ----------

Block Loobpack device support is already added to this ROM (CONFIG_BLK_DEV_LOOP). Have you tried DriveDroid? DriveDroid support has already been added as well.
[Galaxy Tab S2 Original Android Development] BRDigung:
It happens the same without Magisk.

Edit:

Logs after crash without Magisk.
[Galaxy Tab S2 Original Android Development] Deltadroid:
For some reason, wpa supplicant does not see the nodes that I just added.

08-03 20:29:49.626 E/wpa_supplicant( 1152): nl80211: Failed to open /proc/sys/net/ipv4/conf/wlan0/drop_unicast_in_l2_multicast: No such file or directory

08-03 18:26:31.309 E/wpa_supplicant( 1149): nl80211: Failed to open /proc/sys/net/ipv4/conf/p2p0/drop_unicast_in_l2_multicast: No such file or directory

Try writing to the nodes manually as root just to see if they are accessible. Then take another logcat and dmesg to see if there are denials.

echo -n 1 > /proc/sys/net/ipv4/conf/wlan0/drop_unicast_in_l2_multicast

echo -n 1 > /proc/sys/net/ipv4/conf/p2p0/drop_unicast_in_l2_multicast

Edit:

BTW, was streaming to firetv working on this device before I updated the kernel?
[Galaxy Tab S2 Original Android Development] BRDigung:
How can I do that? I need more instructions for that, sorry.

I don't know, try it the first time a few days ago.
[Galaxy Tab S2 Original Android Development] Deltadroid:
It's ok. You have provided me with enough logs already to investigate further.
[Galaxy Tab S2 Original Android Development] no_means_no:
I am using this ROM for quite a while now and am happy with it, updating regularly. But since a couple of days I can't flash a newer update. Dunno if it's related to the files itself, TWRP or the actual ROM Version I have.

I'm using the one from August 7th. Tried the way via the updater, boots into TWRP, after some very short screen it goes into TWRP start screen.

When trying downloading a file and installing manually6I get errors (screenshot).

Any ideas?

Gesendet von meinem SM-T813 mit Tapatalk
[Galaxy Tab S2 Original Android Development] Deltadroid:
This error means the firmware, ie; bootloader and trustzone, need to be updated. These can be updated in different ways, like, for example, installing latest stock ROM or extracting files from stock ROM and only updating the necessary partitions.

Hint: Heimdall can be used to only update the partitions that TWRP and Lineage don't touch.

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] andyvdsteen:
Same for me. Same message in TWRP.

I haven't tried the latest yet. It has a "Fix build error" in the changelog. Not sure if it is related.
[Galaxy Tab S2 Original Android Development] gevilot:
I followed the instruction on LineageOS website and got the latest LineageOS (lineage-16.0-20190811-nightly-gts210vewifi-signed.zip) installed on my T813, while almost everything is working fine, I get very low sound volume even at max. volume, is there additional settings/fix that I need to apply?

Here is how I installed the LineageOS: I used a Ubuntu 18.04LTS box with a manually compiled Heimdall 1.4.2 and TWRP 3.3.1-0. Except for the 1st time when I sideloaded LineageOS ROM, I got "zip signature verification failed" error and had to change the TWRP setting to disable "zip signature verification" before sideloading LineageOS, zip signature verification for OpenGApps was OK though.
[Galaxy Tab S2 Original Android Development] davidnw:
Can your suggest a source or the lastest stock room ?
[Galaxy Tab S2 Original Android Development] Deltadroid:
sammobile.com or updato.com
[Galaxy Tab S2 Original Android Development] AL_IRAQI:
Download latest T813XXS2BSG1 Firmware, from this link

these files are included

aboot.mbn
adspso.bin
cmnlib.mbn
hyp.mbn
keymaster.mbn
modem.bin
NON-HLOS.bin
persist.img.ext4
rpm.mbn
sbl1.mbn
sec.dat
tz.mbn
[Galaxy Tab S2 Original Android Development] ripee:
The latest is SG3 ;) but same idea. See my signature, .BL_CP folder in google drive.
[Galaxy Tab S2 Original Android Development] AL_IRAQI:
SG3 is the same as SG1, but released in south america, you can also see the changelist is the same

CSC for both releases is SG1 also xD
[Galaxy Tab S2 Original Android Development] moloko01:
Same here. Actually I am on lineage-16.0-20190804-nightly-gts210vewifi-signed.zip and can't (manualy) update anymore to 0811 or 0812... In TWRP 3.3.1.0 is shown Error #7 when I try to update.
[Galaxy Tab S2 Original Android Development] ripee:
Still, you can cross flash any bootloader and modem regardless of the CSC.
[Galaxy Tab S2 Original Android Development] TKruzze:
Just to make certain:

I can update my USA Model using your T813XXS2BSG3.tar from HERE and the update instructions from HERE?

Also, will a device wipe be required or can I then just install the latest Lineage update and be on my way? (I'm currently running 0705 version of this ROM)
[Galaxy Tab S2 Original Android Development] Deltadroid:
A device wipe is not required. After updating firmware from stock ROM, just install the new LineageOS update as usual.

I would choose a ROM update from a trusted source. ie; https://www.sammobile.com/samsung/galaxy-tab-s2/firmware/SM-T813/

I don't see US in the list, but Canada should be ok for US devices. US devices should probably use T813XXS2BSG1. The T813XXS2BSG3 update seems to be for South America. I downloaded a few different regional versions of T813XXS2BSG1 and they were all the same. One thing I should mention though is that the German T813XXS2BSG1 version is missing a file (sec.dat). I think Samsung messed up on that one. I used the Canadian T813XXS2BSG1 one and it was the same as the German one except it included the missing sec.dat file.

The instructions you have linked to are correct for Heimdall.
[Galaxy Tab S2 Original Android Development] TKruzze:
This is exactly what I decided to do. I'm about a half hour into the artificially slow download. Thanks!
[Galaxy Tab S2 Original Android Development] gevilot:
As no reply and nobody pointed out a direction, I assume that this volume issue may not be a popular issue? or I missed any step when I installed the LineageOS?
[Galaxy Tab S2 Original Android Development] davidnw:
Can you confirm that the latest LinageOS builds will load when this Firmware is installed, or are dealing with theories about the TWRP error messages ?

---------- Post added at 12:30 AM ---------- Previous post was at 12:17 AM ----------

Why would the developers suddenly change the required bootloader and trustzone without informing users ?

Thanks for the complete solution , I have downloaded the updated firmware and installed it with your command string, and have updated LinageOS without errors.
[Galaxy Tab S2 Original Android Development] Deltadroid:
Updating firmware from stock rom is common practice because it often includes security fixes. Changes can be tracked on LineageOS' Gerrit if you want to know whats going in the next build.
[Galaxy Tab S2 Original Android Development] AL_IRAQI:
im already using it on my tab, flash it everything should be working fine
[Galaxy Tab S2 Original Android Development] no_means_no:
Thank you for your answer, but I am not skilled enough to do that besides I am using windows. I would like to have a solution without fully wiping or via another ROM. But any help is very much appreciated

Gesendet von meinem SM-T813 mit Tapatalk
[Galaxy Tab S2 Original Android Development] OhioYJ:
Just to double check, this is all that needs to be flashed? Then the firmware will be up to date, and I should be good to go? (in theory)
[Galaxy Tab S2 Original Android Development] Deltadroid:
Correct
[Galaxy Tab S2 Original Android Development] Hurr1c4n3:
I got the same issue with my T813. Volume is much lower then my phone when I set it to Max when watching videos.
[Galaxy Tab S2 Original Android Development] Atreya1:
Try using ' volume booster GOODEV " App this may well cure you low volume problems
[Galaxy Tab S2 Original Android Development] TKruzze:
Problems getting heimdall to work properly

I am unable to successfully use heiimdall on either my Windows 7 64-bit Desktop or Laptop that have both had a fresh install of Windows in the past week. I have not installed any other Samsung drivers, so I don't think this is a Samsung driver conflict issue. This is also the first I've ever tried to use heimdall to update my device. I think I used ODIN to install TWRP back when I purchased the device initially.

I've downloaded Heimdall Suite using the link and instructions found on the Lineage Wiki. I'm using Heimdall v1.40 found HERE. The tablet immediately shows in zadig as a MSM8952 with no driver installed. I then successfully install the WinUSB driver and then executre the 'heimdall print-pit' command to test the connection and get the following output:

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

I then tried installing the other two drivers (libusbK and libusb0) with the exact same results. As I mentioned, this has happened on 2 different computers using different USB ports (all direct, no hubs) and different USB cables all with the same failure message. Any suggestions on where to go from here?
[Galaxy Tab S2 Original Android Development] Deltadroid:
Heimdall for Windows is too old. Use Linux and build heimdall from latest sources from here: https://gitlab.com/BenjaminDobell/Heimdall
[Galaxy Tab S2 Original Android Development] moloko01:
So I am just a normal user, not a developer or someone with heavy skills, like the most of the LOS Users. I don't think that it is the way for official builds. Nothing about this in official install instructions. So, how to fix this without spending hours? Why don't you release a fix to handel for normal users?

But, thank you for developing this room.
[Galaxy Tab S2 Original Android Development] ripee:
My bootloaders and modems are taken straight from that trusted source, no need to spend the time downloading the entire thing.
[Galaxy Tab S2 Original Android Development] davidnw:
I updated the firmware as described, and I could then install the latest LinageOS update.
[Galaxy Tab S2 Original Android Development] Deltadroid:
Every official device requires the user to update firmware from time to time from the latest stock ROM. The firmware on these devices should have really been updated a long time ago. Heimdall is the fastest and easiest solution, but you can always make backups and restore them after going back to stock with Odin.
[Galaxy Tab S2 Original Android Development] OhioYJ:
Heimdall is a mess... To say the least. I just got done putting together a guide actually for this:

[Guide]Update Firmware using Heimdall - T813

It's still using Linux, but it just a live USB, explains how to make it. No compiling from source or anything like that. I've updated three tablets now, so it seems solid.

**edit**

Guys I'd just be glad our device is getting more attention. This is a minor bump in the road. It stinks that the firmware is not as easily updated as say a Google device, but it's Samsung. Complaining is going to do nothing but turn off development team.

**edit**
[Galaxy Tab S2 Original Android Development] netbuzz:
For those on Windows devices, here's an easier option to flash the firmware using Odin.

Download Odin 3.12.3 from https://samsungodin.com/download/Odin3 v3.12.3.zip (I have not tried newer versions, but this one works for sure).

Download the tar file posted by [MENTION=4648515]AL_IRAQI[/MENTION] here: https://xdaforums.com/showpost.php?p=80064058&postcount=397

With the device turned off, press ‘Power+Volume Down+Home’ to enter Download Mode.

Connect your phone to your PC with the USB cable.

Right click on Odin 3.12.3 and click on ‘run as administrator’.

There is a section called ID:COM (on the left upper side of the window). The blank space underneath it will turn blue if your device is recognized. (If the phone is not recognized make sure you have installed the USB Drivers).

Click on ‘AP’ and add the .tar file from the firmware archive.

Click Start and Odin will flash the firmware files and reboot the tablet once done.

Now you can install new Lineage ROM updates without error 7.
[Galaxy Tab S2 Original Android Development] TKruzze:
This can't be stressed enough! We made the choice to purchase a Samsung device. We should have known that meant issues like this.

I'm just thankful that delivering a safe and secure OS is a priority for the Lineage team. And thank you for trying to simplify the process!