[RedErik]

Originally Posted by Rgyjil

Thanks for the specifications! Exactly what I was looking for. Does this issue also persist with splitters that have the diode that prevents current from flowing into the Android screen?

Regardless, I suppose ordering the Blankenburg 4605.01 and two Fakra cables would be the safest option.

Apparently it doesn't matter that the diplexer and cables are Z type and the car's connectors are C type?

diplexer
0,5m cable Diplexer-HU
1m cable Diplexer-Android

Seems pretty reasonably priced in total.

I'm not sure about splitters with diods, the circuitry of this diplexer is not super complicated so I wouldn't be surprised if Chinese manged to copy that and implement in a splitter cable. But as you said, for what it costs it's a safer option and proven to work.

As for the Fakra Z connectors, the Z stands for universal coding that fits all other types, including C.

[Bfgrhth]

76544tgvhju

[Kri]

Uploaded 2.0.3 , again no testing / changelog

Kri

[nobuno]

I tested 2.03 and it seems that the battery optimization app has decreased considerably. Next week I will test again on the 8/256 A11.

[murzik]

I am considering to purchase 12.3 snapdragon 662 6/128 unit for F10 from Anvin. Any cons ? Are those unit any different from those from Navifly or Medeke?

[RedErik]

Originally Posted by murzik

I am considering to purchase 12.3 snapdragon 662 6/128 unit for F10 from Anvin. Any cons ? Are those unit any different from those from Navifly or Medeke?

As long as they're SD662 then it's all the same.

[orha12]

Hi i just bought 10.25 android screen.
And it seems like i couldn't get coding the i-drive to be on full screen.
It always half screen.
I'v already adjust the screen settings on the android screen.
Tried with bimmercode and the resolution is great but half screen is showing.
Tried in the past to code 8.8 screen and it's same result.
Tried with esys also (great member from the forum tried to help me).

Is there any other issue in my HU that doesn't let me to make the coding perfect?
Do i need to look for other coding line also?
Please help me i don't know what to do.

[carina77]

Originally Posted by orha12

Hi i just bought 10.25 android screen.
And it seems like i couldn't get coding the i-drive to be on full screen.
It always half screen.
I'v already adjust the screen settings on the android screen.
Tried with bimmercode and the resolution is great but half screen is showing.
Tried in the past to code 8.8 screen and it's same result.
Tried with esys also (great member from the forum tried to help me).

Is there any other issue in my HU that doesn't let me to make the coding perfect?
Do i need to look for other coding line also?
Please help me i don't know what to do.

https://www.bimmerpost.com/forums/sh...php?p=28684954

[murzik]

Got 4G Supported BAND from Avin.
They have SD662 units with North America bands in stock now.

North America
GSM: 850 / 900 / 1900
EVDO: BC0
WCDMA: B2, B4, B5, B8
TD-SCDMA: B34, B39
FDD-LTE: B2, B4, B5, B7, B8
TDD-LTE: B38, B41

International
GSM: 850 / 900 / 1800
EVDO: BC0
WCDMA: B1, B5, B8
TD-SCDMA: B34, B39
FDD-LTE: B1, B3, B5, B7, B8
TDD-LTE: B38, B39, B40, B41

[tmwmad]

Guys I've been supplied an update for my android 11 unit supplied by Avin:- Ksw-R-M600_OS_v2.0.3-ota.zip. I'm not aware of the details in change log but If anyone would like a copy it can be found here.

https://drive.google.com/file/d/13Jp...w?usp=drivesdk

If this is not allowed admin please delete and accept my apologies.

[fabian.zac]

wow

[murzik]

Did anyone managed to root ? I followed Android 10 rooting procedure. But root checker indicates that device is not rooted.

[murzik]

I've received 12.3" unit from AVIN. But, brightness and contrasst seems lower then my older 10" android 9 unit. Especially contrast is low, colors are wased out. Screen looks like old TFT. Are they all like that?

[RedErik]

Originally Posted by murzik

I've received 12.3" unit from AVIN. But, brightness and contrasst seems lower then my older 10" android 9 unit. Especially contrast is low, colors are wased out. Screen looks like old TFT. Are they all like that?

Check if you still have this matte, thick, blue antiglare screen protector on. It's meant to imitate OEM antiglare coating, but it's only a poorly made screen protector.

[murzik]

Originally Posted by RedErik

Check if you still have this matte, thick, blue antiglare screen protector on. It's meant to imitate OEM antiglare coating, but it's only a poorly made screen protector.

That "antiglare" screen protector I removed right away. Still, had to kick the brightness up to 100%. Screen is kind of usable, but to my surprise noticeably worse then my old unit.

[BlackBird11]

Originally Posted by RedErik

Check if you still have this matte, thick, blue antiglare screen protector on. It's meant to imitate OEM antiglare coating, but it's only a poorly made screen protector.

do you recommend removing it? i still have mine on - especially for direct sun it seems like it is the better option?

[RedErik]

Originally Posted by BlackBird11

do you recommend removing it? i still have mine on - especially for direct sun it seems like it is the better option?

I don't give many recommendations these days anyways. Last thing I'm going to tell you is how you feel about your screen protector, whether you like it or not is up to you. All I said it's a fake antiglare and not how OEM screens are made. It's a screen protector and as any other screen protector that is not 100% clear there are going to be some distortions.

[bob.g]

Hey guys,

i installed a 12.3" android 11 662 mekede unit in my e90 back in december. I had no nav before so i had to cut a hole in the dash. I also installed the included cheap external mic and ran it to the top left corner of the windshield since i had heard the built in mic was awful.

Everything works fine and i have been happy with it except for one issue. The phone calls..sometimes they work fine, other times the person cant hear me on the other end. It isn't a low volume issue like many people have complained about with the built in mic. When mine doesn't work, the mic is dead and doesn't pic up any sound at all.

I did a test on a day where it wasn't working. I called another phone, picked it up, and tapped on the mekede external mic and heard nothing. So its as if the mic was disabled completely. I also did a test on a day where it worked fine, called another phone and tapped on the mekede external mic and i could clearly hear the taps. So i know the unit detects and uses the external mic. Its just that some days, its as if it just disables the mic completely.

Has anyone else had that issue? Even though i feel like this is a software glitch, i haven't really seen others mention it. So im tempted to disconnect the external mic for a while to see what happens.

[7ambrion]

after i have installed ota 2.0, HU dont accept any update files ))
so maybe now they must be in spesiell folder or may be some bug after last update (

do somebody know some other method to install ota?

[BlackBird11]

Originally Posted by RedErik

I don't give many recommendations these days anyways. Last thing I'm going to tell you is how you feel about your screen protector, whether you like it or not is up to you. All I said it's a fake antiglare and not how OEM screens are made. It's a screen protector and as any other screen protector that is not 100% clear there are going to be some distortions.

sure, i just asked for your personal opinion and the decision-making is up to me

[8727]

Hi,

I installed a 12.3'' SD662 monitor from navifly. After its installation, BMW iDrive often reboots when I turn on the ignition or start the engine. It happens like 80% of startups.
My screen typically goes like this:
1. iDrive navigation map (thing on the screen last time I stopped the system) appears for a few seconds
2. the screen goes blank and says "No Signal"
3. iDrive startup screen follows saying "BMW connected drive"
4. then, screen returns to the first point and gets ready for use.
After this reboot, the system runs stable and has no problem.

Does anybody experience this and know any fix?
I suspect the power supply may be insufficient for the iDrive system at startup, which causes the reboot. I tried the followings but the reboot persisted.
- changing battery type to 80Ah or 105Ah (originally, this was set 90Ah)
- dropped screen brightness in Android setting (this may save some electricity?)
My battery shows around 12.5V, so I think battery itself is healthy.

Is there any coding option to change the power threshold to trigger iDrive reboot?
Any other help is also appreciated.

[RedErik]

Originally Posted by 8727

Hi,

I installed a 12.3'' SD662 monitor from navifly. After its installation, BMW iDrive often reboots when I turn on the ignition or start the engine. It happens like 80% of startups.
My screen typically goes like this:
1. iDrive navigation map (thing on the screen last time I stopped the system) appears for a few seconds
2. the screen goes blank and says "No Signal"
3. iDrive startup screen follows saying "BMW connected drive"
4. then, screen returns to the first point and gets ready for use.
After this reboot, the system runs stable and has no problem.

Does anybody experience this and know any fix?
I suspect the power supply may be insufficient for the iDrive system at startup, which causes the reboot. I tried the followings but the reboot persisted.
- changing battery type to 80Ah or 105Ah (originally, this was set 90Ah)
- dropped screen brightness in Android setting (this may save some electricity?)
My battery shows around 12.5V, so I think battery itself is healthy.

Is there any coding option to change the power threshold to trigger iDrive reboot?
Any other help is also appreciated.

No, there is no "threshold to trigger iDrive reboot" and no, your issue is not with power delivery. Your headunit sits on a 20A fuse which is more than enough to drive everything including your Android. If all connected devices draw more than that, then fuse pops and nothing works anymore.

Your issue is with CAN bus and Android itself. Either the MCU is doing something stupid, a cable on your adapter harness is pinched or something is not connected correctly.