First post here. Apologies if this is posted in the wrong sub forum. I've read many related posts, but found nothing definitive nor exactly what I'm asking.
I purchased my head unit 3 months ago, and when brand new would pair OK with everything I tried, however my OBDLink MX device took many, many attempts before success. After a few days it no longer worked, so I removed it from the list hoping a re-pair would fix the problem. After endless attempts I can no longer pair the OBDLink MX (appears as named, uses changing 6 digit style to pair) nor another cheap ELM327 device (appears as CHX, uses a static 4 digit code). Both devices pair easily and work great with all other phones/tablets I try.
The manufacturer has given me limited support, and based on an OBD app giving me a popup stating "Bluetooth is not enabled. Do you want to enable it now?" (clicking Yes just hung I think) they believed the bluetooth board(s) were bad. They shipped me 2 new boards to solder in, a SD-968 and a REALTEK RTL8188 ETV.
Given all other devices (multiple phones and a 10Hz bluetooth GPS antenna) continue to work fine with the head unit, and the OBDLink MX worked at first, I am skeptical it's bad board(s). Am I wrong? I don't want to waste time or risk making things worse if this is nonsensical.
Tried so far:
1) swapped the pre-installed Torque app for the real one downloaded from Google Play (tried other OBD apps as well).
2) updated firmware in the OBDLink MX
3) reset wireless networks in the settings (doesn't appear to do anything)
4) installed an app to reach the Developer Options, played around with things
5) installed multiple BT status and reset apps, nothing changed
6) completed a full factory reset
Questions:
1) Does it sound like it's the board(s), should I solder them in now or try something else first?
2) Online specs say BT is MD-725, but my unit factory settings show SD-968 matching what they sent. Which do I want, does it matter?
3) REALTEK RTL8188 ETV looks like its for Wireless, not BT. Is it relevant?
4) Is there a known compatible firmware update that's likely to fix this?
5) Is it possible to brick parts of bluetooth with app options that the head unit BT implementation wasn't designed to handle?
My head unit was purchased from ISUDAR through Aliexpress. It says 7.1.1 but it actually came with 7.1.2 installed.
From my unit:
MCU:
MTCE_GS_V2.70_3
Oct 22 2017 18:59:52
Kernel:
3.0.101+
[email protected] #809
Build:
px3-userdebug 7.1.2 NHG47L eng.hct.20171025.180118 test-keys
From the website:
ROCKCHIP RK-PX3 Android 7.1.1
Quad-Core 1.6GB
DDR3 2GB
1024*600
STM32F091VCT
HITACHI 1200XH
MG1613S
NXP6686
GOC-MD-725 (Bluetooth Chip claims support HFP,HSP,FTP,OBE,OPP,SPP,A2DP)
TDA7388
CMMB/ISDB/DVB-T/DVB-T2/ATSC
No ideas or opinions on this from the experts that hang out here?
I installed the new Bluetooth chip and it didn't help, so now I'm looking for help identifying an app or ROM to flash. I see talk of whitelisting and tinkering with xposed but I'm a noob at that level of detail.
The Isudar brand and the model I have seem rare, so based on the specs above can someone help me identify the right ROMs that will work?
Seller sent me a new firmware version. Includes a .rar and .zip but no instructions to install. Unit has multiple USB ports but no SD card slot. Also has only touch screen with no buttons, so only options appears to be some sequence resetting with a paper clip through that little port on the front. Any help here on the likely sequence to install?
As a side note, I ordered an OBDLink SX cable for a USB solution to OBD and it works pretty well. Better PID/s rate and more stable connection. Given that so many people struggle with BT OBD and these head units are installed (unlike a phone), wire it up and forget it.
Related
hi guys
new to the forum, hopefully someone will be able to help me
my unit has stock MTCC-KLD6-V2.97 Aug 02 2016 with a RK3188 and 1024x600 screen
Firstly the Bluetooth is not working, quite a lot of apps hang at the part where it try's to turn the BT on, especially one app i really need to work.
I honestly don't know what model of BT chip is installed in the head unit, apparently its BT 4.0 as listed on there website
I have been into the factory menu and changed the BT from WQ_BC6 to WQ_BC6B (as suggested somewhere in this forum) but it has made no change and the BT is still hanging at powering on.
Eonon have told me that the Bluetooth only work with devices that don't require a pin and the radar detector device i need to connect does not require a pin but still it does not work.
Not quite sure if eonon has set the setting wrong and i need to change it or i need to goto a custom rom or I need to pull the unit apart to find out.
Found someone else having trouble getting there ALPconnect app to work aswell on these units, in know ALPconnect wont work on older unit like the 4.4.4 as they only had BT 2.0 and the ALP BT only supports 4.0, but this android unit has 4.0 so it should not be a problem but it is.
sterod said:
The app I use, ALPConnect, does the exact same thing. Fortunately, the hardware on mine includes a hardwired speaker and GPS setup that work standalone. The benefit of the app was to get a nice big visual notification of a trap, as it would come into focus, duck the audio and play an alarm. It would also report the frequency of the radar and the type of laser hitting me. While I can get by without all that, I can't have the music blaring like I usually do, as the little speaker is only so loud and the Joying head unit doesn't have Mute Input wire to duck the audio.
While this is going slightly off topic, you may want to look into the AL Priority, it can interface with your V1 too and you will also gain laser protection. This thing has saved my a** countless times and paid for itself already many times over.
Click to expand...
Click to collapse
Secondly the control menu in the android head unit for accessing the cars buttons via cambus does not work, all steering wheels button seem to communicate back and work, but i cannot set my clock on my mazda 3.
Also have noticed that the radio wont mute when notification occur or when using other apps like google maps, no way to set the different volumes in this stock rom. Have played around with the factory menu volumes but it makes no diffidence.
Is it viable and worth changing to a different ROM, like Malaysk? or should i message eonon?
any help would be much appreciated
thanks
shane
I'm having exactly the same issue with a Pumpkin MTCC-KLD6-V2.91. (RK3188/1024x600)
The device I want to pair with appears in Bluetooth settings (with a phone icon?) but connecting to it does nothing. It's just a Bluetooth SPP device, like so many other devices.
Malaysk's ROM (from 7/25) doesn't change anything here.
Any suggestions would be most welcome.
-Zandr
zandrm said:
I'm having exactly the same issue with a Pumpkin MTCC-KLD6-V2.91. (RK3188/1024x600)
The device I want to pair with appears in Bluetooth settings (with a phone icon?) but connecting to it does nothing. It's just a Bluetooth SPP device, like so many other devices.
Malaysk's ROM (from 7/25) doesn't change anything here.
Any suggestions would be most welcome.
-Zandr
Click to expand...
Click to collapse
Waiting on a reply from Eonon, but initial news is not good.
Some serious BT issues in this model the MTCC
Anyone know if any Malaysk's Rom's avalable for the MTCC-KLD6-V2.91 that have no BT issues
I'm having the same issue, though my unit (MTCC KLD6) does not show any devices at all to pair with, and the car unit does not appear on my phone.
I'm wondering - if I take a usb BT dongle and attach it to the usb cable, would that work?
I think it might be another issue with your BT, it should connect to your phone at very least.
Have you had a look in your factory menu to see if the MCU has the Bluetooth option set?
Password for me was 126
Unfortunately the unit does not support external USB Bluetooth and probably never will, unless the manufacturer MTC/Klyde adds the required drivers to the unit or a Awesome developer by some stroke of luck here adds it to the unit. I doubt to see the feature in this unit
Sent from my iPhone using Tapatalk
Thanks for the reply. Yes, i checked to make sure Bluetooth was enabled in the system settings. I've tried a few of them (change setting, reboot, attempt pairing), i guess the next step is to try them all one by one to rule that out. I've sent an email to the seller to see if they have any ideas.
The vendor told me to connect the Key-1 & Key-2 wires from the canbus to the car, not sure why they'd think that would solve BT issues?
Did this fix the issue? I'm unable to see any Bluetooth devices and other Bluetooth devices don't see it.
Sorry to dig up an old thread
I have the Eonon GA2180a (android 10) - and having similar issues to here
I want to pair a bluetooth remote (read, steering wheel controls) to the head unit, but the bluetooth search just shows blank! I can connect to it using my phone but it appears some things are hidden to connect to with these android units? Looks like the bluetooth 'app' is the only way to connect too, theres nothing in the android settings to access a bluetooth menu or anything.
Did anyone get anywhere with this ?
cheers
I installed two different models of Joyings newest PX5-based head units. Both are the 7 inch screen 4GB RAM / 32GB flash double DIN model with flat buttons on the left edge.
Please note that as of May 2018, there appear to be multiple new 4GB / 32GB Joying head units have different internal hardware and are not compatible with each other or with the PX5 2GB Joying head units.
JY-UM128N4PX5 is a QD unit
JY-UO128P4 appears to be an FYT unit
Buyer beware. My recommendation is AVOID the QD based units and seek out the FYT units.
See below for more details.
The following information is for JY-UM128N4PX5. Further down the page is information for JY-UO128P4.
=============== JY-UM128N4PX5 =================
Came with Android 8.0.0 installed.
APP Version TP6735 0.0.65
MCU Version TP6735 4.40
Kernel Version 4.4.103
Master password:126
Password for changing logo:0000
Password for changing UI:8086
So far I have noticed the following:
The unit does not trigger the amplifier turn on signal wire - the orange and black wire labeled AMP-CONT always measures zero volts on my voltmeter. Workaround is to use either the antenna signal wire, or the ACC power signal wire, to turn on your amp. Joying is aware of this issue.
Sleep does not work. The unit shuts down completely about one minute after you turn off the vehicle's ignition. It doesn't sleep and then come back on instantly like my Intel-based Joying unit. Boot time is about 20 seconds. Joying support now says that sleep is not supported on the QD units.
I cannot find the radio settings in the new radio app. You used to be able to slide the bar at the bottom of the radio app to get to settings. Now in Android 8, there are a couple of radio settings that have been moved to the main android setup dialog.
Some of the functionality of the former car settings app has been moved to the android settings dialog. But not everything is there - for example this is where I was looking for the ability to tell the unit to toggle the amplifier signal wire. I could not find any such setting.
AM radio reception is non-existent - static on all AM channels.
FM reception is good, but I cannot figure out how to get the FM Radio to enable display of song and station information - this used to be under RDS settings, which no longer exist.
Bluetooth calling works fine. Seems more stable than my older Intel-based unit.
Sound quality is good - I am using an external amplifier.
The logo set up is missing Porsche and Saab Logos. My Intel-based Joying unit had these. Easy enough to load my own custom logo.
The unit ships with Joying's "Launcher3" selected. On the home screen, the labels of the bottom row of icons are cut off. The screenshots on Joying's website show the same thing. The joying2 launcher is missing.
If you reflash the unit, the vertical keypad on the left side of the unit gets un-mapped and stops working. Fix is to go into car settings and remap it.
========================= JY-UO128P4 ==================
Android Version 8.0.0
Build Number px5-userdebug 8.0.0 OPR5.170623.007
System Info APP 1024x600 2018-04-27 21:42:36
MCU Version 2018-01-23 10:59:33 JY_(R68)_R-86C-096I-NC-NP-1.0-P12S
Passwords:
Factory settings: 3368
Developer Options: 3368
Reset: 3368
Password for changing Launcher:8086
Password for changing screen current:
So far I have noticed the following:
The software on the JY-UO128P4 is very close to that of my older Joying Intel based system.
The developer has replaced all of the system settings screens native to android with their own settings screens. Not super cool. All of the car settings and android system setting are now intermingled.
Upon unboxing, the JY-UO128P4 has only a single Wifi antenna wheras the JY-UM128N4PX5 had two (diversity) wifi antennas. I have not tried to compare reception differences.
The amplifier turn on signal now works as expected (AMP-CONT wire correctly signals 12V when unit is active)
Sleep works as expected
AM radio reception works weakly.
The FM radio application works as expected. Radio app settings are accessed within the radio app. It's possible to enable RDS for song and station ID within the radio app.
All of the joying launchers are available - I prefer launcher 02 and it's available on this unit.
Many more car logos are available on the system. Porsche logo was built-in.
The only things I've noticed so far that are worse with the JY-UO128P4 than the JY-UM128N4PX5
The unit suffers from the android 8.0 bug on Joying where all of your google contacts are deleted if you allow your account on the head unit to sync contacts with google.
As noted above - the native android settings panels are all removed.
The app for setting the color of the buttons on the side panel is limited to pre-determined solid colors - yellow, white, red green etc. On the JY-UM128N4PX5 you could select and set any RGB color, which made it possible to match the button illumination to your other dashboard lights.
As I learn more, I will post more.
ddruker said:
I just installed Joying's newest PX5 head unit. It's the 4GB model.
It came with Android 8.0.0 installed.
APP Version TP6735 0.0.65
MCU Version TP6735 4.40
Kernel Version 4.4.103
So far I have noticed the following problems:
The unit does not trigger the amplifier turn on signal wire - the orange and black wire labeled AMP-CONT always measures zero volts on my voltmeter. Workaround is to use either the antenna signal wire, or the ACC power signal wire, to turn on your amp. I found another post of someone else who had this same issue.
I cannot find most of the passwords needed to set up the unit. The master password is 126 - I found that by watching a joying video. But I cannot find the second level passwords for changing the logo, changing the launcher, etc. Anyone have the other passwords?
The utility to change the color of the buttons on the left side of the unit works, but the buttons do not illuminate one the unit is booted.
I cannot find the radio settings in the new radio app. You used to be able to slide the bar at the bottom of the radio app to get to settings. Now in Android 8, there are a couple of radio settings that have been moved to the main android setup dialog - but for example I cannot find a setting to turn on the functionality to identify song and station names.
Some of the functionality of the former car settings app has been moved to the android settings dialog. But not everything is there - for example this is where I was looking for the ability to tell the unit to toggle the amplifier signal wire. I could not find any such setting.
I cannot figure out how to change the launcher - with the default launcher the lower row of app icons is only half visible on the screen.
Who else has a new Joying Android 8 unit - what else are you seeing? Has anyone found solutions to the items above?
Click to expand...
Click to collapse
I have had several back and forth emails with Joying support in the last couple of days.
They are trying to find the passwords for their new units under Android 8. Support didn't know. They had me try 00000 and 123456, neither of which worked. I told them the main password is 126 - they didn't know this either. I still need passwords for all of the second level settings - change the launcher, change the logo, see if there are more developer options for car config, etc.
They are apparently aware that the AMP-CONT lead to turn on the external amplifier does not work. They recommend connecting the accessory wire from your vehicle to the amp signaling wire instead, so the amp will turn on when you turn your key to the accessory or on position, bypassing the head unit.
They acknowledge there are no detailed settings available for the radio under Android 8 in the radio app. So there is no way to turn on station or channel ID for US customers.
I also let them know about another radio issue - FM Radio reception is normal, but AM reception is awful to non-existent.
Google maps is ok, directions from Google maps are mixing with other audio ok.
Feels like Android 8 on the new Joying 4GB units isn't quite ready for prime time yet... Has anyone tried to upgrade a 2GB Android 6 unit to Android 8 now that the Android 8 files are on Joying's website? Do you see the same behaviors, or am I seeing hardware issue with the brand new 4GB units? I suspect it's all software, but would be nice to know.
ddruker said:
Feels like Android 8 on the new Joying 4GB units isn't quite ready for prime time yet... Has anyone tried to upgrade a 2GB Android 6 unit to Android 8 now that the Android 8 files are on Joying's website? Do you see the same behaviors, or am I seeing hardware issue with the brand new 4GB units? I suspect it's all software, but would be nice to know.
Click to expand...
Click to collapse
The 2GB units are not compatible with the 4GB units. They need different hardware drivers and different MCU firmware as the firmware in the 2GB units is from FYT. I forgot the manufacturer of the 4 GB units but @gtxaspec knows.
There is no downloadable firmware yet for the 2GB units.
hi, i've the same unit and the password was noted into the user manual, it's 3368.
If you buy Joying android 8.0 unit the SKU like:JY-UO135N4PX5 or JY-UOS03N4PX5,password as below:
Master password:126
Password for changing logo:0000
Password for changing UI:8086
TomTom
It seams to be so hard. Again an Android HU, where TomTom navigation does not work. It let's me download the maps, but after that it crashes every time I try to load the application.
I can confirm these passwords are correct:
Master password:126
Password for changing logo:0000
Password for changing UI:8086
Other findings so far:
The illuminated buttons do work - they sometimes take a few seconds to come on after your illumination wire signals with 12V.
The logo selection with this new unit does not include Porsche or Saab. You can still upload your own custom logos.
I updated the unit to the latest (2018-4-20) release on the Joying website which is supposed to include optimizations and Zlink and my unit is now hanging at the Android text logo (right after the animated Android logo). I sent a note to Joying support for help and will also wait for a few hours to see if it comes back to life.
ddruker said:
I can confirm these passwords are correct:
I updated the unit to the latest (2018-4-20) release on the Joying website which is supposed to include optimizations and Zlink and my unit is now hanging at the Android text logo (right after the animated Android logo). I sent a note to Joying support for help and will also wait for a few hours to see if it comes back to life.
Click to expand...
Click to collapse
The same happened to me
After writing about 25 emails with Joying support I had to reflash the whole system ... loosing all my data.
For now I am really not going to try any more updates from Joying with this unit.
Really hoping for a Custom Rom & Root for this unit.
I have one of these as well. Any one find where the setting is to make the sleep mode last longer(2hrs) before it full shuts down? it seems to be locked on 30sec currently. Also it wont pair with my OBDlinkMX BT dongle. in the older MTCD units, making the BT password 1234 let you do it, but not here. anyone have any luck with BT OBD dongle pairing?
I was really leaning towards getting this unit but have been holding off because I wish it had Bluetooth 5.0, maybe I should wait a little longer since it seems to have a fair amount of bugs. I know a lot of people are happy with the Xtron since it has all the best features I just really prefer to have the buttons on the left like this unit has. Looking forward to seeing if you guys can get this squared away
peregrines said:
The same happened to me
After writing about 25 emails with Joying support I had to reflash the whole system ... loosing all my data.
For now I am really not going to try any more updates from Joying with this unit.
Really hoping for a Custom Rom & Root for this unit.
Click to expand...
Click to collapse
I was able to get my unit working again by reflashing. It took about 10 tries with three different USB cards but it finally worked. Joying support provided a file that included a system image and a Window-based chinese language USB card writing programs, along with a word document with instructions. You build the USB drive and then plug it into the left hand USB connector, and click the reset button on the front of the unit. It loads, then tells you to remove the USB drive, and then if you are very lucky it will reboot into Android.
After re-flashing, the vertical keyboard on the left side of the unit did not work. Turned out the mappings had been erased. Fix is to remap the keys - there is an option in car settings.
Current issues still present in the unit seem to be:
Unit shuts off entirely after 30-60 seconds instead of sleeping when you turn off the vehicle. My intel-based unit sleeps for several days.
No AM radio reception - static on all channels.
No way to turn on song or station identification in the radio settings for FM.
AMP-cont signal wire does not work. I've worked around by wiring my accessory wire directly to my amp's signaling wire.
Have not tried Torque and Bluetooth ODBII reader pairing yet - on my list for this weekend.
So, it's not just me...
I purchased a JY-UM135N2PX5 (PX5 2G/16G) with Android 6.0 mid to late March.
I had it on my bench through April, testing and configuring it prior to install.
After trading emails with Joying tech support, I was sent an Android 8.0 update to address a Zlink/iPhone issue.
I started my install in the car today, and discovered "no sound". I guessed that the AMP-CONT wasn't turning on the OEM amplifier. I rechecked the cables, which checked out just fine. Tried a Joying JY-UM135N2 (Intel Sofia 2G/32G Android 6) on the same harness, and it functioned as expected (turned the OEM amplifier on and had sound). I took them both back to my bench and noticed that the "AMP-CONT" on the PX5 unit did not appear to have 12V on it, while the Sofia unit did.
I did not leave the non-functional PX5 unit in the car long enough to see any other issues.
I am curious if I were to revert back to Android 6 on the PX5 unit, if it would fix the AMP-CONT issue (at the cost of breaking the Zlink/iPhone functionality)
ddruker said:
I was able to get my unit working again by reflashing. It took about 10 tries with three different USB cards but it finally worked. Joying support provided a file that included a system image and a Window-based chinese language USB card writing programs, along with a word document with instructions. You build the USB drive and then plug it into the left hand USB connector, and click the reset button on the front of the unit. It loads, then tells you to remove the USB drive, and then if you are very lucky it will reboot into Android.
After re-flashing, the vertical keyboard on the left side of the unit did not work. Turned out the mappings had been erased. Fix is to remap the keys - there is an option in car settings.
Current issues still present in the unit seem to be:
Unit shuts off entirely after 30-60 seconds instead of sleeping when you turn off the vehicle. My intel-based unit sleeps for several days.
Poor AM radio reception
No way to turn on song or station identification in the radio settings.
AMP-cont signal wire does not work. I've worked around by wiring my accessory wire directly to my amp's signaling wire.
Have not tried Torque and Bluetooth ODBII reader pairing yet - on my list for this weekend.
Click to expand...
Click to collapse
Would you be so kind as to share those files with us? This would be a good starting point for further testing and research. Simply upload to a hoster like mega.
z0rn said:
Would you be so kind as to share those files with us? This would be a good starting point for further testing and research. Simply upload to a hoster like mega.
Click to expand...
Click to collapse
Here is a link to the zip file from Joying with the firmware image for reflashing, their USB drive utility, and instructions...
https://drive.google.com/open?id=13HXHRRfuduhIYV41pjQlvsJ0o3xesNBC
Here is the reply I got from Joying support this morning in regards to the open defects I am tracking with the unit. I suspect that all of this will get fixed in subsequent software releases, it's relatively obvious stuff. Can anyone confirm if these same issues exist in the Android 8 builds on Joying's 2GB PX5 head units, or are these unique to the newest 4GB units?
Dear friend,
Please noted :
1) sorry that your system is different with Intel head unit , it do not have fast boot feature . so it will completely off .
2) for the AM receptions is bad , you need to set the proper time and zone . also the radio area choice .
3) sorry, the head unit you purchased do not have the RDS setting .
4) for the am-cont not voltage , please connect the ACC (red wire ) to your amplifier wire . then can offer 12V .
Hope your noted .
Candy
ddruker said:
Here is the reply I got from Joying support this morning in regards to the open defects I am tracking with the unit. I suspect that all of this will get fixed in subsequent software releases, it's relatively obvious stuff. Can anyone confirm if these same issues exist in the Android 8 builds on Joying's 2GB PX5 head units, or are these unique to the newest 4GB units?
Dear friend,
Please noted :
1) sorry that your system is different with Intel head unit , it do not have fast boot feature . so it will completely off .
2) for the AM receptions is bad , you need to set the proper time and zone . also the radio area choice .
3) sorry, the head unit you purchased do not have the RDS setting .
4) for the am-cont not voltage , please connect the ACC (red wire ) to your amplifier wire . then can offer 12V .
Hope your noted .
Candy
Click to expand...
Click to collapse
Are they serious? I would suggest to try the Malaysk Rom, i guess your units are MTCD and MTCE devices so maybe this rom would support the missing software like rds and the other hardware not supported by Joying
https://www.youtube.com/watch?v=WWvgrcn_As8
https://forum.xda-developers.com/an...-malaysk-roms-px5-2-4-gb-8-0-android-t3762724
Good luck!
Flemischguy said:
Are they serious? I would suggest to try the Malaysk Rom, i guess your units are MTCD and MTCE devices so maybe this rom would support the missing software like rds and the other hardware not supported by Joying
Click to expand...
Click to collapse
These units are NOT MTCD/E. Do not use the Malaysk ROM.
---------- Post added at 07:08 PM ---------- Previous post was at 06:53 PM ----------
ddruker said:
Here is the reply I got from Joying support this morning in regards to the open defects I am tracking with the unit. I suspect that all of this will get fixed in subsequent software releases, it's relatively obvious stuff. Can anyone confirm if these same issues exist in the Android 8 builds on Joying's 2GB PX5 head units, or are these unique to the newest 4GB units?
Dear friend,
Please noted :
1) sorry that your system is different with Intel head unit , it do not have fast boot feature . so it will completely off .
2) for the AM receptions is bad , you need to set the proper time and zone . also the radio area choice .
3) sorry, the head unit you purchased do not have the RDS setting .
4) for the am-cont not voltage , please connect the ACC (red wire ) to your amplifier wire . then can offer 12V .
Hope your noted .
Candy
Click to expand...
Click to collapse
I have a 2GB Android version 8.0.0 unit, but my unit is a FYT based unit like the Sofia 3GRs, unlike yours which is a QD unit.
Mine does have fast-boot as my unit is a FYT based unit, using the same hardware/SOM as the Sogia 3GR intel units.
I never used AM-reception. I wouldn't know, but I know from previous users on Sofia 3GR that they also complained about the AM reception
Which RDS-setting? This is so confusing and so not concrete. RDS is a complete set of functions. The syu/FYT based software on the FYT based units support RDS-PS, RDS-PTY and RDS-TA/TP. The latest firmware versions on FYT units (Sofia 3GR and my PX5) also support RDS-RT. They do not support RDS-AF. They implemented "something" like AF. If you use that option it does not select the Alternate Frequency of your radio station, it selects the strongest signal it can find of any station. Note that it is the software. The radio chips in all these units support the complete RDS set of functions.
Don't know about the the amp-cont wire.
You ask about and mention AM and about RDS. I hope you know that RDS can only be used on the FM signal. RDS is not available for AM.
Help
Heres a link I need help to identify my android head unit
https://app.box.com/s/o90d0lnjrqqlek5w1q6lekaj5dgsa20y
Traww said:
Heres a link I need help to identify my android head unit
https://app.box.com/s/o90d0lnjrqqlek5w1q6lekaj5dgsa20y
Click to expand...
Click to collapse
You have an Allwinner T3 chipset in your unit.
Do not use a Joying thread to ask a completely off-topic question.
I've received the same unit, facing the same issues as the OP.
Also the localisation in my language is quite poor.
surfer63 said:
These units are NOT MTCD/E. Do not use the Malaysk ROM.
Click to expand...
Click to collapse
I've bought this unit in the hope that it would be compatible with custom ROMs.
Are you saying that the unit MCU is almost unknown and that no custom ROM would be available in the near future?
Hi. This will, iirc, be my first ever post here but have browsed the forum for a while for Android things. I have just bought a generic Android head unit:
(ah, no links for me...)
2Din-7in-Android-7-1-GPS-Navi-RDS-FM-Radio-Quad-Core-Car-Stereo-MP5-Player-Cam-
This model, but without a camera since I already have a cam. Anyway, this is not the issue. I am trying to get info about it and the seller is not exactly full of help. I suspect they don't really know much about the system. I have got it working fine: Radio is good, installed Poweramp, Sygic navigation etc etc. I also installed Torque pro as I have used it on my phone. My problem is that when I go into the settings there does not appear to be any option for bluetooth. There are very few options in settings in fact and I cannot see any way to pair up my bluetooth obdii unit to the head unit.
I realise I have not given a lot of info here, but there is not much info available from it though. What I can find is:
About Car Machine
Model K6_13_LH
Android 7.1
Kernel Linux Ver 3.4.67
System: K6_13_LH_V2.0.1_20181107
MCV: CM_0.4730.0_180918_17:36
APP: MT1002_V1.0.9
Bluetooth Aug141108
it has an ARMv7 Processor rev 3(v7l) with 1GB ram and 16GB nand flash.
The steering wheel controls don't work either and I know my canbus adaptor is working as it worked fine on the last unit I had.
Any help you guys might be able to offer in the way of pointers for O.S. or even how to get the proper android settings on the machine would be really useful. Ta in advance, and I was not sure if this was the correct place for this post so if not could a mod shove it where it should be, if not here.
[Update]
Just ran some diagnostic tool on the unit. Hmm, It is reporting Android 7.1_KitKat! I suspect this is why the settings menu does not look right... It's also showing a build of ALPS.KK1.MP1.V2.11 so I might be able to find something here for the unit?
I'm guessing that's a no then!?
Hello man.
I bought plenty of android head units.
those devices is a BLUETOOTH READY,
which means ., You're able to connect to your phone and check address book and make phone calls also listen to music through the BLUETOOTH app in menu, NOT TO BE FOUND IN SETTING.
you can think about it simply it's a Bluetooth that's independent from the android system.
so you'll not be able to find and connect to OBD's tools whatsoever.
hope this helps
regards.
I have the same unit. The cpu is MT6582 it's a quad core.
Kingroot failed many times (said it clearly) but, after some reboots, finally succeeded (without saying it clearly).
Once root, I used a shutdown app to boot into recovery, but the buttons are not responding. It also managed to boot into fastboot mode,
but my pc doesn't see the device (I've tried both usb ports). Maybe it needs a driver ?
NOTE: I tried to post a fully detailed write-up of my issues, with screenshots and links, but because I'm a new member the forum won't let me post this with those URL's in the post. Since there's no way to upload and attach images, I'm happy to provide all of this via alternative means, or update the post with the original links if an admin is willing to remove this restriction from my account (I promise I'm not a spammer of any kind)
Hi all,
First time poster here with some unique issues (at least for me) with one of the newer Android stereo units. (AA0495B)
I've already contacted AUTOPUMPKIN customer support and they were absolutely no help in solving this; I've also done my own testing and tinkering but haven't been able to get anything working so I'm hoping someone here with more knowledge of these Android units can help.
Late last year I got an AUTOPUMPKIN Android 9.0 unit (AA0495B) for my track car; the main reason I got it was to run my track timer apps directly from my car instead of having to run it from my phone in a dash mount as most do; the specific app I use is Harry's Laptimer. Now obviously this app was programmed with phone use in mind, but after a bit of doing I was able to get it working completely on the Android stereo unit, so my questions aren't around that app, but rather some secondary hardware related issues using the unit. Overall this stereo unit has been great and free of any major issues like ones I've seen on other XDA posts about other Android stereo units. The app works, connects to my GoPro over WiFi flawlessly, and records track sessions and syncs to video perfectly. My issue is that the HLT app also supports connecting to other kinds of devices via bluetooth for additional data capture, such as the XGPS160 for obtaining more accurate GPS lap data (The 160 captures GPS coordinates at 10Hz rather than the 1Hz of the AA0495B and most Android phones) and I'm having issues getting the stereo unit to connect to the XGPS160 device.
There are several problems in getting this to work, but to keep things simple I'll start with the first problem and then work down layer by layer as each issues is solved; hopefully, if we can get it to work, this thread can serve as a guide for others to get this stereo unit to connect to this and other GPS devices.
PROBLEM #1 - Getting the AA0495B unit to pair and connect to the XGPS160 over bluetooth
So obviously the first step is to get the XGPS160 connected to the head unit over BT. The instructions for this are fairly straightforward and in the XGPS160 manual which I followed. The AA0495B unit has its own custom UI for managing connections to bluetooth devices rather than using the native OS bluetooth menu. The native OS bluetooth menu can be found in the system menu, however when attempting to use it to pair to devices, no devices are detected. If we instead use the main menu Bluetooth button to open the custom BT interface and then hit the search button to scan for devices, the XGPS160 shows up when ready for pairing, so we know the BT radio is picking it up at least. I then click on the name of XGPS160 and press the Connect button to pair the device. After a few moments, the device name now shows as an "available device" meaning it is paired to the unit (at least in theory). We can then click on the name and click the Connect button again to attempt to connect the device. This is where it stops, as it never shows as being connected. For comparison, the UI does show blue "connected" icons when the stereo is connected to my Galaxy S9. It appears this custom BT UI will only show the blue symbols when the connected device is a phone; I also have an OBDII dongle paired and it will never show as connected from this screen, however apps like Torque Pro are able to make the stereo unit connect to it and pull OBD data from the car. I was hoping that maybe this was a case of this custom UI simply not showing that the device was connected when it actually is, like the OBDII device. I attempted to run the "Bluetooth GPS" helper app to see if I could get it to connect; however the XGPS160 doesn't even show up in the list of available devices, whereas the "OBDII" dongle is listed even though it's not currently connected. Presumably this menu is pulled from the OS's list of paired devices, so if I had to guess, perhaps the XGPS160 isn't really paired even though the Pumpkin custom BT UI shows it as paired?
In contrast, I was able to connect the XGPS160 to my Galaxy S9, update its firmware via the phone app, and install and run the helper apps to pull data from it, so there aren't any problems in the device itself, but appears to be an issue with the stereo unit.
Here are the About Machine details from the unit for reference:
Builder Number: 201907091031
Kernel Version:
4.4.167
#44 Mon 07 1 10:07:31 CST 2019
uboot-06 28 2019-18:00:06_M11 1024x600
MCU Version: CSN2_06252019_163051
CPU and Memory size:
64-bit 8-core Cortex-A53 1.5GHz
4GB TC:29C TGT:29C F0:1200M F1:816M
Model & Hardware: PX5
Android Version: 9
So with all that, does anyone have recommendations on next steps? I'm a software engineer by background (though not in smart devices) so I shouldn't have trouble performing any troubleshooting steps necessary.
thanks!
Figured out the issue
Circling back to update this one for anyone else who comes across this issue. Here's the response I got from Autopumpkin support
"After checked with our engineer,sorry to tell you that our headunit cannot connect to SkyPro XGPS160.the reason is car stereo Bluetooth is equivalent to a Bluetooth headset and it can only be connected passively.sorry about this."
So yeh, seems they cheaped out on the bluetooth module and that's the problem. Now if only I could find a way to disable it and use a USB bluetooth dongle I have instead.
I also have the problem with a Kingbaets K1+ Android 8.1
Unfortunately, it is only possible to establish the Bluetooth connections up to Android 6.0.
Later Android versions have a "castrated" Bluetooth interface.
My consequence was that I bought an OWNICE C500+ with Android 6.0.
With this device, Bluetooth hardware can pair with PIN input.
It works perfectly.
Dealers at aliexpress
Hi, does anyone know how to disable ksw Bluetooth? I can only add phone using their overlay tool, the android native built in Bluetooth is disabled and blocked by kswcarproject.
My goal is to add an Xbox gaming controller , I would rather use the native android Bluetooth settings if I can or unlock ksw BT to allow any device to connect to the HU. With ksw BT I have tried both pin code 0000 and 1234 without success, the error message I get is paring failed or rejected.
thanks !!
am I the only one having this issue to pair a non phone device to android Head unit ? There must be someone else who solved this.
I think it's more the opposite, all these headunits are crippled around the BT and only support phones and some OBD2 devices. Not sure anyone has a solution outside of totally custom firmware.
getting access to setting is not the issue, that's simple enough, it's that the BT is crippled at lower level.
gottahavit said:
I think it's more the opposite, all these headunits are crippled around the BT and only support phones and some OBD2 devices. Not sure anyone has a solution outside of totally custom firmware.
getting access to setting is not the issue, that's simple enough, it's that the BT is crippled at lower level.
Click to expand...
Click to collapse
here is what my tests show. If I restart the unit and quickly get into applications and terminate running applications kswcarproject and ksw BT, I get around 1 minute to enable Bluetooth in android and I can search for devices, I find my Bluetooth devices but somehow kswcarproject or any other service is deactivating native Bluetooth and I don’t have enough time to pair any unit. However this is evidence that the technology is capable, we just need to investigate how to disable services or whatever task that is forcing native bluetooth off after reboot. But I do not have knowledge in android infrastructure , but I can help in running tests and dig out logs
You can install default android settings or launchers like CarWebGuru or Nova give you these settings, there you get full BT settings, scan, probably even pair your device, but it won't connect and work. I found this on my IDoing UIS7862(FYT). BT is crippled. I believe they have done the same with 4g SIM connections.
It does work here is the evidence that it works:
And how to do it:
BMW 3-Series and 4-Series Forum (F30 / F32) | F30POST - View Single Post - 10.25" Android 10 HU discussion
Forum for BMW 1-Series 3-Series 5-Series 7-Series M3 M5 M6 Z4 X1 X3 X5 X6 Z2 Z4 325i 330i 335i 535i 550i 755i BMW Forums
f30.bimmerpost.com
Bluetooth is, yes, “crippled” after the device is completely booted up. So we just need to identify what service is blocking or crippling Bluetooth.
Hello guys,
I recently purchased a car that has the Qualcomm snapdragon 625 msm8953 NBT headunit for BMW 7 series (Native Android 10 unit).
I have tried everything to connect carplay but Zlink keeps saying waiting and won't take my iPhone.
I have read online that i need to update the firmware of the device, the version I have is KSW-Q-Userdebug_OS_v2.0.0.
Can someone please tell me where i can find the firmware update for free.
Thank you,