[SOLVED] How to use Steering Wheel Controls (SWC) with Zlink/Zbox/Spotify/Apple Music - Android Head-Units

[SOLUTION]
This integration is not present on most head units so I wrote a Xposed module which hooks the proprietary button press handling methods and translates them into standard HID keypresses. This means that SWC will work with Zlink/Zbox and it will also work with other apps on the head unit such as Spotify and Apple Music.
See https://forum.xda-developers.com/showpost.php?p=79312591&postcount=56 for the first release and follow the thread for later releases.
Note that there are two types of releases, final and debug releases. Final releases do not display and debug information via toast messages on the screen. Debug releases display button press information via toast messages on the screen which allow users to collect this information and submit it on this thread so that it can be integrated into the module and their buttons can be supported.
[ORIGINAL PROBLEM]
Hi all,
I recently just picked up a Witson W2-W329 unit. Basically it's a PX5 unit with the following OS Build and firmware:
CPU: ARM Cortex-A53 eight-core 2+32 GB PX5; CPU: PowerVR G6110
Build: PX5-userdebug 8.0.0 OPR5.170623.007 eng.bsp.20180528.174007 test-keys
MCU: 2018-04-16 17:04:06 ZHAN_(NOR)__90_C9RD6686_CAN(A)PX5D1804160
After some fiddling with USB ports I managed to get CarPlay working and to be honest the interface makes the unit feel premium vs the standard bluetooth audio interface. I'd love to use it over the standard interface BUT.... steering wheel controls don't work.
I've got it installed into a Renault Koleos which has a CANBus box. So here is my question...
Has anyone else used CarPlay on a PX5 unit and been able to use their steering wheel controls with it?
It would seem as if the OS just has to push the commands through to the app via some sort of an API. The kind of integration you would expect...

Are you using the zlink app for Carplay or do you have a dongle?

vassandrei said:
Are you using the zlink app for Carplay or do you have a dongle?
Click to expand...
Click to collapse
Zlink. What Witson unit do you have? Is it PX5 and running CAN? Do you know if the SoM is made by FYT?

looxonline said:
Hi all,
I recently just picked up a Witson W2-W329 unit. Basically it's a PX5 unit with the following OS Build and firmware:
CPU: ARM Cortex-A53 eight-core 2+32 GB PX5; CPU: PowerVR G6110
Build: PX5-userdebug 8.0.0 OPR5.170623.007 eng.bsp.20180528.174007 test-keys
MCU: 2018-04-16 17:04:06 ZHAN_(NOR)__90_C9RD6686_CAN(A)PX5D1804160
After some fiddling with USB ports I managed to get CarPlay working and to be honest the interface makes the unit feel premium vs the standard bluetooth audio interface. I'd love to use it over the standard interface BUT.... steering wheel controls don't work.
I've got it installed into a Renault Koleos which has a CANBus box but I've looked at the wiring diagram of the car and I'm sure that the steering wheel controls are wired directly and not through CAN.
So here is my question...
Has anyone else used CarPlay on a PX5 unit and been able to use their steering wheel controls with it?
It would seem as if the OS just has to push the commands through to the app via some sort of an API. The kind of integration you would expect...
Click to expand...
Click to collapse
I have the same problem, also with can bus with a w2 w207 wiston device for my peugeot 207
joying has similar looking mcu names
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and has also firmware for my car, with can bus and the same px5, screen res & ram. (maybe also for your car)
what is different is that i have a built in dvd drive and the joying unit does not.
1. Is it a bad idea to try this firmware? joying has a newer firmware
2. is it possible to revert to the preinstalled firmware if it does not work properly (backup)?

Zaagfluit said:
I have the same problem, also with can bus with a w2 w207 wiston device for my peugeot 207
joying has similar looking mcu names
and has also firmware for my car, with can bus and the same px5, screen res & ram. (maybe also for your car)
what is different is that i have a built in dvd drive and the joying unit does not.
1. Is it a bad idea to try this firmware? joying has a newer firmware
2. is it possible to revert to the preinstalled firmware if it does not work properly (backup)?
Click to expand...
Click to collapse
A few thoughts:
Some weeks ago the user @walkin123 tried the same thing. He installed the latest Joying FW onto his Seicane unit. The unit accepted the firmware but knew that it was not a joying unit (they must have some sort of a handshake with the MCU) and therefore displayed a banner at the top of the screen indicating that the FW does not match the MCU. Even though his FW supported CAN it seems that it does not support all of the vehicles that the Seicane FW did and so he was unable to select his particular vehicle from the Android system. Even though Android does not perform the CAN decoding it seems as if it configures the MCU and possibly the CAN box as to what vehicle to decode for and without the option to select his vehicle he lost all CAN inputs including steering wheel commands. On the plus side the FW solved all of the other bugs that he was experiencing.
Another possible problem is that while the MCUs and the interconnections within the units are similar they are not identical. For instance they seem to use different radio tuner modules which the MCU controls via I2C/I2S. You may lose radio functionality if the different modules are not protocol compatible but you may be OK if they are.
Regarding the backup and restore option, this is something that I have been investigating for the last week. I believe that it should be simple to make a backup of the /system /restore /data and /misc partitions so that an Android restore should be possible. Whether or not the unit will allow you to force an older ROM over a newer ROM is something that I am unsure of. @surfer63 or another experienced member would be able to help you there. In the case of the MCU I also believe it is simple to extract the img but once again I am unsure of how simple it would be to write it back over whatever you install.
Perhaps @surfer63 or one of the more experienced guys could comment on this.

Ok, thnx for the explanation!
I'll probably wait/hunt for a more suitable firmware then.
I think the swc function for the zlink app is just something they forgot to implement, all other stock apps do have swc, so a small update would fix it.
I also noticed that the zlink software in my unit is 2.X. The latest from zjinnova is 4.X.

Zaagfluit said:
Ok, thnx for the explanation!
I'll probably wait/hunt for a more suitable firmware then.
I think the swc function for the zlink app is just something they forgot to implement, all other stock apps do have swc, so a small update would fix it.
I also noticed that the zlink software in my unit is 2.X. The latest from zjinnova is 4.X.
Click to expand...
Click to collapse
All the best getting firmware out of Witson. I think you would be the first person I have hear of as being successful in doing so. They have literally zero support. I would never suggest buying from them unless you absolutely have to. Joying support is FAR better.

looxonline said:
All the best getting firmware out of Witson. I think you would be the first person I have hear of as being successful in doing so. They have literally zero support. I would never suggest buying from them unless you absolutely have to. Joying support is FAR better.
Click to expand...
Click to collapse
I'm afraid you're right. i think i will try some retailers selling "s200" devices that claim they provide software updates.

Somone on this forum has extracted an updated version of the zlink apk from a joying firmware with build in carplay support. Could this solve the steering wheel problems? Is it possible to run the 2 apk’s with different version numbers side by side?

Zaagfluit said:
Somone on this forum has extracted an updated version of the zlink apk from a joying firmware with build in carplay support. Could this solve the steering wheel problems? Is it possible to run the 2 apk’s with different version numbers side by side?
Click to expand...
Click to collapse
Just be sure you are not mixing the zBox APK with the zLink APK. If you did find an updated zLink APK I'd be interested to know where. I would like to give it a test.

looxonline said:
Just be sure you are not mixing the zBox APK with the zLink APK. If you did find an updated zLink APK I'd be interested to know where. I would like to give it a test.
Click to expand...
Click to collapse
https://forum.xda-developers.com/an...ction-joying-unit-android-auto-t3791200/page3
Its on this page, the apk is included in reply #25. They try to use it in a unit without the carplay function built in
---------- Post added at 11:10 PM ---------- Previous post was at 10:29 PM ----------
looxonline said:
All the best getting firmware out of Witson. I think you would be the first person I have hear of as being successful in doing so. They have literally zero support. I would never suggest buying from them unless you absolutely have to. Joying support is FAR better.
Click to expand...
Click to collapse
On this site there are people who do get newer versions of certain s200 wxxx mcu’s from witson, So if a new version is released you will probably find it there first.
https://www.roadnav.com

Zaagfluit said:
I'm afraid you're right. i think i will try some retailers selling "s200" devices that claim they provide software updates.
Click to expand...
Click to collapse
Sweet mother of pearl.......WITSON just contacted me with a firmware update dated 02.08.2018. After weeks and weeks of absolutely no feedback whatsoever they just dropped this one....
Will install it this weekend and see if it fixes the issue.

looxonline said:
Sweet mother of pearl.......WITSON just contacted me with a firmware update dated 02.08.2018. After weeks and weeks of absolutely no feedback whatsoever they just dropped this one....
Will install it this weekend and see if it fixes the issue.
Click to expand...
Click to collapse
Nice!, Thats fresh from the oven. Is it specific for your car?:angel:

It's labelled as specific in the filename but when you scan through the MCU folder it has a list of compatibly radio and CAN configurations that seems to cover everything that they sell.

looxonline said:
It's labelled as specific in the filename but when you scan through the MCU folder it has a list of compatibly radio and CAN configurations that seems to cover everything that they sell.
Click to expand...
Click to collapse
Sounds promising:good:
---------- Post added at 08:53 AM ---------- Previous post was at 08:40 AM ----------
Zaagfluit said:
Sounds promising:good:
Click to expand...
Click to collapse
Ohh yeah...I got it too!

Zaagfluit said:
Sounds promising:good:
---------- Post added at 08:53 AM ---------- Previous post was at 08:40 AM ----------
Ohh yeah...I got it too!
Click to expand...
Click to collapse
Dig through the archive and check what dates the files were modified on. Looks like they labelled it 02.08.2018 but to be honest there is not much in there that was modified after April.

looxonline said:
Dig through the archive and check what dates the files were modified on. Looks like they labelled it 02.08.2018 but to be honest there is not much in there that was modified after April.
Click to expand...
Click to collapse
I’ve installed it, and it is EXACTLY the same mcu number (same date, same time, same everything) as you described in the beginning of this topic. Nothing changed, zlink app still on 2.4

Zaagfluit said:
I’ve installed it, and it is EXACTLY the same mcu number (same date, same time, same everything) as you described in the beginning of this topic. Nothing changed, zlink app still on 2.4
Click to expand...
Click to collapse
Exactly my point. Did you check the android build details and are they also the same?
Joying actually make improvements based on the problems that the customer is experiencing. WITSON stick their head in the sand and hope that the problem will disappear. I'm planning on doing a youtube review to show how poor the service is and how many bugs the unit has just to try and help other people. To be fair I will probably give it another month to see if they are actually interested in working on new firmware.

looxonline said:
Exactly my point. Did you check the android build details and are they also the same?
Joying actually make improvements based on the problems that the customer is experiencing. WITSON stick their head in the sand and hope that the problem will disappear. I'm planning on doing a youtube review to show how poor the service is and how many bugs the unit has just to try and help other people. To be fair I will probably give it another month to see if they are actually interested in working on new firmware.
Click to expand...
Click to collapse
I did not check the Android build yet. A youtube review might be usefull, also for witson to see how they are screwing things up. I hope there will be custom/alternative roms available in the future, since it uses the same hardware as many other brands. I will try The zlink apk from Joying this weekend to see if it changes anything.

Zaagfluit said:
I did not check the Android build yet. A youtube review might be usefull, also for witson to see how they are screwing things up. I hope there will be custom/alternative roms available in the future, since it uses the same hardware as many other brands. I will try The zlink apk from Joying this weekend to see if it changes anything.
Click to expand...
Click to collapse
I know that gtxaspec is working on a custom ROM for FYT based PX5 units. He fried his FYT SoM though so I think he needs more time to get another. When that is ready it should be compatible with our units provided it does not touch the MCU. That being said I am not too familiar with all of the interfaces between SoM and motherboard and whether there are major differences in implementation between the two resellers. Could be that the Joying ROM (which gtxaspec) is basing his off does not have support for the CAN vehicles that we need...anyway we will see with time.
Let us know how the new zlink app works out.

Related

Which app allows BT Music to show song info?

When streaming music via my phone through Bluetooth I don't get any song/track info on the screen.
Any app that does?
Please suggest an Application to solve this problem
o2sys said:
When streaming music via my phone through Bluetooth I don't get any song/track info on the screen.
Any app that does?
Click to expand...
Click to collapse
I guess there is non to my knowledge. Bluetooth music/phone is a loose end for these kind of head units.
Bluetooth app does not provide concrete integration to the phone. For instance when I play audio attachments on whatsapp from my iPhone or any other app it does not play on head unit but it plays on my phone (even when my phone is connected to head unit). Now I understand it may be dependent on bluetooth version / what protocol your head unit understands.
But to my understanding this is a very loose end with very basic connection (unlike the once you find on a factory head units).
Sorry I was not able to answer your question, but I am also curious if anyone else has an answer for this.
This has been driving me nuts, as well. I just got my joying rk3188 unit last week, and that was the first thing I tried. Disappointed, I thought that upgrading to a malaysk rom might help and it didn't. I would really like to figure out if it's possible at all with this unit, as I pretty much only listen to music from my phone over Bluetooth, and really wanted to be able to see what was going on, on the dash.
From what I have figured out so far is that the Bluetooth avrcp protocol is key here. The phone and head unit have to support it. So for others reading this. That's a place to start. Make sure you have a capable phone first. Personally I have an iPhone 6+ which has avrcp version 1.4. The version is also important. Track info was not supported until version 1.3 and beyond. (Latest is 1.6).
So what I have been thinking is that if the Bluetooth module in the radio supports avrcp 1.3 or better, then at that point it's on the software. Not having the code that processes the data. I am going to open up my unit later tonight to find out what chip is in there for Bluetooth support and see if it is 1.3. If it is, I am going to start looking into that Bluetooth app and see if it can be modified at all.
Since you didn't specify the type of unit, on Newsmy head units the xdAuto rom supports this now.
Well, I'm not sure about the OP, but I have a joying rk3188 unit. I assume that the xdauto rom cannot be installed on the joying head unit? I am new to this, but I thought malaysk was one of the few custom roms out for joying units. I would like to give it a try if possible though.
If not, I might be returning the joying and getting one of these nu3001 units instead. I originally wanted the clean install faceplate, physical volume button and 8 inch screen. But this Bluetooth thing might be a deal breaker.
Also reading about the dual bt on this unit makes me realize that my odb2 I bought is probably not going to work either. Great...
I have the joking rk3188 as well.
When I was reading through the amazon review for joying units one of the joying reps replied to say that their unit supported avrcp. So likely its just a software thing.
Geekybiker said:
When I was reading through the amazon review for joying units one of the joying reps replied to say that their unit supported avrcp. So likely its just a software thing.
Click to expand...
Click to collapse
Yes I noticed that too. Which was a deciding factor when I purchased the unit. Problem is, avrcp v1.0 will only allow you to control the phone from the head unit. It will not send the track information. So if the Bluetooth module in the head unit is 1.0 then it's hardware and it will not work. Note, I was able to get the head unit to change tracks on my phone. So avrcp to some extent is working. I want all that 1.3 goodness though. 1.4 (library browsing) would be a nice bonus.
---------- Post added at 12:44 AM ---------- Previous post was at 12:27 AM ----------
Regarding my previously mentioned plan, didn't go as well as I hoped. I found the Bluetooth module and located what I believe is the Bluetooth IC. Problem is that there is a sticker on it with some markings that I assumed to be the part number. I closed it all up and did some searching and nothing. I probably should have peeled the sticker back to see what was underneath, as well.
The markings on the chip were A5BC6 160F. If anyone has more detail about this chip.
There were a couple more chips on the module. But I was able to identify them as being a headphone processing chip, and the other is a EEPROM.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
creamerBot said:
The markings on the chip were A5BC6 160F. If anyone has more detail about this chip.
Click to expand...
Click to collapse
I don't know about that chip, but there is a good chance it's a CSR Bluecore chip as most units use those.
The problem is that those chips run customized firmwares, so finding the commands to make it work could be quite a bit more difficult.
Most chips and firmware use a variation on serial AT commands.
If you can see the serial port data to it you should be able to identify it from the commands going back and forward.
leonkernan said:
I don't know about that chip, but there is a good chance it's a CSR Bluecore chip as most units use those.
The problem is that those chips run customized firmwares, so finding the commands to make it work could be quite a bit more difficult.
Most chips and firmware use a variation on serial AT commands.
If you can see the serial port data to it you should be able to identify it from the commands going back and forward.
Click to expand...
Click to collapse
I decided to go about this another way. I think I have some bad news for any Joying owners that are hoping for this feature. I decided to use Bluez-Utils and scan the device for service records using sdptool to see what services are available on the head unit. As a base case i also scanned my phone to see what results I get from that. Sure enough this is what i found:
From the phone:
Code:
Service Name: AVRCP Device
Service Description: Remote Control Device
Service RecHandle: 0x4f49110c
Service Class ID List:
"AV Remote Target" (0x110c)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x0103
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
code_ISO639: 0x6672
encoding: 0x6a
base_offset: 0x110
code_ISO639: 0x6465
encoding: 0x6a
base_offset: 0x120
code_ISO639: 0x6a61
encoding: 0x6a
base_offset: 0x130
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0104
From the Head Unit:
Code:
Service Name: AV remote control
Service Provider: CSR
Service RecHandle: 0x10002
Service Class ID List:
"AV Remote" (0x110e)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x0100
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0100
There was more for each device, of course, but this seems to be the bit we need. You can see from the phone that it clearly supports AVRCP, and at the bottom states that the version is 1.4. This matches the specs you will find on apple's website. For the head unit it says that it supports AV remote control, at version 1.0.
I think that solves it. The profile on the bluetooth module of the head unit does not have the right version in order to have a proper piece of software written around it.
If anyone thinks there is an error in my findings, let me know. Unfortunately, though, i just don't think this unit will be able to do more than control the device.
OH, and @leonkernan, notice you were spot on with the chip being CSR.
---------- Post added at 05:37 AM ---------- Previous post was at 05:32 AM ----------
@leonkernan , is there anyway that you can identify for us/me what profile is used in the NewsMy units? I am seriously considering returning the Joying in favor for a CarPad 2 or 3. I would love to know what is in each of those. I didnt realize they also make a version that fits in the dash of a jetta. More expensive than a joying, but for the extra hardware and features, I guess you have to pay...
If you need more detailed instructions on how i was able to pull those specific details, just let me know.
Any help would be greatly appreciated.
creamerBot said:
is there anyway that you can identify for us/me what profile is used in the NewsMy units?
Click to expand...
Click to collapse
Here is the programming guide for the one in the Newsmy units. I know it works because i've been using it for all the work i've done on the Newsmy units.
leonkernan said:
Here is the programming guide for the one in the Newsmy units. I know it works because i've been using it for all the work i've done on the Newsmy units.
Click to expand...
Click to collapse
This is great, very helpful. Looks like it goes up to 1.3, which I guess was obvious by the fact that metadata is working. No mention of 1.4 though. Would have been nice, but I guess I can make do without the library browsing.
Thanks.

Xtrons mtcd (any mtcd?) malaysk rk3188 best ever rom tomtom working !!!

Hi guys and thanks for giving me the opportunity to share my experience here of my four days and four nights of hard work to make my head unit to work in proper mode and to have the Tomtom working.
First of all I want to thanks to MALAYSK for his big and invaluable work for making me and maybe many others happy of having a powerful piece of technology working as it is meant to work.
Secondly I want to THANKS to every person from here that gave me an even small hint that helped me to achieve my task which was apparently a very difficult and risky task for me, trying to make my (not cheap) device to work properly.
I will try, based on my long and tiring experience, to be as clear and tidy as possible, to help even those not very experienced in writing custom software on their devices, to make them working properly.
I want to warn everybody that everything they will do based on my experience, they will do it on their own risk and I will not be responsible for anything gets wrong to their devices. I will be very sorry for this but nothing more. I will try my best to be very clear and to give as detailed instructions as possible to make you happy . I will mention on every procedure to follow if I am SURE or I BELIEVE that the procedure or action works on EVERY similar device with mine.
So lets go!
1. (I BELIEVE) This procedure works on every MTCD device no matter what brand it is based on RK3188 platform (can be checked in ABOUT section of you device settings)
2. (SURE) This procedure work perfect on my device called PF7539BA made by XTRONS for BMW X5, E39 or in my case Range Rover L322 Vogue 2002-2005. They are many other devices made by Xtrons or JoYing based on the same platform.
3. (SURE) The list of materials and files you need to make it done are:
- SD card formatted in windows (FAT 32) minimum 4Gb in size
- Two files called dupdate.img and dmcu.img. (IBELIEVE) These files are called the same no matter what brand is the device made by. The files can be found on the manufacturer website on FIRMWARE UPDATE section. For example XTRONS has on their website allocated on almost every device this section if the device is updatable. Find your device and download this files on your computer first. (http://www.xtrons.co.uk). I recommend to make a folder for original firmware and another folder for custom files that you will download from here!:silly: If the files are in archive format, unarchive them. So in the ORIGINAL FIRMWARE folder created by you on your computer you will have two files: dupdate.img and dmcu.img. They are many MCU device types so please be vary careful not using other than the one is yours. For more informations check this http://forum.xda-developers.com/android-auto/mtcd-discussion-questions-development/comprehensive-updated-mcu-list-mtcd-t3476880. Even the dmcu file on this website is newer than yours I encourage you to use the one downloaded from the manufacturer website.
- Now download the newest dupdate.img file from here (Thanks to MALAYSK!!!) http://huifei.fs-fileserver.de/content/firmware/MTCD%20CUSTOM%20ROMS%20ONLY%20NOT%20FOR%20MTCB%20/RK3188/ and unzip it into the CUSTOM FIRMWARE folder also created by you on your computer.
- Write the file called dmcu.img (ORIGINAL) and dupdate.img (CUSTOM) on the SD CARD
- Put the card into the GPS slot of your device
- Next step is uncertain for me because I do not know if all devices have the same button combination for getting into RECOVERY MODE. I will give the way of doing my device. If does not work please do some research about how to get into your device's RECOVERY MODE. So first thing make sure the device is on and has the button lights on. PRESS POWER button until the button lights flash few times and when they stop flashing (3 to 4 times will flash) release the POWER button and press it again for one second and release it. At this point the device after few seconds will get into recovery mode. It must look like this picture (ignore the error messages at the bottom. I have used this picture from internet as example)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-Press once at a time the power button until you get to the third position called "update system/mcu image from sdcard and clear all". At this point press long the POWER button until the device starts checking the files on sdcard. It will take some time doing the firmware writing. If the flashing procedure was fine, it will reboot and say ERASING and after that will reboot and start as normal the booting process. DO NOT LET IT FINNISH booting as it will not boot properly but do the previous procedure again to get into the RECOVERY MODE again. Once there go to the sixth option called "wipe all data/factory and cache reset" and press long the POWER button until it execute it. The cache clearing will start and after this will reboot normally.
If everything worked well you will get after few minutes into the DESKTOP of the device having a ROOTED and working almost perfect your device!!:highfive:
I want to mention that some of the application are not the same as your original ones but this ones are working and looking better! The custom firmware is based on Lollipop 5.1.1 !!! I do not know if does work on the ones loaded with KitKat.
For those who want to have the (bloody) TOMTOM working you have to install and activate (put check mark on in after installation) the mtcservice-2.28.apk application in XPOSED FRAMEWORK page application which is already installed on your device. Get this https://docs.google.com/uc?export=download&id=0B9YiDhcSP2veZkhMOGQ2T0FNU0U and install. Reboot. Start Xposed manager and go to module and check this application. Reboot. Now you can download TOMTOM from here https://docs.google.com/uc?export=download&id=0B9YiDhcSP2vebzVyT2p0NnhDc1k and install. make sure you have internet on device when starting Tomtom as it will need it for map downloading.
Based on my research and experience this is all I've done to my device and I have a good working device and working (bloody) TomTom. :silly:
Enjoy!!
Xtrons PC71FSFA-B
Hi,
i have a Xtrons PC71FSFA-B with Android 4.4 and would like to give Malaysk Rom a try.
Unfortunately i can't find the required files on xtrons.co.uk.
Do you know where else i could find these Files ?
Is there anything else to take care before installing Malaysk on this Unit ?
Regards
Frank
Any plans for a Malaysk ROM (or any other?) based on Android 6, or even 7?
Any advantages to the newer Android based ROMs (since the current XTRONS devices are based around Android 6)
Malaysk ROM for MTCD units is based on Android 6.0.1...Lots of members (and others) here running it and reckon it is the best available so far. Mine was bought from Xtrons but as @typos1 tells everyone they and other resellers aren't the manufacturers. So PX5 units from Xtrons are all GS units from what I understand.
MacConsult said:
Any plans for a Malaysk ROM (or any other?) based on Android 6, or even 7?
Any advantages to the newer Android based ROMs (since the current XTRONS devices are based around Android 6)
Click to expand...
Click to collapse
ArtfulCodger said:
Malaysk ROM for MTCD units is based on Android 6.0.1...Lots of members (and others) here running it and reckon it is the best available so far. Mine was bought from Xtrons but as @typos1 tells everyone they and other resellers aren't the manufacturers. So PX5 units from Xtrons are all GS units from what I understand.
Click to expand...
Click to collapse
AFAIK Malaysk is working on 6 and 7, RK3368/PX5 units are on 6 atmo and RK3188/PX3 2Gb devices are on 7.
You are correct, @ArtfulCodger, Xtrons are sellers only and units CANNOT be identified by the seller, they can ONLY be identified by the MCU version.
Xtrons also sell lots of differnt units from lots of different manufacturers.
Thanks is it true that all the PX5 units purchased from Xtrons would be GS MCUs? Still trying to get my head around the MCU. For instance the latest GS MCU now appears to be 2.58 and I'm waiting for some adventurous soul to advise if they have found any actual change to how the HU runs.
ArtfulCodger said:
Thanks is it true that all the PX5 units purchased from Xtrons would be GS MCUs? Still trying to get my head around the MCU. For instance the latest GS MCU now appears to be 2.58 and I'm waiting for some adventurous soul to advise if they have found any actual change to how the HU runs.
Click to expand...
Click to collapse
I'll happily be adventurous, now that someone told me how to save mcu settings
I'm planning on playing around with some upgrades, as well as the Malaysk ROM, to see (and document) how these work.
---------- Post added at 06:40 AM ---------- Previous post was at 06:36 AM ----------
Also, not identifying by the sellers and distributors is understandable (this is all about the mainboards etc...), but ultimately each of those sellers makes individual modifications to the head unit configurations that *does* set them apart -- specifically the position and function of the front buttons (which I have found to be different for almost each manufacturer). So, ultimately, whoever the manufacturer of the mainboards is, packages it for XTRONS (or whoever) thus still creating a uniquely identifiable product.
Just saying.
ArtfulCodger said:
Thanks is it true that all the PX5 units purchased from Xtrons would be GS MCUs? Still trying to get my head around the MCU. For instance the latest GS MCU now appears to be 2.58 and I'm waiting for some adventurous soul to advise if they have found any actual change to how the HU runs.
Click to expand...
Click to collapse
Xtrons sell lots of units from lots of different manufacturers, they might sell mainly GS units for a while, then they might sell other types, but its not really relevant to anything. No changelogs are published for MCUs, but its generally a good idea to update it, like any software.
MacConsult said:
I'll happily be adventurous, now that someone told me how to save mcu settings
I'm planning on playing around with some upgrades, as well as the Malaysk ROM, to see (and document) how these work.
Also, not identifying by the sellers and distributors is understandable (this is all about the mainboards etc...), but ultimately each of those sellers makes individual modifications to the head unit configurations that *does* set them apart -- specifically the position and function of the front buttons (which I have found to be different for almost each manufacturer). So, ultimately, whoever the manufacturer of the mainboards is, packages it for XTRONS (or whoever) thus still creating a uniquely identifiable product.
Just saying.
Click to expand...
Click to collapse
In factory settings there is a button to export the config, this is how you save your settings.
NONE of the sellers makes ANY modifications to the units, for some sellers the manufacturers, may add a badge or a sticker, but a GS unit is a GS unit, no matter where its bought from and there is no difference, nothing "sets them apart" unless you count stickers/badges. The position of the buttons is down to the manufacturer, not the seller and its not relevant anyway, because button positions makes no difference to either the MCU software or the ROM, its also simply not true to say that the front buttons are different for each manufacturers, some are, some arent. Its like car dealers - a BMW 3 series bought from one dealer is no different from a BMW 3 series bought from another dealer, even if it has stickers on it saying "ACME BMW Ltd", you could argue that these stickers would "set it apart", but in reality its the same BMW 3 series as one bought from another dealer.
Seriously, unless we re talking after sales support, warranty etc its a waste of time talking about the sellers.
Hi
My stereo is a W164 Mercedes and I want to update but do not know the ROM to use
The details for my stereo are:
Android 4.4.4 Quad Core 1024*600
Model
rk3188
Android version
4.4.4
Baseband version
Unknown
Kernel version
3.0.36+
[email protected]#87
Build number
Alex: 5201-20160410-125900-v3(4752)
TFT: 5303-20160121-103910-V01
MCU: 5303-20160428-113328-V01
Werra2006 said:
Hi
My stereo is a W164 Mercedes and I want to update but do not know the ROM to use
The details for my stereo are:
Android 4.4.4 Quad Core 1024*600
Model
rk3188
Android version
4.4.4
Baseband version
Unknown
Kernel version
3.0.36+
[email protected]#87
Build number
Alex: 5201-20160410-125900-v3(4752)
TFT: 5303-20160121-103910-V01
MCU: 5303-20160428-113328-V01
Click to expand...
Click to collapse
You dont have an MTCD/E unit, try the Android Headunits General forum.

Ownice C500 (2GB/16GB/Cortex-A53) VS New Joying (2GB/32GB/Intel SoFIA 3GR 4 Core)

I am looking for a VW head unit and after reading hundres of threads I came to a conclusion that in the price range up to $300 those two from title are the best choice.
Now I am torn between New Joying Intel 2GB/32GB and Ownice C500 quad core 2GB/16GB.
Are there any comparision tests between Intel SoFIA 3GR used in Joying and Ownice C500 CPU (supposedly Cortex-A53?)?
There's an AnTuTu test by ngochoangimsat of C500:
CPU: 10188
RAM: 3984
3D: 2446
TOTAL: 29946
Ownice C500 - 29
Still looking for the test of Joying.
Are there any comparision tests between their AMP IC (Joying - TDA7388(ST) VS Ownice TB2929)?
I wonder which unit is faster/better as they are priced quite similar on AliExpress.
The cheapest offers I have found:
$285 for Joying 2GB/32GB/Intel (AliExpress: JOYING Official Store, link not allowed yet)
$323 ($278+$45) for Ownice 2GB/16GB/Cortex-A52 (AliExpress: Autolink - Top Car D V D Supplier)
Interested in this as well as I just killed my mtcd kgl screen and digitiser. From what I can see, ownice c500 seems to have more features..4G, DVD drive..But Intel ones seems to get more development at the moment..
I have decided to go with Joying as I have no plans to use DVD drive (I have never used it even though I currently have one) and I have no plans to use 4G neither (I won't buy an extra SIM card, I will just tether connection from my phone over wifi).
C500 CPU scored around 29ks point in AnTuTu while old RK3188 CPU scored around 26k points.
On YouTube movies Intel CPU seems more responsive, it can be only a delusion though.
I am supposed to receive mine on 29/DEC.
i have not tried an Ownice, but I can tell you I went from a Joying MTCD to Joying Intel and it is night and day difference
I am leaning to the Joying intel, but the Ownice is really tempting because:
-the ownice has more features
>TPMS
>4G (this is not important for me)
-Android 6.0
-buttons are much better laid out.
-As I am buying for an Audi A4, the version by Joying has 2 buttons that are not functional meant for DVD operation and have the dvd slot blanked out making it feel like it's missing something. Checking with Joying if it can be reassigned or are they completely none functional.
-has a dvd slot
> not that I will use, but point above...it looks better with the DVD slot...
Reason I am leaning to the Joying unit is because:
-more development on this unit it seems
> unlocking full bluetooth function seems to be close
> have been rooted
-32GB storage
-more user feedback on Intel unit and how well it performs compared to the original MTCD units.
-joying seems to focus more on the software side, which is probably more important
I had similar concerns. The biggest downside of the Joying for me was the knobs placement, I prefer to have them on the lower edge like in the Ownice.
As for the Android version - I wouldn't count on pure 6.0 in Ownice. Seems like they are using some weird mixture of 4.4, 5.1 and 6.0 while majority of their kernel is still 4.4. Offering this mixture as Android 6.0 is kinda cheating...
I would have purchased a joying if they made it my car's form factor. Their website with examples and details alone speaks volumes.
Got a c500 instead. Crossing my fingers.
Sent from my SM-G935V using Tapatalk
So joying just confirmed with me that those buttons are dud...So weird having buttons that does nothing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
vs this from Ownice:
Buttons layout just makes so much more sense...
argh...so hard to decide..just don't want another regret like my current MTCD KGL
i would be interested to see if those Ownice units work with an American SIM, specifically Verizon
I may eventually try finding a sim to work with it. I've been told you can go to a Verizon Store and they can try one out.
Sent from my SM-G935V using Tapatalk
aarick said:
So joying just confirmed with me that those buttons are dud...So weird having buttons that does nothing.
Click to expand...
Click to collapse
That's because they reused the older injection mold and just blanked out the now useless DVD drive slot.
Probably would have cost too much to rework the whole thing.
I'll bet the buttons can still be pressed and remapped in software.
Didn't Intel cancel the SoFia stuff? so probably no future development of any kind?
http://www.pcworld.com/article/3063...-tablet-markets-after-cutting-atom-chips.html
The company is immediately canceling Atom chips, code-named Sofia and Broxton, for mobile devices, an Intel spokeswoman confirmed.
Click to expand...
Click to collapse
Anyway here is sample result for SoFIA 3G-R it says 26719 for Antutu result.
http://www.notebookcheck.net/Intel-Atom-C3230RK-SoC.156853.0.html
I bet C500 handily would beat it because it's processor at least seems to be much better on paper.
Also C500 has better GPU Mali-T720 compared to what Intel has Mali-450.
@concept5400 I think the screenshots from @ngochoangimsat clearly shows the SDK version is 23 in C500. I am not sure why you think it is a mixture. While I read some manufacturers tried to cheat by using mixed stuff. I think there is nothing which points to C500 not being an Android 6.0 device. While Joying is definitetely 5.x and it will probably never get an upgrade because of the dead Intel project.
So if I would compare C500 vs Joying SoFIA. C500 has faster processor, better GPU, supports 4G, android 6.0, many different C500 models with different button configurations, no buttons, dvd, without dvd etc. But Joying ? hmm rooted? I am not sure if it has any advantage over Ownice models other than being rooted?
leonkernan said:
That's because they reused the older injection mold and just blanked out the now useless DVD drive slot.
Probably would have cost too much to rework the whole thing.
I'll bet the buttons can still be pressed and remapped in software.
Click to expand...
Click to collapse
Glad to see another Melbournian here....
I agree and my gut feel is that it'll work as well. The lady at Joying also doesn't seem to know her stuff well.
---------- Post added at 11:13 AM ---------- Previous post was at 11:11 AM ----------
yurtesen said:
Didn't Intel cancel the SoFia stuff? so probably no future development of any kind?
http://www.pcworld.com/article/3063...-tablet-markets-after-cutting-atom-chips.html
Anyway here is sample result for SoFIA 3G-R it says 26719 for Antutu result.
http://www.notebookcheck.net/Intel-Atom-C3230RK-SoC.156853.0.html
I bet C500 handily would beat it because it's processor at least seems to be much better on paper.
Also C500 has better GPU Mali-T720 compared to what Intel has Mali-450.
@concept5400 I think the screenshots from @ngochoangimsat clearly shows the SDK version is 23 in C500. I am not sure why you think it is a mixture. While I read some manufacturers tried to cheat by using mixed stuff. I think there is nothing which points to C500 not being an Android 6.0 device. While Joying is definitetely 5.x and it will probably never get an upgrade because of the dead Intel project.
So if I would compare C500 vs Joying SoFIA. C500 has faster processor, better GPU, supports 4G, android 6.0, many different C500 models with different button configurations, no buttons, dvd, without dvd etc. But Joying ? hmm rooted? I am not sure if it has any advantage over Ownice models other than being rooted?
Click to expand...
Click to collapse
You make some good points there sir!...
just as I was about to bite the bullet and get the joying...I'm back to holding position. Might monitor the c500 development a bit further first and see if it changes. Android 6.0 doesn't quite worry me, but the full bluetooth stack and root is important to me as usually the headunits doesn't work exactly as how i want and xposed and root helps make it work a lot better...
@aarick I found another good point for joying, apparently the intel cpu may be supporting glonass. But I still would not go for Intel.
About the bluetooth. It looks like you can do anything with bluetooth attached device. I am not sure what you want to do exactly? Here is a nice video. Bluetooth stuff appear at 1:20 about https://www.youtube.com/watch?v=MRE-opyLOog
What I want to see in these units is a digital compass. I dont understand why they never have it. I think I will get one of those new C500's with buttons on the left with 7" screen and they have map/sdcard slot also.
yurtesen said:
@aarick I found another good point for joying, apparently the intel cpu may be supporting glonass. But I still would not go for Intel.
About the bluetooth. It looks like you can do anything with bluetooth attached device. I am not sure what you want to do exactly? Here is a nice video. Bluetooth stuff appear at 1:20 about
What I want to see in these units is a digital compass. I dont understand why they never have it. I think I will get one of those new C500's with buttons on the left with 7" screen and they have map/sdcard slot also.
Click to expand...
Click to collapse
Mainly want to be able to hook up my Bluetooth tyre pressure monitoring system to my head unit.
The ownice seems to have their own TPSM kit, but would like to avoid investing further into more stuff that I already own.
I think right now.. I'll be happy with the joying.. But when development catch up for the ownice.. I might regret it..
A few words after testing the unit for the last few days.
Generally speaking responsiveness is at acceptable level.
It's not even close to an iPhone level but it's doing well enough.
Satellite signal is working with GPS and GLONASS at the same time.
I had to switch off AF funcion in the radio because apparently it doesn't work so well - instead of searching for other frequencies of the same station it was changing radio stations.
It was shipped with language changed to my country language and with iGO NAVI with Europe maps and my country language set up as well, even though it was 2014 version of the app and the maps it was a nice touch.
Bluetooth app have a problem - when downloading contacts it is not saving the "+" sign before the country code.
For example - if I have a number stored in my phone as +44 123456789 it will be downloaded as 44 123456789.
Then if that person would be calling me, the unit would show the caller as +44 123456789, without matching it with the saved contact, because it has saved the contact as 44 123456789, without the + sign.
It's a bit annoying but I can live with it.
The following problem is ground breaking for me.
As this is my first Android head unit ever I am not sure if it's Joying only or general problem of those chinese units.
The unit can play radio sound AND sound of ONE other app with radio in the background.
This function is called GPS MIX and it's working only with predeclared NAVI app only.
If I declare Google Maps as my NAVI app - it can play radio in the background with Google Maps on my main screen.
But other NAVI apps in the background cannot produce sound.
If I would put other NAVI app on my main screen it wil start to produce sound but the radio will be turned off the second other app starts to do so.
Therefore I am not able to use two NAVI apps and radio at the same time.
In my country we have a Waze-like app for speed camera and mobile speed control units with a HUGE community and it's working like a charm (YANOSIK app).
The problem is that the app really sucks at turn-by-turn navigation. Everyone is just using it in the background with other NAVI app on main screen.
With this unit when YANOSIK app is working in the background it will not produce any sound, unless declared as the NAVI app in CarMediaSettings. When it's declared as the NAVI app it will produce sound ine the background but other NAVI app will mute/turn off the radio completely.
I am quite desperate with this problem as for now I still have to use my phone for one navi app...
Not really a definitive answer to your wondering, but I have a MTCD which can have two navi-apps produce sound running in the background and run a media app at the same time. In my case Tomtom and Flitsmeister (which sounds as the equivalent of your Yanosik app).
So I don't know about Joying, but there are definately 5.x units out there that can do this.
HVB83 said:
Not really a definitive answer to your wondering, but I have a MTCD which can have two navi-apps produce sound running in the background and run a media app at the same time. In my case Tomtom and Flitsmeister (which sounds as the equivalent of your Yanosik app).
So I don't know about Joying, but there are definately 5.x units out there that can do this.
Click to expand...
Click to collapse
Joying can do multiple nav apps and media app at the same time. Problem is playing the radio and multiple nav apps. Only assigned nav app can be heard when radio is playing.
gustden said:
Joying can do multiple nav apps and media app at the same time. Problem is playing the radio and multiple nav apps. Only assigned nav app can be heard when radio is playing.
Click to expand...
Click to collapse
Well.. not really in my case. When I run multiple nav apps in the background the only one producing sound is the one chosed as The Nav app in CarMediaSettings, others stay silent...
EDIT:
OK, I tested it thoroughly, you are right and I was wrong. The issue is caused by the radio app.
aarick said:
Mainly want to be able to hook up my Bluetooth tyre pressure monitoring system to my head unit.
The ownice seems to have their own TPSM kit, but would like to avoid investing further into more stuff that I already own.
I think right now.. I'll be happy with the joying.. But when development catch up for the ownice.. I might regret it..
Click to expand...
Click to collapse
I actually bought a C500 unit (waiting delivery) but I guess I can't test the bluetooth stuff for you without your sensors but I am not sure why they shouldnt work? I mean if it has an android app and it connects to bluetooth it should work, no?
On the other hand, I never had any case which would save me headaches if I had tire pressure monitoring. So I decided to not invest on one. (also I am not big fan of changing batteries how rarely it may be required ) But that is my opinion...
---------- Post added at 09:26 AM ---------- Previous post was at 09:10 AM ----------
@concept5400 I know this is an annoying response but I have to say... What about driving within speed limits so you wont need to run a speed camera app? I highly recommend this option, it is also safer.
But you can perhaps work around it if you run your YANOSIK app in your phone. Since you don't have to see it, you can even keep your phone in your pocket.

All joying websites are down??

Its almost spring and ill be taking umy summer car out soon and one is my todo projects is revamping the audio in the car as it's old and ancient. I was considering going with a non intel joying unit last year using an external usb dac and amplifier and thought id see whats new.. Seems like. More new options came to be and joying is gone????
Joying has moved to new official website: https://www.joyingauto.eu/
Gesendet ...mit Tapatalk
a_ahmed said:
Its almost spring and ill be taking umy summer car out soon and one is my todo projects is revamping the audio in the car as it's old and ancient. I was considering going with a non intel joying unit last year using an external usb dac and amplifier and thought id see whats new.. Seems like. More new options came to be and joying is gone????
Click to expand...
Click to collapse
Get the Intel. Faster than the px3 or px5 units. Plus the custom roms support the USB dac.
So rom and customization are now good on the intel models? Looks like their prices were bumped on the euro site compared to what they cost before. Whats the latest intel unit then. They all seem 2gb ram only still
a_ahmed said:
So rom and customization are now good on the intel models? Looks like their prices were bumped on the euro site compared to what they cost before. Whats the latest intel unit then. They all seem 2gb ram only still
Click to expand...
Click to collapse
2gb ram is plenty on the units, I haven't come across a need for more, even with tons of apps.
I've just discovered XSofiaTweaker for Xposed works on the Joying PX5, solves a lot of problems.
I really like them, the custom audio apps(Radio, etc) respect audio focus, unlike my experience with the MTC units. Going from Spotify to Radio and vise-versa, works as it should with no back end tweaking.
My Joying PX5 is turning out to be a pretty good, sub $300, deal.
XSofiaTweaker Updates.
nokill switch works, has bugs. Will test SofiaServerNoKill....works! use instead of nokill switch
unmute ch 4 works
ACC_ON/OFF works. (Thank you)
Prevent BT app on top, works!
carter.w.jason said:
I've just discovered XSofiaTweaker for Xposed works on the Joying PX5, solves a lot of problems.
I really like them, the custom audio apps(Radio, etc) respect audio focus, unlike my experience with the MTC units. Going from Spotify to Radio and vise-versa, works as it should with no back end tweaking.
My Joying PX5 is turning out to be a pretty good, sub $300, deal.
Click to expand...
Click to collapse
Can you detail how you installed Xposed on the px5? @surfer63
gtxaspec said:
Can you detail how you installed Xposed on the px5? @surfer63
Click to expand...
Click to collapse
Root info here. Had to use Kingoroot Windows method. Looking foward to finding a method that sticks after reboot(rare issue on these deep sleep units) and a method that doesn't need the cloud.
https://forum.xda-developers.com/showpost.php?p=75869637&postcount=6
Then installed with XposedInstaller_3.1.1.apk, HU then went through a very long reboot. Had to re-root whenever necessary, don't remember details or if it was needed. Though, no issues with Xposed.
https://drive.google.com/file/d/1XwS_puDVVfYpIFQzIeUJsCTjcFJAOL4W/view?usp=sharing
Nice thanks for the reply. Wish I had one of these units...the fyt stuff is really easy to work with. I'm sure a custom ROM can be made for the px5 fyt units as well.
carter.w.jason said:
Root info here. Had to use Kingoroot Windows method. Looking foward to finding a method that sticks after reboot(rare issue on these deep sleep units) and a method that doesn't need the cloud.
https://forum.xda-developers.com/showpost.php?p=75869637&postcount=6
Then installed with XposedInstaller_3.1.1.apk, HU then went through a very long reboot. Had to re-root whenever necessary, don't remember details or if it was needed. Though, no issues with Xposed.
https://drive.google.com/file/d/1XwS_puDVVfYpIFQzIeUJsCTjcFJAOL4W/view?usp=sharing
Click to expand...
Click to collapse
Sounds promising. That XposedInstaller, is that a "tweaked" version? Or does the Google Play version work just as well?
surfer63 said:
Sounds promising. That XposedInstaller, is that a "tweaked" version? Or does the Google Play version work just as well?
Click to expand...
Click to collapse
I recall it being a tweaked version. I can't remember were I got it. Have not tested Google Play version.
I'm pretty sure I found it in a MTCD thread, when I wrongly thought I had a MTCD unit.
surfer63, gtxaspec, your work has not gone unnoticed. I bought a Joying Intel unit last night. TWRP, USB DAC, BT, Custom ROM will be nice to have.
Question, How do you enter TWRP on a unit with no buttons?
carter.w.jason said:
I recall it being a tweaked version. I can't remember were I got it. Have not tested Google Play version.
Question, How do you enter TWRP on a unit with no buttons?
Click to expand...
Click to collapse
Your Google drive link doesn't work. Can you share the apk in some other way?
I think the only way for you is the reset hole. Reset the unit 3x and it will go into recovery mode. But that has no use on a standard Joying ROM as the recovery image doesn't have a menu or so. It only works on a Joying firmware usb-key/SD-card.
---------- Post added at 03:58 PM ---------- Previous post was at 03:29 PM ----------
carter.w.jason said:
I've just discovered XSofiaTweaker for Xposed works on the Joying PX5, solves a lot of problems.
I really like them, the custom audio apps(Radio, etc) respect audio focus, unlike my experience with the MTC units. Going from Spotify to Radio and vise-versa, works as it should with no back end tweaking.
My Joying PX5 is turning out to be a pretty good, sub $300, deal.
XSofiaTweaker Updates.
nokill switch works, has bugs. Will test SofiaServerNoKill....works! use instead of nokill switch
Click to expand...
Click to collapse
Nice to hear that the XSofiaTweaker in general works fine.
The NoKill behavior is strange. The hooks in the modules are the same and I just downloaded the ROM for your unit. The Sofia-1-C9-Server.apk (Sofia) is identical to 000000000_com.syu.ms.apk (PX5 Rom).
The "public static void killAppWhenSleep()" is identical as well.
surfer63 said:
Your Google drive link doesn't work. Can you share the apk in some other way?
I think the only way for you is the reset hole. Reset the unit 3x and it will go into recovery mode. But that has no use on a standard Joying ROM as the recovery image doesn't have a menu or so. It only works on a Joying firmware usb-key/SD-card.
---------- Post added at 03:58 PM ---------- Previous post was at 03:29 PM ----------
Nice to hear that the XSofiaTweaker in general works fine.
The NoKill behavior is strange. The hooks in the modules are the same and I just downloaded the ROM for your unit. The Sofia-1-C9-Server.apk (Sofia) is identical to 000000000_com.syu.ms.apk (PX5 Rom).
The "public static void killAppWhenSleep()" is identical as well.
Click to expand...
Click to collapse
Perhaps we are missing something that's supposed to be called from the other functions that killappwhensleep calls...which is why it's more than just one method fix in the small patches...??
Edit
Is he talking about the sofiaservernokill Xposed module or the sofiaservernokill modded app???

Extremely Weird Radio Issue on Funrover Head Unit

Hi all,
I've bought this unit for my Mazda CX-7 and had it professionally installed - it ran fine for a while and I was very happy with it.
A rather weird issue developed - on this unit the FM radio starts automatically when you turn on the ignition (there doesn't seem to be a way around this) and when the Radio App is running, I can hear the radio fine, and if I start another app such as Google Maps as long as the radio is running I can hear sounds normally. However if I manually exit the radio or if an app takes over audio (say Spotify for instance) the head unit goes completely silent, only to be revived again when I reload the Radio app. This of course makes the head unit useless for music and bluetooth as as soon as any of these apps are loaded the unit goes silent.
On the manufacturer's advice I reset the CANBUS settings and verified with them that the CANBUS was set right for my make and model of car - still the same result. Tried all CANBUS settings that even mentioned Mazda, no luck.
I really don't know how to start trouble shooting this - I have been provided four different firmwares by the manufacturer all of which exhibit the same issue which indicates to me it may be an underlying hardware issue?
Just a quick dump from my 'About Device' if that assists at all. Any help/suggestions greatly appreciated, any relevant logs or files will be quickly gathered and posted
Android Version
8.0
CPU Info
CPU: Intel ATOM 4QuadCore(x86), GPU4D Mali 450 MP4, X86
Baseband version
SF3GR_M-26.3_cpeg_rk-r2p_bc2-20160629_111639
System Info
APP 1024x600 2018-06-06 22:50:08
MCU Version
2018-06-02 12:16:25 FAD_(R76)_90_D1_V1.0_CAN(All)_AMP
CAN Version
Unknown
Car Application
Car Application Information
Serial number
00000000
carburngood said:
A rather weird issue developed - on this unit the FM radio starts automatically when you turn on the ignition (there doesn't seem to be a way around this) and when the Radio App is running, I can hear the radio fine, and if I start another app such as Google Maps as long as the radio is running I can hear sounds normally. However if I manually exit the radio or if an app takes over audio (say Spotify for instance) the head unit goes completely silent, only to be revived again when I reload the Radio app. This of course makes the head unit useless for music and bluetooth as as soon as any of these apps are loaded the unit goes silent.
On the manufacturer's advice I reset the CANBUS settings and verified with them that the CANBUS was set right for my make and model of car - still the same result. Tried all CANBUS settings that even mentioned Mazda, no luck.
Click to expand...
Click to collapse
That the radio starts on these units on reboot can't be changed. It is a hardware "feature". The radio chip and AMP-chip are "awake" before Android is even running. That is why you hear the radio after cold boot. And for your convenience the radio app is also started, but that is only a front-end that allows you to either enjoy and control the radio(-chip) or switch it off.
I don't think the CAN-bus has anything to do with this behavior, but I can be wrong.
I think that when you switch off the radio, also the AMP is switched off, or maybe even disabled.
If you switch off the radio, can you check in your Settings whether the AMP is still enabled? And maybe play/try a few things?
surfer63 said:
That the radio starts on these units on reboot can't be changed. It is a hardware "feature". The radio chip and AMP-chip are "awake" before Android is even running. That is why you hear the radio after cold boot. And for your convenience the radio app is also started, but that is only a front-end that allows you to either enjoy and control the radio(-chip) or switch it off.
I don't think the CAN-bus has anything to do with this behavior, but I can be wrong.
I think that when you switch off the radio, also the AMP is switched off, or maybe even disabled.
If you switch off the radio, can you check in your Settings whether the AMP is still enabled? And maybe play/try a few things?
Click to expand...
Click to collapse
The amp is still enabled in the car settings app if that's what you mean? Or are you thinking more on the hardware side?
carburngood said:
The amp is still enabled in the car settings app if that's what you mean? Or are you thinking more on the hardware side?
Click to expand...
Click to collapse
What I meant is if you switch Amp off (no Amp) and then back to the value it had, and then try spotify or whatever.
Just a guess.
surfer63 said:
What I meant is if you switch Amp off (no Amp) and then back to the value it had, and then try spotify or whatever.
Just a guess.
Click to expand...
Click to collapse
Thanks, gave that a go but no luck any other thoughts ?
Anyone else? Any logs or anything I can provide that may be useful?
*bump*
Last time
*bump*
carburngood said:
*bump*
Click to expand...
Click to collapse
Is the manufacturer not willing to replace it?
No they're not
I have the same problem. The radio worked without any problem until I made the factory reset ( wifi wont work ) and from then on I have only the sound from fm radio app.
Hi there, changing this setting worked for me - for me I had to choose RZC and RZC.AMP but try a few MCU upgrades in this setting and see what works for your vehicle.
I also found the Funrover guys to be very communicative so try contacting them directly - as part of the trouble shooting process they provided me a couple of firmware updates - including putting one together especially for me based on the issues I was experiencing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it does not work with me. I tried all the mcu options, I updated device using the software drovided by funrower, there is still no sound via mp3, bluetooth or video, only radio. MCU i think seted correctly because I have working steering wheel controls or mazda additional display... any other suggestions ??
Did you try all the MCU options with Mazda listed? I had to play around with a few and only RZC worked for me. If none of them work contact Funrover for their latest firmware and try the various Mazda MCU options.
New Funrover firmware ?
carburngood said:
Did you try all the MCU options with Mazda listed? I had to play around with a few and only RZC worked for me. If none of them work contact Funrover for their latest firmware and try the various Mazda MCU options.
Click to expand...
Click to collapse
The CANBUS doesn't work correctly in a recent Funrover Android 8.1 installed in an Honda Accord 7 (recent firmware). I have test several type of CANBUS and there is nothing to do. On the other hand, I have read in another thread that there is identical issue with a Seicane Android 8.0 and a similar Honda car. Perhaps it is a problem related to Android 8.x version. I wait for a response from Funrover but I don't expect much.
carburngood said:
I also found the Funrover guys to be very communicative so try contacting them directly - as part of the trouble shooting process they provided me a couple of firmware updates - including putting one together especially for me based on the issues I was experiencing.
Click to expand...
Click to collapse
Could you please share how to contact these guys? Is there a support email or something?
Hi all
Android 9.0 is out
Any of you installed latest firmware?
I have this head unit with android 8.0 for my kia sportage 2018
https://s.click.aliexpress.com/e/4cTppPHW
https://yadi.sk/d/UifaCXkWMhFmMg
Pacovich said:
New Funrover firmware ?
The CANBUS doesn't work correctly in a recent Funrover Android 8.1 installed in an Honda Accord 7 (recent firmware). I have test several type of CANBUS and there is nothing to do. On the other hand, I have read in another thread that there is identical issue with a Seicane Android 8.0 and a similar Honda car. Perhaps it is a problem related to Android 8.x version. I wait for a response from Funrover but I don't expect much.
Click to expand...
Click to collapse
After that, I have selected XP - Toyota - RAV4 - xxxx16xxxx in my Accord 7 Executive and it works almost completely. State of buttons with LED inside are not shown or shown inverted in the emergent screen. Thus, If a button has LED, I observe its state, but, when a button hasn't a LED, I observe its state on the emergent screen. It's a little yam but it's the only solution I have found with this unit.
On the other hand, I have selected a vehicle in the "China" subgroup and the screen has begin to shown many a many CANBUS codes on the screen. It seems to be a debug option. But unfortunately, I hasn't been able to repeat the sequence in order to activate this mode another time. It ocurred a day when I have tested all vehicle models and I have selected them very quickly.
Pacovich said:
After that, I have selected XP - Toyota - RAV4 - xxxx16xxxx in my Accord 7 Executive and it works almost completely. State of buttons with LED inside are not shown or shown inverted in the emergent screen. Thus, If a button has LED, I observe its state, but, when a button hasn't a LED, I observe its state on the emergent screen. It's a little yam but it's the only solution I have found with this unit.
On the other hand, I have selected a vehicle in the "China" subgroup and the screen has begin to shown many a many CANBUS codes on the screen. It seems to be a debug option. But unfortunately, I hasn't been able to repeat the sequence in order to activate this mode another time. It ocurred a day when I have tested all vehicle models and I have selected them very quickly.
Click to expand...
Click to collapse
After updating to Android 9.0, I have selected Honda Accord 7 and its emerging screen works fine. It seems that update solves the issue.
Android 9.0 firmware for funrover head unit
Hi all, I purchased this head unit with android 8.0 for my kia sportage 2018 https://s.click.aliexpress.com/e/4cTppPHW I need to know if i can update it to android 9.0 firmware. Best regards to all
forum.xda-developers.com

Categories

Resources