Thread

Yes, however i think it is not an issue with amethyst.. right now i saw that if i exclude amethyst from orbot (i have an app selection list), but if i use socks port at amethyst it work .. so, i'm just guessing, probably orbot is dropping socks traffic if it comes from a in the list .. this may be happened after last orbot updates

Personally I didn't notice orbot moved from socks to firewall so it wasn't working with my amethyst orbot setup. Either using firewall mode in orbot and clear net in amethyst or socks in orbot and orbot setup in #amethyst works for me?