Andrew Rowson
Andrew Rowson
That message comes from https://github.com/owntracks/android/blob/master/project/app/src/main/java/org/owntracks/android/services/MessageProcessorEndpointHttp.java#L233, which is where it times how long it takes to send the HTTP request. As you can see, it simply records the time, sends the...
The hard bit here is all the pesky UI work. But d think me should be able to do this.
If you're able, could you also see if you get a different behaviour if you have an app such as Google Maps open in the foreground whilst driving?
> > Right, and that appears to corroborate the theory that the device cannot cope with updating the map and POSTing the data. > > I do not rule out...
> > > > Right, and that appears to corroborate the theory that the device cannot cope with updating the map and POSTing the data. > > > > >...
If you're able to test to see if you get the same behaviour on the same devices across different versions of the app (the apks should be available on the...
It's an interesting idea, but I would worry about the complexity of both the implementation and the UX. What we're potentially talking about is building a rules engine that could...
> * [ ] still uses protocol MQTT v3.1, not MQTT v3.1.1 Just pushed a new version that changes this default. It won't change it for users with an existing...
> > > Now testing version 22013: > > > * [x] now each `PUBLISH` causes the MQTT connection to be re-initiated > > does not happen anymore How weird....
Booo. Let me reproduce.