yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] dk_zero-cool:
Sequentially allows for more actions on the same buttons :)

Besides, Android can't handle two buttons at the same time. No mater what, one will always be processed before the next one starts.

The only issue with multi-keys are Virtual Buttons. Most touch screens can't handle two of them at the same time. But one hardware button and one virtual works fine. Just some info in case you have virtual buttons on your device.
[Xposed Framework Modules] kevin_1351:
Well that's not possible, I have more than 1 gig of my 3 gigs of ram left.

As I said, it's a common issue with new built apps, wanam xposed had this issue too. It's really not my fault or my phone not having enough resources. Everything else works like butter ;)

Could you also add an option to disable your intervention when power+home is being pressed?? For screenshots i mean. Or if that isn't possibe, add screenshots to your app? I'm sure the android sdk has it somewhere.
[Xposed Framework Modules] linsalata28:
I'm having 2 issues with the new update 3.0.4.

When I set long press menu with the screen on to kill application, nothing happens.

Also when I turn on debugging and long press menu with that setting it reboots my phone.

I also had the same issue of it not working on 3.0.2-2. On 2.3.8 everything worked fine for me.

I'm on a htc mytouch 4g running a cm9 based AOSP ROM called AospX.

I tried wiping the data and unistalling the app with no luck. I also disabled any other models that remap the keys.

Edit: Is there a way I can get a log of this from the phone? I'm not near a computer. If so how?

Thanks for any help with this.

I love this MOD and the new update but for now I'll have to go back to v2.3.8 with less options.
[Xposed Framework Modules] nacron:
Well with that figured out, do you think there will be a way to assign the system screen shot to the keys and also voice search?
[Xposed Framework Modules] kevin_1351:
That's exactly what I would like too.
[Xposed Framework Modules] coolkaas:
run torch (as app by tasker app factory), say curr.time and any useful self-writed little tasks.

(if 'run app' action is a feature exclusively of pro version this question doesn't matter for me -- I can't buy a module I haven't Market :( and google acc.)

and I still can't find 'Call' action at 3.0.4 version too. (os 2.3.4).

but thanks at any case for your work.
[Xposed Framework Modules] linsalata28:
Is it possible to add trackpad remap? I have one on my phone but have no clue how to find what key controls it.

It would be nice to have trackpad wake from screen off and unlock from lockscreen.
[Xposed Framework Modules] dk_zero-cool:
You can find logcat apps in market for this. Just remember to enable debug in the module.

If your trackpad does not show up when adding keys, then the trackback is not handled like other keys and I can't do much about it. A lot of these trackpad's has pure and hacked support, especially on unofficial ROM's. So this would be a better question to ask the developer of the ROM, to make the trackpad act as other buttons so that they are properly parsed to the PhoneWindowManager.
[Xposed Framework Modules] Ranomez:
The device info is in the signature, but whatever: HTC One X+ CM11 android 4.4.2, recents key as in the actual recents key single click, if I have the module active even if I don't remap it from within the module the single click action set in any other way (CM Button settings) does not work and if I set a long press action and single press action from within the module the single press will always get registered as a long press (not if I set it in an other way, then the single press does simply not work) and I have no shared_pref folder in the data folder of xposed additions.
[Xposed Framework Modules] egingell:
You need to assume that either the dev assumes your signature is outdated or that nobody can see your signature.

Do you see a signature there? I sure don't.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
True, it is not always visible. But in this case he has 4 devices in that list and I am not about to guess which one he means.

And this is the only key where this is a problem? And again, what module version? Any other modules installed (Sorry if this has been answered, but there has been many posts to day)?
[Xposed Framework Modules] linsalata28:
Thats OK.. Thanks for the reply. It will be great if I just get the other issue fixed.

Thanks for the help and this awesome app.
[Xposed Framework Modules] Ranomez:
Yah, that is the only key with the problem and I do have lots of other modules installed and enabled (around 30 enabled) but even after disabling them I have the same problem and I am on the latest version (3.0.4) downloaded from within the repo, also the last 2.x.x version works just fine (for both saving and having the recents button working)
[Xposed Framework Modules] dk_zero-cool:
Thanks, this seams to contain plenty of information.

Okay, don't care if you do have other modules, just as long as you tried without then I know that this is not just a conflict problem.

But it is strange that only this specific key has problems. I will try to see if I can test this on my own HTC One X which also has this key, however the screen has some large black dead spots (Dropped it outside long ago), so it is not easy to work with.
[Xposed Framework Modules] nacron:
I had issues where pressing home or power would have delayed screen on. It was because I forgot I had that button mapped as well In another module.
[Xposed Framework Modules] themadproducer:
I temporarily reverted to 2.4.8 because my main use, is to have a small delay, recents popup with long press back.

But my home button remained borked. So I uninstall the pro key and reinstalled, maybe with a reboot too. Anyway, problem fixed. I also like the fact that in this version, the non used buttons are not affected.
[Xposed Framework Modules] Ranomez:
The only other module I have that could remap my buttons would be Gravity box and I have the same problem with all other modules disabled.
[Xposed Framework Modules] dk_zero-cool:
I have uploaded a test version (3.0.6 RC) to the OP which should stop some of the complaints if it proves to work properly (Did on my devices).

Added a work-around that in general reduces the long press delay (Still unclear on the side affects).

Added a new custom default long press handler that provides more control over the default behavior (Including long press delay. This is a second work-around). This needs to be enabled in the settings as it is currently added for testing. It can be enabled from within the Buttons settings.

Fixed a small bug that would break a few options like Kill Apps on pre-Jellybean ROM's.

Added screenshot action for ICS+

Some feedback on this would be nice, especially regarding the long press handler.
[Xposed Framework Modules] linsalata28:
This test fixed the issues I had. I haven't enabled the handler option cause everything is working great.

Thanks for the fast fix. Also I love the new screenshot option.
[Xposed Framework Modules] dk_zero-cool:
You might as well test it, requires no reboot. Its a much cleaner way of handling default long press and will most likely become default.
[Xposed Framework Modules] nacron:
Screen shot works great!
[Xposed Framework Modules] linsalata28:
Is it possible in a future update to have individual long press delay for each key?
[Xposed Framework Modules] themadproducer:
@dk_zero-cool

Thank you for this version. My report for ICS...

1) Screenshot...won't work no matter what. :(

2) Long Press Delay...is fast again with internal handler enabled. With I.H. disabled, it's still faster than the previous release. So good stuff there. :good:

3) Short Delay / I.H. enabled, long press home+ pwr button sounds like a machine gun. If the long press menu gets working for screenshots, then this quirk won't matter.

4) Quirks...a few other anomalies depending on setup, where my pwr and home button won't function. Then I turn off the screen with a GESTURE (GMD app) and then the home and pwr buttons work again.

5) Menu long press...does the machine gun thing...even though it is not programmed. It still manages to pull up the stock search option. (machine gun= rapid successive click sounds while button is held down)

---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------

I asked this a few posts ago. I don't think it will happen but maybe with the new handler, something may have changed?
[Xposed Framework Modules] egingell:
Home+Power=>Screenshot

Click Action : Nothing happens.

Long Click Acton : Screenshot happens.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] killoid:
long press duration normal+handler : works as it used to be in v2.3.8. Great Update! :good:
[Xposed Framework Modules] dk_zero-cool:
Enable debug, reboot and then grab a logcat when you try to take a screenshot.

Not sure what you mean? The screenshot is an action that needs to be mapped. Just map it to multi click if that is what you want.
[Xposed Framework Modules] egingell:
That's what I did. Sorry if I wasn't clear.

I turned on logging and set only the Click Action for Home+Power to Screenshot. This time it took a screenshot, but it also opened the power menu immediately after. After the first successful screenshot, I was unable to do it again.

https://www.dropbox.com/s/is8lvly8rqghwh5/spaz.txt

Log steps.

* Turn on debugging.

* Reboot.

* Disable Long Press for Home+Power/Screen On.

* Enable Click for same and set it to Screenshot.

* Opened CatLog and searched for "spaz".

* Pressed Home+Power.

* Screenshot+Power Menu happened.

* Exited Power Menu.

* Pressed Home+Power again.

* Nothing happened.

* Saved log and... well here we are.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
Okay thanks, will have a look at this.
[Xposed Framework Modules] Ninolina:
[MENTION=3147360]dk_zero-cool[/MENTION]

with last few updates my default haptic feedback on keys that are not changed with your module is broken - not working. Last version that it worked is 3.0.2 (before you added -2) and it's the same with newest rc. Can you look at it? So after latest updates my default haptic feedback on buttons is not working but if I change them with your module the haptic is working. I am on TW - Galaxy S4 v4.3.

Thanks in advance. :)
[Xposed Framework Modules] themadproducer:
[MENTION=3147360]dk_zero-cool[/MENTION]

Used CATLOG to make this log.

Long press home button for screenshot action not working.
[Xposed Framework Modules] yurividal:
GREAT! Your new long press handler solves the issue with long press! Also, screenshot feature works just like stock! Perfect version in my opinion.

Thanks+!!

Galaxy S4 i9505 Stock Touchwiz ROM

---------- Post added at 11:10 AM ---------- Previous post was at 11:05 AM ----------

He mentioned that the module takes control over ALL the buttons. So, to have your feedback working again, just add the default stock actions to your buttons. It will work JUST LIKE stock, and will have haptic feedback. :good:
[Xposed Framework Modules] Ninolina:
Thank you for info. :) That worked! ;)
[Xposed Framework Modules] a.fontenele:
I've just tested the latest RC version and man... IT ROCKS!!!

The long pressing timeout could not be better! The Internal Handler made It ultra fast! And that is perfect! :thumbup:

The screenshot function addition is awesome! Now I can use the power button with double click to get a screenshot... :thumbup:

The only funny thing is that menu function for long pressing the menu key does not work. It only works as default. I mean, this is my previous setting:

Menu:

Click: Recent apps :thumbup:

Double click: Menu :thumbdown:

Long click: Menu :thumbdown:

Now...

Menu

Click: default :thumbup:

Double click: Recent apps :thumbup:

Long click: Recent apps :thumbup:
[Xposed Framework Modules] dk_zero-cool:
You mean that the menu pops up and then goes away again? At least that seams to be the issue on my device.

Yes there seams to be a few things left to deal with, also multi key seams to be having some issues in some cases.
[Xposed Framework Modules] yurividal:
Just something i would like to share:

Use the power key as Camera Button when camera app is running. It is awesome! The phone feels like a real camera. =D
[Xposed Framework Modules] a.fontenele:
No... In my case it just had the haptic feedback and no popup, no matter what app I'm using...

I always use the good practice of wiping your app data before setting it up again so that I avoid any conflict issues...

Man, I'm so happy with the changes you made so far though... :D
[Xposed Framework Modules] coolkaas:
dk_zero-cool I humbly remind (third and last time) I CAN'T find out 'Call' action :crying: only 'Call end' present. What happens? Through from 3.0.2 to 3.0.6rc.

'call' is only really used action for me. And it absent.

Do not know what logs or dbg-info I can get for resolve this issue. Please-please help me))
[Xposed Framework Modules] dk_zero-cool:
Yes, and just as great on the SGS3. First time I actually like the position of the Power Button. This button was actually the whole reason for starting this module, because I wanted to disable it.

I know that it is missing. This is because Call and Call End is going to be replaced by a merged action that will work as both depending on whether or not a call is currently active, the phone is ringing or no phone activity at all. But right now I have more pressing things to work out, like getting Click and Long Press to work as they should in all cases and fix the current custom actions so that they don't FC on some devices.
[Xposed Framework Modules] coolkaas:
Now I will silently sit and to wait. :) Thank for answer!

btw when I install 3.0.6 'clearly' I got a fc.

Good luck with evil bugs fighting.
[Xposed Framework Modules] dk_zero-cool:
The only errors in that log is from the NotificationPanel module. There is actually no output at all from Xposed Additions. Did you enable debug and rebooted the device?
[Xposed Framework Modules] dk_zero-cool:
Released 3.0.6 RC2

Removed the old handling of default long press

Improved the new handling of default long press

Fixed issues with long press and multi keys

Added Torch Action (You need a torch app that support broadcasts, most do and most custom ROM's has this by default)

Cleaned up some of the code

Any further issues with this version, enable debug, reboot and grab a log.
[Xposed Framework Modules] themadproducer:
[MENTION=3147360]dk_zero-cool[/MENTION]

Enabled debug and rebooted.

Get this....long press home for screen capture results in UI reboot. Disabling debug and rebooting stops the UI reboot issue. But unfortunately, this prevents me from getting a CatLog. Crazy eh?

Going to install the latest release and try again. Ics.

Update: same issue. Also, as I mentioned a while back, in ICS, if I long press a programmed key combo like home+power, or alternatively, if I do NOT program anything for the home button and I long press it, in both scenarios, I get the rapid fire machine gun of clicks. This is with the new method and latest release RC2. Sorry to sound negative, but at least with my ICS setup, it's all very temperamental.
[Xposed Framework Modules] wilflare:
[MENTION=3147360]dk_zero-cool[/MENTION] I haven't been following the thread much but having some issues with this on my Note 3 (4.3)

- my previous settings all got reset/deleted after the update

- Note 3 default setting on Power+Menu to screenshot no longer works :/

any ideas?
[Xposed Framework Modules] palmuse:
BT Keyboard

Interesting problem here. I have found that your module intercepts the keys from my bluetooth keyboard. Not all but some like the shift, control, etc. This is an issue for me as I type mostly with my BT keyboard.

Is it possible to have the module pass the default keycode unless of is actually modified? I know the module knows the code because it will let me add the shift button as a remap option. Even knows the right from the left. This opens a huge realm of additional remaps but I first need to be able to type normally. :)

Thanks for your efforts and time.
[Xposed Framework Modules] a.fontenele:
(Friendly advice)

Don't take me wrong buddy, but I think the best suggestion anyone could give you right now is to follow up on the thread. I can imagine how frustrating it is for [MENTION=3147360]dk_zero-cool[/MENTION] to answer the same questions over and over again. I'D HATE IT! He is working hard to make this perfect and if we focus on telling him about issues that haven't been told before, that would be certainly useful.

Anyway, he's aware of these issues. I myself, had them. So if you read you will find your answers...

;)
[Xposed Framework Modules] wilflare:
no offence taken! I understand. will probably catch-up on the thread when I can.

reading the past few replies shows that it's an issue he's looking into..

and the settings reset was probably due to a change in code/refresh

EDIT: hmm seems like I have to add the screenshot feature myself... but

I don't see that in my list of actions (is it a RC feature for now?)
[Xposed Framework Modules] themadproducer:
Yes, it's an RC feature.
[Xposed Framework Modules] yurividal:
Yes.
[Xposed Framework Modules] dk_zero-cool:
Well you could just tell your friends that this is the new machine gun feature in Android. But if you don't find it cool to have a machine gun Android device, I do think that I have already located the issue :)

About Screen Shot, I will need a log. Either a logcat app that writes directly to a file constantly, or from a Shell which will catch the error even if it reboots.

No. I cannot just check the current state of one single key as there could be a number of different multi key combos as well.

Maybe I can get it to ignore your keyboard, depending on what kind of flags it is sending. I will look at this at some point, but something like that is quite unstable. Ignoring something based on flags could potentially break a few custom ROM's that does not handle flags properly (cough cough ... Samsung )
[Xposed Framework Modules] sumasage:
I installed xposed addition and it fail to run. It said that I need to install xposedbridge. Where can I download xposedbridge? I went to the link in the OP Which lead to the xposed framework installer which I already installed. Please help. Thanks.
[Xposed Framework Modules] dk_zero-cool:
No it said that you should make sure that XposedBridge was installed (Which is done via Xposed Installer) and reboot the device. So if Xposed is already installed, then I would suggest you try the second thing. Modules are not apps, they act as part of the system which is injected during boot. So you must

ALWAYS

reboot your device when installing/updating modules. And also make sure that the module is enabled in Xposed Installer.
[Xposed Framework Modules] palmuse:
don't spend a lot of time on this unless you hear from others. i want to do some research on it. seems it would be a loss to block the bt keyboard potential. maybe block the bt keyboard as an optional switch for now.

i donated because i see huge potential in this app and respect your time and efforts. thanks
[Xposed Framework Modules] dk_zero-cool:
Yes a switch might be an idea, and yes there could be potential in having external keyboards go through. Don't have one to test with sadly, but in order for it to work proper, I guess default multi keys has to be fixed. But I find it strange that something like Shift? or other meta keys would be dispatched like that. Those are not really buttons but merely on/off switches that is used in combination with others. They should not act as regular buttons. But if this is the case, it is kind of a good thing. That means that they can be used to assign multi key options.
[Xposed Framework Modules] SLeePLatED:
it seem to be work fine on my Note 3
[Xposed Framework Modules] dk_zero-cool:
And RC3 is out

Fix a small issue with default long press (No more machine gun on some stock ROM's)

Added support for default combo keys like Android's Screenshot combo
[Xposed Framework Modules] wilflare:
I'm a little lost.

If Xposed Additions (Pro) is supposed to take over all the controls of keys

why do I NOT have to set the functions for my HOME key, POWER key (yet my HOME+POWER keys to screenshot function is disabled?)

4.3 on Note 3, using latest version (non-RC)
[Xposed Framework Modules] xXYoshiXx:
Great to see active development again. So far I used the module and it works well, but I have some requests for future updates.

- as long as shortcuts aren't supported make application launch possible on screen off (Tasker user)

- support for launching shortcuts

- more than two buttons for multi-keys, for example when using a hardware keyboard

- combination of different clicks, like double click followed by long click

The first two are important, the other two are just ideas. Thank you for taking on the development again.
[Xposed Framework Modules] dk_zero-cool:
Sorry but I have no idea what you are asking?

* say what?

* possible, but unclear on app vs shortcut?

* not sure that is possible, but I will check

* possible
[Xposed Framework Modules] wilflare:
my apologies.

I read back some pages and understood that Xposed Additions now intercepts all the functions of my keys.

this is why my press power+home to screenshot no longer works right?

I would have to manually set the function for it to work.

I'm just curious why I did not have to set the functions of my home and power keys to retain their default function (when the default function of my power+home key was removed)

hope I make better sense now
[Xposed Framework Modules] xXYoshiXx:
The problem I have as a heavy Tasker user with only application launching is that I need to export each task as a separate app. Using home screen shortcuts I can easily create a task in Tasker and assign it to a button, without exporting and installing. Another advantage I see is when I edit a task. Currently I need to export it and install it again, using a shortcut I only need to edit it in Tasker. Shortcuts would also allow to do a lot more things. When you would allow shortcuts along with app launching you don't even need a Tasker plugin, one could launch tasks via shortcut.
[Xposed Framework Modules] killoid:
[MENTION=3147360]dk_zero-cool[/MENTION] in v3.0.6 rc2,i've mapped my home button click action to be disabled while screen off. when i turn the screen off & within one second press the home button,the screen turns on! & moreover,pressing home+power button to screenshot doesn't work! using galaxy y duos,stock 2.3.6 rom.log attached.
[Xposed Framework Modules] dk_zero-cool:
Because I made it to act that way. And default power+home works RC3

Okay thanks, I will look at it

Press and click is not the same thing. Just disable both.

And home+power works in RC3
[Xposed Framework Modules] wilflare:
thanks for the clarification! haha was a little shocked when I updated the app a few days ago. had to reconfigure everything.

in any case, capacitative buttons such as menu and back would still not work during Screen Off with the new update right? As that is a limited of the firmware etc on Samsung?

Using Note 3
[Xposed Framework Modules] dk_zero-cool:
It's a kernel limitation. With a specific configured kernel they could work.
[Xposed Framework Modules] flexxoo:
Last update takes haptic feedback for back and menu button in note 3, no longer works
[Xposed Framework Modules] dk_zero-cool:
Last update has no changes that affects how haptic is controlled. Note 3 and SGS3/4 is already known to have haptic issues, which is why it can be forced from your key configuration in the app. Just add and select the key and then check the preference "Force Haptic Feedback".
[Xposed Framework Modules] killoid:
yet it doesn't work on GB! :confused:
[Xposed Framework Modules] dk_zero-cool:
Gingerbread does not have this combo. It did not even support screenshot at all until 2.3.4 and the combo, I think, was added in 4.0
[Xposed Framework Modules] killoid:
no i have not mapped it by your module but it was by default screenshot taking method of galaxy y duos which is broken after installing latest version! all was okk in v2.3.8.