Android Phone Sensors Missing Data
...
it is not allowed to determine if OUTGOING messages ids are contacts (as far as we are aware, seems to be an API limitation)
see: source code https://github.com/RADAR-base/radar-android-phone/blob/master/src/main/java/org/radarcns/phone/PhoneLogManager.java#L260-L285
...
a bug in the sleep stage mapping, where the "wake" sleep stage is mapped to "UNKNOWN". So during analysis, any UNKNOWN sleep stage can be mapped to AWAKE.
ANDROID USAGE DATA
...
...
TIMEZONE Information
The time in topic "application_time_zone" is provided by the pRMT app while the timezone in "connect_fitbit_time_zone" is provided by Fitbit.
There is also a third timezone topic called “questionnaire_timezone” which is provided with every completed questionnaire from aRMT app.
As mentioned here https://github.com/RADAR-base/radar-android-application-status#configuration , The application_time_zone data is only sent on updates.
It maybe worth combining the 3 and using the data which ever is available at a particular timepoint. App's timezone data should be preferred instead of Fitbit as it may be stale/ outdated (Fitbit does not sync as regularly as pRMT)
But it also depends on the source of the data.
For example For Fitbit data, using the Fitbit_time_zone makes more sense, For Questionnaire data, using questionnaire_timezone makes more sense and so on.
The android_phone_usage_event data is sent by the passive app that does not know the categories of the apps and hence its empty.
This data is then processed and app categories are added from the playstore in the backend and output the data to android_phone_usage_event_output.
Both of them use the same schema.
The android_phone_usage_event_aggregated uses this android_phone_usage_event_output data as input and creates windowed phone usage events with duration of usage of each app.