[230i]

That’s great. I submitted a report too. The only caveat I would make “acknowledged by BMW as an issue” is not accurate. BMW acknowledges it’s a navigation issue. They don’t acknowledge it’s a GPS issue.

 

[230iWhite]

Received a response from higher ups. Won’t post here because my account before was suspiciously revoked. Happy to send anyone the letter via DM.
and if you don’t see me again it’s not because I voluntarily left.

Basically they are completely rejecting that it is a GPS issue. They claim it’s only when you use a map app. They reject the notion it’s a safety issue. They won’t address my specific complaint regarding the MY BMW app having faulty locations.

I’m unsure if they know the ramifications but won’t say. Or really don’t realize it.

 

[euro_i4]

I wonder if this is why BMWs switching to iDrive 9 (Android OS) so fast?

 

[ssh]

I wonder if this is why BMWs switching to iDrive 9 (Android OS) so fast?

Honestly, this fix is not hard at all. I do not understand the hesitancy by BMW. Yes, I'm sure they have to test it, but I'm equally certain that the analysis of the issue will show that the dead reckoning and location information is being corrupted or else simply miss-formatted before being sent to the CarPlay device. This is the kind of thing I've done off-and-on for decades; let me at the blasted code and we'll find it in an hour or two.

 

[FirmRip]

It could even be easy for Apple to fix, too - just change the GPS source from the car to the iOS device. But that may be more difficult with the way they wrote the wireless CarPlay spec.

 

[ssh]

It could even be easy for Apple to fix, too - just change the GPS source from the car to the iOS device. But that may be more difficult with the way they wrote the wireless CarPlay spec.

Not going to happen. The spec is very clear and hasn’t changed for 5+ years. This is 100% on BMW.

 

[cognac4]

Honestly, this fix is not hard at all. I do not understand the hesitancy by BMW. Yes, I'm sure they have to test it, but I'm equally certain that the analysis of the issue will show that the dead reckoning and location information is being corrupted or else simply miss-formatted before being sent to the CarPlay device. This is the kind of thing I've done off-and-on for decades; let me at the blasted code and we'll find it in an hour or two.

Couldn’t agree more! Maybe a resource allocation decison — iDrive 8/8.5 is end of road for current code base so all resources are on iDrive 9?

 

[kpsuperplane]

Couldn’t agree more! Maybe a resource allocation decison — iDrive 8/8.5 is end of road for current code base so all resources are on iDrive 9?

I think the annoying part is just that this takes so few resources, as @ssh said this fix would likely take less than an hour or two for any engineer who works on the system. It's just somewhere along the corporate pipeline this isn't getting passed along, be it feedback/bug report intake, project prioritization, Q/A backlog, etc...

 

[kpsuperplane]

But it also begs the question - this seems to affect all iDrive 8 users, and surely plenty of BMW employees and execs use iDrive 8. Have none of them run into this? Is this issue specific to the Americas?

 

[vancity_330i]

Couldn’t agree more! Maybe a resource allocation decison — iDrive 8/8.5 is end of road for current code base so all resources are on iDrive 9?

This is the concerning part - will they ever get around to fixing this. And BMW hasn't even made it very clear which cars on iDrive 8 are getting 8.5, so that's another thing (news articles seem to suggest the 2/3 series, M3/M4 will miss out?).

But it also begs the question - this seems to affect all iDrive 8 users, and surely plenty of BMW employees and execs use iDrive 8. Have none of them run into this? Is this issue specific to the Americas?

Does look like it's NA specific. The SIB earlier was from the EU and the complaints I've seen here and in other forums all look like folks from NA.

 

[230iWhite]

But it also begs the question - this seems to affect all iDrive 8 users, and surely plenty of BMW employees and execs use iDrive 8. Have none of them run into this? Is this issue specific to the Americas?

This is the concerning part - will they ever get around to fixing this. And BMW hasn't even made it very clear which cars on iDrive 8 are getting 8.5, so that's another thing (news articles seem to suggest the 2/3 series, M3/M4 will miss out?).


Does look like it's NA specific. The SIB earlier was from the EU and the complaints I've seen here and in other forums all look like folks from NA.

Wasn’t there some gossip earlier back that they were trying an SIB in Europe first? I showed my service department this info and he kinda laughed at me.

 

[ssh]

Proof that this is not US (NA) only, that there is a fix, and that they are behaving foolishly.

 

[FirmRip]

Wasn’t there some gossip earlier back that they were trying an SIB in Europe first? I showed my service department this info and he kinda laughed at me.

Here's a link to the reddit comment referenced in the post:
https://www.reddit.com/r/BMW/comments/111gtfz/_/j8h74d4

 

[230iWhite]

Proof that this is not US (NA) only, that there is a fix, and that they are behaving foolishly.

Is this something they really may never fix and hope we stop asking? Or do believe there will eventually be a fix even if it’s summer?

 

[Doc Olives]

But it also begs the question - this seems to affect all iDrive 8 users, and surely plenty of BMW employees and execs use iDrive 8. Have none of them run into this? Is this issue specific to the Americas?

I think a key factor in all of this is the intermittency of the issue. It can affect all iDrive 8 users, but it doesn’t. This thread on i4talk is the biggest collection of people across model type across the whole internet experiencing the issue.

I’m lucky; I’ve had it happen 3 times in 3 months. So 99%+ of the time I haven’t had the issue. Without any basis to say so, I expect the VAST majority of people with iDrive 8 have either never had the issue or just thought it was a one time glitch and for them it was. Absolutely sucks for those who have it as a recurrent issue, but (AND I AM NOT DEFENDING BMW ON THIS!), they are absolutely looking at percent of owners with what they consider a minor technical issue. From a materiality perspective, it’s just not an issue to BMW.

Separately, for those who understand the technical piece, does the intermittency impact the complexity of the fix?

 

[ssh]

Is this something they really may never fix and hope we stop asking? Or do believe there will eventually be a fix even if it’s summer?

I fully expect there to be an update.

 

[ssh]

I think a key factor in all of this is the intermittency of the issue. It can affect all iDrive 8 users, but it doesn’t. This thread on i4talk is the biggest collection of people across model type across the whole internet experiencing the issue.

I’m lucky; I’ve had it happen 3 times in 3 months. So 99%+ of the time I haven’t had the issue. Without any basis to say so, I expect the VAST majority of people with iDrive 8 have either never had the issue or just thought it was a one time glitch and for them it was. Absolutely sucks for those who have it as a recurrent issue, but (AND I AM NOT DEFENDING BMW ON THIS!), they are absolutely looking at percent of owners with what they consider a minor technical issue. From a materiality perspective, it’s just not an issue to BMW.

Separately, for those who understand the technical piece, does the intermittency impact the complexity of the fix?

You've got it. It doesn't show itself all the time for many people.

...and yes, any intermittent issue is always more challenging. If it can't be replicated, it can be more difficult especially for a larger company. My organizations we would look at it differently: check the signals being sent from iDrive over the CarPlay protocol, check the way the GNSS data are consolidated by the code, and so on. However, if there are also issues with the native nav, that actually makes it more challenging.

 

[cognac4]

I’m new to “SIB”s, which I assume to be Service Bulletins, and to BMW software releases and how and when they are disseminated to dealers (vs OTA to customers). But didn’t someone earlier in this thread report that they received the 22-11-530 software update from their dealer and that it didn’t fix the problem.

 

[ssh]

I’m new to “SIB”s, which I assume to be Service Bulletins, and to BMW software releases and how and when they are disseminated to dealers (vs OTA to customers). But didn’t someone earlier in this thread report that they received the 22-11-530 software update from their dealer and that it didn’t fix the problem.

They got an iDrive update, but the conjecture is this is more than iDrive and requires a module update for the TCB.

 

[tonyquan]

They got an iDrive update, but the conjecture is this is more than iDrive and requires a module update for the TCB.

Is this the SIB for this issue (filed with the NHTSA)? https://static.nhtsa.gov/odi/tsbs/2022/MC-10230740-9999.pdf

I've had this issue occasionally so was looking into it.