[UNOFFICIAL][ROM]ALPHA LineageOS 19.1 for SM-T810 - Mar 18, 2024

[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.

 

[lpedia]

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.
Good luck with it.

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.

 

[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

 

[TabWrecked]

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

Is there a way to temporarily turn off SELinux on my rooted tablet without a PC?

 

[lpedia]

Is there a way to temporarily turn off SELinux on my rooted tablet without a PC?

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.

 

[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

 

[IvkovicD]

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.

won't help with BT issue, I did the test already with switched off SELinux....

 

[retiredtab]

Hope, logs help to analyze issue.

There's no logs attached. Please zip them and re-attach again.

 

[IvkovicD]

There's no logs attached. Please zip them and re-attach again.

yes, u're right. somehow it got lost...

 

[retiredtab]

yes, u're right. somehow it got lost...

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)

 

[TabWrecked]

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)

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.

 

[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.

 

[lpedia]

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?

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.

 

[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).

 

[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.

 

[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

 

[bmwdroid]

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

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".

 

[cndv]

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".

I installed 19.1 a month ago/ yesterday i updated and when i tried to update i just noticed there was no twrp installed so i updated it from system 19.1 by pressing side keys because unfortunately touch can't do it, something is not calibrated properly / after that update i uploaded twrp and opened it before booting and clicked restart recovery and then reopened twrp next step was to restart system in twrp and then from system i clicked restart recovery but unfortunately twrp is missing (few versions of twrp i checked and always the same / i didn't upload system but only twrp so i couldn't click system recovery when installing 19.1)


I'll try again next week to reformat everything and install twrp then upload 19.1

But I don't think it will help (it's like 19.1 has a security feature that won't let you delete the original recovery)

Unless is a switch recovery block in the system developer options But I haven't seen anything like that

 

[bmwdroid]

........
But I don't think it will help (it's like 19.1 has a security feature that won't let you delete the original recovery)......

Well mine is and always stays on TWRP.

 

[cndv]

Well mine is and always stays on TWRP.

If I have time today, I will try to upload twrp &wipe & install 19.1