yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Android Development] MrBrause:
Frequently Asked Questions

Q1. Where are the sources?	A lot of work was done by @metterschling

https://github.com/metterschlg/android_kernel_samsung_universal5433

Device Tree

https://github.com/metterschlg/android_device_samsung_gts2-common-selinux

https://github.com/MrBrause/android_device_samsung_gts210ltexx

Vendor

https://github.com/MrBrause/proprietary_vendor_samsung

Build manifest

https://github.com/MrBrause/local_manifests
Q2. Is google needed?	You will experience slightly performance decrease, if you're using a small Gapps package.

Check out these apps F-Droid, Aurora Store, NewPipe, Open Camera.

As there is still Google inside LineageOS (Captive-Portal-Check, GPS SUPL protocol, time-service or firebase-services) make use of Google's services (perhaps MAPS) with a minimal installation.
Q3. What Gapps should I use?	I personally use OpenGapps in the pico variant and install the apps I need afterwards (only Maps and GMail).
Q4. What TWRP should I use?	I use official TWRP 3.7.0_9.

https://dl.twrp.me/gts210ltexx/twrp-3.7.0_9-0-gts210ltexx.img.tar.html

But you can also use LineageRecovery, also in the google-drive.

Flash both of them by using "Odin".
Q5. Do I need to erase everything before installing this ROM for the first time?	If you're coming from stock Samsung Android, an earlier version of Lineage or a different custom ROM, you have to - better format than just wipe - as format data removes also encryption.

Formating with TWRP: Settings->use rm -rf; Wipe->Format->yes

Formating with LineageRecovery: Factory Reset->Format data

If you are staying on perhaps this release you can install newer version simply over this version without wiping anything.
[Galaxy Tab S2 Android Development] ZG_DEV:
Thanks for your great work 👍
[Galaxy Tab S2 Android Development] excelsi:
@MrBrause great thanks for this rom! for me also registering and using fingerprint does work suprisingly 😉

Is there a lineague os 20 ROM planed or in the works? Thanks!
[Galaxy Tab S2 Android Development] MrBrause:
Thx and also great that you keep your tablet alive.

For me the fingerprint-sensor also works, but only when the tablet is not in deep sleep.

As soon as it falls into deep sleep it is not possible to use the sensor before the tablet was woken up.

I was in a discussion about LOS20 for the tablet and one of our members @eduyl successfully build it.

Maybe you could try his sources https://github.com/eduyl or mine if you want to build it for yourself

I am working on LOS18.1 for my Xcover4, so maybe I will give it a try afterwards :)
[Galaxy Tab S2 Android Development] excelsi:
Thanks! Would be nice to have a ROM ready to install as i dont have the knowledge/KnowHow to build it.

@eduyl Maybe you can release your Build. Thanks!
[Galaxy Tab S2 Android Development] freeLogix:
kindly port LOS 20 for T815Y

your rom is stable enough to get daily use
[Galaxy Tab S2 Android Development] knedlyk:
Please!
[Galaxy Tab S2 Android Development] MrBrause:
Hi there, I've received a lot of building errors and warnings during the built (a lot more than under LOS18.1). Although I've build successful, I ended up in boot loop and need more time to deep dive. This will definitely need some time.
[Galaxy Tab S2 Android Development] retiredtab:
Post the logcat and I can take a look.

Edit: Also update your github repo + manifest with the 20 branches so I can what commits you might be missing.
[Galaxy Tab S2 Android Development] MrBrause:
It looped at the samsung-logo, so I've attached the logs catched in TWRP. Hope there is something helpful in there.
[Galaxy Tab S2 Android Development] retiredtab:
Hmm, if you had build errors and boot looped at the Samsung logo, I suspect you didn't follow the 20.0 build instructions with the correct repos (namely LineageOS-UL) and my MPP patch. See

https://github.com/retiredtab/LineageOS-build-manifests/tree/main/20/exynos5433
[Galaxy Tab S2 Android Development] retiredtab:
If you did follow those instructions, then I suspect selinux rules need updating. I recommend you try the build with selinux permissive. Revert

https://github.com/MrBrause/android...mmit/f37fabddacb83dab7533a7360551574cb3e09089
[Galaxy Tab S2 Android Development] retiredtab:
Forgot to mention that you want to upload /proc/last_kmsg and /proc/kmsg while in TWRP as these will have the logs for the OS boot.
[Galaxy Tab S2 Android Development] MrBrause:
Alright, I've attached them.
[Galaxy Tab S2 Android Development] retiredtab:
Let's see your manifest.xml that you are using to build 20 with. Let me know when you push your changes to github as well.
[Galaxy Tab S2 Android Development] eduyl:
I still have the file of lineageos 20 for the t815y but it is not that stable(needs to be restarted every 3-4 hours). But hey It works!!
[Galaxy Tab S2 Android Development] MrBrause:
This is the manifest I use at the moment.

I am also interested in the one that @eduyl used.

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="MrBrause/android_device_samsung_gts210ltexx" path="device/samsung/gts210ltexx" remote="github" revision="lineage-18.1" />
<project name="metterschlg/android_device_samsung_gts2-common-selinux" path="device/samsung/gts2-common" remote="github" revision="lineage-20" />
<project name="MrBrause/android_kernel_samsung_universal5433" path="kernel/samsung/universal5433" remote="github" revision="lineage-18.1" />
<project name="MrBrause/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="lineage-18.1" />
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="lineage-20" />
<project name="LineageOS/android_hardware_samsung_slsi_exynos" path="hardware/samsung_slsi/exynos" remote="github" revision="lineage-19.1" />
<project name="LineageOS/android_hardware_samsung_slsi_exynos5" path="hardware/samsung_slsi/exynos5" remote="github" revision="lineage-19.1" />
<project name="LineageOS/android_hardware_samsung_slsi_openmax" path="hardware/samsung_slsi/openmax" remote="github" revision="lineage-19.1" />
<project name="retiredtab/android_hardware_samsung_slsi_exynos5433" path="hardware/samsung_slsi/exynos5433" remote="github" revision="lineage-20.0" />
<project name="LineageOS/android_device_samsung_slsi_sepolicy" path="device/samsung_slsi/sepolicy" remote="github" revision="lineage-20" />
</manifest>
[Galaxy Tab S2 Android Development] eduyl:
Hmm I use the same manifest. I wonder what error are you getting.
[Galaxy Tab S2 Android Development] MrBrause:
I do not receive an error. This is the one where I am bootlooping at the samsung-logo. I know that @metterschling has a patched repo for gts2, but using this repo led me to some errors during the build-process that I do not know at the moment. I have to implement @metterschling's instructions above.
[Galaxy Tab S2 Android Development] eduyl:
Did you got the compilation error like the one with the lineage wifi1 files? No solution for that just resync
[Galaxy Tab S2 Android Development] eduyl:
Also one more thing you could try using my local manifest here https://github.com/eduyl/local_manifests/blob/main/gts210ltexx.xml and see if it's still bootlooping. Build on the latest 22.04.3.
[Galaxy Tab S2 Android Development] retiredtab:
The above manifest.xml is out of date and incorrect. See

https://github.com/metterschlg/local_manifests/blob/lineage-20/gts28ltexx.xml

See metterschling's 20 build instructions for lte

https://github.com/metterschlg/los-devel-scripts/blob/main/build-environment/los20-build.sh

and his 20 lte tree (you will have to git cherry pick them)

https://github.com/metterschlg/android_device_samsung_gts28ltexx/commits/lineage-20/
[Galaxy Tab S2 Android Development] zhangjiequan:
Greetings,

I hope this message finds you well. I came across a particular model of the Galaxy Tab S2 (9.7") LTE, designated as the SM-T815C, detailed at this link: https://www.mobosdata.com/phone/samsung-galaxy-tab-s2-9-7-sm-t815c.

I would be grateful if you could confirm whether the ROM discussed in the aforementioned article is also suitable for the SM-T815C model?

Additionally, could you kindly direct me to any other discussions or posts within the XDA Forums that may shed light on ROMs specifically for the SM-T815C?

Thank you for your time and assistance.

Best
[Galaxy Tab S2 Android Development] kartik_09:
the c/y or other letters at the end of the name state from which region does the tablet belong to

and i also have a t815Y and all t815 roms i have tested works completely fine and as it should, so ig its probably suitable for t815C,

also all t815 models are exactly the same except the cellular bands, like one has b20 band and the other one doesnt, anyways there wont be an issue with the bands as if im right, this rom does not support lte and worked for me
[Galaxy Tab S2 Android Development] kartik_09:
Well turns out lte and calls works but it would still probably work
[Galaxy Tab S2 Android Development] retiredtab:
If you're bootlooping at the Samsung logo, it probably means you're missing the remove-MPPThread.patch as per these sets of instructions.

https://github.com/metterschlg/los-devel-scripts/blob/main/build-environment/los20-build.sh#L35-L39
[Galaxy Tab S2 Android Development] MrBrause:
I followed those instructions and implemented the MPP-patch. The other fix for samsung_slsi libfimg4x was also needed.

I am building on Ubuntu22.04 with kernel 5.15 (older kernel because of the Dex2Oat issues).

I have a lot more log-files if needed, but no ideas at the moment.

If you have another idea or push me into another direction?
[Galaxy Tab S2 Android Development] retiredtab:
Post all the logs and I'll take a look.
[Galaxy Tab S2 Android Development] MrBrause:
Please find attached three zip-files.

Logs15 and 24 contain 4 files each. Logs22 contains only last_kmsg logs, as these contain the most important information.
[Galaxy Tab S2 Android Development] retiredtab:
I didn't look at the logs yet, but I noticed that you are using

<project name="metterschlg/android_kernel_samsung_universal5433" path="kernel/samsung/universal5433" remote="github" revision="lineage-20-r22" />

Since metterschling doesn't have a SM-T815, he did NOT update the arch/arm/configs/lineage_gts210ltexx_defconfig file that is required to work with the Mali graphics driver R22P0.

Without updating your local copy of arch/arm/configs/lineage_gts210ltexx_defconfig, the graphics will never work and you will never see the LineageOS boot animation and other OS subsystems will fail as a result.

You need to pull his commits and modify your local copy of arch/arm/configs/lineage_gts210ltexx_defconfig to match metterschling's arch/arm/configs/lineage_gts28ltexx_defconfig.

That is, your arch/arm/configs/lineage_gts210ltexx_defconfig needs to look like

https://raw.githubusercontent.com/m...arch/arm/configs/lineage_gts28ltexx_defconfig

You can look at the git commit history at (starting with the Jul 3, 2022 commit and working to the Nov 26, 2023 commit)

https://github.com/metterschlg/andr...arch/arm/configs/lineage_gts28ltexx_defconfig

You can ignore the Jul 3, 2022 commit labeled "Enable SELinux Enforcing" for now until your build boots and works. Once you are happy with your build, then you can enforce and rebuild your rom.

PS. Using a linux tool like meld can help you visualize the differences between lineage_gts210ltexx_defconfig and lineage_gts28ltexx_defconfig
[Galaxy Tab S2 Android Development] MrBrause:
Thanks for the comprehensible answer and it sound pretty obvious as you explain it.

I will keep on working.
[Galaxy Tab S2 Android Development] retiredtab:
Can you update your kernel github repo with the changes you made locally so I can see if you did them correctly?

I took your manifest.xml and was able to make a LineageOS 20 SM-T815 build that is working.

Here's my git diff from kernel/samsung/universal5433 directory.

$ git diff
diff --git a/arch/arm/configs/lineage_gts210ltexx_defconfig b/arch/arm/configs/lineage_gts210ltexx_defconfig
index d745fa8485e..1499aae0f59 100644
--- a/arch/arm/configs/lineage_gts210ltexx_defconfig
+++ b/arch/arm/configs/lineage_gts210ltexx_defconfig
@@ -110,7 +110,7 @@ CONFIG_RESOURCE_COUNTERS=y
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_CFS_BANDWIDTH is not set
-CONFIG_RT_GROUP_SCHED=y
+# CONFIG_RT_GROUP_SCHED is not set
# CONFIG_BLK_CGROUP is not set
# CONFIG_CHECKPOINT_RESTORE is not set
CONFIG_NAMESPACES=y
@@ -1816,8 +1816,8 @@ CONFIG_INPUT_EVDEV=y
# CONFIG_GLOVE_TOUCH is not set
CONFIG_HALL=y
# CONFIG_CERTIFY_HALL is not set
-CONFIG_HALL_ACCESSORY=y
-# CONFIG_SENSORS_HALL_IRQ_CTRL is not set
+# CONFIG_HALL_ACCESSORY is not set
+CONFIG_SENSORS_HALL_IRQ_CTRL=y
# CONFIG_INPUT_EXPANDED_ABS is not set

#
@@ -2763,7 +2763,7 @@ CONFIG_ION=y
CONFIG_ION_EXYNOS=y
CONFIG_ION_EXYNOS_STAT_LOG=y
CONFIG_ION_EXYNOS_OF=y
-CONFIG_DDK_VERSION_OS="n"
+CONFIG_DDK_VERSION_OS="o"

#
# ARM GPU Configuration
@@ -2772,7 +2772,8 @@ CONFIG_MALI_T7XX=y
# CONFIG_MALI_R5P0 is not set
# CONFIG_MALI_R7P0 is not set
# CONFIG_MALI_R12P0 is not set
-CONFIG_MALI_R15P0=y
+# CONFIG_MALI_R15P0=y
+CONFIG_MALI_R22P0=y
# CONFIG_MALI_GATOR_SUPPORT is not set
CONFIG_MALI_DVFS=y
CONFIG_MALI_RT_PM=y
@@ -2796,7 +2797,7 @@ CONFIG_MALI_SEC_LEGACY_SUPPORT=y
CONFIG_MALI_MIDGARD=y
# CONFIG_MALI_MIDGARD_DVFS is not set
# CONFIG_MALI_CORESTACK is not set
-# CONFIG_MALI_FENCE_DEBUG is not set
+CONFIG_MALI_FENCE_DEBUG=y
# CONFIG_MALI_GPU_MMU_AARCH64 is not set
CONFIG_EXYNOS_SOC_NAME="5433"
CONFIG_MALI_SEC_CL_BOOST=y
@@ -2805,6 +2806,11 @@ CONFIG_MALI_PM_QOS=y
# CONFIG_MALI_BTS_OPTIMIZATION is not set
CONFIG_MALI_DEBUG_KERNEL_SYSFS=y
# CONFIG_MALI_EXYNOS_SECURE_RENDERING is not set
+CONFIG_MALI_EXYNOS_SECURE_RENDERING=y
+# CONFIG_MALI_JOB_DUMPING is not set
+# CONFIG_MALI_2MB_ALLOC is not set
+# CONFIG_MALI_PWRSOFT_765 is not set
+CONFIG_MALI_SEC_JOB_STATUS_CHECK=y
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
CONFIG_FB=y

Just to confirm. After you changed your manifest.xml to point to the new and updated repos/branches, did you do a full repo sync? That is,

repo sync --force-sync
breakfast gts210ltexx
brunch gts210ltexx

Since I'm able to make a 20 T815 bootable build, there's something likely wrong with your local configuration or repos?
[Galaxy Tab S2 Android Development] kartik_09:
if u dont mind, could you share .zip file of the build?
[Galaxy Tab S2 Android Development] MrBrause:
Thanks for building and testing the image.

Yes I did a force-sync, but sometimes I had the problem that I got some sync-errors, so I had to remove the repo from the xml and do a force-remove-dirty, and/or remove the .git files/folders from the project/-list folders, followed by a make clean and a brunch gts210ltexx-userdebug directly. Sometimes I only use breakfast and lunch without a brunch and fired the make command with dist otatools and so on to get more detailed error messages.
[Galaxy Tab S2 Android Development] retiredtab:
I will NOT be making any public or private 815 builds available to anyone. I only built and tested it on my T810 (wifi only) as proof of concept to help @MrBrause figure out the problem.

Even though it boots, there could be other problems with RIL/LTE, etc that I cannot test for.
[Galaxy Tab S2 Android Development] retiredtab:
Anytime I run into sync errors, I fix them and once 100% clean, I run repo sync --force-sync AGAIN to verify.

I've had weird problems in the past when I've run into sync errors and where I purposely stopped repo sync because I forgot something, have repo sync say 100% clean and then end up deleting EVERYTHING because when it came to compiling, it had strange errors. In fact, it just happened a few days ago working on a new project.

I don't fully trust repo sync now which is why I run it twice after fixing errors.
[Galaxy Tab S2 Android Development] aljazzair:
Dear @MrBrause

First of all, I would like to thank you for reviving the Tab S2 with this build.

I am currently on a LineageOS 17 version from 20210825 by Ripee.

I would like to try your LineageOS 18 build, can you please if Bluetooth Headset is supposed to work with phone calls using the BT earbuds microphone?

The release notes mention headset should work, but I am unsure if it's just wired, or BT as well.

Thank you.
[Galaxy Tab S2 Android Development] MrBrause:
Hi,

yes it should work, as there are commits inside the device-tree for bluetooth-telephony offered by one of the seniors @metterschling . I did not tested it by myself, but I am interested in feedback.
[Galaxy Tab S2 Android Development] metterschling:
I haven't got BT telephony working, but cabled headset is working with the Audio Policy configuration I provide with my T715 builds. Having tried for months I wasn't able to get every Audio routing working and nobody else was willing or able to help so the current audio configuration is the best we can get. Also see the related poll and posts in my T715 los20 thread for reference.
[Galaxy Tab S2 Android Development] MrBrause:
Thank you for pointing that out.
[Galaxy Tab S2 Android Development] aljazzair:
I have tried the instructions in the LineageOS20 T715 thread (post #14, etc).

First, I reviewed both xml configs and compared them to the one I have in my LOS17 build.

I noticed one was identical functionally but with differences in syntax, the one without the telephony bit. I tried it, and was stuck at the Lineage logo. Then I used the one with the telephony bit, after adjusting the syntax (there were commas instead of spaces in the xml config file).

The tablet booted, I was able to test my BT headset, but it did not work.

So I reverted to the original audio policy configuration.

I have not tried @MrBrause built yet.

Thank you both for your kind feedback.
[Galaxy Tab S2 Android Development] metterschling:
For a programmer the blanks within the XML look strange, but this is what Google defines, see here.
[Galaxy Tab S2 Android Development] aljazzair:
Thanks for the link. I will read it.

In my Lineage OS 17.1 build, so Android 10,

the audio policy configuration xml used commas instead of spaces in some places.

Example diff:

channelMasks="AUDIO_CHANNEL_IN_MONO AUDIO_CHANNEL_IN_STEREO AUDIO_CHANNEL_IN_VOICE_UPLINK AUDIO_CHANNEL_IN_VOICE_DNLINK"

channelMasks="AUDIO_CHANNEL_IN_MONO,AUDIO_CHANNEL_IN_STEREO,AUDIO_CHANNEL_IN_VOICE_UPLINK,AUDIO_CHANNEL_IN_VOICE_DNLINK"

Attached are four files, two from your T715 thread, one is the original policy config from LineageOS 17, the one named 'tested' is the one that allowed the tablet to boot up, but BT telephony was not successful with it.
[Galaxy Tab S2 Android Development] kartik_09:
btw any update for LOS 20 for t815? :)
[Galaxy Tab S2 Android Development] MrBrause:
Still working on it. Dealing with some errors concerning Androids BPF and all the following services i.e. netd, because of the kernel-version < 4.9.
[Galaxy Tab S2 Android Development] aljazzair:
Hello

I tried this LOS18 build on my T815.

Installation went smoothly via TWRP.

I first got it booted with Mindthegapps, did a quick look around for a few minutes and everything seemed to work fine, in fact it seemed to be blazing fast ...

Then I decided to try other Gapps packages. Each time, I erased eveything and started over, with BITGapps and Opengapps. Each time, I did a quick look around to see the differences, and everything seemed OK.

I then tried to switch back to the initial Mindthegapps package, but for some reason, even though I erased everything, it would not install this time (error 1 - could not mount /mnt/system).

Long story short, after an unsuccessful troubleshooting attempt and thorough reading of many threads on this subject on XDA, I finally decided to use BITGapps Mini Package for a real life, intensive use of the tablet for a full day.

Unfortunately I ran into audio issues: for example the Music app would not play sound on the tablet speaker, even though Spotify did.

Same issue with Google Assistant: it would not play sound on the tablet speaker, until at some point I received a phone call and thereafter, sound started coming out of the speaker for other apps, until I rebooted and it went back to no audio.

I tried BT calls, did not work.

I tried to switch to the other audio_policy_configuration.xml provided in the LOS20 T815 thread, but BT calling did not work, nor did it resolve the vanilla audio issues.

In addition I ran into some trouble with the Sim functionality: the tablet sometimes does not recognize the sim card. I have to reboot several times to get it to register. So no calls, no LTE, no 3G.

Also, battery drains faster than it did with the LOS17 build I previously had.

All in all, the tablet is fast and nice to use when it works, but the audio issues and the sim card issues prevented me from using it reliably as a "big phone", like I had hoped to.

Not sure if those are issues that others have noticed.

I will be erasing the tablet again tomorrow, and test drive it with Opengapps to see if it improves the overall experience.
[Galaxy Tab S2 Android Development] MrBrause:
I've never experienced those issues with RIL and so on in the LOS18. Sounds a bit like a problem because of a "dirty" install. I've used OpenGapps from Mini to Pico. I mentioned the installation-process in this thread, thought it was in the FAQ. I always experienced that if I am to fast after the reboot entering the PIN or do not wait a few seconds, I get problems with the SIM card.
[Galaxy Tab S2 Android Development] MrBrause:
As I do not have time for about the next two weeks or so, I uploaded the last booting LOS20 release for the T815 in the google-drive used in this thread at the beginning. Here you have to wait for about 20-30s after booting until the SIM is detected. This release is not tested over a long time, and this is the one with the BPF-errors. The logcat is attached.

I would say that it is NOT stable at the moment.

I used NikGapps-basic-arm64-13 as the Gapps-package.

03-29 12:11:45.470 3866 5028 E BpfNetworkStats: get ifaceStats map fd failed: Function not implemented
03-29 12:11:46.476 3866 5028 E BpfNetworkStats: get ifaceStats map fd failed: Function not implemented
03-29 12:11:46.479 3866 5028 E BpfNetworkStats: get ifaceStats map fd failed: Function not implemented
[Galaxy Tab S2 Android Development] kartik_09:
Wait, how did u use arm64 64bit package, wasnt the tab s2 lower level bootloader ( like note 4) only supported 32bit or arm/armv7a so that it could not at all run 64bit even though it was capable of it and nobody was able to do that on note 4 because u would require UART access for it(to modify lower level bootloader)

Edit: also if ur having eBPF error, does wifi also get affected?