yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
This looks like a 7731 unit but I am not sure whether it is a FYT unit. Looking at the systemUI it is a FYT.

Why do you need a splitscreen launcher? And what do you exactly mean with that?

The splitscreen functionality is offered by Android, not by the launcher.

To enable it you have to tap the "double rectangle" in the top right (and note that the notification bar in the top is part of the SystemUI.apk, never of the launcher).

In the next screen you then first tap the "opened book" icon to select the app you want on the left side, and then (already in the right half of the screen as after the first selection, that app is already in the left half of the screen), you select the second app to be displayed on the right.

Note that you can swipe left-right through the apps to select one, in case you have a lot of apps open.

Edit: I saw that this "how to enable splitscreen" is not mentioned in some Q&A, so I made a Q24 in the Q&A section in post #1 referring to this post.
[FYT Android Head Units] cicciripillo:
hello, I bought this car stereo on AliExpress for my Kia sorento 2011, it was supposed to be 8/128 giga android 12, but unexpectedly it's Android 10....I would like to know if I can personally update the firmware (also mod), to be able to bring it to Android 12 and possibly which firmware to download and the procedure to do it .. thank you in advance for your help .. Thanks
[FYT Android Head Units] kommando:
There are no proper Android 11 or 12 on the current FYT units, there are currently all 10 with some fake 11's and some fake 12's. Older ones are pre 10 of course. So no change possible until they finally get proper 11 or 12 released, more likely they will continue with the fakes until the hardware is changed to support 11 or 12.

The good news is if you are still in the time limit you can raise a dispute on Aliexpress and get a 20% refund for fake Android version. Ask for 25% and accept the 20% offer from Aliexpress.
[FYT Android Head Units] bluemask69:
wrong thread, the right (TS10) is

New TS10 UIS7862 6gb ram 128gb head unit q&a's

So I bit the bullet and bought myself this head unit: https://a.aliexpress.com/_9JZiHu Ad stated that unit is 4gb ts8, but unit shipped and arrived is 6gb TS10. Plugged everything up unit works nice and smooth as expected, but one seriously...

xdaforums.com
[FYT Android Head Units] Specy01:
My unit is a FYT 7862 uis (516) (i.e. a NaviFly M700S 8-128GB), with "ro.build.fytmanufacturer=116", "uiid=4", MCU=YIN and Canbus: Simple: Soft XP (RP5-PA-001).

The unit works very well and I am very satisfied, but to be able to have AA in wi-fi with my Huawei P30 I tried to update the Carlink app, but despite having tried various versions published in this topic, I could not get it. So I updated the unit with the latest firmware on the Mekede website. The update went well but Carlink in wi-fi did not work and installing various versions I also lost the ability to make it work with the cable.

So I wanted to update the unit with the firmware of the Joying that seems to have made AA work in wi-fy

I downloaded the joying firmware from this forum

Android 10.0 1280X720 MIPI Screen New UI 2022.10.27.zip

drive.google.com

Precisely I used this file:

Android 10.0 1280X720 MIPI Screen New UI 2022.10.27.zip

drive.google.com

Because on the joying website I couldn't figure out which one to use for my unit.

I unzipped with 7zip "AllAppUpdate.bin" and changed it to my reseller ID (116) and uiid 4

So in the USB stick I had the following files:

- AllAppUpdate.bin

- lsec6315update

- 6315_1.zip

and the folder:

-oem

Afraid of making mistakes I entered mine:

- config.txt

- updatecfg.txt

except during the flash I had this error as in the picture:

At the end of the countdown the unit started and remained for a few minutes on this screen with the word GOOGLE at 90 °. It seems strange to me since I used my "config.txt" 🤔

For fear of having done a stupid thing I did the reset using the RST button and I put my firmware saved using the "Isec3615 update" joying downloaded

From the link above

Now I have these features in the unit and obviously AA in wi-fi does not work. Carlink's version is v. 2.22.0115.1137

I wanted to know if someone can explain to me what I did wrong:

-1) in the compression of "AllAppUpdate.bin"

-2) in having used my "config.txt"

-3) I was wrong to use that file because it has a different MCU from mine (I did not update the MCU it seems to me that those files I used do not concern the MCU).

-4) I had to wait much longer (when the screen was stopped on the word GOOGLE at 90 °) at that time it was still 'loading' the firmware and in the end the screen would have gone in the right direction.

-5) Other

-6) I can no longer find where you disable "digital well-being" someone who gives me the path please

I wanted to put back the last firmware of the Mekede that I downloaded, but I would also like to be able to put the latest firmware of Joying. In the meantime thank you in advance
[FYT Android Head Units] jbleasdale:
This one. Mine stayed like that for nearly 10 minutes I think.
[FYT Android Head Units] cicciripillo:
Do you have to send me some files to satisfy my request to put an APK Car Launcher and to put Easy Connect type Android auto and carplay? Thank you.
[FYT Android Head Units] surfer63:
1) Did you update the fyt.prop inside the AllAppUpdate.bin to change it from the Joying=43 to your =116?

Did you zip it with the correct password? And zip it without compression?

2) should be fine

3) That will be handled by the manufacturer id -> 1)

4) When x new applications are installed, also x new applications need to be optimized. This will create the necessary "quick load" binary files in your dalvik-cache. This optimization takes a long time. You simply have to be patient.

5) What do you mean?

6) post #1; Q&A - Questions & Answers -> Q22
[FYT Android Head Units] surfer63:
Like mentioned by @bluemask69 : Wrong thread. We don't have that kind of files. You have to use the TS10 thread that @bluemask69 you already pointed you to with link and all. No use to keep asking here.
[FYT Android Head Units] kmecham:
First, thank you for such a helpful resource regarding these units. I have a Joying version of the UIS7862 unit with 8" 1280x800 display. I dislike the navigation buttons being spread out, with home in the top left recent and back in the top right corner. ATOTO and some other units put all three together in the top left corner.

Is this something that can be changed with the launcher or another setting? I am planning to try the launcher that looks most like ATOTO's on Mario's fytfactory site (saw a post suggesting the 1280x720 launchers work on the 1280x800 screen). I just have not tried it yet out of fear of bricking my unit.

I also wondered if it would be better to just try to install the ATOTO A6PF's software on my unit instead. From what I have learned here I just need to put my Joying apps for radio in the build and change a few lines in config files. I HAVE NOT DUG IN DEEPLY TO TRY THIS YET, but if it's a dead end or bad idea please warn me now and I won't research more how to pull it off.
[FYT Android Head Units] surfer63:
No. This has nothing to do with the launchers, but with the SystemUI.apk. That one is responsible for the top notification bar. The launchers "live inside" the SystemUI.apk.

You could of course modify the SystemUI.apk as you only need to change the layout, but that is up to you.

"....and change a few lines in config files."

This is normally always the case but Atoto always likes to give their own twist to firmwares. So make sure you have a backup or a fresh Joying firmware.
[FYT Android Head Units] leo06:
AA and carplay are working fine wireless with that joying firmware. Does your phone supports wireless AA?
[FYT Android Head Units] kmecham:
Thanks very much for the assistance. I will investigate the SystemUI.apk. Am I correct in assuming from information in other posts that edits to the .apks need to be done to the update payload (on a PC) not directly on the unit? Then I can do a full update (or specific parts by modifying the update.cfg file) to get the modified files on the unit.
[FYT Android Head Units] Specy01:
1) yes, as explained in your post I unzipped the AllAppUpdate.bin file, and in the fyt.prop file using Notepad++ I changed the reseller ID with 116 and I also changed the uiid to 4 (which is my uiid). After that with 7zip I compressed the AllAppUpdate.bin file putting the same password and with the faster option and without compression.

3) you mean that I did a stupid thing to update NaviFly with Joying and that I should have installed a firmware with dealer ID equal to mine and MCU equal to mine ie yin?

From your explanations I understood that it could be done even if the MCU is different. I understand that the important thing is to update the MCU firmware for the same MCU. Is it wrong?

4) If you approve, I will try again to update again and this time waiting for the end of the flash and that the end of loading, without stress 🤣 .

@surfer63 is it normal for the screen with the word GOOGLE to be rotated, during the 1st load?

5) I mean that maybe the flash was not successful for some other reason that escapes me and I do not understand 🤔.

6) per me questa volta non funziona. L'ho disabilitato molte volte anche forzando l'arresto dell'applicazione ma al riavvio quel app è sempre attiva (la sua icona è sempre presente nella home come si vede dalle foto postate sopra). Forse si sistemerà se aggiorno di nuovo?

Always thank you for your commitment and your help to all of us 👏🏻
[FYT Android Head Units] Specy01:
My phone is a Huawei P30 that supports AA, so much so that with the firmware of the Mekede that I had before I had AA with the cable. But I would prefer to have it with wi-fi
[FYT Android Head Units] surfer63:
You need to either decompile the apk or unzip the apk and modify the several layouts for the several resolutions.

Then you can use the lsec script option to flash it.
[FYT Android Head Units] leo06:
Supporting AA with wire it’s not the same with wireless. Try to download latest AA to your phone. Also in Android auto settings there is a switch to enable wireless AA, do you have that on?
[FYT Android Head Units] surfer63:
I added a "how to create an lsec flash script to post #2, to V. The lsec_updatesh folder, lsec6315update binary and 7862lsec.sh script (and what about "universal" scripts).

I just extended section V.
[FYT Android Head Units] surfer63:
Deleted. Somehow a double post. I received a gateway error.
[FYT Android Head Units] surfer63:
Note that with wireless AA, you always need to first pair your phone via bluetooth. Then you can use WiFi or USB.

You flashed your unit. Did you pair your phone again?
[FYT Android Head Units] surfer63:
1) No, you explained what your manufacturer id, etcetera was. You did not write that you actually changed the fyt.prop.

3) No, you did correct. What I meant is that if you adapt the id inside the fyt.prop you can indeed use the FYT MCU on your unit as the MCU is "linked" to the id. So you did it correct. There are differences in MCU, but that doesn't matter for a normal firmware flash. It will simply function. The MCU is for your hardware type, so you should not flash one MCU firmware to another MCU (unless you absolutely know what you do).

4) Yes, it is normal for these units. They flash in "portrait mode", meaning on it's side. And on reboot they are in landscape mode.

6) Did you also reboot the unit?
[FYT Android Head Units] Specy01:
1) maybe I can't explain myself well because of the translator. I explain again hoping that it is understood.

Then I actually edited the fyt.prop file with Notepad++ and saved the changes. Then using 7zip I compressed the AllAppUpdate.bin file. Should I do something else that I didn't understand/forget.

3)👍

4) 👍 I will wait for the conclusion of the upload even if it will last more than 10mn. I also specify that I had also done everything with the engine running because my car after a few minutes puts in "energy saving" and deactivates the screen of the car radio.

6) Of course yes, I restarted several times, but that white "dot" is always present 🙄
[FYT Android Head Units] Specy01:
Yes, my P30 is paired in bluethoot and, AA does not even work with my son's Iphone 14 Pro, while before, to him, AA worked in wi-fi
[FYT Android Head Units] Specy01:
Thank you very much, but I did not remember this. Tomorrow as soon as possible I will make the necessary settings. Thanks again for your suggestion 👏🏻
[FYT Android Head Units] surfer63:
Do you mean the "touch assistant"? That is just one of the default installed apks, but you can easily stop it by going to the Apps, find and open it, and uncheck its options.
[FYT Android Head Units] Specy01:
I will do it tomorrow thanks
[FYT Android Head Units] bougar:
Is there no way to make a backup to a TS10 topway unit? I have one and I would like to make a backup in order to personalize it and have something to recover from if something goes wrong.

I would like to install modified settings APK in order to re-map canbus keys.
[FYT Android Head Units] kmecham:
Thanks for your help, and all the work you have put into these units for the rest of us!
[FYT Android Head Units] surfer63:
Please read again ;)

I forgot to add the apk folder inside the oem_app folder on the USB stick in the example template.
[FYT Android Head Units] bluemask69:
...the TS10 thread is here

New TS10 UIS7862 6gb ram 128gb head unit q&a's

So I bit the bullet and bought myself this head unit: https://a.aliexpress.com/_9JZiHu Ad stated that unit is 4gb ts8, but unit shipped and arrived is 6gb TS10. Plugged everything up unit works nice and smooth as expected, but one seriously...

xdaforums.com
[FYT Android Head Units] DaddyFinger:
Deleted - Irrelevant post.
[FYT Android Head Units] Moldeb:
@surfer63 FYI in relation to #1 and if you haven't come across this before: I have a Joying JY-VQD10N4G-DA and ironically fyt.prop shows ro.build.fytmanufacturer=1 so not all Joyings are 43.

Just checked because I consider MD's edition and wanted to verify before I get into trouble - then again apparently there's no AllAppUpdate.bin in MD edition in the first place (and no dedicated thread on this forum, regrettably).

Maybe of interest, ignore if not.
[FYT Android Head Units] surfer63:
Thanks for reporting. I will adapt post #1.

Do you have a link for me to that firmware? I can't find it on the Joying site when searching on your unit JY-VQD10N4G-DA or MD.
[FYT Android Head Units] Specy01:
I ask so as not to make mistakes and send the unit to softbrick.

I have to install the Joying firmware on my Navifly with Id manufacturer 116. Looking at the lines of the Joying fyt.prop file, I noticed that the following lines have no value after the = sign

- ro.build.fytfontsize=

-ro.build.fytlivewallpaper=

While in my file these lines are not there as you can see in the following photos.

@surfer63 puoi vedere anche nella 1° foto che ho realmente modificato il file fyt.prop di joying.

This is Joying's modified fyt.prop

This is my fyt.prop taken from the AppBackup application's backup folder

Do you think I can leave these two commands with absent values, or I should delete these two lines.

Tomorrow morning I should flash with this firmware.

Edit:

I edited part of the post because I wrote half in English and half in Italian. I apologize for the mistake
[FYT Android Head Units] surfer63:
This simply means that the property will be cleared upon flashing. Whatever wallpaper or font size you had selected, you have to reselect it.

But that's not a problem at all.

And if you want to keep the current settings, you add them again.
[FYT Android Head Units] Moldeb:
Yes the newest would be https://drive.google.com/file/d/1JBBniX3aS2JeF7IvXCp7bNhw4CXNIikg/view?usp=share_link (I have an older one that still is truthful about Android 10 ;)

On Joying's https://www.joyingauto.com/blog/post/joying-android-10-0-car-stereo-latest-update/ it is listed under "firmware for 8" or 9" or 10.1" with 1280*800 for new UI:" and then "VQD10N4G-DA" which slightly differs from my model name but apparently is irrelevant as I was told to look for that one.

Edit: actually same name just "JY-" missing - they'll know why...

Edit2: The same seems true for my other Joying radio which belongs to "5) Here is the firmware for 9 or 10 Inch 1280*720 model with MIPI screen/New UI (As below example)" and link to latest FW is https://drive.google.com/file/d/1u5YiGJMkMe9ni8q3iTDnWrptBynSNKDs/view?usp=share_link - just downloaded out of curiosity and had a look...
[FYT Android Head Units] surfer63:
Now I did find it.

And I already had it but then the "Android 10.0 1024X600 1280X720 New UI 2022.10.27.zip" which also has ro.build.fytmanufacturer=1.

Already since 2016 they use(d) 43. I had not even looked at fyt.prop for this.

Strange.
[FYT Android Head Units] Moldeb:
But more compatible so I won't shout at them ;)
[FYT Android Head Units] Specy01:
I tried again this morning to flash the latest Joying firmware on my Navifly with id manufacture=116. Probably it is definitely at 100& the error is in the AllAppUpdate.bin that I modify is that I compress with 7zip since I have the error of the following photo during the flash.

So I'll explain what I do to change AllAppUpdate.bin :

-unzip AllAppUpdate.bin with 7zip by inserting the pasword when prompted.

- the AllAppUpdate folder is created

- in the created folder where there are the unzipped files and folders I open fyt.prop with Notepad++ (located in the app folder)

- with notepad++ I change the ro.build.fytmanufacturer with the value 116 and the ro.fyt.uiid with the value 4 (the value of my ro.fyt.uiid)

- I save with the name fyt.prop

- with 7zip I compress the entire AllAppUpdate folder. Maybe I'm wrong here. Maybe I need to compress all the files and folders???
[FYT Android Head Units] j0hn83:
I find these units are very picky about accepting AllAppUpdate.bin files.

Your unit is rejecting yours for some reason.

I use no compression (fastest), create a .zip file with password, and then rename the .zip to .bin.

You could also try with a different app instead of 7zip.

It's trial and error. It took me about 10 attempts to create an AllAppUpdate.bin file that was accepted by my headunit.
[FYT Android Head Units] Specy01:
When you say "I use non compression (fastest)" does that mean you use the same option that I use, as in the picture

I also rename the AllAppUpdate.7z file to AllAppUpdate.bin. But now I have a doubt:

Should the folder created by unpacking the original AllAppUpdate.bin file be compressed? Or should the folders and files contained in the AllAppUpdate folder previously created by 7zip be compressed to form the compressed AllAppUpdate.bin file? I hope I have managed to make it clear what my doubt is. I the 3 times I did the flash I used 7zip compressing the folder AllAppUpdate unzipped.

I will try with winrar

It's encouraging 🙄
[FYT Android Head Units] surfer63:
Indeed. The bin (zip) should be created without compression. Only store the files.

Like mentioned in post #2:

Specifications: zip format, non-compressed (store), password 048a02243bb74474b25233bda3cd02f8
[FYT Android Head Units] surfer63:
Fastest is with compression. Do not use that. That is why it goes wrong all the time. Use "store"

Like mentioned in post #2:

Specifications: zip format, non-compressed (store), password 048a02243bb74474b25233bda3cd02f8
[FYT Android Head Units] Specy01:
surfer, sorry, your explanation I have read it several times, but with google translate, and the translation is not precise enough so it misled me. from the translation i was understood that "even" the "faster" compression could be used. Now from your answer I understand what my mistake is. Thanks, I'll try again tomorrow morning without compression.
[FYT Android Head Units] surfer63:
Thank you for pointing me to this obviously confusing part of text. I removed it now. Better to give less information in this case, then to confuse users.
[FYT Android Head Units] Moldeb:
You used 7z archive format. Change that to ZIP format (drop down list in 7zip), no compression, with password. Easier: Just use 7zip as file manager so open AllAppUpdate.bin with 7zip (it determines that it is ZIP format) but do not unpack everything. In 7zip browse to the fyt.prop file and only drag that out of the 7zip window to eg your dektop (7zip will ask for password and unpack only that file). Edit fyt.prop on desktop and save. Then drag the file back into 7zip window, same folder. 7zip will ask you whether to overwrite old fyt.prop, confirm and enter password if it asks. That way, you retain the original structure/format, as you don't unpack/repack everything.
[FYT Android Head Units] DaddyFinger:
Hi all,

Please disregard my previous post which I have deleted.

I ran HWGetInfo and found my ro.build.fytmanufacturer=1 and ro.fyt.uiid=4 ...

I also did the backup of my existing firmware and from the config.txt in this backup, my ro.sf.swrotation=90 … sys.fyt.bluetooth_type=1 although I found this not in my backup’s config.txt but rather, in fyt.prop which I got from unzipping my backup’s AllAppUpdate.bin …

After consulting with @bluemask69 (because he had issue with a suitable firmware for NOR MCU too) he prompted me to check in System Info and I found that my unit has a MIPI panel too, so my firmware candidate is Joying's 1280 x 720 MIPI Screen New UI firmware.

This firmware's ro.build.fytmanufacturer=1, ro.fyt.uiid=2, ro.sf.swrotation=90, and sys.fyt.bluetooth_type=1 ... so the only change I would need to make would be at the uiid, yes? I can disregard any other differences? A lot of what I see in Joying’s config.txt is not in my backup’s config.txt but in my backup’s fyt.prop instead (e.g. the bluetooth).
[FYT Android Head Units] Specy01:
Happy to be of help for what little I can do.

Thank you very much, in fact I had never thought of doing so. Today I do not work, so later I will do as you indicated and try again. I hope it will work, in the afternoon I will need the car with the unit fully functional because I have to take a trip with my wife and she likes to listen to music in the car. Thank you, I will let you know in the morning
[FYT Android Head Units] Specy01:
In my opinion, instead of completely deleting the post it would have been better to leave the post and edit it by crossing out the letters in order to understand that that post was no longer needed and write something that explained why. But I confess that from the smartphone I can not understand how to write letters with barrage. You can probably do it from your PC
[FYT Android Head Units] bluemask69:
In previous firmware I had ro.fyt.uiid=1 , but I didn't change the joying value (uiid=2) to 1. Everything works perfectly.

No difference from what @surfer63 wrote about uiid in the post of 9853's fyt type: "The default fyt user id is 2 ([ro.fyt.uiid]: [2]), where it is 6 for the Joyings (also in fyt.prop). As such that is not important if you would flash a Joying firmware (or T'eyes SPRO firmware) onto your unit."

https://xdaforums.com/t/modding-your-joying-fyt-sc9853i-unit-without-root.3974357/post-82589977
[FYT Android Head Units] surfer63:
Yes, you are right.

Some properties are defaults and some are explicitly set in the fyt.prop and/or config.txt.

The fyt.prop is as it is built by FYT. The config.txt gives you additional options which will be set after the fyt.prop. So if you "don't like" a property which has been set in the fyt.prop, you set your version in the config.txt.

Theoretically you could also leave the fyt.prop as it is and set the ro.build.fytmanufacturer=xy in the config.txt, but as this is such a critical property I think it has not been tried yet.

It would make modding a lot easier per device. Download the same firmware for all, add a specific config.txt for the specific device, and add an lsec script for special apks (like the com.syu.ms from @seb21) to be installed based on the ro.build.fytmanufacturer=xy in the config.txt or as variable in the script.