Hello Note forums!
I got my blue N7000 today all shiny and new. As soon as I connected to my home wifi it prompted me to upgrade to ICS, which I did. I then did the rootgalaxynote June 2nd root method and added CWM. Rebooted and everything was peachy and awesome (and I'm a previous S2 owner!)
The only issue I'm really having is the bluetooth. It connects to all 4 of my headsets more or less (some only for phone audio). But it only pairs with my car's head unit. I'll explain.
My n7000 pairs just fine with my Eclipse CD5030. However, I cannot get it to then connect for audio. It just hangs. The head unit is fine - it worked with my 3 previous bluetooth phones withouse issue - HTC Hero, HTC Evo 4g, Samsung Galaxy S2... the only difference is this is the first phone with ICS, the previous phones were all 1.x or 2.x and worked great.
I looked up the details of the CD5030:
BT 2.0
A2DP v1.0
AVRCP v1.0
I would imagine the note is backwards compatible with these relatively old versions. Is there a workaround or is this possibly a bug?
Thanks in advance guys.
Related
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.
Hello everyone. New owner of Motorola MB886 (AT&T Atrix HD) - bought brand new/refurb off local craigslist. Sweet deal, had it rooted, flashed Mexican Retail right away and then unlocked bootloader (just to try other ROMs in the future). Problem is the bluetooth. Wife uses the phone, can pair no problem to the Lexus she drives, but no audio coming in or out during calls. Everything else including streaming works normal. Sometimes the audio kicks in, after a minute or so of wait, for no apparent reason. Device is connected well, no drops. Is this a known bug with Atrix HD on the stock 4.1.2 (JB) ROM? I could see bluetooth being broken on Custom experimental builds, but wasn't expecting it to be the problem. Any fix or other ROMs with working bluetooth? I search and didn't see a dedicated thread, other then few mentions of various bluetooth problems. Google search problem is not limited to Atrix, many RAZR devices have same issue. Just wanted to know what my options are. Thanks.
On ICS, never had any problem with my Kenwood car stereo. Reliable pair, calls, music.
Phonebook works, except favorite contacts don't show up (must be a Kenwood problem).
SMS doesn't really work but then again it's been years since they were trying to support SMS on head units.
Also worked fine with a rental Cruze and actually the title of the current song was displayed on the car stereo (my Kenwood doesn't do that).
Is this it? No other confirmation of Bluetooth problems? Can I at least get a clue if this is a result of wrong flash or problem with the ROM, or any AT&T stock users having the same issue? To me it looks like phone connects using basic sound profile, not as headset. Thanks everyone.
Here is an update to my issue with bluetooth. I ended up creating a full backup using CWM recovery and did a factory reset. Then restored just the data partition (from CWM advance restore) and re-mapped the bluetooth. Everything is working like charm now. Lesson, don't forget to do factory reset after flashing, or if any problems arise. Good luck to everyone.
I have a Galaxy Note 3, rooted and running hyperdrive Rls6
Right out of the box (stock) I wasn't able to pair with the Jawbone mini jam box or any bluetooth headsets the devices wouldn't even show in the device list.
Rooted phone and put custom rom on and still have the same issue.
Yes I have connected all devices to 2 different S4s and to a Galaxy tab 3 they pair and connect without an issue
I mainly want to connect to my Jawbone mini jam box and Plantronics m55 headset
Please Help Me
I'm sure the following is a software issue but I don't know where to report this bug.
When I am listening to music or watching videos on my Note 4 through my Bluetooth stereo headset, I get pops and clicks noises every 2-3 secs and has been driving me up the wall. Talking with someone over the phone through Bluetooth yield no noises. Only way to fix this was to use a wired headphone/headset. My Note 4 is 910C with the latest firmware, not rooted nor modified in any way, everything is at stock.
After a lot of troubleshooting I finally figured it out that it wasn't my BT headset being faulty, nor my Note 4's BT, I will explain below.
I have my Note 4 paired with the following Bluetooth devices:
- LG HBS-900 Headset
- LG HBS-800 (Black) Headset
- LG HBS-800 (White) Headset
- LG HBS-700 Headset
- Sennheiser MM 550-X Headset
- Creative T6 Series II (Desktop PC Speakers that has Bluetooth)
- Samsung Gear Fit Watch
The issue is affecting the HBS-900 and both of the HBS-800. I have done the following which didn't fix the issue:
- Unpair then Re-pair
- Unpaired other headsets
- Restart Phone + Pulled Battery
- Went to "Application manager > Bluetooth" and cleared Cache and cleared Data
- Went to Recovery and cleared the cache
I was left with the last resort to re-flash the latest firmware. But I had a brainwave and decided to unpair the Samsung Gear Fit because out of all the paired devices, only the watch uses Bluetooth 4.0 while the headsets and speaker use Bluetooth 3.0.
Lo and behold, the popping and clicking noises disappeared completely right away. I paired all the other headsets to the phone, and audio was still clear. I replicated the issue again by pairing my Gear Fit back to the Note 4, and immediately the noises were back. And this issue occurs even without having the watch connected to the phone! So now I'm forced to pick either my headset or my watch....
Model N910C
Firmware Origin: XSG (United Arab Emirates)
Firmwares issue experienced: ANK5 and AOA2
Hi budy, have the same problems. But I think problem is between wifi and bluetooth. Whenever there is a information change via wifi to internet there is some strange noice or once in a while bluetooth is bracking up. There might be some frquency problems. So far no solution to these. Just reconnect.......
910f + gear live + connected audio to my home theater by BT , streaming all access music via WiFi = no problem .
Lollipop 5.01 Fixed It...... I think!
quincho54 said:
Hi budy, have the same problems. But I think problem is between wifi and bluetooth. Whenever there is a information change via wifi to internet there is some strange noice or once in a while bluetooth is bracking up. There might be some frquency problems. So far no solution to these. Just reconnect.......
Click to expand...
Click to collapse
Not to do with WiFi in my case. I could have them switch on or off, connected or not connected, the noise will still be there.
But Good News! I saw the official Lollipop for N910C on the other thread, thought what the heck gonna flash it. So I flashed it via Odin but did not wipe my data, seems Bluetooth is behaving now. Maybe the previous mini updates did not do anything to the BT drivers and on Lollipop I saw the version and it's a newer version.
Didn't really want to do this at first cause it's only been released and bound to be buggy, but I did it!
Hi guys,
I have a strange problem with my bluetooth wireless earphones B&O Beoplay H5.
On my previous Note 5 (bluetooth 4) they were playing great, but now on Note 8
(bluetooth 5.0) on pairing I get on the phone a message that "Beoplay H5 canceled pairing"
I hope that on Orego, where the bluetooth should be somehow upgraded
the problem dissapears, but for now if somebody from you knows the solution
please share.
Many thanks in advance for any help.
I have seen this before, bluetooth has problems with backwards compatibility some times, why? I dont know, happens with some devices, that is, I have had bt 3 that did not worked with some 2.0, 4.0 that did not with 3.0, 5.0 that did not 4.0, I have been observing this since my S3, and it has been worsening as bt protocols get higher, it seems that your note 8 having bt 5.0 will reject some, if not all inferior bt protocols I dont think oreo will fix this, as I said, I have seen this happening with gingerbread honeycomb, ice cream, kit kat, lollipop, marshmallow and now with nougat