iDrive screen goes blank "No Signal" in red.. anyone else?

[mikeson]

Yesterday, when I start the car, the screen goes black and 'No signal" in red color.
Radio work but then turned off, and no signal shows again and on again,..
After like 10 min. iDrive boots up and become normal.

Does anyone have this problem?

[YXEM5]

This has actually happened to me twice in the last month. Both times it happened randomly while driving. After about 10 minutes the Idrive reset itself and all was well. I have no idea why it does that but at least now you know you're not the only one! Haha

I talked to my service department about it and they told me it's the equivalent of satellite radio losing signal and not something to be concerned with. Whether or not that's an accurate explanation I don't know.

[Mr.47]

Sometimes Idrive gets locked up and reboots, I wouldn't worry about it, if all is fine afterwards.

[mikeson]

Thank you and big relief. lol

[whitebeast1]

I’ve had this issue a few times on my I3 and they had to replace the battery.

[Maverik259]

I've had it happen 2x in the 6 months I've owned it

[00_Bora]

I had this problem where it would cycle on and off with that message and then later that day, completely off with a small amount of smoke coming from my vents. That was fun!

Had the entire iDrive unit replaced under warranty since they could not boot it up manually at the dealership either.

[TallTrees]

The "computer" systems used in vehicles today is becoming more and more complicated. This has happened to me maybe 5 times in 3 years. I think it's like the BSOD blue screen of death in windows. Sometimes the software get confused and just needs to reboot. Wouldn't worry about it if it's infrequent.

[Dilmorecg]

This has been happening to me every so often. Id say 5 times in the last 3 months. It just re-starts and is fine after. I brought it up with the dealer and they just reset my bluetooth phones...which I dont think has anything to do with the error. Couldn't find any faults or anything.

[RED_Y_]

I have seen this only when my wife is driving and her Apple phone is connected to the car, my Android is fine. I asked dealer to check it out and car is being serviced right now. We will see...

[enigmathedevil]

just Simply Hold the volume knob for 30 sec ( or till it rest again ) and it will rest and .. Problem solved

[Maverik259]

Originally Posted by enigmathedevil

just Simply Hold the volume knob for 30 sec ( or till it rest again ) and it will rest and .. Problem solved

What problem? As in it will never do this again or are you saying to get it to come back on? Cuz mine does it like once a month now. And immediately comes back on.

[jch1511]

I had the same issue. Dealer tried to update the software a few times, did not solve the problem. Finally, they replaced my idrive head unit under warranty due to the repeated system crash and reboot, now the problem is gone.


As a bonus, my armrest USB cable beeping issue got resolved as well. Per dealer shop foreman, it has nothing to do with the cable itself. Rather, the idrive did not put out enough ampere to the armrest USB, the replacement unit has a newer design that solved the USB issue.

My dealer stated that BMW will not fix the USB issue on it's own. However, if you are lucky enough to have your defective idrive unit replaced with a newer version, the USB problem fix is part of the update.

Hope my experience can help some of you folks.

[CaboM4]

sounds like improper NBT2 coding for CID compatibility.

took my F34 back to stock from F15 CID screen retrofit, and when VO_Coding back to stock, based on OTA updates, the iDrive version was set to id6_lite and the screen output coding was not coded correctly for the APIX2 24 bit color screen

seems like an OTA software update bug for NBT2 systems

[Maverik259]

Originally Posted by CaboM4

sounds like improper NBT2 coding for CID compatibility.

took my F34 back to stock from F15 CID screen retrofit, and when VO_Coding back to stock, based on OTA updates, the iDrive version was set to id6_lite and the screen output coding was not coded correctly for the APIX2 24 bit color screen

seems like an OTA software update bug for NBT2 systems

Wow you just put a lot of letters together to make some random words.

[CaboM4]

Originally Posted by Maverik259

Wow you just put a lot of letters together to make some random words.

Here is a glossary of the quite common terms surrounding BMW navigation systems defined for you:

NBT2 - Next Big Thing 2 (latest version of BMW Professional Navigation System)

CID - Central Information Display

VO_Coding - Vehicle Order Coding

OTA - Over the Air

id6_lite - iDrive version 6 lite

APIX2 - Automotive Pixel v.2

[Maverik259]

Originally Posted by CaboM4

Here is a glossary of the quite common terms surrounding BMW navigation systems defined for you:

NBT2 - Next Big Thing 2 (latest version of BMW Professional Navigation System)

CID - Central Information Display

VO_Coding - Vehicle Order Coding

OTA - Over the Air

id6_lite - iDrive version 6 lite

APIX2 - Automotive Pixel v.2

Woooooooow.....

[CaboM4]

Originally Posted by Maverik259

Woooooooow.....

you really are a special variety of jerkoff, huh?

The information provided in my post is intended to help the OP & anyone else having this issue. If you are going to provide nothing useful then piss off

[Maverik259]

Originally Posted by CaboM4

you really are a special variety of jerkoff, huh?

The information provided in my post is intended to help the OP & anyone else having this issue. If you are going to provide nothing useful then piss off

Ok ok snow flake. Don't need to name call like it's middle school. Problem is this is wide spread and has nothing to do with any mods anyone's done. As I also get this "no signal" periodically. And considering the OP never mentioned a single word about having the iDrive altered recently then I would argue your acronyms are pretty pointless as well. Sorry didn't realize you were sensitive. I'll do better next time.

[CaboM4]

Originally Posted by Maverik259

Ok ok snow flake. Don't need to name call like it's middle school. Problem is this is wide spread and has nothing to do with any mods anyone's done. As I also get this "no signal" periodically. And considering the OP never mentioned a single word about having the iDrive altered recently then I would argue your acronyms are pretty pointless as well. Sorry didn't realize you were sensitive. I'll do better next time.

blow me

if you actually knew anything about the workings of the NBT2 EVO w/ ATM OTA software updates ... your response would not have been so ignorant.

Again ... for those with the issue described by the OP ... confirm the APIX settings in your NBT2 with ESYS or BimmerCode App to see if you received an OTA software update that has incorrectly changed these settings, thus causing the "No Signal" behavior of the CID

OP... has this been resolved?

[Maverik259]

Originally Posted by CaboM4

blow me

if you actually knew anything about the workings of the NBT2 EVO w/ ATM OTA software updates ... your response would not have been so ignorant.

Again ... for those with the issue described by the OP ... confirm the APIX settings in your NBT2 with ESYS or BimmerCode App to see if you received an OTA software update that has incorrectly changed these settings, thus causing the "No Signal" behavior of the CID

OP... has this been resolved?

Lol 3 weeks later and you're still butt hurt. Hope they have a "cry room" at the high school you go to and I suggest you use it. Oh and grow up a little. What a snow flake.

[Florida-X3]

This happened to me last night, didn't take 10 minutes to reboot. The "No Signal" message lasted about a minute or two, then went blank and signs of a reboot started about a minute later.