Hello friends,
I have been having this issue for a while now and can't figure it out. When I connect to a bluetooth device (i.e. UE MegaBoom, Alpine Stereo, LG Tones..) it would connect seamlessly but after a little while of listening to music, the audio goes in and out. It's like if you press the pause button and then press play really quick.
I have tried everything I can think of to correct this issue and I am all out of ideas. I have changed different roms (PopRocks, Rapture, Ressurection Remix...) and also kernels (stock, AEL, Emotion and BeatMode). My last option is to just turn it in under warranty and get another one. I have attached some logcats of when it was doing the audio issue so maybe someone can find out what's going on there.
I am currently running Rapture v8.2 with beastmode kernel on stock settings and my note model is N910T on T-Mobile.
Related
Hello all
I recently put 4.2.11.1 on my G1. Now when I pair my headset with the phone. The audio is still transfered though my phone. Is this a known issue? is there a fix?
Tech Specs
Handset: G1 w/Cyanogen 4.2.11.1
Headset: Samsung WEP470
The headset worked fine with stock 1.6
The headset appears to pair fine, even verified the bluetooth 'button' is selected while in a call. Still audio goes through the handset and not the headset.
This really is my only issue I love cyanogen so far and hope that the Nexus One is cracked fairly soon after release.
I have the exact same issue with a parrot ck2100-bluetooth hansfree, also running latest cyanogen
I've had this issue and other Bluetooth audio problems under the last several CM releases (See http://code.google.com/p/cyanogenmod/issues/detail?id=819). When audio fails to go through the headset as you describe, turning the headset off and then on again often fixes it. If that doesn't help, then turning the headset off, toggling Bluetooth off and then on, and then turning on the headset usually works.
hrmm, hope this can get fixed I may have to abandon Cyanogen. I have to field call via bluetooth when I work from home.
usually this happens once a week for my bluetooth if i keep toggling BT on and off several times (usually do it if i forget my BT headset). easy fix. not a serious problem with me.
like the person above said: just turn toggle BT off then on, it should connect fine. if not, what i do is go through the settings and unpair them and pair, it should connect to the phone's audio. rinse and repeat.
not a serious bug that should keep anyone away from a certain rom... especially Cyans
Yall in the wrong forum ppl
If its an issue concerning Cy's rom go in his thread n follow the link to submite the issue.
If u trying to solve the problem go in Q&A and ask there or CY's thread.
This has nothing to do with development.
moved to Q&A
I am also having this issue.
I am having a parot c3100 and it pairs fine. But the sound is send to my phone instead of over my car audio system.
I tried bluetooth+headphone fix, but that doesn't help either.
It looks like every cyanogen (based) rom does have this issue ....
Does anybody have other ideas to get it fixed ?
I'm using a Samsung HM3500 bluetooth headset which also has a A2DP stereo option with my AT&T Galaxy Tab. Whenever I play music through the bluetooth, the music will pause for a split second while I am doing other things on the tab such as loading web pages, opening menus, going back to home, etc. It just seems to cut out when I am doing things that use a little bit of CPU power. When idle it mostly works, with only a few cut outs every few minutes or so.
I have flashed gingerbread and my modem to use it as a phone. Do you guys think this is an OS issue or an issue with my BT headset? Thanks
I use bluetooth headsets alot and i had this issue from overcome beta (first gingerbread release) to 2.0.0 gold. Didn't have it with froyo before and don't have it anymore since overcome 2.0.1.
Thanks, I may have to try flashing Overcome.
If you disable wifi the issue should go away. I know some people were able to decrease the frequency of the breaks in audio by changing the interval at which it searches for wifi locations, but I don't recall. This is a very common issue which has been seen on android and windows mobile devices alike.
I don't think thats the issue I have. I only have wifi turned on when I'm at home and while at the office. During my morning/evening commute (train to subway to bus) is when I use my bluetooth headphones the most, and wifi is switched off. I never got to try it with Froyo because I flashed Gingerbread as soon as I got my Tab last weekend. I will try flashing overcome tonight, hopefully it solves the issues. Thanks
Hey there fellows,
I have a Samsung Galaxy S I9000 that I've been using since Froyo. As an accesory, I've always used the Motorola S9-HD A2DP headset to listen to music and take calls wireless.
The thing is that ever since I've started flashing GingerBread ROMs (stock), it started to mess up.
Let's begin to enumerate the issues:
1) After having the device paired, simple turning the headset on wouldn't connect to the phone (as it worked before 100%)
2) With the headset turned on, if I go to the Bluetooth menu on the phone and "click" to connect, it would say connecting and one of this things would happen:
- "Connecting..." would display forever until I shut the BT radio off
- It would connect and immediately disconnect, even sometimes the headset shuts down too!
- It would connect to one of the profiles: the audio one or the headset one, but not both
- 1 out of 50 times it would connect to the audio profile online and finally be able to play music through them
3) While the headset is playing music (i.e. connected), I turn it off, and sometimes Android keeps showing the icon as connected, for like 10 minutes, until it eventually times out
As you might guess, I've been searching since this arised for a solution, comment, similar behavior reported from other users, etc, without luck; neither here at XDA, Google or other related forums. I've found some *similar* stuff like car audios disconnecting but finally they fixed them or were some issues with the car app or something, unrelated to this.
This started happening ever since the first GingerBread I've flashed; now I'm on stock JVS and the same thing still goes on. I've tried before flashing any kernels (as stock as it gets) and this happens too. I've tried after flashing pretty much every kernel (to see if they somehow fixed this) and the problem persisted.
Let me be clear the the headset works great; if I use it with another phone (Nokia) it doesn't present any of these issues; neither did here before GingerBread!
So far, the only remotely possibility to use it fine and that works 95% of the times is:
1) Erase the headset memory of paired devices
2) Erase the phone memory of paired devices
3) Pair the device
As you can imagine too, doing this EVERY TIME I want to use the headset is an awful lot of pain!
Well, thanks for your time and for reading so far... any kind of pointer, advices, consolation that you can provide would be more than thanked for!
Best regards,
Anyone?
sorry no solutions from me.....but I did incur a similar situation when I flash jvq stock (music player would stop playing music and make bootanimation sounds)before flashing over to re by darky.....since being on darkys the problem has gone.maybe try a custom rom!!!
Sent from my GT-I9000 using xda premium
urban bumpkin said:
sorry no solutions from me.....but I did incur a similar situation when I flash jvq stock (music player would stop playing music and make bootanimation sounds)before flashing over to re by darky.....since being on darkys the problem has gone.maybe try a custom rom!!!
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
That's a good thing I didn't try! I refrained from flashing a Darky because all the "extra" steps involved besides directly flashing the files from Odin and also the auto voodoo lagfix kernel that converts unless you put the files to NOT to on some directory... plus the "bloated" experience over a stock ROM.
I think I should try one though, and also think that the BT should work OK in stock too! First I'd like to confirm if it's a "known" issue with the Ginger ROMs or not...
Anyway, thanks for your advice, might flash Darky soon!
its amazingly easy to do...just follow the guides to the word.....
Sent from my GT-I9000 using xda premium
Hi everyone, thanks for taking the time to look at this.
I'm having an issue where if I run any CM based rom I get "com.bluetooth.android has stopped responding" when connecting to my Mazda car stereo or my jawbone speakers. I've had this issue on every version of CM that has been out since November. If I use a stock based rom, everything works fine and I don't have any issues. It doesn't matter if I'm using 4.4.2 or 4.4.4, the previous scenario still holds true.
Any ideas what I can try in order to solve the issue or at least narrow it down further?
I really like flashing different roms and checking out the awesome features everyone has added, but I unfortunately need my bluetooth to work properly.
Thanks in advance for all the help!
nuggetfn22004 said:
Hi everyone, thanks for taking the time to look at this.
I'm having an issue where if I run any CM based rom I get "com.bluetooth.android has stopped responding" when connecting to my Mazda car stereo or my jawbone speakers. I've had this issue on every version of CM that has been out since November. If I use a stock based rom, everything works fine and I don't have any issues. It doesn't matter if I'm using 4.4.2 or 4.4.4, the previous scenario still holds true.
Any ideas what I can try in order to solve the issue or at least narrow it down further?
I really like flashing different roms and checking out the awesome features everyone has added, but I unfortunately need my bluetooth to work properly.
Thanks in advance for all the help!
Click to expand...
Click to collapse
Ha. I have the exact opposite problem. I have a 2013 Subaru Outback and every AOSP rom works perfectly and any stock rom has issues. Calls work fine on both stock and AOSP based roms, but media playback has always presented a problem for me on stock roms. On AOSP roms I can play Netflix, Youtube, music, etc through my car speakers but I can only get Play Music to work on stock roms. Sometimes on a stock rom, Youtube will play for 2 seconds but then cutoff the audio. The video will continue to play, but the audio is lost. Very strange.
I've searched around a bunch, and it looks like i's not an uncommon issue, but it doesn't look like there's a systematic solution. I assume there are too many variables (car makes, models, years, stereo upgrades, Nav options, etc) to be able to isolate an issue. You just have to keep trying different iterations.
Keep me posted if you find a solution.
Hi guys,
The mi3 is my first Phone which does Not work with my skoda Bluetooth Radio. Neither the car Buttons for next track etc are working nor the track Informations are shown in the Radio screen.
I trink it is a Kernel Problem, right? Or are there any tweaks i could try to get This working?
Thx
Hi
I am also seeing this with Xiaomi Mi3 phone.
The phone plays in the car's audio but you cannot control the track from the car radio buttons. start/stop does not impact the phone and the prev/next buttons are grayed out.
Anyone else seeing this issue?
Anyone knows how could I overcome this?
(I did check with a different phone, lumia 930, and it's working correctly)
Thanks,
Uri
Hi,
I am using my mi3w with Hyundai elite i20. There's no problem in changing the track or anything. The only problem that I've encountered was with the song info display. It isn't showing the song info in car's display.
Edit:
That was with the ivans aosp latest.
Now I'm on MIUI 5.8.28 Beta and everything including the song info display works perfectly with the stock music app.
Sent from my MI 3W using XDA Free mobile app
Music App
Are you seeing this issue with the stock music app? How about trying with any other application.
I cant test it out as, I'm currently not running stock ROm on my Mi3.
Thanks
I am still seeing this issue.
This happens with all music apps and podcast apps.
My ROM is just the native rom that comes with MI3.
Anyone else seeing this?