yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] kampfschachtel:
thank you for the advice. your Q&A is awesome and safed me already a lot time to catch up with Android 6. Thank you for your huge effort spend on this.

kepp my mod list as small as possible: A must mod is viper4Android, so rooting needed.

The USB DAC works without mod but no volume control BUT the follwing happens: (till now no mods/no rooting just the Radio out of the box and updated with 25may release)

I have both outputs (Chinch preout and USB out via DAC) of the joying connected to my DSP and can switch the input from Chinch to USB Digital In.

With this setup the DAB+ app plays only via the USB out/DAC, via Chinch out no sound. Haven't tested more apps so till now.

How can I fix this? I assumed via chinch out I get everything and via USB out only the digital stuff without volume control.
[Android Head-Units] dyabolikarl:
I noticed this too. Rocket player started to keep my unit awake after i added a 64gb card. No idea why (maybe the music scanning).

I disabled the music scan on start up and then there was no music when i started the car (sd card didn't mount fast enough or something).

So i swapped to power amp now i have that 15 second delay on "play command" from the SWC for the music.

I thought i was on drugs wondering why the one button didn't work. Did you uninstall google and it fixed it or what?

Seems I can't win with this thing.
[Android Head-Units] edit:
Yes, after days of testing, wiping, reflashing, and reinstalling I found out that without the Google app, Poweramp plays the music 2-3 seconds after the unit starts. It starts playing even before the Poweramp app pops up on the screen (if the app was active on the screen at engine off).

So I have to let go Google and all the voice recognition features in Waze unfortunately....
[Android Head-Units] hard12figureout:
ble not supported

Hi guys does anyone know how to add ble support to the head unit? Trying to use my airlift performance app and it won't work
[Android Head-Units] kampfschachtel:
so the Android 6 "fun" starts already (info about unit and release see signature):

1) My DVR cam (original joying) is not recogniced, brings up "cannot find tachograph....."

2) in Settings under menu Storage only the internal memory is displayed but the whole SD-Card part is completly gone. I cannot erase my SD card or see who much memory is left....SD is present in the file manager and works. wanna wipe it as it has all the old spotify and goole map offline maps stored which cannot be found be the apps anyways.
[Android Head-Units] midmayzs:
Thank you very much! I'm afraid of the answer. It's a shame. I'm still on 5.1..1 with same problem. Lot of feature on the unit, many fancy dancy think, and who can able to do modding, writing scripts, programming, probably make the unit work. But implement normal WORKING Radio app ... it's insane, shame.

thank you your help, answer again!
[Android Head-Units] kampfschachtel:
HI,

i have a problem routing my joying, I am on 25may release.

Downloaded supersu from the github link and followed process in edit Q&A

E:\supersu\SuperSU>copy_install.bat 192.168.43.59

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

connected to 192.168.43.59:5555

adbd is already running as root

empty host name

287 KB/s (13788 bytes in 0.046s)

223 KB/s (14309 bytes in 0.062s)

39 KB/s (629 bytes in 0.015s)

355 KB/s (346536 bytes in 0.953s)

282 KB/s (104012 bytes in 0.359s)

435 KB/s (6327180 bytes in 14.201s)

414 KB/s (46416 bytes in 0.109s)

su: invalid uid/gid '-c'

su: invalid uid/gid '-c'

chmod: /data/supersu/install.sh: No such file or directory

/system/bin/sh: cd: /data/supersu: No such file or directory

Reboot your Head Unit NOW!

that is what happend. folder resources contain install.sh

can you help what is wrong...
[Android Head-Units] edit:
I installed the the original android settings.apk and renamed the modified joying settings.apk.

I can see my microSD cards just fine under the Storage&USB menu.

My advice is to take the cards and delete the old files and folders that were made by the previous unit in a computer before using them in the new unit... also check the cards for errors.
[Android Head-Units] surfer63:
Some users report this and others don't. I had it myself as well once.

In your copy_install.bat file you will find starting as of line 43

REM internal copy
win-adb\adb shell "su -c mkdir -p /data/supersu"
win-adb\adb shell "su -c cp /sdcard/supersu/* /data/supersu/"

Please change that to

REM internal copy
win-adb\adb shell "mkdir -p /data/supersu"
win-adb\adb shell "cp /sdcard/supersu/* /data/supersu/"

Andif that doesn't work please change it to

REM internal copy
win-adb\adb shell "su 0 mkdir -p /data/supersu"
win-adb\adb shell "su 0 cp /sdcard/supersu/* /data/supersu/"

The Android su command is or can be simpler than the linux su commandand in several versions. It seems that joying changed going from 5.1.1 to 6.0.1 and again somewhere going from 8 May to 12 May to 25 May.
[Android Head-Units] midmayzs:
Thank you, and sorry for my misunderstanding! I'm very sad, because I don't see any chance to changing this. Thank you your help!
[Android Head-Units] kampfschachtel:
the first change worked. Thank you so much for the great support.

install andoid settings right away but still under app setting and then storage still no sd card menu....

but sd card is shown in the file manager and works...
[Android Head-Units] CoMeRtOsE420:
Rooting

Is there a step by step procedure in for rooting the 6.0 updated units?

I see you have to enter and change code but where does all this take place?
[Android Head-Units] edit:
You can use [MENTION=2550900]surfer63[/MENTION] tool

https://xdaforums.com/android-auto/android-head-units/joying-extra-tools-apk-apk-to-help-t3628200

Or read my Q&A

https://xdaforums.com/android-auto/android-head-units/intel-sofia-to-micro-tutorials-qa-t3616074
[Android Head-Units] CoMeRtOsE420:
awesome thanks

---------- Post added at 03:19 PM ---------- Previous post was at 02:43 PM ----------

im getting a system cant find path error
[Android Head-Units] surfer63:
No, you don't have to change code. I already updated the zip.

[MENTION=309187]edit[/MENTION] put in his Q&A thread a short howto. See point 11.

Edit: I took too long to answer :)
[Android Head-Units] CoMeRtOsE420:
Got It!!!

Successfully rooted using this procedure.

https://xdaforums.com/android-auto/android-head-units/how-to-root-joying-devices-t3614933

Thanks for all your help and answering my questions.
[Android Head-Units] Cartel™:
Do we still have to enable adb over tcpip first?
[Android Head-Units] edit:
Yes!
[Android Head-Units] usa911g:
I have update ROM 20170525 but the "Auto Navi" item is gone

did someone occur the same problem?
[Android Head-Units] brian8179:
I recently upgraded to 6.0.1 Now, I am having more bt calling issues. If I make a bluetooth call when google maps is navigating, the caller on the receiver end hears a terrible noise. If I close maps, and make the call again, the reception is normal. Is anyone else having issues running maps and making a bluetooth call at the same time?

Edit - it appears the Google app is causing the problem. I disabled ok Google from any screen and within google maps, and it resolved the issue. Is there a fix for this incompatibility?
[Android Head-Units] edit:
Did a lot of searching for you and come up with the solution to your problem :

https://xdaforums.com/showpost.php?p=72539997&postcount=15
[Android Head-Units] nosidefcp:
anyone can share the launcher apk?
[Android Head-Units] edit:
No, unfortunately. And with Joying not releasing a new firmware for quite a while I don't see any solution on the horizon.

Besides that we don't have many skilled users working to get this unit better... so it is what it is.

There are times when I am thankful that we had a few working on the unit at all or else it would have been really bad for me how it comes out of the box (without root, viper, nokill, custom keys, bt tethering, custom radio skins)

I have given up on Google app because it gave me plenty of headaches and weird HU behaviour on several ocasions.... On the android 5 it worked fine.

Joying never supported Google app officially... you can try to write them though... maybe if more are asking for this it could make a difference in the future....
[Android Head-Units] CadillacMike:
there is a new update out today, although it has the July 7th date, it supposedly fixes the Google app issue. Update is here:

https://www.carjoying.com/blog/joying-head-unit-after-sale-support/59.html

I dont know what #2 means, I assume to do a reset?
[Android Head-Units] nosidefcp:
Anyone can share the launcher apk?
[Android Head-Units] surfer63:
#deleted#
[Android Head-Units] kampfschachtel:
as always does update wipe the unit? And I can't see anymore files for 5009 and 6021 unit...

I already dislike better hate the 6 already after forced to deal with it since 10 days due to a new replacement unit, so many thinks don't work like before or not at all then with 5:

- SD card mess: in 5 you can manage your SD in the settings/ storage and worked fine. In 6 menu is totally gone and I can't manage the SD (eg erase/format/how much memory used) anymore, additionally spotify shows me 4 SD cards, ES explorer 3 and file manager 1 and I have only 1 installed....I just have my workshop PC with SD card slot so I always need to use this one now. what a crap....is there any app I can simply mange the SD card to delete, format it new and see how much memory left: tried a lot apps but non worked or hell of a complex....

6 has a new SD card management but joying developers didn't care about this at all....

- DVR not working in 6, worked in 5

- bootanimation change, doesn't work like in 5....only possibility is to replace it on your USB stick within the upgrade release before installing it, that works

- viper4android: with Android 6 crackles and other artifacts when Viper master is on with USB DAC, works seamlessly with 5

- DAB+ app (original and realzoulou): with 5 no probs with 6 crackles and interrupt as soon as something else is running in parallel. Realzoulou's is much better but still sometimes

- boot time 3sek longer with 6 compared to 5 (I have a faster 6021 unit now...)

- BT pairing: with 6 it dosen't work to connect my carly OBD2 dongle and other BT stuff, used with 5 just the autopair app and worked like charm but it doesn't work with 6 anymore...

- Wifi tethering with phone: no interrupts with 5, with 6 lots with Xiia Live pro

and I have now a faster 6021 unit...

that is a huge downgrade from 5 to 6 for no additional feature at all compared to 5...what a Sugar Honey Ice Tea. Thank you Joying....

I was even so pissed that I risked to brick the motherboard of my new unit and tried to downgrade to 5 by replacing the in the 28thmay 5 release the zip with 60.zip file as edit suggested. Didn't work, mcu upgrade runs through but then it interrupts the update with the "...package error". Reflash with normal 6 works...
[Android Head-Units] pounce:
Yea, pretty sure that means use a pokey thing to stick the rst reset button on the upper left.
[Android Head-Units] edit:
I am curious if the GPS stil works in 3.6km/h increments..... if you guys flash this new firmware please let me know.

Also I would like to know if Google App finally works... I miss entering an address by voice in Waze/Gmaps
[Android Head-Units] grahamwright1:
The update from 6.0.0 took almost 25 minutes for me, and worked smoothly with 3 reboots in the final stage.

File Manager now see's both the SD slots, so that bug is fixed.

The Storage tab in Settings only displays Internal SD storage and NOT SD1 or SD2 - new bug?

When Date & Time settings are left in Auto mode the current Timezone is GMT and I needed to set it manually to the correct timezone.

It wiped my IGO installation and I haven't figure out how to reinstall it correctly yet :(
[Android Head-Units] dyabolikarl:
Is a 3 second delay to change tracks via the steering wheel button a bug or is that normal. I started on 6.0.1 is all.
[Android Head-Units] surfer63:
No, that is an existing bug in the Joying 6.0.1 Settings apk. You need to install the standard full android stock Settings.apk to control that.

No it is not a bug. It can be improved slightly by adding the "shebang" at the top of the launcher script. It starts with

# V3.0 - 2/26/2017 - Example script for Joying 2GB Sofia

I changed that to

#!/system/bin/sh

# V3.0 - 2/26/2017 - Simple Example script for Joying 2GB Sofia

This makes it slighly faster (approx 1 second) as the system does not have to check first whether "this executable" really is a shell script.

Next to that I removed all unused stuff as it makes the loading of the script slightly faster as well, but that should be in the range of milliseconds and is actually not worth the effort.

I wanted to discuss this with [MENTION=3076686]gustden[/MENTION], but I'm so busy right now I forgot.

Edit: the " 3 second delay to change tracks" is not only for changing tracks but in any action via the launcher.sh script.
[Android Head-Units] hipkid:
I'm assuming AF issue was not solved yet :( :(
[Android Head-Units] surfer63:
No, I did a differential check and only the following apks have been changed. It doesn't say anything about what has changed though. It could also be a typo correction in a string.

But anyway, the radio apk has not been changed and neither has the underlying CarRadio apk.

Binary files 20170707/Allap/EasyConnectedFY07.apk and 20170525/Allapp/EasyConnectedFY07.apk are different
Binary files 20170707/Allap/JY-1-C9-BT-V1.0.apk and 20170525/Allapp/JY-1-C9-BT-V1.0.apk are different
Binary files 20170707/Allap/JY-1-C9-Launcher-V1.0.apk and 20170525/Allapp/JY-1-C9-Launcher-V1.0.apk are different
Binary files 20170707/Allap/JY-2-C9-EQ-V1.0.apk and 20170525/Allapp/JY-2-C9-EQ-V1.0.apk are different
Binary files 20170707/Allap/JY-2-C9-Launcher-V1.0.apk and 20170525/Allapp/JY-2-C9-Launcher-V1.0.apk are different
Binary files 20170707/Allap/JY-3-C9-Launcher-V1.0.apk and 20170525/Allapp/JY-3-C9-Launcher-V1.0.apk are different
Binary files 20170707/Allap/PlatformServerSofia.apk and 20170525/Allapp/PlatformServerSofia.apk are different
Binary files 20170707/Allap/Settings.apk and 20170525/Allapp/Settings.apk are different
Binary files 20170707/Allap/Sofia-1-C9-Gallery-V1.0.apk and 20170525/Allapp/Sofia-1-C9-Gallery-V1.0.apk are different
Binary files 20170707/Allap/Sofia-1-C9-Server-V1.0.apk and 20170525/Allapp/Sofia-1-C9-Server-V1.0.apk are different
Binary files 20170707/Allap/Sofia-1-C9-TV-V1.0.apk and 20170525/Allapp/Sofia-1-C9-TV-V1.0.apk are different
Binary files 20170707/Allap/Sofia-2-C9-DVD-V1.0.apk and 20170525/Allapp/Sofia-2-C9-DVD-V1.0.apk are different
Binary files 20170707/Allap/SystemUI.apk and 20170525/Allapp/SystemUI.apk are different
Binary files 20170707/Allap/SYU-1-5009-FloatBtn-V1.0.apk and 20170525/Allapp/SYU-1-5009-FloatBtn-V1.0.apk are different
Binary files 20170707/Allap/SYU-1-C5009-DVR-V1.0.apk and 20170525/Allapp/SYU-1-C5009-DVR-V1.0.apk are different
Binary files 20170707/Allap/SYU-1-C9-Calculator-V1.0.apk and 20170525/Allapp/SYU-1-C9-Calculator-V1.0.apk are different
Binary files 20170707/Allap/SYU-1-C9-Canbus-V1.0.apk and 20170525/Allapp/SYU-1-C9-Canbus-V1.0.apk are different
Binary files 20170707/Allap/SYU-1-C9-CarMark-V1.0.apk and 20170525/Allapp/SYU-1-C9-CarMark-V1.0.apk are different
Binary files 20170707/Allap/SYU-1-C9-CarUi-V1.0.apk and 20170525/Allapp/SYU-1-C9-CarUi-V1.0.apk are different
Binary files 20170707/Allap/SYU-1-C9-Graphics-V1.0.apk and 20170525/Allapp/SYU-1-C9-Graphics-V1.0.apk are different
Binary files 20170707/Allap/SYU-1-C9-UIServer-V1.0.apk and 20170525/Allapp/SYU-1-C9-UIServer-V1.0.apk are different
Binary files 20170707/Allap/SYU-1-FileManager-V1.0.apk and 20170525/Allapp/SYU-1-FileManager-V1.0.apk are different
Binary files 20170707/Allap/SYU-2-C9-CMSettings-V1.0.apk and 20170525/Allapp/SYU-2-C9-CMSettings-V1.0.apk are different
[Android Head-Units] kampfschachtel:
no this is not fixed on my unit...28th may release 6.01 and 6021 unit from factory no upgrade done but reflashed it once to make sure right stuff is on.

Did this with your joying extra soft and full android stock settings doesn't restore the SD card in settings/storage on my unit

Additionally I have one SD card slot with one SD Card but

- Spotify shows 4 identical SD cards to choose where to put the downloaded music

- ES Explorer shows 2 different SD cards but both have the same content

- file manager shows one which is working

what a mess....

I am also fed up with redownloading 20GB music in spotify and 3 GB offline maps in google when I reinstall or upgrade the unit, is there a way spotify and google maps is finding this data on the SD card after reinstall/upgrade?

The new 7th july update is confirmed by joying not to have a seperate update package for 5009 and 6021 unit anymore...

Really tempted to put the new update on quick, as 28th is a crappy buggy update but curious if all the mods still work.
[Android Head-Units] dyabolikarl:
Ahh awesome thanks for that i'll change it. I e-mail joying about it too before I saw this. But lets see how it goes :)
[Android Head-Units] edit:
I am just going to leave this here :

I did some testing because I noticed that the bluetooth speed is a lot lower on Android 6 for some unknown reason:

Unit A - 5009 SoM android 5.0.1 - Bluetooth speed varies around 280-400k with peaks to 560k

Unit B - 6021 SoM Android 6.01 - Bluetooth speed varies around 180-280k with peaks to 350k
[Android Head-Units] dyabolikarl:
This really makes sense I am having all sorts of bluetooth speed issues on 6.0. Sometimes it's ok sometimes it's really slow.

How would we test this and how could we fix this?
[Android Head-Units] hammer_gaidin:
USB Debug

Hello Guys,

I've read through most of this thread, and am having issues connecting to the unit via USB. I noticed the change for the 5555 port. Is everyone just using adb via wifi/network and not USB? Or if you are doing USB, how are you getting the machine to find the unit?

I must have missed something as my head unit isnt even recognized when plugged in.

Thanks,

Hammer
[Android Head-Units] edit:
I tried to test both units with the SpeedTest app (from Google Store) but it does not work corectly... don't ask me why... it barely

So I used a not so great method but it was the best I could come up with : I used Deezer app, set the unit to download HQ (big files) music and monitored the speed from my phone because it is capable of telling you the speed you are downloading from the network.

In fact I noticed that after the update (from android 5 to 6) that the Deezer app takes longer to download/play large files... so fast skipping from one song to the other resulted in longer wait times before the song could be downloaded and played.

Now that I have access to 2 units decided to test both, same app, same location, same phone, same network. Did several tests on each unit to round the numbers and see what was the average/range..... so on.

The difference is clear... on the old Android 5 the bluetooth data transfer was AT LEAST 50% faster.... sad

All these years, of all the Chinese manufacturers, they come up with an unit that has a good BT hardware implementation, android has full access to the chip for the first time, and they decide to ruin it badly with through software instead of building on it, advertise it, take advantage of the feature that no one has..... so, so, stupid.

About fixing it, I don't think there is a solution, but I don't have the skills to tell you anything for sure... unfortunately to be able to fix this we need people with high android skills buying the unit and start working on the problems after they got bothered by them... As I said a few threads back, I am grateful that we had a few that helped us so far... but it is what it is and I think this is the best it can get
[Android Head-Units] shanetrainST:
These are very recent email I received from Joying regarding the BT, I don't think they will fix it, not unless lots of people complain.

Nice day

I have tried my best to contact our factory, but i am sorry this is not a good news for you, we do not get the latest Bluetooth drivers

Nice day

Mandy

Thanks for your support, but i am sorry still we do not have any new firmware and latest improvement for the Bluetooth issue in your Bluetooth apk and your Bluetooth device

Hope you do not mind

Mandy

Sorry for the delay reply, but i am afraid we really can not help you with that Bluetooth issue

Best regards

Mandy
[Android Head-Units] avnb39:
Anyone else having with the launcher settings? I'm trying to change back to the old style, but the new launcher is the only one there in the menu.
[Android Head-Units] dyabolikarl:
I fully regret leaving my java software cert for network engineering now
[Android Head-Units] salias:
Manage to upgrade from Android 5.1.1. to 6.0.1 today.

While listening radio, i cannot hear voice for waze and google map (running at background) but my radio volume turn low and increase again after navigation voice end. When closed the radio, i can hear both navigation voice.

Is'it normal? When the radio not active i can hear both voice without any problem.

2nd finding while in radio interface, press back button will close the radio and goes to main screen. Previously i can still hear radio even press back button.

Not sure this is normal??
[Android Head-Units] surfer63:
It is either/or. You either have adb over WiFi enabled, or you have adb over usb enabled. You can't have both.

If you disable adb over WiFi, adb over USB is re-enabled.

(If you don't know how to do that, use my apk).

Next time be more specific: which android version are you on? And did you try to enable adb over wifi: "I noticed .." doesn't say what you did.

All versions so far, also the new 7 July version, come with 3 launchers. Which menu are you referring to? It is in the settings where you can switch the launcher.

---------- Post added at 08:40 AM ---------- Previous post was at 08:33 AM ----------

If it is really "only" about the drivers, we should try to find the latest X86 bluetooth drivers. With a rooted unit it is easy enough to replace the existing drivers.

The problem here is that we really don't know whether Mandy knows what she is talking about. Is it now a bug (in the apk) or does it have to do with a bug in the drivers which is solved with newer driver versions?
[Android Head-Units] avnb39:
I'm referring to the leftmost menu in the car settings app, very bottom option to change the launcher. Launcher4 is the only option present for me. I upgraded from 5.1.1, if that matters any, and I didn't do any of that weird stuff with pressing RST after the upgrade.
[Android Head-Units] shanetrainST:
Yea I mentioned to Mandy about the drivers and kernel and also what BT stack they use.

Mandy was unable to answer any of those questions.... standard for Joying and was assured they work... :/

I also asked her if she could ask FYT if they could provide uncrippled Bluetooth driver/kernel and was told it was not possible.

From what I understand Joying don't get much creative control over the system and they only get to develop their apps, eg. The BT app.

If there is a way to replace the Bluetooth driver/stack/kernel configs I am all up for trying it.

I did try to replace some of my Bluetooth files from that I copied out of a X86 PC version of android 6.0 but it didn't like it one bit and crashed the BT.

I replaced the Libbluetooth_Jni file in two locations and it didn't fix anything.

I also replace the Bluetooth.apk app but I think that only takes care of BT sharing, but funny enough when I completely removed it my whole BT crashed so it might be doing something??

I really do hope u give the driver replace a try and I will be will to test it on my unit if u do
[Android Head-Units] surfer63:
No, that menu option does nothing.

It is the bottom right menu option (the "toolset"). pin 3368.

Somewhere at the bottom of that menu you find the launcher selection.