yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] DexterMorganNL:
I saw Mekede ( Which has warehouses in Europe ) claims that their units are running on Android 11, but atleast they display API Level 29. Which means it's fake and in fact running Android 10.

Because of being cheated by EKIY, I'm now looking for another headunit. These FYT headunits, seem more to my liking. But would they atleast work good? Without having to look for many workarounds?

I didn't read the whole thread, but have been looking into these devices for a while and because of my experience with Android smartphones in the past. And my ignorance... I have bought a head-unit that in fact runs on Android 8.1 instead of Android 10, because it was a fake Android version:(

It seems to be common practice sadly to fake Android versions..... anyone know if these FYT already support wireless Android Auto? I heard lately lots of head-units supporting it, without resellers knowing it.
[FYT Android Head Units] mariodantas:
Fellows, njew firmware from 7/4/2022 (6315_1.zip file) is signed using diferent keys, prior versios can be signed using testkeys but not from 7/4/22 onwards, does anyone here know where to find these signature keys ?
[FYT Android Head Units] Pino1966:
Hello forum members, I have installed a Mekede m600s car radio with canbus rz-vw-58 in my 2003 Passat b5 car, and therefore I need your help with a problem that I cannot solve with the help of the seller. the problem is that only the steering wheel button function works nothing else, i tried all the protocols and the wiring from the car to the canbus and radio are properly connected. I bought a second canbus from my side RP5-VW-001 and with this canbus the door function is also displayed on the car radio with steering wheel button function, everything else is not. how can i solve this problem? and a question for you are canbus and car radio compatible with my car? sorry, i don't speak english, i translated everything with google translator
[FYT Android Head Units] Pino1966:
can one of you help me, after I installed this firmware IDOING_FYT32_UIS7862_no360_1024x600_UI4_20220511.zip I can't flash any other firmware, how can I flash the firmware from Mekede again
[FYT Android Head Units] Lacki12:
hi, what does this error mean.
[FYT Android Head Units] hanichl:
Extract actual lsecxxxxupdate file from latest ( really latest ) update file for your unit , and replace the actual file on the installation sd-card. then the update procedure will work well.

i assume, you try to do some adjustment stuff, as a "real" update with stock files would not throw this error.
[FYT Android Head Units] arca114@gmail.com:
It's not an error, the system is asking for an update above this date that it's showing you, with the same problem I can't update either because there's no update above that.

There is still no more up-to-date update after this date!!
[FYT Android Head Units] Pino1966:
nobody can help me with my problem
[FYT Android Head Units] Lacki12:
i wanted to try to modify the config for microphone
[FYT Android Head Units] hanichl:
So, as mentioned, act as described. Download the latest ( complete ) update file from your manufacturers website.

Extract it and put the lsecxxxupdate file from the extracted data to your usb-stick or whatever you use.

then start your config process again. there are several descriptions to this subjet, start form post#1 and #2,
[FYT Android Head Units] surfer63:
Why do you want to flash other firmware? Only because your screen is rotated? You can fix that easily. See post #3
[FYT Android Head Units] hanichl:
Be more specific: what unit do you use, what firmware, whats the goal of this ?

Looks like you havent the right firmware to flash your unit.

Be specific, detailed, act as if anyone else would ask You this question.

Then you shurely will get assistance :)
[FYT Android Head Units] Pino1966:
I have a Mekede M600S 6/128 fyt116 and had already described the problem in #post506 and wanted to possibly solve the existing problem with a different firmware, but as I noticed myself, it didn't do much
[FYT Android Head Units] Pino1966:
No, I don't want to flash the car radio because of the display, my problem lies elsewhere, I've also tried to describe it as well as possible in post#506, if you need other data to help me with this problem, then let me know
[FYT Android Head Units] Pino1966:
Hello forum members, I solved the problem in post #507 myself by uploading my backup, but thank you very much for your help and the tips.

but my main problem still persists which is that the car radio doesn't display all the car info no clima, oil pressure, temperature etc except the door functions are displayed on the screen and the steering wheel button function works fine.

I have a VW Passat b5 car, year of construction 2003 and my HU is a Mekede m600s fyt 116 with 6g rom and 128g, my seller delivered it with a can-bus rz-vw-58 adapter, but with this can-bus Adapter only the steering wheel buttons worked. the seller suggested a firmware update and I did it and that didn't lead to a positive result, after my considerations I bought a new can-bus adapter (RP5-VW-001). with this addition, the door function is now also displayed in the HU screen. so I ask you for your help to solve the problem
[FYT Android Head Units] hanichl:
Looks like concerning the canbus protocol, or a not matching canbus box.

Try to change the canbus box settings in System Settings, playing around with all available setings for your car ( preferred: some *vw* type , aka *vag* ).

Have a look at the new descriptions of settings of those units, newly added by Surfer63 and others.

To their contribution, you can locate these settings, and play around. Its the only way . goodluck
[FYT Android Head Units] Lacki12:
Thanks for the help, I installed the config to improve the microphone, the result was negative, I had to go back to the original config of the mekede 700s, did the same thing happen to you too?
[FYT Android Head Units] Solvin:
What do you mean with negative? Has it gotten worse with the settings or just as bad as before?
[FYT Android Head Units] jbleasdale:
Can anyone confirm which is the reversing wire in the ISO harness for an FYT unit?

I would like to cut this to prevent the head unit blanking the screen every time I reverse as there is no camera attached. My previous MTCD unit had a software setting for this, but the FYT doesn't (as far as I can tell and I tried everything I could find!)

Thanks in advance for any help.
[FYT Android Head Units] Lacki12:
it's worse with the config I got on the front page
[FYT Android Head Units] Solvin:
These settings can be flashed back without losing the entire configuration of the HUD, is that correct?
[FYT Android Head Units] Lacki12:
yes, just restore the config file
[FYT Android Head Units] Solvin:
So for that I need only the files config.txt and lsec6315update on the USB-Stick?

Edit: Yeah works as expected. Flashed again only with config.txt and Isec6315update

persist.sys.zlink.mic.vol=9.9 inproves the quality and sound very good, but the other options are crap and should NOT be set:

persist.audio.mic.senstivity=1

persist.btmic.gain=10

persist.btspk.gain=7
[FYT Android Head Units] daviddosa:
You haven't specified what unit you have.

Not sure if this is the ISO harness or not, but here's a pin-out for the Navifly / Mekede units M200-M700(S).

Reversing detection line is on PIN 5.
[FYT Android Head Units] DexterMorganNL:
On mine FYT unit, although Quad-Core version the reverse wire on the harness has a little label on it. So it was easy to figure out.
[FYT Android Head Units] jbleasdale:
Sadly no label on mine, but thanks
[FYT Android Head Units] jbleasdale:
Following up on my HU (Owtosin branded) there is a similar diagram with identical pin-outs.

I cut the wire for pin 5 and the problem is fixed - many thanks!
[FYT Android Head Units] Pino1966:
Can I use this can-bus adapter with the Mekede M600s fyt 116 see photo, it worked very well with my Kenwood car radio
[FYT Android Head Units] daviddosa:
If you can connect it to the unit, then most likely yes. You would have to find the correct CANBUS setting in the menu.

If you cannot connect it straight away, it might require some wiring changes, and still might not work after.

What car do you have? The unit will come with a decoder if its necessary for the car.
[FYT Android Head Units] Pino1966:
i have a vw passat b5 year 2003, yes the car radio would come with a decoder rz-vw-58 but only the steering wheel button function worked and after that i bought a second decoder rp5-vw-001 and with these at least it still works the door function and steering wheel button function, but the remaining things such as air conditioning and etc. are not displayed on the car radio
[FYT Android Head Units] surfer63:
In post #506 you mentioned that you tried all CANbus protocols, but the Settings need to be configured at 2 locations. You do not mention that you tried the Factory settings.

In Settings the 4th options is the "Factory" settings (the crossed screwdriver and wrench). Then you select the 2nd option "Original Car Agreement" with the "volume" icon. In that section a lot of CANbus actions/events are defined which you can switch on or off.

So first select the option where your steering wheel buttons work, and then go into that Settings menu to try some things.
[FYT Android Head Units] Pino1966:
sorry but i don't understand english that well, google translator doesn't translate everything correctly, could you explain it to me with pictures.
[FYT Android Head Units] jbleasdale:
I recently purchased an Owtosin C4 branded (FYT=1) head unit and following the advice here was able to successfully update this using the FYT1_OKNAVI_EKIY_MCU_NOR_UIS7862_no360_UI4_UI6_UI29_UI30_20220112.rar update from 4pda, bringing the software up to date and enabling wireless Android Auto.

Big thanks to @surfer63 for collecting together so much useful info here and making this a straightforward process - much appreciated.
[FYT Android Head Units] surfer63:
First the factory settings:

Then:
[FYT Android Head Units] mariodantas:
No place to doubt, is our hero !
[FYT Android Head Units] iamrance.asa:
@surfer63 I tried the bootanimation update via the lsec6315update method. It resulted in a bootloop for my device and flashing the original bootanimation didn't fix it. What do you think the issue might have been? I typically replace the bootanimation in system>media then change the properties to that of the original on most devices. However, I noticed there's also a bootanimation.zip in oem/fem>media which @gordgelin replaces in his T'eyes mods instead of the normal system>media location. Any thoughts on this?

Also, is it possible to sign a modified (rethemed) system apk with the original signatures to install over the original on these devices? Or do I need to sign them with my own including some of the other system apks?
[FYT Android Head Units] ziddey:
Finally updated again since late last summer. Navifly fyt=1 unit. Instead of mixing and matching random system/app, I saw the joying is fairly up to date (june system/core, may app, so don't need to worry about locked in with a july+ one yet), and is already fyt=1.

Improvements:

Subwoofer settings in the equalizer app is finally fixed. Previously, only the main settings > subwoofer popup worked properly.

Carlink is much improved. Wireless android auto has been connecting promptly and reliably so far... No audio cutouts like with HUR, and overall much more consistent. Resolution is up too. Day/night has been working too (was permanently day before no matter the phone's AA setting). No more HUR means I get to use the external bt now.

Widevine L3! Been available since around April. I know it was a promised feature, but I'm still surprised it actually reached fruition.

Issues:

It seems that the initial volume toggle is no longer working? Despite being disabled, volume still resets after a reboot / sleep.

Not exactly a new issue (I first saw it when I updated to a July 2021 or so app/system): Google photos seems to not be able to see anything on the device. DocumentsUI is supposed to be for external drive access? Either way, it doesn't seem to help. It'd be nice to sync screenshots up for easy access.

The launcher / wallpaper seems to reset every so often. Doesn't seem like every deep sleep, but definitely on every reboot. Is there any way to get it to stick (Nova7)? Set ro.fyt.launcher to nova in config.txt? Maybe I just got lucky but I don't recall previously needing to ever reset the launcher. Note Nova is still set as the default launcher but isn't respected. I need to switch it out and then back.

Something seems amiss with the mobile data. I usually just tether using my phone, so it's not a big deal, but settings shows no ip address, and unrealistically strong signal levels (like -48db). Signal bar seems reasonable though. ifconfig indeed does show it's getting an ip, although usually only a cgnat ipv4 address, despite apn being set to ipv4/ipv6. DNS does seem to work, but beyond that, seemingly no internet. If I force the apn setting to ipv6, I do get an address, and associated CLAT, but nothing works. Haven't dug deeper yet, but the baseband is from last year and possibly the same as I had before (sorry, no screenshot-- see google photos issue above :))

Also, from the main post:

I don't think that's what GPS Mix does? It seems to enable/disable sound mixing scale. As well, with it off, I'm still seeing glonass satts.
[FYT Android Head Units] Solvin:
Is it possible to delete all launchers in the AllAppUpdate.bin and e.g. only store the Agama Launcher APK there? After that still specify in config.txt? Can it work that way?

btw @surfer63 the setting AMP ON/OFF is also there to switch a installed cooling fan on or off.
[FYT Android Head Units] surfer63:
"My" script uses the standard flashing option for a bootanimation.

Copying it to the partition no longer works as FYT uses dynamic partitions since Android 10 which can't be modified. It must be done during flash.

There are 3 locations (as far as I know) where you can put bootanimations where Android will look for it. The flashing one of the lsec6315update takes the default one.

I do not know why you got into a boot loop.

Did you test it? Are you sure you made it correctly? Is it not too big?
[FYT Android Head Units] surfer63:
Yes, it is, but you have to specify the launcher indeed in the config.txt. Next to that: You need a full AllaAppUpdate.bin as since the dynamic partitions the system/app partition is always erased. If you only have a launcher in the bin file, nothing will work.

The AMP ON/OFF is not used by default for it. T'eyes used this work around to add fans on fanless units. The modern units with fans have a different mechanism. (But I am not sure whether T'eyes still uses this work-around)
[FYT Android Head Units] Solvin:
Thank's for your reply and explanations. Last questions: So uninstall system apps with a script in the past is not possible because of the dynamic partitions?

And which 7862 unit has a built in fan? They are all the same and I have never seen this before.

I can't read something on the first page concerning root. Is that possible with this headunits?
[FYT Android Head Units] DexterMorganNL:
Anyone owning the 3GB/32GB version of the Mekede UIS7862? I'm looking into replacing my current FYT Quad-Core based headunit, with one of these. In general I don't expect needing to use the storage a lot.

But does the 3GB RAM have a quick cold boot as well? I'm not a frequent driver, so I will put off deep sleep when not using the car for some days. For multitasking, I guess mostly I will run Google Maps and Spotify together.
[FYT Android Head Units] daviddosa:
I have the Mekede M300S which does have 3GB RAM / 32GB ROM.

It's plenty fast for me. After ignition, takes around 2-3seconds to turn the headunit on. I have autostart for Android Auto, which takes about 15seconds to get connected to my phone. Sometimes my phone doesn't like to connect with the screen off, so I need to unlock my phone to get it to connect faster.

Android Auto does Maps and Spotify (or YT Music, or Tidal, or whatever you fancy) together, no problem.
[FYT Android Head Units] DexterMorganNL:
That's with deep sleep enabled isn't? I'm having that on as well on mine FYT Quad-Core unit, but do disable it when not driving for a couple of days or even longer than a week. But a cold boot takes almost 45 seconds....

Also when I would wanna use Google Maps or Spotify, without Android Auto ( which is great btw ) than its super slow. Which is the reason I'm looking at this Mekede M300S.

Already got the frame, so just need to unit: now I have 2GB of RAM, for my current headunit definitely plenty. It's the Cortex ARM A7 being the bottleneck....

I don't wanna do TMPS or OBD2 etc, just built-in navigation. I'm sure it's asked before, but does the built-in microphone work okay? Because I wouldn't wanna bother with these external microphones, as I almost never make phone calls inside the car.

Oh I also considered the M500s, it's just that I find € 50 extra a bit much for something I might not benefit from. If the 3GB of RAM also performs good.
[FYT Android Head Units] daviddosa:
I don't do anything special. I turn the car off, after 3 seconds the unit turns off too. Longest I left it, without starting the car was 5 days. No problems starting after that time. My car has an "economy mode" which basically turns off everything if the power is getting low. You need to turn the car on to exit this mode. This didn't come up after those 5 days.

I haven't tried using Google Maps and Spotify standalone, since I'm only using AA.

I also never tried the built-in microphone. I already had a mic installed beforehand, I just replaced it with the one included.
[FYT Android Head Units] surfer63:
FYT units since the Android 8.1 units (sc9853i and sc7731) going into deep-sleep, switch completely off after 3-5 days or so. I do not know if this by timer or measuring the voltage of the conitnuous or ACC wire. This means that the unit will do a full boot when not using the car after this period.

I didn't know about these eco mode on cars.
[FYT Android Head Units] DexterMorganNL:
That's good to know, however out precaution I still tend to disable deep sleep. So that's why I'm curious about cold boot, I heard it's only like 20 seconds max for this unit?
[FYT Android Head Units] mariodantas:
@surfer63 look, the REDMOD maintainer dir a new release which contains WIdevine L3 'as per the firmware's changelog), do you think that is possible to embeed Widevine L3 in our 6315 and 6316 firmwares ?
[FYT Android Head Units] ziddey:
6315 since april this year should have widevine l3 already. I flashed the latest joying (june core, may app) on my navifly two days ago, and it indeed supports l3.
[FYT Android Head Units] mariodantas:
Didn't know that, many thanks @ziddey
[FYT Android Head Units] Dabbsy:
I am trying to do a backup before I update the allappupdate.bin and I get this message after the unit reboots.

Is there anyway around this? Thanks
[FYT Android Head Units] surfer63:
I would suggest to download a new firmware, copy the lsec6315update from that firmware and copy it on the USB-stick. And try with that new one.

FYT changed a few things to prevent firmware downgrades.

I am not sure as I am still running an older firmware (why upgrade as for me everything functions?).
[FYT Android Head Units] Dabbsy:
Thank you, I will give this a try.
[FYT Android Head Units] Dabbsy:
It did not work, got the same message.
[FYT Android Head Units] ziddey:
Головные устройства Unisoc на процессоре UIS7862(s) / SC9863a (UIS8581A) Android 10 - платформа FYT - 4PDA

Головные устройства Unisoc на процессоре UIS7862(s) / SC9863a (UIS8581A) Android 10 - платформа FYT, [Головное устройство][Автомагнитола][Android]

4pda.to

There's only one known system that's new enough still.
[FYT Android Head Units] Dabbsy:
Software dated 02-07-2022 used to update the system core cannot be rolled back to a previous version.

That is what it says on the link you sent, matches the date on the picture I posted. Will have to wait for a newer version I guess
[FYT Android Head Units] ziddey:
Be explicit. Where did you get your lsec6315update
[FYT Android Head Units] Dabbsy:
I got it from the joying website, following the instructions on the first page of this thread
[FYT Android Head Units] ziddey:
That's June system, and lsec6315update from Feb.
[FYT Android Head Units] Dabbsy:
So I need to find a lsec6315update from 02/07/22 onwards?
[FYT Android Head Units] Dabbsy:
Thank you so much. So I downloaded the latest lsec6315update file and the 6315_1.zip file and replaced them with what I had on my USB and was able to successfully flash the full firmware. Before that I got my backup also, will post some updated system info soon thanks all!
[FYT Android Head Units] 03hdfatboy:
I recently got an S8 Ultra G2 for my car but decided to temporairly put it in my truck to play around with it while my car is in the shop. I have a bluetooth issue with the unit as it shows all connections as noName and I had to figure out wich one was my phone, LOL but when I tried connecting the OBDII for the torq app it shows noName and looks like a headset icon. I select it and it ask for the pw 1234 and it will connect for like 3 seconds and disconnect. Im running the latest 2022-04-15

I've tried factory reset and even reflashed the firmware with no luck. I did notice that under system info It shows Bluetooth version as Unknown.

Any ideas on how to correct this?

ATOTO S8 Ultra G2

kernel:#251 SMP PREEMPT Fri Apr 15 12:02:28 CST

2022

platform: (61)6315 AF America Full Band carplay2

touch:goodix 911_1060 (fa3916ff)E:0

panel:L8-MIP|-HSD10.1-1024X600_C460 20200526

11:50:4403366

cust:Fri Mar 20 14:21:10 2020

radiotype:tda77xx_7706(0)

audiotype:dsp55

csOmr:101004ff,cs1mr:101004ff

emif:0-13-14e-S0J9K8

f_v:Ls50

APP 1024x600 2022-04-18 09:36:58

System 2022-04-15 12:20:35 Friday
[FYT Android Head Units] marchnz:
What did reseller suggest when contacted for support
[FYT Android Head Units] 03hdfatboy:
I contacted ATOTO directly, was told to reset all wireless connections. No luck

Factory Reset...No luck

Sugested update but I'm on the latest one.

Even tried reflashing firmware with no luck.

Not getting the OBDII working isnt a deal killer but I did like the thought of real time info VIA the head unit
[FYT Android Head Units] marchnz:
Suggest warranty
[FYT Android Head Units] ziddey:
Which dongle do you have? I haven't tested yet, but I remember reading about a whitelist. Most of the pictures of included dongles look like your average elm327 clone though. Maybe it'd work with the soc's internal bluetooth (by setting sys.fyt.bluetooth_type=0 instead of 1), or maybe via the stock android settings > bluetooth (see first post, fyt settings explained, Mario Dantas' app). Just guesses though, and the internal bt can be a bit unpleasant to use.

edit: From a different thread about an older device: https://xdaforums.com/t/q-a-tips-info-roll-up-joying-fyt-sc9853i.3979377/post-80459061

Again, that's for the fyt sc9853i, so may or may not apply here.
[FYT Android Head Units] 03hdfatboy:
Got this in my email,

"I sincerely appreciate your efforts.

>

> Would you kindly send me a clear picture showing the current system version of the car radio first?

> You can locate the current system version of the car radio by going to settings > system >about device> MCU version [quickly tap this option 4 times in a row], then there will be a small window popping up on the screen of the car radio, scroll down to the system version.

>

> Then I will forward your information to our engineers for further analysis.

>

> Thanks for your time and I look forward to hearing from you.

> Stay well and have a good weekend.

> Sincerely,

> Fannie"

At least they are trying to resolve it. My phone connects without an issue, so I would think its something simple. Anyway to get into the OS to check, update or rollback the bluetooth driver?

Could the OBDII be the issue?
[FYT Android Head Units] 03hdfatboy:
Using bilt in BT and the OBDII is ATOTO AC-4450