Hi
I have installed CM13.0 - 20160114 with a clean install.
My problem is, that I tried to use BT with the speakerphone in my car. It connects, but when I want to make a call it doesn't work. Recieving call works with a short delay.
Next problem is, that my heart rate belt doesn't work. I use runtastic, since I had the Blueooth MIDI Service in Doze as "not optimzed", the belt is shown as a Bluetooth device (before it was even not shown), but no pairing.
In CM11 all works fine. Can anybody help me, please? When this doesn't work, I have to go back to CM11.
regards
Friedrich
CM13 (2016-05-12) + BT + Audi A3 speakerphone
I have installed 13.0-20160512-NIGHTLY-i9300 (clean install)
I come from Samsung stock ROM (Android 4.3):
I tried to use BT with the speakerphone in my car (Audi A3). Samsung S3 connects, but when I want to make a call it does not work. The display of the car states: "Netzwerkfehler" (network error). Recieving call works fine. There was never a problem with "Android 4.3".
Could you please fix this issue?
I am going to explain this once so that you know that whatever voodoo or dancing around a build.prop filre because it will do nothing with your bluetooth issue.
/* if we're over buffer high water mark, we're done */
if ((p_port->tx.queue_size > PORT_TX_HIGH_WM)
|| (p_port->tx.queue.count > PORT_TX_BUF_HIGH_WM))
{
port_flow_control_user(p_port);
event |= PORT_EV_FC;
debug("tx queue is full,tx.queue_size:%d,tx.queue.count:%d,available:%d",
p_port->tx.queue_size, p_port->tx.queue.count, available);
break;
}
What we have here is a failure to communicate lol.
The mtu is not being properly negotiated causing overflows of the the audio buffer. So what are the options.
https://issuetracker.google.com/issues/36905704 join the other few thousand people with the same problem.
Look at the 5.0 code https://android.googlesource.com/pl...id/+/android-5.0.0_r3/stack/rfcomm/port_api.c
Which was working.... or use the following to fix the bug
http://androiddoc.qiniudn.com/reference/android/bluetooth/BluetoothGatt.html
Or use a third party app from play store. Testing one right now.
To verify the problem logcat and look for
tx queue is full,tx.queue_size:%d,tx.queue.count:%d,available:%d
I ended up using a third party free ap I found that fixed the mtu issue https://play.google.com/store/apps/details?id=eu.darken.bluemusic&hl=en
The more you know the less time on this pain in the bluetooth you will blow
Related
Hi,
I have many problems with this car kit, but let's start with the most annoying :
kit and phone disconnect after every incoming/outgoing call.
If I receive second call when they are in this "disconnect" state, they magically reconnect and sound is routed to car kit (with some 1-2-3 second delay).
The same happens if I dial new outgoing call.
When call finishes - puff - devices disconnect.
Car kit is upgraded to latest firmware in may.
Phone has stock ROM.
I talked to parrot technical support, they keep telling me "try this/try that" - nothing helps.
Any ideas ?
You know the HTC stock roms are buggy.
i do not use a parrot carkit but use another bluetooth carkit
i have to say that custom roms are behaving better, i can also stream music on mine.
have you tried a custom roms? you can always flash back to HTC rom if it does not work
have a look around in the rom developement section
Fixed
Problem was in Bluetooth settings in Topaz.
Somehow, Audio Gateway was "off" by default, and its power saving mode was "off" as well.
I turned both to be "on", and now phone doesn't disconnect from the Parrot after the call.
Battery life seems to be the same as before.
I was wondering if anyone could help with this problem. My SGS II connects with my in built (Ford) car system, its does everything it should apart from that it can not display the call list (in or out). This was also the problem on my SGS on stock roms until I installed CM7 and then the call lists showed up perfectly. Is it the case that Samsung roms are putting the call logs in a different place that cannot be seen by the car system, if so would it be easy to change this or do I have to wait until a CM rom is made for the SGS II.
SGS II as well as SGS has a very gig problems with BT in car on stock ROM. I had SGS before and there was a problems BT constantly drops in AUDI car system. Temporarily it was solved by BT Fix from the market but finaly solved only coming to a custom ROM (all of them solving that). Now Having SGS II It is total disaster in AUDI - first it constantly drops BT connection and even more - if I'm talking by phone during being connecting to BT, connection failed BUT after call finished phone crushed down and it takes 10 second pushing power button to get it back :-( And then in phone all pairings went out! So - do anybody know this case? And waiting for the custom ROM.
I have a Mercedes E-class (new type). No problems at all with the BT. Very quick to connect, and I can control track fw/bw from the steering wheel. No drops. Works with the default music player as well as Spotify. Phonebook transfere is quick.
In terms of functions I also have no any problems but drops and crashes :-(
Ford focus audio bluetooth
Hello,
I have the same issue with the Ford Focus Bluetooth. It plays ans stops all the time. hands-free works great. Did you solve it?
Hello everybody.
the same issue with new Volvo S60. Previously car kit perfectly worked with Nokia E71... As for S2 - I was able to pair the phone and car. But afterwards, connection could be reestablished only if it's initiated from the phone side (I select "My Car" in bluetooth menu of the phone). Without such actions the car is unable to find the device...
Problem was solved for me when last modem was released. Use ROM with XKE2 modem.
Hi all,
Yesterday I have tested SGS2 (LiteROM 1.5) in my BMW E92 LCI and it works really fine so far.
(call, sms, phone adressbook and bluetooth audio streaming).
BMW offers the possibility to connect two phones at the same time.
I successfully connected my nokia business phone for bluetooth call & SGS2 for bluetooth audio streaming only.
SGS2 is the first mobile that I have connected to my car not only displaying title/artist information properly using the default music player,
but also offers good mp3 sound quality over A2DP.
Strange enough, when I use a different music player (e.g. PowerAMP) the title/artist information is not working any longer. Any ideas?
Cheers, Spad
Problem with transmission over car bluetooth
Hi there,
I have a galaxy s2 that used to connect (with no problems) with my alpine CDE-126BT
After I messed around with the service mode for a while trying to crank up the volumes, there is no transmitted voice over the call (the other side can not here me when I'm connected to the car's Bluetooth).
I know that if I reboot the phone all the changes that was done in the service mode would reset to the default settings, it seems to revert back default but I still have the same problem.
Any advice??
Thanks,
David.
So, I'm having a strange issue with my new Note that I can't quite determine where the root cause may be, or if it's a known issue.
If I register my Note with my car as both a phone and an audio device (how the Infiniti nav/stereo works) I can use the Note as a phone fine UNLESS I start an audio app, such as Pandora. Once a2dp audio starts the Note will no longer connect as a phone device, but it works fine for audio.
I had the phone paired with the stock ATT rom but only used it as a phone, so unfortunately, without a restore to stock, I can't tell if the problem exists with the stock rom.
I flashed to flappjaxxx's rom (which I love) the same day I setup the phone to run Pandora via Bluetooth and that's when I started seeing the problem.
I also see some random connect/reconnects that seem a bit more than usual.
So, I can't say there's a correlation, or if this is a known ICS beta issue or what, but I'm hoping it is and that it's not a design flaw
Way I see it it's either:
1. Flashing to any ICS beta rom has the problem, currently?
2. It's in flappjaxxx's build (doubtful)
3. It's user error...(possible )
4. It's an app issue (ie. Pandora is causing the problem?)
Anyone have any thoughts, suggestions or insights? I've done some searching but haven't found this exact issue yet on any posts.
Thanks!
I have a Kenwood DNX9960 in my Avalanche. It connects also for phone and for streaming media. I can be streaming media from either the stock music player or an internet site like pandora or TuneIn and my calls will automatically come through. When the call ends it goes right back to streaming.
It autoconnects to both as long as my phone is in range when I turn on the kenwood. I did have an issue at first where it would not autoconnect. I deleted the pairing from both my phone and headunit. Then when I repaired I paid close attention to check any boxes to "Always" allow connection and I haven't had any issues since.
I understand the normal pairing process, I've had several phones before that worked fine prior to the Note. So, I'm thinking that it is probably a corrupt bluetooth db... I'm going to be reflashing to Flaps new rom and we'll see how that does
Is there a way to delete the pairing from the nav? I would try that
Sent from my SAMSUNG-SGH-I717 using xda premium
There is. I've tried it all, on both sides of the pairing.
I've reflashed the phone to the B6 from FJ, still no joy. The pairing db was new (so no chance of corruption on the phone) and the pairing deleted on the device.
It seems to be a problem with the phone switching between a2dp and phone bt. When a call comes in (while playing say Pandora over bt) the audio cuts out and then the car shows "disconnected" and then "connection failed" if trying to reconnect to the Note as a phone (ie hitting the phone button in the car).
I'm hoping it's the current ICS build. Just have no way to really know. Hoping some other folks will have seen the same issue.
Going to run some tests with different audio sources and see if the behavior is the same.
Well things seem to be working now, for no obvious reason I'll have to assume that the reflash resolved the issue, I just can't tell for sure why it didn't work immediately after. I think it's due to deleting the old pairing on the car and not shutting down the vehicle.
Cheers.
BT connections
I have similar problem connecting to van audio system (vauxhall). After some experimentation it appears to be an ICS problem, if I reflash my note with gingerbread I have seamless connections for both audio and phone. As soon as I upgrade even with offical ICS bluetooth connections become problematic, I can pair but not autoconnect. Tried samsung and they just "fob off" with it's an incompatable device. Until a bug fix is issued it appears as though it's a choic of staying with gingerbread and have a working system or ICS and no handsfree.
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.
Hi,
I have the problem that the speech quality of the Bluetooth hands-free kit in my car (BMW 1) and my BQ Aquaris x pro with Lineageos 15.1 (have never tested the original OS) is quite bad. On my side, it's not great, but I can understand the other person well (very tinny). However, the people on the other end can barely understand me (high level of background noise, very tinny).
It doesn't make a difference, if I call or get called.
With my previous Samsung S5 with Lineageos 13.1 and Nokia 301, I don't have any problems. In a rental car (Jeep) the speech quality was also bad.
If I just talk on the phone without hands-free, the quality is OK. Therefore, I assume that the problems are due to a bad Bluetooth speaker connection (Bluetooth audio connection e.g. Spotify is also OK).
Has anyone the same issue? Are there any settings I can change or apps in order to improve the current situation?
Thanks for any help,
Schrotti
No one else has this issue? I tried also with a BT speaker with free speech function (JBL Flip4) and the other person on the phone couldn't understand me at all.
This should have been fixed with 2.7.0 firmware update. If not, LineageOS might be a good option for you.
Update - WBS was not enabled and a few audio config issues were fixed, latest LOS 16 has it, just update to that.