yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Walter.White:
Apologies if someone has already asked this before.

Is there anyway to re-map keys depending on weather if the headphone is plugged in or not?
[Xposed Framework Modules] themadproducer:
[MENTION=3147360]dk_zero-cool[/MENTION] [MENTION=5575828]Walter.White[/MENTION]

First of all, wow...what a great video!

To answer your question...NO.

It would be a cool feature to be able to enable/disable remapping on the fly...and even using Tasker profiles to control it all.
[Xposed Framework Modules] dk_zero-cool:
For starters you could explain the issues that you are having, something must have worked for you since you decided to extend it with pro.

No, try enabling the debug option and then grab a logcat when you click the buttons with issues.

No, but if you have buttons on your headset, then you can remap those (if it is wired).
[Xposed Framework Modules] Walter.White:
Yeah its pretty crazy and story behind why that lioness loves that dude is also awesome.

Is it because one has to reboot phone for re-map settings to apply/stick?
[Xposed Framework Modules] egingell:
Other than installing and updating the mod, rebooting has never been required with this.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
Not at all, you don't even have to exit the configuration. Re-map Settings is applied just as soon as you change something. The App part and Module part has a direct IPC connection to one another, and the App part will inform the module of any changes made just as soon as you make them, no reboot required.
[Xposed Framework Modules] hanksgo:
Problem with LG G Pro(E988)

LG G Pro's Quick Memo cannot be exited after Xposed Additions was installed!
[Xposed Framework Modules] paolo200:
Hi

Would love to have this added

To me it is the only thing missing as a remap action

Awesome module by the way :)
[Xposed Framework Modules] My1xT:
yet any info on why I have the haptic problems on any 3.2 version (up to 3.2.2, which is latest)???

If I can help you just ask.
[Xposed Framework Modules] dk_zero-cool:
Sorry but this module does not hook any Activity Parts, so it is not a bug in the module. This module handles device keys, not applications.

You still have problems with 3.2.2? Rebooted?
[Xposed Framework Modules] My1xT:
yes done everything yesterday evening. installing 3.2.2 (yet everything ok, but obvoius since xposed requires reboot after update) -> reboot -> haptic problems...
[Xposed Framework Modules] dk_zero-cool:
In that case I don't think that I can do much more without some source codes from Samsung (which will not happen). I don't know how they have changed the way Haptic Feedback is invoked.

Is there any of the 3.x versions where you don't have this issue?
[Xposed Framework Modules] J_M_V_S:
I made the stupid decision of buying first and trying later, given that I've tried it long time ago and was working fine.

The problem that I'm facing is that no key binding is working at all in any state. I'm on stock 4.4 Sense ROM with the following Xposed modules: App Settings, BootManager, Complete Action Plus, CrappaLinks, FixVisibilityOfMultipleNonFullscreenActivities, GoogleOfflineVoice, MinMinGuard, NFC LockScreen Off Enabler, NotifyClean, Sense 5 Toolbox, SwypeTweaks, XPrivacy & YouTube AdAway.

From those modules the only one that I think can interfiere with Xposed Additions is Sense 5 Toolbox since it also has some options for the hardware keys. I disabled those activities, rebooted and then purchased and installed yours.

Let me know if you need more information.
[Xposed Framework Modules] dk_zero-cool:
Well there are plenty of HTC One with Stock 4.0.4 using this module, so it should work. Try the following...

Disable all modules except Xposed Additions, reboot and check again

If still nothing, check the Error Log in the Xposed Additions App, if you have any errors, click the send button, choose your email app and send the log to me (Email and log is pre-defined). If the module has any errors during boot, it will disable itself to avoid boot problems.
[Xposed Framework Modules] My1xT:
3.1.2 is the version I am always downgrading to.
[Xposed Framework Modules] dk_zero-cool:
An do you only get haptic feedback on key down with that one?

Then I will compare those two and see what the difference is. Maybe there is something that can be done that will satisfy everyone. And Haptic is the only issue?
[Xposed Framework Modules] My1xT:
I get key down on all 3.x (force haptic on, obviously) BUT on 3.2+ I ALSO get key UP haptic feedback, which is annoying...
[Xposed Framework Modules] palmuse:
BT Keyboard

BT Keyboard guy here. Been following this thread and testing all along. Got good news for you.

The keyboard is working now (shift keys and caps]. Huge improvement. Thank you.

Of course, there has to be a but... I have to hold each key about 3 seconds for it to register a single keypress. Now I am a slow typer so... j/k

I know this is not a top priority ATM but thought it might support the lag issue introduced in the later builds.

Curiously, the earlier BT keyboard issue seemed to be due too fast repeating which I presume you caught and squashed. Now it is the other side of the spectrum. I am confident that you will nail this soon (barring the TW junk].

I'd buy this app again seeing the dedication you put into it. Top tier. Certainly. Thanks!

If you need a log let me know.
[Xposed Framework Modules] gregbradley:
Version 3.2.2 on xperia Z1 running android 4.2.2

I just updated to this version of the module and lost haptic feedback. It is this module as I disabled all other modules and just toggled this one.

Its no big deal, I will continue to use it (I find it the easiest way to remap volume up to power menu) but I would love the haptic feedback back.

Thanks for your work.
[Xposed Framework Modules] My1xT:
have you enabled force haptic feedback for the buttons???
[Xposed Framework Modules] gregbradley:
Where is that setting within the module?

I have it enabled in the settings of my phone, and it works when I disable this module.
[Xposed Framework Modules] My1xT:
when you are in the button you create an assignment for the button (if not yet set) and add conditions and actions if needed (if not, you dont need it) and when you are in the submenu of that particular button there's a tick with Force haptic feedback or sth. like that...
[Xposed Framework Modules] gregbradley:
Well, this is for haptic feedback of of home button which had note been remapped. Installing the last versions makes Everingham work fine. I have only remapped my volume up button to the power menu, I shouldn't have to force haptic feedback for non mapped buttons
[Xposed Framework Modules] dk_zero-cool:
If keyboards are better now, it was not intentional. I have never meant to have keyboards as part of this. This was only meant to provide people with extra features on the few keys available on devices to day. Also, most keys on keyboards does not get handled by Android, they are just sent through to the applications. You would actually not even need Xposed to make a remap feature for it. The hardware keys on the other hand get's handled by Android before they are sent to Applications, and some does not get sent at all. So I have to hack my way into that and alter the default behavior, which is a lot more difficult.

So, if I would ever extend this to keyboards (not saying I do), I would have keyboards bypass the current hijacking and add the keyboard control much later where it would be so much easier to handle them. Especially because keyboards has a lot more combo options which would simply not be possible to create in the same module part that handles the hardware keys.

But at the moment I don't even have a keyboard. Maybe if I got a Tablet at some point, not really needed with a small phone.

I don't get why your device does not work with the Haptic Block I made, it have fixed it for everyone else. However, I know what the difference is between 3.1 and 3.2. I just need to make sure that making that change will not break it for someone else. It has been quite proven that this Haptic Feedback thing is very fragile and breaks easily.
[Xposed Framework Modules] dk_zero-cool:
It does not mater if your keys are re-mapped or not. When you install this module, your keys are handled by this module. Like you can't install a new Home screen and then complaint about it not using your old App Drawer?

The problem with the Haptic Feedback is that normally you should check each key to see of they are hardware keys or capacitive keys. Then you invoke feedback on the last type. But some Sony, Samsung and HTC ROM's does not have this identification in their Stock ROM's. So I cannot check the type to decide if there should be a Haptic Feedback or not.

So there are only two options here. Either use the work-around for now by forcing feedback on the keys that should have them. Or switch to a more standard Google ROM like AOSP or CyanogenMod where they don't make so many coding errors.
[Xposed Framework Modules] dk_zero-cool:
@My1xT try the attachment below, it should fix your double haptic issue if you did not have it in 3.1.2

View attachment XPosedAdditions-3.2.2-haptic_test.apk
[Xposed Framework Modules] My1xT:
I test it @ home. But I have an idea. How about putting the different force types into a drop down abd let the user choose.

Maybe I have tge issue coz I have not updated my note 3 to kitkat (which I honestly don't want)...

Gesendet von meinem SM-N9005 mit Tapatalk
[Xposed Framework Modules] dk_zero-cool:
Yes I thought about that, but I think we are starting to find a balance here. Just that many of these ROM's work so differently from one another, and some are far away from pure AOSP. But did it work this time?
[Xposed Framework Modules] My1xT:
just tested, from my quick results I can say the following. FINALLY...

YOU ARE GREAT!
[Xposed Framework Modules] dk_zero-cool:
Great, now I just hope that this does not start reproducing the HTC One Recent Key issue.
[Xposed Framework Modules] My1xT:
You still have the way of letting ppl choose their preferred method for haptic, rather than trying the one for all approach...

Gesendet von meinem SM-N9005 mit Tapatalk
[Xposed Framework Modules] dk_zero-cool:
Yes I know, but I rather keep those types of options to a minimal if possible. I am pissed enough about having to keep the forced feedback option. I always find solutions to problems, but that one just keeps evading me. I am not gonna let the same happen with this one.
[Xposed Framework Modules] My1xT:
But the best point in forced feedback is that I have the option tbat I can (if I want to) activate feedback for buttons that usually dont have it (like volume or alike)

Gesendet von meinem SM-N9005 mit Tapatalk
[Xposed Framework Modules] a.fontenele:
Expand Notification Panel

+1

That'd be quite handy...
[Xposed Framework Modules] jackdubl:
Wrong thread.

https://copy.com?r=cScoov
[Xposed Framework Modules] My1xT:
just another remark about haptic feedback:

nothing disturbing, just sth. I noticed.

Vol+/- has no actions set when screen on (->default, only set action is screen off+hold-> media next/prev) and no haptic feedback enforced.

yet we have the following situation

(both buttons the same)

Screen on + press -> nothing

Screen on + hold -> feedback

Screen off + press -> nothing

Screen off + press -> feedback

to compare 3.1.2 (which is also the expected behavior)

Screen on + press -> nothing

Screen on + hold -> nothing

Screen off + press -> nothing

Screen off + press -> feedback

as I said it's nothing special and you dont particularly need to fix it immediately or whatnot, just noticed and also it's no real reason for downgrading...

also I noted that with this module (dont know since when or if it was all along)

the volume gets up/down at a crazy speed when holding the respective volume button while screen on (my off setting has assigned sth. other for off+hold so dont know if that matters + no screen on condition set, just for screen off).

but those are rather minor and not really disturbing
[Xposed Framework Modules] vespper:
Volume is unstable it goes UP and DOWN so fast when i long press. I didn't set any Action or Condiction for them. I just kept volume buttons default.

Volume is not working gradually as it should be since i installed Xposed Additions.

I am on Meizu MX3 Flyme 3.4.5

Some support would be nice.

Thanks and keep working on this awesome module!
[Xposed Framework Modules] dk_zero-cool:
You are replacing the default key handler with the one in the module, so default action does not mean that the module is not handling it, it just means that you will get the ROM's default action when using it. The module handles ALL keys on your device no mater if you add it in the app and remap it or not, that is the only way to do this. I mentioned this many times before, when you replace your Home Launcher, you will also replace your App Drawer. You cannot have two Home launchers at the same time, and you cannot have two key handlers either. It's one or the other.

Now, Android supports replacing your Home Launcher, but it does not support replacing the key handlers. So you do not have any official API's to help with this. The only way is to hack the system with things like Xposed. It works, but it will never be 100% like the original, it can't.

In short, the volume buttons are as good as they will ever be. The are never going to be smooth using something like this. At least not without removing all support for default ROM actions.
[Xposed Framework Modules] vespper:
If there isn't a solution, maybe could you add new Actions?

Volume UP (done)

Volume DOWN (done)

Volume UP 3 steps + 3 steps + 3 steps depending on the time i keep pressing

And same for Volume DOWN.

So i can set Volume UP for a single click and Volume UP 3+3+3 STEPS when long pressing or something.

Thanks!
[Xposed Framework Modules] paolo200:
Two actions I would love to have is to expand the notification panel and also to show or hide the status bar which is very useful especially when in full screen application mode

Thanks so much
[Xposed Framework Modules] dk_zero-cool:
The only way that would work, is if I rewrote the whole module and 100% excluded all default ROM actions. And since a lot of people uses a lot of different custom ROM's with their own added actions, I don't think that would be appreciated along the way.

This small issue is one that you will just have to live with.
[Xposed Framework Modules] ImpheOtus:
Just FYI, I like the current behavior.

I like having haptic feedback when holding volume keys down and I like volume to go all the way to the right or all the way to the left when holding them down.

It's faster and more intuitive since you can't have an accurate volume with the +3 steps implementation. You end up pressing the volume key more than once anyway to set the desired volume.

At least that's my experience.
[Xposed Framework Modules] dk_zero-cool:
Me to, I only hold down if I want it all the way down or all the way up. Androids default is also to fast to be able to set any desired in between.
[Xposed Framework Modules] xdaver:
I'm on the LG g2 stock room 4.4.2.

When I install the module my power button doesn't turn the screen on or off. But if I long press it the power menu comes up. All of this starts before I even start touching the modules options. Setting the power button to the 'power' function didn't help.
[Xposed Framework Modules] palmuse:
BT Keyboard

Ok. So is this where we leave it? I only ask bc as it is, I cannot use my BT keyboard at all with Xposed Additions. Turning off external = nothing from BT keyboard / Turning on external = 3 seconds held per character typed with no repeat ever

As for the BT Keyboard, I got it because I am worthless with the on-screen keyboard. I have my GS3 set up like a tablet using other xposed mods. I set it up on a stand and pretend I have a tiny PC. Not for everyone, but works for me. everything is fullscreen and the keyboard never gets in the way. It is no bigger than my phone and even has a touchpad and 4way d-button. really quite handy for navigating without touching the phone.

(Amazon - Aerb® Portable Wireless Bluetooth Keyboard Handheld with Rechargeable Lithium Battery for Bluetooth Enabled Devices <$30 US)

Anyway, to each his own. I sure would like to have the functionality of both. I was beginning to test shortcuts like alt-left d-button to go back, ctrl-w to close windows, ctrl-s to bring up settings, etc. I understand that some of this is possible with a standard keyborad handler app that but only to a certain extent. I actually have one but found it to be limiting and awkward to use. Your app has a ton of promise.

If you say I just need to deal with it so be it. I just need to know if you are considering any further refinement. I respect your decisions as the developer and realize I am stretching your intentions for the mod.

thanks
[Xposed Framework Modules] dk_zero-cool:
That makes no sense. But in order to figure out why, I will need a logcat while the screen is off and you press the power button. This means that you will need to get a logcat using your PC shell and ADB. And you need to enable debug in the app as wel.

It's like I have said many times before. This module has never been intended to be used on keyboards. It's meant to add more options to devices built-in buttons. I do think it is strange that your keyboard are getting so large delays when the device buttons don't, it should work the same for all types of buttons. But since I don't have a BT Keyboard myself and since the keyboard was never intended for this module, I am not gonna waste time debugging it. So long as the option to disable/enable externals are working, I am considering this issue to be closed. At least for the time being.
[Xposed Framework Modules] J_M_V_S:
I found the culpruit to be Sense 5 Toolbox. As I need this module for other things, is there anyway in which I can have both working?

Also, it would be a neat feature to have also a way in which the buttons can be re-assigned depending on orientation (for example, Sense 5 lets me switch the bindings when in portrait mode).

BTW I'm using KitKat 4.4.2, not ICS 4.0.4, just in case

Thank you.

PS: Just wanted to say that I freaked out in my first post as this was my first purchase ever and using a lend credit card and then I saw the app not working! I got into panic mode. Sorry
[Xposed Framework Modules] dk_zero-cool:
I don't know, I don't have Sense and thereby no Sense specific modules, so I don't know that one. But if that module hooks the same methods that I do, it does not seam likely, unless you somehow can disable that part in the other module.
[Xposed Framework Modules] J_M_V_S:
I've tried disabling Sense 5 Toolbox buttons mods (not binding keys and back to default) with no luck. I don't think the S5T team will hear me out in this case because I'm using an unsupported device (it's made for HTC One and I have HTC One Dual Sim). Gues I'm out of luck. A shame, because I really wanted to put your module to good use! Thank you anyway.
[Xposed Framework Modules] LuuchoRocha:
Any news about a solution for samsung touchwiz rom and wake up?
[Xposed Framework Modules] themadproducer:
[MENTION=5562153]LuuchoRocha[/MENTION]

Unfortunately, no. And probably don't expect a fix without [MENTION=3147360]dk_zero-cool[/MENTION] having access to source code for TW roms.
[Xposed Framework Modules] FCORivers:
I updated from a old version (2.3.8) to newest and now it is useless. Why would I like to update to a version with less options in first place? Now I dont have an option to kill apps.

I know it is to make people buy the app but why would I buy now, I dont even know if it will have the options I liked before.

...and when the crap hit the fan I was the only one there...
[Xposed Framework Modules] egingell:
Be an ungrateful jerk. See how far that gets you.

If you want those other features. You are welcome to make this yourself and have it do whatever you want it to do or pay for them and be grateful that someone took time and energy to do it for you.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] semanty:
when could the app shortcut be supported？
[Xposed Framework Modules] egingell:
If you mean to press a button and have an app start, that's in the paid version.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
I am guessing that you are confusing conditions with actions, and instead of simply asking politely if I have removed something, you start throwing around accusations.

I have not removed anything, you just need to add conditions before you can add your actions.

The crap have never hit the fan, so I am not sure what you mean. And based on your post, I would say that you will be the first to go once/if that happens. You don't strike me as a very tolerant person.

Once I figure out how they work. Not much information from Google about this, and not much to find on the web either
[Xposed Framework Modules] egingell:
The quote for this reply is the wrong person/post, but I'm sure he knows you're talking to him.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
Thanks for the headsup, just edited the reply :)
[Xposed Framework Modules] semanty:
no, it is the app shortcut, not app itself. eg. one specific contact in whatsapp, i just want to press one key to start chatting with that contact
[Xposed Framework Modules] Gia90:
It cannot detect pressed buttons when adding new key rule.. I'm using the latest version on Nexus4..

The module is enabled and I've reboot several time to make it sure..
[Xposed Framework Modules] dk_zero-cool:
First of all, does the buttons have any effect when the detector window is opened, e.g. does home return you to the home screen?

Second, is there anything in the log? There is an error log option in the app, check it.
[Xposed Framework Modules] siciliano777:
There's a bug in the latest version (same bug was in last version as well):

I don't have my power key set up in the app or assigned to anything, yet every time I press it, it registers as a long click no matter how fast I click it.

Note 3, stock ROM, 4.3.

Thanks!
[Xposed Framework Modules] Gia90:
The N4 has only power and volume physical buttons...when I press one of them they just work as normal (lock/volume control) but they are not detected in the popup window...

The error log is reporting an error about a missing method ... I will post the log as soon as I can
[Xposed Framework Modules] dk_zero-cool:
Ah yes the Note 3 devices, got to love them :s

Well, it would help if you could tell me the last version that works, preferably a 3.x version.
[Xposed Framework Modules] dk_zero-cool:
Good, the module has been made to disable any part that creates errors during boot, which is to avoid creating boot loop issues. So if there was an error in the remap part (like a missing method) during boot, the remap section of the module would be disabled and no longer be able to detect keys being pressed.

The Error Log Screen in the app has a send button. Press that and select your email app. My mail, the log file and everything is pre-defined, all you have to do is press send and you will not need to post anything in here manually.
[Xposed Framework Modules] Gia90:
Sent!

Thank you for your great work and for your help!
[Xposed Framework Modules] dk_zero-cool:
Thanks.

The method that is missing, should not be. Could you send the file /system/framework/android.policy.jar? You can get that using a root file manager.

B.t.w.

What ROM are you using. Nexus devices uses the most pure Android of them all, it's their sources this module is based on, so they are the last to have any issues like missing methods.
[Xposed Framework Modules] hedgegee:
Thanks for the app - its great! :cyclops:
[Xposed Framework Modules] siciliano777:
Sorry, I'm pretty sure it was working fine on v 3.2 and previous. :)
[Xposed Framework Modules] Gia90:
I've sent it to your email