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?
Hi All,
I need to find some info for the Can adapter so i can fix my issue and help other people with similar problems too .Owner of an MTCD PX5 unit, specific for Mercedes ML (W164) that came with the Can adapter.
From day one the steer wheel buttons worked (vol up/down, phone) and reverse camera out of the box BUT i had no vehicle info at all (door opened, fuel level, temperature, parking sensors etc) as many of the users especially on VW units have. The car is a 2010 model therefore the canbus info should be plenty. Tried all the combinations of CanBus under the extra settings with no luck.
One think i noticed is that i had NO Vehicle.apk or microntek apk and MTCCanbus.apk installed on the unit. I tried to install but installation was failing for both. Even copying to system/app/** didn't worked.
Any idea ?
BTW Anyone knows what is the Knob Mode under extra settings ? Mine is set to : 2 10k/20K ADC Ports
Details:
Unit: MTCD PX5
MCU: MTCE_GS_V3.00_3
ROM: Halk9 Mod 3.1 (Android 8)
Can Adapter : GS 10280514 / HW:V2 SW:V3
Can adapter Setting: 23 Benz_B200(simple)
Hi, i have the same car the same headunit and the same problem.
All is fine but i want to have more can-informations/functions.
zollaki said:
Hi, i have the same car the same headunit and the same problem.
All is fine but i want to have more can-informations/functions.
Click to expand...
Click to collapse
Good to know that this is a generic issue and not specific to my unit and car. It seems a lot of people with Mercedes cars have similar problems. I wonder if this is related with the cheap implementation of the Chinese Can adapters or related with the car.
Will keep searching
Another thread is open with more technical details for similar issue, more HW oriented though here > https://forum.xda-developers.com/android-auto/mtcd-discussion-questions-development
I have the same car w164 and px5 android 8
The same problem.
No I have more problems the canbas stop working no reverse camera no Wheel key vol working and no led light on unit key, I think my canbus dead ?
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.
Hello ...
I have a problem with my eonon (klyde) px3 unit. Ever since I bought it, I have had a problem with usb ports.
When I use the USB dashcam and activate it, or when I use the USB flash disks from the speakers to listen to an electronic hiss, like electronic processing noise.. :crying:
If I turn the volume down to 0 the noise ends.
I tried to solve it like this:
- I replaced with new mtcd / mtce,
- I updated to the latest mcu version
- I flash mcu modified by wadzio( the audio sound is better, but the problem remains.)
- Eonon obviously tells me that it is normal to lower AMP to - 20 but the problem remains the same.
- I connected the chassis of the unit to the ground of the machine.
- I connected a 12v filter that is used in the car units of a good audio brand, to eliminate the hiss of the engine and alternator
Neither of these things solved the problems
Do you know if it is possible to install resistors, capacitors, or solve the problem with me or try to find it? Thanks
You are correct that the problem is a hardware issue and not software.
I dont own this variant, but willing to help - if I can get a unit sent to me, I could attempt to find root cause and develop a fix that could then be shared with the community.
marchnz said:
You are correct that the problem is a hardware issue and not software.
I dont own this variant, but willing to help - if I can get a unit sent to me, I could attempt to find root cause and develop a fix that could then be shared with the community.
Click to expand...
Click to collapse
Thanks ...
I have already changed the mtcd cardboard but nothing ..
- The problem is I have the px3 coreboard,
- Display management motherboard that interferes mtcd board,
- Mtcd motherboard badly designed