[fe7565]

Originally Posted by ringo9

Last issue:
Viber calls are fine, but regular Phone Calls people complain they hear their own voice in echo! Anything I can do about it?

Glad you had the LVDS cables sorted out.

Having echoes seems to be an issue for some, and not for others. Some of it could be related to OEM Bluetooth being used for audio and telephone or one instead of the other. Or using the MMI Bluetooth settings for audio or telephone, or a mix of these two.

But before looking at those settings, I would recommend going in the MMI menu and set up your microphone echo configuration. I forgot how it works, but I know that when you are making adjustments it will tell you how much of your microphone is being picked up by the MMI and it will give you a percentage. Adjusting it so it measures 100% is what that menu helps you do.

Also, although not related, it seems that if you set the Loudness from 800 down to 400 it eliminates some of the distortion.

[fe7565]

Originally Posted by sevenofnine

I have a andream cic unit with the hdmi port. I am trying to install a chromecast with google tv but dont have the hdmi option in the menu. Anyone know how to activate it? Running 1.6.9R3

mcu 22.10.10.118
hw b_chl_g

You should have an HDMI icon in your MMI settings. You would have to exit out of your CarPlay or AA menu first, and there should be an HDMI icon along with an AVI in icon, etc

If you don’t see an HDMI icon along with all the other default MMI menu icons it’s possible that a non-HDMI CUST version firmware is installed on your MMI somehow.

[sevenofnine]

Hmm I dont have that hdmi icon in the main menu. I bought the box a week ago from https://www.android-car-dvd.de

Is there a newer firmware I can try and install? Or maybe a older one?

[ringo9]

Originally Posted by fe7565

Glad you had the LVDS cables sorted out.

Having echoes seems to be an issue for some, and not for others. Some of it could be related to OEM Bluetooth being used for audio and telephone or one instead of the other. Or using the MMI Bluetooth settings for audio or telephone, or a mix of these two.

But before looking at those settings, I would recommend going in the MMI menu and set up your microphone echo configuration. I forgot how it works, but I know that when you are making adjustments it will tell you how much of your microphone is being picked up by the MMI and it will give you a percentage. Adjusting it so it measures 100% is what that menu helps you do.

Also, although not related, it seems that if you set the Loudness from 800 down to 400 it eliminates some of the distortion.

Thanks. It had 3 presets: Custom, x3, and default i think, I chose Custom without changing any value and my co-speaker told me it lost the annoying delay so I am keeping there for now.

Any way to tell for sure which F/W I have and If I can flash a newer one? I know it's an Andream, and the code on my box reads: EWM-BMCP-EVO-A which is different than those in the first page. My resolution is somewhat stretched width wise, which means square icons/circles are not perfect squares/circles.

PS. I was hoping I could keep using the touch screen but it doesn't seem to work, only via iDrive controller.

[fe7565]

Originally Posted by sevenofnine

Hmm I dont have that hdmi icon in the main menu. I bought the box a week ago from https://www.android-car-dvd.de

Is there a newer firmware I can try and install? Or maybe a older one?

If you bought it from a legitimate shop, they should be able to give you an answer to what's going on with your HDMI. You could certainly try to upload another firmware yourself, but the seller will most likely not deal with you after that, if they offered any warranty.

For now: You could try to plug in an active HMDI signal and reboot the MMI and see if it registers.

This is similar to what it should look like in your menu:

View post on imgur.com

[fe7565]

Originally Posted by ringo9

Thanks. It had 3 presets: Custom, x3, and default i think, I chose Custom without changing any value and my co-speaker told me it lost the annoying delay so I am keeping there for now.

Any way to tell for sure which F/W I have and If I can flash a newer one? I know it's an Andream, and the code on my box reads: EWM-BMCP-EVO-A which is different than those in the first page. My resolution is somewhat stretched width wise, which means square icons/circles are not perfect squares/circles.

PS. I was hoping I could keep using the touch screen but it doesn't seem to work, only via iDrive controller.

I am not familiar with EVO MMIs. and their specific menus. I know there were some EVO MMIs advertised (on Aliexpress and other Chinese affiliated web sites) with touchscreen a year ago, but did not see one yet on this forum.

I would post some photos of your box, your menus, especially the one that shows your firmware...and see if anyone chimes in.

Here is another EVO with similar model number:https://f30.bimmerpost.com/forums/sh...ostcount=11215 Follow his resolution.

The stretching can be from MMI DIP settings. I know that for 8.8 and 10.25" the DIP should be the same with NBT setup, but maybe EVO is different?


And check in Bimmercode under Expert mode what your OEM resolution is set. There may be a difference between 8.8" and 10.25" in EVO because of the possibly higher resolution screens vs NBT OEM screens. For example 800x480 vs 1280x 720 vs 1920x 980 (these are just numbers I pulled out of a hat).

[ringo9]

Originally Posted by fe7565

I am not familiar with EVO MMIs. and their specific menus. I know there were some EVO MMIs advertised (on Aliexpress and other Chinese affiliated web sites) with touchscreen a year ago, but did not see one yet on this forum.

I would post some photos of your box, your menus, especially the one that shows your firmware...and see if anyone chimes in.

The stretching can be from MMI DIP settings. I know that for 8.8 and 10.25" the DIP should be the same with NBT setup, but maybe EVO is different?


And check in Bimmercode under Expert mode what your OEM resolution is set. There may be a difference between 8.8" and 10.25" in EVO because of the possibly higher resolution screens vs NBT OEM screens. For example 800x480 vs 1280x 720 vs 1920x 980 (these are just numbers I pulled out of a hat).

According to the instructions for this model year F20 the correct DIP switch settings are still: First 3 ON, the rest OFF so I guess it's not that.

If I want to use the OEM BT, does that mean I will need to have my phone paired with 2 devices simultaneously every time?

I also noticed I could not answer a call from the steering wheel Phone button, only via iDrive. Is that due to not using OEM BT?

Here is a screenshot of my F/W screen:

[adiki]

Originally Posted by mauritsje

I had Dynamic traction error, passenger safety error (even though I didnt disconnect the Airbag switch) that stayed on the dash, apart from that there were 3 more errors triggered by the MMI box that arent important and not showing in the dash

2 years after I installed Roadtop module in my car I started getting similar errors on my dashboard. I had passive safety system error and sometimes central air condition and radio panel stopped reacting or turned off. I haven't update the module for longer time. Does it mean the module is broken or is it somehow fixable? After disconnecting the module from the car everything is working fine in the car.

[fe7565]

Originally Posted by adiki

2 years after I installed Roadtop module in my car I started getting similar errors on my dashboard. I had passive safety system error and sometimes central air condition and radio panel stopped reacting or turned off. I haven't update the module for longer time. Does it mean the module is broken or is it somehow fixable? After disconnecting the module from the car everything is working fine in the car.

Likely the MMI is blocking some CAN messages. Like some people had issues with Bimmercode not working at all, or not able to read some ECUs like the HVAC, etc. That's why some people were able to change their MCU version. This version (from page 1) fixed the problems for most, but it's not a one size fits all, so you are doing it at your own risk.



Andream B2-Version [1] [NBT] [GEMINI_PACK.BIN]
Model: EW-BMCP-NBT04X

Note: There are two B2-Versions for 'NBT'. Their updates are not compatible with each other.

B2_V1.1.5 (PIN: 5025) (Not cross compatible)
B2_V1.2.0_t (PIN: 5025) (Not cross compatible)
B2_V1.2.5 (PIN: 5025) (Not cross compatible)
B2_V1.5.0 (PIN: 5025) (Not cross compatible)
B2_V1.5.5 (PIN: 5025) (Not cross compatible)
B2_V1.5.9 (PIN: 5025) (Not cross compatible)
B2_V1.6.2 (PIN: 5025) (Not cross compatible)
MCU 20.10.22.16 (Cross compatibility unknown)
MCU 21.09.13.122 (Cross compatibility unknown)

[fe7565]

[QUOTE=ringo9;29807801]According to the instructions for this model year F20 the correct DIP switch settings are still: First 3 ON, the rest OFF so I guess it's not that.

If I want to use the OEM BT, does that mean I will need to have my phone paired with 2 devices simultaneously every time?

I also noticed I could not answer a call from the steering wheel Phone button, only via iDrive. Is that due to not using OEM BT?

Here is a screenshot of my F/W screen:



Check your OEM screen resolution settings in your car's coding. The default obviously works for your OEM screen, but may have issues with what the MMI is looking for.

Do not think you can answer phone calls via the steering wheel button if you are in MMI mode. Assuming your phone is paired BLE in OEM mode already, I think you should be able to answer phone calls via the steering wheel button, if you are in OEM mode, or switch to OEM mode either with your BACK (or some use the MENU) iDrive Controller buttons. May be able to use a shortcut button for "telephone" using one of the 1-8 OEM user preset buttons.

Some people set "audio" only and not "telephone" in config settings for the phone device in OEM mode, or vice versa. Some also set OEM BLE mode in the MMI settings as well. The BLE is murky for me in many cases, so may want to ask others to chime in.

What I know: the BLE on a device allows connections to up to about 8 devices simultaneously, but the OEM BMW OS and the MMI would have to have that implemented. I do not think the Chinese bothered to put that extra effort in the design. For us morons buying their half-ass devices finding work-arounds for the shortcomings are good enough. I think the BMW OEM allows at least two phones (devices) simultaneously connected, but again, the MMI does not seem to have that enabled. The MMI is using the BLE phone call passed on to it by the OEM head unit and vice versa. The MMI at times uses the BLE cannel between the MMI and the OEM HU for sound, phone, alerts, etc ....and at times uses the direct AUX-IN channel (but not for the phone). Again, feel free to ask others who have a better understanding of this half-ass setup.

(Looks like you have a firmware that is new and not listed or posted here. So, if you do any upgrades/changes, the only way to revert back if you have a back up or if you try another already posted version. Or ask the Chinese seller or their distributor to send you a copy. You may get lucky and after selling your kidney, they may have mercy and send it to you)

[adiki]

Originally Posted by fe7565

Likely the MMI is blocking some CAN messages. Like some people had issues with Bimmercode not working at all, or not able to read some ECUs like the HAVC, etc. That's why some people were able to change their MCU version. This version fixed the problems for most, but it's not a one size fits all, so you are doing it at your own risk.



Andream B2-Version [1] [NBT] [GEMINI_PACK.BIN]
Model: EW-BMCP-NBT04X

Note: There are two B2-Versions for 'NBT'. Their updates are not compatible with each other.

B2_V1.1.5 (PIN: 5025) (Not cross compatible)
B2_V1.2.0_t (PIN: 5025) (Not cross compatible)
B2_V1.2.5 (PIN: 5025) (Not cross compatible)
B2_V1.5.0 (PIN: 5025) (Not cross compatible)
B2_V1.5.5 (PIN: 5025) (Not cross compatible)
B2_V1.5.9 (PIN: 5025) (Not cross compatible)
B2_V1.6.2 (PIN: 5025) (Not cross compatible)
MCU 20.10.22.16 (Cross compatibility unknown)
MCU 21.09.13.122 (Cross compatibility unknown)

Do you mean installing on my Roadtop module last update listed on Andream equivalent?

[fe7565]

Originally Posted by adiki

Do you mean installing on my Roadtop module last update listed on Andream equivalent?

Yes, this version seems to be cross-compatible with B1 and B2 versions or various brands. Again, there is a risk, as with any installs/upgrades. Make sure you have a back up for your current MCU version. I installed this same MCU version on my Carlinkit B2 and my Pangolin (some RoadTop B2 type no-brand name) MMI. On the Carlinkit MMI it fixed the Bimmercode issue. On the Pangolin I never had a Bimmercode issue, and when I installed this MCU version it caused random reboot issues....so I rolled back to my original MCU version.

After MCU update, make sure you clear your error codes with ISTA or some code reader to see what (if any) was solved.

[ringo9]

[QUOTE=fe7565;29808287]

Originally Posted by ringo9

According to the instructions for this model year F20 the correct DIP switch settings are still: First 3 ON, the rest OFF so I guess it's not that.

If I want to use the OEM BT, does that mean I will need to have my phone paired with 2 devices simultaneously every time?

I also noticed I could not answer a call from the steering wheel Phone button, only via iDrive. Is that due to not using OEM BT?

Here is a screenshot of my F/W screen:



Check your OEM screen resolution settings in your car's coding. The default obviously works for your OEM screen, but may have issues with what the MMI is looking for.

Do not think you can answer phone calls via the steering wheel button if you are in MMI mode. Assuming your phone is paired BLE in OEM mode already, I think you should be able to answer phone calls via the steering wheel button, if you are in OEM mode, or switch to OEM mode either with your BACK (or some use the MENU) iDrive Controller buttons. May be able to use a shortcut button for "telephone" using one of the 1-8 OEM user preset buttons.

Some people set "audio" only and not "telephone" in config settings for the phone device in OEM mode, or vice versa. Some also set OEM BLE mode in the MMI settings as well. The BLE is murky for me in many cases, so may want to ask others to chime in.

What I know: the BLE on a device allows connections to up to about 8 devices simultaneously, but the OEM BMW OS and the MMI would have to have that implemented. I do not think the Chinese bothered to put that extra effort in the design. For us morons buying their half-ass devices finding work-arounds for the shortcomings are good enough. I think the BMW OEM allows at least two phones (devices) simultaneously connected, but again, the MMI does not seem to have that enabled. The MMI is using the BLE phone call passed on to it by the OEM head unit and vice versa. The MMI at times uses the BLE cannel between the MMI and the OEM HU for sound, phone, alerts, etc ....and at times uses the direct AUX-IN channel (but not for the phone). Again, feel free to ask others who have a better understanding of this half-ass setup.

(Looks like you have a firmware that is new and not listed or posted here. So, if you do any upgrades/changes, the only way to revert back if you have a back up or if you try another already posted version. Or ask the Chinese seller or their distributor to send you a copy. You may get lucky and after selling your kidney, they may have mercy and send it to you)

Thanks for taking the time to write up that information. It is as you say a half-arsed setup and if it weren't for my unwillingness to switch to an iPhone i wouldn't be wasting my time and money on this. My car had OEM CarPlay activated already, OEM operation with touch function and all but I prefer Android phones. I would also be willing to switch to a newer car with Android Auto correctly implemented but I like my current one for the time being so had to go for those compromise units.

I will play around with settings tomorrow now that the unit is basically working OK, looks like there are a few options to experiment with.

[R4ndy]

I have the andream mmi box for my BMW F15, I like it but…. Doesn’t have touch screen as my F15 is pre 2016.

I also have the Andream BMW e70 CarPlay kit (non Android), but screen only and it’s a touch screen.. hands down a much better unit and a lot easier to install than MMI. Only if they had this for F15

[fe7565]

[QUOTE=ringo9;29808412]

Originally Posted by fe7565

Thanks for taking the time to write up that information. It is as you say a half-arsed setup and if it weren't for my unwillingness to switch to an iPhone i wouldn't be wasting my time and money on this. My car had OEM CarPlay activated already, OEM operation with touch function and all but I prefer Android phones. I would also be willing to switch to a newer car with Android Auto correctly implemented but I like my current one for the time being so had to go for those compromise units.

I will play around with settings tomorrow now that the unit is basically working OK, looks like there are a few options to experiment with.

I like AA better as well (Google Maps), but I have an iPhone and having two phones in the car is a pain with only one data plan (iPhone). Hotspot sharing from the iPhone to the Android (Pixel 3A) may be a work around, but again...a pain. Lately, Carplay (iOS Maps) seems to be much better here in the US, and at times I prefer the iOS Maps audio directions interface vs the Google Maps. But Siri is not as good as Google Assistant IMHO. Can use Google Maps with Siri commands, but it's limited and cannot do searches within Google Maps on voice command, only with button-push voice activation.

Also, if you have AA running on the MMI and long press the steering wheel button, Google Assistant should come up. Or you can just command "Hey Google/ OK Google" and it should appear as well.

Feel free to ask others here for tips, there is a lot of good info and work arounds that others came up with.

[fe7565]

Originally Posted by R4ndy

I have the andream mmi box for my BMW F15, I like it but…. Doesn’t have touch screen as my F15 is pre 2016.

I also have the Andream BMW e70 CarPlay kit (non Android), but screen only and it’s a touch screen.. hands down a much better unit and a lot easier to install than MMI. Only if they had this for F15

The problem with the Android HU screens is the refection. For me that is a deal breaker. I just posted last night on the Android 11 HU thread asking if any fixes to that from a year ago and RedErik said "no". I know there are some half-ass anti-reflection tinted Android screens out there, but do not come close to an OEM BMW screen.

In my old F30, I have updated my Entry HU to NBT and my 6.5" OEM screen to a 10.25" F-15 OEM screen and I have zero reflection in even the strongest sun light. https://f30.bimmerpost.com/forums/sh...168747&page=23

[Leegbr]

Anyone able to tell me which manufacturers software I should be using?

Bavarian automotive current software is;

SDK Version: 25.0.0.7.0.0.2.0
CUST Version: CHL V1.6.6
MCU Version: 20.12.1.18
HW Version: BMW_CICHL

[MacBullyBoy]

Hi folks,

I've just picked up an Andream unit from Ebay (at least, that's what the listing said it was) and have installed it today. I'm looking for some advice on a couple of things;

1. What's the correct model for my unit and what firmware should I install?
2. I didn't have an awful lot of time to play around with it after the install as it took me longer than expected to get the unit in place! But what I did notice is that the only way I could access the MMI menu was by holding down the "back" button for 3 seconds, and not the "menu" button. Is that normal?

FYI, here are the details from my unit;

SDK Version; 25.0.0.7.0.0.2.0
CUST Version: B_V1.2.5
MCU Version: 20.10.22.16
HW Version BMW_NBT

Many thanks in advance for your advice!

[Homersbud]

Originally Posted by MacBullyBoy

Hi folks,

I've just picked up an Andream unit from Ebay (at least, that's what the listing said it was) and have installed it today. I'm looking for some advice on a couple of things;

1. What's the correct model for my unit and what firmware should I install?
2. I didn't have an awful lot of time to play around with it after the install as it took me longer than expected to get the unit in place! But what I did notice is that the only way I could access the MMI menu was by holding down the "back" button for 3 seconds, and not the "menu" button. Is that normal?

FYI, here are the details from my unit;

SDK Version; 25.0.0.7.0.0.2.0
CUST Version: B_V1.2.5
MCU Version: 20.10.22.16
HW Version BMW_NBT

Many thanks in advance for your advice!

v1.6.2 latest - check 1st page under section below for download. I got same box I installed a cpl yrs ago now.

Andream B-Version [NBT] [GEMINI_PACK.BIN]
Model: EW-BMCP-NBT02B

[eltech]

It is possible to answer a call with a button on the steering wheel, for this it is necessary that the phone is connected via Bluetooth with the OEM system of the car and with the MMI. The connection to AA is wireless via WIFI. At the first moment, both Bluetooth connections will be activated, then only the connection with the OEM will remain, with the MMI there will be a connection via WIFI. In this case, I have the opportunity to answer calls (mobile only) from the button on the steering wheel. Calls from whatsapp, telegram, Viber have to be activated from the phone. This is how it works for me - X1 F48 entrynav (equivalent to NBT)

With this scheme , audio connections occur via Bluetooth with the OEM system and the call passes through the OEM . Through MMI only management. There was a moment when the connection with the MMI was lost (the AA interface was changed to the MMI interface), but the call was not interrupted.

Regarding the stretched icons and the lack of screen separation on the 8.8 display On my POCO X3 PRO phone, everything works as it should. I recently conducted an experiment - I flashed an old phone to android 11 and connected it to MMI (only through a wire since the phone did not have wifi 5GHz), so there was no screen separation with this phone and the icons were disproportionate. I do not know how to explain it.

[muniz_ri]

Originally Posted by guafra

Hello everyone, Andream B2 - Samsung S10E wireless, I just got AA COOLWALK, everything is good for beta, the only thing GOOGLE assistant voice commands don't work while driving..Anyone have problem with the commands anyway vowels ?? Thank you

I had the same issue when I upgraded from a Samsung S10E to a Samsung S21FE.

With a wireless connection, Google Assistant works when the car is not moving but does not work when the car is in motion. It works with no issues when using a wired connection.

I looked extensively for a solution but no luck. My workaround is to use a Motorola MA1 and works fine.

[pacstealer]

Originally Posted by ringo9

According to the instructions for this model year F20 the correct DIP switch settings are still: First 3 ON, the rest OFF so I guess it's not that.

If I want to use the OEM BT, does that mean I will need to have my phone paired with 2 devices simultaneously every time?

I also noticed I could not answer a call from the steering wheel Phone button, only via iDrive. Is that due to not using OEM BT?

Here is a screenshot of my F/W screen:

yes, it's because you have to use OEM BT to use the steerihg wheel controls
use that to live better trust me