yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] gamer765:
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.
[FYT Android Head Units] purplefruity:
Why did you buy the joying over Teyes?

I was looking to purchase the Cc2+ however the dash frame is the wrong color and no CarPlay. With joying, there is CarPlay and the dash frame is the correct color. I was thinking of just using nova launcher and making it look more like a radio.
[FYT Android Head Units] erkanbasak:
[QUOTE = "gamer765, gönderi: 84028523, üye: 1488726"]

CC3'ü halka yayınlamaya karar verdim. İyi eğlenceler. Üretici kimliği 43 olarak ayarlandı. Ünitenizi kirletirseniz veya patlarsa sorumlu değilim. 0 destek sağlayacağım. Bana PM atma. Ne yaptığınızı bilmiyorsanız veya stoğa geri dönmek için bir kurtarma güncelleme paketiniz yoksa yanıp sönmeyin.

https://mega.nz/file/aYhyFCjJ#BbF7piHxK1zkOxcNfYHecUEofafEPiDfoq4Ux5SsGZY

[/ ALINTI]

did it work android auto on teyes rom ? how can i install on my unit? can you help me
[FYT Android Head Units] gamer765:
Joying is more readily available and slightly cheaper than Teyes. I also appreciate that they use a singular harness like every other radio manufacturer does and not the mess that is the modular Teyes radio harnesses. Also the fact that Joying has android auto. Those were my deciding factors.
[FYT Android Head Units] gamer765:
I mentioned I will not provide any support for this. These units are not the same as the old SC9853i ones plus we don't have an official update package to restore from should things go wrong. If you really want to flash it, check the thread on how to flash SC9853i, the process is similar for UIS7862. I can't help further to avoid having the finger pointed at me should something go wrong. Also yes, android auto works. I included carkit into the rom.
[FYT Android Head Units] gremlin190:
My CC3 should be here on Monday. I've been trying to follow the forum over on 4da, so I saw some of the issues with the playstore not working. What all do you need to do to get Android Auto working on a head unit without using HeadUnit Reloaded? I'd love to just plug my phone in and have it work (Even better if I can do it wirelessly) :)
[FYT Android Head Units] gamer765:
I'm not sure if Android Auto could be made to work with the Teyes headunits since normally they dont include that feature. Joying includes the feature, so the app just works. The app does appear to do some sort of license check to enable certain features. I've seen checks for Carplay Wired, Carplay Wireless, and Android Auto wired. You can try loading CarKit on the Teyes, but I doubt it would work. I believe the license information for that feature is stored somewhere in fytdata partition.
[FYT Android Head Units] stefcio007:
AutoKit has been updated to take advantage of high resolution displays.

CarPlay looks really good now on a 1280x720 display, I think before it was just stretching 1024x600 no matter which setting you would choose.
[FYT Android Head Units] Pheelyred:
Do anybody know the password for the developer options for the new joying 13.3 10.1 please.....thanks
[FYT Android Head Units] gamer765:
Should be the same as previous units. 3368
[FYT Android Head Units] Pheelyred:
Cheers thanks.....thats working just fine!
[FYT Android Head Units] stefcio007:
You can also use 5768 to adjust the backlight current, which can increase the brightness, use with caution obviously.
[FYT Android Head Units] toecheese:
Just installed one of these Joying units. I usually hook up my car stereo only to 12V constant power so that I can use the stereo without needing the key, and just turn the radio off manually. But I don't see any way to power this unit off. Is there a shutdown button somewhere?
[FYT Android Head Units] barnesk9:
I purchased the 4gb ram 64gb rom version from Amazon (https://www.amazon.com/JOYING-Android-Detachable-Touchscreen-Bluetooth/dp/B08JCTM1Q2) and installed it over the weekend. I upgraded from the intel sofia with android 5. Here's my thoughts

-The build quality is soo much better. The screen feels like they addressed all the issues that the sofia units had and it doesn't feel cheap or flimsy at all. I also really like that there's nothing on the front panel anymore.

- The sound is much better too. I haven't had to turn the volume to the max one time and it's still louder than the sofia unit turned all the way to 36.

- This one included the sim card slot!! Since I just added a free line my car can now have a wifi hotspot for my kids and I don't have to set it up with my phone anymore.

- The external mic actually works! No need for any hardware hacks so that's awesome.

- The software is exactly the same, granted this one runs a lot faster. The ui and menu layout have minimal changes but because all I run is headunit reloaded anyway I don't really care that much.

And yes there is software installed that will do Android auto for you but it doesn't auto launch when you start the unit and you can't change the size of the layout which Carlink has some weird hybrid of the normal and the hidpi screen where the nav bar is in the left but the big bar on the right isn't there.

-The only real negative so far is that the screen freaks out and touches itself for around 6 minutes whenever I start the car on a cold morning. That and no root so I can't get rid of the apps I won't use
[FYT Android Head Units] Duan:
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.
[FYT Android Head Units] barnesk9:
-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.
[FYT Android Head Units] cleaa:
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.
[FYT Android Head Units] gamer765:
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.
[FYT Android Head Units] surfer63:
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.
[FYT Android Head Units] gamer765:
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.
[FYT Android Head Units] surfer63:
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:

How to Manually Clear or Set Dirty Bit on Windows Volume | Password Recovery

In this tutorial we'll show you how to manually clear or set the dirty bit for a NTFS & FAT32 volume in Windows 10, 8, 7, Vista and XP.

www.top-password.com

or

WhatSoftware Blog

WhatSoftware, a daily updated Tech Blog with basic and advanced, unbiased software reviews, computer tips news and more!

www.raymond.cc
[FYT Android Head Units] awellam:
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
[FYT Android Head Units] warata:
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?
[FYT Android Head Units] surfer63:
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
[FYT Android Head Units] surfer63:
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://xdaforums.com/t/fyt-units-n...-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)
[FYT Android Head Units] osmosizzz:
Can anyone run a Geekbench 5 benchmark on the new UIS processor just to have a performance comparison?
[FYT Android Head Units] warata:
Your app perfectly fulfilled my wishes. Thank you very much! It's a pity that the like button can only be pressed once.
[FYT Android Head Units] oitakabuto:
I just bought 10 inch model JY-UQS10N4G and installing it.

Does any one know this model can split screen?
[FYT Android Head Units] Allan_Hun:
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?
[FYT Android Head Units] surfer63:
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.
[FYT Android Head Units] surfer63:
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.
[FYT Android Head Units] warata:
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?
[FYT Android Head Units] surfer63:
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+
[FYT Android Head Units] Allan_Hun:
Is it possible to circumvent the limited bluetooth support with a BT usb dongle?

Could anyone recommend an external mic?
[FYT Android Head Units] surfer63:
No, you can't circumvent the BT support using something else. It is hardcoded blocked in the BT app. The BT stack has been crippled on purpose and there is no way to change this. On Android 5.1.1/6.0.1 a programmer made a workaround. FYT detected that and blocked that workaround as well. FYT simply doesn't want you to connect BT devices other than the approved ones: that means the devices from their resellers.

It is not that the microphones as such are so bad (not very good either). The point is that the microphones are not noise cancelling microphones. That means on higher speeds the noise becomes the dominant sound and is not filtered out. The unit itself does not support noise cancelling either.

If you want something better, you really need to search for some complete nose cancelling solution.
[FYT Android Head Units] Allan_Hun:
I guess the other brands 7862 also share this crippled BT stack?

Could noise cancelling software improve the phone speak quality -Or maybe ASUS AI Noise-Canceling Mic Adapter?

Rear cam has to be NTSC or PAL?
[FYT Android Head Units] lgsony:
i got a HU same with your cpuz but selling said its TS10

i just dont a factory reset and the TLINK for carplay is gone.

mind to share the TLINK apps?
[FYT Android Head Units] stefcio007:
I bought a lavalier mic to test as an external mic. Hopefully the quality is better in terms of the cable sheilding and what not.
[FYT Android Head Units] warata:
That's sad news. This 7682 unit is the best of the more than 30 Chinese android units I have purchased, and even MTCE is equipped with power retention in the event of ACC loss.

It would have been almost perfect for me if this "Delay Power Off When ACC Off" feature was alive.

Thank you anyway.
[FYT Android Head Units] surfer63:
Yes. I know what you mean with that delayed function. Actually it is also builtin to the FYT (Joying, t'eyes, etc) units as the main server remains active for 2 minutes to allow other apps to properly shutdown or to simply kill them.

So it must(!) have this feature, but it is obviously not used for 3rd part apps.

The 7862 units are ARM units and might support Xposed (when rooted). in that case you could still hook on to the ACC_OFF broadcast and use it for your own advantage, like a 10 seconds or 1minute (or so) delay.
[FYT Android Head Units] surfer63:
I don't know about the MTCD-E units, to be honest.

I don't know whether noise cancelling software will help. I know "Noise killer" for Android and now I'm curious as well ;)

I actually never call inside my car other than the extreme short "Hi, I'm home around .." or "Big traffic jam. It will not be home before .."

There are also noise cancelling microphones, but I never tried them and did not read about them either in these forums (but like said: I'm not really interested as I don't use it).

All units support both ntsc and pal. The newer sc9853i and uis7862 units support the AHD cameras going up to 1080p. But you could have found that on your resellers website as well.
[FYT Android Head Units] Allan_Hun:
MTCD-E units? So all 7862 are not same hardware?

I don't trust resellers info. My current unit was listed as 10" 4x1.3Ghz 2/32Gb android 9. But it is 9" 4x1.1Ghz 1/16Gb android 8.1 !

Anyone knows if usb headsets works?

If so asus noice canceling mic adapter should also work...
[FYT Android Head Units] Allan_Hun:
Couldn't you solve it installing an off delay?
[FYT Android Head Units] surfer63:
Sorry. Maybe I spoke too soon. I do not know whether MTC also creates uis7862 units.

Anyway, you can use the hwgetinfo.apk from my signature. It will certainly tell you if you have a FYT unit.

And if it is a FYT unit, the answer is: yes, all FYT units share the same software meaning that on every unit the BT stack and BT app is crippled. Also a very limited and crippled set of BT functionality has been removed from the Settings.apk and put inside the BT.apk
[FYT Android Head Units] Allan_Hun:
My current 8227 is made by xyauto (some apps report manufacturer as alps) But is awfully slow and the soundquality is bad. So I'm looking for a replacement.

7862 would solve the speed problem but it seems like none of the Chinese android headunits have true hifi sound, unless you go digital. And even then the dac implementation leaves a lot to be desired.

The dac in my car only have rca or BT input so the noisy rca output and crippled BT is a problem. Guess I could use a mobile usb dac. But android resamples usb audio to 48Khz before the dac converts from digital to analog with my dsp converts back to analog.

So the audio chain would be unnecessary complicated and the quality would be less than optimal.

If only pioneer and kenwood didn't lock their units and offered facials for my car...
[FYT Android Head Units] surfer63:
Your 1 Gigabyte memory is the performance issue. You need at least 2GB, or better, 4GB. Those 1GB/16GB models are generally very cheap, and for good reason. Please spend little more money on a 2/32GB or 4/64GB model.
[FYT Android Head Units] warata:
I don't know what the off delay you say, but the 7862 ACC Off Delay setting doesn't work.