Database Users

New Android Head Units from Pyle

Pyle has recently released a few head units running 4.4.4 Kitkat. From the Amazon description:
Android OS Computer:
Touchscreen 'Tablet-Style' Functionality
Smart Device MirrorLink/AirPlay Support
Processor: Quad Core 1.6 Ghz Cortex A9
OS Version: Android 4.4.4 (KitKat)
It also indicates "Unlock Tablet-Style functionality." I'm assuming this means it comes rooted.
While Pyle is not known as the paragon of quality, they appear to be the first brand with a US presence offering an Android HU. Since their other HUs appear to follow the US DIN standard these could have the advantage of fitting in one of the readily available dash kits.
Here are the two I found on Amazon:
[amazon dot com]/dp/B01BECUOTE/ref=wl_it_dp_o_pC_S_ttl?_encoding=UTF8&colid=S75ZYKYU5U3C&coliid=I25LAEC05MZLFW
[amazon dot com]/Pyle-PLDNAND621-Touchscreen-Navigation-Bluetooth/dp/B01BECUKD4/ref=pd_sim_sbs_422_1?ie=UTF8&dpID=51uMnRpESgL&dpSrc=sims&preST=_AC_UL160_SR160%2C160_&refRID=1A4EM6W90HKY19XFNMQA_

how much RAM? I wonder where/how it was engineered? The biggest issue w/ these chinese HUs is the poor engineering standards. One of the biggest examples being the internal/external mic wired in parallel on joying/pumpkin HUs. This issue has been around for well over a year now, and despite pumping out new models they still haven't fixed this glaring issue.
To add to that, the whole MCU concept, and the fact that the BT is effectively de-coupled from the core system.
What I'd gladly pay $500 or so for (possibly more) -
- high quality DAC/pre-outs
- no MCU
- parrot BT FULLY INTEGRATED into the OS
- proper internal/external mic interaction
- octacore
- 2GB RAM
- android 5.0. Honestly not that big of a deal if the OS is stable and runs all the standard apps
- fully mappable/customizeable hotkeys for launching custom apps from SWC/physical buttons
That would be nice. I'd sacrifice my car custom plug & play HU with a standard double din w/ those features in a heartbeat. The glaring engineering flaws in all of these current android HUs is frustrating. But I live w/ it b/c it's still a nice upgrade over stock.

Hisma said:
how much RAM? I wonder where/how it was engineered? The biggest issue w/ these chinese HUs is the poor engineering standards. One of the biggest examples being the internal/external mic wired in parallel on joying/pumpkin HUs. This issue has been around for well over a year now, and despite pumping out new models they still haven't fixed this glaring issue.
To add to that, the whole MCU concept, and the fact that the BT is effectively de-coupled from the core system.
What I'd gladly pay $500 or so for (possibly more) -
- high quality DAC/pre-outs
- no MCU
- parrot BT FULLY INTEGRATED into the OS
- proper internal/external mic interaction
- octacore
- 2GB RAM
- android 5.0. Honestly not that big of a deal if the OS is stable and runs all the standard apps
- fully mappable/customizeable hotkeys for launching custom apps from SWC/physical buttons
That would be nice. I'd sacrifice my car custom plug & play HU with a standard double din w/ those features in a heartbeat. The glaring engineering flaws in all of these current android HUs is frustrating. But I live w/ it b/c it's still a nice upgrade over stock.
Click to expand...
Click to collapse
Closest I've seen is the in-dash.net unit which is octacore with android 5.1 coming sometime this year, (allegedly). The MCU issue is unfortunately unavoidable at least until Google adds native bluetooth HFP into AOSP, which isn't likely to happen. And even then you still need something to be the go-between control of the amplifiers, LCD brightness control, etc.
I have the octacore in-dash.net unit and it's pretty good. My biggest beef is with the bluetooth handling. The interface is fairly basic. I think one thing that these units need is their own 'contacts' and 'dialer' apps that can dial via the bluetooth service but that also interacts with my google contacts, google maps, phone links, etc so that I don't have to do the contacts sharing, or copy and paste phone numbers from web searches or maps searches. I've got the feeling that that is easier said than done but it is key in my mind.
This is my first android HU so I'm not super familiar with the mic issues that seem to plague them. My external mic seems to just be really quiet pickup. I was thinking of getting a little pre-amp for it to put in between the plug and the HU. Perhaps I should do some more research first?
I have just been using the built in amp so far. Was thinking about testing the pre-outs on this unit. I suppose I could just break it down and take a look at the components to see if I can determine what DAC is being used.
Oh, also I don't have SWC in my car but this unit is setup for them. Not sure the physical interface specifically as I didn't purchase that option but the mapping is all in the "vehicle interface settings" app on the unit.

Not all of these head units have the mic problem. But joying & pumpkin, which are two of the most popular models, do have this problem. I used to have a joying, now I have a 2nd gen AN-21U, and it doesn't have the mic problem.
Yes the ability to fully integrate our phones with google now via the HU would be perfect. Google now has all my contacts as I have an android phone and save my contacts to google. But trying to call a number this way goes nowhere. Really a way to make the whole experience as hands free as possible would be great. Ford has sync, mazda has gracenote, and there are others I'm sure that attempt to implement a fully hands free system.
Other users have already examined the DAC in these units. One made an audio mod that integrates the DAC directly with the unit instead of passing it through the MCU, which significantly improves the unit's audio capabilities. It's just another example of the head sctatching engineering decisions on these things.
more info here - http://forum.xda-developers.com/android-auto/mtcb-hardware-development/mtc-sound-controlling-bd37xxx-sound-t3234660
Btw I am not sure if there is a universal pre-out configuration for these, but my AN-21U has 1V unshielded pre-outs. Pretty frustrating. I get some "white noise" in the background when I up the volume thanks to the high noise floor. Considering putting in some high quality RCA cables to see if that helps, but obviously if the pre-out voltage was higher this would be less of an issue.

Pyle PLDNAND621
I 've bought and been using one of these for about a week now and had a couple questions for you guys. This radio seems to have an app for controlling the Bluetooth function and is not controlled within the settings menus. Do you think think the app could be changed as a Bluetooth obd2 module I use with other Android device works fine with the same car. I have the same question for the radio tuner app, I don't like the layout and it won't tell me the song titles . I search but can't find a "local station" radio tuner app.
Thanks for any ideas, Doug

I've got it and rooted it on 4.4.4 su etc ...flash fire enabled.....anyone point me to someone that could walk me thru dumping the rom on this unit and someone that can then make a custom recovery we would be in the game for this unit ..it has a recovery ..all I can say for right now .....v4a apk will not work on this unit due to some busy box error I cant stop ..I have it correct in the system ....so we need custom.rom.for it .....any one still wanna rip this thing?

lokisyn said:
I've got it and rooted it on 4.4.4 su etc ...flash fire enabled.....anyone point me to someone that could walk me thru dumping the rom on this unit and someone that can then make a custom recovery we would be in the game for this unit ..it has a recovery ..all I can say for right now .....v4a apk will not work on this unit due to some busy box error I cant stop ..I have it correct in the system ....so we need custom.rom.for it .....any one still wanna rip this thing?
Click to expand...
Click to collapse
Please help. I upgraded my PYLE PLDNANDVR 695 and lost bluetooth. Pyle wants me to send it in for repair. I much rather fixing this myself.

Trying to find what is head unit type and how to update it

I've bought an Android audio system form AVIAN for my car and it stopped working, the company replace it with another head unit (it might be PX5-W211 but I'm not sure) without any documentation at all (not even in theirs sight). I don't have any information about the head unit and the company don't answer my mails. I've asked in Mercedes forum and some one suggest i can use Malaysk ROMs Lollipop 5.1.1. Does anyone have an idea how can I find the hardware type and what ROM version?
1. The AVIAN support said: "We can replace the unit with our new Android 511 Quad core unit for you. This is newer hardware and software. https://avinusa.com/mercedes-benz-e-...w211-w219.html".
2. in the link you can see its Model: PX5-W211 (Android 6.0 Marshmallow GPS Navigation System Octa core CPU (8Core) 2GB RAM memory 32GB internal storage)
3. In the system print screen appears:
"MCU version MTCD_LM_V2.22_1" (from Feb 21 2017)
Android version 5.1.1
Kernel version 3.0.101
What I'd like to have is:
-A good CD player, what i have now is a crappy application, all you can do is: Enter/Exit folder, play/stop, forward and backward. I couldn't find a way to display the tracks names and move to a selected track (when you have 50+ folders and sub folders its a must)
-Enable other android program can access the CD
-BT Tethering.
-Reconfigure some of the hard buttons
Thanks in advance, Haim.

haim_gds said:
I've bought an Android audio system form AVIAN for my car and it stopped working, the company replace it with another head unit (it might be PX5-W211 but I'm not sure) without any documentation at all (not even in theirs sight). I don't have any information about the head unit and the company don't answer my mails. I've asked in Mercedes forum and some one suggest i can use Malaysk ROMs Lollipop 5.1.1. Does anyone have an idea how can I find the hardware type and what ROM version?
1. The AVIAN support said: "We can replace the unit with our new Android 511 Quad core unit for you. This is newer hardware and software. https://avinusa.com/mercedes-benz-e-...w211-w219.html".
2. in the link you can see its Model: PX5-W211 (Android 6.0 Marshmallow GPS Navigation System Octa core CPU (8Core) 2GB RAM memory 32GB internal storage)
3. In the system print screen appears:
"MCU version MTCD_LM_V2.22_1" (from Feb 21 2017)
Android version 5.1.1
Kernel version 3.0.101
Click to expand...
Click to collapse
The new one appears to be a MTCD PX5 system, which is a nice unit and well supported with Malaysk ROMs and other cool tweaks and apps. I just got one for myself and I am very happy with it. These fora have a whole section on MTCD units. Just to make sure, what does Droid Hardware Info say about the CPU?
haim_gds said:
What I'd like to have is:
-A good CD player, what i have now is a crappy application, all you can do is: Enter/Exit folder, play/stop, forward and backward. I couldn't find a way to display the tracks names and move to a selected track (when you have 50+ folders and sub folders its a must)
Click to expand...
Click to collapse
Don't hold you breath, most (all?) MCU apps on these units tend to be sub-par. I am not aware of any nicer replacement app for CD playback, with the reservation that I do not use CDs so I have tried nothing of sorts myself.
haim_gds said:
-Enable other android program can access the CD
Click to expand...
Click to collapse
As far as I know this is impossible. The CD is managed by the MCU rather than the OS.
haim_gds said:
-BT Tethering.
Click to expand...
Click to collapse
Not possible (as far as I know). Once more, the BT module is managed by the MCU rather than the OS. It might be possible to use an external (USB) BT dongle; I have seen reports of this working (but I forgot where...).
haim_gds said:
-Reconfigure some of the hard buttons
Click to expand...
Click to collapse
That should be possible in Malaysk ROMs as well as with third-party apps such as MtcdTools.

Thank you very much sbruda.
I've attached the pictures from Droid Hardware Info
You said "The new one appears to be a MTCD PX5 system", do you mean the system called PX5-W211?
Should I use a special Malaysk ROMs for my radio? (Because it should support Mercedes W211 CAN Bus communication.)
Thanks again

haim_gds said:
I've attached the pictures from Droid Hardware Info
You said "The new one appears to be a MTCD PX5 system", do you mean the system called PX5-W211?
Click to expand...
Click to collapse
Sorry, I got a bit confused by which is one system and which is the other. So:
The one that says "MCU version MTCD_LM_V2.22_1" is an MTCD system, which is great. I am assuming that this is your current system on which you just ran Droid Hardware Info. If so, then the system is an RK3188 rather than PX5 system. It is still well supported by the community. The CPU is a bit slow by today's standards but it may serve your needs (depending on what you plan to do with it). Heck, I have right now in my car an RK3066-based unit (even older and even slower) and it works very well (navigation + Torque + media).
PX5 (aka RK3368) is the latest and greatest from Rockchip and by the name and specs I infer that this is inside the PX5-W211 you mention. I have no way of knowing whether it is still an MTCD unit or something else, so if you are contemplating it you should ask AVIN directly. The PX5 unit is more competent and up to date.
If I were you, I would go like this: If the vendor will replace the current unit with the PX5-W211 free of charge (or at a charge you don't mind) and if said PX5-W211 is also an MTCD unit then I will definitely go for that; I have nothing to loose. If on the other hand the PX5-W211 is not desirable (not an MTCD and/or costs too much money) then I will give the current unit a spin with the Malaysk ROM before exchanging it and see if that satisfies my needs.
Why do I keep mentioning MTCD you ask? Because this MTCD (and MTCB) units have by far the best community support. I would personally not purchase anything else (I tried not long ago and it was not a good experience). Community support is very important because most of the time this is all the support you will ever get; indeed, most vendors are clueless and will provide no support for the OS. In addition, there are several extra things that have been implemented by the community but not by the stock OS provided by the vendor. Mapping buttons to custom actions (which you mentioned in your first post) is one of them.
haim_gds said:
Should I use a special Malaysk ROMs for my radio? (Because it should support Mercedes W211 CAN Bus communication.)
Click to expand...
Click to collapse
You should definitely give it a try. I cannot guarantee but I am pretty sure that you will be pleasantly surprised. Unfortunately I cannot vouch for CAN bus integration (as I never used it) but again I am pretty sure that this will work at least as well as in the original OS.

Thank you sbruda.
I don't think I'm going to upgrade the FW, I have had it with AVIAN crap. I''ll keep it as it now until i got system.
Thanks for the help anyway.
Haim

New Joying PX5-based Android 8.0 Units - [Rockchip PX5 A53 | Android 8.0 | 4GB RAM]

I installed two different models of Joyings newest PX5-based head units. Both are the 7 inch screen 4GB RAM / 32GB flash double DIN model with flat buttons on the left edge.
Please note that as of May 2018, there appear to be multiple new 4GB / 32GB Joying head units have different internal hardware and are not compatible with each other or with the PX5 2GB Joying head units.
JY-UM128N4PX5 is a QD unit
JY-UO128P4 appears to be an FYT unit
Buyer beware. My recommendation is AVOID the QD based units and seek out the FYT units.
See below for more details.
The following information is for JY-UM128N4PX5. Further down the page is information for JY-UO128P4.
=============== JY-UM128N4PX5 =================
Came with Android 8.0.0 installed.
APP Version TP6735 0.0.65
MCU Version TP6735 4.40
Kernel Version 4.4.103
Master password:126
Password for changing logo:0000
Password for changing UI:8086
So far I have noticed the following:
The unit does not trigger the amplifier turn on signal wire - the orange and black wire labeled AMP-CONT always measures zero volts on my voltmeter. Workaround is to use either the antenna signal wire, or the ACC power signal wire, to turn on your amp. Joying is aware of this issue.
Sleep does not work. The unit shuts down completely about one minute after you turn off the vehicle's ignition. It doesn't sleep and then come back on instantly like my Intel-based Joying unit. Boot time is about 20 seconds. Joying support now says that sleep is not supported on the QD units.
I cannot find the radio settings in the new radio app. You used to be able to slide the bar at the bottom of the radio app to get to settings. Now in Android 8, there are a couple of radio settings that have been moved to the main android setup dialog.
Some of the functionality of the former car settings app has been moved to the android settings dialog. But not everything is there - for example this is where I was looking for the ability to tell the unit to toggle the amplifier signal wire. I could not find any such setting.
AM radio reception is non-existent - static on all AM channels.
FM reception is good, but I cannot figure out how to get the FM Radio to enable display of song and station information - this used to be under RDS settings, which no longer exist.
Bluetooth calling works fine. Seems more stable than my older Intel-based unit.
Sound quality is good - I am using an external amplifier.
The logo set up is missing Porsche and Saab Logos. My Intel-based Joying unit had these. Easy enough to load my own custom logo.
The unit ships with Joying's "Launcher3" selected. On the home screen, the labels of the bottom row of icons are cut off. The screenshots on Joying's website show the same thing. The joying2 launcher is missing.
If you reflash the unit, the vertical keypad on the left side of the unit gets un-mapped and stops working. Fix is to go into car settings and remap it.
========================= JY-UO128P4 ==================
Android Version 8.0.0
Build Number px5-userdebug 8.0.0 OPR5.170623.007
System Info APP 1024x600 2018-04-27 21:42:36
MCU Version 2018-01-23 10:59:33 JY_(R68)_R-86C-096I-NC-NP-1.0-P12S
Passwords:
Factory settings: 3368
Developer Options: 3368
Reset: 3368
Password for changing Launcher:8086
Password for changing screen current:
So far I have noticed the following:
The software on the JY-UO128P4 is very close to that of my older Joying Intel based system.
The developer has replaced all of the system settings screens native to android with their own settings screens. Not super cool. All of the car settings and android system setting are now intermingled.
Upon unboxing, the JY-UO128P4 has only a single Wifi antenna wheras the JY-UM128N4PX5 had two (diversity) wifi antennas. I have not tried to compare reception differences.
The amplifier turn on signal now works as expected (AMP-CONT wire correctly signals 12V when unit is active)
Sleep works as expected
AM radio reception works weakly.
The FM radio application works as expected. Radio app settings are accessed within the radio app. It's possible to enable RDS for song and station ID within the radio app.
All of the joying launchers are available - I prefer launcher 02 and it's available on this unit.
Many more car logos are available on the system. Porsche logo was built-in.
The only things I've noticed so far that are worse with the JY-UO128P4 than the JY-UM128N4PX5
The unit suffers from the android 8.0 bug on Joying where all of your google contacts are deleted if you allow your account on the head unit to sync contacts with google.
As noted above - the native android settings panels are all removed.
The app for setting the color of the buttons on the side panel is limited to pre-determined solid colors - yellow, white, red green etc. On the JY-UM128N4PX5 you could select and set any RGB color, which made it possible to match the button illumination to your other dashboard lights.
As I learn more, I will post more.

ddruker said:
I just installed Joying's newest PX5 head unit. It's the 4GB model.
It came with Android 8.0.0 installed.
APP Version TP6735 0.0.65
MCU Version TP6735 4.40
Kernel Version 4.4.103
So far I have noticed the following problems:
The unit does not trigger the amplifier turn on signal wire - the orange and black wire labeled AMP-CONT always measures zero volts on my voltmeter. Workaround is to use either the antenna signal wire, or the ACC power signal wire, to turn on your amp. I found another post of someone else who had this same issue.
I cannot find most of the passwords needed to set up the unit. The master password is 126 - I found that by watching a joying video. But I cannot find the second level passwords for changing the logo, changing the launcher, etc. Anyone have the other passwords?
The utility to change the color of the buttons on the left side of the unit works, but the buttons do not illuminate one the unit is booted.
I cannot find the radio settings in the new radio app. You used to be able to slide the bar at the bottom of the radio app to get to settings. Now in Android 8, there are a couple of radio settings that have been moved to the main android setup dialog - but for example I cannot find a setting to turn on the functionality to identify song and station names.
Some of the functionality of the former car settings app has been moved to the android settings dialog. But not everything is there - for example this is where I was looking for the ability to tell the unit to toggle the amplifier signal wire. I could not find any such setting.
I cannot figure out how to change the launcher - with the default launcher the lower row of app icons is only half visible on the screen.
Who else has a new Joying Android 8 unit - what else are you seeing? Has anyone found solutions to the items above?
Click to expand...
Click to collapse
I have had several back and forth emails with Joying support in the last couple of days.
They are trying to find the passwords for their new units under Android 8. Support didn't know. They had me try 00000 and 123456, neither of which worked. I told them the main password is 126 - they didn't know this either. I still need passwords for all of the second level settings - change the launcher, change the logo, see if there are more developer options for car config, etc.
They are apparently aware that the AMP-CONT lead to turn on the external amplifier does not work. They recommend connecting the accessory wire from your vehicle to the amp signaling wire instead, so the amp will turn on when you turn your key to the accessory or on position, bypassing the head unit.
They acknowledge there are no detailed settings available for the radio under Android 8 in the radio app. So there is no way to turn on station or channel ID for US customers.
I also let them know about another radio issue - FM Radio reception is normal, but AM reception is awful to non-existent.
Google maps is ok, directions from Google maps are mixing with other audio ok.
Feels like Android 8 on the new Joying 4GB units isn't quite ready for prime time yet... Has anyone tried to upgrade a 2GB Android 6 unit to Android 8 now that the Android 8 files are on Joying's website? Do you see the same behaviors, or am I seeing hardware issue with the brand new 4GB units? I suspect it's all software, but would be nice to know.

ddruker said:
Feels like Android 8 on the new Joying 4GB units isn't quite ready for prime time yet... Has anyone tried to upgrade a 2GB Android 6 unit to Android 8 now that the Android 8 files are on Joying's website? Do you see the same behaviors, or am I seeing hardware issue with the brand new 4GB units? I suspect it's all software, but would be nice to know.
Click to expand...
Click to collapse
The 2GB units are not compatible with the 4GB units. They need different hardware drivers and different MCU firmware as the firmware in the 2GB units is from FYT. I forgot the manufacturer of the 4 GB units but @gtxaspec knows.
There is no downloadable firmware yet for the 2GB units.

hi, i've the same unit and the password was noted into the user manual, it's 3368.

If you buy Joying android 8.0 unit the SKU like:JY-UO135N4PX5 or JY-UOS03N4PX5,password as below:
Master password:126
Password for changing logo:0000
Password for changing UI:8086

TomTom
It seams to be so hard. Again an Android HU, where TomTom navigation does not work. It let's me download the maps, but after that it crashes every time I try to load the application.

I can confirm these passwords are correct:
Master password:126
Password for changing logo:0000
Password for changing UI:8086
Other findings so far:
The illuminated buttons do work - they sometimes take a few seconds to come on after your illumination wire signals with 12V.
The logo selection with this new unit does not include Porsche or Saab. You can still upload your own custom logos.
I updated the unit to the latest (2018-4-20) release on the Joying website which is supposed to include optimizations and Zlink and my unit is now hanging at the Android text logo (right after the animated Android logo). I sent a note to Joying support for help and will also wait for a few hours to see if it comes back to life.

ddruker said:
I can confirm these passwords are correct:
I updated the unit to the latest (2018-4-20) release on the Joying website which is supposed to include optimizations and Zlink and my unit is now hanging at the Android text logo (right after the animated Android logo). I sent a note to Joying support for help and will also wait for a few hours to see if it comes back to life.
Click to expand...
Click to collapse
The same happened to me
After writing about 25 emails with Joying support I had to reflash the whole system ... loosing all my data.
For now I am really not going to try any more updates from Joying with this unit.
Really hoping for a Custom Rom & Root for this unit.

I have one of these as well. Any one find where the setting is to make the sleep mode last longer(2hrs) before it full shuts down? it seems to be locked on 30sec currently. Also it wont pair with my OBDlinkMX BT dongle. in the older MTCD units, making the BT password 1234 let you do it, but not here. anyone have any luck with BT OBD dongle pairing?

I was really leaning towards getting this unit but have been holding off because I wish it had Bluetooth 5.0, maybe I should wait a little longer since it seems to have a fair amount of bugs. I know a lot of people are happy with the Xtron since it has all the best features I just really prefer to have the buttons on the left like this unit has. Looking forward to seeing if you guys can get this squared away

peregrines said:
The same happened to me
After writing about 25 emails with Joying support I had to reflash the whole system ... loosing all my data.
For now I am really not going to try any more updates from Joying with this unit.
Really hoping for a Custom Rom & Root for this unit.
Click to expand...
Click to collapse
I was able to get my unit working again by reflashing. It took about 10 tries with three different USB cards but it finally worked. Joying support provided a file that included a system image and a Window-based chinese language USB card writing programs, along with a word document with instructions. You build the USB drive and then plug it into the left hand USB connector, and click the reset button on the front of the unit. It loads, then tells you to remove the USB drive, and then if you are very lucky it will reboot into Android.
After re-flashing, the vertical keyboard on the left side of the unit did not work. Turned out the mappings had been erased. Fix is to remap the keys - there is an option in car settings.
Current issues still present in the unit seem to be:
Unit shuts off entirely after 30-60 seconds instead of sleeping when you turn off the vehicle. My intel-based unit sleeps for several days.
No AM radio reception - static on all channels.
No way to turn on song or station identification in the radio settings for FM.
AMP-cont signal wire does not work. I've worked around by wiring my accessory wire directly to my amp's signaling wire.
Have not tried Torque and Bluetooth ODBII reader pairing yet - on my list for this weekend.

So, it's not just me...
I purchased a JY-UM135N2PX5 (PX5 2G/16G) with Android 6.0 mid to late March.
I had it on my bench through April, testing and configuring it prior to install.
After trading emails with Joying tech support, I was sent an Android 8.0 update to address a Zlink/iPhone issue.
I started my install in the car today, and discovered "no sound". I guessed that the AMP-CONT wasn't turning on the OEM amplifier. I rechecked the cables, which checked out just fine. Tried a Joying JY-UM135N2 (Intel Sofia 2G/32G Android 6) on the same harness, and it functioned as expected (turned the OEM amplifier on and had sound). I took them both back to my bench and noticed that the "AMP-CONT" on the PX5 unit did not appear to have 12V on it, while the Sofia unit did.
I did not leave the non-functional PX5 unit in the car long enough to see any other issues.
I am curious if I were to revert back to Android 6 on the PX5 unit, if it would fix the AMP-CONT issue (at the cost of breaking the Zlink/iPhone functionality)

ddruker said:
I was able to get my unit working again by reflashing. It took about 10 tries with three different USB cards but it finally worked. Joying support provided a file that included a system image and a Window-based chinese language USB card writing programs, along with a word document with instructions. You build the USB drive and then plug it into the left hand USB connector, and click the reset button on the front of the unit. It loads, then tells you to remove the USB drive, and then if you are very lucky it will reboot into Android.
After re-flashing, the vertical keyboard on the left side of the unit did not work. Turned out the mappings had been erased. Fix is to remap the keys - there is an option in car settings.
Current issues still present in the unit seem to be:
Unit shuts off entirely after 30-60 seconds instead of sleeping when you turn off the vehicle. My intel-based unit sleeps for several days.
Poor AM radio reception
No way to turn on song or station identification in the radio settings.
AMP-cont signal wire does not work. I've worked around by wiring my accessory wire directly to my amp's signaling wire.
Have not tried Torque and Bluetooth ODBII reader pairing yet - on my list for this weekend.
Click to expand...
Click to collapse
Would you be so kind as to share those files with us? This would be a good starting point for further testing and research. Simply upload to a hoster like mega.

z0rn said:
Would you be so kind as to share those files with us? This would be a good starting point for further testing and research. Simply upload to a hoster like mega.
Click to expand...
Click to collapse
Here is a link to the zip file from Joying with the firmware image for reflashing, their USB drive utility, and instructions...
https://drive.google.com/open?id=13HXHRRfuduhIYV41pjQlvsJ0o3xesNBC

Here is the reply I got from Joying support this morning in regards to the open defects I am tracking with the unit. I suspect that all of this will get fixed in subsequent software releases, it's relatively obvious stuff. Can anyone confirm if these same issues exist in the Android 8 builds on Joying's 2GB PX5 head units, or are these unique to the newest 4GB units?
Dear friend,
Please noted :
1) sorry that your system is different with Intel head unit , it do not have fast boot feature . so it will completely off .
2) for the AM receptions is bad , you need to set the proper time and zone . also the radio area choice .
3) sorry, the head unit you purchased do not have the RDS setting .
4) for the am-cont not voltage , please connect the ACC (red wire ) to your amplifier wire . then can offer 12V .
Hope your noted .
Candy

ddruker said:
Here is the reply I got from Joying support this morning in regards to the open defects I am tracking with the unit. I suspect that all of this will get fixed in subsequent software releases, it's relatively obvious stuff. Can anyone confirm if these same issues exist in the Android 8 builds on Joying's 2GB PX5 head units, or are these unique to the newest 4GB units?
Dear friend,
Please noted :
1) sorry that your system is different with Intel head unit , it do not have fast boot feature . so it will completely off .
2) for the AM receptions is bad , you need to set the proper time and zone . also the radio area choice .
3) sorry, the head unit you purchased do not have the RDS setting .
4) for the am-cont not voltage , please connect the ACC (red wire ) to your amplifier wire . then can offer 12V .
Hope your noted .
Candy
Click to expand...
Click to collapse
Are they serious? I would suggest to try the Malaysk Rom, i guess your units are MTCD and MTCE devices so maybe this rom would support the missing software like rds and the other hardware not supported by Joying
https://www.youtube.com/watch?v=WWvgrcn_As8
https://forum.xda-developers.com/an...-malaysk-roms-px5-2-4-gb-8-0-android-t3762724
Good luck!

Flemischguy said:
Are they serious? I would suggest to try the Malaysk Rom, i guess your units are MTCD and MTCE devices so maybe this rom would support the missing software like rds and the other hardware not supported by Joying
Click to expand...
Click to collapse
These units are NOT MTCD/E. Do not use the Malaysk ROM.
---------- Post added at 07:08 PM ---------- Previous post was at 06:53 PM ----------
ddruker said:
Here is the reply I got from Joying support this morning in regards to the open defects I am tracking with the unit. I suspect that all of this will get fixed in subsequent software releases, it's relatively obvious stuff. Can anyone confirm if these same issues exist in the Android 8 builds on Joying's 2GB PX5 head units, or are these unique to the newest 4GB units?
Dear friend,
Please noted :
1) sorry that your system is different with Intel head unit , it do not have fast boot feature . so it will completely off .
2) for the AM receptions is bad , you need to set the proper time and zone . also the radio area choice .
3) sorry, the head unit you purchased do not have the RDS setting .
4) for the am-cont not voltage , please connect the ACC (red wire ) to your amplifier wire . then can offer 12V .
Hope your noted .
Candy
Click to expand...
Click to collapse
I have a 2GB Android version 8.0.0 unit, but my unit is a FYT based unit like the Sofia 3GRs, unlike yours which is a QD unit.
Mine does have fast-boot as my unit is a FYT based unit, using the same hardware/SOM as the Sogia 3GR intel units.
I never used AM-reception. I wouldn't know, but I know from previous users on Sofia 3GR that they also complained about the AM reception
Which RDS-setting? This is so confusing and so not concrete. RDS is a complete set of functions. The syu/FYT based software on the FYT based units support RDS-PS, RDS-PTY and RDS-TA/TP. The latest firmware versions on FYT units (Sofia 3GR and my PX5) also support RDS-RT. They do not support RDS-AF. They implemented "something" like AF. If you use that option it does not select the Alternate Frequency of your radio station, it selects the strongest signal it can find of any station. Note that it is the software. The radio chips in all these units support the complete RDS set of functions.
Don't know about the the amp-cont wire.
You ask about and mention AM and about RDS. I hope you know that RDS can only be used on the FM signal. RDS is not available for AM.

Help
Heres a link I need help to identify my android head unit
https://app.box.com/s/o90d0lnjrqqlek5w1q6lekaj5dgsa20y

Traww said:
Heres a link I need help to identify my android head unit
https://app.box.com/s/o90d0lnjrqqlek5w1q6lekaj5dgsa20y
Click to expand...
Click to collapse
You have an Allwinner T3 chipset in your unit.
Do not use a Joying thread to ask a completely off-topic question.

I've received the same unit, facing the same issues as the OP.
Also the localisation in my language is quite poor.
surfer63 said:
These units are NOT MTCD/E. Do not use the Malaysk ROM.
Click to expand...
Click to collapse
I've bought this unit in the hope that it would be compatible with custom ROMs.
Are you saying that the unit MCU is almost unknown and that no custom ROM would be available in the near future?

ROM, MCU, Firmware, Operating System...

Hi Android Auto likers.
i'am new to this, so i need a little help please.
I have a head unit in my car now and some things i miss. So i come here!
For my understanding:
The deep operating system is the ROM, like Bios on a PC?
The MCU, in my case MTCE_CZ_V3.06_2, is the connecting part, or translater between ROM and Android? Like DOS in earlier times.
Android now is like Windows.
My android version is 9.
- The sound over Line out has a background noise
- settings are missed, compared to the smartphone
- instable some times
What i understand, first flash the latest MCU, is that right?
In my case a MTCE_CZ only (found here: MTCE-CZ-3.30sp+by+cs-x)
What means sp+by+cs-x?
I would be happy, if you make some light inside of my head
Regards, Olli

You will see many abbreviations through the forum as you've noticed. You are a bit confused though. First what things are:
- HU: Head Unit, the radio.
- SoM: System on Module, that's basically the motherboard you would find inside an Android tablet.
- SoC: System on Chip, that would be the CPU + GPU+ IO. That part is on the SoM.
- MCU: Micro Controller Unit, is an interface between the car and the SoM and also gives the SoM WiFi connectivity, USB ports and Bluetooth capabilities.
- ROM: The chip that contains the operating system and is also used to describe the firmware.
So you have 2 systems talking to each other and each has it's own firmware. There are custom Android firmware for some SoC's but all can used the generic Android as long as you match the ROM partition. The MCU firmware you have (MTCE_CZ_V3.06_2) is specific for that MCU, vendor and resolution. You must match all the characters except the Version number but you knew that. MTCE is the MCU type, CZ is the vendor and 2 is the settings preset and is usually related to the display res. You should only upgrade these HU to solve a problem. Before you upgrade the MCU always export the settings from the factory settings menu, in fact you should probably make a backup for safe keeping anyway.
In the MTCE-CZ-3.30sp+by+cs-x filename the "sp+by+cs-x" stands for sound patched by cs-x. There's an issue with the audio level and cs-x found a solution, read the thread.
The background noise from the line outs whether you're talking speaker outs or RCA's is due to the low quality of these HU but could also be caused by the gain setting in the factory menu. Some people have found solutions for that are specific to the cause/type of the noise. You'll have to search. Same goes for the instability. Look at installing a heatsink or removing some apps.
These HU's are not phones so it's normal Android settings are missing.

nic2k said:
You will see many abbreviations
Click to expand...
Click to collapse
Thank you very mouch, that you take the time, to explain this to me!
I'am sure, many others will read with lot of interest.
Yes, the reason of background noise (here RCA), is quality. But you get a mega system for very small money...
I have a seperate DSP (Mosconi) with digital input and would love to use it.
Some weekend, i like to have a view inside of the machine, if there is a digital output.
The only mistake of the system now is, original FM/AM Radio failed. No sound, and starts not on last station. Reset here, and adjustments there, it works again.
For 1-2 days... but didn't find, what cures. One time on poweramp, there was TA, Traffic Information, Radio worked again for a time.
Best regards,
Olli

TS10 unit where the stock radio lacks RDS (com.tw.radio app)

Hi,
i have a head unit (TS10) which actually works quite nicely. Its supposedly an octa-core unit (6GB/128GB version) that runs "Android 12" (i suspect that it would be version 10 irl, but anyhow...)
One thing that bothers me a bit is that this unit (or the software on it) is that the radio app (com.tw.radio.Radio) does not support radio text. I have tried other options (the navradio+) which doesn't support it either (it seems).
My previous unit (which was a cheap yt9213aj unit) DID support it. Am i doing something wrong here or does these TS10 units simply not support it?

TS10 support RDS text! And NavRadio running on TS10 support it too.
Why are you saying that?
RDS text depend mostly on the radio stations broadcasts.
If your unit receive the RDS station name then it can receive also the text.
In some countries the text is not sent in the correct field and everything is sent in the RDS name field sequentially.
That's what is called "LiveRDS".
Most of USA radio stations adopt this LiveRDS method.
In Poland is very common too.

Hey KoTiX2,
Maybe its me doing something very wrong here, but i can't get it to work whatever i try. On my old unit, i could alway see the current song/artist, etc in the particular portion of the screen (just beneath the station name) but on this unit, i can't really capture anything. I have tried to enable all/any option available in the menus but to no avail (unfortunately).
I think i have seen fragments of the same question here on this forum where other TS10 users have asked the same thing (and i need to find them again and link for reference). But in general, is there something specific that needs to be enabled for this to work? When i saw (IRL) my old yt9213aj having the support for it (and later on, reading up on how "funky" the implementation actually was for this particular family of units), i started to have my doubts.
(again, idk what is supposed to work and what is not, which is why i'm asking this perhaps daft question)
And please take my question the right way. I see that you are the author of navradio+ which is (imho) a superb application for radio (its rather brilliant tbh - clean interface and well laid out). Of course it could just be my own setup / configuration that is wrong in this case. I simply can't tell.

Check if you have RDS on, it's in the settings: config info. It also depends on what radio module you have, some do not support RDS, for example Phillips (NXP) TEF6851 is without RDS. Or there is an error in the firmware, someone was helped by an update. Your thread is here, try searching:
New TS10 UIS7862 6gb ram 128gb head unit q&a's
So I bit the bullet and bought myself this head unit: https://a.aliexpress.com/_9JZiHu Ad stated that unit is 4gb ts8, but unit shipped and arrived is 6gb TS10. Plugged everything up unit works nice and smooth as expected, but one seriously...
forum.xda-developers.com

Thx Pavel-71, i'll search that thread and/or post there
The unit reports that it has a TDA7708 radio module on-board and when looking at spec-sheets for this module, it should really support this properly. Maybe it is what KoTiX2 mentions above that they store the data in the wrong field (essentially hiding it from view).