yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] acidikjuice:
Thank you for this! I realize you don't want people asking questions in this thread but more about posting solutions, so i'll attempt to add two I think are missing and you can always add your input:

Q: Everytime the head unit enters deep sleep, apps granted the Accessibility permission (such as Tasker, Automate, Launchers) might lose this permission. Anyway to prevent this?

A: This is due to services being shut off (post) when the MCU calls for deep sleep. There is no way to stop this. However, you can use FYTStarter APK (here) for restoring accessibility or other issues between 'deep sleep'.

Q: Third party apps and external keyboards are unable to control volume or other media controls. How to overcome?

A: Volume and some other keys/controls are preempted by the Joying/FYT software. You need to interact with the Joying/FYT services to control these aspects. This post here shows an example apk that can interact with Joying/FYT services to control volume and other aspects (and another version here and some easy to use apk for volume that are tested working here). You can write your own APK using same methods or take advantage of this apk to send intents/commands to control volume and so on. You can use Tasker or Automate to provide this control to other things. For example, use Automate to intercept 'VOL UP' from an external keyboard and then use APK command to send 'VOL UP' to Joying/FYT service (and thus restoring ability to control volume from external controls like Joycon controller or external keyboards).

Q: How can I interface Steering Wheel Controls (Can Bus or other) not supported by Joying/FYT drivers

A: You can always use Joycon interface adapter (http://www.exinterface.com/cpjexr/) to convert SWC and CAN bus commands into USB keyboard inputs. The Joying/FYT work with this but you do need to use third party apps to map keyboard inputs into meaningful actions (start an app for example). As mentioned in above Question, media keys might not work directly from keyboard (unable to control volume for example) and you need to work around that with additional APK, but it can be done.

Q: is there anyway to setup so that when i receive a bluetooth call, i can go back to [other app]?

A: If you have set Waze or [other app] as your Navi app (via Joying settings menu), tapping the Navi button on your screen should allow you to go back to Waze. But also: some apps can be allowed to take over the phone function. Example is Magic Earth and Osmand+. For both I can allow them to make/receive calls. It means that you see a bar on the bottom of the screen, but it is actually not the Joying dialer. So I am IN that app. Google Maps can do that as well and I assume Waze might be able to do is as well too.

Did you give Waze that authorization when Waze asked for it during first loading it? Because if you did, you are in Waze with a phone call overlay at the bottom. Therefore: you cannot go to Waze because you are already in Waze. (Quote from Surfer post)
[FYT Android Head Units] maor23:
i've got a question.

if i download the lastetst version of update without never updating nothing, it will be ok?
[FYT Android Head Units] surfer63:
I really don't understand what you are asking.
[FYT Android Head Units] maor23:
i see there is many version of updates there, and i ask if i can only update with the last version or should i go over one by one with the updates ?
[FYT Android Head Units] surfer63:
All updates are full updates. You can skip all intermediate updates and immediately go for the last version.

Note though that you have to look at the MCU version: G32 or G32 (assuming you have a Joying SC9853i)
[FYT Android Head Units] maor23:
How can i know my mcu version? Like i see, in the last update from april 2020, there is only one link to download so i guess it good for all versions, no?

I also want to get some tips of it, maybe some recommended apps and etc..
[FYT Android Head Units] surfer63:
There is no MCU update in the latest firmware, so you are correct.

No tips about recommended apps. Other threads are for that.

And personally I consider it ********. Everyone has his own preference for certain apps.
[FYT Android Head Units] maor23:
so how can i know if i need os update or mcu update?
[FYT Android Head Units] surfer63:
Check your system info.

You only need an OS or MCU update if something is bothering you. If everything works fine for you, don't bother to upgrade.

For me the necessity to upgrade is two-fold:

fixes for bugs that bother me like Google voice call. But after 3 firmware upgrades claiming they fixed it, they still haven't fixed that. Although I hardly answer to calls in the car, and almost never make calls, it is terribly annoying that every other brand unit (MTC, QD, Atoto, etc) can do that, including all built-in car brand media-systems, but not the FYTs.

Android security fixes. It is still not clear to me whether FYT includes security fixes in their new firmwares by patching their code with the offical Android security fixes. As I hope they are doing that, I still flash every new firmware to my unit. But that's just a blind hope that they do apply the security patches.
[FYT Android Head Units] Lucasmrn:
Hello ! did you have found how to replace Joying setting app from original android settings app ? thank you ! :)
[FYT Android Head Units] surfer63:
No. That is no longer possible. That was only possible on the Intel Sofia models.
[FYT Android Head Units] Lucasmrn:
Thank you for reply, and I have a last question, I have put other firmware ( Teyes SPRO). Firmware was very good and fully functionnal except bluetooth.

I have mod allapp.pkg and fytmanufacturer with my number of head unit, the message "ui and mcu does not match" disapear is very good, but i don't now how to configure my Bluetooth for recognize in this firmware.

Bluetooth version is: GOC_V1.0/2019:07:18:16:59:52_gocsdk2

When i put other firmware he say: "unknow blink" How i can solve it ? mod file ?

Thank you for help.
[FYT Android Head Units] surfer63:
The only reference I have is the bluetooth "blink_config.ini" inside "/system/res/bluetooth". Please check the differences between your original file and the Teyes SPRO file.

I am also very interested in this. Last week (or so) I already wrote that the T'eyes Pro FYT software seems to be way ahead of the Joying software. Can you share some insights? Pros? Cons?

Does Google voice calling work? And did it work on the Joying firmware?
[FYT Android Head Units] Lucasmrn:
Thank you for Help my friend, I will try now. I don't Have a Joying head unit, it's a Ullgo head unit with fytmanufacturer = 108

I will get back to you quickly with specific details, link and all informations i can give you. I have test many sort of firmware on this forum but translation is very difficult on russian forum : https://4pda.ru/forum/index.php?showtopic=936715. This russian forum is a big library for mod our SC9853 head unit !

But I will test the best and after i will get back ;)

Sorry if my english is bad. I'm French :D
[FYT Android Head Units] surfer63:
I did already see that the Google contacts issue is the same as on ours.
[FYT Android Head Units] Lucasmrn:
I'M SO HAPPY ! :D

I Have found How to install all firmware on my head unit and fully fonctionnal bluetooth and CAN control ! (without touch the MCU ! )

1_ For bluetooth the solution is in the "config.txt" at the root of usb key and is very stupid, just replace "Sys.fyt.bluetooth_type=X" X is your number type ! In my case, the type in my original firmware config file the type is: sys.fyt.bluetooth_type=5 and i replace in Teyes config file "1" to "5"

2_If you install other original firmware you have message: "ui and mcu does not match" Juste open allapp.pkg and modify fyt.prop line: fytmanufacturer=x (X is the original value in your firmware)

I think you can try on your head unit, just download the lastest firmware and mod the file with my procedure: https://drive.google.com/file/d/1B-qCsn80P5wu2_fsF_YgCFOkqJvi3gR4/view

I love Teyes firmware because he have great look, very smooth. Launcher quality in my opinion is best than Joying...

Disadvantage for me: French Translation for the setting app is very bad. I think my next step is translate this app.

Other Thing: I want to try CC2 firmware but have some problem with activation. I Will try to test other firmware and i will back to you ;)
[FYT Android Head Units] surfer63:
-- (wrong answer)
[FYT Android Head Units] Lucasmrn:
Link for original CC2 firmware G32:

https://drive.google.com/file/d/16mfZKYcja7U9Hwt41dDtxB40IuAdnDnW/view

But i don't now at this moment how to activate it
[FYT Android Head Units] Lucasmrn:
Thank to [MENTION=2550900] surfer63[/MENTION]

Some commands that can be put inside updatecfg.txt

twipe_all # Wipe entire system
twipe_data # Will wipe data partition (but not /sdcard, internal memory). Wiping the /data partition will wipe all config, all 3rd party apps and updates of system apps. This is the same as a "reset to factory defaults"
twipe_sd # Will wipe internal memory /sdcard (but not the data partition)
dellapp # Remove all 3rd party apps
make_updates # Make an upgrade U-disk boot file
[FYT Android Head Units] sergiola123:
Where is this file located?

Enviado desde mi Redmi K20 mediante Tapatalk
[FYT Android Head Units] surfer63:
I answered you in the other thread. Do not cross-post. It is annoying and confusing. Answers to questions should be contained in one thread, which starts by having only one question.
[FYT Android Head Units] sergiola123:
Sorry

Enviado desde mi Redmi K20 mediante Tapatalk
[FYT Android Head Units] Flemischguy:
Hi,

I want to know more about the Teyes CC2.

I know it's very slim, has DSP and a IPS screen, has a ventilator to cool down the cpu, and is there a micro SD card available?

Is there a thread for this head unit?

Thanks.
[FYT Android Head Units] VwPassat3cDE:
Radio malfunction

Hi guys!

I have a big problem with my head unit. After an update with wrong firmware (from another manufacturer) my radio doesn't work more. Radio receives only 2-3 channels and RDS does not work more.

Seller sent me a new firmware and MCU, i have updated it but the malfunction remain.

Here more information about my head unit:

Cpu: Intel Airmont SC9853i 4GB+64GB

MCU: KEQ_53_C63L_G23P48F64_V:1.0

[IMG="Settings"]https://i.postimg.cc/tCLz9fw7/IMG-20200624-071759-1.jpg[/IMG]

I have analyzed firmware which has caused this defect, i've found this strange file:

[IMG="Folder"]https://i.postimg.cc/fbgcgrcw/Unbenannt.jpg[/IMG]

6521boardcfg.cfg

what is it for?

then i compared my settings with settings from head unit wich radio work normally and i've found this diference:

[IMG="Radio diference"]https://i.postimg.cc/BZmYfmJ1/radio.jpg[/IMG]

radiotype: nxp6xxx_6686 (9M) (0) this is my radio doesn't work

radiotype: nxp6xxx_6686 (9dft) (0) - this is another radio work fine

how can i change this settings? 9M to 9dft?

have anyone any idea how i can solve this problem?

I thank you in advance
[FYT Android Head Units] xjesus:
Hi,

I have a Teyes CC2 with the same CPU, and I can't find an "easy" way to do a full backup of the ROM or at least the apps + config.

Also, I have an annoying issue, I have a rear camera connected to AUX port, and I have another rear camera connected to the "rear camera" and powered only when I set the rear gear, but I can't have both displayed in the same time.

My biggest issue is that the AUX app have dissapeared twice for some reason and I have to install the July upgrade again to get it back.

Hope someone can point me in the good direction to solve these issues.

Thanks!
[FYT Android Head Units] hnkaraca:
How to update

I think my head unit has the same software with yours.

How do you update it? Where do you find the software for it?

Thanks
[FYT Android Head Units] wenefe1:
Good day

I have a problem with a Joying 10.25 Universal Radio

I have probably flashed the wrong MCU version now I only have 2/3 display

what can I do now??

Please help me

I think I need the MCU G23 version
[FYT Android Head Units] wenefe1:
Hello I need your help

I have a Joying 10.25 universal radio I have probably flashed the wrong MCU version now I only have 2/3 of the display I am grateful for every solution
[FYT Android Head Units] marteline:
What app are you using to replace and recompile? I tried android apkeditor and Windows APK Editor Studio, but after replace apk on the headunit (either trough lsec6521update or root access) the rear cam completely stop working.

Another problem about my rear camera, when I steer the wheels till the last position, the guidelines goes back to straight... Is there a way to fix that?
[FYT Android Head Units] surfer63:
In this case you just unzip the apk (like bullet 1 specifically mentions), replace the png images (bullet 2 and 3), and rezip the apk (like bullet 4 specifically mentions).

No recompiling whatsoever.

I have no clue about your guidelines going back to straight position.
[FYT Android Head Units] marteline:
Thanks a Lot... So simple... I feel so stupid... LOL

I Will look into the apk xml files in order to try to find something about the guidelines...
[FYT Android Head Units] jdroid654321:
I have a very basic question. What does the MCU refer to regarding the MCU firmware update? I have a Teyes TPro and the unit came with a separate climate control unit based on an STM32F105 RB chip. Does the firmware update apply to the AC controller or is there a separate MCU in the TPro unit itself for interfacing with other peripherals such as the CAN bus?

I suspect the second(that there's an MCU in the TPro) since I know my AC control unit uses an STM32. My TPro device lists the MCU as G23, but I've seen there's a G32 MCU as well. Is it the Silicon Labs EFM32G?

What do we know about the MCU in these units? What is the MCU responsible for?
[FYT Android Head Units] surfer63:
MCU is the abbreviation of MicroController Unit (see wiki), and in this case interfacing/controlling between the Android layer and the hardware layer (via the closed source drivers). The MCU has its own firmware.

There are 3 big motherboard/MCU manufacturers: FYT (for Joying, T'eyes, FunRover and a few others), STT (QD) and Microntek (all the MTCB/C/D/E units. By far the biggest producer).

These 3 make the motherboard and MCU and the MCU firmware and Android system software. And then you have Atoto and a few others who use a Mediatek chip-based motherboard/MCU and assemble the units around it. I do not know who really manufacturers these motherboards/MCUs.
[FYT Android Head Units] surfer63:
W.r.t. to your post in the other thread about the TPRO and trying to replace the software.

On the Sofia (some models and years ago) we had a very talented hardware programmer. He built the software from the ground up based on the existing Android layer.

His repos are at https://github.com/lbroid

mcud: https://github.com/lbdroid/MCUd

bd37033controller: https://github.com/lbdroid/BD37033Controller

MCUradio: https://github.com/lbdroid/MCURadio

SWIforMCUd: https://github.com/lbdroid/SWI_for_MCUd (steering wheel)

HFPClient: https://github.com/lbdroid/HFPClient (phone)

It is by now old, but these systems have hardware technically hardly changed.

Note that this is on the MCU layer and Android layer (system/boot/vendor/uboot/etcetera) of the unit.

You also need to replace the recovery partition via TWRP (or something alike). This is another big step done by another user but not for the later models.

Like mentioned in other threads: FYT simply builds on-and-on on their old software, simply adding "if..then.else" statements for new hardware and android versions.

LBdroid switched to completely other platforms building the unit both hardware/software wise from the ground up.
[FYT Android Head Units] jdroid654321:
@surfer63 thanks, this is actually very helpful. 🙏

Quickly digging through the code/comments I was able to see what the MCU is responsible for.

Perhaps we will see a custom Android 11 based ROM for the Tpro and compatible in the future after all. :)
[FYT Android Head Units] surfer63:
I almost forgot this post.

It contains the (8.1) source code for these units. This is the AOSP code with some extras (maybe even the drivers?), but not the FYT apps
[FYT Android Head Units] marteline:
Can anyone help me to find a way to open the volume control mixer directly? Maybe using tasker or other software... Because the only way to use it right now is to access settings / factory /type the password / and then click on the sound option...
[FYT Android Head Units] guanoapes77:
Hi Surfer, do you know if i can upgrade android (now is 6) on this headunit? tnx!

View attachment 5255233View attachment 5255235
[FYT Android Head Units] surfer63:
I really don't know. It is a FYT6025 board but uses a SC8830 wich uses the armeaby-v7a instruction set. It is a 32bit arm chip (4x ARM Cortex-A7 MPcore). It looks like a PX3 on a FYT firmware/hardware module board.

The sc9853i CPUs on the FYT6025 use IA-32 (x86), IA-64 (x64) which is an intel 64bit chip.

I have never seen such a chip in a FYT unit and know nothing about it.

But I really don't think you can upgrade it.

Note: You can find a lot of cpu specs on https://phonedb.net/index.php?m=processor&id=554&c=spreadtrum_sc8830a
[FYT Android Head Units] guanoapes77:
Thanks for your reply! ok i will check.. last question sometimes when switch on the headunit the info car app start itself and i must turn off manually, can i do something for stop it? Thanks again!
[FYT Android Head Units] surfer63:
No, I don't think so. I wouldn't know.
[FYT Android Head Units] Stevea53:
How do I get to the config txt. to change bluetooth on my Teyes Spro Plus?
[FYT Android Head Units] surfer63:
What do you want to change? Switching on/off, or what ..?
[FYT Android Head Units] warata:
Hi Surfer, This is a request from me. Is it possible to add a double tap option like the MTCE unit to the FYT HW OneKey app?
[FYT Android Head Units] surfer63:
-- Very short: No.

-- Now the long answer:

Normally in Andoid apps you have the GestureListener , the OnDoubleTapListener is part of that.

However, my FytHWOneKey does not use that listeners. The FYT main server apk is the listener in combination with the MCU. Based on the (hardware) keys pressed it generates an event, which I duplicate, so the user can/need choose for the default action (like the media player) or something the user wants instead (another music player).

I do nothing with the listeners. And the FYT main server and MCU do not listen to double-taps. The latest T'eyes models do support double-tap but I didn't check that.

-- And further explanation:

On the old Sofia models, the main server apk was modified in every release to start another method/function using the external script. There it was possible to act on taps and double-taps, because the script checked if the same key was pressed with (a user configurable) 0.2~0.4 seconds.

My Xposed modules completely "replaced" the internal method/functions of the main server apk (that is what Xposed can do) and in my Xposed modules I had double-tap, because there I used my own routines.

On a non-Xposed unit, or a non-modified main server apk, double-tap is not possible.

By now it is clear that all FYTs using the same board/CPU are 100% compatible, granted you set two properties to correct for the reseller. And even that is done in the settings. Not in the software.

I have already read that there is a new Xpsoed for Android 10 that "should" run on the uis7862. "Someone very brave" has to root his/her unit and install Xposed.

Then my Xposed modules could be used again, of course requiring some modifications for the new 7862 unit.

"Theoretically" I could also modify the main server apk again and deliver a main server apk with a new rebuild FYTHWOnekey.apk. And on a new firmware release modify the main server apk again if necessary. It is now after those years of experience also clear that the main server apk hardly changesand remains the same over all reseller models (same board/cpu).

But I don't want to anymore. If someone wants to take over and need hints, I am happy to provide them.

(This year I will probably buy a new (2nd hand) car and if I do, that one will certainly have an builtin navigation unit. I don't want to spend the time anymore. I am happy with the current functionality)
[FYT Android Head Units] warata:
Thank you for the answer. I understand your feelings and situation. I also spent a lot of money and time on the Chinese android unit. But I can't go back to a conventional unit that I can't see on YouTube while driving.:LOL:
[FYT Android Head Units] Stevea53:
Bluetooth will only recognize my cell phone. It will not find my OBDII, TPMS. I previously posted the problem and was told to add this line to Config.txt to fix the issue.

Sys.fyt.bluetooth_type-0

I do not know where to find that file to add it. I need a little more instruction.

Thank you for replying.
[FYT Android Head Units] guanoapes77:
Hi to all, i've discover a problem with my fyt headunit: when i connect my phone via bluetooth the wifi turn off itself and i can't turn on manually, if disconnect the phone bluetooth i can turn on wifi, do you know why? Thanks.
[FYT Android Head Units] PieterD82:
Does anyone have a (noob friendly) example to do exactly this?

In my case Accessibility permissions are always denied unless i kill Touch Assistant. Then apps that need Accessibility permissions run until the next wake-up from a deep sleep. I then need to kill Touch Assistant again. Needless to say this is highly annoying.

Thanks.
[FYT Android Head Units] surfer63:
Then switch off Touch Assistant entirely. Simply open it and set it to disabled.
[FYT Android Head Units] guanoapes77:
Hi, do you know why my navigation apps like waze, sygic, or maps stop to speak? Thanks
[FYT Android Head Units] surfer63:
Did you root your unit? If so: that's the reason.
[FYT Android Head Units] guanoapes77:
hi, no root. if i go in the settings of accesibility - speech and do 'listen an example' do not speaks. thanks for your help..
[FYT Android Head Units] PieterD82:
Unfortunately it appears to not be this straightforward. I have tried this many times. Touch Assistant simply re-enables itself after the device wakes up from deep sleep. And even when i disable it, it still does not allow Accessibility permissions for other apps that need it unless Touch Assistant is killed. And if killed, it "springs back to life" again when the device wakes up. It really doesn't like to share Accessibility permissions with other apps it seems.

The device isn't rooted and i don't plan to because i read it can cause issues with other things.
[FYT Android Head Units] surfer63:
Sorry. I have no further clues why it does not work for you.
[FYT Android Head Units] PieterD82:
That's fine. You've helped me out a lot with the device already ;)
[FYT Android Head Units] PieterD82:
Well, I went and did it, I disabled Touch Assistant by means of an ADB command line. Problem solved, surprisingly easy.
[FYT Android Head Units] ciris:
Please share
[FYT Android Head Units] PieterD82:
hi ciris,

I suspect you're addressing that question to me. Annoyingly disabling Touch Assistant did nothing. After waking up from deep sleep the device does again turn off all accessabilities for apps that need it, except for one. Tasker seems to be persistent so this does give me hope that there is still a way to keep accessibility on at all times for apps. I've looked further into it and found a plugin for Tasker called SecureTask. I will do my research on this plugin and post my results, if any.
[FYT Android Head Units] axz3200:
Hi. I have a big problem with the Ebilaen 4x64 dsp head unit ORM2.171019.012 firmware like yours. The seller sent you the firmware and MCU. please send me this firmware and most importantly MCU 2019.11.18 09:58:08 KEQ_53_C63L_G23P48F64_V: 1.0
[FYT Android Head Units] VwPassat3cDE:
Hi, I'm sorry, i haven't this version of MCU. I suppose you have some problems with volume and radio frequency wheels, with the new version of MCU this two wheels won't work properly. The firmware you can find on the 4pda forum, unfortunately I don't know how we can obtain the old version of MCU from seller.