BlueAure

I recently found out about Axios which does short bullet point coverage of just the interesting/most important parts of stories. It seems to be a bit biased liberal overall, but being able to get the highlights without wasting time reading all the fluff is pretty convenient.

I just use a cheapo Bluetooth ELM327 clone from Amazon. I got the second cheapest one that reviews said worked and after a bit of fiddling to get it paired, it seems to work alright for the occasional issue.

It’s the best one that I’ve found since the old ES File Explorer sold out and became adware

AndrOBD for connecting to my car OBD2 Bluetooth adapter. It lets you read any diagnostic codes and let’s you reset warning lights.

Aegis for managing 2FA tokens. Weawow for weather. MiXplorer for file management.

Purdue University still has a campus-only file sharing network called DTella that’s DC++. It been getting smaller, but there were a few members that shared 50+ TB at one point.

I don’t think so. It might have been delisted as I don’t see it either. Regardless, it’s OSS so you can get it from the GitHub repo. https://github.com/hidroh/materialistic

I use Materialistic currently.

Assuming that there is at least some amount of slippage between the wheel and ground, it seems to me that you’ll need to regularly check the ToF sensors anyway. I’ve found that encoders are fantastic for a lot of things, but not so much for measuring distance because of the problems you’ve described. Perhaps a recurring local check on a reduced set of points to verify location then forward the full cloud less often for further remote processing? It really sounds like you have a tradeoff depending on whether you value accuracy of location or accuracy of wheel rpm (analogous to speed). Using both would give you a nice way to calculate the ideal motor rpm to minimize slippage in a surface agnostic way.