yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] dk_zero-cool:
No there is a small bug, but I do find it strange that this only affects one app. Either it should launch them all or none at all.
[Xposed Framework Modules] blackbearblanc:
Also affects gallery I see now. And, the Photos app is not showing in app list. I guess these apps are very related
[Xposed Framework Modules] dk_zero-cool:
They might be apps inside apps. One app can some times contain sub-apps. The list in the module only displays main apps at the moment, I will add sub-apps soon.
[Xposed Framework Modules] blackbearblanc:
Actually! Just tested it again. It's all your defaults that works. Screen shot. Volume down and so on. Also the top list with the remaps.. No apps from app list works
[Xposed Framework Modules] jacolguz:
Im so sorry

Im running KitKat NB7 on Note 3 international

FC is when I launch configuration module

I tried:

-clear data of additions

-uninstalling and installing additions

-reboot

-when I try to configure module, crash! FC

Does not give any log (I looked in data folder)

I hope this was useful :)

Tapatalk en SG Note 3
[Xposed Framework Modules] dk_zero-cool:
Well it is a start. Try looking for /data/data/com.spazedog.xposed.additionsgb/cache/error.log

This file should exist, if not the module does not start at boot. If the log is missing or empty, you will need to get a log manually of the crash with a logcat app. But check the above file first.
[Xposed Framework Modules] jacolguz:
I meant that I looked just in that folder, cache folder is empty (cause I cleared data and uninstalled and reinstalled) and now, with de FC does not create any log file

Tapatalk en SG Note 3
[Xposed Framework Modules] dk_zero-cool:
The log file is create during boot by the module. Try rebooting and then open the app and let it FC. After that look again. Otherwise, use a logcat app to get a log of the crash.
[Xposed Framework Modules] jacolguz:
Here is, I found these two lines when I launch xposed additions configuration

18:01:10.185 WindowState( 1440)

WIN DEATH: Window{43a1f410 u0 com.spazedog.xposed.additionsgb/com.spazedog.xposed.additionsgb.ActivityMain}

18:01:10.185 ActivityManager( 1440)

Process com.spazedog.xposed.additionsgb (pid 31352) (adj 9) has died.

I had to use Android Tuner system log

Tapatalk en SG Note 3
[Xposed Framework Modules] blackbearblanc:
I should add, that adding a condition of Camera app works fine, with actions to take picture from within app with power button. It's just the opening of apps with buttons that fails.
[Xposed Framework Modules] dk_zero-cool:
Is that all? That is a strange looking log. Normally there are some indication of the error, and line where the crash happened. Well I will try to figure out what type of error this is, because I have never seen anything like this before.
[Xposed Framework Modules] jacolguz:
Sorry Its my first time with catlog, now I have correct log, Ill send u by email ;)

Tapatalk en SG Note 3
[Xposed Framework Modules] Folowne:
Why restrict re-mapping to device keys only?

Why did you limit re-mapping to device keys only? Now it is not possible to re-map buttons on my Sixaxis Controller anymore. My tablet's device keys are not working correctly, so the only way to control it was through my Sixaxis Controller.

I went as far to support developer by buying Xposed Additions Pro because I felt so obligated and that feature is gone now. This was the only app I found ever to be useful besides Xposed itself.

I hope this feature comes back! It was better this way for me. Now app just force closes every time I try mapping my Sixaxis Controller keys.

Thanks for your time and if I posted in the wrong thread please let me know. First timer here.
[Xposed Framework Modules] dk_zero-cool:
I removed it firstly because this module has never been intended for anything other than re-mapping device keys. Second, I have had a lot of people writing me with issues when using BT Keyboards, Mouses, Gamepads etc. Android has very pore features when it comes to identifying different types of attached devices, the only solution I was able to come up with, was to disable everything external. Maybe I will find a way some time, but for now I have to make sure that the module does not cause a lot of problems for people using different external attachments.

EDIT:

I am gonna through in a toggle for you in the remap settings. Then you can set it to allow external devices. This should fix every once external issues.
[Xposed Framework Modules] dk_zero-cool:
Yes much better, thanks. And the error was just me being an idiot that needs to learn when to rest my eyes, before continuing work. This issue, and the rest that I have gotten to, will be fixed an uploaded within the hour.
[Xposed Framework Modules] Folowne:
Thank you for replying so quickly. Sorry if I was rude. I understand now that you are working excruciatingly hard on this project. I will wait patiently! ?
[Xposed Framework Modules] dk_zero-cool:
I made an edit to my previous post, you don't have to wait that long ;)
[Xposed Framework Modules] dk_zero-cool:
New version is out and should fix all of the issues mentioned since last update
[Xposed Framework Modules] themadproducer:
[MENTION=3147360]dk_zero-cool[/MENTION]

Would a similar Toggle to completely disable Volume keys, work for my issue? If you explained this to me before, I apologize, but some of the technical answers are beyond my understanding.
[Xposed Framework Modules] dk_zero-cool:
The problem is that the control for multi-key support is making it very difficult to handle individual key features like that. It would be a to ugly an implementation, so I rather not.

What pisses me off most about this, is that I cannot find any ROM for the SGS3 I9300 that has this issue, then at least I would have something to work with. It's not like I have the TouchWiz sources laying around to look at. The module is based on the AOSP sources as this is all that I have to go on.
[Xposed Framework Modules] themadproducer:
[MENTION=3147360]dk_zero-cool[/MENTION]

Totally understand.

I haven't heard any other TW device users complain on this thread either. I think maybe your app is still not known very well to all. But it deserves to be! Anyway, thanks for all your effort on the TW based issues, and if you ever think of anything, I will be happy to test. I will keep my subscription alive to this thread. :D
[Xposed Framework Modules] cherylbaker:
I am confused.. i downloaded thus and cannot get it to do anything. Also my screen does not look anything like the play store screens.

Sent from my SM-N900P using Xparent Purple Tapatalk 2

---------- Post added at 08:28 PM ---------- Previous post was at 08:11 PM ----------

Ok well I got SONETHING to work so at least I know I don't have something installed wrong. .

So i did button add a new key and pressed home as my button to remap. I picked lock screen and did long press and picked unlock device.. works. . But if I pick something else like just click and pick camera nothing. . Or double click recent apps nothing. .

Sent from my SM-N900P using Xparent Purple Tapatalk 2
[Xposed Framework Modules] egingell:
Old UI screens on the Play Store. Plus, it looks like there's some Halloween-esque theme going on there.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
You cannot do much from the lock screen. If an app is to be launched from lock screen for an example, the app itself has to have that option added to it's Manifest file. Also remember that the first section of actions are just key codes. They will just make (in your case the home button) act as another button. It is still up to your system or apps to support any actions on those buttons. If you for an example remap home click to the camera key, you will still need a camera app that has added support for the camera key. It is up to that camera app whether or not the camera key code can be used to launch the camera, take pictures etc. Just like the Menu key does not display a menu if an app have not implemented a menu.
[Xposed Framework Modules] wilflare:
the latest update seems to re-introduce some element of wakelag when using the Home Button to wake the screen
[Xposed Framework Modules] ImpheOtus:
I'm on Galaxy S4 jfltecan using stock Google Play Edition ROM.

Menu button is having a small issue, it is vibrating even after I uncheck the "Force vibration" option.

The difference is that it vibrates after releasing the button, not when pressing it. If I enable "Force vibration" then the button would vibrate twice. Once we pressing and another when releasing.

It didn't happen in the version previous to today's both.

Everyhting else is working perfectly.

I really love this module :D
[Xposed Framework Modules] coronanlime:
After updating still have double hepatic feed back on the task key
[Xposed Framework Modules] cherylbaker:
Wouldn't one expect default apps to have such suppott? If not than the program would do nothing and not be helpful?

Sent from my SM-N900P using Xparent Purple Tapatalk 2
[Xposed Framework Modules] fufubrightman:
Failed working when screen is off...(w/ 3.2.1)

1st of all, this is absolutely a wonderful app which I will never uninstall ever!!!!

I just updated the app version to 3.2.1 just now, and found out that my headset buttons won't response when screen is off.

(Headset hook / vol.up / vol.down)

In the ScreenLock and ScreenOn situation, everything works fine.

However, this doesn't happen with version 3.1.2...

Looking forward to an update~~

Cheers from China.

LuvU

============================

Device: Samsung I8190N (S3 Mini)

ROM: Stock 4.1.2
[Xposed Framework Modules] dk_zero-cool:
I am working on merging my current wake fix with the one from 3.1 in order to get all devices to respond while asleep. So try the update once it's done, and write back if it still does not work.
[Xposed Framework Modules] churrolakra:
Hello.. I am trying new 3.2.2 on i9500 tw 4.4.2 omega rom...

The haptic feedback acts strange.. when you press the back or menu button the feedback is done when you lift the finger of the button instead of when you press the button.. (if you turn on the module feedback then you have double haptic feedback, one very short when you press and one longer when you lift the finger)

also Torch command does not work on this phone ...

That is all my report for now! everything else working perfect so far :)

Thanks a lot!
[Xposed Framework Modules] blackbearblanc:
Update fixed my KitKat issues with power button. Thank you sir
[Xposed Framework Modules] a.fontenele:
Last application toggle

dk_zero-cool

I made a post previously with an issue on the last application toggle #1041, but I haven't got an answer... :(

Since you must've been busy fine tuning this module to make it perfect (believe me, you're almost there) I thought I could just wait for the next releases to solve it.

Today I also face the another issue... The funny thing is, instead of taking me to the previous app I was using, it takes me to the second to last. For example, this is exactly what I've done:

1. Go to Whatsapp

2. Press the home button

3. Go to ES File Manager

4. Press the home button

5. Go to QuickPic

6. Double press menu (last application toggle function)

7. Instead of taking me to ES File Manager, which is the last application, it takes me back to Whatsapp, which is the second to last application I opened... :confused:

After all my tests it always takes me to the second to last application I opened instead of the last. I think it should work just as an Alt+Tab function right?

Has anybody faced this issue?

dk_zero-cool, is there a fix for this?
[Xposed Framework Modules] ImpheOtus:
v3.2.2 fixed the problem with double haptic feedback vibration. Thanks, that was quick!
[Xposed Framework Modules] wilflare:
latest update fixed the wakelag issue on my 4.4.2 Note3

thanks :D
[Xposed Framework Modules] My1xT:
3.2.whatnot fixed nothing for me. made things worse.

Media Button on long volume while screen off didnt work anymore (vibration was there, but no function) also I had double haptic feedback, one on press one on release (if I turn off force feedback I only get one on release which is NOT what it should be)

have it now downgraded to 3.1.2.

also why does the Playstore auto-update it when I installed the APK manually? -> annoying when trying to downgrade coz you have to uninstall (lose data) reinstall old version and then disable auto updates before playstore is faster...
[Xposed Framework Modules] dk_zero-cool:
The feedback on up keys are made by the ROM. I have disabled the function that makes those, but since Samsung never fallows any standards, they properly use a different custom function for this (no source, so I can't check). Now I have been working my ass of to get these ROM's working properly, but I am not sure how much more that I can do. I have no such devices to test with and I have no source codes as they don't exactly provide these anywhere. All that I can do is design it all based on the AOSP codes, but if companies like Samsung goes and changes this...

You need to have a torch app installed. Stock ROM's does not provide these, but there are plenty on Play Store.

Makes no sense. The fix that I added in 3.1.2 (and replaced in 3.2.1), has been added back in 3.2.2, so those two versions work the same. If it works in 3.1.2, it should also work in 3.2.2.

I did not create Play Store, so you would properly be better of asking Google about this.

Yes I am aware of this issue, but this action is not quite on the top of my todo. I have been a litle busy trying to correct as many TW errors as possible. But it will be looked at.
[Xposed Framework Modules] My1xT:
When came 322 out? Last time i checked today was 321

About 10:00 GMT

Gesendet von meinem SM-N9005 mit Tapatalk
[Xposed Framework Modules] dk_zero-cool:
So you have not been testing 3.2.2? Because if you was talking about 3.2.1, then it makes sense. I uploaded about 8 hours ago, but Play Store can be a little slow, so If you do not check this thread or Xposed Repo, it can take time to notice.
[Xposed Framework Modules] My1xT:
I was on repo but an hour too early...

Gesendet von meinem SM-N9005 mit Tapatalk
[Xposed Framework Modules] dk_zero-cool:
Well I could kiss you. Please try the latest and tell me that it works...
[Xposed Framework Modules] My1xT:
Right now sudoku'ing, later dinner then bed -> tomorrow (gmt+1 based)

Gesendet von meinem SM-N9005 mit Tapatalk
[Xposed Framework Modules] My1xT:
Just checked repo...

Gesendet von meinem SM-N9005 mit Tapatalk
[Xposed Framework Modules] dk_zero-cool:
Hmm...
[Xposed Framework Modules] egingell:
Click the reload icon on the main Download screen. It only auto checks once a day.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] My1xT:
Saw that and updated. Semms that I'll have to downgrade again.

Just for note (note 3 SM-N9005 MJ3 firmware (4.3))

Gesendet von meinem SM-N9005 mit Tapatalk
[Xposed Framework Modules] blackbearblanc:
Power button for camera works as said previously. But now back button and recents act as long press (for shortcuts set in Gravitybox). I dont know if the two modules suddenly wont get along together. But it happened after updating Additions.

Ill try resetting Gravitybox.
[Xposed Framework Modules] dk_zero-cool:
I don't know how Gravitybox works (never seen the code), but start by disabling all other modules and see how it works if Xposed Additions is the only active one. Multiple modules can easily create conflicts if they hook the same methods and start interfering or manipulating things that has already been altered by another module.
[Xposed Framework Modules] blackbearblanc:
That worked. But dont know what caused it. Nevermind dont need that
[Xposed Framework Modules] J_M_V_S:
Refund

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

I tried this app a long time ago (when it first was available with no Pro version) and it worked great on my HTC One Dual Sim. Today I was able to finally purchase through the Play Store and this is the first app I buy. Now I find that the application does not work and as I rebooted several times to try to fix the problem I lost the 15 minutes window to call for a refund.

It would be nice if the app would work again on my device (and I'm willing to provide logs and test things). I don't want to find myself in a situation where I pay for something that doesn't work.

Please PM if you want more details. Thank you.

mail: jmvs @ [xxxxxxxxx] .com.ar
[Xposed Framework Modules] dk_zero-cool:
So you are saying that you have not gotten any response at all, not one single awake button, no sleep button nothing? That is impossible, at the very least you should get a crash, but no response?

Well I will need a logcat from the time you turn on the device and to the point where it is fully loaded in the GUI
[Xposed Framework Modules] MariusOX:
delete
[Xposed Framework Modules] dk_zero-cool:
Might be possible at some point
[Xposed Framework Modules] signupstuffid:
It works on my HTC Rezound with Sense 4.1 ROM on ICS! Thanks a ton.

Since I switched ROMs I have been looking for somehow to get volume wake back without some app bogging down my phone with a service, or having to learn how to recompile the ROM just to add it.

Unfortunately it looks like I can't get the capacitive buttons to wake the device from sleep. Is that likely a limitation of the hardware, or just something I should report as a bug with Sense based ROMs? I have never used my phone with a CM, or AOSP ROM, so I'm not sure if it would work on it.

When I get done putting it on my GB devices, I'll come back and let you know how it went.
[Xposed Framework Modules] dk_zero-cool:
Capacitive buttons are just a part of the screen. You need kernel support in order to have screen touches reported to the ROM, otherwise when the display is off, it does not register any clicks or movements.

Just one notice, do not use any Re-Mapped keys while having the Power Menu open. No sure why, but this dialog produces reboots when you click on a button that has been re-mapped. Still working on that one, but it's strange. No other dialogs produces this issue. So just click outside the dialog to close it, unless you have not re-mapped your back buttons, then it is safe to use that.
[Xposed Framework Modules] signupstuffid:
OK, just installed on HTC Thunderbolt on GB and it works fine so far. Have mapped the long press of menu to power off. My ROM , liquid smooth, already has volume wake enabled, so I haven't enabled anything else.

Thanks again. When I get access to the phone again I'll see if the kernel has support for active digitizer when the screen is off.
[Xposed Framework Modules] Jimmy34742:
Sorry if I missed this in the previous 11 pages, but I can't find this app listed on the Xposed installer's downloads page. Is it there? Can it be put there so that updates will be easier?
[Xposed Framework Modules] dk_zero-cool:
It willl, but not while in beta
[Xposed Framework Modules] baddai:
too bad this isnt work in my lenovo a800,

i really want remapping my wakeup button since a800 have a fragile power button :(
[Xposed Framework Modules] dk_zero-cool:
And with a bit more information it might come to work, but "not working" is not very helpful. So let's instead try to answer some of this.

What ROM are you using? (Possibly a link to it if it is custom)

Is XPosedBridge installed on it?

Is the module enabled in Xposed?

Does re-map during wake work? (When the screen is on)
[Xposed Framework Modules] baddai:
* im using a custom rom, porting from micromax a110

http://www.needrom.com/mobile/lenovo-a800-lenmic-a800-stablever-1/

* xposed bridged all good, i've been using some other xposed modul in my phone, tweakbox

http://xdaforums.com/showthread.php?t=1629653

and it's working just fine.

* re-map during wake haven't been tried

actually this is how really happen,

i assigned the volume down key to the wake up during sleep.

after i turns the phone off, when i try to turn the phone on again (with volume down key) it only works when i do very quickly after turning down.

Is the phone asleep for a while, i could not wake it up with the volume down key.

thank you for your reply.
[Xposed Framework Modules] dk_zero-cool:
Okay, that means that re-map works, but your device some how refuses wakelocks while in deep sleep. I will add two different wakeup options, hopefully one of them will work on your device (Both does on mine, but only the current works on one of my test devices which is why I used it as default).
[Xposed Framework Modules] dk_zero-cool:
Beta 5 is out

Fixed issue when interacting with some dialog types.

Added an additional wake option for devices where it did not work before.

Fixed the old wake option to hopefully work on more devices (If not all).

Some code rewrite to increase performance.

Added Recent Application list to the re-map options

Added Power Menu to the re-map options
[Xposed Framework Modules] signupstuffid:
Works also on my Droid-X GB 2.3.3 Liberty ROM.

Thanks again for making this possible, and easier for us Android users that don't want to learn to compile a ROM, just to enable custom button actions.

I would like to request a feature for the next version of the app.

More options for screen of button mapping.

The Droid-X with the ROM I'm using has the home button configured to wake the device by default, and no way to change that in it's settings. If I could disable that with this app that would be awesome.

This may be the case with other phones that have physical buttons such as the Droid-X2, Droid Charge, S4 Active, Rugby, etc. As I don't have any of those phones I can't verify this.

Also, phones like the Droid, Droid-X, a few HTC, and many Sony phones have dedicated camera buttons. Is there plans to support these buttons in the future?

If you need help with the Droid, and Droid-X, I can test, or provide whatever info is needed to let you know what those buttons report to the OS as.
[Xposed Framework Modules] dk_zero-cool:
I will look into the camera thing. But your home button, just disable it. It is already possible. I started this mod because I wanted to disable the power button, so of cause this feature is included.

'Button Re-map Sleep' -> 'Home' -> 'Click' -> "Disable"
[Xposed Framework Modules] brotbuexe:
Issue on b5

Button Re-map Awake:

- Back

-- Remap On

--- Click = Back

--- Long Press = Power Off

In b4 both are working. In b5 only the Long Press works. The click isn't doing anything until I disable the Remap.
[Xposed Framework Modules] dk_zero-cool:
Strange. Works fine for me on GB, ICS and latest JB with 3 different devices. Also that option has not been changed between b4 and b5.

Try re-mapping it, select something else in Click and the re-select Back to update the config file. Maybe something went wrong during update.
[Xposed Framework Modules] SAINI99:
Perfect app thankyou very much
[Xposed Framework Modules] spätzlemitsoß:
hi dk_zero-coo,

thanks for your hard work, really like your app!

i have a small question:

In the past i always had phones with a dedicated camera button to quickly start camera from locked/active screen.

Also there was an option to hold button to activate flashlight.

Now with most of android devices that feature is missing.

Do you think its possible to add that feature in a future release?

So we can select camera and flashlight for button remap?

would be a killer feature!!
[Xposed Framework Modules] dk_zero-cool:
I see no reason why not
[Xposed Framework Modules] a.fontenele:
Thanks man! I'm glad you responded and plan on fixing this issue.

I look forward to this last-application-toggle fix, meanwhile, I will keep on motivating people to get the PRO version as I've already done in other threads. This is the least I can do to show my gratitude for such hard work because even with these minor issues I face, your module simply ROCKS! I even added a link on my signature so that people can head over to this thread and benefit from your great creation...

Tks mate!

Sent from my GT-I9300
[Xposed Framework Modules] heddkandi:
I did, and I had the same problem. Should I revert to an older version?