BlueCruise 1.3 Software Update (Coming Soon): Reminder + Tips!

[Deleted member 16048]

How would they know if the OTA update broke something in your car?
It is a software update, does Microsoft know if one of their updates screws something up on your computer?
They can't possibly make everyone's update go perfectly.

There are also automated ways for them to know updates are working. Apple updates will phone home upon completion and before an update begins to keep tabs on the progress. This is how Apple knows how many devices are on the latest version and the pace in which devices are updating.

Furthermore, there have been times where during an update some rollouts are tested and revered, to see what type of completion or failure rates they can expect.

So there are definitely ways, and most of us (End users) will never really know what process they have.

Sponsored

 

[agoldman]

At this point I wish the focus was more on getting more roads BC compatible. Down here in Charleston, SC for instance there are virtually no BC roads aside from the main artery in.

 

[bbulkow]

How would they know if the OTA update broke something in your car?
It is a software update, does Microsoft know if one of their updates screws something up on your computer?
They can't possibly make everyone's update go perfectly.

Microsoft asks people to submit use statistics and crash logs. If you have certain crashes and restarts, information is sent to microsoft (with your permission). They also have user sat surveys ("do you like this thing?") that a lot of people choose to fill out. A lot of people opt-in to user statistics. We generally want to know when something went wrong on our computer (or phone, if you are on Android or IOS there are similar programs) so most people allow for this kind of reporting.

When writing software, you create certain alerts. The most obvious are crashes (internal process crashes, not always full restarts), and you look for "anomolies". You can also send basic use information, and I think there's a question in the car somewhere that says "report use statistics". Let's say most people unlock the trunk from the screen a few times a week. Then, after applying an update, the % of people opening the trunk goes down 50%. They may have broken something. Maybe it's something weird like the button is greyed out. Let's say getting to the screen is really laggy and slow. There's an unexpected change that has to be "root caused" to find the reason. This happens in every software company all the time.

"Aggregate" stats are generally fine. You don't want the privacy liability of storing every single button press - but on the other hand, sometimes you want to look for correlations, which can require joining stats, so you want to keep an anonymized ID. There are limits to exactly how to do this, because an anonymous ID can be used as an identifier. In most cases, companies will aggregate and throw away the source data. They also tend to keep data only a certain amount of time (again for privacy reasons - it turns out old data is rarely useful - the risk of keeping is greater than the off chance you'll find the data useful)

Sometimes, the root cause is positive. Eg, there's a minor change in the app, and suddenly it's really easy to open the trunk with the app, so people stop doing it in-car, and the users love it. Not a bug. You still go through the root cause program to find out the answer.

Yes, I do this for a living. Every company with a consumer product in market that's got software and is connected will do exactly this. Websites tend to do it, too.

 

[jgcom]

** 2021 Job 1 owners everywhere bitterly laugh **

If there was a button on the fob or app marked "frunk," I'm sure I'd push it from time to time ... just to check that is continues not to work.

 

[RickMachE]

At this point I wish the focus was more on getting more roads BC compatible. Down here in Charleston, SC for instance there are virtually no BC roads aside from the main artery in.

BC handsfree only works on divided highways.

 

[AZBill]

On Jul 31th I received OTA power-up 4.3.6, which I observed to function in the following manner:

1. Interstate highway curves > 40 degrees on longer disable BC.
2. Ping Ponging in the lane of travel is actually noticeably worse.
3. Automated lane changes with a turn signal engaged does not operate.

The Fordpass Update Notice states that "...this completes what we call the Product Improvement Program 21G01". Does this mean I should have BC 1.3? As an end-user this Notification Description has a lot of words in it but not a lot of information that would help me understand what expectations I should have and what features are available to me in my Premium AWD w/ExtBatt.

4.3.6 is not BC 1.3. I got it on July 28 and have not noticed any difference in performance. For item 1 in your list, maybe they added some additional areas to the map. I only notice ping ponging under two conditions; high cross winds and sharper curves. Otherwise for me performance is normally very good.

 

[hack-e]

We're down to ~5.5 weeks until the end of Summer. Someone should be getting 1.3 soon. Please let it be me. I have a week of travel next week.

 

[MacherAWD]

We're down to ~5.5 weeks until the end of Summer. Someone should be getting 1.3 soon. Please let it be me. I have a week of travel next week.

Did you get 5.1.1 last night? Rumor has it that is the start of the BC rollout with many more to follow.

 

[hack-e]

Did you get 5.1.1 last night? Rumor has it that is the start of the BC rollout with many more to follow.

No, I didn't. Fingers crossed?.

 

[DadzBoyz]

Right now, 5.1.1 seems to be an Early Access program release.
That said, I've only been in EA about 3 months and have not received it yet. It's probably being released in waves. Hope to see it soon.

 

[lwilliams0514]

Dropped off my MME for the brake contact recall and the 1.3 BC update showed up as a recall to perform so they are doing that too. Now if they can just get the damn frunk button added I will be all set!

 

[generaltso]

Dropped off my MME for the brake contact recall and the 1.3 BC update showed up as a recall to perform so they are doing that too. Now if they can just get the damn frunk button added I will be all set!

Neither of those are recalls. There’s a good chance that the BC update is just the original one that enabled BC (likely not 1.3). Dealers get very confused by this.

 

[TheVirtualTim]

Right now, 5.1.1 seems to be an Early Access program release.
That said, I've only been in EA about 3 months and have not received it yet. It's probably being released in waves. Hope to see it soon.

My '21 received 5.1.1 (it is in Early Access) late in the evening on August 16. I did not realize at the time that it was an Early Access release.

The BC 1.0 updates did roll out in waves -- even within the Early Access Program. Although, to be fair, Ford didn't have nearly as much experience rolling out the updates. I have no way of knowing ... but my "guess" is that with experience, they'll be willing to roll out more cars per wave and get through the updates faster -- at least I hope that will be the case.

With any luck ... they'll sneak in a BCM and GFM update so I can finally use my frunk. ?

 

[lwilliams0514]

Neither of those are recalls. There’s a good chance that the BC update is just the original one that enabled BC (likely not 1.3). Dealers get very confused by this.

I already had BC when I went in. Got it in an OTA late last year I think. I specifically asked if it was the update and they said yes, but the advisors have been wrong before. lol.

The battery contact issue is TWB 22-2143 to be specific. They have to replace the e-parking brake connecters at the wheels.

have over 81k miles and it was time for front brakes.... glad I have ford premium maintenance which is covering the brakes.

 

[RT1 MME266]

Let's roll out already!!

Sponsored