Hey guys, just got a Moto 360 yesterday, and i been having issues with bluetooth. I have an S4 with the AICP rom, which is based off cyanogenmod. I also have Xposed. The issue im having is I cant do anything from my watch to my phone. like ill hit open on phone, nothing. try to send a text nothing. it says im connected but the bluetooth icon isn't highlighted, its greyed out in the status bar. headphones would highlight it, but not the watch. I receive some notifications, but not all and theyre delayed. also bluetooth will knock off my wifi unless i use bluetooth tethering. thanks for any help.
Related
Dear all,
My HTC Desire is now 15 months old, and still works as new. No, better than new since it's rooted and faster.
Coming to the problems:
My car has a bluetooth feature to stream music from the phone, and to take and make calls. Bluetooth music streaming works perfectly, and I can skip songs using the car controls.
I am facing the following issues with the "Phone Connect" feature when I pair the Desire:
After any and every incoming or outgoing call is completed, I get a pop up on the screen which says "Fatal Exception..." and I can only force close from here. When I force close, the signal strength icon shows a cross and all connectivity is lost for sometime, including BT: car says "phone disconnected". After a while the signal strength comes back and BT can be reconnected.
So basically I have to repeat this process everytime I make or answer a call via the car BT feature. Needless to say, it's a PITA.
I am guessing this is a problem to do with the radio or kernel of the phone. Not sure which. Please confirm this, and guide me to a radio or kernel file which may solve this issue.
My second problem has to do with the phonebook feature of the car. It can pull the contacts, the recently dialled numbers, recently received numbers, and missed calls. Only in the Desire it doesn't.
The phonebook feature can only see the contacts in the SIM card.
The recently dialled, received, and missed calls don't work. Numbers only show up on the car list if I have made/answered/missed a call while connected to the car BT.
The only feature that works as it should is redial.
As I am told, all Nokia models work perfectly on the same car model, and since we own a 'smart'phone, not to mention an Android, we should be able to get it to work however we want it to.
Any fixes for this one?
Thanks in advance.
PS. If you want the exact error message thrown by the phone after taking/making a call, I can write it down and get back to you afterwards.
BUMP!
Please help, guys!
I just picked up a my new Note II yesterday, have done nothing to it except install the latest update. This thing is STOCK. My issue is with the Bluetooth connection in my car. I have a 2009 BMW with IDrive which has the Bluetooth integration built in to it. My HD-2, Sensation, GNexus, original Note all connect very nicely to the Bluetooth but my Note II is struggling. I paired it yesterday on the way home from the AT&T store and it worked fine. When prompted to allow the phone book during my initial pairing I checked the box "Don't ask me again" and clicked "Yes", same thing I've done on all my other phones. This morning however it would continue to drop out. It would connect for 15-20 seconds and I would see the little icon that tells me the phone is transferring the contacts then it would simply drop out. 15 -20 seconds later it would recycle and do the same thing again. When I was looking at the contact list on my car's screen it was showing AT&T address book which I do not use (it was just one contact, "something" AT&T) and in fact froze everything AT&T I could through the settings menu . I then deleted the phone from the car's menu and repaired it to the IDrive but this time I said no to allow the phone book. It was not dropping the connection but was constantly trying to obtain the contact data based on the icon on my car's screen. Then all of sudden I received an alert stating an "SOS Call System Failure", my car has a built in SOS function like Onstar....I deleted the phone again and the warning in my IDrive regarding the SOS failure went away.
I searched the BMW forums and found other people with this problem but these were from the '07-'08 time frames and that fix was software to the car. The software in my car is updated and so is the B/T profiles I also found a thread here regarding a similar issue but there was no resolution. Has anyone else had this experience with the Note II? I know enough to get myself in trouble but not enough to figure this out. Is it possible the Bluetooth in the phone only wants to transmit the AT&T address book vs. the Google contacts?? I guess it could be the software in the car but my other Note, whether running stock or CM 9/10 ran flawlessly with regards to the Bluetooth.
Weird, yesterday it's fine and today not so much. Did the last software update have anything in it that affected the B/T?
Any insight would be much appreciated, thanks.
UPDATE-appears my car cannot handle a Bluetooth profile of 4.0. All my previous phones were no higher than 3.0. Hoping BMW will offer a software update at some point but in the mean time if I go with a custom ROM will they probably keep the Bluetooth profile the same as stock or is that something they change??
Hoping someone can help shed some light. Googling didn't turn up anything. My S6 after the 5.1.1 update, bluetooth is borked. It is connected to my Sony Smartwatch 3, Gear 2 Neo, and was connected to my Fibit Charge HR and Microsoft band. The Fitbit Charge HR got a firmware update and then would not pair with my S6, but would pair with my work iPhone. So I thought it was defective. But it pairs with my old S5. So I went into bluetooth settings and did a scan and it will not see it. So, I stupidly unpaired my microsoft band and now it's now recognized at all. The SW3, G2 Neo are paired, as well as my Sync in my car, but show up in bluetooth as "Not Connected" even though they are. This is frustrating and I don't want to go back to my S5. Everything else seems to work okay - just the bluetooth. Anybody have any thoughts? I'm on the latest OTA, OFE.
SO no one's got any ideas. I have wiped cache both while normally running and by booting into recovery. Bluetooth still hosed. Would a factory reset help?
Saafir said:
@kbboykin Does your devics keep a bluetooth pairing history? If so delete it and try again. Have to do that with a lot of my devics
Click to expand...
Click to collapse
I don't think it does. See screenshot. All of these devices are paired and connected, but bluetooth says they are "Not Connected".
I just got my ZenWatch 3. I have installed the Android wear app and ZenWatch manager apps on my phone. I got the watch connected to my phone and synced. Everything is working except speech to text. If I say okay Google and tell it send a text, it will allow me to use my voice to speak the content and it will send the text with that content in it. If I tap in the mic icon on the keyboard it will say speak now and I speak and then it just spins and finally says timeout then retries several times. The other issue is connectivity. I should be able to stay connected using either Bluetooth or wifi. I can get on wifi at the house and turn off the Bluetooth and I have no connectivity at all. Any ideas or solutions or, in the case of my ignorance, explanations?
I suggest you post this in https://forum.xda-developers.com/zenwatch-3
Since this "subforum" is only for the Original asus zenwatch
Each time I use Mi6 via bluetooth in car to answer/make calls - first call goes OK, and all others not - people I talk to don't hear me. It happena in 4 different cars so it's not car's problem. Mi5 was OK. I run 7.1.1 NMF26X global beta. miui 8 7.6.8 global beta. And can't solve it myself. Tried deleting and re-adding cars, restarted phone - nothing helped. When I switch to phone during call - it's OK. As soon as I switch back to car - same problem. No one hears me and I hear everyone.
Any1?
I'm sorry but I can't test because I don't have any Bluetooth devices.
Not using any bluetooth device either.
Hello there
I'm a new xiaomi mi6 user. I have 7.5.25 version rom installed on my phone. My phone does not see andriod wear app on my smart clock with bluetooth. Also does not share internet with hotspot. There is also a problem with the GPS, the satellites can not find it immediately. can you help me.
Thank you
ERSL said:
Hello there
I'm a new xiaomi mi6 user. I have 7.5.25 version rom installed on my phone. My phone does not see andriod wear app on my smart clock with bluetooth. Also does not share internet with hotspot. There is also a problem with the GPS, the satellites can not find it immediately. can you help me.
Thank you
Click to expand...
Click to collapse
Ok, one by one.
1. My phone does not see andriod wear app on my smart clock with bluetooth --> My watch works, did you unpair your watch with old phone first? Android wear watch can only connect to 1 phone.
2. There's personal hotspot, you can see it in the settings menu.
3. GPS needs time to find your phone, you need to have wifi (or mobile data connection to assist the phone), if it located your phone, next time GPS will work faster.
It is a different issue with me: when paired with a BT device with the "phone audio" profile enabled, despite picking up the call on via pressing the green button on the touchscreen, it still defaults to the BT device (and I have to switch audio back to "phone" before the other person cuts off after hearing nothing). This is on the global ROM 8.2.2.0...
The global ROM seems buggy as hell...
alien2k1 said:
Any1?
Click to expand...
Click to collapse
Hello Friend.
The same happens to me.
It connects to bluetooth but I have no output or audio input.
Did you get it fixed?
Thank you
Everyone.
This is not xiaomi's problem.
This problem is due to oreo's new bluetooth stack.
There is no current solution to this. I've searched far, wide and deep.
Android has a great track record in keeping the bluetooth stack broken.
If you try to search google, you will find out that not only xiaomi phones have this problem.
The only theoretical solution is to port old bluetooth blobs, and somehow make it work. But as far as i know, no one has done this before.
There is hope that android pie will fix this. But from what i read, early builds of pie still has this problem.