EX Custom iOS/Android App

leadingedge

New member
Likes
2
Location
USA
What do you mean? the dang thing locks every 10 seconds. There is probably a way to extend that, but in stock form, it is really annoying.
I think @OpaTsupa means that the Stark phone does not have a secure locking feature or passcode option.

As far as the screen going off every 10 seconds, you can change the timing in the Android settings to keep the screen on longer if you prefer.
 

drehwurm68

Well-known member
Likes
51
Location
Austria
I think @OpaTsupa means that the Stark phone does not have a secure locking feature or passcode option.
Maybe the MX 1.0 phone does not, but the Arkenstone does and you can enable the desired mode (pin, pattern) in the securities menu. The dashboard will still come up without the locking feature, but for everything else including the Varg app home screen you'll need to unlock it. That's how I've setup mine.

Michael
 

OpaTsupa

Well-known member
Likes
98
Location
MNE
Maybe the MX 1.0 phone does not, but the Arkenstone does and you can enable the desired mode (pin, pattern) in the securities menu. The dashboard will still come up without the locking feature, but for everything else including the Varg app home screen you'll need to unlock it. That's how I've setup mine.

Michael
Then this is the correct answer. (y)


I assumed that since the Stark app needs to stay open the phone can't be locked.
In any case, I felt a bit uneasy when I saw all my data from Google synced into this dubious device. It even sent email notifications before my personal phone.
 

leadingedge

New member
Likes
2
Location
USA
Maybe the MX 1.0 phone does not, but the Arkenstone does and you can enable the desired mode (pin, pattern) in the securities menu. The dashboard will still come up without the locking feature, but for everything else including the Varg app home screen you'll need to unlock it. That's how I've setup mine.

Michael
Excellent information, thanks @drehwurm68
 

brongle

Well-known member
Likes
65
Location
WA
Hmm, it looks like Group #25 is actually group #26, probably starts with group zero?
Yea the numbering is probably off by one.

DC BUS 4V ?
Bike is probably off so the contactors are open, that measurement will be garbage in this case.


I don't know enough to say whether that amount of imbalance in one cell group is fatal. It's very possible a proper bottom balance would recover things to a normal level if that cell group isn't actually damaged and just fell weirdly low. There is of course also a slight chance that going too low on SOC (maybe less than 10%) would brick the pack or cause that cell group to do very bad things. I'd say Stark probably has the best advice for your situation but that might be tricky given I assume you have no noticable impact to performance on the bike.

The latest version of the Stark app (2.6.0) has some internal code they added which shows the VCU is now reporting a bunch of battery fault flags like "battery high diff", "battery cells incomplete", etc. The first one would likely be flagged for your bike and the latter would likely be flagged for the two folks who had missing cell groups. I assume in the (hopefully near) future these flags will be used to display warnings in the Stark app, but I didn't see that added as of the moment.

Are you using the iOS or Android app? I'm going to push a new iOS release right now (probably will take at least 24hr for Apple to approve) since that can be done while the primary app release review is ongoing. For android I need to wait as Google has no mechanism for releasing a new (even just test) version while they are actively reviewing a previous version (for the full public app-store release). The new app version shows these flags in the service -> battery page so you can at least check and see if the VCU has also flagged your battery.
 

leadingedge

New member
Likes
2
Location
USA
I don't know enough to say whether that amount of imbalance in one cell group is fatal. It's very possible a proper bottom balance would recover things to a normal level if that cell group isn't actually damaged and just fell weirdly low. There is of course also a slight chance that going too low on SOC (maybe less than 10%) would brick the pack or cause that cell group to do very bad things.

I'll probably have to cycle and balance my pack down to close to zero and up to 100 again to see if they level out, my bike is still pretty new and I haven't gone lower than about 30% yet.

Are you using the iOS or Android app? For android I need to wait as Google has no mechanism for releasing a new (even just test) version while they are actively reviewing a previous version (for the full public app-store release). The new app version shows these flags in the service -> battery page so you can at least check and see if the VCU has also flagged your battery.

I'm using your Android app. Great work on the app so far @brongle , it opens up a whole new world of monitoring the bike. Much appreciated.
 

leadingedge

New member
Likes
2
Location
USA
Yea the numbering is probably off by one.
Is the numbering off by one in my bike's firmware, or in how the app reads it?

For android I need to wait as Google has no mechanism for releasing a new (even just test) version while they are actively reviewing a previous version (for the full public app-store release).
Would you be able to share the APK file as a PM or with a link, so it can be installed directly?
 

brongle

Well-known member
Likes
65
Location
WA
Is the numbering off by one in my bike's firmware, or in how the app reads it?


Would you be able to share the APK file as a PM or with a link, so it can be installed directly?
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 just gathered that based on the cell groups on the ends of the two pack sides showing different voltages) or how they identify cells so the in-app numbering is just generated based on how the telemetry displays the cell voltages (as an array of 100 values).

Hey @brongle , you can set up your own business 😁

Hopefully we'll see this stuff in the stock app soon and I won't have to :cool:
 

brongle

Well-known member
Likes
65
Location
WA
+1 on this in general.

Could it be that some person has to manually approve every app and every update on Play Store/Apple Store? 😱
Is that even possible?
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 annoying part is that the review is for an older build that I marked for public release on the app store, but while it's in review no other changes go through. It is fair the process is taking longer since its the "first" public release, but still the reviews have been heavily complicated by the app basically requiring a Stark. I've had to go back and forth and then provide various videos showing how everything works with the bike. Google's just been taking their sweet time while Apple seems convinced I need permission from Stark to connect over Bluetooth (lol... fair I guess?) so it's been an annoying process.

I can probably provide a download page for the latest version of the apk in the near future, it's not much more work. I mostly just haven't done this because I assumed the play store process would be easier and I know Google's looking to clamp down on third-party apk installation in the near future.
 

triptych

New member
Likes
4
Location
USA
I can probably provide a download page for the latest version of the apk in the near future, it's not much more work.
if it's open source you can host it on f-droid, an alternative app store for free open source android apps. you can also push updates to users from here.
 
Top Bottom