yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] farhanito:
Hi,

I just ordered a new FYT device from ali. It's called BT400, i think it's based on uis7862s. But a bit different since it has volume knob and different screen res (1280x800 according to device description).

Will i be able to use this kernel on that device?

Thanks
[FYT Android Head Units] peciu:
Hi,

where can i download the version for 8581 devices? Existing links no longer working.

Thanks
[FYT Android Head Units] mariodantas:
Here
[FYT Android Head Units] le_mi:
Got my M600S now.

One question before install your mod.

Is the MD-EDITION with FMC 100% compatible with the Seb21@xda MS Mod?

I only want to make sure.
[FYT Android Head Units] Matt Devo:
yes, the two touch completely different software components
[FYT Android Head Units] mariodantas:
They work together without problems ! FMC detects Seb21 Mod
[FYT Android Head Units] dishe2:
This is great news, I've wanted to try this on my other car's radio (I have a 7862 in mine and an 8581 in my wife's car).

Is it stable? Do you notice an improvement in performance?
[FYT Android Head Units] louforgiveno:
Definitely stable.....performance could be placebo...but seems better....prior to flashing occasionally my music app would "buffer/pause briefly" as if it couldn't read the data from the thumbdrive fast enough......that hasn't happened once since the flash....everything else smooth as ever
[FYT Android Head Units] dishe2:
I have found that my 8581 device (Atoto A6pf) tends to close whatever app is playing music if I leave the screen, due to the limited memory (2GB is just not enough!). So for example, if I open up the browser bc my kid wants to check the weather forecast while we drive, the music stops. This doesn't happen on my 7862 with 4GB ram. I'm hoping Mario's kernel will make the app closing less aggressive.
[FYT Android Head Units] louforgiveno:
Hmmm...my unit is 2gb ram and doesn't have issues opening apps with music playing.....i use poweramp app btw
[FYT Android Head Units] mcnaugha:
Still reading through topic. So apologies if discussed and fix shown…

I just installed this morning and lost sound output and steerwheel control. Looks like it’s linked to the canbus. It’s lost the setting for my car. Every time I try to select it, the selection doesn’t hold.

The touch buttons down the side of the display do not work now either.

It also reboots every 5 minutes.

Yes I did make the mistake of failing to uninstall the non-MD version. Old age mistake. I uninstalled after applying MD edition and then re-ran the MD install again. Would this mistake cause this canbus issue?

Is this a known thing and what’s the fix?

My car is Vauxhall Insignia which uses GM/Opel canbus under model Regal (I think).

Thanks.
[FYT Android Head Units] 1991-W201:
@mariodantas -

So, I installed the firmware over the weekend and it went well. The only question I have is where to find the FMC Manager app. It appears that IT didn’t get installed. I WILL say that my head unit is “quicker” to respond, but I don’t know the other benefits of the firmware as a result.

Pic #1: That's what was in the root of my USB stick... so, it should've been OK, right? I'm curious why I can't see the FYT Manager app.

Pic #2: Does this give you any insight as to what the problem may be? I just reinstalled it (and updated the boot animation while I was at it...) to be sure I didn't mess something up. I still don't see the FYT Manager app.

If anyone has insight, I’d be grateful… I know Mario is going through a rough patch at the moment.

Thanks in advance!
[FYT Android Head Units] mariodantas:
No FMC icon in your APPS ? where did youi get the firmware ? in the official place (Google Drive) ?
[FYT Android Head Units] 1991-W201:
Yes, from the official site with my login info.
[FYT Android Head Units] mariodantas:
Well the MD-EDITION firmware normally has nothing to do with steering control whells neither the sound, do you have a copy of your original firmware ?, you should have one
[FYT Android Head Units] mariodantas:
Did you see (after uncompressing the ZIP in the USB KEY) a folder named "_fmc" ?
[FYT Android Head Units] mariodantas:
This sould be the contents of the USB key prior to flash MD-EDITION
[FYT Android Head Units] 1991-W201:
This is what was on the USB after unzipping.
[FYT Android Head Units] 1991-W201:
This is prior to unzipping.
[FYT Android Head Units] surfer63:
This is correct. fmc should be installed. Please use the file manager and see if you have under "/oem/priv-app" the fmc apk
[FYT Android Head Units] 1991-W201:
If it IS there, then what? Just click to install, right?
[FYT Android Head Units] mariodantas:
Normally the FMC should be installed while flashing, but if you find in inside /oem/priv-app then run it or flash it again, or simply download the FMC update which will install it withjout the entire kernel !
[FYT Android Head Units] 1991-W201:
OK, I just looked before getting out of the car at work and it was NOT there. If it makes a difference, I formatted the USB on a Mac.

So, is THIS what I should download and install then?
[FYT Android Head Units] LLIyT_HuK:
Did you unpack the archives there? If yes, then this is the most likely reason.

Mac when unpacking archives carries a bunch of junk files in hidden folders and they often affect the firmware
[FYT Android Head Units] 1991-W201:
No, I unzipped it into a folder on my computer and THEN copied the files onto the USB stick. ¯\_(ツ)_/¯ Do y'all think it's worth redoing the entire process with a Windows-formatted USB stick or should I just install the FMC Manager APK?
[FYT Android Head Units] Matt Devo:
redo on a Windows computer.

Mac creates temp files on the USB which screws up install via the script, ran into this myself. Either that or the script needs to be tweaked to avoid copying dot files.
[FYT Android Head Units] 1991-W201:
Heard. I'll give it a go at lunch... ツ
[FYT Android Head Units] mcnaugha:
It is like the kernel wasn't compiled with the drivers for the CANBUS, touch buttons and BT of my unit. 🤷‍♂️ Vendor claimed it was A-Sure sourced. Not sure why it would be different from others.

No, I didn't take a backup but I have recovered by loading a JOYING firmware (launcher3, FYT manufacturer ID = 1, rotate 90) and everything is functional again. Had self-set the CANBUS from the start.

Asking vendor for firmware but they are procrastinating but not sure I need it now as this JOYING firmware seems stable and even slightly faster than I remember the original firmware.
[FYT Android Head Units] mariodantas:
Nooooo, this one:
[FYT Android Head Units] 1991-W201:
Okay. Thank you!
[FYT Android Head Units] 1991-W201:
Okay… this may be a stupid question, but where do I find that?
[FYT Android Head Units] ciris:
I installed bundle 1&2 on my Mekede unit. The color scheme and the main ui icons have slightly changed to red accents. The EQ looks the same but now when trying to access the surround or bass filter tabs the eq just force closes without error. Any way way to get the stock eq loaded back? I would need to get the apk, properly rename for my unit and use the lsecupdate file to get it installed?
[FYT Android Head Units] Battoussai:
Hello everyone. So I also wanted to have this great bonus and a couple days ago I installed FMC with mainframe support and all went well. Also did the sign in procedure. The new app appears on the main menu and it performs sweet. Nice job Dantas!

But there is a "but" or else I wouldn't be here :) - All Google related apps became unusable: Maps just keeps looking for position but MagicEarth goes fine. Gmail not a chance. Google Contacts just blank and can't add or import anything. Google Drive also numb. And the major one is I can't get into PlayStore.

Anyone got this issue before? Is it related do FMC?

Thanks in advance

P.S.: I do have the original firmware to get all back to zero.
[FYT Android Head Units] 1991-W201:
Never mind... I found it.
[FYT Android Head Units] LLIyT_HuK:
Try clearing cache and data on google apps. This is a common problem on FYT devices.
[FYT Android Head Units] Moldeb:
No but I see you've got the answer already. Just to add: You can see all sorts of effects as a coincidence to installing FMC without FMC being the cause. For instance, my unit built up an echo in phone calls (other person heard themselves when speaking (my voice was clear) so their voice in my speakers got picked up by the mic (no echo when I muted the mic) - very annoying for them to hear themselves) and my unit got unstable over time (launcher and app issue). Nothing was related to FMC and I got rid of all these issues through a clean install...
[FYT Android Head Units] ciris:
Ah, Clean Install... Well If I gotta do it, then I will. Thanks for the suggestion. That would be best and get everything setup correctly. *Hopefully!
[FYT Android Head Units] Battoussai:
Ok, thank you. I will give it a go and report later.
[FYT Android Head Units] LLIyT_HuK:
Also check that the date and time on the HU corresponds to the real one.
[FYT Android Head Units] Clandaries:
Here in this thread are many pros :)

So i will ask here. Does someone know if it it possible to receive calls on FYT devices via 4G SIM?

It is possible to make calls and it sounds way better than via bluetooth.

I have installed Google telephone app and contacts app.

What do i need or do to receive calls?

Maybe spoof device model?

Thank you :)
[FYT Android Head Units] LLIyT_HuK:
In firmware until 2020, this worked, and then the developers broke something in the system part. In theory, Mario can fix this if he can find the problem.
[FYT Android Head Units] gordgelin:
probably not broken but disabled, same as usb audio. such things can't be "fixed" without rebuilding firmware
[FYT Android Head Units] LLIyT_HuK:
Your signature is like a continuation of the answer =)

Any suggestions why it was disabled?
[FYT Android Head Units] gordgelin:
incoming (and outgoing) calls on early firmwares were causing random crashes and reboots shortly after answering calls so i think this is why it was disabled

as for usb audio imho its presence is totally against main conception of these devices - everything is tied around mcu+dsp+fm+bt and usb audio breaks EACH of these functions so it had to be disabled, but it is only my opinion
[FYT Android Head Units] LLIyT_HuK:
I read about disconnections on 4pda from old-timers, but nowhere was it mentioned that this could be due to problems. Thank you for sharing your interesting point of view.
[FYT Android Head Units] le_mi:
I use the MD Version with Mainservice and have a question.

After every startup (warmboot) the autoinput accessibility service is off and i have to set it on manually in the options.

Is there a trick to prevent this?

And the next is. Can I flash a Firmware wich is provided from my seller without any problems, if i have the MD Version installed previously? I want to check it solve my problem with the audiofocus between the blitzer.de and the radio app.
[FYT Android Head Units] mrchloo:
guys, I'm unzip "FYTBACKUP_(FYT_8).zip" and copy to pendrive to restore back to origin unfortunately it was fail. may I know what I did wrong? thx

Update: The issue has been solved by use winzip unpack-->repack-->encrypt allappudate.bin
[FYT Android Head Units] dishe2:
Mario! Hope things have been good with your situation!

Any hope you've had a chance to get the app/data restore function working yet?

Also, is there an easy way to skip the boot animation replacement? I like my stock animation in the Atoto units. Another Atoto user tried to just remove the startup images in the folder from the updater, but I think it may have made his bootup blank, which I don't want either. Any advice?
[FYT Android Head Units] Battoussai:
So here I am reporting back. Your first tip did it the trick: clearing cache manage to bring back to life all google related apps. So simple....

Thanks for that.
[FYT Android Head Units] LielBachar:
Hello:)

I flashed FMC with mainservice on my HU.

I processed to flash PeaceOS.

Does it mean I need to flash the FMC again?
[FYT Android Head Units] Tony2k:
Hi @mariodantas, I use DAB-Z but every time I turn on my cartablet this app is paused so I have to tap play to listen the radio. The developer sais that it's caused by something played before but there is no sounds during startup or reboot. Do you know if there is a way to fix this issue with DAB-Z?
[FYT Android Head Units] marchnz:
.bump above the garbage threads
[FYT Android Head Units] 03hdfatboy:
I ran into a few issues awhile back with several apps not working correctly. To correct I reflashed the unit but used my reset to default config.txt not the usual one. I can dm it to you if you'd like to try. Can't hurt
[FYT Android Head Units] 03hdfatboy:
@mariodantas

I tried your "upgrade bundles" on my unit. Was curious to see what you have done. Showed updating, after reboot I didn't see any changes in UI on EQ or otherwise, Did I do something wrong?
[FYT Android Head Units] Moldeb:
Aehm - make sure you read post #1 and briefly think about what a kernel does or doesn't do ;)

Then open FMC app to configure things - but neither your UI (except for system wide dark mode) nor your equalizer...
[FYT Android Head Units] 03hdfatboy:
We're not talking about the same thing, Bud. I've been using Mario's FW for quite some time now. He has a two pack "upgrade bundles" in his shared folder that changes the UI for EQ and a few other things. https://drive.google.com/drive/folders/1nIWvOicjAEctuBC_nvk90shNKC2u1_y8
[FYT Android Head Units] Fltlander:
I need to know what setting to change to log when I do a FYT backup...The reasoning behind it is when I try to do a backup I get an error. I've tried it without and with root and it comes to the same conclusion.I have an Atoto 8s Ultra Pro Gen 2 (UIS 7862s) with the latest FW on their site which is ATOTO_S8_Gen2_8_10_Inch_OS_230411_APP_230413 and Marios 2023-06-09__FYT7862_FW_MD_EDITION_WITH_MAINSERVICE. If any other info is needed just let me know.

I'll fix this first then ask about another problem I'm having.
[FYT Android Head Units] Matt Devo:
those apps are all older than the latest ones from Mekede, so not sure I'd stress over it
[FYT Android Head Units] surfer63:
Which Mekede version do you mean? The 7862 version (7862-A12-wbt-9-10.rar) is still from 14 March.

Or do you mean one of the M6 Pro (plus) firmwares?

And I had a look at the M6Plus firmware as some apks now suddenly have an extension/addition "_YL" or "_YL850" in the name, as if there is something different.

The carlink is of course the same, but for example the radio, now called "190000000YL_auto_com.syu.radio.apk" (for YL850?) is only 1.2MB, but the total folder with libs and assets is 42 MB, whereas the "normal" 7862 version is 18MB with libs and the like 22MB. The normal 7862 radio is 32bit whereas the M6pro radio is 64bit.

The new ones have an "assets" folder containing res_radio.ogg files. But these are not ".ogg" music mediafiles, but zip files containing the res files.

Anyway: when only flashing/copying this "190000000YL_auto_com.syu.radio" with all libs and ogg files and the like and setting the proper file attributes, I could not make it run on my 7862.

Anyone else did some tests? Or flashed the yl850 7862S firmware to their "old" 7862?

Edit: sorry for going Off topic. I thought this was the "MEKEDE M6Pro Plus with 2k (2000x1200) screen" thread.
[FYT Android Head Units] Matt Devo:
the file I'm using is MKD M6PLUS-UI29R-4L-850-国外360-付费语音-横屏2k-20230602-lzp.rar. According to 4PDA, YL850/860 are the designations for the M6Pro and M6ProPlus.

I've tested the above firmware on a M6Pro, M6Plus, and an old (1.8GHz UIS7862 / non-S) M500 (which is currently on my test bench right now). Only thing I change when flashing is the config.txt (BT type, UI/scaling stuff for the M6Plus).

All apps work properly, including the radio. Radio and BT have updated UI on all 3 devices. EQ app changes depending on hardware present. I'm also using MD's kernel and Seb's modded com.syu.ms apk.
[FYT Android Head Units] mrchloo:
deleted
[FYT Android Head Units] surfer63:
I flashed that one as well on my M500S in the car today. Now I can't make my steering wheels work while the cANbus settings are OK.

I will reflash it with the latest Mekede, but not today anymore (car is complaining about low battery ;) )
[FYT Android Head Units] surfer63:
Another reboot fixed it.
[FYT Android Head Units] xtmzone:
Hello everyone.

I'm a newbie in this area and i want to help me with some questions. I just got an android navigation. Find the specifications and model below.

I would like to know if I can also use this firmware on this navigation.

I would like to install a slightly better optimized version compared to what I have now, because I have some problems that I don't know how to solve, such as:

1. Music or bluetooth calls are heard very weakly and sometimes interrupted (I mention that I have a separate microphone, I don't use the one in the navigation).

2. It does not automatically connect to bluetooth when I enter the car with the phone.

3. If we assume that I'm driving and listening to the radio, but I want to play a song from YouTube (from my phone), it doesn't play until I go to the bluetooth application.

Coming back, can you please tell me which version I can install?

From what I've read here, it seems that "MD-EDITION" is one of the best options for my type of navigation.

Thank you very much.

PS : If possible, some steps on how to do the installation would help me.
[FYT Android Head Units] surfer63:
Yes.

1. Always a problem with these units. There are some tweaks. Search the forum.

2. It should. Did you set the connections to "autoconnect"? If not, forget on both devices and pair again with autoconnect.

3. See 2.

Yes

It is well described in the Instructions.txt inside the downloadable zip.
[FYT Android Head Units] xtmzone:
Thanks for all aswers :)
[FYT Android Head Units] Matt Devo:
hi @mariodantas , any chance you plan on updating your kernel to rebase on a newer release (May or June 2023)?
[FYT Android Head Units] surfer63:
I anticipated that Mario might not be around for some time due to all the mishap in his personal life right now, so I used the FYT kernel from the "7862_domestic_system_2023.7.4" version (4 July 2023). That one is really the latest but it is also a lean and clean firmware kernel missing a lot of specific Mekede (or Joying or T'eyes) additions.

I "linux diffed" all the differences between Mario's kernel, the "7862_domestic_system_2023.7.4" kernel and the "MKD M6PLUS-UI29R-4L-8502k-20230602-lzp" kernel.

I took Mario's FYT-Factory scripts and modified them to my liking. I added (scripted) the Google stuff and specific hardware files from the "MKD M6PLUS-UI29R-4L-8502k-20230602-lzp" from the vendor, product and system partitions.

And then added Mario's specific MD-EDITION changes, also for the rooting.

I will test tomorrow. No time tonight.

If working correct I will share it.
[FYT Android Head Units] gordgelin:
mainly it is missing google apps and services since it is version for chinese market. that is main difference, that's why i'd like to get "normal" version :) of course it can be added manually but i don't really like doing it :)
[FYT Android Head Units] Matt Devo:
2nd on the Google Play services. also the default language being Chinese is a bit of a pain to navigate :LOL:
[FYT Android Head Units] surfer63:
That can easily be set in the config.txt

But what is in your view the latest complete kernel?

I do have that "MKD M6PLUS-UI29R-4L-8502k-20230602-lzp" firmwatr from June, but it is actually a 7862s kernel.

I could use that one, or do you have a newer one?
[FYT Android Head Units] Matt Devo:
true, I just didn't realize that was the case when I flashed it to test

the 2023-05-23 kernel from that zip should work on older non-s devices as well. I can flash it to one I have here on my test bench to verify if needed. I'm not aware of a newer build outside of the "lean" 2023-07-04 one
[FYT Android Head Units] surfer63:
It should indeed be completely compatible.

On the other hand: I also think that 2023.07.04 kernel might result in a new firmware within a month from all resellers.
[FYT Android Head Units] surfer63:
I created a "Mario Dantas" kernel based on the kernel of the "MKD M6PLUS-UI29R-4L-8502k-20230602-lzp". The build date of that kernel from that firmware is from "Tue May 23 16:01:21 CST 2023". That kernel is of a firmware for an M6 Pro, but that doesn't matter. These 7862 and 7862s CPU's are 100% identical, be it that the S version has a slightly higher clockspeed.

I do not have an M6 Pro (plus), but an older "standard" 7862 Mekede M500S. As far as I can see/test "everything" works.

BIG DISCLAIMER: This is a direct copy of Mario's excellent work. I only copied what he did*. It is not my intention to "steal" Mario's work. It is just to share a new kernel now that Mario is going through a difficult period. ALL CREDITS FOR THIS WORK GO TO Mario!!!​

*: with a few adjustments.

Changelog (to Mario's previous release):

- kernel version 23 May 2023.

- Added Documentsui to system/system/app.

- Changed serverport back to 7275 (from 7276) for improved security as it is the encrypted port.

disclaimer 2: This is BETA just like Mario mentions.

Note: This is only for the 7862 units. There is not a new kernel for the uis8581a (as far as I know).

Kernel only: 6315_1.zip.

How to flash it:​

= If you already have the mario Dantas kernel installed (with or without fmc or com.syu.ms is not relevant):

Simply copy the 6315_1.zip with an up-to-date lsec6315update and a config.txt to a clean USB-disk. No updatecfg.txt or other file is needed.

= If your system does not have the Mario Dantas kernel yet, you need to download Mario's kernel (post #1) to your computer. Read the instructions in the zip and unzip it to a clean USB-disk.

Then copy "my" 6315_1.zip to the USB-disk replacing/overwriting the somewhat older kernel from Mario.

= If it doesn't work.

Simply flash Mario's previous kernel back on to your unit.

As always: The first boot after the flash takes longer as APKs need to be optimized. So don't worry and be a bit patient.

EDIT: Users report that the navigation window in the Launchers no longer functions with Waze. @gordgelin shared with us that the system framework has been changed since/after March. Mario's latest kernel is from March 4 and still works with this navigation window. If you depend on Waze in that FYT launcher window, do not update.
[FYT Android Head Units] aiui:
so if i change lsec6315update from PeaceOS from @LLIyT_HuK I'll have the best of both worlds?
[FYT Android Head Units] surfer63:
Yes, but in that case you need an updatecfg.txt with contents

test
twipe_cache

or even

test
twipe_data

depending on what you have installed now.

Edit: Best of both worlds is always a subjective user experience ;)
[FYT Android Head Units] Gscipione:
hi I have a mekede m6 pro with MD kernel. I will try to install it when I have time but I very happy that the excellent work
[FYT Android Head Units] Clandaries:
Would it somehow be posdible to make it work with Teyes CC3?

Would also be betatester 👍
[FYT Android Head Units] surfer63:
Yes, it is possible.

The point however is that T'eyes does not use a separate kernel (6315_1.zip) and a separate app level (AllAppUpdate.bin), but a combined firmware using a slightly different partition scheme.

Not a big difference, but as Mario and myself do not have a T'eyes we can't test. (ands I say we, but up to now all the hard work was done by Mario).

And secondly: @gordgelin already created a modded (rooted) complete firmware for the T'eyes, going back to the "old" partitioning scheme, thereby allowing you to modifiy the /system partition.

(That might however not be a bad idea either for the MD-Edition, now that I think of it)

Edit: But I have become more and more a standard user the last year. Apart from the non-functioning RDS-AF, which I really consider a big pain in the ***, I am pretty happy with my standard FYT. So why do the changes?
[FYT Android Head Units] Clandaries:
I have the modified firmware and payd for it but i get no answer about updates. I am still on march firmware of the VVE. Therefore i asked.

😁
[FYT Android Head Units] surfer63:
VVE = Vincent Vega Edition?
[FYT Android Head Units] Clandaries:
Yup