[Galaxy Tab S2 Android Development] MSe1969:
Tips & tricks & FAQ​

Tips & tricks

The only way out of the 'Download mode' is the same way, you got in: [Home]+[Vol.Down]+[Power]

The way to boot into TWRP after flashing it in 'Download mode' is [Home]+[Vol.Down+]Power] until the screen turns black and then immediately [Home]+[Vol.Up+]Power] - some finger coordination required

When starting AuroraStore for the 1st time, you cannot choose "AuroraServices" as install method. Choose "Session Installer" to complete the initial setup. Afterwards, you can and should change the installation method to "AuroraServices"

microG: You should configure https://api.positon.xyz/?key=74600654-2aec-11ef-aa95-3b7218da6865 as an API endpoint in microG Settings -> Location -> ⋮ -> Configure service URL."

FAQ

Q: I want to learn more about the specific features of your ROM.

A: Please refer to the FAQ section here and the next post

Q: Are there features not working (properly) in this build?

A: I re-use the device config and blobs created by the devs listed in the Credits section of the OP, therefore I expect the same issues as outlined e.g. in this thread - in short:

- better use a headset when making phone calls with the tables (lousy mic and sound quality)

- fingerprint unlock does not work, after the device goes into deep sleep - details see here

- DRM level 1 only

- If you charge the device while it's powered off and then want to power it on, you MUST wait at least 30 seconds AFTER disconnecting the charger cable before pressing the power button

Q: Android 11 does not receive any longer ASB patches from Google - what now?

A: The community still provides ASB backports and uploads them to the LineageOS gerrit (I am one of the contributors). To indicate the status of backports, I have added a "Custom patch level" info in the device info settings area. Of course, this is "best effort", but the device blobs of this device anyhow are outdated, hence the situation until February 2024, where official ASB patches were provided by Google, is not that significantly different...

Q: There are also LineageOS 20 builds for this device being offered, why don't you go that path?

A: I repeat, what I have stated already in the OP: The answer can be found here: https://lineageos.org/Changelog-26/ (section "Let’s talk about legacy devices…"). There exists a set of patches to "carve out" the eBPF packet filtering, which then would allow to build LineageOS 20, however - I consider the firewall feature a very important feature of my build, which aims at focusing on privacy and security (with the well known limitations of it being an old device, of course) - to me the loss of packet filtering is more severe than the "win" of having Android 20 and officially provided ASB patches.

Q: Does this ROM support Magisk for root?

A: I don't use Magisk myself. From other threads I gained the impression the answer is yes, but I haven't tested, I will not test it and I can't help you with issues. Independently, this ROM comes with some features, which help avoiding the necessity to have a root solution.

Q: Does this ROM provide OTA updates?

A: Yes, it does! After initially installing, you normally do not need to manually flash any update via TWRP. (This of course assumes, that you did not flash any other stuff on top, such as Magisk)

Q: Can I still sync my contacts and calendar with my Google account using the microG build?

A: Google is not the only option to sync your contacts / calendar - see e.g. this post or this post for more context. Nevertheless, if synchronizing your contacts/calendar with Google is a must for you, please refer to these sources: [1], [2], [3]