yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] dk_zero-cool:
Sorry but this seams useless. If you are playing media, then you will not change the ringtone volume and if you are not playing anything, then just don't press those buttons.

Alternatively buy the pro version, set volume to execute a tasker task and have that task control what to do with your button. This seams exactly like one of the things Tasker was built for.

And b.t.w, some people do use volume for more than just media. I for one use the volume down a lot if my girlfriend calls ;)
[Xposed Framework Modules] UweRammelt:
Hmm - I re-started it and tried again.

It chatches the Power switch, Volume Up and Volume Down, but not the Home or the Back key :(

[IMG="Power is catched, but not Home or Back"]http://abload.de/img/xoomxposedadditionsk4j8f.jpg[/IMG]
[Xposed Framework Modules] ImpheOtus:
I think Xposed Additions only works remapping physical keys, not software ones?

I'm not sure though.
[Xposed Framework Modules] dk_zero-cool:
Well that makes sense. Software keys are not buttons, it's an app. This module does not inject applications, it only works on real buttons that parses through the input manager.
[Xposed Framework Modules] fenchai:
Hahaha i guess sone people really use it.

Well sometimes when you are watching a video, you want to lower volume down, but the video begins to load(this means that no video is playing) so volume is set as ringtone...then when it finishes loading, media buttons are set if pressed. This is very irritating because my internet is not that bad, neither great nor bad so youtube, twitch.tv, browser videos ;) sometimes lag and this problem occurs... I will try to use tasker, but if you can, please integrate this option in xposed additions :D

(I hate tasker interface btw, I use automateit)

Sent from my SM-G900H
[Xposed Framework Modules] gerhardo:
I find it more natural to let PreviousAppliction switch to the previous application in recents lists, even if you have happened to "exit" with back button. This is how I use the function.

The clearest argument is that the description of the function is switching to the "app previous in the Recents list" rather than "the last app in the Recents list you did not exited from the launcher with back button".

Sometimes I want to replace the function with switch to 3rd previous app instead...
[Xposed Framework Modules] dk_zero-cool:
It's not switching to the last recent app you did not exit with back. It is switching to the previous app from the running apps list, it does not use the recent apps list. And if you exit the app, it will no longer be in the running apps list, which makes sense since you closed it. It is two different apps lists. Also the button is meant to switch back and fourth between to apps, so why would you close them before switching?
[Xposed Framework Modules] dk_zero-cool:
Added a poll at the top of the thread. You decide how this action should work.
[Xposed Framework Modules] gerhardo:
It is a matter of habit, I could learn to use Home/Back myself to fit this function - maybe it is even a feature.

But if you do not see the difference in other situations (Recents list) and it is something that has to be explained I suggest changing it. (This is how I implemented this in my mod.)

A poll is good.
[Xposed Framework Modules] Nishchay1:
Here it is brah

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

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

W/PackageManager

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

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

W/WindowStateAnimator

Window WindowStateAnimator{42869f88 Starting com.spazedog.xposed.additionsgb} destroying surface Surface(name=Starting com.spazedog.xposed.additionsgb, identity=10), session Session{42858540 502:1000}

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

W/WindowStateAnimator

Window WindowStateAnimator{42b6adc8 com.spazedog.xposed.additionsgb/com.spazedog.xposed.additionsgb.ActivityMain} destroying surface Surface(name=com.spazedog.xposed.additionsgb/com.spazedog.xposed.additionsgb.ActivityMain, identity=11), session Session{42b28448 2248:u0a10130}

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

W/WindowStateAnimator

Window WindowStateAnimator{42b28688 com.spazedog.xposed.additionsgb/com.spazedog.xposed.additionsgb.ActivityViewerLog} destroying surface Surface(name=com.spazedog.xposed.additionsgb/com.spazedog.xposed.additionsgb.ActivityViewerLog, identity=13), session Session{42b28448 2248:u0a10130}

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

W/WindowStateAnimator

Window WindowStateAnimator{42b6adc8 com.spazedog.xposed.additionsgb/com.spazedog.xposed.additionsgb.ActivityMain} destroying surface Surface(name=com.spazedog.xposed.additionsgb/com.spazedog.xposed.additionsgb.ActivityMain, identity=15), session Session{42b28448 2248:u0a10130}

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

W/WindowStateAnimator

Window WindowStateAnimator{42aba0f0 com.spazedog.xposed.additionsgb/com.spazedog.xposed.additionsgb.ActivityViewerLog} destroying surface Surface(name=com.spazedog.xposed.additionsgb/com.spazedog.xposed.additionsgb.ActivityViewerLog, identity=16), session Session{42b28448 2248:u0a10130}
[Xposed Framework Modules] endofwed:
my home button on my galaxy s2 is not functioning properly. I think what happened was it got pushed too many times over the year and now its jammed, causing it to resent itself and glitch randomly at times.

When i used xposed additions to disable the home button (disabled on wake, not awake, lock), it still functions (somewhat). When i press the home button continuously, it will reset the phone. Is there anyway to permanently disable the home button?

In additiion, I remapped the power button to the volume up button. After the phone is sleep, I cant wake up the phone anymore with the volume up button. I have to plug it in the charger to wake it up. Then everything works as normal but if I dont use the phone for a bit, the volume up button doesnt wake up the phone anymore and with the home button disabled, I have to wake it up manually with the usb cord.

Any suggestions?

sorry for my english
[Xposed Framework Modules] kotey:
You can't, since Android disabled the volume button when sleep. I think I read that somewhere in this thread some days ago.

But don't worry, I think I can help you with that :)

I'm using the same phone, SGS2. Only that my buttons are not broken but I want to keep it that way so I resorted to software solution.

For the capacitive buttons, use Xposed Additions obviously. (In my case, I'm using GravityBox on Jellybean device and Xposed Addition on Gingerbread device, same goal)

Now for the physical button, I use SmartScreen (novum.inceptum.smartscreen on Google Play) so I don't have to press Home or Power button to wake my phone up. Only drawback, you have to use a flipcase or put it in pocket/bag/something to make it sleep automatically (or not, just use the wakeup function only, your choice). And it's using the proximity sensor so some battery there (in my case roughly 2-4%)

This is my setting for SmartScreen. So far it works great.

Screen On - threshold 2sec, delay 1sec, interruptible

Screen Off - delay 1.5sec, lock delay 1sec, only in portrait, only on home screen

Sleep Mode - Off (don't enable it otherwise phone will sleep and turn off sensor)

I tried some others but only this one have the "only" rules so I didn't accidentally turn my screen off during browsing or playing games, so I'd recommend it.

In addition, I also use Button Saviour and added virtual Power Button. You can get that also from GravityBox Pie Control but it didn't work great for me.

So, you'll need Xposed Addition + SmartScreen at the least. Other apps are optional but also recommended.

Note:

All of the apps can work in free (aka no donation) mode, but of course if you can, donate versions are better and you are supporting development.

P/S: Sorry I don't mean to hijack or advocate other app in this thread, only it seems related and my intention is to help, nothing more. Peace.
[Xposed Framework Modules] gerhardo:
Waking with the volume buttons is not in most device HW. However, it seems to be so in SGS2. In CyanogenMod (dont know about other ROMs, maybe in stock too) you can configure the volume keys to wakeup the device. (Maybe sufficient to change the keylayout file if not in options, goggle for WAKE_DROPPED).

Edit: I do not think this module should be involved in the wakeup. While it could work on some phones (should be similar to adding WAKE_DROPPED), there will be too many questions for others.
[Xposed Framework Modules] kotey:
"Recent Apps" didn't work on Galaxy Y

3.2.2 - worked fine except I have to remap Home button in screen off to power.

3.3.0, 3.3.1 (including beta and pre) - immediately downgraded to 3.2.2. didn't work (buttons not responding, including Home/Power)

3.3.2 - seems the issue are fixed but now "Recent Apps" didn't work.

Button mapping works (long click Menu), tried other function (eg Power) and confirmed working. Downgrading to 3.2.2 again for now.

Also, screenshot option seems unavailable on the Galaxy Y (because of stock rom?).

Edit: Tested v3.3.2 on a Chinese MTK ICS phone. Recent Apps working. Screenshot working. Does this mean these problems are Gingerbread or Samsung specific?

Samsung Galaxy Y stock Gingerbread 2.3.6
[Xposed Framework Modules] Wiidesire:
[MENTION=1954283]kotey[/MENTION] Screenshot function with home+power also doesn't work for me with this module (all versions I have tried so far) on i9505 Galaxy S4
[Xposed Framework Modules] endofwed:
Wow, thank you so much!

the smartscreen app did not work in my case, so i ended up using gravityscreen. I did not know these kind of apps existed.

:)
[Xposed Framework Modules] dk_zero-cool:
This does not contain any important log entries at all, only a few warning. Not sure where you got it, put if you used the log viewer in the app, it will not work. This only collects warnings and errors. You need a logcat app or to use ADB on your PC. Also, please include a file or a code block when adding to the thread.

And to others.

Some Stock ROM's checks the device id for some of the actions, like combo screenshot. This has no fix, so no need to keep reporting it. There is a screenshot action in the module, just make a manual screenshot remap option, it's why it is there.
[Xposed Framework Modules] mihapodb:
Helo!

I am totally frustrated because my home button on Note2 is not working from the time I flashed KitKat 4.4

First I was using DN3 and now JellyKat and on none of them home button is not working. I tried so many things and nothing. At least I tried Keynumber Tracker and it did track all the buttons with correct number, but not home key. Like I did not press anything.

So I tried Xposed Additions PRO and it recognises Home button, and whatever I set, it does not change. My home button is only for waking the phone and nothing else. I really misses going to homescreen :/

Is there any suggestion what can I do? Thank you!

PS: I am afraid that is it because all of those roms using S5 style UI where home button is useless for me. How can I get back old Note 2, S3, S4,... home button behaviour?

PS2: now after using xposed additions keynumbertracker shows for every button a ZERO. No any other number :/
[Xposed Framework Modules] dk_zero-cool:
If your ROM is ignoring Home, then not even Xposed can help. But you can cheat. Buy the Pro version and set your Home key to Launch your Launcher app using App Launch. Same result.

About Keynumbertracker, it properly ignores injected keys.
[Xposed Framework Modules] CZ Eddie:
In a rush to head out the door, so apologies if this has already been discussed.

Galaxy Note 3 running custom TouchWiz 4.4.2 ROM.

After a recent update of Xposed Additions, my screenshot key combo no longer works. The combo is hold down power + home and used to work fine.

I tried wiping data on the app but still have the same problem.

Also, if I change the hold-down time from "medium" to "short", then when I press the power button to put the phone to sleep, it will quite often bring up my power menu instead. I think the "short" duration may be just a bit too short, or it's just flakey on my ROM. :)

I'm an Xposed Additions Pro user and proud. Thanks for the cool app! :good:
[Xposed Framework Modules] scopefield:
Does anybody know if it's possible to modify the duration of the long press for each button rather than having them all as slow, normal, or fast? I like fast (otherwise tap and hold home button and volume up/down is way too slow), but the power button is way too sensitive. Any way to change that?

edit: @ CZ Eddie, having the same problem. I like all the other buttons for short, except the power button.

Also OP, awesome job with the app. Pro version works wonders for anybody on the fence about getting it :)
[Xposed Framework Modules] CZ Eddie:
I forgot to mention that after one of the recent updates, my mod to have the Note 3's capacitive menu button be single click = recents, which works fine.

But the long click = menu is giving me a lot of problems. In Titanium Backup It occasionally blips my menu up and then it goes away.

And in Nova Launcher, it consantly loses the ability to open settings from the desktop, you know, where you get the option for either system settings or Nova launcher settings.

If I open Xposed Additions and go into the options there, then reboot, it works again for a little while. Then suddenly the long press = settings stops working again.

---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------

Maybe make short = 80ms?

It's obviously too short for many users phones power buttons.

And to be honest, your 100ms feels a lot longer than the 220ms I have set on my SwiftKey keyboard.

Don't ask me how that's possible, but it's true. :D

Your "normal" feels like a full half second or more.

---------- Post added at 04:07 PM ---------- Previous post was at 04:00 PM ----------

There is no way your ms are working properly in my Note 3. :eek:

Hopefully this will help you a little?

75ms = 0.075

100ms = 0.10 seconds

150ms = 0.15 seconds

screen capture software
[Xposed Framework Modules] dk_zero-cool:
Not really in the need for conversion help, I have a high level in math and am pretty aware of the conversion between ms and s.

What I am wondering, is whether or not people are actually talking about the double click speed or the long press speed. Or if people are not aware that double click is invoked on second and/or third key up and not on key down. The table that I posed is not the long press time outs.
[Xposed Framework Modules] kotey:
That, I think is well known ? I can't do the combo key either ever since. But the issue I'm posting there is another.

But still, thank you now I know there are other devices with some same problems.
[Xposed Framework Modules] CZ Eddie:
Long press for me. :good: I don't use double-click for anything.
[Xposed Framework Modules] dk_zero-cool:
Well Long Press should perhaps be changed a bit. These values are 200, 500 and 1000. Maybe 200, 350 and 500 would be better here?
[Xposed Framework Modules] CZ Eddie:
Ahh, that makes sense. :)

Your proposal sounds great, too! Pretty much that, or like this:

250 | 375 | 500

Thanks for your help. :good:
[Xposed Framework Modules] dk_zero-cool:
On my todo
[Xposed Framework Modules] scopefield:
Long press for me too. The power button is extremely annoying--most of the time, I'm prompted with the power off menu and I barely hit the power button.
[Xposed Framework Modules] kotey:
I'm having different experience. I don't get the power off menu but I get the recents screen when pressing power button (while holding home button). So screenshots I'm getting have recent window on top of it :p
[Xposed Framework Modules] Ninolina:
Thank you for the update, but it's too long now. :( Short option is not short as it should be. There was already option to choose longer so maybe it was not necessary to change the Short duration?

Thank you! :)
[Xposed Framework Modules] egingell:
Why not add a slider or text field for custom delay times?

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
Short has only gone from 200 to 250. The default in Android is 500.

This module should fit anyone, also people who does not know much about ms and such. So textfield is out of the question. A slider might be an idea, as long as this exist from API 9. As long as GB is supported, I am a bit limited in some areas, and I am not gonna create a custom slider just for some duration time which already has 3 times as many options as stock Android.
[Xposed Framework Modules] egingell:
The slider (SeekBar) has been around since API 1.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] Ninolina:
Thank you for answering. :) I just do feel the difference. The slider sounds great! :)

Thank you for all your effort. ;)
[Xposed Framework Modules] fenchai:
Hey dk_zero-cool!! nice update! the torch added is fantasticccx :D great job, my money was wurth :D

Sent from my SM-G900H
[Xposed Framework Modules] killoid:
bugs faced on my galaxy y duos,stock deodexed 2.3.6 rom-

1. even if i haven't mapped anything or added any buttons,when i press these hardware keys (home,volume up & down) thrice quickly,they produce haptic feedback.

2. when adding power key 1st on the key list,it brings up the power menu which can be seen by long pressing the power button only & doesn't go away even if back button is pressed until an action is chosen in the menu.

3. after adding the power button on the key list (not mapped for anything yet) , when i long press the power button,it performs screenshot! (which should be performed by pressing home+power only if i haven't mapped it to another button) & it is solved automatically after some time!

4.the home+power button combo does screenshot but everytime it brings up the recent apps list menu after screenshot.

5.there is no screenshot action in the action list to map it to another button.

6.the error log list is empty either debugging is on or off. screenshot attached.

log attached for more information.

p.s. i am using pro version & all the settings for double press duration,long press etc. are by default what is chosen by the module.
[Xposed Framework Modules] dk_zero-cool:
Will look at this

Will look at this

Will look at this

Sorry, but I am done supporting this feature. Especially on Stock ROM's and especially on Samsung Stock ROM's.

Screenshot was not supported in Gingerbread, so Samsung (If supported) has added their own to this, which means that it is done in different ways than on normal AOSP ROM's in later versions. I can try to take a look, but there is a limit to how much time I am going to spend digging in Samsung's smali codes. This module is based on AOSP with some tweaks to make it work better on other ROM's as well, but since I can't get a source for the others, there is a limit to the non-opensource version support.

The error log is for errors, not debug, hence the 'error' part. So empty just means no errors.
[Xposed Framework Modules] egingell:
5. You can use the command line to take screenshots.

su -c /system/bin/screencap DESTINATION

It doesn't put the file info into Media Storage, though, and there's no feedback (vibration, screen flashes, etc.).

Edit: The screencap binary is in TW JB 4.1+. I don't know about any other flavors.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
GB did not have any kind of support for screenshot, at least not without a few root tricks. Something with restricted access to the framebuffer I think. Samsung added their own custom support in their 2.3 versions, but since they don't provide source, I can only look at smali files which are not very fun to read through. And looking at one ROM might not even be enough, since Samsung cannot stick with any standards. They change things on each release, which makes it difficult to add support for them.
[Xposed Framework Modules] t61p:
Hi. I would like to report one issue about unwanted device wake-up by clicking hardware button like Home/Volume UP/Volume Down button other than Power button. This happens under a certain condition with App Settings Xposed module.

Here is an example to reproduce.

1. enable pattern lock of the device.

2. enable 'Show when locked' in App Settings module for an app.

3. set Home button > Screen Off > Click > 'Disabled' in Xposed Additions.

4. launch the app and turn display off (by clicking power button).

5. click Home button and the device wakes up.

I confirmed it happens on SGNote2(stock ROM 4.1.1) and HTC-J(stock ROM 4.0.4). Logcat is attached below. Would it be possible to solve the issue?
[Xposed Framework Modules] dk_zero-cool:
App Settings? If you have a conflicting module, then that is not a problem for this thread. You should only have one module hooking up the key handling methods, if you have more modules handling the key events, then that is your problem.
[Xposed Framework Modules] t61p:
I reported the issue because I was not sure if it is really module conflicting. As far as I know 'Show when locked' in App Settings just skips pattern lock for an app. It's anyway strange that hardware button other than Power button wakes the device, without remapping it to Power key or even the button is explicitly Disabled in Xposed Additions. (of course if there is no key hooking by other module). A similar issue, device wake up by volume button, has been reported at http://xdaforums.com/showpost.php?p=54160703&postcount=1692. Actually I'm having the same issue and I've been waiting for your reply. It might be somehow related.
[Xposed Framework Modules] dk_zero-cool:
For any input device, Capacitive, hardware, externals etc. there is a config file. In this config file you can define any key as a wake key. This is the standard in Android. Some ROM's, like Samsung ignores this and hard codes power (and some times Home) to be the wake key. This module however fallows the standard, so if a key is registered as a wake key, the screen will be turned on. If you don't like it, then either change the device configs to remove the wake flag, or set the key to disabled in the settings.

If disabled does not work, then this is because you have some other module that interferes, and then it is not my module that turns on the screen.
[Xposed Framework Modules] t61p:
Thanks for the prompt reply. As you mentioned a lot of time, Samsung ROM doesn't follow the standard way then it is problematic. What I can do for now is just accept it...

Anyway, Xposed Additions is really useful app and I like it very much. Thanks again for developing. :)
[Xposed Framework Modules] Smyl3:
The stock screenshot button combo (power, vol-) doesn't work after I enable this module on Android 4.1.2. Not samsung, miui or other custom rom.
[Xposed Framework Modules] fenchai:
I guess thats a price you pay for...

change it to double home press+ hold, its easier ;)

Sent from my SM-G900H
[Xposed Framework Modules] n8r:
Context: Lock screen camera

Had some problems getting shutter buttons on the lock screen Camera app. Looks like the Camera app running on the lock screen is just detected as the lock screen. I created https://github.com/SpazeDog/xposed-additions/pull/13 to address that. Here's to a great app!

(Running Additions Pro, on Moto G, stock 4.4.3, and love it!)