So all my other phones work fine with the Parrot MKi9200. Except the ROG.
I'm going to try describing my experience as best I can. Wanting to see if anyone is having the same issues (with other asus phones even) and has found a solution.
First time I tried connecting, the bluetooth code popped up, I entered the default code and attempted pairing but the Parrot has too many paired devices so it was rejecting the ROG
so i cancelled the pairing and went into the Parrot to delete old devices
Tried pairing again but this time, it no longer asks for the code
The pairing appears to be successful on the Parrot, the phone says it's connected but when I try playing anything, there is no sound at all
I've tried forgetting the connection on the phone and then pairing again. and strangely enough, it no longer asks for the code, which is abnormal
The Parrot has no record of the ROG as a paired device so there is nothing I can do from that end
On the phone I then tried clearing bluetooth cache
setting org.coreaudio something bluetooth to not be optimised for battery
tried pairing a random headphone with the phone and it works just fine
Related
I just bought a Logitech bluetooth audio adapter (Model 980-000540) and am having a lot of trouble getting my Asus Transformer Prime to pair with it.
I've got the gold TF201, 32GB, all software up to date. I've gotten it to pair a couple times reliably, but the other 20 times I've tried pairing it works like this:
1) Press the button on the Logitech that puts it into discovery mode. The light on the unit starts flashing green to indicate it is announcing itself.
2) In the Prime settings, I have Bluetooth enabled, and then search for devices.
3) The Logitech unit shows up in the "Available Devices" list pretty quickly. Sometimes I see (what appears to be) a MAC address, sometimes it shows up as "(A9)Logitech Adapter".
4) When I click on the Logitech item in the list, it goes gray and says "Pairing" underneath it.
5) Most of the time, it the moves to the section above, to indicate that it has paired.
6) Immediately the green light changes to red on the Logitech, indicating it has lost pairing.
7) Shortly afterwards, the Logitech item goes back into the "Available devices" section.
8) If I try to pair now, with the Logitech no longer in discovery mode, the Prime will show a dialog that says "Couldn't pair with (A9)Logitech Adapter because of an incorrect PIN or passkey." The only option is OK, and there is no ability to set the PIN.
This happens 19 out of 20 times, but it's locked on a couple times and seems totally solid and reliable after that. It's just the pairing process which seems unbelievably fragile.
To my surprise, my Samsung Galaxy Nexus (LTE) has no trouble pairing with it at all. It paired the first try, and now whenever I turn Bluetooth back on it immediately syncs with the Logitech with no hassle at all. Rock solid.
I've tried various tricks, but none seem to work:
- Put the tablet into Bluetooth-broadcast-visible mode at the same time.
- Turning bluetooth off and then back on, etc.
Has anyone else had trouble with Logitech bluetooth speaker adapters too? Or does anyone have any tricks or apps that can coax the Transformer Prime into pairing more reliably?
Thanks for any help,
Jim
I had a very similar problem last week trying to pair a LG headset with the prime, connected with phone perfect, and but likewise when trying to connect also to prime second got the lost connection, incorrect pass/pin etc etc.
I solved it by connecting bluetooth headset to phone, then under phones bluetooth settings press and hold device name to bring up a menu, and select options. Then unchecked the Media option/box. I then tried to connect the device to prime and it worked flawlessly. Since then I haven't had an issue and can even switch between the phone/prime & bluetooth device with no issues.
Hope above helps and you get it sorted.
Try this app. It may help if nothing else does.
Bluetooth Address Finder - Market
Not sure if the Prime or your Logitec gives you the option to input the BT address or not. I've not had any problems pairing or connecting to any of my BT devices.
Has anyone come across this before: my obd2ecu adapter keeps asking for a pin every time I connect. Once connected it's fine until I close the app but next time it asks again...... this used to work fine on my one x and my s2.
Any suggestions?
Thanks
My Galaxy Nexus is doing the same thing with my new Passat's Bluetooth connection.
I had to make my GN discoverable and initiate the pairing from the car, which I think might be part of the problem. When the phone isn't in the car, the car doesn't show up in the list of paired bluetooth devices, and when I start the car, it asks for the PIN twice and pairs... without me setting my phone discoverable.
Thoughts, anybody?
Rob
Mine is doing the same ???
Got the Arctic P311 bluetooth headphones and tried to pair them to my prime.
It Pairs and then drops to available devices, I go to pair it again and it tells me that it cannot pair because of incorrect pin or passkey.
There is no spot to put in the pin or passkey
While it was connected I was able to go into settings for the device and it shows a change name field and media and phone
It does not stay connected long enough to do anything and while connected does not have audio
Stays connected for about 10 seconds
I have no roms or firmware just up to date android system.
Have seen that other people have these connected to there prime without problem.
If it helps, tried to connect a Motorola Bluetooth keyboard and it connects then immediately gos back to available each time i try to pair it
Okay, this issue is driving me a bit nuts. This phone seems to have a tendency to self delete bluetooth pairings randomly, such that I'll suddenly find I have to pair again a bluetooth device that I had working before. I know it's not the bluetooth device because this has happened on all sorts of things.... Get in car, no bluetooth connection, see pairing request on phone. Pebble watch suddenly won't connect anymore, look in bluetooth pairings list, no longer there. Worst is the Moto 360, because for some reason, Google decided that you cannot initiate a bluetooth pairing on Android Wear except by factory resetting the watch. So every few days, or weeks, depending on luck, I'd find myself having to factory reset my watch yet again, just to pair it back with my phone.
Just me? Anybody else with random bluetooth pairings deleted? I'm on the current 5.1 firmware.
I haven't used bluetooth much on this phone yet, so I don't know if this is device specific or a general problem. Anyway, my phone pairs with my car bluetooth dongle and works normally the first time, but when it's already paired it just won't connect, no matter what. It works again if I unpair it and pair it again, but that's not very convenient...
Has anyone else noticed this kind of behavior and is there a fix for it?
Try clearing the system cache and a network reset.
Well, I don't know what happened or changed but today it just worked... Weird.
Ah, turns out with this phone, I just need to wait until the dongle is properly initialized before trying to connect, otherwise it just gives up and won't even try again.
With my old Huawei, I could do it straight away and it would connect when it's done...
mcfox_1 said:
Ah, turns out with this phone, I just need to wait until the dongle is properly initialized before trying to connect, otherwise it just gives up and won't even try again.
With my old Huawei, I could do it straight away and it would connect when it's done...
Click to expand...
Click to collapse
Try in safe mode. May have a 3rd party app conflict.
Could also be a coincidence and the crappy dongle is giving up.
It's a cheap eBay bought one that renders an mp3 file on the fly so the car stereo can play it like normal flash storage. My wife's Xiaomi also had some issues connecting to it yesterday, and today as I was driving music stopped several times and the stereo said "USB format incompatible", then skipped to the next track and continued. I'm planning on installing an Aux input into the car soon so I can plug a better bluetooth receiver into that, so hopefully that'll solve the problem.