yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
A custom ROM is a band-aid, not a real solution

I have had 2 Joyings for quite some years (Sofia and PX5 now). The hardware is not good, but not crap either. Support is a mixed bag: sometimes really good, sometimes bad(1). Your complaints are the same as for all the previous units. The software has a few long-lasting, very annoying bugs, but the biggest annoyance is the fact that it is a "closed ecosystem".

It is not running "normal" android, but a crippled version of Android.

Bluetooth has been removed from the normal settings and partially put into the BT app and partially into the MCU. USB has been crippled to only allow certain USB devices, which fortunately, are still a lot, but you can't use normal usb cams as dash cam for example. The radio chip is fully capable of all kind of RDS functionality, but as China does not use RDS it is low priority for them, which means we only get the most basic RDS functionality.

(1): My brother has a 1200 (or 1400) euros Pioneer. There were also issues with bluetooth. He had to wait more than a year before Pioneer considered it important enough for Europe to fix it. So much for an "A"-brand unit and support. So don't blame Joying (or one of the others) too much for delivering a 3x cheaper unit, which is real Android (although crippled), to let you install "everything" from the Play Store and/or F-droid..

When you create a custom rom on top of the existing fiirmware, you can perhaps remove the usb restrictions. The bluetooth however is also put in the MCU which "talks" to the real hardware. There is no way to reverse engineer this. This MCU plus its firmware is a very important part of this unit as "everything" hardware related goes through the MCU.

Making a custom rom would certainly improve the unit, but there are some bottlenecks you can't overcome. You would need to rewrite the android app layer on top of the MCU. More or less like lbdroid tried (intel stuff, MCUd, HFPClient, BD37033Controller, MCURadio, SWI_for_MCUd). I did run that custom ROM for a week, but at that time it was very rudimentary and would require an awful lot of work to make it really user friendly.

And then lbdroid left that project as (and I cite) "the garbage software that the meathead manufacturer has polluted these devices with" was too much, and he continued as [MENTION=9305891]96carboard[/MENTION] on the 96boards (RFC/Feeler project).

I myself have also been looking to create a custom rom, but abandoned it due to these MCU restrictions. My car did not have usb, bluetooth, so I did buy a Joying and am (in general) still happy with it.

If I am going to buy another car, it will either already have a modern unit in it (media, navigation, connections), or it will at least have usb/bluetooth and I will buy a cheap 7"-10" GPS-equipped tablet and put it with one of these nowadays available magnet coupling (to easy remove it) on my dash: big screen, standard android, better resolution, coupling to car audio via bluetooth (preferably) or usb, etc.
[FYT Android Head Units] julien_blanche:
Thank you very much for detailed explanation regarding the custom rom, have considering above there is not much to say about rest of the lifetime of this unit by lowering our hopes about the bugs that can not be solved by joying.

At least if there would be a xposed option most of the software related tuning could be done by our limited knowledge but i guess this is also not an option for a considerable time. Couldn't fine any libraries related x86_64 anywhere.

You seems to only person with knowledge that interesting in this topic and enlighten these head units with some of the precious inputs. From now on i will make a piece with this unit no more stressing myself about bugs.

cheers.
[FYT Android Head Units] czarekurb:
So how to do it? It is possible ? I have been using Tasker recently, basic things I can do but not automatically launch applications after switching on another application. It is strange that once you start them manually, then there is no problem with their automatic start until the radio is turned off.
[FYT Android Head Units] rigattoni:
To bring Tasker to foreground is just a workaround until [MENTION=2550900]surfer63[/MENTION] has updated his Joying Extra Tools for the newest firmware from Joying. As I learned, this has to be done for each single new firmware provided by Joying.
[FYT Android Head Units] zmylna:
Hi All.

Can anyone test that GPS audio mixing works fine?

I have problem with this. I set navigation app then i try to set mixing volume scale but regardles what i set navigation volume is always low. Navigation software is Polish Yanosik.
[FYT Android Head Units] bambapin:
Yes it is low, indeed you can mitigate the issue by setting to level 1 all other volumes and to 10 the GPS one (factory settings -> volume balance settings)
[FYT Android Head Units] surfer63:
This is another annoying "thing" in the FYT software (Joying is just a reseller of FYT units, just as Funrover is for example).

This volume mixing scale is only referential to the separate audio channels on startup. So if you change all kind of volume levels, they will be reset to the mixing volume on reboot. Again: "mixing", not adjusting real-life volume output (hardware from Amp, android audio through MCU through amp). So increasing the navigation bar to 10 and the rest to 3 (for example), is totally useless to compensate for "real world" output volume. So for me this setting is a complete waste of screen space.

And w.r.t to the soft instructions in your navigations app: I experience the same with my OsmAnd and Magic Earth Navigation, both on the old Sofia unit as well as my PX5 unit. I guess it is something internally in the unit (in other words: I do not have a solution).

---------- Post added at 01:52 PM ---------- Previous post was at 01:46 PM ----------

So that finally does indeed work on the 9853i units?
[FYT Android Head Units] bambapin:
Don't know... maybe it depends on the audio channel used by the navigation software, i use TomTom Go with the output channel set to "System" and the mixed level works also after a reboot.
[FYT Android Head Units] surfer63:
I can select media/music channel, notification or bluetooth channel in Osmand. And Media/music and bluetooth channel in Magic earth. On the PX5 and Sofia that does not make a difference apart from the fact that BT has a slight latency as a BT connection need to be opened (virtual in this case), the instruction "send", and then the BT connection need to be closed again. Like if using a phone.

No difference in volume though. And of course: I don't have a 9853i.
[FYT Android Head Units] zmylna:
Ok, i set audio channel in navi app to 'system' and is much better. Now i hear navi directions.
[FYT Android Head Units] bambapin:
I will check as soon as possible if setting the nav output on music channel the mixer makes some difference, at the moment the head unit is on my desk at home connected to my pc :)

I am still trying to solve the universal SWC problem: the "hw" side with arduino was easy, even the development of a server on the headunit to read the data transmitted by arduino (in the end i make it simulate an HW keyboard) was easy, the problem, as surely you already know, is to find a way (if it exists) to hook the native libraries to send the same commands that would send the physical keys of the headunit.

I started looking at the classes in the com.syu.ipc and com.syu.jni packages ... if you have any ideas / suggestions (or even just "let it be, it's impossible" :D) is obviously welcome.
[FYT Android Head Units] Jainyankee1993:
Do any live tv apps work? I can't get my Sling or Youtube TV app to work unfortunately :(. The live TV just never loads.
[FYT Android Head Units] czarekurb:
I confirm, I set the phone to automatically start yanosik after connecting to the radio and messages through the talk channel. Mute the music in relation to navigation messages is too small, It is a pity that you can not reduce the media volume below 86 because so much is blocked

Pozdrawiam.
[FYT Android Head Units] Cr4z33:
Just for my information what does 'FYT' mean? :confused:
[FYT Android Head Units] devtec:
I know since the April update it seems people have gotten their bluetooth calling to be significantly better. Has anyone though gotten their external mic to work, or is this all using the internal mic?

Any settings to disable internal mic and activate external? Have not been able to find anything in the menus...

I know for other Android units people have disabled to internal mic completely (by desoldering) in order to get the external working. Necessary with these units too?

TIA
[FYT Android Head Units] czarekurb:
generally everyone realizes that Joying sells unfinished pieces of clothing, and when yutube is bragging about how their devices are great, let's do some action to put out videos with errors, maybe it motivates them, you have to make noise on the internet
[FYT Android Head Units] julien_blanche:
That makes sense, i may start that youtube video trend when i get a chance. Let people know about what they are going to pay for.
[FYT Android Head Units] czarekurb:
Let anyone who shares the video on yutube will give information, I am already preparing the movie with the problem, propose the title as Joying Android 8.1 Intel Airmont eight-core 1.8GHz SC9853i

Let's see the power of the internet
[FYT Android Head Units] Cr4z33:
For YouTube I solved by using CarStream v2.01 APK.

At least when using HUR or AA.
[FYT Android Head Units] hawkjm73:
I've got a couple of questions I'm hopeing someone has some thoughts on.

Firstly, is there something non-standard about the 4g data connection? I told Play Music to download my music library, set to Wifi only. It preceded to download over the cell modem. I had to turn off data to get it to download over wifi. I've never seen an Android device do that before, so I don't know if Play Music was being a brat or if the head unit mis-communicates cell/wifi status. It isn't a huge deal is that I know about it, but I was curious if anybody else has had similar issues and perhaps looked into what was going on.

Secondly, I'm trying to get Tasker to control the volume. I know the regular Android volumes are prempted, so I need to send out something that looks like a volume knob turn. Several old threads have examples of sending an intent with a key event to a service, but none of those had any effect. I'm suspecting the packages are wrong, but I don't know where to look for the right one. Does anyone know an intent that works?
[FYT Android Head Units] czarekurb:
Bad scaling media pleyer

https://www.youtube.com/watch?v=dmnRW_46MeI
[FYT Android Head Units] Black6spdZ:
has anyone been able to enable the standard android navbar?
[FYT Android Head Units] surfer63:
There are a couple of "real" manufacturers: Microtec who makes the MTC/B/C/D/E units is the biggest one. A lot of these units are sold by Dasaita (Hot audio), XTrons, KGL, Sycane and many others.

FYT is another real manufacturer. Joying, Funrover, Witson (some units) and a couple of other resellers sell FYT units.

There is a 3rd real manufacturer. Joying also sells these units (ending on PX5S), but I can neither remember the name nor find it back. These are different again from the FYT and MTC units.

FYT and Microntec make the units, the MCU firmware and the Android programs.

FYT units and MTC units share a lot of same components like radio chips, BT chips, audio controller chips and more.

Their MCUs and therefore the binary MCU firmware, are different.

Both type of units come with their own Android firmware, as well as with their own MCU firmware.

The MTCD units are all hardware technical and software technical identical. Custom ROMs need to be created for a PX3, PX5, PX30 or PX6. A custom ROM for a PX3 (MTC-B/C) runs on all PX3 mtc units. A PX5 (MTC-D/E) custom rom runs on all MTC-D/E units. Search for HAL9K and Malaysk custom roms.

The FYT units use completely different MCUs and MCU firmware compared to the MTC units. The FYT and MTC units are not compatible at all when it comes to hardware related apps. Of course the standard Android apps "simply" run on Android.

FYT units are more dependent on their MCU versions. I don't know why. But in general a custom ROM for a FYT unit should be used with the MCU firmware the custom rom was built on. Some variations are possible, but not so much. That was on the Sofia. There are no custom roms for the PX5 and 9853i (as far as I know).
[FYT Android Head Units] Cr4z33:
Thanks [MENTION=2550900]surfer63[/MENTION] for the very complete explanation!

Wow there's a world behind these units. :D
[FYT Android Head Units] ojuniour:
any update regarding the newest firmware for the 1280*480 version (both new and old ui version)?
[FYT Android Head Units] julien_blanche:
You should ask from the joying otherwise you have to wait a month for them to publish. Also there is no difference between new ui head units and old ui head units. Their firmware is interchangeable. Only difference is the launcher and settings apk packages. You can install and test the both firmware whatever you like.

As for the different screen resolution head units there is only one difference between the firmwares is that allapp.pkg package. I have checked all files SHA-256 and all of them are the same for firmwares.

In a nutshell, joying is programming common files (6521_1, config, lsec6521update, updatecfg) for all head units (independent screen resolution) and making separation for allapp.pkg as for the update packages.

Also when you making magisk patch image, there is no screen resolution separation because you are using again common files to make that patched image files. So everybody install any patched image files form any joying units for rooting.

Additionally, you can extract allapp.pkg file by apkpack.exe program (attached) and view all apk packages as separate. If you make small modifications like changing icons or backgrounds of the apk you can extract them with apk easy tool and replace the necessary things and then zip the apk. You can put modified apk inside its folder by root explorer.

For instance I took some icons from new ui and put them in to the old ui interface by modifying the launcher.apk package in that way.

I have examined may and june firmwares and they made modifications both 6521_1 file and most of the apk packages itself. So every time they update the firmware they are changing apk files as well. This is exhausting for them also for us to keep modifications up to date by ourselves.
[FYT Android Head Units] fabien_m2002:
For the owners of the new June firmware, what's new, improvements, bugs compared to the May one?
[FYT Android Head Units] zmylna:
From Joying support description:

"solved the Steering wheel problem with the Zlink app, Bluetooth phone call, and the TPMS problem."
[FYT Android Head Units] surfer63:
I also do that. If you use apktool to decompile the apks you will almost always find differences, but the code does not necessarily have to change. They do change part of the code but sometimes only very few things.

So, if you compare with apktool, you will almost always find (small) differences.

If you use jadx-gui, you will find less differences as it shows you the java code (as good as possible).

A second check you can do is to look at the AndroidManifest.xml in the apk. It has a build/compile date. (note that if you unzip, the AndroidManifest will be in binary format. You need apktool or jadx(-gui) to see the ascii version).
[FYT Android Head Units] julien_blanche:
Thanks for your input, i have 2 questions regarding the apk files;

1- Is there a direct option to compare 2 apk files within the apk tool or do i have to examine one by one to find differences ?

2- Can we run or adapt different platform apk files like px5 or px6 to our intel head units ?

thanks..
[FYT Android Head Units] surfer63:
1. You can't do this directly. You have to decompile both apks and use tools like diff (linux) to compare files/folders or FC (windows) to compare files (no folders)

2. Technically yes. All the FYT android apks are pure java so it doesn't even matter whether they are intel sofia, rockchip px5 or intel airmont 9853i. This is not the case however for the main server apk and the sub server apk (and settings). Those are really platform dependent.

Of course apks do evolve. The radio apk for example changed libraries (=dependencies) "somewhere" in the 6.0.1 version, and again on the PX5. The video player and music player are still completely interchangeable (and completely useless from my point of view). In this case also the MCU firmware is a benefit. It functions as a HAL (=Hardware Abstraction Layer) for the apks. They can still talk the same to the MCU and that MCU will convert the commands depending on the radio chip (for example).

Unfortunately FYT, Microntec and "the 3rd" do not use the Android Automotive HALs. This would really break open the market and allow java programmers to build great functioning custom roms without the limitations of the FYT firmware (or MTC firmware).

Of course the manufacturers protect that and want to stay on their own "closed ecosystem", which is actually terrible.
[FYT Android Head Units] bambapin:
I checked the behavior on my headunit. It seems that the only volume influenced by the mixer is the FM Radio, which actually changes the level relative to all of the others and the effect is persistent even on reboot.

However looking at the logs you see strange things, i didn't try the bluetooth but i think that the volume of the radio is managed in a completely different way from all the others.

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

I'm afraid it is not possibile using Tasker... the examples of sending an intent require a server component that actually listen for that event.

Me too i was looking for something similar but i haven't found anything in this firmware, don't know if it is common to all FYT based head units, [MENTION=2550900]surfer63[/MENTION] surely knows more.
[FYT Android Head Units] ghost010:
I have read some page's. Is this unit any good compared to the others.. or is there one unit coming on top of the rest? Could not really find a recommended thread.

I want to use my 350z steering wheel controls: vol up/down, speak / phone(??? thats how the icons look like) and seek up/down(probbably for cd on oem radio).

I never used the middle 2 buttons(speak/ phone?) because.. even tough i have them, there is no carkit. so i have no clue what the 2 exactly do.

I'll be using an amp for the sound sytem, so no stock speakers, head unit does not need to be "powerful".

Apart from that i'll mostly be using spotify, usb, and waze(or flitsmeister).

I'm okey with using different FM/music apps.

it would however be nice if this unit supports "news" or w/e its called..

And does the DAB+ still suck on joying?

I know enough about android phones and regular car stereos.. but this will be my first venture into mixing them.
[FYT Android Head Units] julien_blanche:
If you have lots of time and patience for bug solution process that may take a while or never then go for it but its not worth it. Smooth driving experience is not about that head unit has most powerful specs on the paper its about how powerful software manages the hardware. Think like a bugatti driven by a amateur driver like joying. Worst part is that there will be no custom rom at current situations and you end up with joying support to wait solutions.

I would go with new px6 if i were you because its best bang for the buck as for hardware/software adaption and it has lots of support by users or custom rom options in near future. Think like a nissan gtr driven by a f1 pilot.

Never get fooled by advertised boosted specs that looks superb on the paper when its come down for logical selection.

Hope that helps..
[FYT Android Head Units] ojuniour:
Thanks for the input..

I will have to say the new ui does have a digital clock to the right for the (1280*480 devices) taking about 1//4th of the screen. I do not want that. And I also do know that patching won't have effect on the resolution, obviously. Based on what you said, does that mean i can just literally take the file built for a different resolution and deploy it on mine (which is 1280*480) ?
[FYT Android Head Units] julien_blanche:
New ui is just useless as much as all joying head units and almost there is no brain behind that design. It just kills part of the screen all the time. However i liked its icon packs and adjusted to my ugly launcher :)

Yesterday i ask to joying support about new firmware and they said there is none. I think our 1280x480 devices are not their first priority. After that i start to thinking that i can adapt 1024x600 firmware file to my device.

As for the firmware compatibility, some of the apk files have not multi resolution support inside the allapp.pkg file. That is why they are making different firmware for literally same devices.

Actually they could make a multi resolution apk files inside one firmware for all devices but i think they love extra work.

Anyways, below apk files have not multi resolution support and you have to pull them from your device specific firmware and put inside the any firmware's allapp.pkg then install it;

steering, settings, music, bluetooth and video
[FYT Android Head Units] bambapin:
Maybe I found a way, it's just a proof of concept with a really minimal UI but it's still a start.

Install the app attached, first start it and check if the 3 buttons affect the volume.

If they work, you can use these intents EXTRA from Tasker:

"com.mobeedom.android.hu.VOL_UP"

"com.mobeedom.android.hu.VOL_DOWN"

"com.mobeedom.android.hu.VOL_MUTE_SWITCH"

this is a command line example:

am start -n com.mobeedom.android.test.testhu04/com.mobeedom.android.test.testhu04.TaskerActivity --esn "com.mobeedom.android.hu.VOL_MUTE_SWITCH"

Hope it works, it does on my hu with the 06.12 frmware
[FYT Android Head Units] edcam33:
Is there anyway when using Android auto to eliminate the Joying default pad when calling ?
[FYT Android Head Units] ojuniour:
so basically get the latest (1280*480) update they posted on their website, extract the above apk, then replace it with the VERY newest update posted on this thread?
[FYT Android Head Units] julien_blanche:
1- Get the June firmware for 1024x600 devices and extract the apk package and simply delete the apk files which you don't want to install

2- Get the may firmware for 1280x480 devices and extract the apk package and take these apk packages (settings, music, video, Bluetooth, steering)

3- Now put those files (settings, music, video, bluetooth, steering) to the June apk package and repack them with the software which i shared

4- Now you can update your device with latest June update files.

5- Also oem folder is not mandatory if you don't want to install the apks inside the oem folder just delete the folder.

6- Same goes for the apk package if you don't want to install trash apks like video, calculator, guide just delete them and repack the rest.

If you want to fresh install with deleting everything just replace the command twipe_data with twipe_all inside the updatecfg file, this will delete all internal memory.
[FYT Android Head Units] devtec:
Has anyone gotten their external mic working?
[FYT Android Head Units] edcam33:
Is there anyway when using Android auto to eliminate the Joying default pad when calling ? Model: EU-JY-UO138N4G
[FYT Android Head Units] dirk_:
Hi,

you mean if I make my changes at my rooted radio (fm radio and bluetooth MOD) it is enough to uninstall magisk? How can I uninstall magisk itself?

Sorry for my bad english.

Dirk
[FYT Android Head Units] julien_blanche:
If you are using the stock TS type input mic it is working but you need to be sure that firmly plugged to head unit.

No as far i know

There are 2 way to do this, either you can uninstall it from magisk manager menu or you can put stock boot.img file inside to 6521_1 file that used while patching along with the Isec6521update file.
[FYT Android Head Units] dirk_:
Hi,

thanks for your answere.

Is it correct If I use the second way I must delete the pached_boot.img inside the 6521_1 file?

Dirk