yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] syfq91:
Hi, I flashed joying firmware on my sinosmart headunit (changed the manufacturer code to sinosmart). The flashing is successful but now about 1/3 for the screen is not responding to touch. I tried calibrating in the setting, it shows this message:

"Screen resolution: 1024x600; Touch resolution: 1080x600"

Is the message okay? The touch resolution is higher than my screen resolution (1024x600)

And the calibration does not work, the middle of the screen is still not responding.

When I tried to reflashed back to my original sinosmart firmware, the screen still not working properly.

Anyone have any idea on how to fix this?
[FYT Android Head Units] gamer765:
Sounds almost like you flashed a display/touch config file when cross flashing. List the files that were present when flashing.
[FYT Android Head Units] NRGZ28:
That sounds awesome. Going to try this on my Joying unit :)
[FYT Android Head Units] gamer765:
Forgot to mention, dont flash the MCU bin file and dont flash the hex file as well.
[FYT Android Head Units] Rafeesgh:
Hello i have fyt teyes cc2l and i want to remove dsp app and use in the link dsp app ... how can i do it in fyt units? https://xdaforums.com/android-auto/mtcd-software-development/mod-bd375xx-sound-processor-t3834657
[FYT Android Head Units] gamer765:
You cant. That link is for MTCE MCU units only. That mod will not work on your unit. Apart from the APK, you need a modded MCU which is not available for TZY. Also, you're posting in the wrong thread since Teyes CC2L is not SC9853i based.
[FYT Android Head Units] Rafeesgh:
I have been told that bd37033 is not controlled by mcu in fyt units ... its by system.ms apk ish or something or system server
[FYT Android Head Units] NRGZ28:
THanks for that. I haven't been able to find a download spot for the Teyes ROM yet. Maybe my Chrome translate from Russian to English not just not good enough...

nevermind... found it at cc2.teyes.../down
[FYT Android Head Units] syfq91:
I flashed using this Joying FW. File name-> 9853i OS 1024X600 800X480 1280X720 2020.4.7

oem (folder)/
- 3Ddongtai_V1.8.apk
- Torque_pro v1.8.54.apk
- zlink-v3.4.2.apk
- EasyConnected.apk
- TPMS_USB_U06_M.apk
6521_1.zip
Allapp.pkg
config.txt
lsec6521update

For reference, here is my original Sinosmart FW. File name-> 4+64 20190806_LiJun

升级清除数据 (folder)/
- updatecfg.txt
L8-Normal-1024X600_48M (folder)/
- 6521lcdconfig.cfg
6521_1.zip
Allapp.pkg
config.txt
logo.bmp
lsec6521update
更新记录.txt

I attached the Sinosmart 6521lcdconfig.cfg file in case you want to check. Not sure if this cause the issue.
[FYT Android Head Units] surfer63:
That's more or less correct. See this repo for the sofia, but actually not much has changed.

https://github.com/lbdroid/BD37033Controller

But it's no longer maintained, just like the rest of the repos (MCUradio, MCUd, SWI_for_MCUd, etc.). The developer has long moved on to other devices.
[FYT Android Head Units] Rafeesgh:
Can I modify stock dsp app on fyt head unit?
[FYT Android Head Units] tchleb:
I have an OnePlus 7t which overs tethering over Bluetooth. How I can use internet over Bluetooth on a sc9853i fyt head unit?
[FYT Android Head Units] techy101:
I've never tried over Bluetooth, but it's simple if you run a WiFi hotspot (if you're plan allows you to do that)
[FYT Android Head Units] tchleb:
Yes a Wifi Hotspot is more simpler, but an Wifi Hotspot drains more battery as a Bluetooth PAN.

The other advantage is that a bluetooth connection already exists because of the bluetooth hands-free system.
[FYT Android Head Units] surfer63:
I had not much success with that either. Being a low-energy protocol I also wanted to use a BT hotspot from my phone, but somehow the unit does not work correctly with it.

It is limited to 1.5MBs but for traffic info coming in at 1~5 Kbs, that is a complete overshoot (using offline navigation).

If I share my BT-hotspot to the phones of my wife and daughter it works fine. Just not with the unit.

I blame it on the crippled BT implementation, but that's just an educated guess.

Note also that BT knows many sub-protocols where hands-free and audio streaming are just two (and then audio also knows multiple sub-protocols).
[FYT Android Head Units] tchleb:
With which app you tried? I tried it successfully with BTTether.apk

The app works, but the PAN Auto-connect doesn't not work every time automatically ( I have to press the connect button).

Music Streaming and Google maps works well. With Spotify I don't have any buffering time.

I haven't measured the speed yet.
[FYT Android Head Units] surfer63:
With the BTTether.apk you still mean the lbdroid BTTether.apk?

That's a good one but I think it needs an optional delay time to make sure bluetooth is up and working on the unit after sleep. You might try to use it with fytstarter with some delay.

BTTether was made for android 5/6. It might also be due to Android changed access on Android 7+. You need some extra BT authorisations. If the bttether apk is faster than the units BT, it might not have the access rights to switch on BT.

Maybe I should have a look at that (if I can still find the source code somewhere. It is not anymore on lbdroids repository).

Currently I use macro droid to check on my phone whether I have a BT connection with my unit. If so, the wifi hotspot on my phone is automatically switched on. When the phone loses contact with the unit BT signal, it stops the phone hotspot again. Works fine.

Maybe I should dive into BT again, but WiFi tethering works fine and via the cigarette lighter I can charge my phone as well on longer trips
[FYT Android Head Units] tjuchta:
Ullgo for Dodge Caliber

Android 9.0

APP 1024x600 2020-04-09

CPU:Intel X86_Octa-Core 1.8GHz SC9853 @ 4.0 Gb(Memory)+ 64 Gb(Storage)

MCU Version 2020.05.20 11:29:02 KERD_53_L82_G23P48F64_V:1.0

I Welcome You! Dear help with the purchased Ullgo device for Dodge Caliber the seller sent the firmware in the archive Filemail.com -Firmware of Caliber.zip with only two files 6521_1.zip and lsec6521update. This is an incomplete firmware of the main file no Allapp.pkg. I want to install OS from JOYING. Coca factory code of the manufacturer Ullgo fytmanufacturer=?

Thank you in advance!
[FYT Android Head Units] surfer63:
I do not know whether this is a FYT compatible if it is really Android 9. Did you check that?

That doesn't have to be that way. Some package the Allap apps inside the system.new.br inside the 6521

And if it is Android 9 you can't flash it with Joying software as Joying only has 8.1 for the SC9853i.
[FYT Android Head Units] tjuchta:
hidden radio settings
[FYT Android Head Units] tchleb:
Short update, i found an good & stable Bluetooth Tethering app. Connection between Server & Client works without any coupling problems. The App is called Bluetooth Tethering Manager. There is an Pro version available which supports to start / stop the service over intents.

The connection speed with bluetooth tethering is limited, but for streaming music & update radar / traffic informations is good enough. The benefit for me is that i don't have to start an wifi hotspot which drains the battery more as a bluetooth tethering.

BTW do you know which apps get started before the head unit enters the deep sleep?

I know that after power on / awake from sleep following apps get started (if available )

com.youzi.customer.service

com.syu.market.StartPushService

com.syu.widget.RestartService2

com.syu.widget.RestartService

com.syu.music.Widget

com.syu.dvr.StartDvrService

com.syu.voice.VoiceService

com .txznet.adapter.BootService

com.syu.air.AirService

com.ankai.cardvr.service.ProxyService

com.cpsdna.mirror

com.ecar.assistantnew

com.yh.devicehelper

intent.action.mapgoo.data.sy
[FYT Android Head Units] lebossejames:
Dear,

Have you apk file for application AUX please?

Can you to know how it can display video from AUX signal by code please?

Thank you.
[FYT Android Head Units] Huttah:
Just wanted to report, this NAVITECH 9.7inch Display Head Unit (based upon a lot of reading this thread and others), appears to be an FYT unit running an SC9853i through and through. The update files provided by NAVITECH are identical in naming structure to those listed here, and the PIN codes as outlined in the Q&A thread correspond with the ones on my unit. This made me comfortable enough to attempt utilizing the Developer.zip and its instructions, and it rooted perfectly with full Superuser access through Magisk.

JET apk seemed to recognize the head unit as well, and though I've not fully utilized it, what I've tested seems to work. HWOneKey only works for the BAND hardware button, however. The others do not respond to it at all. When I received a call earlier today, instead of the tiny Bluetooth widget appearing on screen, I was greeted by the prompt asking which app I wanted to open (Bluetooth or HWOneKey), so that seems to work? It would be cool to get the other buttons working, though, and I'm hoping I can perhaps receive a bit of help in this direction.
[FYT Android Head Units] crazyg4merz:
Hello, thank you for the awesome guide. I want to make my own list of apps that I don't want to get killed. But I'm confused about how it works. Here's the base mod that I want to modify: https://4pda.ru/forum/index.php?showtopic=936715&st=29420#entry100221664.

As you can see. There's skipkillapp.prop file for the system and there is unkill_app.txt file inside the 190000000_com.syu.ms.apk package. I thought they should be the same list of apps inside those two file, but it's not. Am I missing something here? I thought unkill_app is a list of apps I don't want to kill and skipkillapp is a list of apps that will be killed when there's OOM problem. Isn't it? Thanks before.
[FYT Android Head Units] angelparras:
Hi @surfer63, how is it going? Now i am asking about the SC9853i ROM, there is any update?

Even about allapp.pkg

If i remove apps like video or bt music from the allapp.pkg, whe i use the SOURCE button, ¿can I avoid those unuseful apps?

After 1 year i am thinking about changing again to px6 because the system. I like the speed but the Joying System is unuseful and i hate it.

Thank you so much.
[FYT Android Head Units] surfer63:
There is no update about the ROM

Yes, you can remove those apps from the ROM but it doesn't make your unit faster or better.

You can't remove the radio apk.

Personally I stopped all "development" activities. Since 2016 we still have the exact same bugs on the latest units.On the previous units you could make XPosed modules to improve some things but not on this SC9853i. Maybe you can do that as well with the new UIS7862, but I don't think I will buy another Joying (although all those Chinese units have their flows which hardly get solved)

I have a 10" with 1280x720 IPS screen, and that one is very, very nice. I simply use the standard unit now using Magic Earth (primary) and OsmAnd (secondary) as navigation apps. I use the ZorillaSoft Folder player Full for music (as the unit also somehow removes the system media database occasionally thereby "breaking" playlists) and I use DABZ as radio app. That combi works nice for me and that is enough.
[FYT Android Head Units] surfer63:
I just mentioned that I won't do any "developments" anymore, but it is still "itching" ;)

@gamer765

About the T'eyes CC2 "custom" Rom for the Joying SC9853i.

Can we still use your Allapp.pkg on the 4 December CC2 release? Or do we (I) need to cherry pick some of the .apks/.props out of your allapp.pkg and create a new one?

Or are your modifications really ROM-date specific and can't we use it at all?

I assume you are no longer "supporting" the 9853i now that you are on the new UIS7862, but if so: Can you share with us what you (exactly) did?

Also: I checked whether you tried to modify the new T'eyes launcher (see attached) to accomodate 1280x720, but I can't find it anymore. Did you? and were you successful? Or is that the com.android.launcher3?
[FYT Android Head Units] gamer765:
I patched the checks in the following apks: bt, music, eq, launcher4, launcher8. Also I edited SystemUI and forced it load config_95 for Teyes UI. Settings was also edited to force customerid 95 for the app to even open also to enable Teyes specific settings like themes. I modified Teyes online radio and removed handling for an error code, which coincidentally unlocked the app (if it can't handle a failed DRM check, it just continues loading). I wouldn't cherry pick the apks from an old release since they probably optimized them in the newer updates.

I wasn't able to modify the launcher for 1280x720 screens. The launcher kept crashing even though everything was correct. Kind of gave up once I got UIS7862 and got CC3 working. The only launcher that does work on that size screen is launcher3, but that is the SPRO launcher. The CC2+ launchers work, but they have an issue running the PIP and instead run it fullscreen.
[FYT Android Head Units] surfer63:
Thanks for answering. I was already afraid so. It is too much work to do that for every new version. SystemUI and T'eyes ui are dependent on the framework-res.apk which is recompiled on every new version.

If Xposed would have worked on the 9853i, one could have written the Xposed hooks for those checks. That would have been more universal and possibly portable from version to version.

Actually this is positive. It saves me a lot of work :)
[FYT Android Head Units] gamer765:
The changes to the apks arent that big of an issue, since for most of them you can just do some changes in the xml. The only ones that really need extensive smali editing is settings and SystemUI. Launcher4 and Launcher8 needs a small smali patch to remove the grey box. I might do another release in the coming days.

I might actually do an Xposed plugin for the UIS7862 so I dont have to do the mods there either, all i would have to do is repack the encrypted oggs and thats it.
[FYT Android Head Units] gamer765:
Actually you can go ahead and cherrypick the apks from the new release. The changelog reveals nothing important was changed. Only Teyes Online and Teyes Radio were updated.
[FYT Android Head Units] surfer63:
You mentioned that you also changed the Settings.

Do you mean the Settings.apk or the 190095003_com.syu.settings.apk or both?

I made those "enhanced" system apk (190000000_com.syu.ms.apk: navii_app.txt, nokill, for the Joying). Did you have a look at that or simply didn't bother?
[FYT Android Head Units] gamer765:
I modded the 190095003_com.syu.settings.apk. I only did the navi_app to insert my preferred navigation app.
[FYT Android Head Units] surfer63:
OK
[FYT Android Head Units] silviox:
the mods of this thread only go for the Joying, or also for my H53 isudar which has the same processor? Thanks for the reply!
[FYT Android Head Units] surfer63:
Joyings are FYT compatibles.

Your Isudar is not a FYT compatible. It's an MTCD/E type unit. please look in those threads.

Actually the MTCD/E units have more tweaking options and they have 2 custom roms.
[FYT Android Head Units] silviox:
Tnx Surfer!

2 ROMS ? where ? re-tnx...
[FYT Android Head Units] surfer63:
HAL9K & Malaysk
[FYT Android Head Units] silviox:
But are for PX5-Px6-PX30 NOT for SC9853i like my H53 Isudar head unit :(
[FYT Android Head Units] surfer63:
Sorry. You are right.
[FYT Android Head Units] surfer63:
When mentioning that T'eyes had released a 4 December ROM and Joying the last one on 7 April 2020, I decided to do a test.

I completely unpacked both firmwares to the lowest partition level (unzip the 6521_1.zip, brotli unpacked the .br dat files, converted the dat files to file images, made squashfs images to redue size 3-6 times, and mounted these squashfs images. All on Linux of course).

I also unpacked the boot images.

When looking at the contents of vendor.img and the boot.img: they are binary identical

When looking at the system partitions: They are binary identical (apart from the build.prop file).

They both (but actually all FYT resellers I assume) do absolutely nothing with the system. The only thing that is done is that they push in their own user_id and vendor_id and make some minor alterations in the prop files. Again only to identify T'eyes versus Joying.

The only changes are in the Allapp.pkg, and then still on minor level. Layouts, some ("DRM like") checks by T'eyes, and the added apps by T'eyes.

So T'eyes updating and releasing ROMs between April and December only has to do with the Allapp.pkg, and ONLY with their own apps and modifications.

Fixing bugs like Google calling, external USB mass-storage writing, the Phone app deleting your Google contacts on sync, max of 255 contacts in phone app: Forget it! Completely untouched!

I already unpacked the Hal9K 4.0 ROM for the MTCD/E units. Not because I think it is compatible, but the developer solved some likewise issues on those units. That has to be "somewhere" in the init.*.rc files (which he copied/duplicated from the boot.img to the system.dat, same with some vendor data), in /system/etc config files, or his additionally created scripts running on startup or resuming from "deep sleep". (Not talking about the Phone app with its horrible bugs since 2016, as that is a FYT phone app).

From some primary investigations I must say though that the MTCD/E Microntek Roms also are 99% comparible with the FYT ROMs on Android system level, apart from being compiled for Arm64 instead of Intel64, and the ususal differences in config files between Android 9 or10 for the Hal9K, versus Android 8.1 on the SC9853i.

I assume all Roms come from some common (very old) base used by all those manufacturers and they contain for 90% the same hardware.
[FYT Android Head Units] yokala:
I flashed the CC2 firmware with the custom AllApp.pkg on my Joying and it's working great !

But how can I have the NoKill server mod ? The JET app keeps crashing on this custom firmware.

EDIT: I just made my own allapp with Surfer63 Nokill apk and it works just fine :)
[FYT Android Head Units] surfer63:
The JET apk only works if you have your unit rooted. Did you do that?

Next to that: I should check my app to see whether it needs "something" extra now the unit behaves as a T'eyes. I can't remember actually.

Furthermore: In post #3 of this thread are a number of pre-build flashable images. They contain also nokill modes. However, I do not know if T'eyes/FYT added something extra to their server apk as the T'eyes units contain some checking on their own apps.

If your unit is not rooted, you can use the rooted bootable image that someone made for the Joying 2020-04-07 as that boot image is identical to that of the 4 December one of T'eyes. Therefore is the rooted boot image also identical. (I did not create a rooted boot.img for the 2020-04-07 as I was not interested anymore in a rooted unit)

Edit: And I just find back in the "how to root .." thread that you already made a rooted boot.img for the 20200407 some time ago. That one could indeed be used for rooting your "T'eyes" unit.
[FYT Android Head Units] yokala:
Yep my unit is already rooted. I did not used my boot image from the 2020-04-07 as I didn't know if it was the same as the custom Teyes firmware so I use this one and patched it with magisk.
[FYT Android Head Units] surfer63:
I forgot to mention: Why don't you use the FYT_Starter apk? It is a much "cleaner" way of restarting your apps after a resume.
[FYT Android Head Units] surfer63:
Do you care to share your rooted boot image?

The original boot images are the same, but I'm still wondering if the Magisk rooting does something different on the T'eyes config or not. I am almost sure it doesn't, but you never know. I am simply curious and like to know.
[FYT Android Head Units] yokala:
Sure, here it is.
[FYT Android Head Units] surfer63:
I did not have time to compare the boot images yet (above), but I now have questions about the launcher3 (only CC2 launcher for 1280x720 screens) for the T'eyes CC2:

It's a widget based launcher. It shows the music player widget or radio widget bottom-right. (By default) the yandex navigation top-right, and some stupid useless car on the left (that is my opinion).

Before I flash the (slighly modified) T'eyes Rom I would like to know:

1. Does the navigation widget also work with other navigation apps?

2. Can you replace the left-car widget by something else? (I really think that's a huge waste of screen space.)

3. Does the launcher have other advantages over other launchers?
[FYT Android Head Units] yokala:
Well, as mentionned by gamer765 the launcher crashes when you choose this layout, the only one that works is the one from the Spro (see screenshot). I couln't find the apk for the cc3 launcher or the cc2+ and I'm not sure if it would work anyway.

Out of curiosity, I changed the resolution of my unit to 1024x600 and the launcher worked fine. The only thing you can change is In the general settings where there is an option to change the navigation to google maps (and it's the full app loaded in the 'widged', that's quite amazing). At the end I prefer having the native 1280x720 resolution with another launcher than downgrading to 1024 only for that.
[FYT Android Head Units] surfer63:
Then I completely misunderstood. I thought the image "01. Style" in your image IS/WAS the SPRO launcher. Sorry.

I am currently still switching between the Nova launcher and the CarWebGuru launcher.

Now, after a short time of use, are you glad you switched to the CC2 ROM? What are the advantages, apart from the "eye candy"?
[FYT Android Head Units] surfer63:
I already modified the main server apk from the 2020-12-04 CC2 firmware.

The default one, the extended one and a nokill version. Currently untested but as the main server is equal to the Joying ones, I don't expect issues. The T'eyes server is extended in functionality because of the options of the new launchers.

See https://github.com/hvdwolf/SC98531BinRepo/releases/tag/20201204

See for reference post #3
[FYT Android Head Units] yokala:
Honestly, at first I only needed to make a clean install on my unit because of incessant crashes and other bad stuffs and I saw the Teyes was available so I tried it.

I'm glad I did it however, it's a much cleaner and prettier interface, there is some cool extra features like the battery level of the BT connected phone in the status bar, when enabled the traffic monitor is on the left where the icon of the running app was previously (there is no icon now), the menu button in the status bar is opening the split screen menu witch is great. I wish all the navigation buttons were on the left, like in your screenshot but I thik it's only on the cc2+ and cc3. It's small things but I like it more than the ugly Joying interface :)

Excellent ! I use yours from the April Joying firmware, are they the same or you spotted some diferences ?
[FYT Android Head Units] surfer63:
If I switch to the Teyes I will of course try the launcher3, which is the SPRO launcher. I will also take a look at the layout xmls (I think)

And yes, I did find differences in the main servers, but like mentioned I only think it is extended w.r.t. the new functionalities that the T'eyes apps and launchers offer.

The basic stuff actually never changed since the Sofia server. Just an extra "if ..then ..else" for new hardware or the new android version (like earlier mentioned by @gamer765 and myself)
[FYT Android Head Units] yokala:
That would be cool !

I read somewhere that the ''premium' features of Teyes (voice, radio ) can be enabled by tweaking the apk themselves, that would also be cool if your have a chance to look into that too
[FYT Android Head Units] yokala:
I just found a major issue with this firmware, the steering wheel app isn't working at all. It recognize the input of the steering wheel buttons but when I click on a function to associate it, it doesn't do anything.

Is there a file or something where I can manually edit thes inputs ?

EDIT: I flashed back the original joying apk and it works fine, that's a shame the Teyes doesn't as it allows long press feature.
[FYT Android Head Units] surfer63:
I really don't know.

Do you have CANbus controlled SWC inside your steering wheel, or some 3rd party SWC control?

I assume you already checked video 21 on their FAQ page?