So I have an Eonon GA1312 Single din (RK3188).
I have been having two bluetooth issues. All have been troubleshot by disabling and enabling/deleteing data/cache of Bluetooth app, different settings and "off" in factory settings for bluetooth tab and a reload of malasyk rom after a factory reset.
Bluetooth will always show every device it sees. I have 6 Devices under "available devices". 2 I know of (game pad and OBD). 4 were because things were in range when scanning. They persist through everything. It's so weird.
Secondly, the ODB, while off is "available", but once conmected it jumps to "paired" devices and connects no problem. My game pad (nes30 pro to test the viability of bluetooth media control without buying one) is there whether in range, on, or not, and if I try to connect, I tap it, I am asked if I want to connect, and it does nothing.
My cellphones connect fine.
I read all over about some bluetooth limitations but found nothing documented on tje wiki or in the forum.
Any help? Sorry if repost, I thought I made a thread but it says it isn't there and I have no move/deleted notices.
Bump for justice.
Related
I purchased marbella GB-6205 V2.2 for my dopod900 but pairing problem is encountered.There shows ? in the icon. I'm running out of tips. ROM 1.30.230WWE. Somebody got any advice
Dont really have a tip i just wanted to see what people came up with. I am haveing the same problem with my Gsat 359. My issue is with the 8525 and Wayfinder. im on VP3gs offical wm6. Also having issues with some of the menus looking like half circules but that is more an issue with the software.
For both posts, I think that you have to be more specific, not being able to pair a device might have lots of causes, in example:
- Are you sure that your devices are indeed in pairing mode, having them to enter in pairing mode can be tricky sometimes
- Usually any device in pairing mode within range will be detected by the PDA/phone.
- Sometimes the keyboard applet appears just above the passkey request window not permitting to see it (happens sometimes with my universal), also there are at least two "common" paskeys used for bluetooth devices (this doesn't mean that some more could exist), usually "0000" and "8888".
- Are you sure that both (PDA/phone and bluetooth device) devices work? Try to pair another bluetooth device with your PDA/phone and try to pair your BT device with another PDA/phone; defective items are always a possibility.
- You might even have had success to pair your devices, the problem might be the software, see all the post that To_mT_om have generated because of problems with third parties BT GPSs, verify your software and a very practical way of being sure that everything went ok with the pairing is to install the app that usually all BT GPSs have included, normally a very simple app that displays geodesic coordinates or even raw NMEA info.
- Some PDAs/OSs might have the need to "create" another serial port for the new BT GPS in order to be accessed by the software, also see the other posts for this information.
Do you need more info?
Verify all the possibilities, perform all the test mentioned and then be very specific about the exact problem, most of the best gurus (and I'm not talking about me!) ask for a tough research of the forum's posts before asking for something that might have been already answered, I understand them when they say that it is not funny to answer to the same question (in various flavors) several times.
One last thing, it's holidays time, many people could be missing in these days.
Good luck
got mine up and runnning. My problem was software related. Downloaded software from handango and i just wasnt working right. Went to the manufacture website...wayfinder.com and the new software found my gps with no problem.
We've tended to find that simultaneously restarting the BT GPS and PDA at the same time (and often with a battery removal on the GPS) can solve issues where the GPS simply doesn't want to complete pairing.
When this fails, it's usually software related or a corrupted Bluetooth stack / registry settings on the PDA..
Worst case, hard reset the PDA..
Good luck
Andy
www.pressdigital.com.au
Press Digital Support Team
Hi, I've got a small issue with my bluetooth a2dp device. The device is this one:
BlackBerry Remote Stereo Bluetooth Gateway. It is made by RIM, but works with any device supporting a2dp. My issue with the Galaxy Nexus is that it no longer auto connects.
My setup is in my vehicle, I keep the bluetooth receiver connected to the aux power jack and aux audio in in the center console. This way, when I start the car, the receiver powers up and tries to auto-connect to the last device. On my vibrant with Android 2.1/2.2 this worked fine. When I dabbled with CyanogenMod and some other custom roms, it stopped working but I chalked it up to some problem with the custom rom.
Now, I'm seeing the same sort of problem: if I keep the screen of my nexus on, I can see the bluetooth icon change blue, and then immediately change back to gray. To me, this indicates that the receiver succeeds in connecting but is then disconnected for some reason. The device only supports a2dp, not the handsfree profile. When I looked into the Android kernel code, I found a place where the kernel will try to connect the handsfree profile if the a2dp profile is auto-connected, but it wasn't clear if that was the actual problem or not.
Anyone else have any similar experiences?
I have the same device in my 2008 Accord coupe which is placed in the center arm console. I had an Evo 3D that would automatically connect when I would start the car and BT was already enabled on my phone. I too switched to a different ROM and would have issues auto connecting so I switched back to a different ROM. Now on my stock GN, I have to manually go into settings and click the device to connect. I see no settings about auto connecting when in range. I will have to see if the BT icon turns blue and then back to gray... haven't looked for that. If anyone has thoughts on this, I'm all ears!!
bigdawgr6 said:
I have the same device in my 2008 Accord coupe which is placed in the center arm console. I had an Evo 3D that would automatically connect when I would start the car and BT was already enabled on my phone. I too switched to a different ROM and would have issues auto connecting so I switched back to a different ROM. Now on my stock GN, I have to manually go into settings and click the device to connect. I see no settings about auto connecting when in range. I will have to see if the BT icon turns blue and then back to gray... haven't looked for that. If anyone has thoughts on this, I'm all ears!!
Click to expand...
Click to collapse
I suspect it has something to do with Android's attempts to auto connect to the headset profile when a A2DP profile is connected.
See:
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true
Click to expand...
Click to collapse
from https://github.com/android/platform_system_bluetooth/blob/master/data/audio.conf
I have seen the code where this happens and it seemed that if the headset profile failed to connect, the A2DP connection was also disconnected. Though, I can't recall what file it was.
jjohns63 said:
I suspect it has something to do with Android's attempts to auto connect to the headset profile when a A2DP profile is connected.
See:
from https://github.com/android/platform_system_bluetooth/blob/master/data/audio.conf
I have seen the code where this happens and it seemed that if the headset profile failed to connect, the A2DP connection was also disconnected. Though, I can't recall what file it was.
Click to expand...
Click to collapse
Strangely enough, the phone paired with the device twice without issue yesterday and failed once later on that same day. I'm toggling BT off and then on to get connection for now.
It seems like the phone and device are connecting without issue but I know I haven't done anything to change it. I'm on AOKP M3 and Leankernel V1.8 if that helps. When I first flashed those two, I still had connections issues, so switching to them wasn't a resolution.
I am not sure this really helps your issue but it is related. I wrote an app that will auto-connect Bluetooth devices. It is free on the market and is called A2DP Volume. The current implementation of auto-connect looks for one device connection and then connects another. I started another widget that will simply connect a Bluetooth device but I have not finished that one. A2DP Volume is free, open source, and ad free. You can find the open source project on Google Code. Just search for A2DP Volume.
I have been trying this for weeks and this app solved it!!! Thanks for making the app!
jroal said:
I am not sure this really helps your issue but it is related. I wrote an app that will auto-connect Bluetooth devices. It is free on the market and is called A2DP Volume. The current implementation of auto-connect looks for one device connection and then connects another. I started another widget that will simply connect a Bluetooth device but I have not finished that one. A2DP Volume is free, open source, and ad free. You can find the open source project on Google Code. Just search for A2DP Volume.
Click to expand...
Click to collapse
jjohns63 and bigdawgr6,
Any update on this problem? I don't have the Nexus, but I have Droid Incredible 2. I also run into the same problem when I use CyanogenMod 7.2, which is a AOSP based ROM. The connection is fine with the stock ROM. I have tried to change things in the audio.config but it does not seem to help. I think I ran into a post somewhere saying HTC stock ROM uses a propietary bluetooth stack and AOSP and CyanogenMod uses BlueZ open source stack, and that is where the problem is.
Anyway, it would be nice if you guys can share some info.
Thanks!
The problem is to connect Bluetooth on a Moto Z Play Android 7.1.1 patchlevel 2/2018 (current in reteu, was same result with Android 6.0.1 12/2016) with a Volvo XC40 car.
The first pairing with Bluetooth succeeds for a second. Then, nearly immediately, both displays (car and mobile) show reconnecting for about 10 seconds. It has a connect for a fraction of a second, and then is reconnecting and so on.
Trying flight mode and then only Bluetooth enabled on the mobile did not help. IIRC it showed some message about "My Volvo Carnull not bonded" (the name of the car for Bluetooth is "My Volvo Car" and some message with typo, something like "conecnting not successful". After that I rebooted, result was the state before with reconnecting.
Did try this several times. Also did try to reduce the amount of Bluetooth access types the car tries. There are 4 connected: phone, audio, internet, contacts. Did also not help.
Has anyone an idea how to get a successful connection or what the cause of the problem is? Did search for similar problems with Bluetooth in cars, but could not find anything (except for that hint with flight mode which did not help).
What I tried by now:
- Flight mode, only Bluetooth (as already mentioned). No change
- Remove all bluetooth connections. Pair new. No change
- Delete data for sytem app "Bluetooth Freigabe". No change
All other bluetooth connections are working fine. Another Moto Z Play using Android 7.0 (01/2017) is working flawlessly with that car. Strange for me is that it didn't work on 6.0.1 in the same way it does now fail on 7.1.1, but the other Moto Z Play using 7.0 is connecting stable.
Still the question: Does anyone have an idea how to get the connection working?
Factory reset?
I see that you deleted all bt connection but do you have some apps that are using bt? Like for smartwatch, headphones...?
I have Amazfit and watch must be connected to be able to pair a new device. Drow me crazy first time when I had that problem. I thought that car audio is broken, then phone... After pairing, watch doesn't have to be connected to reconnect.
Sent from my KFSUWI using Tapatalk
Zeljko1234 said:
Factory reset?
Click to expand...
Click to collapse
I was afraid this reply could come. When doing a factory reset, I do following: Pack /data/media somewhere because Nandroid omits this. Backup all partitions using twrp. Backup all apk using adb. Export SMS. Export contacts. Screenshots of the launcher screens. All this takes about 2-3 hours. Then I struggle a week until my device behaves like before. I'd be willing to do it if I saw a reason why it could help.
Zeljko1234 said:
I see that you deleted all bt connection but do you have some apps that are using bt? Like for smartwatch, headphones...?
Click to expand...
Click to collapse
Headphone, yes, there is August EP650 configuration tool that is not necessary. Thank you for the hint, will try it. Also I read somewhere it may help to delete cache partition, that's also worth a try before doing factory reset. Maybe I'll wait for Oreo before trying factory reset, could be they fixed some bug there.
Edit: BatOn which shows Bluetooth battery for external devices could also be the culprit.
Zeljko1234 said:
I have Amazfit and watch must be connected to be able to pair a new device. Drow me crazy first time when I had that problem. I thought that car audio is broken, then phone... After pairing, watch doesn't have to be connected to reconnect.
Click to expand...
Click to collapse
That's a strange behavior indeed. Amazfit seems to do something wrong.
It doesn't get any better if you upgrade to Oreo, I've been having problems with my Moto Z play disconnecting and reconnecting to the radio in my Corolla constantly ever since I went up to nougat. To be honest I just bought a good pair of headphones and stopped using the radio. Good luck though, if someone finds something that helps let me know.
I'm using bt with car audio, headphones, smartwatch... No problems at all, except one with Amazfit. And that is related to their bt implementation, not Moto fault.
Sent from my KFSUWI using Tapatalk
Seems the last action to remove Bluetooth related apps was the right one . There were two apps installed:
1. BatOn showing the state of battery of connected Bluetooth device
2. August configuration app for August EP650 headset
Removed both as they are usually not needed and it seems to work now. Will see later if it only worked for the short test I did today (currently I try to avoid driving because of an injury) or if it keeps stable.
Good, you didn't have to factory reset after all
Sent from my XT1635-02 using Tapatalk
Helo.
I have chinese android navigation mcwauto 8001 for Audi Q5 8R.
My issue is lack of bluetooth connection when I am using Zlink app.
I am able to connect phone with naviagation via bluetooth, but when I establish android auto connection using USB port the bluetooth connection is lost.
Because of that I am not able to make a call using android navigation/zlink. The call is make by phone speaker instead of bluetooth (android navigation).
What is more I tried several times to force bluetooth connection with my phone when I am using wired android auto, but even I am able to connect bluetooth the connection is lost every time I am trying to call.
When I call I have the message "you are not connected with bluetooth"
My zlink app is 3.9.31 - according to my navigation this is the current version of zlink. I found few newest upgrades but I am not able to install it. Few of them stop installing in about 80%, the rest even installed properly not working, the app just stop responding, and the hard reset are required.
Does any of you know solution for my problem?
The red android auto icon (two triangles) on my navigation are showing and disappearing constantly, does anyone of you know what this is mean?
But it's not an MTCD device new member joined for free support.
Requested moderator move to (Android head-units) forum.
Also, what does seller suggest you do when contacted for support
I'm currently trying to pair my SmartWatch and navigation device with the vivo. With the SmartWatch, Coros Vertix 2, it worked straight away.
With the Hammerhead karoo 2, however, the vivo is desperately trying to establish a connection.
Pairing works, the number code came up briefly at first, but it doesn't appear in the app, not even under the available devices in the BT settings.
Tried lots of tips, removing all paired devices and then restarting, activating/deactivating BT, restarting the navigation device etc..
Nix.
Anyone with an idea what the problem could be?
Solved the Problem with the Help of the customer Service of Hammerhead
Hard Reset of the Karoo and new Pairing wihthin Seconds.