Develop Bugs

[DEV]Stock Headset behavior to be fixed

Hello,
So we're definitly getting there : more and more fixes for our Android ROMS on the HD2. Major bugs are fewer every month and I'm sure we'll reach a very very close-to-native feel in a matter of months.
Still, some bugs seem resistant or maybe, not looked into. That's the case for the stock headset behavior.
Support for the stock headset has been released a few months are the first Nand Android ROMS back in January but was never really improved. And to be completely honest, it never really worked.
Here is the buggy behavior
Musing listening :
When plugged in, the headset will behave properly : back, pause/play, next buttons respond quite well. However after a while (around a minute of music playback I would say but I guess it could be timed more precisely), they don't. Pausing or skipping to the next song might work but most of the time, it would ask several attempts (from two to ten or more !).
The back button never works : either it does not respond at all, either it behaves as a forward song, skipping to the next song.
You have to actually interact with the player with the touchscreen to restore headset responsiveness. Until it breaks again a minute later.
Call answering :
This is a field I didn't experiment much : as answering a call with the headset is a gamble, I tend to quickly disconnect the headset in order to respond. If not, answering with the Play/pause button might not work or might ask for way too many attempts. If I succeed to answer, the person will generally tell me that he or she can't hear me well. Mic issue ?
This happens with every ROM out there, with every kernel, with every Music player, stock or third-party.
I don't have my HD2 with me now (back to HTC for a while) so I can't provide logcat but I'm sure there are other music listeners out there who will help out.
I don't know if it's kernel related or not but I would assume it won't be that hard to fix...we just need someone who look into this.
I'll try to keep the OP updated with new information as it comes out...

I have a blackberry headset that works great. No such problems with pausing and resuming music or even answering calls for hours on end, with long holding to voice dial.
On cm7 roms you can long hold volume up with screen off to skip songs, no problems here, perhaps try another headset.

It seems it works fine with other headset yes but it means it's really not a big issue to fix for users who uses the stock headset...

DannyBiker said:
Hello,
So we're definitly getting there : more and more fixes for our Android ROMS on the HD2. Major bugs are fewer every month and I'm sure we'll reach a very very close-to-native feel in a matter of months.
Still, some bugs seem resistant or maybe, not looked into. That's the case for the stock headset behavior.
Support for the stock headset has been released a few months are the first Nand Android ROMS back in January but was never really improved. And to be completely honest, it never really worked.
Here is the buggy behavior
Musing listening :
When plugged in, the headset will behave properly : back, pause/play, next buttons respond quite well. However after a while (around a minute of music playback I would say but I guess it could be timed more precisely), they don't. Pausing or skipping to the next song might work but most of the time, it would ask several attempts (from two to ten or more !).
The back button never works : either it does not respond at all, either it behaves as a forward song, skipping to the next song.
You have to actually interact with the player with the touchscreen to restore headset responsiveness. Until it breaks again a minute later.
Call answering :
This is a field I didn't experiment much : as answering a call with the headset is a gamble, I tend to quickly disconnect the headset in order to respond. If not, answering with the Play/pause button might not work or might ask for way too many attempts. If I succeed to answer, the person will generally tell me that he or she can't hear me well. Mic issue ?
This happens with every ROM out there, with every kernel, with every Music player, stock or third-party.
I don't have my HD2 with me now (back to HTC for a while) so I can't provide logcat but I'm sure there are other music listeners out there who will help out.
I don't know if it's kernel related or not but I would assume it won't be that hard to fix...we just need someone who look into this.
I'll try to keep the OP updated with new information as it comes out...
Click to expand...
Click to collapse
As for the music, i mainly use the volume rockers on device for volume + (next/prev), the play/pause button does work when songs are playing but after pausing and idling for sometime, the device goes to sleep and the key does nothing (This might be actual behavior ? as the kernel goes into suspend, needs to be checked on a htc with native android)
The call behaviour is true as per your explanation. The mic inuse when wired headsets are plugged is of the device and not of the headset, i have verified this by placing the device away with headset plugged in and gradually bringing it close during a call.

I had recently bought the stock original headset. working very well. i use poweramp. play / pause ffw rwd are all working even when screen is off.
i can answer calls with the call button and the caller can hear me clearly.
maybe another rom or another headset can bring in some varied results.

Then it must be hardware related. I have an EU HD2 and I swear it doesn't work with any rom (Sense/ASOP-CM7/MIUI), any kernel, any player.

What I think would be great is if someone could get it to work perfectly with a set of iphone headphones. EVERYONE makes a nice set of headphones for that dang phone and their cheep
Sent from my HTC Runnymede using XDA App

+1 for the idea !

well..with rafpigna/hieros kernel the headset works almost 100%.
I mean:
when phone is on, everything works 100%
when it is sleeping but music is playong, it works 100%
when radio is playing and the phone is sleeping: I can switch channels and stop it but then I cannot do anything.
with tytungs kernel I could not do anything when the screen was off and the phone was sleeping.
(in the same ROM of course)
so it is bug in kernel drivers

DannyBiker said:
Then it must be hardware related. I have an EU HD2 and I swear it doesn't work with any rom (Sense/ASOP-CM7/MIUI), any kernel, any player.
Click to expand...
Click to collapse
Since you mentioned that, mine is T-Mobile. Might be hardware related.

how about trying Tytung 12.4 v3 kernel?
how about reading the low speakers/Mic gain fix thread?
it's fixed i think, i don't have these issues after installing typhoo' cm7 build with this kernel...

AVRCP bluetooth not working?

Audio/Video Remote Control Profile (AVRCP) is not working on any app. i tried it with my headphones to play/pause and skip a song and nothing. same thing on my car. so its definitely the phone causing the problem. anyone else?

Same here - tried two different devices. No play / pause.

OK, it looks like Google Music has a strangle hold on AVRCP. It works in that app (which I don't use) and nowhere else.
This is one of the reasons I ditched Google Music on my last device. The minute you install it, no other app works with AVRCP.
I tried disabling it in Applications (I am running stock w/o unlock or root ATM), but that does no good. Also tried re-enabling and FC, but again, no joy.
Hopefully someone more skilled that I has a suggestion...
EDIT - there don't appear to be any settings in Google Music to turn off their control. Tried a couple apps in the market like Headset Interceptor, but they did not help.

no google music isnt the problem. it doesnt work on any app. plus on my old phone google music didnt cause any problems and worked just fine.

qman66 said:
no google music isnt the problem. it doesnt work on any app. plus on my old phone google music didnt cause any problems and worked just fine.
Click to expand...
Click to collapse
Hmm... I guess we have two different problems.
On my GNEX, AVRCP (I only care about playing and pausing via BT) works on Google Music, and nothing else.
On my old DINC, I had AVRCP working until I installed Google Music (only change I made), at which point all my other apps' AVRCP capabilities stopped working (Audible, Subsonic, etc.). I then uninstalled Google Music (again, the only change I made), and my AVRCP started working again.
To me, that experience makes it pretty clear that Google Music was causing me grief on my old device, and is mysteriously the only thing that works with this feature on my new device.
Like I said, maybe you have something else going on.

so noone else has this problem?

Try Power Amp
The Power Amp player seems to work on my Senheisser MM450 BT Headphones

I have the same issue.
AVRCP on my bluetooth headset (Plantronics BackBeat 903+) stopped working when I started using Galaxy Nexus.
On my old phone I was using BeyondPod and Player Pro with my headset and play/pause worked from the headset. Now, I cannot stop or play music in those apps.
I can confirm that this has something to do with Google Music.
I found that if I start Google Music then AVRCP works with the headset. If then I go and start Player Pro, the AVRCP stops working, and pushing play/pause button does nothing. Then, when I go back to Goolge Music, everything works fine once again.
So existence of Google Music somehow hampers the ability of other apps to claim bluetooth headset remote control fully. They claim it partially, because Google Music is not starting music on pushing play button, but the player does not start music as well.

Spotify on Nexus S stopped responding to BT Play/Pause after ICS update
I am encountering the same issue after updating my Nexus S to Ice Cream Sandwich via an OTA update.
Using Seinnheser MM450s, I was previously able to fully control Spotify (Play/Pause/Next/Previous). However since updating to ICS, only Next/Previous work. The main button (Play/Pause) has no effect.
However, when I launch the factory Music app, it responds to all controls.
To try and 'debug' the issue, I downloaded a trial of "Headset Droid" app, and used its BlueTooth command monitor debugging facility. As expected, it correctly intercepted and confirmed the Next/Previous button pushes, however failed to acknowledge the Play/Pause functionality.
Has a bug report been filed regarding this issue? Can anyone suggest a workaround?
Thanks - Anj

I have the same issue. Previously - my Nexus One running stock/unrooted 2.3.6 worked perfectly for play/pause/next/previous/start|end call on cheap Chinese Bluetooth headphones. Been using them for weeks with Subsonic, flawlessly.
Moved to Galaxy Nexus, 4.0.1 (apparently .2 hasn't rolled for my geography yet) - same headphones, only next/previous/start|end call work. Play/Pause does nothing in either state, whether I am in Subsonic or not. Haven't tried Music yet as I never use it (lets face it, its of limited value outside the US!).
But I did notice that if I press and hold for quite a while, the play/pause button, it seems to stop the music in some way that isn't quite pause, but nothing else works after that, you have to manually restart it from the app.
(anecdotally, I have the unsubstantiated feeling that some/all system sounds are not piped to the headphones as effectively as Gingerbread. But I haven't tested this yet)
Finally, I note I have occasionally used these headphones on my Honeycomb tablet - Asus Transformer, 3.2.1(?) and it behaves the same as the Nexus One, not the Galaxy Nexus so this is definitely an ICS issue.

I have reported this fault on code.google.com/p/android/issues/detail?id=23172 - please add to the comments so that it gathers momentum as an important issue.

I hate to post a me-too, but me too :-(
I'm using doggcatcher on a rooted verizon galaxy nexus on the stock 4.0.2 firmware. My headphones are a sony MW600. Play/pause/ffw/rew don't work in doggcatcher.
I started up google music and went through the setup wizard. the AVRCP buttons work for google music only. Enabling/disabling doggcatcher's "bind to headset forcefully" option has no effect.
I used Titanium Backup to make a backup of Google Music, and then uninstall it. Now Doggcatcher responds to AVRCP button-presses. Anyone else want to give it a try?

Thanks daoist,
Can you confirm that you have to be root to use that particular functionality of Titanium Backup?
Thanks again - Anj

Interesting. Now it seems like google music and Pandora both respond to it. But google listen does not.
Sent from my Galaxy Nexus using xda premium

I'm having the same issues with my Galaxy Nexus as well. I starred the link mentioned above. I'm using a Plantronics Voyager Pro HD and none of my music controls work. I also can't tap the call button to engage a voice search or anything. I hope Google fixes this sometime soon...This makes my headset quite a bit less useful...

I can confirm the issue on my Gnex LTE running 4.0.2. Google Music works fine. I don't know why, but Doggcatcher is also working fine (Play/Pause works). I noticed that there is a setting in Doggcatcher for "bind to headset" and "start application" - both of which are checked on mine, so maybe that's why it's working.
However, both Pandora and Mog are not working with Play/Pause and there are no headset options in the app settings. So either 1) apps just need to be updated for ICS, or 2) something is amiss in ICS that prevents other apps from using the headset controls. Most likely the latter...

Apparently the developers of Media Button Router have "fixed" this issue.
See here: code.google.com/p/media-button-router/issues/detail?id=10#c5
Download from here: market.android.com/details?id=com.harleensahni.android.mbr&hl=en
I can confirm that after installing Media Button Router and configuring to send all BT commands to Spotify - I no longer have the Play/Pause problem.
Thanks - Anj

qman66 said:
Audio/Video Remote Control Profile (AVRCP) is not working on any app. i tried it with my headphones to play/pause and skip a song and nothing. same thing on my car. so its definitely the phone causing the problem. anyone else?
Click to expand...
Click to collapse
I use beyondpod for podcasts - and avrcp works fine.. worth mentioning that I'm not using google music.
-m

anj747 said:
Apparently the developers of Media Button Router have "fixed" this issue.
See here: code.google.com/p/media-button-router/issues/detail?id=10#c5
Download from here: market.android.com/details?id=com.harleensahni.android.mbr&hl=en
I can confirm that after installing Media Button Router and configuring to send all BT commands to Spotify - I no longer have the Play/Pause problem.
Thanks - Anj
Click to expand...
Click to collapse
that works but EVERY time i hit the play/pause button on my mw600 the prompt comes up, freaking annoying, can we have the app that just does the play pause, i dont wnat it to come up asking me what to play pause.

Sorry to revive but i've got an in-car bluetooth and the AVRCP doesn't seem to work with ICS either.. the first time I click play and the first time I click "next track" on the car after the phone connects, the phone will respond correctly, but will not respond to any subsequent buttons until I press the power button on my phone... It's almost like ICS is sitting on all the commands sent to it's AVRCP like a stack, and when I power the phone (either on or into standby), the next click is executed (without any clicks on the car at the time)..
eg: if I hit "Next" twice and "Rew" once on my car, then every time I tap the power button (between on and sleep), it would execute Next, Next and Rew in that order. I have a lock pattern on my phone too, not sure if that's hampering the AVRCP commands either... only way to get out of this is to turn the BT off on the GNEX then on again.. but it does the same thing after the first succesful AVRCP command again.

those with skype issues...

have anyone tried the altered skype in this thread. i know this one worked on a tablet i had that the regular one didnt. http://forum.xda-developers.com/showthread.php?t=1148708

inthepit said:
have anyone tried the altered skype in this thread. i know this one worked on a tablet i had that the regular one didnt. http://forum.xda-developers.com/showthread.php?t=1148708
Click to expand...
Click to collapse
I may be mistaken but I believe the issue is consistent with apps that use WiFi to make use of their service, instead of Data. The audio lags over the wifi connection. So it's not the app itself, as the issue persists across many apps ie. skype, fongo/dell voice/magic jack.

pm2gonzales said:
I may be mistaken but I believe the issue is consistent with apps that use WiFi to make use of their service, instead of Data. The audio lags over the wifi connection. So it's not the app itself, as the issue persists across many apps ie. skype, fongo/dell voice/magic jack.
Click to expand...
Click to collapse
I'm not entirely sure myself but its definitely not a Skype issue, its some sort of general audio issue and using Skype just seems to be the easiest way to reproduce it. Adam77 mentioned he thinks he knows whats up with it so hopefully we will see a code patch that can be applied to all affected ROMs soon.

yes its a genral audio problem as also the video camera can't record sound as well as the sound recorder. its a general bug in the sound.

bobbinthreadbare said:
I'm not entirely sure myself but its definitely not a Skype issue, its some sort of general audio issue and using Skype just seems to be the easiest way to reproduce it. Adam77 mentioned he thinks he knows whats up with it so hopefully we will see a code patch that can be applied to all affected ROMs soon.
Click to expand...
Click to collapse
No, the problem is when mic audio is routed to userspace, playback becomes distorted. You don't need Skype to reproduce it -- start music playing, then open Sound Recorder. Start recording. Music will stop. While still recording, resume playing via the notification bar. Ugly ugly noises come out.

Watch effecting volume when playing music through bluetooth

I've had the Moto 360 for 5 days now and love it. There is one bug I have noticed and wanted to see if others are having the same issue. When I am listening to music through bluetooth in my car and have the watch connected it occasionally turns the phone volume down to a very low volume. I notice this happen almost everytime I start navigation. Anyone else experiencing the same issue?
I'm using the Moto 360 with the HTC One M8.

I just get choppy volume in that situation. There is a Bluetooth bug somewhere with the moto 360.

ttown said:
I've had the Moto 360 for 5 days now and love it. There is one bug I have noticed and wanted to see if others are having the same issue. When I am listening to music through bluetooth in my car and have the watch connected it occasionally turns the phone volume down to a very low volume. I notice this happen almost everytime I start navigation. Anyone else experiencing the same issue?
I'm using the Moto 360 with the HTC One M8.
Click to expand...
Click to collapse
Ahhhh. I thought I was going mad. I just got a new Sony z3. Been blaming my phone all along.
That makes sense now. So it's the watch that's causing the volume to randomly decrease the volume to its lowest. I wasn't running any watch apps at all.
Any solution anyone.?
Sent from my D6653 using XDA Free mobile app

Is it possible that "OK Google" is inadvertently being triggered by background noise?
When I reply to texts via voice it mutes the streaming music volume on the phone (and also in my car), which I like as it increases the accuracy of my voice reply.

vansmack said:
Is it possible that "OK Google" is inadvertently being triggered by background noise?
When I reply to texts via voice it mutes the streaming music volume on the phone (and also in my car), which I like as it increases the accuracy of my voice reply.
Click to expand...
Click to collapse
I don't think this is the issue. I mostly get this the first time navigation voice directions are given. It turns the volume down on the phone and I can't hear music. I then have to turn the volume back up and don't have issues after that.

I have no issues. Nexus 5 connected to my Moto360 and factory head unit (2011 Camaro). I stream Pandora, Google Play, and have spoken notifications.

no issues here either.

ttown said:
I don't think this is the issue. I mostly get this the first time navigation voice directions are given. It turns the volume down on the phone and I can't hear music. I then have to turn the volume back up and don't have issues after that.
Click to expand...
Click to collapse
Ah, I see. This is testable and will do so today.

I use my X with Moto S11 Flex HD bt head set when cutting the grass.
Before the 360, music would get lower on an incoming notification, and I'd hear the notification sound via the headset.
With the 360 On/Connected, I see the music controls on the screen. Now I notice that when the 360's screen lights up(from twisting my wrist), or I get a notification, the music volume drops slightly for a few seconds, then returns to normal. BUT I do not hear the notification sounds via the Headset when this happens.

ttown said:
I don't think this is the issue. I mostly get this the first time navigation voice directions are given. It turns the volume down on the phone and I can't hear music. I then have to turn the volume back up and don't have issues after that.
Click to expand...
Click to collapse
I used navigation while streaming GPMAA and the volume would return to normal on it's own after giving me an audible instructions the entire way home today. Sorry man, I"ll try again tomorrow, but I couldn't recreate it - it might be phone specific.
Nexus 5
Moto 360
BlueTrip BT Audio
Stock Audi BT Phone

I have had this issue for years (nothing to do with Android Wear in my case). It has to do with how an app obeys the audio focus rules. Some apps are more problematic than others. Rdio is extremely problematic while navigating. Google apps seem to be the best. But whenever the audio focus goes all wacky, it will generally go back to normal once the next navigation prompt plays. With Pandora, this often happens when a navigation prompt plays between tracks...the next track will be much lower in volume. At least, until the next audio prompt. Then volume returns to normal. Skipping to the next track also fixes it.

Bluetooth "Play phone audio on watch" not working at all

(It's been mentioned already by several people here but is burried in the 1.4 update discussions. I feel the need to pull this serious problem to the daylight.)
It behaves as follows:
With the Bluetooth "Play phone audio on watch" option OFF everything works fine but like before 1.4 update (no phone call possible from/to the watch).
When I enable "Play phone audio on watch", strange things begin to hapen when I try to use the newly enabled phone call capability.
Call initiated from the watch or answered on the watch results in mute call. Other than that the GUI of the phone and the watch behaves like the phone call is connected and running. The problem of not working proximity sensor (http://forum.xda-developers.com/showthread.php?t=3330372) also applies here.
Call answered conventionally on the phone results in several seconds mute call (very annoying, making all the "Play phone audio on watch" unusable in practice), after that everything is ok (like in the scenario 1 - "Play phone audio on watch" OFF).
So, it seems I have a problem with sound streaming between my phone and watch. The problem of Shazam not working (http://forum.xda-developers.com/showthread.php?t=3258367) applies fully (don't know if relevant here). I didn't find any other way to test it. I'm on Slimkat 4.4.4, Samsung Galaxy SII. Fresh factory reset after 1.4 sideloaded update.
Microphone is working (Google voice search tested).
Speaker is working (Ringtones are playing)
Please help with further troubleshooting.

This update, to say the least, is very buggy. I have the same issue you do with calls making the phone capabilities nearly useless.
I have factory reset a few times. I think the OS is the culprit. Its putting the watch too far to sleep (if such a thing is possible).
I have hesitation on my watch faces (some more than others) and my bluetooth will randomly drop then reconnect.

nalott said:
Call initiated from the watch or answered on the watch results in mute call.
Click to expand...
Click to collapse
I haven't had this problem so far. Maybe it's related to the Android version running on the phone. I'm using Android 6.0 (HTC One M8 / Google Play Edition).
In case more users confirm this issue, I think it's a good idea to make a report in the AOSP issue tracker:
https://code.google.com/p/android/issues/list
I've done that for the proximity sensor issue.

I can confirm Shazam not working for me with MEC23L.