e-mission / e-mission-docs

Repository for docs and issues. If you need help, please file an issue here. Public conversations are better for open source projects than private email.
https://e-mission.readthedocs.io/en/latest
BSD 3-Clause "New" or "Revised" License
15 stars 32 forks source link

[native code] big gap while starting *some* trips on motorola android (no SIM card, airplane mode) #1044

Open shankari opened 4 months ago

shankari commented 4 months ago

I have an old motorola phone that I use to install my work apps. Since this is not my primary personal phone, it doesn't have a SIM card. And since it doesn't have a SIM card, I haven't bothered to take it out of airplane mode since my last trip. And I'm seeing huge gaps in starting a trip sometimes which leads to incorrect trip durations because we extrapolated the duration of the missing start based on the speed of the sensed part, and if we only sense the end of the trip, that speed is close to zero. So the extrapolated duration is very large.

I am not sure if being in airplane mode is significant - I suspect it is a red herring and this has always been happening. But the bigger question is why OPGeofence didn't work. That uses the motion transition API, which should primarily use accelerometer data. To my knowledge, airplane mode does not affect accelerometer data, and neither does the lack of a SIM card. Why then are we not seeing the OPGeofence trigger?

I have filed an internal issue with detailed screenshots and logs.