yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] Yaoxl:
I don't think so. The firmware package of the public version of UIS7862 contains a compressed package of screen parameters, which contains a variety of supported screen parameter files. In addition, the public version of UIS7862 also supports a variety of screen interfaces, including MIPI and LVDS (30~60PIN)
[FYT Android Head Units] warata:
This firmware did not install successfully on my JOYING 7862.

Has anyone succeeded?
[FYT Android Head Units] Sajito:
Hi warata,

I'm not sure, if I understand correctly what you want to achieve. Do you want to keep the unit on when there is a short "power loss", like when you start the engine? Or do you want to keep the unit on for some time when removing the key and therefore turning the car off completly?

If you want the unit to remain on when starting the engine, there is a setting in settings -> factory -> Original car agreement (or something like that), which is called something like "automatic start stop". When that setting is turned on the unit will stay active for 2 or 3 seconds after ACC Off. For me there is one regression though with that setting compared to the SC9853i android 8 units. The unit will stay on, but sound will still be muted for some seconds. The SC9853i units kept playing sound. Maybe someone on here has a solution for that issue?
[FYT Android Head Units] supersonic64126:
I'm considering getting one of these Joying Android 10 systems to replace my stock Honda Android head unit. The ability to actually be able to run apps natively due to actually usable hardware is very appealing. But I'm curious, is there a way to get these things to support multiple users/multiple profiles so that multiple drivers can each sign into their own apps and accounts with a single sign-in when starting the car? Joying tells me that this isn't possible, but I'm also not sure the understand what I'm saying.
[FYT Android Head Units] warata:
It is obviously a bug to stop the media with a short loss of ACC in less than a second to turn the starter motor in this 7862. It's strange to me that no one in this forum complains.
[FYT Android Head Units] surfer63:
I agree with you, but it is already an issue since the Sofia in 2016, and maybe earlier, but that was my first unit.

I don't know if other units (MTC) do the same. It should be configurable as lbdroid already wrote that for the Sofia.
[FYT Android Head Units] warata:
Hi Surfer, look at this

Since the official JOYING ROM has notifications disabled, it was not possible to interrupt the notification bar of Google Maps on top of other apps. But this was made possible by using a patch that writes the CC3 system UI created by 4PDA's @booroondook. JOYING sells new products one after another, but does not try to improve its functionality. Compared to that, teyes seems to be seriously trying to improve.
[FYT Android Head Units] erkanbasak:
[QUOTE = "warata, gönderi: 84357695, üye: 7432048"]

View attachment 5198197

Bu aygıt yazılımı, JOYING 7862 cihazıma başarıyla yüklenmedi.

Başarılı olan var mı?

[/ALINTI]

I have same problem
[FYT Android Head Units] erkanbasak:
I did fix this problem with capacitor connected on acc cable.

If you fix too watch video.
[FYT Android Head Units] warata:
Thank you. I'm not going to do that mod, but the JOYING 7682 has a big capacitor in it that has some electricity left. I don't know what it helps.
[FYT Android Head Units] warata:
BTW the font size setting has also been removed from this ROM. Has anyone succeeded in resizing the font without root?
[FYT Android Head Units] Sajito:
Weird thing is on my last two SC9853i units, this worked fine with the option I described. Only with the new android 10 units this seems to be broken again. So at some point they had units which worked as you would expect.
[FYT Android Head Units] MrTechie:
For those who were discussing the extension cable or mounting the screen away from the head unit:

I did this recently with this model.

The cable is not a standard IDE cable. I can't remember the correct description but I will try to send my mind back to the80s.

It is a 40 pin reversed (or flipped) flat ribbon cable using standard IDC 2mm pitch connectors.

What this means is: Pin 1 = Pin 40, Pin 3 = Pin 38 etc...

A standard IDE connector (AFAIR) is a straight cable, meaning Pin 1 = Pin 1 and Pin 40 = Pin 40

This type of cable is used for many other applications in electronics, so it's not like they made a proprietary cable.

I did an unboxing of the 10.1 unit here:

And a "remote screen" install here:

And here is a photo of the actual cable that came with the unit to show the connectors, registration keys, and pin outs (Note the red/pink stripe)

I hope it saves someone from blowing up their screen!

p.s. I could be mistaken, trying to find the exact pinout for an IDE cable seems to be a bit difficult. Please feel free to correct me if wrong, but link to the source rather than just your opinion so we can all learn.
[FYT Android Head Units] warata:
I heard that the traditional root method works, so I tried the @Copycat228 idea procedure, but it couldn't make a wi-fi adb connection with 7862.

setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
[FYT Android Head Units] surfer63:
That only works with userdebug releases.

The sc9853i and uis7862 are user releases

[ro.bootimage.build.fingerprint]: [SPRD/sp9853i_1h10_vmmTos/sp9853i_1h10:8.1.0/OPM2.171019.012/14212:user/release-keys]
[ro.build.description]: [sp9853i_1h10_vmmTos-user 8.1.0 OPM2.171019.012 14212 release-keys]
[ro.build.display.id]: [OPM2.171019.012 release-keys]
[ro.build.fingerprint]: [SPRD/sp9853i_1h10_vmmTos/sp9853i_1h10:8.1.0/OPM2.171019.012/14212:user/release-keys]
[ro.build.tags]: [release-keys]
[ro.build.version.release]: [8.1.0]
[ro.vendor.build.fingerprint]: [SPRD/sp9853i_1h10_vmmTos/sp9853i_1h10:8.1.0/OPM2.171019.012/14212:user/release-keys]

If you look for example at the older PX5 models (or the MTC models), you see something like:

[ro.bootimage.build.fingerprint]: [Android/px5/px5:8.0.0/OPR5.170623.007/bsp11071902:userdebug/test-keys]
[ro.build.description]: [px5-userdebug 8.0.0 OPR5.170623.007 eng.bsp.20181107.190240 test-keys]
[ro.build.display.id]: [px5-userdebug 8.0.0 OPR5.170623.007 eng.bsp.20181107.190240 test-keys]
[ro.build.fingerprint]: [Android/px5/px5:8.0.0/OPR5.170623.007/bsp11071902:userdebug/test-keys]
[ro.build.flavor]: [px5-userdebug]
[ro.build.type]: [userdebug]
[ro.vendor.build.fingerprint]: [Android/px5/px5:8.0.0/OPR5.170623.007/bsp11071902:userdebug/test-keys]

On the sc9853i, via the developer options, you can still enable ADB but only over USB. I don' t know for the uis7862 units.

Rooting via Magisk on the other hand should work. Please take a look at 4pda.
[FYT Android Head Units] warata:
Getting a 4PDA account was very hard, but the root method was easy. Anyway, thanks to that, I was finally able to change the dpi.

I remembered, So was Owince K6 (9853i) also a magisk method.
[FYT Android Head Units] shzlmnzl:
thats right. i use an 120cm IDC 40pin cable but not twisted ´(i did´nt find a twisted one with 120cm). I modified the middle edge of one side plug an twisted the plug... it works :)

do you know, where i could find an full black ribbon cable in this configuration?
[FYT Android Head Units] Sajito:
Does Magisk root work the same way like on sc9853i? Using the tools from here https://xdaforums.com/t/howto-root-joying-sc9853i-head-unit.3915530/? Or do I need something else?

Also can someone who is rooted already tell me if Google voice feedback still works after root? On sc9853i it didn't work after root.
[FYT Android Head Units] MrTechie:
If you want a black one, you could order any cable, and make your own ends on it. I think that would be the best way to get exactly what you want.

The connectors are very cheap and can be correctly installed by applying good average pressure across the plug. Im sure you can find some videos on youtube about it.

Good luck and let me know how it turns out
[FYT Android Head Units] Allan_Hun:
I'm just about ready to order my Navifly 9" QLED 7862 6/128G headunit. There is an 15$ option to add voice control software. I'm wondering if this is something I should get or not. Anyone knows if this voicecontrol software offers anything that googles voice control does not already offer?
[FYT Android Head Units] warata:
As you say, the Google Assistant was silent (at least it was working) after installing magisk. So I removed magisk and the unit never booted again. And I did a third firmware flash this week. But this time I added this syntax to the config file.

ro.sf.lcd_density=240

I was able to adjust the font size without magisk, but the Google Assistant stopped working.

However, the Google Assistant sometimes stopped working before I installed magisk, so its relevance to magisk is unknown. I will try to find a solution a little more.

I found that the Google Assistant app can no longer be used on ordinary smartphones. It seems that Google has disabled the assistant app because the long press of the home button still works. So what we should look for is a way to emulate a long press of the home button with the steering keys.
[FYT Android Head Units] surfer63:
(Some information regarding Magisk and rooting. No solution)

Magisk alters the boot image as you all know.

When comparing a magisk rooted boot image and a normal boot image (by completely unpacking them), the only thing that magisk is doing is replacing the init binary with its own version (and making a backup of the original in a hidden folder).

Nothing else is touched. It looks like ueventd and watchdogd are touched, but they are (and were) symlinks to init.

Booting an Android device is equal to booting a linux system: it all starts with the bootloader which does some things like mounting root (/) and also starting init. The init binary is the first "user space process/program" that runs (and has pid 1, identical to any linux system) and starts other processes.

It also starts the .rc files like the init.rc (which is identical on all android systems), and then the machine, device and specifc rc files. None of these is changed.

So I really have no clue why voice feedback is not working from Google Assistant. It is a known fact that Google doesn't like rooted devices and tries to block that more and more, and some applications simply do not funtion on a rooted device. That is why Magisk has the "hide root" option for apps that require this.

The only thing I can think of is that maybe voice feedback detects root, and maybe Magisk is not aware of this and can't hide it (and note that @bambapin already experimented with this (on a sc9853i) and hiding Google Assistant completely made no difference, so it also might be some "in between" process).

But that is just a guess.
[FYT Android Head Units] Sajito:
Since I've never read or heard someone with a device other than these head units, I somehow feel like this is not an issue with the Google apps. I think it's more likely that the original init binary does or triggers something that is required for Google voice to work.
[FYT Android Head Units] Allan_Hun:
Before I order my 7862+DAC I would really like to know how the spdif/Toslink work on these units.

Is it clean or as noisy as the analog rca outputs?

Will the unit play all audio incl bt phone calls through the digital outputs?

Does volume control work and how does low volume affect the soundquality?

Is it possible to get bitperfect output?

How is spdif combability with other devises?

Any other things worth noticing regarding the digital outputs?
[FYT Android Head Units] Allan_Hun:
No one tried using the digital outputs?
[FYT Android Head Units] Flavio:
I use the optical output to connect to my AWAVE DSP-6. I set the volume of the headunit at 36 and as far as I can measure it is distortion free. Everything plays through the optical output.

I use a separate AWAVE DRC remote control for my volume control because the volume control on the headunit is not very ergonomic and I prefer a rotary volume control.
[FYT Android Head Units] Allan_Hun:
Thank you for answering my question.

I would prefer to control volume with the buttons on my steering wheel, but I guess this will be software volume control causing lower audio resolution. Is 36 max volume or does it go higher?

Is it possible to get bitperfect output? And have you tried 24 bit / 96 kHz?
[FYT Android Head Units] Flavio:
Volume goes to 36.

What is bitperfect output?

Haven't tried 24/96 yet. I'll see if I have some tracks and test them.
[FYT Android Head Units] Allan_Hun:
Android normally resamples all audio to 48Khz and applies a denoise filter. Bitstreaming/bitperfect bypass all that and route the unaltered audio to the digital output. So the connected device (dac/dsp) does all the decoding.

If your dsp shows what it is receiving, you could try playing something that isn't 48Khz. If your dsp displays 48Khz when you play something that is not 48Khz it isn't bitperfect.

Many players (software) doesn't support bitperfect, but foobar and usb audio player pro does. Leaving decoding to external equipment normally results in better soundquality.
[FYT Android Head Units] berci--:
Hey, guys!

Hope you guys are doing great.

I have a radio with the same SoC, but a little bit different screen orientation and stuff.

I only have one question. When I put the "sys.fyt.bluetooth_type" value to "0", go to the Bluetooth app and connect my phone the connection status starts to flicker between "Connected" and "Disconnected" this makes the whole feature break.

My question is how can I make this work?

I would love to see some of your guys idea and start to get the issue solved from there. I tried many ways, debugging, trying different type of bluetooth apps and so on, that didn't fix the issue so I'm guessing it's a configuration issue under the hood.

Many thanks!
[FYT Android Head Units] caveiramix:
I think I may have found a workaround to the limited devices the stock Bluetooth settings allow you to see. Install a third party launcher like Agama and access Bluetooth settings from there, it goes directly to Android's AOSP Bluetooth settings and it has the default settings, as expected. Same for wifi.

Hope it helps!
[FYT Android Head Units] surfer63:
As such that is correct and more launchers can do that (CarWebGuru, Nova, etc.). But the BT app itself only allows very few devices to connect.
[FYT Android Head Units] surfer63:
I'm not 100% sure, but I thought this was based on the (integrated) BT chip and how the MCU controls it. You might need to change the value back to 1 or try up to 9.
[FYT Android Head Units] berci--:
I only tried the values from 0-5 but I will give the other ones a try too. What I noticed is that if I want to connect my ODB2 to the bluetooth then the only way to get it working is the 0 value, but if I want to have phone then only the "blank" option worked so far.

Appreciate the reply, hopefully we can find another way to get this working :)
[FYT Android Head Units] Allan_Hun:
With other similar units some users had success with usb BT dongles. But the dongles has to use same BT chip as the headunits internal BT chip. I don't know if this also works on this unit. But china made headunits seems to reuse a lot of code between different generations so it might be worth trying...

Personally I really don't get the logic behind producing a headunit with such nice hardware as this -only cripple it with awful software. How expensive can a decent china based software developer be?
[FYT Android Head Units] berci--:
I totally agree. I have a 9853 SoC radio too and what I noticed is that when I decompiled the "new" bluetooth app's (for 7862) apk the manifests had the same values as the 9853's(attached image).. so the it's a little bit lame that they did this. I guess that the whole issue starts at an app compatibility thing, sicne the 9853 was Android 8.1 and these new units are Android 10 the API has different side of locating and using things.

Hopefully this makes sense. And sadly I would prefer to get this somehow fixed by China or any modification via root and not use an external BT dongle.
[FYT Android Head Units] sciux:
Wonder if any of you can help me.

So I purchased 9" Chinese knock off HU with these specs: CPU uis7862

Ram 6gb+ 128gb ROM,

My issue is that when I make a phone call on Bluetooth app I can hear a person talking, but receiver can't hear me...

HU has its own microphone.

I've tried connecting 2 different phones through Bluetooth same stuff.

Checked permissions and Bluetooth app doesn't request microphone permission therefore I can't enable it.

Microphone does work on other apps.

Any ideas or suggestions?

I have enabled ADB, bootloader already OEM unlocked Hu arrived like that.

Can't find any more setting in extra settings that would help or even engineer mode.

Thanks in advance.
[FYT Android Head Units] surfer63:
Your unit is a TS10. TS stands for Topway Systems(?) (like TS9 sc9853i, TS8 PX5, etc.). You are now in a FYT based units thread. There are also a few other TS10 questions in this forum thread, and also in this sub-forum by several members seeking for help.

I suggest to create a new thread with something like "TS10 uis7862 head units - questions & answers". That might attract more users having the same kind of Topway based unit.
[FYT Android Head Units] sciux:
I wasn't aware of that, that's great to know thanks.
[FYT Android Head Units] Allan_Hun:
How can I know if the unit (merkede/navifly) I am going to order is TS or FYT based?

And what is difference from a users pov?

Does FYT based units have better support from the dev. community?
[FYT Android Head Units] surfer63:
Sometimes you can easily see it from the screens and which apps they show on the screens. Sometimes the only thing is to view and compare those by looking at Settings, the BT app, the radio app, etc. And then there is some "customer 0" who buys a unit and shares his/her system info asking "What is this ../ Can I root ../ etc.". And then you know for sure.

By reading these forums, you see every now and then a unit revealed as type XYZ using MCU firmware UVW. And of course: there are many experts in these forums knowing their "own" platform, and a bit about others.

NaviFly is mostly FYT based. I don't know Mekede. I see that their latest models use Snapdragon chips although they are called MSN89xy CPUs. No idea what MCU or firmware they have.

Sometimes you also have to look at colors and so on. The T'eyes units are FYT units but have "modernized" aps in that colours, buttons, etc. have been touched, but if you really look at the rest of the screen layout (for example the BT app), it is still 100% the same in functionality (and bugs).

If you want the best dev support (custom rom by Hal9K and Malaysk) and the most stable software, you should go for an MTCD unit. MTCD units are never sc9853i or uis 7862 units (so far). MTCD units are PX6/PX5/PX30/PX3 (so far). And then again: not all are MTCD units.

Chinese units don't really shine in quality, but some are slightly better and therefore sometimes more expensive. Cheaper units are often from small resellers offering no support at all, or slightly older models going away for low prices.
[FYT Android Head Units] Allan_Hun:
Thank you for the detailed answer. For your information I'm pretty sure navifly and merkede is actually the same company. Their unit cost exactly the same and specs/ui is identical. I think navifly is a sub firm of merkede.

I just read about hal9k cool features. Especially the do not kill while sleep white list is a feature I most definitely want -because I need torque pro to always be running. Anyone figured out how to get such feature on the FYT 7862 units?

This is kind of a dilemma for me because I also need rca Spdif audio output, best fm radio and really want qled 9" screen, fast hardware and possibly 4g sim card.

So what is the highest speced MTCD unit?

Teyes unit UI looks nice, but they are also quite expensive. Would it be possible to flash Teyes firmware if I get another brand with identical hardware?

I have noticed that some (maybe all?) 7862 unit features 3 usb ports. Anyone knows if all 3 ports share bandwidth? Because if they do share bw i guess a powered usb hub would offer similar performance.
[FYT Android Head Units] piyush7243:
I have. 6/128gb version of the HU and the steering wheel control doesn't seem to learn. Swapped wire harness etc but to no avail. Has anyone faced this issue in past?
[FYT Android Head Units] MrTechie:
I have the same model, it worked fine for me.

What is the actual problem?

Is the HU detecting inputs? Are the small numbers on the programming page changing?

The normal programming method is:

Open programming app

Press and hold button on steering wheel

Numbers at the top of the page should change.

While still holding SWC button, press the function you want it to do.

Release button.

Save

If theHU is not detecting any input: Are you sure your car has a resistive ladder style SWC buttons?
[FYT Android Head Units] piyush7243:
There is no detection of buttons in the software, nothing change in software. Not sure what you mean by resistive ladder style swc buttons
[FYT Android Head Units] toecheese:
I have posted here before about poor radio reception with my unit (JY-HQS01N4G-2) and have found the issue (and a fix).

I checked the unit's blue antenna power output wire with with a meter and it is only outputting 10.6V instead of 12V like it is supposed to. So instead of using that wire, I connected my car's signal booster to to the same 12V supply that feeds the headunit itself and PRESTO! I get normal radio reception again. The booster is not working properly with 10.6V, it really needs the full 12V.

I asked one other Joying owner to check and he is getting 12V from his antenna output. I suspect my unit is defective.

On the Joying forum there are two others reporting bad reception. I'd be curious to know if anyone here has the same issue, what antenna output voltage you are getting, and if this is a widespread fault with these units.
[FYT Android Head Units] warata:
I have the same experience as you with the PX5-FYT unit I once owned. After all it was solved by taking the antenna power from ACC.
[FYT Android Head Units] shzlmnzl:
same here. 10.6V on Antenna (blue) cable.

JY-UQS05N4G-H
[FYT Android Head Units] Bob_Sanders:
The blue antenna wire is not for the antenna signal booster.

It is a trigger wire for a power antenna (a motor driven antenna which goes up when being used, and folds down when not in use)
[FYT Android Head Units] tropby21:
same here. 10.6V on Antenna (blue) cable.

JY-UQD11N6G

The antenna power from ACC ist > 13,5V -

isn't that too much?

While driving the voltage goes over 15V !!
[FYT Android Head Units] ronaldp31:
my radio seems not work after i factory reset cannot find any radio station on fm can someone help how to fix it
[FYT Android Head Units] Bob_Sanders:
Not really.

14.7 volts is NORMAL charging voltage so you are only over by .3 volts.
[FYT Android Head Units] erikg5678:
Were you able to find any Tlink apks?
[FYT Android Head Units] shzlmnzl:
Hi there

I own this unit

Joying New Android 10.0 Single Din Car Radio with 9" IPS 1280*720 Screen

SKU: JY-UQS05N4G-HShip From: Chinese WarehouseCPU: UIS7862 12nm Dual ARM Cortex-A75 + Six ARM A55Ram: LPDDR4 4GB Rom:EMMC 64GBSupport Bluetooth, WiFi, DVR, OBD2, Back-Up Camera

www.joyingauto.com

how can i boot to recovery for an data/cache whipe?

long pressing on RST or POW or the small hole on the main unit is without success.

I want to do an full whipe because, since the Firmware Update the Fast Boot/deep sleep will not work.

The unit is correctly wired but the fast boot will not work. The unit turns off into stand by and after around 20 seconds it powered off completely.

In the menu i cannot change it to an other time. It stuck on OFF.

Also i notice it will not Bluetooth connect to my ZTE Axon 10 pro (no root or so) for hands free calling.

I can see the Joying Bluetooth in the ZTE and the other way too.

I've put on both sides the Bluetooth protocol to 1.4, 1.5, 1.6 but without success.

I had read Somewhere there are Problems with uis7862 and Bluetooth, but hands free calling is an Essential function...

it works with other smartphones, so the reason is on my ZTE...