TFT and General stuff on the latest TFT/App update
This will change as I and others learn about the new bike, so, if we put the pieces of knowledge in a common location we can all collectively become wiser.
What I know so far, the four buttons have permanently assigned functions.
Button Assignment
1 Pause or play music, when you stop the bike the music is paused. When you start it again, you have to navigate through the TFT to music to start again
or push button 1
2 Heated grips and seat, not played with this.
3 Change audio output, this will switch from Radio to music on bike with a radio, if you don't have a radio it will bring up the music screen so you can push
the wonder wheel to move to a different track.
4. Displays Map in full screen, don't really use this.
TFT
Its pretty straight forward to navigate down to menu's and left to right. When you have a sub menu, say music open and you push the menu button up to return to the main screen, pushing the down menu will return you to your last sub menu.
There is no temperature gauge on the TFT all you now get is a warning light if you are too hot, engine temperature is shown on the vehicle sub menu.
There is nothing to show the damping on the TFT, if you push the right button on the handlebar to change engine modes, dynamic will change the damping to dynamic, sometimes when I go over bumpy roads I want to change the damping to Road, this was easy on the older bikes and K16 as it was the first option on the menu button, but now I have to go through menu's to find the damping and change it, when I do change it there is nothing on the TFT to tell you what you have set it to, BTW there is only Road or Dynamic damping as on previous bikes.
When on the main screen pushing the wonder wheel right will open up the split screen and there are four displays for the split screen, trip 1 and trip 2 then map and music.
Pushing the menu button up shows user info e.g. fuel left, tyre pressure etc. You can choose from a list of options.
Music.
Its playing fine from my phone, but you have to remember to switch on your music app. I had a problem with my Sena SRL getting the volume high enough to hear it, I also have a Sena RC 3 remote on the handlebar to change volume, the wonder wheel does not do this. I contacted Sena and they said the wonder wheel is propriety to BMW and that's that. I know BMW said they made the API available, but who knows. Anyway, I think I have the volume fixed, when you have it all connected and working push the volume on you phone to max volume. I had to push the volume up button on my Galaxy S10 to do this.
Phone
I had an issue with making and receiving calls, as in, the phone connected, but no audio or mic. However, it worked yesterday, so a leprechaun must have fixed it when I wasn't looking.
Reference phones, we all now have a dilemma. We used to have dedicated Sat Nav's that could play music and could be locked into the bike when we had a lunch break, coffee etc. Now we have our mobile phone's locked in a cupboard. I like my phone on my person when I go for a coffee etc. Maybe phone my wife or check emails. Now, I have to remember to take the phone out of its hidey place. Yesterday when I went to the dealer he took the bike to check the TPMS and the phone went with him, so that was that, twiddle thumbs time.
So, I am contemplating getting a second phone for the bike, (bit of back to the future), since my phone is now my sat nav etc.it is essentially my old Nav Vi and I don't want to be putting in in and taking it out of its hidey hole all of the time, in addition, what happens if I drop it and break it.
Of course there is a benefit here, I will have two phones on my trips so if I break one, my backup will be in the cubby hole.
To be continued by me and I hope others.........................................................................
What I know so far, the four buttons have permanently assigned functions.
Button Assignment
1 Pause or play music, when you stop the bike the music is paused. When you start it again, you have to navigate through the TFT to music to start again
or push button 1
2 Heated grips and seat, not played with this.
3 Change audio output, this will switch from Radio to music on bike with a radio, if you don't have a radio it will bring up the music screen so you can push
the wonder wheel to move to a different track.
4. Displays Map in full screen, don't really use this.
TFT
Its pretty straight forward to navigate down to menu's and left to right. When you have a sub menu, say music open and you push the menu button up to return to the main screen, pushing the down menu will return you to your last sub menu.
There is no temperature gauge on the TFT all you now get is a warning light if you are too hot, engine temperature is shown on the vehicle sub menu.
There is nothing to show the damping on the TFT, if you push the right button on the handlebar to change engine modes, dynamic will change the damping to dynamic, sometimes when I go over bumpy roads I want to change the damping to Road, this was easy on the older bikes and K16 as it was the first option on the menu button, but now I have to go through menu's to find the damping and change it, when I do change it there is nothing on the TFT to tell you what you have set it to, BTW there is only Road or Dynamic damping as on previous bikes.
When on the main screen pushing the wonder wheel right will open up the split screen and there are four displays for the split screen, trip 1 and trip 2 then map and music.
Pushing the menu button up shows user info e.g. fuel left, tyre pressure etc. You can choose from a list of options.
Music.
Its playing fine from my phone, but you have to remember to switch on your music app. I had a problem with my Sena SRL getting the volume high enough to hear it, I also have a Sena RC 3 remote on the handlebar to change volume, the wonder wheel does not do this. I contacted Sena and they said the wonder wheel is propriety to BMW and that's that. I know BMW said they made the API available, but who knows. Anyway, I think I have the volume fixed, when you have it all connected and working push the volume on you phone to max volume. I had to push the volume up button on my Galaxy S10 to do this.
Phone
I had an issue with making and receiving calls, as in, the phone connected, but no audio or mic. However, it worked yesterday, so a leprechaun must have fixed it when I wasn't looking.
Reference phones, we all now have a dilemma. We used to have dedicated Sat Nav's that could play music and could be locked into the bike when we had a lunch break, coffee etc. Now we have our mobile phone's locked in a cupboard. I like my phone on my person when I go for a coffee etc. Maybe phone my wife or check emails. Now, I have to remember to take the phone out of its hidey place. Yesterday when I went to the dealer he took the bike to check the TPMS and the phone went with him, so that was that, twiddle thumbs time.
So, I am contemplating getting a second phone for the bike, (bit of back to the future), since my phone is now my sat nav etc.it is essentially my old Nav Vi and I don't want to be putting in in and taking it out of its hidey hole all of the time, in addition, what happens if I drop it and break it.
Of course there is a benefit here, I will have two phones on my trips so if I break one, my backup will be in the cubby hole.
To be continued by me and I hope others.........................................................................
1661 - 1680 of 1717 Posts
Just did update, now at 4.3.1 (431010)
Seems I've forgot where to look for this update (4.3.1) on my iphone... any hintsThe 4.3.1 update is also now available for iOS.
Release notes state the usual “This update contains stability improvements and bug fixes”.
Thanks,
edit.. seems I'm not the only one trying to find the update for the IOS system
Weird, took most of the day, but showed up finally.
weird also,, Mine just showed up too
I know you got it now, but for the future you just long press on the App store icon, you get a menu and pick the updates from there and that will get you right to the updatable apps page.Seems I've forgot where to look for this update (4.3.1) on my iphone... any hints
You’ve obviously sorted it now. BTW app updates will appear at slightly different times dependent on local vetting and bylaws for each different country (and sometimes done deliberately to prevent overload on servers). Also, the iPhone seems to have a random way of looking for ‘automatic’ updates and can take a day or two to spot one. You can force it to check for updates via the method described by The_real_hati.Seems I've forgot where to look for this update (4.3.1) on my iphone... any hints
Thanks,
edit.. seems I'm not the only one trying to find the update for the IOS system
Those running iOS, there really isn’t any mad panic to get this 4.3.1 update - nothing obvious has changed other than the version release number in line with the android version. It really is only a benefit to Android users to fix the bug that removed voice instruction on their previous update.
Hi guys, I was wondering if the connected app uses data while riding? I was thinking it doesn’t because guys are using a bike phone without paying for a phone line, and updating and maintaining the appt via Wi-Fi. Just wanted to make sure
Sent from my iPad using Tapatalk
Sent from my iPad using Tapatalk
As far as I can tell the app will only use data for "live" traffic info, so if you're not concerned about that there's no need for a data connection. I frequently ride through areas where there is no signal and the app doesn't stop working....
I think it also uses data for some searches (poi and petrol stations local to you current location) and weather information. If you go to the menu within the app and scroll down to data privacy, section B describes the features that require data and/or your location sending to a server to obtain information.
My bike still has the original software package the bike came with in August 2021. I went through many of the issues described with disconnecting the map randomly or disconnecting by answering a phone call being the two things that drove me nuts.
I feel many of the issues were on the App side of things because as of today these issues are very rare with the latest version. Way faster connection after shutting the bike off at fuel stops and phone calls don't affect the map anymore.
I feel many of the issues were on the App side of things because as of today these issues are very rare with the latest version. Way faster connection after shutting the bike off at fuel stops and phone calls don't affect the map anymore.
I had been struggling with the Motorrad Connected-to-TFT display issues from delivery to about two weeks ago.
tl;dr -- Upgrading to a newer phone may have made all the difference.
I had gone through every bit of the pain owners on this and other forums have described: trouble getting the Connected app to actually connect to the TFT, having to wait a ridiculously long time for the app to connect when starting a ride, having the app spuriously disconnect while on a ride, and so on. I had communicated repeatedly to the Motorrad Connected team, and had received many suggestions from Spandau including disabling the phone's connection to any "competing" WiFi network before attempting to connect the Connected app to the TFT, turning the phone "off" then back on to purge any possibility of competing apps running background, disconnecting the phone from my Apple Watch, and so on.
I dutifully complied. None of the aforementioned prescriptives had much of an effect on anything. Some days the connection worked pretty well, almost to the point of inspiring confidence in the system. Other days, it was a total crap show. Cumulatively I had spent about 15 hours killing time at the Dealer's while waiting for various bike system firmware updates to get installed. Not one of those updates did anything substantive toward getting the problems cured. Disconnecting from the home WiFi network and watch became a familiar annoyance at the beginning of every ride. Really, BMW, this is the best you can do?
Now for the good stuff. I finally upgraded to a new iPhone 14 Pro about two weeks ago. I had previously been using the iPhone 11 Pro Max. Big difference. Out of (now) habit I was disconnecting competing WiFi and restarting the phone before rides. The starting handshake process was still taking longer than I liked, and I still had to "force" the Connected app to enter Maps Mode sometimes, but once everything was connected and running the Map Mode appeared to be more stable than it had ever been. Could this have been the fix? Well, almost...
The older iPhone 11 had been running Bluetooth 5.1, and the modem firmware was signed at version 4.01.02. The new iPhone 14 is running Bluetooth 5.3, with modem firmware version 1.67.04. I suspect there may have been other changes to the WiFi capabilities of the newer phones under the hood, which I have no ability to discern or comment on.
While riding around my local routes I noticed the TFT would drop out of Maps Mode at some very specific places along the route. The good news now is the setup reconnects on its own within approximately 32 seconds. This, for me, represents a huge breakthrough! At a different point on my regular loop the Maps Mode connection drops, and the entire connection between phone and TFT drops (e.g. no "white arrow" mode even), but the connection restarts on its own within approximately 52 - 60 seconds.
I have taken this same route many times over the past two weeks, and have seen much the same results on each ride, suggesting some unidentified environmental factor as the cause of the interference between the phone and the TFT display. Leaking RF from overhead lines? A nearby amateur radio operator? A hidden microwave or 5G repeater? I have no idea, but the locations of the disconnections are specific within about a 1000 yard radius.
Once I saw this relationship emerging I decided to throw caution to the winds and deliberately NOT make changes to my phone's WiFi status before a ride, and to maybe even wear my Apple Watch. On most of the rides I was not wearing the watch anyway. The App–TFT handshake engaged as expected (okay but still too slow and a bit buggy), but once made the connection was stable -- until passing on of the known drop-spots. The App–TFT would reliably reconnect within 30 - 60 seconds depending on the severity of the disconnect.
The good news for me is the phone - to - TFT connection resets on its own almost all the time. Based on my empirical observations I am going to say the resets are successful 90 percent of the time. But not 100 percent! On yesterday's ride, I was wearing the watch, had a total disconnect of the phone app to TFT (again at one of the known dropout sites), but no reconnection this time around. More research is called for!
Maybe some of this will be helpful...? I am encouraged, but not yet thrilled. The fact that the system handshake restarts on its own most of the time is a big improvement. But I want it to be a 100 percent reconnect.
tl;dr -- Upgrading to a newer phone may have made all the difference.
I had gone through every bit of the pain owners on this and other forums have described: trouble getting the Connected app to actually connect to the TFT, having to wait a ridiculously long time for the app to connect when starting a ride, having the app spuriously disconnect while on a ride, and so on. I had communicated repeatedly to the Motorrad Connected team, and had received many suggestions from Spandau including disabling the phone's connection to any "competing" WiFi network before attempting to connect the Connected app to the TFT, turning the phone "off" then back on to purge any possibility of competing apps running background, disconnecting the phone from my Apple Watch, and so on.
I dutifully complied. None of the aforementioned prescriptives had much of an effect on anything. Some days the connection worked pretty well, almost to the point of inspiring confidence in the system. Other days, it was a total crap show. Cumulatively I had spent about 15 hours killing time at the Dealer's while waiting for various bike system firmware updates to get installed. Not one of those updates did anything substantive toward getting the problems cured. Disconnecting from the home WiFi network and watch became a familiar annoyance at the beginning of every ride. Really, BMW, this is the best you can do?
Now for the good stuff. I finally upgraded to a new iPhone 14 Pro about two weeks ago. I had previously been using the iPhone 11 Pro Max. Big difference. Out of (now) habit I was disconnecting competing WiFi and restarting the phone before rides. The starting handshake process was still taking longer than I liked, and I still had to "force" the Connected app to enter Maps Mode sometimes, but once everything was connected and running the Map Mode appeared to be more stable than it had ever been. Could this have been the fix? Well, almost...
The older iPhone 11 had been running Bluetooth 5.1, and the modem firmware was signed at version 4.01.02. The new iPhone 14 is running Bluetooth 5.3, with modem firmware version 1.67.04. I suspect there may have been other changes to the WiFi capabilities of the newer phones under the hood, which I have no ability to discern or comment on.
While riding around my local routes I noticed the TFT would drop out of Maps Mode at some very specific places along the route. The good news now is the setup reconnects on its own within approximately 32 seconds. This, for me, represents a huge breakthrough! At a different point on my regular loop the Maps Mode connection drops, and the entire connection between phone and TFT drops (e.g. no "white arrow" mode even), but the connection restarts on its own within approximately 52 - 60 seconds.
I have taken this same route many times over the past two weeks, and have seen much the same results on each ride, suggesting some unidentified environmental factor as the cause of the interference between the phone and the TFT display. Leaking RF from overhead lines? A nearby amateur radio operator? A hidden microwave or 5G repeater? I have no idea, but the locations of the disconnections are specific within about a 1000 yard radius.
Once I saw this relationship emerging I decided to throw caution to the winds and deliberately NOT make changes to my phone's WiFi status before a ride, and to maybe even wear my Apple Watch. On most of the rides I was not wearing the watch anyway. The App–TFT handshake engaged as expected (okay but still too slow and a bit buggy), but once made the connection was stable -- until passing on of the known drop-spots. The App–TFT would reliably reconnect within 30 - 60 seconds depending on the severity of the disconnect.
The good news for me is the phone - to - TFT connection resets on its own almost all the time. Based on my empirical observations I am going to say the resets are successful 90 percent of the time. But not 100 percent! On yesterday's ride, I was wearing the watch, had a total disconnect of the phone app to TFT (again at one of the known dropout sites), but no reconnection this time around. More research is called for!
Maybe some of this will be helpful...? I am encouraged, but not yet thrilled. The fact that the system handshake restarts on its own most of the time is a big improvement. But I want it to be a 100 percent reconnect.
This information is very helpful, thanks for sharing. I will add that I'm running an iPhone 12, and magically for the past few weeks, the connection between phone and wifi/bluetooth to the bike has been much more stable. It only dropped once in the past 500 miles, and interestingly enough, it totally disconnected from the bike (as in your example), but then about a minute later, like magic both bluetooth and wifi reconnected. I even rode while listening to the XM radio app on the phone (through the bike), and that also worked flawlessly. I chalked it up to the app update but maybe just some good living. Maybe, I'll even try to wear my apple watch on a future ride but that might be tempting the connection gods too muchI had been struggling with the Motorrad Connected-to-TFT display issues from delivery to about two weeks ago.
tl;dr -- Upgrading to a newer phone may have made all the difference.
I had gone through every bit of the pain owners on this and other forums have described: trouble getting the Connected app to actually connect to the TFT, having to wait a ridiculously long time for the app to connect when starting a ride, having the app spuriously disconnect while on a ride, and so on. I had communicated repeatedly to the Motorrad Connected team, and had received many suggestions from Spandau including disabling the phone's connection to any "competing" WiFi network before attempting to connect the Connected app to the TFT, turning the phone "off" then back on to purge any possibility of competing apps running background, disconnecting the phone from my Apple Watch, and so on.
I dutifully complied. None of the aforementioned prescriptives had much of an effect on anything. Some days the connection worked pretty well, almost to the point of inspiring confidence in the system. Other days, it was a total crap show. Cumulatively I had spent about 15 hours killing time at the Dealer's while waiting for various bike system firmware updates to get installed. Not one of those updates did anything substantive toward getting the problems cured. Disconnecting from the home WiFi network and watch became a familiar annoyance at the beginning of every ride. Really, BMW, this is the best you can do?
Now for the good stuff. I finally upgraded to a new iPhone 14 Pro about two weeks ago. I had previously been using the iPhone 11 Pro Max. Big difference. Out of (now) habit I was disconnecting competing WiFi and restarting the phone before rides. The starting handshake process was still taking longer than I liked, and I still had to "force" the Connected app to enter Maps Mode sometimes, but once everything was connected and running the Map Mode appeared to be more stable than it had ever been. Could this have been the fix? Well, almost...
The older iPhone 11 had been running Bluetooth 5.1, and the modem firmware was signed at version 4.01.02. The new iPhone 14 is running Bluetooth 5.3, with modem firmware version 1.67.04. I suspect there may have been other changes to the WiFi capabilities of the newer phones under the hood, which I have no ability to discern or comment on.
While riding around my local routes I noticed the TFT would drop out of Maps Mode at some very specific places along the route. The good news now is the setup reconnects on its own within approximately 32 seconds. This, for me, represents a huge breakthrough! At a different point on my regular loop the Maps Mode connection drops, and the entire connection between phone and TFT drops (e.g. no "white arrow" mode even), but the connection restarts on its own within approximately 52 - 60 seconds.
I have taken this same route many times over the past two weeks, and have seen much the same results on each ride, suggesting some unidentified environmental factor as the cause of the interference between the phone and the TFT display. Leaking RF from overhead lines? A nearby amateur radio operator? A hidden microwave or 5G repeater? I have no idea, but the locations of the disconnections are specific within about a 1000 yard radius.
Once I saw this relationship emerging I decided to throw caution to the winds and deliberately NOT make changes to my phone's WiFi status before a ride, and to maybe even wear my Apple Watch. On most of the rides I was not wearing the watch anyway. The App–TFT handshake engaged as expected (okay but still too slow and a bit buggy), but once made the connection was stable -- until passing on of the known drop-spots. The App–TFT would reliably reconnect within 30 - 60 seconds depending on the severity of the disconnect.
The good news for me is the phone - to - TFT connection resets on its own almost all the time. Based on my empirical observations I am going to say the resets are successful 90 percent of the time. But not 100 percent! On yesterday's ride, I was wearing the watch, had a total disconnect of the phone app to TFT (again at one of the known dropout sites), but no reconnection this time around. More research is called for!
Maybe some of this will be helpful...? I am encouraged, but not yet thrilled. The fact that the system handshake restarts on its own most of the time is a big improvement. But I want it to be a 100 percent reconnect.
. Good luck to all who have been struggling with these TFT connection issues.I had no end of trouble with my Samsung Android phone. Even after getting all of the TFT upgrades, it really hated connecting with the phone, and failed to work most often when I was leading other riders. I'd be holding everybody up for several minutes, turning the bike on and off, restarting the app, cursing... not much helped. I got a Zumo XT and mounted that, which I found was sufficient for all my needs. (except twisty road routing, it sucks at that)I had been struggling with the Motorrad Connected-to-TFT display issues from delivery to about two weeks ago.
tl;dr -- Upgrading to a newer phone may have made all the difference.
I had gone through every bit of the pain owners on this and other forums have described: trouble getting the Connected app to actually connect to the TFT, having to wait a ridiculously long time for the app to connect when starting a ride, having the app spuriously disconnect while on a ride, and so on.
Now for the good stuff. I finally upgraded to a new iPhone 14 Pro about two weeks ago. I had previously been using the iPhone 11 Pro Max. Big difference.
[reply]
I had been struggling with the Motorrad Connected-to-TFT display issues from delivery to about two weeks ago.
tl;dr -- Upgrading to a newer phone may have made all the difference.
I had gone through every bit of the pain owners on this and other forums have described: trouble getting the Connected app to actually connect to the TFT, having to wait a ridiculously long time for the app to connect when starting a ride, having the app spuriously disconnect while on a ride, and so on. I had communicated repeatedly to the Motorrad Connected team, and had received many suggestions from Spandau including disabling the phone's connection to any "competing" WiFi network before attempting to connect the Connected app to the TFT, turning the phone "off" then back on to purge any possibility of competing apps running background, disconnecting the phone from my Apple Watch, and so on.
I dutifully complied. None of the aforementioned prescriptives had much of an effect on anything. Some days the connection worked pretty well, almost to the point of inspiring confidence in the system. Other days, it was a total crap show. Cumulatively I had spent about 15 hours killing time at the Dealer's while waiting for various bike system firmware updates to get installed. Not one of those updates did anything substantive toward getting the problems cured. Disconnecting from the home WiFi network and watch became a familiar annoyance at the beginning of every ride. Really, BMW, this is the best you can do?
Now for the good stuff. I finally upgraded to a new iPhone 14 Pro about two weeks ago. I had previously been using the iPhone 11 Pro Max. Big difference. Out of (now) habit I was disconnecting competing WiFi and restarting the phone before rides. The starting handshake process was still taking longer than I liked, and I still had to "force" the Connected app to enter Maps Mode sometimes, but once everything was connected and running the Map Mode appeared to be more stable than it had ever been. Could this have been the fix? Well, almost...
The older iPhone 11 had been running Bluetooth 5.1, and the modem firmware was signed at version 4.01.02. The new iPhone 14 is running Bluetooth 5.3, with modem firmware version 1.67.04. I suspect there may have been other changes to the WiFi capabilities of the newer phones under the hood, which I have no ability to discern or comment on.
While riding around my local routes I noticed the TFT would drop out of Maps Mode at some very specific places along the route. The good news now is the setup reconnects on its own within approximately 32 seconds. This, for me, represents a huge breakthrough! At a different point on my regular loop the Maps Mode connection drops, and the entire connection between phone and TFT drops (e.g. no "white arrow" mode even), but the connection restarts on its own within approximately 52 - 60 seconds.
I have taken this same route many times over the past two weeks, and have seen much the same results on each ride, suggesting some unidentified environmental factor as the cause of the interference between the phone and the TFT display. Leaking RF from overhead lines? A nearby amateur radio operator? A hidden microwave or 5G repeater? I have no idea, but the locations of the disconnections are specific within about a 1000 yard radius.
Once I saw this relationship emerging I decided to throw caution to the winds and deliberately NOT make changes to my phone's WiFi status before a ride, and to maybe even wear my Apple Watch. On most of the rides I was not wearing the watch anyway. The App–TFT handshake engaged as expected (okay but still too slow and a bit buggy), but once made the connection was stable -- until passing on of the known drop-spots. The App–TFT would reliably reconnect within 30 - 60 seconds depending on the severity of the disconnect.
The good news for me is the phone - to - TFT connection resets on its own almost all the time. Based on my empirical observations I am going to say the resets are successful 90 percent of the time. But not 100 percent! On yesterday's ride, I was wearing the watch, had a total disconnect of the phone app to TFT (again at one of the known dropout sites), but no reconnection this time around. More research is called for!
Maybe some of this will be helpful...? I am encouraged, but not yet thrilled. The fact that the system handshake restarts on its own most of the time is a big improvement. But I want it to be a 100 percent reconnect.
While riding around my local routes I noticed the TFT would drop out of Maps Mode at some very specific places along the route. The good news now is the setup reconnects on its own within approximately 32 seconds. This, for me, represents a huge breakthrough! At a different point on my regular loop the Maps Mode connection drops, and the entire connection between phone and TFT drops (e.g. no "white arrow" mode even), but the connection restarts on its own within approximately 52 - 60 seconds.
I have taken this same route many times over the past two weeks, and have seen much the same results on each ride, suggesting some unidentified environmental factor as the cause of the interference between the phone and the TFT display. Leaking RF from overhead lines? A nearby amateur radio operator? A hidden microwave or 5G repeater? I have no idea, but the locations of the disconnections are specific within about a 1000 yard radius.
Once I saw this relationship emerging I decided to throw caution to the winds and deliberately NOT make changes to my phone's WiFi status before a ride, and to maybe even wear my Apple Watch. On most of the rides I was not wearing the watch anyway. The App–TFT handshake engaged as expected (okay but still too slow and a bit buggy), but once made the connection was stable -- until passing on of the known drop-spots. The App–TFT would reliably reconnect within 30 - 60 seconds depending on the severity of the disconnect.
The good news for me is the phone - to - TFT connection resets on its own almost all the time. Based on my empirical observations I am going to say the resets are successful 90 percent of the time. But not 100 percent! On yesterday's ride, I was wearing the watch, had a total disconnect of the phone app to TFT (again at one of the known dropout sites), but no reconnection this time around. More research is called for!
Maybe some of this will be helpful...? I am encouraged, but not yet thrilled. The fact that the system handshake restarts on its own most of the time is a big improvement. But I want it to be a 100 percent reconnect.
As much as it irked me to have that potential capability to use the TFT for mapping, it really didn't feel worth the struggle.
Then, as it happened, my Samsung got water in the charging port and pffft it was useless. I ordered a refurb'd Google Pixel 4 phone as a change of pace, because Samsungs never worked that well for me.
Well, lo and behold, the Connected app on the Pixel was a whole different experience! It connected right away, dropped out on rare occasions but reconnected almost immediately. It was actually usable! And it's been pretty solid ever since that time. I wonder if it also uses a newer Bluetooth version...
Talking about specific dropout locations - I had an ancient Magellan GPS. It was crap, and all of them eventually failed to be waterproof, but they were cheap on fleabay. Anyway, I was riding up Peekamoose Road through the Catskills, and didn't notice it wasn't updating until I reached an intersection. It had seriously crashed, I needed a pin to hard reset. I shrugged it off, old GPS, it happens. Three years later, I was on the same road, heading south this time. This time I looked down and saw that it wasn't updating. Got to the end of the road, discovered it needed a hard reset. The next year I was on that road again - same thing. Happened every time I was on that road, and never anywhere else. A friend joked that there must be a secret military SIGINT base nearby.
That is because Pixel runs a pure version of Android, while Samsung and some of the other Android phone makers stick their own bit of software on the top pf the base Android OS and THAT is the bit causing problems. Not enough of us riders for them to take notice and test and correct issues.Well, lo and behold, the Connected app on the Pixel was a whole different experience!
I have no issues now with my now Samsung. Older version yes. Maybe needs an updated version
That's very interesting, it's just a shame that there is no indication of timeline.This was on a Facebook group that I subscribe to, currently the App is on version 4.3.1.
View attachment 182646
When riding using the app for navigation is the speed shown on the TFT taken from the GPS or is it the usual bike speedo, (i.e. 5/10% high).
I suspect it is the latter but would like that confirmed.
Thanks
I suspect it is the latter but would like that confirmed.
Thanks
Confirmed.I suspect it is the latter but would like that confirmed.
1661 - 1680 of 1717 Posts
BMW Luxury Touring Community
A forum community dedicated to BMW Luxury Touring motorcycle owners and enthusiasts. Come join the discussion about performance, modifications, classifieds, troubleshooting, maintenance, reviews, and more!
Full Forum Listing
Explore Our Forums
Top Contributors this Month
View All
williamshanejackson
72 Replies
kbob12
63 Replies
Chayside
40 Replies
Recommended Communities
