[r33_RGSport]

Hmm, my '21 came with 07/2020, and I almost never have issue.
I belive that it get resetted whenever I turn on the fog lamp manually then shutdown the car.
If I don't use the fog lamp, it retain the Auto High Beam setting all the time.

[cruzer666]

Originally Posted by ChiefOne

Update on auto high beam - I had no issues with the retention of Auto High Beam once enabled for the first four weeks or so.
Last few days, however, I notice that the auto high setting is not retained. Every time I enter the vehicle and start the engine, I have to enable it again. Once enabled, it does continue to be on throughout the time until I exit the vehicle and lock.
My software version is the same that the vehicle was delivered with - 11/2020.33

I like it to be disabled by default, my neighbors would hate for high beams every time I start my car in the morning

[biterror]

Originally Posted by cruzer666

I like it to be disabled by default, my neighbors would hate for high beams every time I start my car in the morning

The high beams are not activated unless you're driving over 25 mph..

I have to switch on the automatic high beams every day but if I only make a short stop, it seems the car remembers the setting.

[HouseMD]

Has anyone noticed that the automatic high beam sensor seems very sensitive? When on, and going fast enough to have high beams on, my car will switch to low beams when there isn't a car coming. Sometimes it seems like it "sees itself" reflected from something. Other times it seems to get confused with non-vehicle lights.

My understanding is that early versions of auto high beams used the flicker from AC lights so I was wondering if LEDs or maybe fluorescent lights may be the issue.

[TurtleBoy]

It does seem to take lights off the road into account the deciding to turn the high beams on/off. I notice this in a few spots where it consistently goes low beam and I assume it is the lights off the road causing it. That said, I wouldn't call it too sensitive as it seems to work perfectly with approaching vehicles and those I'm coming up on.

You can try turning down the sensitivity to see how it works for you.

[mitch57]

Originally Posted by HouseMD

Has anyone noticed that the automatic high beam sensor seems very sensitive? When on, and going fast enough to have high beams on, my car will switch to low beams when there isn't a car coming. Sometimes it seems like it "sees itself" reflected from something. Other times it seems to get confused with non-vehicle lights.

My understanding is that early versions of auto high beams used the flicker from AC lights so I was wondering if LEDs or maybe fluorescent lights may be the issue.

Originally Posted by TurtleBoy

It does seem to take lights off the road into account the deciding to turn the high beams on/off. I notice this in a few spots where it consistently goes low beam and I assume it is the lights off the road causing it. That said, I wouldn't call it too sensitive as it seems to work perfectly with approaching vehicles and those I'm coming up on.

You can try turning down the sensitivity to see how it works for you.

I've noticed this as well. Since my last update from 03/2020.31 to 07/2020.54 it seems the "Auto High Beams are more sensitive/erratic then they were on the previous version. They don't seem to work as well around corners and are often late at dimming to low beams.

It's quite obvious when you approach a curve and can see the oncoming car's lights around the bend that the car should be able to see those lights. However, it doesn't dim until the oncoming car is directly in front of you. Which, by that time, you've already blinded the oncoming driver with your high beams. This issue seems to occur primarily when driving under 40 mph and when there are no trees or other obstructions on either side of the roadway. Strange behavior.

BMW just can't seem to grasp the concept of testing EVERYTHING prior to releasing updates. Either that or they just don't care as long as it fixes whatever gremlin they are chasing at the current time. They seem to operate on the principal of "Release it now and fix it later" method.

Not remembering the "Auto High Beam" setting, which worked flawlessly on previous software versions, has now morphed into not remembering that setting and also not functioning as precisely as they did on previous software builds.

I'm now following another forum member's lead on not doing any more updates until I'm confident that the update doesn't break something else while it attempts to fix another issue.

[bubbahead]

I’m on 11/20.45 and it remembers setting. Made a note of it today to check after reading this thread.

[ChiefOne]

Originally Posted by bubbahead

I’m on 11/20.45 and it remembers setting. Made a note of it today to check after reading this thread.

I believe mine was remembering too, until one day, for no reason at all, I reset my iDrive (press and hold volume control button), and the world changed .

Now the Auto High Beam setting and the Ambient Light setting goes away with each exit occurrence from the vehicle. AH turns off, and Ambient turns to Orange or Bronze (whatever it is.)

[ifr]

Originally Posted by ChiefOne

I believe mine was remembering too, until one day, for no reason at all, I reset my iDrive (press and hold volume control button), and the world changed .

Now the Auto High Beam setting and the Ambient Light setting goes away with each exit occurrence from the vehicle. AH turns off, and Ambient turns to Orange or Bronze (whatever it is.)

Conversely, mine would forget the setting almost daily. I did an i-drive reboot, and it is now working without issue.

Could just be a coincidence. I had a situation where the car would lose all favourites from NAV daily. Really irritating and went on for weeks. Booked it in for repair and what do you know, it suddenly fixed itself. Considering the nav faves are part of the profile, which is cloud stored, I suspect it was a BMW cloud issue that they eventually resolved. Nothing related to anything I'd done locally.

[ChiefOne]

I think in my case the curiosity to reboot the iDrive got the best of me Well, when I come to think of it though, this started happening after my attempts to charge/trickle the battery. I don't think that would be an issue, but who knows. I am not going to take by vehicle to Service Center just yet, will see how it progresses.

[TurtleBoy]

Originally Posted by ChiefOne

I think in my case the curiosity to reboot the iDrive got the best of me Well, when I come to think of it though, this started happening after my attempts to charge/trickle the battery. I don't think that would be an issue, but who knows. I am not going to take by vehicle to Service Center just yet, will see how it progresses.

Try rebooting iDrive again, maybe it will fix it.

[mitch57]

Originally Posted by ChiefOne

I think in my case the curiosity to reboot the iDrive got the best of me Well, when I come to think of it though, this started happening after my attempts to charge/trickle the battery. I don't think that would be an issue, but who knows. I am not going to take by vehicle to Service Center just yet, will see how it progresses.

Maybe try doing a full reboot by pressing and holding in the volume button until iDrive reboots 3 times. Then release volume button. I think they call this a "Telematics" reboot or something like that.

[ChiefOne]

Originally Posted by TurtleBoy

Try rebooting iDrive again, maybe it will fix it.

Sure will try .. thanks!
I know I read it somewhere, can't seem to find it now. What is the right way to reboot iDrive? I think in my previous attempts I kept it pressed until the screen went dark and then some more.

[ChiefOne]

Originally Posted by mitch57

Maybe try doing a full reboot by pressing and holding in the volume button until iDrive reboots 3 times. Then release volume button. I think they call this a "Telematics" reboot or something like that.

I probably may have done so unknowingly. I kept it pressed for quite long in my first attempt.

[mitch57]

Originally Posted by ChiefOne

I probably may have done so unknowingly. I kept it pressed for quite long in my first attempt.

You have to hold it in for at least 90 seconds to 2 minutes in order to get it to reboot 3 times.

[TurtleBoy]

Originally Posted by ChiefOne

Sure will try .. thanks!
I know I read it somewhere, can't seem to find it now. What is the right way to reboot iDrive? I think in my previous attempts I kept it pressed until the screen went dark and then some more.

Sounds like you were doing it correctly. Once it goes black you can let it go.

[cruzer666]

Correction: I'm running iDrive 11/2020.45 I checked both the automatic high beam setting and the ambient lights, both are being remembered without issues.

[ifr]

I'm wondering if there is a behaviour change with later i-step.

Without any interaction from me I've seen the HBA enable with and without the lights enabled. With just DRL it never enables as expected.

Sometimes when normal beam are active the auto-HBA enablement activates but not always. In the scenario where its not active, most would be tempted to press the auto-HBA and think it has 'forgotten' the activation. I've left this alone, and its enabled in darker lighting conditions, without my intervention.

So there seems to be up to 5 states, at least on my vehicle:
1. Lights OFF
2. DRL
3. Normal beam - no HBA enabled by default
4. Normal beam -HBA enabled
5. HBA active

Alternatively, the profile is intermittently losing some settings that reappear randomly.

[X5 45e]

Originally Posted by ifr

I'm wondering if there is a behaviour change with later i-step.

Without any interaction from me I've seen the HBA enable with and without the lights enabled. With just DRL it never enables as expected.

Sometimes when normal beam are active the auto-HBA enablement activates but not always. In the scenario where its not active, most would be tempted to press the auto-HBA and think it has 'forgotten' the activation. I've left this alone, and its enabled in darker lighting conditions, without my intervention.

So there seems to be up to 5 states, at least on my vehicle:
1. Lights OFF
2. DRL
3. Normal beam - no HBA enabled by default
4. Normal beam -HBA enabled
5. HBA active

Alternatively, the profile is intermittently losing some settings that reappear randomly.

Are you suggesting the AHB symbol is only showing when the function is active?

Above the threshold speed, out of the city and surrounding dark enough and if these criteria are not met AHB is not functional and the symbol is not showing.

[ifr]

Originally Posted by X5 45e

Are you suggesting the AHB symbol is only showing when the function is active?

Above the threshold speed, out of the city and surrounding dark enough and if these criteria are not met AHB is not functional and the symbol is not showing.

No the auto high beam enabled dash light is sometimes appearing with normal light activation and sometimes not. So sometimes I'll have 2 light activation icons and sometimes 3.

HBA is working as normal when enabled and the required pre-reqs are met. It just 'appears' random as to whether HBA function is enabled, without manual intervention.

[floridaman100]

Originally Posted by cruzer666

Correction: I'm running iDrive 11/2020.45 I checked both the automatic high beam setting and the ambient lights, both are being remembered without issues.

I am running the same software version and can confirm the auto high beam setting is still malfunctioning. Setting not being retained. I guess we could rename this feature to partial auto high beam.

[mitch57]

Originally Posted by floridaman100

I am running the same software version and can confirm the auto high beam setting is still malfunctioning. Setting not being retained. I guess we could rename this feature to partial auto high beam.

How about "Manually initiated Automatic High Beams"?