Database Users

Eonon Android 5.1.1 bluetooth issues & canbus issues

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

Joying Head Unit (4GB, PX5 Octa Core) - Bluetooth Tethering

Hi All,
Recently purchased and installed a Joying head unit (4GB, PX5 Octa Core) (link to product)
As this head unit runs android I am trying to tether the mobile data on my android mobile over to the head unit via the bluetooth tethering function. Problem is I dont think its working. Does anyone have any experience with this or know how to get it working?
Steps:
On the mobile, make sure its connected to mobile data
On mobile, turn on bluetooth tethering
Pair mobile and head unit via bluetooth
Still no internet access

Can you access data via hot spot? Make you mobile device a wifi hotspot and connect the headunit to your hotspot.
Sent from my ONEPLUS A5010 using Tapatalk

chper said:
Can you access data via hot spot? Make you mobile device a wifi hotspot and connect the headunit to your hotspot.
Click to expand...
Click to collapse
Yeah I tried this and it works fine. I just though it be better to use bluetooth tethering seeing as the phone is already hooked up to the head unit via bluetooth. Using the WiFi hot spot option just adds another process to the mix.
Because Joying remove a lot of the standard android setting I was thinking there might be a way to access the default android settings again to be able to play around with bluetooth properly. While writing this thread up however I did email Joying about the ability to bluetooth tether and their response was:
"Our head unit can not support Bluetooth tethering"

Hi, I am trying to achieve the same solution however I do not think it's possible. My understanding is that the bluetooth connectivity allowed by the hardware in the head units doesn't cater for the 'full stack' of bluetooth functions, so we're stuck with telephony and audio only with no data transfer.
I would *really* love to be corrected though! It would be great if it could be solved by software alone.
Failing that, could a bluetooth USB dongle work to provide full BT support?

proto__ said:
Hi, I am trying to achieve the same solution however I do not think it's possible. My understanding is that the bluetooth connectivity allowed by the hardware in the head units doesn't cater for the 'full stack' of bluetooth functions, so we're stuck with telephony and audio only with no data transfer.
I would *really* love to be corrected though! It would be great if it could be solved by software alone.
Failing that, could a bluetooth USB dongle work to provide full BT support?
Click to expand...
Click to collapse
I consider this a bug. It did work on the Sofia 3GR units on Android 6.0.1.
It (currently) does not work on the Android 8 PX5 FYT units (like the OP has as well). Can't say anything about the QD units.

Well that gives me some hope at least.
I did note at least 3 'Bluetooth' apps running on my device (that I've been playing with since my previous post).
Perhaps a custom mod may be the answer...

Sorry proto, I've had about five units and all the same. You're right and it sucks. I don't think it's a big as I've come across it many times and only in a few eBay postings did the seller actually specify it has a general bluetooth connection. Otherwise toy even have to buy their obd to get that to work
Sent from my SM-G950U using Tapatalk

Ok thanks for the replies. Hopefully it will be fixed with a firmware update in the future or something.

Is there are any news about this Bluetooth tethering?
I am really interested because my WiFi is really really slow...
I saw that some Bluetooth function are missing, like the possibility to remove paired device or select Bluetooth tethering.

It’s highly unlikely Joying will fix the Bluetooth, they would need to produce a seperate rom with normal BT configured and u would not have access to the Joying BT app.
Currently Joying route all Bluetooth communication via a service called btlink, from there it goes to the joying bluetooth app.
Joying have fundamentally changed the way the Bluetooth is configured so it functions with only their software.
All these headunit manufactures do this to the BT so it functions with their software and they never offer a fix

shanetrainST said:
It’s highly unlikely Joying will fix the Bluetooth, they would need to produce a seperate rom with normal BT configured and u would not have access to the Joying BT app.
Currently Joying route all Bluetooth communication via a service called btlink, from there it goes to the joying bluetooth app.
Joying have fundamentally changed the way the Bluetooth is configured so it functions with only their software.
All these headunit manufactures do this to the BT so it functions with their software and they never offer a fix
Click to expand...
Click to collapse
From which library/framework/binary/whatever is this btlink service started/called?

surfer63 said:
I consider this a bug. It did work on the Sofia 3GR units on Android 6.0.1.
It (currently) does not work on the Android 8 PX5 FYT units (like the OP has as well). Can't say anything about the QD units.
Click to expand...
Click to collapse
Remember that it only worked with a HACK. Joying intentionally disables this functionality.

Bluetooth information
Init.sy.rc
Service blink /vendor/bin/blink
Init.connectivity.rc
Chmod 0666 /dev/tty (This should be tty00)
Now I have modified mine but I think the system/vendor/ect/Bluetooth/bt_vendor.conf is set to
- UartPort = /dev/tty00
Blink is interacting with /dev/tty
Android system is interacting with /dev/tty00 ?
Hopefully all the information is correct as I have modified my unit lots to try give back the Bluetooth to the system and I didn’t keep many notes.
But in short the the system is trying to access the Bluetooth on the wrong Uart port, where as the blink is attaching to the tty device, allowing the joying software to work.
This prevent the android system & apps interacting with the Bluetooth.
Also this is the test app I have been using to try to get it to allow permissions to turn BT on, but it get denied every time
Bluetooth Discovery : Bluetooth LE Scanner
https://play.google.com/store/apps/details?id=com.manjul.bluetoothsdp

i have the 10.1 american version.
if i remember correctly, bluetooth has an issue when your using it as a "media" access point
i think the bluetooth is set for A2DP... probably physically somehow.

shanetrainST said:
Init.sy.rc
Service blink /vendor/bin/blink
Blink is interacting with /dev/tty
Android system is interacting with /dev/tty00 ?
Also this is the test app I have been using to try to get it to allow permissions to turn BT on, but it get denied every time
Bluetooth Discovery : Bluetooth LE Scanner
https://play.google.com/store/apps/details?id=com.manjul.bluetoothsdp
Click to expand...
Click to collapse
Did you try to create a symlink like
Code:
ln -s /dev/tty /dev/tty00
And is it indeed tty00 or tty0?
Did you give the scanner root access?

Bumping this for a slightly odder issue. I'm trying to connect my Joying stereo to a Hondata KPro ECU, it sees the ECU but refuses to link to it in settings, rendering apps like Hondata or RealDash useless, so in turn I'm using a crappy $20 tablet until someone can show how to fix this BT issue.
Joying was no help other than to tell me to buy their OBDII adapter, which I did, but LONG story this is a 2008 Honda engine in a 91 MR2 that has no OBDII port. I've bought an OBDII port off eBay and tried using pinouts from the ECU to hack together an OBDII port but no luck.
Having it via Bluetooth would be easier, it sees the KPro, so there must be a way.

same problem
dont buy this joying head unit
its rabish

RK-A715 Generic Android head unit

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 ?

PX6 - Android 8.1 - Bluetooth

Hi all,
I have a PX6 for a BMW (from AliExpress - model CCT-BBA22B07) and i've been trying to figure out how to enable and use the bluetooth for more than phone calls and media streaming. I want to connect it to a bluetooth ODB2 device.
The PX6 seems to use some of the original headunit's functions and along with some of its own Android features and functions. For example, i can use the original HU for FM radio, CD, Bluetooth for phone calls, etc. while using the Android for other functions like navigation (and any other android app i can think of).
So i ignored the Android bluetooth for the phone and continued using the original HU bluetooth. However, i've been trying to use the Android Bluetooth for ODB2. I've bought a bluetooth dongle (CSR 4.0 usb dongle) hoping that the PX6 will detect it. However, i can't seem to switch on the Bluetooth on the settings. depending on the Bluetooth App i use, it immediately switches off (1ms on, next millisecond off), or it gives an error saying "permission denied"
I tried telling the PX6 to use the Android Bluetooth instead of the HU bluetooth, just to see if the "Factory settings app" prevents control of the Bluetooth, but i can't find the Android bluetooth on my phone (i'm contacting the seller regarding this).
So now that you have the background, basically, i want to continue using my original HU bluetooth for the phone, and i want to have a full featured Bluetooth on the Android device (like a tablet would have). Any ideas on how this is possible? I'm hoping there's no need to strip the screen and remove electronic components from the PC boards?

wow, I have a similar issue, I am suprised NOONE knows anything. xtrons sucks for support

AUTOPUMPKIN AA0495B issues with some bluetooth devices

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