3 ms·
Before everyone grabs their pitch forks....as someone who does telemetry tracking devices, 350megs/mo is pretty easy to do and send nearly 0 data, if you do it
by as-j 6y ago
Before everyone grabs their pitch forks....as someone who does telemetry tracking devices, 350megs/mo is pretty easy to do and send nearly 0 data, if you do it wrong....let me explain:
TLS connection setup is ~10k so if do an 1 HTTPS call/telemetry that's 48 calls home/hour. (11,600/10k = 1,160 https connections/day. There's 1440 minutes/day) Of basically calling home every minute and sending not much.
Ok calling home every minute...but maybe when idle that's not bad for notification updates?
We run long do running TLS connections using MQTT, this works for 5-6 figure of units. And our actual usage when we have good cell coverage is around 25megs/mo, including data. But when you have the qty Google and iOS have....maybe that's prohibitive?
- ignoramous 6y agoThat makes me wonder if its Google Play Services (mandatorily preloaded into every Android device) that connects frequently / keeps a connection idle to support things like Push Notifications?
- ggggtez 6y agoAlso, Google Play Services isn't Google Play. "Services" actually encompasses nearly every single app on the device, since it's more or less a library rather than an app. In which case the suit would incorrectly be blaming the store, instead of the real app that is sending the data.
- izacus 6y agoYes, it's the Play Services which handles push notifications and quite a bit of other APIs bound to Google servers as well (e.g. Nearby, Maps API, etc.)