Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[MajorMajor]

On Android it says:

 What's New
* Crash fix for pre-5.0 (Lollipop) devices.
* Battery tab should now be quicker to load.

[ultrarnr]

I downloaded the iPhone App last night. They didn't fix all the issues as it still doesn't show time till charged.

[Lenny]

Also got the update on iOS. I will check on any improvements this afternoon.

[JaimeC]

Just installed it this morning on Android but haven't noticed any differences yet.  I won't know until I plug the bike back in tonight whether or not the "Time to Charge" problem has been fixed.  Has anyone else noticed?

[JaimeC]

Okay, I just noticed one thing with the new app:  It seems to be able to find and connect to the bike a LOT faster than it used to.  I didn't quite notice it this morning, but this afternoon when I went out to lunch it repeatedly found and connected to the bike almost immediately after initializing.  Previously it would take a minute or two (and there were times when it couldn't find it at all and I had to re-pair the phone to the bike).

Anyone else notice this?  Or am I imagining things?

[Richard230]

Okay, I just noticed one thing with the new app:  It seems to be able to find and connect to the bike a LOT faster than it used to.  I didn't quite notice it this morning, but this afternoon when I went out to lunch it repeatedly found and connected to the bike almost immediately after initializing.  Previously it would take a minute or two (and there were times when it couldn't find it at all and I had to re-pair the phone to the bike).

Anyone else notice this?  Or am I imagining things?

Both the original app from 3 years ago and the new version, when used on my 2014S, connects in about 10 seconds and always has.

[JaimeC]

Both the original app from 3 years ago and the new version, when used on my 2014S, connects in about 10 seconds and always has.

I was never that lucky. 

[Fred]

I'm a bit disappointed with the range. I can't connect from the house to my bike in the garage when it's about 3m away. Bluetooth should have a better range than that.

[SteveInNC]

I'm a bit disappointed with the range. I can't connect from the house to my bike in the garage when it's about 3m away. Bluetooth should have a better range than that.

Tell me about it. I can't keep a connection with my bike directly below me in a basement garage. Literally directly below where I plug my phone in.


Sent from my iPhone using Tapatalk

[Richard230]

I need to be about 5 feet away from my bike for Bluetooth to connect.

[JaimeC]

Aannnnd now that I had a chance to check it... NO CHANGE regarding the "Time to charge" read out.  Why can't they get that fixed???

[Lenny]

2016 FXS, iOS 10.3.1, iPhone SE:

-Bluetooth connects a lot faster now
-riding data is updating while riding for the first time, although there's some latency
-customs settings change seems more stable and reliable
-not randomly losing connection anymore, at least at the first look

Will check charging later and post an update then

Update: remaining charge time still not working, showing 0:00. On the dash -3 amps are flickering up sometimes, but that's it.

[Shadow]

MYM:    ZeroMY2016DSR
FW:     49 rev 3
Phone:  Android 6.0.1
App:    1.5.7
SoC:    Yes
TtFC:   No
Trip:   No, reset is not saved
MBBlog: Yes
BMSlog: "Failed fetching log type: BMS1" warning notification refers to the powertank I don't have one installed. Problem, gets to 100% status and then an error "Failed fetching log type: BMS1". It does provide MBB and BMS0 logs.

[anton]

Model: 2016 SR
Firmware: 50
Phone: Android 7.1.2

Reset is not saved
Time to charge is still 0:00
Connectivity seems to take about the same time, sometimes doesn't connect (just like older version did), requiring force-quitting the app.

[gyrocyclist]

 Model: 2016 SR
Firmware: um, how do I find this? Had it serviced three weeks ago, so it's recent ...
Phone: iPhone 6, 10.3.1

I'm now getting readouts in Drive mode -- before they were all zeros. Yay!

BTW, don't put too much stock in the Release Notes. I work with software (HPC, national lab), and my experience is that there are many, many things that get fixed/updated that never get mentioned in the release notes.

Bottom line, so far I'm pleaased with the update. That said, I haven't tried D/L logs -- which failed (for me) using the previous version.