Overland_android
Overland_android copied to clipboard
Properties Not Being Recorded
I tried your app today, after the iOS developer mentioned someone had created an Android version. The properties seem to be missing wifi, which I'm connected to, battery state, and device_id.
Battery state seems to only opt to true or false. This phone is currently at 100%. Now, with the current global situation, I'm not going out much to really give it a test, but wanted to support this, as the reason I have been waiting for an Android version of this is because I like the features the iOS version offers.
"properties":{"timestamp":"2020-05-12T00:43:13.274Z","battery_level":1,"speed":0.15,"altitude":-5,"horizontal_accuracy":15.1,"vertical_accuracy":-1,"significant_change":"disabled","locations_in_payload":1,"battery_state":false,"device_id":"","wifi":"","deferred":"0","desired_accuracy":"0","activity":"other","pauses":true,"motion":["still"]}}}
battery_state <- battery.is_charging. so if it's false, that means you are not loading your phone. "battery_level":1 means the phone is at 100% as you said.
device_id is undefined because, the device ID can't be configured in the settings, at the present time. So you're right.
"wifi": "" I checked the trigger's working properly. Maybe not when the application opens, but as soon as the phone triggers on the first router, the variable is updated. To be confirmed.
Is setting the device_id in the settings planned in future?
Re battery state...the docs say that battery_state can be unknown, charging, full, unplugged. It doesn't show that false is a possibility.
If I plug it in, it jumps from false to true. Wouldn't that mean that true = charging and false = unplugged ?
If I plug it in, it jumps from false to true. Wouldn't that mean that true = charging and false = unplugged ?
yes, maybe a misunderstanding when I use the term "loading"....
I used the locationTemplate of https://transistorsoft.github.io/react-native-background-geolocation/interfaces/react_native_background_geolocation.config.html#locationtemplate This variable is evaluated for variables using Ruby erb-style tags... And I'm not a expert with that.
I will add it the next update
Anything I can do to help test, tell me. I will likely have more when I'm more mobile.
I just asked the team that manages the react-native-background-geolocation API, it seems that we can't introduce logic in the locationTemplate. I need to figure out how to hack it.