So as the title says, i have trouble connecting to an older Bluetooth device, I have a 2007 vw passat with Bluetooth telephone, despite being old i use it daily because it works perfectly, or at least did with my razer phone 2. Had to upgrade because no parts for the rp2 and the usb-c died on it so i bought an xperia 1 ii, and it just straight up not detected by the car and the phone cant see the car no matter what i do. Messed with the toggles in dev settings, did the cache delete, everything, it doesnt work. Bluetooth is supposed to be backwards compatible so im convinced this is another lovely bug in android 12. Honestly getting kinda fed up with 12 not gonna lie...
Anyone had any problems like this?
Related
So I have an xperia, and I have a new JVC Bluetooth deck, I was so impressed how flawlessly it worked with my old phone the Kaiser/tilt, but to my surprise I have not been able to get it to properly pair up with my newer xperia. They will read each other and try to connect but I always end up getting an error. Sometimes it still shows up as connected but nothing works. I used my kaiser/tilt for both calls and streaming music through my new JVC bluetooth deck and I loved it, so its pretty dissapointing when I upgrade to what is/was one of the hottest & expensive windows mobile phones and it apparently has bluetooth issues.
I tried a few fixes already like changing the registry to read as a normal phone and I added in a missing bt profile, unfortunately nothings changed. I am curious tho because i had a magician and they had whole bt stacks that I messed around with, and I'm also wondering if a flash or two of a new rom may make a difference. Ocerall I'm really happy with the X1 (unlike my tilt/kaiser which had lots of problems) so much so that I don't really feel the need to flash a new rom, but if it might have a chance of fixing my bt I'm all for it.
Let me know if anyone has any suggestions, tia.
For some reason when my phone connects to a headset that supports both audio and phone the audio will not auto connect. I have to open the bluetooth options and hold down on the device i want to connect to then check the audio box.
sounds similar to the problem I'm having... I connect my phone via bluetooth to my car (Ford Sync) and I need to turn bluetooth off then on at least once (if not twice) for the car to recognize the phone.
I am getting so fustrated with this phone... Its been replaced twice (like replacing hardware is going to fix a software bug).
i really want to stay with an Android phone... maybe the Samsung Moment? it appears as if 2.x is now available (unofficially?) since Samsung released the Kernel source like they were supposed to.
TL
It worked before fresh 1.1 so maybe it was just a change in something.
I'm using the stock software and I have the problem so it is not freshrom
man we need an update HTC!!!!!!!
q1 almost over so we're that much closer to getting our official 2.1 update.
I've also got a bluetooth problem - would really appreciate any help you can offer.
I have a Tomtom and headphoned in my Bike Crash Helmet. I want to connect so I can hear music and phone calls through the phone in my helmet and also hear the TomTom.
The Tomtom connects to the Helmet, the phone connects to the Tomtom and I can get calls through the speakers via the Tomtom but music won't play (apart from an annoying second or two after dropping a call).
If I can get the phone to advertise headset features I could connect the Tomtom to the phone and the phone to the speakers (think that would work), otherwise I believe the Tomtom is not advertising media audio, only phone audio and don't expect I can change that.
Any thoughts...?
PS - Have tried the market headset app - unfortunately it doesn't fix the problem...
Time_Lord said:
sounds similar to the problem I'm having... I connect my phone via bluetooth to my car (Ford Sync) and I need to turn bluetooth off then on at least once (if not twice) for the car to recognize the phone.
I am getting so fustrated with this phone... Its been replaced twice (like replacing hardware is going to fix a software bug).
i really want to stay with an Android phone... maybe the Samsung Moment? it appears as if 2.x is now available (unofficially?) since Samsung released the Kernel source like they were supposed to.
TL
Click to expand...
Click to collapse
well now the source for the CDMA hero is out so shouldnt be long till a lot of the little bugs arre resolved.
I recently got my new Renault Scenic car and discovered a rather strange situation.
The phone pairs with the carkit and connects the first time without issues and works like a charm.
But however when I start the car and thus also the carkit the phone connects also but no audio is heared trough the carkit when calling or getting called. The phone says it transfers the connection to the carkit but nothing is heared.
It only works when I have bluetooth off, starts the car and then turning bluetooth on the phone on. Wait till it connects and make a call. With this procedure the connection is good till I step out the car.
Its a work around but hmmm not the one i would love to.
I have a nexus one rooted with the latest MCR (21) and an intersect kernel. Though I tried different kernels also but no go.
Hopefully one of you guys have an idea
Ok I searched a bit and found out the Bluetooth is done with the opensource code Bluez. So I wonder which version of Bluez is in the froyo roms and how it can be updated if possible to a new version.
Anyone knows ?
I feel your pain, I have a Renault Grand Scenic III (purchased last December) and the hands-free is unreliable, but music streaming (A2DP) is even worse as most often than not it will fail to connect.
I have to say that the hands-free works fine most of the times (for the phone part, not for music), but some days it will refuse to work no matter what. Since it isn't working much better with my wife's Nokia (BTW, which I had to do a firmware update or else it went into a permanent reboot loop when connected to the car-kit), I assume the problem lies on the car, not on the phone. I have yet to see if my Hero, which has been recently updated to Android 2.1, behaves any better. A firmware update on the Bluetooth car-kit seems a better approach, but I'm unaware if one exists since after some digging it seems my car doesn't use the OEM Parrot kit that other earlier models carried.
igalan said:
I feel your pain, I have a Renault Grand Scenic III (purchased last December) and the hands-free is unreliable, but music streaming (A2DP) is even worse as most often than not it will fail to connect.
I have to say that the hands-free works fine most of the times (for the phone part, not for music), but some days it will refuse to work no matter what. Since it isn't working much better with my wife's Nokia (BTW, which I had to do a firmware update or else it went into a permanent reboot loop when connected to the car-kit), I assume the problem lies on the car, not on the phone. I have yet to see if my Hero, which has been recently updated to Android 2.1, behaves any better. A firmware update on the Bluetooth car-kit seems a better approach, but I'm unaware if one exists since after some digging it seems my car doesn't use the OEM Parrot kit that other earlier models carried.
Click to expand...
Click to collapse
Hi,
I've just come across your post. Did the situation improve ?
I'd just point out that for me it comes from the Android system : I own a Renault Mégane 3 and was able to fully use the bluetooth system with my HTC HD2 (Windows Mobile 6.5). Now, I've just installed Android 2.2 on it and I encounter a similar behavior... and the car can't connect to the phone directory either...
Looks like I'll boot back on Windows Mobile when driving...
Regards,
Stéphane
My Hero with the official 2.1 ROM is now 100% reliable. The Nexus One with Froyo isn't, A2DP is still hit & miss.
Well... I'm getting the same but not with Renault ones.
I have LiquidAUX on my car and to have both phone and a2dp synced, I have to restart phone BT and LiquidAUX every time I go into car. And most of the times I can only have 1 connection each time, or phone is on and a2dp is off or a2dp is on and phone is off. It's really annoying since I had an HTC Hero with Android 2.2 and it used to work with no problems...
Hello, I've the same issue with my new Renault and Nexus LG. The phone pairs with the carkit and connects the first time without issues and works like fine. Once someone calls, the connection is terrible or lost! I checked the phone compatibility list at Reanoult and the NEXUS LG is on that list. So it should work. Updated R-link2, same issue. I went to the Renault garage and they told me that this is a bug in the Renault software, they can't do anything about it. Can't believe this, there should be a solution or fix.
I have a 2013 Honda CR-V EX. When I bought the car, I had a Verizon Galaxy Nexus. The stock ROMs never did work right for reading back text messages, and at some point a Cyanogenmod contributor figured out the problem (syntax issue I think when Google change their BT stack or something to that effect), and it worked great when I started running nightlies. I picked up a Z3 compact last year, and I always get the notice that the phone doesn't support the Bluetooth MAP function. I hoped it would start working when we got Lollipop, but same thing. Have any of you had success in using Bluetooth MAP on a 2012-2014 Honda? I'm open to suggestions on things to try.
I use BT at home daily for listening to music and netcasts. I have a couple of different BT speakers as well as the awesome Panasonic Link-to-Cell phone system for those who have dropped their home hard-wired phone lines. I also use BT constantly when I am in my car.
With my LG G2, BT connection was seamless and immediate, all the time, for years now. It connected to multiple devices as soon as I walked in the door and with my car audio as soon as I started my car.
With the N5, it always needs to be re-paired manually - especially at home where there are two devices waiting to pair with it as soon as I come home. It'll pair with the Panasonic phone, but when I select a speaker, the N5 disconnects from the Panasonic and then I have to re-pair with it. It will work once I spend a moment managing connections. In the car it often pares immediately, but sometimes not.
Another observation is that the N5's BT range is short, and it will drop if a line-of-sight gets interrupted momentarily.
In an attempt to fix, I have wiped the cache for both Bluetooth apps that come with the VZW N5 - that didn't help. Then, I wiped the system cache, also no dice. I wonder if this is carrier-dependent (I am on VZW) or something to do with older BT devices and the newer BT protocol that the N5 uses. I've read that the N4 has similar BT issues.
Overall, it's usable, but not as good as my old G2. Anyone else have these issues? Fixes??
This issue persists to this day. I can accommodate it with some manual intervention when I want to connect to my BT speakers.
Looking to get a BT 4.x speaker to see if it's just a BT version issue.
I only use Bluetooth in my car and I haven't had any issues whatsoever. Always connects as soon as I start the car and never drops the connection or anything. It syncs my contacts and everything just fine as well. I don't use Smart Lock however. Maybe try turning that off?
billykxda said:
or something to do with older BT devices and the newer BT protocol that the N5 uses. I've read that the N4 has similar BT issues.
Click to expand...
Click to collapse
I think that's the case. For some reason samsung's 4.1 Bluetooth protocol is not backwards compatible. Ever since the s4 Bluetooth meta data has stopped working in my 2012 Mazda. Works fine with my N5 (nexus 5) and my LG G4. If I had to bet I think that's the issue with you. I could be wrong. Just thought I'd share.
mrnovanova said:
I think that's the case. For some reason samsung's 4.1 Bluetooth protocol is not backwards compatible. Ever since the s4 Bluetooth meta data has stopped working in my 2012 Mazda. Works fine with my N5 (nexus 5) and my LG G4. If I had to bet I think that's the issue with you. I could be wrong. Just thought I'd share.
Click to expand...
Click to collapse
Note 5 always works with my car, does not drop or anything but it has an unstable connection to my samsung gear circle headphones. I believe it is the 5.1.1 update, because they work with my wife's note 3 just fine and they used to work fine before the 5.1.1 update.
Did you ever resolve your issue? looks like some are successful after getting their device replaced and others are not and say the problem comes back. All seems to be related to the 5.1.1 update..
Bluetooth and Note 5, horrible combination
IceCreaMan said:
Did you ever resolve your issue? looks like some are successful after getting their device replaced and others are not and say the problem comes back. All seems to be related to the 5.1.1 update..
Click to expand...
Click to collapse
Thanks for writing. I found out that if I disable wifi, it connects a little better, though not as good as my wife's phone, Note 3 (my previous phone)
I tried to find ways to change the frequency it connects, but google was not helpful. Maybe some of the experts here could be helpful, I do not know.
Anyways, I tried to connect to our smart bulb yesterday. It would pair, but would never connect, wifi or not. On the other hand, the Note 3 connected to it immediately.
They keep updating the gear circle software but it is the phone fault, since gear circle is able to connect to my laptop from even another floor!
It's not the BT device... I have terrible luck with expensive purchases and my note 5 was no exception. I upgraded from a galaxy S relay (love keyboards) and about 1 month later my Bluetooth stopped working from all through my house to needing a DIRECT line of sight and max range of about 2 feet. Netflix, hulu, audible all pretty much useless with this issue.
I returned it and got a new one (not referbished) and I noticed a slight lag in key strokes. About 2 weeks go by and the bottom half of my screen is going haywire. Trying to scroll a Web page and it would click everywhere. Typing like I am now would result in 100s of extra letters I was never close to pressing. I returned it and got a referbished one and same thing... my 4th one which I'm using to type this just started doing the Bluetooth thing and I'm so mad.
It's not the Bluetooth device because I tried my old Plantronics I used for 5 years, my new Plantronics, my car, and these weird speakers that have water pumps in them and the issue was the same. I love this phone but it seems to hate me...
Android version
time4my5thnote5 said:
It's not the BT device... I have terrible luck with expensive purchases and my note 5 was no exception. I upgraded from a galaxy S relay (love keyboards) and about 1 month later my Bluetooth stopped working from all through my house to needing a DIRECT line of sight and max range of about 2 feet. Netflix, hulu, audible all pretty much useless with this issue.
I returned it and got a new one (not referbished) and I noticed a slight lag in key strokes. About 2 weeks go by and the bottom half of my screen is going haywire. Trying to scroll a Web page and it would click everywhere. Typing like I am now would result in 100s of extra letters I was never close to pressing. I returned it and got a referbished one and same thing... my 4th one which I'm using to type this just started doing the Bluetooth thing and I'm so mad.
It's not the Bluetooth device because I tried my old Plantronics I used for 5 years, my new Plantronics, my car, and these weird speakers that have water pumps in them and the issue was the same. I love this phone but it seems to hate me...
Click to expand...
Click to collapse
Quick question, do you have android 5.1.1 or 6? I still have 5.1.1 and thats when it started with the problems. It was all fine and dandy with android 5.0.
My wife has a Note 3 with 5.0 and the same headphones are just fine with it.
I have been waiting for android 6 to see if it works out.
My Note 5 upgraded itself to Android 6.0 and all my bluetooth problems are solved magically. I cannot believe how they can manage to screw up things for so many months and we have to wait for the new OS to have it solved. For Samsung Gear Circle none the less. I know I am not buying bluetooth watches or anything in case they screw up bluetooth again in an "update".