yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] MashineGun:
Yep would be great to have long press on prev/next on headset to control volume ;) thank you for great work looks very good
[Xposed Framework Modules] thekoRngear:
Thanks man for this handy module. However I cannot make my S3's capacitive Menu and/or Back buttons work to pause the music. It works flawlessly with other buttons. Another thing is if I made the home button to play/pause the music I just cannot use the Home button to wake the phone up whether the headphones are plugged in or not and in any other state.
[Xposed Framework Modules] Inuyashaxp:
Poorly it don't work on my HTC Desire S with Android 4.03

By pressing the volume up and down button still the volume change only.

Framework installed, module activated in framework and restarted twice. Don't work :(
[Xposed Framework Modules] czechu01:
Hey man! Nice work! Works on stock HTC One music app. But unfortunately doesn't work with spotify. Is it possible to do something with it? Also because One doesn't have camera button or physical menu/home/back button would it be possible to set any activity for a soft key? Another thing - would be really nice to be able to set the default music player to work with your module.

Anyways, thank you for your work!

Wysłane z mojego HTC One przy użyciu Tapatalka

---------- Post added at 01:55 PM ---------- Previous post was at 01:52 PM ----------

Did you set the key hold time for each button? You have to hold volume button in order to make any change.

Wysłane z mojego HTC One przy użyciu Tapatalka
[Xposed Framework Modules] Inuyashaxp:
Hey, yes I did it. I use Poweramp, does it depends on the music app?
[Xposed Framework Modules] esgie:
Thank u for this useful mod.

In my opinion, it'd be nice to add an option, which is not directly related to media control, but surely concerns the extended usability of the hardware buttons: the possibility of controlling the pointer in the text fields with volume buttons just, like they were keyboard arrows (left/right or right/left, depending on i.e. user choice / hardware buttons placement / current screen rotation... ).

Similiar mod has been included in Xblast Tools (btw it is the only Xblast mod which I really use, would be great if I can finally uninstall whole Xblast)...

That one makes writing much lot easier, believe me, as you do not have to aim with your finger at 1mm gap between letters if you find out that you made a mistake, which - at least for me - is the one of the most annoying issues of touch screens (and on-screen keyboard apps...) in general.

I find it a good idea, as the mods related to a greater utilization of hardware buttons would be aggregated in one xposed module, then.

Would be glad if you at least consider above idea ;]

Thx for a great job.
[Xposed Framework Modules] Xspeed:
I'm afraid that's not possible, as this mod is only sending the media signals and it's up to the phone how to handle them.

Yeah, I really don't have a <4.0 phone, but this time I've thoroughly compared the APIs and it seems I've underestimated the differences. Next version will surely work, but it's gonna take a while.

I don't really get what you meant by "sound start @ 20%", but about the rest... this mod is supposed to control the media only. Sorry.

Yeah, it's totally going to be added. But, as I see in the Android API, headsets have only one button?

Headsets can have multiple buttons? It that headset USB or what?

Well, those buttons were requested for phones that didn't have a camera key. The keys are working ONLY when they are physical (as the title suggests). As for the home key, my phone don't have a physical home key, so I'll need to investigate more thoroughly to find the cause.

It seems that it does depend on the way the app handles the media signals. If it doesn't at all, then it won't work.

Maybe I could start another mod for handling physical buttons for other purposes, yes, but this mod is supposed to be media control only. Sorry.
[Xposed Framework Modules] killoid:
no problem.take your time,at least you are supporting GB users.that's enough! :)

p.s. i think this will help you a bit.

https://github.com/liudongmiao/XposedGBModule
[Xposed Framework Modules] Kalaidos:
Gravitybox does have this feature too but somehow it didnt work on my LG G2..

Your mod works great and im happy, thanks :good:
[Xposed Framework Modules] ahm.elghazaly:
Will it be possible to add pressing both volume up and down to simulate play/pause? I have an HTC one so no keys at all. Thanks
[Xposed Framework Modules] Blizzard22:
If I disable the headset controls for Poweramp BeyondPod starts and works great with your mod.

But of course I use my headset controls for Poweramp =/.

Well at least I have found an workaround for this problem.
[Xposed Framework Modules] lesscro:
hi, thx for answer... anyway i m talking about when you plugged headset sound is reset to a specific level... then you can manage to start volume to 20,30,40,50,60,70,80,90 or 100... really usefull tweaks...

cheers
[Xposed Framework Modules] Xspeed:
I'm going to add the power button instead as a possible button.

So, when the music starts the volume is set to a specified level? I think I can do that.
[Xposed Framework Modules] ahrion:
Please add search button instead of camera..
[Xposed Framework Modules] Xspeed:
I'll look into the matter ;)

Sounds like a more serious issue. Could you post your Xposed logs? Refer to the first post for a how-to.
[Xposed Framework Modules] JayjohnX:
First feedback

Have a first result, not all I mentioned, but something.

After you had the idea to watch the logs I took a bit more care when errors are occurring.

I found out that one problem is when I am having my phone in the pocket/upside down (the phone is realizing it using the sensors), and then trying to switch the screen on by pressing the power button normaly it should switch on and show the following behaviour in the log:

PBMC: Processing key POWER down
PBMC: Creating delay event (1) POWER down
PBMC: Processing key POWER up
PBMC: Creating delay event (1) POWER up
PBMC: Delay elapsed POWER up
PBMC: Sending simulated key POWER down
PBMC: Sending simulated key POWER up

But it does not. The screens stays off. If I would press the home button instead, the screen switches on like it should. The reason is that the "Sending simulated key POWER up" is missing. I tried and logged two things.

First, pressing the power button when its coming out of the pocket (doesn't matter what time after I am taking it out of the pocket), screen stays off, then pressing the home button. The log shows a strange behaviour. Instead of simulating the power button it simulates the home button as soon I press the home button:

PBMC: Processing key POWER down
PBMC: Creating delay event (1) POWER down
PBMC: Processing key POWER up
PBMC: Creating delay event (1) POWER up
PBMC: Delay elapsed POWER up
PBMC: Sending simulated key HOME down
PBMC: Sending simulated key HOME up

Second, after pressing the power button the screen stays off and I pressed the power button a second time. The log shows for the first pressing only the simulation of the power down event and after pressing the power button a second time (without the delay elapsing of the power up event) the simulation of the power up event occurs:

PBMC: Processing key POWER down
PBMC: Creating delay event (1) POWER down
PBMC: Processing key POWER up
PBMC: Creating delay event (1) POWER up
PBMC: Delay elapsed POWER up
PBMC: Sending simulated key POWER down
PBMC: Processing key POWER down
PBMC: Creating delay event (1) POWER down
PBMC: Processing key POWER up
PBMC: Creating delay event (1) POWER up
PBMC: Sending simulated key POWER up
PBMC: Delay elapsed POWER up
PBMC: Sending simulated key POWER down
PBMC: Sending simulated key POWER up

Edit:

ok, just had the problem also after not touching it for a while - but this time it was not lying upside down on the table. So anyhow it happened because I haven't used it for a while...
[Xposed Framework Modules] JayjohnX:
Hi,

now the module "died"... But I haven't got any new entry in the log... Now the power button works normal again ;)

When I reactivate it by going into a key mapping setting and opening (just opening, nothing more) e.g. the mapping of the double press of the power button and then closing the app, the log creates the entry:

PBMC: Key mappings: 1
PBMC: Found 5 media players

Then it is working again - and I have again the problem with the power button
[Xposed Framework Modules] livinitwarrior:
Any way in a future update you could have pre-mapped buttons? I'd love to use the home button and recents button
[Xposed Framework Modules] Xspeed:
Pre-mapped? I don't think I understand.

All buttons should work after activating the module.
[Xposed Framework Modules] livinitwarrior:
My home button, recent button, and back button are not working
[Xposed Framework Modules] Xspeed:
If you just have installed PBMC you need to reboot first, then you will be able to use them.
[Xposed Framework Modules] livinitwarrior:
Tried rebooting multiple times. It works on volume and power, but not these three. Motorola Droid Maxx?

Maybe in an update you can have those three pre mapped and have options that way.
[Xposed Framework Modules] Xspeed:
Mate, Droid Maxx has soft back, menu and recents keys! Only physical (aka. hardware) buttons can be used! ;)

I mean, you can't use them while the screen is off, so where's the point?
[Xposed Framework Modules] livinitwarrior:
Oooh... Sad day. Well that works then lol
[Xposed Framework Modules] agiantbluewhale:
Volume button not disabled.

I am on an LG G3, trying to set volume up hold to skip to next track, and volume down hold to previous track. This works, however, the volume also increases to the max when holding volume up, and goes to silent when holding volume down. Am I doing something wrong? I just set 'hold' functions for each button.

Log:

Pastebin link is /iv41HS05 (unable to post links as this is my first post?)
[Xposed Framework Modules] Xspeed:
Thanks for the report!

Interesting, the log is clear as day, but since your device still changes volume, there must be something I overlooked in the code.

Currently my phone is being fixed, but as soon as I will have it back, I'm gonna run some tests and hopefully fix it.

Also, that's when 2.8 is coming out ;)
[Xposed Framework Modules] skepticmisfit:
any chance the vibration when triggering an action can be disabled?
[Xposed Framework Modules] Xspeed:
Come on people, read the FAQ first, lol.
[Xposed Framework Modules] skepticmisfit:
lol I'm sorry, we all derp sometimes
[Xposed Framework Modules] _mysiak_:
Could you please implement additional action - jump to previous/next playlist (directory)? I often skip whole directory in Poweramp and this would be very nice without the need to unlock the phone and doing it from Poweramp :)

Thanks!
[Xposed Framework Modules] Xspeed:
I looked at the official PowerAMP API and it seems there is no way of switching playlists using it.

If you have found an app that can switch playlists in PowerAMP, then tell me.

Using the opportunity, I wanted to explain why aren't there any updates lately.

So, my phone STILL isn't fixed (motherboard dead, blah blah), and I'm stuck with good old SE K850i :eek:

But as soon as it comes back I am gonna resume work at full speed~!

Stay tuned!
[Xposed Framework Modules] _mysiak_:
Thank you for checking. I've dropped an email to PowerAmp developer, will let you know once they add this feature to their API.

Edit: found this information in PowerAmp forum:

It is possible to issue next/prev << >> track or next/prev category <<< >>> commands (this is actually jump to another playlist/directory). I am not really familiar with the API code, but it might be this "id.prev_in_cat" and "id.next_in_cat"
[Xposed Framework Modules] Deviling Master:
Hello XspeedPL,

First, many thanks to you for this module, is what I looked for a long time, and now I explain you why: I configured the next/previous track and play actions on the volume bar (I have a Nexus 5) so when I use Spotify while driving my car, I can change track w/o looking at the display (safety reasons).

I have now a question to you.

When the phone is in my pocket, it happens that the play or next media action is accidentally triggered, so the media player app starts playing the last track I was listening in the previous session.

Is there a way to trigger the actions ONLY if the media player (Spotify) is already opened?

Thanks again for your work

Regards
[Xposed Framework Modules] Xspeed:
Sure mate, first you need (if you haven't done so already) set Spotify as the signal receiver. Then you can set 'running only' in signal sending preference.
[Xposed Framework Modules] Deviling Master:
Thanks for your help, this is very helpful.
[Xposed Framework Modules] tuffluck:
So can I use this with headphones that have 3 buttons that are made specifically (and only) for iphones? I read a couple of searches stating you can't, but others suggested you can at least set the vol +/- to work.
[Xposed Framework Modules] Xspeed:
It won't hurt to try. Install and enable the module, reboot the device, and then try mapping the buttons (only after a full module activation more buttons are able to be mapped).

Good luck ;)
[Xposed Framework Modules] _mysiak_:
Hi, me again :)

Additionally to this (Edit: found this information in PowerAmp forum:

It is possible to issue next/prev << >> track or next/prev category <<< >>> commands (this is actually jump to another playlist/directory). I am not really familiar with the API code, but it might be this "id.prev_in_cat" and "id.next_in_cat")

Action Box can control jump to next/previous directory . Maybe you could just add an action "custom shortcut" where we could choose any shortcut already available in system/other apps or created by Tasker etc. Direct control of music player via shortcuts instead of simulated headset key presses might be more responsive as well. Just an idea.. :)
[Xposed Framework Modules] Xspeed:
Thanks for all this info, I think I might be able to implement that as a feature ;)

My SP should be back next week (finally...), and as I've said before, it's going to be CODING TIME.
[Xposed Framework Modules] Rom:
Take time to me and others translaters to complete futur update please :P

(I anticipate :D)
[Xposed Framework Modules] espinal123:
Does n't work for me

i just installed it, I have the original android 4.4.2, It doesn't work, I'm new here, do I have to install a special room?
[Xposed Framework Modules] Xspeed:
You said you just installed it, but did you reboot? :p

If yes, send me your logs (instructions in first post).
[Xposed Framework Modules] _mysiak_:
[MENTION=6208136]espinal123[/MENTION] - if you are new, also question about working root and installed Xposed framework comes into the mind.. :)
[Xposed Framework Modules] espinal123:
yes, I have read something about it, now I know I need to root the cellphone and install xposed thing. Any tutorial would be aprecciated. Thanks
[Xposed Framework Modules] _mysiak_:
Please follow appropriate threads - about rooting you need to check your phone model section, Xposed has dedicated forum as well.
[Xposed Framework Modules] espinal123:
I just rooted my s4, and it worked perfectly.

Thanks
[Xposed Framework Modules] Xspeed:
2.8

Because of today's special occasion, I wanted to push an update.

There isn't actually anything big yet, but I can tell that app & shortcut actions are under development ;)

- Increased responsiveness
- Added an option to boost free memory before play signals
- Added update reboot reminder
- Allowed soft keys to be used (for lulz rly)
- Little visual details improved

Happy Holidays!
[Xposed Framework Modules] Rom:
Hey thanks for this update, i will update french translation in some hours (its 00H33 clock in France..), and i wait for futurs major updates :D :good:

Happy holidays too ;)
[Xposed Framework Modules] Rom:
[MENTION=5292510]XspeedPL[/MENTION]

I have finish to update the french translation :) :good:
[Xposed Framework Modules] Shadow_Reaper:
Hi buddy I have a really annoying issue

Hi, as the title says, I have a really annoying issue. I'm not gonna enter in details as I already filed a bug report.

In a few words the problem is this:

I mapped the volume down key to go back to the previous song when you hold it down for a moment. Instead of this it just restarts the current song, and MAYBE after several attempts it may actually go back to the previous song.

Wanam allows me to go back to the previous song with no problems at all. I obviously disabled Wanam in order to avoid conflicts with PBMC.

Here's my bug report: http://xdaforums.com/devdb/project/?id=5889#bugReporter

Hope you can fix this soon.

Merry Christmas
[Xposed Framework Modules] blackshadow0990:
Hi developers, I have a questions

Hi, first of all I want to excuse to you if my question has been already made but read about 40 pages is very very long, anyway, my question is: drains this app lot of battery? because I have found many apps similar but all suck lot of battery, thanks in advance.
[Xposed Framework Modules] _mysiak_:
I believe that standard behavior is first "back" press = jump to beginning of the song and another "back" jump to previous song. Only if you press "back" during first few seconds of the song it jumps back to previous track. Otherwise it just plays current song from the start. The same behavior was present in Rockbox and other players with limited number of physical buttons, so I guess that nothing to fix here :)
[Xposed Framework Modules] Shadow_Reaper:
Hi, I understand what you're saying but couldn't at least be an option to choose the preferred behavior? I mean, this module has everything I need, the only problem is this.

The user should be able to choose the expected behaviour.
[Xposed Framework Modules] Xspeed:
I believe that this module doesn't drain any battery at all. It only activates when you press a set button, sends a chosen signal and deactivates itself ;)

Sure, I could add an ability to send a double "previous media" signal. Sadly this is all I can do , because the implementation of the rewind button varies from player to player.

You can find more insightful info about this matter here: https://ux.stackexchange.com/questions/64118/differing-behaviours-of-the-previous-song-button
[Xposed Framework Modules] Shadow_Reaper:
I see. I don't want to annoy you but, could you implement the double signal function? I think it should be an option and the user should decide which behaviour fit it's own needs
[Xposed Framework Modules] Xspeed:
No problem, it's already marked as a planned feature now ;)
[Xposed Framework Modules] Shadow_Reaper:
Thank you very much buddy. I wish I could help somehow.
[Xposed Framework Modules] Xspeed:
You already help by giving feedback and posting ideas for features ;)
[Xposed Framework Modules] bluenumb:
Dear developer, first of all thank you for your work. I've a problem, maybe already found by someone... When I hold a volume key to change a track, sometimes, in special if I'm not so quick, after the change also the volume start to change. Is not a way to avoid this problem? I'm using an HTC One E8 dual sim. Thank you, Valerio.
[Xposed Framework Modules] Xspeed:
First things first, Xposed logs are needed for me to analyze if the module is working correctly (instructions are in the first post).

Also, this happens when you just hold a mapped key? So like, you hold it, a next media signal is sent and then the volume changes?

Do you have some kind of functionality on your phone to gradually change the volume when holding the button?
[Xposed Framework Modules] bluenumb:
First of all, I just activated the log, how I can send you this log?

It happens only when the screen is On, in this case first the media signal next-previous is sent and then volume start to change if I continue to hold the button, if the screen is Off the next-previous media signal is sent and then nothing happen.

No, I don't have functionality to gradually change the volume when holding the button.
[Xposed Framework Modules] fabioffs:
Hi, I am using this module + Xposed back-ported to Gingerbread and is working perfectly.

Many thanks for your great work!
[Xposed Framework Modules] Xspeed:
Read the first post:

How to report problems efficiently?
- Enable the 'Debug log' in PBMC settings
- Use PBMC functions that don't work as intended
- Export the logs from Xposed app and put them on PasteBin
- Post here/send me the link along with more information about your device

There's an option to export the logs in the Xposed Installer.

Glad it still works for Gingerbread, as I have no devices to test it on ^^
[Xposed Framework Modules] Xspeed:
I think that the repeated VOLUME UP and VOLUME DOWN events are the source of problems. If I am right, I can easily add an option that will fix them ;)

On a side note, please learn to use PasteBin. Don't spam logs in the post.
[Xposed Framework Modules] bluenumb:
Dear XspeedPL, sorry. I've to learn a lot of things about the use of this way of communication... Sorry for the spam, yesterday I had the sensation about something wrong... The log was very very long...

Anyway, Thank you for the effort you are putting in help me and in develop this very useful module!
[Xposed Framework Modules] neonixxx:
Just wanted to say thanks for this great module. I'm surprised things like this aren't a more popular feature. I think actions without turning the screen on are indispensable.

I submitted a feature request, but I'm not sure how or if XDA notifies OPs of things posted there, so I just wanted to drop a line to say so just in case. :p

My feature request is for a torch toggle, which I know if beyond the scope of this module, but it would honestly make it a perfect solution, as the only other modules for screen-off button actions have bugs or are limited. And non-Xposed solutions are crap. Hopefully you can consider it, I have a donation on it if you need a little incentive. ;)
[Xposed Framework Modules] Xspeed:
No problem, we all learn something new everyday ;)

As you can see in my response, shortcut action feature may be just for you. It was requested since long ago, and now it's finished.

And as for the "scope" of the module, I've been lately considering a name change from "Physical Button Music Control" to just "Physical Button Control" and going all out on all sorts of functions and features, but I don't know.

The possibilities are limited, since most devices have just 3 buttons. I've been thinking that I could do the change once I implement an ablity to use button combinations and sequences.

But that's gonna need yet ANOTHER ~80% code rewrite and A LOT of time.

And about the '2.9' itself: it's DONE! Right now I am waiting for translators to finish their work, and as soon as possible, one of most awesome updates will be out!

Stay tuned! ;)
[Xposed Framework Modules] neonixxx:
Ah, I hadn't seen that post. That is awesome to hear! :D

If you want an extra opinion, I think renaming and going all out is a good idea if you've the time to do it. Combinations would be cool, but I honestly don't think the possibilities are all that limited since you have enabled a lot of different press options for each button already (kudos for that, by the way). Then again, I wonder what sort of functions you have in mind. I can't think of too many things beyond shortcut and app launching. I guess there are plenty of toggles people may want (ringer mode comes to mind), but with shortcut actions, a lot of toggles will be achievable by linking to Gravitybox's shortcuts. Well that's my 2 cents.

Anyway, you've got me really excited for the new version! Any chance an impatient guy can get a pre-release package if he doesn't need translations? ;P
[Xposed Framework Modules] Rom:
[MENTION=5292510]XspeedPL[/MENTION]

French translation is fully updated :good:

Merry Christmas to everyone :)