11-22-2019, 09:14 AM | #46 |
First Lieutenant
84
Rep 396
Posts |
Andream
Just finished the install. I didn't have to move anything to glovebox as I had just enough space below the HU.
Initial impressions (about half an hour use) - All seems to work really well. Sound quality is good. It's better than bluetooth, but not as good as USB. I tried playing music through USB while carplay is connected and this works too. I have fibre optic cable, which I had to move. I have to say, this is slightly different to what was advertised on their Andream aliexpress store when I bought it. I feel like this is an updated unit and they've also updated their listing to reflect the new unit. |
Appreciate
2
theblues86.50 Firefly1337846.00 |
11-22-2019, 10:06 AM | #49 |
First Lieutenant
84
Rep 396
Posts |
|
Appreciate
1
theblues86.50 |
11-22-2019, 10:09 AM | #50 |
First Lieutenant
84
Rep 396
Posts |
Yeah, the dip switches on my unit are slightly different. See attached. 1 is track 7 and is oem car cam apparently. I have no idea what "track" is though?
|
Appreciate
0
|
11-22-2019, 10:25 AM | #51 |
Second Lieutenant
846
Rep 280
Posts |
Thanks for the pic. Where did you get it from, though?
My unit came with no instructions whatsoever. I don't really need any aside from the dip switch setup but yours differs from the one they have on their sales page. Looks like I will have to try out a few combinations... According to their sales page they also feature their own PDC&Camera screen generated by the MCU (like in the Android 10.25" touch displays). My car does not have a camera and I don't want to use that screen. Maybe I will have to set the switch to on anyway to fake using the original screen. |
Appreciate
0
|
11-22-2019, 10:27 AM | #52 | |
First Lieutenant
84
Rep 396
Posts |
Quote:
I didn't receive any installation instructions either... all instructions are on the product page on the link above. I don't have a camera either, just PDC and all of it works with above. |
|
Appreciate
0
|
11-22-2019, 10:32 AM | #53 | ||
Second Lieutenant
846
Rep 280
Posts |
Quote:
I have this one: https://www.aliexpress.com/item/4000174276908.html Quote:
You set switch 7 to 'on' (for OEM cam) while not having a camera installed. |
||
Appreciate
0
|
11-22-2019, 10:40 AM | #54 | |
First Lieutenant
84
Rep 396
Posts |
Quote:
You should try my dip settings then? |
|
Appreciate
0
|
11-22-2019, 10:48 AM | #55 |
Second Lieutenant
846
Rep 280
Posts |
Ok, the link works after changing my country to United Kingdom (does not work for Germany apparently).
I will definitely try your config, we seem to have the same setup (NBT EVO, no camera, 8.8", 2015). Thanks I will report back tomorrow. |
Appreciate
0
|
11-22-2019, 01:16 PM | #56 | |
Enlisted Member
10
Rep 45
Posts |
Quote:
The problem is my CarPlay box is another one lol |
|
Appreciate
0
|
11-22-2019, 02:06 PM | #57 | ||
Second Lieutenant
73
Rep 237
Posts |
Quote:
Quote:
Firefly1337 do you have 8.8 non touch screen? I'm in the same situation with my original screen |
||
Appreciate
0
|
11-22-2019, 02:29 PM | #58 |
Second Lieutenant
87
Rep 212
Posts |
So this product:
https://www.aliexpress.com/item/4000174276908.html Is different than this: https://www.aliexpress.com/item/4000133829758.html Based on the DIP switch positions. |
Appreciate
0
|
11-22-2019, 04:02 PM | #59 | |
Lieutenant
370
Rep 552
Posts |
Quote:
They also both have the same model number in specifications: EW-BMCP-NBT01A You can message them to confirm if you're concerned about this. Different dip switch reference graphic does not represent what you would be getting. |
|
Appreciate
0
|
11-22-2019, 07:42 PM | #60 | |
Private
22
Rep 75
Posts |
Andream $148/each
Quote:
|
|
Appreciate
0
|
11-22-2019, 08:01 PM | #61 | |
Second Lieutenant
87
Rep 212
Posts |
Quote:
|
|
Appreciate
0
|
11-23-2019, 01:56 AM | #64 |
First Lieutenant
84
Rep 396
Posts |
|
Appreciate
0
|
11-23-2019, 08:54 AM | #65 | |
Second Lieutenant
73
Rep 237
Posts |
Quote:
|
|
Appreciate
0
|
11-23-2019, 09:20 AM | #66 |
Second Lieutenant
846
Rep 280
Posts |
Okay, unit is installed in my car and I just finished my test drive.
First of all my dip switch config: - 1 on (Track OFF) - 2 on (360 OFF) - 3/4/5 on/off/off (for 8.8" 2015) - 6 off (unused?) - 7 on (for OEM camera even though I don't have one) - 8 off (for OEM mic) Everything is working fine including the switching to OEM PDC. My use case is Android Auto with a Pixel 3. Over USB this worked fine out of the box. After plugging in my phone it automatically established a connection through BT, no idea why though (seems unnecessary for wired connections). At this point I connected over WiFi to the unit (pass is '88888888' i.e. 8x8) but I could not get it to work straight away. I decided to take a test drive anyway to try out the unit. Shortly afterwards the unit crashed and only showed a black screen while my phone was telling me it found a WiFi connection for Android Auto. I think it tried to connect via WiFi while being connected over USB which caused the crash. To my knowledge there is no way to force reboot the unit, so you have to park and turn off the car completely to initiate a normal boot. The 2nd try I did not connect USB and instead tried wireless again. I yet have to test the boot behavior, but on a running unit you have to be connected to the WiFi network and initiate the BT connection manually (can be done in the unit's settings). That triggers a popup displaying Android Auto and the phone's name. Confirming the popup instantly opens Android Auto (there is no lag or wait whatsoever) - completely wireless. The WiFi from the unit is 5 GHz by the way, at least that's what my phone connects to (maybe 2.4 GHz is supported concurrently aka Dual-Band). The included antenna works fine and delivers 100% reception. No idea what the BT connection is used for other than sending the trigger to connect and also no idea yet how this 2nd BT connection might interfere with the one from the iDrive. I forgot to bring another phone/camera but I can assure you there was no cable attached to my phone while taking the pictures It really works wireless (but bear in mind that it might only work for Pixel and some Samsung and Nexus devices due to official Google limitations). I am also under the impression that the resolution is not 100% correct. At least I remember it a tiny bit better using HeadUnit Reloaded with custom 160 dpi. But I could be wrong. There is actually not much to say about the iDrive controller input, it just works That's it for now, I will use and test it more in the following days and weeks. Last edited by Firefly1337; 11-23-2019 at 09:28 AM.. |
Appreciate
1
mlev370.00 |
Post Reply |
Bookmarks |
|
|