yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] ronin4740:
Question about Joying units - JY-VO131N4GSN

I've skimmed through this forum and see some things I like about the Joying unit and a few that might cause some issues for me but as I'm still wanting to replace the aging RNS-315 in my VW with something that has Android Auto capability I'm wondering if the JY-VO131N4GSN is a decent unit (it's available in the US warehouse) or if there's a better recommendation?

I've looked a bit but haven't found a review on this unit. Would appreciate your thoughts.

Thanks.
[FYT Android Head Units] mclaudio:
Find a teyes unit

Enviado do meu SM-N975F através do Tapatalk
[FYT Android Head Units] techy101:
Hello,

Reading through everything I think I may have a newer firmware than the April version. If so, is there a way to dump it for people?
[FYT Android Head Units] eyalber:
Navigation app mute while radio is on

Hi,

I have the original Joying 8 core intel 4/64. Strange issue I have is that no matter what navigation software I'm using, if the radio is on in the background, the voice of the navigation software will not be heard. I can see that when the navigation voice is used, the radio volume will go down a bit, but I can't hear the navigation at all. If the radio is off, it is working OK with all other apps including the original music player.

Amy idea?

Thanks,

Eyal
[FYT Android Head Units] cottec:
I'll hopefully get my new unit this week, will check if there's the same newer firmware installed.

did you already contact the devlopers, probably they're planning to release it soon, after you finished the testing :silly:
[FYT Android Head Units] techy101:
I have a Joying JY-BO124N3N (4GB/64GB) and have been taking some measurements on the bench and can shed some light on power consumption for those who are concerned about parasitic drain when connecting the unit directly to the battery:

•	When the device is booted up and operating, sitting on the main launcher screen at full brightness with the volume muted the current draw is ~1.2A @ 12VDC

•	When the device is in its initial standby (the ignition has just been turned off and the device screen goes black) the current draw is 0.6A – 0.8A @ 12VDC

•	After 50 seconds the device goes into a deep-sleep mode and the current draw drops down to 0.09A @ 12VDC

An Optima Yellowtop H6 has a capacity of 72Ah. Making the (false) assumptions that the head unit was the only thing drawing from the battery and the battery voltage maintains a constant 12V as it drains, it would take roughly 8,000 hours (333 days) for the battery to drain completely. I chose Optima for this exercise only because they publish the capacity of their batteries.

Cars will have much more significant sources of parasitic current draw than the head unit’s 90mA so it’s safe to assume that these have a negligible impact on the vehicle’s battery standby time when connected directly to the battery.

I hope this helps put some minds at ease about using this connection method.
[FYT Android Head Units] ronin4740:
I looked for a Teyes unit specific for my car without much luck. Went ahead and ordered the JY-VO131N4GSN. Hoping to have it by next weekend.
[FYT Android Head Units] cottec:
Thanks for sharing those details.

- Now I'm glad to hear, that i can run it on the bench using an 2A power source

Unfortunately i need to disconnect by car's battery quite often as the immobilizer is draining the battery like crazy (known lotus issue :) )

do you think this would harm the unit in any way?
[FYT Android Head Units] techy101:
This is only in standby. If you were playing something with the internal amps a 2A supply wouldn't be sufficient.

I wouldn't think so... I can't imagine why it would, but I can't say with 100% certainty.
[FYT Android Head Units] cottec:
nah, only for setting up the unit without any speakers connected
[FYT Android Head Units] techy101:
I'm digging into the quiet static that these units always put out when not muted. Has anyone had luck fixing this?

I'm going to be experimenting with some EMI shielding options on the PCB and adding fans/heat sinks while I'm at it. When muting, the output it appears to shut down the audio output from either the DSP or the amplifier IC, which makes things silent. However, as soon as you turn the volume up at all, the audio outputs appear to turn on and the noise comes back. It's at a consistent level regardless of volume setting which makes me think it's being picked up post-amplification. On the PCB there are a bunch of traces running close and parallel to the output traces and I'm thinking this may be the source of the noise.

I'd thought it may be related to the LCD, and/or the ribbon cable connecting it, because they can be extremely noisy. However this capture was taken with the whole screen module disconnected from the main PCB so I can safely say that the noise is present in the main PCB.

Here's an oscilloscope capture switching the output between muted and not muted. It was taken on the front left speaker output. I wish I had a set of near-field probes to snoop for this but I can't justify the $200 on a set just for this project.

On another note I think I can shed some light on the reason the bluetooth system doesn't allow for non "approved" devices to pair. The bluetooth radio is a custom rolled part and is contained on a SIP but looks to be controlled by its own dedicated STM32 microcontroller. If that's actually the case then it makes sense why bluetooth devices can be limited like they are.
[FYT Android Head Units] surfer63:
In the Settings app, you can specify an app as your navigation app (3rd menu general as I remember) so that the unit knows when the navigation apps speaks and it will ower the radio or other media player.

Secondly: Some navigation apps have the option to use bluetooth or builtin speaker. The fact that it detects bluetooth makes it sometimes use bluetooth. Most function better with builtin speaker (or whatever it is called). Simply check which options works best for you.

---------- Post added at 01:12 PM ---------- Previous post was at 01:09 PM ----------

There is a way to dump it, but creating a new system image is actually not possible, so it will not be of much use unless a user does a complete restore using your units backup.

And having new firmware might also mean new MCU firmware. It might be better to wait a little longer to see if Joying releases new firmware.

But thanks for the offer.

Edit: T'eyes units also use FYT firmware. They had new firmwares on 4 July and 23 July. The previous one was in April, just as ours. That might mean that the Joying might get new firmware soon as well.

---------- Post added at 01:18 PM ---------- Previous post was at 01:12 PM ----------

Thanks for the confirmation. Over the years we had several users with the right equipment doing this measurements. Someone did it for one of the very first SC9853l models as well.

With regards to your 333 days: That is for 100% battery drain.

Note that your battery needs to have at least 50% reserve to be able to start in cold weather. That makes it "only" 166 days :)

Note also that your unit will completely switch off after 5 days (or so) of "no car usage". Just to make definitely sure not to drain the battery.

It happens to me quite regularly and now with home-working due to corona even more often.
[FYT Android Head Units] techy101:
I guess this is part of what I was getting at when I said false assumptions. It's the engineer in me trying to isolate to a single variable for the exercise ;)

Once I garage the car for the winter, and if I remember, I'll throw it onto my logging meter for a week and see what happens when it switches off.
[FYT Android Head Units] eyalber:
Thanks for the reply.

So obviously I selected Waze as the default navigation app, and also, Waze can output to the speaker by default.

I updated to latest FW (April 2020) today and same result. Before I had FW from 2019.

I checked today on another SC9853i Joying unit and all works there. The differences are - on the working unit, the FW was from Jan 2020 (older than mine), but the MCU was newer, from Jan 2020 and G23 type, mine is from 2019 and G32 type.

Anyone with G32 MCU who can test this?

Any idea?

Thanks.
[FYT Android Head Units] techy101:
Well, I managed to break my touchscreen digitizer. When I was re-inserting the flat flex ribbon to the main PCB I put it in at a bit of an angle and think I shorted out the control IC (Goodix GT911). Tracing it out I'm getting a poll from the main system SoC over the I2C lines but nothing back. The chip still has power so I'm hoping that it was just this that was damaged and not something on the main SoC. It's a chip on flex IC that I can't find easily, however I was able to find cheap touchscreens online from China that use this same IC. I've ordered a couple and plan to try lifting the IC off the flex and transplant it into my head unit. The sucky part is that they won't be here for about a month. In the meantime I'm going to be ordering another head unit from Joying and, if I can fix my existing one, will end up selling this replacement.

In the meantime, here are some photos of the main PCB from my JY-BO124N3N. Overall I was impressed with the build quality. There were a few through-hole solder joints that could have used a bit more solder, but they were still making good contact. Reviewing the board under the microscope I didn't see any obvious cold solder joints and the whole thing looked well manufactured.

The bluetooth module uses a Realtek bluetooth IC with a UART interface. This is controlled by the separate STM32 MCU over UART, which is what makes it more difficult for direct interfacing with the bluetooth chip from within Android.

The signal routing from the DSP to the amplifier IC is shown in another picture. The rear left and right channels pass darn near underneath the SoC daughter board which IMO is a poor design to prevent noise. The front left and right channels exit the DSP much farther away and closer to the amplifier. I have the two paths circled in the image. The amplifier IC has both mute and standby pins. Tracing out the routing on the PCB these are more or less tied together. It looks like when the system is muted both pins are asserted. This is why the slight static disappears when the volume is turned all the way down / the system is muted.

On the rear of the PCB, from the amplifier IC to the harness output, they left the traces un-masked. Usually when I've seen this done it's to add solder onto the traces to increase their current carrying capacity (we'll skip over the discussion about the actual effectiveness of this practice with AC signals) but they haven't done that here. They just don't have any soldermask.

Also on the bottom of the PCB is a section for another two large IC's. I'm going way out into speculation zone here, but I'm wondering if they're another microcontroller and some type of flash memory. There are four differential pairs going from under the main system SoC to the TSSOP package IC footprint. I find it really odd that they populated these 100 ohm resistors when they don't go to anything... It seems like a strange waste of money.

Those are the most interesting things going on inside there. Hopefully other people also find it interesting :p
[FYT Android Head Units] Hammerhand.17:
My touch screen stopped working again yesterday.

Could you please point me in the direction of where are the connections that I should take a look?

It's a physical issue for sure, because last time it happened, it started working again when I moved the unit to unscrew it, and so I didn't keep looking.

Thanks.
[FYT Android Head Units] bambapin:
Hi, do you use a synthesized voice (should be the ones pronouncing street names) or a sampled one?
[FYT Android Head Units] techy101:
I'd try re-seating the IDC ribbon that connects at the LCD. If that doesn't work then try re-seating the other end by removing the top of the head-unit section. My pictures aren't the best because the whole thing is torn apart.
[FYT Android Head Units] Hammerhand.17:
Ok, I will try it next week (lots of job this week), for now I used a wireless mouse to settle everything on.

Thanks a lot!!
[FYT Android Head Units] seninnha:
After reading different topics, i guess, my unit is somehow a Joying unit. Looking at HW GetInfo my unit is marked as SPRD SP9358i

[ro.vendor.product.brand]: [SPRD]

[ro.vendor.product.device]: [sp9853i_1h10]

[ro.vendor.product.manufacturer]: [SPRD]

[ro.vendor.product.model]: [sp9853i_1h10_vmm]

[ro.vendor.product.name]: [sp9853i_1h10_vmmTos]

Also stock launcher is showed in different Joying units.

Unit is working great only need to figure out some settings. Unfortunately i am not able to find any info about them.

One of the things I am trying to change is how Sound reacts when reversing the car. I installed a backup camera and when ever i reverse, music volume goes down.

Can this be change so music keeps playing at same level?

Second question.

When installing this unit, i did not use the delivered CAN adapter. According to seller this one is for cars who are equipped with JBL sound system. My car isn't so i used the standard harness.

Now I though I would be able to see some car info on my screen, but no matter what Can setting I use (inside Factory settings) nothing appears on mt screen (only app Car Info).

My Car is a 2004 Toyota Prius.

When searching for a unit I came across the shop i bought it from and one of the buyers posted a picture of his Airco buttons on his Android screen. NO idea how he did it

Already asked the seller about it but he did not react.

Here you can see what I mean:

[IMG="Car Info"]https://www.mupload.nl/img/7ygzq8rywyy7v.jpg[/IMG]

Anybody an idea how this can be done?
[FYT Android Head Units] surfer63:
You could be right but above mentioned properties are meaningless. It defines that you have a sp9853i SPReaDtrum. That is literally every 9853i.

You should look in the properties for "fyt".

Yes. It literally is mentioned in the settings about "volume when in reverse" (or something like that: away from my car)

Are you still using the standard harness without CAN? In that case you will never see something.

About the screen: NOT if you really have a FYT/Joying compatible and NOT with the standard apps. For other brands I wouldn't know.
[FYT Android Head Units] seninnha:
OK...I will see if I can use the second Harness with CAN adapter. Just for testing.

About reverse sound. I can only find setting to change how much sound needs to lower (or raise)

And main question: which unit I really have

Is this something ?

[ro.build.fytid]: [FYGrp01]

[ro.build.fytinputmethod]: [com.google.android.inputmethod.pinyin/.PinyinIME]

[ro.build.fytlivewallpaper]: []

[ro.build.fytmanufacturer]: [116]

[ro.build.host]: [bsp-04]

[ro.build.id]: [OPM2.171019.012]

[ro.build.product]: [sp9853i_1h10]

And I think this is installed software:

[ro.vendor.build.fingerprint]: [SPRD/sp9853i_1h10_vmmTos/sp9853i_1h10:8.1.0/OPM2.171019.012/26521:user/release-keys]
[FYT Android Head Units] surfer63:
Yes, it is a FYT build unit, so a Joying compatible. It is also important to know that your manufacturer is

[ro.build.fytmanufacturer]: [116]

There are some minor differences and they are dealt with by manufacturer id and (sometimes) the sys.fyt.bluetooth_type. If you simply flash a Joying firmware (with manufacturer id 43) onto your unit, you will most probably detect minor little errors/glitches. Before flashing you need to change the Joying id to your units id (and sometimes the sys.fyt.bluetooth_type as well)

(Enough posts on how to do that: Search).
[FYT Android Head Units] ronin4740:
Went to swap out the RNS-315 audio unit with a Joying android auto head unit this afternoon. Plugged the new unit in and it failed to power up. Following their instructions I connected the accessory wire which also failed to power up the new radio.

Giving up I then put the original radio back in and found it also wouldn't turn on.

Seems over popped a fuse or blown a relay or fired something but I've continuity checked all the fuses and they seem good.

Anyone happen to know how the power line at the back of a VW radio wiring harness is connected to battery power or what I should check to solve my issue?
[FYT Android Head Units] ch_swat_89:
Had the same problem on my vw passat. it was the fuse in in the enginge fuse box. a green one i think....
[FYT Android Head Units] ronin4740:
I'll go through them again. Thanks for replying
[FYT Android Head Units] ronin4740:
I did find and replace a blown fuse. Now it's working properly.

Wondering how to change the display from km and c to mi and f?

Also wondering where to disable the contact sync so that it doesn't delete my contacts again?

Finally having issues with the zlink app - getting an error when I try to register an email address... Wanted to get android auto working and believe I have to run the app on my phone?
[FYT Android Head Units] ricanxd:
Yeah I never found a way to change measurement units from km to mi or c to f.

Zlink never asked me for any email address. You do need auto installed on your phone for it to launch in HU.
[FYT Android Head Units] ronin4740:
So I just launch android auto on my phone and it connects over Bluetooth to zlink on the head unit?

Sorry for the newb questions.
[FYT Android Head Units] techy101:
What part of the head unit? In the car info app there's a function to do this for my BMW and probably others that have the CAN interface. https://youtu.be/eOP-XFMWaZE?t=1398

Go to Settings -> User -> Account -> Select your google account -> Account Sync -> Turn off "Contacts"

On my unit the account text and background are both dark and so it's nearly impossible to read, but if I turn the brightness way up and get close to the screen I can just barely make it out.

Finally having issues with the zlink app - getting an error when I try to register an email address... Wanted to get android auto working and believe I have to run the app on my phone?[/QUOTE]

Can't help there. zlink has never asked me for an email account. Is it an actual Joying head unit? If so here's the ZLink apk that came on my unit, maybe it'll work for you??
[FYT Android Head Units] techy101:
I *think* that it uses Bluetooth for phone calls and the wired connection for music, etc... but I'm not 100% certain on this.
[FYT Android Head Units] ronin4740:
Thanks for the replies.

My note 20 complains that the zlink software is too old. The 3.5 version I found on xda won't install at all...

I guess I'll ask Joying for their apk or try to get it out of my head unit somehow
[FYT Android Head Units] ricanxd:
Has to be wired
[FYT Android Head Units] ronin4740:
So if it has to be wired do I need a dongle? If so which one do I buy?
[FYT Android Head Units] techy101:
That depends on which unit you purchased. Some of them have Android Auto built in and others require a dongle. What is the exact unit you have?

---------- Post added at 02:53 PM ---------- Previous post was at 02:47 PM ----------

Give the 3.4.2 version I posted a shot even though it's older. That's what I'm using with Galaxy S20 running One UI 2.5 and it works just fine.
[FYT Android Head Units] ronin4740:
I get the attached when I run the zlink apk you sent

I bought a JY-VO131N4GSN-US-JY-VO131N4GSN unit
[FYT Android Head Units] techy101:
Well shoot. Contact Joying, they usually respond very fast.
[FYT Android Head Units] ricanxd:
I connect thru usb
[FYT Android Head Units] ronin4740:
...and that worked the third or so time I tried it. Might just do this that way.
[FYT Android Head Units] spiker88:
I have the 1280*480 screen. It works well in split screen mode b/c I get two square screens for things like maps and media. But there are some annoying features, like the keyboard taking up almost the entire screen.

I have a couple apps that I cannot see to the bottom of (app is designed for a typical smartphone aspect ratio). I am unable to scroll down to access key information & buttons. Is there any way to enable scrolling? Other workarounds?

thanks
[FYT Android Head Units] seninnha:
Which version of Spotify do you guys use in this Intel unit?

Reason for asking this is the fact that I miss the CarView function.

On my former PX5 unit this function was available, but on my new Intel it does not appear in the setting.
[FYT Android Head Units] julien_blanche:
It looks like they have developed a new android 10 head unit with UIS7862 8 core cpu [MENTION=4149147]1.8[/MENTION] Ghz with 1280x800 new screen as below

-New screen is much much more clear and it has very good quality unlike current models

-Finally optical digital output (SPDIF) has been added

https://www.youtube.com/watch?v=iE8NJWTlQDI&ab_channel=Boyka
[FYT Android Head Units] techy101:
I'd be really curious if the screen from my current unit would be compatible with the base unit if that SoC is significantly better, or if they'll bring better panels to smaller screen units.
[FYT Android Head Units] julien_blanche:
It's very unlikely hence their marketing purpose is selling new head units.

Most probably new screen power requirements will be different then ours..
[FYT Android Head Units] ricanxd:
I emailed them recently asking about any updates to the current Intel units. They replied back saying no. Let's see if they stop supporting the current units.
[FYT Android Head Units] surfer63:
Customer support will continue.

For firmware support/upgrades I'm sure they will stop. They did that when going from Intel Sofia to PX5. From PX5 to SC9853i. So I am sure they will stop that for the SC9853i as of the moment they start selling the new UIS7862 Cortex A75 units.

Edit: They are already for sale: https://www.joyingauto.eu/joying-an...h-1280-800-screen-single-1din-car-stereo.html

and they now finally support 5GHz WiFi.
[FYT Android Head Units] techy101:
I'm going to be extremely unhappy if my unit is obsoleted within a few weeks of purchasing it...
[FYT Android Head Units] ricanxd:
Hopefully someone can port Android 10 over to older unit
[FYT Android Head Units] surfer63:
It is not the Android itself. It's the proprietary closed-sourced hardware drivers and interfaces that need to be recompiled for Android 10 and nobody has the sources. Same for the radio apk etcetera. It is not a standard FM radio using the FM radio chips in some phones. It is only a Gui to hardware controlled by the MCU.

So even if you are a real programming guru, you will not be able to do that.

For the Sofia Intels a "guru" did analyze "everything" and build a new system that could interface with the hardware radio/audio processing, but it was really rudimentary and CANbus functionality and the like did not work. But for the Sofias the Android code was not obfuscated yet and could more easily be decompiled.
[FYT Android Head Units] bogdi1988:
damn you guys! it looks too good to resist so i just pulled the plug on one!
[FYT Android Head Units] ricanxd:
Yeah I forget there's a lot of proprietary components involved with these units.
[FYT Android Head Units] surfer63:
Yes. That happens with most Chinese units. If you have a 1024x600 unit, you might start flashing the T'eyes firmware. They just released a new firmware on 23 July and a new radio app on 7 August.

I have a 1280x720 Joying. That resolution is not directly supported by the T'eyes firmware. If T'eyes continue to support their SC9853i models I might convert one of their firmwares into a Joying. Changing that firmware to 1280x720 can not be a big change as Joying supports 1280x720 and 1024x600 with one firmware.

(With only 2 minor changes you can use their firmware if you have a 1024x600 unit. Well, actually 1 more change (locale/language/region settings) as they start their firmware in Russian instead of US English, but that has nothing to do with the MCU and hardware)
[FYT Android Head Units] tangcla:
What benefit does the T'eyes firmware offer over the standard Joying?