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.

Buying a Chinese Android head unit

Hello guys!
So, I have a 2005 Audi A4 B7 and I'm thinking about buying an android head unit for my car. So far I have found 2 head units that look somewhat like the factory one, or that I like. They both have Android 8.0 / 8.1, Quad-Core with 2GB of RAM. Now, are these chinese head units generally worth it? I'm really concerned about sound quality (I have an aftermarket amplifier and subwoofer installed). Now I have a Kenwood head unit and the sound output is decent, can't really complain (better than factory radio).
And I have a few questions.
One of the units is made by Mekede (the factory look-alike) and the other one is made by Wondefoo. Has anyone had any previous experience with these 2 makers?
Also, I do not see an AUX IN on these chinese head units. Do the have one? Is it possible to have one? I'd much rather play music over BT, but is generally the connection stable?
Seeing as they are Android, am I able to install 3rd party apps, such as Vanced YouTube ? Or Waze (or any other app that does not come preinstalled) ?
Generally speaking, how is the boot up time on these units?
They both cost around $210. Are they too cheap? Should I try and save up more? Look for other makers? Most of the times I'm going to be listening to music (either via USB, BT - or any way it can be connected to my phone; or YT) while, sometimes, using Google Maps / Waze. Are these cheap android head units generally laggy when multi-tasking? Does it really matter which one I buy, as they're all "cheap chinese products"?
Here are the links to the units:
1. Mekede
2.Wondefoo
Or if you guys could recommend me another one which really is worth the money, it'd be appreciated. I'd like it to have volume knobs, and the factory look-alike is a plus.
I am sorry if these questios have been asked before!
Thank you!

One thing to keep in mind - RAM amount. 1GB of RAM is not enough for these units. I'd recommend 4GB of RAM, but make sure you get at least 2GB of RAM for sure (and even that may not be enough).
Try to find a unit with PX5 (octa-core) or PX6 processor and 4GB of RAM, if possible. Android 8.0 or 8.1.
In terms of sound quality, I too was concerned. I ended up rooting and installing Viper4Android and the sound quality is great. I'm using an extenral amp, but the internal amp sounded good with V4A as well. Viper4Android gives you a LOT of flexibility in customizing the sound to your liking.

jtrosky said:
One thing to keep in mind - RAM amount. 1GB of RAM is not enough for these units. I'd recommend 4GB of RAM, but make sure you get at least 2GB of RAM for sure (and even that may not be enough).
Try to find a unit with PX5 (octa-core) or PX6 processor and 4GB of RAM, if possible. Android 8.0 or 8.1.
In terms of sound quality, I too was concerned. I ended up rooting and installing Viper4Android and the sound quality is great. I'm using an extenral amp, but the internal amp sounded good with V4A as well. Viper4Android gives you a LOT of flexibility in customizing the sound to your liking.
Click to expand...
Click to collapse
Must be a PX5 or PX6 ? Most of the sellers don't list their processor model, just listing it as "octa-core". I'm aware that V4A can give you a lot of flexibility in sound customization (I've used it on my phone for a while)
Do these head units integrate well with the CAN ?

Here are the more technical names (may help identify them):
PX3: Cortex A9 (Quad-core) - 32-bit ARMv7 architecture.
PX5: Cortex A53*(Octacore) - 64-bit*ARMv8 architecture.
PX6: Cortex A72 (I'm not sure of the details - brand new platform)
From what I've seen, most Android 8.0 units are PX5 and most Android 8.1 units are PX6 (brand new). Units with older versions of Android are probably PX3, I'm assuming. Most of these units do not get "official" major Android version updates - the manufactureres just release new models instead of upgrading existing models (but some can be upgraded via custom ROM's).
Personally, I would probably look for a PX5 MTCE octa-core unit with 4GB of RAM. I wouldn't consider anything older than a PX5/Android 8.0 unit - and like I said, I'd recommend 4GB of RAM if you can find it. The PX6 units are brand new - there are no custom ROM's or anything for them yet or anything. They also seem to come with less RAM and storage from what I've seen?!?!
Only way to be 100% sure what you are getting is to ask the seller - they should be able to tell you the processor type and "MCU" type (MTCE-XXX),where XXX is the MCU type. The MCU is like the "go between" between the Andorid OS and the radio hardware (MCU type can be seen under the Android settings menu) - you may even ask them to send a screenshot of the hardware info from the Android settings to confirm what it actually is.
Just a "general" overview of some of the basics - I hope that helps.
Oh - and if you have a CANBUS car, you need a CANBUS adapter. If the seller is selling a unit specifically for your car, they usually include the CANBUS adapter. That will allow your steering wheel controls to keep working and other items.

Yes. That actually helped. These with 4 GB RAM and at least a PX5 cost more, about $350 so I'm going to wait, save up a bit more, because I also need to convert my car from 1 DIN to 2DIN and that will cost me at least an extra $70.
I also want one that looks like the factory equipped one, so, yeah, I'll just wait another month or so.
Thank you for your answers, guys!
Sent from my SM-G935FD using Tapatalk

I have a mekede unit supposed to be android 8.1..... It's not it's actually 6.0
This was from mekede official store on aliexpress
They are now not answering my messages and unfortunately I didn't figure this out until after the buyer protection time limit had ended.

Just to post an update to my original post... At first, I thought that the sound quality was great. But the more and more I used the head-unit, I found that sound quality was NOT up to par with my previous WinCE head-units. And I also ran into noise-related issues. I did everything in my power to try and resolve these issues (including using external amps for better sound quality), but in the end, I gave up and re-installed my WinCE head-unit.
Unfortunately, from my experience, these Android head-units just aren't up to par in terms of sound-quality and noise-rejection. I had noise-related issues from the LED backlighting, USB devices, wifi and bluetooth wasn't very good either. Hopefully, they continue to improve upon these units, because having the head-unit run a full version of Android is great - but sound quality is also important - and even more important to some (like me). Would be great if the big audio companies starting building full Android head-units (Pioneer, Kenwood, Alpine, JVC, etc).
Since my WinCE unit supports Easy Connect, I can still get the advantages of Andoid for certain things while also having fantastic sound-quality and no noise issues. Best of both worlds. Granted, the WinCE unit is significantly more expensive ($699 vs $350), but just like anything else - in most cases, "you get what you pay for". The WinCE unit that I'm talking about specifically is the Dynavin N7 - and they use high-qaulity sound components. But I also had Rosen WinCE head-units and they sounded great as well (but again, significantly more expensive).
All depends on what is most important to you - software flexibility or sound quality.

My new 2021 PX6 from Phoenix Automotive Vertical Fast Boot OEM fiber option. Had this for about 2 months. I use it with an external OEM AMP. Used in a Lexus.
AMP is not fiber. The unit is a PX6 MCU RL78c (2014 Chip-set) NCHHWY V332-0 , Framework px6-userdebug 9 PQ2A 190305.002. OS 9.
Audio is very good! I love the sound. Speakers: OEM Mark Levnson in the front, 6.5inch JBL GX600C + Sound Ordnance M2-10DVC 10inch in the back.
Tested only with stock HU.
What works on the stock PX6:
(With correct wiring harness)
1. Fast-Boot. After first 2 setup boot-ups, on is instant for 24 hours of nonusage.
2. AC controls work (Cooling).
3. Searing Wheel controls work out of the box on Lexus w/canbus included.
4. Audio player works but not a good GUI.
5. Phone works with Bluetooth.
6. Android Auto is installed and works.
7. DSP Sound works with an EQ and many settings, GUI is good.
8. Most User Settings seem to work. Wheel mapping may stop after Fast-Boot for 5 minutes (bug).
9. Navigation (Google Maps) works, GPS works.
9.5. Maps works Off-Line in Google Maps.
10. Radio with about 16 memory storage.
What is not working in a Lexus / Toyota :
1. Factory Settings. All-access is denied. Locked out! Big Issue for me.
2. GAS monitor/usage. This should work out of the box. Phoenix says it is not working and is disabled in Lexus. BUT is advertised to work on the Phoenix site.
3. Sound MAX loud setting will NOT save after reboots. After boot, the sound is all the way up, loud. After talking with Phoenix tech, no fix. However, if FastBoot is on, the audio may save to a lower setting for about 24hours. If you don't use HU for 24 hours settings are lost again..
4. Screen will reflect windshield in GS Gen3 Lexus. May be an issue in sunlight.
5. If you wear Sunglasses or have glasses that do auto shade to dark, you may not like the screen because it can be hard to see.
6. Radio- Local / Distance not working. Can't find a fix. However Local radio is working fine. I get most local stations clear.
7. Temp display worked for 2 days now showing -40 at all times. (No fix).
8. Fast-Boot image changing. The stock app that changes the BOOT-Image will not work. It is out of date and will not work with Android 9+. It needs an update from Manufacture. A Phoenix Auto add-on app (download), also will not work, out of date. App complains of an Error with the Android version.
Add-On that work:
1. Musicolet from Play Store. The Stock Audio player sucks big time.
2. Bluedriver OBD2 reader.
3. Torque Lite or Pro OBD2 reader.
4. Function Generator, from Play Store.
That's about it.
Roger Out

Ready to make my Joying better but I need some guidance

I am not new to flashing ROMs, been doing it as a novice for years on phones and tablets. I love Android and the openness of the environment so when I was ready to do a Android head Joying seemed like the right choice based on what i read and the float mount (Airmount?); I can still argue FOR joying on many fronts but there are a few Key items that just drive me nuts.
They are trying to be too proprietary, i get it you want to offer a specific environment but i came here for Android and I want just that.
why are the bluetooth settings in the Phone app???? and why is it so hard to connect a device???
Why are the settings in general so custom????
Now what I do like and certainly want to retain is the DSP, but it would be nice if the Sub settings where part of the DSP as they should be.
Communication sucks with joying, that may be a bit of language barrier but that leads into my last issue:
terminology - I am not a stupid person but i can't figure out what specific information is truly needed when I start looking at upgrades.
I think the important information is that I have a 7 inch SC9853 with Android 8.1, correct me though because i want to understand this. What is GTX and PX5 in reference to? Sofia is the non-intel based units, right?
So what ROM should I be looking at? I want to upgrade my current unit to Android 9 but Joying has said it will not get 9 which sucks because I just bought it a year ago.
So my questions are:
-What Custom ROM do I need?
-Is there a custom ROM that is based on 9?
-Does a custom ROM retain the Same DSP functionality? The way I understand it is that the UI is specific to the physical Sound Processor chip on the board, is that true?.

Mr.Adam said:
They are trying to be too proprietary, i get it you want to offer a specific environment but i came here for Android and I want just that.
why are the bluetooth settings in the Phone app???? and why is it so hard to connect a device???
Why are the settings in general so custom????
I think the important information is that I have a 7 inch SC9853 with Android 8.1, correct me though because i want to understand this. What is GTX and PX5 in reference to? Sofia is the non-intel based units, right?
So what ROM should I be looking at? I want to upgrade my current unit to Android 9 but Joying has said it will not get 9 which sucks because I just bought it a year ago.
So my questions are:
-What Custom ROM do I need?
-Is there a custom ROM that is based on 9?
-Does a custom ROM retain the Same DSP functionality? The way I understand it is that the UI is specific to the physical Sound Processor chip on the board, is that true?.
Click to expand...
Click to collapse
In short (as so much has already been written about it):
your questions: There is no custom rom. question 2 & 3 are therefore not relevant.
Based on all licenses they must open their code as they are expanding on the Google system, but they don't. Try to get a loyer working on that in China. (This is for the system with all kind of custom hardware drivers. They do not have to open the source code for their apks). Note that this is FYT, not Joying. Joying is just a reseller of FYT hardware and software.
I do not know what GTX is. PX5 (PX3/PX30/PX5/PX6) are rockchip based units. The Sofia and Airmont SC9853i are Intel based units.
They close Bluetooth as they only want you to buy "their" hardware, e.g. the hardware suppliers they have contracts/arrangements with.
The settings are "so custom", because the unit IS custom. It contains a lot of hardware components and links to car hardware, you will never find in a phone. So that is not something you can blame them for, it is because an Android car head unit IS custom.
Google is in close cooperation with several car brands to make head units that ARE Android Auto. They now run in all kind of "unexpected" hardware "challenges", but they will succeed (google for it).

so then with that and based on what i see there isn't really much aftermarket support for any of these "Android" head units and they all mostly suck in their own way; you have to pick and choose the features you want the most and give up the rest...
so a head unit that just did Android Auto would be better than a on-board Android unit feature wise......

China headunit flash Android Auto.

Hi all,
Some time ago I found a thread on here that directed people how to reimage the head unit with an Android Auto. Is this possible for all head units, or are there things to watch out for? I tried searching but could not find the relevant info(Could be on me).
If I go into About Device of the Head Unit all it shows me RK3368 as name, no more info. All I can find is a thread how to update a headunit with the PX5 to Android 10, which it is already running. If possible I'd really like to flash Android Auto on it, as the current solution feels a bit like a bandaid solution.

Bump

Found some more info. It's a S32F0 MCU, with a PX5 board.
Still trying to figure out if it's MTCB or MTCD and if I can flash Android Auto on it. Any help would be appreciated

DragonSlayer3X6 said:
Found some more info. It's a S32F0 MCU, with a PX5 board.
Still trying to figure out if it's MTCB or MTCD and if I can flash Android Auto on it. Any help would be appreciated
Click to expand...
Click to collapse
Okay so here is an obvious question - why on earth would you put Android Auto on a real Android device? Android Auto is a scaled down version of true Android with some "lite" functionality and support for some basic apps. Android Auto is for those who (for some reason) can't install a proper Android Head Unit.
To put it simply, you can do everything on your Android that you can on Android Auto but not the other way around.
You have S32F0 as MCU, meaning it's not MTCx. Luckily for you, you can still use the only mod that matters - Malaysk. Forget anything else. With Malaysk you can customize your head unit with nearly no limitations to make it fast, user friendly and overall just awesome.
Go to this thread and follow it's instructions.

iceblue1980 said:
Okay so here is an obvious question - why on earth would you put Android Auto on a real Android device? Android Auto is a scaled down version of true Android with some "lite" functionality and support for some basic apps. Android Auto is for those who (for some reason) can't install a proper Android Head Unit.
To put it simply, you can do everything on your Android that you can on Android Auto but not the other way around.
You have S32F0 as MCU, meaning it's not MTCx. Luckily for you, you can still use the only mod that matters - Malaysk. Forget anything else. With Malaysk you can customize your head unit with nearly no limitations to make it fast, user friendly and overall just awesome.
Go to this thread and follow it's instructions.
Click to expand...
Click to collapse
Hi Ice,
Thank you for you answer!
My main reason is the ability to mirror screen. I don't have a 4G dongle attached to my radio, as that is quite expensive over here. So I was thinking to be able to use my own phone as mirror onto the radio to navigate, play spotify etcetera.
For example I can copy my phonebook to the head unit, unfortunately both me and my wife use the car, which causes a very long contact list with duplicates etc.
What I've seen with friends is that Android Auto fixes some of those issues, as you don't run a seperate instance of the phonebook or whatever, but it's a mirror from your phone.
I've seen Malaysk's post, but also read in the thread there are quite some issues and support is flaky at best. Are those posts stirring sh*t for no reason, or do they have a point?
Finally, the seller claims my headunit is real Android 10, with build number 205150. I cannot find anywhere if this is real Android 10, or the so called fake android 10.

DragonSlayer3X6 said:
Hi Ice,
Thank you for you answer!
My main reason is the ability to mirror screen. I don't have a 4G dongle attached to my radio, as that is quite expensive over here. So I was thinking to be able to use my own phone as mirror onto the radio to navigate, play spotify etcetera.
For example I can copy my phonebook to the head unit, unfortunately both me and my wife use the car, which causes a very long contact list with duplicates etc.
What I've seen with friends is that Android Auto fixes some of those issues, as you don't run a seperate instance of the phonebook or whatever, but it's a mirror from your phone.
I've seen Malaysk's post, but also read in the thread there are quite some issues and support is flaky at best. Are those posts stirring sh*t for no reason, or do they have a point?
Finally, the seller claims my headunit is real Android 10, with build number 205150. I cannot find anywhere if this is real Android 10, or the so called fake android 10.
Click to expand...
Click to collapse
Mirror screen functionality on Android Head Units is shaky at best.
You don't need 4G dongle - hotspot from your phone to give access to the Internet on your head unit - that way you can run any Android app on the head unit, Spotify, YouTube, Internet Radio etc etc. Make sure to give full permissions to your phone
Use BlueTooth on your phone to use handsfree calling. Use Google Voice to dial any number (no need to mess with Contact Books), your wife can do the same and your Android Head Unit will not sync contacts back to your phone
I know Malaysk developer as I'm also a Russian-speaker and his work is exemplary. If anything, his firmware is by far more stable and effective compared to anything you get from factory. People who complain about it, simply do not have the right skills of installing it and using it. Spend some time with Malaysk tutorials - well worth it. Malaysk also offers ROOT natively and Viper4Android which means you can tweak most parameters on your head unit and considerably improve the sound in your car.
Doesn't matter what Android version you have. You should go with Malaysk firmware for Android 9 (most stable). You will need to get a "rollback" software to successfully install it if your Android is anything but version 9. For that you'll need to purchase MOD Installer Pro 2 for €10
Whatever is possible to do your Android Head Unit will only be possible with Malaysk. If Malaysk can't support it, then it's simply not doable.
You can also look into "profiles" on your Head Unit. I.e one profile will have your stuff, and the other one will have your wife's.

PX5 processor module replacement - no multimedia sound

Hello. I bought a damaged radio and replaced the PX5 processor module from another radio (PUMPKIN). After replacing the PX5 processor module, the radio works - I only had a problem with Bluetootch - the GOC-RF210 module was installed in my radio, which was not on the factory settings list. So I replaced the BT i140 module with Pumpkin. After switching the BT module to the i140 and selecting it in the factory options - it works without any problems. Radio works, navigation, DSP processor, bluetootch. The only problem is the lack of voice only in the MUSIC application (e.g. from a flash drive) and movies from the Internet and navigation. Visually, everything works only without a voice. Oddly enough, there is sound from the radio and BT. There is also a beep sound from the buttons all the time. I was restoring factory settings, updating the MCU but nothing changed. I did not find a solution in the factory settings. There was also no sound before replacing the BT module. Can anyone help in solving the problem? Regards.

So, based on some of your comments, I am assuming the PX-5 module still has the same Android SW that it had on the PUMPKIN unit, or you installed it again using a PUMPKIN release
"the GOC-RF210 module was installed in my radio, which was not on the factory settings list "
Could it be that you're mixing PX5-Android OS from one provider with the MTCD/E board of another provider? Do you know who manufactured the "original unit" (the Physical unit, regardless of where you took the PX5 from)
So, while I can not give you a definite answer, this is the thinking process I'd follow if I were on your shoes:
1) PX5 is a standard board/HW. All units are the same. What is not (always) the same is the modifications each provider makes to the underlying Android OS to be able to control the MTC-D from Android... although there is a lot of overlapping and compatibility among providers.
2) The fact that you were not able to see on the "Pumpking-Flavor" of Android-UI the Bluetooth module used by your motherboard, points to some level of incompatibility there... but that incompatibility would be between Android-flavor and the micro-controller of your motherboard, not between PX5 and your motherboard (because all PX-5 are the same, HW-wise)
3) I'd try to define who was the manufacturer of the motherboard/main unit and flash on the PX5 an Android version provided by them and a Firmware version provided by them. Meaning, your unit won't be a Pumpkin anymore. It will become back whatever it was before changing the PX-5, but with a new PX-5
If you are not sure who was the original manufacturer, try with Hal9K ROM or Malaysk. But DO NOT change the Android version you have now... let's focus on a problem at a time
My gut-feeling is that your MTCD/E microcontroller is expecting a specific code to instruct the BCM chip (the audio processor, which selects input audio to be played) to connect the PX-5 Audio to the Output... but the App running on the PX-5 which is in charge to talk with the micro-controller is sending some other code, because it expects to be talking to a different board.
While somebody could counter-argue "why only the sound is not working, if the motherboard is not compatible", I'd say that maybe the Android-SW is expecting the motherboard to have a DSP while it doesn't have one (or the other way around), so it COULD be that everything works except the audio...
Is either that, or some physical failure... Do you know why the original PX-5 failed?

Thank you for valuable information. The USB handling system (GL850G) burnt in the processor of the processor module, but after replacing it, nothing changed. There is still a short circuit in the module that I have not located. As for the rest of your information, I have to analyze it for a while because I do not have much experience in software modification. regards

bogsie said:
Thank you for valuable information. The USB handling system (GL850G) burnt in the processor of the processor module, but after replacing it, nothing changed. There is still a short circuit in the module that I have not located. As for the rest of your information, I have to analyze it for a while because I do not have much experience in software modification. regards
Click to expand...
Click to collapse
What I was able to check. The sound from the multimedia certainly reaches the BU32107EFV sound processor - there is an analog signal at the processor's input, but the sound does not come out of it. I admit that I have no experience in programming - I only managed to update the MCU to the CSN2-D-1152020_114103 version - I understand that this applies to this processor module? So how do you find the right motherboard firmware? I am also asking for tips on how to install it. regards

bogsie said:
I admit that I have no experience in programming - I only managed to update the MCU to the CSN2-D-1152020_114103 version - I understand that this applies to this processor module? So how do you find the right motherboard firmware? I am also asking for tips on how to install it. regards
Click to expand...
Click to collapse
Not MTCD, requested a moderator moves to [Android Head-units] forum.
This and other questions have been written about almost daily.
Note that the replies about "MTCD" do not apply.

Then please give me a link to solve this problem, because I am not English-speaking and it is difficult for me to navigate the forum here. regards