[Mjam]

1. Volume bug i 3.8.3 (since 3.8.0): Volume settings does not stick between reboots. The graphical representation will seem to be right, but just touching the bar will synchronize volume to its graphical representation.

This can be fixed by installing 3.6.3 on top, without loosing the new features of 3.8.3 (like global iDrive). System info will still show 3.8.3.

(I did this two times, but no guaranties. Also, one should install 3.8.3 again before upgrade to next version, just in case.)

2. Seatbelt warning light bug (Dashboard): Both driver and passenger must fasten seatbelts for the warning light to go off, even if no passenger is present.

Edit: According to replies, this bug probably only applies to E8x and E9x models. I will contact my seller with this info. As always, the chance for a bug to be fixed, increase with the number of reports, so all who wants this and other bugs fixed, should report them to their seller.

[Kri]

Originally Posted by Alves_369

Thanks Kri, so i can't customize that ? Any solution ir another APP? Another question i have carly obd2 bluetooth..i can t pair with my android.. this is why?

Yes you can`t customize that :/

Bluetooth is also limited only to BT Hands free and music support, there is no generall BT support like for mouse/keyboard/ other BT type devices.
This is not changeable.

Kri

[kenza750]

Originally Posted by Mirjam

1. Volume bug i 3.8.3 (since 3.8.0): Volume settings does not stick between reboots. The graphical representation will seem to be right, but just touching the bar will synchronize volume to its graphical representation.

This can be fixed by installing 3.6.3 on top, without loosing the new features of 3.8.3 (like global iDrive). System info will still show 3.8.3.

(I did this two times, but no guaranties. Also, one should install 3.8.3 again before upgrade to next version, just in case.)

2. Seatbelt warning light bug (Dashboard): Both driver and passenger must fasten seatbelts for the warning light to go off, even if no passenger is present.

This probably applies to all E6x, E8x and E9x models. Can anyone confirm if this bug also is present in F models?

@2: I have an E61. No seatbelt issues. Works for driver and passenger independently. I am running 3.8.3 on SD625 with the latest MCU from Andream (191127)

[Alpina_Guy]

Originally Posted by Mirjam

[B]
2. Seatbelt warning light bug (Dashboard): Both driver and passenger must fasten seatbelts for the warning light to go off, even if no passenger is present.

This probably applies to all E6x, E8x and E9x models. Can anyone confirm if this bug also is present in F models?

No bug on my D5 (F11)

[Cskelton]

Nood question. What are the OEM files for?

[floc]

Originally Posted by Mirjam

1. Volume bug i 3.8.3 (since 3.8.0): Volume settings does not stick between reboots. The graphical representation will seem to be right, but just touching the bar will synchronize volume to its graphical representation.

This can be fixed by installing 3.6.3 on top, without loosing the new features of 3.8.3 (like global iDrive). System info will still show 3.8.3.

(I did this two times, but no guaranties. Also, one should install 3.8.3 again before upgrade to next version, just in case.)

so you have to install 3.8.3, install 3.6.3 and then root, correct?

[Soprono]

Has anyone who perhaps has an Avin unit attempted their UI update? They sent me two files

1. Ksw-P-Userdebug_OS_v3.0.8-ota.zip
2. Qualcomm-OEM（8)_2019.12.11.zip

Told to put the Ksw-P-Userdebug_OS_v3.0.8-ota.zip file on the root of a USB stick and then the OEM folder which was inside the Qualcomm-OEM（8)_2019.12.11.zip file on the root of the USB too. The OEM file contains the factory_config.xml and splash.img file.

Putting the stick in the car yields no results. I have tried 3 different USB sticks now. All less than 32GB, FAT32 formatted and named in the way Avin requires but still nothing? Iv also tried an SD card and also attempted.

[elnino72]

I have a doubt his rear camera acquired for my e92, it is the one that replaces the handle of the tailgate but it is pointed too low, what rear camera did you buy?

[Mjam]

Originally Posted by floc

so you have to install 3.8.3, install 3.6.3 and then root, correct?

Yes, but no root necessary. I don't know why this works, or why the version is not completely downgraded, and hence global iDrive support is kept (this was introduced in 3.8.0, right?). Previously a downgrade would be complete.

[mangozac]

Originally Posted by mangozac

The surrounding traces look like this will suit a TJA1020 LIN Transceiver IC (https://www.nxp.com/products/interfa...ceiver:TJA1020). The CAN transceivers fitted are also NXP so that makes this even more likely. I expect then that mounting this LIN IC will allow the MCU to begin performing the related E series LIN functions.

The second and more annoying problem is that the power for the device is wired into the Accessory terminal R on the car, so the entire unit is powered down immediately when the ignition is turned off. From my research this seems to be a common, lazy approach with these but I'm curious if anybody has managed to get one working properly with both power and accessory signals?

It's late but I'm following up on these posts of mine from last year, for anybody else using these in pre idrive applications.

I can confirm that fitting the LIN transceiver chip and setting the car type to E60/E83 made the steering wheel controls begin to work. Limited information alo becomes available in the "dashboard" screen.

I also swapped the power supply connection so that it's permanently powered. The MCU automatically detects the LIN bus messages and will shut the android unit off when the ignition is turned off. The best thing is that it does a clean shutdown, so that when powered back up the system can resume from where it was (i.e. from the playing song track). I'm disappointed that boot time is still around 30 seconds from turning on the ignition though

[RedErik]

Ok the results of microphones test are in... and are a little bit disappointing. I have purchased the following mics from RS Components:

724-3144 6mm noise cancelling
724-3138 6mm uni-directional
724-3153 9.7mm noise cancelling
754-2104 10mm uni-directional
I also got couple of 4mm mics, but soldering pads are so small I couldn't be bothered with them.

In my opinion the 9.7mm noise cancelling is the way to go. At 80mph with windshield defrost fully on, mic perfectly cancelled out all static noises, and all that was recorded was my own voice. However (there is always "but") all of the tested mics were very quiet. I have some experience with electronics but not much with audio. I assumed that if head unit's pcb has 2.2k ohms resistors for the mic, the 2.2k ohms mics I bought would be direct swap. They are not. If there is an android setting to control mic's volume I can't find it. I have now few options:
1. use OEM side instead
2. raise my voice when I'm talking
3. figure out how to build an amplification circuit and not fry all the rest of head unit
4. look for a 3rd party app to control mic's volume/sensitivity

I'm also open to any suggestions and willing to do more tests if you guys have any ideas.

[ozumct]

Originally Posted by Soprono

Has anyone who perhaps has an Avin unit attempted their UI update? They sent me two files

1. Ksw-P-Userdebug_OS_v3.0.8-ota.zip
2. Qualcomm-OEM（8)_2019.12.11.zip

Told to put the Ksw-P-Userdebug_OS_v3.0.8-ota.zip file on the root of a USB stick and then the OEM folder which was inside the Qualcomm-OEM（8)_2019.12.11.zip file on the root of the USB too. The OEM file contains the factory_config.xml and splash.img file.

Putting the stick in the car yields no results. I have tried 3 different USB sticks now. All less than 32GB, FAT32 formatted and named in the way Avin requires but still nothing? Iv also tried an SD card and also attempted.

You have to stick the USB into the USB female adapter that comes directly from your Avin screen (cable harness provided by Avin) - and not into the cars USB input.

[foxi_brown]

Hi guys,

I have my SD625 unit installed into a BMW X1 F48 and I'm overall very satisfied with it. I have one question:

I didn't have Audio right out of the box with the Android HU. As the F48 (2019) doesn't have an AUX input (only USB) my seller (Aliexpress) provided an USB -> AUX converter (appearently from KSW). I don't know how this adapter work but at least it is working Unfortunately there is a slight delay between Audio signal and Video output. Video is approximately 500ms before Audio signal. This happens in all Video sources (Youtube, Twitch etc.) Anybody else has this problem or has an idea how to fix that?

Thank you for your help!

[Kostisuk]

Originally Posted by Mirjam

1. Volume bug i 3.8.3 (since 3.8.0): Volume settings does not stick between reboots. The graphical representation will seem to be right, but just touching the bar will synchronize volume to its graphical representation.

This can be fixed by installing 3.6.3 on top, without loosing the new features of 3.8.3 (like global iDrive). System info will still show 3.8.3.

(I did this two times, but no guaranties. Also, one should install 3.8.3 again before upgrade to next version, just in case.)

2. Seatbelt warning light bug (Dashboard): Both driver and passenger must fasten seatbelts for the warning light to go off, even if no passenger is present.

Edit: According to replies, this bug probably only applies to E8x and E9x models. I will contact my seller with this info. As always, the chance for a bug to be fixed, increase with the number of reports, so all who wants this and other bugs fixed, should report them to their seller.

Can you please upload 3.6.3 ?

Originally Posted by Cskelton

Nood question. What are the OEM files for?

I was wondering the same

[lehtee]

Originally Posted by Kostisuk

Can you please upload 3.6.3 ?




I was wondering the same

3.6.3: https://mega.nz/#!RQVFSaRR!IshEBaaVQiyz1m6ObxBPqzH4VJt0QYOjwVvGT48 HA28

OEM contains the factory_config.xml,which is used to save system settings. It only needs to be updated when they add new factory setting. To update copy the OEM folder to root of your usb stick (unzip!)

[Alves_369]

I guys how can i reduce the boot time on mine?i have the Slash screen of BMW M..thanks

[Victor8490]

Hello! I recently installed a reversing camera by connecting the power directly to the screen without connecting to the rear light.

Is it necessary to configure something in the factory menu?

Because when I reverse gear nothing happens

I have it connected as in the following photos

[Mjam]

Originally Posted by Victor8490

Is it necessary to configure something in the factory menu?

System, Camera selection: Adding camera.
Vehicle, Gear selection: Automatic (but try Manual if this doesn't work).

[Victor8490]

Originally Posted by Mirjam

System, Camera selection: Adding camera.
Vehicle, Gear selection: Automatic (but try Manual if this doesn't work).

First of all Thank you for your help.

But it still doesn't work.
I have tried manual and automatic and it does not work.
Can protocol settings, there camera selection, 360 camera and DVR how they should be?

[Mjam]

Originally Posted by Victor8490

Can protocol settings, there camera selection, 360 camera and DVR how they should be?

Can protocol: Is your car CIC, NBT or NBT-EVO?

Camera selection: This setting should not be 360, not Original camera, but Adding camera (or whatever the first choice is named now).

DVR is not relevant here.

How do you get this blue "No signal" screen? You should not switch to DVR. Your pictured connections seems to be correct, but the unit should stay at the Android screen if "nothing happens". When things are working, the unit should automatically switch from Android to the PDC / Rear camera screen when in reverse gear (this is not the same as the DVR screen).

[Victor8490]

Originally Posted by Mirjam

Can protocol: Is your car CIC, NBT or NBT-EVO?

Camera selection: This setting should not be 360, not Original camera, but Adding camera (or whatever the first choice is named now).

DVR is not relevant here.

How do you get this blue "No signal" screen? Your pictured connections seems to be correct, but the unit should stay at the Android screen if "nothing happens". When things are working, the unit should automatically switch from Android to the PDC / Rear camera screen when in reverse gear.

my screen is 6-pin cic

since I updated to the latest version 3.8.3 only nbt/nbt evo canbus 1.0 and nbt/nbt evo canbus 1.5 nothing of cic appears

that no signal screen appears for something else, what you say happens when I gear backwards I stay on the android screen without doing anything

[Mjam]

Originally Posted by Victor8490

since I updated to the latest version 3.8.3 only nbt/nbt evo canbus 1.0 and nbt/nbt evo canbus 1.5 nothing of cic appears

Did you import the factory_config as well? Verify that you have this inside that file (you can add this if not):

<CANBusProtocol>
<Protocol id = "1">[1]CCC / EVO_1.0DIN_OldCAN</Protocol>
<Protocol id = "2">[2]CIC / EVO_1.0DIN_NewCAN</Protocol>
<Protocol id = "3">[3]NBT / EVO_1.5DIN_OldCAN</Protocol>
<Protocol id = "4">[4]NBT-EVO / EVO_1.5DIN_NewCAN</Protocol>
</CANBusProtocol>

What MCU are you on?