Oddbean new post about | logout
▲ ▼
mwaters | 3 months ago (raw) | export | reply | flag +1 
 Every time I switch away from #amethyst version 0.90.3 the #tor settings are reset to off and I'm back in #clearnet. 

I've nuked the #android storage and setup again. 

Also tried logging in with and without #Amber. 

Is this happening to anyone else?
▲ ▼
Vitor Pamplona | 3 months ago (raw) | root | parent | reply | flag 
 What do you mean by switch away? Everytime you send the app to the background?
▲ ▼
mwaters | 3 months ago (raw) | root | parent | reply | flag 
 Yes.

Either switch to another app, or kill it. 

Switched to version 0.89.10-fdroid and it works as expected.
▲ ▼
mwaters | 3 months ago (raw) | root | parent | reply | flag 
 I hope I haven't ruined your weekend dude.
▲ ▼
mwaters | 3 months ago (raw) | root | parent | reply | flag 
 Fixed in version 0.90.4
Thank you!
▲ ▼
mwaters | 3 months ago (raw) | root | parent | reply | flag 
 This bug is only fixed in 0.90.4 when I upgrade from 0.89.x with my settings intact. 

If I nuke Storage and setup 0.90.4 fresh then this Tor reset bug remains.
▲ ▼
mwaters | 3 months ago (raw) | root | parent | reply | flag 
 Started again on version 0.90.0-fdroid and that's where the bug is introduced.
▲ ▼
mwaters | 3 months ago (raw) | root | parent | reply | flag 
 https://github.com/vitorpamplona/amethyst/issues/1037
▲ ▼
kohei | 3 months ago (raw) | root | parent | reply | flag 
 That also happened to me and I got it working with these steps:

1. Uninstall Amethyst including cache and storage
2. Change socks5 port 9050 to anything else in Orbot
3. Open Amethyst and connect to Orbot with the port number you changed
3. Open Orbot and exit Orbot from More tab
4. Launch Orbot again, and connect to Tor network
5. Open Amethyst and refresh page
▲ ▼
mwaters | 3 months ago (raw) | root | parent | reply | flag 
 Thanks for confirming this and outlining your procedure.

I simply keep a copy of #Amethyst 0.89.x locally , set that up correctly and then upgrade using #Obtainium.
▲ ▼
mwaters | 3 months ago (raw) | root | parent | reply | flag 
 Tried your port change procedure today and can confirm it works around this #amethyst bug. 

Thanks nostr:nprofile1qqsd03kszje59q2m52wy3u6yne8squ7lsn626kq2u9e48qzp564mdwqpr9mhxue69uhhyetvv9uju7t00fhhycfwwahhymry9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpzfmhxue69uhhytntda4xjunp9e5k7tc5sref5