[eleykin]

If you have nothing nice to say why are you even commenting. I have never coded a car before so im asking for advice from people that have actual experience and have done this. Why do you feel that you should chime in your 2 cents you low life.

[LexxM3]

Originally Posted by eleykin

If you have nothing nice to say why are you even commenting. I have never coded a car before so im asking for advice from people that have actual experience and have done this. Why do you feel that you should chime in your 2 cents you low life.

He made a valid comment and your response is actually the one off side. Coding, particularly ESys coding, while not difficult, requires a certain competence and experience, which in turn requires some ability to research the basics yourself. His comment is why I haven't responded ... nothing nice to say as it doesn't sound like you are ready for coding at this stage and this means you will get yourself into trouble. This particular coding fix is weird and should absolutely not be your first coding experience.

The most constructive thing I can add is that you should probably get someone else to code this for you — there are people and companies around that will do it for a fee, for example our own r33_RGSport may be able to help.

[RayoVac]

Originally Posted by eleykin

If you have nothing nice to say why are you even commenting. I have never coded a car before so im asking for advice from people that have actual experience and have done this. Why do you feel that you should chime in your 2 cents you low life.

Note... all I said was that I had concerns for your chances of success. This lead you to call me a Low Life... pretty much says all I need to know about you.

If you truly want help from folks, your ability to show you are willing to help yourself FIRST and NOT be defensive towards criticism, will help you succeed. Ya know... Bees to Honey and all.

Have a great day and good luck with your coding ventures.

[RSnic]

IFR,

Yesterday I coded the function in ICAM you suggested in an earlier post in this thread. Came out this and it worked fine as I backed out of my garage & set off -- initially displaying rear camera in center display & then front camera as I put car in drive. TERRIFIC!

Subsequently, as I pulled out of parking lot , it didn't work.

When everyone talks about putting view in Automatic, do you just tap iDrive on camera icon with A?

[ifr]

Yep once it's in auto it should stick in auto once the coding takes effect.

There's something odd about the ICAM ECU in that for some it takes time (days) before it works. I suspect a battery reset would do the trick, or possibly some diagnostic measures plan in ISTA, but without that you just have to wait.

[anuj452]

@ifr - I coded my car today after OTA update to 07/2020.80

This time the automatic backup camera function worked right after my coding session, unlike before where it took 5-7 days..

Originally Posted by ifr

Yep once it's in auto it should stick in auto once the coding takes effect.

There's something odd about the ICAM ECU in that for some it takes time (days) before it works. I suspect a battery reset would do the trick, or possibly some diagnostic measures plan in ISTA, but without that you just have to wait.

[ifr]

Originally Posted by anuj452

@ifr - I coded my car today after OTA update to 07/2020.80

This time the automatic backup camera function worked right after my coding session, unlike before where it took 5-7 days..

Good to know. LexxM3 can now grow a pair, do his update and validate your experience

[LexxM3]

Originally Posted by ifr

Good to know. LexxM3 can now grow a pair, do his update and validate your experience

I was thinking the same thing (although very few people are allowed access to my "pair" ).

But it seems I should go straight to 11/2020.xx at the dealer (they are ready to update on my say so) and that version hasn't been proven yet to work with the hack. I really couldn't live as happily with the car as I do now without this camera switching working properly, it is used and necessary multiple times every drive (example from yesterday in pic: that's with rims necessarily about 1" from the curb).
.

[ifr]

Originally Posted by LexxM3

I was thinking the same thing (although very few people are allowed access to my "pair" ).

But it seems I should go straight to 11/2020.xx at the dealer (they are ready to update on my say so) and that version hasn't been proven yet to work with the hack. I really couldn't live as happily with the car as I do now without this camera switching working properly, it is used and necessary multiple times every drive (example from yesterday in pic: that's with rims necessarily about 1" from the curb).
.

Looks like ICAM ECU is updated as part of 07/2020 AND 11/2020 and will need re-coding.

Bit of a risk with the 11/2020 update, but also brings support for TLA etc. Decisions decisions!

[RSnic]

IFR,

Once again, you nailed it!

I did the coding to ICAM you suggested. After coding, still had same problem until yesterday-- so it took 6 days for change to catch

Thanks again

[Consuldean]

I changed that on my car this weekend (Saturday) my car with iSTEP 11/2020.64 car... It's been 5 days and hasn't changed yet.

Will update this when and if it gets to behave correctly :-)

[VTENGR]

Originally Posted by Consuldean

I changed that on my car this weekend (Saturday) my car with iSTEP 11/2020.64 car... It's been 5 days and hasn't changed yet.

Will update this when and if it gets to behave correctly :-)

Be sure when you go in reverse that you select the camera icon with the A inside for auto. Even if you're coding has kicked in, if this isn't selected it won't switch automatically. Took me a little over a week for it to kick in.

[Consuldean]

Originally Posted by VTENGR

Be sure when you go in reverse that you select the camera icon with the A inside for auto. Even if you're coding has kicked in, if this isn't selected it won't switch automatically. Took me a little over a week for it to kick in.

Thanks, I did that and it works now.

Interestingly enough, the switch from the rear to the front camera doesn't happen at the moment we switch the gear but rather when the car starts moving... which differs from the standard non US behavior if I recall correctly.

Also, it seems that the small animation for the switch between the rear and front camera isn't systematic : I sometimes see a switch happening immediately and sometimes the transition (fast forward).

Anyway, I can't complain - I now see the front when I drive forward which is good :-)

Thanks ifr and VTENGR.

[moholland]

OMG I was so excited to code this fix, until I realized it doesn’t work in Bimmercode. Such a bummer! I’m new to all of this stuff... any chance bimmercode gets an update to access this setting?

[anuj452]

Well, this issue continues with the version update to 03/2021.40

I did the coding, but it did not work right after the coding session...

Lets see how long it takes for this to start working again...

[LexxM3]

Originally Posted by moholland

OMG I was so excited to code this fix, until I realized it doesn't work in Bimmercode. Such a bummer! I'm new to all of this stuff... any chance bimmercode gets an update to access this setting?

Anything is possible, but it seems pretty unlikely for several reasons:

- this is pretty specialized; the always-rear view behaviour is explicitly conditioned in coding to only a few of BMW's many regions, specifically USA (includes Canada), South Korea, and India; it would be out of character for Bimmercode to include something this specialized and it's hard to both test and maintain as working into the future

- the code fix doesn't take right away, requires a delay of (so far) up to a week, and we don't know why this behaves like that; for something as simple to use as Bimmercode, this kind of an uncertainty is a showstopper

- the required ECU (ICAM3) is not currently supported by Bimmercode

The only way I see this happening is if Bimmercode starts to support ICAM3 for some other reason and adds Expert Mode for that ECU. It's a stretch.

[anuj452]

Its been 10 days now and its not working yet ...

I have to manually select the [A] button everytime...

Originally Posted by anuj452

Well, this issue continues with the version update to 03/2021.40

I did the coding, but it did not work right after the coding session...

Lets see how long it takes for this to start working again...

[anuj452]

Coding fix is not working with the version update to 03/2021.40 :

[LexxM3]

Originally Posted by anuj452

Coding fix is not working with the version update to 03/2021.40 :

At least a week has passed since coding?

[LexxM3]

@anuj452, any updates after time has passed since the coding?

On my part, I report the disheartening news that with zero iDrive updates and no related coding changes, the coding for proper camera switching on my car suddenly stopped working after about 1.5 years working properly. I don't know what to correlate it to, but my best observation is that perhaps the loss was correlated to the "triple iDrive reset" (press and hold volume through at least 3 reboots) that I did for the first time ever about a day before it happened to recover spontaneous loss of Spotify. Or perhaps it's related to whatever BMW black magic happened to cause loss of Spotify and Weather apps for so many of us in the first place.

@ifr, does that perhaps give any hints as to why there has always been that weird coding to take delay for this?

For my part, I'll start recoding everything related back to stock, wait a couple of weeks, code back to "fixed" and wait a couple of weeks to see if I can get it back. As it stands, I suddenly absolutely hate the car every day now because of this lack and have almost hit curbs already as a result. Idiotic.

[ifr]

Originally Posted by LexxM3

@ifr, does that perhaps give any hints as to why there has always been that weird coding to take delay for this?

If the coding is still set and no i-step upgrade performed, then it would suggest that its profile related. I've seen lots of issues with back-end profile changes like the missing heated steering wheel, vanishing favourites, HBA unsetting, Speed camera alerts 'moving' from HUD to CiC, etc. Maybe its something along those lines.

In that case the best approach would be to decouple the profile and CD account, reset all car settings and start again after an idrive reboot. Drastic and a mare as you'll lose all seat settings etc, without any guaranteed gain, but if it bothers you that much its probably worth a shot. Make sure the coding is set as desired, before resetting anything.

[LexxM3]

Originally Posted by ifr

If the coding is still set and no i-step upgrade performed, then it would suggest that its profile related. I've seen lots of issues with back-end profile changes like the missing heated steering wheel, vanishing favourites, HBA unsetting, Speed camera alerts 'moving' from HUD to CiC, etc. Maybe its something along those lines.

In that case the best approach would be to decouple the profile and CD account, reset all car settings and start again after an idrive reboot. Drastic and a mare as you'll lose all seat settings etc, without any guaranteed gain, but if it bothers you that much its probably worth a shot. Make sure the coding is set as desired, before resetting anything.

Well, I "fixed" it back to proper operation without using the "profile nuclear option" … but I don't really have an exact set of reproducible procedures to do so and thus I don't think we're any closer to precisely figuring out what is really going on behind the scenes. I'll document what I have observed however to build up "experience".

Using prior hints of:
- camera must be in A for proper switching
- the car maybe (or maybe not) remembers the A mode

With car running and tested to NOT properly switch, I manually set the camera mode to A and, of course, the camera started to switch properly. I then turned off the car and locked it. Coming back to the car, suddenly camera switching works without manually setting A (ie A was remembered).

Trying to explicitly break it again, I then tested by manually setting mode to reverse and repeating above shutdown and re-entry. Upon opening, camera is still in A mode (ie non-A mode was NOT remembered). In other words, I was not able to break it again and so that means my "fix" procedure above is fragile and unlikely to be a complete story.

So it seems to me that "somehow" it had spontaneously managed to remember the non-A mode for me in the past 2 weeks, although I've never been able to force that when intended. It then remembered A mode when I set that manually, something I was also never able to do without the magic coding when intended. I suspect that this "somehow" is the key to understanding what's going on, but we have no idea what that "somehow" is; perhaps it's related to some backend profile data change by BMW per your thoughts, @ifr.

What a mess. But at least I am back to loving the car again. anuj452, perhaps that and @irf's "profile nuclear option" gives you something to try?