yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] Thorsteenster:
What is this "Xposed", does it come preinstalled? I hate the default music player on mine and installer Player Pro which I'd bought years ago. Seems like it can't see my SD, and when I try to give permission from with in Player Pro it errors with cannot open folder selector or something to that affect.

I can open an mp3 from file browser in Player Pro and went through all the app settings changing anything that looked remotely related with no success
[FYT Android Head Units] CTDPeti:
Xposed framework, has an own thread, lets use search, it is a developer tool for rooted devices.

I tried more 3rd party music players and all of them need to give manually the music folder path

Sent from Caterpillar S41 using Tapatalk
[FYT Android Head Units] tangcla:
We have a new version of firmware!

https://drive.google.com/open?id=1wXAq7buphpz6cY7slVMteALwIG6PrgpM
[FYT Android Head Units] rigattoni:
The complete firmware is not really stable as it should be.

I got the new firmware yesterday and I had really problems to get it go to sleep mode after flashing the update.

I needed to flash back to the march version and had problems to get this working with sleep mode.... Took half the day to get it working...

There were a couple of resets and new flashes necessary to get it nearly stable coming back from sleep mode even without installing any 3rd party software on it.

Each single 3rd party app has issues and seems not to be optimized yet to be used with this chipset so it´s really a "va banque" play if an app works as expected.

Just now it seems to work on the bench, but I still need some app installation to be done to get the unit car usable.

I test really after each installation some clamp changes and if it is stable I setup the next one.

Just a word about rooting:

Don´t root directly after flashing the new firmware. Let the system get the needed update from playstore and first if you did that try to flash the rooted firmware. Otherwise you don´t get a stable working unit. I registered some strange playstore issues, like finding updates, but no download possible, because they stuck in waiting for download.

I am not amuzed about this unit in the moment. Too many stability issues....
[FYT Android Head Units] DustoMan:
I'm really annoyed that my steering wheel controls no longer work in Android Auto. It's not just "play/pause" but also "Next"/"Previous" so I can't do quick skips foward/back in my podcasts without reaching for the screen. I wonder if going back to the version of zlink that was in the prior version would make any difference. It's just in the oem folder of the firmware download so it's wouldn't take much to extract it.
[FYT Android Head Units] seb21:
Hi

I was able to mod Joying bt app to allow to pair with any OBD device.

Just replace original bt app and fix the permissions.

No need to reboot.

Paired device will be recognised by system as "OBD II".

Tested with Vgate device (Bluetooth name "V-Link")

Note: This mod will allow you to pair any device ,but it will be seen by system as OBD. Tried this with my bt keyboard.:mad:

I'm cannot use links, so sorry for this inconvinience.

Link:

DELETE_MEhttps://ufile.io/bub0g3js
[FYT Android Head Units] r9ronie:
Apps crashing frequently

Are you guys facing apps crashing like Apple music and Kodi?
[FYT Android Head Units] Black6spdZ:
Is there any way to enable the standard android nav bar?
[FYT Android Head Units] tangcla:
Which firmware version are you running?
[FYT Android Head Units] Black6spdZ:
April release
[FYT Android Head Units] tangcla:
See above, May release.
[FYT Android Head Units] Black6spdZ:
So May release includes the standard android nav bar? No release notes and didnt feel like wiping my box to find lots of new bugs instead of fixes and improvements
[FYT Android Head Units] tangcla:
It's meant to.

None of the firmware upgrades come with change logs so it's up to you. Either that or roll back to March (and deal with poor Bluetooth call quality).
[FYT Android Head Units] Drakknoid:
I'm not sure how I should edit it.

Should it look like this with everything after the # removed including the #?

com.google.android.googlequicksearchbox
com.txznet.txz

or remove everything above com.google.android.googlequicksearchbox

com.google.android.googlequicksearchbox #Google语音
com.txznet.txz

or just remove all the #

语音应用，语音应用在录音时需要机器临时静音，以免干扰录音，影响识别效果
通常语音应用录音开始时会请求Audio Focus,该文件中适配的应用，在申请Audio Focus时
服务会做相应的音频处理，释放Audio Focus时恢复到当前状态声音输出
com.google.android.googlequicksearchbox Google语音
com.txznet.txz

or another way that I'm not thinking of.

any help would be appreciated.
[FYT Android Head Units] seb21:
Put # before com.google

#com.google

#com.txz
[FYT Android Head Units] yzf750:
New Joying update fixed this and all of google problems with voice responses. Its not on there blog yet but some of us got emailed a link to the update. I updated this morning and got the pull down status bar fix too.
[FYT Android Head Units] tangcla:
Yep, I posted the link yesterday, too :)

I will be doing the firmware flash tomorrow.
[FYT Android Head Units] sergiola123:
could you put the link?

Enviado desde mi Redmi Note 5 mediante Tapatalk
[FYT Android Head Units] Drakknoid:
Yup fixed the google voice bug.
[FYT Android Head Units] tangcla:
https://drive.google.com/open?id=1wXAq7buphpz6cY7slVMteALwIG6PrgpM
[FYT Android Head Units] kouklo:
Sorry, unable to open the file at this time.

Please check the address and try again.
[FYT Android Head Units] tangcla:
Try this:

https://drive.google.com/open?id=1wXAq7buphpz6cY7slVMteALwIG6PrgpM
[FYT Android Head Units] julien_blanche:
Hi, i just got my new Joying 1280x480 10.25' Intel head unit with old UI. Can I install the new UI firmware on it to try out ? (Basically same head units, only diff is the interface)

If I brick my device at the end is there any recovery process available?

Thanks.
[FYT Android Head Units] julien_blanche:
I took apart the unit and made some measurements regarding the rca out voltages with 50hz 0db test track

Front and Rear channel outs: 1.9v

Sub out: 0.6v

Head unit is using 25v 10000uf input filter capacitor to eliminate DC ripple voltage and noise which is very good comparing to other head units (3300uf capacitor).

There is slight audible difference between Rca and Digital outs regarding voice quality (i can live with that) , 2 db difference between volume levels. Also attached internal photos for your reference.
[FYT Android Head Units] thomasorr:
I've updated to the latest firmware 2019.05.15 and rooted it however the root now breaks the TPMS, it seems as though the unit cannot talk to the TPMS USB device.
[FYT Android Head Units] fabien_m2002:
Hello

what's new with the new firmware?

I cannot see it in joying website, why they remove the link? Not stable?
[FYT Android Head Units] tangcla:
I've posted the changes earlier in the thread, look a few posts up.

These haven't been finalised yet, and will be put on the website soon.
[FYT Android Head Units] surfer63:
Can you explain what you did?

What did you enable/disable/change in which smali?

Did you only change the goodriver -> driver stuff in "com/syu/app/ipc/IpcObj.smali" ?

(I apktool-ed your bt mod and the original)
[FYT Android Head Units] seb21:
There are 3 methods calling FuncPairLink.

I changed the result of the name comparison always be TRUE , in all 3 methods.

Java decompiled:

if (!android.text.TextUtils.isEmpty(strName)) {
if (com.syu.ipcself.module.main.Main.mConf_PlatForm != 5) {
bPopPwd = strName.startsWith("OBD");
} else if (strName.startsWith("OBD") || strName.startsWith("gooddriver")) {
bPopPwd = true;
} else {
bPopPwd = false;
}
}
bPopPwd =true; <--- something like this
com.syu.app.App.bPopObdFlag = bPopPwd;

Smali :

.line 766
:cond_5
:goto_2
const v0, true <--- added this
sput-boolean v0, Lcom/syu/app/App;->bPopObdFlag:Z
[FYT Android Head Units] surfer63:
Thanks for your explanation
[FYT Android Head Units] Cr4z33:
Is Android Auto supposed to work flawlessly with latest firmware updates?

I am setting up and wiring a brand new 1DIN 4GB unit with default (ak not updated by me yet) firmware set to March 2019.

So fa I ran all Google Play Store updates, but AA is not working yet.

The Z-Link screen keeps saying it is waiting for the phone to be connected by USB (although it is and although the cable starts charging the smarphone...).

I know I could use HeadUnit Reloaded, but I would better like to use it the normal way by connectin the phone (S10+ Exynos with stock unrooted Pie firmware) by USB.
[FYT Android Head Units] tangcla:
Have you enabled usb debugging on the phone? It's necessary.
[FYT Android Head Units] Cr4z33:
Oh crap really? :(

Pff that's not good if someone wants to protect his phone...

At that point I might have to go for HeadUnit Reloaded anyway.

Thanks for letting me know.
[FYT Android Head Units] DustoMan:
You don't need usb debugging enabled to use zlink. Your phone needs to be plugged in and unlocked. I just make sure it on the launcher screen and then it connects. It's like this with any Android Auto receiver.

---------- Post added at 11:07 AM ---------- Previous post was at 11:00 AM ----------

And you need the Android Auto app installed on your phone. I figured that was obvious, but all you mentioned was updating the play store. It doesn't need to be installed on the radio.
[FYT Android Head Units] Cr4z33:
Yeah I know how it works usually on common radios. ;)

In fact it works flawlessly on my wife's 2019 Ford.

Anyway in the meantime (waiting for Joying support team to see what's going on here) I am using HUR in WiFi mode.
[FYT Android Head Units] DustoMan:
Ok. Have you tried using a different USB cord? Are you plugged into the USB socket on the radio and not using any splitters or extensions? I have found these radios to really not like those which is really unfortunate.
[FYT Android Head Units] Cr4z33:
It's a straight USB cable connection between phone and Joying USB port. :)

So far I've tested already three cables:

Stock S10+ cable

Brand new Aukey nylon cable

Some spare Cisco cable

All of them were not detected by Z-Link, but were charging the phone.

Let's see what the Chinese guys will find out? :eek:
[FYT Android Head Units] DustoMan:
That sucks. TBH this version of zlink is way more buggy than the one in the April firmware. I will sometimes get a red screen on my phone stating that the car software doesn't meet Android security requirements. But then a second or two later it will connect for about 15 to 20 minutes and then disconnect. The disconnect sometimes happens when my phone gets a notification but sometimes not.
[FYT Android Head Units] julien_blanche:
There is no voltage at (orange-black) Amp-cont wire to turn on the external amplifier when the head unit starts. Does anybody know anything about this ? It should put 12v on that wire acc to wiring diagram.
[FYT Android Head Units] seb21:
Have you turned on AMP in settings ?
[FYT Android Head Units] julien_blanche:
currently I have 9853i 1280X480 head unit with firmware 2019.5.15 and had discovered following issues;

1-Bluetooth screen does not minimize during calls

2-There is no voltage on AMP-CONT (orange-black) wire, normally there should be 12v on it to remote turn on external amplifier

3-Top status bar color is neutral and white lettering on it, if there is white screen under the status bar then I can not see any home or back icons neither clock and any other data at the status bar

4-Currently car play function through Zlink ver 1.3.1 does not work with IOS 12.3
[FYT Android Head Units] Russell_S:
Well I've checked mine and I can confirm that mine does the same whereby in Poweramp when you raise the volume to 100% it almost immediately drops back down to 87%.

However, I have had a play with the settings and I've found what is causing it.

If you go into the 'Poweramp settings --> Audio --> Output --> OpenSL ES Output' you will see the following screen:

View attachment 4713176

Under 'Use For Output Devices:' click the settings icon (circled in red) for whichever ones says Active, in my case 'Wired Headset/AUX (Yours will probably be the same). You will then see this screen:

View attachment 4713175

You will probably see the 'No Headroom Gain' setting will be disabled. Enable it (as in the picture) and the volume control will then stay at 100%. However, on mine I think there was some distortion present.

Maybe you just need to re-teach the steering wheel commands in the 'Car Control' app.

Hope this helps.
[FYT Android Head Units] K1kote:
Guys recommend buying these new Joying devices with 8.1? There are already roms or mods?

Im looking this for my Jetta

https://www.joyingauto.com/joying-n...avigation-system-with-bluetooth-4gb-32gb.html

Enviado desde mi Pixel 2 XL mediante Tapatalk
[FYT Android Head Units] fabien_m2002:
Hello

thanks you for your settings but it does not work with mine. I don't know why because we have same unit. I set all your settings but volume still drops down to 87%

For steering wheel commands, it's an issue well known related to the API which has changed and does not work anymore.
[FYT Android Head Units] PaulBorges:
Hello guys it's possible to get root privileges on this new radio with the intel chip?:eek:
[FYT Android Head Units] surfer63:
I suppose so. My method for rooting the PX5 might also work for the new Intel Airmont but not with the same files, as these PX5 files are for an ARM architecture, not an Intel architecture. So do not use my PX5 package. The Intel sofia package is probably too old and might not work on android 8.x

The SuperSU package also comes with an X86 and an X64/AMD64 su version. The apk is of course multi-architecture.

But if I were you I would wait until you have a ROM available from Joying so you can reflash in case things go wrong.

You could start with a complete listing of your /system.

In a terminal something like

ls -lR /system > /sdcard/system_listing.txt

and attach that to a post.

And if you have adb already running over tcpip you migh do an

adb shell ls -lR /system > /sdcard/system_listing.txt
[FYT Android Head Units] PaulBorges:
total 1540
drwxr-xr-x 2 root shell 4096 2008-12-31 16:00 xbin
lrw-r--r-- 1 root root 15 2008-12-31 16:00 vital-app -> /data/vital-app
lrw-r--r-- 1 root root 7 2008-12-31 16:00 vendor -> /vendor
drwxr-xr-x 9 root root 4096 2008-12-31 16:00 usr
drwxr-xr-x 3 root root 4096 2008-12-31 16:00 tts
drwxr-xr-x 3 root root 4096 2008-12-31 16:00 res
-rw-r--r-- 1 root root 1398357 2008-12-31 16:00 recovery-from-boot.p
drwxr-xr-x 56 root root 4096 2008-12-31 16:00 priv-app
drwxr-xr-x 3 root root 4096 2008-12-31 16:00 media
-rw-r--r-- 1 root root 2946 2008-12-31 16:00 manifest.xml
drwx------ 2 root root 4096 1970-01-01 00:00 lost+found
drwxr-xr-x 6 root root 12288 2008-12-31 16:00 lib64
drwxr-xr-x 26 root root 12288 2008-12-31 16:00 lib
drwxr-xr-x 5 root root 4096 2008-12-31 16:00 framework
drwxr-xr-x 2 root root 8192 2008-12-31 16:00 fonts
drwxr-xr-x 2 root root 4096 2008-12-31 16:00 fake-libs64
drwxr-xr-x 2 root root 4096 2008-12-31 16:00 fake-libs
drwxr-xr-x 15 root root 4096 2008-12-31 16:00 etc
lrw-r--r-- 1 root root 15 2008-12-31 16:00 config.ini -> /oem/config.ini
-rw-r--r-- 1 root root 74748 2008-12-31 16:00 compatibility_matrix.xml
-rw------- 1 root root 3332 2008-12-31 16:00 build.prop
lrw-r--r-- 1 root root 19 2008-12-31 16:00 blink_ring.mp3 -> /oem/blink_ring.mp3
lrw-r--r-- 1 root root 21 2008-12-31 16:00 blink_config.ini -> /oem/blink_config.ini
drwxr-xr-x 3 root shell 8192 2008-12-31 16:00 bin
drwxr-xr-x 74 root root 4096 2008-12-31 16:00 app

ls -lr /system > /sdcard/system_listing.txt

---------- Post added at 11:36 AM ---------- Previous post was at 11:16 AM ----------

That's it

total 1540
drwxr-xr-x 2 root shell 4096 2008-12-31 16:00 xbin
lrw-r--r-- 1 root root 15 2008-12-31 16:00 vital-app -> /data/vital-app
lrw-r--r-- 1 root root 7 2008-12-31 16:00 vendor -> /vendor
drwxr-xr-x 9 root root 4096 2008-12-31 16:00 usr
drwxr-xr-x 3 root root 4096 2008-12-31 16:00 tts
drwxr-xr-x 3 root root 4096 2008-12-31 16:00 res
-rw-r--r-- 1 root root 1398357 2008-12-31 16:00 recovery-from-boot.p
drwxr-xr-x 56 root root 4096 2008-12-31 16:00 priv-app
drwxr-xr-x 3 root root 4096 2008-12-31 16:00 media
-rw-r--r-- 1 root root 2946 2008-12-31 16:00 manifest.xml
drwx------ 2 root root 4096 1970-01-01 00:00 lost+found
drwxr-xr-x 6 root root 12288 2008-12-31 16:00 lib64
drwxr-xr-x 26 root root 12288 2008-12-31 16:00 lib
drwxr-xr-x 5 root root 4096 2008-12-31 16:00 framework
drwxr-xr-x 2 root root 8192 2008-12-31 16:00 fonts
drwxr-xr-x 2 root root 4096 2008-12-31 16:00 fake-libs64
drwxr-xr-x 2 root root 4096 2008-12-31 16:00 fake-libs
drwxr-xr-x 15 root root 4096 2008-12-31 16:00 etc
lrw-r--r-- 1 root root 15 2008-12-31 16:00 config.ini -> /oem/config.ini
-rw-r--r-- 1 root root 74748 2008-12-31 16:00 compatibility_matrix.xml
-rw------- 1 root root 3332 2008-12-31 16:00 build.prop
lrw-r--r-- 1 root root 19 2008-12-31 16:00 blink_ring.mp3 -> /oem/blink_ring.mp3
lrw-r--r-- 1 root root 21 2008-12-31 16:00 blink_config.ini -> /oem/blink_config.ini
drwxr-xr-x 3 root shell 8192 2008-12-31 16:00 bin
drwxr-xr-x 74 root root 4096 2008-12-31 16:00 app

ls -lr /system > /sdcard/system_listing.txt
[FYT Android Head Units] surfer63:
No, it is not "ls -lr".

It really is "ls -lR"

-r, --reverse
reverse order while sorting

-R, --recursive
list subdirectories recursively

You only list from z-a. I need the listing though all subdirectories.

If your android does not support the ls -lR, try "busybox ls -lR /system > /sdcard/system_listing.txt".

Joying, or actually FYT, sometimes delivers really crippled versions of the linux tools.

Edit:

Otherwise do a:

ls -l /system/bin > /sdcard/system_listing.txt
ls -l /system/xbin >> /sdcard/system_listing.txt

Note the >> in the 2nd line
[FYT Android Head Units] surfer63:
You are not a unix/linux user I guess ;)

The second command is also necessary. That is why I mentioned the >>.

>: redirect to file, >>: redirect and append to file

and I forgot one thing:

so please do both commands:

ls -l /system/xbin > /sdcard/system_listing.txt
ls -l /system/etc >> /sdcard/system_listing.txt

I guess FYT is still using the exact same setup they use on the Sofia 3GR and PX5, which means that the su binary should be in /system/xbin.
[FYT Android Head Units] surfer63:
You didn't use the >> in the second command. Only the etc folder is now captured. /etc does contain the init folder, which is good.

Finally I need xbin

ls -l > /system/xbin > /sdcard/system_listing.txt

Is this now the /system/xbin folder as well?

I think this is the /system/bin folder.
[FYT Android Head Units] PaulBorges:
I used the first 2 commands,

ls -l /system/bin > /sdcard/system_listing.txt
ls -l /system/xbin >> /sdcard/system_listing.txt

I think that 2 folders are this....

Confused....:eek:
[FYT Android Head Units] surfer63:
Yes, you are right. The strange thing is that your unit does not seem to have an su binary. That makes it different to all previous Joying units.

Your xbin folder seems to be completely empty apart from tcpdump. I have never seen that.
[FYT Android Head Units] PaulBorges:
That's right!

What you think about root it? Possible?

I need to change the hosts file and the generic.kl :D

Thanks
[FYT Android Head Units] surfer63:
Yes, I still think it's possible. In the SPDIF thread you can read that FYT/Joying is currently working on the firmware to correct an error with ODBII. That means (most probably) that they will publish a new firmware in the (very) near future. When that becomes available it is more easy to check the entire config and see how it can be rooted (if possible).

Why do you need to change the hosts file?

And what is the generic.kl ?
[FYT Android Head Units] PaulBorges:
Hosts file to use adaway, because this radio unit have sim card 4G internet.

The generic.kl is a file in the keyboard configuration and i want to change 3 keys ( volume_up, volume_down and mute ) to (sound_up, sound_down and sound_mute). I have one knob volume and dont make the volume change correctly.:fingers-crossed:
[FYT Android Head Units] PaulBorges:
/system/usr/keylayout/generic.kl

Seems that multimedia keys -113,114,115 only work with SOUND and not to VOLUME. I already test it on the SOFIA model and the exchange works.

Thanks
[FYT Android Head Units] prrlhkr:
Hey guys, new to xda but I just got one of these units. I can confirm the only thing in /system/xbin is tcdump. And yep, the OBDII is broke. I am paired with the adapter but torque can't generate a list of Bluetooth adapters.

Happy to report these radios do not appear to have a high pitched whine over the speakers (a complaint I've had with all my previous Joying HUs), RDS works for us in the US, and you can actually install Netflix from the app store (my life is complete)!

In case anyone's curious, Passmark score of 118566 on the cpu
[FYT Android Head Units] PaulBorges:
About the OBDII same issue in my radio. Connect and disconnect the bluetooth. I ask to the joying about the issue and th3y answer that i have to wait for the firmware.... :crying:
[FYT Android Head Units] yzf750:
So whats up with the stock music player. It finds none of the music on my unit. I have to use file explorer to click on a song to get it to play on the stock player. My pandora music downloads to /music folder on the unit also and it does not see it. My older Joying always found any tunes on the unit and played them right from the player.
[FYT Android Head Units] SummerLiu:
which firmware you used to update your unit, the 1280*480 unit has a different firmware.
[FYT Android Head Units] julien_blanche:
The firmware which joying support gave me..

Does anybody know how can I install exposed framework to this intel head unit ? cos software is awful and lots of bugs in it..
[FYT Android Head Units] avtintellegent:
hello masters. I am still a little confused by the unit that I have when I install the phone apk. the call is going well, but the sound produced from the other person is silent ... is there a solution
[FYT Android Head Units] tangcla:
Have you upgraded your firmware?
[FYT Android Head Units] avtintellegent:
I still use manufacturer software. Phone and message menu does not exist.

so I decided to install both applications ... the message menu went well. the phone menu didn't work properly
[FYT Android Head Units] tangcla:
Manufacturer has released new firmware - use this:

https://drive.google.com/open?id=1wXAq7buphpz6cY7slVMteALwIG6PrgpM
[FYT Android Head Units] blinger:
I'm on the new version firmware now. Anyone have issues getting chrome to load webpages?
[FYT Android Head Units] avtintellegent:
Thanks you so much... I Will try it. :good::svetius::o
[FYT Android Head Units] rigattoni:
Please use the thread search for xposed.

this has been asked and answered yet.
[FYT Android Head Units] ch_swat_89:
while navigating over google maps and telefon call, i loose audio when google is telling me the navigating instructions. Only setting google in background and recall helps....

any fix for that?
[FYT Android Head Units] sergiola123:
Does anyone have the latest update that some users sent by mail?

Enviado desde mi Redmi Note 5 mediante Tapatalk
[FYT Android Head Units] tangcla:
Literally, three posts above yours. :rolleyes:
[FYT Android Head Units] sergiola123:
ups, sorry
[FYT Android Head Units] Cr4z33:
Any trick to get Google Assistant to work (apart from inside Android Auto)?

Once installed and if I want voice output instead of text it says it is not supported yet.
[FYT Android Head Units] tangcla:
Works fine for me, I just tested it today.

What firmware are you on?
[FYT Android Head Units] Cr4z33:
Latest firmware.

I've to say that I installed Google Assistant manually from the Play Store.

Was that correct?
[FYT Android Head Units] tangcla:
Mine already had "Assistant" in the apps, didn't manually download it - not sure why that is.
[FYT Android Head Units] Cr4z33:
Hmm mine not... that's weird...
[FYT Android Head Units] sergiola123:
Root new update?

Enviado desde mi Redmi Note 5 mediante Tapatalk
[FYT Android Head Units] Black6spdZ:
where did you find the root for newest version?