yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] badbob001:
I know there actions for camera shoot and camera focus but can there be a single action for focus-then-shoot?

The mic off is actually a toggle and it's easy to lose track of the state of the mic. Can you please add discrete 'mic on' and 'mic off' commands? Also, the 'mic on/off' doesn't work unless the phone app is in the foreground. Is there a way to set a 'app target' for an action so the mic command always goes to a particular app such as the phone app?

Say I set different key-bindings for app A and app B. If I invoke app B from A so app B is now in the foreground, the bindings are still for app A. For example, I have different binds for the camera app and the video player app. If I run either directly, the bindings are correct. But if I'm in the camera app and play back a video I just took, the bindings are still for the camera app even though the video player is in the foreground. Is there a way to have the keys bound to the foreground app and not the parent app? This would also be an issue when launching apps from a file manager, where the module thinks the file manager is in the foreground when it's really the invoked app in the foreground.
[Xposed Framework Modules] Cyboy:
So nice but I'd suggest you to

1-add a confirmation dialog before such heavy process killing function

2-add ability to use combined key(eg power+vol down)

3-mouse keys remapping(back to the GB)
[Xposed Framework Modules] dk_zero-cool:
Mic, Focus etc. are not actions, those are keys just like Power, Home, Back and so on. The module just makes one button act as another, how the buttons act on the system is up to the system and the applications.

If you want more extensive options, consider Pro+Tasker.

It should alreayd use the foreground app, but I will see if I can re-create and fix this issue.

People do not want to have a box popping up every time they use that actions. I for one was bothered enough just by CM's Toast message in their implementation.

Open the app, look at the top where it says something about Pro and click on it.

Open the app, click on Buttons and check 'Allow External Devices'.

And just to comment you from Play Store

You cannot have two modules handling keys. So you will just have to choose.

Also why is it that you think that it is my job to fix compatibility with other modules? Write to the GB developer and see what answer you will get there.
[Xposed Framework Modules] Moon Shadow - NM:
Ignore.
[Xposed Framework Modules] h1ghland3r:
Even in 3.3.4 my Power Button doesn't work. What am I doing wrong? Coming back again to 3.2.2.

Sent from my Moto X
[Xposed Framework Modules] dk_zero-cool:
Could not say without a debug log.
[Xposed Framework Modules] Cyboy:
1-Yes.. but add a simple tickable option for it please.

2-i cant buy your app because of sanctions,bans,etc over here(Iran). but i can translate your app to Persian(Fa) instead*

3-already did ,it does not recognize the pressed button on mouse while its working well yet.have you tried it at all?what should appear on the key-reading box then?

4-Regem-Ex and GB are working togather on my device like brothers :D

Regem-Ex is used to kill stupid stuck and hung-up apps on my phone ,but its not as powerful as yours.
[Xposed Framework Modules] dk_zero-cool:
I have not tried a Mouse no, I don't have any external devices that can be attached to my Phone.

There is no module out there as powerful as this when it comes to remap. While others adds a few simple options by intercepting a few supported buttons, my module completely replaces Android's internal key control, which means that other modules needs to be compatible with this and not the other way around.

Another solution would be to change the priority of the modules, so that GB is always executed before my module. But I think that this is something that should be added to GB (If priority support has been added to XposedBridge).
[Xposed Framework Modules] Cinner:
Is this mod supposed to work after your device goes to deep sleep? On my HTC One, I can set a button to wake my phone but only for a few minutes after the screen turns off. I seems that when the phone starts to sleep, I can no longer wake it using this Xposed addon.
[Xposed Framework Modules] dk_zero-cool:
Yes it is meant to work in deep sleep. Some devices however does not work with "Power" in sleep mode. Switch to "Power Forced" and it should work just fine.
[Xposed Framework Modules] lmike6453:
I have to pop in here to stress my thanks to you! You really made button remapping a breeze in comparison to modifying system files manually..

Suggestions would be to allow the remapping to load an application, or a shortcut within an application(similar to long pressing to add on custom 3rd party launcher)

Getting crafty with it...if you can remap a hardware button to launch a folder(flyout style), that could completely replace PIE for us in conjunction with apps!

EDIT: Remapping the Back key causes haptic feedback not to work. Tried to uncheck and rechecked in settings, and menu haptic feedback works but not the Back key. Running 4.3 stock on Vzw Galaxy Note 3
[Xposed Framework Modules] spätzlemitsoß:
already answered, just read some threads before:
[Xposed Framework Modules] jj411:
nice mod. finally found an option to wake the device using volume keys without having to switch roms. :good:
[Xposed Framework Modules] xXYoshiXx:
A little report regarding the softkeys issue: on my Acer Iconia a700 the softkey remapping works, on my Xperia ZL not, so maybe it is a ROM issue? Also a little request, how about a delay fir the double click actions, like for the long press?

Thanks for the great module, like it a lot.
[Xposed Framework Modules] dk_zero-cool:
Normal hardware key events is registered by the kernel which sends it to Android Input System. From here the key events are transfered to Androids framework where actions are decided based on the key code. This is the part the module injects.

The Software keys on the other hand is nothing more than an Application, just like any other Android system Application like the Panel, the Notification and so on. Now I don't know how Android normally does it (Never played with a pure code), but CyanogenMod ROM's makes sure to send most of the Software buttons through Android's Input Manager, allowing the module to intercept them. But that does not stop other ROM's from just performing the tasks directly from within the Software Button Application, which means that the Event Manager will never know that any button was ever pressed, and thereby neither this module. The only way here is to inject the Software button application itself. But if different ROM's does not fallow a particular standard, it would mean a different injecting code per ROM.

Instead you should maybe just use another Soft-key application

Now about delay. Note that if you raise the delay on double click, you also raise it on regular clicks. The only way to see if someone is making a double click, is adding a delay to the regular click and wait and see if they press again before that delay is done. At the moment, any normal clicks you make, takes 100ms, which is the delay it has while waiting for a double click. If you raise this, then you will just add a very noticeable lack on your normal key presses. I started with 150ms, and even with this little, the phone started feeling non-responsive.
[Xposed Framework Modules] shinpil:
What a fantastic!

I've been waiting feature like this for 3 years!

This works perfect on galaxy s4.

Thank you very much!!!:laugh:

I found there is a little bug. The menu key does not haptic when I re-mapped the key.

I think it would be more perfect if you add new re-map configuration like killing all background apps, killing foreground app, launching specific app.
[Xposed Framework Modules] signupstuffid:
So with the 2.1.0 update I was able to remap sleeping home button to volume up, which effectively stops it from waking my Droid-X. I wanted to do this because the face buttons seem to press to easily in pocket, and my ROM, would not let me turn off the home button wake device function.

I was not able to get my monster ibeats earphones remapped to work for the functions I remapped it to on the same Droid-X with liberty ROM.

I'll test that feature on my Rezound, and Droid 1 and come back and update.

Edit: The next and previous media buttons remap fine on my ICS Sense 4.1 Rezound (ROM in signature), but the play/pause doesn't remap at all. Either awake or asleep, it always sends media play/pause, no matter what its mapped to.

You really are adding all the features that are making this module super useful!!

Thanks for all you time you spend writing this module :) :good:
[Xposed Framework Modules] nimrodity:
2.1 acts totally weird, none of the actions does what it´s setup too,not even if i setup 2 buttons the same ,both buttons behave differently. 2. beta 3 was just fine

sorry, my bad i understoof wake and sleep the opposite way, works now
[Xposed Framework Modules] gladson1976:
Is it possible to disable/remap the bluetooth headset call connect/disconnect button when not in a call.

I have a Samsung HM1700 bluetooth headset and the button on top of the headset is used to connect and disconnect calls.

When not in a call, pressing the button redials the last dialed number.

I need to disable/remap only the last number dialing functionality when not in a call. I've pressed that accidentally quite a few times :)

The call connect and disconnect are quite fine, when there is a call. The problem is with pressing the button when not in a call.
[Xposed Framework Modules] alirezaafkar:
Doesn't work on my S3 using Carbon ROM. Android version 4.3.1

When I remap any button that button doesn't work anymore! Totally disabled!

Edit : Worked !

I was waiting for such app for long time

Thanks man

---------- Post added at 10:35 AM ---------- Previous post was at 10:25 AM ----------

It's possible to add an option to launch custom app?
[Xposed Framework Modules] brotbuexe:
Autorepeat for Volume Up/Down with Longpress would be nice. So you can hold the key and it goes all the way up or down.

And a click + hold as a button map option would make even more functions possible. Not that I need that...
[Xposed Framework Modules] dk_zero-cool:
I don't have headphones with buttons, so I can't test it. Maybe the Play/Pause button on yours is not really a Play/Pause. It might be just a Play. It all depends on what key codes the buttons sends out and what your ROM redirect them as.
[Xposed Framework Modules] jsminnis:
Is there a chance that you could make it so we could map buttons to an app of our choice while the screen is off. I have an s view case and I would love to map the home button to voice search.
[Xposed Framework Modules] brotbuexe:
I don't use it either, but I just tried a one button cable headphone.

It does not work with the "Media Play/Pause" remapped. It just do play/pause without getting remapped.

Looks like it's another keycode.

https://play.google.com/store/apps/details?id=aws.apps.keyeventdisplay shows:

Press buttons to see the keycodes:

^Â KeyDown:Â Â Â Â Â Â action=0 code=79 repeat=0 meta=0 scancode=226 mFlags=8 label='' chars='null' number=''

^Â KeyUp:Â Â Â Â Â Â Â Â action=1 code=79 repeat=0 meta=0 scancode=226 mFlags=8 label='' chars='null' number=''

Logcat:

10-17 13:31:00.354 V/KeyguardHostView(19833): show transport, gen:21
10-17 13:31:00.354 V/KeyguardHostView(19833): music state changed: 3
10-17 13:31:00.624 V/KeyguardHostView(19833): show transport, gen:22
10-17 13:31:00.624 V/KeyguardHostView(19833): music state changed: 3

Hope this helps.

But we could keep in mind that the button also does answer / hang up when a call comes in.
[Xposed Framework Modules] xXYoshiXx:
The app you linked is already in use, but it only hides the softkeys dynamically, the replacement navigation bar doesn't offer much customization regarding button presses and covers the bottom part of the app it floats above.

So do you think you could look into adding a way to intercept the softkeys? This is one of the features I'm missing from a the custom ROM running on my RAZR.
[Xposed Framework Modules] dn06se:
Hi OP, I have choosen the "Never" in both "wake on plug and unplug". But I still gets screen turns on when plug and unplug charger. :crying:

My phone:

----------------

- Note 2 internation

- stock touchwiz rom (rooted) - 4.12

- other xposed modules works

- already restart many times and ticked the module in xposed app

- installed addition settings 2.10

However thanks for this xposed module. :good:
[Xposed Framework Modules] dk_zero-cool:
The app I linked to injects key events through the terminal, which will be intercepted by Android's Input Manager and transfered to my module. You have to provide the app with root access and then enable it's xposed module.

The other thing I don't know. I will look at it at some point, but at the time being I have other things to do with this module. And it was meant to Re-map button events, not application touch events.
[Xposed Framework Modules] dn06se:
bug in wake on plug/unplug

:confused::confused:
[Xposed Framework Modules] a.fontenele:
[MENTION=3147360]dk_zero-cool[/MENTION]

The Torch addition now simply rocks! I don't even need any other third party app and that is awesome!

IMHO the PRO version is worth three times its price at least. No cutting-edge phone can offer what your module itself can. It comes down to be by far one of the best apps I own. Thanks a lot for that!

In my opinion and taking into account my phone's daily use, no smartphone will ever be good enough without your module.

Cheers mate!
[Xposed Framework Modules] dk_zero-cool:
Thanks.

Yes I looked around in Play Store and noticed how few Torch apps actually support Intents. So unless you had a custom ROM with build-in support like CM, you where kind of out of luck without any Native support in the module.
[Xposed Framework Modules] a.fontenele:
Torch timeout

That's great my friend! I'm glad to see how committed you are to this app. I honestly wish you could make more profit out of it... I'm trying to do my part in convincing even my non-power-user friends to purchase your app, hahaha...

Another question, there is no timeout for the torch if I accidently set it right? Is it in your plans to implement it? Maybe 5 minutes to avoid a battery drain...
[Xposed Framework Modules] dk_zero-cool:
Yes it is on the ToDo list
[Xposed Framework Modules] a.fontenele:
Wow man... You rock!

As for the Long Press Delay subject, I kinda agree with [MENTION=2186813]Ninolina[/MENTION]... But for me short delay shoud be 150... If I'm not mistaken you already used this delay in the past versions and it was my favorite... Picky as it sounds I feel the difference since my phone's response's gotta be as quick as it gets...

Couldn't you do something like this maybe so that everyone is happy?

Long Press Delay

Very Short (150ms)

Short (200ms)

Medium (350ms)

Long (500ms)

It's just a humble suggestion... It would maybe be quicker to implement it than the slider thing... What do you think?
[Xposed Framework Modules] dk_zero-cool:
I have already added two sliders (or SeekBar as Google calls it) for Tap and Long press. Range is set to 50/200 for Tap delay and 100/500 for long press delay. Will be in the next release.
[Xposed Framework Modules] a.fontenele:
Awesome! You are the man!!! :D

I look forward to it!
[Xposed Framework Modules] dk_zero-cool:
Beta Release

New 3.4.0 Beta is out on Xposed Repo (Remember to enable beta releases in XposedInstaller).

The changelog is short, but the entire Re-Map engine has been rebuild, which hopefully should fix a lot of issues and make it easier for future support of external devices among other things.

Also I did a little digging into the default combo events such as default screenshot. It seams as if I got that thing sorted out on most ROM's. Tested this on ICS, Jellybean and KitKat CM ROM's along with the older Gingerbread Stock Samsung on Galaxy Y, all with success. Just remember that different ROM's has different ways of handling this.

Stock/CM = Vol Down + Power - Hold for long press

Stock Samsung = Home + Power - Then Release Power while keeping Home pressed

And there might be other combinations in other ROM's.
[Xposed Framework Modules] Andreydroid:
Hello,

i have some troubles with my Highscreen Zera F.

I use Xposed Additions with Xposed framework and all looks good, but latest version, that recognize hard buttons is 3.2.2 on my phone.

All versions higher 3.2.2 (i try all of them) do not recognize then i press any of hard buttons to configure module.

I use stock v10 ROM, android 4.2.2, phone rooted, xposed and busyboxed.

3.2.2 works fine.

Think about to go PRO version but need solve that problem.
[Xposed Framework Modules] dk_zero-cool:
Sounds strange. Try the Beta instead, a lot of things has changed to fix both known and unknown issues. Just setup XposedInstaller to allow betas (Just swype far to the right after selecting the module, or change globally in it's settings)
[Xposed Framework Modules] Andreydroid:
I try latest beta. Same problems.

I have 6 hard buttons on my phone.

1 power, 2 vols and 3 sensor buttons (home, back and menu).

On latest beta phone recognize 3 sensor buttons but actions now work.

So i can configure to Power phone by 1 click back button then screen off but this is now work - nothing happens then i press back button then screen off.

All this works fine on 3.2.2 version with vol button.

3 hard buttons still not recognize at all in latest beta.

Maybe i can help with logs or something?
[Xposed Framework Modules] dk_zero-cool:
I don't quite understand what you mean. Let's take this one thing at a time

By sensor buttons you mean Capacitive?

You know that Capacitive buttons does not work when the screen is off?

What are you trying to do? And what conditions, screen off, screen on? What actions? What buttons?
[Xposed Framework Modules] Andreydroid:
Ok, i undestand about cpacitive buttons.

App recognize them then i press them.

But other 3 hard buttons doesnt work.

vol+ and vol- and also power button do not recognized then i press them in app.

Again - 3.2.2 and lower works fine for my phone.
[Xposed Framework Modules] dk_zero-cool:
So if you click on "Add new button" and then click on Power, nothing happens?

I think your device is registering your hardware buttons as a Keyboard. Those has been disabled since 3.3.x. I am working on allowing users to enable support for those types, that should fix your problem, even though regular hardware buttons should not be handled as keyboards.
[Xposed Framework Modules] Andreydroid:
Ok thank you, i will wait for workaround in new version.
[Xposed Framework Modules] Planterz:
Am I completely blind or something? Because I can't find the haptic feedback options. Verzion 3.4.0b1. Samsung Galaxy Light SHG-T399 4.2.2JB.
[Xposed Framework Modules] dk_zero-cool:
There is only one Haptic Feedback option, and that is to Force it. But unless you are using the Google Play edition, you should not need it as Haptic should already work.
[Xposed Framework Modules] Planterz:
I'm using the one from the Xposed Repository.

I simply cannot find the option for haptic feedback. This is all I see, and there's nothing underneath when I try to scroll.
[Xposed Framework Modules] dk_zero-cool:
Since Haptic Feedback is related to buttons, I would try to click on 'Buttons'.
[Xposed Framework Modules] Planterz:
OK, I got it. I looked under buttons, but didn't see anything about haptic feedback, Just long press delay, Allow external devices, and Add Keys. I didn't look under Add Keys, because it didn't make sense to me to add keys, since all my keys work. But I found the haptic feedback there. It just wasn't very intuitive to me, I guess.

Thank you. Works perfectly, and this feature is greatly appreciated.
[Xposed Framework Modules] a.fontenele:
[MENTION=3147360]dk_zero-cool[/MENTION]

Man, nice work on the beta release! The sliders are awesome! I guess nobody will dare to complain about the delay now, hahaha...

I haven't found any issue so far.

I got a question though. I've set back key long press to kill application and since the latest release, I've noticed that if I accidentally press and hold it while in the home screen, I get a black screen which I cannot escape from, unless I reboot my device. Am I the only one facing this?
[Xposed Framework Modules] Spere:
So you are killing you launcher? What launcher you use? Do you have several launchers installed? What device?

If you make back long press kill an app, doesn't it do its job if you are on launcher and, long press it and get launcher killed.
[Xposed Framework Modules] egingell:
If your launcher can't recover from getting killed, there's something wrong with it not Xposed Additions.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
Well both. XA should not kill the default Launcher, but the Launcher should just restart itself.
[Xposed Framework Modules] dk_zero-cool:
3.4.0 is out, this time with added Keyboard support (Thanks to a friend with a BT Keyboard that I could borrow for a few days).

Also on ICS+ you now have a list of different external device types (Keyboards, Gamepads/Joysticks etc), you need to enable the type of external device that you want to use.
[Xposed Framework Modules] fenchai:
guys, anyone experiencing when screen off and playing music, I click once volume+ button and it acts as long press. same for volume -

? what is going on? I dont have any task or xposed aditions doing this. any idea?

This made the volume from 20% to 100% in 1 click, and 100% to 0% with one volume down press... :$

Sent from my SM-G900H
[Xposed Framework Modules] fenchai:
Ok, I just discovered it is a problem with xposed additions.hope you can fix this issue dev :D

(I know it's xposed additions because I turned module on and off for all my xposed modules. and yours made the volume issue btw)

update: I just reverted to 1 version before, everything works. it is a problem from the newest version.

update 2: ver 3.4 and betas seem to have this issue.

Im sure that i installed 3.4 and it wasnt on experimental, if it was then sorry for bothering if it was still in beta state.

Sent from my SM-G900H
[Xposed Framework Modules] Wiidesire:
On Galaxy S4 i9505 now all buttons do not work again... I should deactivate automatic updates..^^
[Xposed Framework Modules] Cyboy:
Ok?
[Xposed Framework Modules] truedis:
Button remapping doesn't seem to be working right for me on Kit Kat ... is this a known issue? I can't really determine whether KK is supported or not.
[Xposed Framework Modules] ImpheOtus:
I'm on S4 GPe 4.4.4 and XA works perfectly.
[Xposed Framework Modules] Antitype:
Gamepad Issues: Buttons Waking Device During Screen-Off

Thanks for adding back gamepad support in version 3.4.0. Very grateful it came back. Having issues with gamepad waking devices back on during screen-off. If device is sleeping and if any buttons not re-mapped with Xposed Additions is pressed on a gamepad it will power the device back on during screen-off. I did this a lot accidently just trying to change a song.

For instance if you re-mapped X button to "Media Next" and were to change songs with that X button in screen-off and accidently hit Y button instead, Y button will wake the device. (Y button should do nothing, not even wake up device if not mapped. This should be the default behaviour.)

A workaround I found is to add every button the gamepad has and disable it for every click-activity you won't be using during screen-off. A bit tedious but it wll prevent waking up if wrong button is pressed. However pressing combo buttons will still wake the device. Combo keys are not pressed together at the same time but one after another in rapid successions, I didn't realize this.

In short if no key has been re-mapped with Xposed Additions it shouldn't do anything during screen-off yet it still wakes the device. A bit annoying but I can live with it.
[Xposed Framework Modules] chattyuk:
The latest update seems to have messed up a few things. I have menu set to recent apps and long press menu to open menu. Since the update menu opens menu, double tap menu opens recent apps and long press opens s-finder. I have a galaxy note 3 on kitkat