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

Search This thread

Allan_Hun

Senior Member
Mar 11, 2014
401
114
Gl.Rye
The atoto one will most likely work with atoto units only. All other DVR cams are most likely the same thing just with a different brand sticker slapped on it. I personally wouldn't use those DVR cams since they're limited to 720p resolution at a measley 30fps. They also feature ADAS but most people end up turning it off since alerts are annoying and delayed and end up being dangerous if you actually rely on it, so it's a toy at best.
The atoto cam is actually an Anytek x28 cam, and it works with other "none atoto" HUs...
I don't care much if it is full hd or only 720p -720p should match our screen resolution anyway. So I think pic quality at night and app quality matters more.
And yes I do know it's a toy gimmick -But my car is all about toy gimmicks :)
I also realize that none of the hu resellers produce their cams, so identical are available from other cheaper sources. But I have read that some cams looking identical have different hardware inside, so I'm a little worried that cheaper version might be inferior.

Anyone have any experience with these dvr cams?
 

yokala

Member
Oct 6, 2016
32
6
Samsung Galaxy S10e
Hi Guys,

I'm trying to source a third party display to fit in a custom dash kit for my vehicle. I'm not too familiar with firmware and drivers but I write Javascript evey day, can solder, and fabricate reasonably well.

Does anyone know where to start?
  • It sounds like the unit has to be using LVDS or MIPI to talk to the mainboard (because that's what the CPU supports), but beyond that I have no idea what to look for in a display controller.
  • If moving to a different resolution screen, are there config files that need to be updated in the firmware? Is this just like updating a JSON config?
  • Has anyone tried swapping two different Joying screens on the same head unit?
If it can help you I found that file online. It's a collection of configs for different display. I used one of the file to make a 1024x600 display work on a Joying head unit that came originally with a 1280x720 display.
If you find a display that match one of these config files you can flash it by copying it on a USB key along with the 'lsec6521update' binary like any update or firmware.
 

Attachments

  • LCD_Panels.zip
    10.4 KB · Views: 9

Spiff198

Member
Aug 21, 2017
23
0
EDIT: XDA didn't like me attaching the photos, just got broken links so I'm sorry that they're embedded like this.

Joying just sent me a review unit of their new 10.1" Android 10 head unit so I figured it should have its own thread. It looks like they're pumping out updated versions of all their previous devices by the day so I imagine they'll have versions of this in all the different screen sizes soon. First impression is good. The interface is appreciably more responsive than the Intel unit I currently have in the car. I'm working on some videos but figured I'd throw some pictures in here. Here is an unboxing and interface tour video:

The PCB looks is clearly iterative but looks to have some significant redesigns, especially with the power supply which is much larger than on the previous Intel design, through that might be required for extra derived voltages for the new UIS7862 SoC.

The previous Intel PCB used an STM32 MCU in between the main SoC and the bluetooth module which probably contributed to the difficulty interfacing Bluetooth devices that weren't specifically allowed by Joying. The area where this chip was now looks to be filled with power components though the same Bluetooth module is still used. I'm hopeful that this means there's direct communication from the SoC to the BT module, but that'll take more digging to determine. There is also a new general purpose ARM Cortex-M4 MCU added between the SoC carrier board and the DSP chip (GigaDevice GD32F330R8T6). I'm curious if that's taken the place of the old STM32 chip or if it's used for something else. Hopefully I'll be able to determine what it's used for, but I'm not touching anything until I get it installed and reviewed.

The green PCB is the Intel board and the yellowish one is the new Android 10 board. Of note is the fact that the new PCB has Joying's name silk screened onto it where the old Intel one didn't. So, at bare minimum, this board is spun just for Joying, even if the only differences are the silk screen layers.

Any requests for specific details?

yHVsNkX.jpg


BF1savB.jpg


b7WJzrV.jpg


3exgCwW.jpg


1W9xbit.jpg


RQ38Whj.jpg


b70J2vp.jpg


IzADAW0.jpg


nZUo3Z5.jpg


YKA0Apr.jpg


BMnYuWV.jpg


zhoRUwF.jpg


WI1D5tO.jpg


Rprw1Fx.jpg


MxcsJYf.jpg


iTAU0dU.jpg
 

Spiff198

Member
Aug 21, 2017
23
0
EDIT: XDA didn't like me attaching the photos, just got broken links so I'm sorry that they're embedded like this.

Joying just sent me a review unit of their new 10.1" Android 10 head unit so I figured it should have its own thread. It looks like they're pumping out updated versions of all their previous devices by the day so I imagine they'll have versions of this in all the different screen sizes soon. First impression is good. The interface is appreciably more responsive than the Intel unit I currently have in the car. I'm working on some videos but figured I'd throw some pictures in here. Here is an unboxing and interface tour video:

The PCB looks is clearly iterative but looks to have some significant redesigns, especially with the power supply which is much larger than on the previous Intel design, through that might be required for extra derived voltages for the new UIS7862 SoC.

The previous Intel PCB used an STM32 MCU in between the main SoC and the bluetooth module which probably contributed to the difficulty interfacing Bluetooth devices that weren't specifically allowed by Joying. The area where this chip was now looks to be filled with power components though the same Bluetooth module is still used. I'm hopeful that this means there's direct communication from the SoC to the BT module, but that'll take more digging to determine. There is also a new general purpose ARM Cortex-M4 MCU added between the SoC carrier board and the DSP chip (GigaDevice GD32F330R8T6). I'm curious if that's taken the place of the old STM32 chip or if it's used for something else. Hopefully I'll be able to determine what it's used for, but I'm not touching anything until I get it installed and reviewed.

The green PCB is the Intel board and the yellowish one is the new Android 10 board. Of note is the fact that the new PCB has Joying's name silk screened onto it where the old Intel one didn't. So, at bare minimum, this board is spun just for Joying, even if the only differences are the silk screen layers.

Any requests for specific details?

yHVsNkX.jpg


BF1savB.jpg


b7WJzrV.jpg


3exgCwW.jpg


1W9xbit.jpg


RQ38Whj.jpg


b70J2vp.jpg


IzADAW0.jpg


nZUo3Z5.jpg


YKA0Apr.jpg


BMnYuWV.jpg


zhoRUwF.jpg


WI1D5tO.jpg


Rprw1Fx.jpg


MxcsJYf.jpg


iTAU0dU.jpg
how is the heat sink attached to to cpu? and what are the dimensions of heat sink
thinking about adding fan when mine arrives. My px units ran hot
thanks:)
 

Allan_Hun

Senior Member
Mar 11, 2014
401
114
Gl.Rye
My unit runs at 60 at ambient (23°C). Worthwhile question..
WATERCOOL IT!
No honestly I hate fans so if I don't feel it slows down due to thermal throttling I will just let it swet.
60°C at idle? Seems a bit high if so. But without knowing where the sensor is placed, this reading isn't very useful.
Anyone knows what temperature the unit starts throtteling? That could give an idea about what temperature the manufactor believe is safe.
Do we know what process the soc is build on?
 
Last edited:

TacticalSmoores

New member
Jul 5, 2015
2
0
I see 40°C+ ambient temps in the summers. There's no airflow behind my headunit. I think I will need to invest in a fan and heatsinks.

I'm thinking Noctua's NF-A9 FLX (92mm) would work pretty well in a car. It comes with adaptors that should bring 15v down to 12v. And, at 17db you're not going to notice it behind the dash.
 

Allan_Hun

Senior Member
Mar 11, 2014
401
114
Gl.Rye
2 days ago I replaced my tomostrong 4core 16/1gb headunit with a mekede 7862 128/6gb unit. So far I have been quite happy with the new unit. But I just realized that bit perfect audio output through the spdif does not seem possible :-(
Anyone knows if the 7862 can play bit perfect audio through usb with usb audio player pro?
 
I am not sure that this a Joying problem but I am asking anyway.

I recently checked my Google devices page and cleaned it up by signing out of old devices which I do not own anymore. Mistakenly I also signed out of my Joying headunit remotely.

When I got in my car the next day I could not sign in to my account anymore. The Check Info window flashes and returns to the previous window. This happens with Play Store, Maps, Chrome, etc.
I did some research and though it might have something to do with the Android System Webview issues of recently. I tried every solution I could find but to no avail.

In the end I decided to do a factory reset but to my surprise, I still can't sign in to my Google account after a reset! The issue is the same, the Check Info windows flashes and disappears. So either the Joying factory reset is not a deep enough reset or something is wrong with my Google account?
I am very hesitant to sign out of my other devices to see what happens there.

I would appreciate some help.
 

gottahavit

Senior Member
Nov 10, 2009
1,378
316
Not sure if this will be relevant with the Joying or not, but just found the USB Mode toggle on the UIS7862 IDoing. It's the "..." menu at the root of developer setting. Two items in Chinese, top one is host mode, bottom is device mode. Got USB Debugging working fine even with usb-c cable from my laptop.
 

Allan_Hun

Senior Member
Mar 11, 2014
401
114
Gl.Rye
Not sure if this will be relevant with the Joying or not, but just found the USB Mode toggle on the UIS7862 IDoing. It's the "..." menu at the root of developer setting. Two items in Chinese, top one is host mode, bottom is device mode. Got USB Debugging working fine even with usb-c cable from my laptop.
What is the password for developer settings?
 

Allan_Hun

Senior Member
Mar 11, 2014
401
114
Gl.Rye
WATERCOOL IT!
No honestly I hate fans so if I don't feel it slows down due to thermal throttling I will just let it swet.
60°C at idle? Seems a bit high if so. But without knowing where the sensor is placed, this reading isn't very useful.
Anyone knows what temperature the unit starts throtteling? That could give an idea about what temperature the manufactor believe is safe.
Do we know what process the soc is build on?
Replying my self (going mad?)
Unisoc 7862 is most probably build on TSMC 12nm. So same process as Geforce 10/16/20 series.
Would you be worried if your geforce ran at 60°C ?
 

xdamember2

Senior Member
Mar 8, 2016
349
81
Roseville
Do you, or anyone else, happen to know what frequencies the 7862 supports?
I need 800, 1800 and 2600mhz for 4g. It would be a deal breaker if I have to connect through my phone's hotspot...
Here's what Joying told me:

item only supports the below types:
GSM: GSM850 EGSM 900 DCS1800 PCS1900
WCDMA: BAND1 BAND2 BAND5 BAND8
TD-SCDMA: BAND34 BAND39
TDD-LTE: BAND34 BAND38 BAND39 BAND40 BAND41
FDD-LTE: BAND1 BAND2 BAND3 BAND5 BAND7 BAND8 BAND20 BAND29A

and not supported types:
AT&T: BAND12 BAND14 BAND17 BAND29 BAND30 BAND66
Verizon Wireless: BAND13 BAND66
T-Mobile: BAND12 BAND66 BAND71
Sprint: BAND25 BAND26 BAND41
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Not sure if this will be relevant with the Joying or not, but just found the USB Mode toggle on the UIS7862 IDoing. It's the "..." menu at the root of developer setting. Two items in Chinese, top one is host mode, bottom is device mode. Got USB Debugging working fine even with usb-c cable from my laptop.
    1
    I figured out the trick today to replace the launcher with a custom one on the IDoing. Apparently they don't show the "pick default launcher" setting, but if you install Nova and then any launcher you want you can use Nova settings to set any launcher as default(probably well known trick here, but never found it searching).

    IDoing says they are looking at options to fix the KPH to MPH(not holding my breath).
    1
    I also found the BSP and kernel source codes, very recently uploaded.

    BSP source on Github
    Github root of unisoc-android that has tons of other things I do not yet understand in there

    The same guy has a bootloader unlock tool on his personal Github.

    @surfer63 is this of any interest to you?
    It's pretty much the whole Android OS source only. This doesn't include any FYT proprietary apps/libs source code. With this you could probably build a new fixed Android base and restore some features that were removed/disabled, but you can't do much else. The hardware was built in a way that custom proprietary libraries are necessary to communicate with it rather than using Androids built in native HALs. So even if you build an android package including the native fm radio app with this, it won't work since it can't communicate with it, unless someone wants to volunteer and reverse engineer and write new libraries for aosp.
    1
    Hello guys,

    do you have issue with microphone on these head unit? During a call, the caller ear a lof o echo and the volume of the voice is very low. I’ve done a test downloading a MIC test app and the quality is very terrible. If I’m also very near the MIC nothing change. I want to know if you have same trouble, may be it’s my mic fault.

    thanks
    An update: seller (Joying EU) send me a new firmware (2021-03) that has mic gain set and also another change on BT side. After installation (that has wiped all the unit) now the mic quality is better than before.
    1
    So same pass as factory settings?
    yes
  • 4
    EDIT: XDA didn't like me attaching the photos, just got broken links so I'm sorry that they're embedded like this.

    Joying just sent me a review unit of their new 10.1" Android 10 head unit so I figured it should have its own thread. It looks like they're pumping out updated versions of all their previous devices by the day so I imagine they'll have versions of this in all the different screen sizes soon. First impression is good. The interface is appreciably more responsive than the Intel unit I currently have in the car. I'm working on some videos but figured I'd throw some pictures in here. Here is an unboxing and interface tour video: https://youtu.be/h__Zc0fwOtw

    The PCB looks is clearly iterative but looks to have some significant redesigns, especially with the power supply which is much larger than on the previous Intel design, through that might be required for extra derived voltages for the new UIS7862 SoC.

    The previous Intel PCB used an STM32 MCU in between the main SoC and the bluetooth module which probably contributed to the difficulty interfacing Bluetooth devices that weren't specifically allowed by Joying. The area where this chip was now looks to be filled with power components though the same Bluetooth module is still used. I'm hopeful that this means there's direct communication from the SoC to the BT module, but that'll take more digging to determine. There is also a new general purpose ARM Cortex-M4 MCU added between the SoC carrier board and the DSP chip (GigaDevice GD32F330R8T6). I'm curious if that's taken the place of the old STM32 chip or if it's used for something else. Hopefully I'll be able to determine what it's used for, but I'm not touching anything until I get it installed and reviewed.

    The green PCB is the Intel board and the yellowish one is the new Android 10 board. Of note is the fact that the new PCB has Joying's name silk screened onto it where the old Intel one didn't. So, at bare minimum, this board is spun just for Joying, even if the only differences are the silk screen layers.

    Any requests for specific details?

    yHVsNkX.jpg


    BF1savB.jpg


    b7WJzrV.jpg


    3exgCwW.jpg


    1W9xbit.jpg


    RQ38Whj.jpg


    b70J2vp.jpg


    IzADAW0.jpg


    nZUo3Z5.jpg


    YKA0Apr.jpg


    BMnYuWV.jpg


    zhoRUwF.jpg


    WI1D5tO.jpg


    Rprw1Fx.jpg


    MxcsJYf.jpg


    iTAU0dU.jpg
    3
    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
    2
    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.
    2
    Whats the plus of going with Joying over Teyes?
    The main difference between Joying and Teyes is 2 things: Teyes releases updates more often than Joying. Teyes software looks more appealing than Joying.
    If you look back at the SC9853i platform, Joying units last received an update on April 7 of this year. Teyes on the other hand, their last update was just a few days ago, December 4. It seems like Teyes continues support for their products even after new ones are released to replace them, while Joying abandons software support once new products are on the horizon. Joying software looks dated and bland, and overall their user interface looks clunky and out of place. In my opinion, it looks like someone forced an outdated AOSP-ish tablet UI into a head unit. If you look at Teyes units, they're all about the bling and eye candy and making the user interface look modern and like it actually belongs in the car. There is a caveat though, CC3 in its current state is rather buggy. On my CC3 converted unit, I can't seem to use Google play store. I've also read people are having issues signing into yandex products as well. It's not a huge deal breaker for me since it'll get resolved with future updates.
    2
    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.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone