yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
See @j0hn83 's answer above.

And next to that: Where should one answer? You get two more and more deviating threads if one user starts to answer thread 1 and another user starts to answer in thread 2. And if you get the exact same answer, then one of those users trying to help you has wasted his/her very valuable time on some answer that was already covered in the other thread because some user who doesn't care in wasting other persons time, asked twice (or even more).

That's why it is not allowed. I assume you did not think of that, but please do in the future.
[FYT Android Head Units] TauTau:
how can I check this?

"Always look at the API/SDK version. If it says API/SDK 29 it is is Android 10. Real Android 11 is API/SDK 30."
[FYT Android Head Units] TauTau:
my previous unit (Skyshadow, TS18) woke from deep sleep when I put the key into the keyhole (Benz S211) without turning. My new FYT (7862S) requires me to turn the key to position 1, though i can hear the fan turn on when i put the key in (so there is power to the unit). Can this behaviour be changed? I liked it the way it was with the TS18
[FYT Android Head Units] mastrv:
It depends on the wiring for your car.

I have a Kia Sorento 2012. I have the schematics for the radio and know what each wire does. For the original car radio, there was a wire that was activated/voltage appeared when I unlocked any door. This wire provided power to the original radio before I started the car. I knew this/found it out from the schematics and by hearing the DVD/CD spin up when I had left a DVD in the radio. I tell you this because perhaps the wiring for you car has something similar. So, it may be possible if you know what each wire in your wiring harness does and yours has something similar to what I described. I'm guessing you or the installer wired your new unit normally, not using this extra wire. If this wire, or something similar, does exist, it may be as simple as using this wire instead of the accessory wire to power your FYT. It may not be anything like this, though.

I would recommend you find/get the schematics for your car or go back to the person that had installed the TS18 to see if they can provide you any info. Maybe go to the parts counter for you car dealer and ask them to see the schematics on a screen. Nowadays, parts counters have everything digitized and easy to lookup.
[FYT Android Head Units] TauTau:
hm, both units were installed by me, there was no special wire involved. I used the same wiring for both units (the S211 is special, since the wiring is in the trunk)
[FYT Android Head Units] Rabidoe:
I have been fighting an issue in my unit that when I use bluetooth calls or facebook messanger the person on the other end can hear a bad echo of themself. I have done the internal mic ribbon disconnect and tried the config.txt settings to no avail.

I have disabled my phone mic while on a bluetooth call and they cannot hear me which leads me to belive the units external mic is not working. However if I disconnect my phone from the unit and then call using messanger the units external mic works however the echo is present. If I use a voice recording app on the unit the echo is not present in playback.

It seems rather than a mic issue its is somehow that the sound from the voice calls gets feed back into the outgoing sound internaly somehow.

Has anyone had a bad echo issue and worked out how to solve it?

I am at a loss now, tried everything. Ready to bin the headunit...
[FYT Android Head Units] 3PI:
The echo problem usually occurs because the microphone you are speaking into has too much gain (or is too sensitive), and because the listening volume of your speaker is too loud.

at high volumes, the microphone picks up some of that audio signal and an echo occurs.

Try lowering the conversation volume and adjusting the config.txt settings file microphone gain lower
[FYT Android Head Units] mrmidnight:
Hey all, I have a cc3 2k and I'm wondering if I can actually flash another brands firmware to it. Thought I would enjoy all the teyes stuff but there's a few things that annoy me, like that teyes assistant.

Thanks!
[FYT Android Head Units] Clandaries:
Try it and tell us. Would like to know it to 😁
[FYT Android Head Units] surfer63:
I assume you can do this. Should not be a problem.

Or you take an lsec script to remove the /oem/app/TXZ* or only the /oem/app/TXZAIPal

Also set in your config.txt "persist.fyt.launchertzyguide=true" to "persist.fyt.launchertzyguide=false".

Edit: I forgot that those stupid Teyes firmwares have the AllAppUpdate.bin as part of their system partition, which makes it read-only. Only Teyes limits their users in that way (and in quite some other ways). Even more reason to flash another firmware ;)

And you can indeed flash it with a firmware that doesn not contain the TXZ apks.

And if it doesn't work, you simply flash your Teyes firmware back. As long as the recovery partition is OK, you can recover from any soft-brick. But I can't imagine that will happen. So many users have flashed the Teyes software to their Joying or Mekede (and back again), why not the other way round.
[FYT Android Head Units] mrmidnight:
Awesome! Since I have one of the 2K models is there any particular firmware I need to be looking for when looking at other manufacturers?
[FYT Android Head Units] Racker_CRO:
How can I check if my M500S needs an update? Firmware or MCU? Where can I find just MCU update (if possible)? I've checked on Mekede software page and there is only this FW "7862-A12-wbt-9-10.rar" for 7862 9'' 10''.

This is my unit info

I guess the update will wipe all and set the unit to factory default?

Thnx.
[FYT Android Head Units] surfer63:
Your app version mentions 09 Mrch 2023 which is "only"a week older than the latest 7862-A12-wbt-9-10.rar file which is available. So no real need to upgrade.

There is no MCU update and why would you do that? What problems do you have?

I simply flashed the latest "MKD M6PLUS-UI29R-4L-8502k-20230602-lzp.rar" from 13 May which is actually an M6 Pro firmware. I only replaced the config.txt with the config.txt from my M500S (with a few personal tweaks).

The normal updatecfg.txt contains the "twipe_data" which removes all 3rd party apps, updates from system apps (Google Maps, for example) and all app data and settings.

I tried with "twipe_cache" to keep my settings, 3rd party apps and app data, and that worked fine. If it gives you an unstable system, you either need to reflash with twipe_data, or only flash a config.txt and updatecfg.txt with twipe_data.
[FYT Android Head Units] maciej.kubiak:
Ok, i made something with microphone signal. If i installed Microsoft launcher i saw box options. There is nic options to switch but Chose aby mic do nothing. Both still working. I have some idea - on originals wire is Black cable (in toyota its signal from mic- (19 pin). Maybe this is clue of problem? Now i know that some options are hidden in launcher but they are available on another launcher. So If this option doesn't work, isolating the Pins of installed mic of this unit disable both mic, maybe this 19pin (ground/minus od toyota mic OEM) made problems?
[FYT Android Head Units] surfer63:
As already mentioned earlier: it depends if you have new hardware (M6Pro) or older hardware. I even asked you what you have. You didn't answer that.
[FYT Android Head Units] maciej.kubiak:
8581 unit, no name in toyota Avensis t27 2016 year manual gearbox. I made everything from this thread and q&a methods alternative.
[FYT Android Head Units] surfer63:
The 8581a doesn't have the option to switch between internal and external microphone and I see you already taped the internal connection.

I can't help you with Toyota specific issues. Maybe another user with a Toyota,
[FYT Android Head Units] maciej.kubiak:
So i wrote about it. P6pro have switch microphone option. In my unit is already after changing launcher from build to Microsoft launcher and then in settings is available this switch. But its doesn't work (switch) - they work both all the time. But If I isolated with tape this 2 circuit od interior mic, both doesn't work. The mic OEM toyota i will make to Jack with Amp voltage 5v, but If i can't disable interior mic i'm afraid IT will no work...
[FYT Android Head Units] wipika1:
Generic question but I don't want to create a separate thread for it -- mods please remove and notify me if necessary.

I've set CarLink 2.0 to be launched when connecting my phone via USB...but it doesn't launch automatically. I've enabled the relevant setting both on the CarLink settings and on the FYT settings. Any ideas why this is happening and how to fix it?
[FYT Android Head Units] Tigrowski:
Are there any music player, radio and dialer apps that can be installed on those uis7862 devices instead of the default ones that would integrate seamlessly with the system? The default ones are atrocious to look at, buggy and non reliable as hell :( Is it even possible to install some alternatives and set them as actual defaults for the device?
[FYT Android Head Units] old.splatterhand:
What exactly do you mean with

?

I use Gone Mad Music Player and Jetaudio and both are playing my (mp3) music without problems from internal memory or from usb stick.
[FYT Android Head Units] Tigrowski:
Yeah, by that part I meant ones that can be set to be truly default, ie. they start autoplaying when the radio is being turned on and the default ones isn't trying to take their place or overwrite as the default. Don't have much experience with these types of units but from the past I remember some Chinese radios which did have this issue, ie. the media buttons in the widgets still only controlled the preinstalled Chinese media player and not the custom one, the steering wheel keys caused the music to switch to the default player etc. That's what I meant by integration.
[FYT Android Head Units] Fbocsa:
Hello I have a problem to run the appbackup script on my device. I have tried it with Fat32 USB drive as it was written in previous posts but always get "dead android No command" screen.

About the hardware info it looks FYT unit so it should work.
[FYT Android Head Units] Racker_CRO:
I tried to use appbackup script but it keeps failing on zip operation. Tried with two different sticks both FAT32 and with a lot of free space (one is 64GB another 16GB).

I can see AllAppUpdate.bin is created in BACKUP folder but if I try to open it with 7zip or WinRar I get an error "Unexpected end of archive".
[FYT Android Head Units] Astur_Torque:
I just received my new unit comming from sofia. I pluged everything but i was unable to make the steering wheel work even with canbus connected (weird because it responses when I switch the headlights on and off, but I wasn't able to make the steering wheel work.. Open Corsa D here)
[FYT Android Head Units] giorgisp:
Hi guys, I'd like some help from the more experienced modders here.

I am attempting to modify my SystemUI.apk to change the layout of the status bar. Specifically, I want all the navigation buttons on the right, and potentially to add more buttons (volume, screen off, app shortcuts etc.)

First, before making any modifications, I wanted to check whether I can successfully recompile and replace the original SystemUI.apk on my M700S:

I pulled SystemUI.apk and framework-res.apk from the device

Decompiled using BatchApkTools

Recompiled

Signed the SystemUI.apk using the included key in BatchApkTools (I think it's from AOSP?)

Flashed the recompiled SystemUI.apk onto my device using the below 7862lsec.sh script:

#!/system/bin/sh

#replace original with modded one
cp -vr /storage/sdcard1/APK/SystemUI /oem/priv-app/
chown -R 0.0 /oem/priv-app/SystemUI
chmod 755 /oem/priv-app/SystemUI
chmod 644 /oem/priv-app/SystemUI/SystemUI.apk

The structure of my USB drive is:

- APK/
- SystemUI/
- SystemUI.apk
- lsec_updatesh/
- 7862lsec.sh
- lsec6315update
- updatecfg.txt

In updatecfg.txt I simply put twipe_cache.

I performed the flashing, and after reboot I had no navigation or status bar, which I half expected something to be broken on the first try.

Of course I have a backup of the original SystemUI.apk. I tried to restore it using the same script, but after reboot it's still broken.

What am I doing wrong? Is there something wrong with permissions or the way I'm flashing it?

And, what is the correct way to make modifications to SystemUI.apk?

Any help would be greatly appreciated!
[FYT Android Head Units] LLIyT_HuK:
What key did you use? It is important. Need platform.pk8

Try mine https://xdaforums.com/t/allappupdat...8581a-only-for-1280x720.4571073/post-88639663

Also check the contents of the /oem/priv-app/ folder, it looks like you copied the SystemUI apk a little wrong
[FYT Android Head Units] surfer63:
What are the contents of your USB-stick and what kind of unit do you have?

Same to you: What kind of unit do you have?
[FYT Android Head Units] giorgisp:
It looks like I was using the wrong key. Now I selected platform.pk8.

I cannot restore the SystemUI, I tried flashing yours with your script exactly, but it's still broken after reboot. Now I even reflashed my kernel 6315_1.zip and it's still not fixed. Looks like I will need to wipe completely.
[FYT Android Head Units] Racker_CRO:
My unit is Mekede M500S. I unzipped the content of appBackup.zip on USB stick, nothing else.
[FYT Android Head Units] LLIyT_HuK:
Also check the contents of the /oem/priv-app/ folder, it looks like you copied the SystemUI apk a little wrong

Most likely you now have SystemUI.apk located in OEM/priv-app/SystemUI/ and in OEM/priv-app/. If so, then this is the cause of the problems, delete the extra one.
[FYT Android Head Units] surfer63:
The copy command "cp -vr /storage/sdcard1/APK/SystemUI /oem/priv-app/" is OK. The first PATH is a folder and the second PATH contains a trailing slash, which means the folder SystemUI and its contents will be copied into folder /oem/priv-app/

There must be another reason why it is not successful.

And to prevent you have old "garbage" left behind, your script should better be:

#!/system/bin/sh
rm -rf /data/dalvik-cache/profiles/com.android.systemui*
rm -rf /data/dalvik-cache/arm/*com.android.systemui*
rm -rf /data/dalvik-cache/arm64/*com.android.systemui*

#replace original with modded one
cp -vr /storage/sdcard1/APK/SystemUI /oem/priv-app/
chown -R 0.0 /oem/priv-app/SystemUI
chmod 755 /oem/priv-app/SystemUI
chmod 644 /oem/priv-app/SystemUI/SystemUI.apk

Twipe_cache only works when flashing firmware (when installing apks, Android takes care of it). It simply does not work when you simply replace an apk.

When copying/replacing an apk, you must make sure that you yourself remove the cache.

The lsec scripts are a "post flashing" action.

edit: Maybe I should have said: "As far as I know, you yourself have to remove the cache". I am not 100% sure. I simply always do it as I had bad experiences in the past.
[FYT Android Head Units] giorgisp:
I'm not sure what went wrong the first time. I did a factory reset to get it working again.

I have now managed to successfully modify the status bar layout to bring the buttons to the right side and clock to the left, by editing status_bar.xml.

I decompiled and recompiled SystemUI.apk with BatchApkTools, selected platform.pk8 key for signing the APK. I copied the modified SystemUI.apk onto the device using the script from your mod and everything is fine.

Many thanks LLIyT_HuK and surfer63 for your help!

Do you know if there's a way to add buttons to the status bar? I'd like to add volume +/- and a screen off button (on my M700S they are in the navigation bar at the bottom). Also, is it possible to put app shortcuts in the status bar (e.g. Google Maps)?
[FYT Android Head Units] wipika1:
Another mod question -- does anyone know what is the .apk for the A/C controls and if it's possible to modify the graphics? There are several buttons on the A/C interface that don't do anything for my car and I'd like to change the layout as well. Any guidance is more than welcome.
[FYT Android Head Units] Fbocsa:
I have formatted the USB to FAT32 and copied the content of the zip to it. I have no idea the unit brand and type. I have ordered it for my car it works well in normal use but the CAN bus connection isn't working. I see the original screen on the unit it is extracted from the LVDS signal by the CAN Box but the others features aren't working.
[FYT Android Head Units] migaja:
I have the same error as Racker_cro when executing appbackup script, but I did manage to unzip the file AllAppUpdate.bin. I don't know if it's complete, the file size is about 873 MB, ¿isn't it a bit lighter than expected?.

My Unit is from a reseller, with UIS8581a soc. Thank you in advance.
[FYT Android Head Units] surfer63:
Thanks for this reply. So you do have a 887 MB file. That is good.

Can you give a listing of that AllAppUpdate.bin?

Like an "unzip -l AllAppUpdate.bin > AllAppUpdate.bin.txt" and share that txt file?

If I look at your HWGetInfo.txt, I see that your /oem/app is missing the "Ver" file. I assume that one is giving the error.
[FYT Android Head Units] migaja:
Ok, I've attached the listing. In the listing there is a Ver file, I've attached it as well with txt extension added (otherwise website won't let me upload it). The content of that file is "2023-05-25 11:05:34"
[FYT Android Head Units] Tigrowski:
How can I apply the launchers/themes from Mario Dantas website linked in the initial post? I've tried installing a theme from here: http://fytfactory.mariodantas.com/index_l_1280_720.php

The installation went successfully, I've ejected my flash drive but now I can't find the new launcher anywhere on the device :( The launchers list in the Chinese menu just lists those "official" ones I've installed from their store but not the one I've just installed manually :/
[FYT Android Head Units] j0hn83:
I get this error every single time I run a backup but the backup ALWAYS works. I just ignore it now.
[FYT Android Head Units] Racker_CRO:
Well, I wouldn't ignore it since it's a backup and it should be 100% reliable. Every time I run that script my AllAppUpdate.bin is different in size, always around 850MB but content is different. If I open it with WinRar or WinZip it will throw an error unexpected end of archive but not with 7zip. When I try to open same file from FW I've downloaded from official site it doesn't generate an error with any of those compression tools.
[FYT Android Head Units] j0hn83:
@surfer63 explained in another post some time ago that the error can just be because of a missing res folder or something like that. It really is nothing to worry about. The backup works perfect every time for me.
[FYT Android Head Units] Astur_Torque:
Where I can find the lastest firmware available for Mekede? in the webpage says not available
[FYT Android Head Units] papero1159:
Hello,

I have a sinosmart 7862 and I had to install the Toppal application for voice calls as the google assistant call function (and only this function) is not activated (I think it's in the firmware).

Is it possible to reactivate it?

Is this problem has been found on other Chinese android car radios?

Thank you

Ps: apologize for my bad English
[FYT Android Head Units] hugovw1976:
Hi, I buy "2k" 8 GB RAM 128 storage unit and rear camera don't work is AHD 720p camera I think it's setting problem ( I test the camera in other unit I have TS10 and camera is fine) but I can't find were to change camera resolution in menu, in my TS10 unit I can chose from different settingf 1080p, 720p, 25fpd, 30fps, abd others but in this unit only can chose from AHD and TVI (I atach link to video) any one know where to find those setting in this unit?

Video
[FYT Android Head Units] TauTau:
with my device I had to set the correct canbus adapter and vehicle in the settings (I think in factory settings)
[FYT Android Head Units] wipika1:
Greetings all -- the seller I got my unit from sent me a new firmware (the "global" version that has the Google stuff).

I'm posting it here for anyone interested -- not sure what are the material differences between this and other firmwares posted here so use at your own risk!
[FYT Android Head Units] papero1159:
Hi thanks fot the share.

It is ok for sinosmart?
[FYT Android Head Units] wipika1:
I am not sure but I would imagine yes -- generally speaking the firmwares would fit any 7862 FYT unit.
[FYT Android Head Units] Clandaries:
Does someone know if it is possible to buy a complete replacement board somewhere?
[FYT Android Head Units] surfer63:
Thank you. This is also a very new one.

The App layer (AllAppUpdate.bin) is from 2023-06-12 15:29:13

The kernel is from "Wed Jun 28 18:22:57 CST 2023". This is however slightly older than the FYT foreign kernel.

Yes, If you do the necessary tweaks like explained in post #1 and post #2
[FYT Android Head Units] Fredday:
Hello guys,

I also got the mekede m6 pro 2k version recently and I installed the mario launcher34 and noticed that now the funtion of the car showing your actual gps speed is starting to have a life of it's own, I guess this is because the gps tracking has been changed to google instead of chinese servers? Is there a way to fix this?

I also noticed the MCU stayed the same when I did the software update I found in this forum. My kernel however went from 334 to 370 I believe. How can I update the MCU itself?

Another question I have, which I saw posted earlier as well but without an answer, is there a way to switch the google maps app shown on the homescreen to another for example waze and so on? The same thing with the media player on the homescreen, is there a way to change this to like bt music from your phone?

Many thanks in advance if you can help a newbie like myself ;-)
[FYT Android Head Units] samplerwrcPL:
What Voice Control do you recommend? Google Assistant offline works poorly. Is it worth installing Toppal or NexAI? How are they different and which is better?
[FYT Android Head Units] sawixso81:
Just curious...where would the lcdconfig.txt be located?
[FYT Android Head Units] surfer63:
Did you read post #1?

This thread is NOT meant for:

buyers advice (is this one better than that one?)

4G providers, DAB+ modules or DAB+ software (see here for DAB-Z by @realzoulou), Navradio+ (see NavRadio+ ported to UIS7862-FYT devices by @KoTiX2 , sub-woofers, OEM cameras, OBD devices, TPMS or other peripheral devices.

ABSOLUTELY NOT for posts about "what is/are your favorite app(s)?" <==
[FYT Android Head Units] wipika1:
Is it in your plans to release an updated OK-Kernel version based on this one?
[FYT Android Head Units] surfer63:
No. The foreign kernel is from 17 June, so that one is newer.

And I just created a rooted and an optimized kernel from the domestic version of 24 July. Nothing newer than that one.

But it is too late to test now (22:25 here)

And finished a first release of the scripts, but that has to wait for the tests as well.
[FYT Android Head Units] wipika1:
I think the one I shared is the foreign ("global") one, no? So Jun 28th should be the latest?

In any case -- thank you so much once again for all the work you're putting into this. Much appreciated.
[FYT Android Head Units] sawixso81:
Just curious...where would the lcdconfig.txt be located

I could use the mipi for 1280×800 7872
[FYT Android Head Units] prokiller1199:
Hi good day, how do I check the compile date of AllAppUpdate.bin through pc?

and also the kernel date without flashing?
[FYT Android Head Units] surfer63:
You have to unzip the AllAppUpdate.bin. Inside it is a textfile "Ver" which contains the creation date. That is not the same as every compilation date for every apk, but at least "some" apks should be recompiled and renewed.

For the kernel you need to extract the system* files from the 6315_1.zip (or 6316_1.zip) and unpack it to a partition file and mount that one. Inside /system/system/ you will find the "build.prop" file which contains the compilation date of the kernel. If you are on windows, you need something like "diskinternals linuxreader" or "p7zip" or ëxt2reader", but there are more.

You can find how to unzip/extract those files in post #2.