yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
Some prefer the look & feel of the launcher highly over any launcher from Joying as it really focuses on cars, like the launchers on builtin units in modern cars. The other apks are the same.

Note that the launcher needs some "internal" software as well which means you can't simply install their launcher on your Joying (I already tied and someone else "also experienced" here tried it as well. Can't remember who that was).

Next to that they deliver additional voice control software as the Google voice has the same issues on the T'eyes as on the Joying (after all it's all FYT firmware), so on some (most?) units Google Voice works, on others it doesn't (like mine). To overcome that they deliver additional voice control software.

And there are a few other more Russian related apks.

But the biggest benefit is that they still deliver new firmwares trying to remove bugs and keep up-to-date with Android 8.1 patches.

And the community on 4pda has more developers than we have here.
[FYT Android Head Units] techy101:
My unit also has the 1280x720 displays so I've not been able to play with other firmwares. I'm a hardware engineer so have very little coding expertise (other than bare-metal stuff in C).

It looks like they officially released the new 10.1" unit in both single and double in configurations. I'm going to get one and will do a full review and deep dive when it comes in. I'm also happy to take requests for things to test.

https://www.youtube.com/watch?v=_wiLTQoSNhU

https://www.joyingauto.com/joying-n...stereo-with-powerful-android-10-0-system.html
[FYT Android Head Units] ricanxd:
If you can let me know if they release it for the 1280x720. Wouldn't mind flashing a new firmware
[FYT Android Head Units] surfer63:
Well, I showed you the link. I do not have more info than that. Just keep an eye on it. Maybe they will release a 1280x720 firmware. I am not going to track that same link for you.

---------- Post added at 08:31 PM ---------- Previous post was at 08:28 PM ----------

Try to negotiate with Joying. Say that you just bought a unit and now they release a new one.

Some users did that also when Joying sold the first set of PX5s and then released a better PX5. They had to return the old unit but got some big reduction on the new one.

It can't hurt to try that as well for this unit.
[FYT Android Head Units] ricanxd:
Sorry I completely missed the link. Thanks
[FYT Android Head Units] julien_blanche:
Good for you and congrats for your next head unit however not everything as it seems like on the product page on new head unit, looking forward to see your thoughts though..
[FYT Android Head Units] bogdi1988:
I'll keep y'all posted! One of the things that sold me on it was the 5GHz wifi. Be default Samsung phones go to a 5GHz hot spot unless you configure that manually to 2.4 so I am excited for the faster wireless connection and less things to change on my part.
[FYT Android Head Units] julien_blanche:
Joying had a problem with wifi speed that it drops dramatically when you connect your phone's Bluetooth and wifi hotspot at the same time caused by head unit is using same bandwidth for them

I did a test when i bought the head unit;

only wifi is connected: 50mpbs

bluetooth and wifi are connected: 6-7 mpbs

I hope that they have overcome with that problem on their new headunit

cheers...
[FYT Android Head Units] bogdi1988:
I don't even hook up the bluetooth on the unit. WiFi reception is still fairly garbage.
[FYT Android Head Units] ronin4740:
I asked about returning the unit I just bought and they will let me but they want me to ship it to China... And their reply was kinda confusing. Said something about returning in two days and not opening it when I asked if I could return the unit I have after I receive the new unit.

Guessing they want it back now rather than letting me wait unit the new order arrives... That's fine but am wondering what they'll do since I have already installed it.

Also need a faceplate kit which I can only get from China at the moment.

Will probably buy the new unit and ship the one I have back. Just waiting to see if I can return to their USA warehouse instead as it will save on shipping costs.
[FYT Android Head Units] lexuz:
Normally you have to ship it back to china. I've paid with PayPal and had them pay (partially) for the shipment. Kiting customer service is not bad in this situations. You will need some patience to deal with them because of the language barrier.
[FYT Android Head Units] ricanxd:
I sent them something back once to swap and they asked for proof of shipping and then they shipped me the new unit once I proved I sent it out.
[FYT Android Head Units] Baby.Boy:
Hello and thank you for sharing this firmware.

My device is not exactly Joying, but Joying's firmware and MCU is installed on it.

Anyways, I tried Teyes ROM and while it is amazing, I have a problem.

It says the MCU and UI is not matched, meaning that the MCU is not right for the ROM, which is correct, and I tried to install their MCU, but it is giving me error when it checks the second file, which is the lsec6521update, because when it checks the stm32ud, it says successful.

I tried different lsec6521update from Teyes, but none of them works; any idea?

BTW, most of the things works on the ROM without MCU update, I have found only one thing that doesn't work and it is the default music player which I'm not gonna use anyway, but there is an annoying banner at the top of the screen that makes me want to upgrade the MCU.

EDIT:

I was able to fix the music player; the ROM is working excellent, the only thing is the always on top message that says the MCU doesn't match the UI.

EDIT 2:

After literally hours of trial and searching, it seems like I have found the solution, except that it doesn't resolve the issue.

Apparently I have to change the ro.build.fytmanufacturer in the fyt.prop, which I do, to 43, but after I flash it, the message is still there.

I have changed the "ro.fyt.uiid" as well as removing a warning in the fyt.prop.

I don't know what to do anymore.

I had installed MEKEDE ROM and had no such issue.

Please help me if you can, 'cause I don't know what to do anymore.

BTW, if I change the entire fyt.prop(to my previous one), the message disappears, but that introduces another problem, which is the "Settings" not opening anymore.

UPDATE 3:

Sooo for some reason, when I change the manufacturer code today, the message goes away, however, the problem of "Settings" not opening after that still remains.

I haven't changed anything besides the manufacturer code, I have even installed the ROM again with wipe data, but still I can't open the settings after changing the manufacturer.

Last update:

After installing different versions of the firmware and changing the manufacturer code, I'm still facing the same issue, which is settings not opening up.

I'm tired of flashing for 50th time.

If you can think of anything, I'd appreciate it if you could share your thought.

Thanks.
[FYT Android Head Units] surfer63:
With regard to the new uis7862 units (and maybe we need a new thread for it as this is the SC9853i thread):

I got my hands on a competitor firmware.

The system/vendor partition and new sock0 and product partition are still brotli compressed sdat images and can easily be converted to default ext4 (or squashfs) images using brotli and sdat2img (and optionally mksquashfs).

The new sock0 partition seems to contain the kernel drivers.

The Allapp.pkg has changed to a AllAppUpdate.bin file.

It is now a zip archive but protected with a password, and I did not find the password yet.

When simply unpacking the entire folder structure for the apks is unpacked but not the files (apks, libraries, etc).

It seems there are 3 new apks: TXZCore, appstoreDAMS and a "190000000_com.syu.voice". Is this the same voice command app already delivered with the T'eyes units next to Google Voice?

Edit: And Joying now also starts selling new non-FYT PX5 Android 9 models like they did earlier as well?
[FYT Android Head Units] turboaxt488:
Has anyone had any issues with the am/FM tuner failing?

Mine worked for all of 10 minutes and now just makes a humming noise. Connections are good. I've made another post in the general forum and attached a Google drive video
[FYT Android Head Units] gamer765:
I shared the password on 4pda. I'll see if I can find it and post it here.

Password for unpacking AllAppUpdate.bin: 048a02243bb74474b25233bda3cd02f8
[FYT Android Head Units] Baby.Boy:
Hello.

I have a weird problem with WiFi.

I have 2 WiFi connection in my house and the unit connects to one of them everytime without any problem.

However, the second one has and old router and no matter what, the unit wouldn't connect to it.

It connects to phone hotspot without issues as well; so it's just that specific one that it doesn't connect to.

I've tried changing the channel, changing the name and password, but to no avail.

Any ideas?
[FYT Android Head Units] bennyasf:
how do i unpack? can i use winrar or 7zip?

edit was able to unpack with 7zip and all apps are there password worked great

edit 2: i can get the links to all android 10 firmware if needed but like someone else said you will get mcu and ui error but most things work also getting another firmware tonight with internal carplay activated
[FYT Android Head Units] gamer765:
Please post links if you can. Even better if you can get Teyes CC2+ firmware.
[FYT Android Head Units] bennyasf:
i believe this is it (https://files.fm/u/zbrbnqv4) all firmware i have is found on 4pda
[FYT Android Head Units] Baby.Boy:
I have tried Teyes firmwares(both CC2 and SPRO) and as I said when I set the manufacturer code, the settings doesn't open anymore.

Please post your results if you are successful with these firmwares, or possibly even a solution.
[FYT Android Head Units] kouklo:
Is it 5G? I've never been able to connect to 5G with my device, It cant even see any kind of 5G network. Im not even sure if the unit can do 5G, Its strange tho because I didnt even know it was possible to buy anything that didnt have 5G. LOL
[FYT Android Head Units] Baby.Boy:
No, as I said the one that it doesn't connect to has an old router/modem, and it isn't 5G, the other one is not 5G either.

The unit is able to detect and show the WiFi, but it just doesn't connect to it, and it doesn't report any errors either.

The problem is that the other WiFi that the unit connects to is kind of far and is a bit wonky, otherwise it would be fine.

IDK if it's because of headunit itself or the modem, I'd say the modem because otherwise it would've had problems with other WiFi too.
[FYT Android Head Units] bennyasf:
how did you change to manufacture code?
[FYT Android Head Units] Baby.Boy:
After installing the firmware, extract the allapp file and change it in the fyt.prop, repack it and flash the allapp only.

Don't flash it with the firmware, otherwise you'd get signature error.
[FYT Android Head Units] bennyasf:
how do yuo flash the app only and how do you repack?
[FYT Android Head Units] surfer63:
Look at my thread https://xdaforums.com/android-auto/android-head-units/modding-joying-fyt-sc9853i-unit-root-t3974357

post 1, 2 and 3

It doesn't describe the altering of the manufcturer id and optionally the "sys.fyt.bluetooth_type" though.
[FYT Android Head Units] gamer765:
Brother, try this settings apk. I removed the check on startup. It's good to find out all restrictions and patch them. I'm in the process of creating a firmware based on the Teyes firmware and am patching all apps to remove their DRM. I'm pretty much done, but I'm stumped on one apk, MonoAuth, I dont really understand what it is for and i dont have the patience to keep digging in it. I'm mainly waiting for Teyes CC2+/CC3 firmware to drop so I could use those launchers as they'll work for all screen resolutions.
[FYT Android Head Units] Baby.Boy:
Thank you very much!!

I thought there was something wrong with my unit, albeit very unlikely, because it seemed like other people were able to install it; so they have some sort of DRM, I see, thanks a lot.

You have no idea how many times I have flashed their firmware, trying different versions and various methods, just to make it work, but to no avail.

Although I can't download the file, it gives me error 404, not sure if it's XDA or what...
[FYT Android Head Units] gamer765:
Something must have gone wrong. Try this one. [MENTION=6861316]Baby.Boy[/MENTION] Seems uploads on XDA are broken. Try this link instead.

https://anonymousfiles.io/yYFs7M3U/
[FYT Android Head Units] bennyasf:
does this apply to the new untis? since they dont have the app pack but .bin instead
[FYT Android Head Units] surfer63:
I already wrote about that one and how to unpack the rest of the ROM. It was even in this thread maybe 2 days ago.

It's password protected zip file. And [MENTION=1488726]gamer765[/MENTION] wrote what the password was.
[FYT Android Head Units] marcus82:
stupid question... ma how do you call from this head unit? because using stock app is not user friendly while driving and I'd like to use voice commands

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[FYT Android Head Units] gamer765:
I'm one of the few lucky ones that Google Assistant works for making calls. I just tell it to call someone and it makes the call. It appears to be a huge YMMV for everyone.
[FYT Android Head Units] marcus82:
wow, how does it work?

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[FYT Android Head Units] gamer765:
The same way it works on your phone. Say the hotword and give it the command.
[FYT Android Head Units] marcus82:
strange, my radio tell that it can't call

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[FYT Android Head Units] gamer765:
That's why I said im one of the lucky few it does work for.
[FYT Android Head Units] bennyasf:
yes i saw i was able to unpack but not able to repack my only options for repacking are .zip which is why i ask how to repack
[FYT Android Head Units] surfer63:
I assume you are on windows. If you would have been on Linux or MacOS it would be simple. Windows is based on file extensions. On other OSes you simply give it the name you want.

Maybe if you try with a command line zip, it might work.

And what you can try is just to zip it to AllAppUpdate..zip and then rename it to AllAppUpdate.bin.
[FYT Android Head Units] sean19661:
This fixes unmatched View attachment McuUnmatchUnlock.apk
[FYT Android Head Units] bogdi1988:
So I just got the unit and got it installed. So far, it is DAMN fast! WiFi is super fast as well! It installs apps soooo fast compared with the Intel one. Super happy with it. And yes, that bigger screen is money!
[FYT Android Head Units] bennyasf:
for the new radios or just the android 8.1?
[FYT Android Head Units] wooldogsinc:
This is the Teyes activation app to upgrade to CC2 firmware. Requires an unlock code and access to the internet.

May I ask how you bypassed restrictions?
[FYT Android Head Units] gamer765:
I manually patched each app that calls libsyu_jni.so to check for activation data. I removed said calls, so the app continues on without a clue that it needs to be activated. Since MonoAuth is the activation app, I will not touch it at all, it isnt needed. I was planning to do legit activations but it wont be possible since there are also checks on the MCU to check the vendor. Maybe with the new ARM based units, we could achieve something similar with an Xposed module. I am currently working on Teyes Voice as the activation stuff is handled in one of the native libraries. Even though I can enable everything in the Java side, the library still locks it down.
[FYT Android Head Units] wooldogsinc:
Activation request is removed by a small edit of the resource res/values/bools.xml to true

CC3 coming
[FYT Android Head Units] gamer765:
I'm aware you can modify a bool for activation, but I don't consider that a real crack. I prefer not to touch resources since sometimes resources don't decompile properly and then recompiling it is a headache. Plus editing the bools.xml doesn't fix the famous gray box on non Teyes devices, a smali patch is absolutely necessary. I believe I am the first to ever resolve this issue and make the launcher available to everyone outside of Teyes and Kingbeats. All other cracks only take care of the first check, which is enough to get it working on SPRO units to convert SPRO to CC2 without payment.

Also I'm aware CC3 is coming and I will be cracking that one as well for myself.
[FYT Android Head Units] Dhunt84:
Which unit did you get? I'm looking to get one now.
[FYT Android Head Units] bogdi1988:
Their new 10.1" unit with Android 10
[FYT Android Head Units] Dhunt84:
Do you know what cpu it has? And are you using a SIM card in the unit?
[FYT Android Head Units] teamoushy:
since i rooted and unrooted my SC9853i, bluetooth is not working, can some one advice me what to do? should i try #1611 ?

Edited, working fine after changing bluetooth to =3
[FYT Android Head Units] nolimitzr2:
Would a few of ya here with Joying/Mekede/Teyes or any similar FYT intel unit take a picture of the 20 pin harness that contains the 4g sim dongle...I need pin out for the subwoofer rca as Mekede packaged the wrong harness gonna take forever to get the harness so in mean while was going to move the pins from another unused RCA like CVBS and make subwoofer out.
[FYT Android Head Units] stefcio007:
I think I have an FYT compatible Intel unit. Any way to fix the annoying OBD bluetooth issue? I searched but can't go to the root folder to replace the stock SU bluetooth app.

Edit; I actually have an UiSC7862, is there a thread for these?
[FYT Android Head Units] lnfcrs:
Looks like my audio died, it cracked, popped and now no sound. I tried different headunit and sound works fine, therefore my unit is not producing sound anymore. Fuse is intact, cables looks good and now I have serious question. My HU has TDA7851L sound chip that most likely is the culprit and I have a working unit with Toshiba TCB501HQ sound chip. I am a newbie in electronics, but comparing datasheets it should be ok to just desolder and replace mine with the working one. Or am I wrong and it wont work like that?
[FYT Android Head Units] bogdi1988:
If the pinouts are the same then yeah. In and out ?
[FYT Android Head Units] techy101:
There may be some slight differences with the support components, specifically the input caps for the audio channels. The TDA7851L shows 0.1uF input caps while the TCB501HQ shows 0.22uF caps. This may make for a slightly higher cutoff frequency per page 5 of the TCB501HQ datasheet. Recommended power supply capacitance is also a bit higher for the TCB501HQ than the TDA7851L. In practice I don't think either of these will make an appreciable difference, but they are worth noting.

Pin 1 is used differently in the TCB501HQ, it's used as a DC offset detection pin, however page 11 of the datasheet mentions that it can be tied to GND if unused, which is how the typical application circuit of the TDA7851L is configured, so this also shouldn't be an issue.

Pin 25 is a bit confusing, The TDA7851L shows it being a "clipping detection" pin and the typical application circuit has it pulled high with a 47k pull-up resistor. The TCB501HQ calls it a high-side switch that looks to be an output to indicate the chip has powered on. From my pictures this pin looks unused because it's not connected on the top or bottom layers, but that doesn't mean it's not connected on any inner layers. However, I would expect that they've just ignored it.

TL;DR

If something else didn't fail which caused the chip to blow in the first place, it should work as a drop-in replacement
[FYT Android Head Units] lnfcrs:
Thanks, love to see descriptive and easy to read text!

This how pinouts look on my model JY-UOS03N4G. Pinging with multimeter Pin 1 ping with Pin 2,6,8,13,18,24. Pin 25 didn't ping with anything on the board and I tried to touch everything :laugh:

Also, can I somehow visually understand if it is "blown", because mine looks fine. And if it is indeed is fine, what other components might not give me sound, but everything else is working fine? I've tried sound from any source and first I've had loud cracking sound like some wires are touching, but after no sound appears at all. I've looked the board for vizual solder cracks or even maybe corrosion or dirt, but everything looks ok.
[FYT Android Head Units] techy101:
Do you get any signal from the RCA outputs?
[FYT Android Head Units] lnfcrs:
I don't use RCA, only standard wires. Still checked by connecting HU back in the car. No Volts shown when trying to measure RCA outputs. There are 6V reading from ground wire to any audio output wire. Also have done complete erase and still no audio comes from music and other sources, but there is system touch sound and also radio is hissing, but couldn't find any station with sound( I have never used it before, so dunno I was like that before).
[FYT Android Head Units] techy101:
Do you mean you've never used it before at all?
[FYT Android Head Units] wooldogsinc:
CC3 is out with a lot of bugs on 4pda

Will you be sharing your deactivated build's?
[FYT Android Head Units] gamer765:
I've already cracked the CC3 launcher, but it won't work just yet since Teyes started encrypting their resources. We don't yet have the password to decrypt the resources so it won't be working for a while. Someone managed to get it to launch, minus the encrypted resources. If we plan on ever getting it to work, we need dumps from an actual CC3 unit to extract the decryption keys.
[FYT Android Head Units] ricanxd:
I'm looking to switch to one of those teyes units. They have a custom one for my car. CC2 plus with Android 10 6+128 gb QLED.
[FYT Android Head Units] lebossejames:
Dear,

Do you know why BLE is not supported with the last firmware?

https://developer.android.com/guide/topics/connectivity/bluetooth-le
[FYT Android Head Units] blinger:
Anyone with a teyes 9 inch unit could take a photo of their circuit board behind the capacitive buttons? I want to see if I can solder the missing components to retrofit it in my 9inch joying without capacitive buttons.
[FYT Android Head Units] Guyzer73:
Hi,

It's been a while. I now have a FYT clone and am having the issues with the panel light buttons. In my case they are hard buttons, not touch type.

Do you think it would be worth trying to install the only firmware I have with twipe_all and then reinstalling the same with twipe_data to get the panel lights working?

I'm currently waiting for the Android 10 firmware which has been promised, and could in theory do it at that time by installing the old firmware (downloaded with no other firmware on the PC) with twipe_all and then the new Android 10 with twipe_data.

I have nothing but time to lose, but thought I'd ask what you think? And it gets on my OCD nerves that whilst the illumination comes on with the "small lights" control, it's white and not green as the rest of the car. I've already tried the manual setting of the colour through RGB input and this did nothing....

Thanks

Guy
[FYT Android Head Units] bommelkopp:
Questions about Teyes FW on Joying

Hi,

i own a JY-UOS01N4, specs from title.

Original FW, also with updates worries me a lot...

So: When i flash the actual Teyes FW, would it be possible to use the SWC-buttons each twice (short and long press)? Joying FW is not able to differentiate that...

And: In the root directory of unzipped FW is a "config.txt" where settings for language can be made. Will german language appear directly after flashing?

Thanks

Bommel
[FYT Android Head Units] gamer765:
1. Flashing original Teyes firmware will not work, you will be left with an inoperable device.

2. Long press and short press steering wheel control programming is a Teyes exclusive feature requiring a Teyes CC2 corresponding MCU. You will not be able to flash it on your Joying. You must switch steering wheel control back to Joying or at least to SPRO.

3. If you put the correct language code in config.txt the unit will boot to the selected language.

If you plan on using CC2, I suggest you check 4PDA forums for my release of cracked CC2. That is my final release since I no longer use Joying SC9853i, I've moved on to a Joying UIS7862 that I've converted to Teyes CC3.