yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
You should read the first two posts of this thread.

Check your manufacturer id and sys.fyt.bluetooth_type property (explained in post #2) and check these with the downloadable firmware.

98% will work but these two should be tweaked.
[FYT Android Head Units] arca114@gmail.com:
She is Android 10 but when you view this as 12 and fake ok.
[FYT Android Head Units] Dr. Se3da:
manufacturer id and sys.fyt.bluetooth_type property

With this info can you assume that MD EDITION is suitable for it?
[FYT Android Head Units] surfer63:
You need to be clear what you want.

You reacted on a full firmware (M6PRO-UI46-1280兼容1024.rar) and now you are asking about the MD-EDITION, which is only a kernel.

What do you now want?

And if it is the MD-EDITION kernel only that you want, you need to switch to that thread.

If it is this full firmware you need to change the nanaufacturer id as this firmware has the Mekede 116 id.

You also need to adapt the bluetooth type as this Mekede firmware is 7 (sys.fyt.bluetooth_type=7)
[FYT Android Head Units] Dr. Se3da:
As the full firmware still android 10 which my unite had so I'm going to flash MD EDITION, that why I'm asking if it will work?
[FYT Android Head Units] Dr. Se3da:
So i will flash (M6PRO-UI46-1280兼容1024.rar) all i need to edit manufacturerid and Bluetooth id in config.txt of M6PRO firmware with my original manufacturerid 124 and Bluetooth type 1, nothing else need to be editing?

And what about ro.fyt.uiid=2 that u ask to copy it?
[FYT Android Head Units] khani47:
Sorry for being numb, but post #23 tells me nothing about the 5ghz issue
[FYT Android Head Units] Dr. Se3da:
I edited the config.txt and fyt.prop

I changed

(manufacturerid to 124 instead of 116)

(fyt.uiid to 2 instead of 4)

(Bluetooth_type to 2 instead of 7)

Then i have to put fyt.prop into allappupdate and archive it to new zip? And config.txt direct in to the flash memory?

Is that all i need before flashing it?
[FYT Android Head Units] coolcat2xx7:
Hello everyone, does anyone have any experience on using uis7862 on a unit with 4gb vs 8gb Ram, does it have a significant difference? Please share your experience, thank you.
[FYT Android Head Units] surfer63:
Yes, indeed. And please note that when you re-zip the AllappUpdate.bin, you have to do this again with password and without compression.
[FYT Android Head Units] surfer63:
To both:

First of all: Please link to the post! Every post has in the top-right the number #wxyz. Right-click it and copy the link (or click it to open it and copy the address bar URL).

Post #23 happens to be one of my posts and says absolutely nothing about 5GHz issue.

So please link to and mention the correct post.
[FYT Android Head Units] Dr. Se3da:
I did as u say

Changed manufacturerid and Bluetoothtype and flash it but unfortunately it didn't boot up just remain at Google logo so i had to reinstall backup which i did from my unit before and it came back to the original firmware

Anyway it's bad but Thanks for your help
[FYT Android Head Units] yihinlau0988:
Sorry for reviving a rather old comments..

I was having issue with my Carlink app hence started to search for method to update the app, end up found #659 of this post. I tried to flash the zip file that Solvin posted, turns out it seems to be unsuccessful because of read / write permission or FS mounting issue. Does anyone has a clue?

After unsuccessful flashing, i did tried to install the APK from the zip file directly on the HU. this time it did install and updated the APP. Wireless Carplay works however lost Wired carplay... i am lost at this point. any suggestions are appreciated. thanks!
[FYT Android Head Units] 03hdfatboy:
On my Atoto I had to change BT type in the config.txt to 0 and have had no other BT issues. Music and phone is BT 1 BT 2 is for OBDII and other data.
[FYT Android Head Units] jbleasdale:
How long did you wait?

Mine stayed at the Google logo for 8-10 minutes during an update, before completing just fine.
[FYT Android Head Units] 03hdfatboy:
Mine was on the google screen for a good 5min Also. Reflash it and wait, it should go past it
[FYT Android Head Units] LLIyT_HuK:
Aaaaaa... Guys can not just sew firmware from other devices. You should first backup and use your config.txt when flashing. BT version, display rotation, additional settings, all this may differ.
[FYT Android Head Units] MonopolyBoy:
How to xhange IT?
[FYT Android Head Units] Dr. Se3da:
After flashing it reboot to Google logo and wait for 5 or more minutes then it restart and opened android update then reboot again to Google logo and wait more minutes then i was afraid of being corrupted so i flash the backup
[FYT Android Head Units] Dr. Se3da:
How I can re-zip AllappUpdate to .bin after extract it?

AllappUpdate.bin is 800MB When i re-zip it the size became 450MB and .zip not .bin
[FYT Android Head Units] surfer63:
Which files exactly did you flash?

And what was in your updatecfg.txt?
[FYT Android Head Units] surfer63:
Read post 2
[FYT Android Head Units] Dr. Se3da:
This files which I flash and updatecfg.txt
[FYT Android Head Units] Dr. Se3da:
I checked post 2 but I didn't get it
[FYT Android Head Units] surfer63:
As such that is OK.

However, the fact that it boots to Android logo means that the Android kernel is functioning.

If nothing else happens you have a completely empty oem partition as your AllAppUpdate.bin was not correct. Not one single apk was installed.

We have seen that before with incorrectly repacked .bin files.

And the AllAppUpdate.bin from that firmware was 786 MB. So an uncompressed .bin (did you use the correct password??) of 800 MB is completely OK.
[FYT Android Head Units] Dr. Se3da:
I used the correct password but to be honest i didn't extract AllappUpdate.bin, i just extract the file and edit it and added it to the existing archive as i didn't know how to repack AllappUpdate.bin
[FYT Android Head Units] phoenixuwe:
Hi

have the following problem: Can't update because the radio requires a version after 07.2022.

Even the original cannot be uploaded because it is older.

What option do I have?
[FYT Android Head Units] Dr. Se3da:
I extract AllappUpdate.bin and edit files and repacked it as u mentioned and flash it and wow it's work but the home launcher keep flashing and when i try to change it he needs a password, i tried all passwords which u mentioned above but no luck so i download a new launcher from MarioDantas website and it works perfectly

So what the password to change home launcher
[FYT Android Head Units] LLIyT_HuK:
try 8086
[FYT Android Head Units] Dr. Se3da:
I tried it but didn't work
[FYT Android Head Units] Dr. Se3da:
I tried all of this but didn't work

Factory menu / Developer options: 3368

Backlight Current Adjustment: 5768

Door lock interference: 0000

To change home launcher: 8086

Developer password: 7788, or tap 7 times on

"About".
[FYT Android Head Units] Dr. Se3da:
What is the password for change home launcher?

I tried all of this but didn't work

Factory menu / Developer options: 3368

Backlight Current Adjustment: 5768

Door lock interference: 0000

To change home launcher: 8086

Developer password: 7788
[FYT Android Head Units] Pino1966:
is this rom also suitable for the mekede m600s, or only for the mekede m6pro, thanks for your reply
[FYT Android Head Units] arca114@gmail.com:
Friend your radio is from another manufacturer so different code, the codes you mentioned are working on mine smoothly..
[FYT Android Head Units] surfer63:
If you have a uis7862, download a new lsec6315update. Enough links in this thread and otherwise use a new firmware which comes with a new lsec6315update.
[FYT Android Head Units] arca114@gmail.com:
Hello friend, the radio that I installed is Rom and a Mekede M700s and I installed it without problems and I'm using it together with MD EDITION. I think you won't have any problems either.
[FYT Android Head Units] Xcaptain:
Just for curiosity shake: Is it possible to run the Android Auto APK standalone on the FYT unit? Not wireless AA that tethers to a phone, but like a launcher of some sort?

I installed the AA apk, but I wasn't able to run it (no 'OPEN' option on the dialog after installing the APK, and no icon on the homescreen too.

I'm running Vivid launcher which satisfies my use case for now, but it lacks some nuances that I wish were more configurable, which it does not.
[FYT Android Head Units] Dr. Se3da:
All password correct and works fine except home launcher
[FYT Android Head Units] Tony2k:
How can I change phisical buttons function?
[FYT Android Head Units] surfer63:
Next time: search first before asking.

Read modded syu.ms.apk

And if that doesn't work: Use my FytHWOneKey.apk (see my signature and the post)
[FYT Android Head Units] Tony2k:
I already tried FytHWOneKey but seems able to configured only some kind of buttons that my headunit never has. I'll take a look to syu.ms.apk
[FYT Android Head Units] surfer63:
What kind of unit do you have?
[FYT Android Head Units] keylimesoda:
[sorry, just realized this thread isn't for Teyes devices]
[FYT Android Head Units] Xcaptain:
How many of you here have a working— or can toggle options successfully— with the Car/Vehicle Settings app?

Per the T'eyes documentation, looks like my car (2016 Toyota Fortuner) doesn't have CAN information sent to the headunit, thus only the steering switch button works.
[FYT Android Head Units] Tony2k:
I have a FYT M500S (7862S) ro.build.fytmanufacturer=116
[FYT Android Head Units] marjanoos:
This is a 💩. If one client/node is connected to the CAN bus it can receive all of the communication. Chinese won't put any additional effort in improving the implementation.

Maybe they would but why should they if people give them 5 stars feedback anyway?
[FYT Android Head Units] Tony2k:
After flashing latest Medeke firmware for m500S (7862-A11-wbt-9-10.zip) I can't flash Mario Danta's firmware. What can I do? There is no recovery in this headunits?
[FYT Android Head Units] Xcaptain:
are you saying that the canbus information is there but the decoder isn't doing the job properly?
[FYT Android Head Units] marjanoos:
Yes. It also may be the issue of comunication between canbus decoder and headunit.

For example: I have 2007 Ford Mondeo with Convers+ instrument cluster. It has big display between the odometer and engine rpm. With OEM head units it can display navigation arrows, RDS information or for example search for phone contacts from connected phone.

With aftermarket head units I can achieve FM frequency at best. But it's possible to have more, one russian proved that with his custom made canbus decoder and Ownice head unit (not FYT though).
[FYT Android Head Units] surfer63:
I don't think 💩 does justice to the work put into this. So I do not agree.

Yes: all signals reach the CAN bus controller, but not all can be interpreted.

And you are right: CANbus controllers are low-margin products, so the Chinese, but also non-Chinese, don't move heaven & earth to get it complete.

The CAN protocol has some standards but every car manufacturer builds its own protocols on top of that. Some car manufacturers are very open to their protocols, others are not. This means that you have to re-engineer the several CANbus protocols for all brands & models of cars.

So for an OEM unit they have all protocols available, but to protect their own OEM units they keep their protocols secret.

You can call it 💩, but I don't agree at all. Have you any idea how many cars and models, there are? And since 1992? When the CAN protocol became a standard, with several modifications per brand and model since then?

It is really undoable to do this for all cars, models and CANbus implementations. I personally think that, in this case, the Chinese did a lot of good work in enabling as much as possible. (And some people complain that the Chinese copy everything, and if they don't copy everything it is still their fault ;) )

And you can also order CANbus controllers from other manufacturers that somehow re-engineered more for that specific brand and model of car, and which you can connect to your unit.
[FYT Android Head Units] marjanoos:
Yes, I agree that it's too much work to implement all of the available cars.

But with 💩 I meant Teyes' explanation why some functions don't work. This fragment to be more specific:

"due to computer system does not send a complete Canbus data to its radio plug, therefore some functions may not be fully realized"
[FYT Android Head Units] surfer63:
Yes, you are right. That last sentence is indeed some animals 💩
[FYT Android Head Units] SyCoREAPER:
Alright folks, I know it was meant in good fun but even censored profanity is still profanity. Lets keep things on track on professional.

Thanks

SyCoREAPER
[FYT Android Head Units] Xcaptain:
This has shed some light of some uncurbed curiosity. T'eyes, to some extent is at the mercy of the manufacturers. I — for the sake of curbing this curiosity— have gone through the list of the car models in the canbus setting and have seen some strange activities that confirmed both @marjanoos and @surfer63 's statement. I saw radar information popping up and dynamically reacting -- though incorrectly-- to the sensor reading. AC UI popping up, canbus clicking (like that of the auto door lock, but without it actually locking), etc. It's like witnessing a kid playing in the playground really.

It's true, that the Chinese manufacturers are in for some real feat enabling thousands of model specific features, but at the very least, they should at least work for the very basic information like the door open/close status, radar sensor reading, and trip computer.
[FYT Android Head Units] Teslic:
Hi everyone!

After days of research on different forums and internet, I think I found a right place to submit my post.

I have Cortex-A55 (or also called SC 9863) processor based device.

It is 12.3 inch device

My current system version is: V3.1.1_BMW_12.3_622_E

MCU: BMW_N32_72-Jan 25 2022-16:35:26-HD-C-R03-00

I am having some difficulties with display of original car display menu (if I go for 10.25 inch nav) I get 2/3 display presented. Android side works as expected. (apart from android auto it also is showing just on left 2/3 of display)

This is my current interface look:

Is there any chance that I can upgrade to:

I have downloaded Mekede 12.3-9863-2合1_国外UI39-1920x720兼容1280x480-20220607-lzp

Can I run it on my device?

In this current version of my interface I do not have many options. All is locked, and I can not change a lot.

Since last update menu where updates are downloaded and executed is also password protected and now I do not know password to check if there is anything new.

There is only Factory settings available with password 8888.

I have tried many different passwords with no luck.

There is only just one thing that I managed to find, that is using 7777 password, I get to choose few different menu types (I guess for other devices).

I am not a android developer (I was only per few months about 7year ago) but I do programming and I think that with your instructions I can do much my self.

I have coded my BMW to send picture from 6.5 to 10.25, and changed screen type to "brites".

My greatest current issue:

Thank you all,

Please help :)

Mario
[FYT Android Head Units] LLIyT_HuK:
BMW firmware is completely different. Either there is heavily modified FYT, or a completely different platform. If you have a link to the original firmware, then send it. Then it will be possible to say something while there is not enough information.
[FYT Android Head Units] Tony2k:
Antbody know what's mainservice version of MD Edition firmware?
[FYT Android Head Units] Xcaptain:
Hi @surfer63, is it common to have these fail message in red?
[FYT Android Head Units] surfer63:
Yes, sort off.

The first is because the oem/res file is missing. That happens on about 50% of the FYT units.

The second is because many files in the /sys/fyt folder are locked. Actually that part of the backup is not necessary. It contains a number of settings for the FYT apps (equalizer, colour of (soft) buttons, setting of external Amp, etcetera). I think I will remove it. It will fail in 90% of the circumstances.
[FYT Android Head Units] Moldeb:
I've seen a problem recently and don't think it's been discussed yet:

As soon as I make or receive a call, upon ending such call the media/nav volume is not restored to original but remains much lower until I reboot the system.

I'm wondering whether someone has seen this before.

I use MD-Edition but doubt that it's kernel related. Other than that I had no major changes in apps but gplay updates took place of course (play services etc...).

Thanks for any insights!
[FYT Android Head Units] Rachid007:
Hi, what is the difference between these two methods? The second method doesn't restore the unit to its factory settings ?

PS: Thank you for all these very useful explanations
[FYT Android Head Units] surfer63:
Option one does not flash the kernel (6315_1.zip for uis7862, or 6316_1.zip for uis8514). It will only restore the FYT apk layer.

In option 2 you also add a 6315_1.zip (or 6316_1.zip) ti the usb-stick so that your kernel will be flashed as well.

As these FYTS have universal kernels, and users want to try the Mekede or Teyes apk layer, that is backuped with my script. Not the universal kernel.

In the unlikely cause that your system is unstable after a restore, which nobody ever mentioned to me, you can do a full flash with any kernel added to it.
[FYT Android Head Units] arca114@gmail.com:
Hello, good morning, I need some help, I do modified software tests on my radio, now in this one that I tested called PeaceOS the screen is vertical, and I passed the original rom again and it was the same way what can I do?
[FYT Android Head Units] LLIyT_HuK:
You forgot to put your config.txt on the firmware)) This file specifies the correct angle to rotate the display.

What is your HU?
[FYT Android Head Units] arca114@gmail.com:
In the first test, there was no config. Text, and in the second test I passed the full original rom and it didn't go back to normal coming back from work I'm going to go through it again but I thought it was strange because it didn't go back to normal.
[FYT Android Head Units] LLIyT_HuK:
the reason is only in this file)
[FYT Android Head Units] surfer63:
Well, @LLIyT_HuK clearly specified in his his work instructions that you had to put your own config.txt to the usb-stick.

It is strange though that your original firmware doesn't have a config.txt.

Anyway. Create a config.txt with the line "ro.sf.swrotation=90" and copy it with your lsec6315update onto a clean usb-disk. So only these two files.

Then flash it.

Unless you have a Joying. Then you need to specify "ro.sf.swrotation=270" in the config.txt
[FYT Android Head Units] arca114@gmail.com:
Ok friend I will try again when I get home thanks..
[FYT Android Head Units] arca114@gmail.com:
Thanks

I forgot to mention that my original firmware has the file and the file I downloaded from PeaceOS that didn't have it did not return to the normal screen..
[FYT Android Head Units] LLIyT_HuK:
And in the case of UIS8581A "ro.sf.swrotation=0"...

As well as bluetooth modifications...

Therefore, in order not to make a bunch of separate assemblies, it is easier for the user to report their config.txt file))
[FYT Android Head Units] Tahvaja:
Hi all! A new FYT here. (UIS8581A) Here are the main issues with the head unit ATM:

1. The lack of AF in the radio. I guess there's not much we can do about it?

2. Wi-fi is not on/not connecting to the iPhone hotspot when I start the car. I have to turn on the head unit wifi manually everytime, even it should be always on. Is there something I can do about it?

3. The audio quality is ****ty even with the external mic that came with the unit. I've tried every setting. Any ideas?
[FYT Android Head Units] Pacote-san:
This units supports AHD camera on both read and front connectors? If I were to go AHD1080 I would have to got for both rear/front or I can have a AHD1080 on reverse and a AHD720 on the front?
[FYT Android Head Units] Xcaptain:
My Mekede M6 Pro 2K unit comes with a rather small Wi-Fi antenna. Where my phone gets reception in the car, the headunit barely has 1 bar. I say barely cause Everytime it gets connected, it disconnected itself, and turned the wifi off.

I went and toggle the wifi throttling option in settings > wifi > advance, as well as the one in Developor options, still no luck.

I switched between 2.4Ghz (my iphone tethering) and 5Ghz (my second home wifi) it won't connect.

I disabled Bluetooth, still doesn't connect.

Anybody has any idea what may be the cause of this behavior?

I assumed by turning off the wifi throttling, the wifi will simply stays on, but that doesn't seem the case.

Anybody experienced something similar before? Any tips on how to fix this?
[FYT Android Head Units] arca114@gmail.com:
Fourth attempt and I can't get my radio back to normal, MEKEDE M700S
[FYT Android Head Units] LLIyT_HuK:
Add this file when flashing the drain or PeaceOS. Or you can flash it separately only
[FYT Android Head Units] arca114@gmail.com:
Buddy, I'm already hot in the head, what the **** was that that happened... I did the procedure you mentioned and it doesn't come back after passing this Rom Paceos, I've passed the rom mekede 4 times and one that I use a lot of modified and it doesn't come back..
[FYT Android Head Units] arca114@gmail.com:
Friend your file was the salvation, return to normal screen. I did the previously mentioned procedure from the file and it didn't work, but I just have to thank you for the help.
[FYT Android Head Units] LLIyT_HuK:
Show a photo or screenshot of the files from the flash drive that you are flashing
[FYT Android Head Units] arca114@gmail.com:
Paceos firmware that gave the screen problem it was without the text file and I didn't see it.. Now the mekede file had the but it wasn't correcting the image.
[FYT Android Head Units] LLIyT_HuK:
Can I see the native file or its contents?
[FYT Android Head Units] arca114@gmail.com:
Are you referring to the original file??
[FYT Android Head Units] LLIyT_HuK:
Hmmm.... I don't understand, but it's good that now everything works as it should)
[FYT Android Head Units] arca114@gmail.com:
I believe that the update I did first with the PeaceOS firmware left me some traces of your files, now I went back to the Mekede firmware and the screen was vertical and I had to go through the file you sent me again to correct the problem, is there any another thing I can do to end the problem.. I'll send mekede's config text and it's normal...
[FYT Android Head Units] LLIyT_HuK:
If you used the updatecfg file when returning to the drain and there was twipe all, then there could not be any traces of PeaceOS) if you didn’t use it, then there can be absolutely any problems
[FYT Android Head Units] arca114@gmail.com:
The firmware is complete with all the necessary files, I don't understand why it's giving this problem now.
[FYT Android Head Units] Rachid007:
Hi again, by the way, are there any difference between HU with UIS7862S processor and those with UIS7862 processor because apparently i have one with UIS7862S.

In other words, will everything that worksfor units with the UIS7862 processor (MODs, firmwares...) also work for those with an UIS7862S processor?

Thanks in advance for the clarifications
[FYT Android Head Units] surfer63:
No. There is no difference.

The uis7862 is the 1.8 GHz version released in 2020.

The uis7862s is the 2.0 GHz version released in 2022.

Otherwise see here: https://gadgetversus.com/processor/unisoc-uis7862s-vs-unisoc-uis7862/
[FYT Android Head Units] LLIyT_HuK:
By the way, a question for you) Are the mekede m6pro and m6pro plus firmware compatible with the firmware of other devices on uis7862 (s)? Are there any differences in allappupdate.bin or 6315_1.zip?

I saw the difference in the config.txt file