yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-20.0-20240316-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.

Mar 16, 2024

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

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

3. Enabled zram. See https://github.com/retiredtab/Linea...mmit/15fea0fa098b58edc7f9efff3d63cb92e36ed6a8 and https://github.com/retiredtab/msm8976-common/commit/c1e350f2ca2988c1f8ce79ee5c50078b5c66119f
[Galaxy Tab S2 Android Development] simquax:
First of all thanks a lot for the ROM, awesome job!

Used the official LOS 16.0 and ripee's LOS 17.1 before. Compared to the both there is an additional delay of about 5 seconds between Samsung logo screen and LOS boot animation. Booting itself is very fast, though.

My config: TWRP 3.6.2_9-0, Mar 16 build of the ROM, no GApps, F-Droid + Privileged Extension OTA instead

What could cause the delay? Is it something to worry about?
[Galaxy Tab S2 Android Development] fredmo:
After substituting the battery following an extensive 8-year usage period, the unanticipated system restart has not recurred thus far. This suggests that the battery replacement has potentially resolved the issue.
[Galaxy Tab S2 Android Development] retiredtab:
As you're probably aware, each new version of Android adds more code and bloat. I estimate each new Android version adds about 10 to 15% more code and this affects boot time.

As long as it boots, there's no problem. Keep in mind, you're only booting if you're upgrading the rom via TWRP.
[Galaxy Tab S2 Android Development] simquax:
Actually the tablet feels at least as fast as on day one at the moment, maybe because Andoid has been performance-optimized, too, and I've installed just a handful of apps yet. I'm using it as a comic book reader for the main part.

Thank you, that calms me down. In fact, I didn't upgrade but had to install the required newer version of TWRP first, followed by Wipe Dalvik / Art Cache, System, Data, Cache + Format Data.

That brings me to my last question: I've never done Android system updates manually. As I understand it, I could either select the downloaded file in the Settings app > System > Software update or boot into recovery and do TWRP > Install.

What's the recommended way?
[Galaxy Tab S2 Android Development] 2faraway2:
TWRP->Install (called 'dirty flash') :)
[Galaxy Tab S2 Android Development] retiredtab:
OTA, over the air, is NOT supported in any rom I build and I have NO plans to ever do so. It's another headache that I don't want to deal with.

Boot into TWRP and flash the new build.
[Galaxy Tab S2 Android Development] Sunport:
And again thx for this firmware too, install today to my own t813 without gapps, using Aurora on your advice - real faster working against with gapps! 👍🍻
[Galaxy Tab S2 Android Development] retiredtab:
Just beware Aurora Store is in the process of moving it's servers so there will be disruption in the next 48 hours until it's done. You may get bad gateway, no server found, etc. I run into this myself today.

https://gitlab.com/AuroraOSS/AuroraStore/-/issues/1076
[Galaxy Tab S2 Android Development] Alex7779:
@retiredtab

Hello, thanks for the ROMS!

I would like to ask if it would be theoretically possible to have a newer kernel on this device.

Android API 33 supports MIDI 2.0 and I would like to try it on my T813.

I just read there need to be some configs set in the kernel and only recent Linux für nel support MIDI 2.0.

Kernel Configuration¶​

The following new configs are added for supporting MIDI 2.0: CONFIG_SND_UMP, CONFIG_SND_UMP_LEGACY_RAWMIDI, CONFIG_SND_SEQ_UMP, CONFIG_SND_SEQ_UMP_CLIENT, and CONFIG_SND_USB_AUDIO_MIDI_V2. The first visible one is CONFIG_SND_USB_AUDIO_MIDI_V2, and when you choose it (to set =y), the core support for UMP (CONFIG_SND_UMP) and the sequencer binding (CONFIG_SND_SEQ_UMP_CLIENT) will be automatically selected.

Additionally, CONFIG_SND_UMP_LEGACY_RAWMIDI=y will enable the support for the legacy raw MIDI device for UMP Endpoints.

MIDI 2.0 on Linux — The Linux Kernel documentation

Any thoughts on this?

Thanks
[Galaxy Tab S2 Android Development] retiredtab:
Theoretically possible = yes. However, it's not a trivial task and I will not be even attempting to try.

I've tried upstreaming other kernels in the past and it's a manual error prone time consuming process laced with merge conflicts that need to be resolved manually. The process easily takes days if not weeks. At the end of the process, there's no guarantee that it will work or be bootable or reliable.

In addition, many of Samsung proprietary blobs may only be compatible or work with the current 3.x kernel. Updating the kernel may break proprietary blob functionality like wifi, bluetooth, graphics, sound, gps, etc.

As you can see in these commits, I already had to hack the proprietary blobs to work with Android 13.

https://github.com/retiredtab/propr...mmit/22b769bb251e7e96531618b796b6e896b0d1d079

https://github.com/retiredtab/propr...mmit/626e38a95e3eecc41a5d1e4b0d03359a264e3ec2

If some people want to try, they are welcome, but it won't be me. If they get it working, they are welcome to post here and I will see about incorporating into the rom. For those trying, I suggest starting with kernel 4.19 or higher.
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-20.0-20240410-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.

Apr 10, 2024

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

2. Whatever LineageOS changed since Mar 5th build. About 6,400 files needed to be recompiled.
[Galaxy Tab S2 Android Development] Sunport:
Updatind previous version by TWRP is OK! Thank you 🍻
[Galaxy Tab S2 Android Development] Alex7779:
Clean installed 20240410, works great! Thank you!
[Galaxy Tab S2 Android Development] fredmo:
@retiredtab could you please take a look at the issue of build?

build instruction · Issue #1 · retiredtab/LineageOS-build-manifests

Based on your comment Q1. Where are the source and kernel source files? A1. The kernel source files are at https://github.com/syphyr/android_kernel_samsung_msm8976/tree/lineage-16.0 The device tree...

github.com
[Galaxy Tab S2 Android Development] retiredtab:
I don't know why you are even asking me this question because you're following ChatGPT's instructions instead of the one I provided. If you want to use ChatGPT to build this, then ask ChatGPT to solve it.

I provided instructions for building LineageOS and ONLY LineageOS.
[Galaxy Tab S2 Android Development] Alex7779:
@retiredtab

Sorry if this question is a bit off topic, but I just thought about Midi 2.0 again. If an upstreamed kernel is unlikely to work, what about backporting Midi 2.0 to the 3.10 kernel?

I am thinking about giving this a try.

It would be great if just backporting the USB gadget driver would be enough.

But I fear there will be lot of modifications needed.

github.com

linux/drivers/usb/gadget/function at master · torvalds/linux

Linux kernel source tree. Contribute to torvalds/linux development by creating an account on GitHub.

github.com

Just a shot in the dark.

Anyways I am happy with the ROM!
[Galaxy Tab S2 Android Development] retiredtab:
All my github code is open source which means anyone can take it, modify it, and do whatever they want to meet their requirements. See FAQ #1.

So if you want to try incorporating Midi 2.0 from Linux 6.x down to 3.10, kernel, go ahead. Just be aware that it's likely going to require a LOT of modifications, merge conflicts, manual intervention, understanding of C, make, etc.

If you can get it compile without errors, there's still no guarantee that Midi 2.0 will work, is stable and reliable and that you didn't break any other usb functionality like charging, mtp, adbd, etc.
[Galaxy Tab S2 Android Development] fredmo:
But I scripted also your comment of the : https://github.com/retiredtab/Linea.../20/msm8976/20-msm8976-build-instructions.txt
[Galaxy Tab S2 Android Development] rhcohen:
Hey, I am wondering if anyone using this ROM has gotten Nearby Share to work. When I attempt to use the "Nearby share" option to send a file to another Android device, I get the message "Nearby Share is now Quick Share, Update to Quick Share to continue sharing with nearby Android devices..." but when I click on "Update" nothing happens. From a bit of web searching I've found that this is because the device is recognized as Samsung and so looks for Samsung's version of Quick Share, but the Samsung Play Store is not installed; but I've also read that the Samsung version of Quick Share doesn't run on LOS. So it seems I need to find the APK for generic non-Samsung Quick Share. Does anyone know where to find that, or have another workaround? Thanks.
[Galaxy Tab S2 Android Development] Alex7779:
Just checked, yes nearby share doesn't work, but send to devices does.
[Galaxy Tab S2 Android Development] lineagefan123:
I'd really like to try this build, but...

I use Lineage OS for 10 years on several devices.

On my SM T813 I use the advised TWRP, erase flash as proposed. But I end up in a boot loop. When I go back to the official lineage 16 it works again.

I had the same problem with ripee's unofficial builds, only once it has worked with some kind of dirty flashing I remember.

Could it be because I have initially used Odin as flash tool? Or maybe some drivers are missing and I should go back to stock ROM first?
[Galaxy Tab S2 Android Development] lineagefan123:
OK I've solved it: I went back to stock ROM and then clean-flashed and it works :-)

I think I've once read that some drivers have to be available from stock ROM to make the custom ROM work
[Galaxy Tab S2 Android Development] Sunport:
Someone check please WiFi access point
[Galaxy Tab S2 Android Development] moloko01:
You have to wait a while and reboot. I now have Quick Share and it works. You have to set visibility to 'all'.
[Galaxy Tab S2 Android Development] rhcohen:
@moloko01 , can you provide more details? This is on your SM-T813? When I click on "update", even if I wait half an hour, then reboot, I still do not have Quick Share. This is in contrast to when I get the same message and click "update" on another Samsung tablet that is on stock ROM, where the Samsung store opens up and invites me to update. But there is no Samsung store on LOS (and my understanding is that Samsung's version of Quickshare requires OneUI, which we don't have on LOS). So -- you must have managed to fool Google in thinking your T813 is not a Samsung device. How did you manage that?
[Galaxy Tab S2 Android Development] Sunport:
I think this is depending of what ggaps you install, maybe try another? I not install it and no near share function at all.

Guys check WiFi access point working OK?
[Galaxy Tab S2 Android Development] moloko01:
I don't have Samsung Store on my SM-T813 (LOS20). This don't works in LOS. But I have installed Google Apps (Mind the gapps). Maybe this makes the different. This also works on our SM-T713 (LOS20) and SM-T720 (LOS21).
[Galaxy Tab S2 Android Development] rhcohen:
Hmmm. I also have MindTheGapps installed. I thought maybe an update to MindTheGapps would help, but I just checked and found that the latest version for Android 13 is still the one I have installed, MindTheGapps-13.0.0-arm64-20231025_200931. Is yours the same version? Or maybe it somehow depends on what Google server you access. So, you did nothing other than click on the "update" button? Did you get some kind of notification that an update was actually in progress? I also thought that updating LOS (20) to the latest (April) release might help, but it did not.
[Galaxy Tab S2 Android Development] moloko01:
It is not importend witch version of Gaps you have installed. It will be updated with Google Play.

I klicked on update and after e while Quick Share was there.
[Galaxy Tab S2 Android Development] potsieanz:
Been using this for a couple of days on my T813 and it is fantastic thanks. Faster and more modern feel than OS16 which I was using, plus getting security updates again.

Bitwarden is slow to respond to commands, but others are great.

Thanks again
[Galaxy Tab S2 Android Development] Sunport:
Already using couple of months - working like a charm, very happy and thank you very much ❤️ 👍🍻
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-20.0-20240516-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.

May 16, 2024

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

2. Whatever LineageOS changed since Apr 5th build. About 8,700 files needed to be recompiled.
[Galaxy Tab S2 Android Development] Sunport:
Updated by TWRP successful and Magisk automatically reinstall too.

Someone please check WiFi Hotspot - other device try connect but can't obtain IP address.

Just curious this is because dirty update or not.

Any way this function absolutely not necessarily so thank you very much for keep alive my lovely device software updated ♥️♥️🍻🍻
[Galaxy Tab S2 Android Development] yoshkapundrick:
I screwed up something.

Upon reboot I get "Factory Data Reset" "Restarting".

Can someone explain how I screwed up?
[Galaxy Tab S2 Android Development] yoshkapundrick:
Solved by installing 20 on top of a clean 18.
[Galaxy Tab S2 Android Development] Reynald0:
It seems that in the latest build when we enable GPS, and we get satellite data, the tablet reboots, I saw we get satellites. I can't reproduce the same reboot on t810 where it works fine tho.
[Galaxy Tab S2 Android Development] retiredtab:
I test GPS on every single build because it's stated as working in post #1. The reason I test it, even though I don't use it myself, is because it's been broken since 17.1 so as a courtesy to the community, I check it with all my builds BEFORE uploading it to the public.

I've enabled gps now for almost 2 hours and letting it run 2 gpstest programs + Waze

https://f-droid.org/en/packages/com.android.gpstest.osmdroid/

https://play.google.com/store/apps/details?id=com.chartcross.gpstest&hl=en&gl=US

https://play.google.com/store/search?q=waze&c=apps&hl=en&gl=US

and all 3 above work fine and give correct gps location. There's no crash or reboots. I've also toggled on/off the gps multiple times and still all 3 programs work with no problems.

As you also probably know, even though the T813 and T810 have similar specs, the former runs msm8976 and the latter run exynos5433. Thus they come with completely different gps drivers and the former requires the presence of pm-service which I had to kang from another device back in Feb 24, 2023. See

https://github.com/retiredtab/propr...mmit/626e38a95e3eecc41a5d1e4b0d03359a264e3ec2

I suggest do the following.

1. Backup your data.

2. Do a clean install (wipe everything in TWRP and FORMAT YOUR DATA -> answer yes).

3. Boot the clean OS and only enable GPS. Then download and install the GPStest program from f-droid in the URL given above.

4. It should work and show your location with crashing or rebooting.

5. If yes, then restore your data and programs.

6. If you can reliably reproduce the tablet rebooting, then get an adb logcat following the steps EXACTLY in FAQ #9.

EDIT: I'm running the May 16 build. I eat my own cooking.
[Galaxy Tab S2 Android Development] Reynald0:
After some retries it worked with GMapsWV.

It could also be some race condition caused by this specific app called GMapsWV: https://f-droid.org/en/packages/us.spotco.maps

I used the DivestOS repo one, they are different size from F-Droid and DivestOS repo.

I see a lot of stuff happening both releated to Adreno, BPF, and so on in the adb logcat, also some reflections error.

The app I used at first to get the GPS data worked properly the first time: https://f-droid.org/en/packages/com.mirfatif.mylocation/

Thank you for your support, I tend to think what happened was caused by the app I used, and is not releated to the rom itself, I apologize, and I catch the occasion to wish you a happy weekend.

The next time it will happen I will try to reproduce it from a clean install, regards.
[Galaxy Tab S2 Android Development] lojelo:
Since my T810 died yesterday (many thanks to retiredtab for the years of service you provided for my device.

I have dug the wife's old T813 out and just installed the latest build.

I have never seen this before on boot but having a look about on the net it seems a normal thing I'm talking about the message that pops up top left on boot up. I take it that this is nothing to worry about.

set warranty bit :kermal

Though I have had a shutdown of this device bit like the same problem I was having with the T810 before it died.

Thanks
[Galaxy Tab S2 Android Development] retiredtab:
That is normal.
[Galaxy Tab S2 Android Development] fredmo:
Hello,

Would you have an idea why the generation of the zip image file is failing on this missing file ? and howto fix it?

FileNotFoundError: [Errno 2] No such file or directory: 'out/target/product/gts210vewifi/obj/PACKAGING/target_files_intermediates/lineage_gts210vewifi-target_files-eng.me/SYSTEM/vendor/vendor/etc/recovery.img'

build instruction · Issue #1 · retiredtab/LineageOS-build-manifests

Based on your comment Q1. Where are the source and kernel source files? A1. The kernel source files are at https://github.com/syphyr/android_kernel_samsung_msm8976/tree/lineage-16.0 The device tree...

github.com
[Galaxy Tab S2 Android Development] Alex7779:
Slightly off topic but is it possible to get HD audio apt-x or LDAC Bluetooth audio on this ROM? Can't find a working magisk module for it. Thanks

Edit: Ok, I got AAC to work, I think apt-x is not supported by my headphones
[Galaxy Tab S2 Android Development] retiredtab:
See

https://xdaforums.com/t/lineageos-1...85-gtanotexllte.4432957/page-72#post-89525959
[Galaxy Tab S2 Android Development] retiredtab:
In 18.1, I added the aptX libraries via

https://github.com/retiredtab/propr...mmit/3f6bd0d979ae25e3ba23e2c214fa7207c81f6b32

but for 20, aptX supposed to be included in AOSP Android 13 QPR2 starting Nov 2023 as per

https://review.lineageos.org/c/LineageOS/android_device_sony_nile-common/+/372258

So, in theory, it's built in, but I have no means of testing it.
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-20.0-20240623-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.

Jun 23, 2024

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

2. Whatever LineageOS changed since May 5th build. About 22,000 files needed to be recompiled.
[Galaxy Tab S2 Android Development] retiredtab:
I see no such wording in the updater section. I've even checked the 3 dot menu and refreshed. My roms don't and never will support OTA as per FAQ #22.

Edit: In addition, my T813 boots to TWRP for my recovery option as expected.
[Galaxy Tab S2 Android Development] Reynald0:
Edit: it was a battery problem, not releated to the rom. Happening also with the stock rom.
[Galaxy Tab S2 Android Development] retiredtab:
I have now released an ALPHA version of LineageOS 21 for T813. See

https://xdaforums.com/t/unofficial-rom-alpha-lineageos-21-for-sm-t813-jul-9-2024.4681948/

As such, I will ONLY build LineageOS 20 on even numbered months. So next 20 builds will be Aug, Oct and Dec 2024. I have not yet decided on the build frequency for 2025.
[Huawei Mate 10  Questions & Answers] Xenon-X:
I have Huawei mate 10 ALP-L29C636E2R1P12 running EMUI 9.1 when I check the update it's showing me you are upto date. And the cust is C636 I am in Africa how can I force update it to EMUI 12 View attachment 5942373
[General Questions and Answers] GoldenStarGamer:
I have a Samsung Galaxy A13, wich contains a Gyroscope, but it is not supported by ARCore.

I wanted to use AR apps but it blocks me.

I have researched and found arcore-patch but it doesn't have an option for my phone.

I also saw this post but i am afraid it might be virus.

How can i install ARCore support on my phone and install AR apps from google play without rooting?

I posted it here because there isn't a forum for my device.
[General Questions and Answers] xXx yYy:
The mentined phone basically supports AR. Do you have installed on phone Google Play Services for AR ( formerly ARCore ) - latest release dates 2023-06-28 - what is required to run AR apps?

My recommendation: Ask ARCore developer community for assistance.
[General Questions and Answers] GoldenStarGamer:
My device is not in the list for supported phones but has the hardware capabilities to run arcore
[General Questions and Answers] xXx yYy:
You're right: the Samsung A13 5G is supported, but not yours.
[General Questions and Answers] declandude25:
i have the same issue, i have an up to date samsung galaxy A13 4g device, but i cannot install the app "google play services for AR" (my phone is capable of running) with red text saying my device isnt compatible.
[Samsung Galaxy S23 Ultra] Aleks95:
Hey guys hope you all are doing well,

i was just wondering if im doing something wrong or is it the night mode bug im reading all over the news over the news.

So when there is a singe light source like on these pictures im getting some weird artifacts or idk how to call it around the picture, on normal light conditions they dont exist or in low light. They just show up in ultra low light.

For clarification im on the june update
[Samsung Galaxy S23 Ultra] NXUS:
Same thing in my very low light pictures but do not have comparison pictures from before the update.
[Samsung Galaxy S23 Ultra] Aleks95:
you helped me remember that i have a picture from the exact same object before the update, looking at the picture its super dark. So i think maybe its a limitation of the camera, because samsung is brightening the picture to 11
[Touch 3G General] fenikso:
When playing music I often get small breaks during MP3 playback. Half a second of silence or something like that at random times about 5 minutes apart.

It does not matter what player software I use. This problem is also very common among the HTC Diamond users http://xdaforums.com/showthread.php?t=412065 .

Do you have the same problem? I bet you do :( .
[Touch 3G General] mordecai83:
strange, ive been using my phone everyday as an mp3 player and i havent heard it skip even once.

Does it lag with every song, or are there specific songs where it lags. Are there any that absolutely never lag? Also what kind of headset do you use for listening?

edit> Also, what ROM are you using?