Version 1.0.12: Dutch and Russian translation

Version 1.0.12 again brings new translations, Dutch and Russian, done by Ivo Janssens (with support from Evelien Urkens and Andreas Van den Bergh) and Alexander Nedilko, respectively. If you would like to help to translate phyphox into your language as well, check out our languages page for more information.

Also note, that we will happily share worksheets in any language. Since we can only provide the website in English and German, only those worksheets will be found directly in the experiment data base (like a fantastic new worksheet on pressure by Holger Jessen-Thiesen), but we will share any material in other languages on our languages page (like the first Dutch worksheet by Dirk Janssen). For more material we can also add a dedicated page for a specific language or add a link to an external collection.


Changes on Android and iOS

  • Dutch translation.
  • Russian translation.
  • Inelastic collision experiment hides invalid intervals.
  • Translations are now also applied to units.

Changes on Android

  • Fix lines connecting to first point when loading a previously saved state.

Changes on iOS

  • Fix crash when value element has empty map tag.

Two new events in Göttingen and Hamburg

Two new events have been added to our calendar. The first one is a physics colloquium in Götting on 23rd April (held in English). The other event will be held in German on 16th June in Hamburg as a workshop (not to be confused with the talk and workshop in Hamburg this Friday, 13th April).

New events in Hamburg and Aachen

We have added two new events to our calendar (both held in German). The first one is a teacher conference on 13th April 2018 in Hamburg. The second one is our training for phyphox in academic teaching which was quite popular last year. While a detailed program will follow, you can already save the date: 7th September 2018 in Aachen.

Version 1.0.11: Czech and Polish translations for phyphox

With version 1.0.11 we introduce the first translations of phyphox, which are Czech and Polish, done by Karel Havlíček and Tomasz Greczyło respectively. If you would like to help to translate phyphox into your language as well, check out our languages page for more information.


Changes on Android and iOS

  • Czech translation.
  • Polish translation.
  • Introduced a new “language” entry to the info menu on the main screen.
  • Fix: Flickering in motion stopwatch.

Changes on Android

  • Update to file format 1.6 and support audio sample rate output. (Which has been introduced as a hotfix to iOS previously.)

phyphox in Taipei

Last week, I had the chance to speak at the Annual Meeting of the Taiwan Physical Society and to give a workshop at the National Taiwan Normal University. For this I have to thank Professor Chih-Ta Chia for the invitation, the warm welcome and the great hospitality. The same thanks go out to all the friends, teachers and students I met there who helped to make these three days in Taipei unforgettable.

If you are interested in the talk, you can see the recording here:

Version 1.0.10 (hotfix for iOS)

If you are using an iOS device (specifically an iPhone older than the iPhone 6s or most iPads) and tried our latest update, you will quite certainly have encountered the error “rate mismatch”. Sorry about that, we have just released version 1.0.10, which fixes this. (Since this only fixes the iOS issue, there will be no 1.0.10 on Android.)

If you are working with your own phyphox experiments, the following details might be relevant to you:

The problem here is, that there is no guaranteed way to force a certain audio sample rate. You can set a preference, but the system might chose to ignore this (for example when using AirPlay, which forces 44,1 kHz). Since many experiments require the exact data rate for their calculations, we inserted a check, which tests if we actually got the correct rate. Turns out that this resulted in the error on all older devices which natively run at 44,1 kHz because a) we checked to early and the desired rate might still be set correctly and b) there are several more scenarios which prevent switching to a specific rate. Therefore we now allow that the system sets a different rate and modified our file format, so that the experiments can get the actual sample rate and use it for their calculations.

This means, that at the moment the file format in iOS supports this new output while the Android version does not. We will fix this with the next update soon, but if you rely on the exact sample rate for your own experiment, please let me know, so I can help to get this right now.