The android versions are notoriously badly implemented/written.

The command line client toxic seems to work even when unable to write to the filesystem at all.

Solution: comment the part out where it got stuck, and sideload.

I would call that a work around, not a solution. For a project that cries about privacy, the fact that all the implementations are so .. anti privacy like that is pretty bad.

I've noticed that too for the Antox Android client. It's a definite red flag. The TRIfA Android client doesn't have that problem though.

I'm pretty sure the Android client is 3rd party. I suggest toxic on a bouncer, accessed via mosh for better usage. If you handle it right, you can get push via the terminal receiving the bell character and reacting accordingly.