yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] vinhZ:
I think it is an os issue in version 5-6. Google took away reading and writing directly to usb devices. In 6 google compromised and gave us adoptable storage, http://www.androidcentral.com/adoptable-storage , adoptable storage is a compromise , since the adopted usb drive won't work outside of your google device.

---------- Post added at 11:03 PM ---------- Previous post was at 10:56 PM ----------

There is a setting in carsetting that allows you to choose a navigation app. This will enable voice prompts in said app.
[Android Head-Units] faisdogg:
Is it available as an apk for easy installation, I'm not an expert in android development

---------- Post added at 05:38 AM ---------- Previous post was at 05:13 AM ----------

That doesn't work for me. Works fine with local music, but it doesn't work with radio and Bluetooth music. I can hear it lowering the volume but no prompts are heard. It only started happening after android 6 update
[Android Head-Units] edit:
After a lot of testing I found out a combination of settings that prevents the XiiaLive Pro to shutdown the unit when you turn off the engine:

1. Settings -> Stream ->Stream Engine -> switch from the default FFmpeg to Android

2. Settings -> Stream -> Unlimited retries must be OFF
[Android Head-Units] KlaverBoer:
I have the same issue (see #214 ) just like everyone else who installed the 6.0 firmware i think. I have reported it back to Joying Support. Maybe you should do that to. Hope that they will fix it in a future release. For the time being i'm using Waze. That works fine in combination with the FM Tuner.
[Android Head-Units] sanangel:
Any fellow forum that is from Russia?
[Android Head-Units] vinhZ:
Confirmed, I've rarely use my FM radio. There is no voice feed back from google maps when the FM radio is in use.
[Android Head-Units] gtxaspec:
Velvet.apk seems to be one of the culprits that causes shutdowns... :( :(
[Android Head-Units] surfer63:
This is an old issue and still on the 6.0 as well. you need one of the modded SofiaServer apks. All of them come with the "nav_app.txt" patch.
[Android Head-Units] psxsnake:
I don't have this problem using TomTom and Radio... is correctly mixed
[Android Head-Units] sanangel:
TomTom Go works for you after starting Joying? In my case it does not open and it works, it stays loading ...
[Android Head-Units] psxsnake:
you can see
[Android Head-Units] KlaverBoer:
I already installed the modified sofia server apk. But it doesn't solve the problem for Google Maps/Radio.
[Android Head-Units] sweetnothings:
i have this problem too on android 6 (even with v6 of gustdens noKill installed)

sound of radio gets lowered while gmaps should output sound, but gmaps sound dousnt get mixed in.
[Android Head-Units] gustden:
The modded SofiaServer apk doesn't fix it for me. Seems to be a diffferent issue on 6.0.
[Android Head-Units] surfer63:
Let's hope it is due to the beta version and not some new Joying improvement built in. :rolleyes:
[Android Head-Units] sweetnothings:
thinking the same, lets all submit this bug to joying so they can look on that bug.

did someone check this issue is with original sofiaserver as well? just to be sure
[Android Head-Units] mancavetoyz:
need help

I have the (Joying) JY-JL001N2 Intel Jeep Specific unit with 5.1.1 on it. THere are some things that I want to get but need info on getting files and how to setup correctly. Let me know if these things can be accomplished in 5.1.1 or do i need to switch to 6.0

1) the built in equalizer is crap. not enough control on just three bands.

2) want to install Viper4android to get better sound.

3) do i need to root, if so how do you do it correctly.

4) want split screen.

5) 4.4 had RDS working on the redio presets..5.1.1 on this unit doesnt.

6) a good launcher. I really mis the system in my F-150.

7) cant get the damn system to stop muting or pausing when my phone gets a notification...allways muted Rocket player, spotify and just about everything else.

Thats a pretty good list..I wont add more till later. Any help would be greatly appreciated.
[Android Head-Units] gtxaspec:
Unchecked media audio in your phones Bluetooth settings, under the Joying unit's entry. , that will fix the muting and pausing.
[Android Head-Units] mancavetoyz:
isnt listed. it only shows the following.

Sync Contacts

Phone Favorites

Phone Recents

All Contacts

I have a Iphone 6S
[Android Head-Units] naplesbill:
With an iPhone you have to use an app to disable media control on bluetooth. I don't know the app name though.
[Android Head-Units] bigsteve01:
New update on joying website

[youtube]ppRlTR9YV0U[/youtube]
[Android Head-Units] mancavetoyz:
anyone try this update yet?
[Android Head-Units] CadillacMike:
on the YouTube page it says, "Newest android 6.0.1 upgrade firmware for the second update has fixed the Easy Connected, Bluetooth, DAB+, etc."

Although on the Joying Blog it just has the standard: "Optimize the head unit system and fix some bugs"
[Android Head-Units] mancavetoyz:
the screen was laggy as *$^%%# in the video after the update. Anyone else catch that.
[Android Head-Units] PsychoMcSatan:
I'm not too concerned seeing as this was first boot after an update.
[Android Head-Units] CadillacMike:
i did notice that, but i figured it was a one off, or that's a unit they have beat to crap from testing
[Android Head-Units] gustden:
The 6.0 -> 6.0 upgrade did not wipe all my apps. Unit was very unstable at first, I was able to get into the settings and did a master data reset ( wiped all apps ). Seems to be working better now.

Enabled ADB, rooted, and now restoring all my apps and data via Titanium.
[Android Head-Units] mancavetoyz:
can someone give me instructions to root after installing 6.0.

also, what is ADB? do i need to enable it? if so, how do I enable it?

how do you use split screen?
[Android Head-Units] mancavetoyz:
ok, so i should just be able to install viper4android with no problem since it is allready rooted?

just curious to see the split screen. main reason i upgraded.
[Android Head-Units] gustden:
Just an update on the May 8th ROM.

Notes:

- ADB was not enabled by default, had to set port to 5555 on the unit to connect via adb. ( same as last rom )

- The voice from google maps still does not work when playing the FM radio. It does lower the volume, but no voice is heard. ( same as last rom )

- I installed the settings from the 5009_60 package to get the stock android bluetooth settings to work. ( same as last rom )

- Bluetooth seems to be working better. I was able to pair ODBII, TPMS, and my phone with tethering without any issues so far. I was able to make voice call over BT, where it was rebooting my unit previously.

- Overall it is working very smoothly, so far :good: ( Bluetooth was my big complaint with the 6.0 beta )
[Android Head-Units] edit:
Please tell us if the bluetooth problems that you experienced were solved with this new firmware.
[Android Head-Units] doctorman:
I hear you...

not sure if carjoying has the source code, perhaps the company who makes the board has it. and I have no idea who that is. yup.. sure contact all the sellers till it is released.
[Android Head-Units] gustden:
From the code, this is domain where the units "phone home" to. I'm guessing they sell the 5009 package to Joying.

http://www.carsql.com/series/complete.html
[Android Head-Units] gtxaspec:
I believe the designers of the head unit package are "fyt". That reference is found across all mtcb/c/d products. Then repackaged by other guys, in joyings case, it would be SYU, aka carsql.com.

I think.
[Android Head-Units] gtxaspec:
I actually had a colleague who speaks mandarin call SYU, asking for details on the software, they will only speak to you if you are a contract partner. But they are the software development house for the Joying unit, among others.

The FYT references are buried in the smali and randomly throughout various files in the firmware
[Android Head-Units] mancavetoyz:
so i installed the viper4android after updating the unit to 6.0. viper installed but failed to update drivers. it says the unit needed to be rooted. i thought 6.0 was rooted out of the box.
[Android Head-Units] gtxaspec:
Been stuck at work past few days. Will put the unit tonight to upgrade to latest ROM, I'll flash your boot.img before I do.
[Android Head-Units] vinhZ:
What do you mean by shutdowns??? Mine doesn't seem to ever go to sleep now since I've installed a modded car server.app

And even on the Original carserver/and no velvet it would coldboot in the mornings.
[Android Head-Units] gtxaspec:
On my install, I narrowed the problem to the velvet.apk(the one that was posted here that enabled ok Google anywhere) it would cause the unit to shut down instead of sleep with the nokill server apk.

Apparently the nokill code is there by design, to prevent the unit from shutting down instead of going to sleep due to certain apps not playing well with the hardware somehow
[Android Head-Units] mancavetoyz:
00

I installed viper from the link in the roll up for this thread. installed but said it needed to be rooted to update the drivers.
[Android Head-Units] gtxaspec:
You are right;

Because, if you install 5009_60.zip with an empty Allapp.pkg, what I mean,if you install the firmware with none of the custom apk's for the device, after 5 minutes or so the unit shuts down. So somewhere one of the sofia apks is probably keeping the unit awake.
[Android Head-Units] gtxaspec:
Off topic, if your boot.img patch works, how feasible do you think it would be to patch the recovery image, to change the signature keys file:

'Recovery checks the signature against public keys stored in the recovery partition RAM disk, in the file / res / keys '

My goal is to build a custom rom, bypass joying for most of the OS.

---------- Post added at 07:58 PM ---------- Previous post was at 07:51 PM ----------

Yes, in my testing the unit would always shutdown after a short while no matter what.
[Android Head-Units] gtxaspec:
There are other devices including tablets which use the sofia platform, like the telecast x98 tablet. I remember reading some kernel sources are available for those. Might be worth a look.
[Android Head-Units] gtxaspec:
Hmm, isn't the mcu exposed as a tty? I think the sofia app's just read and write through this.

I wish we could figure out how to flash the Joying through USB, then we would use the Intel flash tools to pull and then write back to the various partitions, which is what the telecast guys are doing with recovery... Argh. I mean I don't mind blind flashing to mmcblkp... But it could be easier...
[Android Head-Units] gtxaspec:
I "bricked" my unit by flashing my own incorrectly packed recovery image. Luckily, these things have the hypervisor , so long as the recovery or boot partition is working, it will repeatedly try to boot off either of those. So I was able to boot normally and re flash the stock recovery, so I feel semi brave enough to take the risk to flash a test recovery Lol. Just don't flash both at the same time.
[Android Head-Units] gtxaspec:
Omg. Must. Modify. Recovery. To. Enable. Custom. Rom!! No sleep for me tonight.
[Android Head-Units] Hilari0:
(SOFIA 3GR) 1.Intel4 core CPU, 4 core GPUmali450. AtomX86 architecture, clocked at 1.2G; Andrews version 5.1; 2 built-in 2G / 3G Internet, wireless WIFI connection, standard intelligent voice voice; 5009 / 16G / 0.KNB 3, support GPS and GLONASS dual mode navigation; BLSCSJOO57 4, built GPS module / power / Bluetooth 4.0 / WIFI / audio and video processing; 5, support dual MIC voice recognition higher; 6, support video multi-coal 1080P, USB video 1080P; 7. Support collision sensor, remote monitoring, real navigation, track Playback, rear view; 8. Support cloud dog, electronic dog; 9, support all software online upgrade; 10 can support LVDS. MIPI interface, 5.7.36.8,8.8, and other multi-resolution display; 11 core board and FYT5000 series full compatibility, platform switching easier; 12 car standard, low temperature -30 degrees / high temperature +75 degrees.

Google translate on Android can do pictures, but not so helpful...

But, does this mean if we blew up a coreboard, we could just buy one of those 5009 modules and chug it in and get it working again? Not sure if joying sells them as replacement. Wonder if the other modules are compatible as well.
[Android Head-Units] Survivalism:
Super exciting, thanks to you and doitright for pushing the envelope on these head units.
[Android Head-Units] doctorman:
MAY 8 2017 UPDATE RELEASED

Bluetooth Fixed

BUG FIX for Android 6

https://www.carjoying.com/Joying-blog/59.html
[Android Head-Units] gtxaspec:
new_boot.img doesn't boot. i suspect because the image is smaller than the original one.

-rw-rw---- root sdcard_rw 16777216 2017-05-10 20:29 boot.img
-rw-rw---- root sdcard_rw 13783040 2017-05-10 20:24 new_boot.img

Also, I have the recovery image, http://mirrors.gtxlabs.com/joying/recovery.img

your command line for mkbootimg doesn't specify the second loader, how did you leave that out and get the same size file?

Edit:

Hmm looking at recovery.img vs my re packed version, it seems there is another loader that wasnt extracted, because there is a file size different, about 11MB vs 16MB original. looking at the original with a hex editor, my repacked ends at about 00b61de000, and the original has additional content start at 00b61fed00, maybe another loader?
[Android Head-Units] gtxaspec:
I used your boot image off your github repo.

---------- Post added at 07:03 PM ---------- Previous post was at 07:02 PM ----------

Hmm, interesting. Time for take two.
[Android Head-Units] dayanandgp:
Hi All, I have a very annoying problem. Every time the unit is turned on(from sleep), my 128 gb usb drive is "initialized" or it says "external storage device being installed".. Due to this my poweramp doesn't resume the music automatically. I am getting very frustrated due to this as the usb drive is visible after 2 seconds. Is anybody else facing this? Resetting dirty bit is no solving the issue..
[Android Head-Units] gtxaspec:
Sure, I'll try that tonight.

---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------

Also, Any luck with the kernel sources from the Asus?
[Android Head-Units] gtxaspec:
Hmm, most of the drivers seem to be available for the hardware I've dug through on the device and through the logs. Hopefully we can get the boot.img process working and then see if I can't get a kernel compiled to test! I'm tempted to open the unit to see if there is a jtag easily accessible for further research. I've been following the guys on 4pda.ru, and they were able to flash from the pc using Fastboot by shorting some pins on the usb controller the mcu from another brand Intel sofia unit (not joying, unit was not using FYT 5009 SoM) and then using the Intel flash tools. Downside to our joying unit is that everything is on the SoM, there is very little on the mcu board itself.

Some of the Joying units have a mini 5 pin USB on the front panel, my unit doesn't. I wonder what that is used for...? And what happens when you plug that port into the pc...

I also recently contacted one of the sofia Linux kernel project leads at Intel, hopefully he can shed more light on the platform for us.
[Android Head-Units] knuchel:
Custom Boot Logo Update

Hi,

I did update to 6.01 Beta - unfortunately I cannot find a way to update the boot logo with a custom picture. Anyone managed to make this work?

Thx
[Android Head-Units] windowsdan4216:
Has anyone installed the recent 6 update??

It's a disaster for me, everytime the HU reboots it optimises all the apps and wipes everything to fresh install again!?!! :crying:

How can I fix this rediculousness? Any ideas?
[Android Head-Units] gustden:
I had the same issue. If you can get into the settings do a master reset / clear data of the unit. After the master reset, mine booted normally.
[Android Head-Units] gtxaspec:
<blank>
[Android Head-Units] sanangel:
If you are root, you can replace the logo.png with a custom one with a file manager as root Explorer
[Android Head-Units] wanb1i:
I tried this script and the script seems to work, but the settings don't work at all? Is this for the Marshmallow release?

With this installed I have no settings at all! So I put back the previous settings.apk and now have the stock Joying settings back.

Should I also remove the Oat folder, etc that wasn't there before?

Every time the system reboots it optimizes the apps (4 apps to be precise), not sure what they are, but it started after I used your setting script.

Does anyone have a Marshmallow Full settings apk that works on the 6.0 update?
[Android Head-Units] windowsdan4216:
Thank you for this. Worked a treat!

Do you know if the last No Kill Sofia apk works with this latest May release?
[Android Head-Units] knuchel:
Screen Dimming

Under 6.0.1, my screen dimming is not going dark enough (I changed in general Android Setting and the Car Settings lowered the lower band). Still the light is too bright at night. Any suggestions to lower brightness automatically?
[Android Head-Units] gtxaspec:
]

Working on it, we need to be able to modify the recovery image and write it back to the device. The problem is the structure of the image is non standard. If you scroll up [MENTION=8255813]doitright6[/MENTION] and I are trying to figure out how to properly repack it. Feel free to help out, I don't mind being the Guinea pig to test anything on my unit.
[Android Head-Units] gustden:
I just added updates for the latest Joying ROM dated 5/8/2017 to the key mod thread.

https://xdaforums.com/android-auto/android-head-units/joying-2gb-steering-wheel-key-t3543390

There are 3 separate files depending on what you want. I had issues with the music player advancing with the no kill patch, so I added a "pause" on sleep to the nokill code.

It is working real good on my unit with the latest ROM. All include additional navigation apps listed in the navi_app.txt file within the apk. Google maps voice is not working when listening to radio, it is unrelated to this mod and has been reported to Joying.

V6.1-Sofia-1-C9-Server_NOKILL.zip - Original file with task killer removed, pauses music before sleep, .

V6.1-Sofia-1-C9-Server_NOKILL_GVS.zip - Task killer removed, Google Voice Search on 'SRC' key, pauses music before sleep.

V6.1-Custom_Keys-Mods.zip - Complete key modifications ( requires launcher.sh )
[Android Head-Units] :
Thread re-opened. Let's stick to the topic at hand folks. :good:

Any concerns with a Moderators action should be pm'd to the moderator. But know that we don't discuss issues with members with 3rd parties. That's private, right? :)

Cheers,

Darth

Senior Moderator
[Android Head-Units] Skater4599:
Has anyone tried the original 5.1 hi on this update? I don't like the new ui, it's the main reason preventing me from updating. Otherwise I'd love to update for TomTom go Support
[Android Head-Units] shanetrainST:
Looks like the May 12 Joying Beta firmware beta is out on their blog.

Appears to be a May 12 MCU also?
[Android Head-Units] CamryGuy:
They have added a subwoofer eq finally. Wanted to add some low mids to the woofer channel.

Edit: Damn! Its just a sub volume, not an eq at all.
[Android Head-Units] gtxaspec:
Need some help reverse engineering on the unit. We were disrupted by bad moderation earlier.

1. Custom Recovery Partition

I. This will allow us to flash our own 5009_60.zip file. The goal is to replace the file in /res/keys ( these are signature keys, the recovery binary compares the signature of the 5009_60.zip file and checks to see if the signature matches the keys, if it doesn't it won't allow the file to flash )

II. The problem we are having is the recovery.img structure is non standard, when we rebuild the image file, the one that mkbootimg spits out will not boot on the unit. See https://github.com/lbdroid/JoyingIntelStuff/issues/2 Please post any replies there, as this board is not able to provide a proper "forum" for us to discuss this.

2. fwu_image.bin (inside every 5009_60.zip, this is how the recovery gets updated, as in 5.1.1 to 6.0.1 )

I. We extract the file contents using https://github.com/InvisiBot/fwu-shredder .

Ii. This file includes :

-rw-rw-r-- 1 aag aag 14320936 May 12 23:44 boot.bin
-rw-rw-r-- 1 aag aag 1019384 May 12 23:44 mobilevisor.bin
-rw-rw-r-- 1 aag aag 42902 May 12 23:44 mvconfig_smp.bin
-rw-rw-r-- 1 aag aag 114492 May 12 23:44 psi_flash.bin
-rw-rw-r-- 1 aag aag 11937064 May 12 23:44 recovery.bin
-rw-rw-r-- 1 aag aag 603144 May 12 23:44 secvm.bin
-rw-rw-r-- 1 aag aag 1020824 May 12 23:44 slb.bin
-rw-rw-r-- 1 aag aag 2666496 May 12 23:44 splash_img.bin
-rw-rw-r-- 1 aag aag 7168 May 12 23:44 ucode_patch.bin
-rw-rw-r-- 1 aag aag 131072 May 12 23:44 vrl.bin

Now these files are typically used by Intel's Flash Tools. Normally you could flash these via USB in Windows, or using Fastboot using USB. On our unit's we are unable to access the device using USB to PC. So, the next step is to find out how update-binary processes a section within updater-script, here we see that the script extracts the file and sticks it on partition 122.

package_extract_file("fwu_image.bin", "/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID122");

then

intel_install_firmware_update("fwu_image.bin", "/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID122");

So, if we are able to modify recovery.bin, repack it into fwu_image.bin, and flash fwu_image.bin to partition 122, will this be enough? Will the mobilvisor take over, or is "intel_install_firmware_update" a special command sent somewhere to tell the mobilvisor to actually flash it?

Need to decompile and analyze update-binary!

We blow these open, and every SoFIA device becomes accessible, thus custom recoveries and CUSTOM ROM's will be possible.
[Android Head-Units] shanetrainST:
Anyone have any ideas on why I keep getting disconnects/reconnects on my Bluetooth device on my Joying 6.0 Headunit?

Bellow is the main errors I see in my HCIsnoop.log when it drops connection from my App to my BT Device

fc:66:d7:53:d4:83 () 2:22:85:2d:f8:7b (JY-Android)	ATT	14	Rcvd Error Response - Attribute Not Found, Handle: 0x0001, Handle: 0x0001 (Generic Access Profile)

fc:66:d7:53:d4:83 ()	22:22:85:2d:f8:7b (JY-Android)	ATT	14	Rcvd Error Response - Attribute Not Found, Handle: 0x0007, Handle: 0x0007 (Generic Access Profile: Peripheral Preferred Connection Parameters)
[Android Head-Units] p33t-r:
Did they fix the issue with Google Maps (and Google TTS overall) voice prompts/instructions while listening to FM radio?

I regret updating to 6.0 because of that issue.

I have other app that uses Google TTS and there is an option inside the app to change the voice channel of the TTS prompts. With Music or System channel enabled - TTS doesn't speak. On Notifications channel it works fine with FM radio. Sadly, there is no option in GMaps to change the audio channel...
[Android Head-Units] gustden:
I did notify Joying of this bug on the first 6.0 release. Here is their response:

Check the following options in the car settings:

Navi App: Google Maps

GPS Mix: On

Auto Navi: Off

If the problem still, hope you can show me in a video how do you set all this option as requirement and how the radio running and google map do not have sound.

Hopefully they fixed it in the May 12 update, but I'm not going to bother loading it to find out. This is really the only issue I am having with the May 8 release.
[Android Head-Units] wt93205:
Updated to the May 12th and the radio issue is still there. Also now if you install the Google app for the "ok google" you can no longer get to the home screen or any apps. Basically it freezes. Uninstall the google app and then you can use the unit again but now I have no "ok google" or voice with google maps with radio. At least they fixed the bluetooth and added a subwoofer control.
[Android Head-Units] :
Hi, do you remember the name of the app to disable media control on Bluetooth? I have an iPhone 6s and this has been driving me crazy! I have the Joying JY-JL001N2. I'm having the same issue as mancavetoyz

Thanks!!