yashsingh1/xdaforums huggingface dataset:
[MTCD  Android Head Units Q&A] avenant:
Another question :p To connect the unit with a computer through USB, do you need a USB OTG cable or a regular USB cable? I tried with a regular cable, but this does't work...

Also useful for other users, I used this app: https://play.google.com/store/apps/details?id=options.developer.com.developeroptions To get to the developer options settings menu, because it is not possible to get to the developer settings menu like on a phone, to enable usb debugging

I also enabled adb in the factory settings with password: adbon

This is also a useful app if you have the device rooted with the update.zip in this thread, to reboot, and reboot into recovery: https://play.google.com/store/apps/details?id=com.codem.reboot
[MTCD  Android Head Units Q&A] doitright:
I don't think it is possible to adb in on a wire on these things. I think the only option is to adb over wifi. If it is possible to adb on a wire, you would need an A-Male to A-Male cable like this; https://www.amazon.ca/NEW-ft-USB-MA...d=1479744817&sr=8-1&keywords=usb+a+to+a+cable
[MTCD  Android Head Units Q&A] avenant:
I was able to use adb over wifi with this app: https://play.google.com/store/apps/details?id=com.ttxapps.wifiadb

however on my unit it is impossible to boot into fastboot mode, when I gave the command: "adb reboot fastboot" it just rebooted, I think they have disabled this option in the rom on my unit.

too bad, because I know of a way to test TWRP without installing/flashing it, but one needs to be able to boot into fastboot mode, in order to test it.
[MTCD  Android Head Units Q&A] ikerg:
[MENTION=7624154]k2ck[/MENTION]oj@hotmail.com...

How much available space on Rom.do you have?

I am.guessing why I have only 3gb free on a 16gb ROm

Enviado desde mi D6603 mediante Tapatalk
[MTCD  Android Head Units Q&A] doitright:
Well, to start with, there is no such command as "reboot fastboot". What you are thinking of is "reboot bootloader". Second, on devices that do have this option, it is implemented in the BOOTLOADER. Third, yeah, I wouldn't expect that to be implemented in chinese head units.

I wouldn't suppose that your "I know of a way to test TWRP"... would be "fastboot boot bootableimage.img", would it? Not exactly a secret ;)

My suggestion for testing bootable images, is that you just make sure that the OTHER bootable partition is always actually bootable. For instance, if you know how to boot into recovery, you can mangle the boot partition all you want and be able to fix it. So flash the "experimental" sysimage to the **regular** boot partition.

Or keep a good rooted sysimage on the boot+system while you're testing out things on the recovery partition, and MAKE DAMNED SURE that you don't eff it up.

The only distinction between the boot and recovery partitions, is that the boot partition is DEFAULT, and the recovery partition takes intentional action to start.
[MTCD  Android Head Units Q&A] wanb1i:
Thanks! I now have permanent root without using KingRoot! Yea! You're a RockStar! :cool:

Now all we need is a clean ROM, hopefully Marshmallow or Nougat?

---------- Post added at 03:00 PM ---------- Previous post was at 02:04 PM ----------

I have my 8" single din rooted now, but I don't know how to pull the firmware. You provide the instructions and I'll do the work, upload it to my Drive and put a link up here.
[MTCD  Android Head Units Q&A] doitright:
Don't give him *too* much credit, after all, the thing SHIPS with root enabled. It just only works over ADB.

What you can do to dump the internal, is plug in a USB disk that is at least double the size of the internal storage of your head unit, and run the following;

dd if=/dev/block/mmcblk0 of=/path/to/usbdisk/dump.img

Edit: Make sure that the USB disk is formatted with some filesystem that allows for that big of files.
[MTCD  Android Head Units Q&A] wanb1i:
OK, 2 questions

Does the dump include all my personal data as well? If so, how can I keep that information out of it?

Will a 16gb USB formatted as fat32 work?

I haven't heard from anyone on the personal data, so, until I do I won't post the firmware. Isn't an update a complete version of the firmware?
[MTCD  Android Head Units Q&A] rcll:
This looks interesting. Do we know exactly what bug they mean?

I'm guessing Joying units can't flash this. We have to wait for Joying to arrive at the same fixes independently or do the manufacturers share some MCU code?

Has anyone gotten the Google app to speak its search results on any of these HUs?

Google app Settings > Speech Output: On should work but no audio is generated on my 10/31 dated MCU, 8" sdin Intel unit from Joying.
[MTCD  Android Head Units Q&A] ikerg:
All manufacturers Shared mcu prior to Intel units (mtcd units).

Now joying uses completely different mcu...

Enviado desde mi D6603 mediante Tapatalk
[MTCD  Android Head Units Q&A] rcll:
So your Hotaudio Intel unit uses a different MCU than the Joying Intel units? Or you have MTCD MCU on your unit?

I asked Joying and they just sent the latest update for their Intel unit: https://mega.nz/#!E5BSmbSY!Hl8EPRcHCKD07b-Ls40_bmrc72BOtB2x59bLbGby-I0

This update is dated 11/15 and seems 200MB larger than previous updates, it looks like they left extra files in the zip.

The McuUpdateAll.bin md5 unfortunately seems to be the same as the one in the 10/31 update, but maybe there are other improvements in the app part.
[MTCD  Android Head Units Q&A] ikerg:
Joying is not using mtcd. Mine is mtcd

Enviado desde mi D6603 mediante Tapatalk
[MTCD  Android Head Units Q&A] avenant:
No, it would be: fastboot boot loader.efi, and then you can you can test different versions of TWRP by: fastboot boot TWRP.xxxx.img

this way TWRP doesn't replace recovery.img, and you can test different versions, before actually replacing the original recovery
[MTCD  Android Head Units Q&A] doitright:
Factory reset first, then dump.

No. Needs to be BIGGER.

---------- Post added at 03:18 PM ---------- Previous post was at 03:14 PM ----------

I'm guessing that you were either tired or drunk when you wrote that reply, since that is *EXACTLY* what I said.
[MTCD  Android Head Units Q&A] kc2koj@hotmail.com:
Is your hotaudio unit 16gb or 32gb
[MTCD  Android Head Units Q&A] doitright:
HA! Found some *REALLY* useful information.

Turns out that this SoC is in use by ASUS.

ASUS is GPL compliant.

Zenpad C 7.0 aka Z170C aka P01Z

Kernel source code can be found HERE: https://www.asus.com/us/Tablets/ASUS_ZenPad_C_70_Z170C/HelpDesk_Download/

Note that there *may* be driver changes for interacting with the MCU.
[MTCD  Android Head Units Q&A] ikerg:
16gb

Enviado desde mi D6603 mediante Tapatalk
[MTCD  Android Head Units Q&A] doitright:
And to reply to myself to add more information;

1) The asus units ship with fastboot.

fastboot oem unlock
fastboot oem unlock confirm

2) Chinese OEMs tend to only change the bare minimum from whatever they are handed.

3) The "original" bootloader code therefore most likely includes fastboot as well, we are looking at a littlekernel based bootloader. Possibility exists for the device to be accessible over fastboot.

4) Possibility exists for the ASUS bootloader to be directly compatible.

5) Possibility exists for fully custom bootloader.

6) Power up with "Vol+" triggers fastboot.

7) Power up with "Vol-" triggers recovery.

(6, 7) are most likely not directly applicable unless those same GPIOs are connected to something we can interact with, such as, for instance, the two steering wheel input connectors, or for those with units having physical buttons, to those buttons.

8) System partition is consistent between JOYING and ASUS at /dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID068

9) fwu_image.bin (whatever that is...) is also consistent at ImcPartID122.

10) The joying image has an added service called "camcap", which based on the name, is *probably* for capturing dashcam automatically, with low overhead, and much sooner than it would if it was through Android.
[MTCD  Android Head Units Q&A] rcll:
Looks promising! Your units are coming in soon?

This is probably the rearview camera passthru mode, it switches to rear camera immediately on mine even before Android boots.
[MTCD  Android Head Units Q&A] doitright:
Last night Joying sent me a DHL tracking number and said "usually 2-7 business days".

I don't believe that rearview passthrough mode has any relation to Android at all, at *any* point in the boot process. Its a feature of the MCU.

The "cap" part is also inconsistent with anything to do with rearview, since it would be short for "capture", which the rearview cannot do.

But then there is, of course, the "China" in it, and the tendency for things to be misidentified on account of languages that just don't align.
[MTCD  Android Head Units Q&A] ikerg:
Do you know what differences are between sofia3gr and sofia3grw devices?

Hotaudio guy gave me the ROm update for sofia3grw and my device seem to be sofia3gr only

I checked the firmware posted by k2ckoj on OP and the firmware given by HotHaudio and they have both the same checking on the update script:

getprop("ro.cpu.type") == "" || getprop("ro.cpu.type") == "sofia3grw" || abort("This package is for "sofia3grw" cpu type; this is a "" + getprop("ro.cpu.type") + "".");

getprop("ro.product.device") == "sofia3gr_car" || abort("This package is for "sofia3gr_car" devices; this is a "" + getprop("ro.product.device") + "".");

show_progress(0.750000, 0);

So...according to the script my unit gives a "sofia3gr" result from cpu.type

Do you know what could it be happening?

The Unit under device Info shows this:

Enviado desde mi D6603 mediante Tapatalk
[MTCD  Android Head Units Q&A] doitright:
No guarantees, but I suspect that they made an error in the install script.

The ONLY reference I can find via google to "sofia3grw" is to an intel MDS sheet referring to it as "SOFIA 3G-R W" from back in march of last year. The other interesting thing is that it comes with a part number of "PMB8016", which YES, is still the chip we have (or an approximation of it). Intel is known for renaming things almost daily.
[MTCD  Android Head Units Q&A] ikerg:
K2ckoj could install the update on his unit which ia provided by the same script.

So bonroad unit is sofia3grw and mine is sofia3gr

Enviado desde mi D6603 mediante Tapatalk
[MTCD  Android Head Units Q&A] doitright:
My point is that this doesn't necessarily mean that there is an actual difference, since these tags are things that can be set in the system.

In any event, I would consult with your unit's manufacturer to determine the proper course of action.
[MTCD  Android Head Units Q&A] ikerg:
I am.on it...but never get a completely clear answer from Chinese people.

I have to make different three questions about the same to figure out they want to say.

I asked yesterday and he answered me that decompress the update.zip file...so I told him that send my question to their software developer

Enviado desde mi D6603 mediante Tapatalk
[MTCD  Android Head Units Q&A] doitright:
Yeah, unfortunately I know exactly what you mean.

Like trying to explain to them what the recovery console IS, no choice but to send them a link to a video.

They obviously sell enough (well, Joying at least) to justify hiring someone who actually knows a bit of english.
[MTCD  Android Head Units Q&A] MorpheusOp:
This means i can install the update on my Bonroad device MTCD_HXD Intel? I dont have any news of update from manufacturer.
[MTCD  Android Head Units Q&A] ikerg:
K2ckoj installed his bonroad update (mtcd) .

Hotaudio is my manufacturer and the update is for mtcd Intel as well.

Previous rk3188 mtcd shared ROMs without any problems.

I don't know if someone tried to share mtcd roms from different manufacturers on the new intels

But my guess is that all mtcd will have common rom

Enviado desde mi D6603 mediante Tapatalk
[MTCD  Android Head Units Q&A] michaelpop:
Factory settings pw and dvr app

Hello, guys!

Just received my new HU, a Intel SoFIA-based JY-VL130N2. Great performance increase, but being a Joying, it was very clear that "the finishing" of the apps is very chinese, therefore I found following problems for which you could maybe help me.

What I found out after a couple of hours of testing:

1.) 126 doesn't work anymore for entering the "factory settings" folder. Does anybody know the new pw?

2.) the DVR app is missing. When installing the DVR app from MTCD (MTCTravel3), it opens, screen remains black, when I click record the app is closed with an error.

3.) - When I run the DVR app I used before on the MTCD-device (DailyRoads Voyager), the cam's image is not appearing.

- On a standard camera-app I noticed that when starting the app, the screen is black but when I choose to change the camera (let's say from "front camera" to "rear camera"), the image shows.

- Then I installed AutoBoy BlackBox, another dvr app. That one has the possibility to swap the cameras, so it swaps from black screen to camera. BUT the image is rotated 90 degrees and when I click record it freezes.

- I think for both 2 and 3, the reason is that the "default camera" is "the other, which is missing". How could I make them swap by default so that the dvr-apps run? Or did anybody find a solution?

4.) When trying to search radio stations and pressing an arrow, it only increases 0,05mhz and doesn't search the next radio station as it should do. Any ideas for settings for this app?

Thanks in advance for your advices!
[MTCD  Android Head Units Q&A] wanb1i:
I can't answer all the questions but I can answer 1 & 4

1. New pw is 3386

2. Long press the arrow button
[MTCD  Android Head Units Q&A] michaelpop:
thx a lot, wanb1i!
[MTCD  Android Head Units Q&A] wanb1i:
You're welcome.

Don't forget to hit the thanks button!
[MTCD  Android Head Units Q&A] michaelpop:
Just tested 3386, doesn't work, wrong password.
[MTCD  Android Head Units Q&A] rdevi:
Try 3368
[MTCD  Android Head Units Q&A] michaelpop:
Works, thx!
[MTCD  Android Head Units Q&A] wanb1i:
Sorry, my dyslexia! It's 3368.
[MTCD  Android Head Units Q&A] ikerg:
Finally i received a new update for my system.

According to HotAudio my system requires different ROM as I have enabled the 3G

Sofia3grw = wifi only

Sofia3gr = wifi + 3G

I suppose that drivers for 3G and baseband are included onto kernel on my version

I imagine that anyone that could enable the 3G (by soldering a sim card slot and antenna) could enable the 3G by using this kernel.

Hotaudio MTCD (not joying) Intel sofia 3gr (3G enabled) 20161021 ROM:

Edit: same file for sofia WIFI only....waiting for the good one...I will post here when available (removed link until I receive the good one)

Enviado desde mi D6603 mediante Tapatalk
[MTCD  Android Head Units Q&A] doitright:
Well, technically, the "3g" in "SoFIA 3G-R" means.... "3g".

Note that adding the cellular radio wouldn't be quite as simple as just adding a simcard slot. It would require also an antenna and some frequency filtering circuits. Wouldn't be worth doing.
[MTCD  Android Head Units Q&A] ikerg:
Am I wondering...if my 3g model is not very sold (is a reality, but I get it as it is a replace of the broken rk3188 at no extra cost) if I update with with the standard wifi....I could make my 3g not working anymore but it could be still full functional the reat of the unit right?

Enviado desde mi D6603 mediante Tapatalk
[MTCD  Android Head Units Q&A] doitright:
It is very possible that it could work with the non-3g system build.

However, I would caution you to find a safe way to test out the kernel so that you don't brick it in the experiment.
[MTCD  Android Head Units Q&A] ikerg:
Chinese manufacturers are going to move to PX5 with DSP included amplifier In a short time. This sofia platform is a continuation for the low end Android models. I think not all the manufacturers that produced rk3188 mtcd will release sofia because they will prefer to enter into the px5 development/production

Enviado desde mi D6603 mediante Tapatalk

---------- Post added at 02:31 PM ---------- Previous post was at 02:29 PM ----------

Yes...at least having a way to enter into recovery to going back to my firmware if something goes wrong

Enviado desde mi D6603 mediante Tapatalk
[MTCD  Android Head Units Q&A] doitright:
To what do you refer to as "PX5"?

Edit: Think I found it. It seems to refer to an evaluation board with RK3368.

The RK3368 is a pretty crappy chip. It seems to have single core benchmark scores at MOST 20% higher than RK3188, and multi-core scores of about 50% higher -- which is pretty pathetic for having twice as many cores.

In other words, the SoFIA will slaughter it almost as badly as it slaughters the 3188.... which is pretty severe.

So spec on the RK3368;

8 core A53 at 1.5 GHz.

PowerVR G6110 GPU (NEVER NEVER NEVER touch a powervr!!!)

32bit memory bus width (i.e., same as the RK3188).

Its a pretty sad low end chip.
[MTCD  Android Head Units Q&A] kc2koj@hotmail.com:
update.zip worked on bonroad unit ...i removed the mtc file after i unziped and just used update zip file......
[MTCD  Android Head Units Q&A] kc2koj@hotmail.com:
ikerg do you have pictures of you android unit
[MTCD  Android Head Units Q&A] ikerg:
Enviado desde mi D6603 mediante Tapatalk
[MTCD  Android Head Units Q&A] j2mcentire:
Have you noticed any differences with this rom?

I have the same unit as you, but mine bootloops every couple weeks and I have to do a factory reset. Also the radio's RDS is all screwed up.
[MTCD  Android Head Units Q&A] kc2koj@hotmail.com:
i have not noticed any difference ..but i haven't gone through all apps and features yet... i can say there no harm in trying the rom out ...the root update.zip also works...give it a try it might cure the bootloop...and you can always flash back the stock rom if you dont like...im looking for the stock mtcd file ..right now i have mtcd_hct_v1.81_1 ..aug 19 2016 13:17:41...anyone know where i can download this file..or if there is a updated version .....what version do you have ??
[MTCD  Android Head Units Q&A] doitright:
Given that they're publishing changelogs, do you think you could try harassing them for some SOURCE CODE to go along with them? Especially KERNEL source. I know the chances are low, but worth a shot.
[MTCD  Android Head Units Q&A] doitright:
I've been looking through Russian forums, and came across this;

http://4pda.ru/pages/go/?u=https://...%3D240&usg=ALkJrhiXUchbkWq9OYlOGyVUwFg-E2UUUQ

Now no guarantees since I am reading this through google translate, HOWEVER, I *think* the guy is saying that he took out the CPU check from the updater script and installed the wrong firmware (i.e. 3gr vs 3grw) and it "went normally".
[MTCD  Android Head Units Q&A] doitright:
This looks interesting.... https://downloadcenter.intel.com/do...to-Project-Release-Notes-and-Software-Package
[MTCD  Android Head Units Q&A] Blaze Falconburger:
I'm tempted to get one of these generic ones for my e46 (but unfortunately there is no Intel version with built in fascia yet) - how is the sound quality? This is to replace an MTCB which had poor sound quality in my experience, but made slightly better with V4A
[MTCD  Android Head Units Q&A] wanb1i:
From a sound quality perspective, I'm very happy with the HU. It sounds 200% better than the OEM HD HU installed by Toyota. It has some other issues, but I am overall happy with the purchase.
[MTCD  Android Head Units Q&A] twokidsandaphone:
Ordered a Bonroad Intel unit

Ordered one of these for what will now be my winter car. Have two Newsmy Carpad3s so curious how it will compare. About half the price of the Newsmy after shipping.

http://www.aliexpress.com/item/32717762566/32717762566.html
[MTCD  Android Head Units Q&A] CadillacMike:
i would say both my MTCD and current Intel Joying units also sound substantially better than my previous OEM head unit in the Jeep, the 430N
[MTCD  Android Head Units Q&A] Blaze Falconburger:
Thanks both, I was never satisfied with my rk3066 mtcb in terms of sound - it wasnt anywhere near as good as the 10 year old standard radio - in fact thats how i broke it, doing the sound mod. Have ordered a new joying so fingers crossed..
[MTCD  Android Head Units Q&A] bluemask69:
Blaze please update your experience with the new Intel radio when it will be in your car.

I have the same old rk3066 mtcb , connected with Audi Bose Sound System , and the sound is very poor compared to old Audi Chorus radio (Blaupunkt).

I'm waiting good news from Joying when Audi A3 model (now available on Joying website) is right fully tested , then i will buy it.
[MTCD  Android Head Units Q&A] avenant:
When trying to connect to an odb2 bluetooth dongle, my units android version tries to directly connect with a certain password to the dongle, it shows a message about the password being wrong, obviously not the default 0000 or 1234 password, and doesn't show the usual dialog where you can enter a password for connecting, which makes it impossible to connect to any bluetooth obd2 dongle ( I have 3). I suspect they sell their own overpriced elm327 dongles, with a specific password being programmed into the dongle, I was wondering if this is the problem mentioned in the wiki here: http://xdaforums.com/wiki/Hui_Fei_Type , about the obd2 dongle needing the name obd, or is this: android trying to connect with a specific password to the dongle another problem? I asked the manufacturer for the password they use to connect to an odb2 dongle, but they are always rather slow replying, if they will give the password at all.....
[MTCD  Android Head Units Q&A] Cid6.7:
I'm on bored with this unit now finally

The seller has just sent me this one Bonroad 7" 2Din 1024*600 Android 5.1.1Ram 2G https://www.aliexpress.com/item/32748633877/32748633877.html

I will install it as soon as it gets here & let you all know whats what & I hope I have 0 issues with this one :)
[MTCD  Android Head Units Q&A] doitright:
They borked up the configuration screens pretty badly.

Their "bluetooth" application will REFUSE to pair with ANY device that isn't (a) a phone, (b) has the name "ODB2" or "ODBII" or some other variation of that theme. They've also broken the bluetooth pairing PIN prompt.

First thing you need is this;

http://xdaforums.com/android-auto/m...elopment/bluetooth-settings-launcher-t3504526

That adds a launcher icon that will start the REAL System Settings --> Bluetooth activity. This will allow you to pair to ANY bluetooth device, regardless of the unnatural restrictions they added to their own bluetooth application.

SECOND, since they broke the pin prompt, you need to know the workaround for it.

On a normal Android device (phone, tablet, etc.), when you select a device to pair with, it will first try to use the standard pins (0000, then 1234), and if neither of those work, it will prompt you to type in whatever the pin for that device really is (i.e. 6789, or whatever else it may be).

On THESE, it will ONLY try the pin listed in the chinese bluetooth application. You know, the one that is SUPPOSED to only be used when a different device initiates a pairing request WITH THIS ONE. Of course, that is stupid to begin with, since Android devices pairing with each other use a special protocol that allows them to exchange pins and simply ask you if the two devices are showing the same pin. Thats all broken.

So in other words, the workaround for the missing bluetooth pin prompt, is WHEN it says that it failed to pair because of a bad pin, you go into the chinese bluetooth application, change the pin, go BACK into the REAL bluetooth settings activity, and try again.