As announced. Many fixes, and new speed control for average speed control systems, a new research tool, and mode that might work a lot better for ELM based dongles.
Author: Jeroen Meijer
- Growth: 3.1% for 30 days, 60% for a full year.
- ANRs and crashes are very low, way under “bad behavior” threshold. Attacking them systematically has payed off.
The Tire IDs (and pressures) are conveniently labeled Front Left, Front Right, etcetera, but the car has no separate receivers for the individual wheels. It just sees four values coming in and checks it. Enough for the warning light, but not for us users. We want to make sure the pressure is stated for the correct wheel, and the ID for the correct wheel is displayed.
We’re in a pickle a bit as we received a report that the Rear IDs in CanZE are swapped, while we have followed available documentation. As none of the developers have a TPMS equipped car, it’s impossible to experiment. So in case you are a “tire guy” with a TPMS equipped ZOE, please do some experiments and confirm (or deny) said report. Thanks!
In the next release we plan to introduce dark mode for Android 9 and 10 devices. It will have a dark, light and System (as in, follow what Android does) mode.
Until now, we’ve been keeping CanZE compatible with API level 15, meaning Android 4.0.3. For reference, we’re talking Samsung S2 era, early 2012 phones. To make dark mode work without over-complicating the code, we have to let go of supporting Android 4 and make API level 21 the minimum requirement. These are late 2014/early 2015 phones. The number of active users below API level 21 is approximately 2.5% of the active users, so we feel this is a fair compromise.
The sun-setting of Android 4 support has been announced starting today in the news bar. If you run CanZE on an Android 4 device it will no longer receive updates, but it will still run the older versions.
Things have been slow as vacation progressed. And of course now work is competing. But that doesn’t mean things have halted. A new release is in the making, though it mainly fixes language and edge case stability issues. No new functionality.
- Growth has slowed down but is still going on quite nicely: 2.4% in the last 30 days and we’re now at about 5300 active Android devices
- ANR’s are virtually zero (one user impacted)
- Crashes are down to a record low 0.15%, less than one per day. This is half of the peer median. And half of those are Bluetooth related.