Originally Posted by Hammz

Most of the radio issues are probably really BCM issues. Remember, there is no direct connection from the handlebar controls to the radio except via the BCM. While the touch screen should be internal to the radio, all volume & mode inputs are from the BCM. Don't know how fast the BCM processor is, but from the delays for simple things like activating the horn, it seems to be fairly slow to me.

I agree that the voltage drop when starting the bike seems to affect the radio boot process, particularly if you don't wait long enough for the boot process to complete; the disclaimer accept screen comes up long before the boot process completes. This leads to all types of odd issues, many times repeatable, but sometimes not.

I have been turning the ignition switch to ACC to let the BCM/radio boot up while I'm gearing up. I use ACC because it boots fine in this position & uses less battery energy because the headlight/tail lights are off (TP side markers are on, but still less draw than in ON position). Once I'm ready I check to verify the boot has completed by checking status line for bluetooth, CB, intercom icons are there, then select the NAV button to verify the NAV is also ready. When confirmed, I turn ignition switch to ON, wait for dash warning lights to go out, then start the engine. After it's started, I then go into the menu system to cycle the CB off then on (failing to do this keeps the CB inoperative when the transmit button is depressed).

This sequence probably takes longer to do than to read, so learn patience; you should find your self having less infotainment system issues if you can do this. If you ride a lot with others, it's going to be hard to wait long enough, but if you turn to ACC before starting to gear up, it helps.

Enjoy your new ride!

Originally Posted by skyhawk85u

I heard about the CB bug before but on a group vacation last week I never bothered to turn it off and never had a problem. Occasionally after transmitting on the CB the intercom VOX wouldn't work though. I never did figure out if waiting or transmitting again kicked the VOX back on but it always came back eventually. Due to nav issues I often turn the bike on to ACC to keep the nav alive, especially at a quick gas stop.

Originally Posted by Hammz

To further qualify the CB issue, it was not present in the early version of 1.17.4, but the version of 1.17.4 that I downloaded on 6/26/14 does have the CB issue. I suspect there are at least 2 builds labeled 1.17.4 & the later download was changed in an attempt to shorten boot times by eliminating/modifying some of the original boot up subroutines? In any event, the CB problem is not present in all downloads of 1.17.4 so your experience may differ from mine.

Originally Posted by offthewall

That doesn't sound right to me. Being in the software field, I can't see anyone releasing two different versions of any software with the same version number. It just isn't done. There would be no way to track such a situation. If there were multiple .4's, there would be a different build number or other identifier. There would never be two different software versions with the exact same numbering scheme.

Originally Posted by Hammz

Normally, I would agree, but first hand experience with a 1.17.4 downloaded in Feb 2014 vs a 1.17.4 downloaded Jun 2014, both installed on the same bike, worked differently, consistently. I can't imagine any other reason for this except the downloads were somehow different.

Originally Posted by offthewall

Did you go back and forth and repeat the issue(s) with each version more than once? That is the only way to prove such a thing. There are too many variables involved if you only noticed it one time to make such a conclusion.

Originally Posted by Hammz

If you're asking if I redid the early download, then went back to the later download, I did not. I did the later download to my bike & observed how HDF reported functions worked on my bike. My buddy's bike with the early download consistently functioned differently. After doing the later download to his bike, it functioned the same as mine. The only thing different besides the date of the downloads was the program used to unzip the iso file.

Originally Posted by offthewall

Sorry, it's the ex research scientist in me.

Your conclusion that there are two different .4's is random and not supported by the facts. It's also the unlikely conclusion. You could just as likely conclude that the act of applying the .4 update twice is what fixed your CB issue.