be careful how you mount it, make sure that there is enough dampening. people have had issues with excessive vibration and damaging the OIS and focusing motors in the cameras.
~15,000km with this phone. Tens of thousands more on older phones all the way back to the 5s. Which of course wasn't nearly as good: no always-on display and had to use the Quad Lock "poncho" in the rain.
what is insane, is that ble is largely unsecured in modern implementations. when testing, i kept picking up everyones whoops/assorted ble devices spamming out heart rate data to whomever wanted to connect.
note using a phone mounted to a bike or motorcycle can cause damage over time to the camera assembly especially the motors used for OIS. depending on how much you ride or the quality of the roads you ride, it could be an issue.
your project does look amazing. sorry that the appstore team is holding things up.
RE: ANT+, a hackrf one and fable was key to the hack.
I find colour useful for a navigation map, mostly. I think the 4-colour eInk displays would be plenty for that, although they have refresh constraints iirc.
A good UI design would mostly avoid the need for colour.
For me, it matters only when I'm futzing with the map: dragging around or zooming. For the rest of the info on the display, anything more than 500ms interval seems like a waste of power.
PMTiles is the underlying technology I believe. We use it on oceanconnect.ca and in my opinion it’s pretty awesome. Very efficient to store and retrieve, and cut our S3 PUT request costs by something like 90% across the project.
reply