Database Info

Definite issue with BT media and ICS ROMs

FYI, there is an issue with pretty much all ICS ROMs and the BT stack included in them. I have a brand new, top of the line Jawbone BT that supports everything, works flawlessly in Cyanogen and non-ICS ROMs, but will barely work in ICS.
Basically, after a reboot, it connects and says Connected (no media), then switches to Connected. Everything works fine until I disconnect and reconnect again.
After that, it will work for only voice calls. Media will always go out the speaker. I have tried everything to fix it to no avail. The only resolution to get A2DP media streaming back is to reboot.
When it happens, the media checkbox is still there and checked, but it doesn't work. I switched back to HyperSensation (Cyanogen) and everything works as it is supposed to.
Apparently ICS bluetooth works fine for some BT headsets and not others. This also seems to be an ongoing problem for other phones as well, even non-ICS.
I am not well versed in reading the debug logs, but if anyone is interested I can post them here, provided they tell me which ones they want.

I'm having troubles to. My problem is I cannot start a call via the Bluetooth Dial button on my radio. It's as if the phone doesn't even recognize that you are pressing the button. Tried installing Vlingo, but the prompt doesn't even work anymore.
The old solution was to install the Voice_dialer.apk...but that doesn't seem to be compat either

I can confirm the issue with the virtuous ICS as well. I have bt stuff from Jawbones to BlueAnt's and all have the same issue. Prior to this was the issue of cutting out and now it's the off/on bt streaming. To "fix" the issue, is to reboot. Annoying yes. But ICS is still so sexy

I've got the same problem, ROM Elegancia ICS 1.0.6 and 1.1.0
After pairing with bluetooth headset, first time I play music everything is ok. after re-connecting, music controls works ok, but sound is thru phone's speakear not thru the headset.
After rebooting the phone the situation is the same- first connection everythings ok, another ones not.
Checked with SE MW600, Jabra extreme and car's bluetooth.
The problem occurs even with clear installation (before I restore backups).
Still can not find solution so I got back to GB.

So its not just me! I can confirm that my Beats Wireless acts exactly like described.. And with a reboot fixing it again!
I think the devs here might be able to fix it, but its properly not going to be an importent issue to fix.. Fingers crossed for a fix, or maybe the future leaks will have it done!
Sendt fra min HTC Sensation Z710e med Tapatalk

ftblstr2319 said:
I'm having troubles to. My problem is I cannot start a call via the Bluetooth Dial button on my radio. It's as if the phone doesn't even recognize that you are pressing the button. Tried installing Vlingo, but the prompt doesn't even work anymore.
The old solution was to install the Voice_dialer.apk...but that doesn't seem to be compat either
Click to expand...
Click to collapse
Vlingo has always been problematic for me... My solution (worked on ICS too) was to get it working on an older ROM (not sure which one anymore) then use titanium backup and back up APP+DATA on a ROM that it is working on. Then, restore APP+DATA on the new ROM.
The first time you hit the button on your headset it will ask you what app you want to use for voice dialing and give you Vlingo, Vlingo InCar, or Voice Search. Choose Vlingo and check the box to make it default and you are good to go.
Just make sure after you get it working on the new ROM to back it up again... then the next time you switch ROMs, restore whatever the latest backup is. I am not sure what it changes, but I have been through Cyanogen, all of the ARHD versions, all of the InsertCoin versions, and a few others (I can never make up my mind on ROMs) and this trick has worked in all of them.
IMPORTANT: Make sure in Titanium Backup to uncheck the option to restore system libraries in ROM (that can cause issues going between major versions of android), and make sure toenable the features in Titanium Backup for attempting to migrate data.

I also get the same issue when I try to connect my MW-600 with ARHD ICS 6.0.2.
Can anyone help?

You guys who just have to reboot your phone are getting off easy. When I lose Audio Streaming to my car head unit, I have to delete the device and re-pair it to my phone after a reboot.

Same here with mw600 on virtuous Inquisition 2.0.1. Only first connection plays music through headset.
I am sure that first 4.0.1 beta base was not affected. This bug came with 4.0.3
Sent from my HTC Sensation using Tapatalk

dante-fu said:
Same here with mw600 on virtuous Inquisition 2.0.1. Only first connection plays music through headset.
I am sure that first 4.0.1 beta base was not affected. This bug came with 4.0.3
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
really??.. Im gonna try an old backup then.
Edit:
Backup was removed sadly.. :/ cant test it, but maybe someone else can?

Well, the ROMs are still there to download
With 4.0.1 I was on radio version 10.59. I am not expert on radios and RILs but I guess these things affect also BT performance. Right?
Sent from my HTC Sensation using Tapatalk

Shidapu said:
really??.. Im gonna try an old backup then.
Edit:
Backup was removed sadly.. :/ cant test it, but maybe someone else can?
Click to expand...
Click to collapse
I reverted back to the virtuous 4.0.1 build from the most recent (having the new fw and radio) and has fixed the Bluetooth issue. Now I just have to live with messed up signal bars and a browser that randomly exits.
Sent from my HTC Sensation using xda premium

Hi,
Reporting this BT issue for me (SGS 2 with ICS 4.0.3, XXLP2 that can be found on XDA, originally from samfirmware):
I try to send files from my laptop to my SGS 2, 1 at a time and the transfer will suddendly halt some of the way through and ICS looks like it's rebooting but it's actually not, I mean not a full proper reboot; the phone does not switch off, the boot anim plays as if restarting, first BT is off then the icon come up in the top bar...
Hopefully, the Simple & Clean, ICS version, is round the corner ;o)
beng

using arhd 6.1.1 here on sensation XE with SE mw600 headset, no issues, calls and media working as normal

BT connectivity seems to be fixed in the latest leaked ICS + Sense RUU.
Is the sensation supposed to support any other remote control features than pause and play over BT?

I can confirm that on my Galaxy s2 using the 'official' ICS rom released yesterday still causes my phone to reboot.
This happens when bluetooth is paired with my car stereo and streaming audio or voice calls. It causes a reboot, usually happens after 10-15 minutes.
Never happened on gingerbread of any version. And has happened on all versions of ICS leading up to 'official' release.

I can confirm that bluetooth will cut off and be off completely quite randomly while listening to music or Pandora.
Only a reboot gets bluetooth to turn back on.
I have experienced this on two Motorola S9-HD headsets on various ICS roms
Sent from my HTC Sensation Z710e using Tapatalk

[Q] Wifi Issue

I own a HTC One S with stock vodafone (gb) rom, rooted, ICS 4.0.3, Touch 4.0. As I see a lot of people have similar issues as mine, however, I wasn't able to find a working solution. So the problem is that the phone stopped being able to connect to wifi networks - no matter if secured or free. I tried to change the settings from dhcp to static, stll nothing. It goes through connecting>obtaining ip address>authenticating>saved,secure... in whatever order, and the cycle repeats over and over... Sometimes bars appear, blink and disappear again. I had no wifi problems until last night, when I went to a place with free wifi, and for the first time I could not connect to it. After that the issue continued at home. Restarting the router/phone don't work. Has anybody found a working solution?

martochkata said:
I own a HTC One S with stock vodafone (gb) rom, rooted, ICS 4.0.3, Touch 4.0. As I see a lot of people have similar issues as mine, however, I wasn't able to find a working solution. So the problem is that the phone stopped being able to connect to wifi networks - no matter if secured or free. I tried to change the settings from dhcp to static, stll nothing. It goes through connecting>obtaining ip address>authenticating>saved,secure... in whatever order, and the cycle repeats over and over... Sometimes bars appear, blink and disappear again. I had no wifi problems until last night, when I went to a place with free wifi, and for the first time I could not connect to it. After that the issue continued at home. Restarting the router/phone don't work. Has anybody found a working solution?
Click to expand...
Click to collapse
Not a good solution but you could try a factory reset if nothing else works.
-Sent from my TMOUS HTC One S.-
-Stock/rooted 2.21 + 1.06s baseband-
-Hboot 1.06-

I rebooted the phone a few times (waiting 6 mins when off) without fastboot on and on the third time it started working. I hope this doesn't happen again... As I searched through the forums I saw a lot of people having similar issues mainly with dhcp.. hope there's a fix for that...

Problem appeared again... This time reboot isn't solving anything. When I put it on static IP it connects to the network and disconnects over and over again. This s*** is driving me crazy...

are you running a custom kernel?

No. It's stock. Recovery is CWM, phone is rooted via this method http://forum.xda-developers.com/showthread.php?t=1577831

it could be the boot.img causing your issue. i rooted via this method http://forum.xda-developers.com/showthread.php?t=1583427 and have never had a problem with wifi unless i had flashed a custom kernel

Well.. I don't know, because I haven't flashed a custom ROM.. Just rooted the stock one... Btw it started working again after like 10 reboots with no fastboot on, but experience tells me that it'll go crazy again...

you could also try flashing a custom rom, it might fix the issue

[Q] Bluetooth Issue - All Jellybean ROMs - All Kernels

Can someone please help me with this. I really want to update to Jellybean but I have the most annoying bluetooth issue on every ROM I have tried.
I have tried all JB ROMs and standard Kernel and the Sultan Kernel. I have asked in a couple of the ROM threads but got no reply.
The issue is when I connect to my car it takes 5 seconds for the sound to transfer from the phone internal speaker to the bluetooth in my car.
Use my phone for work and can't wait 5 seconds in the car when I receive a call before I can hear the other end of the conversation.
It worked perfectly on my old ICS ROM.
Anyone encounter this or know how to fix it?
Thanks a million for help!

turn your phone s-off if u ain't.
:-??
------------------------------------------------
PRESS THE PRETTY "THANKS" BUTTON IF I HELPED
Sent from a shaked up HTC Sensation XE using xda premium

lassykk said:
Can someone please help me with this. I really want to update to Jellybean but I have the most annoying bluetooth issue on every ROM I have tried.
I have tried all JB ROMs and standard Kernel and the Sultan Kernel. I have asked in a couple of the ROM threads but got no reply.
The issue is when I connect to my car it takes 5 seconds for the sound to transfer from the phone internal speaker to the bluetooth in my car.
Use my phone for work and can't wait 5 seconds in the car when I receive a call before I can hear the other end of the conversation.
It worked perfectly on my old ICS ROM.
Anyone encounter this or know how to fix it?
Thanks a million for help!
Click to expand...
Click to collapse
It could be a device incompatibility with the blue tooth receiver.
There are a few devices that just don't work right with the JB roms even though bluetooth does work. For instance on both Bruce's ROM and the offical CM10 rom, I don't have this problem. So it CAN work. But like I said there ar enumerous people who have had issues that turned out to be some kind of issue with the device not communicating well with JB.
It could still be an issue with your phone though. Do you have any apps that might interfere with bluetooh like an automatic volume up app when blueooth connects or something like that? If so, delete all that stuff. See if the results improve.
Do you have another bluetooth device you can test it with? At lest we could narrow down if it's a reciver issue or a ROM issue.
Also try doing a fresh install after a full wipe. Then just boot it up and try it. Don't install anything else. Just see if you have the problem on a completely clean install. If you don't, you might have an app interference issue.

Skipjacks said:
It could be a device incompatibility with the blue tooth receiver.
There are a few devices that just don't work right with the JB roms even though bluetooth does work. For instance on both Bruce's ROM and the offical CM10 rom, I don't have this problem. So it CAN work. But like I said there ar enumerous people who have had issues that turned out to be some kind of issue with the device not communicating well with JB.
It could still be an issue with your phone though. Do you have any apps that might interfere with bluetooh like an automatic volume up app when blueooth connects or something like that? If so, delete all that stuff. See if the results improve.
Do you have another bluetooth device you can test it with? At lest we could narrow down if it's a reciver issue or a ROM issue.
Also try doing a fresh install after a full wipe. Then just boot it up and try it. Don't install anything else. Just see if you have the problem on a completely clean install. If you don't, you might have an app interference issue.
Click to expand...
Click to collapse
Hi thanks for replying.
I will try Bruce's ROM but the official CM10 ROM didn't work for me.
I don't have any apps that could be interfering as all I have done whilst testing this problem is do a full wipe, install the JB ROM and go and check the bluetooth.
I will check tonight if the issue exists on another bluetooth device and report back any problems.
Cheers

AW: [Q] Bluetooth Issue - All Jellybean ROMs - All Kernels
Delete please

[Q] Bluetooth handsfree problem

I have a Sony bluetooth head unit in my car which supports handfree and audio streaming profiles. I can play my music through the head unit just fine via bluetooth. I can also make and receive calls without problem when I am listening to the radio (ie when I am not listening to my own music). However, when I am playing my own tunes and I either make or receive a call, the head unit indicates I am on a call, it mutes the music but I just get silence through the speakers.
I used to have a Galaxy S Advance and it all worked just fine without too much configuration on the phone or head unit; basically just pair them up, make sure the right boxes are ticked in the bluetooth options and thats it.
Any idea what the problem could be? I've tried an upgrade to 4.2.2 but it didn't help...

Hi,
I have a similar problem. I can pair my s2 plus with cm11 from this thread to my car kit (Parrot MKi 9200). Playing music via phone on the car speakers works fine but when I place a call the receiving phone just gets loud static (and my voice very very silent).
I wanted to ask the developer of the cm11 I am using if he sees a way to exchange the bluetooth module (or what androis equivalent is) to the one of e.g. Android 4.1.2 because I know that one works perfectly. I am posting here because I havent reached 10 posts yet.
Of course I am open to other workarounds and ideas.
Thanks,
Kiesel

Bluetooth
Same issue here,
everything (music etc.) is okay, but the phone connection.
I'm connecting to my Ford Sync.
I can connect, but then the quality of the voice is very very bad, I can hardly understand anything...
I thing there's a configuration file in the etc/ folder, maybe that need some upgrade?!?
Hope someone can help, because I really like to keep CM11 on my phone...
Dan

This is a known problem wich has been asked 100 times before
Sent from my GT-I9105P using xda app-developers app

safariking said:
This is a known problem wich has been asked 100 times before
Sent from my GT-I9105P using xda app-developers app
Click to expand...
Click to collapse
How is this message supposed to be of any help? Of course we know that. We have seen a lot of threads. I have read the whole bug report including all the comments on googlegroups, I have browsed dozens of websites and googled my ass of. What I didnt find was an explanation (at this point I dont expect to find a fast solution anymore). After reading the googlegroups bug call I thought it was a problem with the bluetooth stack that apparently is being redeveloped by google. But here cooldevelopment said it isnt a google problem.
I fully understand that it must be annoying for you to see this question a million times but please understand, that it is also annoying (and unsatisfactory) to not know whats going on.

DeKiesel said:
How is this message supposed to be of any help? Of course we know that. We have seen a lot of threads. I have read the whole bug report including all the comments on googlegroups, I have browsed dozens of websites and googled my ass of. What I didnt find was an explanation (at this point I dont expect to find a fast solution anymore). After reading the googlegroups bug call I thought it was a problem with the bluetooth stack that apparently is being redeveloped by google. But here cooldevelopment said it isnt a google problem.
I fully understand that it must be annoying for you to see this question a million times but please understand, that it is also annoying (and unsatisfactory) to not know whats going on.
Click to expand...
Click to collapse
I know what you mean but i think the best method now is to wait until cooldev find a solution to this

As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?

kidmanis said:
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
Click to expand...
Click to collapse
Hmm, interesting. I will try this out as well. Might probably be a week though, I am leaving for holidays tonight and cant risk making my phone unusable. Maybe somebody else is willing to give it a try?

kidmanis said:
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
Click to expand...
Click to collapse
Thanks now i know where to search the problem.

Hi,
here is a logcat of a bluetooth connection during a call on stock rom/stock kernel.
What I did:
-start logcat
-start bluetooth
-chose a contact
-call contact-
-talk for a minute
-hang up
-stop logcat
I then wanted to flash the mosh kernel and do the same again but the last time I checked there wasnt this huge plethora of different kernels to choose from. Very impressive work!
Could you tell me which one you would like me to flash and I would then redo everything?

Hi,
I tried installing mosh kernel 1.8 and 1.85 (for stock, init.d enabled) on sazy rom but it didnt boot. It stayed at the very first screen you get when you turn the phone on. I then installed your cm11 build8, connected via bluetooth to my car and had someone call me.
Attached is the logcat.
Do I need the samsung stock rom for mosh kernel? I thought sazy rom was a stock rom?

[Q] Headset issue with Sebastian Kernel's ROM

Hi everyone,
this is my problem. I use almost always a very good quality headphones set (but without mic): obviously if I need to answer/make a call I have to talk into the phone's mic. Well, very often I'm not able to send my speech...I'm receiving very well, but the listener on the other side is not able to hear me, or at least he listen a very-very-very low sound. I did myself a test, calling me from an other mobile phone, and obviously I tried more than one headset.
I wrote "very often": actually, at the beginning after a reboot, this is not happening. It starts happening after a while, usually one hour after reboot: if you have a call, you are able to talk for 5 maybe 10 seconds, then there is the issue.
I thought it was a ROM bug (I was using Viper 3.1.4), then I tried Viper 5, then Elegancia, then Revelation...same problem... so I think it could be a kernel related bug ( @SebastianFM Kernel). Actually, no AOSP ROM has the same issue (Albinoman, Sultan, bilal, etc.).
Please, someone with these ROM can check if it is true?

Sorry for bumping it up. Anyone has experienced same issue? @SebastianFM, could it be ROM related issue, or I must search in a different place? Take in account that it happens only in ROM powered with your kernel...
pdbc said:
Hi everyone,
this is my problem. I use almost always a very good quality headphones set (but without mic): obviously if I need to answer/make a call I have to talk into the phone's mic. Well, very often I'm not able to send my speech...I'm receiving very well, but the listener on the other side is not able to hear me, or at least he listen a very-very-very low sound. I did myself a test, calling me from an other mobile phone, and obviously I tried more than one headset.
I wrote "very often": actually, at the beginning after a reboot, this is not happening. It starts happening after a while, usually one hour after reboot: if you have a call, you are able to talk for 5 maybe 10 seconds, then there is the issue.
I thought it was a ROM bug (I was using Viper 3.1.4), then I tried Viper 5, then Elegancia, then Revelation...same problem... so I think it could be a kernel related bug ( @SebastianFM Kernel). Actually, no AOSP ROM has the same issue (Albinoman, Sultan, bilal, etc.).
Please, someone with these ROM can check if it is true?
Click to expand...
Click to collapse