Head unit is this one from Idoing.
I have the BT1 ODB2 Dongle from Ecutek, and downloaded the ECU Connect App.
I confirmed that this works from my Phone (Galaxy S21). It successfully finds the dongle and the app works from there.
When I try from the head unit - it tries to find BT devices, but every device is listed as "noName". It finds anywhere from 4-10 devices (depending on how long I let it scan). A couple of devices actually pair, but they do not work for ECU Connect. So I assume they are not the correct devices. I think at this point I've gone through every 'noName' device. Most do not pair at all. The ones that do pair, I've renamed so I can keep track of which ones they are.
Now, when I try using the native BT connection on the head unit - it can actually find and correctly identify the Ecutek dongle. However, connecting from here does nothing - I must connect from within the ECU Connect App which of course fails.
I tried some random BT scanning apps - they all show similar behavior with devices being displayed as "noName". Googling this "noName" BT issue doesn't come up with anything useful.
Any ideas for what I can try or at least try to diagnose the issue? I have a friend who says he ran into something similar with a similar head unit, but he cannot remember how he fixed it...
I figured it out. Figured I'd write it up here since I couldn't find this anywhere else on the internet.
Sparing all the middle troubleshooting steps, here's a summary:
First, these Chinese Android head units all seem to struggle to pair with certain BT devices. This 'noName' issue is merely a symptom of other problems.
The Ecutek BT dongle has a passcode. The head unit is trying to use a passcode of '0000' when negotiating with the dongle. If this is not the passcode, it will fail silently most of the time. Sometimes you get a failure indication.
Steps to fix:
Connect to the Ecutek BT dongle via your phone. Your phone has a better time negotiating this connection. Once successful, it will ask you to enter the passcode (if one was set up previously). For me, my car had a previous owner/tuner - so I imagine they set it up already.
At this point, you can reset the pre-existing passcode (i.e. if you do not know it). Follow the prompts in the ECU Connect app to reset the passcode.
After resetting, change the passcode to '0000'
If you already have the passcode set to something else, you can reset the passcode within the ECU Connect app. Simply reset to '0000'
Back in ECU Connect when looking up new BT devices, you will still have the 'noName' issue. I simply tried every 'noName' device until one worked. It appears that both successes and failures can be silent when in the head unit's BT screen... You can tell that it worked by pressing 'back' from the BT screen. If successful, ECU Connect will recognize the device and show a success message. If it doesn't, then this 'noName' device is not the right device.
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
Hi,
I've just purchased one of these head units for my car. I can connect my phone to it via Bluetooth just fine for calls and music, but I want to connect the head unit to my ODB2 bluetooth dongle so that I can create a Torque dashboard for it.
However, when I go to the general settings, Wifi is listed but Bluetooth is not. I've searched and searched but there is no way for me to connect the head unit to a Bluetooth device. I've tried various third party apps that claim they are able to enable Bluetooth and connect to devices, but they all just seem to hang when I try to enable Bluetooth. Tried a system reset too, but that Bluetooth option is still missing from the settings menu.
Please can anyone help?
G
I'm also interested in knowing this. Torque doesn't seem to detect my bluetooth ELM327 at all. I also attempted to connect a USB-based ELM327 module, and Torque seems to detect it, but it doesn't work beyond that, and the headunit gives me a low-power warning light.
Hi did you get anywhere with this I have the same problem can't get Bluetooth options to show
I have exactly the same problem. I'm running a PX5 unit from Witson. Custom built for a Koleos. MCU is not a standard MTC device. I have no bluetooth option available in the settings and the stock bluetooth app does not display any search option whatsoever. It seems that it broadcasts itself for other devices to detect it but you can't search for devices. Seems like they may be handling the bluetooth via the MCU directly and not via android which is strange because they openly claimed that this device was compatible with the OBD II dongle that I purchased. They even shipped it in the same package. Will keep looking and post if I find anything.
I had the same problem with a different Chinese head unit. Solved by buying a WiFi ELM327 dongle which connected fine with the head unit's built-in WiFi.
Update to my earlier post...I managed to get mine working over BT with the WITSON unit. In the end I had to disconnect my phone completely and reboot the unit. Then I found a search option on the dialer page. Searching found the OBD II module and I was able to pair with it. After I was paired with it I was able to add my phone again and both can run in parallel. I have not been able to test much but it seems like this continues to work until the unit goes into a deep sleep and shows the startup logo again. If that happens then I need to go through the learning process again. Meh...
Hi friend, just a question, in the dialer where did you find the search option I cant find it in my android radio??
If you have the swm 8802 you cannot connect to obd2 this requires bluetooth 4 and the 8802only support bluetooth 2
Always Connect ODB First
The ODB readers are a tad picky but they connect using the same menus as any other BT hardware (headset, speaker, etc). First, turn on the car ignition, do not start.
2. Make sure no other BT equipment is connected to the head unit or even on & near by.
Next, place the head unit in searching/Discovery mode and then & only then plug the ELM BT Module into the car ODB II Port. Most cars must be 96 & newer. 95 GM with for the plug but won't work. They're usually ODB 1.5, don't ask, your screwed.
Finally wait for the module to pop up and ask for the code, it's 1234 not 0000.
After your paired, THEN open Torque and let it connect. Don't start the vehicle till the car icon stops flashing.
You should be good to go from then on. If you ever have problems after that. Make sure the app is totally closed, force stop and then follow this procedure again.
---------- Post added at 07:55 AM ---------- Previous post was at 07:30 AM ----------
vincentstans said:
If you have the swm 8802 you cannot connect to obd2 this requires bluetooth 4 and the 8802only support bluetooth 2
Click to expand...
Click to collapse
Mine connected no problem. Did it just like I do on my phone. I just got mine too though. Could be an update maybe
the original question wasn't answered and I have that problem too. I don't have a Bluetooth discovery/search option anywhere. the small bluetooth-like icon on the main panel just changes the color of the leds.
so can't connect new phone. although Bluetooth seems to be working, since an older phone, already paired, is still working.
Following this as my head unit is same. Theres no blietooth menu/option but it connects to a phone.
Ive tried a third party bluetooth manager but all that says is bluetooth disabled by admin??
A fix
That happened to me trying to add and ODB2 bt dongle. I had to use the app for bluetooth linking provided by the head unit. When I purchased the unit, I changed the bluetooth discovery and pairing code to 0000. Well, changing it to 1234 allowed me to add the ODB dongle.
I saw it on a YouTube video, and well, it worked for me. (And no, no native bluetooth option, came disabled for my unit as you said)
Hope it works for you too.
same problem with me
Hi sir did you found solution for this problem. I also have this problem with my native bluetooth. when i turn open system setting bluetooth missing. i try to open using shotcut and found shotcut to turn on bluetooth but when i turn on. it do nothing.
I can play music, make call using bluetooth app provide from head unit. Problem is i cant use it with OBD2 . same with your statement this bluetooth only stream signal to other. this Head unit cannot find other bluetooth.
Kindly please assist me. did this head unit still have hope to turn on native bluetooth or not. I still search many post regarding this issue. But issue bluetooth like this not many discussion.
Hello there,
My problem is some how different. My hu use the bluethoot to find the obd2 adapter but there is no dedicated pair button. I can pair my phone for calls and music but connecting from phone to hu.
My unit is a 8227l from seicane.
Has anyone any solution? Thank you!
blongro said:
Hello there,
My problem is some how different. My hu use the bluethoot to find the obd2 adapter but there is no dedicated pair button. I can pair my phone for calls and music but connecting from phone to hu.
My unit is a 8227l from seicane.
Has anyone any solution? Thank you!
Click to expand...
Click to collapse
Change the pair code in the bluetooth custom app provided, to 1234 and try again.
I had this happen and I think I figured it out.... in factory settings there's an option to choose bluetooth connect automatically or with pin. I checked with pin and was able to pair. I think the options are reversed in the settings
I have the same problem i can't connect to the android 7.1 car head unit any more , the bluetooth setting is missing , the wifi settings appear but bluetooth doesn't appear any more
Anyone can help me to fix this issue please ?
Karemz said:
I have the same problem i can't connect to the android 7.1 car head unit any more , the bluetooth setting is missing , the wifi settings appear but bluetooth doesn't appear any more
Anyone can help me to fix this issue please ?
Click to expand...
Click to collapse
I bought a bluetooth usb adapter and I can't select it on the system. I think this would be the way out, but we need to replace the driver inside android. Does anyone have any ideas?
venomrocha said:
I bought a bluetooth usb adapter and I can't select it on the system. I think this would be the way out, but we need to replace the driver inside android. Does anyone have any ideas?
Click to expand...
Click to collapse
I have a Teyes Spro with the same Bluetooth issues as most on this post describe. Did you find an answer to your usb adaptor to solve the Bluetooth problem? I was told to add a line to the config.txt file but cannot locate where to access that to add it.
Bought a Teyes Spro headunit and I have a problem with Bluetooth discovery on my obd II and tpms modules. Does anyone know what is in the "Developer" tab? It is password protected not accessible. The 168 factory access code does not work for it. Anyone know the password?
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
Howdy,
Does anyone have a clue how to connect PH-1 to Skoda via either Android Auto or MirrorLink interfaces?
I've tried connecting the devices to my Skoda '17, and it failed 99 trials out of a hundred. In most of attempts made to connect the phone to the headunit the were no reactions on the car's screen.
When plugging PH-1 to the USB-A plug on the car's side, nothing happens. The car has 'Welcome to SmartLink. Please connect a device via USB. ' on its screen.
Only once had I the car to ask me to decide what type of connectivity I'd like it to be used: Android Auto or MirrorLink. I chose Android Auto and got something like Connection failed on the car's screen. Then nothing. I had no luck to connect the phone in any further attempt.
I have tried rebooting the phone, the head unit, I've even tried resetting SmartLink settings in head unit. Nada.
I have Sygic with MirrorLink feature installed, and the phone isn't connected to head unit via Bluetooth.
Does it mean Essential Phone does not support neither Android Auto nor MirrorLink interface? If so what was that Skoda asking me to choose how I'd like the phone be connected: via Android Auto or via MirrorLink? Just a glitch?
Does anyone have a clue? Thank you.
somewhere else i read that a person had to use
"fastboot -i 0x2e17 < your file/zip here >
to get fastboot to work.
good luck.
Luxon said:
Howdy,
Does anyone have a clue how to connect PH-1 to Skoda via either Android Auto or MirrorLink interfaces?
I've tried connecting the devices to my Skoda '17, and it failed 99 trials out of a hundred. In most of attempts made to connect the phone to the headunit the were no reactions on the car's screen.
When plugging PH-1 to the USB-A plug on the car's side, nothing happens. The car has 'Welcome to SmartLink. Please connect a device via USB. ' on its screen.
Only once had I the car to ask me to decide what type of connectivity I'd like it to be used: Android Auto or MirrorLink. I chose Android Auto and got something like Connection failed on the car's screen. Then nothing. I had no luck to connect the phone in any further attempt.
I have tried rebooting the phone, the head unit, I've even tried resetting SmartLink settings in head unit. Nada.
I have Sygic with MirrorLink feature installed, and the phone isn't connected to head unit via Bluetooth.
Does it mean Essential Phone does not support neither Android Auto nor MirrorLink interface? If so what was that Skoda asking me to choose how I'd like the phone be connected: via Android Auto or via MirrorLink? Just a glitch?
Does anyone have a clue? Thank you.
Click to expand...
Click to collapse
Don't know about Sygic or Mirror Link but the Essential phone works fine with Android Auto as far as I know. Works for me & wife's cars "out of the box" just plug the cable in. (not Skoda or VAG cars though). Often with Android Auto it's the cable, try some different cables. Else there is an app here on XDA that allows you to use an old phone to connect via wifi though a bit buggy I believe, called HeadUnit Reloaded I think
Edit:didn't read your post properly it seems, you could try setting a different Bluetooth codec in developer options ....
For those interested, for historical purposes, low-quality AKAI USB-B-to-USB-C cable was the culprit. Changed it to HTC's cable and it worked fine, the head unit did recognize the phone and started Android Auto shell. Never thought new cable could wreck the whole thing. Looks like the new AKAI brand owner produces crapware.
I installed an Atoto S8 (2nd generation) head unit in my car, and I'm noticing that it only reconnects to whoever drove the car last.
For example, I usually drive the car. But when my wife drives, we need to manually go into settings to find the list of paired devices on the unit and then click on her phone to connect. After that, it will auto-connect whenever she drives until I take the car. My phone won't connect anymore unless I go into the list of paired devices and do that same thing. Silly and annoying because we share the car sometimes and have to keep track of who drove last if we want our phones connected.
I reached out to Atoto because their linux-based F7 didn't do this (I owned one previously), it would reconnect to any previously paired device automatically like any head unit should (obviously most recent first, but then if not found move on to another previously paired). They said the Android based units don't work like that, then gave me a silly reason for it that didn't make sense (something about security unlocking which the F7 doesn't have to worry about).
I'm wondering, do all Android head units have this issue or is it unique to this brand?