yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] dk_zero-cool:
Let's start with the most simple thing here. Trying to block a device restart will not protect your device. It's like people thinking that a harddrive cannot be accessed because you have a Windows Login with a password. You can always restart a device, if not by a power press, then by removing the battery or simply creating a short circuit via the usb input.

It is true that this has been added to the module. But only for devices missing this feature (which has mostly been a few watches). It is normally built into the kernel and is used to ensure that a devices can always be rebooted in case of UI crashes where you cannot access the power menu. I can add an option to disable this, but it will not be in the current version. I am currently working on rebuilding the whole module, UI included. This has put the current version into a bugs-only state and no new features will be added to it.

I do encourage you to find other means to protect your device as you current solution really only provides a false idea of protection. There is no way for you to ensure that your device is not shutdown. Likewise there is no way to protect your SIM from being removed, signals being blocked, boot loader being cracked and device wiped and so on. Anyone with a physical device can do whatever they want. The only thing that you can protect, is the data on the device via encryption. Trust me, if I stole your device then you would never hear from it again. It would not mater what kind of anti-theft software that you had installed.
[Xposed Framework Modules] egingell:
I've told several people that all I needed was a zip file (or ADB in some cases) to disable a lock screen and delete security apps. The phone doesn't even need to be booted up. It's scary how insecure these things actually are.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
This is like with any type of device, which is also why I have full disk encryption on all my devices, desktops, laptops, phones etc. You cannot make sure that your devices is not stolen. All you can do is make sure that no one can access the data currently on them. At the same time you can also make sure to always have backups so that you do not loose that as well.
[Xposed Framework Modules] jiznon:
The one function I want to use this module for is not working:

Long hold Back button -> do anything (I want previous application)

I've tried forcing haptic feedback with no change. I tested actions with other buttons and they work fine (long press power button -> previous application.)

OnePlus One running latest CM12S (stock ROM for the phone). Any ideas?

**EDIT: Having the module installed an enabled also disables the baked in Tap To Wake feature of the ROM. Had to uninstall until these issues are resolved.
[Xposed Framework Modules] NoLoHeDecidido:
Hi guys,

The power button of my phone is broken. More specifically, it is so so sensitive. If I touch it just a little bit, screen turn off, the power/reset menu appears... Who knows what happen when the phone is in my pocket... :D

So, I have thought disable the power button with this MOD (for click and for long press, and when screen is off, on, or lock), but the point is.... what will happen if my phone turn off accidentally? or the battery goes down 0%? What will be the power button behavior when the phone is off? No behavior? :( Normal behavior? :)

I hope I explained correctly, and sorry for my English if you find any mistake. And thanks for your answers!
[Xposed Framework Modules] dk_zero-cool:
This module only works on buttons and the OnePlus One does not have any Back button. The software keys are part of an app within Android, it will not be affected by this module.

This module only works while the device is booted into Android. If it is turned off, the module is not loaded and does not work. So your button will have it's normal behavior.
[Xposed Framework Modules] jiznon:
The OnePlus One has a Back button. I'm not referring to soft keys (onscreen buttons). I'm referring to the Back button on the OnePlus One.

The OnePlus One has a Menu/Apps button, Home button, and Back button. All capacitive. As well as a volume rocker and Power button, which are tradition hardware buttons.

Are capacitive buttons considered soft keys?
[Xposed Framework Modules] egingell:
No. At least not on either of my phones.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] jamesbond22:
When module is activated then all video I can not watch in horizontal position. All video on strength displayed in a vertical position. It is bug?
[Xposed Framework Modules] NoLoHeDecidido:
Cool! Thanks!
[Xposed Framework Modules] mihapodb:
If someone still wondering if it is working on android 5.1 - it DOES NOT. I can get xposed framework flashed and boot normally, but when I enable xposed additions, it does not boot.
[Xposed Framework Modules] dim^n:
How to save settings on 3.5.6? I cant use any other version cause they cant do anything! I want to use tasker and per app settings, also two buttons setting. Strange, that the app cant save its own settings... Or it have temp settings? Before reboot app "remembers" it, and it should be hidden settings somewhere. Where I can find it?
[Xposed Framework Modules] a.fontenele:
Hi [MENTION=3147360]dk_zero-cool[/MENTION]

For some reason I don't know I am now facing the same issue I had some versions ago... The torch...

I long press the power key to turn it on while the screen is off, but now it only works if I turn the screen on and off and then long press the power button. Any ideas?
[Xposed Framework Modules] TheDynamo:
Hi, Just purchased today and tested on amazon fire phone that has been rooted on current Kit Kat. When i press any of the physical buttons to map nothing happens within the app the phone continues doing what it would normally do when button was pressed.

I know it has only just been rooted/updated and is not a stock android but can you advise why it is not working?
[Xposed Framework Modules] ajoh99:
Purchased pro version just now, having some issues. Using an LG F3Q, when I enable support for the hardware keyboard, I can custom map keys like I want to, but when I use the keyboard for typing, some keys don't work, and the FN key does not work, preventing me from using characters like @ ? and some others.

I saw the post regarding something similar on a slide out keyboard phone from July last year. Tested all releases from 7/10/14 to the current. Keyboard only works with versions after the new remap engine was added that allows support for joysticks and etc, where there is a list of 3 options to choose from. In all versions where my keyboard keypresses are detected, the FN key doesn't work in normal use.

How can we fix this?
[Xposed Framework Modules] jellybeangod:
working on 5.1?

I'm trying this on the alpha 5.1 and it loads OK but when I try to select a key to remap I'm not offered any choices to make a selection from. Just me or is this due to the alpha nature of 5.1 xposed?
[Xposed Framework Modules] egingell:
You don't choose the button, you click the button when the popup shows - it listens for the click.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] AssassinsLament:
I couldn't get it to detect my external keyboard click, so I don't think it's working right with Xposed 5.1
[Xposed Framework Modules] egingell:
And is "allow external devices" checked?

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] AssassinsLament:
Yep.

I'm using a JoyCon Exr to send keystrokes to it, although that shouldn't matter because it emulates a hardware keyboard. It worked fine when I had android 5.0.2 on it and the official Xposed. I'll test it again later.

Edit:

Made sure to have external devices checked, then tested again, and it still doesn't work.

I even tried the device's (Nexus 7 2013 LTE) Volume Up and Volume Down buttons and they aren't detected either.
[Xposed Framework Modules] beezar:
Tried searching, but can't find for the life of me how to remap my recent apps button to pull down the notifications bar on my Note 4. Any ideas?
[Xposed Framework Modules] egingell:
There's no option for it. You'll have to get Tasker and make a task for it.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] Einheit-101:
Is very buggy @ HTC ONE S 4.1.1 and doesn't work 99%

Does not work at all @ Motorola Droid Maxx 4.4.4,

But power button stops working after installation.

Sorry, I can't use this :D
[Xposed Framework Modules] beezar:
Thx, got this to work with a Tasker shortcut, but noticed there was a significant delay between pressing the button and the notification pull down coming down. Any faster option?
[Xposed Framework Modules] egingell:
I don't think so.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] a.fontenele:
There is an app called SideControl:

https://play.google.com/store/apps/details?id=com.jamworks.sidecuts

You can use gestures or simply evoke the notification pulldown shortcut from this app using xposed additions...
[Xposed Framework Modules] a.fontenele:
[Duplicate]
[Xposed Framework Modules] wredmatic:
Please help;

Xposed Additions won't intercept any keys presses. When it prompts me to press a key, and I do, nothing different happens (i.e. hitting the "volume up" button just increases the volume). The plug/unplug actions still work though, so the module must be installed properly. I get no error messages or anything either.

Perhaps the newest lollipop version for the 2013 Nexus 7 is not supported yet? It worked fine under 4.4.4, and it's listed in the "confirmed working" xposed modules (for lollipop)., so someone (perhaps with a different device) has gotten it to work.. After upgrading to lollipop I installed the files in the xposed lollipop thread (xposed-sdk22-arm*.zip and XposedInstaller_3.0-alpha*.apk) and version 3.5.7 of Xposed Additions.
[Xposed Framework Modules] SairesArt:
Bugs bunny on OPO

Ultra awesome module, but unusable, because:

Breaks Double Tap to wake on CM12 (OnePlusOne), even when nothing applied. Basicly, install Module, can't use double tap to wake, deal breacker.

Wake from Hardware buttons (Assinging Power to Homebutton) doesnt wake/ work at all

No option for "under all conditions", have to manually go through, screen off, screen on and lockscreen

(minor thingy, I suppose it's unfixable) small 50-100ms-ish delay compared to normal non module assign functionality. [no xposed addition, volume up reacts after 50ish ms, with xposed additipnd volume up reacts after 100ish ms)
[Xposed Framework Modules] dk_zero-cool:
Then you have a CM12/Kernel issue, cause others with this device has gotten this to work after my latest fixes.

Again a kernel issue. The one you are using is properly disabling hardware buttons while the device is asleep. If the kernel does not send the key to Android, the module never gets it. Home as Power is working fine on other devices, mine included.

This module was never meant to reach this size and as such the backend is not built for advanced conditional checks. I am in the works of making a new version with a more complex backend that should gain much more flexibal choices. But these things take time, and I don't have much of that at the moment, so this will hopefully be done some time during the end of the summer.

Avoidable. This is how Android's key injection system work and since this is Native, it cannot be changed via Xposed. Everything related to Xposed Framework is based on hacks. It will never be perfect.
[Xposed Framework Modules] jiznon:
OnePlus One here, stock kernel, same issues.
[Xposed Framework Modules] xtam:
How much this module affects battery life?

Does it check periodically for press buttons actions?

If i will install deep sleep xposed module, will it work?
[Xposed Framework Modules] dk_zero-cool:
The module does not have any services running in the background. It uses hooks to attach itself to several system functions, like the one that receives key presses from the kernel. Xposed modules are split into two parts. One is the normal app that can be used to configure everything. This part can be closed, put to sleep and so on, just like any other app. The second part is a module that get's attached to other processes during boot. This part will stay there as long as the process it is attached to, stays open, which in this case is the main system. In other words, even if you delete the app, the module will stay active until you reboot.
[Xposed Framework Modules] xtam:
Thanks
[Xposed Framework Modules] robertogl:
Question for people that tried that module on Android 5.1.1: if you restore a backup of the app (or you update Android without wipe) Xposed Additions works or it needs a new configuration? Thanks :)
[Xposed Framework Modules] dk_zero-cool:
Configurations is newer versions of the module is handled by the application part, which means that it works just like with any other app.
[Xposed Framework Modules] robertogl:
Yes, i've asked that because some people are reporting that on 5.1.1 they can't set any button from Xposed Additions, but in my case i don't need to do that, if the app 'remember' the old configuration. Maybe the module works with the old configuration...
[Xposed Framework Modules] wredmatic:
robertogl: what version are you running now? 5.0.2? If so, let me know how this works out for you. If you can set buttons on 5.0.2 and not on 5.1.1, I might just "downgrade" back to 5.0.2.
[Xposed Framework Modules] robertogl:
Tested right now on 5.1.1 (CM 12.1). Xposed Additions is working: i've updated without wipe so i've not done the configuration again, so i don't know if that works, but coming from cm12 it works ;)

Thanks [MENTION=3147360]dk_zero-cool[/MENTION] !
[Xposed Framework Modules] SairesArt:
I'm in francoKernel. And the current Official CM12 update (5.0.2).

So is it safe to say Xposed Addition is not compatible with fk and fk doesn't send wake signals from hardware buttons?

Would the correct thing be contacting franco for a fix?
[Xposed Framework Modules] dk_zero-cool:
It does not really have anything to do with compatibility. The kernel if the first to get any key presses, Android's framework is the last. Xposed modules can only add hooks to the Android Framework, we cannot change the kernel during runtime, so if the kernel does not send the key presses to the Framework, it is not possible to act on them.

But yes, I would start by writing to the developer
[Xposed Framework Modules] techdog:
FYI...

I am on SlimKat 9, dkp kernel (latest version). I have been having issues with my timers and alarm clock for the last month and a half and could not pin down from where the issue was coming. After installing/re-installing a bunch of different apps, it appears the issue is coming from xposed Additions AFTER version 3.5.0. I have no issues with versions 3.5.0 and before but after that my timers and alarms do not work correctly.

The only key that I re-map is the Home key. Installing Xposed Additions does not cause any problems until I Add the Home key and map answering calls, the timer/alarm issue starts. (I have not experimented with adding the Home key and NOT set it for answering calls, since that is one of the primary functions that I want.) I don't have to add any other key re-mapping to cause the problems.

Just thought you would want to know. For the time being, I am going to stay on 3.5.0.

Thanks for all of your hard work.

techdog
[Xposed Framework Modules] dk_zero-cool:
Not sure why it would seam this way, but there is no way that this module can break your alarm. This modules ads hooks to the class controlling buttons, it does not touch any of the alarm classes. There is nothing related the alarms going through Xposed Additions.
[Xposed Framework Modules] techdog:
Let me explain what I see happening....

I will set a timer for 10 minutes, for example. After 12 minutes, I notice the timer has not gone off. If I hit the home key, the timer goes off. For some of the timers that I have experimented with, the timer display is -2 showing that it has been going off for 2 minutes. A similar behavior is exhibited with alarms. So, you are correct, the alarms are firing but they are unable to unlock the screen to display the alarm or to have the sound enabled.

Thanks.
[Xposed Framework Modules] dk_zero-cool:
That still has nothing to do with buttons. If an alarm wants to turn on the screen, it uses the Power Manager. If it wants to play audio, it uses the Audio Manager. This module injects itself into the Window Manager, which has nothing to do with neither Power Manager nor/especially Audio Manager. I really fail to see how this can have anything to do with this module.
[Xposed Framework Modules] kornelius1982:
Excellent app!!

I`m using this (paid version) app to arrange every button as I was using in CM roms.

No issues and no complains at all! :good:
[Xposed Framework Modules] techdog:
Ok. Well.... I will have to continue looking.... This issue is driving me crazy.
[Xposed Framework Modules] dk_zero-cool:
Yes, I would love to help, but your issue affects things that is not related to this module. Try disabling other modules one by one, it could be a conflict problem.
[Xposed Framework Modules] Shahbaz23:
Screen Off Button Mapping

On my Wiko Rainbow, none of the screen off button mapping are working... May be the kernel doesn't support it or so... but can anyone tell me how can I make a task in tasker so as to wake my screen by pressing on the keys when my screen is off :confused:
[Xposed Framework Modules] dk_zero-cool:
If this is a kernel issue, it is simple to check. Do your power buttons work while the module is enabled? If so this is a kernel issue as the module also handles screen on/off for the power button, even when it is not remapped.

About your Tasker question, this will not work. If Android and thereby the module does not receive any button presses when the device is sleeping, it will not receive them to execute Tasker Tasks either. Nothing in Android get's any key presses, because it never leaves the kernel (If the above is the case). Nothing will work, no app, no module, no shell script.
[Xposed Framework Modules] Shahbaz23:
Yes my power buttons work even when the module is on... I don't have any problem with the power button or volume rockers with the module on or off...

Regarding the Tasker, yes you are right, I got your point...

Is there any way I could wake my phone by long pressing the home key (or any other key)? :confused:
[Xposed Framework Modules] dk_zero-cool:
You can use any key that the kernel keeps active during sleep. The power button for example will of cause be enabled in every kernel, volume keys are on some/most devices, home might provide problems if your kernel disables it during sleep. But any key that works during sleep can be configured to wake the device with click, double click, long press etc. But the module cannot change any kernel behavior, so it is up to your kernel.
[Xposed Framework Modules] kornelius1982:
Hey bro,

Is there any way to disable home button wake in TW roms?

I tried home button in lockscreen condition, ticked single click `disabled`, but home button still wakes the phone.

Thanks for your awesome work!
[Xposed Framework Modules] mando41:
Are you trying to keep the phone from waking with the home button when the screen is off? If so, make the condition screen off instead of lockscreen. Works for me on TW.
[Xposed Framework Modules] kornelius1982:
Changed condition to screen off and homw button just disabled when screen is off.

Lol, you're absolutely right )))

Thanks bro ;)
[Xposed Framework Modules] Kev1000000:
I also cannot get XA to work on the Nexus 7 2013 running 5.1. No keypresses are recognized.
[Xposed Framework Modules] newarkoz:
After upgrading to 2.2 a "CLEAR DATA" fix the FC! :)
[Xposed Framework Modules] flexxoo:
I loved the new layout but the remap buttons with screen off dont work is like it doesn't recognized. Good job!!! With new update.
[Xposed Framework Modules] dk_zero-cool:
Try clearing the old app data, seams to fix all kinds of issues with this update.
[Xposed Framework Modules] Saeedblack:
also don t work with this method

how can i send a log?
[Xposed Framework Modules] flexxoo:
I did and it works with screen on but it doesn't with screen off any ideas???
[Xposed Framework Modules] dk_zero-cool:
You need to get a logcat via ADB during boot. How I cannot help with, it's not that easy if it is not setup on your computer. Search for adb on google.

What buttons are you trying to re-map to?

And you do remember to switch into Sleep options right? In the Re-map settings you have "Select screen state". You need to switch to "Screen Off" to configure sleep Re-map.
[Xposed Framework Modules] flexxoo:
With screen off media next and media previous with volume buttons, play and pause with power long press.
[Xposed Framework Modules] dajmanjt:
Exact same thing happening to me. Screen on remap works but screen off does not. Funny thing is it vibrates like it knows I'm giving it the command but nothing happens. Yes I know you have to select screen on our screen off remap. And yes I did the data reset because it was force closing when I first updated. Multiple reboots as well.
[Xposed Framework Modules] spätzlemitsoß:
I can confirm this. Screen off remap is not working.

I cleaned app data, chache, reinstalled.. but its not working.

And when i use default setting some buttons are without function?

e.g. power long default screen on has no function?
[Xposed Framework Modules] brotbuexe:
Same for me with the screen off.

Back button (keyocde 4) Click Action when Screen Off

- media/play pause does not work (was working with version before)

- volume up does not work (was working with version before)

- power on works

Media Play / Pause and volume up work as map action for Screen On.

I've attached a logcat doing screen off, trying two time doubleclick back and long press back, then screen on by click on back (remapped to power).

Do you plan a donation or pro version?
[Xposed Framework Modules] dk_zero-cool:
It will be looked into

Not meant to. The default power is handled by Android's version of the method that I replace to add these features. There is still not, and will never be, any way for me to redirect long press actions manually to that method. Android does not provide such an option. What I did was find a way of allowing applications to get the defaults so that for instance volume can be changed all the way by holding down the button. But if you want power menu on long press power, you can select it from the list.

So to sum up

No Re-map = Android's (Or custom ROM) button features + Applications

Re-map = My features + Applications
[Xposed Framework Modules] dk_zero-cool:
Thanks, might come in handy

Not really. Tried it with Mounts2SD and I must say, to much extra work. I am to lazy for that sort of thing and it kind of drags the fun out of it.
[Xposed Framework Modules] spätzlemitsoß:
Ah, ok. Now i understand your remap implementation.

Thanks!