yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Android Development] lojelo:
Well I spent nearly 3 hours last night trying to get into download mode, got up this morning after leaving tablet turned off and it worried 1s time flashed twrp with Odin and Magisk with twrp and everything is now back to normal twrp is now my recovery option again.

Yes adb also worked as well.

Still have the backup problem though not had time to do a fresh clean install to see if it actually gives you the option not to install it.
[Galaxy Tab S2 Android Development] lpedia:
Good to hear you got it working!

You do not get an option not to install SeedVault after a clean install. It's there, whatever you do. But it might not pester you after a clean install. It will be interesting to hear what happens if you do start afresh again.
[Galaxy Tab S2 Android Development] lojelo:
I have done a clean install I put the password in for speedvault sent backup to SD card thats not sending any annoying notifications anymore.

Though WiFi is terrible again only getting 90mb Max on 1gb connection.
[Galaxy Tab S2 Android Development] retiredtab:
A "clean" install to me includes format data in TWRP. If you don't format data, strange things can happen.

I made no changes to the device tree as written in the Oct 9 release notes. While I can't test up to 400Mbps, the adb logcat shows argosd is up and running. See

$ adb logcat -C | grep argo
10-13 10:41:48.800 0 0 I [c6] argos_probe: Start probe
10-13 10:41:48.800 0 0 I [c6] argos_probe: parse dt done
10-13 10:41:52.416 0 0 I [c4] sec_argos_register_notifier: sec_argos_l1ss_notifier(dev_num:4)
10-13 10:41:52.416 0 0 I [c4] sec_argos_register_notifier: sec_argos_l1ss_notifier(dev_num:2)
10-13 10:41:52.497 0 0 E : [c5] argos_irq_affinity_setup dev_num:-1 should be dev_num:0 ~ 6 in boundary
10-13 10:41:57.060 0 0 I [c7] init: starting service 'argos-daemon'...
10-13 10:47:23.484 0 0 I [c3] argos_pm_qos_notify: name:WIFI, speed:74Mbps, prev level:-1, request level:0
10-13 10:47:23.484 0 0 I : [c3] argos_freq_lock name:WIFI, CPU_MIN=0, CPU_MAX=0, KFC_MIN=0, KFC_MAX=0, MIF=0, INT=0
10-13 10:47:23.484 0 0 I [c3] argos_irq_affinity_apply: irq277 affinity to cpu_mask:0xF
10-13 10:47:23.484 0 0 I [c3] argos_pm_qos_notify: name:WIFI TX, speed:74Mbps, prev level:-1, request level:0
10-13 10:47:23.485 0 0 I : [c3] argos_freq_lock name:WIFI TX, CPU_MIN=1200000, CPU_MAX=0, KFC_MIN=1000000, KFC_MAX=0, MIF=0, INT=0
10-13 10:47:23.485 0 0 I [c3] argos_pm_qos_notify: name:WIFI RX, speed:74Mbps, prev level:-1, request level:0
10-13 10:47:23.485 0 0 I : [c3] argos_freq_lock name:WIFI RX, CPU_MIN=1000000, CPU_MAX=0, KFC_MIN=800000, KFC_MAX=0, MIF=0, INT=200000
10-13 10:47:25.489 0 0 I [c2] argos_pm_qos_notify: name:WIFI, speed:100Mbps, prev level:0, request level:1
10-13 10:47:25.489 0 0 I : [c2] argos_freq_lock name:WIFI, CPU_MIN=0, CPU_MAX=0, KFC_MIN=0, KFC_MAX=0, MIF=0, INT=0
10-13 10:47:25.489 0 0 I [c2] argos_irq_affinity_apply: irq277 affinity to cpu_mask:0xF
10-13 10:47:25.489 0 0 I [c2] argos_pm_qos_notify: name:WIFI TX, speed:100Mbps, prev level:0, request level:1
10-13 10:47:25.489 0 0 I : [c2] argos_freq_lock name:WIFI TX, CPU_MIN=1500000, CPU_MAX=0, KFC_MIN=1200000, KFC_MAX=0, MIF=0, INT=200000
10-13 10:47:25.489 0 0 I [c2] argos_hmpboost_apply: hmp boost enable [5]
10-13 10:47:25.489 0 0 I [c2] argos_pm_qos_notify: name:WIFI RX, speed:100Mbps, prev level:0, request level:1
10-13 10:47:25.489 0 0 I : [c2] argos_freq_lock name:WIFI RX, CPU_MIN=1200000, CPU_MAX=0, KFC_MIN=1000000, KFC_MAX=0, MIF=0, INT=200000
10-13 10:47:25.489 0 0 I [c2] argos_hmpboost_apply: hmp boost enable [6]
10-13 10:47:27.491 0 0 I [c6] argos_pm_qos_notify: name:WIFI RX, speed:128Mbps, prev level:1, request level:2
10-13 10:47:27.491 0 0 I : [c6] argos_freq_lock name:WIFI RX, CPU_MIN=1500000, CPU_MAX=0, KFC_MIN=1000000, KFC_MAX=0, MIF=0, INT=200000
10-13 10:47:29.492 0 0 I [c6] argos_pm_qos_notify: name:WIFI, speed:94Mbps, prev level:1, request level:0
10-13 10:47:29.492 0 0 I : [c6] argos_freq_lock name:WIFI, CPU_MIN=0, CPU_MAX=0, KFC_MIN=0, KFC_MAX=0, MIF=0, INT=0

I went to fast.com and I got 120Mbps which matches +/-5% what the adb logcat reports of 128Mbps.
[Galaxy Tab S2 Android Development] lojelo:
Yep a full format was done.

I've just sorted it mate it was the router, the wife just told me our internet was down earlier today and every time this crappy virginmedia router reboots it keeps turning on channel optimisation which makes my WiFi worse.

I have disabled it and all is OK again, so it wasn't a ROM problem it was on my side.
[Galaxy Tab S2 Android Development] lpedia:
So ... it was not the clean install that stopped it from nagging, but giving it the 12-word encryption key and somewhere to store the backup. The nagging about 'failed' backup was because it couldn't actually DO a backup until it'd been configured. 😉

There seems to be no way to tell it that you don't want it to do backups. 🙁
[Galaxy Tab S2 Android Development] lojelo:
@ lpedia When I 1st installed version 19.1 I upgraded from 18.1 I didn't do a clean install thought I explained this in my 1st post in this topic but looking back I didn't. I used the 12 word encryption key 1st time around I only had 2 options for backup 1 was some online back option the other was choose location but now I have more options!! I sent the backup to the sd card but every time I rebooted the device it kept sending me notifications saying failed backups it was annoying.

What I have noticed now after a clean install is, it is now giving me more locations to backup to, speedvault is working and backing up to the sd card fine but I can also now use one drive I didn't have this option last time I have no idea why this is working ok now I am just happy those notifications have stopped and it's working fine.
[Galaxy Tab S2 Android Development] lpedia:
Very strange! But good to hear that it's working now!
[Galaxy Tab S2 Android Development] tonyo07:
I want other rom i dont like lineage os anymore is waste time test it
[Galaxy Tab S2 Android Development] bmwdroid:
So go on and build one.

I'm willing to test it.
[Galaxy Tab S2 Android Development] zero_ap:
I have something weird going on with my tab s2, the initial release of 19.1 (20220809) works perfectly including functioning gapps. dirty flashed the first update (220911) on its release, it was good and gapps survived the update and again works flawlessly.

The newest release (20221009) i dirty flashed it and for some reason broke the internet connectivity and all gapps stopped working.

The wifi says its connected but NO internet, ive rebooted the router, rebooted tablet etc. i know my net is working since all my other devices connects to the net just fine.

So i clean installed 20221009 without any GAPPS (full wipe & format) and the wifi still just sits there connected but no internet, even after rebooting it and the router again.

So i did full wipe and clean installed the previous build 220911 and wifi WITH internet is back but i cant get any gapps (nikgapps) working, the zip flashes succesfully but play store is missing. I tried flamegapps it returned an error stating the device is ARM and not ARM64
[Galaxy Tab S2 Android Development] bmwdroid:
@zero_ap I've flashed mine dirty again over the as well dirty flashed September version.

Every thing is working as before.

Btw NikGapps64 work on mine.
[Galaxy Tab S2 Android Development] retiredtab:
I don't use any gapps so please direct your gapps questions to the gapps project or use this

https://xdaforums.com/t/exynos5433-...on-for-19-1-roms-sm-t710-and-sm-t810.4480041/

where others can help you with gapps.

As for Oct 9, 2022 build, I just did a format data, wipe everything and I have no problems getting wifi on 2.4Ghz. I then booted into TWRP formatted data, wiped everything again and went through setup again with wifi on 5Ghz and it worked fine.

As a reminder, I personally test each build wrt to post #1 what works before uploading. If there was a problem with wifi, I definitely would have noticed because I stream video from newpipe to audio over bluetooth which tests multiple things at one time.

There are problems with S2 devices working with pure WPA3 networks and if you have hybrid WPA2/WPA3, it can work if you make "802.11w Management Frame Protection" optional. I'm running openwrt which allows for this parameter.

In addition, as I mentioned in post #42, I have made no changes to the wifi code and even have an adb logcat showing it works. I have not touched any wifi code since Aug 2021.

Since the public ALPHA began on Aug 9, 2002, I have only made one change to the device tree code and that was removing the menu option for fast charging. All other code changes are made by LineageOS/Google AOSP + monthly security patches.
[Galaxy Tab S2 Android Development] wikakasa:
that is an great rom! wating for full version or at least beta now (:

also for people that it boot loops : first install some android 10 rom and then upgrade to this rom without formatting data. worked for me i guess
[Galaxy Tab S2 Android Development] bmwdroid:
afaik none can be left when doing "format data" after wiping.

System partition will be overwritten anyhow.

On a SD card you should delete in TWRP the folder "Android".

Can't help with the other questions as I either don't do what you're doing or have no need for that.
[Galaxy Tab S2 Android Development] lpedia:
Thank you for the very detailed review!

It's always a good idea to give a brief list of your setup up front, such as

what ROM you had before this one

how you installed this ROM - in particular, did you Format Data, and are you using the recommended version of TWRP?

what addons you installed, if any - gapps, Magisk, etc

what accessories you're trying to use with it (eg Samsung Tab S2 Keyboard Cover)

etc

Make sure to read the FAQ for this thread, https://xdaforums.com/t/unofficial-...-for-sm-t810-oct-9-2022.4480033/post-87283709.

If you're having problems such as apps or system crashing or BT devices not connecting, always try to get a logcat when the problem occurs, and upload it to this thread when reporting the issue.

Note Q18 of the FAQ: this ROM is kept as close as possible to pure LineageOS. It doesn't have any Samsung-specific additions, and the default apps and settings are whatever comes with LOS.

About cleaning out stock ROM remnants: if you formatted data, there should not be any such remnants. No need to root the device. But if you didn't do that, some or all of your problems might be caused or exacerbated by such remnants.

About the issues with the kb+touchpad in the Samsung Tab S2 Keyboard Cover: apart from possible interference from data partition remnants, it's possible that not all of its functions are available or work properly without some Samsung-specific code that the stock ROM would have had, but LOS does not.

About your suggestion of including a notepad-like text editor: LOS doesn't include one. But you can always install apps via TWRP after flashing the ROM and before first boot. I often add F-Droid that way to a clean install if I'm not installing gapps, for example.

About an alternative to Bromite: one unGoogled privacy-oriented Chromium browser I'm aware of is Brave.
[Galaxy Tab S2 Android Development] retiredtab:
The 18.1 and 19.1 roms that are based on my repos all use "stock" LineageOS bluetooth code. Bluetooth and bluetooth audio are both tested on my builds to a bluetooth usb adapter running on my Lubuntu 20.04 computer. I stream audio over it and it works fine.

I'm currently building the 19.1 Nov 5th security patches and it will take at least 2-3 hours before it's done, but there are 2 bluetooth related changes wrt to the Nov 5th patches as per

https://review.lineageos.org/q/topic:S_asb_2022-11

Other than that, I have made no device tree bluetooth code changes since Aug 11, 2021. I know we have people using bluetooth with a variety of devices.

You can try the Nov 5th build once I have verified all the functionality in post #1 (like I always do). If it doesn't pair with your m535, try a different bluetooth mouse because there's nothing I can do with the bluetooth code.

The announcement for the Nov 5th patches will be after this post.

I tried Bromite 106.0.5249.163 and there's no crash for me.

I don't have any gaming controllers so I cannot verify.

I don't have Samsung physical keyboard to test or verify. The functionality above may require proprietary software or drivers in order to work and won't be included LineageOS.

Already documented in post #1. I will not be spending any time fixing this as there's other priorities.

That's probably a config.xml file somewhere in LineageOS to display that. If I can easily find that setting, I can put it into the code, but otherwise I won't spend hours or days looking for it.

LineageOS doesn't include one and you can always add one yourself.

The above is a LineageOS app and there's nothing I can do. You can always disable it and download another.

See settings, system, buttons, backlight.

I test all my builds for deep sleep. Every public build I've uploaded does deep sleep properly. Download devcheck by flar2 and you can verify for yourself.

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

I downloaded Bromite from github and 106.0.5249.163 is the latest there is. So I suggest that message is false. Personally, I use Brave on desktop + Android. Brave is based on open source chromium and comes with built in ad block + privacy features.

Every build based on my repo has been SELinux enforcing since day 1. The other builds were/are not my work.

If you came from stock, you MUST as per FAQ FORMAT DATA in TWRP.

As a side note, people who report boot loops in any of my roms simply are NOT READING/FOLLOWING instructions to FORMAT DATA in TWRP. I simply ignore all posts that say my roms boot loop because I personally test each one before uploading.

I see complaints daily/regularly re boot loops on other roms/devices and it simply comes down to people not following or reading the instructions.

As lpedia wrote, you can get a logcat (also in the FAQ), but there's no guarantee that it will show anything or that I can fix the problem.

Thanks for your feedback.
[Galaxy Tab S2 Android Development] retiredtab:
Regarding the bluetooth pairing, there's one possibility that I thought of, after I hit post button, and it maybe SELinux related? The rules for it might need to be modified to allow more bluetooth functionality.

With the Oct or Nov build, it really doesn't matter, try this.

# connect device to PC, make sure adb debugging is enabled
adb root
adb shell
# temporarily turn off SELinux enforcing
setenforce 0
# Verify it's permissive mode by getenforce
getenforce
# now try all your various bluetooth device pairing that didn't work
# if they work now, let me know and I will send further instructions for you to gather the correct logs.
# if they don't pair, then it's NOT SELinux related.
# reboot OS once you are done
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-19.1-20221110-UNOFFICIAL-gts210wifi.zip

Package Complete: out/target/product/gts210wifi/lineage-19.1-20221110-UNOFFICIAL-gts210wifi.zip
#### build completed successfully (02:29:57 (hh:mm:ss)) ####

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.

19.1 has been my daily driver since July 2022.

Nov 10 , 2022 release notes

1. YOU MUST read posts 1-4 if you haven't already.

2. Nov 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-11

3. Whatever LineageOS changed since Oct 5th patches (about 10,000 files had to be recompiled).
[Galaxy Tab S2 Android Development] lpedia:
The LOS built-in (AOSP) Calendar does require at least one account to sync with.

A good alternative, if you don't want to have any cloud accounts, is an app called Etar - Open Source Calendar. It's an enhanced version of the AOSP Calendar. One of the enhancements is the option to add a local calendar, thereby not have to link any accounts to the app. Available from F-Droid: https://f-droid.org/en/packages/ws.xsoh.etar/
[Galaxy Tab S2 Android Development] TabWrecked:
Sorry I couldn't figure out how to use logcat properly on android without adb as I'm not a programmer, here's what I did:

-Installed Termux from f-droid and installed logcat on it.

-Gave Termux writing permissions and typed logcat > /sdcard/logcat.txt

-Pressed pair button on bt mouse > bt restarted even without pairing > clicked on pair when it appered > bt restarted again without pairing

-Pressed Ctrl+C in termux to stop logcat (what's the proper way?)

I didn't know which level of filter to log so I left at default, sorry for the spaghetti.

EDIT: The log was useless without root permissions so I deleted it, new log coming in a new post.
[Galaxy Tab S2 Android Development] lpedia:
About taking logcats without using adb: there are Android apps that read and save Android logs. One example is LogCat Reader. I haven't used it myself, but it sounds like it'd do the job well.

The default logcat output should be fine - and control-C is the only way I know of to quit the logcat command when you're running it in a terminal app or via adb.
[Galaxy Tab S2 Android Development] TabWrecked:
Thank you Ipedia for your suggestions, I got the LogCat Reader and it immediately asked for root permissions so I went ahead and got Magisk installed.

edit: log was removed because it wasn't useful
[Galaxy Tab S2 Android Development] TabWrecked:
Is there a way to temporarily turn off SELinux on my rooted tablet without a PC?
[Galaxy Tab S2 Android Development] lpedia:
adb root is switching the adbd service on the device to root mode, and adb shell is invoking the device's own shell and running the shell as root, having switched adbd to root mode.

The same can be achieved on the device itself with Termux, as long as the device has been rooted and Termux can therefore run as root.

Run Termux, make sure it's in root mode (# prompt - run su if necessary), and execute the setenforce and getenforce commands. Use this approach wherever instructions begin with adb root and adb shell. 🙂

TL;DR: For those with a PC, adb can provide root access to the device without having to actually root it. LOS (and Android generally) has an adbd service that runs on startup if "USB debugging" has been enabled in Settings > System > Developer options > Debugging. adb on the PC can tell adbd on the device to switch to root mode if "Rooted debugging" is enabled in the same Developer options section. From then until next boot, adb commands will run as root on the device.

But adbd running as root does not authorise apps like Termux to switch to root. You need a rooted device for that.
[Galaxy Tab S2 Android Development] IvkovicD:
Hi all, got focus on this T810 version last Friday and applied it alreay to my device. Most stuff is runnign well, except some Bluetooth issues.

I cannot pair a specific bluetooth keyboard to it (see also some other BT topics in this thread before) ,. Keyboard worked in old Android V10 version with T810 before - also a custom rom.

I can pair another two bluetooth keyboars ("lofree, 1percent" and "1byone") and a cheap bluetooth mouse. But my main keyboard simply does not pair. It Is a "Doraby Wireless keyboard "- say simply "a nameless one", but it works very good). Anyway, I have fetched some logs from pairing process. It looks like the bluetooth stack process dies with a FATAL after initially having found new device successfully, and when I press "approve for pairing", it is gone showing a disabled bluetooh (obviously).

Maybe the log file helps hereby. As keyboard is workig well with a Samsung Galaxy S9 Android V12.1, the V10 before on the TAB S2 and with Windows 10, and I can pair other two bluetooth keyboards, I simply must assume, that sth weird at the bluetooth stack between both devices (T810 and keyboard) got the stack dying.

Hope, logs help to analyze issue.

Regards & Thanks,

Dejan
[Galaxy Tab S2 Android Development] IvkovicD:
won't help with BT issue, I did the test already with switched off SELinux....
[Galaxy Tab S2 Android Development] retiredtab:
There's no logs attached. Please zip them and re-attach again.
[Galaxy Tab S2 Android Development] IvkovicD:
yes, u're right. somehow it got lost...
[Galaxy Tab S2 Android Development] retiredtab:
Let's try a permissive kernel first. This will disable SELinux at boot. While setenforce 0 does disable SELinux, it does it after the OS is booted. This might make a difference with some bluetooth devices?

1. download boot-permissive.img onto T810

$ sha256sum boot-permissive.img
00f5beda2da7f906388766c0365a93d186dc197d95b93af23552bb383ec85814 boot-permissive.img

2. boot into TWRP

3. click install

4. touch install image

5. choose boot-permissive.img (from where ever you downloaded it to)

6. select boot (when prompted for select partition to flash image)

7. swipe to confirm flash

8. reboot system

9. after OS boots, choose settings, privacy, trust and verify that SELinux is disabled.

10. Now retry pairing the problematic devices (take adb logcat at same time)
[Galaxy Tab S2 Android Development] TabWrecked:
Confirmed it disabled SELinux, however the bluetooth connection to certain devices (like the mouse i have) still crashes the bluetooth (disables and re-enables bluetooth upon failing to recognize or pair the device).

Unfortunately I have to give up for now and try some older versions, good luck with the progress.
[Galaxy Tab S2 Android Development] TabWrecked:
I just tested both of the LineageOS 18.1 (alpha by ripee and beta by retiretab). Bluetooth mouse connects properly on both of these. Perhaps you could find some leads by comparing them.

Sorry if it's unrelated but, while trying to log and disable selinux I had to root my device using magisk in my previous install. However I don't want root or any addons anymore. Do I need to perform any extra operation to unroot my device or wiping/formatting before installing LineageOS 18.1 already cleaned everything?

Thank you retiretab and Ipedia for your time and efforts.
[Galaxy Tab S2 Android Development] lpedia:
Clean flashing any ROM (including Format Data) will have removed Magisk and any other addons - so no, you shouldn't need to do anything else to get yourself a nice clean unmodified ROM. 🙂
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-19.1-20221209-UNOFFICIAL-gts210wifi.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.

19.1 has been my daily driver since July 2022.

Dec 9 , 2022 release notes

1. YOU MUST read posts 1-4 if you haven't already.

2. Dec 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-12

3. Whatever LineageOS changed since Nov 5th patches (about 6,100 files had to be recompiled).
[Galaxy Tab S2 Android Development] bmwdroid:
@retiredtab thx again very much.

Flashed it today not wiping anything before.

On mine that worked fine.

If I find anything worth reporting I will do that.
[Galaxy Tab S2 Android Development] cndv:
Hi

I don't know if anyone has written about this but this system overwrites twrp (I install twrp then of course enter it and it works but when I turn the tablet off and on twrp is missing /I tried several versions but the same thing /on 18.1 there was no such problem)

the tablet is tab s2 810
[Galaxy Tab S2 Android Development] bmwdroid:
sorry but I strongly disagree.

My TWRP 3.7.0-9_0 stayed like it was before.

you probably have activated "update recovery when updating system".