Banana Studio
Guides

iPerf for Android 1.21: Ready for Android 17 with Local Network Access Support

iPerf for Android 1.21 is ready for Android 17. When needed, the app now asks for the new "Nearby devices" (local network) permission and explains why, so LAN bandwidth tests and the built-in iPerf server keep working. This release also updates Google Play Billing and the advertising SDK.

On this page

iPerf for Android 1.21: Ready for Android 17

We're happy to announce iPerf for Android 1.21. This release prepares the app for Android 17, which changes how apps talk to other devices on your local network. You can keep measuring Wi-Fi and Ethernet throughput between your phone, tablet or Android TV and your PCs, routers or NAS, just like before.

It's available for phones, tablets and Android TV on Google Play and the Amazon Appstore.

What's new in 1.21

Android 17 support

iPerf now targets Android 17 (API level 37), the latest version of Android. The app follows Android 17's new privacy rules and is ready for devices that receive the update.

New: local network access ("Nearby devices") permission

Android 17 adds a privacy protection called local network protection. Apps built for Android 17 can no longer reach devices on your home or office network unless you grant the "Nearby devices" permission.

That matters for a network testing tool like iPerf, because most tests run inside your local network:

  • Client mode: connecting to an iperf3 or iperf2 server on your PC, router or NAS (for example 192.168.1.10).
  • Server mode: other devices on your network connecting to the iPerf server running on your phone or TV.
  • UDP tests (-u) to and from local devices.

Without the permission, Android 17 silently blocks this traffic: a test against a local server fails or times out, and other devices can't reach the server on your device.

What iPerf 1.21 does:

  1. On Android 17 and later, the first time you open the app, iPerf shows a short screen explaining why it needs local network access.
  2. Tap Request permission, then choose Allow in the Android prompt.
  3. That's it. You only have to do this once; the permission stays granted, including after a reboot.

On Android 16 and earlier, nothing changes: no new screen and no new prompt.

Your privacy

The permission is used only for the traffic of the iperf commands you run. iPerf does not scan your network, discover devices in the background, or collect any information about your devices.

If you denied the permission

If you tapped "Don't allow" earlier, or the Android prompt doesn't appear anymore, you can enable it manually:

Settings → Apps → iPerf → Permissions → Nearby devices → Allow

On Android TV the path is similar: Settings → Apps → iPerf → Permissions.

Updated Google Play Billing

In-app purchases (such as removing ads) now use Google Play Billing Library 8, the version Google Play currently requires. Existing purchases are still recognized; you don't need to do anything.

Updated advertising SDK

The advertising SDK (Liftoff Monetize / Vungle) has been updated to its latest supported version, as recommended by Google Play. This keeps the free version stable and compliant with current store policies.

Minimum Android version is now Android 6.0

The latest Google Play Billing and advertising libraries no longer support Android 5.0 and 5.1. iPerf 1.21 therefore requires Android 6.0 (Marshmallow) or newer. Devices still on Android 5.x keep the previous version installed, but won't receive this update.

Tips for upgrading

  • Using "Start iPerf server on boot"? If your device runs Android 17, open iPerf once after updating and grant the "Nearby devices" permission. A server started at boot can't show the permission prompt itself, so without the permission it won't accept connections from devices on your local network.
  • A test against a local server suddenly times out? On Android 17, check first that the "Nearby devices" permission is allowed for iPerf (see above).
  • Testing against public iperf servers on the internet? Those tests don't need the new permission, but granting it lets you test both local and internet servers without interruptions.

Compatibility

Minimum Android version Android 6.0 (previously Android 5.0)
Target Android version Android 17 (API 37)
Devices Phones, tablets and Android TV
Bundled tools iperf3 3.19.1 and iperf2 2.2.1 (unchanged)
Stores Google Play and Amazon Appstore

FAQ

Why does iPerf need the "Nearby devices" permission? Starting with Android 17, Android requires this permission for any app that connects to, or accepts connections from, devices on the local network. iPerf's main job is to measure the network performance between your device and other local devices, so it needs this permission to work.

Does iPerf scan my network or track my devices? No. The permission only lets the iperf commands you start send and receive test traffic. iPerf doesn't discover, list or store information about devices on your network.

I'm not on Android 17. Will I see the new prompt? No. Devices running Android 16 or earlier keep working exactly as before.

Do I have to grant the permission again after a reboot? No. Once granted, it stays granted. Android may reset permissions of apps you haven't opened for several months; if that happens, just open iPerf and grant it again.

Feedback

We'd love to hear from you. If something doesn't work as expected on your device, especially on Android 17, please use Feedback in the app menu, or leave a review on Google Play or the Amazon Appstore.

Thank you for using iPerf for Android!

Related posts