yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
Now, that would be nice. I have no problem of copying it.

FYT themselves violate all international laws by not giving their software source code when asked for. Not for the FYT apps themselves as that is proprietary code, but for the modification of the underlying system software (like the bluetooth we discussed in another thread, the crippling of USB, and more) . The international Android license clearly states that when you modify it, and users ask for it that you have to share it.

Problem that many international lawyers face when trying to prosecute Chinese vendors, is that the Chinese government does not give them any chance.
[FYT Android Head Units] xadamadax:
Surfer, i am most excited to see what you personally will do with it :laugh: i'm just uploading it to my gdrive for now, will update with link.
[FYT Android Head Units] surfer63:
I am not sure if I can really do something with it, but I'm most interested in having a look into it. The way they build the graphic part of their own programs makes it hard to change the look and feel and impossible to use them in split-screen mode. Leaving the logic intact and changing the Gui into an auto-sizing, split-screen enabled mode would be nice.

So I might only go for the quick wins.

I hope that [MENTION=575209]bambapin[/MENTION] and [MENTION=1488726]gamer765[/MENTION] will also have a look at it. They are better programmers than I am.

There are also some good programmers on 4pda that might do wonders with the source code.

Although in general: I am currently really satisfied with my unit. The one annoying thing remains that I can't make phone calls via Google Voice (although I have a 2-step voice command work around), but that is not because I am using it, as I don't want to make phone calls in the car other than the ultra-short "Hi, I'm home in an hour. Bye". It is the fact that it should function, but it doesn't.

(Besides: I am working steadily on my own "non-car" photographic project. That is where I currently spend my time.)
[FYT Android Head Units] bambapin:
I'll do for sure!

I am very curious to see how the low-level services and the priorities of the audio mixer are implemented.

Thank you [MENTION=641999]xadamadax[/MENTION]!!!
[FYT Android Head Units] xadamadax:
You guys are very welcome, here is the link.

https://drive.google.com/drive/folders/10uNmmbkGoB8sR5hgUYZuFVD-WDb0gOY4?usp=sharing

Let me know if you have issues accessing
[FYT Android Head Units] techy101:
That's amazing, thank you!

It looks like they have the PCB files in there too. I can't wait to have a look at them.
[FYT Android Head Units] gamer765:
This is amazing, with this we should be able to do a lot of stuff with our units. We can even roll our own custom ROMs if we wanted. I'm not a ROM cook, but I can definitely use this for our bluetooth endeavors and possibly legitimately unlocking features that are locked on our units.
[FYT Android Head Units] gurishark:
This looks interesting, but sadly the code for the FYT apk's are not there or am I missing something?
[FYT Android Head Units] xadamadax:
My main motivation for sharing here :D

[MENTION=11086615]gurishark[/MENTION] - you need to download the split zip in source, extract it, and then extract the tar inside. The apps specifically are in \idh.code\packages\apps

There are also lots of python scripts and windows tools, and it seems apps that they use for configuration purposes and later remove. So should be a lot of powerful stuff.

I sell these in the vertical style for a few different cars and we run a custom rom that I'm looking to make much much better. [MENTION=11086615]gurishark[/MENTION], [MENTION=322244]gamer[/MENTION], [MENTION=575209]bambapin[/MENTION] or whomever PM me if you want to chat.
[FYT Android Head Units] gurishark:
[MENTION=641999]xadamadax[/MENTION] - I think the apps in \idh.code\packages\apps are the standard apps from Android AOSP source, not the FYT apps or modified by FYT version of the apps. But still lot's of nice stuff there :good:
[FYT Android Head Units] gamer765:
I agree with the above, theres no FYT apps in the source code, only the standard AOSP apps, plus a few Spreadtrum proprietary apps. True this dump is good for building new base ROMs, but you're gonna need to pull FYT proprietary APKs and libs from the stock ROM. We can probably use this dump to restore the bluetooth stack in our units. If we want to fix the FYT proprietary bluetooth app, we need the source for that. Its difficult to work on the ready built apks since theyre obfuscated and makes tracing hard. However, im more interested in getting source code to libsyujni.so so we could roll our own. Also, my time is mostly dedicated to reversing Teyes stuff. I'm working with a guy from 4PDA and got a fytdata dump from a CC2 unit to work with.
[FYT Android Head Units] xadamadax:
got it! sorry my mistake, glad it will help some. please share what you find from the dump from the cc2 :D as i'm sure you will. I spend time on 4da, but its a pain without an account and keyword search is trash with translate
[FYT Android Head Units] gamer765:
I managed to make an account using translate and found a trick online on how to bypass the annoying captcha, so I dont have to do it at all anymore. I only managed to get hold of this person because they have a Teyes unit that im guessing has issues and they want to basically convert a Joying unit to Teyes. So I asked for a dump and I found what I was looking for in it.
[FYT Android Head Units] surfer63:
I used the "howto" on this website to register on 4pda: https://www.offlinemods.net/2017/09/how-to-register-account-on-4pdaru.html

But there are more. Simply search for "register on 4pda" or "bypass 4pda captcha"
[FYT Android Head Units] gamer765:
Not sure if anyone is interested, but i've been working on this meanwhile I work on libsyu_jni hacking. Only tested the SPRO+ launcher since it finally includes 1280p resolution support. Pretty sure other launchers are working perfectly now as well. Fully optimized. The radio app was fixed to allow station logos outside of the europe area. Would be great if everyone could compile a logo database for all cities. I got lazy and only did some for NYC. Add logos to res\drawable-nodpi-v4 directory and add stations and city info to res\raw\radio_freqs.json. Now that i've got the basics down, I think i'm going to move on to Teyes firmware since it is likely that Joying will not update their firmware anymore.

SPRO+ Launcher: https://anonymousfiles.io/0htP2gCO/

CC2 Launchers: Removed since reported it doesn't work.

CC2 Radio with Logo support: https://anonymousfiles.io/TTAbC26x/
[FYT Android Head Units] surfer63:
Before I could not install the launcher on my system. What did you change? or was it only the the 1280x720 resolution?

And w.r.t. the logo database: I already looked at it and also mentioned this to someone else, but In Europe (at least in the Netherlands and Germany), it is different. Every region has its own frequency. A radio station can have 11 different frequencies in the Netherlands. Only for the Netherlands the database would be huge. so I stopped it for myself. Maybe even more because I now use DAB+.

And indeed: I am also thinking of switching to T'eyes.
[FYT Android Head Units] gamer765:
Only the SPRO+ launcher will work for our 720p unit since that one has the added 720p resources. The CC2 launchers will continue to work only on 640p resolution units with the exception of launcher8, that one has the necessary 720p resources. We have to wait for the CC2+ firmware to drop so we can grab the launcher from there. W.r.t. the logos, previously it would only show if you had Europe selected in the radio settings, if you had another other region selected, no logos would show, if you added your stations and logos to the apk, the app would crash if you tried to set your city. Now it's enabled for every region.
[FYT Android Head Units] gamer765:
Removed the CC2 launchers since I received report that the grey box still shows up.
[FYT Android Head Units] gamer765:
Found more activation stuff in com.syu.us.

I think I fully solved this issue. I believe it checks the MCU if it contains TZY, if not, it will throw a blank window.
[FYT Android Head Units] gamer765:
Please test this modded launcher. I believe it should work 100% now.

https://anonymousfiles.io/G1AQjNiQ/
[FYT Android Head Units] surfer63:
How should it be installed?

Simply put it on a usb-stick and install?

Or via a minimal apk flash?

I copied it onto a USB-stick and simply double-clicked it to install. It installed and I rebooted. Then absolutely nothing: only the configured background screen and a non-functional topbar.

Fortunately my steering keys still worked and I tried to start navigation, but "no navigation app was assigned" which made it possible to reassign CarWebGuru and then from CarWebGuru make that the default launcher again.

I tried twice, but twice after reboot I only got the configured background screen.

And actually this is exactly the same as when I tried with the original launcher.

And by the way: the apk is called "190095005_com.android.launcher4.apk", but when installed I can only select "launcher 3" as launcher (with the blue-white T'eyes "roof" icon").
[FYT Android Head Units] gamer765:
Forgot to mention, only for 640p and lower devices. Won't work for 720p. For 720p only the SPRO+ one will work. I am personally using that one on my device.
[FYT Android Head Units] surfer63:
Ah.

As you removed the CC2 launchers, I thought this was an improved version of the SPRO+ launcher. So I downloaded the SPRO+ launcher again from your previous post.

But it still doesn't want to install. The install starts and asks whether I want to accept all necessary rights, and when I click Continue (or Yes or whatever), I get the error triangle that it is not installed.
[FYT Android Head Units] gamer765:
You probably have another launcher installed with package name com.android.launcher4? Uninstall the previous ones before installing. I'll double check though maybe I uploaded the one without signing. My apologies, I uploaded one without a proper signature. Use this one instead. This one is the SPRO+ launcher with 720p support.

https://anonymousfiles.io/a5HFcBQD/
[FYT Android Head Units] surfer63:
One of my flash scripts removes all Joying/FYT launchers together with a lot of useless apps, incl. data and cache. I did that already months ago.

There is no Joying launcher on my system anymore. Only CarWebGuru and Nova.

But that also came to mind with me so I really did check: No trace of any Joying launcher.
[FYT Android Head Units] gamer765:
I posted an updated version above. I resigned it.

Here's what the SPRO+ launcher looks on my Joying.
[FYT Android Head Units] surfer63:
I don't want an upside down launcher :laugh:

This signed version installs fine and works fine. Thanks. :good:

I will test the coming days.

I already found out that my FYTHWOnekey does not work correctly with this new launcher. I wanted to reassign the BAND (radio) button to my DAB+, and the Music button to my media player, but it seems that it functions slightly different with this new launcher.
[FYT Android Head Units] techy101:
Just installed this on my 720 unit. Is there a way to revert to the stock Joying launcher, it seems to have disappeared when I installed this?
[FYT Android Head Units] gamer765:
Yes, uninstall the launcher. Go to settings and select the launcher, uninstall updates. The Joying launcher disappeared because it has the same package name.
[FYT Android Head Units] homer.ali:
I've been trying to read through this thread and I apologise if this is a frequently asked question.

I have a joying 13.3 inch sc9853i headunit with Android 8.1.

Unfortunately since this unit is so new (had to buy directly from joying by email) the firmware for it is NOT on the referenced joying blog..

I would like to root this unit/use some of the mods referenced in this thread but am a bit afraid as any firmware that I can see specifically references a screen density that is not the same as my headunits (1920x1080).

Is it possible for me to use the allapp.pkg method to flash mods into this unit and should I do so without fear?
[FYT Android Head Units] gamer765:
Received confirmation that my new patch fully works now and no more gray box. These are the new and updated and the very first time these launchers work on a unit that is not Teyes. Only for 640p resolution and lower.

CC2 Launchers: https://anonymousfiles.io/krNXTrdv/
[FYT Android Head Units] surfer63:
That should theoretically be possible, but without a proper name of your unit (like EU-JY-UOS02N3) we can't say for sure.

And you don't tell which mods you want to flash. On a new unit with new firmware and possibly new MCU firmware, I would certainly not flash an existing, and by now older, server mod.
[FYT Android Head Units] mastrv:
Is it possible to root a unit and then un-root it?

I think it would, but wanted to see what others thought. There are a couple of things that I want to do, such as adding package names to unkill_app.txt, navi_app.txt and a few other of these txt configuration files, but I want to leave the unit unrooted. I found when I rooted the unit that some things didn't work properly, such as Chrome not loading pages and the Play Store not downloading apps...those are the ones I can think of now.

Rooting and then un-rooting would also avoid having to create an AllApp archive and then flash it, etc. I would be able to root, make changes, and then un-root...or better yet, to backup/copy files that I may be testing with. There are changes/updates that the manufacturer makes and you can loose track of which one you have installed on your unit.

I would think it's possible due to the semi-automated method of rooting that was presented with the lsec.sh scripts. All you would need would be to have another script to write the original backup image to the unit...OR, change the name of the original image to magisk_patched.img and then use the write script to write it back out to un-root it.

Now that I've finished writing this out, it should be definitely be possible. I don't see any down side in doing this.

Lastly, is what I'm thinking of doing possible? Would updating those configuration txt files directly do what I want? Could someone point out the directory or directories where they are located...if not, I'll post them when I get around doing this. My unit is running well and there's no real need or rush to do this.

Thanks in advance
[FYT Android Head Units] surfer63:
Yes, of course. Simply flash the original boot image. Indeed using the lsec.sh script.
[FYT Android Head Units] homer.ali:
Hmm I'm mostly interested in just getting adb over WiFi working and maybe adding some apps to the nokill list so music autoresumes on restart.

I have my system info page attached as well as mcu version. I'm used to px5 headunits but none of the numbers here strike me as a common model name of this unit. As I said I ordered this directly by emailing joying as it is not a fully released unit yet.

It is the one in this video: [youtube]hu-kKUBxRRA[/youtube]
[FYT Android Head Units] surfer63:
It's huge. And the rotation is a nice gimmick, although I would not know whether you would use this often after 2 days of playing with it ;)

I don't even know whether this is a FYT unit. Can you run my HWGetInfo.apk (see signature) to see if this is a FYT compatible? It will immeidately say so and deliver a zip with all kind of info.

Forr all(!) the SC9853i's so far, adb over WiFi will never work, whether you root the unit or not. It is not supported by the kernel. I just explained that to [MENTION=6959209]bennyasf[/MENTION] in the rooting thread.

If you want autostarting apps after sleep, you better use [MENTION=575209]bambapin[/MENTION]'s fytstarter. It will simply start the apps, you select to be available after sleep. But that one will only work if it is a FYT compatible.
[FYT Android Head Units] surfer63:
Just to inform: These modded CC2 launchers and SPRO+ launchers only need to be adapted to make them run on non-T'eyes firmware? Right?

If you simply flash the T'eyes firmware on your unit, you only would need to alter the "ro.build.fytmanufacturer" to "43" (from ro.build.fytmanufacturer=95) and remove the below Russinan "stuff" from the config.txt to make it start in English.

ro.product.locale.language=ru
ro.product.locale.country=RU
persist.sys.language=ru
persist.sys.country=RU

Edit: and remove "persist.sys.timezone=Asia/Shanghai"

That is at least what 2 users did and what I advised other users to do (until now I was not interested enough to do it myself)..

Or does this DRM also affects your correct T'eyes software functioning on your Joying, if it detects another manufacturer id and thereby other MCU?

(And as a side-note: I am not sure whether I continue with the SPRO+ launcher. Just as with the Nova launcher, DAB+ always start after coming out of sleep. It does not do this with the CarWebGuru launcher. I already addressed this earlier to [MENTION=7838245]realzoulou[/MENTION], but he mentioned it had nothing to do with DAB+ and was due to Nova. I am not sure now. But that's for another thread)
[FYT Android Head Units] rackxp:
Did you install the teys firmware?
[FYT Android Head Units] gamer765:
Changing ro.build.fytmanufacturer to 43 only gets rid of the mcu mismatch error. The Teyes launchers, at least CC2, have built in DRM to prevent users from using the extra features without paying extra for them. If the launcher fails to find activation data in fytdata via libsyu_jni, it will throw an alert dialog requesting you to input your license. Existing patches on 4pda go this far, they only patch this check and it works for most users because they intend it for SPRO users who want CC2 features. They're aware of the gray box appearing for users on other head units, but they don't know how to patch it. The gray box appears because the launcher also checks the mcu version string to see if TZY exists. If it does, it will allow the launcher to operate, if TZY is not found, it will spawn a blank alert dialog that you cannot dismiss. My patch gets rid of this check altogether so the launcher will work as normal. What is the package name for DAB+?
[FYT Android Head Units] surfer63:
Thanks for the explanation

com.zoulou.dab
[FYT Android Head Units] gamer765:
I uploaded wrong version of patched CC2 launchers. This is the correct one.

https://anonymousfiles.io/AVV5tqGO/
[FYT Android Head Units] homer.ali:
Agreed-- "gimmick" is the exact word I used too.

The screen size is definitely nice though and it's blazing fast..again maybe my standards have just been lowered given my experience with previous headunits but this certainly seems to have been worth my money--even unmodded.

looks like it is based on reading about your software. Will be happy to provide the zip if you feel that would be helpful!

Hey thanks man! Looks like that does do what I want.

Only thing missing for me still is to be able to grant some apps secure access. I guess if adb/wifi isn't working I might have to use full root. Unless there's a usb port that allows for adb/usb. Do you happen to know of there are pitfalls down that route as well?
[FYT Android Head Units] surfer63:
If you enable developer options, you can use "adb over usb".

And there's another step to do. [MENTION=2534110]rigattoni[/MENTION] explained it somewhere in one of the 3 main 9853i threads.
[FYT Android Head Units] rackxp:
hey [MENTION=2550900]surfer63[/MENTION] is their a way I can flash my joying unit with another joying firmware? It has a strange DPI where it makes the CarPlay resolution really big? I have the unit with a 1024x720 screen? I've rooted and changed the DPI but still no change.
[FYT Android Head Units] surfer63:
If it is rooted, what do you get in a terminal if you give a

wm density

I guess it will (still) say 160.

All Joying firmwares come in 160 DPI. Flashing it with another Joying firmware will therefore not help.

I do not know if you use the Joying_Extra_tools on your rooted unit to set the DPI, but otherwise did you try it from the rooted terminal?

wm density 200

Do not go above 200, or test real good. The Joying/FYT apps do not autosize and can look completely distorted if you set the density too high.
[FYT Android Head Units] gamer765:
Done building my DRM free Teyes ROM, will hopefully get around to testing it today.
[FYT Android Head Units] rackxp:
I have done that. The issue is the ICONS get smaller but its like joying do something with the UI as they remain the same size?
[FYT Android Head Units] gamer765:
Tested and it works for me perfectly. Use latest CC2 base rom from the Teyes website and replace AllApp.pkg with my provided version. Only things not working yet is Teyes Voice. I set com.android.launcher3 as the default launcher on boot since it is the only launcher working on screen resolutions 1280x720. All other launchers are for resolutions 1040x640 and below. In other news Teyes is teasing release of CC3 and am eagerly awaiting for that ROM to drop to port that launcher.

https://drive.google.com/file/d/18xwMhs1OyN6uFmt9Mg3aQ_7pspgtAKVS/view?usp=sharing
[FYT Android Head Units] techy101:
Which display configuration(s) does this work with?
[FYT Android Head Units] gamer765:
Technically all, but the default launcher only. The other launchers are for 1040x640 and below only.
[FYT Android Head Units] techy101:
Shoot. That's what I get for having a 1280x720 unit ?
[FYT Android Head Units] gamer765:
I have the same 1280x720 unit, so I'm stuck with the default launcher, which is from SPRO, which is still better looking than the Joying default launchers.
[FYT Android Head Units] techy101:
Agreed 100% that it's better than the Joying launcher.

The unit I'm testing out right now is the 10.1" 1280x800 display which I would love to test another launcher out on.
[FYT Android Head Units] Android49:
mine is having this resolution 1024*768. Does this will work?
[FYT Android Head Units] gamer765:
You can give it a try, your unit might actually be 1280x720.
[FYT Android Head Units] rackxp:
Thanks mate,

I installed this however I just have a pink screen its like the launcher is missing?
[FYT Android Head Units] gamer765:
You can take apkpack and unpack it and you'll see launchers are there. Which FYT compatible unit did you try it on? What steps did you take to flashing? Did you also create an updatecfg.txt file with twipe_all in it?
[FYT Android Head Units] rackxp:
I just downloaded the file, replaced the file you said to and did the software upgrade when I stuck the USB key in?
[FYT Android Head Units] gamer765:
Generally, when you're crossflashing firmware from different vendors, it goes without saying that you need to completely wipe the device. Joying devices have an FYT ID of 43, Teyes has an ID of 95. Joying firmware has their ID number in the filenames of their apks such as 190043001_com.android.launcher3.apk and Teyes has 190095001_com.android.launcher3.apk for the launcher for example. If you dont wipe, you get both of those files with the same package name, but different file names so Android will not be able to load any one of them.
[FYT Android Head Units] rackxp:
Ok great. What’s the best way to wipe and start again?

Appreciate your help.
[FYT Android Head Units] gamer765:
Create an updatecfg.txt file with the following text in it.

Put it together with everything else you're flashing. Don't forget to make the necessary changes to config.txt and fyt.prop in AllApp.pkg.
[FYT Android Head Units] rackxp:
Thanks mate,

What changes are needed in the config file? and the FYT.prop?

I wiped the unit and with the updatecfg.txt but still have a pink screen.
[FYT Android Head Units] rackxp:
I fixed it by changing the config file to have the launcher of 3. I just need to figure out why I can't program my steering wheel controls.