New Joying Android 10 UIS7862 Octacore 1.8GHz (4GB RAM, 64GB flash)

Duan

Senior Member
Jul 29, 2004
78
0
26
I bought two of these, one went into my VW CC (SKU JY-VQ151N4GN) and the other into my wife's Honda CRV (SKU JY-HQ122N4GN--).

The Honda had a stock HU and the CC had a RCD330 fitted.

The internal mic on the Honda does not seem to work well at all and I have subsequently installed the external mic that came with the unit. Its better, but not great. I have not really tested the mic in the CC.

My wife is complaining that she has to manually adjust the volume level as speed increases or decreases... I have not paid attention in my car, but there must be a setting somewhere? Does anyone know?

The 2.4g WiFi sucks, the 5g is ok.

Bluetooth seems buggy and this may also affect the wireless CarPlay. Both our units support wireless CarPlay, but it seems wired CarPlay is not available. Is there a way to enable wired CarPlay?

Our cars are right hand drive and I have noticed that CarPlay is configured for left hand drive, does anyone know how to change that?

I am generally happy with the new unit. The old RCD had Wired CarPlay but was not compatible with my Dynaudio Amp, so it would actually hurt my ears. The new Joying unit sounds miles better.
 

barnesk9

Senior Member
Sep 23, 2008
106
7
38
Our cars are right hand drive and I have noticed that CarPlay is configured for left hand drive, does anyone know how to change that?

I am generally happy with the new unit. The old RCD had Wired CarPlay but was not compatible with my Dynaudio Amp, so it would actually hurt my ears. The new Joying unit sounds miles better.
-for wired CarPlay I believe that you need a dongle to do it. Not sure about making it right hand drive

-for speed controlled volume, there was an app that I used to use for my tablet in dash install I'll update this to add the name if I remember it.
 

cleaa

New member
Jul 1, 2015
2
0
21
Does anyone have problems with writing to pendrive by 3rd party apps like autosync / root explorer ?
Native file manager writes like a charm to usb drives.
 

gamer765

Senior Member
Jan 14, 2009
481
187
63
I have the same issue writing to usb drives. Other file explorers either crash or just refuse to write at all. FX File Explorer crashes when trying to enable write permission for the usb. Root File explorer says it doesn't have permission to write. I think FYT might fix this in a future update.
 
  • Like
Reactions: cleaa

surfer63

Senior Member
May 4, 2010
3,493
1,308
253
Zwolle
hvdwolf.github.io
I have the same issue writing to usb drives. Other file explorers either crash or just refuse to write at all. FX File Explorer crashes when trying to enable write permission for the usb. Root File explorer says it doesn't have permission to write. I think FYT might fix this in a future update.
This started already on the Sofia when moving to Android 6, continued on the PX5, was unsolved transferred to the 9853i and now also on the UIS apparently.
FYT really sucks at bug solving and Joying doesn't seem to be able to persuade them to work a little harder on this (or any of the other bugs).

Edit: I guess they somewhere went wrong when converting the old "vold" config (< 4.3) to standard linux "fstab" (Android 5 intermediate) to Android >= 6.0. Someone should modify the boot.img.
But it actually doesn't suprise me. They are still using code from android 1.6 and their screen layout is even too old to be recognized by Android Studio.
We are on 8.1 (sc9853i) and 10 (uis7862) now but they simply patch and extend their code with another "if .. then" for new hardware or android version. I assume that is the cheapest.
 
Last edited:
  • Like
Reactions: cleaa and ArmchairA

gamer765

Senior Member
Jan 14, 2009
481
187
63
This started already on the Sofia when moving to Android 6, continued on the PX5, was unsolved transferred to the 9853i and now also on the UIS apparently.
FYT really sucks at bug solving and Joying doesn't seem to be able to persuade them to work a little harder on this (or any of the other bugs).

Edit: I guess they somewhere went wrong when converting the old "vold" config (< 4.3) to standard linux "fstab" (Android 5 intermediate) to Android >= 6.0. Someone should modify the boot.img.
But it actually doesn't suprise me. They are still using code from android 1.6 and their screen layout is even too old to be recognized by Android Studio.
We are on 8.1 (sc9853i) and 10 (uis7862) now but they simply patch and extend their code with another "if .. then" for new hardware or android version. I assume that is the cheapest.
You are absolutely correct , they just patch their software with "if .. then" conditionals for new hardware releases. There's references to many old hardware in their software. What surprised me though is that USB worked properly for me at least on SC9853i, so there is some form of regression with these new UIS7862 units. Another annoying issue is that whenever I plug in my USB to the headunit, Windows always complains about it finding errors when I plug it to my PC. Doing a disk check on the USB results in no errors found 99% of the time, but the 1% of the time it does, several files either go missing or are corrupt.
 
  • Like
Reactions: cleaa and ArmchairA

surfer63

Senior Member
May 4, 2010
3,493
1,308
253
Zwolle
hvdwolf.github.io
You are absolutely correct , they just patch their software with "if .. then" conditionals for new hardware releases. There's references to many old hardware in their software. What surprised me though is that USB worked properly for me at least on SC9853i, so there is some form of regression with these new UIS7862 units. Another annoying issue is that whenever I plug in my USB to the headunit, Windows always complains about it finding errors when I plug it to my PC. Doing a disk check on the USB results in no errors found 99% of the time, but the 1% of the time it does, several files either go missing or are corrupt.
USB mass storage devices have a "dirty bit" flag which is some 1 hex value "somewhere" (I never checked it) on that mass storage device. If you do not unmount/eject the usb stick properly (Settings -> device -> storage -> unmount/eject icon), this "dirty bit" flag is set.
Windows is really picky on this.

See for example:
or
 

awellam

Member
Sep 9, 2015
12
0
21
I just finished installing the 8" model. Found a few bugs straight away. The worst one being, when using FM radio then switching off the car the radio continues to play even though the screen had turned off. It stays playing for about 2 minutes.. anyone else had this problem
 

warata

Senior Member
Apr 25, 2016
366
68
38
Tsu
hello I usually using Google Voice Search for steering switch learning, is there a way to launch the Google Assistant instead of voice input on the steering switch?
 

surfer63

Senior Member
May 4, 2010
3,493
1,308
253
Zwolle
hvdwolf.github.io
I just finished installing the 8" model. Found a few bugs straight away. The worst one being, when using FM radio then switching off the car the radio continues to play even though the screen had turned off. It stays playing for about 2 minutes.. anyone else had this problem
That is strange as it should switch off in 2-3 seconds. However, the systemsgoes into sleep and gives apps the time to nicely closed down before swtching off hardware. That is the approx. 2 minutes
 

surfer63

Senior Member
May 4, 2010
3,493
1,308
253
Zwolle
hvdwolf.github.io
hello I usually using Google Voice Search for steering switch learning, is there a way to launch the Google Assistant instead of voice input on the steering switch?
Not directly. 2 years ago I wrote the FytHWOneKey apk that could do these things and I released the last version 1 year ago (or so). As I now have a "button-less" unit with a 3rd party SWC-control (steering wheel without buttons), I don't need it anymore: no hardware buttons to redefine, and training the 3rd party SWC-buttons already point to the wanted apps, instead of the CANbus defined apps.

The app probably works on the UIS7862 as Joying/FYT hardly ever change something, but I have no idea or give guarantee as I don't have a UIS7862.

See https://forum.xda-developers.com/t/...-unit-hardware-buttons-fyt-hw-onekey.3912075/

EDIT: I wrote in that post: "It does not work in combination with the Steering Wheel keys."
(So long ago I can't even remember)
 
  • Like
Reactions: warata

warata

Senior Member
Apr 25, 2016
366
68
38
Tsu

Attachments

Allan_Hun

Senior Member
Mar 11, 2014
373
112
73
Gl.Rye
I'm about to return my 8227L headunit because it's awfully slow and rca output is noisy.
I guess this unit would solve the performance issue, but I daubt it would solve the rca Noise.
So I'm thinking digital audio is the way to go.
But I have a dayton dsp that I really don't want to change. It has rca and bluetooth inputs.
Thinking about my options i came up with 3 different way to connect the 7862 with my dsp:
Option 1:
Spdif from hu to a dac with spdif input and rca output from dac to dsp.
Option 2:
Usb from hu to dac with usb input and rca from dac to dsp.
Option 3:
Bluetooth from hu to dsp.

For options 1&2 I would have to purchase a dac, and the extra d/a conversion seems kind of stupid.
Android resamples usb audio to 48Khz so that would probably also degrade the sound quality slightly. I don't know if android also resamples spdif audio?
I also know that androids denoise filter causes some issues with volume control when outputting audio through usb. I'm guessing this also applies for spdif?
I'm also wondering if there are other issue with androids digital audio output. Things like mixing several input sources into one output works ok?

Option 3 (bluetooth) would be digital directly from hu to dsp -but would introduce compression. Personally I don't mind audio compression if the bitrate is high (320kbs sounds ok)
But the stinking 8227L would not pair with my dayton dsp. So I'm wondering if the 7862 would fair any better?

Am I missing any better options on how to get quality audio from an android hu into my dayton dsp?

Regarding Bluetooth. I have a nice obd Reader from scantool. But the sucky 8227L refuse to pair with it. I assume it because the reader use BT LE. So does the 7862 support audio output through BT LE?
 
Last edited:

surfer63

Senior Member
May 4, 2010
3,493
1,308
253
Zwolle
hvdwolf.github.io
I have the same issue writing to usb drives. Other file explorers either crash or just refuse to write at all. FX File Explorer crashes when trying to enable write permission for the usb. Root File explorer says it doesn't have permission to write. I think FYT might fix this in a future update.
To add to my previous comment (which was actually a rant about the non-existent bug-solving capabilities of FYT. I got a little bit carried away ;)).
I use total commander. Total Commander shows the usb stick (or SD-card) twice. One version is not writable/accessible. The second is writable (or the other way round. I always forget and can't remember now either).
This due to the fact that if you look at the mount points (in a terminal execute the command "mount"), you see that there is a read/write mount and a read-only mount. Most file managers only show one of them. Total Commander (and maybe a few others) show both mounts.
 
Last edited:

surfer63

Senior Member
May 4, 2010
3,493
1,308
253
Zwolle
hvdwolf.github.io
I've decided to release CC3 to the public. Have fun. Manufacturer ID is set to 43. I am not responsible if you brick your unit or it explodes. I will provide 0 support. Do not PM me. Do not flash unless you know what you're doing or have a recovery update package to revert back to stock.
https://mega.nz/file/aYhyFCjJ#BbF7piHxK1zkOxcNfYHecUEofafEPiDfoq4Ux5SsGZY
Sorry for reacting so late. For whatever reason I completely missed your post (due to the new forum migration?).
I'm asking purely out of curiosity as I do not have a uis7862.
Did you again modify the T'eyes apps to remove the T'eyes checks?

I see that you did not remove the language/country settings for Russia.
 

warata

Senior Member
Apr 25, 2016
366
68
38
Tsu
hi surfer, I would like to use your app "ACC_ON broadcast events".
Because Joying's 7682 will stop media if ACC is interrupted even for a moment.
So I want to play the media after stopping for 1 second after losing ACC.
What syntax should I write?
 

surfer63

Senior Member
May 4, 2010
3,493
1,308
253
Zwolle
hvdwolf.github.io
hi surfer, I would like to use your app "ACC_ON broadcast events".
Because Joying's 7682 will stop media if ACC is interrupted even for a moment.
So I want to play the media after stopping for 1 second after losing ACC.
What syntax should I write?
Long answer to explain, but in short: "sorry, but you can't".

For 3rd party apps that ACC_ON/ACC_OFF broadcast doesn't work anymore on the SC9853i and uis7862 versions. As of Android 8.1 it is not allowed anymore to use that broadcast unless the app is "system signed", like the other FYT apps and specifically the main server app who broadcasts these events (and who receives it again from the MCU). Of course I don't have the FYT signing keys and neither has anyone of the other developers in the world, so not one single 3rd party app can do that. This is also the reason why apps like Tasker/MacroDroid/Automate etc. only partly function and can't use the "ACC_ON" broadcasts either.
Note: If you completely switch off and start your unit, you can still use the "boot completed" broadcast, but you don't want to wait 30-40 seconds if your device can resume in 1-3 seconds.

And with regard to your specific situation: If you start your car you turn the key completely. When turning the key it passes "ACC_ON"* , is turned further to start the engine (ACC_OFF) and when your engine is running, you release the key and it slightly turns back to the ACC_ON position.
When you turn off your car and immediately rotate the key back to it's ACC_ON position, you also "generate" the ACC_OFF and then ACC_ON broadcast. But we can't use that anymore
There is nothing you can do about that (as far as I know).
*: of course the technical name is different, but I translate it to our events/broadcasts

However, the main server apk starts a number of apps on resume. Most of them are still valid, but 3 of them are no longer in the firmware, but are started never the less.
@bambapin created FytStarter that uses the launch intent of one of those apps.
You can use Fytstarter to (re)start apps after resume, but not after the momentarily off/on action. So that won't help in your specific situation either.

And lastly: It is still alowed the use the USB broadcasts (ACTION_USB_ACCESSORY_ATTACHED, ACTION_USB_ACCESSORY_DETACHED, ACTION_USB_DEVICE_ATTACHED, ACTION_USB_DEVICE_DETACHED). When your unit resumes from sleep the external USB (mass storage) devices need to be remounted and apps like mediaplayers, need to know about this.
@realzoulou wrote an app for this broadcast, but I have no idea what it further does and whether you can use it.

My FytHWOneKey still contains ACC_ON/ACC_OFF as that can still be used on the PX5 and Sofia units.
Maybe I should build in an Android version check to hide these options on Android 8.1+
 
Last edited:
  • Like
Reactions: warata