Lets make wifi fast again!
 help / color / mirror / Atom feed
From: bob.mcmahon@umbernetworks.com
To: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: [Make-wifi-fast] iperf2 Android testers needed - Google Play release
Date: Fri, 07 Aug 2026 15:40:50 -0700	[thread overview]
Message-ID: <d84eb65a52b92c52295b6da9fbfec0cf@umbernetworks.com> (raw)

Hi all,

I'm looking for 30-40 volunteers to help test the iperf2 Android client 
so I can get it onto the Google Play Store. That will make it 
installable normally, without the warnings associated with sideloading 
an APK from SourceForge.

As a thank-you, I'll send an iperf2 shirt to everyone who completes the 
testing.

WHAT THE APP DOES

The app is a native iperf2 client for Android, with:

  	* Live throughput, RTT, and bytes-in-flight meters
  	* TCP and UDP testing
  	* L4S testing, including Prague where supported
  	* Bounceback/RPS responsiveness testing
  	* Request/reply latency histograms
  	* Support for testing under simultaneous working load

The goal is to make real network performance, responsiveness, and 
L4S/DualQ testing easy to run directly from a phone or tablet.

If you'd like to try the current APK before signing up, it's available 
here:

https://sourceforge.net/projects/iperf2/files/iperf2.2.2_4August2026_android.apk/download 
[1]

For the closed test, I'll send a Google Play opt-in link directly to 
everyone who volunteers.

WHY I NEED VOLUNTEERS

Google requires new personal developer accounts to complete a closed 
test with at least 12 testers continuously opted in for 14 days before 
applying for production access.

I'd like 30-40 volunteers so we have plenty of active testers and useful 
feedback rather than merely clearing the minimum.

WHAT I NEED FROM YOU

If you're willing to help, please email:

iperf2-android-testing@umbernetworks.com

Send the Google account email address you want to use for testing. It 
can be Gmail or another email address associated with a Google account.

TIMELINE

Now through August 13:
Please sign up.

August 14:
I'll send the closed-test opt-in link. Please opt in, install the app, 
open it, and run your first test that day if possible.

August 14 through September 4:
Please remain opted in for the full period and run a few real tests 
during those three weeks. Trying different networks, test modes, and 
working-load conditions would be especially useful.

HOW IT WORKS

  	* I'll add your Google account to the closed test and send you the 
opt-in link.
  	* Open the link while signed into that Google account and select 
"Become a tester."
  	* Install iperf2 from Google Play.
  	* Run some actual tests during the testing period. Feedback on bugs, 
usability, statistics, or unexpected network behavior is welcome.

If you use multiple Google accounts on your Android device, make sure 
Google Play is using the same account that you used to opt in.

Thanks for helping get iperf2 onto Google Play.

Bob

Links:
------
[1] 
https://sourceforge.net/projects/iperf2/files/iperf2.2.2_4August2026_android.apk/download

                 reply	other threads:[~2026-08-07 22:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d84eb65a52b92c52295b6da9fbfec0cf@umbernetworks.com \
    --to=bob.mcmahon@umbernetworks.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox