yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Android Development] prkfsz:
Trying to backup data using backup function in settings. I get to choose the location of the backup but the option of storing it on the inserted micro sd-card is greyed out. Options to choose from are internal sd-card and the device sm-t813. Whatever option i choose i can't find the backed up file to copy it to the micro sd-card. Where does it end up? And how come saving it on the micro sd-card is not possible?

EDIT

Found it. One has to check for 'show hidden files'. And it was even saved on micro sd-card, i presume when i chose the internal sd-card.
[Galaxy Tab S2 Android Development] prkfsz:
Another roadblock.

Using Mull-browser and i want to save bookmarks. When trying to save them i get no relevant choices for me. I need to save them as a file but the app does not see native file explorer which is required for that. I find this rather common behaviour with apps even on stock roms while trying to save content. Installing another file explorer has always solved that problem so far. But this device refuses to grant the external file explorer access to storage, "for my protection". I can''t find any alternatives where that would be possible. I have granted to the extern file explorer permission to access all files, but that doesn't help.

How fix this?
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-20.0-20230918-UNOFFICIAL-gts210vewifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.

Sept 18, 2023

1. Incorporates Sept 5th security patches as per https://review.lineageos.org/q/topic:"T_asb_2023-09"

2. Whatever LineageOS changed since Aug 5th security patches. About 9,500 files had to be compiled.
[Galaxy Tab S2 Android Development] FordPrefect:
Thank you so much for your efforts! You brought new life to my old tablet.

I installed the new build. Everything went well, and it's running perfectly nice. I noticed one thing .. With the August build at least for me, GPS location didn't work. It never got a lock and timed out. With the new build it works.

The battery life is amazing!
[Galaxy Tab S2 Android Development] FordPrefect:
Sorry to pull up that older post, but it was asking about similar experiences.

I was searching custom ROMs for my good old T813 tablet. I tried several of the LineageOS versions around, and unfortunately I was experiencing the very same behavior. The tablet crashed and boot looped. It seemed to work for some time, but then crashed in different apps, different scenarios etc. When it even crashed while being in TWRP recovery, I figured that this can not possibly be any custom ROM failure. I found hints that other people were talking about temperature being too high.

Finally, I decided to replace the battery. I ordered a 20 Euro piece from a Chinese shop. After replacing ... boy, I was surprised! The tablet runs as new, and I happily returned to this build. The battery life is amazingly better than before. As a side note, the new battery even has a 6950 mAh capacity, as compared to the original 5800(?). So in a way, battery life even is better than ever.

Bottom line, I recommend giving replacing the battery a try.
[Galaxy Tab S2 Android Development] prkfsz:
Thank you for answering to that. By now I did get quite convinced that the battery is the culprit. Just didn't get around to order a new one. Can you post a link of the one you got? Even tho I am always suspitious of chinese batteries with higher capacity than original... 😄🤔
[Galaxy Tab S2 Android Development] fredmo:
Nice work !

I upgraded the TWRP, did a full wrap, installed your version, and did some APK installations.

Compared to the Lineageos 17.1, I have the feeling that the battery is working!

But on the other hand, I completely removed Google, It's a clear install without GPS, without Google Store...

I will limit myself only to my apps needed, and my preferred internet browser, no more.

Thank you again.
[Galaxy Tab S2 Android Development] FordPrefect:
Using this version for several weeks now, without any major problem. The only (very minor) thing I noticed is that when I'm in an application, and press the Home button, for a split second a full screen app icon is visible. Lacking a better description and I have no clue how I could capture this. Anyway, it's really not an issue.

The only thing I feel sad about is that the fingerprint sensor does not work. I know it's known and (not) working as advertised. It's just that I wish it worked. Thanks for the good work! Looking forward to installing the October update.
[Galaxy Tab S2 Android Development] retiredtab:
I have a SM-T290 which is running official LineageOS 20 and it shows the same behaviour with the split second full screen app icon showing. This is either a LineageOS or AOSP ""feature". Either way, it's likely upstream and I won't be spending anytime looking for the code and it's beyond my skill set.
[Galaxy Tab S2 Android Development] FordPrefect:
That's OK, it was just an observation, but is really a non-issue for me. Thanks for looking into it!
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-20.0-20231011-UNOFFICIAL-gts210vewifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.

Oct 11, 2023

1. Incorporates Oct 6th security patches as per https://review.lineageos.org/q/topic:"T_asb_2023-10"

2. Whatever LineageOS changed since Sept 5th build. About 21,000 files needed to be recompiled.
[Galaxy Tab S2 Android Development] FordPrefect:
Installed the new version and it works perfectly nice. I didn't encounter any problem so far. Good job, thanks for your efforts!
[Galaxy Tab S2 Android Development] fredmo:
Hello,

I installed the version of the 19/09.

Is it normal that after going on "System" -> "Upgrade manager", the new version of the 11/10 is not proposed?

Is the upgrade over the air supported?

Thanks
[Galaxy Tab S2 Android Development] FordPrefect:
OTA is not available on this build. You have to download the updates manually, and then install with twrp.
[Galaxy Tab S2 Android Development] fredmo:
Useful info :

The firmware of 19/09 had an automatic reboot when Firefox was running the URL drive.google.com

This issue is not reproduced with the firmware of the 11/10.
[Galaxy Tab S2 Android Development] retiredtab:
I've made zero changes to my device trees since July 13, 2023. It might be an AOSP or LineageOS change that affected Firefox?
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-20.0-20231113-UNOFFICIAL-gts210vewifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.

Nov 13, 2023

1. Incorporates Nov 5th security patches as per https://review.lineageos.org/q/topic:"T_asb_2023-11"

2. Whatever LineageOS changed since Oct 6th build. About 11,000 files needed to be recompiled.
[Galaxy Tab S2 Android Development] FordPrefect:
Installed the new build, and it works perfectly nice so far. Thank you for keeping our good old tablet up to date!

Just out of curiosity, do you think that we will eventually have a working camera or fingerprint sensor? I mean as a "side effect" of updating the LineageOS tree? Again, this is no deal breaker for me, just curious to get your judgment.
[Galaxy Tab S2 Android Development] retiredtab:
To expand on what I already stated in post 1 under section "Known issues/What doesn't work/what's not tested"

the camera hal stopped working properly starting with LineageOS 17.1. In 16.0, it worked using hardware hal hwbinder, but that causes a crash in 17.1. So hardware hal passthrough was used in 17.1 and while camera works, there's a 10 second delay before it activates. There's only two options: hwbinder or passthrough.

Passthrough works in 18.1, but not anymore starting with 19.1 because LineageOS deprecated most of the old camera functionality. While the repo I used to build 19.1 and 20, LineageOS-UL, reverted most of those camera changes for "legacy" devices like ours, there's something else that causes passthrough not to work. hwbinder causes a crash in 19.1 and 20 as well.

As I stated in post #1, the Samsung camera drivers are proprietary so they can't be changed and there's no open source implementation.

As for fingerprint, I've spent weeks working on fingerprint for the ST-813 predecessors, namely the SM-T800 and SM-T810. The fingerprint drivers are Samsung proprietary and they never worked 100% properly with the two predecessors. Since I never use this feature and there's viable alternatives like pin or pattern lock and unlock, I won't be working on fingerprint.

In addition, Android 12 requires keystore2 implementation which is responsible for lock/unlock. If it wasn't for Kyle Harrison who kindly pointed out that my kernel hwbinder code was too old, there would be no LineageOS 19.1 or 20 for any of the roms that I build. I spent 3 months of my free time trying to boot into the lock screen before I got Kyle's analysis. In addition, I found that keystore2 was not compatible with Samsung's propreitary fingerprint driver in SM-T810.

If people require these 2 features, they are welcome to try and fix it themselves as all my code is open source on github. As I clearly stated in post #1, I won't be spending any of my free time looking at these 2 features unless someone hands me WORKING TESTED T813 code. Pointing to other githubs that have working camera and fingerprint for completely different devices DOES NOT COUNT.
[Galaxy Tab S2 Android Development] retiredtab:
@MSgtTUSMC, the above is now fixed in the Nov 13, 2023 build. I did nothing to fix it so the fix probably came from LineageOS.
[Galaxy Tab S2 Android Development] FordPrefect:
Thank you for the detailed explanations! My question never meant that I'm asking you or someone else to work on it. Was just curious about the technical background of the problem. You do an amazing work, and I never thought it would be possible to bring such an up-to-date version to the T813! Thanks again :)
[Galaxy Tab S2 Android Development] mielcu3:
Hi mate, can you help me adapt T-713 ROM to T-719 device? I tried to change device id in script, but still getting some error with installation tries.
[Galaxy Tab S2 Android Development] retiredtab:
This thread is for T813 ONLY. Please take your discussion somewhere else. Thank you.
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-20.0-20231211-UNOFFICIAL-gts210vewifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.

Dec 11, 2023

1. Incorporates Dec 5th security patches as per https://review.lineageos.org/q/topic:"T_asb_2023-12"

2. Whatever LineageOS changed since Nov 5th build. About 7,500 files needed to be recompiled.
[Galaxy Tab S2 Android Development] fredmo:
Hello,

Sometimes, there is a crash of the tablet / black screen and reboot.

It would be fine to enable the core-dump support of the kernel to share with you the debug information,

or if it's already available, please explain how to activate it.

By default, please find a boot logcat, I don't know if it would be helpful.
[Galaxy Tab S2 Android Development] retiredtab:
Your logcat.txt shows nothing that helps. Follow the instructions exactly in this post below step 1 to get tombstones.

https://xdaforums.com/t/troubleshoo...rs-running-any-version-of-android-10.4308203/
[Galaxy Tab S2 Android Development] fredmo:
As requested :
[Galaxy Tab S2 Android Development] retiredtab:
There's nothing there to indicate a problem. If it happens again, you will have to provide way more detail like:

1. what date/time did it random reboot (down to the minute and second helps)

2. what were you doing, what app were you running

3. what is/was the battery % level

4. get both the logcat and tombstones
[Galaxy Tab S2 Android Development] FordPrefect:
Using the December build for about two weeks now in everyday use, and for me it works flawlessly! Always a pleasure to see my good old tablet running just as new. Thanks a lot!
[Galaxy Tab S2 Android Development] moloko01:
Congratulation and thanks for your great work. This runs better than the LOS 17.1 we had used before.

We own 3 S2 tabs (2 sm-t813 + sm-t713).

Issues with unlock fingerprint is not importand for us and WE don't use the Kamera on this devices.

We got bootloop (first time) by battery less then 20% as told from others before. But there is no need to change the battery on our devices. This goes better after each charge.

Battery stats must learn after set up .

Only issue for us ist the missing of a soundliberary to watch TV. So this is an issue of LOS 20 general and WE have ti wait.

Thank you for keep this devices alive!

Copy/paste this for 713 and 813.
[Galaxy Tab S2 Android Development] retiredtab:
Is there an error message in logcat for this missing sound library? If yes, please get a logcat as per FAQ #9 in post #2.
[Galaxy Tab S2 Android Development] moloko01:
No, I have no logcat and the app (Dreamplayer for Fritzbox, based on VLC) shows no Errormassage.

Problem ist known:

[UNOFFICIAL][ROM]ALPHA LineageOS 20 for SM-T813 - Jun 23, 2024

PLEASE BEFORE YOU decide to try this rom, you MUST read all of post 1, 2, 3 and 4 (about 10 minute read). If you think this is an unreasonable request, then stop reading now and find another rom. Thank you. This is ONLY for the SM-T813. I do not...

xdaforums.com
[Galaxy Tab S2 Android Development] A_l_S.001:
Hello everyone,

Here are my experiences with the installation of the Rom.

After many failures, I now have everything the way I want it.

Here are the steps that led to my success (I'll leave out the others):

1. installation of TWRP 3.0.1 with Odin 3.14.4 and then a backup of the existing system (Android 7)

2. installation of TWRP 3.6.1_9 (3.7.0_9 does not work for me)

3. installed lineage-20.0-20231216-UNOFFICIAL-gts28ltexx.zip and LiteGapps_arm_13.0_v2.8_official.zip in TWRP. Then restarted the tablet and set it up.

4. later restart the tablet into TWRP and install Magisk-v22-0.zip (the .akp file must be renamed to .zip).

5. restarted the tablet and set up Magisk (which then wanted to update itself again).

6. done

I haven't tested everything yet, but what I can say is that it's fast and doesn't contain any superfluous stuff. The Play Store works and it's easy to get everything you want.

Many thanks to metterling and everyone else

Great work!!!
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-20.0-20240112-UNOFFICIAL-gts210vewifi.zip

Release notes

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.

Jan 12, 2024

1. Incorporates Jan 5th security patches as per https://review.lineageos.org/q/topic:"T_asb_2024-01"

2. Whatever LineageOS changed since Dec 5th build. About 17,500 files needed to be recompiled.
[Galaxy Tab S2 Android Development] fredmo:
Hello,

We saw 2 reboots this morning,

but strangely by connecting in USB the tablet to capture the adb log, I don't succeed in reproducing it,

Nevertheless, please find the adb log.

There are some warnings, which could interest you :

1/ "ro.vndk.version not defined or invalid (), this is mandated since P."

2/ libprocessgroup: Failed to open /dev/blkio//cgroup.procs: No such file or directory

3/ BpfNetworkStats: get ifaceStats map fd failed: Function not implemented

Regards,
[Galaxy Tab S2 Android Development] retiredtab:
Of the 4 things, I asked for, you only provided only half of ask #4. Looking through 58,000 lines of logcat code is not my idea of fun on my weekend having NO CLUE what you are doing. If you're not going to provide the other detailed information, there's no sense looking through your log.

As for 1. that message is harmless. 2. is fine. 3 is fine because our kernel is too old to support ebpf and we need hacks to make it even boot Android 12 and higher.
[Galaxy Tab S2 Android Development] fredmo:
As previously I didn't succeed in reproducing, I share what I have.

The crash could appear during browsing with Firefox, or while checking the Android settings menu, or by reading ebook, there was no scenario.

But this time, I have a scenario :

With firefox nightly, after installing it from:

Directory Listing: /pub/fenix/nightly/2024/01/2024-01-08-04-03-05-fenix-123.0a1-android-arm64-v8a/

I try to open again the same URL with the firefox nightly

There is the both logcat and tombstones.
[Galaxy Tab S2 Android Development] rhcohen:
Hello, I am new to this ROM (but an old-timer with LOS) -- I installed it two weeks ago, as an app I was using with started requiring a newer OS. Considering this ROM is designated as "Alpha" I am amazed at how well everything works. Great work, @retiredtab . I do have two questions:

(1) I have been on the December build. To update to the Jan 12 build, can I just do a dirty flash, or is it advised to wipe and do a clean install?

(2) There seems to be a general issue with LOS on many devices that speaker volume and microphone gain are much lower than stock. I am experiencing that. The fix seems to be to change settings in the files media_profiles.xml and sysstem_paths.xml, in /etc and /vendor/etc. But the proper settings are evidently device-specific. Does anyone out there know of good settings for the t813?
[Galaxy Tab S2 Android Development] retiredtab:
You can do a dirty flash, but I always recommend backing your data before doing so in case something goes wrong.

The file is mixer_paths.xml in the stock rom and it is IDENTICAL to the one in T813. It's just renamed mixer_paths_wcd9330.xml in LineageOS for some reason, but the 2 files are IDENTICAL.

If you want to change the values, it's probably line 1092 and/or 1093 at for speaker

https://github.com/retiredtab/gts210vewifi/blob/lineage-20/audio/mixer_paths_wcd9330.xml#L1092-L1093

I suggest making it in increments of 3, so change it to 34.

For mic, it's probably line 1152 and/or 1153. It's at 38 so you can try 41.

To edit this file.

# 1. Boot into TWRP
# 2. Touch Mount System to mount the /system as read write
# 3. on your PC, get mixer_paths_wcd9330.xml via pull
adb pull /system/vendor/etc/mixer_paths_wcd9330.xml
# 4. Use a text editor to make the changes to your local copy of mixer_paths_wcd9330.xml
# 5. push the file back onto the tablet using
adb push mixer_paths_wcd9330.xml /system/vendor/etc/mixer_paths_wcd9330.xml
# 6. reboot tablet
# 7. repeat until you're happy with the values.
# 8. If there's no change to the volume or mic, then look at some other values in the .xml file.

Note when you upgrade to next month's security patch, it will overwrite your changes in mixer_paths_wcd9330.xml. I have no plans to make changes to this file as it's identical to stock and I have no problems with the speaker volume.
[Galaxy Tab S2 Android Development] rhcohen:
@retiredtab , thanks so much for the quick reply, and for replying to both of my questions. I didn't expect an answer from you on the second one, that was more for anyone on the thread. I am surprised that mixer_paths.xml is the same in stock. Something must be different tn the audio processing of LOS, since, at least for me, speaker volume is noticeably softer and tinnier on LOS, and I've read lots of comments on XDA about this in multiple devices. As to the mic: it seems fine for calls using my two VOIP apps (Google Voice and my cell carrier's app), but for recording, either with the LOS recorder app or with a third-party app I've used for many years, the microphone gain is way lower than on stock. (At least that is my experience). But I think you've pointed me to the right lines in mixer_paths to modify the mic (in the Recording Scenario). As to the speaker, that seems low for both media and VOIP apps, so I suppose I might need to modify lines 1975 and/or 1976, in addition to 1092/93. DAC1 playback volume seems like it's on a different scale than Speaker playback volume, as the value is nearly six times higher (175). Seems like a change to 178 would have no noticeable affect.
[Galaxy Tab S2 Android Development] fredmo:
Hello,

Even if there is a Firefox crash, it's strange to have a hardware reboot of the tablet.

Should I do a reset factory of the tablet? to format the filesystem?

Would it be beneficial for my random hardware reboot ?
[Galaxy Tab S2 Android Development] rollinrollinrollin:
^^Perhaps the battery or this one?

[UNOFFICIAL BUILDS] for Samsung Galaxy Tabs S2 /e/OS-R

Made a short test, indeed it crashed fast while typing an URL in browser Mull. Max. auto brightness seems not to be the problem but indeed Live Display/Auto outdoor something

community.e.foundation
[Galaxy Tab S2 Android Development] bacano3:
Can anyone tell me if this ROM supports Zwift app without any issue?? Does it support Bluetooth to connect external sensors?

I'm trying to revive my old tablet just to use as a screen for Zwift indoor cycling because the app is not supported anymore on the original Android 7.0 it has now.

Zwift - Apps on Google Play

Zwift: Indoor cycling made fun

play.google.com

Thank you.
[Galaxy Tab S2 Android Development] maiki1:
i can't install zwift on this rom and problem with pairing garmin connect with my watch otherwise bluetooth works
[Galaxy Tab S2 Android Development] bacano3:
That's too bad.

Is there any error while installing the Zwift apk?

The app should be using newer Android API not available on the device.
[Galaxy Tab S2 Android Development] maiki1:
I couldn’t install it with play store but with aurora once zwift launch it asks to update with play store
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-20.0-20240220-UNOFFICIAL-gts210vewifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.

Feb 20, 2024

1. Incorporates Feb 5th security patches as per https://review.lineageos.org/q/topic:"T_asb_2024-02"

2. Whatever LineageOS changed since Jan 5th build. About 15,500 files needed to be recompiled.

3. Updated selinux rules to allow built in files and music app to work. See https://github.com/retiredtab/msm8976-common/commit/db8c134a9a7360ad7faa864e4196ae4f481fc818

NOTE: The updated selinux rules is exactly WHY I test each and every build before uploading. So one or more of the Feb 5th patches affected that functionality.