[liebo11]

A couple questions that I’m hoping you guys can answer...

1) I love when I put the car in reverse and the cameras turn with the wheel. Any way to set the “a” (which I have to hit to get it to work) on the screen to be automatically activated when I put in reverse? I feel like it used to be like this a couple updates ago and isn’t anymore...

2) Does anyone notice with the 11/2019 update that the screen on waze/google maps etc. seems a little less clear? Almost like lines going across it or grainy?

Thanks in advance!

[LexxM3]

Originally Posted by liebo11

A couple questions that I'm hoping you guys can answer...

1) I love when I put the car in reverse and the cameras turn with the wheel. Any way to set the "a" (which I have to hit to get it to work) on the screen to be automatically activated when I put in reverse? I feel like it used to be like this a couple updates ago and isn't anymore...

2) Does anyone notice with the 11/2019 update that the screen on waze/google maps etc. seems a little less clear? Almost like lines going across it or grainy?

Thanks in advance!

Funny you should post re: (1) right now. That has been discussed extensively — on US cars, that function became broken (ie camera doesn't follow R/D gear correctly) in 07/2019.xx and didn't get fixed in 11/2019.xx. It does, however, work correctly everywhere other than USA (and Canada, which for this function is coded the same as USA). However ...

... one of our esteemed coding members @ifr suggested a code for me to try. I tried a couple of weeks ago and it didn't fix the issue then. But, I just recorded it again on a whim last weekend and have now noticed this week and carefully/explicitly verified just a few minutes ago that ... ready? ... it did fix it!

That's right, my 11/2019.40 Canadian G05 X5 now correctly follows camera display when shifting from P to R and then D! This is unprecedented and oh what a relief.

Let me discuss this with @ifr privately and we'll post the coding if we agree this is, in fact, working with this coding.

Regarding (2), sounds like it's a CarPlay issue — I will never know anything about it and will never be able to help as I assert CarPlay is a bad idea as a whole after trying to tolerate it really hard multiple times.

[liebo11]

Interesting.

So to be clear, when I hit the “A” in the middle of the virtual car camera thing, it follows the car.

When I don’t, it doesn’t. I’m just thinking it should really be automatic, no?

[LexxM3]

Originally Posted by liebo11

Interesting.

So to be clear, when I hit the “A” in the middle of the virtual car camera thing, it follows the car.

When I don’t, it doesn’t. I’m just thinking it should really be automatic, no?

Yes, that's the bug: A is not automatically selected in this situation on US/Canada cars.

[liebo11]

Oh... that is stupid!

[maczrool]

Never observed this on any version. Currently on 07/2019.53 and have a US model.

[LexxM3]

Originally Posted by maczrool

Never observed this on any version. Currently on 07/2019.53 and have a US model.

That seems unlikely to be accurate as this is extensively documented. For example: https://g05.bimmerpost.com/forums/sh....php?t=1660292 , but there are several other detailed threads.

It is possible that you're reporting camera view behaviour for something other that the "from P to R to D" sequence — this is the sequence we're discussing and nothing else.

If we are on the same page, then you're an anomaly and we want to learn about it. In this case, since you're into coding, I really (really) want your fresh FA, SVT, and all NCD files. Please.

[maczrool]

Sorry, false alarm; missed the P part. I had skimmed through the thread and never really came away with what the problem was given that I always see appropriate view in my use. If I put it P, that’s where it stays until exit the vehicle and and then return. I’ve bounced back and forth between R and D on occasion and not had a problem there either. A non-issue for me, but if it affects you, I can see how it would be bothersome.

[limited1]

Originally Posted by LexxM3

Funny you should post re: (1) right now. That has been discussed extensively — on US cars, that function became broken (ie camera doesn't follow R/D gear correctly) in 07/2019.xx and didn't get fixed in 11/2019.xx. It does, however, work correctly everywhere other than USA (and Canada, which for this function is coded the same as USA). However ...

... one of our esteemed coding members @ifr suggested a code for me to try. I tried a couple of weeks ago and it didn't fix the issue then. But, I just recorded it again on a whim last weekend and have now noticed this week and carefully/explicitly verified just a few minutes ago that ... ready? ... it did fix it!

That's right, my 11/2019.40 Canadian G05 X5 now correctly follows camera display when shifting from P to R and then D! This is unprecedented and oh what a relief.

Let me discuss this with @ifr privately and we'll post the coding if we agree this is, in fact, working with this coding.

.

Any luck determining if coding fixed it? Pretty frustrating to not have this work.

[LexxM3]

Originally Posted by limited1

Any luck determining if coding fixed it? Pretty frustrating to not have this work.

There have been two people including myself that can verify that it does, in fact, fix it. However, both of us had a weird nuance that we haven't gotten to root cause yet, hence I haven't posted it publicly. The nuance is that after coding, it seems to potentially take days for it to start to have the effect. For me it was an uncertain number of days, more than 2, less that 14. For the other member it was almost exactly a week.

There is a plausible theory circulating that the ECU in question is not being reset through the coding process and a reset is required for this setting, hence a delay to some other random event that resets the ECU. I don't actually know how to force an ECU reset from ESys, need to research.

So, if you want it, happy to send by PM if you promise to feed back careful observations and further ideas to solve the delay mystery, if any.