yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] Specy01:
Surfer63, Moldeb, @john83, and everyone else, big thanks to you all; I finally managed to flash the latest Joying firmware on my Navifly M700S with Id manufacurer=116. Thank you for supporting me and for your patience.

After doing all the various settings I have some problems that I will list:

1) When I press the physical button of the unit, i.e. the one to return to the Home, the following options appear. I haven't put the final choice yet, whenever it appears I choose (only this time because I want to replace the lanchers).

2) I don't like Joying's firmware lanchers at all, so I'd like to put the Mekede one I like best, i.e. the so-called UI22. Can someone explain to me how to do it please?

3) I use the latest Naviradio+ but I noticed that if I listen to the radio and then use the navigation app (Maps), the radio (ie Naviradio+) stops, i.e. no sound is heard. How can I make the radio continue playing with the Maps app open?

@KoTiX2 can you tell me something about it?

Especially for the third point, I'm interested in having a fairly quick solution, if possible, because in the afternoon I have to take a long journey and reach a destination I don't know.

Always thanks in advance.
[FYT Android Head Units] j0hn83:
In config.txt file I have the line

"ro.fyt.launcher=com.android.launcher22"

And inside my AllAppUpdate.bin inside the App folder I have a folder 190001022_com.android.launcher22 containing the launcher apk file 190001022_com.android.launcher22.apk

If you are missing any of these then you may have issues using that launcher.

As for Navradio+, have you uninstalled the original radio app? I don't get the behaviour you are seeing.
[FYT Android Head Units] mariodantas:
ro.fyt.uiid=X is mostly used by FYT 95 and 116 (Teyes and Mekede) for launchers and systemUI behaviour as per SystemUI smali code
[FYT Android Head Units] surfer63:
Go to @mariodantas FYT factory website. Choose the launcher you want and an installable zip/script is created.

7862/8581 FYT Factory by Mario Dantas

Simpler than that is hardly possible.
[FYT Android Head Units] kmecham:
I have been exploring the differences between the AllAppUpdate.bin for both old and new versions of the 10-27-22 update and noticed the change in MFG id and uiid. Old is 43 and 6 while new is 1 and 2 respectively.

The two versions are interchangeable on my hardware, most of the fyt apps were reskinned in the new UI, and there are four launcher options built in. I also compared to the ATOTO A6PF (9") and found it interesting some of the things that I assumed would change are identical, including StstemUI.apk.

I was successful in flashing the ATOTO firmware to the joying (using MFG 43, uiid 2, and setting rotation to 270). The only thing that does not work is that I cannot access the Factory menu on the unit. The Joying HW must do something different and not allow the touch screen presses to be captured to open it up. Another interesting point is the SystemUI.apk is identical to both recent Joying versions. This means the ATOTO 11-04-22 update is be using the same home (top left corner) all apps & back (top right corner) navbar layout, not having all 3 in the top left corner.

Does anyone with an ATOTO A6PF have firmware that has the combined 3 button in the top left corner layout? I would like to explore the difference in SystemUI.apk
[FYT Android Head Units] kmecham:
Does uiid make much difference on Joying units?
[FYT Android Head Units] mariodantas:
Didn't explore Joying's SystemUI.apk file to provide a good answer fellow !
[FYT Android Head Units] kmecham:
Has anyone tried adding Gesture Navigation to their Joying FYT unit? I have installed Conea's "Gesture Control"

Gesture Control - Apps on Google Play

Control your phone with gestures. You will love the innovative home bar!

play.google.com

It works well, and after adding "com.conena.navigation.gesture.control=-10" to skipkillapp.prop it remains working after deep sleep. However, after cold boot the app cannot work as the Accessibility settings to use it is reset to off. I can re-enable through the app (links to Accessibility settings) and it works great until the next cold boot.

Does anyone know how to make this setting persist? Maybe the app needs to be added to one of the whitelists in the various AllAppUpdate.bin config/prop files?

Also, is it possible to remove and add apps to AllAppUpdate.bin? I have read about not being able to change the Android Manifest here in several posts, but also saw an post where someone said they adding a new launcher and repacked AllAppUpdate.bin. I am not fluent enough in Android APK development to know the limits of what is possible, and have only made a minor change to existing apks or icons. Sorry for the newb question.
[FYT Android Head Units] kmecham:
So far I only have checked Joying and ATOTO, but they were the same once unpacked.
[FYT Android Head Units] surfer63:
I did a very quick look at the Systemui as it might indeed be handy to have all 3 buttons on the top-left side.

It is in the status_bar*x.xml. There are several statusbars depending on the type of launcher being the several launcher6, launcher10 or launcher12 series.

Also: your "apps" button is actually called "split_screen" button.

Anyway, they use a

<linearlayout>
<framelayout>
<linearlayout>
[id/home button declaration on left side]
...more stuff...
</linearlayout>
</framelayout>
...more stuff...
[id/back and id/split_screen button declaration]
...more stuff...
</linearlayout>

I am currently too lazy to do anything with it. ;)
[FYT Android Head Units] kmecham:
Thanks for pointing me in the right direction. I will try to experiment with it, but had absolutely no idea where to begin before.
[FYT Android Head Units] kmecham:
One more set of questions regarding backup camera lines. I need to adjust mine, and investigated the method described in an older thread where you could locate and modify the images overlaying the camera feed.

https://xdaforums.com/t/q-a-tips-info-roll-up-joying-fyt-sc9853i.3979377/

Post 1, paragraph #23

However in the Joying and ATOTO firmwares I have checked, the com.syu.us.apk are not the same as what is being drawn on the screen. Now instead of lines, a trapezoid shape with graduation lines is drawn. I assume these lines are drawn dynamically now. Has anyone experimented with these to try to change the length/width (and curvature) of this trapezoid?
[FYT Android Head Units] surfer63:
It has indeed changed. I wrote that long time ago (long time in head units terms).

It is now in the dbcl1.png to dbcl26.png (left) and dbcr1.png to dbcr26.png
[FYT Android Head Units] mastrv:
@Specy01 I have an older head unit but it behaves the same. The radio sound stops when I exit the radio app. However, I normally have navigation, Waze, split screen with either the radio or Poweramp. When I do split screen with the radio, the sound does not stop. Poweramp does work in the background, though.
[FYT Android Head Units] DaddyFinger:
Hi all,

So I decided to give the firmware flashing a try.

I'd edited the fyt.prop from the AllAppUpdate.bin of the Joying 1280 x 720 MIPI Screen New UI firmware using Notepad++ to change ro.fyt.uiid= from 2 to 4, then got the 5 files in my formatted USB drive and got down to it.

I ended up with this:

And after the GOOGLE word loading was done and it rebooted I got this:

And it went into a loop :cry:

Am I understanding it correctly that the problem was specifically with the config.txt file and not the rest of the files?

Anyway, I decided to download a fresh copy of the Joying firmware, and this time I thought about what @bluemask69 said about not changing the uiid and I decided to try a Hail Mary and straight copying the 5 files from the new download over to the (re)formatted USB drive, unmolested :LOL: i.e. I did not make any changes at all, ro.fyt.uiid=2 was left untouched.

And it worked :love: I did not get any errors during or after. The GOOGLE word during the loading was upright this time ... the previous failed flashing the GOOGLE word loading was -90degrees like the above photos.

I don't understand though ... in a full firmware flash, the original company's boot animation still remains? I see @surfer63's guide to change boot animation, but does anyone know where I get my hands on the Joying boot animation that corresponds with this particular firmware? EDIT: Nevermind, I found this firmware’s “Powered by Android” logo … selected it, and now the original company’s is gone.
[FYT Android Head Units] surfer63:
No, it is not the config.txt.

It had extracted the AllAppUpdate.bin (with the fyt.prop).

Then it copied the config.txt to look for modified properties.

And then you get the error which must be inside the 6316_1.zip.

It mounted the /system partition but could not copy at least one file from the brotli compressed dynamic system partition inside the 6315_1.zip.

And with a non-functioning /system, you can't correctly start Android.

I guess you have a usb-stick with errors, or a corrupt 6315_1.zip (maybe also caused by a faulty usb-stick).

That is why you need the "test" line in the start of your updatecfg.txt.

(Some additional info: If you unzip the 6315_1.zip, you get a folder META-INF. Inside that folder META-INF you will find folder "com/google/android" with the "updater-script". That one tells you what is done during a flash.)

Very good though that you now have a functioning system again.
[FYT Android Head Units] maids:
will any of these work on my head unit please

I have an issue with waze being too small to read this unit uses zlink to connect phone
[FYT Android Head Units] MyAlpDroid:
Hi,

I have develop an app for Joying and Alpine A110 which mahe retrofit to Android Head Unit possible. Now,swr are working, infotainment metadata and nav info are send to the car cluster but

Joying uis7862 has poor bluetooth media player and radio. Specifically , it don't send media metadata to other apps and I am not able to know which music or artist is playing when I use my phone and bluetooth. In fact, I am interested to catch phone info too.

Do you know if :

- I can mod my Joying head unit and change bluetooth player and bluetooth phone by another app (like radio by NavRadio+) ?

- Which intent or service I can call with existing com.syu.music and com.syu.bt to catch metadata ? Or where I can find documentation about it ? (if exist)

Thank you

My project : https://github.com/MyAlpDroid/AlpDroid
[FYT Android Head Units] surfer63:
No, this is not a FYT unit.

With regard to Waze: Try Settings -> Display -> Fontsize
[FYT Android Head Units] maids:
in waze or head unit
[FYT Android Head Units] surfer63:
Android Settings
[FYT Android Head Units] maids:
in the head unit? waze is fine in our other car
[FYT Android Head Units] surfer63:
Yes, of course. Android Settings is the head unit.

And again: your unit is not a FYT unit. What we tell you here might not be applicable for your unit. I just gave a general advice.

It could also be an issue with the DPI setting.

Your other car is not relevant if you don't tell us what kind of unit you have there. And if it is not a FYT either then you better ask in a forum for your specific unit. Maybe there are experts there who do know your unit and know how to change it (if it is up to DPI setting).
[FYT Android Head Units] maids:
I have been trying for months to fi d out the model hence why I posted pictures this was in a car we purchaced
[FYT Android Head Units] Specy01:
I fixed the problem by changing the lancher as suggested by surfer63. On the site of @mariodantas there are many beautiful lancher. By installing (very easily) what I was interested in, the music was automatically settled.
[FYT Android Head Units] surfer63:
Your K4811 sock is a unisoc 8581 CPU, but not a FYT.

Chick this thread and this post. That guy seems to have the same unit.
[FYT Android Head Units] surfer63:
The first is a simple No.

The second is a bit tricky.

I have the idea that the metadata from the older com.syu.music combined with the older launchers on sc9863i and PX5's did send metadata.

I did not check at all for the new unit. I don't use the standard music nor the standard radio.
[FYT Android Head Units] MyAlpDroid:
Thank you.

I did this morning an update to last firmware (15 08 2022) of my joying. I don't know if they change something in bluetooth app but now my apps receive metadata from bluetooth.. Sorry asking before update but my problem seems to be solve by new firmware.
[FYT Android Head Units] docsaq:
I have an issue. I have an android headunit that I know is with UIS7862. It went into some sort of software glitch. It kept going in a loop with CarGuruWeb. I went to the shop I got it from and he said he can not help and as I caused it by applying the software (Carwebguru) there is no warranty. The recovery was also not working with 'No command' error. A friend of mine thought he could help and he gave me a firmware upgrade on a usb. I applied and it upgraded but to a window which is upside down and saying UI and MCU are not compatible. The upgrade was from Joying. He said with the loop ongoing there was no way of modding the upgrade to my device. All buttons and touch screen is working. I was wondering if Installing a modded firmware from here can help me or there is no way out ? The unit is unbranded.
[FYT Android Head Units] Specy01:
I'm sorry for you. Before updating the firmware it would have been wise to read the first two posts of this treath, and you should have made a backup of your firmware Meanwhile, take a picture of the characteristics of your unit and put them here. Go to settings-system-device information. Take pictures and also click on "system info" and take pictures. I hope the gurus of this forum can help you, they are very prepared and helpful, but I recommend reading the first 2 posts
[FYT Android Head Units] DaddyFinger:
It shouldn’t be a faulty USB drive I think … I’d installed the unmodified Joying firmware as well as 1 of the launchers on @mariodantas ‘s site 😉 with it without problems. Possible that it was something messed up in the re-zipping of AllAppUpdate? I use WinRAR and chose “Storage” though.

Can I say that, I am not particularly fond of Joying’s launchers or their default music player? 🤪 The folder system of the default music player is pretty bad.

The good thing about the Joying firmware is that … well … at least now I have an English UI, as well as Play Store and Youtube - these were not available in the original’s firmware, there was a “Download Market” (direct translation) instead. I am under the impression this is a Chinese-only equivalent of the T’Eyes meant specifically for the Chinese domestic market - from what my friend who helped buy this unit tells me, this brand of Android players has the highest sales volume every month on the Chinese online shopping portal they use.
[FYT Android Head Units] docsaq:
You are right. I had no clue regarding availability of such a forum. And I thought my friend who actually works at a shop installing all sorts of infotainment systems would be aware of this. Will post those details shortly. Thank you.
[FYT Android Head Units] surfer63:
First of all, you should have mentioned what kind and type of unit you have (no brand is clear, but is it 7"-10", Tesla style (I suppose not), MIPI screen). As you were partly successful in flashing a Joying unit it should be FYT.

First try to flash with a mekede firmware and simply try the '7862/9" 10" ' or the '7862 7inch/8inch' depending on the unit.

I think it will solve the "upside down" issue, but if you still have the same issues with "UI and MCU are not compatible", you need to go forward with the next steps.

If you still have your original firmware, you should check what your "ro.build.fytmanufacturer" is. Then you can use my script from the first post #1 at "Mods, useful software, tweaks for your system, etcetera." and then the 3rd bullet "Change FYT manufacturer". If you don't have your original firmware anymore, you can start with a value 1 or 116.

For the upside down part: if you still have your firmware, check the value for "ro.sf.swrotation" , it is most possibly "ro.sf.swrotation=90". Joying uses 270.

So if you use my script "Change FYT manufacturer", also add a text file config.txt adding tyhe following 2 lines

test
ro.sf.swrotation=90

Flash that to your unit.

If you still get the "UI and MCU are not compatible", you do not have the right "ro.build.fytmanufacturer". Like mentioned: 43 is Joying (but lately also changing). So try 1, 116, 31, 95 as those are the most common, but the complete list (as far as I know) is 0, 1, 8, 15, 31, 32, 43, 49, 51, 53, 62, 63, 94, 95, 103, 107, 108, 11, 112, 116, 130.

You simply have to try them.
[FYT Android Head Units] docsaq:
First I was able to resolve both issues using the scripts given in this forum. Thank you very much. Unit was unbranded 10.1 inch non MIPI. I was lucky that it was FYT otherwise could have bricked it. I haven't been into tech for a long time. Maybe a decade ago I had tried rooting and custom roms but now was too lazy to look it up myself. I relied on my friend thinking he was an expert and knew what he was doing. Eventually had to spare time to find and go through this post. Thanks to you and other wonderful people here, It got resolved. Joying interface is pretty much same and I might think of tweaking it (like removing horrible default music player).. but that's for another time.

Thank you all.
[FYT Android Head Units] born2lose:
hi guys,

absolute newbie, but I hope you can help. not sure even if this is the correct thread to post, but you’ll let me know :)

I have recently purchased an eonon q67pro headunit based on Unisoc UIS8581A (3 GB RAM, 32 GB storage, android 10, 1024*600 7-inch display). not sure if it is fyt or not…

the problem is that the unit does not recognize 3g dongles. no matter what dongle brand or carrier I use, it’s not detected. I do not have a ’mobile network’ section in settings.

I’m assuming eonon have removed something from the firmware. is there any way to get a 3g dongle working, meaning maybe a firmware flash? from what I read in the first post, I cannot flash the uis7862 firmware directly onto my uis8581a unut - do I have other options?

any help is appreciated!
[FYT Android Head Units] fight2k:
Did someone has problem with sound?

Only radio app got sound all others apps like YT, Spotify etc after two seconds getting mute and when increase volume to the maximum I can hear that music is still playing but really quiet

Uis7862 FYT 31
[FYT Android Head Units] bluemask69:
wrong thread, the right is here

https://xdaforums.com/t/some-questions-about-a-fyt-unit-with-unisoc-uis8581a.4461867/
[FYT Android Head Units] Saffy79:
Hi, without sounding dumb how do i apply the above mods? I have done the firmware update without any problems.. but not sure on how to apply the other mods mentioned above.
[FYT Android Head Units] mariodantas:
read, read, read, Page 1
[FYT Android Head Units] peciu:
Is this correct "persist.audio.mic.senstivity=1",

is there a typo and it should be "persist.audio.mic.sensitivity=1"?
[FYT Android Head Units] j0hn83:
Not a typo.

persist.audio.mic.senstivity is correct.

It's how it was on my pre installed firmware and every firmware update I've downloaded.
[FYT Android Head Units] mancypher:
Hi forumers. I am new to this Android head unit scene.

Bought this recently. Highest spec 8+128 with 2k screen.

Just want to know how do i read the build number for this. Been long time since i dabble in android. [the last was a Galaxy Note 2 with custom ROMs, years ago]

Attached is the specs.
[FYT Android Head Units] vkelectronics:
Good day to all team

Does anyone knows how I can change the resolution of the TFT from 1280*720 to 1024*600
[FYT Android Head Units] surfer63:
31-10-2022. See system info
[FYT Android Head Units] zelixsphere:
Hello Family. I have a Phoenix Automotive Tesla Style Screen with a confirmed FYT system(sc7820) (I did actually read everything on the beginning posts). I have searched everywhere on google as well as reached out to phoenix automotive, (they no-showed for a virtual meeting). I am stuck on an android boot screen, after flashing a boot image. The device is in fastboot mode.

What caused this?

I flashed a new custom boot logo, as indicated directions-wise, on the first topic, and the system will not boot correctly as a result

Things I have tried:

1) Reset Button, 20-sec hold while powering the vehicle on, then short press then 5-sec press of reset button

2) Reset Button, just as a separate repeated attempt

3) 2 fingers on screen during boot

4) 5 fingers during boot

5) Tried re-flashing via USB the backup I made via (following the instructions provided)

6) Tried reflashing the secondary flash suggestion (full flash)

7) I even tried the keyboard idea, plugging it in, and hitting alt print screen + E or L or I

Things I have noticed:

-I do not see firmware auto-starting like when the system is loaded.

-I do not think the USB ports are being activated and the system freezes before the USB ports are initialized.

-There are a set of buttons at the bottom, but they are car-specific, and not menu, or volume leys

- After a long, long while, if the system is on, it will reboot, and do it all over again

- Only thing on the screen is Android Green Logo, and Fast Boot Mode (top left).

- I am a highly knowledgeable tech savy person, so feel free to make me get my hands dirty using software, or other suggestions. I will not suggest that I should short out the IC chip, as some people have tried this with issues on tesla style screens

Any suggestions would be amazing and appreciated, please.

Separately want to thank this community for all the amazing resources, and ideas. @surfer63 amazing software, thank you.

Again appreciate any help anyone can provide

Chris
[FYT Android Head Units] surfer63:
What is an sc7820? I can't find any CPU worldwide that is a sc7820.

Your first say "I am stuck on an android boot screen, after flashing a boot image."

You end with "I flashed a new custom boot logo, as indicated directions-wise, on the first topic, and the system will not boot correctly as a result"

What did you flash? And if you really flashed a boot image: which boot image? where did you get it?

And if it is a FYT unit, you should ask Phoenix for a firmware for your unit. The FYTs are built this way that if they can't boot, they "search" for a new flashable usb-stick. First ask Phoenix if they have an original firmware.

But also "- After a long, long while, if the system is on, it will reboot, and do it all over again".

The older FYT units were optimizing all apps after flashing and simply got too hot and rebooted. And on the next run the same. Please also check if the flash was maybe correct but your unit gets too hot. If so, use a hairdryer on "cold" to cool your unit to make it finish the optimizing step. (Yes, that's how we sometimes had to do it 2015/2016 with FYT units).
[FYT Android Head Units] zelixsphere:
Hello! Thank you for the response. That was a typo, my apologies. The Unit is as follows:

sc7862 also known as uic7862 specs can be found fairly easily (with the correct model, sorry again) here https://gadgetversus.com/processor/unisoc-sc7862-specs/

When I say flashed. I mean I flashed the current system, with the FTP Factory Firmware from here

7862/8581 FYT Factory by Mario Dantas

Then I further updated the boot logo file utilizing the process shared from your specific first post --> Q&A section , number

Q14: I want to replace my boot animation and/or boot logo. How do I do that?

Copy the lsec6315update binary and your bootanimation.zip and/or your LOGO.bmp onto a clean USB-stick and connect it to your unit. It will only flash your bootanimation and your boot logo.

I have of course requested the original firmware they provide, and I have even scheduled a meeting with them, which they no-showed for (they scheduled, and didn't show a virtual meeting) I am still awaiting them for this. I did make a backup, via the FTP Factory Manager, provided in the FTP Factory Firmware.

I hope this clears up the confusion I may have caused, but alas, stuck currently at the booting screen of an android green logo, with the verbiage "fastboot" at the top.

Appreciate any help.

Chris