continue test after connection loss + suggestions

[bojogon7]

When dicconected from internet you get:

Data Transfer Error
Lost connection during test.
DataChannel failed due to network instability
Data channel closed

Suggestion:
Continue test after loss
add graph with downtime and time
Add prolonged test (with bigger packet interval) about 2 h
Add button redo test

[vishnunuk]

Working fine.

[vishnunuk]

Continue test after loss?

retry in the background.. I will look in to this soon.

add graph with downtime and time

Total test duration right. downtime ?

Add prolonged test (with bigger packet interval) about 2 h

Check, Max in setting, you can choose UNLIMITED

Add button redo test

manual refresh is much better.

[bojogon7]

Continue test after loss?

retry in the background.. I will look in to this soon.

Thanks. Currently if it encounter connection loss it crashes.

add graph with downtime and time

Total test duration right. downtime ?

Yeah just add graph similar to packetstats maybe with time stamps and option to maybe export cached data to spreadsheet .ODS or something. Maybe also measure ping for better clarity?

Add prolonged test (with bigger packet interval) about 2 h

Check, Max in setting, you can choose UNLIMITED

Ok it didn't click with me at first, maybe consider renaming this to something other? Unlimited test, extended test, prolonged test etc.

Add button redo test

manual refresh is much better.

Yes it would be also good, currently it doesn't show anything, maybe add refersh button after end of test.

Maybe for later if you have time you can consider packaging it as app and add it to F-droid, flathub, and exe etc. I can create separate issue for it if it interest you. Because currently for android you have to keep it opened in tab for it to work.

[vishnunuk]

Go to settings >Advanced

[vishnunuk]

Check https://openpacketloss.com/selfhosted-server we have server for Android, iOS, Windows, Linux and Mac. Also available as docker image.

[vishnunuk]

connection loss it crashes.

This is exactly what we need. you should fix the connection problem and retry. maybe giving it 1 more chance to recover is a good idea. I will consider this on the next update.

[bojogon7]

Check https://openpacketloss.com/selfhosted-server we have server for Android, iOS, Windows, Linux and Mac. Also available as docker image.

Can you consider flathub, fdroid and stand alone apk ports?

[bojogon7]

connection loss it crashes.
This is exactly what we need. you should fix the connection problem and retry. maybe giving it 1 more chance to recover is a good idea. I will consider this on the next update.

Can you consider constantly retrying?

[vishnunuk]

Maybe in Max it might be useful. Let me check.

[vishnunuk]

I worked on this around Oct/Nov 2025. This was already implemented, and I had just forgotten about it.

Currently, retry behavior depends on the selected test mode:

Standard Tests (Quick / Default / Finite Duration)

For fixed-duration tests (e.g., 30 seconds), if the connection drops or the server becomes unavailable:

• The test fails immediately and stops.
• An error modal is shown (e.g., "Lost connection during test").
• The modal includes a Retry button.

Current behavior:

Clicking Retry triggers window.location.reload(), which refreshes the page and starts a new test. It does not resume from where it stopped.

Continuous / Real-time Mode (MAX + Unlimited)

For long-running tests using MAX preset + Real-time mode + Unlimited duration:

• There is a built-in automatic reconnection mechanism.
• On connection loss:
  • Packet sending stops.
  • The client attempts to reconnect (up to 10 times with exponential backoff).
• State is preserved: current Sent and Lost counts are retained.
• Automatic resumption: once the connection is restored (e.g., cable replugged or server back online), the test continues from the previous state instead of restarting.

[bojogon7]

Thanks I will try.

Can you consider fdroid and flathub packaging?