yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] fenchai:
Hi Dev. I have decided to stay on low version 2.3.8 because that is the only higher version working for me.

Btw after having home volume menu and back key modified, I cant not take screenshot, home+power button.

Is there a way to fix this?

another question, anyone knows a way so that rocker volume only triggers music state and not ringer or alarm.. ONLY music volume...anyone?
[Xposed Framework Modules] dk_zero-cool:
That was not fixed until the 3.x release. The old 2.x code structure was not able to add default combo.
[Xposed Framework Modules] fenchai:
Well, thats so unfurtunate T.T

I still cant understand why the newer versions dont work...I have tried the latest beta and it seems to have fixed "some" buttons for me but still... the recents buttons doesn't change any action set to it... im scratching my head so badly.
[Xposed Framework Modules] EmbGuy:
Ouya Console

Newbie questions.

I have an Ouya console (Android 4.1.2) running XBMC. I got a PC Media remote control (Chinavision CVSB-983) with an USB IR receiver which sends ASCII keycode to the USB port of Ouya console. I configured my Harmony 700 to communicate with the USB IR receiver.

I like to map the unused keys on my Harmony 700 remote to send more commands to Ouya. I tested my concept on my Windows 7 running XBMC using AutoHotKey and it works.

Q1. Can I use Xposed Additions to remap the keycodes received from the USB IR receiver like AutoHotKey does on a Windows box?

I installed Xposed framework on my Ouya to get Google Play working on Ouya.

Q2. I went to the Exposed Module Repository and cannot find the XposedBridge module. Is XposedBridge same as Xposed framework? If not, where I can find the XposedBridge apk?

TIA
[Xposed Framework Modules] dk_zero-cool:
I don't know if it will work, but maybe.

About Xposed

Xposed Bridge = The actual Xposed Framework Part

Xposed Installer = The App where you install and control modules. It is also where you install/enable Xposed Bridge.

Xposed = A replacement for the Android app_process which is what makes Xposed Bridge work.

Xposed Framework = Just a general word for Xposed/XposedBridge

Just go to this page and download Xposed Installer. Install it on your device and you can then install Xposed Bridge and any module from there.
[Xposed Framework Modules] EmbGuy:
dk_zero-cool,

Thank you for the explanation on xposed related terms.

I updated the Xposed Installer to the latest version and installed the Xposed Additions(XA) 3.3.0-pre on my Ouya.

There is only one physical button on Ouya console. XA can intercept the power key only and cannot intercept any keys from my Harmony remote/USB IR receiver. XA cannot intercept the keys on Ouya game controller either.
[Xposed Framework Modules] pan.zupa:
Hello,

I used last stable and last beta versions of Xposed Additions and I have the same problem on my HTC One (m7).

When I assign volume down key as a power button on screen off condition it works for very short time after. When phone is not used for 5 or more minutes there is no possibility to wake it up by pushing volume down.

Do you have such problem? What can I do?
[Xposed Framework Modules] dk_zero-cool:
Gaming controllers and Keyboards are disabled from xposed as they created to many issues for people. Other device types you have to enable external devices in the module settings.

If your kernel is disabling certain keys during deep sleep, there is nothing that I can do. The module already automatically re-assigns the regular power button when enabled which uses the same function, so if your power button is working an volume is not, then there is not much that I can do. It would be an issue for whomever made your kernel/rom.
[Xposed Framework Modules] pan.zupa:
This is stock kernel and rom from HTC.
[Xposed Framework Modules] dk_zero-cool:
Which is no surprise. Stock ROM's does not have many features, especially sreeen off features, so they properly just sort out keys from within the kernel. Xposed cannot reach all the way down to the kernel, so nothing I can do about it.

Just install a custom kernel (You don't need to switch ROM's for this). At the same time you get a lot if security/enhancement fixes, performance boost, more battery lifespan etc. Stock kernels are full of bugs and cheap hacks because companies like HTC and Samsung is not willing to waste much time assembling these.
[Xposed Framework Modules] pan.zupa:
Thanks for clarifications dk_zero-cool. I will try to install custom kernel. Thanks
[Xposed Framework Modules] dk_zero-cool:
Let me know how it goes, cause like I said if your power button works by default with the module enabled, there is no reason why any other key would not when remapped to power. Not unless the keys are disabled within the kernel.
[Xposed Framework Modules] mnz007:
+1

Sent from my Galaxy S2
[Xposed Framework Modules] dk_zero-cool:
And you get the same answer as he did, so just read above replies.
[Xposed Framework Modules] D00ky:
Is it normal that after enabling module, home button on s3 gets feedback even if no button is assigned in settings? Anyway it is nice to see that doubled feedback on samsung in solved.
[Xposed Framework Modules] h1ghland3r:
After this last update, my Power Button stopped working... =(

Sent from my Moto X
[Xposed Framework Modules] killoid:
the latest version just disabled all my hardware buttons! they stopped working though i've not assigned any of them. i couldn't get a log cause error log wasn't starting up. something's really bad happened i think. btw if i randomly start pressing all the buttons,some buttons functions for one time only.i'm on galaxy y duos,stock deodexed 2.3.6 rom. previously i was on v2.3.8 which was the most suitable of all.
[Xposed Framework Modules] EmbGuy:
The remote sends keyboard ASCII code to the USB IR receiver. XA will not work for me. I will look for other solution to my problem.

I learn a few things about Xposed in the process. It is a neat way to customize phone and tablet.
[Xposed Framework Modules] dk_zero-cool:
Again, assigned or not assigned, the module controls all buttons, otherwise it would not be able to detect which buttons should have default or custom actions.

And I don't know if this is normal or not. Samsung has a weird of controlling it, you just parse the key to Samsung and it will decide if there should be a feedback or not. It worked fine on my SGS3 with several Stock ROM's.

Sorry to hear that, but with this little information I am not sure what I can do about it. I don't know what device your are using, what ROM, if it is custom or stock (although issues mostly mean stock), I don't have a log or anything besides the fact that something is not working for you.

Well Galaxy Y Stock 2.3.6 issues I can work with, have one of my own for testing. I will look at it.

I have plans for an addition option to enable Keyboards and Gamepads next to the regular external device option, just did not have time to add it yet.
[Xposed Framework Modules] h1ghland3r:
It's a Moto X 4.4.3, Stock Rom. I don't have a log. In adittion, I'm using Gravity Box. I got back to previous version of Xposed Additions and the power button works fine.

Sent from my Moto X
[Xposed Framework Modules] ImpheOtus:
I updated to 3.3.0 stable, and capacitive buttons stopped vibrating when pressed.

I'm using Danvdh's [ROM]【4.4.4】Google Play Edition 【AOSP】- 06-27-2014 with my S4 i337m

"Force haptic feedback" option in 3.2.2 worked without problems.

What could be going on?

BTW, of course I rebooted after updating.

Do I need to remove all actions and start over? Clear app data maybe?
[Xposed Framework Modules] claytonjn:
On my Galaxy S5 with TouchWiz based ROM, installing 3.3.0 causes the app switcher (recents) key to stop working. Vibration occurs when tapped, but no action is taken. I typically have no actions set and use stock behavior, but I also tried setting the stock actions through Xposed Additions to no avail. In addition, I tried wiping data of Xposed Additions. I turned on debug logging and rebooted, then tapped the app switcher key but didn't see anything in the Xposed Additions log of Xposed Installer log, so I'm assuming it logs to the system logcat. I attached (hopefully) a logcat of tapping the key. I was supposed to meet up with my girlfriend an hour ago so I don't really have time to investigate further.

Reverting to 3.3.0-pre fixes the issue for me.
[Xposed Framework Modules] coolkaas:
YES. :cowboy: this is true.

i wrote about this a couple weeks ago.

difficult to get info from phone with very drunk hard-keys :)

this is maximum what i can:
[Xposed Framework Modules] Wiidesire:
Galaxy S4 i9505 with MGA Bootloader and NF1 firmware. With newest version everything stopped working. Besides that if I choose torch it says that I need to install an torch app. (worked before)
[Xposed Framework Modules] dk_zero-cool:
Well I guess that there is not much AOSP over these ROM's after all, otherwise they would operate like the AOSP code.

I will add back the forced option.

There is no real difference between those two. 3.3.0 is just the pre where I removed the pre fixed the part where volume was triggered on long press and released it.

Like I said, I will run some tests on my GY. But thanks for the log, might prove useful.
[Xposed Framework Modules] dk_zero-cool:
More information is needed. Log would also help.
[Xposed Framework Modules] ImpheOtus:
Thanks for quick reply and implementation ;)
[Xposed Framework Modules] mnz007:
I'm using a custom kernel (Dorimanx) with stock JB 4.1.2.

Sent from my Galaxy S2
[Xposed Framework Modules] dk_zero-cool:
Well then it is your kernel dev you need to ask, I cannot change kernel behavior using xposed.

Every button that is assigned as power (Including default for the power button) turns on the screen the exact same way, no difference at all. So if your power button (Unmapped) works as it should, but your volume (Mapped) does not, then you have a kernel problem which in turn is not a module issue or my problem to deal with. The module cannot remap buttons if it never receives them.
[Xposed Framework Modules] hamsup1o:
screenshots are finally working properly on v3.3! thanks! :)
[Xposed Framework Modules] Tlamaki:
Hello, version 3.3.0 disabled all the hardware buttons :crying: version 3.2.2 was working perfectly, though.

I have a very rare phone, Motorola Defy Pro running GB 2.3.7 stock room

:crying: please help!

thank you.

EDIT: I just read that you have plans to add an option for enabling keyboards/gamepads :)
[Xposed Framework Modules] Phone_BrickerT_T:
Just chiming in to say that latest version (3.3.0) also killed all my hardware button remaps. I'm on a galaxy s4 running the Google play edition ROM.
[Xposed Framework Modules] mnz007:
Thanks for your reply. The problem is only when the screen is off. It's working on lock screen and when the phone is unlocked.

Sent from my Galaxy S2
[Xposed Framework Modules] thurst306:
I reinstalled because it wasn't working when I updated, then bought pro again (don't know why I had to buy it again) and I still can't find any tasker options. Am I doing something wrong?
[Xposed Framework Modules] dk_zero-cool:
In the list of actions, scroll down to the applications and Tasker should be as the first option.
[Xposed Framework Modules] Blizzard22:
This module improved greatly and now after trying the most recent version on my Note 2 I can confirm that wakeup on usb plug can be disabled with this module. =D

I've got only one suggestion :

Could you please allow similar settings to plugging headphones/headset to the phone?

Currently my phone wakes up when I plug my headset which is annoying.

I've obtained the logcat from my phone so maybe it could help you with it.

Thank you for the great module!

http://dl.dropboxusercontent.com/1/view/9jgqtqirmsqqvj3/Public/Headset2014-07-15-01-00-20.txt
[Xposed Framework Modules] thurst306:
Nope, don't see it. I can see the option to open the tasker app, but no option to run tasker tasks.

Edit: I found it. Had to enable external access in tasker.
[Xposed Framework Modules] dk_zero-cool:
Ahh yes, that is right, I should add a message about this.
[Xposed Framework Modules] neonlite:
with 3.3.0 my menu button which is mapped to recent apps and long hold to show menu stopped working.

reverting to 3.3.0-pre works. cant keep it, because its automatically updating to 3.3.0.

Note 3 - stock rooted TouchWiz 4.4.2.
[Xposed Framework Modules] ryuseiken:
Hello, version 3.3.0 disabled all the hardware buttons, version 3.2.2 was working perfectly. Fix please, It is very useful.

Samsung Galaxy S4+ | i9506 | v4.3
[Xposed Framework Modules] siciliano777:
Just wondering, will the ability to map shortcuts/activities be coming anytime soon?
[Xposed Framework Modules] dk_zero-cool:
Okay, button issues should be fixed in 3.3.1. Tested on 3 different devices with 3 different Android versions, including Galaxy Y Stock 2.3.6.
[Xposed Framework Modules] Blizzard22:
I've found out that pressing the volume button wakes up the phone when Xposed Additions is enabled.

Could you please fix that or give an option to disable this?

Normally my phone doesn't wake up when I press the volume buttons and I normally control my music player with the volume buttons but currently I can't do that anymore.

Here is logcat of this error:

http://dl.dropboxusercontent.com/1/view/2m7poea5rysvbet/Public/Volume2014-07-15-13-32-56.txt
[Xposed Framework Modules] Wiidesire:
Fixed my issue on Home and Back Key on Galaxy S4, but the Menu key cannot be assigned to something else. Also it still tells me to install a torch application, it worked before.

edit:

Menu Key mapping with Lockscreen works, but with Screen on not
[Xposed Framework Modules] dk_zero-cool:
As long as I don't have a device with a recent apps key, I don't think that it is getting fixed. I have tried everything that I can do from just looking at logs. So if the key works with default actions and only have problems being mapped, then I have to consider this as good enough for now. For some reason this key acts differently than the others, I cannot test anything to figure out why and what.

I will however look into the Torch issue.
[Xposed Framework Modules] Wiidesire:
Thanks anyway, but just to let you know, everything worked perfectly with 3.3.0b3 and I think also with 3.3.0-pre, so it must be some changes you did after that ;)
[Xposed Framework Modules] t61p:
Hello, dk_zero-cool.

I report an observation about re-mapping of the Recent App Button on HTC-J(4.0.4) with Xposed Additions version 3.3.1.

I confirmed that:

- for Long Press, re-mapped key/custom action works now.

- for Click, re-mapped key/custom action doesn't work and the click always act as default behavior.

So, there is at least one progress. Thanks!

Here is what I've done. Please have a look at logcat file.

1. enable only Xposed Additions and disable any other Xposed modules

2. enable debug of Xposed Additions then reboot device

3. click/long press Recent App Button before re-mapping

4. click/long press Recent App Button after re-mapping
[Xposed Framework Modules] dk_zero-cool:
There is a small bug in my code, so thanks for the log. If this causes your recent apps problems I don't know, it depends. The bug is that all single click events get's disabled for non-pro users. But this affects all buttons, not just this one. So if you do not have pro, you should not be able to remap single clicks to any buttons. (And an update is of cause on it's way).
[Xposed Framework Modules] coolkaas:
*dancing* All keys works at v.3.3.1 at android 2.3.4 SE stock.

thank you genius dk_zero-cool!!

(I click all 'tnx' buttons under your nick at this page )
[Xposed Framework Modules] dk_zero-cool:
And recent apps click will hopefully work with 3.3.2 which has been released. At least it re-enables single click mapping again for all other buttons.
[Xposed Framework Modules] killoid:
button issue is fixed with the latest version. but a new issue has occured,my device is constantly auto-rebooting after a while using. however, the error log is empty when i clicked to see it even after turning on debug. is that normal? & btw the home+power screenshot function works now but it pops up the recent apps menu everytime after screenshot. using galaxy y duos,stock 2.3.6 rom.

EDIT: constant reboot issue is gone with v3.3.2. but other issues are still persisting.
[Xposed Framework Modules] t61p:
I've confirmed that re-mapping of Recent App Button for both click and long press works fine. Thank you very much!
[Xposed Framework Modules] ImpheOtus:
My buttons still don't have haptic feedback.

If module is disabled haptic feedback works fine.

Am I missing something?

Galaxy S4 i337m, running [ROM]【4.4.4】Google Play Edition 【AOSP】- 06-27-2014
[Xposed Framework Modules] cottino:
[MENTION=3147360]dk_zero-cool[/MENTION]

Last version works very well with the Galaxy S5, switch button too.

Now I can reconfigure it as I want.

Thank you very much :good:
[Xposed Framework Modules] Wiidesire:
thanks, everything working again on my Galaxy S4 i9505. Good job :good:
[Xposed Framework Modules] dsmboost:
Just a small suggestion for the dev. The short long press delay is a little too fast. Hardware buttons like the power button often take a little more effort to press, so it ends up pulling up the reboot menu sometimes when trying to turn the screen off. I think another 100 - 200 ms added to short delay would be optimal if that's possible.
[Xposed Framework Modules] dk_zero-cool:
I don't think that you will want another 200 on short.

Short = 75ms

Normal = 100ms

Long = 150ms

There is only 25ms between Short and Normal. So if you think that Short is to fast, then use Normal instead.
[Xposed Framework Modules] dsmboost:
There is no way normal is 100ms on my Note 3. It feels more like 500ms (in other words, way too long for me). Long long press feels like a second and a half. Could this be a Samsung thing that's affecting the speed?
[Xposed Framework Modules] ImpheOtus:
Vibration in capacitive buttons is working for you?
[Xposed Framework Modules] dk_zero-cool:
In that case you do not want me to set Short to 275. I will look into this and make sure that the module is not using the long press timeouts for tap. Cause the values that has been set for tap matches what I said, below is the array that should be used for tap.

<string-array name="delay_tap_values">
<item>75</item> <!-- Short in ms -->
<item>100</item> <!-- Normal in ms -->
<item>150</item> <!-- Long in ms -->
</string-array>

Haptic has been fixed on all Stock Samsung ROM's, but this does not include the Play Store Versions, which seams to be a whole different breed of Samsung Android.
[Xposed Framework Modules] ImpheOtus:
Wow... really? That sucks big time! I'm sorry for any inconvenience.

Would you add the "Force Haptic Feedback" option in the next release?
[Xposed Framework Modules] dk_zero-cool:
It's not easy as just adding. It took me a long time and a lot of code digging to figure out how their Stock versions handled it, since they changed the way Android normally does it. The Play Store version should be built from pure AOSP code, but it seams that even these versions has been changed, and in a different way as their normal Stock once. And figuring out it not the most easy thing to do, since they don't really release any source codes for their versions.

But if you can pull /system/framework/android.policy.jar from your device, I will see what I can do.
[Xposed Framework Modules] ImpheOtus:
Of course! Whatever I can do to help.

I attached android.policy.jar to this post.

BTW: "Force Haptic Feedback" option used to work perfectly on v3.2.2

In fact I reverted to that version which works perfectly for me. The problem is that Play Store keeps asking me to update and I can't unlink the app from the Play Store with Titanium Backup.
[Xposed Framework Modules] dsmboost:
What is the stock delay on most phones? It must be longer than 150 ms. I remember an old custom Samsung rom I was using where a dev implemented short timeout delay and it was about 200 ms. Stock was near 500ms I believe. Maybe I am mistaken, but the values you have don't seem right, they're way too fast, even for the long value.

I can confirm haptic feedback was fixed on my Note 3.
[Xposed Framework Modules] dk_zero-cool:
/** * Defines the duration in milliseconds between the first tap's up event and
* the second tap's down event for an interaction to be considered a
* double-tap.
*/
private static final int DOUBLE_TAP_TIMEOUT = 300;

But as you just pointed out, even 100 feels to slow, which is why I use lower values.

The default Android 500ms is for long press.
[Xposed Framework Modules] dsmboost:
I guess what I'm trying to say is, your normal value does not seem to be changing the stock value. It still feels like 500ms. Maybe someone else with a Samsung phone (and on a stock based rom) can confirm if they experience the same thing.
[Xposed Framework Modules] dk_zero-cool:
My module does not use any stock methods of controlling double tap. It uses my own custom code to create the delay which in turn uses values from my own settings to determine the delay time. So it is not possible for any of it to be using stock values unless I personally make it do so. But like I said, maybe there is a small mistake where it uses the long press values array instead of the double tap, and I will look into it. But there is no way it is using stock values.

EDIT:

Nope, the values are correct. When you select Normal, it will take 100ms to initiate a double click event after the second release of the button. Remember that things have changed in 3.3.x. It no longer uses double tap but instead double click. Difference is that tap is initiated on second down while click is initiated on second up. This is because 3.3.x also has double and triple long press events.
[Xposed Framework Modules] Nishchay1:
Sir i'am using a mediatek 6589T device . Since the recent version of ur xposed additions module , my power button is not correctly mapped. Even when i press it once the power off menu shows up. But this should happen when i long press my power button.

Either way ( short press or long pressing) the power button the power off menu is shown. So i cant turn off my screen using my power button. Turn on works fine though
[Xposed Framework Modules] slugger666:
I confirm the same behavior on my MTK 6589 device.

I had to uninstall the latest version and go back to 3.2.2 version which works fine.
[Xposed Framework Modules] dk_zero-cool:
Enable Debug, Reboot and grab a log while pressing the power button
[Xposed Framework Modules] UweRammelt:
Hi All!

Is there a way to kill the actual App by long-pressing on BACK or HOME on a Xoom 2 Tablet with 4.0.4?.

The BACK and HOME keys are soft-keys (on display).

Someone gives me a hint to try out Xposed Additions, but I did not find a appropriate feature . . .

.
[Xposed Framework Modules] fenchai:
Hi Dev, the latest version FINALLY WORKS, If I see nothing is wrong, I will support you by buying it <3 thanks!
[Xposed Framework Modules] dk_zero-cool:
First go into keys and add the key you want to use. Next click on the added key and add a screen on condition. Then go to that condition, enable the event you to use (like long press). Now click on that and choose the kill foreground app action.
[Xposed Framework Modules] UweRammelt:
I chosed "Add new key" and the message box "Intercept Key Code - Press the key that you wish to add" appears.

Then I press the BACK key or the HOME key, but the system goes back or home instead of the key code appears :confused:

.
[Xposed Framework Modules] dk_zero-cool:
In that case i guess that you got a popup message when you launched the app. I suggest you close the app, open i again and read it.
[Xposed Framework Modules] fenchai:
Hello, is there a way to make volume buttons ONLY change media volume, because who wants to change ringtone volume anyways? you just want to change it when you want it in vibrate.

This option is in the other xposed module, but it is a bit buggy because it is only for aOSP based roms, can you PLEASE implement this useful feature pretty pleaseeeeeeee? :)