Android Phone Sensors Missing Data

Discussion around peculiarities of Android phone sensors, data incompleteness, known issues, work-arounds etc.

See page on phone sensors data for some documentation of the sensors and the specification documents in github:

https://radar-base.org/index.php/data-sensors/

https://github.com/RADAR-base/RADAR-Schemas/tree/master/specifications/passive

Values not recorded if unchanged

There are two data streams, the light sensor and battery level, that only record data if the value changes. Therefore the data is collected in very irregular intervals.

Night time values may get limited by Android

There is some indication that over the night Android makes assumptions around sensor activity variability and may limit the data collected.

See issue raised in relation to the Light and Battery sensors on Android.

RSD-18 - Getting issue details... STATUS

Details of phone sensor details for pRMT https://radar-base.org/index.php/data-sensors/

Environment Sensor → Light

Other → Battery 

Other Android limitations

Android may be more aggressively limiting phone sensor data collection

RSD-13 Text Messages Contacts Status can be NULL

https://radar-base.atlassian.net/servicedesk/customer/portal/1/RSD-13

schemas https://github.com/RADAR-base/RADAR-Schemas/blob/master/commons/passive/phone/phone_sms.avsc  # value is unknown if contact is unknown, don't assume that it is false.

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

you see the value is not initialized for outgoing 

// Only incoming messages are associated with a contact. For outgoing we don't know
        Boolean sendFromContact = null;
        if (type == PhoneSmsType.INCOMING) {
            sendFromContact = targetIsContact;
        }

Possible Solutions:

Some of the contacts will later be know because the same hash value is seen in INCOMING, it may at that point be possible to add populate a TRUE value into some of the messages that previously were OUTGOING. See the image attached to the issue

FITBIT DATA Anomalies

Sleep stages Unknown

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.