• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

General Medeke/Navifly 7862

Search This thread

MasK

Senior Member
May 15, 2005
1,266
129
Singapore
www.imraneo.com
Can you identify which pin on the canbus decoder is connected to the reverse wire? Seems like that might be redundant?

The only repo I've found has been in this massive russian thread: https://4pda.to/forum/index.php?showtopic=1000996&st=5000

Seemingly only modified firmware (not sure what's been modified) or factory 360. I did come across a June navifly stock firmware buried in the thread and updated my unit with it. Not easy to search the thread for me since it's in russian, but it's where the bulk of the info is.

edit: you've played with the factory settings, toggling off all the 360 ones? seems like it's being actively discussed in that thread right now
OK... I solved it!

I saw my old Dasaita PX5 "reverse cont" wire connected to pinX on the canbus connector AND the power connector. (I think its Pin8 as u shared above)
Canbus connector on the new Mekede is also the same (standard), so I followed that pin to the power connector. I cut that wire, and connected it to my cam out. Thats it!
Now.. this reverse wire is in pin 3. The pin location on Mekede/Navifly description is pin 2. Its all wrong. lol

Anyways, I still don't know what the "cam12V" does. Probably for different car configurations. In the process, I even cut the VCC and headlight sensor too.
But all is good now and I thank you for proving me with the wealth of info and thoughts!
 

silviox

Member
Jun 17, 2009
20
1
47
Milan
OK... I solved it!

I saw my old Dasaita PX5 "reverse cont" wire connected to pinX on the canbus connector AND the power connector. (I think its Pin8 as u shared above)
Canbus connector on the new Mekede is also the same (standard), so I followed that pin to the power connector. I cut that wire, and connected it to my cam out. Thats it!
Now.. this reverse wire is in pin 3. The pin location on Mekede/Navifly description is pin 2. Its all wrong. lol

Anyways, I still don't know what the "cam12V" does. Probably for different car configurations. In the process, I even cut the VCC and headlight sensor too.
But all is good now and I thank you for proving me with the wealth of info and thoughts!
Have you some pics of this operation??? Tnx
 

MasK

Senior Member
May 15, 2005
1,266
129
Singapore
www.imraneo.com
Have you some pics of this operation??? Tnx
I have attached the pic of the wire which I cut and also the correct pinout diagram which I got from a friend who got a Mujajndo HU with similar specs. I hope this helps.
 

Attachments

  • HU wiring.jpg
    HU wiring.jpg
    92.2 KB · Views: 88
  • Mekede-HU-rear.jpg
    Mekede-HU-rear.jpg
    714.4 KB · Views: 81
  • Like
Reactions: silviox

surfer63

Senior Member
May 4, 2010
3,738
1,434
Zwolle
hvdwolf.github.io
Are there any APKs from Dasaita/Teyes that we can use on the Mekede?
I prefer the FM radio and music player apps from Dasaita.
Music player: perhaps.
FM radio: No. In all these units the radio is controlled by the MCU having its own firmware. And these MCU firmware is different on FYT models versus MTCD/E units versus TS8/9/10 units (and so on, and so on). The FM radio app on every unit is simply a graphical interface giving commands to and receiving data from the MCU. There is no direct interaction to the FM chip.
Unlike DAB+ apps that directly "talk" to the hardware in the dongle over USB.

But you could mod the lay-out of the FYT apps on the Medeke. ;)
 
  • Like
Reactions: marchnz

silviox

Member
Jun 17, 2009
20
1
47
Milan
I have attached the pic of the wire which I cut and also the correct pinout diagram which I got from a friend who got a Mujajndo HU with similar specs. I hope this helps.
I also connected the third pin to the positive of the cam and it turns on, but it remains fixed ON, even without having engaged the reverse gear. Any advice to fix it? thank you
 
Last edited:

MasK

Senior Member
May 15, 2005
1,266
129
Singapore
www.imraneo.com
It means your cam is supplying constant 12V even without the reverse gear. Did you just install the reverse cam or was it working with your previous headunit?
Generally, reverse cams are connected to the reverse lights, so it will only turn on when you're in reverse.
 

Bob_Sanders

Senior Member
Jul 17, 2019
241
53
Winnipeg
It means your cam is supplying constant 12V even without the reverse gear. Did you just install the reverse cam or was it working with your previous headunit?
Generally, reverse cams are connected to the reverse lights, so it will only turn on when you're in reverse.
Well.... a lot of people (myself included) like to use the cam as a monitor too so it really needs to be connected and powered up all the time. Yesteryear's head units only operated the rear cams in reverse but most of today's units have apps and such to take advantage of the rear cam as a monitor.
Soooo.... If you wish to use the rear cam as a monitor while driving forward then cam POWER must be connected to 12 volts any time the vehicle is running.

I also connected the third pin to the positive of the cam and it turns on, but it remains fixed ON, even without having engaged the reverse gear. Any advice to fix it? thank you
Pin 3 is the TRIGGER which changes the video input from what ever you have the head unit set on, to the reverse input. People kind of get this a bit confused. It's like watching a dvd on your tv... not only does your dvd player need to be plugged in and powered up so it can work, but the tv needs to be set on the DVD input as well.

Just as with the dvd player, the Cam needs power to work, and just as with the tv, the head unit needs to be on the 'rear cam input'. Pin 3 is what does that. When you feed it 12 volts, it automatically switches the head unit to the 'rear cam' input. When you remove that 12 volts the head unit goes back to what ever input it was on before.

You need to supply pin 3 with 12 volts ONLY when in reverse. It should be connected to the +12 volt side of the reverse light. At the same time your cam has to have 12 volts to operate.
 
Last edited:
  • Like
Reactions: silviox

silviox

Member
Jun 17, 2009
20
1
47
Milan
the cam has already been used with another car radio and it worked, so I think the problem is the wiring or the canbus different, something escapes me .... At the moment I have not connected the positive of the cam to the reverse light (on my jeep renegade it's in a complicated place!) but I'm connected directly to the trunk's 12V. Before it went, with this new car radio no.
 

silviox

Member
Jun 17, 2009
20
1
47
Milan
Well.... a lot of people (myself included) like to use the cam as a monitor too so it really needs to be connected and powered up all the time. Yesteryear's head units only operated the rear cams in reverse but most of today's units have apps and such to take advantage of the rear cam as a monitor.
Soooo.... If you wish to use the rear cam as a monitor while driving forward then cam POWER must be connected to 12 volts any time the vehicle is running.


Pin 3 is the TRIGGER which changes the video input from what ever you have the head unit set on, to the reverse input. People kind of get this a bit confused. It's like watching a dvd on your tv... not only does your dvd player need to be plugged in and powered up so it can work, but the tv needs to be set on the DVD input as well.

Just as with the dvd player, the Cam needs power to work, and just as with the tv, the head unit needs to be on the 'rear cam input'. Pin 3 is what does that. When you feed it 12 volts, it automatically switches the head unit to the 'rear cam' input. When you remove that 12 volts the head unit goes back to what ever input it was on before.

You need to supply pin 3 with 12 volts ONLY when in reverse. It should be connected to the +12 volt side of the reverse light. At the same time your cam has to have 12 volts to operate.
ok the trigger, but unfortunately I only have the possibility to see the activated cam WITHOUT the possibility to use the car radio, the navigator or other. I can only see the image behind me and stop, I can't switch to the classic interface :(
 

MasK

Senior Member
May 15, 2005
1,266
129
Singapore
www.imraneo.com
ok the trigger, but unfortunately I only have the possibility to see the activated cam WITHOUT the possibility to use the car radio, the navigator or other. I can only see the image behind me and stop, I can't switch to the classic interface :(
So it looks like you reverse cam is permanently connected to 12V. You'll need to find a 12V/trigger source which only turns on when youre in reverse.
One common method is the reverse lights. You'll have to wire the reverse light to the front into your Headunit, so you can see the cam only when youre in reverse.
Does this make sense?
 

pcmicro

Member
Apr 24, 2018
36
8
I purchased a Joying 7862 10.5 inch head unit, because I read that the Navifly/Mekede ones do not sent the proper low-level line output signals the amplifier(s). I discovered that Joying's firmware does not allow making hands-free phone calls using Google Assistant. When I give the voice command "Hey Google, call mom", it responds with "I'm not able to make calls yet". Has anyone has been able to make this work with the Navify/Mekede head units? I asked some resellers and they said that I can pay $15 more for "Voice software" that will allow Google Assistant to work. Is this true?

I have 2 weeks to return my Joying for a refund, which I'm now considering. I contacted Joying support directly, and they responded that since I bought it on AliExpress I should contact my seller for support. When I asked the seller about the issue, they told me to install a firmware update dated 2021.7.5 to see if that solves it, but the result was the same. I regret spending so much more on a Joying brand and getting bad support.
 

Allan_Hun

Senior Member
Mar 11, 2014
433
123
Gl.Rye
I purchased a Joying 7862 10.5 inch head unit, because I read that the Navifly/Mekede ones do not sent the proper low-level line output signals the amplifier(s). I discovered that Joying's firmware does not allow making hands-free phone calls using Google Assistant. When I give the voice command "Hey Google, call mom", it responds with "I'm not able to make calls yet". Has anyone has been able to make this work with the Navify/Mekede head units? I asked some resellers and they said that I can pay $15 more for "Voice software" that will allow Google Assistant to work. Is this true?

I have 2 weeks to return my Joying for a refund, which I'm now considering. I contacted Joying support directly, and they responded that since I bought it on AliExpress I should contact my seller for support. When I asked the seller about the issue, they told me to install a firmware update dated 2021.7.5 to see if that solves it, but the result was the same. I regret spending so much more on a Joying brand and getting bad support.
Google says "I'm not able to make calls yet" because google believes our headunit is a tablet. If you set minimum width=400 in developer settings google will try to make the call.
On my unit width=400 caused other problems so I immediately returned to stock width.
Regarding the paid voice software: It is not google but an inferior Chinese voice app. It doesn't support my native language so I can't use it for navigation. Voice calls sort of works but I have to pronounce the contact name in english.
 
  • Like
Reactions: MasK and pcmicro

pcmicro

Member
Apr 24, 2018
36
8
Google says "I'm not able to make calls yet" because google believes our headunit is a tablet. If you set minimum width=400 in developer settings google will try to make the call.
On my unit width=400 caused other problems so I immediately returned to stock width.
Regarding the paid voice software: It is not google but an inferior Chinese voice app. It doesn't support my native language so I can't use it for navigation. Voice calls sort of works but I have to pronounce the contact name in english.
Thanks Allan. I gave it a try and the icons and text became annoying large as soon as I changed the width.
When I gave the command "Hey Google, call mom" this time it responded with "Calling Mom, Mobile", but the call was never made. I watched my phone and it was never told to make the call. I also tried typing in the command instead of using the microphone, with the same result. However I can open the Bluetooth app and make a call manually.
 

Allan_Hun

Senior Member
Mar 11, 2014
433
123
Gl.Rye
Thanks Allan. I gave it a try and the icons and text became annoying large as soon as I changed the width.
When I gave the command "Hey Google, call mom" this time it responded with "Calling Mom, Mobile", but the call was never made. I watched my phone and it was never told to make the call. I also tried typing in the command instead of using the microphone, with the same result. However I can open the Bluetooth app and make a call manually.
Have a look at this: https://forum.xda-developers.com/t/...s-from-google-voice-to-joying-bt-app.3685217/

Someone also made a guide on how to make Google voice call on none joying units, but I can't find it now. It basically involved replacing the stock dialer with a modded joying dialer.
 

pcmicro

Member
Apr 24, 2018
36
8
Have a look at this: https://forum.xda-developers.com/t/...s-from-google-voice-to-joying-bt-app.3685217/

Someone also made a guide on how to make Google voice call on none joying units, but I can't find it now. It basically involved replacing the stock dialer with a modded joying dialer.
The "GVC Callhandlert 4 Joying" app did not appear to be compatible with the Joying 7862 firmware. However after doing a factory reset I tried your suggestion again on changing the "Smallest Width" to 400 DPI under Settings > System > Developer options. The first few times I tried to make the call using Google Assistant it failed, but then it prompted me to choose which phone dialer to use, and I selected "BlueTooth", and "Use every time". When I told Assistant to "Call Mom", it displayed a confirmation icon which just says "Call", and I had to touch that before Assistant would dial the number.

Next I tried to set a higher "Smallist Width" DPI value, and I found that it works when I set it to 596 DPI. This resolution looks much better, but the icons are still noticeably bigger then when it is set to 720, so I continued to look for a better solution. I tried disabling the "Developer Options", and this restored the high resolution and allows Google Assistant to make the call! :)

Now the only annoyance is the confirmation button that says "Call" which I must touch with my finger before GA will dial the phone number. I had the same issue with my Dasaita PX6 after I allowed the Play Store to update the Google App (com.google.android.googlequicksearchbox) to a version higher then 11.30.12.29. The Dasaita firmware came with version 10.65.11.21 which is much smaller in size then all later versions (which became larger with each version). I upgraded it to version 11.1.9.29 which I found to also be fast -GA makes the call about 3 seconds after I tell it to call.
In comparison, version 11.30.9.21 took 6 seconds to make the call, and version 11.30..12 took 8 seconds.

I would like to downgrade the Google App on my Joying 7862 to use version 11.1.9.29 but since this is a system app and my Joying is not rooted, I don't know how it can be done. Perhaps the Google App can be replaced with the older one in the Joying firmware. Perhaps someone with more experience such as @surfer63 can tell me how ?
 

surfer63

Senior Member
May 4, 2010
3,738
1,434
Zwolle
hvdwolf.github.io
I would like to downgrade the Google App on my Joying 7862 to use version 11.1.9.29 but since this is a system app and my Joying is not rooted, I don't know how it can be done. Perhaps the Google App can be replaced with the older one in the Joying firmware. Perhaps someone with more experience such as @surfer63 can tell me how ?
Why do you say the Google app is a system app?
As far as I know the Google app is not a standard part of the firmware. And even if it is part of the firmware, it is not a system-signed app as part of the FYT firmware. You can copy it directly over the existing one by flashing it via an lsec script. Note though that if your system has optimized the currently installed app (if it was in the firmware that is), you need to replace those odex and vdex files as well (under application folder in /oat/arm64). Edit: You can also simply remove them and the new app will place its opmitized vdex and odex files in /data in the program folders.
And if it was never part of the firmware you can simply uninstall it. Go into the Google Play Store app and set update to manual. Copy the 11.1.9.29 on a usb-stick and install it from there by double-clicking it (possibly you get a question if it is allowed to install from that file manager). Then go into the play store again and set update to automatic again, but set the Google app immedately to manual update to have it not updated automatically. That's how I did it with CWG when a number of versions contained a bug that "bugged" me. When solved, I set it to automatic update again. Which in your case would not be advisable.
 
Last edited:

silviox

Member
Jun 17, 2009
20
1
47
Milan
Problem: Jeep Renegade / Mekede M300. I use and configure the SIMPLESOFT canbus, put the reverse gear and start the camera. OK. I change canbus (Raise), I configure (parking sensors ok, steering wheel buttons ok), I put the reverse gear and nothing, nothing happens. Suggestions ? I want to use the RAISE because it also contains the parking sensor speaker, the SIMPLESOFT, it has no internal speaker.
 

marchnz

Senior Member
Nov 26, 2012
3,750
752
wombleton
From MTCD, to FYT - moving to the dark side :)

I brought two M600 units (fyt = 116 Mekede) received a couple of days ago.

As part of the sale, the reseller sent me 'upgrade' Android 11 files.

These turned out to be nothing less than a prop script, which set build type =11 - switching on fake Android 11.

Initial thoughts.
While I am yet to install in the vehicle's, the devices themselves are much better looking, better/brighter displays and faster than the PX5 MTCD devices I have been hardware developing.

They're also more resilient to messing around with image files and alot easier to recover.

Device configurations and customisations such as volume dependant speed, a real equalizer multiple launchers make for a much better experience so far. Hoping the Audio side is just as good.

Will post back.
 
  • Like
Reactions: surfer63

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    From MTCD, to FYT - moving to the dark side :)

    I brought two M600 units (fyt = 116 Mekede) received a couple of days ago.

    As part of the sale, the reseller sent me 'upgrade' Android 11 files.

    These turned out to be nothing less than a prop script, which set build type =11 - switching on fake Android 11.

    Initial thoughts.
    While I am yet to install in the vehicle's, the devices themselves are much better looking, better/brighter displays and faster than the PX5 MTCD devices I have been hardware developing.

    They're also more resilient to messing around with image files and alot easier to recover.

    Device configurations and customisations such as volume dependant speed, a real equalizer multiple launchers make for a much better experience so far. Hoping the Audio side is just as good.

    Will post back.
    1
    What does the reseller suggest when contacted for support.
    Seller has not answered me. I did however solve my problem. There was one more canbus box setting for Mazda 6 that I did not try last time for some reason and now the steering wheel controls work. Car clock is now stuck in 12 hour mode though which is shame, but other than that it works fine.

    One of my speakers however sounds very bad now so I might have to tear the unit out and fiddle with the wires. Radio signal is also worse than with the original radio.
    1
    Radio signal is also worse than with the original radio.
    Does your car have an amplified antenna? If not: Did your unit came with an antenna amplifier?
  • 2
    I purchased a Joying 7862 10.5 inch head unit, because I read that the Navifly/Mekede ones do not sent the proper low-level line output signals the amplifier(s). I discovered that Joying's firmware does not allow making hands-free phone calls using Google Assistant. When I give the voice command "Hey Google, call mom", it responds with "I'm not able to make calls yet". Has anyone has been able to make this work with the Navify/Mekede head units? I asked some resellers and they said that I can pay $15 more for "Voice software" that will allow Google Assistant to work. Is this true?

    I have 2 weeks to return my Joying for a refund, which I'm now considering. I contacted Joying support directly, and they responded that since I bought it on AliExpress I should contact my seller for support. When I asked the seller about the issue, they told me to install a firmware update dated 2021.7.5 to see if that solves it, but the result was the same. I regret spending so much more on a Joying brand and getting bad support.
    Google says "I'm not able to make calls yet" because google believes our headunit is a tablet. If you set minimum width=400 in developer settings google will try to make the call.
    On my unit width=400 caused other problems so I immediately returned to stock width.
    Regarding the paid voice software: It is not google but an inferior Chinese voice app. It doesn't support my native language so I can't use it for navigation. Voice calls sort of works but I have to pronounce the contact name in english.
    1
    My new Navifly 7862 FYT unit was installed in my car yesterday. My mcu FYT is same as yours (except date 19.11.2020) .
    Great sound (linked in optical to my DSP) , great QLED Panel and great superfaster GPS connection. I'm very very satisfied about this radio except 2 things:

    - the launcher is very bad (similar to Android 9 launcher of MTCE units). I can't understand why the launcher after boot show ever sound settings panel (i need ever to tap "home" icon). Is possible to change this launcher?
    - I can't find how to silence tap sound

    thanks for help
    In the settings (it might be in the factory settings. Use pin 3368 for the factory settings access) there is an option to launch Navi software but you can actually choose any app to launch on start up. Find that setting and change whatever is launching to something else and test the result. Then report back.

    It is possible to change the launcher in the factory settings (again, I think it is located in factory settings). There are 5 or 6 options of default launcher. I choose not to use any of them and simply choose the Microsoft Launcher. But there are other car specific launchers that you can download. You can use any launcher that you like using on your phone, too.

    Silence for tapping screen is in the settings somewhere. I might have gone into the Pure Android settings to turn it off. I really can't remember any more.

    In Microsoft Launcher, there is a link to open the pure Android settings. There are other more complex ways to get there, though.

    Also make sure you switch on the setting that allows the radio to go into sleep mode or you might find yourself with a flat battery one day.
    1
    Can you disable it in the Factory Settings? I recall some settings / options regarding the rear camera. Factory pin is 3368
    1
    Does anyone know how to disable the reversing camera? I do not have a camera nor will I install it.

    when I put the gear in reverse, the screen goes black and the music cuts out.
    On most FYT models you have to cut/disconnect one of the wires. It should be in the installation instructions.
    1
    Radio signal is also worse than with the original radio.
    Does your car have an amplified antenna? If not: Did your unit came with an antenna amplifier?