yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] haax:
Is it possible to skip tracks on lockscreen only when music is playing? Now when I long press vol+/- it always starts to play next/prev track, even when music player wasnt used for hours
[Xposed Framework Modules] Xspeed:
Just try again.

adb logcat >log.txt

And pastebin the whole thing.

Just make sure to set "Music" to "Music playing" on your chain. It's bound to work.

It checks whenever there is something being played through the music channel.

If it still starts the action, it means there IS something playing in the background.
[Xposed Framework Modules] aLexzkter:
Document exceeds the limit.

It's a 2mb .txt file, for just 20 seconds of logcat. So I attached it to a .zip file here.

I was thinking and how is the led pulse going to work if the phone is plugged in to the usb while debugging?. It's already turned on... Unless I perform a wireless debugging... which I've never done before.

EDIT: Or I use gravitybox to disable charging led.

I'll post here a pastebin from the first and only 'PBMC' entry to the end of the logcat with disabled led on charge, just in case it makes any difference.

http://pastebin.com/Y3K9L7dL
[Xposed Framework Modules] haax:
Thanks, I had previous 4.0 beta and didnt have this option, updated now and works well.

Cheers!
[Xposed Framework Modules] Xspeed:
[MENTION=2976156]aLexzkter[/MENTION] Still nothing there, maybe you're doing something wrong?

Time for another release

- Reduced app permissions
- Fixed flashlight action on Marshmallow
- Added unsafe keys warning
- Minor UI improvements

Basically adding polish to the app itself.

Enjoy!
[Xposed Framework Modules] aLexzkter:
Print debug information to the Xposed logs wasn't selected when I started with the logcats.

Now it is:

http://pastebin.com/EFZDirhJ

Screen was on, music paused. Then I play/paused 3 times.
[Xposed Framework Modules] Ksawery:
The new version 4.0 beta 4 doesn't work to me. I've returned to beta 3 that works fine.

Possibly It's due I've disabled the resources hooks.
[Xposed Framework Modules] MESA:
Hello. My device is Xperia V running stock JB 4.3

Beta4 is not wotking. It says Module is not enabled but it is. Beta3 worked out fine
[Xposed Framework Modules] DallasBelt:
Same here.
[Xposed Framework Modules] Xspeed:
My god, ProGuard played a trick on me again. Sorry for that, a fixed version is up on the repo.
[Xposed Framework Modules] Ksawery:
The new new beta 4 works to me but now the flashlight doesn't work. I use Kitkat. In beta 3 it worked fine.
[Xposed Framework Modules] Xspeed:
Yeah. It doesn't work because I removed camera permission and added flashlight permission to the app.

I thought Android's flashlight permission is for using the flashlight, but it seems you need access to whole camera anyway, how stupid is that...

Once there is something more to be done, I'll release the fixed next version.
[Xposed Framework Modules] Chamelleon:
[MENTION=5292510]XspeedPL[/MENTION]

After update still "Activate this module..." bla bla bla. Updated few times and still no luck. I'd rather not to wipe whole data to back to beta 3.

Log in attachment.
[Xposed Framework Modules] Ksawery:
Ok. Thanks. Meanwhile I return to beta 3.
[Xposed Framework Modules] Xspeed:
I had a mess-up with that. Check for updates in the Xposed Installer. Newest version has the same name (beta 4), but is fixed.

If nothing comes up, I'll just release the fix for that as beta 4.1 or something tomorrow :P
[Xposed Framework Modules] totbl:
Where would I find the Media receiver list? Also, I believe it's the Eleven music player. It came stock with my CM13 OS. Not sure how to confirm if it is or isn't Eleven tho. Def. looks like it.

*EDIT: Never mind! Found the list in settings and saw my player there. (Eleven confirmed.) Ticked that player and everything's working great! Can't thank you enough. Cheers, mate.
[Xposed Framework Modules] Chamelleon:
I had to completely uninstall beta4 and make clean install again to make it work. Unfortunately I couldn't restore my data backup to keep my settings. Actually I could restore it but all settings disappeared every time after leaving app.

So I made clean install and for now it's OK, I even make Flashlight working. Instead of default flashlight action I change it to "Toggle Flashlight" shortcut from GravityBox and it's working like it should.
[Xposed Framework Modules] Xspeed:
Glad you got it working ;)

Yeah, I'll guess I should release the flashlight fix as it is.

Expect it today.
[Xposed Framework Modules] Chamelleon:
Ok, thank You.
[Xposed Framework Modules] Chamelleon:
So, latest beta is working but partially. I can turn on flashlight (default one, not one from GB) but I can't turn it off. The other thing is buttons list scrolling. In main window, single touch acts as press and instead of scrolling only moving or deleting buttons is working.
[Xposed Framework Modules] aLexzkter:
Bug.

Also, SOMETIMES when scrolling on the Chain list menu by swiping from the right / center part of the screen, the chains get accidentally reordered, that's annoying.

Btw, what happened with the pulse led bug? I don't think there's anything wrong with my phone. I updated to the latest version, and again, it only worked on the first chain activation, unexpectedly (wasn't paying attention)

Also, the notification sound volume is a little bit high, will we ever be able to set the volume ourselves ?

Loved the search on keypress action window. Thanks
[Xposed Framework Modules] Ksawery:
I have the same problem...
[Xposed Framework Modules] Spodi2290:
I noticed PBMC is like completely disabled while there is an ongoing phone call, is this intentional? As I'm using a custom rom the button control changed from my previous one, so nearly all keys are remapped with PBMC. I was a little bit confused, when I tried to look up something while a call :)
[Xposed Framework Modules] shda:
Hello everyone. I've got problems with PBMC next media/previous media. It simply doesn't work whatever settings I choose. When I press volume button, there is s a vibration, but track doesn't change.

Samsung I9500. Stock rom, rooted. Android 5.0.1. Here is xposed log: http://pastebin.com/38wyKn2L

Thanks
[Xposed Framework Modules] Xspeed:
This is what happens when you do stuff in the middle of the night instead of sleeping.

Thanks for reporting those :)

I am gonna revert the chain list management changes. I kinda screwed it up yeah.

Pulse LED is going to be customizable in the next version (color and length).

As for the sound... though thing to do. As I said it uses music volume, so I'd have to lower the music volume itself. It's possible, but a hassle and a quite hacky solution. I'll think about it.

Yup. I am gonna change it back.

You're right, and it is intentional. I made it that way all the way back around 2.x versions, so quite a long ago.

Maybe I'll add another chain option: Call mode - idle, ringing, incall? Hah.

What music player are you using?

And what signal receiver have you set in settings?
[Xposed Framework Modules] shda:
I use poweramp and poweramp is set as a signal receiver in settings.
[Xposed Framework Modules] Shadow_Reaper:
Hello, I'm having issues with the latest version.

I currently have installed the beta4 fix1 version.

I have configured the VolumeUp button to skip to next track when listening to music when I press and hold it.

The VolumeDown button goes back to the previous track when I press and hold it too. Both are set to respond after 400 ms.

The problem is this:

When I hold either of them, The media player changes the track according to the designated function each button has, BUT just after the track is changed (the delay time is over), it proceeds to raise or lower the volume.

If I don't tick the "Cancel original key functions" option, it does the same thing (except that now it starts right after I hold the button since it does not "care" about the delay time)

Also, if I tick the "Cancel original key functions" option, when I remap the single press action for each of the volume buttons so that they actually raise or lower the volume, they just don't do what they're supposed to do. The only way they work is if I leave this option unticked, but then I still have the problem described above.

I have a Samsung Galaxy S4 GT-I9500 running KitKat 4.4.2

Here's the log

http://pastebin.com/B5AsSNr2

Thanks in advance!

P.S: I didn't have this problem in 3.0.4. Also, that version has an option to circumvent the first problem if I'm not wrong.

Enviado desde mi GT-I9500 mediante Tapatalk
[Xposed Framework Modules] shda:
Isn't this error

from the log file

somehow related to my problem?
[Xposed Framework Modules] aLexzkter:
Please, don't forget to add the possibility to change the notification sound. Or just hardcode a nice beep ring . I dislike it being the same sound as the one I have set for message notifications.:good:
[Xposed Framework Modules] Xspeed:
I remember people talking about PowerAmp working before in this thread, use the search, maybe those posts will help you.

I don't use it myself, but you can always try setting media receiver to "Let the system decide" if you have one music player anyway.

Ah right. My guess is that only happens while using PBMC with screen turned on, yes?

Android before Lollipop has some issues with cancelling keys. Well, I suppose I can try to fix that now.

Nope. ALL things related to PBMC start with "PBMC: " in the logs. It's some other module.

Umm, you know you can change the sound since beta4, right? O.o
[Xposed Framework Modules] shda:
Can I do something else to clarify the problem?
[Xposed Framework Modules] aLexzkter:
Lol, there were plenty of new features, I missed that one indeed, works great. Now it makes sense to use sound notification:good:
[Xposed Framework Modules] Spodi2290:
Seems like I'm always requesting new features, I'm evil :mad:

The other one I requested (different action with music playing or not) works flawless for now, so I'm really thankful for that :highfive:
[Xposed Framework Modules] shda:
Sorry for bothering. I solved the issue. No problem with PBMC. Poweramp has an option to react or not on headset buttons. And reacting is disabled by default.
[Xposed Framework Modules] Shadow_Reaper:
Yes you're right. It happens only with screen on, either locked or unlocked. I didn't notice that yesterday.

Anyway, I never really used it with the screen on, so that may explain why I never had this issue in the first place.

I've been testing the keys and I found that remapping the keys to do their single press original action is in fact, working. I don't know what I did wrong but that's working.

Enviado desde mi GT-I9500 mediante Tapatalk
[Xposed Framework Modules] Xspeed:
Too many new features for you? Haha

No problem mate!

The more possibilities the better, I think :silly:

Glad you got it working ;)

So, the only problem that remains is cancelling the keys while screen on.

I will try to fight it on Monday, because I am away for the weekend.
[Xposed Framework Modules] Xspeed:
This was supposed to come out yesterday, but duh... life and stuff :silly:

beta5 rolling out:

- Added notification light color and duration customization
- Reverted chain list management control
- Fixed flashlight control
- UI changes and tweaks

Seekbars look more nicer now. Tell me what you think ;)

Enjoy!
[Xposed Framework Modules] Ksawery:
Now the flashlight works fine!
[Xposed Framework Modules] Viper4713:
How exactly do you configure it to not change the volume? An example of my problem is if I hold volume down then my volume turns down only 1 volume step then the song changes, it also does the same when trying to go to next song, in my car its not an issue sense the volume is all the way up, but with headphones its annoying that the volume keeps turning up.

"Cancel original key functions" works I suppose but then you can not change the volume at all anymore.

If anybody can shed some light on how to use this properly it would be appreciated! :good:
[Xposed Framework Modules] Xspeed:
Have you seen the BIG link in the first post? Please, try to learn to read provided information first.

Beta version FAQ: Help and information about the newest 4.0 beta release!

Glad it does ;)
[Xposed Framework Modules] aLexzkter:
[MENTION=5292510]XspeedPL[/MENTION] just updated to beta5 on my note4 (5.1.1) and led turned on red on first chain activation, only, as usual.

Tried it on an lg g2 with cm13 and works perfectly, led turns on white though.
[Xposed Framework Modules] Cryosx:
Feature request: audio beep when pausing/playing, next song, etc. (just like in poweramp)
[Xposed Framework Modules] killoid:
or maybe a short vibrate? or a vibrate option along with controlling it's threshold?
[Xposed Framework Modules] Blizzard22:
Looks like 'exclusive signal receiver' works without starting the app. Thanks a lot!
[Xposed Framework Modules] Xspeed:
I too would rather prefer a vibrate option over a beep. But if you want, I could make both.
[Xposed Framework Modules] ahrion:
Can you add multiple apps to select for exclusive signal reciever? Make it so whichever one is running gets the priority??

Thanks
[Xposed Framework Modules] aznrice2k4:
OMFG! I LOVE YOU MAN! The physical power keys and volumer rockers on my HTC One XL is broken so this made my love you!
[Xposed Framework Modules] killoid:
i think the vibrate option is better.you can do that. :)
[Xposed Framework Modules] Humpertle:
If keyguard is disabled (tasker + secure settings, android 4.0.4) then power button (enabled as play\pause signal, delay 300ms) not working. Play\pause works, but screen always off. I can't turn on the screen.
[Xposed Framework Modules] Xspeed:
I just tested my own power button and it seems it can be memory related (?).

At first several tries it was randomly turning the screen on/off, and sometimes pausing/playing the music (no matter holding or not).

Then it started working as it should be.

All I can suggest for now is increasing the delay to 500ms.
[Xposed Framework Modules] Humpertle:
In my case screen always off.

Not working. Screen always off :(

delay 1000ms - same.

enable compatible mode - same.
[Xposed Framework Modules] Xspeed:
Hmm, don't use it for now then until I think of some way to fix this.
[Xposed Framework Modules] Kiicek:
Hey, is it possible to have an option for enabling the media keys function only when headset is connected? It would prevent accidental playback from the speaker.
[Xposed Framework Modules] Mad_BillY:
srry, i'm kinda newbie here !

is this root needed app or not ?!
[Xposed Framework Modules] Blizzard22:
You need to install Xposed framework (which requires root access) and install this module.

Please read the instructions of Xposed framework in their thread.
[Xposed Framework Modules] Mad_BillY:
tnx a lot !
[Xposed Framework Modules] sugarkane87:
Perfect! this is what i'm looking for, thank you :good:
[Xposed Framework Modules] sirganon:
Working great with Pandora on my gs3. :thumbup:

Sent from my SGH-T999 riding a Dirty Unicorn
[Xposed Framework Modules] Xspeed:
Done...

...and done!

Notice:

A future version (it's gonna be like, 2.0) is going to be an almost full rewrite to fix several problems like not being able to set two functions to one key. It's going to be cool and all, but it's gonna take a while to do. So, don't worry, I am still working on this.
[Xposed Framework Modules] vk89bna:
Vibrating function work according to time set only for play/pause by power button but for volume button which are set for next and previous track is start vibrating as i start pressing it
[Xposed Framework Modules] Xspeed:
I don't know if I get what you meant, but if you have a delay set on a key, then the vibration will start only after that delay, otherwise it will start immediately.
[Xposed Framework Modules] Dj Telo:
Hello!

Quick (and probably dumb) question. Does this module also work with virtual keys? I mean, for instance, with phones that only have menu/home/back on-screen keys.

Thanks!
[Xposed Framework Modules] Xspeed:
LED capabilities vary from device to device, you might get only some colors or no colors at all.

Do other apps like Facebook or Snapchat have their colored notification LED on your Note4 and G2?

Maybe there's something I'm missing then.

It does, but not while the screen turned off.
[Xposed Framework Modules] Dj Telo:
Thanks for your reply. I've known this module for quite a long time but I discovered it after Xposed Additions so I never really gave it a try. Now I am planning to change my Samsung S4 for a Nexus 6P and it appears that Xposed Additions is not capable of remapping the non-physical keys so I was looking for an alternative. It looks like PBMC can be helpful here. I have started playing with it, still in my S4, and even though it is taking a while to configure, I am amazed by the flexibility and the possibilities of the module. Just one question: will a backup made with Titanium Backup be enough when I transfer everything to my new phone in order to keep all my configuration? If not (and even if the answer is yes I still would like to know), is there a file somewhere in the module data that I could manually export through a file explorer where all the configuration is stored (like a xml or txt or something)?

Finally, a small suggestion: when I try to set a delay or a vibration duration in a key chain it is difficult to see the value of the slider while my finger is on the slider itself. It happens that the number is so close to the cursor that the tip of my finger almost covers it. It would be nice to have a manual input via keyboard or if the number were a little bit further from the slider.

Thanks for your work! ;)
[Xposed Framework Modules] Xspeed:
All configuration is kept in app's storage, so TB and any other backup tool should do fine.

I'm still experimenting with the seekbars.

On one hand, you want to see the value.

But on the other, I want to keep it as compact as possible, because too big UIs scare people.

You're welcome ;)
[Xposed Framework Modules] Dj Telo:
So far I have been able to remap single, double and triple (+hold) combinations of the headset button to media and Tasker actions, either with screen on, screen off or lockscreen. It works perfectly!

Now I am trying to remap the power button (yes, I took the risk). My goal is to be able to toggle the torch with a triple click + hold. The thing is that the original function of the key is lost, even though I have also created a combination to map it to its original function. The two combinations that I have are:

Power Pressed > Power Released (delay 0.15 s) = KEYPRESS (POWER)

Power Pressed > Power Released > Power Pressed > Power Released > Power Pressed (delay 0.3s) = TOGGLE FLASHLIGHT

The torch toggling works perfectly, but the power button won't wake the device no more. There must be some basic thing about the dynamics of this module that I am still not understanding completely. Could anyone give me a hand?

I did this because I know my ROM allows waking the device by pressing the home button, so I could afford the risk.

Thanks in advance!

EDIT: it seems to work but only sometimes... I don't know what the issue is... :S
[Xposed Framework Modules] Xspeed:
Well, enable debug log in settings, try it again and post the log here.

Or just look through it yourself, if you're feeling clever ;)

And beta6 has just arrived by the way:

Added an ability to map by telephony state
Possible fix for notification light problems
Fixed light duration
Restored the ability to set multiple chains of the same type with different delays
Various UI tweaks

Multiple chains of the same type - for people who love to experiment ;)
[Xposed Framework Modules] Dj Telo:
Well, here it is:

http://pastebin.com/BNvLKZXc

I cleared the Xposed log and immediately after I turned the screen off via the power button and tried to turn it back on via single presses of the power button. It didn't work. For more details:

String named "Power 1 Off": Power Pressed > Power Released (delay 0.15 s) = KEYPRESS (POWER); only executed with screen off.

String named "Power 3H Off": Power Pressed > Power Released > Power Pressed > Power Released > Power Pressed (delay 0.3s) = TOGGLE FLASHLIGHT; only executed with screen off.

Both strings cancel the original key functions.

Using a Samsung S4 with a CM13 based custom ROM (VRToxin).

Thanks for your reactivity ;)

EDIT: if it might help, I have observed that after multiple single clicks the screen doesn't turn off, but if right after I do a long press, the "triple click and hold" combination is detected and the torch is turned on, so it looks like the system is waiting for the "triple click and hold" combination and ignores that a single click should already trigger another action. I thought that this was solved by adding a delay to the "shortest" combination at the end, but I must be doing something wrong.
[Xposed Framework Modules] Xspeed:
[MENTION=2625872]Dj Telo[/MENTION]

I see the problem now. The mechanics can be a little confusing at first.

Look, all buttons you press are put into a queue.

Now, what happens:

1. You press and release POWER once

QUEUE: ..., ..., ..., ..., Power down, Power up

Power 1 Off is put as a candidate to run

2. You press and release POWER again

QUEUE: ..., ..., Power down, Power up, Power down, Power up

Power 1 Off is NOT put as a candidate again, because the queue did contain (Power down, Power up) before

3. Press and release POWER for the 3rd time

QUEUE: Power down, Power up, Power down, Power up, Power down, Power up

Power 1 Off is NOT put for the same reason

Power 3H Off is put as a candidate

Why does this happen?

Only that we can stop chain Power 1 running in place of chain Power 3, because the queued keys would match them both otherwise at step 3.

How to fight this?

When any chain is executed the queue is cleared, so you can execute Power 1 again if it was blocked.
[Xposed Framework Modules] Dj Telo:
But if I understand it correctly, the 0.15 s delay at the end of Power 1 should allow Power 1 to run between 1 and 2, right? In other words, if the power key is not pressed for a second time less than 0.15 s after the first release, Power 1 should be triggered. However this does not always happen...
[Xposed Framework Modules] Xspeed:
Look, the way I made it work is that three consecutive presses of a key doesn't do a single press action three times, but one single press, one double press and one triple press.

So, with 3 presses of a key we have:

1x single press action

1x double press action

1x triple press action

Instead of:

3x single press action

2x double press action

1x triple press action
[Xposed Framework Modules] Dj Telo:
I am sorry, but I am not quite following. I see your point of how the 3 consecutive key presses are parsed, but I don't see how this justifies that the first single press action sometimes is not detected. I don't want to be annoying, so thanks for your patience. :)

Changing subjects. A few things that I am missing from Xposed Additions are the possibility of remapping a chain to show the recent app list and to unlock the device if it is on the lockscreen. Am I missing them or they do not currently exist? In case they don't, maybe you could consider them as a feature request for the future.

Thanks again!
[Xposed Framework Modules] Xspeed:
It's not your fault. I suck at explaining and making proper documentation.

I really hope someone would miraculously come and do it for me :silly:

Basically, when you press power two times, PBMC does nothing, because there is no such mapping.

Recent app list can be done via a keypress (app switch key).

As for unlocking the device, I'll see what can be done ;)