Hi everyone,
I've been running LiquidSmooth on my wife's S4Mini as well as my S4, and ran into an issue earlier today, that I can't seem to resolve.
I can't pair the device no matter what I try, apparently the UP24 is using Bluetooth Smart, and the error I get is:
Couldn't pair with UP24 because of an incorrect PIN or passkey.
Does anyone have any ideas on what I can try to remedy this?
Many thanks,
--schiz
Please ignore, the issue has been resolved, it was a faulty UP24 item.
thanks,
--schiz
Related
hey y'all
after waving my carkit goodbye cause i thought it didn't work with android, i decided to try and connect the phone to my computer, heey Bluetooth keeps disconnecting as soon as it has a connection, thats sounds familiar, that was the problem with my carkit/headset.
mmm, but wait, i flashed 3 different radio's all the problems remain.
currently at cyaogen mod 7 rc2 and well, does anyone know how to get bluetooth working?
phone to phone file transfers no problem, everything else, doesn't work
any suggestions?
Delete me - posted the wrong app. i am looking for the other
i have the same problem as well!!!
any help?
Hi all
I've searched for this issue on the forums but can't find anything that addresses my particular problem. I was wondering if anyone had any thoughts or suggestions.
I'm running CM 7.1.0 stable on my HTC Desire GSM and all is well - all except bluetooth. I don't seem to be able to pair with any devices.
The particular device I'm trying to pair with at present is a PLT BB903+ headset. I know the device works fine since I was able to pair with it when I was running stock Sense and I can pair with it using my wife's BlackBerry without any issues.
The device always appears in my list of found devices, whether it's in pairing mode or not, and even if it's switched off. I've wiped my Bluetooth pairing data using Titanium Backup but it still appears there as "Paired but not connected". Trying to connect fails but no error message appears. Unpairing then repairing has the same result - failure, no error message, and the next time I scan for devices it still appears as "Paired but not connected".
I've installed "Bluetooth File Transfer" from the Market as suggested elsewhere. When I attempt to pair using this I get the message "Pairing operation was aborted by user".
Any thoughts? Anyone had similar issues, resolved or otherwise?
Miz.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Bluetooth issues
Mizake said:
Hi all
I've searched for this issue on the forums but can't find anything that addresses my particular problem. I was wondering if anyone had any thoughts or suggestions.
I'm running CM 7.1.0 stable on my HTC Desire GSM and all is well - all except bluetooth. I don't seem to be able to pair with any devices.
The particular device I'm trying to pair with at present is a PLT BB903+ headset. I know the device works fine since I was able to pair with it when I was running stock Sense and I can pair with it using my wife's BlackBerry without any issues.
The device always appears in my list of found devices, whether it's in pairing mode or not, and even if it's switched off. I've wiped my Bluetooth pairing data using Titanium Backup but it still appears there as "Paired but not connected". Trying to connect fails but no error message appears. Unpairing then repairing has the same result - failure, no error message, and the next time I scan for devices it still appears as "Paired but not connected".
I've installed "Bluetooth File Transfer" from the Market as suggested elsewhere. When I attempt to pair using this I get the message "Pairing operation was aborted by user".
Any thoughts? Anyone had similar issues, resolved or otherwise?
Miz.
Click to expand...
Click to collapse
I wish someone could reply on this..... I have the same problem. Is it an issue with the Radio??
appreciate any help
There sometimes is a Reset-Button on under the Panel. Take it off and see if there is something.
i`m on 7.1.0 and my bluetooth works fine pairing with an alpine CDE-133BT.
But i have a different Issue:
a crackling and swishing noise in the background as soon as the bluetooth-channel opens for a2dp... with loud music it`s not hearable but with soft and quiet music it`s so annoying!
tried cm7 stock kernel, different Manu`s and Tiamat`s and i flashed the latest Radio... I think i try a different ROM... let`s see...
Hi, i've got a NTT Docomo Galaxy Nexus and my question is that if the bluetooth is different than the one in another versions?, my question is because I can't synch my cars handsfree (a handsfree from a Seat Ibiza) and I was hoping if someone can help me connect my phone to my cars radio, thanks!
At which stage occurs connection problem?
bluetooth
kraleksandr said:
At which stage occurs connection problem?
Click to expand...
Click to collapse
Thanks! problem solved, the problem was that my galaxy didn't find the car bluetooth and when it found it there was a connection error, I tried and tried again until it connects
Hi everyone I just upgraded from an ET4G to the Note 2 and I noticed that the new phone won't push SMS messages to my head unit in my car.
I know that this has been an issue for people with several Samsung devices in the past. I'm not exactly well versed when it comes to the underlying workings of various bluetooth profiles, but is there anyone that can possibly enlighten me as to what the root cause of the problem is, and is there possibly a method for overcoming the issue?
For what it's worth my Note 2 is currently on the stock rom (rooted) and the head unit in question is the Kenwood DNX9990HD. SMS via bluetooth worked flawlessly with this head unit on my ET4G (cm9 and cm10). I'm guessing that this ability was something that was embedded in Cyanogen but I'd be much appreciative of any insight that you guys can give.
Thanks in advance!
Nillaz
Hey Guys,
Having an issue with my bluetooth connections after updating to 4.3, anyone else having this problem?
When I try and connect to anything I get "Cannot communicate with xxxx", tried it with my car, my roku, and my laptop and got the same error across the board. Tried a factory reset and got same results....
Is this a known issue?