Related
Hey All,
I have been scouring the web in hopes of answers and can find none. Evidently I'm not the only EVO owner in this boat either. I own a 2011 Ford Explorer with Sync & MyFord Touch (Fully updated). I pair the phone to the car it makes the connection fine. Begins the setup and sometimes will even connect and be recognized for a bit. But then the phone drops the bluetooth headset part of the connection. It appears (but I can't confirm) that Bluetooth streaming audio is still connected. There was a blissful 3 day window where it all just worked. Then it went to hell...... I saw one post where it said to switch the Bluetooth name back to "PC36100" and that didn't help. I saw another that said use a 4 digit pairing code and that didn't help either.
Its worth noting that I'm running Myn's Warm 2.2 rls5 with the stock & fully updated HTC kernel. So here's what I'm hoping to figure out:
*Have you had this issue with ANY car?
*Have you had this issue with Ford SYNC/MyFord Touch
*Aside from unpairing & repairing were you able to get around it?
*Is there a Kernel with a better bluetooth stack I should try?
Thanks for any help, many thanks will be given!
Unfortunately, the HTC bluetooth is totally worthless. I have a 2010 Ford Focus with Sync and it would connect and sometimes work for awhile, but people on the other line always complained of poor quality. And it wouldn't even connect all the time either. Lots of deleting and readding the phone.
Couple weeks ago I switch to CM7. Since CM has a bluetooth stack they built themselves and actually implemented correctly, I haven't had any problems pairing my phone. I can make calls, stream music, gps, etc and it is all fine. Always connects too. What is nice also is the audio will automatically stop if Google Navigation is giving directions or if someone calls. When I shut my car off and open the door, the audio stops and when I get back in it automatically starts again where it left off.
Basically if you want to use your Evo with a Ford Sync system, you'll need to run a version of CM.
Arg. I'm still waiting on my Explorer
On my 08 Explorer with Sync and Myn's RLS4, all is good. I turn BT off and make sure it is on before I turn the key. I stream audio constantly, and talk a bit. I literally just got around to putting on RLS5 today, haven't driven yet.
I partially agree with teamgreen02. It's HTC, not Ford. Does texting work with CM7? That would push me over the edge (or Explorer, pun intended)
It seems that there are a bunch of phones that have issues maintaining connectivity with the latest Sync system. I had to re-pair a BlackBerry to an '11 Explorer this afternoon. There is a backwards pairing procedure that may help rectify your issue. If you try searching for your phone from the vehicle instead of searching for sync from your phone, it has, in my experience, minimised connection drops, especially on the latest versions of Sync...
Btw, I am like the only tech at my dealership who really understands how to even pair phones to Sync, let alone diagnose the concerns our customers have described. There is also a system compatibility chart that we reference to determine if a particular device has been tested and verified to work with certain features of Sync. Last I checked (the October 2010 update) the Evo still wasn't certified compatible/tested...
Sent from my PC36100 using XDA App
Does anyone have any updates on this? My wife's Sync is working fine with her Evo but the sound quality sucks when she calls. Her phone isn't rooted.
I did update the Sync software from v1 to 1.1 (She has a 2008 Ford Edge Limited) but need to do further updates to the system since there are updates available.
Here is my experience/.02.
My wife drives a 2011 Ford Edge with sync....she has a stock Evo4g. When she bought the car 2 months ago, bluetooth seemed to work fine...now she is having the exact same issues everyone else is having. The bluetooth connects/disconnects and just plain doesn't work. I attempted to fix it and.....no. If i unpair from both the car/phone then retry to connect them, it connects for a second and when it tries to send the phonebook from the phone to the car, the connection dies. The phone still displays that bluetooth audio (not phone) is connected.
I then tried my Evo 4g (CM7) on her car...no problems whatsoever. Sync'd and connected fine...phonebook transferred over in about 5 seconds and everything worked great.
To note, my Evo 4g also works perfectly on my 2011 Infiniti G37...
So I think my example further proves that HTC's bluetooth software is likely the causative agent and is likely junk....root or die i guess =p
hope this helps someone
I rooted and installed MIUI and dont have any problems yet with sync.
Although,
I was looking looking to pull the bluetooth stack of the droid X which has the MAP bluetooth profile, that will allow ford sync to read and write text messages for you.
any ideas on how to do this? Or where to find in in the droid X?
2010 Ford Focus here, works fine for me. Using Fresh 3.5.1.
The bluetooth stack should all be dependent on what kernel you are using on your rom, so if you already have it rooted, try to change kernels and see how it improves...
as far as the MAP profile, i found this thread in the Q&A section, and it also recommends pulling the MAP profile (for text messessaging) from the motorola droid kernels.
I wish i knew how to do this.
I was hoping for someone to be able to do this for us
EDIT: I also found this thread:
http://forum.xda-developers.com/showthread.php?t=741332
its trying to get the MAP profile into the nexus one...
they found the new bluez stack had the MAP profile included:
http://code.google.com/p/google-summer-of-code-2010-bluez/updates/list
I have not used sync in a long time in my 2010 escape, but I'm wondering if the text message function works as well. Any word on this?
Sent from my PC36100 using XDA Premium App
lawmangrant said:
I have not used sync in a long time in my 2010 escape, but I'm wondering if the text message function works as well. Any word on this?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
No, the text messaging does not work for the unrooted Evo and it doesn't work for a rooted Evo under Myn's Warm TwoPointTwo RL5.
I Just had a 2011 Explorer limited for the past week as a rental and it worked fine for me (music & calls). I know this does not help much hope you get it going.
i had my EVO running fresh 3.5 and worked great in my Escape, i just switched to twopointtwo ROM and now here i am looking for a solution, not sure if its the rom or the kernel since i switched both..
alexdogg said:
i had my EVO running fresh 3.5 and worked great in my Escape, i just switched to twopointtwo ROM and now here i am looking for a solution, not sure if its the rom or the kernel since i switched both..
Click to expand...
Click to collapse
got it working for a day but its disconnected again, im going to explain what i did hoping someone with more knowledge can help us SYNC users to connect bluetooth
used fresh EVO 3.5 for a while and worked great, then i got bored and changed rom to myn's warm 2.2 with the kernel included and bluetooth started disconnecting after 30 seconds or so...
i tried
ms79723's SBC for Netarchy's CFS More Aggressive 4.1.9.1 Kernel (v7)
Ziggy471 Warm TwoPointTwo RLS4 Kernel
they didnt work either... so heres the funny thing..
i wiped and reflashed a fresh version of the same rom (Myn´s warm 2.2), this time i didnt restore anything, no apps, no contacts, anything, left it clean.. then i paired it up and voila.. it worked for a long time in my ESCAPE, so i thought it was working and restored all my apps and data.. and to my frustration... its disconnecting again.
so does this have to do with the kernel or with some apps or what.
has anyone figured out how to get sync working with blue tooth messaging.
marcw2 said:
has anyone figured out how to get sync working with blue tooth messaging.
Click to expand...
Click to collapse
I don't think the android kernels have the message access protocol that is needed for this to work.
Sent from my HTC Evo 4G
2010 Ford Focus. Bluetooth sucked with stock ROM and warm, dropped connection all the time. Works great with CM7. Definitely an issue on the phone side and not the car in my case.
I am also wondering if we can somehow get the text messaging working. I don't think its officially supported on any Sprint phones.
2010 Moutaineer here - never had a problem with Bluetooth on rooted stock EVO ROM.
Listen to music all the time - even the "call-transfer" functionality works fine when I enter the vehicle while talking on the phone.
Only thing is - I wish the damned thing would auto-synch for media-audio on Aux1 instead of me having to select the source all the time - anyone know how to do this?
2010 Lincoln with mytouch/sync and rooted with stock rom. No problems at all. Sometimes it gets a little static sound but I just turn my Bluetooth off then back on.
Sent from my PC36100 using XDA App
Think the problem lies with the Sense BT stack.
Hi guys,
I have a very strange problem with my beloved note. After I get in the car and drive off I remember that I have to turn bluetooth on so it can connect to the hands free system. The thing is that it doesn't connect automatically, I have to go into the settings and tap the BT name in order to connect it. If on the other hand if I have BT already enabled on the phone before starting the car, it conmects automatically. With the first version of GB the Note had in November I didn't have this issue, but after the first update it started not to work. Now I am on official unrooted ICS 4.0.3. Never had this problem with any other phone.... Any help would be highly appreciated.
Thanks.
Sent from my GT-N7000 using XDA
Anyone?
Sent from my GT-N7000 using XDA
n.vasiliu said:
Hi guys,
I have a very strange problem with my beloved note. After I get in the car and drive off I remember that I have to turn bluetooth on so it can connect to the hands free system. The thing is that it doesn't connect automatically, I have to go into the settings and tap the BT name in order to connect it. If on the other hand if I have BT already enabled on the phone before starting the car, it conmects automatically. With the first version of GB the Note had in November I didn't have this issue, but after the first update it started not to work. Now I am on official unrooted ICS 4.0.3. Never had this problem with any other phone.... Any help would be highly appreciated.
Click to expand...
Click to collapse
You can try Automatic Bluetooth Toggle PRO (I think there is trial version on Google Play). I don't know if it will help you. If not then I'm sorry you will probably have to go back to GB. I'm still on GB as I was also having issues with bluetooth on stock ICS (CM9-based ROMs worked well though).
Thanks a lot. GB had the same annoying problem though :-(... so it's not that....
Sent from my GT-N7000 using xda app-developers app
Hi,
Did you allow the pairing automatically between the devices?
When you pair at installation, it isn't permanently (= automatic) yet. When you get in your car and pair for a second time, normally your phone asks you if you allow your hands free system to access your phone; at that moment you have to tick "don't ask me again" and "yes" for automatic paring.
You might want to disassociate the two and try a new setup (pairing).
To disassociate, stop the system in your car (that cuts the BT connection between the two), disassociate on the phone (push and hold your hands free system in the BT section of the phone and chose disassociate), reboot your phone (so it forgets your cars BT system) and start pairing all over again.
I would provoke the second connection so you get the "automatic" question to make it work.
Good luck :good:
I have the same problem with the original ICS rom.
Flashing a custom ICS rom fixes this problem.
I tried kingdroid (worked ok)
I tried Cyanogen (phone ok, no media audio over BT but connection OK).
I had a similar problem after upgrade with stock ICS through software update. I couldn't pair Note with Mercedes bluetooth. Galaxy Note recognized Mercedes BT & vice versa, but connection was impossible. I read every forum on internet but no help. Everybody was blaming Samsung and ICS. Some suggested resseting Note to factory default, others downloading bluetooth app etc.
Until...I finally figured out that something was confusing my car's BT, so I resseted car system, and the problem was solved.
Sent from my GT-N7000 using xda app-developers app
These is a twist with "old" BT systems and ICS: Old BT systems want you to insert a pin code, ICS wants you to to confirm a code that the BT system sends and that ICS shows on the screen.
It's obvious that that ICS on an old system can be a hassle.
A work around is to put the car in discover mode (so it shows the pin code) and then send a contact (or a picture) from the phone to the car system. As the car replies, your phone will show the possibility to insert the PIN Code.
After that your system should work.
At second connection make the pairing automatic (as I described above) and you're happy.
(This is not my discovery, I found this solution on the SE XPeria Ray forum as I had problems with my wifes phone )
Thaks a lot. I will try as soon as I get the chance and will let you guys know.
Sent from my GT-N7000 using xda app-developers app
So with the workaround mentioned above - it doesn't work. When turning on bt on the phone it won't automatically connect to the car.
Sent from my GT-N7000 using xda app-developers app
Try A2DP Volume on the market.
I have the same problem as you. I used a leaked ics rom on my galaxy s2 and also had the same problem we now have on our ics galaxy notes. My car's head unit is a 3 year old eclipse cd5030. For the last month ive just been manually pairing it every time. PITA. Ill try the workaround suggested earlier in this thread and let you know. Otherwise i think cyanogen mod rom may work.
Sent from my GT-N7000 using Tapatalk 2
Let me know. I am.not going through the trouble of putting anoyher ROM on the phone.just for that
Sent from my GT-N7000 using xda app-developers app
n.vasiliu said:
Let me know. I am.not going through the trouble of putting anoyher ROM on the phone.just for that
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I had similar issues with Parrot 9200 kit in my car. Paired automatically under GB but on stock ICS wouldn't pair unprompted. Sometimes it would but only after minutes.
I'm on Paranoid Android 0.4 now which is CM9 based. It's better but often still slow to pair unprompted. Main improvement for me is that the phone doesn't carry on playing music through its own speaker, like it did on stock ICS, when I turn off the engine.
There is an app on the market called "Auto Connect 2.0", but it is only available for ICS and above Android versions
atiesfo the
i have same problem with my note, but with my Galaxy S1 works fine, when i upgrade the android to 4.0.4 solves the problem.
Trying to connect the N4 to a car Bluetooth audio (2012 model car, relatively new, only 9 months old).
(1) I had a very hard time getting the two paired: lots of "connection failed" attempts until they finally connected.
(2) The phone does not send artist/track info which is surprising as I have an older LG phone running Android 2.3.4 and that sends all the info.
(3) Without any music being streamed to the car audio, if I make a phone call via the car bluetooth, when the call ends the music player on the N4 starts automatically. This is very annoying, not sure if it's a problem with the car implementation sending a "play" command at the end of the call or the N4 doing something weird. I tend to blame the N4 as two other phones, an iPhone and the older LG mentioned above do not do this.
(4) The car has a play/pause toggle that it can send to the bluetooth player. Pause works, the player on the N4 pauses, but then play doesn't work, I have to hit play on the device.
(5) After I use bluetooth on the N4, I find that sometimes the widget toggle can no longer turn bluetooth on/off until I reboot the phone.
(6) After I use bluetooth on the N4, the phone sometimes randomly reboots. Not sure if it's really related or just a coincidence. Given (5) above I suspect something is going on.
Anyone else having such a hard time with the bluetooth part? Potential hardware issue or simply buggy software that we can hope to get addressed at some point?
I have experienced the issue with track information not being sent. Also random changes in volume during playback. Seems there's still some work that needs to be done in 4.2 regarding blue tooth.
Sent from my Nexus 4 using Tapatalk HD
sirxdroid said:
(2) The phone does not send artist/track info which is surprising as I have an older LG phone running Android 2.3.4 and that sends all the info.
Click to expand...
Click to collapse
Is this an issue that can be addressed by flashing a custom ROM or perhaps using a different music player than stock or is there more to it, deep down in the bluetooth drivers and it would need a fix from Google in the form of new drivers?
Yeah I have had a few issues too. My track/artist/album names do not send where my S2 sends them. Also the headunit I have has buttons for shuffle and repeat and these do not show up at all (I assume because it detects they aren't supported). I haven't taken a call yet or tried turning BT off after streaming but I'll give it a shot and see.. My nexus 4 also randomly shuts down for no apparent reason sometimes (rarely atm). I think it's just 4.2.1 problems - I doubt a different music app will fix it (I tried one), custom ROM may work though..
My N4 is paired with an Alpine 135BT and it's worked very well so far. I initially had some trouble connecting but once they were paired I didn't have any additional connection issues. The N4 does automatically play as soon as it connects to the unit. I've got BeyondPod and Spotify installed and for whatever reason it always defaults to BeyondPod instead of Spotify even if I had BeyondPod closed and Spotify open. Not a big deal to me though.
Are you running the stock rom or a custom rom? I had my EVO LTE hooked up to the same head unit. It worked perfectly on the stock software but gave me all kinds of trouble when I started using custom roms. Otherwise, it could just be that the N4 and your particular head unit just don't play nicely together.
sirxdroid said:
Trying to connect the N4 to a car Bluetooth audio (2012 model car, relatively new, only 9 months old).
(1) I had a very hard time getting the two paired: lots of "connection failed" attempts until they finally connected.
(2) The phone does not send artist/track info which is surprising as I have an older LG phone running Android 2.3.4 and that sends all the info.
(3) Without any music being streamed to the car audio, if I make a phone call via the car bluetooth, when the call ends the music player on the N4 starts automatically. This is very annoying, not sure if it's a problem with the car implementation sending a "play" command at the end of the call or the N4 doing something weird. I tend to blame the N4 as two other phones, an iPhone and the older LG mentioned above do not do this.
(4) The car has a play/pause toggle that it can send to the bluetooth player. Pause works, the player on the N4 pauses, but then play doesn't work, I have to hit play on the device.
(5) After I use bluetooth on the N4, I find that sometimes the widget toggle can no longer turn bluetooth on/off until I reboot the phone.
(6) After I use bluetooth on the N4, the phone sometimes randomly reboots. Not sure if it's really related or just a coincidence. Given (5) above I suspect something is going on.
Anyone else having such a hard time with the bluetooth part? Potential hardware issue or simply buggy software that we can hope to get addressed at some point?
Click to expand...
Click to collapse
(1) Haven't had any connection issues so far on my vehicle or my wife's.
(2) Currently stock Android uses AVCR v1.0 which only only allows you to control via Bluetooth (play, pause, etc) but not send track info. Other manufactures that customize Android (LG, Samsung, etc) will sometimes use v1.3 that supports track info. That's why your old phone did it.
You could install a custom Rom that has v1.3. I think cm10 does.
(3) Again, not happening on my two cars. The only time the music starts after a call is if it was playing before the call. I'm wondering if you have another music/podcast player that is taking over Bluetooth controls and causing problems. I use the stock player and Player Pro. If I don't disable the headset/BT controls in Player Pro I have control issues.
(4) I have the same issue. To get around this I cheat and push the track advance button on the radio to play the next track.
(5) This is an issue I've had on all of my previous android phones. I haven't noticed I my N4 because I never toggle off Bluetooth anymore.
(6) Not having this problem but maybe try solution in (3).
Sent from my Nexus 4 using xda premium
got the sony mw600 for bluetooth audio.. no id tags on display.. on every musicplayer (play music, poweramp, cm musicplayer..) the same.
dont know why, but today even the start/stop, forward and prev. buttons didnt work! the only thing i can use is volume control..
anyone an idea?
Any luck with this?
I want to buy one but couldn't find it in Sri Lanka so planning to order one via ebay & need to check if it works. Running cyanogen mod 10, heard that the bluetooth stack was updated on CM which supports most of the features since stock rom only has older stack version which can have issues!
clsmn said:
got the sony mw600 for bluetooth audio.. no id tags on display.. on every musicplayer (play music, poweramp, cm musicplayer..) the same.
dont know why, but today even the start/stop, forward and prev. buttons didnt work! the only thing i can use is volume control..
anyone an idea?
Click to expand...
Click to collapse
dark5un0 said:
... that the bluetooth stack was updated on CM which supports most of the features since stock rom only has older stack version ...
Click to expand...
Click to collapse
using the actual cm10.1 nightly with franco r53
Wow, maybe I'll wait for a few weeks & see if it works out for you..
Sent from my Nexus 4 using xda app-developers app
dark5un0 said:
Wow, maybe I'll wait for a few weeks & see if it works out for you..
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well.. Sound and controll works.. even headset-function works for telephone calls.. only thing not working now is id for tracks
Awesome! Thanks for the reply! I hope it worked out soon!
Sent from my Nexus 4 using xda app-developers app
I also have the track name issue. This is a massive let down. I like to just get in my car and flip through tracks with my phone in my pocket. My iPhone did this, my s3 did this. Why not the nexus 4? Come on Google. Sort it out
TrickyTree1984 said:
I also have the track name issue. This is a massive let down. I like to just get in my car and flip through tracks with my phone in my pocket. My iPhone did this, my s3 did this. Why not the nexus 4? Come on Google. Sort it out
Click to expand...
Click to collapse
my impression is that almost nothing involving Bluetooth functions as it should currently on the N4. I can't even get a mouse to work. what a shambles! it's not as if BT is some new technology. this all better get sorted out in 4.2.2.
If I'm not mistaken Google moved to a new Broadcom b/t stack. Yeah, good move! And I agree, b/t has been around for like what at least 10 years now? You'd think that getting track info should be a given by now. I have a crappy old LG phone running Gingerbread and it has no issues at all.
Bluetooth
When I got the N4, I connected my helmet headset to it and everything seems to work fine. My headset supports ad2p music and phone. Both connected and both worked, including play controls. Not sure about the audio quality, I didn't test it long enough After I flashed Jellybro (CM 10.1 Kang) Music connects, but phone goes on a connect/disconnect loop. Audio needs further testing, can't tell if the left side is off because of the bluetooth or not. Controls work most of the time, every now and again playback will decide to pause itself and sometimes the play command doesn't work. Haven't had a chance to flash stock CM 10.1 nightly yet either.
Play/Pause Works Inconsistently
Has anyone had this issue?
I am on stock 4.2.2, I connect with my car stereo no problems. I use to be able to just hit play/pause on my car stereo and it would just play music from Google Music. Now, sometimes when I hit the play/pause button on my stereo, it won't play. I have to manually hit play from my phone. After initially doing that, then I can hit play/pause and the control is there. I haven't had the problem since I got my phone on Nov 14th, this issue just started to happen. I notice this after installing Light Manager, but I have uninstalled it and still the issue is there. It is inconsistent, but the issue is more often than not.
Thanks in advance for your input.
Just reiterating, stock Android does not show artist/track info, it is not in the protocol, but you can skip tracks or go back to previous tracks. If it is important to you, you should root and get a custom ROM, not sure which ones for N4 has it though, been too happy with stock to root.
About time, Google:
http://www.androidpolice.com/2013/0...vrcp-1-3-coming-to-android-with-api-level-18/
Is anyone else having problems wit Bluetooth audio streaming in car? My music sounds like it's speed up a tiny bit. Kinda like chipmunks voices. Is this a ROM issue?
Sent from my Nexus 4 using xda app-developers app
I am subscribed to a few Google group conversations about Bluetooth issues with the Nexus 4 and reading each complaint prompted me to ask. Does anybody out there with a Nexus 4 NOT have an issue with Bluetooth?
I am on my 2nd replacement Nexus from Google Play device support and a third is on the way. If this third device doesn't work, then I either can opt for a refund or wait for Android 4.3 to hopefully fix it, if the problem is software salvageable. So I'm just curious if anybody's N4 actually has no issue with Bluetooth and in what manner do you use Bluetooth and with what devices?
Sent from my Nexus 4 using xda app-developers app
I got my N4 in the first batch from play store back in November
I have never had any issue with Bluetooth
Granted I don't use it often (once every couple weeks on average) but each time I have its never failed in any way.
I have used in my car for hands free and also to send pics to my GF's phone and a couple times to transfer files from my laptop
Started out stock and then last few months been on custom ROM's with no change
Day 1 N4 here too - never had bt problems. Pairs with my car, Motorola headset, and Moga Pro just fine. Fiancée's stock unrooted N4 pairs with her car and jawbone speakers fine. Hoping 4.3 brings LE bt support for my fitbit flex, but besides that haven't had to do anything but turn on bt and pair.
What problems are you having? Haven't heard of people really having issues...
Sent from my Nexus 4 using xda premium
To my knowledge from researching the problem myself people claim it's a hardware issue based on some of the responses they get back from google I guess? I knew right away it wasn't just me when someone else I know has a N4 as well and when I use my LG Tone with his while connected via WiFI it pulls a dubstep and drops.
Other than that it's the only issue I have with BT that I can replicate. Hands-free while connected via data works like it should.
No Bluetooth problem here.
pshaww said:
I am subscribed to a few Google group conversations about Bluetooth issues with the Nexus 4 and reading each complaint prompted me to ask. Does anybody out there with a Nexus 4 NOT have an issue with Bluetooth?
I am on my 2nd replacement Nexus from Google Play device support and a third is on the way. If this third device doesn't work, then I either can opt for a refund or wait for Android 4.3 to hopefully fix it, if the problem is software salvageable. So I'm just curious if anybody's N4 actually has no issue with Bluetooth and in what manner do you use Bluetooth and with what devices?
Click to expand...
Click to collapse
Stock 4.2.2 doesn't work properly with my car (BMW E61 5-series). Basic phone works, but no contact sync due to bugs in the N4 bluetooth stack. Moved to CM10.1 which contains various fixes for this and it's worked perfectly since then.
Honest truth - if the first device didn't work and the second was the same, why on earth would you assume that this was a hardware problem and keep sending the phone back? Either request a refund, switch ROMs or put up with it!
Oh sure I guess I have heard people mention that... BT and both 2.4ghz and 5ghz wifi coexist just fine on both N4s here. I just wish it could take advantage of my ac router.
Sent from my Nexus 4 using xda premium
No problem here, using it everyday in my car
Tapatalk 4 beta via Nexus⁴
hi!
the problem is there, that's a fact, and i have it too...
https://code.google.com/p/android/issues/detail?id=42255
http://www.youtube.com/watch?v=Ipud-wAAE0E
i wonder why this isn't fixed by google? maybe really a hardware related problem?
Yesterday I had the same problem with bluetooth like this one in the video.
Sent from my Nexus 4 using xda app-developers app
I have no issues with Bluetooth, it syncs with my laptop and headset. Also I have a December nexus.
Sent from my Nexus 4 using xda app-developers app
pshaww said:
I am subscribed to a few Google group conversations about Bluetooth issues with the Nexus 4 and reading each complaint prompted me to ask. Does anybody out there with a Nexus 4 NOT have an issue with Bluetooth?
I am on my 2nd replacement Nexus from Google Play device support and a third is on the way. If this third device doesn't work, then I either can opt for a refund or wait for Android 4.3 to hopefully fix it, if the problem is software salvageable. So I'm just curious if anybody's N4 actually has no issue with Bluetooth and in what manner do you use Bluetooth and with what devices?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Try matr1x kernel. I also had the same bluetooth problem since the first day. I installed d matr1x kernel v10 and now it's solved. Les changelog.
I have had zero Bluetooth issues. I pair with my pioneer in dash for pandora , Bluetooth Google play music, hands free and so on.
Cm10.1
Faux kernel
Sent from my Nexus 4 using xda app-developers app
No Issues
Bought my N4 a month ago and I have used Bluetooth hands-free headset, transferred files from my old phone and from my netbook without any problems. Haven't tried stereo audio, though.
Got my N4 in the second batch of those available and have no issues pairing with my vehicle. I don't use Bluetooth for anything else, though
Bluetooth generally works, it only screws up from time to time for things like pairing with a new device. It's been more or less this way since JB and generally if you have a regular bluetooth setup of headset, in-car radio etc, it 9/10 works just fine.
Introduce some complications and it does wonk out sometimes. I've had plenty of times where it wouldn't want to pair right to my laptop or desktop after I factory reset my device. Sometimes it just won't get picked up either when BT is on, visible and another device is looking for it.
I believe I remember reading that there was a legit explanation for this regarding drivers and or some security thing but it's been long enough that I don't remember what the details were or where I even read it on XDA. May have even been the GN forums.
I've seen the exact problem indicated by the video on CM 10.1. I just restarted, wiped dalvik and all was well again.
Other than that my BT has been perfect. I use it daily in my car for audio streaming and phone. At home I pair it to my PC for audio streaming and it works perfectly.
Sent from my Nexus 4 using xda app-developers app
I actually haven't run into many issues with Bluetooth. I use it mainly with Jawbones Jambox and it pairs up just fine. I think it may have dropped connection a couple times but less than a handful. I do run into problems when I miss a call from someone though. The audio quits playback though the devices remain paired.
Sent from my Nexus 4 using xda app-developers app
I guess I have issues. I leave BT on all the time and only randomly does it automatically connect when I get in my car. I generally have to go in to the BT settings and click the device to pair with. It identifies the device, but doesn't connect automatically.
On stock 4.2.2, I had issues with BT not connecting at all and it would get stuck in an on/off post ion (it would never fully turn off or turn on when I toggled the switch). I would have to reboot to get it to work. I have yet to see this happen on cm10.1, I just have the automatic connect issue with cm10.1
Sent from my Nexus 4 using xda premium
I usually have no issues pairing and using. But I definitely have these two issues:
1. BT won't turn on at all (like in the video).
2. I notice my phone hot and draining battery. I look at the BT indicator and it is blue indicating a connection but I'm not connected at all. I only use BT in the car and I'm nowhere near my car. Yet the indicator is blue and my phone is hot.
Either is resolved with a quick reboot. I'm not troubled by it but is annoying at times.
In my quest to resolve my Bluetooth issues (mainly interference issues between my moto 360 which is BT le and my car not being able to connect when the watch is on and in range). I've found many people complaining that many bluetooth issues popped up after Google switched to using BlueDroid for the Bluetooth stack around android 4.4. I came across this project https://code.google.com/p/aosp-bluez/https://code.google.com/p/aosp-bluez/ which attempts to build Bluez (the previous default Bluetooth stack) back in to android 4.4 & 5.0 (and above possibly).
Any ROM devs care to chime in on whether they'd be willing to try this in their build? I'm not against trying to build it myself but it sounds as though I'll need some drivers that may or may not be available for the N6 as it is for the N5. Any help, advice or a point in the right direction would be greatly appreciated. Thanks!
Sent from my Nexus 6 using XDA Free mobile app
bump