I'm just curious if anyone else is seeing this problem (cut/paste from my report on MOTODEV.com):
The Bluetooth AVRCP (Audio/Video Remote Control Protocol) is broken on the Droid4, at least with respect to the stock Play Music application. Both firmware versions .215 and .219 are affected.
When the display is off, remote control commands from headsets are sometimes not being correctly processed by this device. I'm seeing this with both of my tested headsets, a Sony MW600 and Scala Rider G4. The failure is somewhat intermittent, but occurs most of the time. If the failure doesn't occur immediately after turning the display off and using music controls on a headset, it will certainly occur if you try turning the screen on/off a few times and playing with the headset music controls for a minute (you don't need to 'mash controls", just behave as a normal user would).
During the failure mode, the log is showing that events are being received via AVRCP, it's simply not acting upon them, e.g. pressing the headset play button has no effect but results in the following (while music is playing, with the display off).
05-08 01:47:01.256 4317 4317 I MediaPlaybackService: play()
Click to expand...
Click to collapse
And whether you're seeing it or not seeing, let me know what ROM you're running. I'm ready to flash something new just over this issue.
Related
Anyone have any info on this?
My old Orbit2 used to continue to play music through HTC Audio Player as well as Windows Media Player however now if I tap the power button to put device into sleep mode the music pauses.
Anyone have any suggestions/fixes for this?
Any help would be appreciated.
Not sure of Orbit as I do not own one.
But all the WinMo device I have are behaving the way you describe in TD2.
There is apps inside or 3rd party which you can just switch the display off (not the power off), So the device is not off but the display off can save you a lot of battery.
Yeah, I got an app touchlock pro that turns the display off.
Just a bit annoying that I had the problem on the orbit 1, was fixed on the orbit 2 and now the problem is back on the topaz.
Still its a minor thing I suppose - Rest of the functionality seems great so far
Just a little update on this if anyone was interested.
Upon further experimentation I have discovered that i using my bluetooth headset for music playback i can now lock the phone by holding down the end call key and then press the power button to turn the display off whilst maintaing music playback.
Not sure if this works when using a wired headset but it did not seem to work just playing out of the speaker minus the headset.
My D2 continues to play music with the screen off using both coreplayer and windows media player.
EDIT: I thought I would double check - strange, today it stops the music! I know for a fact the other night I was listening to music and the screen was (almost) definitely off. I will investigate further.
EDIT2: I thought further and I know it was playing music with the screen off. I know this because I was happy that the volume buttons still worked.
I just did some checking.
When the headphones are plugged in the music continues playing when you turn off the screen and the volume buttons continue to adjust the volume.
Without the headphones plugged in the music stops when you turn off the screen.
Thanks for that, not actually used the wired headset before but what you have said is correct. it is a shame the same method for bluetooth stereo wasnt implemented or perhaps its just my bluetooth headset. looks like might have to get the wired headset out for a bit.
Hey, is there a way to skip songs with the headset we got?
i never noticed this until today.... how annoying, i just finished loading up my new microSD.
If anyone has a fix for this, please post
Thanks!
Mine appears to be fixed now when using my bluetooth headset or the wired headset But still stops if playing through the phone speaker.
I use a Jabra BT8010 bluetooth headset, and the music continues to play after pressing the power button. The music is shut off if playing through the phones speaker....this is the same as my previous phone (htc TYTN II)
I'm wondering if anyone else is having strange behavior either with Bluetooth audio or headphones. The phone is AT&T stock rooted 1.26.502.10 with unlocked bootloader and CWM. Here's a brief summary of what I am seeing:
When listening to audio books using headphone (Audio Book Player app) when I place the phone in my pocket in a locked state, it will wake up and dial the last number. It seems like there is a pocket sensor that is tripped and initiates a call. This can repeat itself several times. The dialing attempt tends to terminate itself if I don't intervene in time. I have not been able to reliably repeat the behavior in a predictable manner.
For bluetooth audio music (paired with an up-to-latest Ford Sync system) there is inconsistent behavior when using Google Play Music. Sometimes everything is fine. Sometimes on-screen (car side) audio controls will not work. Sometimes it will skip to the next song after possibly 10 seconds on the current song.
This is driving me crazy. If I don't figure it out, I'll throw on a custom ROM this weekend,
Thanks!
I have not had any of those issues so unfortunately I cant be of much help. The one problem I have had is that I have a bluetooth headset that also does media playback, which I always disable when in the car because my car does not do bluetooth and I want the audio to go out the headphone jack. Everytime I disconnect the headset it rechecks the "media" option on the headset and my audio plays from my headset and I have to go back to the bluetooth options and uncheck it. Very annoying.
Looks like it is a hardware issue. I can replicate by turning or wiggling the headphone. Problem appears to be in the headphone jack.
Back to the AT&T store
Sent from my HTC One using Tapatalk 2
I have experienced the song skip as well. I can't successfully recreate it, but it always occurs when I'm on my motorcycle. At first I thought it was the headphone control being depressed, but I have eliminated that. So I think it does have to do with vibration/movement of the phone somehow.
qwen3579 said:
I have experienced the song skip as well. I can't successfully recreate it, but it always occurs when I'm on my motorcycle. At first I thought it was the headphone control being depressed, but I have eliminated that. So I think it does have to do with vibration/movement of the phone somehow.
Click to expand...
Click to collapse
Try putting pressure from various angles on the headphone plug as well as pressing on the case in the corner where the headphone is inserted. Much weirdness ensues in a very repeatable manner.
rootshot said:
Try putting pressure from various angles on the headphone plug as well as pressing on the case in the corner where the headphone is inserted. Much weirdness ensues in a very repeatable manner.
Click to expand...
Click to collapse
Hmmm...nothing happening when I do any of that.
I found that the wind across the microphone is somehow triggering the skip, for me anyways. I use the headphones that came with my One and I simply placed a piece of tape over the microphone. No more song skips.
Very strange as nothing is activating the voice control in the first place.
I've been having a weird bug with my bluetooth
My nexus is stock unrooted. I have the bluetooth paired to multiple devices but I notice it when connected to my Scion xB (2012)
When I get in my car, the phone auto connects and starts playing my music from google play, or my audio book from Smart Audio Book Player. Every once in a while, the phone will be playing the media file but I will get no sound until I tap the volume button on the phone and then it magically works.
Anyone have any ideas?
I have weird problems sometimes where my physical volume keys wont change Bluetooth audio at all.
ill hit volume down, and it will pop up on the screen and ill turn it all the way down, but audio volume doesnt change. Ive had small BT problems on every android phone ive ever owned.
this is one of those things where apple is crapping on us.
I just got a 128 GB OnePlus 3T a few days ago to replace a dead Nexus 6P. So far I'm very happy with the phone (performance, screen, etc, camera is almost as good, blah blah) except one thing.
My bluetooth is completely nuts. Sometimes I will turn it on via Settings or Quick Settings and it will not turn on at all (the slider moves to the right but stays greyed out, then moves back to the left). Other times I am "luckier" and it switches on and begins scanning, and I can see devices in the area. I pair to a speaker dock via NFC or my wireless headphones via tapping on them and the connection is established, you can hear the speakers go "hey something connected".
So that's all fine. But then you start playing music. About 40-60 seconds in it will skip, crackle, or pause the music entirely. Sometimes the device makes its disconnect noise immediately followed by its reconnect noise. At this point pressing 'play' again starts the cycle over again, usually, or sometimes it will just refuse to "talk to" anything any more until you reboot the phone.
The phone came with OOS 3.5.4 out of the box and immediately got an OTA to 4.1.1. I was suspect about the upgrade procedure and sighed and did a full reset and re-flashed the full 4.1.1 image using adb sideload, logged back in, did the barest of minimum updates to the Google apps to make it stop complaining, and then tried music again. More skipping and pausing. My headphones have a volume up/down key on them, pressing that pretty much immediately results in a disconnect.
It's like the AVRCP (command) bluetooth protocol is "fighting" the A2DP audio stream protocol? It doesn't make any sense. This would also explain why my car audio has NEVER worked, because my head unit uses AVRCP to read track names and my headphones and speaker dock don't have any sort of screen to speak of.
I want to love this phone and don't want to pay double for a similar Pixel, but I might just have to return it if it's effectively useless at one of the main things I have a phone for! :crying:
Hmmm...My Bluetooth connection never have that issues. I used Bluetooth headphones and my car head unit. Running oos 4.1.1 as well.
Try dirty flashing your ROM, there might be something wrong with the drivers. Bluetooth commands (volume, pause, voice assistant, skip, etc.) work find on my headset, I don't believe its a compatibility issue.
If that fails, it might be a hardware defect?
I don't have problems with Bluetooth im using sony wireless earphones everyday. Try reformat the phone
Hi!
Android Nougat has heavy issues regarding bluetooth connectivity. If you Google it you will see...
I have the very same Problems like you with my car radio...
This must be finally adressed by Google.
Assassin1985 said:
Hi!
Android Nougat has heavy issues regarding bluetooth connectivity. If you Google it you will see...
I have the very same Problems like you with my car radio...
This must be finally adressed by Google.
Click to expand...
Click to collapse
Huh? Must be an compatability issue between the BT device and your phone. I have 6 active BT devices I use all the time with this phone and my tablet. Car stereo, fitnessband, speakers and inear plugs.
Only issue I sometimes face is the 'stuck in connecting to last used device' where BT needs to be turned off and on again. Wouldn't call it a heavy issue.
bluetooth perfect here. better than my lg g3 that i had previous.
So, more info. If 2.4 GHz WiFi is active in ANY WAY, the bluetooth goes nuts. AVRCP (bidirectional commands) make it worse. Putting the phone in airplane mode to disable the "ambient" wifi location scanning and such, then turning bluetooth on manually and playing some downloaded music, seems to work fine. Switch the WiFi on though (even though my access point is 5 GHz), bam down the toilet. Ugh.
I did a complete reset and flashed OOS 4.1.1 from adb, no improvement. I'm trying the Open Beta 4 right now but I doubt it will be any better.
Did you turn off the scanning feature?
Happens to me like once every 3 days. I usually reboot by then
evilspoons said:
I just got a 128 GB OnePlus 3T a few days ago to replace a dead Nexus 6P. So far I'm very happy with the phone (performance, screen, etc, camera is almost as good, blah blah) except one thing.
My bluetooth is completely nuts. Sometimes I will turn it on via Settings or Quick Settings and it will not turn on at all (the slider moves to the right but stays greyed out, then moves back to the left). Other times I am "luckier" and it switches on and begins scanning, and I can see devices in the area. I pair to a speaker dock via NFC or my wireless headphones via tapping on them and the connection is established, you can hear the speakers go "hey something connected".
So that's all fine. But then you start playing music. About 40-60 seconds in it will skip, crackle, or pause the music entirely. Sometimes the device makes its disconnect noise immediately followed by its reconnect noise. At this point pressing 'play' again starts the cycle over again, usually, or sometimes it will just refuse to "talk to" anything any more until you reboot the phone.
The phone came with OOS 3.5.4 out of the box and immediately got an OTA to 4.1.1. I was suspect about the upgrade procedure and sighed and did a full reset and re-flashed the full 4.1.1 image using adb sideload, logged back in, did the barest of minimum updates to the Google apps to make it stop complaining, and then tried music again. More skipping and pausing. My headphones have a volume up/down key on them, pressing that pretty much immediately results in a disconnect.
It's like the AVRCP (command) bluetooth protocol is "fighting" the A2DP audio stream protocol? It doesn't make any sense. This would also explain why my car audio has NEVER worked, because my head unit uses AVRCP to read track names and my headphones and speaker dock don't have any sort of screen to speak of.
I want to love this phone and don't want to pay double for a similar Pixel, but I might just have to return it if it's effectively useless at one of the main things I have a phone for! :crying:
Click to expand...
Click to collapse
Hi, I have the exact same phone and been having stuttering performance with Bluetooth and Sony MDR-X330BT and worked fine with the 1+ 3. I decided to tell the phone to forget the headphones and start afresh; big mistake headphones kept refusing to pair. I noticed they have the NFC symbol on one of the earpads so I enabled NFC and used app I had downloaded a while back, 'Tap-and-Pair' that did not work either. I did a search today and found a great app that worked - 'NFC Easy Connect' from the Play Store. Now all I need is stable connection from car system which appeared to be tied in with length of screen life before going to sleep but think it may be faulty Twingo as been on the car forum and found others with similar issues but different smartphone to the 1+ 3T. Hope this helps.
My P20 Pro works fine with all bluetooth playback controls, except for "Play". So whenever I pause the music with my headset or in the car, I have to go on the phone to press play again. I thought that it was some power saving feature or some such, but it turns out that pressing "Next track" works perfectly, so it's only the "play" command that it ignores.
However, if I wait too long with pressing next track ("too long" being perhaps one minute) instead of resuming in the app currently in use, it will play from the stock Music app, even though I have never opened it. I also changed the "default music app" to Google Play Music, but this is completely ignored.
Happens with all apps and all bluetooth devices.
Anyone else experience the same issues? Any way to fix this? It's driving my nuts.
Same issue here, all my Bluetooth earphone control not working with poweramp
Sent from my CLT-L29 using Tapatalk
Mine works well with shuttle+(pro/paid version). My only issue is the extremely low volume level and the lack of eq(shuttle+ has built in eq, but the volume is still ****ty low)
Same issue with Spotify.
lobr1 said:
Same issue with Spotify.
Click to expand...
Click to collapse
I've no issue with my Spotify and Bluetooth headphones. Mines not a headset , where the mic is included in case that makes a difference. Also is apx compatible
Sent from my CLT-L09 using Tapatalk
I have the exact same problem, for example with Audible. Think it's the AI trying to conserve battery. Hope it'll learn soon to leave it alone.
Same problem here on the Huawei P20 with both LG and Bose Bluetooth headphones.