yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Original Android Development] fastsquatch:
Of course.

There are vulnerabilities in CPUs even (the Spectre family side-channel attacks require loading processor microcode at boot for instance)

There are vulnerabilities in bluetooth functionality implemented as firmware, like I mentioned above. Same for wifi chips, nfc etc.

Then there are the google security updates which patch kernel/library native code as well Java-level libraries etc

Of the three, lineageos is only able to handle the last. The vendor is responsible for the first two and in my experience they all do a terrible job. I have sympathy for the difficulty of the job though. At least with lineageos we can keep using our old hardware and have most of the stuff fixed, just not the firmware usually, after 1-2 years.
[Galaxy Tab S2 Original Android Development] lmacmil:
So do we know that the two Samsung updates in 2019 addressed any of these potential hardware/firmware issues? Or did they just incorporate the latest Google security updates?
[Galaxy Tab S2 Original Android Development] Deltadroid:
Samsung should have released fixes for QualPwn in their latest firmware update which patches the modem.
[Galaxy Tab S2 Original Android Development] lmacmil:
First I've heard of this but after reading about it I'm not worried about it.
[Galaxy Tab S2 Original Android Development] spiff72:
Any ideas what is wrong if the Google Photos app crashes upon launch? I have cleared cache and storage for the app without success.
[Galaxy Tab S2 Original Android Development] deejayjaytay:
Hey, I remember your avatar! Did you ever get the Duo/echo problem resolved?

Thank you!
[Galaxy Tab S2 Original Android Development] KeepingItCuttingEdge:
No, someone complained yesterday when I was using video chat on the tablet.

I STILL don't see why this seemingly simple issue that plagues so many people can't be fix!

Who knows!

---------- Post added at 05:42 AM ---------- Previous post was at 05:33 AM ----------

Could you explain how this is relevant since these are wifi-only tablets and don't have modems in them? I don't understand...

Thanks
[Galaxy Tab S2 Original Android Development] god_md5:
try this one T713XXS2BSG1_T713OXA2BSA1_HOME.tar update in Odin3_v3.13.1, and next time odin flash only BL use twrp, and boot to twrp ,it can flash the new lineage os..

https://drive.google.com/file/d/1xf2syEpiuDNygMeXHxge_4DK6Zp3qPUG/view?usp=sharing
[Galaxy Tab S2 Original Android Development] Deltadroid:
There are updates to modem.bin in latest firmware
[Galaxy Tab S2 Original Android Development] KeepingItCuttingEdge:
Right but that could just be a filler/blank file because the flashing scripts usually look for it...

I'm still asking, but how would a WiFi-only tablet have a modem?
[Galaxy Tab S2 Original Android Development] Deltadroid:
What ever Samsung uses the modem partition for, It is used for something related to radio signals. Since Samsung's stock firmware release last month, nothing has changed in the modem partition, but Samsung just updated Trustzone to a new version this month.

Edit:

This is what has changed in the firmware since TZ.BF.3.0.3-00054 to TZ.BF.3.0.3-00077

diff -ru T713XXU2BQI1_T713PHN2BQI1_FIRMWARE/ T713XXS2BSG1_T713PHN2BSB1_FIRMWARE/
Binary files T713XXU2BQI1_T713PHN2BQI1_FIRMWARE/aboot.mbn and T713XXS2BSG1_T713PHN2BSB1_FIRMWARE/aboot.mbn differ
Binary files T713XXU2BQI1_T713PHN2BQI1_FIRMWARE/cmnlib.mbn and T713XXS2BSG1_T713PHN2BSB1_FIRMWARE/cmnlib.mbn differ
Binary files T713XXU2BQI1_T713PHN2BQI1_FIRMWARE/hyp.mbn and T713XXS2BSG1_T713PHN2BSB1_FIRMWARE/hyp.mbn differ
Binary files T713XXU2BQI1_T713PHN2BQI1_FIRMWARE/keymaster.mbn and T713XXS2BSG1_T713PHN2BSB1_FIRMWARE/keymaster.mbn differ
Binary files T713XXU2BQI1_T713PHN2BQI1_FIRMWARE/modem.bin and T713XXS2BSG1_T713PHN2BSB1_FIRMWARE/modem.bin differ
Binary files T713XXU2BQI1_T713PHN2BQI1_FIRMWARE/NON-HLOS.bin and T713XXS2BSG1_T713PHN2BSB1_FIRMWARE/NON-HLOS.bin differ
Binary files T713XXU2BQI1_T713PHN2BQI1_FIRMWARE/rpm.mbn and T713XXS2BSG1_T713PHN2BSB1_FIRMWARE/rpm.mbn differ
Binary files T713XXU2BQI1_T713PHN2BQI1_FIRMWARE/sbl1.mbn and T713XXS2BSG1_T713PHN2BSB1_FIRMWARE/sbl1.mbn differ
Binary files T713XXU2BQI1_T713PHN2BQI1_FIRMWARE/tz.mbn and T713XXS2BSG1_T713PHN2BSB1_FIRMWARE/tz.mbn differ
[Galaxy Tab S2 Original Android Development] xmas112:
1. In case of micro sd card(exfat format) inserted erorr mesagges happen.(ex. Blootuth error, google service error....)

2. Expanded desktop mode not working.
[Galaxy Tab S2 Original Android Development] ins0mniac:
I like that. I don't want them to work :D
[Galaxy Tab S2 Original Android Development] tjupille:
Go into Settings and search for "buttons". You can turn the backlight on/off and adjust the on-time
[Galaxy Tab S2 Original Android Development] xmas112:
Everything is good!

but Only 2 ploblems.

1. expand desktop mode error.

2. micro sd card exfat format not support.

Only support fat32.

PlZ fix it. Thanks.
[Galaxy Tab S2 Original Android Development] DungeonseekerUK:
I've been running this for a few days now and it's nice and stable, works good and I'm more than happy with it.

Thought I'd share the few minor issues I've had:

SeLinux isn't working at all (listed as a known bug).

The ROM has problems with certain SD Cards though as long as it's a FAT32 formatted card it's good.

The GAPPS Package listed in this thread crashes on first boot and the first boot setup wizard never launches, easily fixed by manually setting everything up (not a ROM problem but worth mentioning).

I'm having major problems with location services and GPS. Anything that requires access to location services doesn't work correctly, they cannot find my location at all using GPS, WiFi or Bluetooth. I've just installed Google Maps as a test and it refuses to locate me despite the GPS symbol showing in the notification tray and as a consequence it can't find routes either. I've tried every setting i can find in relation to location but so far cannot find the issue.

Edit

Nevermind, the solution to this issue is already in this thread. Settings > Security & Privacy > Location > Advanced > Scanning > Enable WiFi scanning.

Overall this ROM is exceptional considering how young Pie still is and as long as you don't need location services for anything there's no reason to not upgrade.
[Galaxy Tab S2 Original Android Development] tjupille:
After a couple of weeks of regular use, the major problem is that wifi is not turning off during sleep, so giving horrible battery life on standby.

Minor problem is that the recent apps display has reverted to the old style (vertical scroll) in the last two releases. [EDIT: ok, I figured that one out. I use Nova Launcher, and I froze the default Quickstep launcher with Titanium. Turns out that the new recents behavior is handled by the launcher. Restoring Quickstep restored the horizontal scroll, even though Nova is still the deafault.]

Other than that, it's a great daily driver.
[Galaxy Tab S2 Original Android Development] dantibes:
hello

I wanted to inform you that I have tried the below-indicated new linegeOs ROM 16.0 on the tag s2 sm-t819 version: lineage-16.0-20180911_193527-UNOFFICIAL-gts210velte .zip.

Everything seems to work well, I will report any bugs
[Galaxy Tab S2 Original Android Development] xmas112:
lastest version flash error.

Trust zone and bootloader error.
[Galaxy Tab S2 Original Android Development] LuK1337:
Thanks for such a detailed report, you're awesome.
[Galaxy Tab S2 Original Android Development] xmas112:
I just modified 9/15 'updater-script' file.

And i succeed flashinng lastest version.

but sadly still not support 'exfat' micro sd card..

Always thanks your effort..
[Galaxy Tab S2 Original Android Development] LuK1337:
Thanks, that's useless information to me.
[Galaxy Tab S2 Original Android Development] Andvark:
I dirty-flashed the 915 version over the 911 version with no problems. The only issues I've seen (in both versions), besides the ones already known, are:

The status bar clock settings have no effect (Settings > System > Advanced > Status bar > Clock). Hiding the clock (under System Icons) works only temporarily, until the device is locked/unlocked.

The Notification sound setting for Charging sounds (Settings > Sound > Advanced > Charging sounds) has no effect. It can be enabled and disabled, but the Notification sound setting has no effect.

These are very minor issues, and I am truly amazed at how well this ROM performs, especially considering how new it is. It is now my daily driver. I've used many "mature" ROMs that were never as stable and complete as this one. :)

One issue that prevents me from using Wi-Fi scanning apps isn't related to this ROM at all, but to Pie itself. Google has decided to throttle Wi-Fi scanning, as discussed here. I don't know if this "feature" can be disabled in a custom ROM or not. Seems like a pretty short-sighted decision on Google's part to not at least include a permission to allow the old scanning behavior.
[Galaxy Tab S2 Original Android Development] LuK1337:
>Hiding the clock (under System Icons) works only temporarily, until the device is locked/unlocked.

Funfact, that is AOSP bug (which i reported here ~ https://issuetracker.google.com/issues/115769355)

>The Notification sound setting for Charging sounds (Settings > Sound > Advanced > Charging sounds) has no effect. It can be enabled and disabled, but the Notification sound setting has no effect.

Will be fixed soon (TM)
[Galaxy Tab S2 Original Android Development] Andvark:
Thank you for the reply. I'm not sure that I was very clear with the first issue; there were actually two related issues with the clock. The status bar clock settings have no effect (Settings > System > Advanced > Status bar > Clock) was referring to the inability to re-position the clock (it is stuck on the left) or change the AM/PM style (Show seconds does work). If you are already aware of this, my apologies.
[Galaxy Tab S2 Original Android Development] LuK1337:
Yes, none of that was ported yet lol.
[Galaxy Tab S2 Original Android Development] DungeonseekerUK:
I'm not sure if this is a ROM issue or not but I'm having issues with Firefox totally ignoring notification settings and even Do Not Disturb.

I have a known problem where the notification sound was causing videos and music to pause however on the Stock Samsung Firmware I fixed by by disabling the Allow This App To Interrupt Other Apps setting for Firefox.

On this ROM the same issue occurs however the above setting doesn't resolve it so after more googling the workaround is to mute notifications entirely. Tried it, nothing. Next I went into Apps > Firefox and disabled notifications on FF entirely, FF notifications still fire but then last night I put my tablet down to go to sleep, it was 23:45 and DnD was active and should have muted everything (except media) and yet FF was still firing notifications.

What's weird is only Firefox is affected, other apps respect the muting and DnD perfectly but again, this issue was not present on the stock firmware.

Any ideas?
[Galaxy Tab S2 Original Android Development] deejayjaytay:
Spicy!
[Galaxy Tab S2 Original Android Development] heartog:
I don't know if this is normal or is it just me, but the Bluetooth battery indicator doesn't show like when I was on lineage os 15.1. Thanks!
[Galaxy Tab S2 Original Android Development] enestu:
Except for little things and some very rare app crash (Google Art when I use the camera), I found this rom/compilation/port very stable. Good battery life on new S2.

Great work LuK1337 !
[Galaxy Tab S2 Original Android Development] heartog:
While using LineageOS 16, I've noticed that if I switch to manual brightness, it would stay at the level of my automatic brightness instead of my previous set manual level. It wasn't like that with LineageOS 15.1, so I want to know if this is a "feature" of Pie or is this a rom issue? Thanks.
[Galaxy Tab S2 Original Android Development] hjkyui8878:
Heimdall on windows 10 64bit is OK

Heimdall 1.4.2 on windows 10 64bit is OK. You don't need to use it by Linux. I've package all of files, which can be possibly used. The key is zadig.exe,which you need to use to replace the sumsang device's drive with the new libusb's drive. After that, flash the files ( --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 ) by heimdall. The way is best. So we can avoid flashing stock rom and wiping all data. I couldn't sent a link because of new users. If someone want to get files, you can sent me a message.
[Galaxy Tab S2 Original Android Development] itsita:
Hey!

Any chance of porting the newer kernel to the T719 users among us ? :)))
[Galaxy Tab S2 Original Android Development] GmanGrout:
Can anyone possibly help me . Was using lineage 16.0 then tried to restore original firmware as my tablet was playing up. Now getting an error in Odin SW rev check failed.. any ideas ? Driving me mad. Thanks in advance.
[Galaxy Tab S2 Original Android Development] nigeldr:
Like other's I'm not able to update to the recent builds because of the "Assert failed: samsung.verify_trustzone" error, I completely understand that I need to perform the update of the bootloader files but I'm unable to find any exact steps to perform this update. Many individuals have posted suggestions which I've read through but after an hour or so of hunting and downloading I just don't know what steps to take.

This post clarifies some of what's needed https://xdaforums.com/showpost.php?p=80114459&postcount=362

First issue is that I'm unable to find any recent firmware downloads for the Australian region, the latest appears to be Aug 2017, can we use the any region? Working on this assumption I've downloaded the latest UK version, extracted individual files and then put in a separate folder the files that I'm told we need (sbl1.mbn, aboot.mbn, rpm.mbn, tz.mbn, hyp.mbn, sec.dat, keymaster.mbn, cmnlib.mbn, adspso.bin, modem.bin, NON-HLOS.bin)

Some posts say to use Heimdall but then go on to say this no longer works with Windows and suggests to use Odin, the post above goes on to say " It is also possible to create a custom Odin package containing only the bootloader files mentioned above and update that way." how is this done ?

Also not sure how to match the PDA when we have to download from a different region "As long as the PDA is the same, then the bootloader files should be the same too. The files from the CSC are not used for LineageOS"

Is the group mind able to come up with a definitive guide for performing this update ?
[Galaxy Tab S2 Original Android Development] Ecthelion3:
Ok, I also faced the challenge to update my bootloader in order to be able to update LineageOS to the latest versions and I am a Windows user and I did not want to do a clean install of first the Samsung ROM and then LineageOS, thereby losing my data. So I read a lot of posts here in the forum and used the following solution to update my Tab S2:

- Download Odin from https://samsungodin.com/download/Odin3 v3.12.3.zip

- Download the latest Samsung firmware from https://www.sammobile.com/samsung/galaxy-tab-s2/firmware/SM-T713/

- Extract the .md5 file contained in the downloaded zip. You can use 7Zip for this. It can handle tar files as well, which is needed for the later steps.

- Rename the file, so that it gets the extension .tar instead of .md5

- Extract the files sbl1.mbn, aboot.mbn, rpm.mbn, tz.mbn, hyp.mbn, sec.dat, keymaster.mbn, cmnlib.mbn, adspso.bin, modem.bin and NON-HLOS.bin from the tar file and place them in any folder on your disk

- Use 7Zip (or another program that can create tar files) to create a T713.tar file containing the files extracted in the last step

- Turn off your Tab S2. Enter download mode by pressing Power+Volume Down+Home at the same time. Confirm that you want to update your system by pressing Volume Up.

- Connect the Tab S2 to your PC with the USB cable. I'd suggest to not connect any other Android device at the same time now.

- Run Odin as Administrator

- Make sure the ID:COM field changes to blue, which indicates your device got detected

- Click on the AP button and select the T713.tar file we created above

- Click Start to flash the file. The Tab S2 should reboot at the end of the process.

Afterwards you should be able to install the newer LineageOS versions (but no longer the older ones).

Of course I take no responsibility if you brick your phone or nuke the world using the steps above ;).
[Galaxy Tab S2 Original Android Development] lmacmil:
What bootloader were you on? I originally updated to LOS15 from the BRB2 firmware from February 2018. Had no issues with that update nor later updates to LOS16. I'm currently on the August 10 build.
[Galaxy Tab S2 Original Android Development] Ecthelion3:
I don't know exactly which bootloader version I was on. I think it must also have been start of 2018 or so when I bought my Tab S2. But whatever bootloader version I had, I faced the same issue that some others here in the forum had, and could not update to LOS 16 versions built after August 7th. But after applying my solution posted above I am now on one of the latest LOS 16 builds.
[Galaxy Tab S2 Original Android Development] nigeldr:
Brilliant, thanks very much, this was exactly what I needed to complete the update. Your post should be the post that gets linked for anyone else with the same issue.
[Galaxy Tab S2 Original Android Development] knoxjon:
If it helps anybody, I just followed Ecthelion3's steps in post 385 (thanks Ecthelion3!). I am in the US, and I used the latest XAR on sammobile - Cellular South T713XXS2BSG1 from July 1. I was on BQI1 and the August 8 build. Now I am on Sept 8.

FWIW it booted just fine with the new bootloader and the old nightly. Upgrading to the latest nightly took an unusually long time, and I had to reboot to get it to cooperate, but it's working fine now.
[Galaxy Tab S2 Original Android Development] cdub50:
trying to install nightly via sideload on TWRP 3.3.1-0 it loads the splash screen of OS, but eventually reboots back into recovery any ideas? I installed nightly rom, gapps, and su via sideload and rebooted but no luck. Thanks

EDIT looks like issue is flashing SU just did rom and gapps and was able to get past splash screen
[Galaxy Tab S2 Original Android Development] mielcu3:
How to do it ? I have issue with installation lineage os no SM Galaxy Tab S2 t719 LTE. I recevied ERROR7, with is the bootloader issue.
[Galaxy Tab S2 Original Android Development] cdub50:
Use latest Odin and latest twrp 3.3.1.0 should get you past the error.
[Galaxy Tab S2 Original Android Development] KeepingItCuttingEdge:
Could you just post a link to the .tar file you made since you've already gone through all the effort to make it? :good:

THANKS
[Galaxy Tab S2 Original Android Development] Ecthelion3:
I'm sorry, but after successfully flashing my device I deleted the files I downloaded for this, including the tar file I created.
[Galaxy Tab S2 Original Android Development] lloydsw:
Just followed post #385, worked well for me.
[Galaxy Tab S2 Original Android Development] roton:
This is a bit late for you but might help someone else.

You need to go into "META-INF\com\google\android" inside the zip file.

In there just delete the lines which start with "assert", so basically you delete everything up until the first "ui_print".

credit to https://www.youtube.com/watch?v=VCqROwIGLLE
[Galaxy Tab S2 Original Android Development] dr71399:
Hello hope you can help me I tried to flash LineageOS 16.0, ROM then I got stuck on boot loop kept loading twrp recovery... I updated my twrp threw Oden with the newest version..now I'm up and running..but haven't tried to reflash...so my question is what do I need to do before reflashing LineageOS 16.0, ROM?

Thanks so much for your help I really appreciate it
[Galaxy Tab S2 Original Android Development] Willi1999:
I tried to flash SM-T713 LineageOS 16.0, ROM then I got stuck on boot loop kept loading twrp recovery (twrp-3.3.1-0-gts28vewifi.img). I updated my twrp with Heimdall v1.4.1 according to the instructions of the website.

How can I fix this?

Thank You
[Galaxy Tab S2 Original Android Development] Willi1999:
I read on and tried the following:

- I updated Heimdall to 1.4.2 (Linux Mint).

- Installed TWRP 3.3.1-0 with Heimdall.

- With Heimdall (ADB-Sideload) lineage-16.0-20191007-nightly-gts28vewifi-signed.zip installed.

- With Heimdall (ADB-Sideload) open_gapps-arm64-9.0-pico-20191009.zip installed.

- I downloaded the latest Stockrom (25.8.2019) from sammobile (SM-T713, AUT, Switzerland).

- I extracted the files according to [MENTION=5227588]Deltadroid[/MENTION] #335 and transferred them with Heimdall.

The tablet boots up to the Lineageos logo, then restarts into recovery mode (TWRP).

Further I tried with Odin to install the Stockrom again. Installation works, but the Stockrom only starts up to the Samaung logo and gets stuck.

Who can help me? I don't know any more.

Thank you and greetings.

Sorry for my bad english.
[Galaxy Tab S2 Original Android Development] Deltadroid:
The issue is probably with opengapps. Try MindTheGapps instead.
[Galaxy Tab S2 Original Android Development] Willi1999:
Thanks for the help.

I have reinstalled as suggested:

- lineage-16.0-20191011-nightly-gts28vewifi-signed.zip

- MindTheGapps-9.0.0-arm64-20190615_031441.zip

Now it works well. :)

Thanks and greetings
[Galaxy Tab S2 Original Android Development] drt054:
I flashed the latest firmware via ODIN and it never fully boots up. Just stuck on "Samsung" forever. Back to Download and flashed TWRP, latest LOS and when LOS boots up, I get Bluetooth has stopped and Wifi won't turn on. So I tried the same process with the earlier firmware and same result. Anybody else?

UPDATE: Finally got a good boot up from the firmware. Then flashed TWRP, LOS, Gapps, Magisk but still getting the bluetooth has stopped and Wifi still won't turn on. I did not get these errors when the Sam-stock booted up.

Tried the same process all over again this time not wiping /system before flashing LOS and same results.

All latest builds from October are still breaking Bluetooth and Wifi. Anybody else??
[Galaxy Tab S2 Original Android Development] drt054:
Nevermind.. 10/17/19 build works for me!!!
[Galaxy Tab S2 Original Android Development] zwipz:
Bug: Can not enable encryption

What is your--

LineageOS version: 16.0-20191024-NIGHLTY-gts28vewifi

LineageOS Download url: https://download.lineageos.org/gts28vewifi

Gapps version: not installed

Did you--

wipe: yes

restore with titanium backup: yes

reboot after having the issue: yes

Are you using--

a task killer: no

a non-stock kernel: no

other modifications: no

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

It is not possible to enable encryption.

After pressing the "Enable encryption" button; a green android is shown for about a second, then the screen goes black until the login screen appears.

I believe the following info from my logcat is relevent:

10-26 04:34:40.499 357 3042 E Cryptfs : Bad magic for real block device /dev/block/bootdevice/by-name/userdata

10-26 04:34:40.499 357 3042 E Cryptfs : Orig filesystem overlaps crypto footer region. Cannot encrypt in place.

I have also tested this on a slightly older release, 20191016, installing gapps (open gapps pico) does not help either.

No logcats have been performed using the these setups but the visible results are identical.
[Galaxy Tab S2 Original Android Development] Deltadroid:
TWRP 3.2.3 is the only version that formats the data partition correctly with the proper encryption footer.
[Galaxy Tab S2 Original Android Development] zwipz:
Thank you!

I can confirm that it works with 3.2.3 (I was using 3.3.1 before).
[Galaxy Tab S2 Original Android Development] kcallis:
I have a side question... I usually back up my apps using Titanium, but I have never felt a need to back up my data partition. Since I am going to format the data partition, what is a decent app to backup my pictures, documents, etc?