So I have a weird problem with two different sets of head phones. One came with my S3 when I bought it originally that has two volume buttons and a third button plus a mic. The other set that I tried is just a random black pair I bought somewhere that only has one control button and no mic. I know for a fact neither set are "designed for iphone".
The problem I'm having is with my OPO while using PowerAmp. If the screen is on then the push button controls for play/pause/prev track/next track all work perfectly with one/two/three button pushes. But as soon as the screen is off the control button won't do anything really but turn the volume up on the music. Sometimes the play/pause control will work as it should with the screen off but only about 20% of the time. And as soon as I turn the screen on where I am on the lock screen, in app or in a different app the controls work perfect.
I never had this problem with either set of headphones in Poweramp or any other music player on my S3.
Any idea what would cause this or how to fix it? I ordered a set of 1+ silver ear buds for black friday to see if that fixes the problem or not.
bump, anyone?
Related
Firstly - hello all! What a great forum, I've gone from knowing nothing about Windows Mobile to having a fully customised Raphael in about 48 hours!
But: I have a set of Motorola S9 Bluetooth headphones which work excellently (although I haven't yet made or received a call using them). I also have a Sony a2dp Bluetooth headunit which also works excellently.
However .... As a matter of course I use the one touch power button to lock/standby, and when I press play/pause on either bluetooth device it automatically unlocks the phone.
When I'm driving this isn't such an issue as I will be ordering a Brodit Car Cradle very soon. But when I have the handset in my pocket using the S9 having it unlocked is a recipe for unwanted screen presses. I use the Touch Media Player (I know it's not the best but it seems to work OK for what I want) and the handset switches to the Music screen automatically (as well as unlocking) whenever I press play/pause. So theoretically it's pretty likely that it's only the media player that will get messed with, but you never know...
So my question is: Is there any way of stopping it from unlocking like this without introducing extra locking/unlocking complications?
hi
im using the Jabra BT3030, that uses A2DP aswel, on my touch pro and my phone stays locked when i start stop use the voice dailing, changing volume or song.
the phone turns on that is true, are u sure u are using the lock function
to realy lock ure phone u have to press and hold the end call button for 2 seconds(lower right button). if that button is not set to lock u can change that in ure phone settings under settings>long press end key there u can chose lock device
i hope this helps, let me know
WildFire
Yeah, I'm using SonyEricsson HBH-DS980, and for me too the phone only turns on upon play/pause etc., but does not unlock.
Have you guys had any problems with receiving/making call using your headests? I have a problem that after a few minutes into a call my headset disconnects, although BT stays on, and I have to restart the headset to re-acquire BT-lock. And it keeps doing this every few minutes. Highly annoying - renders my headset completely useless for phone calls (luckily it still rocks for listening to music).
Mine does the same. Both with my HBH-DS970 and with my HTC BT headphones. I tried the long-press end key lock which works, but prevents me from changing tracks using the HTC headset, yet the volume control works. Weird huh?
I haven't tried the long end key press to lock the device. But thats because I use that for switching on vibrate mode.
Anyone got any other suggestions?
I'm using the motorola S9 too, and my TP doesn't unlock when I press play/pause.
Note that I've installed Answerkeydisabler and Advanced Config Tool and played with locking/screen-off, and may have activate some options leading to this behaviour...
ross
u can always set the long key to "always display the quick list" so u can chose to lock ure device or set ure vibrate ringer
also u can just use the volume keys to change ure ringer to vibrate/sound to
I am now using the quick list so it sort of solves the problem. But it still seems a little awkward compared to just pressing the power button once and not having the a2dp commands reactivating it.
Are we saying that this cant be done?
Any ideas?
I have a Motorola S305 and I'm using Mortplayer to listen to audiobooks/podcasts.
In the menu options, you can set the Rewind/FFW/Stop buttons on the headset to control the podcast.
But no matter what button I assign to Rewind, it just doesn't work. What is the deal?
I can set all three buttons to FFW and all three work fine.
But it seems there's something wrong with Rewind. Setting any of the three buttons to Rewind in the app means that the button basically dies and is unresponsive (until I set it to do something else).
This worked fine on my Nexus One, so it's not the headphones (especially since all 3 buttons work fine when used for other functions).
Admittedly, it was with an older version of Mortplayer, so perhaps this is a bug with the newest version?
Has anyone else run into this issue with the Sensation?
I listen to music on my phone all the time and I really like how the stock music player responds to the headphone control. I'm using my old HTC headphones which have three buttons, and the default settings (actually there's no settings in the stock player for headphone control) is that the two buttons on the sides serve as volume button and the middle button serve as play/pause/next button. I love this because I don't need to reach in my pocket to change the volume or song and it kinda saves the hardware keys.
But I noticed a problem later: All three buttons work when the screen is on or just turned off (either manually or automatically), but the center button (play/pause/next) stops working after a while. The volume buttons are fine. I also noticed that if I double clicked to change the song, the music would just stop, but if I just turned on the screen, it started playing again (next song). So this is what I thought: the buttons sent the signal, the music player got it, but it couldn't do anything because the phone was "sleeping" after being turned off for a while.
Today I found this little app called "Headset Button Controller", which is basically a settings app for headphone control. It solved the problem perfectly! It probably works its way around the phone's power management. Idk. Here is the link to market: [damn I can't post it, you need to search it on your own] I'm on stock 2.3.5 and have used the stock Samsung headphones to re-show the problem and found out it's not my HTC headphones' fault. I believe there're more people in the same situation and thank god I finally find a way to solve it! Happy sharing!
Thanks would give this a try. Double click never work for me
Sent from my SAMSUNG-SGH-I727 using xda premium
Good find. I have run across more than a few with this issue
Sent from my SAMSUNG-SGH-I727 using XDA App
Stock Blaze that I use to listen to music on while walking my dog every day using headphones. But I've noticed an odd problem- sometimes when I plug in my headphones and hit the middle button on the cord (it's a headset with a mic and three buttons marked Play/Pause, FF and Rew) the music app starts up and plays whatever I was last listening to but the media volume has gone to zero. And sometimes while I'm listening the media volume will drop to zero for no reason, with no buttons being touched- the app is still playing but I have to turn up the volume.
I should add that the headset I'm using seems to work differently with the Blaze than it did with my previous phone, a T-Mobile G2. With the G2 the Play/Pause button worked as advertised, and the FF and Rew buttons on either side worked as next or previous track. On the Blaze the Play/Pause seems to work as advertised as well, but the FF and Rew buttons work as media volume up and down- sometimes- sometimes none of the buttons do anything until I close and reopen the music app.
Anyone else having similar problems or got any ideas? I use my phone to listen to music while waking the dog for about an hour every day and seem to have problems like this at least every other day- it's becoming a royal pain!
I'm having this same problem with my tablet, it please let me know when you find a fix
Sent from my GT-P6800 using xda premium
I bought a Bluetooth controller https://www.amazon.ca/images/I/51rPNr9NjcL._AC_SL1000_.jpg to use on my bicycle so I don't need to unlock the phone and mess with the screen to skip songs, and it works fine when using a regular headset in the 3.5mm port. But when I use my Dragonfly USB DAC all that works is volume up/down and the play/pause button. The previous track button acts like volume up, and the next track buttons acts like volume down.
It works fine on my Galaxy S8. And this is not an issue with a certain app because I tested it on many music apps. It seems to be the phone itself.
Can anyone think of why it would be doing this, or any way to remedy the issue? Or is this just an unfixable bug?
evil-doer said:
I bought a Bluetooth controller https://www.amazon.ca/images/I/51rPNr9NjcL._AC_SL1000_.jpg to use on my bicycle so I don't need to unlock the phone and mess with the screen to skip songs, and it works fine when using a regular headset in the 3.5mm port. But when I use my Dragonfly USB DAC all that works is volume up/down and the play/pause button. The previous track button acts like volume up, and the next track buttons acts like volume down.
It works fine on my Galaxy S8. And this is not an issue with a certain app because I tested it on many music apps. It seems to be the phone itself.
Can anyone think of why it would be doing this, or any way to remedy the issue? Or is this just an unfixable bug?
Click to expand...
Click to collapse
Your is a rare specific use which i don't think xiaomi did ever test their phone in this condition, the only way to get it fixed is trying to report using their channels (feedback app, mi community etc..), or you can try switching to custom roms to see if it works fine there