Hello there,
I'd like to introduce myself ! I am the typical forum's reader because I am from Spain and I usually post on spanish forums because the language but now, I have a problem that seems not to be as common as I thought:
I have a SGS2 with Vanilla Rootbox CROM running and JellyBam as 2nd rom.
I have just bought a bluetooth headset that supports AD2P and I can listen music through its "speakers" (is a system for a bike helmet) but I have tried with normal and skype calls and I cannot hear anything neither my voice is "heard" in the other side of the line.
I have tried changing the kernel: Siyah, Dorimanx and Stock kernel.
I have tried both roms (vanilla and jellybam)
I have tried it in my sister's galaxy s 2 with official rom and it works without problems so, I think that it could be an AOSP issue.
I don't know what could I try, I have been searching a similar topic but I just found old threads and just similar, not exactly the same.
So, please, could you help me with this??
Thanks in advance!!
Someone please
antonioxerez said:
Hello there,
I'd like to introduce myself ! I am the typical forum's reader because I am from Spain and I usually post on spanish forums because the language but now, I have a problem that seems not to be as common as I thought:
I have a SGS2 with Vanilla Rootbox CROM running and JellyBam as 2nd rom.
I have just bought a bluetooth headset that supports AD2P and I can listen music through its "speakers" (is a system for a bike helmet) but I have tried with normal and skype calls and I cannot hear anything neither my voice is "heard" in the other side of the line.
I have tried changing the kernel: Siyah, Dorimanx and Stock kernel.
I have tried both roms (vanilla and jellybam)
I have tried it in my sister's galaxy s 2 with official rom and it works without problems so, I think that it could be an AOSP issue.
I don't know what could I try, I have been searching a similar topic but I just found old threads and just similar, not exactly the same.
So, please, could you help me with this??
Thanks in advance!!
Click to expand...
Click to collapse
After pairing the 'Bluetooth' to ur device, go to settings>bluetooth and check the settings of the paired bluetooth and see if any thing is unchecked there for 'Phone' if so enable and then try
Sun90 said:
After pairing the 'Bluetooth' to ur device, go to settings>bluetooth and check the settings of the paired bluetooth and see if any thing is unchecked there for 'Phone' if so enable and then try
Click to expand...
Click to collapse
It is enabled already , but Thank you
Enviado desde mi GT-I9100 usando Tapatalk 2
This sucks!
Enviado desde mi GT-I9100 usando Tapatalk 2
Uup
Enviado desde mi GT-I9100 usando Tapatalk 2
Alright, well, I've had a lot of trouble in this area as well, and I have found a few ways to get the Bluetooth headset working with Skype. I'll tell you now, that it's probably got more to do with Skype than whatever ROM/kernel you're running. I tried this on my stock 4.2.2 Nexus 4, and on CM10.1 stable, running Franco's Kernel r151. The headset I'm using is the LG HBS730, which has served me well in all tasks on my phone other than Skype, of course. This is a long-standing problem I've had with Skype; the conspiracy theorist inside of me wants to believe it's because Microsoft wants to push their Windows phones by purposefully making their Android client suck, but the realist in me hopes that's not true (what with the wide range of Android hardware that the Skype Client would have to support). And besides, Skype's as broken on Windows phones as it is on Android, minus the glaring battery issues.
Okay, to get the headset working, I've done the following.
1. Before I start skype, I turn my bluetooth headset off. I wait until it disconnects.
2. I turn my phone's Bluetooth off and on again. Do not reconnnect the headset yet.
3. Sign into Skype (I'm using the version that was updated on July 10, 2013, since I can't seem to get a real number on the version of this miserable app).
4. Join the call that your friend(s) are in. You will start to hear them over your phone's loudspeaker.
5. Turn your Bluetooth headset on, wait for it to connect. When it connects, Skype should automatically recognize it, and start using both the mic and the earphones on the headset, and you should be able to talk normally.
Here are some things that will annoy you, though:
When you get a regular phone call, the Skype call will be put on hold. When you end the phone call and try to rejoin the Skype call, Skype will still see the headset as connected, but will continue to use the phone's speaker and microphone.
This is going to happen a lot, and here's how to fix that:
1. Leave the call, and sign out.
2. Close the app from the little task manager thingy (If it's a Galaxy SII, just hold the home button and swipe it away).
3. Disconnect the Bluetooth headset. You can turn your bluetooth on your phone on and off again real quick if you think that helps--I have yet to determine if it does.
4. Sign back into Skype, and join the call.
5. Turn your headset back on again, and Skype should connect to the headset.
For some bizarre reason, I have not been able to connect my headset to my phone, and sign into Skype with the expectation that anything will work, at all. I wish it weren't so complicated, but it is.
Oh, and FYI, don't bother with Skype premium. Group video doesn't work on Android phones OR Windows phones (even from Windows desktop to Windows phone, my friend and I tested; way to sell broken services, Microsoft!), so if you're on-the-go a lot, it's a total waste of money. Also, if you're bike riding, you're probably just going to piss off your friends in the Skype call with all the ambient noise. The mute feature on my headset is not recognized by Skype, so I have to dig my phone out of my pocket to mute it from the screen.
I hope this helps, but more than that, I hope that one day, Microsoft will restore my faith in Skype. But considering it took them this long to revise their app to the point where Bluetooth even pretends to work, I'm not crossing my fingers.
Related
Hello all,
I have been using android on my hd2 for some time. There is 1 thing that I am unable to do which is frustrating.
Under winmo, I could listen to audio books via the Bluetooth headset, is this not possible on android?
Any help gratefully received.
Sent from my HTC Desire using XDA App
It is quite difficult to do it in Android at the moment. There are a few builds where this is possible, like forum.xda-developers.com/showthread.php?t=740963 (shubcraft) and forum.xda-developers.com/showthread.php?t=736545. However, these builds are not 'perfect' IMHO.
There are builds where you can listen to audio via bluetooth but if you get a call, it may reboot, like forum.xda-developers.com/showthread.php?t=769026.
There is no build I have found yet, that has Hotmail ActiveSync support, complete Bluetooth audio (to sync with Ford a2dp), no SOD and good battery life!
I can listen thru my Sony Ericsson HBH-DS headset just fine on following builds and phone calls also :
HyperDroid
Bangster's
mdeejay
...rest I do not run regularly but I suspect will work fine
Is the media-routing Problem similar to my Problem ?
I dont know if this issue is known, so i post it here in hope, that it will be fixed =)
I have in all Android apps wich had something to do with the sound-input/output problems. I had no sound there.
I tested FritzApp! ( a App wich allows you to use your Androidphone as an normal DECT/IP Phone with the Fritzbox!)
Either my communicationpartner hears my voice nor I hear him. Dialing works perfectly just the sound doesnt
And with MicDroid ( Something like LaDiDa for Iphone). ( Records just "Rauschen")
Can you confirm this kind of issue or am I the only Person, plz post your problems.
Or is this problem known ?
kind regards
malla
Click to expand...
Click to collapse
I would say that it is similar because even my BT system (on some builds) recognizes the phone, connects, plays music, dials calls, but there is no audio (in/out) once the call is connected. This is confusing because there is no issue in connecting as an audio device, the problem is in the phone device.
ranaonline said:
It is quite difficult to do it in Android at the moment. There are a few builds where this is possible, like forum.xda-developers.com/showthread.php?t=740963 (shubcraft) and forum.xda-developers.com/showthread.php?t=736545. However, these builds are not 'perfect' IMHO.
There are builds where you can listen to audio via bluetooth but if you get a call, it may reboot, like forum.xda-developers.com/showthread.php?t=769026.
There is no build I have found yet, that has Hotmail ActiveSync support, complete Bluetooth audio (to sync with Ford a2dp), no SOD and good battery life!
Click to expand...
Click to collapse
Try the new beta from Darkstone desire hd,works for me!
Including calling with bluetooth,without any tricks or errors!
I'm hoping someone here has some *real* ideas or answers regarding this issue.
I have a handsfree Bluetooth kit in my car so that I can safely place calls while driving. This worked flawlessly with my previous Windows Mobile phones (Tilt/Tilt II). With the phone tucked in my pocket and the mobile OS “locked” I could press the voice activation button on the dashboard and easily call someone. Not so with my shiny new AT&T Samsung Galaxy S II. Now I have to dig the phone out and unlock the device before I can use my handsfree system… are we back in the smartphone dark ages?? I might as well take up texting and driving while I’m at it and forget the handsfree unit altogether.
Apparently Google in their infinite wisdom has decided already paired Bluetooth devices pose a security risk. As such, when Android is “locked” it disables any control from Bluetooth. I suppose if you work for the government or some place that you need Pentagon like security this makes sense. For the 95% of us that don’t need these draconian measures this is just plain stupid and potentially unsafe.
I've already rooted my phone. I've tried other ROMs like the latest builds of UnNamed, ICS'd Out, and CyanogenMod. None of these allow Bluetooth operation while the phone is locked (and in fact all of them introduced other issues). I've searched the forums but most similar posts go unanswered or contain nonconstructive replies (flames, unrealistic answers, etc).
I can't and won't disable ALL security. I won't give up making phone calls while driving - I'm on the road a decent amount and need to use that time productively. What are my other choices? Go buy an iPhone or a Windows Mobile unit which work "right"?? Seems like a crazy oversight by Google/Samsung/AT&T if those are my only options!
I would suggest using the official samsung Car dock, as the USB port on there has a special impedance that tells the phone to go into driving mode, which once you unlock the phone, it stays unlocked until you either lock it, or take it off the dock. It also charges your phone at the same time. However if you have a case, this will not work for you. You would need to solder up your own usb plug that has a certain impedance over some pins (theres a thread somewhere about that, its like a jig, but with different impedance) and just plug that in when you're driving, but you still have to unlock the phone at least once with it plugged in.
My clarion cz500 car stereo has no issues making or receiving calls via Bluetooth while my phone is locked.
Sent from my GT-I9100 using xda premium
My biggest gripe with Android is that BT calling does not work as well as it did with WinMo's Voice Command (which works really well considering how poorly much of WinMo worked). Initiating calls via BT is my main gripe with Android. I wish Google would get it right already. That said, I have no problems answering calls via BT even when the phone is locked.
My phone is paired with the built-in BT in my car and I have no issue with making/taking calls while the phone is locked. Maybe its a compatibility issue with your particular hands-free device?
I also have no BT problem when locked, using the standard BT in my Toyota Avalon, 2011. Running rooted, UnNamed ROM, Entropy's DD 120811 kernel.
For those of you who think BT calling works just fine, I have to ask, have you ever used a WinMo phone with Voice Command? If not, then you don't know how well it's supposed to work. With VC, I could touch the call button on my BT headset or BT car stereo at ANY time, get a little chime and then say the name of the person I wanted to call and have it dial automatically. I never had to touch the phone to do this. When I try this on my Cappy or SGSII I get nothing. I have to initiate the call on the phone and using voice recognition on Android is spotty, at best, and requires more steps. At least answering a call is relatively easy. I have no love for MS, but they got this part right on their phones.
Miami_Son said:
For those of you who think BT calling works just fine, I have to ask, have you ever used a WinMo phone with Voice Command? If not, then you don't know how well it's supposed to work. With VC, I could touch the call button on my BT headset or BT car stereo at ANY time, get a little chime and then say the name of the person I wanted to call and have it dial automatically. I never had to touch the phone to do this. When I try this on my Cappy or SGSII I get nothing. I have to initiate the call on the phone and using voice recognition on Android is spotty, at best, and requires more steps. At least answering a call is relatively easy. I have no love for MS, but they got this part right on their phones.
Click to expand...
Click to collapse
Sgs2 does this stock with no problems via samsung/vlingo voice command app. Seems hit or miss on some custom roms. As long as device has bt turned on and had been prior paired with a headset, just have to turn headset on then hit the button on the headset. Voice prompts over headset ensue
Sent from my SGH-I777 using XDA App
I'm headed into the AT&T store tomorrow to do some definitive tests but so far I'm skeptical people who say it's working for them truly have their phone locked. The Bluetooth unit in question is a Parrot CK3100 LCD - a bit dated (3 years old) but it works flawlessly with several WinMo phones, several non smartphones (mostly Nokia's), and we just tried a friend's iPhone 3GS and iPhone 4. In all cases phonebook and voice dialing not only worked excellently it worked when the phones were truly locked and the screen off.
On the other hand the 3 Android devices I've tried all have the same problem - they won't dial out either by phone book entry or voice recognition unless you unlock the device first. The 3 devices are: Samsung Galaxy S II (AT&T), Samsung Galaxy S (Verizon), and EVO 3D (T-Mobile).
Unfortunately I don't have any other Bluetooth headsets to try out, hence my planned trip to AT&T. I plan on walking out of their either with a Bluetooth device that works or an iPhone Thanks for the replies.
I hear you. I have a Motorola FINITI bluetooth headset and it will not voice dial with the screen locked on my AT&T Galaxy SII.
Is there not an option to keep it from locking? :/
Sent from my Galaxy Nexus using xda premium
mohitrocks said:
Is there not an option to keep it from locking? :/
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Some roms give you a quick toggle in your status bar called secure mode, this should do it.
I'm on villain rom with jaykay mod quick toggles and i have that options.
Sent from my GT-I9100 using xda premium
My stock phone is paired with the built-in BT in my car. I also have I have no problems with making or receiving calls while the phone is locked.
I can also make calls using voice dial when the phone is locked using my plantronics BT headset.
GeorgeP said:
My stock phone is paired with the built-in BT in my car. I also have I have no problems with making or receiving calls while the phone is locked.
I can also make calls using voice dial when the phone is locked using my plantronics BT headset.
Click to expand...
Click to collapse
Are you using a pattern/pin lock? Or just the slide to unlock.
Just slide to unlock.
It works very well and very straightforward. I just press and hold the call button on my headset (while the phone is locked), and then after the tone say, "call John Doe on mobile" and it works.
Something for OP to consider in troubleshooting why he is unable get this work:
The BT voice dial works through the older pre-installed Vlingo (version 2.x). Even though I have the newer version (3) of Vlingo installed, the phone still launches the older preinstalled version of Vlingo for BT voice dial. So it seems the BT voice dial function is in some way hardcoded to that version of Vlingo.
Perhaps OP is using a custom ROM in which the older pre-installed Vlingo is removed(?). I know that is the case with some of the custom ROMs for the Int'l SGS2.
If I were to freeze or remove the older version of Vlingo, that might impact BT voice dial. Although I wouldn't expect it to affect the use of my phone through my car's build in BT.
Try it with a pattern lock or some kind, I believe that is what the OP has and its what "locks" the phone from using BT dialing, whether its voice based, or address book based from a headunit.
OK, if OP means that type of lock, then, no you cannot make a call when locked.
Although, it is not clear to me why one would want BT to bypass the lock in this manner. It seems the PIN or pattern lock would be pointless. If the phone is stolen (or lost) the person who stole it (or found it) could have access to your phone's contents through bluetooth. Am I missing something?
Definitely missing something. He wants the phone to be able to make calls while the phone is locked which is why i suggested to keep it unlocked by enabling driving mode through the mount.
My point was that allowing bypassing the lock through BT creates a exposure many would not want. The simplest solution might be keeping it unlocked either using a mount as you suggest, or using one of the profile apps that lets you create a profile to keep the phone unlocked when plugged in. He could then plug it into the car power adapter.
I use a pattern lock, and can make calls through the built-in BT in my car when the phone is locked. I can dial on the car's touch screen (disabled when the car is in motion, except for pre-set speed dials), or tell it to call someone by pressing a button on the steering wheel and saying the name. The car BT compares the spoken name with the list of contacts from my phone that have been BT-loaded into the car's contact list. Nevertheless,the call is made though the phone, since the vehicle BT is not itself a phone. Has anyone noticed that we have not heard again from Rajah, the originator of this thread? Rajah, are you there? Were your issues resolved?
Hi, noticed with ALL AOSP / AOKP ROM's 4.2 and above that Bluetooth has an issue, bothering everyday use and still not fixed. Once you use BT car hands free and you want to to take the call back on the handset (internal or external speaker does not make any difference) the sound never comes back to the phone. Tried at least 3 different CM10 and above based ROM's, all has this problem. Anyone can get it fixed? For everyday use this is a real issue, cannot be that you cannot leave your car until you finished the call /or need to close the call and call again with BT off. Not realistic during a daily use. Thanks for any comments
i am having the same problem.
also when calling can't turn off my car. then it quit my call
Verstuurd van mijn GT-I9300 met Tapatalk
My bluetooth also stopped working after upgrading to 4.2
schaduw1984 said:
i am having the same problem.
also when calling can't turn off my car. then it quit my call
Click to expand...
Click to collapse
I was very happy with LiquidSmooth 2.8, so I decided to upgrade to 2.9.
Everything works very well, except for bluetooth.
Symptoms:
- A2DP streaming to my car stereo (JVC x250BT) works
- Bluetooth calls with car stereo result in either no or horrible sound
- Bluetooth calls with my (Parrot ck3100) carkit work sometimes on the first call after a reboot (usually fails)
- Bluetooth calls with a JabraBT215 headset also fail
- All the above has been tested with the device being the only registered (and therefore connected) device.
-- sometimes, I can hear the sound rapidly switching between the handset and the bluetooth device.
Occasionally, I also got no incoming sound during calls with no Bluetooth device connected.
Sometimes, connecting a wired headset would help.
I tried to highlight the point few months ago already on a development forum but I am too junior to be listen to... Even i strongly believe this is a real bug gating real everyday usage if you sometime want to use your phone as a phone..
Sent from my GT-I9300 using Tapatalk 2
Hey All,
So, I've been searching all over for an answer to this, I've found a lot of information about S-Voice's problems being used over a bluetooth device but I haven't been able to find any direct discussion of the issue I'm experiencing.
What I've found is that when I have S-Voice's voice wake-up feature enabled, it'll work totally fine with bluetooth off. However, as soon as I toggle bluetooth on the wake-up feature just completely stops working. I don't even need to be connected to a device, as long as bluetooth is on S-Voice Wake-Up does not work. I can manually launch S-Voice and it will hear me just fine, but saying the wake-up command does nothing. As soon as I toggle bluetooth back off, it'll wake up again just fine. I do get that with a bluetooth device connected the microphone on the device needs to be active, so I could understand if this was happening while I was paired with a headset or something, but it seems really odd to me that just having bluetooth on at all would disable the wake-up command feature.
I did try Ok Google and found that it works whether bluetooth is on or off, but I really like the increased functionality that S-Voice offers and I think that for the most part the updates Samsung has done on it are great, so I'd like to get this working if possible.
Has anyone else experienced this, either on the Note 4 or on any of the other Galaxy devices? Anyone have any ideas or solutions?
Thanks!
I'm having the same issue with svoice, thought it was just the bluetooth in the car at first til I red your post
Widespread
I've got exactly the same problem.... Lovely new note 4 which is forcing me to use my hands on the phone whilst driving... Samsung need to think about this.
Apparently an issue for a few years due to Bluetooth /svoice conflicts, but not acceptable to leave it unaddressed.
I can still use my car system to skip music tracks on the phone, or dial numbers from the car stereo touch screen, but surely this is one of the most valuable areas for voice control?!
Bluetooth off then everything works fine, but Bluetooth on and svoice just fails. No wake up or voice recognition.
I don't use a headset, and the car doesn't have an inbuilt mic, so phone mic is used for calls (which is still fine incidentally.. Only svoice which is screwed.)
Looking forward to someone finding a simple solution to this, as I have spent hours in the menus trying to make a difference but Samsung might have just let us down I'm afraid... And if that's the case then I look forward to hearing them fix it, and update our ware to get everyone on track again.
Resolved and simple
After much fckin about I managed to get this sorted and the answer is simple..... You can't have both apps always trying to recognise the voice all the time.
Go to the settings for ok Google and voice detection then always on... Uncheck it and suddenly svoice is working again... On my way to the car for final checking now,but preliminary checking says all should be good.
Nope
Ok... It works until the system is fully connected.
As soon as the connection is made then the handset microphone switches off again.
Note 4 s voice is officially dangerous to Road users and Samsung are ultimately proving themselves irresponsible for creating a system which forces use of hand and eye coordination when in Bluetooth and car mode.... Seriously Samsung... Sort this sht out.
When driving, set to hands free mode, this allows use of svoice on bluetooth
Ooof said:
Ok... It works until the system is fully connected.
As soon as the connection is made then the handset microphone switches off again.
Note 4 s voice is officially dangerous to Road users and Samsung are ultimately proving themselves irresponsible for creating a system which forces use of hand and eye coordination when in Bluetooth and car mode.... Seriously Samsung... Sort this sht out.
Click to expand...
Click to collapse
Note 4 and above have it listed as car mode.
svoice works perfectly with blue tooth when car mode is enabled.
Set it up at home before you use it the first time.
Hello,
I didn't find other references about this one.
I noticed a really poor and crappy performance when Bluetooth is connected to my audio car system.
I experience subsequent and short connection drops/re-connections, also during phone calls.
In addition:
- audio volume is very low, also when all pumped up.
- I don't get recent inbound and outbound calls and contacts lists sharing.
It's a pity. Other devices work flawlessly, even some old (non smartphone) GSM devices.
Is anyone experiencing something similar?
Thanks for any info.
xda_dentex said:
Hello,
I didn't find other references about this one.
I noticed a really poor and crappy performance when Bluetooth is connected to my audio car system.
I experience subsequent and short connection drops/re-connections, also during phone calls.
In addition:
- audio volume is very low, also when all pumped up.
- I don't get recent inbound and outbound calls and contacts lists sharing.
It's a pity. Other devices work flawlessly, even some old (non smartphone) GSM devices.
Is anyone experiencing something similar?
Thanks for any info.
Click to expand...
Click to collapse
That's strange, I have BT constantly on as I have the phone paired with a Sony Smartwatch 3, plus I exclusively use my Jabra BT headset during my long commute for music, videos and calls and never had a single problem with the volume level, connection and sound quality.
I had the same problems you have with a damn expensive HTC M9.....
Yeah, that's strange, I suspect the audio system it's just choosy... It's likely that the phone will work OK if I try some other BT device.
I'll do it when possible.
This was just to check if someone else had the same issue.
Thanks!
Yes, I did notice the relatively low volume when I connected the phone to my Vw stereo in my car.
1. Low volume for both music and voice calls compared to my previous phone (ip5c)
2. Also the phone has a problem with avrcp profile, so it cannot display the song name/metadata on the stereo screen !
Connects to car ok but doesnt load the contacts.
ive just discovered this problem also it connects to my sony car system fine but will not load the contacts unlike my sony z1 compact.
sam0056 said:
ive just discovered this problem also it connects to my sony car system fine but will not load the contacts unlike my sony z1 compact.
Click to expand...
Click to collapse
Someone got this to work over on the OPO forum but never worked for me ,give it a try.
https://forums.oneplus.net/threads/...-for-new-updates.403586/page-30#post-14056981
Seriously Operational Problems OPX
OPX BLUETOOTH. There is recognition problem many devices and components.
OPX DUAL SIM, DUAL STAND BY 4G? Not applicable. When you run out of card data is committed as required by the company, another card is not using the data only telephone contact
[email protected] said:
OPX BLUETOOTH. There is recognition problem many devices and components.
OPX DUAL SIM, DUAL STAND BY 4G? Not applicable. When you run out of card data is committed as required by the company, another card is not using the data only telephone contact
Click to expand...
Click to collapse
1. learn english
2. don't cross post things that have nothing to do with the thread
Thanks
xda_dentex said:
- I don't get recent inbound and outbound calls and contacts lists sharing.
Click to expand...
Click to collapse
I have the same problem in my car (Kia Ceed GT). Nothing helps. I'm waiting for some custom ROMs, I don't believe that Oxygen will ever fix all bugs.
Tapatalk @ OnePlus X
This app seems to fix all issues:
https://play.google.com/store/apps/details?id=com.android_rsap.irmctest
It's the trial.
There's the paid version too.
Disclaimer: it's not mine, I had the link from a twitter user
I have the same problems in my Skoda Octavia 2015 (no ID3 tags, not possible to change track by the steering wheel buttons, sometimes stuttering, quite poor audio quality when calling). The Honor 7 works perfect with the Skoda, the iPhone from my girlfriend as well.
But I connected the OPX to a Renault and there it worked faultless.
So I don't know where's the problem... maybe the OPX doesn't support all AVRCP versions?
In my Kia AVRCP works with PowerAmp and Deezer. But I still have the same problem with contacts and calls list.
Tapatalk @ OnePlus X
xda_dentex said:
This app seems to fix all issues:
https://play.google.com/store/apps/details?id=com.android_rsap.irmctest
It's the trial.
There's the paid version too.
Disclaimer: it's not mine, I had the link from a twitter user
Click to expand...
Click to collapse
That app worked for me but its only trial,hopefully OP release an update to fix the BT.
It seems their are taking care of this:
https://twitter.com/OnePlus_Support/status/668932234989162496
xda_dentex said:
It seems their are taking care of this:
https://twitter.com/OnePlus_Support/status/668932234989162496
Click to expand...
Click to collapse
I wouldnt hold your breath they have the same problem with the OP2 and thats been out months.
https://forums.oneplus.net/search/7767779/?q=bluetooth+contacts&o=relevance&c[node]=148
I've the same problem of dropping calls when connect with my car (Opel Ampera).
Did pair the Plus X several times but problem not solved.
Hello guys,
any problem with bluetooth headphones? I wanted to buy one (for running). May I expect the same glitches as with the car connection?
Thanks.
CyanogenMod 12.1
vonski said:
I have the same problem in my car (Kia Ceed GT). Nothing helps. I'm waiting for some custom ROMs, I don't believe that Oxygen will ever fix all bugs.
Tapatalk @ OnePlus X
Click to expand...
Click to collapse
I installed Cyanogen rom 12.1 beta and they have fixed the bluetooth problem. i also had that problem but just installing the rom cleared it all up
I'm waiting for more stable version of CM.
For now I've installed Bluetooth Phonebook app from store and it solved problem.
Tapatalk @ OnePlus X