yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] ImpheOtus:
Try removing your button's configuration, reboot and set your actions again. Maybe that would fix it.
[Xposed Framework Modules] BluBBa:
I have the same issue with my Galaxy Note 3 as user chattyuk.

Now its like samsung default: Click Menu and long click for Google Search

And double click for recents for some reason.

Tried your suggestion:

removed buttons and rebooted

Created new button configs

Still Problem as stated above.
[Xposed Framework Modules] ImpheOtus:
You and [MENTION=1117994]chattyuk[/MENTION] are on a Stock Samsung ROM?
[Xposed Framework Modules] BluBBa:
I am. Stock 4.4.2

Dont know bout chattyuk.

/edit: After pushing the menu button (which is supposed to be recents) a few times. The first time it shows the menu. After that its working as the recents but it resets on every new screen. So if i switch from one app to another using recents - the first click on menu is always menu.

Yea just checked again this is how it is right now. First time ->menu, then its recents. Resets on every new screen.
[Xposed Framework Modules] ImpheOtus:
Let's wait and see if [MENTION=3147360]dk_zero-cool[/MENTION] knows what's going on.

You may have to provide a log.
[Xposed Framework Modules] truedis:
Just downgraded from 3.4.0 to 3.3.4 as the "new re-map engine" changelog entry made me suspicious and what do you know, button remapping works fine now.

I'm on a Galaxy Note 3 VZW running 4.4.2
[Xposed Framework Modules] dk_zero-cool:
Okay first of all, putting something in quotes means that you don't quite think that it is true. It is a new re-map engine whether it is working for you or not.

Second of all, I did release a beta to begin with. When I do not get any feedback I take that as working and release it. This will not change.

Third, and this goes for all. Small indications that something is not working, is not going to fix it. I am not even going to try without something more useful information like a proper description of the problem (which some of you did provide parts of) and a log (which none has yet provided).
[Xposed Framework Modules] truedis:
Whoa, whoa, settle down, I'm not trying to insult anyone. I put it in quotes because it's quoted directly from the changelog ... that's what I understand quotes are for. I'm happy to provide logs or whatever else you need. I'm just saying that the new re-map engine doesn't work for me on my device, and the old one does. I realize that this is a free product that you put your valuable time into, and I'm not trying to be ungrateful.
[Xposed Framework Modules] dk_zero-cool:
It was just an information based on how I read it, nothing more to it.

Also remember that there is no tone in messages, so things can be misread. I try to adapt my words in ways that will limit confusions, but not always with success.

Now in order to have a chance of fixing anything, I need a detailed explanation of the issue. Also a log with debug enabled and you pressing to invoke whatever it is that is not working, will go a long way.
[Xposed Framework Modules] :
Please help me, it's not working at all on my Moto X :(. First time I've installed it, it's the last version (I've also tried 3.3.4, but the results were the same), I've already deactivated Gravity Box, rebooted and everything. Still nothing. I've tried using Volume Button -> Screen On -> Click -> Screenshot. Reboot. Nothing happens. Tried Volume Up + Volume Down -> Screen On -> Click -> Torch. Reboot. Nothing happens. Tried Power Button -> Screen On -> Click -> Recent Apps. Reboot. Nothing happens. The buttons just don't do anything. Force Haptic Feedback is working fine, I get the button feedback perfectly. I really want to buy the Pro version to explore it more, but I have to get it to work in my device first.

Thanks,
[Xposed Framework Modules] badbob001:
I'm on the Pro version and I can't figure out how to add an action for a Tasker task. I'm currently using the trial version of Tasker downloaded from the Tasker website and not the Play store.
[Xposed Framework Modules] a.fontenele:
Hi [MENTION=241623]badbob001[/MENTION], let me try to help you... As I don't know how well you know how to deal with tasker, I'll try to cover everything from the basics...

1st - enable "Allow External Access" on Tasker:

2nd - You must have tasks already created to chose from, here are some examples:

3rd - In Xposed Additions Pro follow the screenshots I provided bellow:

As you can see, I set the home key double click to toggle auto brightness...

Let us know if it worked for you and hit the thanks button if I helped somehow... ;)
[Xposed Framework Modules] dk_zero-cool:
Well for one I must say that you do provide very specific information about your issues, so thanks for this. But I will need just a little bit more.

Since Forced Haptic works, I am guessing that the module settings has no problem intercepting your buttons when using the Add Button?

After you try to click some buttons to make some of the actions work, it the Error Log in the module settings empty, or is there some errors being displayed?

I need a log that is taken while you are pressing a few re-mapped buttons (Just remember to tell me which actions should have been executed for the buttons you try). You can use ADB on your PC or one of the Logcat apps from Play Store to get the logs. Remember to enable debug in module settings and reboot before getting a log.

Yes just fallow the stepts posted above, Tasker does not work until you enable external access in Tasker to the allow the module to use it's Tasks, it's a security thing in Tasker. You would also know this if you read the dialog messages when first opening the module settings with Tasker installed ;)
[Xposed Framework Modules] Ninolina:
[MENTION=3147360]dk_zero-cool[/MENTION],

I am on Galaxy S4 android v4.3 and newest version v3.40 and the one before are not working ok for me. It seems that buttons that are re-mapped must be pressed 2 times that it will do what it should as re-mapped. If it pressed just once it will do as it is default for that button. It the same for Home, Back and Menu button. I send you log by mail and here is attached file in this post. The previous 3.3.2 was the last that worked ok.

Is my log ok or you need more information's?

Thank you for your great work! :)
[Xposed Framework Modules] badbob001:
I was so sure that enabling the external access setting in Tasker would do the trick, but it doesn't. Restarting a few times also didn't help. The thing is, I installed Tasker just recently but had Additions installed a long time ago. Perhaps Additions only integrates with Tasker if Tasker is already installed on initial startup? Should I uninstall and reinstall Additions? I don't see an option to export/import my settings so I wonder if an reinstall will wipe my settings.

Update: in the Error Log, I see:

W/PackageManager

Not granting permission net.dinglisch.android.tasker.PERMISSION_RUN_TASKS to package com.spazedog.xposed.additonsgb because it was previously installed without

So... reinstall?
[Xposed Framework Modules] :
I've sent all the logs and logcat to your email :). Thanks a lot for helping me. Just another question: when I enable Additions, my power button become useless. Even If I haven't re-mapped the power button, just activating Additions makes it useless. I've already re-installed, deleted data, cache and everything just to see If it helps, but nothing has changed. If I disable Additions at Xposed the power button works perfectly. Is that normal? (also tried downgrading to 3.3.4. Same results)
[Xposed Framework Modules] luisblop:
[REQ] Call button option checkbox to only take calls.

Hi,

So far this module is really helpful, I appreciate your hard work.

I write this time because I would like to make a request concerning the call button option. In fact it can be useful to add a checkbox to only use the key to take calls and avoid the hangup behavior.

For instance when trying to do simultaneous tasking during a call and perhaps ending by mistake the phone conversation because of using the same configured key. In many cases the [HOME] key.

I hope you like this suggestion
[Xposed Framework Modules] c37:
Thanks for developing this useful module! But I have one little problem with it:

I am on a Xperia Z1 Compact (running Cyanogenmod 11 Nightly 2014-07-25), which only has soft buttons, and when Xposed Additions is enabled, haptic feedback for the back and home buttons does not work anymore. The recent apps button works fine, though.

I cannot force haptic feedback on them, because the soft buttons are not recognized by the new button chooser.

Is there any way to fix this?
[Xposed Framework Modules] xdapao3:
Just to report that 3.4.0 (paid version) works *fabulously* on both my Note 3 and Tabs S (HW and SW details in my sign)!!

On both devices I have remapped (several actions each) the Menu button (Recent Apps on the Tab S), Home button, Back button and Volume UP button and finally EVERYTHING works as it should!

Both of my devices are SO MUCH BETTER because of this module! It really should come preinstalled and by itself would be reason enough to root! LOVE IT!!
[Xposed Framework Modules] Respect Milo:
Note 3 USB Actions

I use OTG USB drives and OTG cables with USB drives daily on my Note 3 (AT&T). Everytime I connect a USB drive, Samsung's "My Files" opens automatically. Can an option be added to stop this? It's a small thing, but it bugs me to no end. If there is already a solution that currently exists I can't find it.

Thanks!

Recently contract free. Recently rooted. First XDA post! It's a brave new world.
[Xposed Framework Modules] falo88:
issues with 3.4.0

Hi,

I am having problems after latest update. My GS3 has a very sensitive power button, so I use this module mainly to disable the power button. However, after I upgraded to 3.4.0, I am unable to disable power button. Also, I remapped home button long press to open power menu, but after update I have to double click in order for the command to work. Another thing I noticed is that in order to make the remapping work, I have to enable custom actions on my custom ROM (gummy) settings. Anyone have any solutions or experiencing same issues? Thanks!

---------- Post added at 07:48 AM ---------- Previous post was at 07:42 AM ----------

This is what I have on error log

W/PackageManager

Unknown permission net.dinglisch.android.tasker.PERMISSION_RUN_TASKS in package com.spazedog.xposed.additionsgb

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

W/PackageManager

Unknown permission net.dinglisch.android.tasker.PERMISSION_RUN_TASKS in package com.spazedog.xposed.additionsgb
[Xposed Framework Modules] CZ Eddie:
The new long-hold adjustable times are awesome, thanks!!

And just a heads up to anyone else who has had the problem I'm about to detail. I had changed my Note 3's settings button so that single-click=Recents and long-click=Menu.

The Recents function has always worked fine. But the Menu function on long-press has been flakey. Sometimes it works, sometimes it doesn't.

I just changed my long-hold press time down to 300ms and so far, the Menu function has been holding it's capability. I have not lost it yet. :good:
[Xposed Framework Modules] falo88:
Tried it at 300ms on my gs3 and still have same problem
[Xposed Framework Modules] neonlite:
Hmm.. I'm in the same boat, except that the menu button doesnt work on the first click (does not open recent applications), have to press 2 times to let it open. any other settings I have to check?
[Xposed Framework Modules] CZ Eddie:
Are you guys on 4.4.2? And using the latest update of Xposed Additions?

I dunno. Maybe try 250ms?

I'm not aware of any other settings that need to be made.

If it works at all, then afaik, you've done all the settings necessary.
[Xposed Framework Modules] falo88:
Yes I am at 4.2.2 with latest update. In fact, this was not an issue before the new update. Tried at numeous speeds and still no change.
[Xposed Framework Modules] babydown:
I configed to use camera focus button for next song (click + screen off + media next) but when used, I had to press double camera focus button (not click) to make it work. Is it bug or I config wrong ????
[Xposed Framework Modules] killoid:
[MENTION=3147360]dk_zero-cool[/MENTION] v3.4.1 is far more better than any other versions till v2.3.8. only 2 issues i've faced-

1. when i slide the sliders at most left for double tap it stucks at 50 ms & for long press at 100 ms. but when i exit the module & come back again they show both the values 0 ms. screenshot attached for better understanding.

2. when the long press slider is at most left (0 ms or 100 ms,u say it), back button (didn't map it till then) doesn't exit any app with only single click.i've to double click it to exit any app.

tested on my galaxy y duos,stock rom.
[Xposed Framework Modules] :
Still not working on my Moto X. :(
[Xposed Framework Modules] pure.by:
A good app, but not compatible with HTC One Mini running InsertCoin (Android 4.4, Sense 6).

Messes up system button assignments even for unedited buttons (for instance double tapping home button for recent apps stopped working after I created a custom action for VolumeUp).

Goolge Now swipe-up-from-home gesture got all messed up.

Generally, 4/5 times any button on my device is pressed, it either gets ignored, or it passes through with a huge lag (5~10 seconds). This affects all phone buttons, not only customizes ones. Makes phone unusable.

Luckily, after disabling this addon in Xposed settings and restarting the phone, everything got back to normal.

Any ideas how to get this app working the propper way?
[Xposed Framework Modules] :
Same here with my Moto X. Only enabling Additions, without even re-mapping any button, my power button becomes useless, does nothing. Also, can't make it work with any button. It detects that I've pressed the button, but does nothing.
[Xposed Framework Modules] falo88:
New update fixed the doubleclick problems and the power button its partially disabled. I am still having trouble disabling the power button completely, meaning that when I press it, it doesnt turn off the screen, but after about 5 seconds it does turn off the phone. Like I said before, my gs3 has an extremely sensitive power button and I would like to know if there is a way to disable it entirely.

PS: I used to be able to disable my power button completely in older versions.
[Xposed Framework Modules] bjrmd:
Something to try:

As the phone is booting up, press some of the problem buttons before xposed kicks in.

I was having issues with unresponsive soft keys(back/menu) on my note 2, probably a conflict with the custom kernel that had a bunch of new reassign button features and xposed additions. If I let it boot all the way the soft keys would not even register as being pressed. But, if I start pressing as the first image of home screen appears, they work and keep working until the next reboot.

Can't really blame either developer and don't expect any custom fix.
[Xposed Framework Modules] pan.zupa:
Hi I have updated from 3.3.0-pre to latest version and mappings stopped working.

I Uninstalled the module and installed it again then I set mapping configuration but it still doesn't work. Of course I restart phone after each step.

What to do?
[Xposed Framework Modules] a.fontenele:
[MENTION=3147360]dk_zero-cool[/MENTION]

Version: 3.4.1

• Fix buttons not working for non-pro

• Fix do not kill Home Launcher → Thank you so much for this update man! I really appreciated it! It is flawless now! :D

:good::good::good::good::good::good::good::good:
[Xposed Framework Modules] pan.zupa:
I just saw that there is 3.4.1 version. It works flawlessly!

Big thanks [emoji3]
[Xposed Framework Modules] mkdr:
v3.4.0/v3.4.1 broke a lot of things, again, for me (i9300 + SlimKat 4.4.4), had to revert back to 3.3.4 which works great. Buttons arent working anymore from my Lockscreen (LockerPro), the screen flickers and I am brought to the PIN entry, from there the buttons work. It works normal/perfect with 3.3.4.

It would be nice, if new things like "rewrote..." or "changed how..." would be optional to toggle on/off in the app, if they mean the code has changed 100% and have a 100% chance things broke for a lot of people.
[Xposed Framework Modules] Wiidesire:
Buttons do mostly work again with newest version, however while screen is off and you want to change the volume it goes completely up and down (mute) instead of just one step. Galaxy S4 i9505.
[Xposed Framework Modules] dk_zero-cool:
When a code is completely re-written, you can't just keep the old one and add a toggle. We are not talking about small changes here, and I am the one that has to maintain it and do the work of getting two different systems working in one module.

The way these things work is that developers (Me in this case), releases a beta version, which I did. Then we wait for someone to test and respond, which no one did. When a week or two pases and no one complaints about issues, we consider this to be because no one is having any issues and we release it as stable. I did my job when I released the beta of 3.4, but if no one test it and provides any feedback, then there is not much that I can do. I only have 3 devices to test on myself, and this version is working perfectly on all of them.

I will once again install SlimKat on my own SGS3 and work these issues out. But I am not home this week, so it will not be until some time this weekend.

And then it might be a good idea if more people enabled Beta notifications in XposedInstaller and started testing and reporting issues in much earlier stages. Otherwise we will have more of these issues in the future.

I will add this on my Todo for this weekend
[Xposed Framework Modules] :
Please help me If you could :(. Just need to work here then I will buy the Pro version . I've already send you the logs to your email. Moto X 4.4.3 Stock room.
[Xposed Framework Modules] TLK3:
Try 350ms. I was having similar issues with long press and it's working perfect now. I'm using 150ms for double click, in case anyone else is having problems.
[Xposed Framework Modules] gerhardo:
For those with problems: XPosed modules are not like normal Android apps.

Normal apps are built on the Android API. Mostly the same for each Android version, with new versions mostly expanding.

For XPosed, the Android internals are hooked. It is equivalent to you are replacing bricks in a house foundation. The ROM makers do not expect the bricks to be replaced and move them around so what corrects a problem for one ROM can give problems in another.

This module also supports pre 4.0 where the internals was changed a lot.

So if you have problems, be very specific with the device and ROM version (down to details).

Be also prepared to supply logcats and the system files.
[Xposed Framework Modules] dk_zero-cool:
I have your logs on my PC, and they will be looked at soon. But could you also send a résumé of the problem to my mail? Its easier to store.
[Xposed Framework Modules] mkdr:
Beta of one week is way too less, give it at least a month if you do a major rewrite. And of course you can toggle if you want, it's just more work to implement. Thanks for looking into it, for now I am using 3.3.4 which worked great after all and I was happy with that version. You should do beta opt-ins via Play/Plus, thats the better way of handling it, and people will get a beta via play store then.
[Xposed Framework Modules] falo88:
This problem was solved with the latest update.

Now, the only issue I am experiencing is that I cant disable the power button completely.
[Xposed Framework Modules] Ninolina:
[MENTION=3147360]dk_zero-cool[/MENTION], all is working great now! :)

I just bought PRO version! :) It's even better! ;)

Keep the good work! ;)
[Xposed Framework Modules] egingell:
The problem with Google's beta opt-in is there's no distinction between beta and stable.

And a toggle would require both codebases be present and he would effectively be supporting two separate apps in one.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] truedis:
[MENTION=3147360]dk_zero-cool[/MENTION] thanks for the fix to button remapping for non-pro in 3.4.1 - working great for me on my VZW Note 3
[Xposed Framework Modules] dk_zero-cool:
Play Store is not very good at anything, so I keep it's usage limited, and it is also the reason why we use XDA for support and such. And I am not going to wait one month when I get no response within a week (Not one single response). I can't do much work while a beta is out, as the best way is to freeze any changes.

Also the reason for the changes was that to many people had issues, and each small change to fix one users issue, just caused a new issue for another user. So while the module might have worked for you, it did not for others and I was having a hard time making it work. So I decided that a bigger change was needed, because I do have other things to do than just keep trying to tweak a code base that had proven impossible to make work as it should. Now I can tweak this and see if I can get a better result, without breaking things for users with no current issues.
[Xposed Framework Modules] hello_world.c:
Module prevents physical home key to wake up device

I have a Galaxy Tab Pro with CM11 nightly from 29-JULY-2014. There is a settings option to wake the device with the physical home key/button which is enabled. As soon as the Xposed Additions module is loaded (even default/unconfigured), the wake up doesn't work anymore. Disable the module & reboot and it works again.

This seems to happen with any 3.x version. I tried the latest 2.x briefly and it didn't have that effect, but it also doesn't have the functionality I need so it's not a workaround for me.
[Xposed Framework Modules] dk_zero-cool:
That is a bug in CM where wake keys does not work on injected keys. Not a bug in the module, and side affects should also be considered when using modules to change default Android behavior.

And if you want Home to wake the device, then just enable this in XposedAdditions. This is what the module is for, so if you install it then why not use it as it was intended?
[Xposed Framework Modules] hello_world.c:
Is that in the full/paid version? I didn't see this option in the free version, nor in the screenshots in the Play store. Wanted to try everything in the free version first.
[Xposed Framework Modules] egingell:
It's "Power".

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] hello_world.c:
I see the light now. Thanks.
[Xposed Framework Modules] heather1209:
It appears that that ability to disable the screen wake on plug/unplug doesn't work for the HTC One M8 (I'm running ViperOne rom with the Checkm8 kernel). I changed kernels specifically to try and get this mod working but no luck. Any ideas?
[Xposed Framework Modules] dk_zero-cool:
Stock ROM's often change things in the Android source, HTC has properly changed something in the code that controls this part. You could start by checking the log and see if there is an error.
[Xposed Framework Modules] 954wrecker:
[MENTION=3147360]dk_zero-cool[/MENTION]

Is setting something up on amazon app store possible or is it a huge pain in the ass? I know myself and probably lots of others with a ton of amazon coins would love to send some of them your way. I would personally buy it 5 times, once with every account I have. I know nothing of how amazon works but I'm trying to get my favorite developers some extra coins.

sent from my note 3
[Xposed Framework Modules] egingell:
Amazon coins?

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] toyongbanatero:
Lags on my phone

I have an MTK Jellybean 4.2.2 device. The latest version lags on my device. Everytime I press a button (my phone has capacitive buttons as well as pure hardware buttons), it lags. A random delay of 1000 - 2500 ms before the button respond. Even those that I did not remapped. Please fix. Great module though.

(On a side note, I downgraded to 3.3.4 and I do not experience the delay. Not a workaround though because my ROM's default screenshot combination can't be detected natively. I'm also planning to buy pro, but not until this is fixed. Thank you.)