Android benchmarking app

[barbibulle]

Android counterpart to bench.py. Only RFComm Server, RFComm Client, L2CAP Server and L2CAP Client are supported in this version.
Also, BT addresses must be entered manually, scanning isn't built-in.

[mogenson]

I've noticed that the app can be suspended when throughput data transmission takes a few seconds:

11-07 16:14:04.508  5080  5242 I btbench.socket-server: got connection
11-07 16:14:14.252  1310  1750 D ActivityManager: freezing 5080 com.github.google.bumble.btbench

Is it possible to keep this app from being frozen by the Activity Manager? https://source.android.com/docs/core/perf/cached-apps-freezer Maybe keep the display on to keep the app in the foreground?

[barbibulle]

I've noticed that the app can be suspended when throughput data transmission takes a few seconds:

11-07 16:14:04.508  5080  5242 I btbench.socket-server: got connection
11-07 16:14:14.252  1310  1750 D ActivityManager: freezing 5080 com.github.google.bumble.btbench

Is it possible to keep this app from being frozen by the Activity Manager? https://source.android.com/docs/core/perf/cached-apps-freezer Maybe keep the display on to keep the app in the foreground?

I usually have a developer setting that keeps the screen on while on USB adb. That does help prevent freezing the app. The other method is to do to the Developer settings and changing "Suspend execution for cached apps" to "disabled".

A cleaner long term solution would be to create a background service in this app, so that it can continue working without beeing frozen, even if you switch to a different app, but that's a task for another PR :-)

[mogenson]

@barbibulle when going from phone (RFCOMM client) to USB dongle (RFCOMM server) I've noticed that even though we're calling create insecure RFCOMM socket, I get a pairing request popup on Android. This makes a test hard to automate using the ADB shell launcher commands.

Do you know what maybe causing the bonding attempt?

[barbibulle]

@barbibulle when going from phone (RFCOMM client) to USB dongle (RFCOMM server) I've noticed that even though we're calling create insecure RFCOMM socket, I get a pairing request popup on Android. This makes a test hard to automate using the ADB shell launcher commands.

Do you know what maybe causing the bonding attempt?

The "insecure" part of setting up an RFComm socket is a bit misleading. It's just about whether you want MITM protection or not, but not whether you want any form of security or not. Android will always require the devices to have a pairing and to encrypt the channel. If you don't bond, it will re-pair every time you setup the socket. To avoid the dialog coming up everytime, what you need to do is to bond the devices. You can do that from either side. From the Bumble side, you can use the pair app to initiate pairing and bonding. Or you can use the nrfConnect app on the phone to do that as well.

[mogenson]

Thanks for the info and context. Looking forward to having the BtBench app as part of the Bumble project.