Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Time offset not applied in all tables #21

Open
r-franke opened this issue Jun 26, 2020 · 0 comments
Open

Time offset not applied in all tables #21

r-franke opened this issue Jun 26, 2020 · 0 comments

Comments

@r-franke
Copy link

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%";):

WhatsApp Image 2020-06-26 at 12 12 12

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:

WhatsApp Image 2020-06-26 at 14 14 54

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)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant