yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] tangcla:
I had no issues with updating using microSD card, I use the smallest cards I have available (2 or 4GB) but I did find using a 64GB card caused issues.

Re wifi - I read somewhere earlier that BT connection causes the wifi speed to drop significantly.
[FYT Android Head Units] andTab:
I tried with the phone nowhere near the car and it makes no difference :(

One other thing that I wish this did: share the GPS location to the phone for Android Auto. My phone's GPS sucks (randomly doesn't get a fix at all) while this thing gets a perfect fix every time INSIDE of buildings.

And one more question: the radio reception seems to suck. Is this common or is there a fix/wrong setting?
[FYT Android Head Units] hellkaim:
The question is: how you use the WiFi and from where do you get the signal. Also, check how your antennas are located inside the dash. My be they are in some metallic shielded space?..

I am using WiFi with my phone with Bluetooth simultaneously with no issue what's or ever. The speed greatly depends on the cellular network and not on HU<>phone connection.

There is a speciall application that can do it, but it uses Bluetooth (at least the one I know). As our units has crippled Bluetooth capability there is no way to push that data to other devices.

In the radio app tap on a gear icon located on the lower right corner of the screen. There will be amplification levels there for FM and AM band. I also noticed that in my car using an FM amplifier (active with 12V input) ruins the resception after about 2-3 days. At first it's very good, but suddenly there will be no stations. Not any. Unplugging the power to amp gets all back to normal. It might be you have such amp integrated in your car or have other filtering setup from the factory that ruins the resception.
[FYT Android Head Units] julien_blanche:
Wifi speed drops when you are using BT at the same time, this issue has been explained extensively before and reported to joying with no luck. Although they are using the separate antennas wifi speeds drops from 50 mpbs to 5-12 mpbs depends on your setup and phone because both of them are using the same data path on the motherboard.

This issue exist at most of the Chinese head units no matter what you do...
[FYT Android Head Units] hellkaim:
That sucks! Are they using kind of i2c or similar instead of USB/PCIe?

There is a thing called "Bluetooth coexistence" on some hardware (esp. routers) that is addressing the issue. I do not remember exactly how it is implemented, but seems it dials with collision detection mechanics that takes in to account not only WiFi signalling, but also the Bluetooth throughout WiFi circuitry.

As WiFi and Bluetooth are managed by MCU it well may be that such an logic is not there or has not being activated.
[FYT Android Head Units] ricanxd:
On a side note. That Android auto is working with my pixel 4 XL on Android 10. I finally remembered to check and see if it worked. The HU definitely didn't seem to like the OnePlus 6T.
[FYT Android Head Units] ProBird79:
I just received my HU today. I tested CarPlay and it works as it should. My Nexus 6 running LOS 15.1 doesn't connect to Android Auto at all. It doesn't even try to connect for some reason. Is there a trick to get it working?
[FYT Android Head Units] ricanxd:
Not sure, mine worked without any other steps. Try turning on USB debugging in the developer options.
[FYT Android Head Units] MrVerm:
Hi guys,

I received my headunit today, a Witson Android 9.0 For FIAT 500 (W2-RL315B).

When ordering however I was trying to order a PX5 based HU but due to incoherent item titles and descriptions on the sellers part on AliExpress I received a SC9853i unit.

At first I was pretty disappointed, then I found out the SC9853i HU's supposedly have better hardware and performance. The PX5 has better community support though I feel, which is why I wanted a PX5 from the start.

What are your thoughts on this? Return for a PX5? Or keep cause it is superior over a PX5?
[FYT Android Head Units] ojuniour:
Definitely keep the SC9853i .. I mean sim card uspport (regardless oif you need it or not) and actual built in DSP.. fasterCPU and runs ALOT cooler than px5..
[FYT Android Head Units] andTab:
On mine the touch buttons on the left have stopped working.

They aren't even lit

Any idea how to fix?
[FYT Android Head Units] julien_blanche:
Can you describe the issue more in detail, exactly after what you did this issue occurred ? If it happened out of the blue then most probably touch digitizer went bad, try to reach the joying support..
[FYT Android Head Units] surfer63:
Note that in the Settings app under Factory, you have the "MCU panel key" ON/OFF option. Setting this to OFF disables your hardware buttons or the left OnScreen buttons (whatever is relevant for your unit)

Secondly: Maybe you need to reassign the actions to those buttons again in the Settings app. See also Joyings blog video for that.

Thirdly: Note that in the settings the "Back Light Control" -> "Small light control" can be set to ON/OFF. When setting it to ON, it will be controlled by day/night time. When setting it to OFF it will be controlled by switching on/off your headlights. The latter doesn't work for many users, including me. This bug is already in the firmware for several months. In other words: my buttons light up during boot (as they are tested) and then never again with the "small light control" to OFF (and please don't start about the terrible translation to English of this option ;). I already suggested much better English strings for this setting).
[FYT Android Head Units] andTab:
Thank you.

I can usually get the keys to work briefly by learning them or by turning MCU panel on/off but it stops working pretty quickly.

This started after upgrading to the latest firmware (though I also had they keys stop working intermittently before - they are quite unreliable; it really sucks that one can't use a Bluetooth remote, since I have 5 button one for my phone)
[FYT Android Head Units] andTab:
It seems like paying around with the panel key setting has fixed the issue of the keys not responding and the lights now come on at night (though the day/night switch time appears to be all screwed up, not sure where one can fix that)
[FYT Android Head Units] runehasa:
Voice dialing

Anyone know a way to remove google assistant from being the default speech app when I push my steering wheels speech button? The reason I ask this is like other people in this thread I am having the issue when my voice dialing will not work if I am connected to an internet source. If I use a voice assistant like Hound which only works while connected to the internet I have been able to successfully dial out by using its voice command. when connected my phones hot spot. If I could just find a way to assign my steering wheels speech button to bring up hound instead of google assistant I would be golden. Any help would be greatly appreciated as I have combed the menus trying to find a way to clear the default for speech.

Edit.

Well i found a work around that isnt really ideal but it gets the job done. I set the NAVI/GPS button to open Hound as opposed to GPS then changed the steering wheel control to GPS for my Speech button instead of Speech. Never really use the physical navi button so it kind of works. I can now voice dial while connected to the internet using that. If someone has a better solution im all ears.
[FYT Android Head Units] yzf750:
I wish more people would complain to Joying about the google assistant bug not making calls. When only a couple of us do Joying just blows it off and shoves it under the rug thinking its not important since no ones contacting them about it. Get a few hundred people emailing them and they may fix it then. Its sad, I posted on their forums about it again a couple days ago, asked when it would get addressed and they reply " send us a screenshot of your unit ". I replied "I have and others have also". Dead silence from them then, and no reply to it anymore from them on the issue.
[FYT Android Head Units] bengali548:
Does anyone know how to prevent Joying OS from killing my Tasker and AutoInput apps when I turn off my car or when I clear my app drawer?
[FYT Android Head Units] surfer63:
It is really annoying indeed. I really like my new unit. I hardly ever call in the car but the fact that it doesn't work and Joying doesn't mention it anymore or starts to aks completely irrelevant questions, shows to me that they have no clue whatsoever how to solve this.
[FYT Android Head Units] bengali548:
Does anyone know why my accessibility services keeps resetting for AutoInput? I have to keep giving it permission and theres no way to access a battery menu so I cant adjust any power saving options
[FYT Android Head Units] hellkaim:
Not much can be done without rooting/flashing.

You may find here the guide how to make allapps.apk and put Hound there under the name of Google Assistant. This will replace the Google Assistant app with Hound but will still be usable by Joying firmware as internal apk name will be the same.

Other workaround is to go and root the unit as it is confirmed that after that Google Assistant will.stop working. But who cares - you will be able to replace it and set Hound as a default app.
[FYT Android Head Units] ricanxd:
Anyone else having to start the DVR app in order for it to record?
[FYT Android Head Units] surfer63:
Sometimes I need to start it. Sometimes it starts after 1-2 minutes. Sometimes it doesn't.

I use [MENTION=575209]bambapin[/MENTION]'s Fyt-Starter app to make sure the DVR app starts on ignition. (There should be another, later link, but I can't find it).

Another "thing" that happens to me is with the length setting for the recorded files: 1 min, 2 min, 3 min.

The first one is never recorded/saved. Meaning that with a setting of 1 minute I miss the first 1 minute of recording. With 2 minute setting, I miss the first 2 minutes of recording. And the first 3 minutes for the 3 minutes setting. Why is that happening?

So I record with the 1 minute setting.
[FYT Android Head Units] ricanxd:
Thanks
[FYT Android Head Units] yzf750:
Yep, another unfixed Joying bug with the newer dvr camera and app. The old Sofia units with the older Joying cameras and app worked flawlessly. Mine even timestamps the videos with the wrong dates with the new camera and app.
[FYT Android Head Units] ricanxd:
Yeah I don't know why the auto start option is not even in the DVR settings like all the older units had. Updated DVR app, I'll check if they've fixed anything
[FYT Android Head Units] jose.marcos.3720:
Hi everybody.

I bought this new unit JY-VO130N4GS two days ago. I installed and I have big problem with the bluetooth quality. It is very poor. Apparently the sound in the receiving end is okay, but the sound through my speakers is distorted and noisy. Is very difficult to understand the caller. I already upgrade the unit with september 2019 official firmware with the same result. If I send sound through bluetooth, the sound is quite good.

Anybody has this problem?

Thanks in advance
[FYT Android Head Units] surfer63:
Temperatures of this Joying SC9853i unit

I have the JY-VO132N4GS (4GB/64GB/1280x720) unit.

In my previous Joying Sofia-3GR I had a coolsink and a fan which kept temperatures below ~60	°C. In my previous PX5 I only had a fan which kept temperatures below ~65 °C.

In my current SC9853i I neither have a sink nor fan.

Previous week I had a 1hr10min drive in the morning and back in the afternoon. I always drive on cruise control and hardly ever use airconditioning, but I wanted to have as much the same circumstances. Note that most units are built into the dashboard between/under/above the heat/cooling air vents (ventilation openings). These heating/cooling funnels do have influence.

[B]2019-11-15-Morning[/B] [B]2019-11-15-Afternoon[/B]
- Cruise control at 120 km/hr - Cruise control at 120 km/hr
- outside temperature 4-5 °C - outside temperature 7-9 °C
- climatronic 20.5 °C - climatronic 20.5 °C
- Mediaplayer, temp app and Magic Earth (navi app) - Mediaplayer, temp app and OsmAnd+ (nav app)(before vert. divider)
Mediaplayer, temp app and Magic Earth (nav app)

See attached two images of the recorded temperatures (using a newly created temperature measuring app which is simply a rip-off of my JETs temperature monitoring function. You start it and it does nothing more then measuring temperatures for coretemp 1/2, 3/4, 5/6 and 7/8, and then saves this to a .csv file in /sdcard. See also attached).

And as expected: cpu cores 1/2 and then cpu cores 3/4 are most used. I have no idea how much heat dissipation is "seeping through" from cores 1/2 to the other cores.

Temperatures still get higher then I expected. What's more: OsmAnd+ is obviously using the CPU more intensive than Magic Earth does, as temperatures with OsmAnd+ are 10-14 °C higher then with Magic Earth. With OsmAnd+ > 90-95 °C, and with Magic Earth < 85 °C (in the cooler morning and slighlty warmer afternoon).

Anyway, somewhere in the off-days between Christmas and New Year I guess I will again put a fan inside my unit.
[FYT Android Head Units] hellkaim:
First of all: how speakers are connected: a) using RCA, or b) using standard harness adapter?

Do you use any external amp?

It is also not clear: are you using your phone connected by Bluetooth and that when sound is crappy or it is always like that?

I never heard of any issue with speaker other then small hiss if there is a silence (muted audio).

The quality of the microphone is terrible and there are solutions for that, but inly affects your partner.

Please tell us more about your setup so we could make any suggestions.

PS. I personally think you have some electrical interferience there.

---------- Post added at 10:06 PM ---------- Previous post was at 09:45 PM ----------

I have the same unit and am living in a climate where lowest temperature is +2 °C. Most of the year we have >24 °C and there are extencive periods with >32

°C.

Now combine it with >60 °C on dashboard almost 7 month a year and you will get pretty bad environment for cooling electronics.

The highest temperature I recorded was 64 °C. This was with a radiator and a small fan plus air-conditioning with bright sun and outside temp of 34 °C.

Right now as we are in low-mid 20th range the temperature never exceed 50 °C and the cooler is stopped (I connected it to amp wire so I can switch it on/off from the menu).

So yes, this unit is hot and it requires active cooling. The setup I have is a pretty loose one: I used PcCooler NB-400al with some thermal paste + glue + some foam pad (on top of the radiator to push it down) and a BFB0512HHA 5*5*1 cm fan. I did not polish the original heat think neither I did screw the cooler to it. I just selected a spot near the CPU and glued the cooler there. The fan is located in the corner of the case with additional holes drilled and is blowing onto the cooler.

I will have to remove the unit soon so if there is an interest I can make some photos.

---------- Post added at 10:13 PM ---------- Previous post was at 10:06 PM ----------

AndroidAuto is a proprietary Google staff. As you are using other OS you may be missing needed services/apk there.

I can assure you that it is not really needed to have AndroidAuto with that unit. You can use a launcher like AGAMA and IMHO result will be way better then AndroidAuto
[FYT Android Head Units] ProBird79:
Thanks for the reply. It ended up being the cable. I switched cables and it's now working.
[FYT Android Head Units] hellkaim:
Good to know that LOS has support for AndroidAuto built in. ;)
[FYT Android Head Units] andTab:
Would love to hear what people would recommend to improve the microphone.
[FYT Android Head Units] jose.marcos.3720:
Yes. I connected with original harness. I have original vw external amplifier (Dynaudio ).

Everything sounds fine even bluetooth music. The problem is when I make a call the other side can listened me clear but his voice through my speakers are ****. Is like the treble are too loud and the voice is distorted.

I try setting to 0 frequencies 5k. 8k. 10k. 12k and this problem dissapear, but is not a solution have to change the equalizer everytime that i want to use the bluetooth. I dont know if there are any app or way to change equalizer only for one app.

Thanks in advance
[FYT Android Head Units] SpoonerPS3:
Don't they include an external microphone? I would give that a try if you don't have any luck with the internal one.
[FYT Android Head Units] hellkaim:
Lets start from the origin of the issue: the onboard microphone (located in display panel) and the one that connects to mini-jack at the back of HU share the same line. In other words they are soldered in parallel to mic inputs of the main board.

So if one connects the external mic to mini-jack the echo effect is inevitable. An as it is a physical issue there is no software way to neglect it.

The solution here is to cut the wire that connects built-in mic or not to use external mic.

The exact wire may differ (YOU SHOULD CHECK WITH JOYING) but in most cases it is a red wire in the display cable. Joying is aware of the issue and will tell you exactly what wire to cut.

The internal mic is a simple one and has no insulation what's or ever. It is very sensitive to vibration, air flow (if you have an air duct near the display) etc. It has a haul effect also ;) I do think that putting it in some foam will help, but I did not test it. It also may be that just by glueing it most issues can be resolved. It is a field for experiment ;)

The external microphone use a 4 pin head. Professional mics do a food job here, but they have a narrow field and should be located precisely. I was experimenting with lavaliere models and got very dissent results but they have to be located in front of you and there are not many places in the car for that.
[FYT Android Head Units] hugorafael:
Thats good to know, I am thinking of using my vehicle mic as the external one, cutting its wires and soldering on the plug at the back of the unit
[FYT Android Head Units] surfer63:
Work-around for not working Google Assistant

Like many users with a Joying SC9853i, Google Assistant works fine but NOT for calling. You get the message "I can't dial yet" (in your language).

Based on the post of [MENTION=4620563]runehasa[/MENTION] (#1332, thanks for the inspiration!), I also found a work-around which is not so great, but at least makes voice dialling possible (disclaimer: for me it makes it possible, I hope it works for you as well.)

Step 1 (work-around 1)

(Attached images from left to right)

First I installed Voice Search from the Play Store. Maybe other apps work as well, but this one was the first I installed (based on the screenshots) and it worked.

First I set in the Settings of Voice Search to always start with the main command, via the "triple-bar-menu" in the top-center of the screen. (image 01-appVoiceSearchSettings.jpg; I "blurred" the big advertisement)

Then in the Options (+ sign top-right), I only select the "Call" option (image02-appVoiceSearchOptions.jpg)

Now when I open Voice Search I get a "voice prompt" where I only mention the contact (no "call John Doe", only "john Doe") (image 03-appVoiceSearchContact.jpg)

And when I name the specific contact. In this case "thuis" (home in Dutch), the dialing works (image 04-dialing.jpg. I "blurred" the advertisement again)

This (first work around) does work, but is not 100% what I want.

Step 2 (work-around 2)

The 2nd work-around, on top of this 1st work-around, is the following:

Via the steering wheel button I open the Google Assistant.

Inside the Google Assistant I say "Open Voice Search"

Voice Search opens with the default main command, which is now (only) the dial command, which immediately waits for the contact to be named.

I say (in this case) "thuis" and my unit dials out via my phone.

drawback: The Voice Search app waits quite short for the contact to be said. It sometimes means that you still need to tap the screen and repeat the command, or simply start again with the SWC tap to open Google Assistant.

I have been thinking to create a likewise activity as the google search voice in my HWOneKey app. That makes it possible to start the Voice Search app instead of the Google Assistant, but actually I do not want this. I do like the Google Assistant for quite some useful "things" and I do not want to disable it only for voice dialing.
[FYT Android Head Units] hellkaim:
Test it before soldering. It might require some circuitry on the unit side (boost?). Also if it is a noice cancelling one it might not work at all. In any case the external mic in HU just uses tow wires.

---------- Post added at 07:26 PM ---------- Previous post was at 07:23 PM ----------

Good luck with that. Is is as cheapo as hell. And as I mentioned - without cutting the wire to internal you will end up with echo effect.
[FYT Android Head Units] hugorafael:
Yes I will, I dont know how exactly mic Works but I will check impedance of both and test if it Works before doing it permanently

I know for a fact that my vehicle mic is a very good one because I used it a lot before switching head unit, and also, it stays hidden near the roof lamp, which is a bonus
[FYT Android Head Units] hellkaim:
So we all ending up with external (additional) application that wraps google assistant/ contacts whatever to execute call action...

It's easier to completely remove Google Assistant with AllApps.apk and replace it with voice assistant of one's choice.

---------- Post added at 07:37 PM ---------- Previous post was at 07:32 PM ----------

Look not at equalizer but to "sound mix" or how it is called in settings. The menu item shows bars that corresponds to different sound sources. Try to reduce the Bluetooth or Phone bar. You may find the setting thet will reduce the effect. Did you cut the internal mic wire?

I already mentioned thet any external mic connected to HU will run in parallel with built in one. Ask Joying regarding what wire to cut, but usually it is a red wire on display harness.
[FYT Android Head Units] surfer63:
I only call it work-around (or actually two). I don't like it anymore than you do.

I simply want Joying (or actually) FYT to solve this.

Note though that almost all "voice" apps, somehow use the Google Assistant as their engine. Removing Google Assistant will only make it worse.

Bestee was nice on my PX5, as it doesn't need Google Assistant, but it doesn't work on the Intel units.
[FYT Android Head Units] hellkaim:
Youp, just keep us posted. As much info we collect the easier it gets.

---------- Post added at 08:03 PM ---------- Previous post was at 07:45 PM ----------

It's not 100% right. As some apps do relay on Google Assistant (let's call them wrappers) there are several that use Google Voice API. In that case Assistant presence is not required on the device. BUT, as API access at scale is a payed service all.of those apps are a payed apps.

There are several apps that uses Amazon or Microsoft API and they require respected accounts within A or M. But they are also payed apps.

There are few (I can remember 2) that has their own voice recognition tech (surprisingly mature/good)... and they also have to be purchased.

The other issue with voice dialing is the ability of the app in question communicate with Bluetooth app in HU. This actually quite narrows the list but still one can choose of at least 4-5 apps.

I ended up giving away that option. I do not want to have 2+ apps one on top of another just to make calls. I use my phone as a calling device and a call is picked by HU so I'm ending up with the same result.

Another interesting story is a contact sync. I will discribe it in a separate message.
[FYT Android Head Units] surfer63:
I know. It is already an issue for many years, coupled to a maximum of 255 contacts as well.