yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] Cavalier Condorelli:
I opened the com.syu.canbus.apk file with 7zip and I changed the images files directly inside the archive, then I substituted the original apk with the modified one in the headunit filesystem and everthing worked as expected.

BUT I also need to change the strings.xml file so I have to decompile and recompile the com.syu.canbus.apk. I tried to use both apkeasytools and APKToolGUI but when I go to replace the modified com.syu.canbus.apk file in the filesystem of the headunit this time the application turns out to be not installed. What am I doing wrong?
[FYT Android Head Units] Ashraf MK:
(Solved)

Hi..I have a question why all the Bluetooth devices detected as noName?

However, the device can be paired with the player.

I’m using AllAppUpdate PeaceOS with latest MD edition kernel with mainservice dated 26-4-2024.

Thanks in advanced.

Fixed. Re-flash the kernel with config.txt.
[FYT Android Head Units] surfer63:
The lsec6316update is an executable. Of course it will contain the text fail and probably also success, depending what the outcome is.

Did you read the first posts of this thread? It tells you that the AllAppUpdate.bin is an encrypted zip file. Treat it like that.

And about the flashing: Read this thread. It has already mentioned many times that the dm-2 error is always there and completely harmless.

If you had searched on dm-2 you would have found many hits.
[FYT Android Head Units] surfer63:
Did you simply try to side load it, or did you flash it? The latter will only work. You cannot simply install it "the first time".

Secondly: did you sign it with the platform keys? If not, you can still flash it but your launcher will not work at all.
[FYT Android Head Units] surfer63:
You need to sign it with the platform keys first if you really decompile/recompile.
[FYT Android Head Units] Hminhh:
Mod edit - translated by https://translate.google.com/. Oswald Boelcke, Senior Moderator.

Looks like I haven't signed the app yet. I will try again. Is there any way to try exporting the apk file on my computer? Thank.

I mean, after the mod is finished, is there any way for us to test it on the computer?

*********************************

Có vẻ như tôi chưa ký ứng dụng. Tôi sẽ thử lại. Có cách nào để thử xuất file apk trên máy tính của tôi không? Cảm ơn.

Ý mình là sau khi mod xong thì có cách nào để chúng ta test trên máy tính không?
[FYT Android Head Units] Cavalier Condorelli:
Where can I locate the platform keys required to sign the recompiled apk in the tool?

I did sign it with the default keys provided by both the mentioned tools.

I did not zipaligned the signed packages
[FYT Android Head Units] Tigrowski:
Is there any way to increase the microphone gain on this device? In my case, the volume is tragically low, both on the built-in microphone (which would be understandable) and the external one that's attached to my headliner. It's so low that I basically need to yell the whole call to be just audible enough to be able to talk with me freely :/

Do you know of any way of fixing this?
[FYT Android Head Units] surfer63:
English is mandatory in this forum. Switch off auto-translate.
[FYT Android Head Units] surfer63:
You should not use the test keys. You need to use the standard google android keys.

Explained and attached to the first or second post of both my Launcher34 mod thread and to my modded SystemUI thread (actually 90-95% of that mod is done by @LLIyT_HuK. I only modded the split screen).

The keys are also somewhere in the @KoTiX2 thread from his NavRaadio.
[FYT Android Head Units] Badger50:
Thread cleaned.

Greetings to all. As a friendly reminder, we are all required to treat each other with respect without the "snarky" replies and accusatory tone as stipulated in XDA Rule 2.3:

Spoiler content hidden.

Please remember that it is always better to "report" a post you think violates the Forum Rules, rather than replying to them.

Thank you for your cooperation, and a pleasant day to all.

-Regards: Badger50
[FYT Android Head Units] Oswald Boelcke:
Hello and good morning, @Hminhh Welcome to XDA! I hope you'll always get the support you require and have enjoyable times on our Forums.

However, as a one-time courtesy I've translated your above post. With reference to rule no. 4 of the XDA Forum Rules, please post in English or add at least an English translation to your Vietnamese posts.

Spoiler content hidden.

Regards

Oswald Boelcke

Senior Moderator
[FYT Android Head Units] reosman:
Where can I find the latest software for 2024 or can anyone share it?
[FYT Android Head Units] Hminhh:
Sorry I didn't pay attention to the automatic translation, I just wanted to ask is there any way for me to review the results I just modded on my computer?
[FYT Android Head Units] gordgelin:
probably no since these are not just some random android apps and they just won't work in android emulator but you can try
[FYT Android Head Units] Hminhh:
specifically it is a launcher that I modded
[FYT Android Head Units] gordgelin:
all FYT oem launchers have deep integration with core system and services so they won't work in emulator maybe with some rare exceptions, you can check yourself
[FYT Android Head Units] Ohm711:
Is there a way how to enable realtek BT IC without original firmware? BT 1 in confing is no longer working. I asked the seller for firmware file, but he is ignoring me.

Thanks.
[FYT Android Head Units] edris90:
To any with insight that would care to share.

How do I find my uuid to my fyt mekede m6 pro unit running peaceos?

I want to join the dudu OS beta and I need it to do that.

Also where is the uuid stored?

So I can back up that part of the flash just in case it's ever corrupted.
[FYT Android Head Units] j0hn83:
It's the serial number listed in about device section.
[FYT Android Head Units] edris90:
Thank you for the reply.

I had mirrored my question in the Dudu telegram thread.

They identified "machine quick eesponsecode" as the 32 digit alphanumeric UUID

So if anybody else is trying to identify their UUID there you go.

Still find it odd that no one has identified where that is for simple DD back up , modification or restoration.

With other phone-like socs it's one of the first things identified to keep it safe to tinker.
[FYT Android Head Units] marchnz:
Ask question in dudodudu thread?
[FYT Android Head Units] gordgelin:
it is hardware id and can not be "simple DD" backed up etc
[FYT Android Head Units] RustyWar:
would someone be able to help me find the Video Output Settings on my unit sold by SLASUKOR its just not there infract most of the factory settings listed here are not.. any help is appreciated thank you
[FYT Android Head Units] gordgelin:
these devices do not have video output, only with 3rd party usb dongle, also your device is SC7731/UIS8141E and does not belong to this topic

of course there is not android 12 also. it is 8.1
[FYT Android Head Units] volkslove:
I need some assistance with a major F up!! I recently changed my android head unit to a Hiirode branded uis7862 6+128G 360Cam. (The previous unit did not have a 360 Cam.)

Anyways I did the "AllAppUpdate.bin" which I did using the USB stick from my previous unit and believed it was successful. Unfortunately the AllAppUpdate.bin did not work because of an error that flashed on the screen which I missed and later discovered was a "6D DDR!Pls use lsecXXXupdate file after 2022-11-011"

I tried flashing the firmware (MD-edition) which did not work as planned and thereafter thought I would revert to the previous by using the backup from AllAppUpdate.

Long story short _ I do not have a backup of the previous setup and all hardware is not working as I pushed the backup files from my previous non-360 cam head unit into the new one.

I have asked the reseller for the stock firmware but I am not confident he will provide it. Is there any possibility of reviving my head unit.

Sorry for the long post...
[FYT Android Head Units] ka-topwayts10:
I have the below in my skipkillapp.prop. Does that mean that I have Teyes FYT?

Script:

ru.teyes.update = -14

cn.teyes.online = -14

mdm.tw.com.mdm = -14

com.ms.ms2160 = -14

ru.yandex.yandexnavi = -14

com.syu.onlineradio = -14

com.yf.teyesspotif = -14

I searched everywhere in other files but couldn't find anything pointing to Teyes.
[FYT Android Head Units] surfer63:
No. My mekede has the same. You have to find the manufacturer id. if it is 95 it is Teyes, otherwise it is not.
[FYT Android Head Units] marchnz:
No body knows what the unit is, post screenshots of Android System information including MCU version or use the script Surfer developed to make your life easier
[FYT Android Head Units] ka-topwayts10:
Do I have to unzip the 6316_1.zip on the USB root or just keep as it is along with the backup 4 files?

I also see another zip file inside the 6316_1.zip file which is compatibility.zip, do I unzip this too or just keep the entire 6316_1.zip as it is?
[FYT Android Head Units] volkslove:
Thank you for the response. Hopefully the attached will help. As mentioned I do not have a backup of the headunit prior to uploading the incorrect unit backup. i am not sure if the results contained in the attached are inaccurate because of the incorrect backup being restored to the headunit.

The original OS was a fake android 13 and after the mistake it is reflected as fake android 12 which is incorrect.
[FYT Android Head Units] surfer63:
Just like it says: Download the latest firmware from Mekede. Get the lsec6315update out of it, and use that one.

Assuming you have a standard FYT.
[FYT Android Head Units] Ashraf MK:
Hi.

I just flashed my firmware and I found my Bluetooth is not functioning.

Unable to rename the device and unable to detect any devices.

I checked the sys_fyt_bluetooth_type=0 in the config is correct with my player. Then I changed to type=1 also not working.

What is the problem and how to fix it?
[FYT Android Head Units] surfer63:
You created your own mod and you are not telling us what you changed?

You modified a Teyes firmware for a non-Teyes unit, or the other way around?
[FYT Android Head Units] Ashraf MK:
This is firmware for 360 player and not a Teyes firmware. The manufacturer ID = 1.

The modded only the systemUI (non teyes) and additional UI.

Btw I’m not using the 360 MCU even though the player equipped with 360 module.

But I tried this firmware with other 360 player and also got the same problem with Bluetooth (the player that I extracted the AllAppUpdate).
[FYT Android Head Units] volkslove:
This was extremely helpful and sorted it out. Now there is just a message saying UI MCU does not match. I remember finding a list of all possible manufacturer numbers but for the life of me I cannot find it again. Since I do not know the original manufacturer number I am just wondering how many options there are to try? 😅
[FYT Android Head Units] surfer63:
Too many.

Do you know your brand? Otherwise use 1 which is universal.
[FYT Android Head Units] volkslove:
Brand was "Hiirode".

Does the information in brackets mean anything at the end of the message, i.e. (YIN)? Is it saying that YIN is the MCU and I should find the number for YIN? Or it saying that the current incorrect firmware is for YIN and is incorrect?
[FYT Android Head Units] surfer63:
YIN is mostly 116 or 1, but not always. I simply don't know hirode.
[FYT Android Head Units] Ashraf MK:
My bluetooth problem is fixed.

I flashed back with my own config (Bluetooth id=0).

Then I tried with the 360 player’s config, the Bluetooth and player were running well with the additional 360 floating shortcut on the screen.

I don’t know what was wrong with my Bluetooth earlier.

However, the Bluetooth for 360 player that I flashed with this firmware is still not good. I suspected its Bluetooth module was faulty because the Bluetooth still not good after I rolled back the backup files.
[FYT Android Head Units] Ashraf MK:
Talking about YIN MCU, is it possible to flash from YIN to NOR MCU with the same FYT 1?
[FYT Android Head Units] volkslove:
Well got it to work with (1). A strange issue is any idea why the 360 model is translucent? Something new. Wasn't like this before I f'd it up
[FYT Android Head Units] j0hn83:
What's incorrect? If it's identified as API 29 then it's Android 10

If the release builds in system info starts with a Q then it's Android 10.
[FYT Android Head Units] volkslove:
Thanks
[FYT Android Head Units] Mibuix0r:
I just get this pop up? If I hit start it goes to the android guy screen and says "no command". I am on a Atoto P9 uis8581a
[FYT Android Head Units] j0hn83:
Format the flash drive as FAT32 and copy the files over again or try another flash drive. Something is corrupt or formatted incorrectly.
[FYT Android Head Units] Mibuix0r:
Appears I needed to use the USB-A on the fast boot connector and not the USB-Cs on the actual unit.
[FYT Android Head Units] surfer63:
Hi, these units do not have a fastboot connector, just 2 or 3 USB-A connectors.

And if you have a USB-C port, what kind of unit do you have? As far as I know the FYT7862/8581 units do not have a USB-C port.

Only the 7870 (800/880) series have a USB-C and in that case my script will not work.
[FYT Android Head Units] j0hn83:
Just Atoto changing the interface. It's USB 2.0 by the sound of it.

And Atoto call waking up from sleep "fast boot" and they even call 1 of their cables a "fast boot connector".

It looks like a fuse tap kit for tapping in to B+ and ACC in the fuse box.

Nothing to do with Android fast boot though.
[FYT Android Head Units] Mibuix0r:
Yeah this is with their new P9 that came out a few months ago.
[FYT Android Head Units] AstroScience:
Hey guys,

my unit (7862S - FYT 1) loosing some settings after sleep, especially in equalizer and boot sound volume setting for BTPhone. No matter what I try, after sleep, those settings get back to defaults.

So far I've only flashed MD kernel and didn't messed around with the unit too much.

Is there anything can be done about it?
[FYT Android Head Units] marchnz:
Reload factory firmware?
[FYT Android Head Units] AstroScience:
After long time refusing, the seller sent me this update and I want to share.

Can anyone please tell me more about it, for which units this one is? Or reseller just downloaded it somewhere and keep silent about it?
[FYT Android Head Units] Ashraf MK:
Hi..I have a problem where my player suddenly crashes then I perform the factory reset. But the player is stuck on the boot.

Then I flashed back the firmware with the backup.

All the flashing went well with no abnormality.

But the player is unable to boot and appears the text “fastboot mode” after the boot animation.

How fix the problem? Thanks.
[FYT Android Head Units] gordgelin:
try to flash stock firmware (no backups etc). but probably flash memory dead
[FYT Android Head Units] Kwen:
on 4pda someone said that the uis7862 worked on band 4 AWS 1700/2100 in Mexico, have anyone confirmed this to be true? I plan to use it on the Videotron/Fizz network in Canada
[FYT Android Head Units] marchnz:
Guess you have limited ways of validating, including things such as buying one, contacting person who made comments and asking seller.
[FYT Android Head Units] Kwen:
ok so there seems to be actual Android 12 firmware for the UIS7862 now, anyone tried it? Or is that also a fake?

May need a full wipe?

On the mekede site

MKD_7862_安卓12_国外UI22_360_横屏1280x720兼容1024x600_20240401_lzp.rar

1 file sent via WeTransfer, the simplest way to send your files around the world

wetransfer.com

Link name is "MS Android 12"

File name is "MKD_7862_安卓12_国外UI22_360_横屏1280x720兼容1024x600_20240401_lzp.rar"

Which translate to "MKD_7862_Android 12_Foreign UI22_360_Horizontal screen 1280x720 compatible with 1024x600_20240401_lzp.rar"

File list:

6315_2.zip

AllUpdateA12.bin

config.txt

lsec6315updateA12

updatecfg.txt (contains formatdata)

I also grabbed the on on 4pda, same file structure

A12_7862_UI6,10,36三合一_1280x720兼容_国外_无碟_Android12_带小窗口_zl_20230423.zip

"A12_7862_UI6,10,36_3in1_1280x720 compatible_foreign_discless_Android12_with small window_zl_20230423.zip"
[FYT Android Head Units] Warlord721:
Maybe you should have started a new thread for this, especially if it is legit.
[FYT Android Head Units] j0hn83:
Been around for a long time.

Unless things have changed in the last few weeks, my knowledge of things is as follows....

It's not possible to update from Android 10 to Android 12.

This is for units that ship with Android 12. It's locked down like Android 13 on the 7870 devices. Little uptake, little support.

Even the likes of Mekede/Teyes/DuduAuto can't update an Android 10 unit to Android 12. It would need sent back to FYT.

These Android 12 units showed up here months ago

A thread from November
[FYT Android Head Units] gordgelin:
it is locked EVEN MORE than 7870, actually they have stepped down a bit with 7870 )))
[FYT Android Head Units] TiagoMoreira:
help me, I installed fyt mariodantas and then PeoceOs, cool, in Peoce I had a problem with my canbus, but as I backed up my original fw, I went back to the original, so my bluetooth is not working, when I looked in the specifications it is non-existent . Does anyone know how to solve this, UIS8581a bluetooth version blink_2161 release/2022
[FYT Android Head Units] marchnz:
Read on and enjoy xda
[FYT Android Head Units] Johnny#C#:
Hello, I need some help with two issues. I own a Navifly 7862.

1. Trying to solve my BT weak audio issue I changed the OEM app 190000010_com.syu.bt following the instructions from post #2 . I use 7862lsec.sh to remove the old app and replace it with a newer from AllAppUpdate.bin in MEKEDE download site.

#!/system/bin/sh
rm -rf /data/dalvik-cache/profiles/190000010_com.syu.bt
rm -rf /data/dalvik-cache/arm64/*190000010_com.syu.bt*
rm -rf /oem/app/190000010_com.syu.bt
rm -rf /data/data/190000010_com.syu.bt
cp -r /storage/sdcard1/OEM_APP/* /oem/app/
chown -R 0.0 /oem/app/190000010_com.syu.bt
chmod 755 /oem/app/190000010_com.syu.bt
chmod 644 /oem/app/190000010_com.syu.bt/190000010_com.syu.bt.apk

The result is that Bluetooth app does not launch properly, when it starts just shows an empty screen. Is there something I could do to fix that?

Also I realized that bluetooth audio is not managed by this app, I use phone and get sound to my speakers even without this app working. So the weak BT calls audio issue is located somewhere else... 🤔

2. I had recently used a custom kernel (MD-fmc) that could enable/disable root binaries. Some of my apps stopped launching due to protection on modified firmware. So I replaced the kernel using my old 6315_1.zip and also 7862lsec.sh to remove ("rm -rf ...") custom fytmanagementcenter and media/bootanimation. The update completed but my apps still complain about modified firmware and data and privacy protection. Any ideas on that??

In every change my updatecfg.txt only includes

#test
twipe_cache

I don't know if any other wipe type is needed to work, but I prefer not to lose any of my data and installed applications. Any help would be appreciated!
[FYT Android Head Units] surfer63:
Did you sign your app with the android test keys or with the android default keys, or not at all?

And what did you actually modify? You tell us absolutely nothing.

Removal of the cache does not remove all system settings.

So yes: you do another wipe type and you will therefore lose settings and data.

Next to that: The FMC app makes modifications to files in the /oem partition which have nothing to do with normal settings. Did you undo your changes before you uninstalled the fyt management center?
[FYT Android Head Units] Johnny#C#:
Thanks for the reply.

I didn't sign it, actually I have just followed the #2 post instructions to replace oem apps. I used 7862lsec.sh to remove fyt management center and also change my 190000010_com.syu.bt app and 190000000_com.syu.ms

The script I first followed is:

rm -rf /data/dalvik-cache/profiles/com.mariodantas.fytmanagementcenter*
rm -rf /data/dalvik-cache/arm64/*com.mariodantas.fytmanagementcenter*
rm -rf /oem/priv-app/com.mariodantas.fytmanagementcenter*
rm -rf /oem/priv-app/com.mariodantas.fytmanagementcenter-signed-platform
rm -rf /oem/priv-app/com.mariodantas.fytmanagementcenter-signed-platform/com.mariodantas.fytmanagementcenter-signed-platform.apk

rm -rf /oem/media/bootanimation*

rm -rf /data/dalvik-cache/profiles/com.syu.ms*
rm -rf /data/dalvik-cache/arm64/*com.syu.ms*
rm -rf /oem/app/190000000_com.syu.ms

rm -rf /data/dalvik-cache/profiles/com.syu.bt*
rm -rf /data/dalvik-cache/arm64/*com.syu.bt*
rm -rf /oem/app/190000010_com.syu.bt

cp -r /storage/sdcard1/_app/* /oem/app/

chown -R 0.0 /oem/app/190000000_com.syu.ms
chmod 755 /oem/app/190000000_com.syu.ms
chmod 644 /oem/app/190000000_com.syu.ms/190000000_com.syu.ms.apk

chown -R 0.0 /oem/app/190000010_com.syu.bt
chmod 755 /oem/app/190000010_com.syu.bt
chmod 644 /oem/app/190000010_com.syu.bt/190000010_com.syu.bt.apk

After that I used a more simplified 7862lsec.sh (as I said in previous post) to replace again 190000010_com.syu.bt, because it didn't work. I last used my bt app from AllAppUpdate.bin that previously used.

I hadn't done any critical change. Of course before uninstall I had removed root binaries using the FMC. Then I used my previous 6315_1.zip together with 7862lsec.sh, lsec6315update and updatecfg.txt (#test, twipe_cache).

I can provide any other information and steps that are useful
[FYT Android Head Units] surfer63:
If you modify an app you always have to sign it again. Unless you simply unzip, replace an image, and rezip.

If you modified anything with regard to "non-binary" data like smali, xmls or something else, you need to re-sign.

your script(s) are OK.

The boot animation (or boot logo) have nothing to do with your issues.
[FYT Android Head Units] Johnny#C#:
How can I sign it?? What's the procedure? Or, if I take the last Allappupdate.bin, rezip it with new apps (include the other) and update it, will it work or will affect my entire setup?

I try not to lose my installed apps. I try to fix my issues with BT audio and the privacy protection for apps, without losing everything.

I know about boot animation, has nothing to do, I just wanted to remove it.
[FYT Android Head Units] surfer63:
Search.

See here and here
[FYT Android Head Units] TraxOf63:
Hello, what are these settings for? I have the impression that nothing changes regardless of the values. In fact, what values should be applied? THANKS
[FYT Android Head Units] surfer63:
So you did search through all the 30+ hits you get when searching on vcom? And you did not find an answer in those 30+ hits?

Search.

avdd and vcom are color calibration. It is weird though that you see the options on a grey-scale screen.
[FYT Android Head Units] TraxOf63:
no, the answers found were not very clear. However, here I have my answer ;) thank you very much!
[FYT Android Head Units] surfer63:
I only now realize what you are saying/typing.

Did they make the latest firmwares of the 7870 a bit less "locked up"?

What is now easier to do, or how did they "step down"?
[FYT Android Head Units] gordgelin:
no, they made 7870 a bit less locked up comparing to 7862 Android 12.
[FYT Android Head Units] hal752:
This could be due to the unit loosing power completely. Maybe comfirm your acc and live power is correct.
[FYT Android Head Units] Mibuix0r:
Is there a way to get a persistent notification to show in the status bar by the clock? Would like to have a temperature from a weather app display up there but it seems to be blocked on the unit. Do I need a different launcher or will that not help either?
[FYT Android Head Units] StarFla_er:
Hello, sorry for my English.

I have Kingbeats K2+ 3/32, i install TWRP first and do all backup. After this I have mistake I put another recovery.img (from CC2) not K2+.

After rebut I get black display and buttons lighting😥

If turns parking lights on/of, buttons lights(see video I put in YouTube).

PC see it SPRD U2S Diag

What I can to do?

I see in this forums maybe problems in lsd config?

posted on YouTube, FYT works
[FYT Android Head Units] StarFla_er:
Maybe someone knows how to enable fastboot through in FYT connected usb keyboard?