yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] ciris:
Check your PM
[FYT Android Head Units] abd alaa:
Is there a way to turn off some usb ports when the car is switched off
[FYT Android Head Units] gordgelin:
no need to do this since they all switched off anyway when device is off/sleeping
[FYT Android Head Units] abd alaa:
I have a USB hub with an LED and after turning off the car, I can see that the LED is still on.
[FYT Android Head Units] gordgelin:
just wait about 3-5 min....
[FYT Android Head Units] abd alaa:
W

Will try again today.
[FYT Android Head Units] abd alaa:
Worked, thanks.

One more question please, is there a way to disable the auto-start Apps, such as the 360 camera and other Apps ?
[FYT Android Head Units] Trayal:
Just a heads-up/warning... as of a couple weeks ago, my m700s just spontaneously started to destroy every USB drive plugged into it. I lost $300 worth of USB hardware before I finally figured out what was going on. Proceed with caution on these cheaply developed and manufactured Chinese units.
[FYT Android Head Units] sly2:
I also have the M700S and after 2 days the USB ports have gone. Fortunately, no USB devices are broken. But without USB this unit is only half because I have DAB+ and DVR connected there...

As I see these units have problems with the internal USB hub...
[FYT Android Head Units] emzobg:
I have the following problem:

Mekede m500s

Speaker output is messed.

Front left speaker corresponds to Front Right

Front right - Rear Left

Rear left - Front Left

Only Rear right is rear right.

I've cut and soldered the wires of the harness and ..... the result is the same :eek:
[FYT Android Head Units] j0hn83:
Which wires did you cut?

There's a couple ways the car can receive audio from the head unit.

Here's the pin out for the power port (G).

If you already tried changing those then let us know and we'll talk you through the next thing to try.
[FYT Android Head Units] emzobg:
Yep. exactly those wires.

And no difference, which is weird.
[FYT Android Head Units] xdsbx:
hi, i have the last firmware update for m300s june 2023 here is the Link to download on my Mega
[FYT Android Head Units] surfer63:
I hope it is the latest, and not the last :)

Thanks.

Application layer date is "2023-07-13"

kernel date is "Tue May 23"
[FYT Android Head Units] xdsbx:
Yes. I hope it too.
[FYT Android Head Units] nurex:
So, after a restart of the FYT device, all USB no longer work. This is a new device where everything is original except system UI and launcher... This is already the 2nd device which has no USB function after a few days. That can't be

Mekede M700S
[FYT Android Head Units] sly2:
I got my new unit 2 days ago and I think, it was my DAB+ Dongle. Now I have my second unit at home and test it, make it with all updates and until now all is working well, USB too...

I hope, that's really only a software fault...
[FYT Android Head Units] nurex:
After a restart, the USB ports go back and when it goes into standby and I then turn on the ignition from the car again, then the USB ports no longer work. I also have a DAB+ dongle on it
[FYT Android Head Units] sly2:
check it without the dongle...
[FYT Android Head Units] nurex:
I just tested, it's not because of the dongle.... Sometimes the USB goes after a reboot and sometimes it doesn't. I don't understand it... It's already the second new M700S
[FYT Android Head Units] j0hn83:
Do you have anything else connected via USB?

Did Mekede also send you new USB cables or just a new head unit?

I've only ever seen 2 posts where the USB ports have stopped working and 1 of those posts was yours.

The chances of this happening to you on 2 units in a row are extremely slim and to me this suggests the possibility of some kind of accessory misbehaving.
[FYT Android Head Units] sly2:
I soldered an USB socket directly to the board, before the hub without any success...
[FYT Android Head Units] nurex:
I only have TPMS, DAB+ and a USB stick connected. But even if I unplug everything and only connect a USB stick, it doesn't work. Mekede has also sent new USB cables
[FYT Android Head Units] nurex:
did you happen to have a DSP plugged in?

I had a Hizpo S8 and there was the same problem when I connected a Helix DSP.

When I had made the settings with the laptop in the DSP, the left and right output had been reversed.

After restarting the head unit, it was back to normal. I had this phenomenon with Digital Out (coaxial and optical) and RCA
[FYT Android Head Units] nurex:
In the meantime I haven't connected anything to the USB ports, just a USB stick with music. When it boots from sleep mode, the USB ports are as if disabled and sometimes after a reboot the USB ports go again, but rarely.

Now I have switched to USB 1.0 in the settings and after the automatic restart the USB ports are active again.

If I drive away with the car, then I see if they are still there after the sleep mode.

I also find it very strange that this happens to me with 2 new devices.

I've never had such problems with my other head units (Hizpo and Topway TS10)...

It's not because of the wiring, I'm always very meticulous and accurate.

I have now ordered an Ekiy T900 (which is also a FYT)

I'm still getting poor from all the purchases 🙈

EDIT: Here's another one with this USB problem on a FYT device (see Picture)
[FYT Android Head Units] surfer63:
You know that the USB-ports are switched off on deep-sleep and "come back" as last after deep-sleep and reboot?

That means that app that rely on instant avalailabilty, like a music player that wants to continue immedfiately, will always fail. The entire Android will be running including your music player, but it will fail as it can't find the USB-storage (yet).

And if you then reastart the music player, it will find the USB-storage.

That is one of the reasons why you should never use "nokill" or automatic start for apps that rely on USB.
[FYT Android Head Units] nurex:
I don't have any apps that start automatically, that rely on USB. Even after 20 minutes, no USB is found, neither by the music player nor by the TotalComander or File-explorer.

I had even reset to factory settings, but that didn't help either.... It doesn't get into my head why this also happens with the 2nd FYT device within a few days. I hadn't flashed any kernel or firmware. I only successfully flashed the Launcher34 mod on the new device.

It's very strange
[FYT Android Head Units] nurex:
Does anyone know if the GL850 IC was installed for the USB hub in the FYT devices?
[FYT Android Head Units] sly2:
this is the chip from my both Mekede M700S:

right of the chip is a tiny switch IC for direct OTG on the alone (null) USB port/cable
[FYT Android Head Units] nurex:
I'm thinking about updating the MCU.

The data from the MCU goes into the USB hub and this is controlled via the MCU, so to speak. I have a NOR 53 MCU.

But I can only find NOR MCU files with 360 on 4PDA....I need but without 360.

EDIT:

I'll test that later. But you have to flash the MD kernel with root:

{Mod edit: Link to 4pda removed. Oswald Boelcke, Senior Moderator}
[FYT Android Head Units] j0hn83:
No idea about the NOR MCU but with the YIN MCU it is universal. Both 360 and non 360 units use the 360 MCU.

Also, links to 4pda are banned on xda so you may wish to edit your post.
[FYT Android Head Units] nurex:
Oh sorry, I didn't know that the links are forbidden. I just wanted to edit but the mod was faster
[FYT Android Head Units] sly2:
I have in both units the YIN MCU with older firmware date
[FYT Android Head Units] Oswald Boelcke:
@nurex

I've removed the link from your above post. 4pda is not only another phone related website (and not at all affiliated with xda-developers) but also well known for the distribution of malware and warez. Links or references to 4pda and support for issues with that website are not accepted on XDA at all.

XDA Forum Rules (excerpt):

Please refrain from sharing links or references to 4pda in future. During the next days I'm going to have a closer look into your post history.

Moderator Announcement to all user of this thread!

I've sanitised this thread from all links or any other references to 4pda! And I've subscribed to the thread. Anybody who still means to provide such references might expect consequences to the account; we don't joke about our stance to that platform.

Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[FYT Android Head Units] sly2:
uff...
[FYT Android Head Units] nurex:
Sorry, I didn't know that the Russian site has to do with wa**z and malware.

I think XDA's approach is completely correct in this regard!

Thanks for pointing this out
[FYT Android Head Units] sly2:
back to the point. I got the USB hub IC and will try to change it in the next weeks. maybe it helps...
[FYT Android Head Units] mrchloo:
MCUALL 2023.04.18 09 35 59 NOR 53 L6315 N32P48F64 E60 V1 fyt.zip

drive.google.com
[FYT Android Head Units] nurex:
I've been trying everything all night to get the USB to work properly again.

-Device removed from the car and connected only to 12 V

-MCU updated

- System completely updated.

No improvement!

USB only works sporadically (only rarely during a complete reboot) I can rule out software.

I'm not going to try anything more on the scrap part.

An Ekiy T900 has been ordered. The M700S then flies into the trash
[FYT Android Head Units] sly2:
the problem with the usb hub is very strange. it seems like the chinese are using some cheaper faulty chips or it's really something with the firmware.

this is what i read in the readme of MD upgrade bundle 1:

Mario DANTAS provided mods:

-- Removed "if usb=adb then usb=none" restriction (useful in some headunits)

but I don't know how to understand this correctly.

Hopefully your next unit is not the same inside....(y)
[FYT Android Head Units] Jasper101:
Has anyone had any issues using the MD-EDITION with FYT Management Center Platform Kernel? I flashed my M6 Pro Plus (2K) with it and it caused many issues including making the usb ports not work for CarLink, making the reboot button not work, and making the sleep button not work. I also was not able to find the FMC app on the device despite seeing a success message when I flashed it a the MD Kernel. Anyone have any suggestions?
[FYT Android Head Units] Lucana:
Good morning.

Does anyone have the three apks of the Nexai program for these radios?

I installed the voice recognition but it only comes out in Russian language, and it fails to change it.

I imagine that updating the app will solve it.

I would appreciate if you give me those apk.

Thank you so much!
[FYT Android Head Units] Spark972:
Fortunately I had rewired the oem usb socket of my car to the unit for full integration, I think the issue is in the poor harness that come with these unit.
[FYT Android Head Units] zen kun:
Hello, I came across with your post, I know that is old, but I'm the developer of AutoZen, and the "voice assistant" is a custom implementation using some AI, with the UI similar to android, but is not "from android", the same for the calls, is my own implementation (unfortunately google forced me to remove dialer feature).
[FYT Android Head Units] fra_dta:
Hi, I bought an M300s, Navifly/Mekede, with its retrocamera, I installed it, and the camera is in mirror mode, the left side is swapped with the right, I tried to check the settings, but nothing seems to work, is there some way or some setting to put it not mirrored?

Regards

P.S. this is the unit,

https://it.aliexpress.com/item/1005001810304474.html?spm=a2g0o.order_detail.order_detail_item.5.4cae582fRl8iWA&gatewayAdapt=glo2ita

and this is the camera,

https://it.aliexpress.com/item/4000...il_item.2.4cae582fRl8iWA&gatewayAdapt=glo2ita, the little squared
[FYT Android Head Units] Johnny#C#:
Hello, I have a Navifly 7862 updated with November 2022 firmware. I had an issue with microphone (external and internal) volume but made some mix with older firmware files and fixed. It is long time now that I have issue with Bluetooth speaker volume, I need to have it at almost maximum level to hear. I cannot fix it with any config.txt attribute neither Volume Balance Settings (in factory settings) work for any other than music. Bluetooth app uses separate volume from other sources. I suppose it is something inside apk configuration but I don't know how to edit. Does anyone else face this issue? Are there any ideas?

Thanks
[FYT Android Head Units] PORRETE66:
hola, me llamo Antonio soy de España, he comprado el mekede m6 pro plus 4g/64gy no encuentro la carpeta con los logos par la pantalla de inicio, alguien tiene la carpeta para instalarla en mi radio?

Mod translation: Hello, my name is Antonio, I am from Spain, I have bought the mekede m6 pro plus 4g/64g and I cannot find the folder with the logos for the home screen, does anyone have the folder to install it on my radio?
[FYT Android Head Units] Badger50:
Greetings, and welcome to XDA. As a friendly reminder, we ask all members to please post in English as stipulated by XDA Rule #4:

Spoiler content hidden.

Thank you for your cooperation, and enjoy your stay on XDA.

-Regards: Badger50
[FYT Android Head Units] tmark00:
Hi. I don't know if this is the right thread to ask. I have a Mekede M6 Pro plus 8/256GB radio. I'm getting down to installing the 360 cameras, and I have a question about whether you've connected the red wires for the signals - the reverse light, and the turn signals. I see that the radio responds to the reverse signal from CANBUS - so connecting the wire would be duplicating the existing digital signal.

How to do this optimally?

Regards,

tmark
[FYT Android Head Units] faria:
NO wires are required if you get a a canbus signal. Simply Plug an Play.

If you don't get a signal from the indicators then you will have to connect the wires to the indicators + wire corresponding sides of the vehicle.

This feature does not work on this device, but there is 2 ways of uploading your car logo into the unit. Whats your car Model?
[FYT Android Head Units] MasK:
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!
[FYT Android Head Units] silviox:
Have you some pics of this operation??? Tnx
[FYT Android Head Units] MasK:
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.
[FYT Android Head Units] silviox:
Tnx for all my friend, today I look at my situation if it is the same as yours ;)
[FYT Android Head Units] MasK:
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.
[FYT Android Head Units] surfer63:
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. ;)
[FYT Android Head Units] silviox:
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
[FYT Android Head Units] MasK:
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.
[FYT Android Head Units] Bob_Sanders:
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.
[FYT Android Head Units] silviox:
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.
[FYT Android Head Units] silviox:
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 :(
[FYT Android Head Units] MasK:
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?
[FYT Android Head Units] Allan_Hun:
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.
[FYT Android Head Units] pcmicro:
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.
[FYT Android Head Units] Allan_Hun:
Have a look at this: https://xdaforums.com/t/app-joying-...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.
[FYT Android Head Units] pcmicro:
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 ?
[FYT Android Head Units] surfer63:
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.
[FYT Android Head Units] silviox:
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.