brongle's latest activity

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...

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...

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...

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...

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...

Hmmm and you checked with the bike on? It's possible they don't do/mean anything yet and they just added them for testing with newer...

Ah I put them on the battery page under the service menu, should look something like this: The field names are basically directly...

For the most part yes, the internal builds seem to be 99% automated although sometimes they do take a bit of time to be "approved". The...

Yep, I sent you off a link to the latest build. And the issue is with my app, the Stark app doesn't reveal the internal pack layout (I...

The EX phone is produced by a Chinese company Shenzhen Emdoor Information Co., Ltd. and Stark uses their MDM (Mobile Device Management)...

Yea the numbering is probably off by one. Bike is probably off so the contactors are open, that measurement will be garbage in this...

I don't think 14/47 with 17s would even get close to 154kmh on the current motor so I wonder how inflated that number is. It's a...

With the Stark phone off and the Svag app exited out everywhere I would try a generic BLE scanner tool and see if your bike shows up in...