yashsingh1/xdaforums huggingface dataset:
[MTCD Android Head Units General] Guillermo h:
I share the OTA update link of 16-10-2020 and the official MTCE V3.67 of Dasaita. Cheers

https://drive.google.com/file/d/1fJ...imconversation.0.0.52dc3e5frjVccW&usp=sharing

https://drive.google.com/file/d/1VH...imconversation.0.0.52dc3e5frjVccW&usp=sharing
[MTCD Android Head Units General] thienthanty:
The latest update system is MAX10 HA3_rk3399_10.0_ota(20201019) https://www.sendspace.com/pro/dl/mp1q1q

Work fine with the MAX6 ( Recovery 10 )
[MTCD Android Head Units General] k3dar7:
You know also latest for px5 please?
[MTCD Android Head Units General] thienthanty:
HA3_px5_10.0_ota(20201019) https://www.sendspace.com/pro/dl/w05atl
[MTCD Android Head Units General] k3dar7:
thanks, you really superfast :) btw: from where you get it?
[MTCD Android Head Units General] thienthanty:
From Dasaita.
[MTCD Android Head Units General] Deezy972:
Where can i find this info?
[MTCD Android Head Units General] plablo:
Hi thienthanty, can you upload to drive.google?, sendspace is too slow for me:(
[MTCD Android Head Units General] mikrocefal:
hello ,I have a dasaita PX6 ha-5216-max10-AHD (1024/600) with firmware HA3_rk3399_10.0_ota (20200915) and MTCE_HA_3.62

new firmware official dasaita : HA3_rk3399_10.0_ota (20201113) ==> 2020-11-13 !!

PX6 android 10 （1113）

https://drive.google.com/file/d/1rO-wBK8rvVZsXT_5IjN3MyuMY00utZZX/view?usp=sharing

3.67 MCU

https://drive.google.com/file/d/1VHmt2nffbQdc2iHiy_Pl3rNwLXN4cVea/view?usp=sharing

:)
[MTCD Android Head Units General] plablo:
Thanks for your quick response; downloading ?
[MTCD Android Head Units General] abogrhen:
yesterday i just installed 20201019:p

but it took me more than 4 hours to download from sendspace :crying:

this one is less than 5 minutes

thanks
[MTCD Android Head Units General] Ramias:
Max6 running the latest official Android 9.

How do I delete a paired bluetooth phone? It shows my phone; when I press on the screen, it gives me a box that says "Connect" and "yes or no" but no delete option. I've done the "reset connections" option that is supposed to reset wifi and Bluetooth but it does not remove previously paired phones.
[MTCD Android Head Units General] h@wk3y3:
Hi there,

I'ts been a while since I have been on this site and I see now Android 10 is available....I have some questions.

1/ is this suitable for a Max6 unit and is it a difficult upgrade?

2/ where can I find upgrade instructions

3/ where can I access the required files to download.... fast downloads would be preferred as I recall sendspace files take hours to download.

TIA...
[MTCD Android Head Units General] Guillermo h:
What version of Android do you have?
[MTCD Android Head Units General] h@wk3y3:
[/COLOR]

Android 9 - kernel 4.4.167

MCU Version 3.45_1
[MTCD Android Head Units General] Guillermo h:
I summarize:

1. You must create a boot card with the .img file, it is better to use the complete image that weighs 2.4 gb (micro sd between 4 gb and 16 gb of storage)

2. You must enter recovery mode and from this menu you must select system update from sd. This process can take up to forty minutes.

I have the file and I can share it with you if you want, I recommend you read a little more about this process; it is not complicated.
[MTCD Android Head Units General] h@wk3y3:
Thanks

I've done some research and found this video...https://www.youtube.com/watch?v=GgmSE8d7wM4

Is this the process??

Just noticed I have Bluetooth module WQ_RF210 and wonder it this upgrade will work? If not should I just go with the Android 9 latest firmware?
[MTCD Android Head Units General] markgeary:
Hi, thanks for the reply - Yes i know they all generic units with slight variations. The problem is that the MCU list on the front does not say which class of unit its for. Therefore flashing the ones from the front list is a bit hit and miss especially when other users have said that restoring their own mcu.cfg also solves the same issue. The question is - if you restore a config file to a MCU with the miss match error. Indeed the error disappears but you might also be damaging the unit (as i found it starts to overheat).

Saying that - even though my unit is now up to date, i don't see any difference in functionally or performance. I wonder if its even worth updating?

My main issue is the poor WIFI performance - trying to sync 300 mp3's through plex @ 0.34mb/s is a nightmare!
[MTCD Android Head Units General] typos1:
They ARE NOT "all generic units" and I NEVER said that they were - there are about 15 manufacturers making them to a reference design, with slight differences in minor hardware (radio tuners, wifi chips etc), but interchangeable software.

The thread CLEARLY states its about Dasiata/Hotaudio units which have "HA" MCUs - there is nothing "hit and miss" about it - if you have a GS unit and you tried to flash an HA MCU without using [MENTION=4974080]marchnz[/MENTION]'s guide, then the problem is a user error, ie you have not bothered to read up on these units and how to flash an MCU before doing so, youre lucky that you didnt brick your unit.

The other users that said restoring the mcu.cfg solves the wifi issue, obviously DID read guides properly and are talking about flashing an mcu.cfg file made from an HA unit on an HA unit after updating its MCU. Theyre NOT talking about flashing an mcu.cfg file on a GS unit thats had an HA MCU flashed on it by a user who didnt bother to read either this thread properly or [MENTION=4974080]marchnz[/MENTION]'s. The mcu.cfg file simply restores the MCu's config ie its settings, it will therefore NOT sort out any wifi problems caused by flashing the incorrect MCU on a unit without reading up on how to use a different MCU on your unit.

A heat sink for your wifi chip may help.
[MTCD Android Head Units General] markgeary:
I see this is a friendly place - so ill reply in the SAME tone as you are.

Firstly the sole definition of GENERIC means one board that can be REBRANDED by different manufactures and placed into different markets. The fact that it can take different MCU boards means the base board is generic.

Secondly, i never said anything about the MCU being linked to my wifi chip or the problems being related. The chips are not related and are not on the same board!

Third, it does not mention Hotaudio... it mentions Dasiata... Since i am new to this unit, i assumed that was just the manufacturer and that all PX5 units where the same. (which they are with differing MCU boards)

Lastly, please dont make assumptions of what i have and have not read. I have read alot about the MCU and flashing process. I solved the MCU issue myself by reading it all. My goal is to solve the WIFI issue (which other users are also experiencing). Therefore i tried the other MCU's to see if there was anything related that controlled the power output setting for the wifi chip - as these base setting can only be got at through rooting the device/ or if they added it to the factory settings menu which seems to be controlled by the MCU).
[MTCD Android Head Units General] typos1:
ONE BOARD IS NOT "Rebranded" - the motherboards are different between manufacturers, the units ARE NOT generic ! The MCUs are on the motherboard, no "MCU board" is used and the MCUs used are ALL EXACTLY THE SAME (often mounted on different places on the mobo but the SAME chip), its the MCU software thats slightly different. The SoMs are the part that is the same on all units (I think you were referring to the MCU as "the chip" not the wifi chip).

Reading the thread will reveal its for HA units. NEVER assume !! The thread was created by the manufacturer called "Hotaudio" !

I assumed nothing - your post said that you had flashed an HA MCU onto a GS unit and clearly said that flashing MCUs from it was "hit and miss" when it is not if you flash the correct MCU on to your unit - it was clear from reading your posts that that you had not read (or did not fully understand) the thread.

I did not say that you said anything about the MCU being linked to your wifi chip, but IT IS on all units and ALL wifi chips (whatever type is used) on ALL MTCB/C and D units are on the motherboard with the exception of MTCD Sofia units where it is on the SoM.

Restoring the mcu.cfg file to an HA unit that you have updated the MCU will not EVER, under ANY circumstances, make it get hot - all it does is restore the original MCU settings. The reason it may have made yours hot is probably because you flashed an HA MCU onto a GS unit either without reading [MENTION=4974080]marchnz[/MENTION]'s thread on how to flash a different MCU onto your unit, or if you did read it, its one of the few examples where you cant flash a different MCU onto the unit.

Never flash an MCU if you dont know what units its for - your posts suggest you did this - you say its not clear what unit the MCUs in it are for and yet you went ahead and flashed them anyway.

There are so many things you have said that are incorrect it suggests that you have not read up on things and if you have you have not understood fully. If I sound annoyed its partly because you could have ruined your unit (ie I have your best interest at heart) and partly cos yet again I find myself typing stuff I ve typed many times before because someone has not read/understood things fully (like the wiki for instance).

As I said before a heat sink has helped wifi reception problems in the past, also some units have joint wifi/BT chips with only one antenna fitted, fitting another antenna can solve the problems. If youre after the base settings then just root the device and get them.
[MTCD Android Head Units General] f1x:
I think you guys have too much faith in the MCU :). MCU of these units is nothing more than "configuration storage" and some kind of "repeater" (e.g. Radio App <-> Radio Module). As far as I remember there are 2 virtual COM port connections between MCU and SoC (one for CanBus decoder and second for radio chip, CD, amplifier, hard buttons and touchscreen).

Everything that you can see in Factory Settings is stored inside MCU. All capabilities like CanBus kinds, bluetooth modules or knob modes are stored in MCU and forwarded to SoC using mentioned COM connection. That is all what MCU does on these head units. It could not do nothing more due to very limited FLASH memory (192 or 256KB - I do not remember how much exactly). So there is no rocket science at all :).

For 100% sure I can say that MCU does not deal with Bluetooth or WiFi module directly like everyone was saying. I reversed implementation of bluetooth and Wifi starting from module (driver) up to Java layer (Bluetooth app). Bluetooth and WiFi are connected with SoC using USB intterface (you can observe ioctl calls at sdsdk and gocsdk like for regular USB devices). Also *sdk binaries contain implementation of bluetooth stack.

Modules (drivers) for WiFi and bluetooth are loaded by Android via *sdk binaries. How Android knows what module should be loaded? Using configuration stored in MCU. So starting point of the investigation problems with WiFi are SoC and drivers for WiFi module.
[MTCD Android Head Units General] mlkemac:
Any idea how to reset mcu to factory?

Im having Bluetooth nightmares. I can't even connect devices anymore.

On hotaudio px5 2.59

Tried reflashing mcu no luck.
[MTCD Android Head Units General] typos1:
If you didnt make an mcu.cfg before you flashed then no, short of finding someone else with the exact same unit and asking what all their settings are. Have you made sure the BT module is set to the correct type ?
[MTCD Android Head Units General] marchnz:
Factory settings - Bluetooth type.
[MTCD Android Head Units General] 2shaelib:
I recently bought a new radio and it has hot audio 2.60_b2 MCU . If there is a way to dump it ill supply it here.
[MTCD Android Head Units General] pubeth:
Does anyone kindly help to guide me how to uninstall Google Maps? After I updated 20170901, Google Maps comes with it. I cannot remove it 'cause it keeps freezing once start to navigate.
[MTCD Android Head Units General] echudoba:
Root with kingoroot, install supersu, root explorer and delete it. Then install maps 9.46.2 (last stable version) and don't let it update. OR install a custom rom. Lot's of details with a search for maps, kingoroot, etc.
[MTCD Android Head Units General] ikerg:
All the times I rooted with KingoRoot is impossible to run supersu, as it gives the message that the "Binary is busy"

Tried:

* Root+Delete KingoRoot+install SUperSU --> Same errror

* Root+install SuperSU --> Same Error

as well tried Same procedures above but with a reboot after the rooting --> same Error
[MTCD Android Head Units General] echudoba:
Somewhere in the menu of Supesu is a way to upgrade or uninstall it. Uninstall it and it will remove the other binary that is blocking you. Then reinstall SuperSU.

Edit:

Worked for me did it not work for you? Here is the post I got my info from.

https://xdaforums.com/showpost.php?p=73361039&postcount=1936
[MTCD Android Head Units General] pubeth:
Thank you! I'll try as described above this weekend and let you know the result.
[MTCD Android Head Units General] typos1:
Anyone who upgraded their SoM to an RK3368/PX5 want to sell their old RK3188/PX3 SoM ?
[MTCD Android Head Units General] droc.noles:
Anyone else getting feedback as to when we'll see an Android version leap for our HA PX5 units? A few weeks back my seller mentioned that their engineers were no longer looking at Nougat (which they had mentioned would be ready by the end of August previously), and were moving straight to Oreo in "a month or two". Feeling a bit skeptical to be honest.
[MTCD Android Head Units General] arima0k:
Thank you. I can flash the mcu and update firmware normally, actually hotaudio send me the original firmware via email, the only error i can see in the process is

E: 1 parse errors
handle script error! ignore...

but everyting else -complete, succes!!!- and still booting to the recovery.
[MTCD Android Head Units General] pubeth:
I had loop with purify and kingroot. Cannot go thru. pls help to advice.
[MTCD Android Head Units General] pubeth:
I can root the device and remove google maps now. My bad.
[MTCD Android Head Units General] makes2068:
Use Kingoroot not kingroot!

Send from D6603 with Tapatalk
[MTCD Android Head Units General] Ramias:
I have Max 6 with Android 9. But I have to remove the radio from the car to reach the built-in SD slot. If I pay the 10 euros for the Mod installer, can I use the USB in my car (wired to the radio)? I've used that USB for other updates. I have MTCE_HA v3.65_1 and will install the factory Android 10 for Max10 from the first post in this thread. I have the built-in chip for wireless Apple Car Play. Will that still work if I upgrade to Android 10 for the Max10 (when I have the Max 6)? The settings screen shows my resolution is 1024x600.
[MTCD Android Head Units General] Guillermo h:
Of course it will work for you, I have the same bluetooth module with android 10.
[MTCD Android Head Units General] h@wk3y3:
So I am good to go with the Android 10 upgrade then ... great.

I have MTCE_HA v3.45_1

Can you please share the file/s?
[MTCD Android Head Units General] Ramias:
Does anybody know if the official dasaita Max 10 Android 10 will work on my Max 6 with a slightly different screen resolution? I plan to buy the Mod Installer Pro to do it.

Thank you
[MTCD Android Head Units General] freaksamael:
Does MTCE_V3.65 is the latest version compatible with PX5 or can be upgraded to MTCE_V3.67 ? Thank U!

EDIT: yes, MTCE_V3.67 it's compatible with PX5
[MTCD Android Head Units General] vz_commo:
yes it does, im using it on mine, upgraded using Mod Installer Pro from Android 9 to 10
[MTCD Android Head Units General] nayotake:
Does anyone know if you can change the default apps on the Android 10 default launcher?

Navigation was easy enough to set to whatever app I wanted, but I can't find a way to change the default Radio or Audio Players.
[MTCD Android Head Units General] SYoung:
I also have a PX6(1024x600). It came preinstalled with firmware version 20200706 and MCU version MTCE_HA_V3.57_1. I had some problems with Carplay. Sometimes it connected quickly, sometimes it took a while or it didn't work. I updated both Android and the MCU with your version and Carplay works reliable so far.
[MTCD Android Head Units General] ikerg:
Dasaita android 10 works for both resolutions.

Just upgrade to android 10 (but first the recovery)

Enviado desde mi SM-G975F mediante Tapatalk
[MTCD Android Head Units General] talrhv:
Hi all, im trying to update my dasaita px6 unit to android 10 (from android 9) and when i try to update it shows error on the recovery menu. mcu version is 3.45 do i need to update it to 3.67 before im trying to update? am i missing something else?

im using hal9k android 9 mod

i tried with the 20201113 update file.

thanks!
[MTCD Android Head Units General] shakum:
PX5 on a Jeep Wrangler here, it seems like the lastest Android 10 update breaks Bluetooth. Cannot discover any bluetooth device. Is this a known issue? My Bluetooth module is MD725 when I see under Driving Settings (code 126).

Android 9 and 8 seems to work fine with bluetooth.

---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------

PX5 on a Jeep Wrangler here, it seems like the lastest Android 10 update breaks Bluetooth. Cannot discover any bluetooth device. Is this a known issue? My Bluetooth module is MD725 when I see under Driving Settings (code 126).

Android 9 and 8 seems to work fine with bluetooth.
[MTCD Android Head Units General] shakum:
Actually Android 9 has issues also where I cannot even sign-in into my Google Account. Tried factory resetting and wiping all data and ensuring that time zone is correct etc.

Anyone else have this critical issues? May have to roll back to Android 8
[MTCD Android Head Units General] marchnz:
A quick search of the forum lists multiple posts related to this issue.
[MTCD Android Head Units General] Guillermo h:
The bluetooth MD725 does not work with android 10.
[MTCD Android Head Units General] shakum:
That's correct. I wish Dasaita would post their supported BT modules with their releases :) I think one solution may be to get this Bluetooth IVT-i145 on ali express and swap out the MD725 module.
[MTCD Android Head Units General] Guillermo h:
Correct, for my particular case my Dasaita with android 10 has an RF210 bluetooth module.
[MTCD Android Head Units General] marchnz:
Unlikely any Chinese reseller wants users to upgrade. They would want you to buy another unit to obtain the upgrade. Probably why they dropped support for the most common type of BT module.
[MTCD Android Head Units General] VALiK1977:
Dasaita max 10. I have used different updates from 202009 to 20201111. And I cant change the language in Chrome interface. Also I can't update or delete Chrome. Why is it so?
[MTCD Android Head Units General] graycorgi:
Just wanted to report that my MAX 6 has never been more stable than with this combination of MCU and software. I probably will never update it again. The included Zlink also works a lot better with Android Auto and it actually looks high resolution (on Zlink 3.x.x it was very compressed/fuzzy). This is a winner. Thank you for sharing these updates!
[MTCD Android Head Units General] spoonkin:
Hands free help

Hi guys. Just recently got my for ur car model HA2135B, 7". Everything looks and sounds okay. Except for the hands free. It has very bad noise background where the other person can’t hear me at all. It has noise and I sound very far away while the head unit it just next to me.

As a head unit I use hands free alot because I drive often. I hope someone can help
[MTCD Android Head Units General] halloj:
If so, why is it not reflected here? https://xdaforums.com/android-auto/...asaita-mcu-updates-rockchip-px5-octa-t3575155
[MTCD Android Head Units General] Akuma666:
Hi To The Android Guru's,

I have a Dasaita PX5 unit that got bricked when I tried a factory reset. Unable to get into Recovery Mode (RM) as the lights on the soft buttons blink but will not let me invoke RM. The unit does not have a SD-Card Slot. After a lot of searching and reading on this forum, found MarchNZ's OTG upgrade thread.

The unit was running MTCE_HA_V3.14_1 with Android Version 8.0.0 provided by Dasaita. It is an Octacore 64-bit CPU / 4 GB RAM / 32 GB Disk

Fabricated the OTG cable using

R1-2.2K

and

R2-3.3K

. Connected the SoM board to Windows-7 Professional machine after loading the drivers and the board got detected on the first try. Downloaded the following to flash the bricked PX5 unit.

1) Downloaded firmware: px5_OREO_Full_OTG_13032018-UseToRecoverOrCreateNew.7z

2) Downloaded Tools: tools-master.zip

When I try to flash sdupdate-A8-Kumarai.img using the RK Tool, the process stops at "Wait For Loader Fail" step. Attached screen shot for better clarity. Tried this multiple times after "Reset Device" & "Erase Flash", but the process stoped every time at the same point.

Not sure what I am doing wrong but any help coming my way at this point will be much appreciated.

Unfortunately, due to the XDA upgrade, a few of the threads that I was going through are not accessible as of now.

Thanks in advance.
[MTCD Android Head Units General] marchnz:
Perhaps ask in the thread discussing this. Also, wipe first.
[MTCD Android Head Units General] Akuma666:
Unable to access one of the threads that was relevant and was discussing this topic in detail, due to the XDA upgrade. Hence posted my query in this thread. Request you to share the relevant thread URL.
[MTCD Android Head Units General] demetry14:
Are we still not getting changelogs for the firmware?

Does anyone know what 3.67 does?
[MTCD Android Head Units General] aud_61:
I have a Dasaita PX6 max6(Dual-Core-Cortex-A72@1.8G,Quard-core Cortex-A53@1.5G,Mem:3841MB)-AHD (1024/600) with firmware HA2_rk3399_9_ota (20200521) and MTCE_HA_3.62, before upgraded.

I've followed your footsteps; with 3.67 MCU and PX6 AD10(20201113) fw, by using Halk ModInstallerPro with successfully upgraded.

However, I've just found some strange for my Wifi status, which not shown Connected status(as attached photos), although it is connected, have you or any one experienced like this? Even, tried to got back to MCU 3.65, or 20201019fw, still got the same results.

Thank in advanced and Regards,
[MTCD Android Head Units General] blu1111:
Same situation with:

V10 HA3_px5_10.0_ota(20201019)

MTCE V3.65

Also always active icon "<...>" on top of the sceen.

I report also bluetooth trouble with RF210 module, the bluetooth appear connected with phone but after few minutes it don't communicate (connected but without transmitting) also impossible to disconnect from unit.
[MTCD Android Head Units General] jacobo marco:
a question.

i have this model:

Dasaita HA2100

but audio amp settings, dsp & cut freq, didn't work on rear speakers

its normal?
[MTCD Android Head Units General] marchnz:
What did the reseller say when contacted for support?
[MTCD Android Head Units General] jacobo marco:
I have not contacted the dealer yet
[MTCD Android Head Units General] aud_61:
Have you turned the setting Tab to "ON"?, and try setting to "REAR" fad.
[MTCD Android Head Units General] ask77:
Hi ! I have a MTCE Dasaita Max 6 4GB/64GB running HAL9K Mod v4.2 android 9 . I have successfully upgraded to stock Android 10 HTC7 ROM purchasing mod installer pro 2 from HAL9K . Everything is working fine except for the wifi which refuses to turn on . I had upgraded the MCU to MTCE HA V3.67 from v3.45 before upgrading and did a factory reset . I have tried various other ROM's from the Rockchip PX6 android 10 folder on the Yandex but the wifi is not switching on My bluetooth module is WQ_RF210 and it is working fine. Please help. Thanks
[MTCD Android Head Units General] marchnz:
What do you see in logcat?
[MTCD Android Head Units General] aud_61:
It is almost close to my case, which is posted above thread #3806, but my WiFi was connected but shown status "Not Connect"(either connected via home Wifi or car mobile Wifi router), as attached photos. Could you pls. check whether actually not connected or just shown the status "Not Connect".
[MTCD Android Head Units General] ask77:
In my case the wifi is not switching on, also there is no mac address being shown for the wifi .