Dasaita MCU with DSP: Bluetooth not working - MTCD Android Head Units Q&A
I have a one year old 7" Dasaita PX5 4GB RAM, Android 8, which performs flawlessly. Even the Blootooth and MIC volume level issue was solved in this unit, it has configured Bluetooth WD-BC6.
I wanted to upgrade to DSP, so instead of removing componentes and soldering wires , I just bought in Ali Express Dasaita Official Store the Dasaita MCU board with DSP:
https://es.aliexpress.com/item/32965198383.html?spm=a2g0s.9042311.0.0.6de363c0vGoD1p
After installation on new MCU board, everything is working fine, except Bluetooth, which is not working, if I go to FACTORY SETTINGS, (Password 126) I can select different Bluetooth Adapters, like: MD725, WQ_BC5, WQ_BC6, WQ_BC8, Parrot_FC6000T, SD-968, SD-BC6, SD-GT936, IVT-i145, SD-8350
But after trying several of them, Bluetooth is still not working. Dues anybody know which one I should select.
etulio said:
I have a one year old 7" Dasaita PX5 4GB RAM, Android 8, which performs flawlessly. Even the Blootooth and MIC volume level issue was solved in this unit, it has configured Bluetooth WD-BC6.
I wanted to upgrade to DSP, so instead of removing componentes and soldering wires , I just bought in Ali Express Dasaita Official Store the Dasaita MCU board with DSP:
https://es.aliexpress.com/item/32965198383.html?spm=a2g0s.9042311.0.0.6de363c0vGoD1p
After installation on new MCU board, everything is working fine, except Bluetooth, which is not working, if I go to FACTORY SETTINGS, (Password 126) I can select different Bluetooth Adapters, like: MD725, WQ_BC5, WQ_BC6, WQ_BC8, Parrot_FC6000T, SD-968, SD-BC6, SD-GT936, IVT-i145, SD-8350
But after trying several of them, Bluetooth is still not working. Dues anybody know which one I should select.
Click to expand...
Click to collapse
what BT module does your new unit have?
I did not check the Bluetooth module and I mounted the unit in the car. I took pictures of the board, but they do not show the BT model. So to check it physically I would have to disassembly again. To save this step, I was asking here just in case somebody has this MCU and knows the anser. But looks like I'll have to dissassembly.
Finally, I removed the new unit to check the BT, and it ios as follows:
The BT card in the "old" (one year old) board is:
Silk Marks in the back of the PCB: GOC-MD-705D
Paper label on top of QFP IC (Probably FW version and date) = A5BC6 1907
To have it working I selected in HU Factory Settings : WQ_BC6
The BT in the new MCU with DSP is smaller (shorter) and marks are:
Silk Marks in the back of the PCB: GOC-RF210 2019.04.27
There are no FW labels in the ICs on Top side of the PCB
What do I have to select to have it working?
In Factory configuration, the available BT optios are:
MD725
WQ_BC5
WQ_BC6
WQ_BC8
Parrot_FC6000T
SD-968
SD-BC6
SD-GT936
IVT-i145
SD-8350
I am attaching pictures of Old and New BT boards.
MCU has the latest FW 3.37, but PX5 has Android 8.0 one year old.
etulio said:
Finally, I removed the new unit to check the BT, and it ios as follows:
The BT card in the "old" (one year old) board is:
Silk Marks in the back of the PCB: GOC-MD-705D
Paper label on top of QFP IC (Probably FW version and date) = A5BC6 1907
To have it working I selected in HU Factory Settings : WQ_BC6
The BT in the new MCU with DSP is smaller (shorter) and marks are:
Silk Marks in the back of the PCB: GOC-RF210 2019.04.27
There are no FW labels in the ICs on Top side of the PCB
What do I have to select to have it working?
In Factory configuration, the available BT optios are:
MD725
WQ_BC5
WQ_BC6
WQ_BC8
Parrot_FC6000T
SD-968
SD-BC6
SD-GT936
IVT-i145
SD-8350
I am attaching pictures of Old and New BT boards.
MCU has the latest FW 3.37, but PX5 has Android 8.0 one year old.
Click to expand...
Click to collapse
Good post, an example of what information to post. Also good /must to know MCU version and that you have upgraded it to the latest available.
Unfortunately I still dont know what BT module you have - it might be a new model or compatible with one of the others lists, or it might require new firmware. Have you tried cycling through all of the MCU BT options, restarting in between? Also try reviewing logcats for BT detected type.
Hi, thank you for your help.
MCU PCB is the latest one: HA-D6100-MAIN VER 0.1 20190701, that integrates a DSP board. MCU FW version is the latest one from Dasaita, MCU 3.37. I tried cycling all MCU BT options with restarting in between, but without success. I do not know how to check Android BT logs.
I purchased this MCU PCB in Aliexpress Dasaita Official Store and I send messages asking for support, but I got no answer. I had to open a dispute to get an answer from Dasaita, now they say that they will send a new BT module, but if the real problem is the lack of support by MCU FW, this new module will not fix the issue.
BT Module and MCU PCB are very new, so probably they will release soon a new MCU FW that will support it, but the Dasaita support
Still not working
etulio said:
Still not working
Click to expand...
Click to collapse
Hello. I had a similar problem. Today I solved it. With the help of seller Dasaita on Aliexpress, I found out that the motherboard has a fresh Bluetooth chip installed. As the seller says installed RF210 Bluetooth 5.0 chip, which is not supported by Android 8. Therefore, all you need to do is install Recovery Android 9, then the firmware with Android 9, and then in the Factory Setting, in the Bluetooth settings on the first tab, select RF210 (it will be added to the list, on Android 8 it simply does not exist). That's all. Everything worked for me. The sound is better than it was on the old Bluetooth chip.
555sssaaa said:
Hello. I had a similar problem. Today I solved it. With the help of seller Dasaita on Aliexpress, I found out that the motherboard has a fresh Bluetooth chip installed. As the seller says installed RF210 Bluetooth 5.0 chip, which is not supported by Android 8. Therefore, all you need to do is install Recovery Android 9, then the firmware with Android 9, and then in the Factory Setting, in the Bluetooth settings on the first tab, select RF210 (it will be added to the list, on Android 8 it simply does not exist). That's all. Everything worked for me. The sound is better than it was on the old Bluetooth chip.
Click to expand...
Click to collapse
Thanks for taking the time, your explanation solves the puzzle. Good to know they finally have an updated BT option, wonder if they improved the code/drivers.
I will add links. I installed Recovery and Android 9 according to the instructions Hal9k. Hal9k, thank you very much!
Link to his Mod - h t t p://4pda.ru/forum/index.php?showtopic=973606&st=0#entry91199154
Link to Recovery for Android 9 - h t t p://4pda.ru/forum/index.php?showtopic=883219&st=24080#entry84508631
The link to the instructions for installing Recovery - h t t p://4pda.ru/forum/index.php?showtopic=891403&st=540#Spoil-77218289-3
Probably on this forum there is a description of the upgrade from Android 8 to Android 9. But I rarely come here. I just saw a problem similar to mine and want to share its solution. I hope this helps someone.
Hello,
I have the PX6 (Adroid 9) with the RF210 BT module, but it doesn't work at all. I've installed the latest MCU and the one before that (MCU 3.45 then MCU 3.53).
I also installed the latest firmware update (20200521). In the end I also installed Hal9k mod, and it still doesn't work.
Does your BT work?
RupOase said:
Hello,
I have the PX6 (Adroid 9) with the RF210 BT module, but it doesn't work at all. I've installed the latest MCU and the one before that (MCU 3.45 then MCU 3.53).
I also installed the latest firmware update (20200521). In the end I also installed Hal9k mod, and it still doesn't work.
Does your BT work?
Click to expand...
Click to collapse
No, it did not work. But I did not try to install Android 9, mine was at Android 8.
SD-BC6
Hi,
I have tried all the BT setting and for me finally working SD-BC6 (PX5 with Android 9 Malaysk mod) . Finally means that my mobile can connect and working and ODB2 module can connect and working. All others setting worked only for mobile or only for ODB2 or not worked at all.
Related
Gala (SDVC) app for PX5?
I can`t find a working SDVC app for my PX5 GS unit. It is my second unit because the first has had a fault and was exchanged. On the first unit I used Graser´s Dasaita tool for volume control. On the new unit that isn´t working anymore and also MyMTCService does not recognise the unit as MTCD and so the sound control is not working. The only thing that is different to the old unit are the connectors. The GPS connector uses now a Fakra plug, but I don´t think that this is a problem since all other GPS apps are working normally. Neither Malaysk, the original GS ROM nor a HA ROM is working. I've tried also different MCU's.
Here you can see the problem with Grasers Dasaita tool. I am not driving and not changing the volume level: https://youtu.be/aT0asijim5g @Graser maybe you can help me?
Bluetooth setting in factory settings.??? MTCD KLD (seicane mk4 golf HU)
I updated the MSU and Seicane sent me a new system update. MCU is MTCE-2.65. After updating was complete i had lost my Bluetooth. WIFI works normal and all buttons around the HU is working normal Bluetooth is missing the device name and pass code that was there when it came stock. wont find my phone or odb2 adapter. I was wondering if there is a posiblity that it some how changed the Bluetooth settings?
Did you find a fix? Hello Cody, Did you get any feedback on this? I've got the same problem on a MTCD GS unit, unresolved! Richard.
MTCE and BLE modules compatibilty
Hi, I really need my PX5 to support Bluetooth low energy (version 4.0 minimum) so I could receive gps beacons, which use the protocol. Looking at the factory menu in my unit i can see that i have BC5 bluetooth module which is version 2.1 only. Other types i can select are MD725, BC6, BC8, FC6000T and SD-968. From what i managed to figure out, only MD725 and BC8 have the 4.0 protocol, however i can't manage to find module that supports them and fits the module slot in my unit. I did actually find the following item: https://www.aliexpress.com/item/32974934318.html It sates both BC8 and I145, which I understand is another module supported bu some units, but not mine. Could someone maybe confirm this one works under BC8 setting? Alternatively, any way to update the bluetooth support in my units to have I145, other than MCU update? because I can't find one for my unit (MTCE_HZA). Thanks for any help!
PX6 MX MCU update failed
Hi there So i downloaded from here MCU MX v3.71 as i have v3.60_1 at the moment. Formatted a 4GB USB stick as FAT32, default allocation list and copied dmcu.img on the root of the USB Then, inserted the stick into HU USB port, clicked on MCU update, it was found, system restarted. next ? surprise: Android green guy dead, and "no command" on the screen. I shut down the car for 5 mins to let the unit go to sleep and when i put the ignition on, the unit started fine, but still having old MCU next, i plugged the USB stick into my computer and surprise: "this disc needs to be formatted". Somehow, android unit didn't update the MCU but damaged the USB stick filesystem. Did anyone have the same issue ? I am afraid now to use a different USB and repeat the process because my reset button is inside the screen and i need to dismantle half the dashboard to reach that button. I have an AOTSR PX6 RK3399 unit with Android 10 and HCT2 kernel (firmware), MCU is MX v3.60 Thanks
tox2k4 said: Hi there So i downloaded from here MCU MX v3.71 as i have v3.60_1 at the moment. Formatted a 4GB USB stick as FAT32, default allocation list and copied dmcu.img on the root of the USB Then, inserted the stick into HU USB port, clicked on MCU update, it was found, system restarted. next ? surprise: Android green guy dead, and "no command" on the screen. I shut down the car for 5 mins to let the unit go to sleep and when i put the ignition on, the unit started fine, but still having old MCU next, i plugged the USB stick into my computer and surprise: "this disc needs to be formatted". Somehow, android unit didn't update the MCU but damaged the USB stick filesystem. Did anyone have the same issue ? I am afraid now to use a different USB and repeat the process because my reset button is inside the screen and i need to dismantle half the dashboard to reach that button. I have an AOTSR PX6 RK3399 unit with Android 10 and HCT2 kernel (firmware), MCU is MX v3.60 Thanks Click to expand... Click to collapse What issue do you think will be resolved by updating the MCU? The MCU isn't Android.
my Waze app keeps crashing... i know that this issue might be from the firmware but i have a 2 unit pieces for Opel Astra J, it has a original fitting HU with DVD player which connects with 2 lots of pin cables to the display, and no reset button or hole. So is not a 1 unit Android, is 2 pieces. All main cables come from the big HU which sits instead of the original HU I am really afraid to put another Android 10 firmware as i don't know how to enter recovery if something goes wrong
tox2k4 said: my Waze app keeps crashing... i know that this issue might be from the firmware but i have a 2 unit pieces for Opel Astra J, it has a original fitting HU with DVD player which connects with 2 lots of pin cables to the display, and no reset button or hole. So is not a 1 unit Android, is 2 pieces. All main cables come from the big HU which sits instead of the original HU I am really afraid to put another Android 10 firmware as i don't know how to enter recovery if something goes wrong Click to expand... Click to collapse You've confused MCU with Android. At that point, I agree, leave it as is.
tox2k4 said: Hi there So i downloaded from here MCU MX v3.71 as i have v3.60_1 at the moment. Formatted a 4GB USB stick as FAT32, default allocation list and copied dmcu.img on the root of the USB Then, inserted the stick into HU USB port, clicked on MCU update, it was found, system restarted. next ? surprise: Android green guy dead, and "no command" on the screen. I shut down the car for 5 mins to let the unit go to sleep and when i put the ignition on, the unit started fine, but still having old MCU next, i plugged the USB stick into my computer and surprise: "this disc needs to be formatted". Somehow, android unit didn't update the MCU but damaged the USB stick filesystem. Did anyone have the same issue ? I am afraid now to use a different USB and repeat the process because my reset button is inside the screen and i need to dismantle half the dashboard to reach that button. I have an AOTSR PX6 RK3399 unit with Android 10 and HCT2 kernel (firmware), MCU is MX v3.60 Thanks Click to expand... Click to collapse hi, i have same AOTSR headunit, can you please post the url where you have downloaded MCU MX v3.71, thanks
tox2k4 said: my Waze app keeps crashing... i know that this issue might be from the firmware but i have a 2 unit pieces for Opel Astra J, it has a original fitting HU with DVD player which connects with 2 lots of pin cables to the display, and no reset button or hole. So is not a 1 unit Android, is 2 pieces. All main cables come from the big HU which sits instead of the original HU I am really afraid to put another Android 10 firmware as i don't know how to enter recovery if something goes wrong Click to expand... Click to collapse same here, Waze keep crashing randomly
vralvi said: hi, i have same AOTSR headunit, can you please post the url where you have downloaded MCU MX v3.71, thanks Click to expand... Click to collapse No, search for it.
vralvi said: same here, Waze keep crashing randomly Click to expand... Click to collapse here is thread: https://forum.xda-developers.com/t/...ith-mx-or-mx2-to-use-it.3913654/post-84413769 I only wanted to update the MCU because it is the last version, but this does not manage applications, it's the ROM that does that, as marchnz said. You may need to ask from your seller support a newer version of the ROM you are running. I did the same but the language barrier is huge, i did not solve anything OR install a custom rom such as Malaysk ROM. I read somewhere here that Waze app needs to be downloaded from Aptoide and has to be a specific version for it to work but i cannot recall which thread was it.
tox2k4 said: here is thread: https://forum.xda-developers.com/t/...ith-mx-or-mx2-to-use-it.3913654/post-84413769 I only wanted to update the MCU because it is the last version, but this does not manage applications, it's the ROM that does that, as marchnz said. You may need to ask from your seller support a newer version of the ROM you are running. I did the same but the language barrier is huge, i did not solve anything OR install a custom rom such as Malaysk ROM. I read somewhere here that Waze app needs to be downloaded from Aptoide and has to be a specific version for it to work but i cannot recall which thread was it. Click to expand... Click to collapse thank you
tox2k4 said: here is thread: https://forum.xda-developers.com/t/...ith-mx-or-mx2-to-use-it.3913654/post-84413769 I only wanted to update the MCU because it is the last version, but this does not manage applications, it's the ROM that does that, as marchnz said. You may need to ask from your seller support a newer version of the ROM you are running. I did the same but the language barrier is huge, i did not solve anything OR install a custom rom such as Malaysk ROM. I read somewhere here that Waze app needs to be downloaded from Aptoide and has to be a specific version for it to work but i cannot recall which thread was it. Click to expand... Click to collapse MCU MX v3.71 worked on my unit, i upgraded from 3.60 with no issues
Xtrons PX5 Android 10 no more audio
Hey guys. I have installed an Xtrons PBX70M164 which is an MTCE GS PX5 4G/64G Android 10 device, about two weeks ago. Things were working fine. But I noticed some days ago that I didn't have any more audio. I was not completely ready with installation because I still needed to install the DAB+ radio. So I was messing with the FM and DAB antenna's. I do have the MOST fiber optic system in my car. I connected an MP3 player to the unit to verify if this could be the problem, but it's working as expected. Then when I connect the Xtrons radio, no more audio... Also one other thing is that I cannot scan for FM channels on my radio anymore? I tried to disconnect the device, factory reset and check all the cables. I'm not sure what else I can do. Is the device broken? What else can I check? Thanks!
Send it back or see an experienced auto electrician/installer.
Update: the device was actually faulty and Xtrons replaced it for a new one.