yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Android Development] codiflow:
Unfortunately the app RethinkDNS (which is a VPN firewall and an internal DNS resolver with blacklist function) does not work at all with either the 19.1 ROM, nor the 18.1 ROM.

Together with a developer of RethinkDNS I found out that the DNS requests are not being handled like they should or like they are being handled in other ROMs. So all DNS requests seem to come from "Unknown" instead of a proper UID (which most likely should be 1052 which is Android DNS daemon) and therefore can not be routed correctly.

This is what the developer said about it:

I don't know if you are interested in digging deeper into this issue. If yes I kindly offer my help here.

Maybe this can also solve the issue with the not working "network transfer rate widget" in the top bar which in the 19.1 ROM always shows 0 for me. I already tried to disable and reenable it and theres also no VPN active but it still just shows 0.
[Galaxy Tab S2 Android Development] retiredtab:
I've never heard of RethinkDNS until today. Since it's on fdroid and open source with no ads, I decided to try it out. As you stated, it doesn't work on T810 18.1 or 19.1. I also tried 20 and it doesn't work either.

RethinkDNS does work in 18.1 T813 (the msm8976 version) S2 tablet.

I think the main problem is the T810's kernel is 3.10.9. The T813's kernel is 3.10.108. I also tried SM-T560NU running my 20 build with 3.10.108 kernel and RethinkDNS works fine. Despite both T813 and T560NU running 3.10.108, there's significant differences between the kernel code.

So the T810 kernel is 99 kernel revisions behind T813 and T560NU. As I mentioned before, updating the kernel 99 revisions is not an easy or trivial task. Each revision could contain hundreds of commits. Some might get merged automatically, others require error prone time consuming manual intervention.

Now, if people reading this think I'm lazy or won't try to update the kernel, let me recount an experience I ran into with building 19.1 msm8916 devices.

There's a patch that I use below

https://github.com/DerpFest-AOSP/pa...mmit/22fd53a977eeaf4e36be7bf6358ecf2c2737fa5e

so the log doesn't get spammed constantly. The "real fix" as per LineageOS developers is to fix the TCP/IP code in the kernel. Someone competent with kernel knowledge kindly made these patches available to me and I put them into the 3.10.108 msm8916 kernel when initially making 19.1. These patches are on https://review.lineageos.org and used by others.

For 3 weeks, I had problems with random reboots.

Since 19.1 was new to me at that time, I thought I was missing a commit or didn't implement something. Then I decided to start from scratch and just load nothing but the OS, no 3rd party apps. I configured just wifi and enabled airplane mode. This is a simple as you can get. 6 hours later the device, while in suspend/deep sleep mode, rebooted itself.

That's when I rolled back the TCP/IP kernel patches and all my random reboots were gone. The TCP/IP patches were a total of 11 commits.

Now imagine trying to update 99 revisions where each revision might contain 100s of commits and people should start to understand/appreciate the difficulty of this task.

Even if the T810 kernel could be updated to 3.10.108 "cleanly", there's no guarantee that it will be stable, free of memory leaks and/or random reboots, work with the existing closed source proprietary Samsung drivers.

I suggest you try another app if you need dns+firewall. Other's may work with an older kernel?

I think the above showing 0 is a side effect of FAQ 17. There's nothing I can do. The community put in a hack just to get 19.1 to bypass the eBPF requirement. Namely, this

https://github.com/retiredtab/andro...mmit/883a46487a72150a8c828c9bdca1b88ff582c65d

and

https://review.lineageos.org/c/LineageOS/android_system_bpf/+/320591

That's why a lot of older devices never "officially" made it to 19.1.

Somewhere in one my threads, someone found another app that shows network traffic, but I don't remember which rom (I build many) or what the app is called. If your search skills are A+, you can find it on xda.
[Galaxy Tab S2 Android Development] codiflow:
At first again a very BIG THANKS for answering so fast and in such a detailed manner 🥳

As 99% of my apps are from F-Droid and therefore trustfully a MITM-DNS/Firewall is not essencial for me at the moment. Just pointed that issue out here to let you and others know about this limitation.

And I hope I did not send the assumption you are "not putting enough effort into your ROM". I can imagine what it means to maintain such essential software others rely on – especially if we are talking about a mobile OS like Android. So thanks for the insights on the challenges you as a ROM maintainer are facing 😎

Big respect also for testing my issues with RethinkDNS directly. Maybe you might have found a new trustworthy app through this? I really love it since I discovered it a few months ago and for me it's a great substitute for AFWall+ / Netguard in combination with a Wireguard proxy. 🥳

Thanks also for the side note about the network traffic meter. It's not essential for me too – just thought about some correlation here 😜
[Galaxy Tab S2 Android Development] retiredtab:
I only wrote what I wrote because there's ALWAYS one person, NOT YOU, who is going to ask or wonder why the kernel can't be upgraded.

When making 19.1, it was a completely frustrating experience since I could not get it booting with any of the devices where I had successfully made 18.1.

After 3 months of frustrating troubleshooting, Kyle Harrison was kind enough to look at my logs and within 1 day, he said that the kernel's binder code was probably too old. In Android 12, Google made keystore2 a requirement.

While the msm8916 kernel code was at the "latest", 3.10.108, the binder code doesn't work with keystore2. In fact, the binder code needed a CVE patch and others to work with keystore2. Getting the correct patches took several days to figure out.

After I got 19.1 booted and running on msm8916, you would think it's an "easy" matter to take those same patches and apply them to the exynos5433 (T710, T810). Nope, I had hand edit those patches manually.

https://github.com/retiredtab/andro...mmit/83b1fca00a0cfa92fcbb57c59202024f30ab0884

Once I got 19.1 T710 running, I couldn't get 19.1 running on T810. 3 MONTHS LATER, after chasing many dead ends/rabbit holes, etc, I finally found the problem

https://github.com/retiredtab/andro...mmit/6bd444b5950c6d4e066e1fcb5fbeafa10744c527

To get 20 running for exynos5433, it took me 3 weeks of troubleshooting to come up with this patch. This was all done without adb logs which makes it 100x more difficult to troubleshoot.

https://github.com/retiredtab/Linea...lob/main/20/exynos5433/remove-MPPThread.patch

In addition, most 3.x kernels had a problem with a very long delay (several minutes) at the Samsung startup screen with LineageOS 20. This was seen on multiple Samsung phones, tablets, etc. The problem turned out to be the kernel entropy code being too old and luckily someone found a patch after weeks of troubleshooting.

As you may have guessed by now, that patch didn't work 100% with exynos5433 because our kernel is much older, so I had to go and hand edit and make modifications.

https://github.com/retiredtab/andro...mmit/66b583ecd3227f869546038eb7714dcb5ffff691

So as you can see, it takes MONTHS to figure out 1 problem. The fact that 19.1 is even running on T810 is a result of 6 months of combined troubleshooting.
[Galaxy Tab S2 Android Development] retiredtab:
I can put your tutorial in the FAQ for those interested.

BTW, I tested RethinkDNS with the 18.1 and 19.1 Sept 5th patch builds. I will upload both builds and make the announcement on xda after I go through QA with them later today.

That's why our group purposely puts only ONE ROM, one build per thread. We don't have a megathread that covers 3 versions of LineageOS for 6 devices with 2000+ posts. I read every single of them to get a handle of the problems with 17.1, but it makes way more sense to separate out the different devices and LineageOS version into their own thread.
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-19.1-20230916-UNOFFICIAL-gts210wifi.zip

NOTE: lpedia has made the build and I have been personally tested it 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 16 , 2023 release notes

1. Sept 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-09
[Galaxy Tab S2 Android Development] eduyl:
Got this rom to boot on gts210lltexx liking it rn !! i don't really use sim on my device so ..
[Galaxy Tab S2 Android Development] rybarillos:
Quick question: A few years ago Google made headlines on phasing out 32-bit ARMv7 support on Android (which is our tablet). Was there any mention that support will become obsolete starting Android 12/13?

And was the dropping of support only related to running & installing apps? Or running the OS itself?
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-19.1-20231010-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.

Oct 10 , 2023 release notes

1. Oct 6 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-10
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-19.1-20231118-UNOFFICIAL-gts210wifi.zip

NOTE: lpedia has built the rom and I have tested the build 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 18 , 2023 release notes

1. Nov 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-11
[Galaxy Tab S2 Android Development] codiflow:
I can report that updating to the latest ROM with FDE (Full disc encryption) enabled works like a charm.

Boot into TWRP => Don't decrypt data => Swipe to Allow system modification

"Advanced" => "ADB sideload" => Check both boxes => Flash new image using `adb sideload lineage-19.1-20231118-UNOFFICIAL-gts210wifi.zip`

If you want / had root: "Back" => "Advanced" => "ADB sideload" => Flash current Magisk using `adb sideload Magisk-v26.4.apk` => "Back" => "Reboot"

Thanks for your efford @retiredtab 🥳

Is there a way to donate you some money? 😉
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-19.1-20231216-UNOFFICIAL-gts210wifi.zip

NOTE: lpedia has built the rom and I have tested the build 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 16 , 2023 release notes

1. Dec 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-12
[Galaxy Tab S2 Android Development] friendly-me:
I wiped the device and installed the December release. It works well, but I can't "see" wifi networks on 2.4 GHz and channel 13.

I don't know if this worked with samsung rom.

Does anyone know if this is a hardware thing or specific to this release? Or, specific to me..

(it's not a big problem since I usually use 5 GHz networks, but wanted to ask)
[Galaxy Tab S2 Android Development] retiredtab:
2.4Ghz channel 13 is, if I recall right, only supported in some parts of the world due to regulations. If it doesn't work, I have no plans to fix it.
[Galaxy Tab S2 Android Development] lpedia:
Whether channels 12 and 13 are available / working would depend on the router's and device's radio firmware.

From the "2.4 GHz 802.11 channels" section in https://www.electronics-notes.com/a...2-11/channels-frequencies-bands-bandwidth.php,

Radio firmware is country-specific because of such differences in radio transmission regulations. If the wifi router's firmware is for a country that restricts channels above 11, those channels would likely be unavailable on its wifi networks. If the phone's / tablet's firmware is for such a country, the device would probably not see 12 or 13, even if they're available.
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-19.1-20240119-UNOFFICIAL-gts210wifi.zip

NOTE: lpedia has built the rom and I have tested the build 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 19 , 2023 release notes

1. Jan 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2024-01
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-19.1-20240216-UNOFFICIAL-gts210wifi.zip

NOTE: lpedia has built the rom and I have tested the build 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 16 , 2023 release notes

1. Feb 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2024-02
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-19.1-20240318-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.

Mar 18 , 2024 release notes

1. Mar 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2024-03

2. The built in files, camera and music apps crash unless SElinux policy is updated. This is precisely WHY each build is tested before being uploaded. See

https://github.com/retiredtab/andro...mmit/519a249a5fd8105817fbc033b78fa10a82304acb

3. For 2024, going forward 19.1 will be built on March, June, September and December ONLY.
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-19.1-20240623-UNOFFICIAL-gts210wifi.zip

NOTE: lpedia has built the rom and and I have 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 release notes

1. Apr, May and Jun 5 security patches as per

https://review.lineageos.org/q/topic:S_asb_2024-04

https://review.lineageos.org/q/topic:S_asb_2024-05

https://review.lineageos.org/q/topic:S_asb_2024-06

2. For 2024, going forward 19.1 will be built on March, June, September and December ONLY.
[Xiaomi Poco F3 GT /  Redmi K40 Gaming] Adamtbkml:
Hi

I have problem when i flash the global rom I felt a small problem with the touch. There are some wrong touches, especially when scroling down or up in screen

Is the problem with the rom?

Or the problem of the touch screen

Any one have this problem ?
[OPPO A72 Themes, Apps, and Mods] xloolx:
Hi guys any stable resurrection Remix rom for oppo a76

And thx
[OPPO A72 Themes, Apps, and Mods] duddlee:
Hy how to unlock bootloader and root A76
[OPPO A72 Themes, Apps, and Mods] pcuserpro:
Hello, please create a new thread.

Sent from SM-A336B using ReLabs
[Redmi Note 9 Questions & Answers] tavern1:
Hello everybody!

Redmi note 9 (merlin) - MUI 12.0.5 - Fastboot unlocked

I follow a post to install TWRP, but it was probably a bad release for my phone.

I think I've completely brick my phone, no recovery, no fastboot.

The device reboot with logo Redmi and I can see the open padlock. When I try to boot on EDL mode the device is visible but really unstable

ttyACM0 is visible after volume down but disappear after 6 seconds . I don't have time to do anything.

View attachment 5685807

Commande line with flashtool :

./flash_tool -s ../V1104/merlin_global_images_V11.0.4.0.QJOMIXM_20200528.0000.00_10.0_global/images/MT6768_Android_scatter.txt -d MTK_AllInOne_DA.bin -c firmware-upgrade -a auth_sv5.auth

View attachment 5685841

I don't know if it's a problem with M6768 or i forgot something ...Don't know what to do .... Please Help !! :)

- Same error with Windows.

- Test with battery charged, plugged and unplugged
[Galaxy Tab S2 Q&A, Help & Troubleshooting] retiredtab:
I'm NOT a gapps user so I will NOT be participating in this thread. I'm not supporting or answering any gapps project questions.

This thread is for users who want/need to run gapps with 19.1 on exynos5433 devices like SM-T710 and SM-T810

I opened this thread as a courtesy for users who want/need gapps.

At last count there were 5 gapps projects and they are in various states of "working" wrt to 19.1. It's your responsibility to put in some hours of research to find out what gapps works for you.

All I can say is that some testers report that NikGapps 12.1L arm64 core (May 1, 2022) work. Despite the arm64 name, that version WILL work on exynos5433. Your mileage may vary.

https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-SL/01-May-2022/
[Galaxy Tab S2 Q&A, Help & Troubleshooting] pflyaz:
I can confirm that I have successfully installed NikGapps Core along with @retiredtab's T170 and T810 LOS19.1 ROMs. I have my complete set of Google Play Apps available to me on the tablet after installing them, including sensitive ones such as Peacock, Netflix, Disney+, etc. All Apps run normally, and when I check Google Play/Settings and scroll to the bottom, I see “Device is certified”.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] bmwdroid:
I've tried to install BitGapps pico + Flamegapps basic (both ARM and ARM64 versions).

NikGapps64 finally worked.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] chappatti:
Installed the ROM on clean wipe on Galaxy Tab S2 T810. Then NikGapps Full thru Basic in different tries.

1. With NikGapps Full to Basic there is no onscreen keyboard that comes up to set up wifi or PIN. Only a Google Voice typing error shows up. How is this solved?

2. After set up without Wifi, the tablet says "Tablet starting....." and does not go further.

Any ideas welcome....
[Galaxy Tab S2 Q&A, Help & Troubleshooting] bmwdroid:
Did you "format data"?

That solved it on mine (with the 2nd flash) testing the prealpha build.

I took only core instead of basic.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] retiredtab:
I had this in my 19.1 msm8916 post #1, but forgot to add it to exynos5433 post #1. The following is now added to 19.1 T710 and T810 post #1. This would also apply to things like wifi password, etc, not just bluetooth pin.

keyboard bug workaround. When prompted to enter something like a Bluetooth pin, sometimes the keyboard is not shown on the screen or off screen. The workaround is to bring up the built in browser, touch the url panel where the http address is and then press the number key when the keyboard pops up. Leave this browser open like that, then press the home button and try your Bluetooth pairing again.

This keyboard bug is a LineageOS bug as per

https://review.lineageos.org/c/LineageOS/android_packages_inputmethods_LatinIME/+/325438
[Galaxy Tab S2 Q&A, Help & Troubleshooting] chappatti:
I figured this out and everything runs good.

I used two files (one file in attachment). The zip file is flashed from TWRP. I also installed the Gboard apk from :

Gboard - the Google Keyboard 12.1.06.463429027-beta (arm-v7a) (nodpi) (Android 6.0+) APK Download by Google LLC - APKMirror

Gboard - the Google Keyboard 12.1.06.463429027-beta (arm-v7a) (nodpi) (Android 6.0+) APK Download by Google LLC - APKMirror Free and safe Android APK downloads

www.apkmirror.com

and apk was installed normally. Gboard gets installed and all is good. I think the apk alone should do it, but I did not try that alone. (For some reason attaching the apk file to this post fails). Once this is done and the Wifi is set up one can then download any other keyboard they want from app store.

Also, I don't recommend using NikGapps above "basic", on Tab S2 T810. A Gapp keeps crashing and the tablet is stuck on "Tablet starting.....".

I downloaded Basic NikGapps from here: https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-SL/09-Jul-2022/
[Galaxy Tab S2 Q&A, Help & Troubleshooting] chappatti:
Please see my post above.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] Pawel_:
I struggled with Installing Gapps on the latest Nov 11, 2022 release.

Tried:

NikGapps NikGapps-core-arm64-12.1-20220908-signed.zip and NikGapps-basic-arm64-12.1-20220908-signed.zip - both installs without issues in TWRP but no Play store or any other apps in the system.

BiTGApps-arm64-12.1.0-v1.7_signed.zip - fails with error "unsupported platform"

BiTGApps-arm-12.1.0-v1.7_signed.zip - installed and Play Store is visible. Get it here https://bitgapps.github.io/download.html
[Galaxy Tab S2 Q&A, Help & Troubleshooting] Dr_MC:
I installed NikGapps-omni-arm64-12.1-20220709-signed.zip from twrp and it is working well. I have the play store.

I was surprised to see that it is an arm64 version even though ( I thought that) the t710 (exynos) has an arm32 processor.
[Sony Xperia 1 IV] aygul12345:
Hi,

If you have your phone rooted, which callrecorder tweak is available to record the phonecalls (Include works with Google Dailer)?
[Sony Xperia 1 IV] ig2205:
I have a rooted Xperia 10 IV and use Skvalex. It is one of the best recorders, but a paid one.
[Sony Xperia 1 IV] aygul12345:
So you having good expieriance with Skvalex? (https://github.com/Magisk-Modules-Repo/callrecorder-skvalex/)

Are there more Rooted Callrecorder vendors?
[Sony Xperia 1 IV] ig2205:
I have been using Skwalex for several years on different phones and have always been satisfied. Do not use the "lite" version only you need to download the full version, e.g. 3.5.0, because then it displays phone numbers.

Skvalex can be installed on two phones.
[Sony Xperia 1 IV] Assimilator-X:
It constantly hangs and a hit and miss. I have some recording that did not recorded at all . That software is buggy as hell. Just go for the LSposed app of google dialer call recording. Only thing you need to take care is to press the record button when you want to record it, then make sure thet you share the recording over BT to your PC othervise it will be overwritten when you record the next call from the same number.