Hello All
TlDr; Has anybody replaced a PX5 (Rev 4, the ones with "fewer pins") with a PX6 (4 more pins) on their units? Which "Pins" you left unconnected, the 4 on the left or the 4 on the right? (@marchnz have you done this by chance?)
My old PX5 unit (Flash memory on core board) died and I am in the process of looking for a new unit. But I was thinking on "resurrecting" the old one for my dad's car or some other project, and got a used PX6 module. Problem is, seems my unit was older than what I thought, as the number of pins on the PX5-Rev 4 is lower than the PX6 (and "newer" PX5)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I saw another post claiming that those modules are compatible anyway, so I checked the schematics of a similar unit and found that 5v VCC is provided in the pins 1 & 2 (the ones on the left, looking at the module from the top) while most of the last pins (7x) are either ground or WiFi related (and my MTC-D has an external WiFi/BT module)
But when trying to mount it, the screws work PERFECTLY if I leave the first 4 pins unconnected. And looking for a PX5 module in eBay I found one that seems to be the "transitional revision" that has 4 more pins but are left out of the connector...and those are on the left !!!
I am at lost at what to do here. Does anybody has the pinout / schematics of the core boards itself? (either PX5 or PX6). Has anybody faced this isue before?
Thanks !!!
Max
I saw another post claiming that those modules are compatible anyway, so I checked the schematics of a similar unit and found that 5v VCC is provided in the pins 1 & 2 (the ones on the left, looking at the module from the top) while most of the last pins (7x) are either ground or WiFi related (and my MTC-D has an external WiFi/BT module)
Regards: Pubg Name Generator
Well, I decided to take the risk, and indeed the schematics that are available are at least "confusing" (if not plainly wrong) as they show up a connector numbered with 76 pins (as if it were a real 76 pin connector) but the number of physical pins in the diagram is only 72 (you won't realize that if you do not really pay attention). So, old MCUs and old PX5 boards have VCC on pins 1 & 2 (left, looking at the top)
NEWER (76-pins based MCUs & PX5/PX6) have VCC on pins 5 & 6... meaning the FIRST 4 pins are either unused (or maybe used for features only available on MTC-E MCUs and PX6). So, the photo above is correct, when you are using a 76 pin PX5/6 on a 72-PIN MCU the first 4 pins are lef unconnected/floating and VCC is actually Pin 5 of the longer board.
I tested it and everything works (audio, video, wifi, touchscreen...)
Hope this helps somebody in the future
maxiauer said:
Well, I decided to take the risk, and indeed the schematics that are available are at least "confusing" (if not plainly wrong) as they show up a connector numbered with 76 pins (as if it were a real 76 pin connector) but the number of physical pins in the diagram is only 72 (you won't realize that if you do not really pay attention). So, old MCUs and old PX5 boards have VCC on pins 1 & 2 (left, looking at the top)
NEWER (76-pins based MCUs & PX5/PX6) have VCC on pins 5 & 6... meaning the FIRST 4 pins are either unused (or maybe used for features only available on MTC-E MCUs and PX6). So, the photo above is correct, when you are using a 76 pin PX5/6 on a 72-PIN MCU the first 4 pins are lef unconnected/floating and VCC is actually Pin 5 of the longer board.
I tested it and everything works (audio, video, wifi, touchscreen...)
Hope this helps somebody in the future
Click to expand...
Click to collapse
These four pins are DSP (digital signal processor allowing advanced sound adjustment and enhancement). Nothing happens if they are not involved. You did a good job. The most common problem when replacing the board is non-functioning Bluetooth, the BT module must be replaced, but that is not your problem.
Just a little info. If you have a PX6 board. HCT-RK3399-REV12 with android 11, so they started putting the U-blox MAX-M10S (W10050-KB) gps chip on it, it doesn't show any satellites on android 10, just to clarify, if you wanted to downgrade to, android 10, for example on Hal9k mod 5.
Related
UPDATE: November 8, 2014
* JTAG is disabled by QFuse.
* UART is available via the headphone jack for debugging/etc (Pinout to be posted later w/ examples)
* Searching for ways to access VSSQ and VSS (all other eMMC pins are accessible otherwise).
* New photos detailing locations of pins have been uploaded.
Current Located eMMC Pinouts:
CMD, DAT 0 to 7, VDDI, VDD, and VCCQ
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Notes:
* VCCQ is is attached to 1.8V going to GND and an AGND connection going through two capacitors; one is 4.7u while the other is 0.1u.
* VCC is attached to 2.95V GRND with the same 2 capacitors leading to AGND.
* All DAT pins have 47K resistors leading to 1.8V GND.
* The CMD pin has a 10K resistor leading to 1.8V GND.
CLK
I'm currently searching how to access VSS and VSSQ.
As far as I know jtag ports are disabled on most msm8974 soc phone in the qfuse table. That is why dont find any jtag solution for LG G2 after 13 months of its release or for any other msm8974 phones. Try to find the pins for the emmc to get direct access to it then we can mount it to the pc as an external hdd or flashsdrive.
So I have found the pins for the eMMC chip, and nicely enough they are located below the eMMC module itself. However, it is under the lid, so access requires you to desolder the lid from around it.
One thing I noticed with JTAG is that there is a *WATCH_DOG ENABLE* function that is activated by applying a 22K resistor to on of the leads (might be a different value, not at home so I don't have the PCB layout handy).
I also noticed that applying a resistor to one of the GPIO pins will trigger "FORCED_USB_BOOT", which may be handy for loading a bootloader from USB for eMMC partitioning via fastboot/etc. Haven't done enough research on that to give a definitive answer though.
Came across some more information.
Apparently, the Nexus 5 (both the D820 and D821), have four different boot configurations. Boot0, the one that is disabled altogether by default, can be activated via adding a 22K resistor to pad R3025 (attached to pin BF20 on the MSM8974). By adding this 22K resistor, we should be able to use Boot Config "0" and at the same time enable hardware Watchdog which makes me assume this is a debug mode for the Nexus 5 (and hopefully this might enable the JTAG pins). Will update as I come across more information.
Sorry, but I just want to butt in a let you guys know that there are users on here that still appreciate your dedication and curiosity to Android. This is why I love Android.
Carry on, definitely following this thread.
-------------------------------------------------------------------------
[ DEVICE : N5 ] [ ROM : L DEV PREVIEW ] [ KERNEL : ELEMENTALX ]
Thanks for the support, dEris!
So after digging around some more, the four boot configurations and Watchdog enabling GPIO pins are standard on all of the MSM8974 SOCs. The info I posted apples to both the LG G2 and Nexus 5. The MSM8974 has these GPIO pins standard across, from what I can tell, all boards. If that is correct, backing up the eMMC might be far simpler than I originally thought.
Just keep in mind that I am making a lot of assumptions here. I do not have the hardware to test this myself with, and until I do this is all speculation.
Alright, I've edited some photos to show all of the eMMC's pins on the PCB. One thing I'd like to note that the eMMC CLK pin is located on the other side of the board by the MSM8974 instead of near the eMMC chip itself.
Here are the photos:
Using these diagrams we should be able to connect directly to the eMMC chip.
Derragon said:
Alright, I've edited some photos to show all of the eMMC's pins on the PCB. One thing I'd like to note that the eMMC CLK pin is located on the other side of the board by the MSM8974 instead of near the eMMC chip itself.
Here are the photos:
View attachment 3004913
View attachment 3004912
Using these diagrams we should be able to connect directly to the eMMC chip.
Click to expand...
Click to collapse
So it is not required to find Vcc, Vss, VccQ and VssQ connections?
Sorry, I am pretty new to all of this, so thanks for the info on the other pins that I need to find. Will post a diagram of where VCC, VCCQ and GND are when I get back from work. Sorry for not posting those ones!
Derragon said:
Sorry, I am pretty new to all of this, so thanks for the info on the other pins that I need to find. Will post a diagram of where VCC, VCCQ and GND are when I get back from work. Sorry for not posting those ones!
Click to expand...
Click to collapse
My Nexus 5 refuses to power-on and I'm fairly interested in recovering all the data stored on the eMMC chip. This thread is helping out and it would be awesome to have the location of the various power pins. By the way, how did you manage to get all this information? Thanks anyway for the work you've done.
Hey is VSS and VSSQ the same thing as Ground?
heyho,
i've bougth a official supported dab+ usb staff antenna for my radio.
after starting the stock dab+ app it says: connecting... now im plugging in the usb antenna it the app is ready (so far it seems the antenna is working).
but now, on the top left there is a signal bar with no green bars.
i've already tried some postions in my car (see photo ) and some other locations which are marked online as very good dab+ area but still no f*** signal.
i've already contacted the erisin support, they want me to send the unit back from china to europa (i have to pay for shipping, hahah...) and they will check the device... realy!?...
MTCD KGL 1.92a_2
Youre sure it's a dab+ antenna ? For me it looks like a dvb-t external antenna.
danielloe said:
heyho,
i've bougth a official supported dab+ usb staff antenna for my radio.
after starting the stock dab+ app it says: connecting... now im plugging in the usb antenna it the app is ready (so far it seems the antenna is working).
but now, on the top left there is a signal bar with no green bars.
i've already tried some postions in my car (see photo ) and some other locations which are marked online as very good dab+ area but still no f*** signal.
i've already contacted the erisin support, they want me to send the unit back from china to europa (i have to pay for shipping, hahah...) and they will check the device... realy!?...


MTCD KGL 1.92a_2
Click to expand...
Click to collapse
Same Problem here.
I have the second unit and still the same problem.
I installed the Antenna as discribed in the manual, but it doesn't work.
Erisin said they tested all products bevor shipping, it must be an installation error from my side...
Hi all,
I have the same DAB+ box. It is not only an antenna. For me it looks like a complete receiver box for DAB+. It has to be installed before starting the app. Maybe before booting the head unit. I'm not 100% sure. But not afterwards.
BTW: I'm not happy with this tool. Fo me it doesn't make any sense to have a receiver box with a fixed connected antenna with a magnetic socket. How will you install this in a car? A connection for a separate car antenna would be much more better.
Kind regards
Ricki2411
Ricki2411 said:
Hi all,
I have the same DAB+ box. It is not only an antenna. For me it looks like a complete receiver box for DAB+. It has to be installed before starting the app. Maybe before booting the head unit. I'm not 100% sure. But not afterwards.
BTW: I'm not happy with this tool. Fo me it doesn't make any sense to have a receiver box with a fixed connected antenna with a magnetic socket. How will you install this in a car? A connection for a separate car antenna would be much more better.
Kind regards
Ricki2411
Click to expand...
Click to collapse
i already installed the antenna fix into my car. still no signal etc.
I have the same problem on two units.
- Erisin ES4046B with RK3188 and Android 5.1.1
- Erisin ES6046B with PX5 and Android 6.0.1
The application works, so the DAB + key is recognized but does not pick up the signal.
Does anyone have a solution to this problem?
Thank you.
im currently out of this issue.. i have sold my antenna..
i will order a 3rd party antenna with android driver.
I will post my feedback later this month
danielloe said:
im currently out of this issue.. i have sold my antenna..
i will order a 3rd party antenna with android driver.
I will post my feedback later this month
Click to expand...
Click to collapse
what type of dab+ adapter are you using?
I have a 3rd party window antenna but that's no party either. The signal is lost many many many times
Verstuurd vanaf mijn Z2 Pro met Tapatalk
---------- Post added at 02:44 PM ---------- Previous post was at 02:37 PM ----------
I have this one (my second one of the same type and model, I shipped the first one back, that had even worse reception)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Verstuurd vanaf mijn Z2 Pro met Tapatalk
danielloe said:
heyho,
i've bougth a official supported dab+ usb staff antenna for my radio.
after starting the stock dab+ app it says: connecting... now im plugging in the usb antenna it the app is ready (so far it seems the antenna is working).
but now, on the top left there is a signal bar with no green bars.
i've already tried some postions in my car (see photo ) and some other locations which are marked online as very good dab+ area but still no f*** signal.
i've already contacted the erisin support, they want me to send the unit back from china to europa (i have to pay for shipping, hahah...) and they will check the device... realy!?...
MTCD KGL 1.92a_2
Click to expand...
Click to collapse
What are good areas for the antenna?
Verstuurd vanaf mijn Z2 Pro met Tapatalk
Hello
I recently update my Dasaita PX3 unit with Witson PX5 core board and Android 9 Hal9k firmware. MTCD is 3.71d. USB porst are not working and I see sporadic resets. USB reset after startup is enabled, temp outside 5 celcius. Please help!
I see 4 less pin on Wiston coreboard header than in PX3. Is it problem?
I noticed that 4 unpopulated pin should not be an issue - PX5 is wider than PX3 board, soldered connector on both board have the same size.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What checks / tests have been done
On PX3 I used all USB, the same devices are not discovered after switch to PX5.
USB Host Controller app discover only wifi device, no hub or other devices.
USB devices are also not working in recovery (both android 8 and android 9 recovery - mount usb is not working)
I noticed that 4 unpopulated pin should not be an issue - PX5 is wider than PX3 board, soldered connector on both board have the same size.
I also noticed that android resets usually when more demanding task are executed. I see more reset with high brightness than with low -> I'm wondering if internal PSU can deliver enough power for PX5 board.
On PX3 I already noticed brightness fluctuation. It was not an issue for last 2 years. I thought it bad filtering of engine coil/injector
khorh said:
On PX3 I used all USB, the same devices are not discovered after switch to PX5.
Click to expand...
Click to collapse
Hi, maybe it's not your problem, but does the board fit well in the pins? For the board to work well, I had to remove the heat sink screw, collided with mother on the board. I have isudar px3 android 7.12, 2 GB RAM. MTCE_GS_V3.67. I bought a Witson px5 4 GB RAM board for Android 10. Unfortunately, Bluetooth does not work. I have a BT A5BC6 module and WQ_BC6 in the factory settings. Otherwise, everything works fine. What I read may not work wifi, bluetooth and USB. Does your bluetooth and wifi work?
I have MD725 v1. It works correctly. Wifi also work correctly.
I removed one screw from PX5 which conflicts with soldered thread on main board, I removed also rest of glue
to not prevent tight fit. I drilled heatsink to add 3rd screw and add additional heatsink on top of it:
PX5 is taken from following board. It seems to have one usb (direct connection instead of hub?).
Do you know which PINs are for USB? I can check resistance, at worst case I can even solder PX5 to mainboard but prefer not.
Nice. I only added an anodized heatsink and the temperature dropped by 8°C. I will attach the fan to the top cover. I don't know where it is on the USB board. If the SD card works, I would probably leave it at that. Maybe they would advise on 4pda.ru, but only in Russian. I use a translator.
Аппаратное обеспечение ГУ Microntek (RockChip PX3/PX5/PX6/PX30 Android 5/6/7/8/9) - 4PDA
Аппаратное обеспечение ГУ Microntek (RockChip PX3/PX5/PX6/PX30 Android 5/6/7/8/9), [Головное устройство][Автомагнитола][Android]
4pda.ru
Check second USB Data line D+/- continuity. Use schematic found in hardware section or my signature.
Yup, issue with connector confirmed. I measured from plugged PX5 to U27 chip ARM DP and ARM DM lines, one did not work.
Now I have only resets with high brightness and screen flickering. Seems like MTCD issue https://forum.xda-developers.com/t/...asaita-max10-px6-4gb-64gb-android-10.4140875/
Do you think adding cap to TFT+5V may help? For me it seems like voltage drop which lead to cpu reset
Do you also see dependency between TFT+5V (4.2v in datasheet) and brightness? I see 3,86 with medium brightness,
Hello!
Hopefully someone can help me here.
I installed the NaviFly 7862 in my Rio 2013, and all works fine EXCEPT the steering wheel control.
As far as I know, I dont have a CAN decoder in my car. But whatever I try I cant get the steering wheel controls to work.
I might just be stupid as hell and missed something though.
Excessed said:
Hello!
Hopefully someone can help me here.
I installed the NaviFly 7862 in my Rio 2013, and all works fine EXCEPT the steering wheel control.
As far as I know, I dont have a CAN decoder in my car. But whatever I try I cant get the steering wheel controls to work.
I might just be stupid as hell and missed something though.
Click to expand...
Click to collapse
Did you connect the "key" and "Can Out" cables together?
Midway down the page they discuss and show picture
Tips
www.joyingauto.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Emg24538 said:
Did you connect the "key" and "Can Out" cables together?
Midway down the page they discuss and show picture
Tips
www.joyingauto.com
View attachment 5420119
Click to expand...
Click to collapse
I dont have these cables on the unit
S
Excessed said:
I dont have these cables on the unit
Click to expand...
Click to collapse
Sorry my mistake.
It doesn't look like your car uses canbus for swc, and doesn't have canbus wires in the radio harness.
What does the navifly harness have connected to key1?
Kia Rio (2011-2017) MP3/CD Head Unit pinout diagram @ pinoutguide.com
Looks like it should be B4. Then you can map the buttons in the app.
B4Steering Wheel Remote ControlSteering Wheel switch pushed0.5V ~ 3V
https://www.aliexpress.com/item/1005002291499893.html
Assuming that's what you've bought, I wish they had a more detailed picture of the harness.
If B4 is unpopulated, maybe there's a stray/improper connection instead that you can borrow the lead from?
And from the listing:
main harness pinout showing location of key1 if your harness is unlabeled
ziddey said:
It doesn't look like your car uses canbus for swc, and doesn't have canbus wires in the radio harness.
What does the navifly harness have connected to key1?
Kia Rio (2011-2017) MP3/CD Head Unit pinout diagram @ pinoutguide.com
Looks like it should be B4. Then you can map the buttons in the app.
B4Steering Wheel Remote ControlSteering Wheel switch pushed0.5V ~ 3V
https://www.aliexpress.com/item/1005002291499893.html
Assuming that's what you've bought, I wish they had a more detailed picture of the harness.
If B4 is unpopulated, maybe there's a stray/improper connection instead that you can borrow the lead from?
And from the listing:
main harness pinout showing location of key1 if your harness is unlabeled
Click to expand...
Click to collapse
Thanks for the reply, it is indeed this unit. Just different front.
I've made better pictures of the harness;
That would mean that KEY1 (Black) is connected to Ground.
Ground is spliced to b5. Which, according to the pinout is empty.
ok.. what's your b4 connected to? It looks like b4 is the brown wire, and you've got a black wire for b17 (swc ground).
looks like the navifly listing picture is very incorrect as far as main harness pinout. See this post instead: https://4pda.to/forum/index.php?showtopic=1000996&st=100#entry100193155
Even just comparing the color coding, it looks like navifly screwed up and reversed #7-ant cont and #8-key1.
If so, use a paper clip, thumbtack, pushpin, whatever to release the pin and swap them around. Might as well inspect the rest of the pinning..
Following that blue wire to the car end, it lines up properly with A18 remote power supply for antenna..
Hopefully no damage was done as a result
ziddey said:
ok.. what's your b4 connected to? It looks like b4 is the brown wire, and you've got a black wire for b17 (swc ground).
looks like the navifly listing picture is very incorrect as far as main harness pinout. See this post instead: https://4pda.to/forum/index.php?showtopic=1000996&st=100#entry100193155
Even just comparing the color coding, it looks like navifly screwed up and reversed #7-ant cont and #8-key1.
If so, use a paper clip, thumbtack, pushpin, whatever to release the pin and swap them around. Might as well inspect the rest of the pinning..
Following that blue wire to the car end, it lines up properly with A18 remote power supply for antenna..
Hopefully no damage was done as a result
Click to expand...
Click to collapse
It indeed looks as of the blue and brown wire are swapped.
I also found the reason why I couldnt figure it out.
This is the image they provided for the pins;
They casually switched KEY1 and KEY2 with Battery GND and Battery 12v...
Gonna try and switch out the two cables later (Ant and Key1)
My Diagram for most android head unit , Key1 is #7
sometime brown or pink depend on headunit model
Paragon Super said:
My Diagram for most android head unit , Key1 is #7
sometime brown or pink depend on headunit model
View attachment 5422815
Click to expand...
Click to collapse
Thanks a lot, only your diagram is different than the other one. Now im even more in doubt xD Now the problem is that B4 in my car is unpopulated.. So I have no clue as how to connect my steering wheel controls now.
So I'm going to try that later. Hopefully it works.
EDIT: I think I found it. Navifly, and almost all online sources, have the diagram for mp3/radio. My old head unit was a nav screen and has the steering wheel controls at b5 in stead of 4.
I fixed it by moving B4 on the car side to B5. Steering wheel works properly now.
Thanks a lot for the help!
Excessed said:
I fixed it by moving B4 on the car side to B5. Steering wheel works properly now.
Thanks a lot for the help!
Click to expand...
Click to collapse
Hi, I just want to say thanks!. My kia 2021 connection was 99'9% as yours, and this post was really helpful!
7q7 said:
Hi, I just want to say thanks!. My kia 2021 connection was 99'9% as yours, and this post was really helpful!
Click to expand...
Click to collapse
Glad to have been of help! Just curious; Is your audio balance correct? My phonecall audio comes from the back of the car. I'm guessing those cables are wrong on the head heading as well. But it's around freezing here, and to cold to sit on my car without heater hehe
Hi everyone,
so i've bought a new android unit for my car. I have been checking the other posts in this forum but they are kind of "pro level" so i felt the need to clarify some doubts. I know you guys are experts, if you can help be i would be thankful. I'll also provide some feedback that maybe can help people who are considering buying it.
The unit i've bought is this one:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Link for it: https://www.aliexpress.com/item/1005003003858975.html?spm=a2g0o.9042311.0.0.27424c4ds0To05
I have a Ford Grand C-Max manufactured 11/2015 (the restyled one), and i thought this radio would be a good fit (i've had other android units in my past cars). I bought the 6G+128GB version (TS6 version), with Android 11. The brand is "Navifly", however i guess this is just another brand variation.
1) Feedback
Positive- Fast and fluid Android experience - no lag to complain about.
- Sound Quality - a great improvement over the Ford Sync 2 original radio - better definition, better bass, supports higher volumes without distortion
- Radio has RDS - it actually shows the station name (we don't have DAB in Portugal, it is still FM) and the tuning quality is good
- GPS is ok. Not awesome, but usable. Supposedly, it also gets some Glonass satellites, but as you know Glonass constellation is sparser, so it usually only gets GPS triangulation. I use Waze, sometimes it takes a bit to understand where it is.
Negative- Quality of design and build of the plastic fairings: the plastic fairings are much lower quality relatively to the Ford ones. They don't precisely fit the car dashboard, by a couple of milimiters. I have it provisionally installed, but i'll have to shave some plastic when i get it definitely installed. Additionaly, the chines fairings don't have the metal clips/retainers that the original plastics have to get it securely in place. I've has to order some to get this sorted out...
- The CANBUS communication:
-> i am not getting any steering wheel communication at all (no volume control, no call pick up. This is the worst part for me
-> the information of the parking sensors is erratic. My car has 6 sensors at the front and 6 at the back (360º coverage) and there is quite an error on the info shown in this android unit, so i am not not trusting it a lot. Besides that, it is slow to react (couple of seconds), and the car should be drawn vertically (you brain needs to rotate the view 90º to get it right).
-> No Park Assist (automated parking) information is shown at the unit, so the Park assist is not currently working
-> I can get reversal signal, climate info (when i change it), and open door information.
- The screen. For its size, its low resolution, not bright enough, and it is very reflective. Not very happy with it.
2) Help RequestI need help to sort the CANBUS limitations. This is the canbus box they sent me:
I guess this box is not the most adequate for my C-Max. I can't read chinese characters so i really don't know what it says at all. I've tried to get into the canbus box definitions in the settings menu and have tried selecting other canbus choices with no avail: i couldn't get steering wheel info at all. So i've went a bit overkill and ordered two canbus boxes to see if a different canbus box solve my issues. I've ordered these two:
- Another Hiworld box (i guess this is a newer version than the one i have, so i hope they have sorted out the issues) https://www.aliexpress.com/item/1005002718903038.html?spm=a2g0o.9042311.0.0.27424c4dac8EZc
- An XP one: https://www.aliexpress.com/item/1005002327630203.html?spm=a2g0o.9042311.0.0.27424c4dac8EZc
So i now have three questions for you guys:
1) Is this a FYT unit? Or a Mekede?
2) Will any of the new boxes sort out my canbus miscommunication?
3) Is there any place where i can get a firmware update? Or canbus firmware update? This is what the Android System settings show about my unit:
Thank you guys in advance for your help!!
I have tried other two canbus boxes from Hiworld and XP, with no avail. Still no steering wheel controls. Any suggestions?
JMourinho said:
I have tried other two canbus boxes from Hiworld and XP, with no avail. Still no steering wheel controls. Any suggestions?
Click to expand...
Click to collapse
What does reseller suggest when contacted for support.
JMourinho said:
So i now have three questions for you guys:
1) Is this a FYT unit? Or a Mekede?
2) Will any of the new boxes sort out my canbus miscommunication?
3) Is there any place where i can get a firmware update? Or canbus firmware update? This is what the Android System settings show about my unit:
Click to expand...
Click to collapse
Hi,
1) Mekede = FYT, not every FYT is a Mekede. But your unit is a Topways built unit sold by reseller TopNavi, so neither a Mekede nor a FYT nor a NaviFly. You are in the wrong sub-forum. Please ask in the general Android Head Units subforum
2) Ask your reseller TopNavi.
3) Please ask your TopNavi reseller or in the general Android Head Units subforum. There your will find the TSx series with firmwares and other information.
And by the way: It is a fake Android 11. It is still Android 10 (Api/SDK 29) as displayed on the web page. One can write a script that will set the "Android level" to any version you like: Android 10, 11, 31, 451, 10961, 4, ..
But it is a nice looking unit compared with the standard Ford units.
EDIT: This seems to be a FYT after all. Sorry for the confusion.
In my signature you find on the 3rd line the "HWGetInfo.apk". Please run it and share the created zip file.