[MTCD Android Head Units General] ikerg:
Reserved: Q&A

1. I have a MTCD RK3188 unit. Can I use the firmware updates here published?

No. All the stuff here published is for RK3368 (PX5) MTCD units. Only the MCU files could be used for your unit (if it is really a MTCD)

2. My MCU is XXX and i can't find new updates from manufacturer for a long time. Can I update from other Brand MCU?

Not all the MTCD MCUs are the same, but quite similar between them. There is a thread that is collecting all the MCU cross compatibility based on user experiences.

https://xdaforums.com/android-auto/.../mtcd-verified-cross-compatible-mcus-t3624724

3. How Do I enter into recovery menu?

Depending on the HeadUnit, the entering into recovery process could vary.

Reset Button Procedure (You need a needle to access that button inside the Reset hole)

Applicable to:

[*] HeadUnits with no physical buttons on Headunit (just capacitive buttons) [Brands: Dasaita]

1. Press Reset and hold until button light blinks (15-20secs)

2. Release Reset and press again. Hold it until you see the Marshmallow logo

3. Release Reset and wait for the Recovery menu to appear

[*] Power Button Procedure [Brands: Dasaita]

Applicable to:

[*] HeadUnits with physical power button on Headunit [Brands: Dasaita]

[*]When none of the above procedures worked:

1. Disconnected all power from the unit... ACC & BAT disconnected

2. Prepared 12V power supply with on negative and two positive connectors

3. Connected negative to GND & one positive to BAT

4. Connected USB keyboard

5. Press right ALT (ALT GR on some keyboards) and PrintScreen

6. Connected the other positive lead to ACC (unit does not work if both BAT and ACC are not connected)

6a. Start pressing repeatedly on E (not holding E pressed, but press...release... press... release..... rapidly)

7. The boot logo shows (MarshMallow...etc) and after a few seconds the unit reboots itself

8. Release right CTRL & PrintScreen and continue to repeatedly press on E.

9. The Recovery shows on screen.

4. I have a complete Bricked Unit with a continuous loop. What can I do?

First of all, you have to try to reload the firmware into the unit. As you are not loaded into Android system, you must reload the firmware by using the recovery menu. To enter into recovery menu read the FAQ#3.

Most of the times, reloading the Android firmware solve the issue. Try with different firmwares if you can't succeed at first time. When, even having tried to update your firmware from recovery, but it did not succeed, you probably have corrupted your NAND. In that case a more complex solution is available (desoldering/soldering is required) to come the unit back to life. Thanks [MENTION=4974080]marchnz[/MENTION] for the detailed description on the following thread:

https://xdaforums.com/android-auto/mtcd-discussion-questions-development/px5-stuck-bootloop-t3635412

5. I notice echo on my Bluetooth Calls

Echo has been reported on severla Brands/Models for PX5 firmwares. The echo is not instantaneous and it appears after some minutes of conversation. Currently [MENTION=7621504]f1x[/MENTION] is developing a solution based on tunning the Bluetooth drivers. You can follow the solution in this thread:

https://xdaforums.com/android-auto/...elopment/px5-solution-bluetooth-echo-t3638779

6. My HeaadUnit never shuts off and, even several days, after switching engine on the Headunit starts in a few secons....Can I kill my car battery?

These units are designed to enter into deep sleep state detecting ACC off, in order to avoid each time you connect the car, you had to wait a full cold boot (20secs) and they just wake up in 2seconds. During This sleep state, the Headunit consumes a small current (just 100-150mA). Such current can't drain your battery.

Some manufacturers (like Dasaita (HA)) have implemented a menu in which, apart of Auto-Sleep you select at which time you want to HeadUnit shuts off completely, useful for long car unused periods.

7. My apps are killed during Sleep and they don't start again after waking up

These HeadUnits kills background processes (except specific ones) during deep sleep state (see Q&A#6). The killing process is managed by MTCManager.apk file. A developer (@graser) has been released a tool that is based on adding apps/services to a whitelist to pevent the unit killed them during sleep. You need root & Xposed Framework

8. Google Maps Hangs when starting a route

It has been identified that Google Maps hangs constantly. One of the reasons provided is due to corrupt data after not properly exiting Maps application, which occurs automatically bu the ROM when entering into sleep.

Three Solutions have been reported:

8.1 -> Install 9.46.2 version --> https://www.apkmirror.com/apk/googl...ation-transit-9-46-2-11-android-apk-download/

8.2 -> Add Google Maps to the Whitelist on Graser's app (see FAQ#7) [Root & Xposed required]

8.3 --> Clear Maps Cache before starting app (after each sleep). You can use this apk: https://xdaforums.com/attachment.php?attachmentid=4295635&d=1507415766

9. I cant find MTCDs MCU updates, but MTCE. Can I update a MTCE over a MTCD?

HCT developers, starting from MCU version 2.65, has been renamed the MCTD as MTCE. It is reported to be a major software update and it is fully compatible with MTCD MCU. Therefore, you can upgrade to MTCE from MTCD safely.

10.Can I replace Google Now by Google Assistant?

Yes you can. extracted from https://xdaforums.com/android-auto/...ment/px5-to-install-google-assistant-t3629660. Thanks [MENTION=7562259]apollo1976[/MENTION]

1) change the resolution using the "Resolution Changer Pro" app (https://apkpure.com/resolution-changer-pro/com.nexter.miniscaler). I set the 1280x800 resolution, with DPI 280. Other user reported that thw working resolution is 1365x800

2) Reboot the system

3) Installed the Google Assistant apk (https://www.apkmirror.com/apk/googl...assistant-0-1-174051423-android-apk-download/)

11.How can I root my unit?

PX5 devices under MM can be rooted easily by means of using kingoroot app (not kingroot).

http://es.kingoapp.com/

When installing a Warning message will appear, but you can continue the installation.

You need internet connection for kingoroot during root process.

After getting root privileges, remove kingoroot and install SuperSU