So, just to be clear, this relies on the core to show the progress of 0 when we're not connected.

by definition, 0 means "error, cannot connect, aborting", at least on rust/cffi event level:

changing that to another meaning or having different meanings between cffi and jsonrpc here is a call for trouble.

android also shows "connecting", but does that only before the first event is emitted.

android also shows a hint "since forever", we can think over rewording (eg. pointing to troubleshooting, that was not always available).

so maybe a better and easier approach for desktops is to do the same:

• as long as screen shows "Connecting..." show the unconditional hint multidevice_same_network_hint

that way, we also do not need to think about what is "slower than expected" - and we can maintain the same wording across all platforms

this is how android looks like:

by definition, 0 means "error, cannot connect, aborting", at least on rust/cffi event level:

Good Point, we should use some different value for the connection step then if needed. Or change the logic in desktop to wait for first update.

On desktop it does not rely on the error in the progress report event, it just displays the error getBackup throws.

by definition, 0 means "error, cannot connect, aborting", at least on rust/cffi event level:

Just in case i've checked that the core only reports 0 on errors or a canceled transfer.