yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] sweeds:
I'm certain that it's been installed correctly. I've gone through the motions extra times jic.

I think something with the ROM/this app is overriding. Such as the hooks being changed, like you say.

But I don't yet know how to fix it.

Here's the log when trying to "intercept key code"

com.spazedog.xposed.additionsgb.backend.service.XService null android.os.DeadObjectException at android.os.BinderProxy.transact(Native Method) at com.spazedog.xposed.additionsgb.backend.service.IXServiceChangeListener$Stub$Proxy.onBroadcastReceive(IXServiceChangeListener.java:152) at com.spazedog.xposed.additionsgb.backend.service.XService.sendBroadcast(XService.java:541) at com.spazedog.xposed.additionsgb.backend.service.IXService$Stub.onTransact(IXService.java:242) at android.os.Binder.execTransact(Binder.java:404) at dalvik.system.NativeStart.run(Native Method)

Edit: looked up DeadObjectException. I think you may be right. Whatever handler the Xposed app is looking for, it's no longer an accessible object in the ROM.
[Xposed Framework Modules] gerhardo:
This module will not change the wakeup behavior, if the device is in deep sleep normally only Power will wake up.

This module intercepts the call after being delivered so it will not affect battery in any measurable way.

(When pressing Power, it starts a wakelock for some seconds, so if you push power a lot you may notice a very marginal additional battery drain.)
[Xposed Framework Modules] Anistruk:
I had my home button set to wake up the phone, after install the module and set the home button to Call Button i can not wake up the phone with the home button.

Is this the normal behavior?

Thanks in advance.

Regards
[Xposed Framework Modules] abhi08638:
Yes as most phones usually turn off capacitive buttons to save power. If it is a hard button like an s3's home button then it would still work
[Xposed Framework Modules] Anistruk:
It is a hard button, is a Galaxy S. And it appens just when i activate de module.

Regards
[Xposed Framework Modules] JLsoft:
Awesome...can you post a recent apk that has this fix applied, please? :)
[Xposed Framework Modules] gerhardo:
There is a link on page 131 to the xda thread for the mod, not to mix up the the functions (until dk_cool-zero accepts to merge, of course)
[Xposed Framework Modules] ogi010:
Bug with LG G2 on 4.4.2

Not sure if this is the best place to post this, but I isolated a fault to be with xposed additions on my LG G2 (LS980) running 4.4.2. Without any settings, xposed additions was preventing a short press on the power button from turning the screen on/off. Once I uninstalled xposed additions and rebooted my phone, the behavior went back to normal. I'd be happy to do any testing.
[Xposed Framework Modules] paul42x:
Not working Note sweet rom

Hi,

Love this module but it randomly (but most of the time) causes the hardware buttons just stop working.

I'm using a Samsug Note with sweet rom 11.1.

Any help would be appreciated.

I'm new to this - is another xposed module possibly conflicting?

Thanx
[Xposed Framework Modules] Anistruk:
I had the same behavior at a Galaxy S, and it appens at the moment that i activate de module.
[Xposed Framework Modules] siciliano777:
OK, I've started having issues with the s for switch voice app. ? all I'm trying to do is map google voice search to the home button. I'm really looking forward to future releases that might include being able to map shortcuts!
[Xposed Framework Modules] omnomnommm:
volume buttons problem when screen off

Hey, I was wondering if there was a fix for a volume buttons issue when screen is off.

If i'm playing music, and I click volume up, then it goes direct to max. Or if i click volume, down, it goes straight to mute.

I'm using S4 i337 4.4.2 TW.

Thanks!
[Xposed Framework Modules] bkd11:
I have a Motorola RAZR HD with Slimkat 4.4.2 build.4 and I'm having the same issue. I'm currently using version 3.1.2 and the problem doesn't exist, I'm able to add buttons. The problem started at version 3.2.0 and every version after (I've tried them all..lol). It just won't detect any buttons in the Intercept Key Code window. I have tried re-installing the Xposed framework many times, and other modules that I'm using are working fine. I love this app and purchased the Pro version when it first came out. I'm just looking for a solution so I can use the updated versions. Thx!
[Xposed Framework Modules] clemson77on:
I'm wanting to be able to long press the volume button on my HTC One and have an app I have (garagemate) open or close my garage door. Or I may even use Tasker. Can this be done with Xposed Additions? It sounds like it can but I need to be able to do this without going through the lockscreen. My goal is to long press the volume button and not even have to take the phone out of my pocket.
[Xposed Framework Modules] egingell:
If merely running the app activates the garage door, then this app will work fine (donate). If, however, it's an activity shortcut or widget, you'll have to use something else until such feature is implemented.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] clemson77on:
It looks like it could have lots of uses so I purchased the pro key. But the issue I see is that I can't start an action to open a custom app with the screen off. Is this something that may be added later, or something that's restricted within Android?
[Xposed Framework Modules] cyphomatic:
I have an annoying issue. The new releases are very buggy for my setup. The 2.3.8 worked perfect without any problems and did what it should do for me. When I disconnect xpposed additions from google play (titanium back) to protect 2.3.8 from updating, the module connect itself to the play market. Is there a way to stop this? I believe the market link is also unnecessary, because I update my modules trough xposed framework itself.
[Xposed Framework Modules] gerhardo:
Launching an app when screen is off may not work as an user expect. It depends if screen should be woken up etc.

I guess dk_cool-zero disabled this, to not get discussions similar to haptic feedback behavior (depends on the ROM, but similar anyway).

The long term solution is likely App Shortcuts, that can be customized some (with Tasker/Llama etc).

dk_cool-zero has said he is working on it.

Meanwhile, I enabled custom app launch in a time limited test build, see page 131 for a link.
[Xposed Framework Modules] clemson77on:
Thanks! I'll give both of those a try.
[Xposed Framework Modules] cramu:
Found this statement when I tried to find out if it is possible to remap hardware buttons only when camera app is open.

Is this still true or did you change your mind?
[Xposed Framework Modules] egingell:
This can be done with the donate version.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] cramu:
Thanks just bought it.

Zooming seems to not work with Google camera.

Can anyone confirm?
[Xposed Framework Modules] clemson77on:
I just want to thank you and let you know that this worked like a charm. Now I'm able to pull up in the driveway and just long press my volume button without even turning the screen on and get my garage door to open. Convenient and cool.

BTW, after installing this modded version, I had to remap the power button. It wouldn't turn the screen off. I remapped it for screen on and screen off (one click - power, long press - power menu). Will any of this mess me up if I need to get into recovery mode?
[Xposed Framework Modules] gerhardo:
Xposed is not involved in recovery mode, so if you get the power menu, it is fine.

Mapping Power to long press should work the same.

Will look into the problem. It may be related to relaying-unmapped-events directly.
[Xposed Framework Modules] juntjoo:
it says I need bridge. I Click that link it brings me back to xposed page in the play store. Now what. Where for this bridge thing?
[Xposed Framework Modules] egingell:
What?

You need the Xposed framework. That's what "bridge" is. And there's no Xposed page on the Play Store.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] juntjoo:
Sure there is. I was just there. Installed xposed additions and it said get xposed bridge, found the link, brought me right back to xposed additions

---------- Post added at 02:52 AM ---------- Previous post was at 02:52 AM ----------

I'm going in circles. Where's the one stop shop to get my buttons remapped? Thanks
[Xposed Framework Modules] egingell:
All of the links in the OP are mirrors to download this module.

You need the framework to make it work. In a different thread in this same forum.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] juntjoo:
Okay, I think I have to enable it. ..

---------- Post added at 03:00 AM ---------- Previous post was at 02:58 AM ----------

Misleading. If bridge is installed with additions, it shouldn't suggest it's not installed. It said to make sure it was installed and enabled. The only way for me to know bridge was installed is the fact the app is interacting with me. Anyway
[Xposed Framework Modules] egingell:
There's also the fact that you would have installed it yourself (I would like to think you'd know what apps you have installed) or it would have been listed as a feature of the ROM (if it came with it).

You keep calling it "bridge" which suggests that you have no idea what you're doing. I would suggest that you read the first page of Xposed Framework thread and the Index which is a sticky thread in this forum. While you're at it, read whatever you can about your phone in its forum.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] onyxogen:
Would it be possible to add a master switch the disables the functionality without having to reboot? This way external physical keyboards could be used without rebooting.
[Xposed Framework Modules] egingell:
Not without a reboot.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] luisblop:
[HOME] button behavior with samsung phone solved.

I want to thank the developer. After one year searching in vain for a fix about my [HOME] button frustrating behavior. Finally I got to solve it with your Module. I thought I had to live forever with that.

The issue was when pressing [HOME] to wake up my phone. Not only the screen was turned on but at the same time it send me back systematically to the home page. So any active app was closed and I had to start all over again. It was a pity having a samsung galaxy phone with those big physical home buttons and not being able to use it. At the end I only employed the power button.

Happily I can forget that issue from now on. Really really a big THANKS!!!

NB. By the way if someone wants to know, the fix was successfully done by remapping [HOME] with the condition screen off. Voila!
[Xposed Framework Modules] onyxogen:
:_( I thought that you can do something like "if (switch==false) return ;" on the first line of every overriden function... Which effectively disables the module
[Xposed Framework Modules] gerhardo:
Mod updated to not bypass Power button
[Xposed Framework Modules] egingell:
Yeah, but it hooks onto the Android framework itself... I dunno, maybe.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] signupstuffid:
This module has really gotten better over the various updates.

I originally just wanted a way to remap volume buttons to wake my phone. It does that and more now.

I have made a long press on menu turn off the screen, long press on back kill the current app, and my headphones next and previous buttons control the volume instead of track change.

The coolest thing it has let me do so far is to make my bluetooth reciever track buttons a remote camera release. The piece of hardware I use for that is the Samsung HS3000. The most functional bluetooth receiver I've used. Which is likely why it's sold out nearly everywhere.

http://www.amazon.com/Samsung-Stere...eadset/dp/B0057WWK5E/ref=cm_cr_pr_product_top

All of this I have been able to do with the free version.

[MENTION=3147360]dk_zero-cool[/MENTION]

If you could get he following wowwee gun via headphone port control to work, I'd buy the pro version in a heartbeat.

http://www.amazon.com/WowWee-W0140-AppGear-Commandar-Application/dp/B007HZDA6C

The cool thing with this device, is that it holds the phone and if I could get the trigger to detect with this app I could turn the make that my shutter release, and have a cheap pistol grip for camera use on my phone.

I would even be willing to ship one of my toys guns to you to let you use it for testing.
[Xposed Framework Modules] bkd11:
Any feedback on this issue?
[Xposed Framework Modules] sweeds:
Since we're seeing the same thing on different phones with the same ROM, and from what I've been told; the ROM itself is changing some of the nav btn framework and when the Xposed app looks for certain "nav btn pressed" hooks, they've been changed at that point and the app does not get that event fired response.

IDK if there's a work around that Xposed Additions can provide, or if we'd need more serious involvement from the SlimKat devs. Or... find an alternative solution.
[Xposed Framework Modules] egingell:
Button: Back

Condition: App - ADW.Launcher

Action: Click - Last Application

From home: Click Back, go to last app as expected. Click Back again and nothing. Several seconds later, the phone soft-rebooted.

Trying again for a log. There was nothing logged.

Edit: The reboot was a coincidence (I thought it might be). At any rate, I did the above plus explicitly set Back to Back on Screen On Click and it works fine. Still no errors; however, I did get this:

W/ContextImpl
Calling a method in the system process without a qualified user: android.app.ContextImpl.startActivity:1221 com.spazedog.xposed.additionsgb.backend.PhoneWindowManager.toggleLastApplication:1035 com.spazedog.xposed.additionsgb.backend.PhoneWindowManager$8.run:1235 android.os.Handler.handleCallback:725 android.os.Handler.dispatchMessage:92
------------------------
W/ContextImpl
Calling a method in the system process without a qualified user: android.app.ContextImpl.startActivity:1233 android.app.ContextImpl.startActivity:1222 com.spazedog.xposed.additionsgb.backend.PhoneWindowManager.toggleLastApplication:1035 com.spazedog.xposed.additionsgb.backend.PhoneWindowManager$8.run:1235 android.os.Handler.handleCallback:725
------------------------
W/ContextImpl
Calling a method in the system process without a qualified user: android.app.ContextImpl.startActivity:1221 com.spazedog.xposed.additionsgb.backend.PhoneWindowManager.toggleLastApplication:1035 com.spazedog.xposed.additionsgb.backend.PhoneWindowManager$8.run:1235 android.os.Handler.handleCallback:725 android.os.Handler.dispatchMessage:92
------------------------
W/ContextImpl
Calling a method in the system process without a qualified user: android.app.ContextImpl.startActivity:1233 android.app.ContextImpl.startActivity:1222 com.spazedog.xposed.additionsgb.backend.PhoneWindowManager.toggleLastApplication:1035 com.spazedog.xposed.additionsgb.backend.PhoneWindowManager$8.run:1235 android.os.Handler.handleCallback:725

Edit: Soft-reboot was not a coincidence. It just did it again. This time while on the home screen.

Edit: Your app seems to delete the error log on boot. Can't get error when the phone spontaneously soft-reboots (system_server crash, I assume).

I have a theory: maybe infinite loop when Additions thinks ADW is the current app and/or when ADW is the last app.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] gerhardo:
Problem seem to be related to EnableCallRecording extension

A quick check in the code finds no reference to PhoneFeature class, but this could be indirect

Enable debug in the app, reboot and make a logcat.

It is possible to send the logcat directly to dk_cool-zero from the app
[Xposed Framework Modules] juntjoo:
Thank you
[Xposed Framework Modules] bkd11:
Well the work around I've been using is staying on version 3.1.2. Like I said the problem didn't start until I updated to 3.2.0. I haven't yet tested with any other ROMs yet to confirm if this is specific to the SlimKat. I guess when I have a chance I will flash a different ROM and find out.
[Xposed Framework Modules] iede:
I'm using latest version (3.2.2) of Xposed Additions in my Note 3 (4.4.2). Everything works fine except when I enter single handed mode, the on screen button doesn't work.

Switching to version 2.3.8, and on screen button works again but the touch key light is always off :(. Can we fix this in latest version? I prefer touch key light not on compared to my on screen button not working. Thanks!
[Xposed Framework Modules] a.fontenele:
[MENTION=3147360]dk_zero-cool[/MENTION]

Any news to when GO TO LAST APPLICATION (will be fixed), APP SHORTCUT and NOTIFICATION PULLDOWN functions will be available?

I wonder because we all miss your updates... :D
[Xposed Framework Modules] sweeds:
Ahh THX! For now, I'll consider that a fix. Downgrading to Xposed Additions 3.1.2 fixes the button remapping on SlimKat 4.

For those that need it: http://repo.xposed.info/module/com.spazedog.xposed.additionsgb

:good:
[Xposed Framework Modules] jiu2k:
Please add toggle for Expanded desktop

Immersive mode on small screen phone is not convenient to swipe down for notification. As of now, I remap one key to display power menu to toggle on/off for expanded desktop.
[Xposed Framework Modules] gerhardo:
I assume you mean that the log is empty after the reboot, which is normal, the app parses the log after a reset.

To debug this, I assume that dk_cool-zero needs a logcat, captured when the problem occurs.

logcat instructions: http://xdaforums.com/showthread.php?t=1726238
[Xposed Framework Modules] TopTomy:
Hey guys,

Just downloaded this module and set my volume keys to power on the screen + unlock the device.

is it going to affect my battery life? or will it prevent my device from getting into deep sleep?

THX
[Xposed Framework Modules] coolkaas:
no. phone will sleep completely. this module only hooks (replace) some system code for pressed keys and give a more actions choice for us.

while you not press any key phone sleep as usually.
[Xposed Framework Modules] TopTomy:
Hey, thanks for the reply and explanation. Cheers
[Xposed Framework Modules] gerhardo:
Probably not what you want as a direct action. Expanded Desktop is implemented in the ROM (or Xposed mod, like GravityBox). Reimplementing in this mod would not sync with other settings.

If there is an app activating, you can use it now.

However, if App Shortcuts are implemented, Expanded Desktop could be toggled anyway (maybe using Llama/Tasker and intents if no shortcut is available).
[Xposed Framework Modules] ptaq1234:
Hello:)

I'm sorry, but i didn't read this whole topic. I have an issue on my desire x. When I short press app change button (the one on the right) it makes it a long press all the time, no matter how long I really press it. It is very annoying cause I love this app but with this bug it's unusable for me :( could u make a fix please?
[Xposed Framework Modules] gerhardo:
The AppSwitch/RecentApps key seem to be specially handled, the up event is absorbed in Android, I see this in the emulator too.

So only the Recent App key can only map a single event (right now it is long-press action, could be click too), no multi events either.

Edit: The test was incorrect, ( an error in my mod), but a similar problem could occur in the standard module too.

Fixed this in my mod (link on page 131), patch not accepted yet.
[Xposed Framework Modules] ptaq1234:
Thanks for the reply :D

I was downloading different versions, to chceck if this bug is occuring all the time. I figured out that version 2.3.8 is working almost perfectly. Re-map works perfectly (no long press bug), but in this version there was a change with vibrations (they are longer and stronger) [changelog: added custom Vibrator class to fix haptic feedback on TouchWiz ROM's].

I think this change caused vibrations longer than intended. I also think that this change can be easily reverted by decompiling this version of app and changing Vibrator class to match older version. I'm not a developer, but I think I can handle this :) The only problem in my case would be to find this :D

Anyway thanks for help, and if you know where should I look for vibrator class you would save me much time :)
[Xposed Framework Modules] gerhardo:
There is indeed a problem in the code. My reproduction was incomplete, in my mod.

So AppSwitch key is passed on.

See my prev post.

There has been many changes from 2.x to 3.x, I would not expect replacing classes would work.
[Xposed Framework Modules] ptaq1234:
I believe there is everything ok (for me) in version 2.3.8. As I said earlier - works like a charm. I'm using it for 2 days now. No bugs, nothing. This is the version Kill App function was added (this function I wanted so badly :D ) In version 2.3.5 however, there was no kill app function, but vibrations were perfectly fine. So my guess was to take vibration class from 2.3.5 to 2.3.8 (revert changelog a bit) ;)

Please tell me where can I find it so I can at least try.

Thank you :)
[Xposed Framework Modules] mkdr:
Doesnt work on my S3 with SlimKat rom. Isnt it compatible? It doesnt recognize any hardware keys. Ive read on page before, that I should try an older version, and I tried XPosedAdditions-3.1.4r which works. Please fix this, I want to buy the Pro version.
[Xposed Framework Modules] gerhardo:
For those with problems with 3.2.2: Someone need to enable logging, use the extract log feature (or adb logcat) to pinpoint the problem.

You can even email dk_zero-cool from the app itself, otherwise post it here.

(I would expect the problem to be in the init phase, maybe related to Xposed version.)
[Xposed Framework Modules] mkdr:
The dev should know what he had changed. <= -3.1.4r working, > -3.1.4r not working.
[Xposed Framework Modules] egingell:
Doesn't mean you shouldn't still provide logs.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] gerhardo:
There is no way a devloper can know all changes all ROM developers make. XPosed is about hooking into the Android internals.

After 3.1.4 there has been a bunch of error checks, it may actually be one of them that fails...