yashsingh1/xdaforums huggingface dataset:
[MTCD Android Head Units General] gunnermike:
I redownloaded and tried several times.
[MTCD Android Head Units General] Floston:
And why you did not unpack the archive?

On SD or USB there should be an update.img file
[MTCD Android Head Units General] :
You are now on android 8? If not you must upgrade the recovery first.

Android 8 have update.zip rom.
[MTCD Android Head Units General] Nasty_z:
Okay so I managed to install Magisk using [MENTION=6738895]kumarai[/MENTION] method for rooting Oreo rom. I have a PX5 2GB Ram model. I upgraded previously using Malaysk's instructions (I was on Malaysk rom). I am now on stock oreo rom.

Anyway, Magisk works for root permissions but I cannot install any module. This, of course, means I can NOT install Xposed or Viper4Android.

Whenver I try to install any module, I get this -> "Error extracting zip file"

Any help will be very appreciated. Been trying to get this to work all day today, changed firmwares 4 times to make this work (very annoying). I always get the same error when installing modules :(

I have also tried removing the module files from zip and re-zipping them and then installing them using Magisk Manager but that also does not work.

If anyone can help, please do.

Thanks in advance.
[MTCD Android Head Units General] typos1:
Upgrading to Oreo is different than for all other Android versions, there is a specific thread on how to do it in the MTCD software forum.
[MTCD Android Head Units General] gunnermike:
I have tried following that post. I cannot get the unit to boot from the SD card. I have even tried the process on two different SD cards. It seems to me that Dasaita should release an OTA that is installed the same way all other updates are.
[MTCD Android Head Units General] typos1:
Its nothing to do with Dasaita - the software is done by the makers of the SoMs - HCT and this is the way they have chosen to do Oreo.
[MTCD Android Head Units General] cybermaus:
I just now received this Dasaita V600 Octo core 4MB 32B unit. And it does not start. Not at all.

I will contact seller of course, but just a quick question if anyone has some quick tips.

Searching XDA, I did find these two posts, but as I still need to do the back and forth with the seller, I cannot open the device.

It is on my workbench at the moment, with only +12.5V to +Battery/+Acc, and Gnd to Gnd connected.

Apart from an initial pulse to charge internal capacitors, it is only drawing 1mA for a few seconds, falling off towards a permanent 0.5mA, so I am pretty sure it is not merely a disconnected screen, but the unit actually not powering on.

- Screen stays completely dark. Also no vague backlight on a black screen, and if I stare closely with a flashlight, no visible images

- When I provide power to the units, the 4 small physical buttons do briefly flash blue.

- If I keep a button pressed down while providing power, they stay blue, until I release the button

I briefly wondered if I received a refurbished unit, as it had no protective film on the screen, but did have several finger smudges. However the QA stamp on the side (not a label, but stamped on metal) has 2018-3-29, which is 5 days after I bought it and cannot be more then a single day before they shipped it. On the other hand, the rubber pull-tab on the back is broken off and has scratches, so maybe the QA stamp only means, "QA after refurbishing".

Any tips or hints are appreciated.
[MTCD Android Head Units General] typos1:
Any pics of how youve wiredit up ? It sounds like the ignition wire isnt connected.
[MTCD Android Head Units General] cybermaus:
Indeed, wiring, thanks.

Old guy here, had not installed radio's in decades. It seems manufacturers kept the old ISO 10487 plugs, including keying, but changed core wire allocation.

Seems a bit weird and I'd expect rekeyed tabs in such case. Anyway, works now.

I have a model HA2137-V840 with MTCE_HA_V2.75_1 Nov 29 2017 12:48:53 and ROM px5-userdebug 8.0.0 OPR5.170623.007 eng.htc.2018

It has the newer Android 8.0 "Gold" user interface

A few follow up questions:

- Any way to get it to setup internet over bluetooth to my phone (already tried the setting-bluetooth widget on desktop, it too goes to the same limited interface)

- I hate the radio screen: too crowded, too much screen elements, and why in gods name does accidentally touching the prominently placed search button overwrite all previously set channels without so much as a warning or confirmation. In other words: Any alternative radio app's?

- Pressing back on the radio to go to main menu should not kill the sound, but it does.

- In general I dislike the dark-gold-on-black. Not enough clarity and contrast. Any possibility to change?
[MTCD Android Head Units General] typos1:
No way to set up internet via BT, you have 3 options - wifi, hotspot or 3G dongle.

No alternative apps, unless you try the MTCRadio apps from other RK3368/PX5 ROMs. Use the arrows if you want to search without changing the saved stations.

Pressing "back" SHOULD kill the sound from the radio - "back" means youre exiting from the app, its a standard computer thing thats been around for years, press "home" if you want to keep the app running.

Yes, use another RK3368/PX5 ROM.
[MTCD Android Head Units General] cybermaus:
Thanks for your replies.

You may have missed my use of the word "accidental". It is to easy to accidentally touch the search, and there is no confirmation of any sort.

I don't think that standard is written in stone: Take your favorite Music app on your phone rather then the head unit. Play a track. Press back. Does it stop playing completely, or move to the notification area? Not entirely sure about your phone, but mine keeps playing.

Anyway, its not that I do not appreciate your help, thanks for conforming my worries, apparently we'll have to live with this. But above two functions are not very ergonomically friendly, the accidental touch being the most annoying, as it erases my presets.
[MTCD Android Head Units General] typos1:
Yes, I did miss the "accidental" in your post, cant really say much about that, never had that problem myself, another ROM may well have a different radio app.

I disagree about the home and back thing - phones usually have a notification when playing music with a stop function there, a music player from the app store may behave as you would like. Never heard anyone complain about this before in 3 year+ in the headunit forums. Still, each to their own. :)
[MTCD Android Head Units General] emre33:
Blue UI HA_PX5_8.0_ota(20180413）https://www.sendspace.com/pro/dl/7smety

THX [MENTION=6942549]hotaudio[/MENTION]
[MTCD Android Head Units General] blu1111:
I prefer this version instead of the GS version.

but in both version i can’t make shortcut in desktop. Is it a bug or Android 8 don’t permit this?
[MTCD Android Head Units General] typos1:
Its the launcher, try a different one.
[MTCD Android Head Units General] zeyret:
Does the BT MD725 work?
[MTCD Android Head Units General] ikerg:
Bt on md725 works and always worked for all dasaita units under android 8.

The issue is that other low quality md725 chips used by other manufacturers (we are looking for which manufacturers are) that have been identified by md725 type 2 inside the android code require other implementation that is not included in android 8 by developers (hct). We don't know why but the only way to push hct to implement it (If there is no technical issue to do that) is by means of claims to the MANUFACTURER of that not supported units.

As i said...this is not the case of dasaita and therefore the answer to your question under this dasaita thread is "yes, md725 bt works"

Enviado desde mi SM-G950F mediante Tapatalk
[MTCD Android Head Units General] marchnz:
From log cats of working and not working, we can see that [type 2] Realtek chips do not return a serial number. From photographs I couldn't establish any chip difference and it could be MCU or EPROM settings within the Realtek that determines MCU type - quality as a factor was not validated.

The v600s Dasaita all use bt968s from what I have seen and read, is that correct?

They all have pretty poor Bluetooth a2dp and hands-free quality, independent of reseller or factory. This is because of the HCT provided Android.

These units are so close to being amazing (e.g. Bluetooth quality) and it would appear HCT are unable to address these last issues, ostensibly because everything is modular in these units and HCT are unable or unwilling to want to get the module suppliers to provide quality code.
[MTCD Android Head Units General] ikerg:
V600s are now sd968 but in my case my v600 is md725

Enviado desde mi SM-G950F mediante Tapatalk
[MTCD Android Head Units General] GixxerRaider:
Anyone can advise me what firmware to i need to use to upgrade. No sd slot but onky usb.

Model: PX5 2 x 32gb

Android Version :6.0.1

CPU: ARM Cortex-A53 eight-core 2+32G PX5 GPU: PowerVR G6110

Mcu verison : 2018-02-05 18:12:21 BFD_(68)_26_C26_R68_V1.00_CAN(All)gVOut

Would any kind souls advice?
[MTCD Android Head Units General] ikerg:
wrong thread....it is not a dasaita unit....not a MTCD unit. .please post int he correct thread...probably the joying px5 units related thread

Enviado desde mi SM-G950F mediante Tapatalk
[MTCD Android Head Units General] ricanbandit:
I Love my Dasaita V800 - Are there any tools like the joying tools out there for these?
[MTCD Android Head Units General] demetry14:
Any news on an MCU update? My BT OBD adapter hasn't worked since 2.75, and the unit won't accept a downgrade from 2.80 to 2.75.

My OBD2ECU adapter wont connect.

My Logcat from: Settings > Factory Settings > Logcat

https://drive.google.com/open?id=1f-CfbV-5D6FDoM7TzCOEeGMQ2sW9nueC
[MTCD Android Head Units General] typos1:
I was going to suggest some sort of software fix that shows the MCU a serial number "from" the MD725, but thought there was a software fix for the MD725 problem.

MTCD Tools, Grasser app.
[MTCD Android Head Units General] GixxerRaider:
I am just asking and seeking for advice. Why sound so hostile.
[MTCD Android Head Units General] typos1:
Probably cos it clearly says in the first post that this is for MTCD/E MCU units only.
[MTCD Android Head Units General] gunnermike:
I flashed the latest Rom and now it won't boot. The soft keys just flash.
[MTCD Android Head Units General] ikerg:
Have you tried again with reset button?

Enviado desde mi D6603 mediante Tapatalk
[MTCD Android Head Units General] V.Alecks:
Hello! Tell me, what to do during an incoming call, the music was put on pause, and after talking again played? (PX5 HA)
[MTCD Android Head Units General] ikerg:
I dont remember if it is paused or it continues even muted I will check. What does your unit do?

Enviado desde mi D6603 mediante Tapatalk
[MTCD Android Head Units General] V.Alecks:
I wish that music was put on pause.
[MTCD Android Head Units General] gunnermike:
I finally got it to boot after pulling power from the unit.

The echo appears to be gone. The GPS is nearly useless. Anyone else haveing problems with the GPS?
[MTCD Android Head Units General] ikerg:
My gps locks in just 2-3 minutes

Enviado desde mi D6603 mediante Tapatalk
[MTCD Android Head Units General] stinger4321:
Mine locks instantly
[MTCD Android Head Units General] Caspar1974:
Mine is fine too. No connecting time or what so ever.

Verzonden vanaf mijn iPhone met Tapatalk
[MTCD Android Head Units General] 93starletgt:
Why is there a Nougat 7.1 system update for the PX3 and not for the PX5?
[MTCD Android Head Units General] ikerg:
Px5 will update to nougat...but it will take some more time

Enviado desde mi D6603 mediante Tapatalk
[MTCD Android Head Units General] marchnz:
MCU HA v2.52 enables the menu "Shutdown Delay when ACC off" - and can then select between AutoSleep (fastboot) or up to 1 hour.

Well done [MENTION=6942549]hotaudio[/MENTION]
[MTCD Android Head Units General] leonkernan:
Agreed, thank you for giving us the choice!
[MTCD Android Head Units General] jaume2971:
i am MTCB HA 2.73 with android 4.4.4 ?? it s compatible de board px5 2 gb ??

thanks

Enviado desde mi SM-N910F mediante Tapatalk
[MTCD Android Head Units General] tephra:
where is this menu? do i need to run the latest android release as well?
[MTCD Android Head Units General] marchnz:
Yes; MCU and Android FW.
[MTCD Android Head Units General] tephra:
perfect thanks.. ill update Droid tonight :)
[MTCD Android Head Units General] ikerg:
No. Only MTCD

Enviado desde mi D6603 mediante Tapatalk
[MTCD Android Head Units General] prmah:
[MENTION=6942549]hotaudio[/MENTION] are you selling PX5 core board also ?
[MTCD Android Head Units General] jaume2971:
No, I would buy it if it was compatible
[MTCD Android Head Units General] GixxerRaider:
I am a newbie in Andriod auto unit. If i have known, I would'nt have ask. Cos i would slap myself first. Thanks bro. Some ppl just have no common sense at all.
[MTCD Android Head Units General] JonatanP:
As we have been talking, it has become clear that this information is erroneous or false, maybe Dasaita does not want to solve the problem and for that reason blames others.

I know that you are aware of the problem, but I put it here so that it is known among all the users to try to make Dasaita do something.

My unit is dasaita, it has the md725 type 2 chip and there is no way to make the bluetooth work.

different versions of MCU tested, different roms of android 8 more recent, try to select other chipsets, reinstall the rom again, several restarts, stop the bluetooth service once configured the name and pin.

apparently none of this works, so there is no choice but to wait for a solution from dasaita, this is my radio:

https://es.aliexpress.com/item/Dasa...32793462549.html?spm=a2g0s.9042311.0.0.LMlb3G
[MTCD Android Head Units General] ikerg:
We talked about this after publishing this information....I did talked to dasaita and they are currently checking on the same unit like yours if that occurs for android 8

.....So...they are doing something...

I am waiting for their reply. I will.keep you informed

You are the only guy that reported this behavior on dasaita unit, the other Bluetooth malfunctions reported are MX.

Hope all we can find a solution together....But take into account that Dasaita is at least checking your problem...

Enviado desde mi SM-G950F mediante Tapatalk
[MTCD Android Head Units General] ikerg:
Dasaita tried with your unit ... using the mainboard with md725 and putting a coreboard with android8...the Bluetooth was working well.

I have a dasaita with md725 as well...and I did the same with a android 8 coreboard and the Bluetooth worked as well...

What I didn't do is to upgrade my 2gb/32b px5 coreboard to android8 .... But as the mainboard is the one that contains the md725 chip....I don't think that this could be the issue...

Enviado desde mi SM-G950F mediante Tapatalk
[MTCD Android Head Units General] marchnz:
Attach logcat, this will show version of md725 in your unit.

---------- Post added at 08:25 AM ---------- Previous post was at 08:17 AM ----------

Not doubting what Dasaita may be doing, what is confusing is that I have provided the analysis and root cause, being missing g BT library.

I would assume all that is needs to happen is for Dasaita reporting my finding to HCT and for HCT to resolve and provide a fix/update to Dasaita.

HCT I would assume have the source. All Dasaita do is make cosmetic changes, such as lanucher and call it 'theirs.'

Make sense? I don't see any response from Dasiata on my findings.
[MTCD Android Head Units General] JonatanP:
This? https://pastebin.com/9EZDtqyd

Thanks for your help
[MTCD Android Head Units General] marchnz:
Hi,

Doesn't seem to be a full logcat from boot or is filtered.

Try logcat from factory settings menu - instead of entering a password, enter 'logcat' and a logcat should be created.
[MTCD Android Head Units General] demetry14:
[Deleted]
[MTCD Android Head Units General] JonatanP:
I used the terminal to create the logcat, I did not read your message well, tell me if this helps you, thanks.

http://www.mediafire.com/file/pbrp3db1kaa8agv/logcat.txt
[MTCD Android Head Units General] moby j:
Hello newbie here,

my HU now is Rockchip PX5 Octa-Core 2G RAM 32GB

PX5	6.0 UPDATE HA (20171214), MCU MTCE V2.75

my questions are :

1. I tried to update the MCU to 2.80 from setting-> update MCU find the file dmcu.img, reboot after that nothing happen. the MCU version still 2.75

2. If I want to upgrade to android 8, do I need update it using PX5_8.0_hct3_1_ota_20170108 first or I can flash directly to Blue UI HA_PX5_8.0_ota(20180413) (planning using [MENTION=6738895]kumarai[/MENTION] tutorial)

I would appreciate any help
[MTCD Android Head Units General] gunnermike:
Is there a way to upgrade to 8.0 without having a micro SD card? I have the USB adapter that came with the unit.
[MTCD Android Head Units General] ikerg:
Yes. By building a usb otg cable.

You need to open the unit, extract the som and Connect it to the pc with the usb otg cable

Enviado desde mi SM-G950F mediante Tapatalk
[MTCD Android Head Units General] marchnz:
Although you have a type 2 md725 (is reporting serial number) this doesn't appear to be the issue.

Check your BT settings in factory settings because I don't see issue in logs, BT SDK loads OK and appears you might have a separate BT such as bc-6 or sd968.

You could also take internal pics of the headunit and attach here to help identify.
[MTCD Android Head Units General] JonatanP:
probe in the factory settings to select the different bluetooth chipsets one by one.

The only difference I've seen is when selecting parrot the bluetooth name and pin "CAR-KIT" and "0000" appear automatically as in Android 6.0

I really prefer not to disassemble the radio completely to check the chipset since it would take many hours and is a little risky due to the quality of the plastics.

I do not know if this can help you, this is the radio: https://es.aliexpress.com/item/Dasa...-2011-NO-DVD-with-2GB-Stereo/32793462549.html
[MTCD Android Head Units General] moby j:
Please help
[MTCD Android Head Units General] demetry14:
The only way I have found on my unit that the MCU flashing works is:

MicroSD card

Format to fat32

Place only the dmcu.img file on it.

Plug in the MicroSD to the mSD slot

wait for the head unit to recognize the update and ask you if you want to update.

Click yes

Let it do it's thing and reboot.

For me all other methods like clicking "Settings > System > MCU Update" fail to find the file or perform the process in full. But that's been my experience... So try it and if it works, great... If not try others methods and figure out which works for you and your unit.
[MTCD Android Head Units General] moby j:
Thx [MENTION=4284937]demetry14[/MENTION], before this I succeed to update MCU using USB, but you give me some point "fat32", thx for the input I will try using micro SD if failed using usb.

Another question point 2 can I update the HU using the latest update.zip or I need update it from 1st andoid 8.0 file?
[MTCD Android Head Units General] demetry14:
I personally would do the 1st Android 8, then follow that with any updates. But that's personal preference.
[MTCD Android Head Units General] royalhawk2002:
This is my XTRONS PB68WRJP (Jeep Specific), with stock ROM (see attached pictures).

Is there any update of MCU and ROM out of here ?

I would like to enable the split screen function that is not working on my unit.

Any help will be appreciated.

Thanks
[MTCD Android Head Units General] typos1:
You can also do it from recovery.
[MTCD Android Head Units General] demetry14:
Personally for me, since upgrading MCU to 2.80 I am unable to get into Recovery with the same method I used before... So I resort to putting files in specific places and waiting for the system to acknowledge.

But thanks, I know once I can get back in recovery is how I would normally do it.
[MTCD Android Head Units General] typos1:
Long press the power button in the status bar, it will give you a reboot menu which includes a recovery option.
[MTCD Android Head Units General] marchnz:
Hi,

Note that, in latest HCT / HA Oreo [HA_PX5_8.0_ota(20180413).7z] contains a new file [sdsdk6]

which supports BC6 and BC8

, this is probably the resolve for your issue :)

For MD725 users, sadly [SDSDK] is

not included

to support MD725.
[MTCD Android Head Units General] JonatanP:
Before of sending the logcats i have these ROM and doesn't work :/

Maybe I need to wait the fix for md725
[MTCD Android Head Units General] BadAzDB:
I'm a bit confused. I need an "update.img" file in order to restore my bricked unit. Which one of these am I supposed to use? My unit is MTCD.
[MTCD Android Head Units General] ikerg:
But your issue, according to [MENTION=4974080]marchnz[/MENTION] is completely different.

My md725 is the same as yours (according to Dasaita). Mine worked if I replace my android 6 coreboard to android 8 4gb coreboard. (I never tried to upgrade my 2gb coreboard to android 8)

The issues reported by MX boards with md725 are translated as No mac addresses nor pin nor bt name and looking for a logcat no serial number is given by bt chip to the system

In your case, even not mac address nor pin nor bt name the bt chip is reacting to the system and giving a serial number.

So, in my opinion, it is a completely different scenario and issue.

Am I wrong [MENTION=4974080]marchnz[/MENTION]?

Is as well related to drivers or missing SDK?

Enviado desde mi SM-G950F mediante Tapatalk

---------- Post added at 03:55 PM ---------- Previous post was at 03:53 PM ----------

I assume you are under android6...so get the latest android 6 one..

Enviado desde mi SM-G950F mediante Tapatalk
[MTCD Android Head Units General] emre33:
MCU: MTCE_HA_V2.83

https://www.sendspace.com/pro/dl/tvnlyz

THX [MENTION=8150222]Dasaita[/MENTION]
[MTCD Android Head Units General] Toto1365:
update

what does this update do for improvements?
[MTCD Android Head Units General] demetry14:
My BT issues where OBD would connect but no apps could see it connected and BT issue where it would no longer connect to MCU have been resolved...

I installed MCU 2.83 and 20180427 7.1.2 Rom. Still didn't work.

So I did a factory reset, reconnected to OBD BT and now it works!
[MTCD Android Head Units General] Clandaries:
Is it somehow possible to extract the car logos from MCU with logos and put them into MCU without logos?

I have got MX. V2.83 but without logos.

Regards

---------- Post added at 08:27 AM ---------- Previous post was at 08:27 AM ----------

Is it somehow possible to extract the car logos from MCU with logos and put them into MCU without logos?

I have got MX. V2.83 but without logos.

Regards
[MTCD Android Head Units General] Floston:
What for?! When there is with LOGO :)

Look in the signature
[MTCD Android Head Units General] emre33:
Glonass (Russian GPS) support does not work under Android 8.0!

You can see Glonass satellites, but NOT USE them!

Do you know that?

GPS Status & Toolbox http://mobiwia.com/gpsstatus/

green: satellite is used while determining the location

gray: orbital data is not available

In View: 18

In Use: 8

But all other programs show this!

Are developers aware of the problem? I checked all versions of android 8.0, each one is flawed

[MENTION=8150222]Dasaita[/MENTION]
[MTCD Android Head Units General] rexmako:
Please, how do I get a very good phone dialer on my unit? LM-2.75
[MTCD Android Head Units General] typos1:
If you have MM, then any RK3368/PX5 ROM will do, if you have Oreo you need an Oreo update zip.
[MTCD Android Head Units General] JonatanP:
[MENTION=4974080]marchnz[/MENTION] I can confirm what I have md725, I reinstall android 6.0.1 and the bluetooth works fine, the problem is in android oreo, maybe with a solution for the others md725 can fix my problem also.
[MTCD Android Head Units General] marchnz:
I have written extensively about this. Until HCT include [sdsdk] in Oreo, md725 is not fully supported.
[MTCD Android Head Units General] Clandaries:
I had to change the Bluetooth in factory settings to SD-986 and it is working 100% now.

Regards
[MTCD Android Head Units General] ikerg:
So you never had a md725. You always had a bad configured settings?

Enviado desde mi SM-G950F mediante Tapatalk