Logging: Wrong numbers for performance?

[buchbergerd]

Bug Report

Thanks for the app! Unfortunately, performance measurements with it do not work for me:

Context

• Device: Crosscall Core-Z5
• Carrier Privileges (Y/N): no
• Android Version: 14
• App Version: 0.5
• Git Hash: The one from Releases

Description

In the log file, there are always the same numbers for downSpeed_kbps and upSpeed_kbps.
Moreover, for me it is not really clear what/how it measures. Does it need iPerf3 running? I tried with and without, but in both cases it does not work.

This is what I always get:

InterfaceThroughput,android_version=14,manufacturer=Crosscall,measurement_name=\nNEOS,model=Core-Z5,radio_version=S.HI.4.3.3.c6-00218-KODIAK_GEN_PACK-1.61458.6\,S.HI.4.3.3.c6-00218-KODIAK_GEN_PACK-1.61458.6,sdk_version=34,security_patch=2025-03-05,soc_model=SM7325 MobileRxBytes=27523881i,MobileTxBytes=1377656701i,downSpeed_kbps=72087i,upSpeed_kbps=60000i 1744727433027

The fields downSpeed_kbps and upSpeed_kbps are always the same, regardles of good or poor connection and without any noise. MobileTxBytes changes.

How to Reproduce

Steps to reproduce the behavior:

1. (Variant with iPerf running: Start iPerf)
2. Settings -> Logging -> Enable "Log throughput information"
3. Enable logging to file
4. Move around, close to base station and far away etc.

Expected Behavior

I would expect measurement results for the throughput, according to the settings in the iPerf tab. There should be some noise and clear differences between the values, depending on the position.

Actual Behavior

It's all the same value.

Screenshots

n/a

Additional Context

Possible Fix

[hajoha]

Hi @buchbergerd, thanks for the report! I will try to reproduce the issue with our Z5 and will get back to you asap.

[hajoha]

So I did a quick setup and created a simple Grafana dashboard.
Those variables (MobileTxBytes,MobileRxBytes) are just counters counting up, for each byte send/recvd, since the last boot. Here is the doc

For downSpeed_kbps and upSpeed_kbps, those are only estimations of the OS what it thinks how good the link to the next hop is. Here is the doc and here.

You probably want to get the actual iPerf3 traffic data, this is located in the omnt/iperf3LP/. This is also upladed to the Influx, if Influx is enabled and correctly configured. With the _measurement=Iperf3.

[buchbergerd]

Ah, thanks for the clarification @hajoha !
Maybe you could make it more clear in the app that the Performance Logging has nothing to do with the real measurement and rename the logging item?

Which app do you use for the influxdb? Using a db via network does not make sense for me: The phone might leave coverage and the connection breaks in coverage tests. In throughput tests, it distorts the results.
Could you please add the feature to upload later, when the smartphone is back in the lab?

[hajoha]

You can just activate Log to file and upload that file to a later point to your influxdb instance. iPerf3 will also generate a lineprotocol file located in in the mentioned path. Here is the doc. Maybe this section is of interest. To achieve this, you can disable Influx Logging, enable it when you are back in the lab and then manually select every run and press upload.

[PeterHasse]

@buchbergerd thanks for reporting the issue. I added a Note to the documentation to make this more clear, see https://github.com/omnt/OpenMobileNetworkToolkit/blob/rel/0.6/docs/home.md
we try to also make this more clear in the UI in the future

[hajoha]

Please see #62