You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been running some test with Apollo today and we ran into something that confuses us.
If we look at the extracted data we can see that most timestamps have been corrected for the offset except for these tables (gotten with SELECT DISTINCT activity FROM apollo WHERE output NOT LIKE "%OFFSET%";):
Especially for Telephony Activity this is leading to inconsistencies in the data. If we do apply the offset to Telephony Activity then everything fits in nicely with the rest of the events. However if the offset isn't applied to Telephony Activity then we're seeing things like outgoing calls started while the screen is off according to the other events.
Example:
The above example was manually parsed and the offset was calculated from correlating events on the phone. The offset was 96 seconds and this matches the offset found in the database.
However if we don't apply the offset to the two yellow lines then this call takes place when the screen is off.
Are we misinterpreting something or is this an error in the module(s)?
The text was updated successfully, but these errors were encountered:
We've been running some test with Apollo today and we ran into something that confuses us.
If we look at the extracted data we can see that most timestamps have been corrected for the offset except for these tables (gotten with
SELECT DISTINCT activity FROM apollo WHERE output NOT LIKE "%OFFSET%";
):Especially for
Telephony Activity
this is leading to inconsistencies in the data. If we do apply the offset toTelephony Activity
then everything fits in nicely with the rest of the events. However if the offset isn't applied toTelephony Activity
then we're seeing things like outgoing calls started while the screen is off according to the other events.Example:
The above example was manually parsed and the offset was calculated from correlating events on the phone. The offset was 96 seconds and this matches the offset found in the database.
However if we don't apply the offset to the two yellow lines then this call takes place when the screen is off.
Are we misinterpreting something or is this an error in the module(s)?
The text was updated successfully, but these errors were encountered: