yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] dk_zero-cool:
Really? Then that must be a Samsung feature, cause even in the official 2.3.6 source codes, there is no such feature.

Well I will look at it, I myself have a regular Galaxy Y with stock firmware that I can test with. The combo should be "Home+Power"?
[Xposed Framework Modules] dk_zero-cool:
Next official release is out. It has been named 3.1.0 instead of 3.0.6 due to large changes, especially the long press handling part.

For those already using RC3, there is only two changes made

Added the missing CALL code in actions

Added option in each key config to use a key as a call button. This means that the button will use your regular defined click action, unless the phone is ringing or when having an ongoing call. In those two cases the key will be used as CALL and ENDCALL depending on the current phone state to either hangup or pickup phone calls.
[Xposed Framework Modules] killoid:
yeah it's samsung stock firmware feature. yup it is. :) maybe u can check this thread too.

link→ http://xdaforums.com/showthread.php?t=2273451
[Xposed Framework Modules] dk_zero-cool:
Not sure what version of the app you are running, but with latest official and RC version, it is working just fine on my Galaxy Y. Remember that you need to reboot after updating modules.
[Xposed Framework Modules] killoid:
strange! i reboot everytime i update my modules. & i double check everything. i've now disabled the module & screenshot function is working again! :confused:

EDIT: seems like it is taking longer pressing than usually it took to take screenshot via home+power.sometimes recent app list pops up due to long pressing of home screen.i've disabled long pressing action of home & power button so that recent app list or power menu dont appear while taking screenshots but sometimes pressing the two buttons simultenously pops up the recent app list! very strange! :silly: hope you will find some workaround to fix these issues.
[Xposed Framework Modules] blackbearblanc:
Hi. Not sure if I'm doing things correct.

Was hoping to remap Power button or Power button Long Press to open Camera.

But I dont see that option. Only Turn phone off and screen on and off.

And, that ruined screenshot action by power and volume down.

Im on Nexus 5 4.4.2.

Rebooted every time
[Xposed Framework Modules] themadproducer:
Yes, I agree,.. Lots of practical uses for "shortcuts" or "Activities".

- launch Tasker shortcuts (huge bonus)

- launch shortcuts that we already have, that do various things like eg... flashlight, halo window app launch (xhalo), Greenify... The list goes on.
[Xposed Framework Modules] cottino:
With Xposed Addition 3.1.0 my Galaxy Note 3 long press home button doesn't open task manager anymore.

Screenshot is OK
[Xposed Framework Modules] blackbearblanc:
Ah Maybe I need pro version. Ill try now
[Xposed Framework Modules] thereald:
[MENTION=3147360]dk_zero-cool[/MENTION]

The new update now works but the actions awake for remapped button are gone (long press, double click & default click)

Why did you removed them?

I'm glad that I have an TB Backup from the old version (2.3.8), cause the new version is useless for me without the above mentioned actions, I also own the pro version...
[Xposed Framework Modules] sheraro:
version 3.1.0 :

- kill apps working again thanks !

- home key still wake phone on screen off even after disabling it

- gamepad still not working inside games and emulators ( it works outside them though :silly: )

I pressed lot of buttons and attached a log (enabled debug and rebooted)
[Xposed Framework Modules] LuuchoRocha:
I have the same problem with my all hardware keys (vol+, vol-) after set "disable" at all options with screen off.

I generally use the long press of the vol buttons to skip tracks but with the last version they wake up the phone and don't do the selected action...

I hope you can fix this issue. Thanks!!
[Xposed Framework Modules] themadproducer:
@dk_zero-cool

Holy Butternut Squash Batman!!!

I have to admit something. I was losing faith...especially being on ICS and not being able to produce a logcat the EASY way. I had reverted back to 2.3.8.

BUT....today I installed 3.1.0 and....wow....it feels like a new app. 9 out of 10 things are working...and they work faster and smoother than ever!!!

Killer update...at least for me.

Thanks so much and hats off to you dk_zero-cool.

Now here's the nitty gritty.

:( Kill Foreground app seems to still kill more than just the current foreground visible app. Example...it kills "Widget Locker". Also, for future reference, is there a way to add "Widget Locker" to a black list...so that it can't EVER get killed...even if it's in the foreground...especially when the screen turns on in one's pocket?

:( Volume keys now WAKE up device by default...as a previous user has mentioned. I too use "long press track skip" via another module which no longer functions since the screen turns on. So is there a way to allow user to NOT HOOK into the volume rocker keys? Or simply prevent the screen from turning on?

The Good

- stock menu+pwr button screenshot works perfect! No need to program it. :good:

- Short and medium press delay times are FAST! :good:

- no more machine gun! :good: I will miss it...lol. ;)

Overall, it feels really solid...no more clumsy and finicky behavior.
[Xposed Framework Modules] dk_zero-cool:
I have not removed anything, I have added a lot of new stuff. I have no idea what you are missing, don't quite understand, but the UI has changed, so have a better look and you will find everything is still there plus more.

There is nothing in that log related to the module?

Hmm this could only be caused by one thing and that should not be causing this issue. Do you use a Samsung ROM? It's mostly Samsung that messes up Android's default behavior.

Glad that it is finally working for you. I will have another look at the Kill Apps action, but I am having a hard time reproducing this issue. I have tried having several different apps opened, and I cannot get it to kill anything else than the outer most foreground app. Not one single time have it killed anything else other than what I wanted it to. Do you have this issue with every app, or just some specific once?
[Xposed Framework Modules] themadproducer:
[MENTION=3147360]dk_zero-cool[/MENTION]

Kill Foreground app...

I know for certain that Widget Locker gets killed no matter what. I will do some testing later today to see if other apps are getting killed too. As an example...I currently use a GMD gesture swipe to kill foreground app with no issues.

Re Volume wake...

Does the volume wake your device(s)?

Was that intended?

Can it be reverted or preset to not do this?
[Xposed Framework Modules] elevengu:
Thanks dk_zero-cool for fixing the settings to save properly in 3.0.4! :highfive:

Unfortunately, 3.1.0 has a major regression with the new long press handler. I am certain this worked with 3.0.4. When setting the long press for a given key to the original click for that key, the setting is ignored and the original long press (often nothing) is activated instead.

Example: I have my Home button click set to Power and long press to Power Menu. Both work perfectly. But it would be impossible to map long press Home to Home. In that case, long press Home would bring up Recent Applications instead (Samsung's default mapping).

I'm assuming what happens is something like Xposed Additions passes through the key unmapped. The same thing is probably happening for click too, but there's no problem there since you get exactly what you want anyway (e.g., Home for Home).

If there is no easy fix for this, I would be content with a workaround to select old or new long press handler, as was apparently the option during 3.0.6 RC.

Here's another issue I just wanted your clarification about whether this is a bug or a feature. On 2.x, Global User Rotation allowed me to rotate into all 4 orientations at any time. I would only use 2 of the 4, but this was acceptable. On 3.x, Global User Rotation now only rotates into 2 of the 4 orientations. My problem is, they aren't the 2 that I want. :silly: Anyway, all I wanted to know is if this is intended or expected behavior. Thanks!
[Xposed Framework Modules] egingell:
Looking through your code (for an older version, anyway), it appears you are killing by process ID. Multiple apps can share the same process. Have you thought about using the command line? E.g. am force-stop PACKAGENAME

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
There should be no volume wake unless you configure it to be. I think there is a problem in the pokeActivity on some ROM's. It is meant to start the CPU in case it is sleeping (Some devices do not react on buttons if that is the case). But it seams that some ROM's has changed this behavior to force the screen on. So instead of a partial wakelock, it sets a full one instead.

Xposed Additions does not parse anything until it is clear what action to take. I just tested it and you are right. But this is not a bug in my module. This is android changing the KeyEvent and automatically adding a repeat flag, because the native handler has registered the key being parsed through multiple times. Luckily I think I know how to stop it from interfering, and I will check that out tomorrow.

This is a bug, there should be 4 and there is going to be 4 :)
[Xposed Framework Modules] themadproducer:
[MENTION=3147360]dk_zero-cool[/MENTION]

Foreground kill...

Another quick test shows that Tasker and Widget Locker are getting killed...maybe more?

Volume Wake...

I read your explanation. Thx.

So is it something you can adjust or do you have a recommendation?

Settings?

---------- Post added at 04:18 PM ---------- Previous post was at 03:55 PM ----------

@dk_zero-cool

Had to temporarily revert back to X.A.2.3.8... because I use the Volume rocker every day for music with screen off.

But an interesting observation.

I also have a NEXT/PREVIOUS song widget in my Widget Locker lock screen, and they become unusable with X.A.3.1.0. They work fine reverting back to X.A.2.3.8.

So do you think we could have a USER OPTION to disable the HOOKING of the volume rocker...or however it is done in 2.3.8? At least temporarily? ;)

Please! :D
[Xposed Framework Modules] wilflare:
[MENTION=3147360]dk_zero-cool[/MENTION]

updated to the latest version!

got my default power+home function (Screenshot) back!

but trying to insert any two keys and enter their conditions menu causes FCs :/

is there a default Torch function for Note 3?

(can we ask for recommendations here!)
[Xposed Framework Modules] egingell:
If it's TouchWiz, it might have a torch option built in.

Try this from the command prompt as root:

am start "com.android.settings.torchlight.TorchlightSettings"

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] applesandsynths:
FC on 2 key button remaps

Also experiencing force closes on 3.1.0 when trying to create any two button combos on a Galaxy Note 3 running 4.3
[Xposed Framework Modules] oilfighter:
I think I found a bug.

I have a Samsung Note 3.

I noticed that you can't program a long press to perform the original function of the key.

Example: You can't program Menu key's long press to perform the "Menu" function, or have long press "back" key to perform "Back"

My usage is to map both menu and back key's short press to perform "back", and long press to perform "menu"

You can't assign "menu" function to the long press of the menu key, but works on the back key.

I'm on the latest version of xposed additions.
[Xposed Framework Modules] egingell:
Same on the SGS4 JB 4.2.2 Stock MF9.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
So affected applications are those running in the background like Takser service and such?

Thanks for the observation, got the same issue today which is strange since it was working just fine yesterday on the same version. I will see to that it is fixed.

This is known. Not really sure if this is a bug and if so, if this is the module or Android. The problem is that Android is correcting and auto changing the key events in certain circumstances. Bug or not, it's a wrong behavior and I am working on correcting it.
[Xposed Framework Modules] egingell:
I believe this to be an accurate statement.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
This is why I have not found any issues when testing this, I did not test background service since the action should be made to only affect foreground applications. At least now I know what type of apps I can use for testing.
[Xposed Framework Modules] oilfighter:
It used to work perfect on 3.0.4. I updated to latest xposed additions today for the haptic feedback, and it broke the keymap.

Either way, I can't do 1 handed use on a device as big as the Note 3 without your app, so for now I'll just long press the back key as menu button. Keep up the GREAT work!
[Xposed Framework Modules] dk_zero-cool:
I know it worked on 3.0.4 because that one did not handle long press the same way. I know what the issue is, so it should take long to fix it.
[Xposed Framework Modules] egingell:
I can list several apps: Tasker, Facebook, Med Helper, Google+, MB Notifications, Alarm Droid, Tapatalk... I have an app that restarts apps after they're killed and those are the repeat offenders. Keep Running, the app I alluded to previously, however, does not get killed. I know this because it restarts said apps as expected.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
At least it does not kill the app that restarts the others :)
[Xposed Framework Modules] themadproducer:
Quick off topic question...have you used the RESIDENT feature in the module named APP SETTINGS? If yes, how would you compare it to KEEP RUNNING? I was surprised that after Xposed Additions killed Tasker and Widget Locker...that App Settings did not restart them for me.
[Xposed Framework Modules] egingell:
I have used that feature of App Settings. Apps still get killed by the system. They're just lower in the queue.

Keep Running just restarts apps. It's not without its flaws, but it gets the job done.

Until I figure out what's leaking RAM, I have to ensure that certain apps stay running.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] blackbearblanc:
Screens from play Store has a different layout than the one I use. Black and orange..

Did I download the wrong one? Or is that older screens used?
[Xposed Framework Modules] wruster:
task manager long press home button doesn't work for me too
[Xposed Framework Modules] coolkaas:
dk_zero-cool

(thanks for CALL button!)

so if all work I get you next idea to realize it in future))

to add more (personalized) _contexts_ for buttons.

now we have 3 contexts (conditions in your notation): screen on, screen off and lock screen. I offer to add conditions depends on foreground app! ))

okay, this result settings to branchy tree)) but we'll be able to tune 'personal' per-application keys reaction. eg in Camera long Home is shot, in Call is answer a call, etc.

what you say about this?

all this will significantly expand use of 2-3 hardware buttons in our modern devices.

---

an idea to run activities I advise to add a half-year ago)) (it is a pity only in the pro, which I cant buy as market-less))).

direct activities control is good thing.

(again thanks for all what you do!)
[Xposed Framework Modules] dk_zero-cool:
The app uses default ROM layout, I just have a different ROM theme than you ;)

I added that to Pro at the same time I added App Launch
[Xposed Framework Modules] applesandsynths:
Menu key remapping not working

Hey hey,

Just noticed that on my Note 3 (4.3) using Xposed Additons 3.1.0, I am not able to remap the menu key. If I try remapping it to a long press of the Menu key, nothing happens asides from haptic feedback. If I try remapping it to a doubletap of the Menu key, it launches Google Now search for some reason.

Just wanted to give a heads up.

Thanks!
[Xposed Framework Modules] dk_zero-cool:
New version is out which should hopefully fix some issues with long press, multi key setup and the kill application action. Also the rotation actions has been changed to instead toggle between 0/90 and 0/270 which makes it easier to toggle between landscape and portrait.
[Xposed Framework Modules] cottino:
Hi dk_zero-cool,

I bought Pro version but I can't use Application Launch function.

When Xposed Additions load all my app crashes at 60-70% :crying:
[Xposed Framework Modules] LuuchoRocha:
volume wake

Thanks for your explanation, and yes, I have a Samsung ROM... But the issue of the wake up's doesn't appear in 2.3.8 version...

Because that, I go back to older version. I think it's solutionable... BTW, I used GravityBox to remap vol keys and there is no wake up, works fine..
[Xposed Framework Modules] egingell:
Kill Foreground App seems to be working properly.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
I know. Still working on that, but not sure about the cause and fix.

What works in other modules is of no use. I change things to fix issues people are having, like some devices not reacting to key events when the device sleep. In your case this fix causes the display to wake. This is an error from Samsung. GravityBox does not wake the device because it iether dont have this fix, wich means that others might have some issues with that module, or it uses the same fix that I used before. It is not as good as the current fix, but thanks to Samsung it seams that I will have to re-add it.
[Xposed Framework Modules] oilfighter:
The Dev knows, he updated the app today, and fixed that issue.
[Xposed Framework Modules] themadproducer:
[MENTION=3147360]dk_zero-cool[/MENTION]

Kill Foreground app...seems to be working without killing Tasker and Widget Locker etc. Thank you. One step closer to perfection good man. :good: Did I ask you....is it possible to have a blacklist or a way of preventing this kill action, when Widget Locker or similar, is in the foreground?

Volume key wake...if/when you end up finding a solution to the Samsung/volume thing, I will be able to finally use this module as my daily driver.

Home long press...maybe a glitch or quirk...but now when I long press Home button, without programming it....it vibrates twice rather than once. Not a big deal. Just reporting it.
[Xposed Framework Modules] applesandsynths:
!

Thanks for the heads up!
[Xposed Framework Modules] thereald:
I need to apologize by myself, the whole UI changes totally confused me ;)

Everything fine now, thanks a lot!
[Xposed Framework Modules] Ara Seferian:
I loveeee this module it's the best ever.

I bought a pro version but the only one bug to report is that sometimes I cant wake the device when the screen is off I remapped to wake by focus button but when the screen is off its not responding to my click its taking some time and its affecting the power button too which is unresponsive too but I can live with that.

Just reporting :p

And Thank you for this great module!

Sent from my LT26i
[Xposed Framework Modules] Ranomez:
[MENTION=3147360]dk_zero-cool[/MENTION] I have tested all the latest versions and they still don't work on my HTC One X+ with CM11 settings still getting lost after reboot, only have lib and cache folders in the data folder of the app, Recents Key still not working properly, would xposed's debug.log help cause the normal log will have no data even if I enable the debug options in the module cause as soon as I reboot the phone all the module's settings get lost, any way I can help you find the cause, really want to use the module, and I still wonder why the 2.3.8 version is the last one that works properly?
[Xposed Framework Modules] themadproducer:
[MENTION=2621033]Ranomez[/MENTION]

I feel for yah and hope it gets sorted out. :crying: dk_zero-cool does give a couple of brief explanations in recent posts (especially addressed to me) about the newer method he uses. Granted, there are bugs to work out, but it is a superior method. Unfortunate in your case that it totally fails...for now anyway. I too am on 2.3.8 but only until the volume wake issue gets sorted.
[Xposed Framework Modules] elevengu:
dk_zero-cool, you are the man! Everything works perfectly for me now! :victory:
[Xposed Framework Modules] nitephlight:
app list could use a sort by name unless its just my screwy device lol.
[Xposed Framework Modules] themadproducer:
Known issue...on the to do list. ;)
[Xposed Framework Modules] egingell:
It actually is sorted, but by package name rather than friendly name.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] nitephlight:
if that were true them all the htc apps would group no? good to here its on the list!

---------- Post added at 11:06 PM ---------- Previous post was at 11:06 PM ----------
[Xposed Framework Modules] egingell:
I didn't even notice. Maybe mine's not as sorted as I thought.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
Hmm it should be sorting by App Label. I will have a look.

It seams that the + in HTC One X+ is only providing + problems, cause again I cannot reproduce any of these issues on my regular HTC One X.

I have attached a debug version of the app in this post. It has debug enabled by default so that you can create some logs of these issues
[Xposed Framework Modules] inancatil:
Will this app compatible with tasker? It will be good if we can trigger task with button combination

SM-N9005 cihazımdan Tapatalk kullanılarak gönderildi
[Xposed Framework Modules] nimrodity:
sleep still changes my volume on long press
[Xposed Framework Modules] dk_zero-cool:
You updated the module to Beta3?

Then you rebooted to make the new changes take effect?
[Xposed Framework Modules] flexxoo:
It doesn't work anymore! !!!
[Xposed Framework Modules] dk_zero-cool:
That is not very useful info
[Xposed Framework Modules] nimrodity:
sorry, didn't reboot, you're right it works
[Xposed Framework Modules] flexxoo:
Im sorry, I updated to the beta and now all the options that I had before are not working and yes I did reboot the phone!!!!
[Xposed Framework Modules] squeezed:
Same here, updated to beta, enabled in Xposed Installer, rebooted! All buttons ineffective!
[Xposed Framework Modules] favero_:
Just intalled it. I'll reboot and see if it works.

A suggestion though: do you think it's possible to add a feature to remap the hardware buttons, for example transform the power button in the camera one, or something like that?

Thanks!
[Xposed Framework Modules] tennyleaz:
I did enable your module in xposed framework.

This is a list of my files in /sysrem/usr/keylayout

Hope this will help.
[Xposed Framework Modules] dk_zero-cool:
You all might want to open up the app and actually enable some of the buttons before expecting them to work? By default they are all set at System Default.
[Xposed Framework Modules] tennyleaz:
I did enableed both home and vol buttons, normal press or long press.

All not working for me.
[Xposed Framework Modules] dk_zero-cool:
Okay, then try enabling a long press sleep button and see if that works, if so, then your device does not send press announcement while the screen if off in which case you need some changes to the keylayout files.
[Xposed Framework Modules] dk_zero-cool:
Beta 4 is out

Should fix the display not turning on issue

Added ICS and Gingerbread support, so it should now support anything from 2.3 and up

Removed the current button controls and added full button re-map

The package name (The 'com.xxx.xxx' name, not the Label) however was changed a bit due to the new support testing, so this package will not replace the current installed version, but install it along side it. You will need to manually remove the current version if you already have one installed.

Also note that due to major differences between Gingerbread, ICS and Jellybean (Their undocumented System Classes), GB and ICS does not at this time, support the USB Plug Controls (It will come). The Button Re-map controls however is working fine in both.