The three tests were done in a row, just by deactivating the access
point for 30 seconds between two tests, and generated one big
aggregation file. Here is the detailed (but approximate) timing of the
three tests:

- T0: AP started (12:30)
  - Elapsed:    00m 00s .00
  - Total time: 00m 00s .00
- T1: t01 started
  - Elapsed:    00m 06s .50
  - Total time: 00m 06s .50
- T2: AP stopped
  - Elapsed:    05m 05s .75
  - Total time: 05m 12s .25
- T3: AP started
  - Elapsed:    00m 37s .02
  - Total time: 05m 49s .27
- T4: t02 started (12:36)
  - Elapsed:    00m 14s .99
  - Total time: 06m 04s .26
- T5: AP stopped
  - Elapsed:    05m 07s .29
  - Total time: 11m 11s .55
- T6: AP started
  - Elapsed:    00m 34s .48
  - Total time: 11m 46s .03
- T7: t03 started (12:42)
  - Elapsed:    00m 06s .97
  - Total time: 11m 53s .00
- T8: AP stopped
  - Elapsed:    05m 09s .06
  - Total time: 17m 02s .06

This timing is approximate because the chronometer was started only
after the given action had begun (because the chronometer was an app
running on the smartphone-access point, it was not possible to start
both the access point and the chronometer at the exact same time).

We assume time T0 is 12:30, but the precise hour was not wrote down at
the time. No big deal though.