yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] VidasS:
tried to play with backup script to awoid errors with excluding symlinks:

find /oem -type l > /storage/sdcard1/symlinks.txt

/storage/sdcard1/7zzs a -r -tzip -mx=0 -p048a02243bb74474b25233bda3cd02f8 -x@/storage/sdcard1/symlinks.txt /storage/sdcard1/BACKUP/AllAppUpdate.bin /oem/* > /storage/sdcard1/backup_oem_log.txt

But it seams to ignore that setting... :/

Thinking to install mekede firmware on my unit. I have unit with 360 and 2k screen, so I presume i need to take M6PLUS-UI46 2000x1200 firmware, maybe someone has to share it? I used out my nutstore downlond limit for wrongly chosen one...
[FYT Android Head Units] surfer63:
I really don't understand this issue. You start the radio, you slect frequencies and add it to 1 of the 18 favorites, and done.

For the rest of your life, you don't have to look at it.

And changing the app to make it a user selectable frequency is a lot of work and totally useless, if you have 18 configurable presets.
[FYT Android Head Units] surfer63:
The shell used in the recovery mode is extremely simple and far from posix compliant.

I have written and rewritten commands in posix/bash/zsh/tsh "dialects", but only the most simple commands are possible.

A lot of parameters valid for find/ls/ln are not working. Piping and redirecting hardly works and it differed going from Sofia3GR to PX5 to sc9853i to uis7862. And actually the options became less. From my "Joying Extra Tools" apk, which started on Sofia 3g, I had a more extensive set then now on the uis7862.

The terminal when Android is normally running is fully bash compliant.

That is indeed quite annoying. You can only do that once a day and if you are too late the total number of downloads for all users has already exceeded. So try again, or hope that someone has it. (I don't have it)
[FYT Android Head Units] j0hn83:
Currently uploading to my Google Drive for you. Should take 10 mins.

I've made that mistake so have about 3 nutstore accounts.

I think they reset once every 30 days.

Here you go: https://drive.google.com/file/d/13-Ks6iWTxJHp5DjVMMHBfIsD9-vuflLD/view?usp=drivesdk
[FYT Android Head Units] louforgiveno:
Does the Mekede site/ firmware page not load on mobile for anyone else.....initially i assumed their site was down (2 weeks ago)

Just tried again and page just refuses to load at all
[FYT Android Head Units] VidasS:
Thanks a lot :)

surfer63 in post #2 is there a typo or it should be so?:

persist.audio.mic.senstivity=1

sens{i}tivity

on RU forums there is both versions but seems that on newer posts it's persist.audio.mic.sensitivity
[FYT Android Head Units] surfer63:
Sharp that you spotted it, but it is a typo by the Chinese. So the missing i is correct. It is indeed persist.audio.mic.senstivity=1

This has been discussed before (also on 4pda) and led to quite some confusion. But the incorrect spelling is how it should be used.
[FYT Android Head Units] VidasS:
Be carefull with current backup script as if it shows error it might be that not all files was properly copied.

Jus now comparing the files I see that there less stuff, somehow from log file and size of the backup i thoght that it worked fine just failed on those symlinks. But extracting AllAppUpdate shows an warning and just part of it is extracted:

Tried to look how Russians do it, but it seams it needs a registration to get their files.

Another thoght to awoid errors is to copy /oem withtout symlinks to some place and only then do the backup (the only concern is aditional storage required and a bit longer process).
[FYT Android Head Units] VidasS:
Also found quite differences on app/customer_config.properties:

in my backuped files:

keep_services = [{"pkg":"com.syu.rearcamera", "action":"com.syu.rearcamera.keepAlive"},{"pkg":"com.syu.forwardcamera", "action":"com.syu.forwardcamera.keepAlive"},{"pkg":"com.syu.doublecamera", "action":"com.syu.doublecamera.keepAlive"}]

on Mekede:

keep_services = [{"pkg":"com.syu.rearcamera", "action":"com.syu.rearcamera.keepAlive"},{"pkg":"com.syu.forwardcamera", "action":"com.syu.forwardcamera.keepAlive"},{"pkg":"com.syu.doublecamera", "action":"com.syu.doublecamera.keepAlive"},{"pkg":"ru.mail.channel.voiceservice", "action":"ru.mail.channel.voiceservice.KWSScheduler.keep"},{"pkg":"com.syu.lsgpsblue", "action":"com.syu.lsgpsblue.keepAlive"},{"pkg":"com.chungauto.warranti", "action":"com.chungauto.warranti.keepAlive"},{"pkg":"com.chungauto.tracking", "action":"com.chungauto.tracking.keepAlive"}]

I don't like that "com.chungauto.tracking" thing :D can I alter these configs? :)
[FYT Android Head Units] danielsdian:
I managed to run the new script on it! Im attaching the report
[FYT Android Head Units] surfer63:
Can you please explain what is missing?

This error message is a known 7zip message, but can also occur due to a corrupted USB-stick. Do you always safely remove it? Did you check it?

The Russians simply use the script from @mariodantas . You can try that one as well.
[FYT Android Head Units] surfer63:
Yes. By altering the AllAppUpdate.bin as described in post #2, you can also change settings in the prop and config files.
[FYT Android Head Units] pmsmiers:
That doesn't work in my case, I know how it works. My first station is 88.0 but for some reason it never starts from one of the 18 stations, it always starts from 87.5
[FYT Android Head Units] surfer63:
You have a brand-new unit. The firmware is from 2023-02-04 13:56:54

7862 unit, ro.build.fytmanufacturer=1 , sys.fyt.bluetooth_type=0.

There are several options to go from here:

- Simply take a Mekede 7862 360 2000x1200k firmware and use the config.txt and fyt.prop rom this fytinfo.

- Take a Mekede 7862 360 2000x1200k firmware and use the config.txt and fyt.prop rom this fytinfo, and combine it with @mariodantas MD-EDITION kernel.

This all based on th assumption that you have a faulty install. If you have a faulty unit, this will not work.

One other question: How hot is it where you life/drive? Did you connect the fan (ventilator) on the back and switched on the AMP setting?
[FYT Android Head Units] danielsdian:
Yeah, I will try to flash the second option that you gave. How do I combine the kernel?

I live in Brazil. Its HOT, but the cooler is always on, even when I take the keys off, its hardwired to one of the 12V lines by the manufacturer.
[FYT Android Head Units] olemann96:
Hello

Is there any way to turn on the device without ignition? Like the original radio. And is there any possibility to show battery voltage in the status line?
[FYT Android Head Units] surfer63:
No.

You have to modify the Systemui.apk
[FYT Android Head Units] surfer63:
Make sure you have a clean FAT32 formatted USB-stick

First unzip the 7862-360-200x1200 firmware to a USB-stick

And as described in post #2:

Unzip the AllAppUpdate.bin somewhere on your computer

copy the fyt.prop, the fyt_build.prop from your fyt_info.tgz in place of those from the AllAppUpdate.bin

Repack the AllAppUpdate.bin

Copy it onto the USB-stick

Copy the config.txt from your fyt_info.tgz onto the USB-stick

From marios unpacked kernel zip:

Copy the "_fmc" folder including contents to the usb-stick

Copy the "lsec_updatesh" folder including contents to the USB-stick. Overwrite when asked for.

Copy the 6315_1.zip to the USB-stick

If desired: copy the bootanimation from marios kernel onto the USB-stick

Flash it.
[FYT Android Head Units] danielsdian:
I tried to unzip the AllAppUpdate.bin but it asks for a password, any ideas?

I downloaded the 7862-A12-9-10-360 firmware...
[FYT Android Head Units] surfer63:
Did you read post #2? That gives the password and also tells you exactly how to repack it.
[FYT Android Head Units] surfer63:
I just realized that it is really simple to use any FYT AllAppUpdate.bin and still do not get errors of the fytmanufacturer and the like.

I could create a lsec cript that might be called "preflash", which copies from the unit the existing fyt.prop and config.txt out of the /oem/app folder and save it to a folder on the USB-stick called "myconfiguration".

Then you copy any AllAppUpdate.bin to your USB-stick.

Then you unzip a script called "flash-script" to the USB-stick.

The lsec6315update would simply flash the AllAppUpdate.bin and this lsec "flash-script" would simply copy your saved/backuped fyt.prop and config.txt back onto the unit.

And upon reboot you have the new Android apps with your own config.txt and fyt.prop.
[FYT Android Head Units] Specy01:
If I understand correctly, it would be a fantastic thing and this would allow those who, like me, are newbies to be able to flash the "AllAppUpdate.bin" without having to make changes to the said file.

If you do thi, many would be very grateful. I hope I understand what you mean. Although I managed to edit that file, but after trying several times. However, if it creates too much effort and time to you, don't break your head too much for others. It is right that each of us commits a little and learns something. It is not right that we have everything already beautiful and ready and do only cop /paste without understanding what we do.
[FYT Android Head Units] danielsdian:
I got it right, but my headunit wont even boot anymore. I'll need to buy another one...
[FYT Android Head Units] surfer63:
Already working on it but it is the (extended) Pentecost weekend, so I have other "obligations".

Scripts and "Readme_First" have been written as that was easy, but I want to first test it myself.
[FYT Android Head Units] surfer63:
I have a Mekede M500s with a ro.build.fytmanufacturer=116 (fyt.prop) and a ro.sf.swrotation=90 (config.txt).

I tested it with a Joying AllAppUpdate.bin with a ro.build.fytmanufacturer=43 (fyt.prop) and a ro.sf.swrotation=270 (fyt.prop and config.txt).

I simply used the "pre-flash" script to copy my Mekede 500s config to USB-stick and then flashed the Joying bin using the "flash" script. It all worked fine be it that some apps had slightly different icons and layout, but that is obvious.

Then I took a Mekede AllAppUpdate.bin and flashed it back.

All good.

You can find both scripts in one zip in post #3 under bullet #4.

Let me know your experience and inform me about typos or unclarities in the "00_Readme" or forumpost "Readme".

Anyone wanting to use this in his/her own scripts: be my guest! If you improve it, please let me know.
[FYT Android Head Units] arca114@gmail.com:
Why buy another unit???
[FYT Android Head Units] Astur_Torque:
Hi

Do you mean 8 GB units are useless because they're not going to use more than 6 GB?
[FYT Android Head Units] Astur_Torque:
Time to move from old Sofia3GR, is literally dragging and everytime it boots you have to change the time ehehe
[FYT Android Head Units] Dekdek1:
@surfer63 hi..

Im trying to flash mekede 6 Pro to my sinosmart unit..

I have read your instruction on copying some line from config.txt and fyt.prop.

I have no problem for editing the config.txt on the new firmware... However, the fyt.prop is in allappupdate.bin.. Do I extract the allappupdate.bin first, then edit fyt.prop, then compress it again before flashing?

Thx in advance.
[FYT Android Head Units] Dekdek1:
Hi.. Anyone have m6 pro plus 1280x720 firmware? I can only find the 2k version firmware on mekede website.

Or. An I use the 2k firmware even though my screen is not 2k?

Tq in advance!
[FYT Android Head Units] Specy01:
Read the first 4 surfer63's posts of this topic. However, the answer to your question is, yes, the procedure is correct.
[FYT Android Head Units] DJBBOX:
Hey guy I have been looking for hours and cant find a single live link that has the MCU files for updating FYT YIN = 116 to the latest or something later than my actual 2020.08.12 MCU version and also I understand the latest android firmware is still an android 10 with modded id to show 12 but what is the latest update for this unit? a link that works could be useful I think I have a mekede\navifly m600 or m600s could you guys point in the right direction?
[FYT Android Head Units] Dekdek1:
does it mean if i wanna flash to other firmware, i need this config file on the root of the usb stick during flashing?
[FYT Android Head Units] arca114@gmail.com:
Just for those who have problems like I had to flash the wrong firmware on the lcd, be very careful when passing a new firmware if you have lcdconfig, delete it.
[FYT Android Head Units] surfer63:
# Deleted #
[FYT Android Head Units] Dekdek1:
But now I want to flash from sinosmart to mekede m6 pro. Should I copy the 6315lcdconfig from original firmware to the new firmware (root of usb stick during flash)?
[FYT Android Head Units] LLIyT_HuK:
Mario can help with that once he gets back into modding. I tried, but standard means does not work. There is a possibility that the output is tied to the MCU.
[FYT Android Head Units] arca114@gmail.com:
This device what is the resolution, 2k?
[FYT Android Head Units] Dekdek1:
But now I want to flash from sinosmart tk mekede m6 pro. Should I copy the 6315lcdconfig from original firmware to the new firmware (root of usb stick during flash)?

My current device is 1280*720
[FYT Android Head Units] Dekdek1:
My current unit brand is sinosmart. The lcdconfig file is from the original sinosmart firmware. The question is whether I include this lcdconfig file when I flashing to other manufacturer firmware.
[FYT Android Head Units] DJBBOX:
"ignored" buahahahaa any input anybody? thanks in advance
[FYT Android Head Units] arca114@gmail.com:
Friend this will not change anything in relation to your screen so you don't need to touch it but I will leave the file available for you, but remember and at your own risk, I do some things in my guinea pig radio to help the community, so sometimes it can go wrong ok.You can flash lcdconfig file with lsec6315update. Make sure your radio is the same screen as this Mipi print
[FYT Android Head Units] arca114@gmail.com:
Save a print like this from your machine.
[FYT Android Head Units] surfer63:
@arca114@gmail.com : You mentioned that you have the entire collection of the lcdconfig files for the Mekede M6Pro and likewise models from other resellers, and that you were willing to distribute them.

I can't find anywhere on the forum if you already did this.

If not, can you please share them.

If you already shared them, please give a link to the post.

EDIT: Never mind, I already downloaded them from another location.
[FYT Android Head Units] j0hn83:
Personally I don't ever upload MCU files.

They don't need updated, it offers absolutely no benefit what so ever.

I have never seen a post where an issue has been fixed by an MCU update on an FYT 7862 device, but I have seen dozens where they have gone wrong.

No manufacturer adds them as standard to these devices.
[FYT Android Head Units] j0hn83:
If you aren't changing the screen, don't use a 6315lcdconfig file.
[FYT Android Head Units] DJBBOX:
thanks man I appreciated it. I am having issues with the unit randomly rebooting and thought could be the MCU as after I reset still persisted but I did flash last night an updated firmware with date of 2022 and for my surprise it fixed other issues that I did not know the unit had like play store and chrome not updating and also a few software issues that I thought were normal for a Chinese unit. I will try and run this update to see if it solved the issue
[FYT Android Head Units] babkha:
hi all! I'm new here, so I apologize in advance for any inaccuracies. Does anyone know where in Europe to buy a head unit in UIC7862 for Honda Jazz 2003? for example MEKEDE. I don’t want to buy in China, because I pay a lot for customs clearance. Thank you
[FYT Android Head Units] LLIyT_HuK:
For example, by updating the MCU on many devices, a bug with incorrect backlighting of buttons on the side panel was fixed.
[FYT Android Head Units] Astur_Torque:
Same but Corsa D
[FYT Android Head Units] Clandaries:
Buy at Aliex..... Send from Germany, Poland or France and so on is possible.
[FYT Android Head Units] babkha:
Thanks, I would to receive same links
[FYT Android Head Units] arca114@gmail.com:
Hello, I sent you in the private conversation, the website did not arrive???
[FYT Android Head Units] arca114@gmail.com:
Downloads

FYT Platform Sofware download7862/9863 9"&10" 2K 2000*1200 UI Package 7862 Universal UI Package 1024*600/1280*720 FYT7862/9863/7731 Physical Buttons MCUkey Match Learning

datongcaraudio.com
[FYT Android Head Units] surfer63:
Yes, I received that one. Thank you.

I thought you mentioned that the lcdconfig files were just a bunch of config files in a zip. That is how I downloaded them from 4pda.

I can't even find them inside the 3 files on that download page.

But I downloaded 40~60 config files from 4pda
[FYT Android Head Units] LLIyT_HuK:
I apparently received the link as a bonus in private))
[FYT Android Head Units] arca114@gmail.com:
Yes, there are several files but it's enough to help..
[FYT Android Head Units] matrixx1:
Hi. I have Mekede M6 Pro Plus. I have a question regarding wifi. My unit can hotspot via 5Ghz Wifi, but it cannot connect to an 5Ghz hotspot of an iPhone? Does the 5Ghz wifi only work for thetering?
[FYT Android Head Units] louforgiveno:
It works on 5 for me. I vaguely remember seeing a post similar to yours and if memory serves it had to do with the 5g frequency of the country the individual was in that was incompatible with the head unit.

I recommend removing the password credentials from the iphone hotspot to test if you can get it to connect.
[FYT Android Head Units] j0hn83:
5Ghz works on these units but does not support WiFi channels 134 and above.

My phone tries to use channel 149 for WiFi tethering and it will not connect.

It also may not support some channel widths but I haven't checked this yet.

Use an app like WiFi Analyser on a different apple/Android phone to see what channel number and width the WiFi is on your iPhone.
[FYT Android Head Units] LLIyT_HuK:
Comrades, is there any point in using 5Ghz on the head unit?) Slightly increase the exchange rate, but significantly worsen the quality of communication.
[FYT Android Head Units] louforgiveno:
I thought i read that the 2.4ghz can cause bluetooth connectivity issues....not my experience, but i thought it was something that been determined a while back as something to be wary of.
[FYT Android Head Units] j0hn83:
5Ghz WiFi works flawless on my Mekede M500s.

It doesn't worsen the quality of communication at all.

My only gripe is my Chinese Xiaomi phone tries to hotspot a 5Ghz channel that the head unit does not support (channel 149). This means I need to do a workaround sometimes to use 5Ghz.

That's the fault of the phone. WiFi channel 149 is not used here.

I just ran multiple speed tests on my unit trying the different options.

Bluetooth Tethering: 0.4Mb/s down 0.5mb/s up

2.4Ghz WiFi: 2.7Mb/s down 8.1Mb/s up

5Ghz WiFi: 58Mb/s down 54mb/s up
[FYT Android Head Units] WarSpaz:
Could you please share the workaround to use 5ghz with your Xiaomi? :)
[FYT Android Head Units] j0hn83:
If your Xiaomi phone is already connected to a WiFi network, it will create a hotspot on the same channel.

This means when I get in the car at home I am already connected to my home WiFi (5Ghz channel 36) so the hotspot uses the same channel.

To use 5Ghz any other time I need to start a hotspot on the heat unit, connect to it with my phone, then enable the hotspot on my phone.

Basically Xiaomi phones (including Poco phones) must be connected to 5Ghz WiFi before starting the 5Ghz hotspot.

It's frustrating, but it's the phones fault for using such an odd, high wireless channel by default.
[FYT Android Head Units] WarSpaz:
I see! Nice and easy explanation, thanks :)
[FYT Android Head Units] Matt Devo:
So I've read through most of the forum here and on 4pda, and haven't seen anything discussing removing (or at least hiding in the launcher) some of the unless bundled apps like the voice assistant, touch assistant, etc. Is that something I need MD's kernel and root to do, or can I just script it as part of my custom USB install stick?
[FYT Android Head Units] hanichl:
JOYING has released new firmware 2023-05-23

https://www.joyingauto.com/blog/category/updated-files-released/
[FYT Android Head Units] Ahto Simakuutio:
Some launchers can do that. I'm using Car Launcher Pro which offers hiding unneccessary apps in the app drawer.

More serious solution would be to create a script to delete or rename the apk's such that they are not found by the system.
[FYT Android Head Units] surfer63:
There are two solutions:

- Unpack the AllAppUpdate.bin, remove the unwanted apps, repack and flash.

- Use an lsec script that simply removes or disables the apps from the unit.

The second option is actually the simplest and can be used on any "existing" FYT system, where the disabler has the option to enable the app again (requires another script). See attached for the screenbutton an "app_remover" and "app_disabler" script. Extend for your needs.

Note that in few occassions the numbers in front of the package name can be different based on the fytmanufacturer id. Joying for example often has something like "190043001_com.syu.radio.apk" instead of "190000001_com.syu.radio.apk".

I hope these scripts are clear.

Edit: And when modifying these scripts on Windows, use a good editor like notepad++ and not Notepad from windows.
[FYT Android Head Units] Matt Devo:
gracias, I already had something similar, but still not 100% sure how to derive the package name or path. The package name I found an app to show.

for example, in your script you reference the touch assistant as `/oem/priv-app/190000000_com.fyt.screenbutton/190000000_com.fyt.screenbutton.apk` but how did you get the path? in AllAppUpdate.bin, the file is located in the `app` subdir, not `priv-app`

and likewise, is there an easy way to install user apps via the update script as well?
[FYT Android Head Units] surfer63:
You are absolutely right. I apologize for my sloppiness. I simply took one of my own scripts and only changed the "190000000_com.fyt.screenbutton/190000000_com.fyt.screenbutton.apk" FYT part, because I had used my script for a priv-app.

I corrected the scripts in above posts.

Thanks for pointing this out.

With regard to the package name: It is 99% of the time the name after the long number for the FYT apps. FYT has taken over SYU in 2015/2016. FYT was the hardware builder. SYU the Android (and before that the WinCE) software builder. That is why most apps are called "<number>.com.syu.<app_name>, while some of the newer apps, also for Teyes, are called "<number>.com.fyt.<app_name>".

And indeed: there are apps to show the package name (my FytHWOneKey apk for example).

And if you use play.google.com from the browser on your PC and you search for example for "Magic Earth", it will show your search result and when you click the app, you see in the address bar something like https://play.google.com/store/apps/details?id=com.generalmagic.magicearth.

The last part is the package name (like for Google Maps: https://play.google.com/store/apps/details?id=com.google.android.apps.maps)

Of course this does not work for the FYT/SYU apps ;)
[FYT Android Head Units] Matt Devo:
thx again. Any thoughts on installing 3rdparty user apps via the update script? Thinking launcher, file manager, icon pack, etc
[FYT Android Head Units] surfer63:
Actually the same. Download Marios MD-edition. It installs fmc, which is a 3rd party app, in the same way. Mario makes it a private app (/oem/priv-app), but that is not necessary at all for any normal app.

Or have a look at my carlink installer. It also install libraries.

Edit: Updated the incorrect link.
[FYT Android Head Units] Pfeffernuss:
Absolutely pretty amazed that the new Android Auto (Coolwalk / split screen) works fine on my Joying head unit. Get in the car, phone in pants, unit auto connects, shows live Maps and starts playing audio through YouTube Music.

All wireless and without enabling tethering as well.

Reads aloud new Whatsapp messages etc. Very pleased 😎
[FYT Android Head Units] Matt Devo:
thx. I had seen both of those, but I wasn't sure if there was a difference in installing as a system app vs user app. Guess it doesn't matter if I install them as system apps :)
[FYT Android Head Units] Pfeffernuss:
Unable to find firmware...

Is there another way you can link to it please?
[FYT Android Head Units] hanichl:
Link is corrected, please retry