yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] 3PI:
Hello.

I have a problem with "Mercedes canbus". Let's see if you can help me.

I have a Medeke/Navfly 7862 FYT (116) unit mounted on a SLK-350 Mercedes R171, 2006 year

The canbus module provided by the seller is an XR.

I have not been able to correctly adjust the Canbus version in the 7862 FYT configuration, since my car model does not appear in the hidden menu configuration. The closest thing is an A-CLASS w169. Other car setups work the same, or just don't work at all.

There is a very big error when handling, from the steering wheel, the configuration of the car's instrument panel menus, since the FM radio memories change themselves. And it shouldn't have that effect.

The outside temperature does not appear either, nor do the parking sensors work on 7862 FYT.

Is there any way to update the functionalities of cambus mercedes? Has anyone experienced something similar?

The seller has not been able to provide me with a solution. After several questions, the technical service has disappeared.

Sorry for my English. I use google translate
[FYT Android Head Units] Lakis_dj:
On the radio, the stations are on the RIGHT, is there a setting to have them on the LEFT?
[FYT Android Head Units] DexterMorganNL:
I believe not: I just replaced the app by @KoTiX2 NavRadio+ free https://xdaforums.com/t/dev-new-nav...53i-fyt-devices.4387965/page-40#post-88247931

Only downside is, that this apps conflicts with the original FM Radio so you have to remove it. Which on its turn, cripples the FYT Car Launchers. Youcan't use the FM Widget or shortcut for the radio. If you do try it, your launcher will crash and reset to the default one.
[FYT Android Head Units] KoTiX2:
In the full version of NavRadio+ you can select in the settings to have the vertical buttons list on left or right side. You can also choose an horizontal grid with customizable number of rows and columns.

In the next version there will be also a carousel view ;)
[FYT Android Head Units] DexterMorganNL:
I meant in the original radio app, none of these settings is possible. So I recommend NavRadio+ ( I guess the free version doesnt allow to change it? )
[FYT Android Head Units] KoTiX2:
Oh i misread your post then :p

I edited my post.

Free version of NavRadio have only the horizontal grid view.
[FYT Android Head Units] Johnny#C#:
Hello,

I own a Navifly 7862 for two years now. I always had weak microphone. At first the seller recommended to plug the external microphone. better than internal. I also used persist.btmic.gain=9 than 7 in config.txt and did work for me, better than before.

Recently I got a new update and reset the device. As usual I changed my config.txt and persist.btmic.gain. But with the latest update the microphone almost does not exist. When talking in BT calls almost nothing is heard to caller and when I use a recording application it can record but very weak, heard from the deep... Tapping on microphones can be heard from far.

Since then I tried multiple things:

update again

factory reset and new update

settings in config.txt:

persist.sys.zlink.mic.vol=9.9persist.audio.mic.senstivity=1

persist.btmic.gain=10

persist.btspk.gain=7

downloaded the firmware directly from http://www.mekede.com/Software Download Address1/

tried to change ro.build.fytmanufacturer=1 or 116 and ro.fyt.uiid=4 or 2 at fyt.prop (did't expect anything from this but gave it a try)

used original global config.txt

persist.btmic.gain=7

persist.btspk.gain=7

I also tried another external microphone. Factory setting which exchanges front/back microphone does nothing. I suppose something with the newer update and after causes that, since it happened after the update, worked before.

Any suggestions? Anyone has similar issue?

Thanks
[FYT Android Head Units] pir8man:
on the older models the software switch does not operate. there is a tape over the ribbon cable to the internal mic trick.

https://xdaforums.com/t/medeke-navifly-7862.4248969/page-12#post-86341115
[FYT Android Head Units] Johnny#C#:
Thanks for the answer. I don't know whether I need to hack the hardware, the internal mic. I suppose is firmware issue.

I bought the device in Apr 2021 and had the previous update in Jan 2022. It worked till recently, it was not perfect sound but I could be heard. After the latest update both microphones, internal and externat are weak, they work very low, in levels that almost can't be heard. Toggling the mic selection option in factory settings does nothing. The seller had sent me an update from Aug 2022, I also used the one from MEKEDE site, in Nov 2022 (the last one also write that Android version is 12, I didn't know it could take 12). Everytime the result is the same...
[FYT Android Head Units] pir8man:
The hardware change was in Aug 2022, which allows the software switch to work. So both are always enabled on yours without the mod.

Which drops quality in both due to power supplied to run only one.

They are all android 10. The a11 a12 mod is a text setting, not an apk upgrade.
[FYT Android Head Units] arca114@gmail.com:
I need help, my screen looks like this and I don't know why, how can I fix it?
[FYT Android Head Units] arca114@gmail.com:
What a scare, I managed to solve it.
[FYT Android Head Units] arca114@gmail.com:
How do I change it to Portuguese Brazil, can anyone change it for me? I tried to do this, not sure if it has anything to do with it, but my screen stayed horizontal.

ro.product.locale.language=ru

ro.product.locale.country=RU

persist.sys.language=ru

persist.sys.country=RU

persist.sys.timezone=Europa/Moscou
[FYT Android Head Units] surfer63:
rotation has to do with something like ro.sf.swrotation=90 or some number like that.

Brazil has two time zones. You have to find out yourself.

Simply remove those settings from the config.txt. And you obviously did not read post #2 of "General FYT based Spreadtrum uis7862 (unisoc ums512) - Q&A, Mods, tips, firmware"
[FYT Android Head Units] arca114@gmail.com:
Taking advantage of this to modify this is also to leave it horizontal.
[FYT Android Head Units] arca114@gmail.com:
I made this modification and got this error.

ro.product.locale.language=pt

ro.product.locale.country=BR

persist.sys.language=pt

persist.sys.country=BR

persist.sys.timezone=America/São_Paulo
[FYT Android Head Units] mastrv:
Can't you just change the language through the Android settings?
[FYT Android Head Units] surfer63:
If you download a firmware from 4pda, you should ask on 4pda, not here. If you don't speak russian then don't go to 4pda and download stuff you can't get support on. You are doing the worst of both worlds.

Leave these 5 settings out of the config.txt and when your units boots, it will be in English. Then change it to your liking.

Just as @mastrv mentions.
[FYT Android Head Units] dinkili:
it can be replaced with the same one on the left, but you have to uninstall the old one
[FYT Android Head Units] Johnny#C#:
Hi,

I had the same issue once I tried to wipe config.txt with a script in lsec_updatesh. After that I just did a new update/installation without that script and it fixed.
[FYT Android Head Units] Johnny#C#:
I think the radio is in apps in AllAppUpdate.bin, you have to replace it with another before installation
[FYT Android Head Units] Johnny#C#:
So, if I manage to change the ribbon and cut off the internal microphone, will it work? I am not familiar with hardware changes like that. But the question is why with the previous update I had from 2021 it was working? I remember I always had both microphones listening, but with the software switch on, the external microphone was louder, so I could use them without problems. If I could find somehow the setting or configuration that made the previous update to work, maybe I could use it here too, without any hardware hack
[FYT Android Head Units] dinkili:
get the radio application to remove and restore
[FYT Android Head Units] zytw:
Maybe. Anyway, I suggest you do complete power-off and on before that (pull out off the unit harness, wait 30 seconds, then push it back). If it doesn't work, ask the seller for the original firmware and flash.
[FYT Android Head Units] Matt89s:
Nothing to do reset done, firmware updated, cables disconnected, the problem persists. Incredible I have no words. I don't know what to do anymore :( you constantly hear this background white noise on the speakers and when I open applications like bluetooth radio that have access to the speakers it makes a small beep

Edit:It seems like there is some process that is not closing and making the speakers remain with no sound but waiting for
[FYT Android Head Units] zytw:
It seems like a hardware issue. Did you check the harness? loose? short circuit? GND well-grounded to chasis? Same issue when you use the factory stock head unit? Can't figure out other reasons, maybe you have to ask the seller for a replacement.
[FYT Android Head Units] Matt89s:
Let's not joke it's not a hardware problem it's definitely due to the flash operation I carried out, now it's figuring out how to go back ...
[FYT Android Head Units] Matt89s:
After several flash firmware and reset to factory settings, the situation seems almost back to normal. The white noise has disappeared, I do not understand why but only with the engine off was there a slight noise when closing and opening the bluetooth and radio, but in any case it is something imperceptible if you do not notice it. However, all of this remains a mystery
[FYT Android Head Units] surfer63:
Sorry. Was on travel for a couple of days (first time since Covid).

I assume it has to do with settings being corrupted because of an incorrect flash. Maybe the config.txt should also have contained a twipe_data command, but that would also have caused that all your settings and 3rd party installed programs would have been wiped.

But in the end you still ended up there.

Now that everything has been flashed and wiped multiple times I would like to ask about the original issue: Is your unit going back to English after a reboot?

Also: I did not know you had the original firmware, but fortunately you did.

What is in the config.txt of your firmware?
[FYT Android Head Units] Matt89s:
In reality, the problem of white noise when apps are closed is still present, including the beeps when opening and closing the radio and bluetooth apps. Also I have a problem with two buttons on the steering wheel that conflict ... Clearly the language problem is still present. I just don't know what to do to fix it, instead of solving I caused other problems ... please help me
[FYT Android Head Units] surfer63:
With regard to changing the config.txt on the oem partition.

See this post from @gordgelin

So for the time being I am also out of options.

An option might be to do aagain a full flash and change the config.txt on the USB-stick immediately with the Italian codes.
[FYT Android Head Units] Matt89s:
This was done and did not fix the bug

EDIT:

I noticed that when I enter the car maintenance app and change the language, Italian has a check mark. But I leave the app and come back and go to language the check mark is no longer there
[FYT Android Head Units] uberNoobZA:
You mentioned 3 floating buttons. I've reset my Navifly 7862 to factory and now have a floating button that brings up some shortcuts in a square when I tape it. I can move the button around the screen, but can't find how to get rid of it. Would you know how I can hide this buttons ?
[FYT Android Head Units] nnquynh:
I don't know if it is the same with Navifly, but by Ownice 7862 you should swipe down from the top of the screen, and touch the icon "suspension close" to switch off this floating button
[FYT Android Head Units] WV1:
I had the same. Turned it off in one of the settings menu's not sure which one though.
[FYT Android Head Units] surfer63:
Not in the Settings. This is the Touch Assistant apk. It has an option to "display button" and "start automatically".

Switch both to off in the apk
[FYT Android Head Units] Petepango:
Will the Joying UIS7862 Android 10 1280x800 ROM found in below youtube video work on Navifly/Mekede UIS7862 Android 10 1280x800 units?
[FYT Android Head Units] MasK:
Hi all.

I just got a Mekede 7862 6/128 unit and my reverse cam doesn't work.

When I shift to reverse, the +12V does turn my cam on (as I tested it via DVI-IN) so clearly the canbus should be working. It's just that the Android doesnt change to cam input. Am I missing something here?

Also, my backward/forward steering media controls are swapped. Is there a way to re-map it? I don't quite understand how to use the steering learning page (does this even work?)

Thanks for any help. I'm also asking the manufacturer for help but theyre a bit slow and there's translation that goes on too...
[FYT Android Head Units] ziddey:
@MasK

easy part first: The swc programming doesn't apply when using canbus instead of key1/key2. There's a setting to flip the controls if they're swapped. It's under factory settings (pin 3368), then something like car agreement (can't remember the actual name).

What car is this? If you have a traditional resistor network style steering wheel wire, you may be able to use that instead and program as desired.

I haven't tested canbus yet (my car doesn't have canbus leads in the radio harness, so I'll have to tap it from somewhere else).

You wired your camera power to the reverse light? In that case, you can splice it to the power wire that's married to the composite cable and hook it up to the "back" wire on the headunit harness. That'll trigger it outside canbus.

Or you can tap the same reverse wire up front to "back", and hook up cam 12v to power the cam instead (doesn't really make a difference though since I don't know if there's a way to force the reverse camera when not in gear).

As far as utilizing canbus for reverse, you can try checking in factory settings that the proper canbus config has been applied. Or you might need to find the manual for your canbus decoder. My unit came with one (a raise box for mazda), and it seems to provide a reverse out pin. So I'm not sure if the headunit would directly be able to pick up reverse via canbus, or if I'd need to add a wire to connect that pin to "back" (no matter since I already tapped a reverse source). Curious since I haven't been able to find a canbus message for reverse for my car anyway (seemingly only in-gear or not).

I did notice a reverse power setting, but haven't checked what it does. I have it disabled, but when going in reverse, it does provide 12v. Maybe it'd reverse it to ground instead?

So if you verify the canbus settings to be proper on the headunit, you might need to fall back to using the "back" wire to trigger instead.

* check if your canbus decoder has a pin for reverse and it works as expected

* find a reverse source under the dash and tap that

* feed the reverse signal back up via the composite/power combo wire since you've already got it tapped

First two options would let you use the headunit to supply power to the cam and undo the reverse tap in the reaer.

Curiously, I get some group loop interference if I connect the cam to ground. If I leave it floating, and just rely on the composite cable's ground to the headunit, the video is good.
[FYT Android Head Units] MasK:
Thank you for your detailed explanation!

The swapping of the buttons is settled.

As for my HU, firstly, there is no "back" wire for my unit. Here's the listing (Qashqai):

https://www.aliexpress.com/item/1005001830516390.html

I do not have the manual for my canbus. It is also a Raise unit as in the attached pic.

The only pin layout I know is for the power connector here:

https://ae01.alicdn.com/kf/H918b860cfee441929908c1848857d360K.jpg

As I follow the reverse cable, it is already split into to the canbus connector and a cable harness which connects to the car. I used to have a Dasaita which has a difference Raise unit and the "reverse trig" wire for that canbus connector doesnt match up to this one. Perhaps these 2 Raise units have different pin configuration.

Currently the power of my cam comes from the "cam 12V" wire, as shown in the attached pic. Interestingly this wire turns on only when I am in reverse gear. How does it know I am in reverse? I don't know. Along with this "cam12V" cable bundle, I have the CAM-IN RCA and also a "IR" wire. I wonder if the IR means infrared or something else.

The manufacturer is not responding yet and I am so close to getting this done. Otherwise it's a blazing fast unit..
[FYT Android Head Units] ziddey:
Ah yeah, my unit (navifly) has 02 on the main plug labeled as "back" instead of "reverse". When I apply 12v to it, the headunit supplies 12v to cam12v and switches to the camera view. That's very strange it's able to detect and supply power but not switch to the camera app. Maybe there's a setting that needs to be toggled?

Nissan-深圳睿志诚科技有限公司

深圳睿志诚科技有限公司

www.szraise.com

The pdfs under df-rz-22 might be close enough if you compare a few

like:

You said you have a reverse wire in the stock radio harness? And that's spliced with a wire going to the canbus decoder and to the headunit's reverse wire??
[FYT Android Head Units] MasK:
Yes, so if you apply 12V to your reverse in, you get a cam12V out and also display switches to cam.

Electrically mine seems to work the same way, however the unit does not switch to cam :(

Thats right. It's pre-connected. So thats probably how it kkows that my gear is in reverse.

This all seems to be a SW/MCU issue. I also dont think the installation would require me to strip any wires, etc. Kinda tempted to factory reset the unit too...

Do you know if theres a FW repository for these units?
[FYT Android Head Units] ziddey:
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
[FYT Android Head Units] j0hn83:
On the older FYT devices without a dedicated mic port, the internal and external mic are always on. It is hard wired this way and it cannot be changed with software.

That's why many users modify the units to disable the internal mic.

The software switch for changing front/back mic does NOTHING at all for devices that don't have the newer dedicated mic port on the rear.

It doesn't turn anything off or make anything louder.

If you think it was louder before with the switch then it is probably just confirmation bias. The brain believes what it expects.
[FYT Android Head Units] Johnny#C#:
Thanks for the answer. It was louder, really. I was using microphone since 2021 for calls all the time, google search, maps, a few assistants, etc. After the last update (Aug 2022 and Nov 2022, I have tried) none of those works with microphone. In BT calls it listens nothing and in other apps it is very weak...
[FYT Android Head Units] j0hn83:
The settings containing the external/internal (back/front) microphone switch was not released until August 2022.

There's no way you could have been using that option since 2021.

Your microphone may have been louder before you performed an update but it was not because of the software microphone switch. It does nothing on units without the relevant hardware.
[FYT Android Head Units] marjanoos:
By "older FYT devices" you mean old revisions which were produced before mid 2022 or all devices which aren't M6Pro?
[FYT Android Head Units] j0hn83:
I mean all devices that aren't the M6Pro and the new Teyes CC3 2k.

These newer devices have a separate, dedicated mic port on the rear.

On devices like the Mekede M500s, M600s and the Teyes CC3 there is no dedicated mic port on the rear. It doesn't matter when they were produced, they didn't revise them in mid 2022.

On all of these devices, no matter the manufacture date, the internal mic is always on. The external mic is always on (if connected).

The setting labelled "Back Mic Switch (Front Mic / Back Mic) only works on these newer models with the dedicated mic port.
[FYT Android Head Units] marjanoos:
Thanks. I wish at least one chinese company would put an effort to make device without such irritating bugs and really refined. I would pay more, but there's no choice.
[FYT Android Head Units] surfer63:
You might call it a bug. I call it a design flaw which they fortunately now (6 months ago) fixed. That is is not backwards compatible is because it is hardware.

You can also request a new motherboard. That was more common some years ago, but if you request it they might send you a new one. Of course it will cost money ;)
[FYT Android Head Units] evilution.dk:
Hi all. Has anyone experienced poor audio quality when streaming from phone via the bluetooth app? It sounds very compressed. I have an M600s with the latest firmware from the Mekede website. I have searched extensively but have not yet found a solution for my device. Could it really be that the module is of such poor quality?

EDIT:

Through 4PDA I was able to learn that you can switch to using the internal BT module by setting 'sys.fyt.bluetooth_type=0' in config.txt. This allows for use of the AAC codec which can be set under developer settings which solved my problem.

Now, it seems that the BT app cannot see devices but you can pair up from phone side. Also, other codecs such as LDAC or aptX do not seem to be supported.

I have not observed any issues from switching module so I am curious as to why they added a second module in the first place.

Anyway, I hope this can possibly help others in the future.
[FYT Android Head Units] DexterMorganNL:
No, but why not stream directly from the headunit? I have used that feature in Bluetooth one time, and it works just fine. But the volume is partly controlled by your phone.
[FYT Android Head Units] evilution.dk:
Thanks for the response. Streaming through the unit indeed does work good but I know my girlfriend would prefer to use the BT audio feature. I just did not imagine that compression would be the challenge here.
[FYT Android Head Units] evilution.dk:
Just to notify anyone subscribing to the thread that I managed to find a solution for this :)
[FYT Android Head Units] marchnz:
Which was
[FYT Android Head Units] Moon2:
Its in his original post as an edit (3 posts above his latest post).

https://xdaforums.com/t/medeke-navifly-7862.4248969/post-88290735
[FYT Android Head Units] marjanoos:
Did you manage to deal with that delay?

I hope you will come back to the forums and reply me :)

@DexterMorganNL you wrote that delay is inevitable but actually it's not. I had MTCE device previously and reverse image was instant (and I know that's different device). Here it's about 3-4 second which makes the reverse camera useless.
[FYT Android Head Units] DexterMorganNL:
Yes a delay, while starting the engine: not while the engine is running, than there is no delay between going into reserve and the camera. The delay is because the headunit needs to wake from sleep.
[FYT Android Head Units] marjanoos:
There's no difference in my case. When I put the reverse with engine running, 3 seconds between reverse screen is showing.

Also was anybody able to install updates for those integrated app store apps? Like canbus, protocol etc.? When I try to install them, I get "app wasn't installed".
[FYT Android Head Units] DexterMorganNL:
Only the Carlink, the others I didn't try to install and no that app store show some error. So it's not working somehow.
[FYT Android Head Units] marchnz:
The correct answer was: First post updated with details to resolve the issue.
[FYT Android Head Units] marjanoos:
For the record: I was dumb :D I assumed that if there's no camera attached, head unit would go into reverse mode as quick as if camera was attached (but with black screen only).

So when I thought "well, let's try to connect the camera" and I've found that image is showing instantly.