Recent content by brongle

The best starting point would be the svag-mini repository, that implements all of what you want above. Because I built that on the ESP32 BLE stack it doesn't contain any of the PIN generation code because I found that wasn't required. I'd like to publish the app but I decided to wait as Stark...

I'll take a look when I get a chance, I haven't tested on the Arkenstone in a while so it's very possible I broke something.

Pretty sure 1.4.0 is the bugged release, I think 1.5.0 is the latest now although I'm not sure how they are rolling things out.

Seems like me either, and it's not like I've done anything to deserve it... 😅 I think they've been basically spending 100% of their effort aligning everything to the new VCU and firmware so that the MX/EX/SM can all share the same work and benefits. Now that they've finished that work with...

Ah! I think Alta was on to something with the simplicity and usability of their interface, its a shame Stark wants to be so fancy at the cost of any functionality... Are you pulling data from CAN or BLE?

Ah yes that was some of the inspiration for sure! I think their approach is probably better in many ways as tapping into the CAN interface lets you still connect the phone, and probably access some more data as well. I've been meaning to poke into the EX connection hub to see if there is an easy...

Slow rollouts of updates like this help catch potential issues before they cause wide-spread problems. The issue folks are seeing with the battery warnings is why you want to take an approach like this. While Stark probably should be doing a better job at internal QA you still cannot test for...

I've been wanting to build this since before starting on Svag, but it made more sense to get a better understanding of the BLE interface and build something more widely usable first. Right now this is a very early prototype which just integrates a 20x04 LCD and a small ESP32-C3 powered via a USB...

It's based mostly on mileage. I believe this time they are also rolling out the firmware to MXs first, I've seen a lot of people on old bikes having issues with battery warnings popping up now (which seems to be a bug).

Does v1.6.1 (build #36 on android) fix connecting to your MX by chance? It should be available in closed testing.

Stark does a slow roll-out of firmware updates based on bike usage, so far I've only seen 1.4.0 on an MX. I'm guessing us higher use EX riders will see it in the next week or so.

I have a new build pending review on Android/iOS which should hopefully fix the MX issue. It also heavily changes how the app syncs some data over Bluetooth to be a bit nicer to the VCU and also use a fair bit less phone battery. Some screens will now take a moment to load in depending on what...

Ah yea thats the one sorry, I should be more specific when talking about versions... 😅

What version are you running? I think I know what I broke but just wanna double check. Ah interesting, I guess we will see what it holds. Good to see the app still works and connects on that firmware version. Does he have a lot of ride-time on his MX?

The EX/1.2 drivetrain & pack have supported 6.6kw charging from the getgo, but it was only enabled for some users (mostly Stark staff and I guess a few competitors). I'm guessing this is either a bug on their side with the account-flagging or they are potentially slowly rolling out a higher...