yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] dk_zero-cool:
Well I did locate the crash origin. However, that does not explain the reason, so could you tell me what you did and what happened?

You click on add button?

Then press the button you are trying to add?

Does the button name and/or number appear in the dialog's right side? If so, what does both say? It should be "number (name)", for an example "26 (Power)"

And then you click Okay?
[Xposed Framework Modules] slonn:
It's JellyBean 4.2.2. The code it gives is '0' for each key pressed (power, volume up/down).

Sendt fra Z1

---------- Post added at 09:36 AM ---------- Previous post was at 09:32 AM ----------

Actually it works now. Haven't done a thing (at least I think) other than leave the phone untouched over night :-o

Sendt fra Z1
[Xposed Framework Modules] killoid:
i clicked on add new button,then a pop-up appeared to select key which i wanna configure but after pressing anykey it doesnt show anything u mentioned above as example but when i pressed the ok button on the pop-up,the app crashes.

EDIT: i am extremely sry,i did something wrong.i didnt press the keys correctly! but now it works fine! sry for bothering u! & thanks for the great module! :good:
[Xposed Framework Modules] spätzlemitsoß:
Thanks for the explanation. So the kernel disables volume and other buttons on deep sleep.

I was playing around with it a little more.

- When i lock phone and the screen turns off and i immediately press volume to wake it works.

- When i press volume approx. 5 sec after i lock the phone it does not work.

- When i press volume button several times it will sometimes wake up. I guess thats the point, when your wake lock is active.

Would be nice if you could add an separate option to trigger wakelocks with adjustable interval/duration, so we can adjust it to our device.

I guess this could fix the problem for all keyactions and people can decide if they want to use wakelock or not.
[Xposed Framework Modules] dk_zero-cool:
The module and settings part communicates via broadcasts (The only way in Xposed for now). It may be some instability as broadcasts is not meant as a two way communication method. I will see if I can somehow stabilize it, or find another way of communicating. Please do report if you get further issues with this.
[Xposed Framework Modules] wmiswm:
HI OP, I actually wrote to you on this before. I have set to wake screen during phone call by pressing the power button. Then after remap the power button to long click power during screen off, it is extremely difficult to wake the screen during phone call. Is there any possible remedy to this?
[Xposed Framework Modules] dk_zero-cool:
It should not be. I have HOME set to wake the device and it is working fine during calls also. Have you tried Forced?

Not all ROM's act the same. The kernel itself also has a lot do say. Can't really to much more than I already have. The power option sends poweron notification to the Input Handler and forced mode manually triggers a full wake lock. If your ROM ignores both, then you have a ROM issue as this is the only two ways to wake the device. The wake lock method is even a standard Android app API, so that shoudl work.
[Xposed Framework Modules] floyd372:
[MENTION=3147360]dk_zero-cool[/MENTION], I've remapped the camera key to open the camera on single press, but it doesn't seem to work for me, I also tried rebooting.
[Xposed Framework Modules] wmiswm:
the problem is that I do not have home key, I have power key only. I have tried force power, but for unknown reason that will disable my soft navbar.
[Xposed Framework Modules] geo307cc:
Xposed Bridge?

Sorry guys for my question,but where can I find the Xposed Bridge?I searched everywhere but I can't find it!Is it an .apk?If yes,please someone to provide me the link.If it isn't,please someone explain me what I have to do.I want to try the Xposed Additions,it's gonna be a very helpful app for me!Thank you all in advance! :D
[Xposed Framework Modules] dk_zero-cool:
Navbar's injects keys and my module does not interfere in injected keys, so I cannot see how that could be a problem.

It is written clearly in the first post
[Xposed Framework Modules] lmike6453:
I've been following this thread but I'm not sure if haptic feedback is working correctly with a remap.

If i remap the BACK key to...

short press = default

long press = recent apps

The long press has haptic feedback but short press does not. Is this intended?

[MENTION=3147360]dk_zero-cool[/MENTION] I really want to buy your pro version to support you but I want haptic feedback on all BACK key presses/long presses.
[Xposed Framework Modules] dimikon:
Any news for the soft reboot issue?Was my logcat at post #315 helpful at all?
[Xposed Framework Modules] shinpil:
I also have the same problem

+1
[Xposed Framework Modules] dk_zero-cool:
If your key is a hardware button, then it is not supposed to have feedback on clicks. This is an Android rule. If it is an captivate button, then feedback should work. It calls the same method as it does when using long press, so if it is not working on captivate clicks but on long press, then it's a ROM issue as it is an internal method controlling it.

Again, for all. The module does NOT control the haptic feedback. It only tells Android to do an haptic feedback and the reason for it. On clicks it tells Android to make an captivate feedback and on long press it tells Android to make a long press feedback. How Android decides to handle that is up to the ROM and it's internal configuration.

Still looking into that, but I am at work at the moment, so I have other projects that I am forced to work on. Will look further once I get home.
[Xposed Framework Modules] killoid:
i faced some issues.i have remapped my buttons for media playing while screen off.below is the conf.

Home→key code 3

screen state→off

click action→media play/pause

long press action→disabled

volume up→key code 24

screen state→off

click action→media previous

long press action→disabled

volume down→key code 25

screen state→off

click action→media next

long press action→disabled

the key conf.s r working only for long press actions.click action doesnt work as configured.i've tried w/ headphone plugged & w/o headphone plugged,but no result.logcat attached if u find it helpful..
[Xposed Framework Modules] dk_zero-cool:
You have a specific camera button on your device?

And you just set to default in the Click action?

What key number does it display?

You know, it was. It was almost at the top, which means that it was almost overwritten as the log has a limit, but you managed to get it. It seams that your ROM is missing the method that is used to inject key codes to Android. What Android version did you use? exactly, the whole version number and also whether it is custom or stock and possibly a forum link is it is custom.
[Xposed Framework Modules] lmike6453:
Thanks for the quick response and the detailed explanation, makes sense. For reference, I am running stock 4.3 on the Galaxy Note 3(verizon).

Is there a way to tell that captivate key to longpress feedback on short press as a workaround? I can test etc if needed no problem if you want to pursue getting it to work somehow just let me know!
[Xposed Framework Modules] dk_zero-cool:
Yes, I can tell it to make a long press feedback on click, but why would I. It would break possible settings implementations. Is your issue regarding a captivate button?
[Xposed Framework Modules] dimikon:
My rom is stock,i bought Lenovo A660 from china.It is dual sim,ics 4.0.4 ODEX Mtk6577 and in version infos it shows

A660.V2,2012/06/06 00:30 and

A660_S025_121122

and i also found Kernel Ver. : 3.0.13

gcc version 4.4.3 (GCC)

edit:im going to try new version now.
[Xposed Framework Modules] dk_zero-cool:
New release is out which should fix the soft-reboot issue. It may also fix other issues due to the compatibility changes that I have made, but I can't be sure. Let me know how it goes.
[Xposed Framework Modules] dk_zero-cool:
Yes I thought so, I found a small error in the code which would affect all ICS ROM's. It is fixed in 2.3.2
[Xposed Framework Modules] lmike6453:
No worries, it was just a suggestion because I'm not sure what else might work. Yes it is the BACK captivate key, here's my issue detailed from the last page

Others reported the same issue so I know it's not just me. Not sure if they are on 4.3 version like myself
[Xposed Framework Modules] dimikon:
Soft reboot issue total gone. but specifically what i would like from your application is to be able to wake up my screen by clicking or longpressing

the volume button,as the power button is hard to press for my phone.the options i have for screen off state are : power and power force but none of them wakes up screen.Is it possible to achieve that? Otherwise i ll just keep using one of the 3rd party lockscreens that do the job :)

EDIT:volume up seems to work only if i first press volume down ,then volume up

volume down works! which i hadnt tried
[Xposed Framework Modules] dk_zero-cool:
That's strange. Either captivate click feedback is turned off on your device, or your captivate buttons is not registered as captivate. What ROM and Kernel are you using?
[Xposed Framework Modules] dimikon:
I think i found a bug.For screen on state ,and for any button, if u select something different from 'default' eg Power off menu,for long press , then click of that button does nothing whatever u select and vice versa

Found that only Home button let s you use both click and long press actions.

And i think i just finished searching for what i needed from yr application ,thank you !
[Xposed Framework Modules] killoid:
same issues for me,no improvement.. :(
[Xposed Framework Modules] dk_zero-cool:
You will have to specify? Clicks and Long Press is working fine for me, and I have had no other reports either.

This I have not yet looked into. I found soft-reboot issues to be more important, but it will come.
[Xposed Framework Modules] dimikon:
For instance,let s say that i want to remap menu key when screen on. If i assign Power off menu to long pressed,then when i press the menu button nothing happens.Same if it was the volume button , simple click wouldnt raise or lower volume.But as i ve already said,home button only does the job so i assigned Power off menu to long press ,and click default,and simple click brings me to homescreen.I think maybe this happens because home button is the only that was preassigned for long press (no other buttons would do smth different when long-pressed) to open recent apps...and i have a fourth button for that so its okay.

Moreover,lets say that i would like to turn off screen anytime by pressing volume down key.So If i assign power force to longpress,then i wont be able to turn down volume ,cuz by simple click nothing would happen . If you fix that then its gonna be perfect app :P
[Xposed Framework Modules] dk_zero-cool:
This works fine for me on all buttons. And it does not mater whether they have default actions in the ROM or not. My module uses a custom Event Handler that bypasses the original one. I don't use any of Android's key controls to handle anything as these are to limited to be used for something like this.

What did you setup single click for? Default? And what ROM?
[Xposed Framework Modules] dimikon:
I tried default and others like volume up,or volume down or recent apps to see if it s working ,but no.Rom is stock ,i have given you more details in post 343

(.I edited my above post)
[Xposed Framework Modules] dk_zero-cool:
Yes you did, I'm just starting to get tired I think, it's late here. I will look at it tomorrow, but your boot issues is gone never the less, so we are getting closer.
[Xposed Framework Modules] wmiswm:
Is it possible to give a choice of force waking the screen during call, not power or power forced etc? I wish to have a single button to wake up my screen during call. Power or power forced cannot always work, and the key sequence becomes extremely difficult to control if I remap a button during screen off to power/ power forced.
[Xposed Framework Modules] dk_zero-cool:
Android (older once) does not provide many options here. I have added a little different work-around to the forced Power, hopefully this will work. I have also added the new PowerManager.wakeUp() which will work, but it only exists in Android 4.2 and 4.3, so it will not help GB, ICS and older JB.
[Xposed Framework Modules] wmiswm:
thank you very much. My os is 4.2.2, so should have the ability. The problem is that after mapping the power button during screen off to either power or power forced, it becomes very difficult to wake the screen by power button during phone call; sometimes it works, sometimes it does not work, depends on how soon exactly I release the power button long press, very tricky. The best is that there is an individual option to wake the screen during call directly in the selection menu, then I can use whatever button combination for the purpose. You can actually specify that this option is for 4.2+ etc if your concern is that it is not working on older os.

And for the double click, it seems that it is not working for me, always no response no matter I select short, normal, or long.
[Xposed Framework Modules] floyd372:
Yes, there is a dedicated key for camera.

I've set camera for click action, and toggle auto rotation for long press.

Long press works, but nothing happens on click action. And the camera key code is 27.

Here's a SS of my setup.
[Xposed Framework Modules] dk_zero-cool:
Not sure what that Camera action actually does, I think it is meant to take pictures, not open the camera app. If you have a Camera key on your device, then set Click to Default instead, that will trigger your camera key like when it is not Re-mapped.
[Xposed Framework Modules] dk_zero-cool:
What version are we talking about? Double click is in pro, so are we still talking the latest release, because that one should work. What did you configure it to?
[Xposed Framework Modules] floyd372:
I'm sorry I didn't get you.

My camera key clicks pictures on single click by default ie without remapping, and opens up on long press by default. All I wanted to do is single click to open camera, and long press for something else.

Could you make the click action to open camera instead of clicking pic ?:)
[Xposed Framework Modules] wmiswm:
latest from the google playstore. Yes, I am on pro version. BTW, how can I find out which version I am using? There is no "about" info in the app.

Double click assign to power/power forced. Double click will not wake my phone up no matter how I set the short/normal/long.

My phone is xperia z 4.2.2

Actually I do not mind double click not working. I just wish to wake my screen during call after remapping the power on screen off. Without remapping at all, I can easily wake my screen during call using the power button.
[Xposed Framework Modules] dk_zero-cool:
Like I said, set the Click option to default for your camera button

Currently I have Android 4.0 installed on my daily device to fix some of the ICS issues. When I am done, I will install 4.2 and have a look at this before moving back to 4.3. It should all be working, if not, then it needs to be fixed. Especially Double click, I mean, you paid for it so you should damn well have it.

The Power on during call should work in the next release. Especially if you are using Android 4.2 as I have added the new wake option that was introduced into 4.2
[Xposed Framework Modules] wmiswm:
fine, thank you very much. I shall wait and test your next release. No hurry indeed.
[Xposed Framework Modules] floyd372:
Yes I did that, but it works just like before remapping. Single click nothing happens, long press opens camera, then within camera app single click captures picture.I also have power shutter option in camera settings, which actually clicks pictures on single press of the Camera key , when camera is ON.
[Xposed Framework Modules] dk_zero-cool:
Well if you set Single click to Default, then it is surposed to work like before, that's what Default means. Long press however should execute your custom long press action. What ROM version do you have and did you enable the module in XposedInstaller?
[Xposed Framework Modules] floyd372:
I'm using cm10.1, that's 4.2.2. And yes I've enabled the module, and using others keys that I've remapped apart from the camera key.
[Xposed Framework Modules] dk_zero-cool:
So other keys is working fine? But Long press does not work on Camera? Sounds strange. Don't really have a device with Camera button. Did not even think they existed, thought only the Samsung Camera had such a button.
[Xposed Framework Modules] floyd372:
Bro you didn't get me I guess :o, long press works, the only thing that doesn't work for me is ,single click camera key to open camera , no matter what i do.

For the camera button, I'm using a Sony Ericsson.:)
[Xposed Framework Modules] dk_zero-cool:
In that case you have no problems. Unless your ROM by default is able to open camera when you click the camera button, then there is nothing to do. This module does not launch apps yet. It will come in the Pro version just as soon as I get the last small bugs sorted out, but right now there is no app launch.
[Xposed Framework Modules] floyd372:
Aaah , so I think I'm going to buy the pro version. Anyway thank you.
[Xposed Framework Modules] dk_zero-cool:
New release is out, it should fix most of the remaining issues, including ICS Click not working, Power Forced not working for some and hopefully double click while screen is off.

The only remaining issue I think, is the capacitative haptic feedback. So far, the reports I have gotten has been on Android 4.1.2, 4.2.1 and 4.3 all using Samsung's TouchWiz, which tells me that once again, Samsung is the problem. If anyone NOT using TouchWiz has this issue, let me know. Also if there is still other issues on the table besides this, because I cannot remember anything else. There has been a lot of bugs reported, and a lot bugs fixed the last couple of days, and I have no idea where we stand on this anymore.
[Xposed Framework Modules] wilflare:
anyone using this on the Galaxy Note 3?

hoping to change the capacitative buttons longpress action to something else
[Xposed Framework Modules] dk_zero-cool:
I have just been Emailing someone using it on Note 3. Only issue is the missing capacitative haptic feedback on single Clicks. Other than that, it is working fine.
[Xposed Framework Modules] wilflare:
thanks your module seems exactly what I have been looking for!

hope it won't cause conflicts with Wanam Xposed
[Xposed Framework Modules] lmike6453:
You seem to have the issue narrowed down to Samsung devices now which is great to know it's not just me. Here's a screenshot of my stock rom/kernel on note 3
[Xposed Framework Modules] killoid:
sry to report,new version didn't fix the issues i am facing...
[Xposed Framework Modules] wilflare:
[MENTION=3147360]dk_zero-cool[/MENTION]

thanks so much for your app! this is exactly what I wanted

the only thing that does not work on my Note 3.. is that for capacitative buttons, on Screen Off, the actions don't do anything
[Xposed Framework Modules] dk_zero-cool:
What issue is that? And what ROM are you using?

What actions are you trying? If power does not work, use Power Forced.
[Xposed Framework Modules] dk_zero-cool:
I will not have time to make something like that right now. It will require a bit more work, not just the feature itself, but the settings for it will require more than a small check box. I will look into it, if and when I get time.
[Xposed Framework Modules] nimrodity:
Don't know if it's ok to do requests but I would like to ask if the possible

-when screen is off volume down is power button and when screen is on its volume down again

And maybe this one too

-when screen is on volume up is power button and when screen is off its volume up again

Sounds weird I know, just asking
[Xposed Framework Modules] and2:
a big thank you, works great here :good:
[Xposed Framework Modules] dk_zero-cool:
If you install CM or AOKP, you will have a whole settings section with different custom key controls. The reason why I added the power button thing, is that it has not been added to any ROM (Because in most cases, it is a strange thing to have, unless you have a Samsung where this button is placed in a stupid place and reaches to far out of the cover).
[Xposed Framework Modules] nimrodity:
I use an aokp cm and pa Rom but none of those has such a feature. But it's like I said just wanted to know

Gesendet von meinem ProBam by codexc [MENTION=243864]xda[/MENTION] mit Tapatalk 2
[Xposed Framework Modules] Christiancs1969:
They should . RootBox has

RootBox s2
[Xposed Framework Modules] nimrodity:
They all have volume wake but the issue is its still also volume down when screen off and every time I turn off via volume button it changes my volume, that extremely annoying when listening to music

Gesendet von meinem ProBam by codexc [MENTION=243864]xda[/MENTION] mit Tapatalk 2
[Xposed Framework Modules] polobunny:
I have just the opposite problem. I cannot put my phone in my pocket without pressing the home key and waking up the phone.

We used to be able to modify seckeys.kl to remove WAKE function from HOME button but not anymore.

Do you believe this would be possible for you to do?
[Xposed Framework Modules] dk_zero-cool:
The latest version has the ability to disable HOME, check the OP for download
[Xposed Framework Modules] dk_zero-cool:
Just launch an error report for your ROM. That way, the internal method will be fixed and no additional module will be needed in the future. But if the developers are not aware of this issue, then it is hard for them to do something about it.
[Xposed Framework Modules] polobunny:
Doh! Black on white and still didn't see that in the changelog. Thanks a lot!

---------- Post added at 03:33 PM ---------- Previous post was at 03:30 PM ----------

Usually just a matter of changing WAKE to WAKE_DROPPED for the volume keys in the /system/usr/keylayout/sec_keys.kl file (or another file in that directory. Check it out nimrodity, until it gets fixed in your rom.
[Xposed Framework Modules] dk_zero-cool:
He's problem seams to be related to turning off the screen using volume buttons. This feature is not related to sec_keys.kl, as the device is already awake at this time.
[Xposed Framework Modules] polobunny:
Oh #@!* I need to party less hard on my days off, I'm getting unable to read. Sorry again. @_@
[Xposed Framework Modules] Tindoshox:
Works well on my S3 mini:good:
[Xposed Framework Modules] gregferns:
Hi dk,

I have a canvas hd, and it has soft buttons only and a power button on the top right side. Just like Samsung. I tried your module and effectively power button stopped working but home soft key was also not working..

I had to do a battery pull and then disable your module.

Any help? What do you need from my side to get this working please

Thanks

Greg
[Xposed Framework Modules] dk_zero-cool:
I can't get it working. Soft buttons are not buttons, they are a part of the display. When your display is turned off, Android will stop regestring any touches on the display. The only way to get it working, is by implementing a hack into the kernel. It cannot be done from XPosed.

However, I might have another solution for you. I could implement so that only a double press on the power button will turn on the display. That way, it will not turn it on when you do a single press. But that is the best that can be done on devices with soft buttons.
[Xposed Framework Modules] Census Taker:
A double press option on the power and home buttons would be quite a useful blocker for the casual office snooper. Very few of those read these forums and they are unlikely to notice double pressing the button is the way to turn the device on.

I guess the downside would the increased wear on the buttons.