yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] Matt89s:
Hi surfer63 have you already had pleasure to help me in the past on this post for canbus problems on navifly uis7862 FYT=1 on Golf 7. 5

I wanted to update you about the reply above, I have installed the FYT=1 Android 10.0_UIS7862_with360_AQUAUI_TOPPAL_UI17401_UI3_20211120_TAN version of tyuktha.

I have to say it fares much better than navifly's previous stock firmware. The modified firmware has a teyes CC3-style navigation bar, has the back, home and recent app keys on the left, and instead on the right appears volume, gps status, date and charge status of bluetooth device and, if necessary, external temperature (if activated on canbus settings).

The graphical interface has improved, especially in the home screen, navigator widgets, music app widgets and radio app widgets appear with icons of a soft green color.

The radio app has been purged of the AM part, somehow it is also possible to download the station logos from the network by correctly selecting the city name from the RDS.

Now by selecting the bluetooth app, the audio of the radio or other apps is no longer interrupted but only stops when you actually make a phone call.

The microphone now in the phone call is clearer for the listener.

However, I am not using the graphical interface of the mod firmware, so I had to adapt the config.txt to the Agama launcher that I am happy with, also I have correctly installed NavRadio+ and I have set the steering wheel control button through your very useful App FytHWOneKwy radio to NavRadio+ and works perfectly.

Also I mixed the above firmware with core 2021-12-07_System_1638860547 and updated MCU MCU NOR 20211009.

On this firmware there is a carlink app that featured the wireless android auto function.

But it didn't work on my HU maybe because of the incompatibility of my phone (with android 10) because android auto wireless requires installed on android 11 or higher smartphone. The carlink app then crashed.

At that point I replaced the carlink app with a previous one with wired android auto and everything works.

I have successfully replaced the bootanimation, the boot logo and everything works fine.

The only problems that remain are the ones I already had before installing the firmware: D

An issue with the aftermarket steering wheel controls of a one button clashing with another on each reboot from deep sleep and the RAISE decoder canbus box having issues:

choosing canbus supplier other than RAISE (XP or HW) does not share 100% the information of the car but with correct MFA language.

Or by selecting the correct RAISE canbus and sharing the information but at each restart it changes the MFA language to English.

That's all at the moment, I hope it will be useful to someone with Golf 7.5 and UIS7862 FYT=1 owners
[FYT Android Head Units] surfer63:
Bluetooth: It is not clear to me yet, how he did that.

Microphone:

The default FYT firmwares use in config.txt:

persist.btmic.gain=7
persist.btspk.gain=7

Tyukta uses:

persist.sys.zlink.mic.vol=9.9
persist.audio.mic.senstivity=1
persist.btmic.gain=10
persist.btspk.gain=7

That obviously gives a clearer sound.

The core 6351_1.zip is actually universal (for FYT uis7862 units that is). If that is 100% true I don't know, but so far it is.

Modifications can be for screens in the config.txt: standard, Tesla style, etcetera

MCU firmware is definitely not universal.

The AllAppUpdate.bin is reseller dependent (ro.build.fytmanufacturer=<xyz> and sometimes sys.fyt.bluetooth_type=<x>). And in some cases the "non-standard" resolutions require other apps, because the FYT apps are terribly built and not according Android auto-size rules.

Tyukta has a lot of firmwares for the several reseller ids, but I think it can be done in one script. Check the reseller id and in the lsec script do a "sed" action to update to the correct reseller id. But I am still waiting for my unit to arrive, so I can't test.
[FYT Android Head Units] Aksuli:
I have a problem with my Mekede uis7862 unit on my 2008 Mazda 6 with Raise MZD-RZ-05 canbus adapter.

I can't make my car's info display to show average fuel consumption or km to empty like I could with stock media unit. I can only make it to display clock and current fuel consumption using "Car info" application that was pre-installed on the unit.

Also I can't make it to show 24 hour clock, only 12 hour clock (24 hour is used in my country).

Steering wheel controls work fine and the info display shows correctly "music" when playing music etc.

I have tried to search for information if I have wrong canbus adapter, but I'm pretty sure it's the correct one. Now I'm thinking if it is related to the firmware or "Car info" application.

Could installing other manufacturer's firmware or some modded firmware help with this issue? Or is there possibly an updated version of this "Car info" app? Any help is appreciated!
[FYT Android Head Units] slinbin:
I'm confused !

1. Not being satisfied with WiFi reception I'm wondering if it is possible to change the antenna, but the small build-in antenna does not seem to come off, anyone know if it is fixed to the PCB or exchangeable ?

2. In the bottom of the device there is a slot that appear to be for a SD card, the specification states there are no SD-card slots, so far I have not dared trying it out as I risk dropping the card into the PCB enclosure), anyone got some info to share about this port ?
[FYT Android Head Units] halloj:
#2 is for a sim-card.
[FYT Android Head Units] slinbin:
Oh, I see,

So that is a second SIM ?

as there is already one in the harness (have not tested that yet)
[FYT Android Head Units] halloj:
Correct, there are two sim-slots.
[FYT Android Head Units] CaliBurr:
Wait this disables the internal mic? I went through the trouble of installing an external mic on my FYT UIS7862 from "HengCheng" it is the model Pro s9. I am having the issue where audio comes from both microphones and previous threads said you had to open the unit and disconnect the wires. Also interested to know how to disable the Bluetooth bar from preventing navigating apps during a call, and to continue playing audio from an app before actually dialing someone.

The manufacturer has stopped responding, and only gave me an update once to get Google login working... could I install another firmware package and system apps? Where could I locate these if so?
[FYT Android Head Units] ludditefornow:
Where exactly is this config.txt stored? I have a Config.txt stored in my "main storage' / SD card. My config.txt file only has one line and that line is

bt# my BT name for my head unit # then my PIN for BT pairing.

Is this the config.txt where I can add some lines for MIC gain and other things that you note.

With your heading #test, should that be called "code" or some other heading? I am really basic at this stuff but I would like to see if I can get better Mic response.
[FYT Android Head Units] surfer63:
config.txt is in /oem/app, just like fyt.prop
[FYT Android Head Units] ludditefornow:
Thanks. I have been doing a lot of reading today. I found FYTBACKUP_UIS7862_UIS8581A+20211107 on 4PDA and extracted my config.txt.

If anyone is interested, I have attached it. I have a Navifly unit as per my post here https://xdaforums.com/t/medeke-navifly-7862.4248969/post-84681347

I see my BT is set to 1 from factory and I get OBD and phone working. I was interested in seeing what happens if I change that. I also want to test mic performance.

Can someone link me to a simple person's version of how to update the config.txt file when I am unrooted. Please. I am simple. I need basic guide. I will report back my findings if someone takes the time to explain step by step what I need to do.
[FYT Android Head Units] muzoss:
Maybe someone has solved the problem with the volume button on Agama Launcher, like in CarWebGuru, namely on newer software it does not work at all, ie it can not be adjusted louder or quieter, while on older original software, from Navifli, it is possible, but in a few seconds it returns the same volume as before
[FYT Android Head Units] surfer63:
No, it does not. This makes the microphone, internal or external, a bit clearer.

No, you don't have to desolder the wires for the external microphone.

You can tape the outer two connections of the flat connector on the side. Links and pictures have been shared by multiple persons (including me).
[FYT Android Head Units] surfer63:
It depends what you want and need to change. You can write a script that uses sed for example to change lines inside the config.txt.

Or you can write a script that completely replaces the config.txt.

Attached is universal script for sc9853i, uis7862 (ums512) and sc9863a (uis8581a) that replaces the config.txt in its entirety.

There is NO config.txt in this script.

Unzip it to a clean USB-stick and copy YOUR config.txt in the top-level of the USB-stick.

And of course: Make sure you made a copy/backup of your config.txt in your /oem/app. If you have the firmware of your unit, you already have the original config.txt in your firmware.

This is a universal script for sc9853i, uis7862 (ums512) and sc9863a (uis8581a).

Note: As I still didn't receive my uis7862, I could not test it there.
[FYT Android Head Units] CaliBurr:
Thank you for the response @surfer63 . Do I need to open the unit? I looked and it doesn't look like unscrewing the back would allow access to the internal mic. this is my unit. What do you mean tape the wire lead ribbon connector on the side?
[FYT Android Head Units] surfer63:
Method #1 (units approximately after August 2022 with firmware after approx. August 2022, the so-called M6Pro units with 2.0GHz uis7862S CPU):

In the Settings: Settings -> Factory -> Back MIC switch:

Back MIC switch -> When set to "On" the internal microphone is switched on, but only new M6 pro hardware. When set to "Off" the internal microphone is switched off. Use this "Off" setting when you have an external microphone connected. If you have an old(er) firmware and not the new M6 pro, you need to use method #2.

Method #2 (units before approximately August 2022 OR with firmware before approx. August 2022):

Look here (and translate to English). The second image is a series of three images. https://vk.com/@teyes_by_maga-vneshnii-mikrofon This is from @gordgelin

Below image comes from 4pda, but I can't find it back. It is not mine. I am sorry that I can't give the correct credits here.

Method #3 Completely remove the internal microphone

See this youtube video (from Teyes Australia)
[FYT Android Head Units] slinbin:
Anyone with experience on adding an external antenna?
[FYT Android Head Units] ludditefornow:
Thanks, all done.

As a tangent question, what are the rest of the entries calling for in the config.txt noted below. Is there a list of what the other items can be affected by the config.txt?

EG: in "persist.syu.voicehint=false" what is voicehint? also what is voiceint?

Is it worth creating a sticky thread to nominate what all these items are and how they affect functionality?
[FYT Android Head Units] surfer63:
Like mentioned "somewhere" earlier: I wanted to create something like a "FYT based Spreadtrum uis7862 (unisoc ums512) - Q&A, Mods, tips" thread as soon as I had my Mekede unit. It was supposed to be delivered before 10th of January., but it is currently "somewhere" and nobody knows where. Early this week I was told it might be early March: 3 months delivery time :mad:. That is becausethey use the very cheapest way of transporting. If I had known that I had simply purchased a Joying: more expensive but all my units arrived with 15 days.

But if I have time I will create the thread today. I have 90% already written.

Bur describing all config.txt entries? That is not possible as the config.txt is used like some kind of prop file. A derived one of the FYT based fyt.prop, which again is derived from the build.prop.
[FYT Android Head Units] martindagun:
Hi all,

I was originally planning to buy the Teyes CC3 unit, however am now thinking of getting the Naviflyer unit as I understand it's the same hardware and much cheaper.

I've been reading some issues with the unit from last year, however, have most of these now been fixed? Does the Google Assisstant now work ok?

I'm planning to install the UDT launcher as I really like the look of the Teyes interface. After this is installed, is there anything the Naviflyer unit is missing from the Teyes unit?

Thanks in advance
[FYT Android Head Units] surfer63:
There are 2 things to keep in mind here. Both Joying and T'eyes are more expensive, that's true. but I would never buy a T'eyes due to their closed license-restricted applications policy and blocking of open-soruce Android functionality, which is actually against the law, or they should provide the source code about what they did, to re-eable the open source stuff.

I have had 4 Joyings and now I ordered a Mekede via "standard shipping" as that was so much cheaper than DHL and "theoretically" the same transport time.

My Joyings always came via DHL and took 6-15 days maximum to arrive.

My Mekede is now 5 weeks (38 days) in transit, and is expected to arrive early March ("My friend, be patient, do not worry", which makes me furious).

NaviFly and a couple of others use the same cheap transport option. If you are lucky your unit arrives in approx. 15 days or less.

I also heard from other users ordering Mekede, NaviFly, Zhan or Isudar using standard shipping, that they had to wait 2 months or longer. Compared to DHL or UPS, which is in general 50-70 euros more expensive, but will generally deliver easily within 2 weeks.

For me personally it means that next time I will pay 100-140 euros more for a Joying and have it in 4-10 days, where this 100-140 euros more perhaps consists partly of the 50-70 euro DHL/UPS transport costs.

I regret my decision to go for a much cheaper, same quality unit a lot now, as the much cheaper is obviously partly in the shipping company. I hate it that I have to wait up to 3 months for this unit.

If you order a Mekede or NaviFly with DHL, you are not so much cheaper than a Joying, but perhaps have it within 2 weeks.

Note though that currently it is Chinese New Year. Nothing will happen before 7 February.
[FYT Android Head Units] martindagun:
This probably isn't a huge issue for me. I will set it up once with the maps, music etc and leave it.

I'm in Australia so shipping normally isn't too bad from China. Plus I'm not in a huge rush to get the unit.
[FYT Android Head Units] ludditefornow:
I played around with FYT HW OneKey version 1.4 just now. The first two bluetooth entrys for the MODE button (BT AV and BT Phone) seem to be linked. By that I mean if I only have com.syu.bt in only BT AV or BT Phone, both apps (or the section of the bluetooth app) still open when clciking the Mode button.

Adding an app other than com.syu.bt in BT AV or BT Phone resulted in the app not opening unless you added the app into both of those. Adding a new app in the third option AV did work. However, no app would work in the 4th option Video is I had my custom app in 3rd AV option.

I have settled on using Android Assistant as the only app associated on the mode button only. That is working reasonably well for now.

With Android Assistant I can start NavRadio app, I can start Google Maps and start directions all from a single click of my Mode button. I can also start most other apps except I cannot start the OEM Bluetooth app. That seems to have been blacklisted by the OEM.

But I have found a long winded way of voice dialing. Using the app AutoZen, the creator has included what looks like a cut down version of Google Voice search / Android Assistant. I believe that is it from Android because of the graphic visuals on the left hand side of the voice pop up box.. From within the app, I can voice dial. Here is a video attached showing this.

How would one go about finding what source/library (whatever it is) the creator used to implement the voice dialing? Because it certainly circumvents the OEM's crippling of voice dialing. If we can find the source from Android, surely a stand alone app could be created and then that could be linked to the MODE button and the Android FYT HU world could rejoice!
[FYT Android Head Units] Matt89s:
My friend, be patient, do not worry - Chiese seller on any question you ask him, XD

Too bad it won't do anything really effective to help you and you'll have to fend for your self 😒
[FYT Android Head Units] CaliBurr:
How can I tell if my HengCheng Pro s9 is open source? @surfer63You don't even have a medke yet and you are this active? You are awesome dude. Now I know not to recommend the teyes anymore. I thought it was the superior unit. Is Dasiaita a whole different platform? I don't understand all this. Shouldn't you be able to install any Android version that is open source up to 11 is on any unit?
[FYT Android Head Units] surfer63:
I was not 100% correct.

None of these units is 100% open source. The Android layer is open source. And that is partly blocked by T'eyes.

Of course the applications delivered with these units (all units) are closed source (unfortunately).

T'eyes however blocks some of the open source stuff by adding closed source programs. I personally consider that bad practice.

T'eyes offers other software like very limited voice recognition programs in only a few languages, and at the same time block Google voice which is 100 times better and for 35+ languages.

If your HengCheng reseller doesn't do that, it is OK.

Dasaita is a whole different platform. Read thought these forums and Google. That is how we all learned it.
[FYT Android Head Units] Radzią:
I just bought mekede m700s. With 8GB of ram. Curiosity, because this processor probably supports a maximum of 6gb I'm curious how they solved it.

My second question is whether this ROM has any ota or a page where I can download the update? Any custom ROM?
[FYT Android Head Units] ludditefornow:
I created a split screen shortcut that opens NaviRadio and Google Maps together with Split screen Launcher https://github.com/paprikanotfound/SplitScreenLauncher . I am trying to find a way for Google Assistant to call this shortcut. But I am coming up empty on how to open shortcuts with Android Assistant.

Any ideas?

I am really seeing a future of using my steering wheel mode button calling Android Assist and then trying to find a way to get Assist doing what I need.

I can call NaviRadio app, Pulsar music app, Auto Zen, Google Maps and Microsoft Launcher app.

I can call Maps to start a trip ("Go to the Grand Canyon Car Park"). Stop the trip ("Close Google Maps")

I can call Auto Zen and then manually hit the mic button and then voice dial and start a call.

I'm starting to think that there is a future with this direction.
[FYT Android Head Units] surfer63:
I was too much thinking of a script.

This is soooo simple.

Simply copy your config.txt onto a USB-stick and add the lsec7862update. That is enough as the binary already copies it automtically to /oem/app when "flashing".
[FYT Android Head Units] spludgey:
Does anyone know if it's possible to change the pulldown menu to include notifications, like on a mobile phone?
[FYT Android Head Units] surfer63:
This is done by the SystemUI.apk which has been compiled by FYT for these units in combination with the other software.

You can't use another SystemUI.apk on these systems. Modifying this one would require "reverse engineering" the code in smali.

But you might be lucky: {Mod edit: Reference to 4pda removed. Oswald Boelcke, Senior Moderator}of 4pda had modifiied the SystemUI of the uis7862 to display notifications, but I don't know whether that is in a pull-down or by simply displaying it in the notification bar by simply overwriting previous ones.
[FYT Android Head Units] surfer63:
See your inbox
[FYT Android Head Units] spludgey:
You're a champion!

But gee, the Russian captcha was a real challenge! :LOL:
[FYT Android Head Units] surfer63:
I will add that to the Q&A. There are some good howTos.

Question from my side (still waiting for my unit):

There is this black wire (I assume) in the purple frame on the back of the Mekede. It is displayed on mutlipe images, but you can't see where it is going to and it is not explained on the website.

What is it for?
[FYT Android Head Units] surfer63:
Let me guess. Is this for the fan?
[FYT Android Head Units] Excessed:
Is there someone that can tell me how I can install a firmware which allows wireless Android Auto on the Navifly 7862?

I'm have found several firmwares, but I have not a clue on which one actually works.
[FYT Android Head Units] spludgey:
It is the fan power. It goes into one of the plugs that go into one of the ports above.

It's a bit strange that they don't do it internally, so it seems like it was easier to do it this way as they're just an OEM unit and not all "manufacturers" have fans.
[FYT Android Head Units] surfer63:
The firmware has hardly anything to do with wireless Android Auto if it is not too old. You need the latest version 2.0 of the carlink software. There are links in many posts in this forum. Simply search for it.
[FYT Android Head Units] ludditefornow:
It looks like a cable tie. I hope your unit arrives soon. It must be so frustrating.

@Excessed , my Navifly unit came with AA. I don't use it but tested it once and it hooked up fine and it took me a bit of time to actually stop it working. My unit specs are on the second post of this thread.

@surfer63 and @Excessed again, I have a newer ROM noted in this thread. It is still up on the share. I can keep it hosted for a while. https://xdaforums.com/t/medeke-navifly-7862.4248969/page-2#post-85113901

I still haven't used the ROM, though but I got it direct from Navifly.
[FYT Android Head Units] Excessed:
I have the latest firmware according to Navifly. So I'll try to install carlink 2.0.

Thanks!
[FYT Android Head Units] surfer63:
Is your firmware newer than the official version from Mekede's download page?

Support / Software Download Address
[FYT Android Head Units] ludditefornow:
A

A fan can be a good thing, but I live in a location that sees 35 degree C days in summer so it gets much hotter in a locked up car and I have never had heating issues with no fan. The screen has been uncomfortable to touch because it was so warm, but again I've not had an issue.
[FYT Android Head Units] ludditefornow:
I uploaded that ROM on June 1, 2021 so I dare say that there has been a newer one since, but I can't be sure.
[FYT Android Head Units] spludgey:
Oh, so a nice mild summer, greetings from Australia. ;)

Though due to La Nina, it hasn't been hot here this summer either.

My screen gets quite hot, but the unit still seems to be working fine.
[FYT Android Head Units] Excessed:
Navifly send me their update file on 31-12-2021. So I'm guessing it would be newer then the one in June. Can't say for sure, will check it out tomorrow.
[FYT Android Head Units] surfer63:
The latest Mekede is from 22 Jan 2022. Just downloaded and checked it.
[FYT Android Head Units] Excessed:
Can I install that on my Navifly you reckon?
[FYT Android Head Units] surfer63:
Yes, but ... first read post 2 of my "General FYT based Spreadtrum uis7862 (unisoc ums512) - Q&A, Mods, tips". ;)

I think NaviFyl and Mekede are 100% compliant, even on reseller id, but I'm not sure.

Running my HWGetInfo.apk (see my signature) will give some more insight.
[FYT Android Head Units] Excessed:
Thanks for the help. I'm going to familiarise myself with the post tomorrow when I have some free times on my hands.
[FYT Android Head Units] Excessed:
Tried to install Car Link 2.0, but I get "app could not be installed"
[FYT Android Head Units] surfer63:
The carlink 2.0 came at the same time as firmwares from Joying and T'eyes around end of September. Maybe your kernel 6315_1.zip is not up to date enough.
[FYT Android Head Units] Excessed:
Thanks again, will check tomorrow if I can get it to work
[FYT Android Head Units] surfer63:
Also: You might first need to uninstall the previous version.

And if carlink was in your units firmware when it arrived, then it is prabably differently signed than the new one.

If that is the case you first need to remove the installed one by script.