I have tried to use a bluetooth application we wrote to transfer data (SPP) and it pairs and connects and starts to send data but it stops after around a minute. I know there are various items about bluetooth paring etc so I guess this is due to a known bug in the hardware/kernel drivers etc. Can someone let me know if this is the case.
Related
Is it possible to put the old android 1.6 bluetooth control into a nexus ROM?
My G1 worked great with my car's built in bluetooth system, but my N1 wants to be a PITA. It refuses to stay connected, it is constantly disconnecting and reconnecting, disconnects after about 30 seconds and reconnects a couple minutes later and then repeats this cycle. (I know this because my car tells me audibly every time this happens) It also will not transfer audio to the system, or the system voice controls will not answer or start calls even when the phone and system show connected (the brief times that it does show connected). That fact makes me wonder if the bluetooth audio problems others complain about is the same issue I am having, and that their phones are not connecting properly as well. I think the issue may be caused by how the N1 treats phonebook access. With the G1 I would get a "connection complete" message when the bluetooth connects and a "transfer complete" message when the phonebook access completes. I never receive the transfer complete message for the N1
The real crazy thing is that I can get it to work if:
I do not have the phones bluetooth turned on
I then get into the car and start the car (its bluetooth then turns on)
I then turn on the phones bluetooth (if the phone does not connect to the system immediately I click connect manually)
I then must make a phone call within just a few seconds after the phone connects
After that everything works as expected. I have found no other combination of turning on or off bluetooth on the phone or car system that also works.
I was having problems with my car audio as well, until I updated to Cyanogen's latest. Everything seems to be working quite well now. What ROM are you using???
Stock ATM. The N1 is good enough stock (as opposed to the G1) but for the lack of free tethering. I'm sure it can be even better though. Staying connected to my cars system seems to be my biggest issue, audio works great when I get it to connect properly.
if got the same issue on my parrot.
but the problem still persists on the latest cyanogen mod
Yeah, I don't know what it is that is different in 2.1, but 1.6 works great with bluetooth.
I don't guess its possable to do, I hope an official fix comes soon.
Okay, this issue is driving me a bit nuts. This phone seems to have a tendency to self delete bluetooth pairings randomly, such that I'll suddenly find I have to pair again a bluetooth device that I had working before. I know it's not the bluetooth device because this has happened on all sorts of things.... Get in car, no bluetooth connection, see pairing request on phone. Pebble watch suddenly won't connect anymore, look in bluetooth pairings list, no longer there. Worst is the Moto 360, because for some reason, Google decided that you cannot initiate a bluetooth pairing on Android Wear except by factory resetting the watch. So every few days, or weeks, depending on luck, I'd find myself having to factory reset my watch yet again, just to pair it back with my phone.
Just me? Anybody else with random bluetooth pairings deleted? I'm on the current 5.1 firmware.
So all my other phones work fine with the Parrot MKi9200. Except the ROG.
I'm going to try describing my experience as best I can. Wanting to see if anyone is having the same issues (with other asus phones even) and has found a solution.
First time I tried connecting, the bluetooth code popped up, I entered the default code and attempted pairing but the Parrot has too many paired devices so it was rejecting the ROG
so i cancelled the pairing and went into the Parrot to delete old devices
Tried pairing again but this time, it no longer asks for the code
The pairing appears to be successful on the Parrot, the phone says it's connected but when I try playing anything, there is no sound at all
I've tried forgetting the connection on the phone and then pairing again. and strangely enough, it no longer asks for the code, which is abnormal
The Parrot has no record of the ROG as a paired device so there is nothing I can do from that end
On the phone I then tried clearing bluetooth cache
setting org.coreaudio something bluetooth to not be optimised for battery
tried pairing a random headphone with the phone and it works just fine
Hi all,
first post, this issue starts to drive me mad :crying:
My device is a Lenovo C2 (K10a40), not rooted (If BTW anyone knows how to root this device: You're welcome )
I have Bluetooth connections to many devices. My car and my wife's car (Phone Audio and Media Audio) , Raspberry pi (Media Audio, to stream from device to rasppi), a Philips TV with a "built in" Bluetooth speaker, to stream from device to TV, and my Linux PC (Phone Audio and Media Audio), to dial etc. from my pc when sitting at my desk.
ALL of these connections are working fine, except one, to one car:
- When paired for the first time, all worked fine for a long while, days/weeks/months
- No idea why, once and suddenly when re-connecting the device and the car, after some seconds, AOSP standard media app "Music" starts, and again after some seconds, a popup says "Bluetooth Share has been terminated" (or very similar, translated from German msg).
- Car says on radio screen "A2DP has been terminated"
- Both car and device tries infinite to reconnect, same issue
Tried the usual stuff:
- Clearing cache: no change
- Resetting network (and Bluetooth) settings: no change (after painfully adding all WLAN and Bluetooth connections again :crying
- Rebooting both car's radio and android device. no change
I didn't try and really, really, really don't want to try a factory reset, would take me ages to reinstall and reconfigure everything, as I'm not sure if simply restoring a backup after resetting the device will re-introduce the error anyway. I don't want to test it :silly:
What sometimes, whyever only sometimes helps (for a short while, sometimes days) is to drop phone from car's paired devices and vice versa, and re-pair after that.
My question is, could be a deep technical answer if necessary: What on earth triggers the start of the "Music" app, after (re-)connecting both device and car? The Bluetooth crash *** ONLY *** happens, if "Music" app starts. Before first crash "Music" app has NEVER been started. Now, when successfully paired after dropping connections as described, "Music" app does also not start at first. But as soon as "Music" app was used to stream media to car, it's going to start automatically after reconnect. Although if for instance media playback has been terminated before disconnecting, e.g. for listening to radio. For a while then reconnect with automatic start of "Music" app works, and after a while the crashes appear again.
On the other hand, if "Music" app is started automatically after a re-pairing, after dropping connections before, at the first Bluetooth connect, the crash is ALWAYS a result.
I also found out, that if I'm DISABLE A2DP "Media Audio" profile in the connection settings of the android device, connection is stable and "Phone Audio", including adressbooks sychning etc. works fine and stable. But unfortunately not "enough", I need A2DP for navigation audio.
Any hints how to get rid of these "Music" autostarts would be great!
I made a bixby routine as follows: when my phone connects to my car bluetooth (VW Passat), it should do several things. But the problem is that the routine almost never starts working by itself? It only works after I manually turn off bluetooth and turn it back on after im already connected to my car. Anyone else have this problem? With tasker there's no such problem when connecting to my car bluetooth, but i'd like to use bixby routines instead of tasker...
Even though I have another routine which does several things after connecting to my BudsLive, and that one always works by itself without problems.
When you get in the car do you activate "media" on car, or just get in and let the phone connect to car? I have noticed on a lot of devices if you don't "fully" connect to media on car, such as playing streaming music many phones don't see the connection unless Media connected (you can pause music). I'll get phone calls fine, but no messages or Maps audio at all unless Media connected. As I said, same with all my older phones, started I think around Android 9. Think part is car manufacturers don't want to support phone options anymore, they want you to use Android Auto or Car Play and leave the software to Google and Apple.
mt2020 said:
When you get in the car do you activate "media" on car, or just get in and let the phone connect to car? I have noticed on a lot of devices if you don't "fully" connect to media on car, such as playing streaming music many phones don't see the connection unless Media connected (you can pause music). I'll get phone calls fine, but no messages or Maps audio at all unless Media connected. As I said, same with all my older phones, started I think around Android 9. Think part is car manufacturers don't want to support phone options anymore, they want you to use Android Auto or Car Play and leave the software to Google and Apple.
Click to expand...
Click to collapse
The thing is, my car bluetooth doesnt want to activate "media" lol. It only connects for phone calls. When i try to activate media the button always returns back to off. Seems to be a samsung/volkswagen problem since i see alot of posts with the same problem when googling
I had Bixby Routines set up on my S21 to do some things automatically when connected with a car Bluetooth kit. Everything was working fine until the last update of One UI 4.0. After the update, nothing happens when I connect to the Bluetooth kit in the car. I deleted the Bixby routine, reset the app data, deleted the Bluetooth partnership, and reconnected to the car's Bluetooth kit - nothing helped.
When I create Bixby routines using regular Bluetooth headphones, everything works fine. The problem only occurs with the car's Bluetooth kit. While searching the Internet, I found out that there was a similar problem with Bixby procedures before. Back then, Bixby routines would not work if the bluetooth device did not have an audio profile. My BT car kit does not have such a profile, only a hands-free profile is available. Has the old malfunction returned?