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

Help determining if BT problem is software or hardware

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.

BMW E8x E9x CIC PX6 Android 10,25" trouble with bluetooth, idrive, display ect.

Hello guy`s
i have some issues with a 10.25" Android Navigation display i bought.
i also did some chat with the sellers but it seems their english is not very good...
From what i saw the system is the same PX6 System 2GB ram /32GB flash as sold for all other E Series BMW cars, only the additional mount is different.
Unfortunately i can`t attach pictures or extranal links yet, so i`m writing the Android spec here.
MCUVer: 023042bGS-CIC-HW7-190118[B1280_170325]
FrameworkVer: 8.1.0 OPM5.171019.019 eng.zxw.20181228.162012
AndroidVer: 8.1.0
AppVer: 2019030801_1280x480_970
Ram: 2G
1st "issue".
when booting the device it does display the Lockscreen, not directly the BMW GUI, i have to swipe to unlock the screen.
any way to change this to go directly into the GUI?
I haven`t found an option yet.
2nd. issue.
Bluetooth does not work like it`s meant to from an Android Device.
there is only a bluetooth menu at the BMW GUI, where i can search for Bluetooth devices and connect them.
the problem is now, it only does find other mobile phones, it does not find the original CIC, not a BT headset, also not a BT mouse or BT keyboard.
when i go to to normal android settings "connected devices" i don`t have an bluetooth option here.
the BMW configuration has set "WenqiangBC6" BT Module enabled.
I want to use an additional Tsumbay Ai01 controller, but i also can not connect this device.
is it possible to reenable the original Bluetooth option there, i think it only has been disabled ?
3rd issue.
It has been delivered with an additional "pseudo" Idrive controller that is directly connected to the Android screen.
the problem is, that the controller will always only work for about 30-60 seconds, then it will not respond anymore, i have to reconnect the controller to get it work for again 30-60 seconds.
does someone also has this controller and had such trouble , or a fix for this ?
4th "issue".
I`m using google maps as i lost the Igo Software because a "factory reset" has been made.
when doing navigation, half of the screen is consumed by grey (bottom) or green (top) surfaces including the Status bar.
is there any chance to change the visuals of google maps to look like Android Auto or at least to make the bars smaller oder disable automatically disable the status bar ?
i have found no option for this, also not for scaling, probably it`s also disabled ?
5th "issue".
the harness does have alot of "CAN" connectors, "CAN A" "CAN B" "CAN C" "CAN 1" "CAN 2".
there did came no description whith the device, does someone have a description of the harness ?
i already updated the cartype.xml and factory.xml to get ID6 back, but that does not help for the other issues.
i hope someone can help me at least with some of the issues
sincerely Chri

Hello
I was able to "solve" the 3rd issue, when the Android navigation is set between Car and original CIC-HU, the original CIC controller does work fine so the pseudo controller isn`t needed anymore
The only thing is that i found a new issue,
7th issue,
the Aux Autoswitch option does go to the wrong menu point.
so when selecting "Music" it does not switch to AUX.
I made a video to show the Start to unlock issue and the Auto AUX issue, maybe this will help
https ://youtu.be/ETWdRfly6PY
you need to remove the space after https
sincerely Chri

Hey Chris, I'm also Dutch and I'm seeing a lot of the same issues..
Doe you know the factory settings code to get in the factory menu?
Thanks!

Hi to all
I have the same unit i get it from AliExpress navifly
I had the same exact issues like chris i did a factory reset and eventually i lost everything i did something wrong and now i have the unit is infinite loading on android and it’s not turning on. I am wondering if someone can help me with this and by the way the factory reset code is 1314

Has anyone solved the bluetooth problem? I just want to load normal android on it to be honest. Their audio bluetooth and phone stuff is taking control somehow. I don't even care for it.

same problem with bootooth here. Not able to connect bluetooth device from other apps (OBD or Flitsmeister)

GertrudeHarolds said:
same problem with bootooth here. Not able to connect bluetooth device from other apps (OBD or Flitsmeister)
Click to expand...
Click to collapse
meanwhile it`s a known common thing that Bluetooth is locked on this devices so only smartphones for playing music and do handsfree calling is possible, it is not possible to add other bluetooth devices like OBD dongles, mouse, keyboard ect.
Chri

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

Android 10 Snapdragon 625 HU kswcarproject

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,