yashsingh1/xdaforums huggingface dataset:
[MTCD Android Head Units General] slyski:
I have this version: MAX6 version: PX6 HA2_rk3399_9.0_ota (20210301) updated. I want to go back to the previous version, but how? Downgrade is always canceled because the current version is newer. Ask for tips
[MTCD Android Head Units General] thienthanty:
Format usb or sd card to Fat32 :)
[MTCD Android Head Units General] argwallace:
I had wanted to do the same as the other user, downgrade to an earlier version on Android 9 but I get an error too. I have tried multiple USB drives and reformatted them as indicated.
[MTCD Android Head Units General] kovacs.david:
Methods to upgrade Andorid 9 to 10 is described here in detail:

https://xdaforums.com/t/upgrade-met...rockchip-unit-px6-px5-px30-and-other.4132123/

You will need an img file instead of update.zip to do this from SD card. Using USB drive will not work at main version upgrade.
[MTCD Android Head Units General] king_taco:
yes it was fat32, but still no go.
[MTCD Android Head Units General] KevinC4:
What issue did you have?
[MTCD Android Head Units General] shdwkeeper:
Has anyone been able to get the OBDlink MX+ to pair on the Dasaita PX6 Max10 unit? I can see it as available, but I have tried multiple times, factory reseting etc.. and haven't been able to get it to work.
[MTCD Android Head Units General] Guillermo h:
I have my OBDLink MX + working with my PX6 MAX10 unit in my CX5, if it appears as available it is already a big step, once you connect your device to the OBD port of the car, put the ignition in the ON position and verify that the blue led starts flashing ,, which means you are looking to pair with the unit; But the next and immediate step is to open the application (Torque, ForSca, etc.) who finally ends the pairing process, in this step the orange led flashes and if it is successful the red led is activated and remains constant.

Greetings
[MTCD Android Head Units General] shdwkeeper:
So you never even paired it with your headunit first? You just tried to pair it within the application? I tried a few apps, but they can't see the OBDlink at all unless it's already paired with headunit ahead of time. I'll try what you did and report back.
[MTCD Android Head Units General] Guillermo h:
It is paired when you open the application, if you try to do it with the unit it does not execute anything since it only asks you if you want to link with OBDLink MX + but you will not get the successful link confirmation dialog box.

Greetings, try it, if you can; after the first time the following connections are very fast.
[MTCD Android Head Units General] shdwkeeper:
Nope can't get it to pair. Did you change the name of the OBD device or leave as default factory name? Im trying the torque app (flashing car icon) and the default obdlink app. Both just say searching and never connect. I'm on latest firmware for the obdlink mx+ also.
[MTCD Android Head Units General] Guillermo h:
There is no need to change the name of the device, it is important that you always check that the blue light flashes as it indicates that you are trying to pair and the key is in the ON position, and at the same time open the application; If it still does not connect, go back and remove the OBDLink MX + and repeat the operation. Check inside the application in configuration, type of connection (bluetooth), connection (automatic).
[MTCD Android Head Units General] shdwkeeper:
Yup, the blue light is flashing and key is in the ON position, remove the OBDLink MX+ from where, it's not added anywhere because it never connected. The headunit sees the OBDLink but it never connects to it, so I have nothing to remove. Or do you mean unplug it from ODB port? I have the connection set to automatic as well.
[MTCD Android Head Units General] Guillermo h:
Yes, remove it from the OBD port of the car and repeat all the steps.
[MTCD Android Head Units General] Guillermo h:
If you still cannot connect, go to the bluetooth application in settings / all applications / bluetooth and clear the cache memory, remove all available devices and start the whole process again.
[MTCD Android Head Units General] shdwkeeper:
What bluetooth radio (WQ_RF210) do you have? My device is a dasaita.
[MTCD Android Head Units General] Guillermo h:
If I have the same one, my unit is also Dasaita PX6 MAX10.

Make sure that at the time of pairing the OBDLink MX there are no other devices that want to connect with the unit, for example cell phones.
[MTCD Android Head Units General] shdwkeeper:
Is your OBDlink have latest firmware, are you running a Mod? I'm running Hal9k rom. Just trying to narrow it down here.
[MTCD Android Head Units General] Guillermo h:
shdwkeeper, It also happened to me that within the application (Torque, ForScan) it had recognized another device and for this reason it did not connect to the OBDLink MX +, for this reason it is important to delete all the data in the bluetooth application and the OBDII diagnostic application.​
[MTCD Android Head Units General] shdwkeeper:
Ok, I have done that but will try it again. Thanks for your patience. I just want to get this to work.😀
[MTCD Android Head Units General] Guillermo h:
If my OBDLink MX runs the latest software and I don't use hal9k.
[MTCD Android Head Units General] Guillermo h:
Patience too, will do it; Several of us have gone through this process and some had thought about returning the OBDLink MX +, and in the end everything worked.

Greetings
[MTCD Android Head Units General] shdwkeeper:
Ok, I will try all this again, maybe I'll put the original software back on the unit with Android 10, if I can't get it to work. I will turn off Bluetooth on phone, delete cache from Bluetooth App and Diagnostic Apps.

Does your OBDlink software work also? Or just Forscan and Torque?
[MTCD Android Head Units General] shdwkeeper:
Your on Android 9 or 10 with Original software?
[MTCD Android Head Units General] Guillermo h:
Android 10, Works well OBDLink, ForScan, Torque.
[MTCD Android Head Units General] shdwkeeper:
Factory Software image?
[MTCD Android Head Units General] Guillermo h:
Now I don't have an image, but I am running the last update of May 07, 2021 and MCU 3.75b
[MTCD Android Head Units General] shdwkeeper:
What launcher you running?
[MTCD Android Head Units General] Guillermo h:
CWG, CarWebGuru
[MTCD Android Head Units General] shdwkeeper:
Ok im on default software, reset everything nothing is hooked up to the unit and it still will not connect to the obdlink mx+, no idea why. I opened up Torque app and the device is flashing blue and it didn't connect. Cleared cache and started over and nothing connects. I have no idea
[MTCD Android Head Units General] shdwkeeper:
Also, my $10 piece of crap OBD hooks right up to the headunit, but I want the better software and support, that's why I'm trying to get OBDlink Mx+ to work.
[MTCD Android Head Units General] marchnz:
Is MX+ legacy BT password/pin same as Head unit pin.

My OBDLink LX default legacy PIN was changed by a firmware update. It took me sometime to figure out what was going on.
[MTCD Android Head Units General] shdwkeeper:
@marchnz It seems like the pin is a random 6 digit pin, when it connects with my phone it's different every time.
[MTCD Android Head Units General] Guillermo h:
Look within the applications that bluetooth devices are available, I mean Torque / ForScan / OBDLink; at my step that although it already appeared as an available OBDLINK MX + device, it did not connect since another device appeared in the application.
[MTCD Android Head Units General] shdwkeeper:
There is nothing connected at all, it's a brand new fresh install, this OBDLink is the first device to connect to this headunit. It says its available in the Bluetooth app, but it won't connect. Inside the application Torque, OBDLink etc.. there are no bluetooth devices available. It says I need to pair it first, just like the picture I posted previously. I dunno.
[MTCD Android Head Units General] Guillermo h:
It is a great advance to see that your unit recognizes the OBDLINK MX + and that it says it is available, just as you mention it; now the work is linking, but as I write this step again it is the app you use for the diagnosis. In that order of ideas I advise you to provisionally install the ForScan and try to link the OBD through this application, I am attaching an image where this application establishes the available devices, before when I had the same problem as yours, I would see the address of another device that I assume was my I Phone, so I had to clear the cache of both the diagnostic application and the bluetooth. Make sure to give the necessary permissions of the applications you install, for example access to bluetooth.

I encourage that if you can !!!!!
[MTCD Android Head Units General] shdwkeeper:
Ok, I will clear cache. Install the ForScan app, even though I have a Toyota and it's not made for my vehicle, does that matter?
[MTCD Android Head Units General] Guillermo h:
It doesn't matter, all we want is for ForScan to serve us as a linking tool.
[MTCD Android Head Units General] shdwkeeper:
Ok, will try and report back
[MTCD Android Head Units General] sopdu7:
Good morning , my head unit have “hct2”, can i install “hct4” or 6 or 7 ?
[MTCD Android Head Units General] shdwkeeper:
Those are just di

I believe those are just different skins and looks. Make sure your MCU is the correct one though from the manufacturer.
[MTCD Android Head Units General] shdwkeeper:
Never

Couldnt get it to work even with Forscan installed. Spent many hours doing this, and it's not worth the time anymore. My cheap $10 OBD works though. I like the OBDLink MX+ and the options and wish I could get it to work. If someone ever comes up with a step by step on how to do it, that would be great. Right now it seems it's random whether it works or not.
[MTCD Android Head Units General] Gruiter:
Did you ever get it to work? I have the same problem.
[MTCD Android Head Units General] Guillermo h:
I repeat, I went through the same thing and with all the indications given I managed to connect it, it must be doing something wrong. Review again the steps that I have indicated.
[MTCD Android Head Units General] Guillermo h:
Steps to connect OBDLink MX +:

1. Keep the key in the ON position (instrument panel shown).

2. Verify that the blue OBDLink led is flashing.

3. Immediately open the diagnostic app you have (OBDLINK, Torque, etc.) from the previous step.

4. Verify that the orange led is now flashing and finally, if everything has gone well, the red led of the OBDLINK MX + should remain on.

Read this carefully so as not to always have to ask for the same thing, additionally in the diagnostic app settings that have, verify what type of connection they have, the protocol (automatic), allow bluetooth to be activated once the app is opened .
[MTCD Android Head Units General] Gruiter:
Thanks. I try it again.
[MTCD Android Head Units General] shdwkeeper:
Nope, never got it to work. I have a $10 device that works though. Wanted to get the OBDLink to work but couldn't
[MTCD Android Head Units General] marchnz:
Not that, the "LEGACY" pin. It's documented on the OBDLink site and is likely your head unit and ODBLink are different, therefore your unit won't pair.

As I have said a number of times now, check that the headunit and Legacy PIN are the same. Try 0000, if that doesn't work try 1234, but the two must match.

Even then, I had multiple reboots to leaving it for a day with the hal9k v3 mod. It did work.

In any case if people want blazing fast OBD updates and instant/reliable day-on-day connectivity, USB via the OBDlink SX is the only way to go. No comparison between the USB SX and any other BT connected device.

One more time: Forget cheap knock off or Genuine Bluetooth OBD interfaces.

The OBDLink SX USB is the best performing reliable connect-everytime answer.
[MTCD Android Head Units General] Guillermo h:
I have linked my OBDLink MX + adapter without having to get involved with codes (0000,1234, etc); Moreover, I understand that the OBDII handles a six-digit code, while the unit only four digits, I insist that if those people their unit already recognizes the OBDLink MX + and it is as available, they are one step away from making the pairing. In my case, it lasted a long time trying to link the OBDII until I succeeded, despite appearing as available it did not link it, finally I realized that in the application (ForScan) another device with a certain address was available and that it was the cause of not allowing to link the OBDLink MX +, which I assume was my I Phone; which is why I had to remove it through clearing the application cache and it worked. The OBDLink MX + works very well and its connection is very fast and stable, without necessarily being a USB connection.
[MTCD Android Head Units General] themaninblack80:
None of the links are working, anyone have updated ones? Specificaly the P5 - 10 version.
[MTCD Android Head Units General] ikerg:
Which Dasaita model do you have?
[MTCD Android Head Units General] themaninblack80:
PX5 4G Ram+32G Rom
[MTCD Android Head Units General] ikerg:
Which is your current ROM versión?
[MTCD Android Head Units General] themaninblack80:
9
[MTCD Android Head Units General] ikerg:
Take into account that you cant upgrade from A9 to A10 directly. You need to upgrade your recovery partition first
[MTCD Android Head Units General] Rottgrub:
A good rule of thumb is if it ain't broken, don't fix it. That said, if you uncompress the 20170901 update, it also has the 2.61 (maybe 2.62?) MCU update, which is newer than the one listed separately.

Cheers!
[MTCD Android Head Units General] hv006:
thanks a lot for fast responding i updated both i got mcu 2.61 now installed :)
[MTCD Android Head Units General] echudoba:
You have the 8/18/2017 build in it now. MCU is out of date. If you download the Sept one it comes with the mcu. I believe like mine v2.61. Play it safe and go into system settings and back up your settings to sd and gps before you do your update. This will create a dmcu.cfg.

Edit: I see you got it OK
[MTCD Android Head Units General] emre33:
[MENTION=6942549]hotaudio[/MENTION]

MTCD >-> MTCE MCU not compatible?

MTCE

V2.65 https://www.sendspace.com/pro/dl/ufie8k
[MTCD Android Head Units General] marchnz:
Could be a typo. Try comparing this mcu with mcu bundled in latest combo update zip.
[MTCD Android Head Units General] typos1:
I dont think there are any MTCE units . . . yet and if there were I doubt they would be on version 2.65 already . . . unless a company has done what KLD did with MTCB (they made MTCC MCUs as an update for MTCB).
[MTCD Android Head Units General] roly01:
Is anyone experiencing bad sound quality when streaming with Bluetooth? I have a Dasaita 10.2" Android 6.0 PX5 for Jeep Wrangler and the sound quality is great when listening to the normal radio but when streaming through A2DP Bluetooth the sound is horrible and has a lot of background noise.
[MTCD Android Head Units General] marchnz:
That's a shame. Has anyone else noted this issue on these forums ;)
[MTCD Android Head Units General] jawest12:
I have this issue now as well. Same radio, in a wrangler. I don’t use Bluetooth much. But it’s audible in calls too
[MTCD Android Head Units General] typos1:
In one of the 4 other RK3368/PX5 threads, there are some fixes for some BT bugs and other bugs, in fact I think the guy has opened a thread for his fixes, youll have to look through all the threads.
[MTCD Android Head Units General] roly01:
I tried the fix for the Bluetooth echo you are talking about but it has no affect on Bluetooth streamig :/
[MTCD Android Head Units General] ikerg:
Dasaita has tested it...it is labeled without typo as MTCE by hct (developers) and it is fully compatible with MTCD

Enviado desde mi SM-G950F mediante Tapatalk
[MTCD Android Head Units General] typos1:
Ah, thats an interesting development, so it seems either one company or HCT/MTC themselves have done what KLD did with MTCB/C !

Of course, as [MENTION=4974080]marchnz[/MENTION] has found that almost all MTCD MCU are actually interchangeable, even if it is an HA only development everyone should be able to benefit.

Any idea what the differences are ? Has Hotaudio said ? of course I expect there are no changelogs as usual.
[MTCD Android Head Units General] dominicanodcora:
can i use mtce HA v2.65 on my px5 octacore device?

Currently installed MTCD_HA_V2.59a_1
[MTCD Android Head Units General] :
Why not, you have HA mcu in your device! If doesn't work, your device don't work right, today!
[MTCD Android Head Units General] IgMan98:
i have installed last release v2.65 and update 20170926 with wipe data.

after a while WiFi and BT lost connection. and so two times.

what must i downgrade to get working WiFi and BT? v2.65 to v2.59 or 20170926 to 20170818?
[MTCD Android Head Units General] roninbz:
how should I flash it? it works on its recovery or I need TWRP? I don't know how to „import” the exported file....
[MTCD Android Head Units General] echudoba:
Not sure but easier to try mcu first. But before you try it could you see if maps is fixed? You have to try to navigate and see if you get any stop errors. Also check factory settings for anything new. I look at the apk's in the rom and changes have been made to factory settings. Maps is the same version as 9/1 but they may have made other changes to correct the issues with maps.
[MTCD Android Head Units General] RazGame:
Maybe hardware issue ... I have KD unit and I have this problem too.
[MTCD Android Head Units General] roly01:
I believe it maybe a Bluetooth driver issue not hardware. I think it has to do increased streaming bitrate and the chip not handling it properly.
[MTCD Android Head Units General] themaninblack80:
Correct, I saw that mentioned and the thread related to that process
[MTCD Android Head Units General] ikerg:
The upgrade from A9 to A10 is not supported by Dasaita as it is not a direct upgrade and it requires additonal procedures that Dasaita does not provide
[MTCD Android Head Units General] ikerg:
I am asking for the updates....I will publish them once receive them
[MTCD Android Head Units General] defekticon:
I upgraded the GS MTCE MCU today from 3.61 to 3.73 and got the version unmatch-01 error however this px5 is running Android 10, as a result i cannot get the McuUnmatchUnlock.apk to run. it installs, but quits immediately. Is there any solution to this scenario?
[MTCD Android Head Units General] ikerg:
Are you sure both (original and New mcu upgrades were from the same manufacturer?)
[MTCD Android Head Units General] defekticon:
I'm only as sure as this link that GS = Xtrons

MTCD

View and download from Yandex Disk

disk.yandex.com
[MTCD Android Head Units General] defekticon:
Ok so it's slowly dawning on me that the ib90m245ln xtrons unit may not have a GS MCU. Is there anyway that I can verify the MCU type since I've already updated?
[MTCD Android Head Units General] ikerg:
So you didn't check the mcu information prior to upgrade. Now you have to search on xda how to solve it......because there is the answer.
[MTCD Android Head Units General] ikerg:
Try going back to mcu 3.63 or ask xtrons for a support mcu file
[MTCD Android Head Units General] ikerg:
Here you are some repository of mcu

https://disk.yandex.ru/d/umCvHqCDzHccr
[MTCD Android Head Units General] defekticon:
I figured it out, that model is an LM MCU. Which sort of fixes my problem, the LM MCU update worked, but the LM Update.zip on that yandex link appears to be corrupt as it fails signature verification: Signature length doesn't match EOCD Marker. (Unless I'm doing something else wrong here)
[MTCD Android Head Units General] ikerg:
Here you are the only Mcu I found for 3.67d LM manufacturer. it is a sound patched one (sound enhancements included) - NOT VALID FOR DASAITA UNITS (Dasaita Units have the last 3.73 MCU version - see first post)

Take into accuont that this thread is for Dasaita Units (HA manufacturer) so next time post on the corresponding thread/forum
[MTCD Android Head Units General] gianmaxfactor:
Hi everyone, I have just bought an Android head unit. I don't know a lot about, for it comes completely unbranded, although I'm sure of: A-MEDIA, PX5, RK3368, HTC2, Android 10

I would kindly ask to you:

1 - Can I "root" without flashing a cooked rom (I want to just root my current system, it would suffice to my needs)

2 - What kind of updates apply for my system (without flashing any full rom, of course)

Thanks a lot
[MTCD Android Head Units General] ikerg:
This thread is for stock dasaita units and upgrades.

On your device info settings you will have under MCU version which type of unit you have...
[MTCD Android Head Units General] ikerg:
Dasaita will update the links on their web on the following days. Please be aware on

www.dasaita.com
[MTCD Android Head Units General] gianmaxfactor:
Well, thanks, I know something interesting now in my way to understand what's inside my head unit (I didn't ever noticed that "Dasaita" was a vendor, sorry for having posted in the wrong forum
[MTCD Android Head Units General] ikerg:
If your version of mcu starts with MTCD or MTCE then you can post on the threads for that specific units (which Dasaita units are as well MTCE) where you can find all the information you want.

MTCE_XXX_YYYY where xxx is the manufacturer and yyyy is the version

Lot of sellers that sell mtce units but only few are manufacturers as well. Dasaita is manufacturer and seller (HA code on MCU - as previously to Dasaita they called HotAudio)
[MTCD Android Head Units General] Guillermo h:
Update available MCU 3.78 and MAX10 Android 10 OTA 22072021
[MTCD Android Head Units General] gianmaxfactor:
Thanks, it looks like I have got an MTCE_MX one, and from what I found, it's already at its latest version
[MTCD Android Head Units General] pakoner:
kindly, can anyone share the latest dab+ dasaita app? (w8)...

v1.38 I have it; I wanted to know if there is a better app, it is not possible without images \ logo stations
[MTCD Android Head Units General] Clandaries:
Hi all, so i can use the MCU file on PX5 and PX6 devices?

Regards
[MTCD Android Head Units General] Androidmick:
Hello, i own a px5 android 8 (latest) and i would like to install android 9 or 10. Is it possible ? Is there any detailed instructions to do it? Im not an expert so i dont want to brick it .

Thanks
[MTCD Android Head Units General] ikerg:
There are not official tools to do it. So the procedure is not recommended by Dasaita.

There are many threads in forums to do it...but not in this.
[MTCD Android Head Units General] marchnz:
See my thread regarding Upgrading to Android 10 using official free tools.

Check your BT first.

The FYT units are better in this respect:)

My opinion, Dasaita are selling their units at a premium/ high cost, whereas the new FYT units with 7862 are superior and far less buggy.
[MTCD Android Head Units General] majidkorai:
Is there change log available for this update ? What’s new in this ?
[MTCD Android Head Units General] ikerg:
Guys ... have you tried the vivid launcher?

Developers are asking for help to.report bugs and enhancements. It is an exclusive development for mtcd units.

You can ask for new features to be included. Don't miss the opportunity to have a customizable and well.working launcher for our units.

Dasaita is working with the developers as well

Here you are the link for the specific thread. You an install the launcher...Dasaita is now delivering the new products under exclusive RoM integrating vivid launcher.

https://xdaforums.com/t/vivid-launcher-official-post-keep-updating.4335473/

And for US market (USA, Canada & mexico) Dasaita is preparing an exclusive interface....wait for it.....
[MTCD Android Head Units General] ikerg:
No changelogs are available...but mcu updates are more related to support for new canbus/new car models
[MTCD Android Head Units General] wanze2001:
Mod edit - translated by https://www.deepl.com/translator:

Can I use the dasaita dab+ adapter with the new px5 version?

I have currently installed Malaysk Rom but there is no sound in the Dab app....

**********************************

Kann ich den dasaita dab+ Adapter auch mit der neuen px5 Version verwenden?

Aktuell habe ich malaysk Rom drauf aber bei der Dab App kommt kein Ton....