Symptoms are basically that after a while the connection just "dies" without any ability to reconnect (eventual Failed to establish new connections to remote error) unless Cloak client is restarted.

Also affects UDP (more obvious there because you can just see " read from stream 1 with err " healthy messages stop with no further events) but it's the first time for me that TCP cloak got completely disabled.

NOTABLE FACT:
connecting the phone to my laptop over USB solves problem utterly and completely, both TCP and UDP cloak start working flawlessly.

I initially suspected:

• infamous TTL-based throttling
• local filtering shenanigans (the environment I'm currently in is hostile)
• some particular phone anomaly

I think it is not TTL-based throttling because it has been replicated by my colleague in a decent EU country on a connection where mobile hotspot is explicitly enabled and billed separately.
Also in most cases mobile operators also detect USB Tethering and Cloak works perfectly for me when connection is shared over USB

I doubt it is local hostiles somehow detecting cloak because of aforementioned replication by a colleague in EU and because connection from here works over USB

It has been replicated on three different android phones (Pixel 5 with CalyxOS, some noname brick with LineageOS and a XIaomi unit)

The connection looks like this when breaking hard

Laptop with Cloak (linux)
|
|wifi (android hotspot)
|
Android Phone
|
internet

And it looks like this when working perfectly
Laptop with Cloak (linux)
|
|USB wire
|
Android Phone
|
internet