yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] markmorto:
New material(-ish) design radio and Bluetooth/dialer mods

Here's a new radio mod and matching Bluetooth/phone mod in my attempt to have a more modern-looking system using the standard Joying colors. Some changes as compared to previous mods:

No frequency band on the radio - use the buttons (software or hardware if you have then) to navigate

Single-page navigation on the radio - no scrolling to find buttons

Dedicated matching settings buttons in both mods

I don't get the scrolling text on the channel buttons with RDS in my area, so I have to make a guess to line-up the text. if you have issues, please take a screenshot and I'll get them fixed.

Radio mod: https://drive.google.com/drive/folders/1cuQ8qig5bRWl0vb_jldHFpCm2ZcMhLKc?usp=sharing

BT/Phone mod: https://drive.google.com/drive/folders/1901REzN4X1UGNlhd6rbehEfYtAVPmeRg?usp=sharing

Note that the radio mod has a VW watermark behind the RDS text. This is configurable! You can remove it, or replace the image with a logo to match your car/truck.

To change this image:

Use 7-zip to extract the radio APK file.

In the res\drawable-nodpi-v4 folder, find the "radio_menu_bottom_bk.png" image. It should be a VW logo.

Either rename this image to something like "radio_menu_bottom_bk-orig.png" to make the logo disappear, or open the image and replace the logo with one to match your car/truck. You must keep the name the same.

Copy the updated image back into the APK file. If you renamed it to make it disapper, make sure the original image is removed from the APK.

Copy the updated APK file to your head unit, in the /system/app/JY-1-C9-Radio-V1.0 folder, replacing the one that's in there.
[Android Head-Units] alessondanilo:
Thanks, as soon as I get home I'll do it.

Could you let me know where the links to update are located?

There is already a time that I do not follow the forum and now I went to see the domains of joying (carjoying.com/blog/joying-head-unit-after-sale-support/59.html) is offline.
[Android Head-Units] markmorto:
Try here - https://www.joyingauto.com/blog/category/updated-files-released/
[Android Head-Units] alessondanilo:
I did this, removed the connection cable from the screen and replaced it. The screen came back with the picture, but now the touch does not work, the side buttons work, but the touch does not work. What can it be?
[Android Head-Units] markmorto:
There are a couple ribbon cables - did you try to reseat all of them? One connects to the display from the mainboard, and there's another that connects from the display to the display board. Try to reseat all of them and see if that helps. It's possible you could have a bad display if reseating the cables doesn't work.
[Android Head-Units] markmorto:
EasyConnect basically plays whatever is on your phone in a separate app window. The radio app is installed on your head unit. So they're both running at the same time in different locations, and the Android operating system allows you to display only one at the same time.

You could try to run one of the apps in a window but I don't know if it will work well. To do that, you need to install the default (not Joying) Settings application and enable widowed mode. Then you could (if it works) open the task manager and choose the window button for the EasyConnect or radio app.

Edit: I added some screenshots with the dual-window and the radio app. Note that the radio is a system app and doesn't scale like Maps and Power Amp do. I didn't design the new radio mod for dual window, but it sure works good.
[Android Head-Units] alessondanilo:
I already connected the cables and the touch still does not work, I can not get past this screen. What can it be?
[Android Head-Units] markmorto:
The system has a very out-of-whack number associated with the horizontal screen, although the vertical looks okay. That's showing there's definitely a problem.

I don't really know enough about how this works to be sure that it's not a hardware problem, but you could try to reflash the unit to see if fresh software solves the problem.

You might want to try Joying support - those numbers might mean something to them.
[Android Head-Units] gtxaspec:
Re flash, that odd number means the configuration file is corrupted for the initial display calibration.
[Android Head-Units] alessondanilo:
could you let me know the correct update link?
[Android Head-Units] surfer63:
Adroid 6 only basically supports split window. The SofiaServer models will probably never see Android 8 Oreo, but Joying is now working on the PX5 models with Oreo.

Android 8 supports out of the box window splitting, which means that you can simply put your navigation in the left half and your media player in the right half (or so).

If the Joying apps will not be adapted, and I'm afraid they will not, they will probably not seamlessly support this split window mode. Perhaps they will literally only display a half window. We will see.
[Android Head-Units] markmorto:
Interesting discovery with BT app leads to new functionality

I was playing around with my latest BT phone/music "material design" mod, basically just to make the "Call" and "End" buttons larger, and I discovered that there was a button that matched the same conventions as the rest named "bt_menuav".

So, I added it to the other menu items, and voila - the phone/BT app now opens the BT music player, and vice-versa. In other words, you don't need to open the phone app separately if you have the BT music playing.

I updated my Google Drive with the latest file: https://drive.google.com/open?id=1rnXLeO_XGmVhbi9n5zSPkSV9XJcvyd68

Check out the screenshots. The "Settings" icon on the BT music player brings you back to the phone app.
[Android Head-Units] pwood999:
Does the BT Dialler have a Mute button for outgoing audio ? I often do conference calls from the car, but cannot get any of the Joying diallers to mute the outgoing audio ? They seem to just dump the call.
[Android Head-Units] markmorto:
No mute button that I could find. There are three buttons on the dialer page, one (speaker) just switches the audio, where it either plays from the phone or through the head unit, and the other two disconnect/reconnect the phone to Bluetooth, so you can control if it plays through the car or not.
[Android Head-Units] karazz:
Hi all,

I'm having some trouble to determine my MCU version. The unit states jy_(_r76)__90_c9_7706_5009_CAN and the Joying website states:

MCU version is 9.20 or more later

or

MCU version is 5.25 or more earlier

Is my version 5009? So would it be version 5.25 or earlier? Or am I mistaken here?

Thanks in advance
[Android Head-Units] surfer63:
The MCU type is 5009. The Sofias come as 5009 or 6021 series.

Your MCU line is not complete. It should say something like MCU: 2017-10-25 19:20:05 JY_(_R76)__90_C9_7706_5009_CAN.

Or another date than the 2017-10-25 of course.

Please check again.

And in case of doubt, please contact Joying directly as nobody can see from your line what version you have.
[Android Head-Units] etrefal:
Nice mod, looks really good! I've tried it earlier today, and I noticed that on my unit the LOC and ST functions were reversed. Thought you'd like to know.

I'm back to your "blue circular" mod for the moment, it's also really good! I'll try to roll my own background image to replace the VW one, maybe it'll work.

The bluetooth mod you did is also very good. Somehow on the first execution my screen was filled with grey vertical lines and the unit rebooted. But after that episode it worked like a charm. I very much like the feature you added to get to the Bluetooth Music app!

Thanks!
[Android Head-Units] markmorto:
Glad you're enjoying them! I looked into the button issue and you're right - they were switched. But here's the funny part - I never modified those; just copied and pasted the content from the original radio app. Since I based all my mods off the original, they all have the ST/LOC bug. I'll get this fixed tomorrow in my mods and update my Google drive.

As far as the weird lines, that can happen sometimes, especially when applying mods that have a lot of graphical changes. Basically the level of modding for these apps is very simple. It's like updating the images and HTML on a Web page, and each time the app loads initially, it refreshes the content.
[Android Head-Units] etrefal:
Strange indeed, because I'm using the "blue circular" variant I installed from [MENTION=2550900]surfer63[/MENTION]'s JET, and the LOC and ST functions are mapped correctly - well, the corresponding indicators turn on and off when using the associated button. I didn't pay attention to what the radio was actually doing. I had noticed similar behavior with another variant a few months ago (from memory: Red Sanangel mod), the save and stereo buttons were reversed on the toolbar at the bottom, but the functions weren't. Maybe Joying is messing with the code in some rom updates?

I was a little worried when the grey lines appeared, but since everything worked normally after the reboot...

Thanks again!
[Android Head-Units] surfer63:
That is exactly the reason why the JET apk tells you to (soft) reboot: to prevent these kind of things. There is a pre-compiled, optimized version "on disk" and there can be remnants in memory.

This optimized dex version uses program parts that are used when starting up (to speed that up) and parts that are used very often.

Just do the soft reboot (as that is what JET does after asking), and the new apk will automatically be optimized. Otherwise the new apk will try to use parts from the optimized, precompiled old version.

(soft reboot: only restart the graphical environment

(hard reboot: "warm sitch off / switch on: completely restarts the unit.)
[Android Head-Units] etrefal:
I'm pretty sure I did a soft reboot when JET asked - I always do when I try radio mods, but maybe I didn't that particular time.
[Android Head-Units] markmorto:
There is a dependency between LOC and ST, at least that's the way it appears. Either you need ST for a successful LOC or vice versa. That's the way it seems anyways - if I lose LOC, I typically also lose ST in a bad reception area. I can confirm on my end that all my mods had these button functions reversed. I just uploaded updates for all of them.
[Android Head-Units] etrefal:
In typical applications, LOC is to tune only local stations - those whose signal is the best, and filter out the rest as interference. ST is to cancel stereo decoding, which is useful in fringe areas where stereo comes and goes. Normally (a keyword here) they should be independant, but who knows with this implementation! :)

Thanks
[Android Head-Units] Need4Camaro:
I'm in need of help.

I am trying to update to the most recent Android 6 Firmware from the Joying website however I am getting an error as attached in the image below.

I am using the firmware with the file name 旧FYT SOFIA 1024x600 .zip and I extracted to a FAT32 SD Card.

What is causing this?
[Android Head-Units] gtxaspec:
Try a flash drive, or swap the sd card slots...or try a different memory card. It's an installation media issue.
[Android Head-Units] markmorto:
Unbranded Material(ish) Design radio mods

Having the flu last weekend is probably the only reason I created these new mods, but it is what it is.

My last update was branded for VWs only, but after driving around with VW on my radio, I decided I wanted something different. What I ended up with is the the same as the last Material(ish) Design mod, but with a different background image.

In the original mod, I removed the frequency controls, but in this update, I put in an image of frequency being controlled. Just do yourself a favor and don't think about it too long.

A also added a red variant, because, hey why not?

Downloads:

Blue radio: https://drive.google.com/open?id=1CABlfP8oFfUeaaWZNlVtm9RE6eN7RIxn

Red radio: https://drive.google.com/open?id=14DG_qBKJH0x45N4Bd-BekdACFFgWsO9x

I also added a new BT/Phone mod in red:

(New) Red Material(ish) BT/Phone: https://drive.google.com/open?id=1kZ6pMk1vPduLh6Wfij3fAVfmuheJa-nv
[Android Head-Units] etrefal:
Very nice mods! Blue one going in my car soon!

Thanks Mark
[Android Head-Units] Umitb:
Hi,

I am getting such an error What can I do to help you? OTA package and app package must update same time

Thank you
[Android Head-Units] markmorto:
Could you provide additional information? Is this happening during an update, are you trying a new mod, etc.? When does the problem happen?
[Android Head-Units] Umitb:
I uploaded the stock and then I made a special offer. Now neither stocks nor customs have been loaded.
[Android Head-Units] dbboy:
I don't have this option. Any ideas or have I missed something?
[Android Head-Units] markmorto:
It's not included in the standard Joying Settings app. You need to replace it with the standard Android Settings app from the Joying Extra Tools app.

Once the new Settings is installed, go into device settings and press the build number 7 times to enable the Developer option in Settings. Then you can go into the developer options to enable split screen.

Seems complicated, but it only takes 10 minutes to get split screen working.
[Android Head-Units] tosamm:
Hello,

I did not find the mirror for the android 6 firmware or did I miss something?

I´ve been looking in different places like the new joying site or the forum itself, but no luck yet.

Give me a hint please.

The Unit is a Joying, running at the moment with Android 5.1.

Thanks, Thomas

P.S.

I just checked the HU. It seems that it won't make sense to update. It's 1GB RAM device with a A9 1,6GHz processor. I guess, it's not recommended?
[Android Head-Units] etrefal:
This thread is for the Sofia 3GR units, it has an Intel-based processor, not an A9 - don't try the Intel firmware.
[Android Head-Units] gtxaspec:
FYI, joying sells the FYT6026 core board as an upgrade to any FYT6021 based unit on their site now...
[Android Head-Units] fabien_m2002:
Hello

is it true Viper is better than mixing with equaliser under Winamp?
[Android Head-Units] surfer63:
This removal of the deep_buffer: Is that only for 6.01?

Or do I also need to remove it when I want to use the "USB enhanced" audio_policy.conf on my 5.1.1 device?

(I'm checking for my APK to make it suitable for both 5.1.1 and 6.01)
[Android Head-Units] AssassinsLament:
You can but Joying's software changes it back almost instantly. They do it in the Sofia-1-C9-Server-V1.0.apk.

It's all subjective. Viper4Android isn't something you just install and it works, there's so many features that can be changed to make it sound how you want it. After installing viper, I suggest searching through google for ideas on what to set, then do trial and error to see how you like your system to sound like.

It should be removed on both.
[Android Head-Units] wanb1i:
I cannot get your root script to work, something doesn't like the "-c" portion of the script:

E:\Program Files (x86)\Minimal ADB and Fastboot\fix\root>copy_install.bat 192.168.43.66

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

* daemon started successfully *

connected to 192.168.43.66:5555

restarting adbd as root

connected to 192.168.43.66:5555

198 KB/s (13788 bytes in 0.067s)

176 KB/s (14302 bytes in 0.079s)

19 KB/s (629 bytes in 0.031s)

209 KB/s (346536 bytes in 1.617s)

207 KB/s (99916 bytes in 0.470s)

167 KB/s (6539610 bytes in 38.167s)

68 KB/s (46416 bytes in 0.659s)

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!

E:\Program Files (x86)\Minimal ADB and Fastboot\fix\root>E:\Program Files (x86)\Minimal ADB and FastbootE:\Program Files

Any help would be appreciated!
[Android Head-Units] surfer63:
The bat file contains

..\win-adb\adb kill-server
..\win-adb\adb connect %1
..\win-adb\adb root
..\win-adb\adb connect %1

Please change that to:

..\win-adb\adb kill-server
..\win-adb\adb connect %1
REM ..\win-adb\adb root
REM ..\win-adb\adb connect %1

(Or remove these 2 lines)

and please try again.

If that's the issue, then that's also the change between 5.11 and 6.0.1
[Android Head-Units] wanb1i:
so now it says the device is OFFLINE and I can't get it back online, do I need to reboot it again?
[Android Head-Units] surfer63:
Yes, that't the tcpip stack and adbd getting corrupt. Unfortunately that has not been solved in 6.0.1 obviously.

So yes, please reboot.
[Android Head-Units] wanb1i:
Same result with one difference, see below:

E:\Program Files (x86)\Minimal ADB and Fastboot\fix\root>copy_install.bat 192.168.43.66

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

* daemon started successfully *

connected to 192.168.43.66:5555

mount: Operation not permitted

mkdir: '/sdcard/supersu': File exists

191 KB/s (13788 bytes in 0.070s)

178 KB/s (14302 bytes in 0.078s)

19 KB/s (629 bytes in 0.031s)

234 KB/s (346536 bytes in 1.442s)

212 KB/s (99916 bytes in 0.459s)

208 KB/s (6539610 bytes in 30.634s)

197 KB/s (46416 bytes in 0.229s)

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!
[Android Head-Units] surfer63:
Please restore the original 2 lines like so:

..\win-adb\adb kill-server
..\win-adb\adb connect %1
..\win-adb\adb root
..\win-adb\adb connect %1

And change

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

to

..\win-adb\adb shell "mkdir -p /data/supersu"
..\win-adb\adb shell "cp /sdcard/supersu/* /data/supersu/"

And please try again.

(As mentioned: I can't experiment myself right now, so this is a theoretical approach)
[Android Head-Units] wanb1i:
Not sure what just happened.... here's the readout: :confused:

E:\Program Files (x86)\Minimal ADB and Fastboot\fix\root>copy_install.bat 192.168.43.66

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

* daemon started successfully *

connected to 192.168.43.66:5555

adbd is already running as root

already connected to 192.168.43.66:5555

160 KB/s (13788 bytes in 0.083s)

167 KB/s (14302 bytes in 0.083s)

13 KB/s (629 bytes in 0.046s)

233 KB/s (346536 bytes in 1.452s)

222 KB/s (99916 bytes in 0.438s)

205 KB/s (6539610 bytes in 31.005s)

168 KB/s (46416 bytes in 0.268s)

Reboot your Head Unit NOW!

Also weird, I manually copied the files to /mnt/sdcard/supersu and now that folder and all the files are gone!
[Android Head-Units] surfer63:
It seems though that the script ran correct this time, otherwise you would have had errors.

This means that those 2 "su -c mkdir .... etc" lines need to be changed for 6.0.1

And yes: everything is gone from the intenral memeory (/sdcard) as I clean up at the end of the script

REM Clean up
..\win-adb\adb shell rm -rf /sdcard/supersu
..\win-adb\adb shell rm -rf /data/supersu
[Android Head-Units] wanb1i:
Ok, I guess that makes sense, rebooting not to verify root. Thanks Dude, that worked!

Do I need to change the busybox or will installing stericson's Busybox fix it? if I do need to mod the Busybox what do I need to change in the script to do it.
[Android Head-Units] wanb1i:
Thanks so much for your help, I never would have figured it out by myself! Now my HU is 98%. If I could get my PTT key to initiate Google Voice, without messing up the rest of the keys, I'd be done! I have gustden's newest app installed, but it doesn't engage Google Voice and that key is not programmed. Do you have any ideas?
[Android Head-Units] gustden:
Here is an update Sofia-1-C9-Server-V1.0.apk (April 27 - android 6). It has the task killer removed and will call the google voice search from the 'SRC' button of the key mapper. You should be able to map this to any key on your steering wheel.
[Android Head-Units] gtxaspec:
just discovered that the "config.txt" inside the root firmware directory is copied by recovery to the unit, AND processed by init, so you may enable ADB here.

just add "service.adb.tcp.port=5555" to the last line. no need to unpack Allapp.pkg. Then flash again.
[Android Head-Units] wanb1i:
Thanks! I really appreciate it! :good:

So this is the same as your latest app for the Marshmallow update, except it has Google voice on the src button?

---------- Post added at 07:30 AM ---------- Previous post was at 07:27 AM ----------

Where is this file located on the HU?
[Android Head-Units] surfer63:
It is not on the HU. It is in the downloaded ROM zip.
[Android Head-Units] wanb1i:
So, if I've already updated the firmware, I have to use terminal & reboot anytime I want to use adb? There's no file that can be edited after it's installed to add adb permanently?

Surfer, one other question, there's a recovery script in your signature file what does that do, is it twrp? Not sure what I thought I was seeing, but I was incorrect about a "Recovery" in your script, sorry!
[Android Head-Units] gustden:
Exactly!
[Android Head-Units] wanb1i:
Thanks so much! :D
[Android Head-Units] Redbullssg:
How do you know what core board you have?
[Android Head-Units] gtxaspec:
By model number of the unit, or by looking inside. FYT 6026 is the px5.
[Android Head-Units] Redbullssg:
Okay, so mine is the 5009 and not compatible then.
[Android Head-Units] Nightmare[ITA]:
hey there

Indeed, i just installed one today!

I am using a huawei e3372 dongle with sim from my local provider.

Plug it in, install "PPP Widget", set APN setting and you're good to go, the app will recognize the Stick and take care of the rest.

I noticed some Bugs with WiFi lately. The device runs slower with WiFi connected and it Started to randomly loose connection, so i had to turn off and on the WiFi in Android.

I am very happy with this, works perfectly.

In addition i don't have to turn on WiFi hotspot all the time, you just get in, BT and Dongle connect automatically and you can drive off without moving a finger.

Also when streaming something on the device you save a lot phone battery.
[Android Head-Units] Redbullssg:
I know that once you have updated to the 6 from the 5,you can't go back. But why is that? Is there any option to go back to 5 at all? Replacing something?
[Android Head-Units] gtxaspec:
Limitation of the bootloader. No way to rollback.
[Android Head-Units] edit:
In my Ford headunit (Oval shape) the 5009 motherboard was compatible with the one with 6021... Compatible with the display, the cables... I am curious if i can swap the board for the new model... I don't want to because the px5 can't do BT tethering but... I am curious
[Android Head-Units] jodybgoode:
Does anybody know if I can usb tether to my head unit. I had to get a straight talk branded galaxy j7. I don't have any way to root. Bluetooth tether is way slow and foxfi doesn't work. I can usb to my pc with pdanet. I just can't figure out how to make it work with my headunit.
[Android Head-Units] gtxaspec:
Yes, if you have the 6021 the 6026 is px5 based and is pin compatible though.