Phase out Orbot support once TorVPN reaches stable

[Ganwtrs]

TorVPN is an official client for accessing the Tor network and has a better security posture than Orbot.

For example, Orbot is

• Incompatible with MTE and hardened_malloc due to memory corruption bugs that remain unresolved despite numerous community reports
• No formal threat model
• People have to regularly write GitHub issues asking for the Guardian Project to put the updated applications on all of their means of distribution (Orbot can be outdated for weeks or a month+ on the Play Store)
• Incredibly overcomplicated app, constantly introducing bugs
• They regularly ignore privsec issues / feature requests, and have even explicitly stated in some cases that people should just use the Tor Project's Tor VPN app

Taken from mollyim/mollyim-android#657

[andyzu2020]

You're probably using GrapheneOS and that's why you have the right problems, on the other hand Orbot is safer than TorVPN, Orbot can for example, assign a different circuit to each application, sacrificing latency and speed for paranoid security.

A quick fix:
Run Orbot in bridge mode (non-VPN) to reduce memory load: Settings > Bridges > obfs4

[Ganwtrs]

Orbot can for example, assign a different circuit to each application, sacrificing latency and speed for paranoid security.

Doesn't TorVPN have a difference circuit per connection? That might debatably be better