yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] Battoussai:
Hello, maybe I can help. I have a D-Noble UIS 7862 radio on my VW. I have the firmware backup from my seller. What is your radio model?
[FYT Android Head Units] Specy01:
It's not an app. I got this screen by setting the canbus Simple Soft XP, both with "ALL" and with "408" . As you can see from the photos.

As soon as you set the canbus, I am shown a rectangle at the bottom of the screen, as in the picture. And this box/rectangle appears every time you act on the air conditioning with physical controls.

The big screen instead,

You get it from the menu "Vehicle settings"

And "Air condition Control"

And you get that screen

But as you can see from both these last photos, whether the air conditioning is on or off does not change anything in the representation of the central on / off button.

I hope i have been helpful.
[FYT Android Head Units] aveeish:
Thank you so much! One more question: Did you have to use the reverse detect wire for rear camera?
[FYT Android Head Units] Specy01:
Maybe try setting up another type of Citroen. I despite having the 308 I can have the best results by setting the canbus for the 408.
[FYT Android Head Units] j-5:
Hi @surfer63 . Love all you've done here.

Quick question on this.

I made the backup and tried to do a restore, but the head unit cannot read the allappupdate.bin. I can't open it in Linux either, but can in Windows. Do I need to remove the password protection before attempting to reflash?

edit: 7Zip shows me this:
[FYT Android Head Units] Moniushko:
I did, and it's able to restore my AllAppUpdate.bin. However, I flashed newer firmware so I'm unable to go back to any firmware before July 2022. I wouldn't mind this but for some reason the newer firmware breaks my RDS on any radio app (it worked before).

I did flash the IYING firmware found from this post (just the AllAppUpdate.bin) and it miraculously worked on my HU without having to change the manufacturer ID.

Everything works except that "hybrid driving" window keeps popping up again every time I change drive modes or start driving, which renders my HU useless. The "hybrid driving" window seems to be coming from the Car Information app (which reads off the CANBUS). I tried the modified com.syu.ms from @seb21 but it still gives me the same issue. If I change the com.syu.ms from my original firmware backup, the "hybrid driving" message no longer appears, but it breaks Carlink and Android Auto doesn't connect when I plug in my phone.

These headunits are great, but are a real headache! :cry:

That would be great, thank you! My model is MIBIV-927. Do you know what date the firmware has?
[FYT Android Head Units] surfer63:
This looks like a bad usb-stick. Can you check your usb-stick and give it another try?
[FYT Android Head Units] j-5:
I can't do another backup since I'm in a no-boot situation.

The file on disk where I offloaded the stick after backup seems to be corrupt as well. I"m not sure what the size is supposed to be, but my backup is 365MB, while the ones downloaded from 4PDA are 1GB or so. No telling what is missing, but it seems 7ZIP extracts everything then has issues with the SystemUI.APK, which has a corrupt font file in it.

I have a ticket out to the reseller to see if I can get an original allupdate.bin, else I will have to try one of the russian ones. :/
[FYT Android Head Units] surfer63:
What unit do you have? And do you have a 360 camera?
[FYT Android Head Units] j-5:
FYT=1 some generic unit.

I don't have a 360, but supposedly the unit supports that feature.

I went ahead and did a restore using one of the Russian FYT images since my unit is a 2000x1200

(Android 10.0_ID1_UIS7862_no360&with360_2000x1200_UI2_NexAi_APP20220701_SYS20220718)

and it's operational again, though now I do have to go through and put back all my customizations. Second time around makes things better, though right? :D

Edit: Unit isn't stable in this state. From a power off state, it reboots a little after the UI launches and goes into recovery mode and reloads the kernel.

bother...
[FYT Android Head Units] taufikthexfader:
Dear @surfer63 @mariodantas

Is there any way we can hide/disable on-screen statusbar & (home / apps / back shortcuts) completely? Since we already have capacitive buttons on side of the HU and those shortcuts on statusbar often overlap with apps own shortcuts..
[FYT Android Head Units] mariodantas:
Didn't see somethig to do that till now, but as I'm working in a SystemUI mod and diving deep in the smali, i should find a way to do that !
[FYT Android Head Units] Battoussai:
I will send you a private message.
[FYT Android Head Units] surfer63:
There are some "full screen" and "immersive mode" apks in the Play Store. You can try those.

Note that this is no longer supported on Android 11, but even if your unit says it is Android 11 or 12, it still is Android 10.
[FYT Android Head Units] bluemask69:
@surfer63 Wich is the correct procedure to update MCU ?

- Put the file Stm32ud.bin and GD32_E230_64K_Flash.Hex of original MCU package WITH THE LATEST lsec6315update (taken from the latest official stock firmware) on to pendrive FAT32

- Put the file Stm32ud.bin and GD32_E230_64K_Flash.Hex WITH THE lsec6315update (old version) included in MCU package on to pendrive FAT32

- Put only the file Stm32ud.bin and GD32_E230_64K_Flash.Hex included in MCU package on to pendrive FAT32

thanks
[FYT Android Head Units] Aaaron16:
I understand from previous posts that images can no longer be signed using the ASOP platform keys. Is it instead possible to replace the platform key on the generated image with my own so I could sign my own updates?

If so, where does the public portion of the platform key reside on the OS image? I see in the Google documentation there are keys stored in the recovery image at /res/keys and for OTA images at /system/etc/security/otacerts.zip, but can't find where the APK signatures are getting compared.
[FYT Android Head Units] surfer63:
That depends.

I did not do that yet on these 7862 devices.

The stm32ud.bin and lsec6315update is the "plain" firmware.

The hex file is for the 360 camera system. If you have a 360 camera system you must flash the bin file and the hex file. And you need the lse6315update for the flashing.

I don't know if MCU flashing also works with the old lsecupdate. The best is to use the lsec6315update from the firmware version you flashed the last time. That is the version that best fitst your current installed firmware.

EDIT: And make sure you flash the MCU firmware that belongs to your manufacturer id. If your id=1, then flash with MCU for 1. If it is 116, then flash with the MCU for 116. If you don't do that you might end up with a bricked device or badly functioning device.
[FYT Android Head Units] j-5:
Interesting. I used the tool from @mariodantas to modify my 6315_1 then did a flash of the allappupdate.bin.

Now my unit reports corrupt and does a recover at every reboot (not boot loop), so I'm not sure what the cause is. Are the issues related perhaps or am I way off?
[FYT Android Head Units] mariodantas:
Fellow, i don't understand what the AllAppUpdate.bin has to do with my tool

Do you want to sign a 6315_1 file ?, ok send it to me I'll sign it (with TESTKEYS by the way) and return you back the signed zip
[FYT Android Head Units] j-5:
The tool is a huge help, very useful indeed.

I'm just troubleshooting, appealing to the more knowledgeable here, not trying to cast doubt on the utilities you provided.

Does repack.sh sign the zip with different keys?
[FYT Android Head Units] surfer63:
If the AllAppUpdate bin was not correct, I assume you don not have a "FYT system" at all, only Android. I assume all FYT apps that should reside in the /oem folder are simply not there.

Please flash again with a proper AllAppUpdate.bin. Your unit is still functional as it tries to do a proper install from the recovery.
[FYT Android Head Units] j-5:
Thanks for the tip.

Are there any specific apps I should look for in the /oem to verify? I do see all the apps that are part of my original (albeit corrupt) backup, both in the allappupdate.bin/app folder as well as the /oem folder of the HU.

All the functions do work, radio, Settings app, etc. I haven't found anything amiss other than the recovery on reboot issue ("need to wipe userdata" reason is: RescueParty)

(The new AllAppUpdate also looks a lot better than my original did, fwiw)
[FYT Android Head Units] leo06:
Does anyone have ddpai dashcam? I installed the app but the live video isn’t working, I can see other data but no video. Just a blank screen.
[FYT Android Head Units] selre:
Hi peeps, got a car with a fyt unit installed. All is mostly well. However on the ac control screen the dual zone climates are controlling the opposite side to what the screen is displaying. door open and closes show doors right way round as theres a setting to change that. wonder if anyone knows a way to reverse this round. Assuming its the old lhd and rhd diferences problem. Thanks all :)
[FYT Android Head Units] surfer63:
Well, If you see all files and folders then my conclusion is obviously wrong :).

I vaguely remember that when we experienced a lot with the old Sophia 3GR models (2015/2016) that this also happened if some flag/property/system file was not set ("install finished" or "install correct" or "all files installed") the units would do the same.

This was inside a hidden system folder "/sys/fytver" which were only accessible by root, and even then not always as the com.syu.ms kept locks on the files.

Still the colors of the leds are saved in that folder.

So I still think that with a correct AllAppUpdate.bin you might correct this.
[FYT Android Head Units] j-5:
It’s looking like it’s the 6315_1.zip. I’m still getting to root cause, but it’s pointing to the mod I did to the aspns-conf.xml file. I still need to test if the problem is my direct editing, the injection, or the file itself. The xml reader on the head unit reads it fine, so guessing it’s one of the other issues.

What I did was try the original unmodified 6315_1.zip that came with my allappupdates.bin, it worked, meaning the system was stable. Then I unpacked and repacked the same original with @mariodantas tool, and that one also worked, so not a signing issue.

My next test is to use the injector for my mod, if that works then the issue is directly editing the file in the mounted file system.

Interestingly, when I first flashed the 6315, and on original firmware (before my failed restore that got me here), the unit did a recovery on first boot. I didn’t check subsequent boots at the time.
[FYT Android Head Units] Moniushko:
I managed to resolve the annoying "hybrid driving" window any time I changed drive modes or started driving. I decompiled @seb21's modded com.syu.ms using APKLab in VSCode. I looked at the converted Java code and found a method that creates an intent for "com.syu.canbus", "com.syu.carinfo.golf7.Golf7FunctionalHybridDrivingInfo1Acti". I have no idea why this was in here. I edited the equivalent smali file and basically deleted everything in the method, leaving an empty method (the app would error out if I deleted the method entirely). I recompiled the code and installed it as an update over the existing Main Server apk and viola, it worked! Got a fully working Carlink that now works with my headlights, no more annoying window pop up, and thanks to Seb21's mod I can remap steering controls if I wanted to!

So to make everyone aware, the version of Carlink is dependent on the version of com.syu.ms.
[FYT Android Head Units] bluemask69:
I want to explain to you the "origin" of my question.

My system have a MCU version NOR_53_L6315_G23P48F64_V1:0_FYT dated 19 November 2020, my Navifly is FYT=1 checked with your HWgetinfo.

I read on 4PDA that this mcu version (11/19/20) for FYT=1 is very bad for power consumption and must be updated.

I found on 4PDA 2 mcu FYT=1 NOR (without camera 360) as "candidate for update" :

- 20201214 version with only Stm32ud.bin and GD32_E230_64K_Flash.Hex files in folder

- 20210529 version with Stm32ud.bin, lsec6315update (22 September 2021 dated) and GD32_E230_64K_Flash.Hex files in folder.

I have on my 7862 Navifly (no camera 360) a 2022 Mekede firmware recently updated., with lsec6315update dated 4 July 2022.
[FYT Android Head Units] mariodantas:
RescueParty = Something installed in the AllAppUpdate.bin not corresponding to the platform manufacturer (chinese security implementation since 2022-07-02), is seems like you have a MOD Settings or SystemUI (both priv-apps) in the AllAppUpdate.
[FYT Android Head Units] surfer63:
Please check if the original xml has dos line endings (\r\n) or only linux/unix line endings (\n). Some FYT apps don't care, others have issues with the dos line endings.

If you are on windows use Notepad++ or so. It also has the option to convert line endings from one system to another.
[FYT Android Head Units] j-5:
file apns-conf.xml

apns-conf.xml: XML 1.0 document, Unicode text, UTF-8 text

cat -e apns-conf.txt

<?xml version="1.0" encoding="utf-8"?>$

Both the new and original allappupdate.bin contain a SystemUI folder containing SystemUI.apk. No "MOD" folder though.
[FYT Android Head Units] aveeish:
This is what AIDA64 and Fake Device test report. I thought there isn't Android 11 for these headunits?
[FYT Android Head Units] j-5:
Neat trick, since API level 30 was only announced in February, 2020.
[FYT Android Head Units] surfer63:
Not February 2020, in September 2020.

Depending if it is Asian date format or English date format, this ROM is from 5 February or 2 May.

Someone really put some effort in this fake.
[FYT Android Head Units] aveeish:
Could you send me a link to an official site with this info?
[FYT Android Head Units] j-5:
I did in my reply. Check the link I included.
[FYT Android Head Units] aveeish:
That's Wikipedia. I don't think AliExpress will accept it for a dispute
[FYT Android Head Units] j-5:
Android 11 Beta is available today

As we shared with you last week, we postponed our beta release of Android 11 so that people could focus on important discussions about racial justice. Today’s release lo…

blog.google

That't the beta announcement.
[FYT Android Head Units] aveeish:
Thank you so much!
[FYT Android Head Units] bluemask69:
I installed some apps (then uninstalled) and now I have a strange behaviour of the screen, it scroll up and down (1 cm down) and seems to load something. I tried to stop some android processes and uncheck buttons of Nexi Voice App , but remain the upper left white dot point and nothing happens. I think to reflash the fully Mekede rom... Other solutions?
[FYT Android Head Units] warata:
hello everyone, I installed the latest firmware (2022-10-27) distributed by JOYING official on the unit.

I haven't seen any particular improvements, but I noticed that the date of the baseband version has changed.

Does anyone know what this baseband version means?
[FYT Android Head Units] j-5:
The floating dot is touch assistant, you can go to the app and uncheck the options to turn it off.
[FYT Android Head Units] Petarkco:
Don't know but it seems significant enough that you can't rollback to the previous firmware.
[FYT Android Head Units] xavierabell:
Hi, I have a Chinese UIS7862 head unit with FYT=1. All is working well except that there is frequent restart whenever i start navigation using Google Maps. The head unit would go unresponsive up to a point the system restarts itself. Sometimes the system will restart randomly when I play Youtube videos.

At this point I do not know what is the actual root cause of this happening, but I keep getting the issues almost everytime i'm driving.

Does anyone have similar issues?
[FYT Android Head Units] bluemask69:
I had problem with my 7862 NOR FYT=1 , see my last post. I resolved the problem : I updated the mcu with latest MCU NOR_with 360 system 20220624_E60.rar , then flashed latest firmware (2022-10-27) distributed by JOYING official.
[FYT Android Head Units] aveeish:
Hi all,

I was looking android headunits and found some are offered with 3 USB ports. Then I looked at the pinout for my HU and found out that connector E has two USB inputs. Could I just make a 6 pin connector with all the pins connected or do I need to activate the third USB port somewhere?
[FYT Android Head Units] Specy01:
When I bought the Navifly M700S, it came to me with two wires to connect on the back. At the other end of one of the cables was a USB plug, while the other cable had two USB plugs. I think all these devices have these cables supplied. Indeed, I also received a cable to connect to the original USB port of my car (a Peugeot 308) but unfortunately I do not know where to connect the other end of the standard USB plug to the car located on the armrest.
[FYT Android Head Units] xavierabell:
Im not sure if my issue has anything to do with mcu. Anyway, my unit is without 360, maybe i can give it a shot to update the mcu. Where did you get the mcu update file from?
[FYT Android Head Units] xavierabell:
After some further reading. I found the mcu update file from 4pda site (MCU NOR_without 360 system 20211009).

I will try update the mcu and see if it fix the instability issue.
[FYT Android Head Units] bluemask69:
no probz for 360 camera I don't have it, try the mcu I suggested to you , it works (recommended on 4PDA)
[FYT Android Head Units] surfer63:
Please do some googling both.

Baseband version updates are part of normal Android updates/patches. In this case FYT has obviously updated the underlying kernel with available patches from Android.

Baseband is the low level firmware for the "radio" which in this case is for (cellular) calling, WiFi, Bluetooth, texting. (so not the AM/FM radio).
[FYT Android Head Units] warata:
Sorry for asking without searching. And thanks for the clear answer.

It seems that it was true that I felt that the 4G communication speed was improved from this update.

Another change point. The maximum volume control bar of 30 has been subdivided into 36.
[FYT Android Head Units] jbleasdale:
Please can you point me to the firmware version? Of the 14 listed here, which is relevant for generic FYT units?

I can't decipher the Joying model numbers to know which to use unfortunately.

Many thanks
[FYT Android Head Units] surfer63:
What is generic in your words?

generic units are units not for one particular dashboard facia, but can be 7"/8"/9/10"/8.8"? being 800x480/1024*600/1280*720/etc., auto-rotating or not.

This is the same question as "what unit do I need for my car"?, without mentioning what you are looking for and which car you have.

Be (more) specific and based on that you do not need to even look at the model numbers. If it is (for example) 9" 1280*720, you can simply choose between old gui and new ui. And if you don't like it, reflash it.

And if you bought a Joying, why don't you know your own model?
[FYT Android Head Units] jbleasdale:
Apologies. Not a Joying, it's an Owtosin model https://www.aliexpress.com/item/1005004176674537.html

This is 1280x720p, not auto-rotating.

Looks like I need to check the panel type.
[FYT Android Head Units] surfer63:
It is not a MIPI type otherwise it would be mentioned on AliExpress. However, please google for "mipi android screen" to learn about it and to be absolutely sure.

I would take 2) or 3).

Note that there are actually not 14 options if you examine the links. Some are the same like 2) and 6) (didn't check further).

Most are still the same but simply contain a different config.txt and different fyt.prop inside the AllAppUpdate.bin.

Read post #1 and #2 to check on your manufacturer id and bluetooth setting before you flash.
[FYT Android Head Units] deadeye920:
What did you do that made the headlights switch work? I have two different versions of carlink. One works with the headlight switch but carlink appears to be running at 30fps and one that doesn’t work with the headlights switch but runs in 60fps
[FYT Android Head Units] surfer63:
I downloaded the latest firmware from Joying and Mekede and the Joying 6315_1.zip does indeed contain vendor, product and system compiled on 27 October. That does not necessarily mean that new Android source code is used for the compilation and build of system, but it is most likely. So the included baseband might indeed be updated compared to the other firmwares.

The latest system, product, vendor from Mekede is compiled on 28 July despite the November 2022 downloadable firmware version. Maybe that Mekede November version only contains updated FYT apks, like the Settings.apk. The kernel 6315_1.zip is older than the Joying one.

So I will flash the Joying kernel (6315_1.zip and lsec6315update) this weekend on my Mekede.
[FYT Android Head Units] bluemask69:
The system is now very stable, I suggest you update with the joying firmware.

I have wanted to update the mcu for a long time but I have always had many hesitations, I decided to replace the November 2020 NOR mcu which could potentially cause problems. I'd like to add a very functional T'eyes launcher that I saw among those on @mariodantas' site but I was discouraged from doing so due to incompatibility on 4pda.
[FYT Android Head Units] surfer63:
What do you consider "very functional"?

To me the T'eyes launchers, and other new launchers, are not functional at all, but very rigid. They simply provide an "area" in the launcher window for Google Maps or another application (if you use the right helper app). To me that is "eye candy", not functionality. It even means that it makes the laucher less flexible as you can't use that area for anything else: always the same app.
[FYT Android Head Units] bluemask69:
I have used the Microsoft Launcher on the PX Rockchip for a long time. It's good but I would like to try using a basic native launcher, which allows me to drag and drop apps downloaded from Google Play onto my desktop. I really liked this 19009500 com.android.launcher4 on page 6 of @mariodantas site
[FYT Android Head Units] surfer63:
I will only update the kernel with the Joying kernel version. My FYT top-layer (Mekede AllAppUpdate.bin, May 2022) functions fine and I am not interested at all in Android Auto on these units.

This new kernel hopefully provides the new standard Android security patches and bugfixes. And as already has been mentioned by @warata also contains the updated baseband firmware. My 5GHz WiFi functions really disappointing. Maybe it is the "micro" antenna that gets delivered with the Mekedes, maybe it is the WiFi kernel driver layer that is now hopefully at least a bit improved.

Besides, when only flashing a kernel I do not need to reinstall or reconfigure anything.

Edit: I flashed the latest Joying kernel. 5GHz did not improve :(.It is fine for the rest.
[FYT Android Head Units] warata:
@surfer63 has already given you the correct answer but to tell you my case

I always choose the "1280*720 models without auto-rotated" version of the firmware.

Actually my unit is a 1280*800 model, but the above selection works fine.

However, It needs to add this line in the config file

ro.sf.swrotation=270

If I don't, the screen will turn sideways.

Anyway, the 7862 series has a variety of models, so it's not easy to identify. You will have to do trial and error to find the best solution.
[FYT Android Head Units] mariodantas:
It signs with testkeys !
[FYT Android Head Units] aveeish:
Hi all,

I have a subwoofer and the volume between the sub and speakers isn't linear. What I mean by that is if I adjust the gain on the HU and sub at a certain volume the sub volume level is very different if you change too much the total volume( set the sub gain at volume 20, the sub level is too low at volume 10 and too high at volume 25-26). Is there a fix for this?
[FYT Android Head Units] blue_one:
Good evening dear fellas, I have a new head unit and I am a bit lost what kind of software/mods/infos will match my device. My first thought was that it's one of those fyt7862 units that are mentioned here but none of the software (backup script e.g.) works for me. Any help is much appreciated.

Best regards
[FYT Android Head Units] popamor:
Wow, you are the first one that I found that has similar unit as mine. QF001.