There is a public library for which Debian’s Tor infra fails. Cannot ever build a circuit. I assumed the library was blocking Tor, but Orbot running on AOS has no issue.
Most of my Tor access is from Debian. Makes me wonder if all the locations where Tor is unreachable is perhaps not due to a blockade, but rather software deficiencies. Or if the PC is rightfully more distrustful than Orbot.
My version of Orbot apparently pre-dates that. At the bottom of the orbot screen it says “trouble connecting? Use bridges [boolean slider]”, and the switch is toggled off. I don’t see mention of “Smart Connect” in the settings.
Hmm. Only other thing I can think of is if you have an always on VPN on the phone and Orbot is routing the Tor connection through it to explain the behavior.
Either way, a bridge on the computer should mask the use of Tor and hopefully allow it to connect. Its what bridges were designed for.
I’m not sure what the Tor Project advice is these days, but my phone is setup to have Netguard hijack the VPN option of AOS and force select apps over tor (to Orbot). It’s annoying because in fact it is impossible for me to run Netguard and Tor over a VPN. Because Netguard hijacks the VPN, I cannot use a real VPN. I can run a VPN (generally openVPN), but then I must give up Tor if I do that. Orbot can only run in parallel, but because Netguard loses the VPN slot I can only use Tor-aware apps in that situation. So ultimately what you’re thinking is not possible with my tool chain (of old versions).