yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] dk_zero-cool:
Well one problem. It seams that Samsung skipped 4.2 on the SGS3 and went strait from 4.1 to 4.3, so I cannot find any 4.2 Wiz for it. Does any older module versions work on your 4.2? The beta for an example? or 2.x?

Or it could have been another version of the player? I just tested this on Player Pro and it is working fine. What about if the screen is on?
[Xposed Framework Modules] killoid:
no i am using the author's original v1.1 on my GB & it hasn't been updated for years! it works flawlessly when screen on. btw i noticed a strange behavior, when i am on another app, turned the screen off & tried to play pressing home button it works! same thing is with media next & previous while screen off. & i have configured them on long press respectively for volume down & up button.
[Xposed Framework Modules] egingell:
Every 2.x version works. I'm using 2.3.8 now with no issues... other than not being able to set Power click to open Screen off and Lock. :)

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
http://developer.android.com/training/managing-audio/volume-playback.html

That is how applications use the media buttons. There are many ways to implement this into the actual application activities, I don't know when your player starts and stops the listeners, so I would try and download another player and see if that produces the same issues. The log shows your media key being dispatched successfully. What happens after that is not a part of the module, that part is controlled by the ROM and then by the music player. One of those might have a problem.

Could you try the Beta ? It has debug enabled which means that it will produce log entries of every key event. A log would help explain the issue, especially since I can't get a 4.2 Wiz ROM myself to test this on.
[Xposed Framework Modules] egingell:
Aside from not saving the settings, that one actually works.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] killoid:
tried it with miui music player & jetaudio but same thing,these also used to work on v2.3.8.
[Xposed Framework Modules] dk_zero-cool:
Well then at least it is not hopeless and I can check the changes between those two. I will try to locate the possible issue and correct it along with this not saving preference issue. Then I can upload a version with logs enabled which will make it easier to debug if the issue is still existing.

EDIT:

I have uploaded an attachment below which should fix the not saving config issue, and hopefully your click issue on Wiz 4.2

I will try to test this player against different Android versions. But right now I am more interested in some of the more pressing issues.
[Xposed Framework Modules] egingell:
So far so good. Now if only the app list were alphabetized... :p

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] killoid:
for now i'll go back to v2.3.8 which was last stable version for me. hope u'll hunt down the pesky bugs! :good:
[Xposed Framework Modules] raffles496:
i just install the new version, and after reboot, the settings is not deleted. EXCELLENT

but in my case, the quickbutton (included in others smartphones LG) no work fine. in old versions (2.x.x) if work good. sorry i know, i'm boring you with this problem :( .

Sorry for my bad English and greetings from Mexico.

Enviado desde mi LG-P714 mediante Tapatalk
[Xposed Framework Modules] dk_zero-cool:
Great, that was the two major once. Well the app list has a few things that I need to deal with. The icons is sometimes to big and it seams to be crashing if there is to many apps installed.
[Xposed Framework Modules] egingell:
Oddly enough, I only see abnormal icon sizes on my S2.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] xdapao3:
After some use I realized that this longer "short" delay settings on 3.0.2-2 is a big issue to me (it really has a huge impact in actual use) and went back to 2.3.8.

On my Note II (N7100) running rooted stock 4.1.2 + Nova Prime launcher (which can itself assign additional actions to buttons) + Firefox (as a secondary browser) I have NO ISSUES whatsoever with 2.3.8 and with the long press delay setting on "SHORT". The only action invoked by long pressing the Note's 2 capacitive buttons is always and only the one I set in Additions and can't understand why would you care about non-standard use of long presses on some 3rd party app.

At least please give us the option (maybe put a disclaimer or something on this "shortest" delay setting).

I have set Additions like this:

- Menu button single press is Menu (so nothing changed here)

- Menu button long press is Recent Apps

- Back button single press is Back (so nothing changed here)

- Back button long press is Home

- Home button single press is Home (so nothing changed here)

- Home button long press is Call

So really I have only changed the long press actions of the physical home button and the 2 capacitive ones flanking it. I don't need anything else and I could trim the changes down to one single killer setting which is what I really, "desperately", need: to be able to set the long press action of the Menu button to Recent Apps.

This really has meant a huge improvement in the way I can use my Note II (much better than the LMT pie that I was relying on) and I absolutely LOVE IT. I have bought the Pro version just as a thank you although I don't need any Pro version feature (the only other thing I would really like is to have a "Go to last used app" action in order to be able to quickly switch between the 2 most recent used apps).

This is so much of a biggie to me that I was going to replace my G Pad 8.3 with the Samsung Tab Pro 10.1 instead of the Note 10.1 2014 (which is what I really want) just because in the new Tab Pro Samsung has finally swapped the STUPID Menu button with the Recent app button!! Your module made me reconsider my purchase and I am trying to check if it works well on the Note 10.1 2014 (BTW does anyone know??) so I can get it instead of the Tab Pro... that's how much your awesome module means to me!!
[Xposed Framework Modules] a.fontenele:
Screen Capture not working

dk_zero-cool

Tks a lot for your hard work on making this module work smoothly. I made sure to buy the pro version mostly because you deserved it.

Aside from the preferences not being saved, the screen capture does not work after the latest update either.

---------- Post added at 11:26 AM ---------- Previous post was at 10:35 AM ----------

That would be simply perfect to have too... I'd assign "last used app" as single click and Recent Apps would be the double click...

+1
[Xposed Framework Modules] MiZoSpaDe:
I'm using stock 4.0.4 rom..also this issue happens to be with the recent apps key only. as i tried the home key and worked just fine ..
[Xposed Framework Modules] nacron:
Cool, I was having a weird issue today where both my menu and back button lost haptic feedback, restarting didn't change it. I think the autoupdate from the old version through play store messed up the settings as there no buttons assigned anymore in app but the button actions still worked. I turned off the module and restarted and then reenabled and restarted and then remade action to show search on menu long press. I like the new button reassignment menus, more logical. Just a suggestion, in this screen, maybe a suggestion or prompt to check off the item to choose the action. I was kinda confused what to do this point.

haptic feedback works on button reassignment on the note 3 now. Thanks for your continued development! You have a new pro user.
[Xposed Framework Modules] churrolakra:
hello..

forceclose to me when I try to add condition to a button. BUilding application list...then force close:(

I am on omega 4.4.2 touchwiz I9500.. previous version worked perfect..

i am really exited to try the new features.. help !!

:) thanks a lot
[Xposed Framework Modules] Ranomez:
Updated to latest version and it keeps loosing my config after reboot and also the recents key normal click does not work anymore (when set by an other way) and if set by xposed additions clicking it just does a double click, I am on cm11.
[Xposed Framework Modules] dk_zero-cool:
The 2.x version worked the way it did because it was possible with so few options. With the addition options in 3.x, I had to change a lot of the behavior. Otherwise it would simply use to many resources and you would have have about 1 second delay on each button click (Now that would have been annoying). I have said this before and now I am going to say it again. I work with programming, not magic. No mater how much I would love to, I cannot go beyond the tools that I have available. The only way to make a 100% integrated handler, is to built it into a ROM and build the entire ROM from source. Xposed can only execute custom code before and after the original code. I cannot in any way change the original code, only manipulate it as far as parameters and results allow me to.

That said, I have never claimed that this was the end solution. I have an idea in my head about how this module should behave, and I am a damn stubborn son of a *****. So I am gonna make this module act as I want it to, and I don't care how white I am gonna get from the lack of sun light. But for now, I have more important things to fix in the module. So I will work on the long press issue once those things are fixed.

Try the test version one or two pages back. It fixed the issue for others. It is added as an attachment to one of the last posts.

The config from 2.x was not compatible with the new version, so I changed the name of the file to make sure the new version would not try to use anything from the old one. It still worked because the module part is added at boot to the core system and reinstalling the app itself will not affect the core parts without a reboot. That is why you always has to reboot when updating Xposed Modules.
[Xposed Framework Modules] xdapao3:
:good: Maybe an idea would be to make a "light" version of the module then..?

I mean, I think lots of people would be happy to just being able to assign some different basic actions to the normal control buttons of our devices.

Besides bug fixing if it all works well I really don't need anything else if adding features would mean prejudicing how well that core function works.

I am going to stick to the 2.3.8 version and all I want (and would be willing to support) is that it continues to work like it does now once I update my Note II to 4.3 and (probably) to KitKat later on once it's released.

Not to talk about the fact that I hope that 2.3.8 works on the Note 10.1 2014 as well as it does on my Note II!! DOES ANYBODY KNOW? :fingers-crossed:

BTW, the ONLY (very) trivial issue I have with 2.3.8 is that pressing the capacitive buttons they don't light up anymore (only pressing the home button when the screen is off and long pressing the menu button and invoking the recent apps action do). Also, if I set a non-standard action for the capacitive buttons as their standard action (which I don't need and haven't done), they don't trigger the haptic and audible feedback (I have both of them enabled in the general settings).

OK, got it... Still love your module (it has made using my Note II so much better!) and still happy to have bought the Pro version just to support it.

At this point I just hope 2.3.8 will continue to work on my Note II like it does now through the next software updates and I hope it works on the Note 10.1 2014 as well (or, as crazy as it may sound, I will have to get the TabPro instead just because of this :eek:).
[Xposed Framework Modules] coolkaas:
can't find 'Call' action, only 'Call end' presents. :)

at 2.3.8 all ok.

os 2.3.4 stock sony ericsson.

is pro version allow to run app with screen off?
[Xposed Framework Modules] churrolakra:
I attach catlog, hope it is usefull
[Xposed Framework Modules] dk_zero-cool:
No. The screen is off. Is there a reason for launching apps on an inactive device? Cause I could add it, but just can't see why.

File not found. But I have already made a new way of handling the application list. Hopefully this will fix the issue. Just have a few more tweaks to sort out, and then it's go time. Some of the minor things will have to wait a bit, I can't have a release where clicks does not work, app loading crashes and settings are not saved.
[Xposed Framework Modules] dk_zero-cool:
Okay new release is out that should hopefully fix the most important issues.
[Xposed Framework Modules] yurividal:
Thank you! Just tested it, and seems all issues reported were fixed. But, i rolled back to 2.3.8 because the long press "short" time thing was bothering me a lot.

Is that your main goal now that you fixed all the issues on 3.0.4??
[Xposed Framework Modules] Walter.White:
[MENTION=3147360]dk_zero-cool[/MENTION] I have the pro version. But I was wondering if the following feature is possible??

Currently there are 4 options as to when Re-map keys:- 1. Screen ON 2. Screen OFF 3. Lockscreen 4. In particular Application

But with #4 it looks like that application has to be in foreground for the re-map to work...Is there anyway to re-map particular keys regardless if that particular application is in foreground or background (as long as its running).???

For instance I have re-mapped Long press Volume Up key to media next when Pandora is On but that setting only works if I'm actually in Pandora app but if Pandora is playing music in background that setting wont work. :(
[Xposed Framework Modules] dk_zero-cool:
Everything is possible, but this will not become an option. The module has to configure your events on every single press of a button. As of now, this means each time you press a button down, the module has to check the screen state, lock screen state, which app is at the top and then check configuration for each of these things for not to mention the work the system does when it dispatches the event. Every single time you press a button. What you want would start producing so much lag on each press that you would have to enable a screen saver to watch while your key events get's done processing. We are not just talking about one app here. The module would have to check all running apps and then it would have to find out which of these would have priority over others. Remember, you can assign more than just one application as a condition.

However, I have been working on the idea of making a Tasker plugin, if I get the time. All configurations are handled via a system service, so it would be possible to have a plugin for Tasker that could change configrations. But again, if I get time. It would first require me to learn how it's plugins work.
[Xposed Framework Modules] Walter.White:
Gotcha. This app is great as it is. I was just throwing some ideas around to make it even better..
[Xposed Framework Modules] sheraro:
xperia play with GB 2.3.7 here, about launching an app while screen is off it could be helpful if we want to launch the camera on the go ;)

I also would have to address some concerns for future updates :

in 2.3.8 version , remapping back key results in deactivating all gamepad buttons minus d-pad , so I wasn't remapping it and all was ok , but with this version , just having this module activated without even remapping anything deactivate the gamepad !

I miss the checkbox to activate/deactivate the remap of a key , it was convenient, now we have to delete the remapping to deactivate it ...

yes the foreground/background thing , but can you implement this scenario : if an app is LAUNCHED activate its related remapping AND don't change it UNTIL another app is launched witch have its own remapping ... (I think it will speed up calculus a little by not always checking the screen state)

EDIT : 4 - while screen off , remapping home to play/pause music (poweramp) is working but it will wake the phone in the same moment , witch wasn't the case of v2.3.8

But I think and correct me if I'm wrong it's impossible to know witch app is actually launched in android as I searched a little ...
[Xposed Framework Modules] doomboy1000:
Just tried version 3.0.4, on an ICS 4.0.4 Touchwiz ROM (mostly stock, it's deodexed and zip-aligned but I don't think that's any cause for problems here).

Module disabled (default phone behavior):

STRONG vibration, triggered UPON pressing of the keys (my phone has hardware keys)

Module enabled:

WEAK vibration, triggered on RELEASE of a key

Anyone else getting this? FANTASTIC Xposed module, by the way!
[Xposed Framework Modules] pratik_vartak:
Just install new version 3.0.2-2

Before this M using 2.3

m on stock deodex rom on galaxy core duos

now m having some problems

1st one is my home button which is physical key not working when screen is off. As its default action is turn on d screen when screen is off

2nd one is its take much more time to force stop fourground as any key remapped for it.(compair to previous version)

Config: i have just config menu key for force stop foreground app
[Xposed Framework Modules] egingell:
The latest is 3.0.4.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
Why concerned? Go to the module, add the home key, add screen of condition, go to condition and set click to Power.

Android's internal handler is never used as primary in this version, so it has no power control anymore. My module will toggle the screen on/off when the power key is clicked, other buttons needs to be configured.
[Xposed Framework Modules] nacron:
Was having issues with lag between pressing home or power and the screen coming back on, pinpointed it to gravity box. Set key map in gravity box all back to default seems to have fixed that. A bug I noticed is that I can no longer take screenshots by using home and power on my Galaxy Note 3. Used to work on the older release
[Xposed Framework Modules] egingell:
Sounds like we need a screenshot function to explicitly set.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
Yes we do, and one is already scheduled to arrive at some point :)
[Xposed Framework Modules] egingell:
I just use the side-of-hand gesture myself - makes me feel like I'm scanning the screen with my hand :p, but cool nonetheless.

P.S. I don't know if anybody figured this out in the new UI, but you can add multi-key combos by hitting the combo just as you would any other single-key when adding keys. I figured it out by accident. lol

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] nacron:
Tired adding long press home and power with a random action to see if it works but it just turns the screen off

Also, is there any way to add the voice search action so that it launches Google now voice search? I tried looking through apps but the only thing I can do is bring up Google now. Using gravity box and voice search is an action you can choose so I have that as double home tap
[Xposed Framework Modules] egingell:
I did long-press power+home and long-press home+power and they both worked as expected. It was a paid feature before.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
Multi-key needs the pro package installed. And with that package you also get Application launch for your second question.

Also, don't report bugs if you have other modules messing with keys, that will create conflict so any reports will be useless unless you tried without the other.
[Xposed Framework Modules] egingell:
For the record, there's no conflict with Xblast's Volume Key Cursor Control feature. :)

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] themadproducer:
Yup...just noticed a lot of the same stuff you guys just mentioned...incredible timing.

My observations...

Screenshot...

Without any button presets, I can no longer take the home+pwr key screen shot. So I suppose the button is hooked no matter what due to the workarounds and code juggling you mentioned recently? Adding the screenshot action to the list could definitely help for some of us.

Vibration...

Home button vibrates on single click even without any presets. Never preferred it vibrating on single click...because it has it's own REAL physical feedback. So the home button is hooked even if we are not changing it from stock?

Disabling the module is the only way I can prevent the above.
[Xposed Framework Modules] dk_zero-cool:
Yes, with the module enabled, the module will handle all keys. With the added features I needed more consistency. However, your home should not produce any vibration. Properly a setting in the key injection which triggers the original feedback when it should not.
[Xposed Framework Modules] Ranomez:
Updated to latest version (3.0.4) and it still does not keep the config after reboot on my phone and the recents key not working, what logs do you need?
[Xposed Framework Modules] killoid:
i am happy to report that new version is all okk with GB! previous issues have gone! yaay! but a tiny issue,in v2.3.8 the long press duration normal was ok but now it seems to take a bit longer time. i've set it to short with the new version,now it seems to be good! :)

p.s. i actually uninstalled prev ver. & installed it freshly after reboot,so no problem occured i think!
[Xposed Framework Modules] dk_zero-cool:
First of information about what device you use and what Android version. Second, I would need to know what permissions the file /data/data/com.spazedog.xposed.additionsgb/shared_pref/config.xml has (Via shell or a root explorer).

Now when you say Recent key, do you mean a key mapped to Recent Apps or an actual recent key on your device? In case of the first, I would need a logcat of you pressing that key.
[Xposed Framework Modules] kevin_1351:
I love your module but i still have one big problem. I have more than 800 apps, and even with the newest version, at 641 or something it just FCs. (When the app list is loading i mean)

So the issue still isn't fixed. Your app isn't the only one that has had this problem, but other devs have made it working, so I'm sure that it's just some cache size boundary or something that needs to be increased.

EDIT: Well I've tested it on my other note 3 now which has only 654 apps and still..... FC...

I'm sure it's easy to fix.
[Xposed Framework Modules] a.fontenele:
Wow! And I feel bad when I can't keep my application manifest to the minimum of 110 apps, lol... I guess we are opposites, hahaha...
[Xposed Framework Modules] nacron:
Yep, I purchased pro yesterday. Gravity box was on default for everything so it wasn'

Yep, I purchased pro yesterday. Gravity box was on default for everything so it wasn't messing with anything and I made double sure by turning it off and restarting. Had to resort to using multiple modules because not one has all features I want.

The problem I found was that the system items like for instance assigning search to home+power long press results in the screen turning off. Assigning apps works fine.
[Xposed Framework Modules] kevin_1351:
I meant 800 sorry hahah, yeah you're right, but with greenify and so on it doesn't even make a difference. //
[Xposed Framework Modules] dk_zero-cool:
Or your device is running out of ram before it's done. Seriously though, 700 apps?

Well I will try to see if I can find a solution for this.

First of all, did you remember to press the correct button first? You can assign different actions for Home+Power and Power+Home, so you need to press them in the correct order. Also remember that the second button needs to be pressed before the first one becomes a long press, which depends on your long press timeout settings.

Also did you use the newest version?
[Xposed Framework Modules] nacron:
Interesting, I assumed because it said home+power it was press at the same time not sequentially. When I assigned an app to that action, it seemed like it didn't matter if I pressed home first but now that you explained it that way, I can get search to pull up.