Search results

Ok, I believe I've sorted that issue out as Google just defaults to US & UK for closed testing. I opened it up to the entire world so hopefully that lets you all see the app and install it now.

I'll take a look when I have a chance later this week, I guess Google is weird about some of this stuff. I thought about doing an Apple watch app since those can use Bluetooth but haven't really played with it at all yet. Eventually I'll get the code for the app open-sourced and then perhaps...

Ok well I suppose it was a bit foolish of me to think that was going to take any time at all, the build has been approved and should be available to those that join the group via the link. I'm not too familiar with the Play Store but I don't believe there is anyway to provide feedback so please...

The Android version is currently pending review by Google, it will hopefully be available for testing after they complete that review. If you'd like to join the Android "closed beta testing" group please visit this page. I'll post an update in this thread when the version is actually approved...

Thought this would be interesting to post as well even though its in early stages, this is a companion website to the app which supports uploading the tracks/recordings (however you want to call it) for visualization. At the moment all the data remains on your local machine and its designed for...

If you want you can play around with my beta iOS app which does display a ton more information from the VCU, and AFAIK shows pretty much everything you can see over the CANBUS/OBD interface but works over Bluetooth. Even then Stark doesn't have a ton of internal diagnostics data when it comes to...

Sadly the icon is displayed by the VCU for a generic fault condition, internally they just condsider it a "malfuction indicator lamp". I'm guessing since Stark sent out a new throttle they've narrowed it down to incorrect throttle position readings. Next steps might just be a VCU swap or perhaps...

My next guess would be maybe the 1.2.8 firmware was the first version on the MX that tracked mileage on the VCU? I'm not sure when you updated or if you remember how much you've ridden since but if its not that then possible the MX version just doesn't have a proper built-in odometer. And yes it...

Correct, the Stark phone only records rides and ride data when connected to the bike. On the EX the VCU has an internal odometer based off (I'm guessing) the motor encoder that is very accurate (it has no concept of hours however). This is the number I display in the UI everywhere. On the latest...

Ok perfect, that'll make it easier to test with. I'll try and make sure it retains support for text scaling while being a bit more... usable!

Yea I'll go through the whole app and try to make it work better on a smaller screen. Do you have your text size turned up by any chance or is that just the default? The Bluetooth performance of the VCU is actually very good, the Stark phone itself is the limiting factor having a super old...

Awesome! I'm glad to hear it works on the MX, I'm guessing that's only true for the latest 1.2.8 firmware but I imagine most people have updated by now. Apple provides no way to automatically provide a pin, it must be input by the user. If it fails to connect in the future you can go into the...

Apple has approved the build I submitted and it's now available for public testing. If you'd like to test it out please join the Public Test Group which is managed via Apple's TestFlight system. Feel free to give feedback either here or via the built-in TestFlight feedback mechanism (taking a...

I haven't experimented with the MX series yet but from my understanding the 1.2.8 VCU firmware is the first version thats the same between MX/EX models. Stark did have something in the release notes mentioning they aren't using the new bluetooth interface for MX models, but I don't know if that...

Interesting! I honestly didn't think the Stark app was showing any faults except for insulation loss. I took a deeper look at the app and that alert should be for the battery overheating. Weirdly enough they show icons for IGBT (inverter) over-temps, battery voltage drops, and battery...

Android will come after I finish getting the iOS version released (unless things really get delayed), purely because I've been actively using and testing the iOS version. While around 95% of the code and functionality is shared, some minor details do have to be sorted out on in a cross-platform...

Thanks for those interested in testing! I'm still working on getting the test build approved, it has to go through Apple's review process and that is sadly complicated by the fact the app interfaces with a Bluetooth peripheral. Apple requires a video of the app being tested alongside the...

FWIW I don't think the battery is really a limiting factor (at least with the new 7.2kwh pack), it's the inverter and motor which will eventually heat-soak and cause throttle cut-outs. I've pushed the EX pretty hard and I've only seen max battery sensor temps of 115F (46C) and that was after a...

I haven't implemented any of the "writing" to the VCU functions like lock/unlock or charging/map config for a few reasons. There is a bit more risk to bricking the VCU once I'm writing data to it even if I keep things identical to how the stock app functions. There is also an issue of access...

I've found the same, on my lighter emoto (erpss 2.0) swapping the seat ended up being a requirement after a while because more than 30-45mins was unsustainable. On the Stark I've pretty much gotten used to it and don't really notice any discomfort unless I'm really out for a long time.