yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] dk_zero-cool:
It would not seam so. Version 3.x takes controll of all buttons, it's the only way to implement all the new features. Your ROM, for some reason, wakes the screen when keys are injected, I can't change that fact. If I was you, I would try a custom kernel or a custom TW based ROM. If that still causes issues, at least you can have a dev look at it. But I cannot change native code behavior from with XposedBridge.
[Xposed Framework Modules] themadproducer:
Ok,

At least we know what is going on here. Thanks for your reply and suggestions.
[Xposed Framework Modules] wilflare:
hmm if I download the RC here will I still get updates via the Play Store when the stable build is released?
[Xposed Framework Modules] dk_zero-cool:
Well I do have one last thing that I can try. Will provide a test for you later today.

Yes of cause
[Xposed Framework Modules] wilflare:
thanks! same thing for the Repository right? cause for some reason sometimes the update shows up first in the Repository... the Play Store is usually slower..
[Xposed Framework Modules] themadproducer:
Sounds good. I look forward to it.
[Xposed Framework Modules] dk_zero-cool:
The repository is updated as soon as I click the save button. Play Store takes up to an hour to update after I click save.

And yes all will alert you of updates, even if you install the RC manually.
[Xposed Framework Modules] djdelirius:
I recently updated from 2.3.8 to 3.1.2 and my soft keys(the menu and back buttons) quit vibrating and no sound upon keypress. I'm running 4.3 custom stock touchwiz ROM on my Samsung Note 10.1 2014 with JSS15J.P600UEUBMK1 firmware. Luckily I had a recent backup of it in Titanium Backup Pro so I was able to narrow the problem down to your app as I was updating multiple apps. So I got my haptic and sound back. Not sure what the cause of the hijack was but just wanted to let you know.
[Xposed Framework Modules] cottino:
Hi,

now Xposed Additions works well with over 500 apps, too.

Thanks a lot :good:
[Xposed Framework Modules] KestrelX:
I am trying out the RC to see if it fixes the two problems I am having.

Still testing the first one (the wake lag). So far so good on my Galaxy Note 3 and Galaxy Tab Pro 8.4.

But the second issue I was having is still present:

On my son's Samsung Galaxy Tab Pro 8.4 (rooted, stock touchwiz/kitkat), I wanted to remap the recent app button since he keeps accidentally hitting it while holding the tablet in landscape. (stupid hardware buttons, ugh!) So I tried remapping click action to disabled and long press click action to recent apps, so that just accidentally brushing the button wouldn't open up recent apps.

The long press remap works fine, but regular press/click does not get disabled. This does work correctly in 2.3.8. I have attached a log file which (hopefully) captures me attempting a single click and long press click of the recent apps button after setting it up in xposted additions and then rebooting. Let me know if I screwed it up, or if there is something else you want me to try and get in a log.

Just fyi, on my Samsung Galaxy Note 3 (touchwiz, JB), I can remap the Menu button to Recent Apps and remap long press Menu button to Menu button without any issues in the recent RC version. So far it looks like the RC version is working well on that device.
[Xposed Framework Modules] dk_zero-cool:
First of all you need to enable debug in the app and reboot. Otherwise the module will not print logs. Second, how did you get this log? Because something is wrong with it, it does not look like normal logcat output.
[Xposed Framework Modules] KestrelX:
Oops I missed the debug option. Will do it again tomorrow. And use a different app I guess, lol. I used logcat extreme this time.
[Xposed Framework Modules] KestrelX:
Take two.

Here are two logs - the first when I configured the remap. The second after rebooting and trying to regular press the recent buttons and then to long press it. Hope I got it right this time :p
[Xposed Framework Modules] dk_zero-cool:
The second one is what I need, but it only contains your long press action which is looking fine, but then again it was not your issue. You need to grab a log when you do a single click.
[Xposed Framework Modules] KestrelX:
I did a single click *right* before the long press. I can't imagine how it would not be in that log. I can try again when I get home, but I am not sure it will be any different.
[Xposed Framework Modules] KestrelX:
Ok here we go. This time I hit the single click 3-4 times and did not do any long presses.
[Xposed Framework Modules] dk_zero-cool:
Well I see why it does not get disabled. Normal clicks are executing long press events. Thanks for the log, I will see if I can figure out why long press is not dismissed on key up.
[Xposed Framework Modules] Zyquil:
Don't have logs with me atm, but will try to provide them when I get the chance.

Updated my Xposed Additions from 3.0.4 to the latest 3.1.4rc and I'm getting a bug.

I remapped my Recent Key softkey to single click (Menu) and long press (Recent Apps) but the single click doesn't seem to work. It still acts as a recent apps key on single as well as long press. However, when I remove the mapping, long press (Menu) works fine but single click seems to be bugged, as it opens the recent apps but opens the menu first before doing so.

Not sure what the problem was so I disabled it for the mean time.

Running on Stock JB 4.1 on my 5035E.
[Xposed Framework Modules] themadproducer:
[MENTION=3147360]dk_zero-cool[/MENTION]

Ready?

In my last few rounds of testing, if I wait about 15secs with screen off before pressing the volume button,... then volume button does not wake up screen. WEIRD? Reproduceable. But if I keep pressing it over and over, eventually, it randomly turns the screen back on? Or if I long press sometimes? Just strange. Just reporting.
[Xposed Framework Modules] dk_zero-cool:
The problem is that it never executes single click. Don't know why, but it is only affected by recent keys for some reason. I am already trying to figure out why, but this is not a problem in the latest release? Only in the RC?

Sorry, was just in the middle of a lot of code changes and I forgot all about this. Will try to have et ready to day.
[Xposed Framework Modules] Zyquil:
I'm actually not certain if it's only on the rc. I'm coming from 3.0.4 then jump updated to 3.1.4rc. And I agree, I believe it's only the Recent Keys as I've set the Vol Down to single click Power and it works just fine. The issue is that I disabled remapping of any key (no key maps but X Additions enabled) and somehow single click triggers the Menu before actually opening Recent Applications.
[Xposed Framework Modules] KestrelX:
My recent apps button issue has been happening in all 3.x versions I think.
[Xposed Framework Modules] Recognized Noob:
me too facing recent key issue
[Xposed Framework Modules] Goliath27:
Anyone know if there is an xposed app for Google keyboard suggestions? Mine doesn't always show in certain places like password and email fields, or search bars. Similar to this:
[Xposed Framework Modules] dk_zero-cool:
You want your keyboard to suggest passwords?

And about Emails and such, those things are not part of regular suggestions, those are individual app features. Suggestions lookup words in dictionaries while you type and suggests words based on what you have typed. I don't think that your emails (or passwords for that mater) is part of any dictionary.
[Xposed Framework Modules] egingell:
The keyboard can't see what's in the password field as you're typing it (it at least I hope it can't), so it can't predict. One might be able to make the dictionary return common website from the browser's history and email addresses from your contacts.

I just want the keyboard to always auto-capitalize/correct (it doesn't on Words With Friends and Facebook) and prefer user dictionary entries over built-in ("ROM" is in my user dictionary, but "ROOM" is always suggested).

At any rate, this is not exactly the thread for module suggestions or requests.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] Goliath27:
My mistake. I thought there was an actual module that I seen before but couldn't find now.

On Perfect Keyboard, it still allows you to see suggestions even in places like Google now.
[Xposed Framework Modules] DennisDD78:
Guys, this module works on 4.4 ?
[Xposed Framework Modules] dr3mro:
I love closer but will it support art some day?
[Xposed Framework Modules] egingell:
Nope. Never. But nails and/or screws support art... or tables, desks... some guy.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
Okay, I have attached 4 test versions for you. Let's see if one of these works.
[Xposed Framework Modules] paolo200:
Hi

I don't know if Samsung touchwiz is the cause but I found a horrible bug. I wanted to assign open camera on double tab when the screen is locked so it does open camera which is great but not only I can access the gallery without unlocking but pressing the back button sends me right back to the home screen. How is that even allowed to bypass the lock screen I don't get it.

I'm on note 3 N9005 running kitkat 4.4.2 stock ROM NB4 rooted
[Xposed Framework Modules] themadproducer:
[MENTION=3147360]dk_zero-cool[/MENTION]

Sorry to report, that all 4 cause a repeating soft or UI "Boot Loop" just after Go Launcher begins populating icons. Lucky I am able to disable xposed framework in recovery. No harm done but you best remove the links.

Thanks for the work.

Do you know what might be causing the loop?
[Xposed Framework Modules] dk_zero-cool:
It is not a bug, that is intended. I am looking to change this, but at the moment I cannot get any application to launch on top of the lock screen, so I have set it do be unlocked on app launch.

We are in Xposed, we can do whatever we want. With Xposed Modules, normal application rules does not apply.

I have rewritten a lot of code (commit), including the entire reflection library (commit), which might be the cause. Not good as this is not just one or two lines we are talking about.

Could you get a logcat just before it reboots?
[Xposed Framework Modules] themadproducer:
@dk_zero-cool

I don't know how I would go about getting a log since it never really boots up to a point where I can click or run anything.

If you know of a way, please advise.
[Xposed Framework Modules] paolo200:
ok I understand

Thanks for looking into it though ;)
[Xposed Framework Modules] dk_zero-cool:
You will have to get a logcat via ADB on the PC.

You can find a lot of tutorials on how to setup ADB on windows, like this one

And if you are not to familiar with using the terminal to use ADB, you can use applications like this one after your ADB setup.
[Xposed Framework Modules] dk_zero-cool:
Okay I have altered the module some more to make sure that it should not be able to create boot loop issues. If there is an error during boot that could crash the system, that part of the module will be automatically disabled.

So try the new attachment. It should boot and only print the crash report which you can then get via ADB, or a logcat app depending on how long your ROM keeps the log.
[Xposed Framework Modules] themadproducer:
Sounds good.

I will test it later tonight when I get home and send you a report.

Have a good wknd.
[Xposed Framework Modules] dk_zero-cool:
Just to be clear, this does not fix anything for you. It simply allows you to boot your device by disabling whatever part of the module is having issues. To fix it, I will still need a log.
[Xposed Framework Modules] themadproducer:
Ok, thanks for the heads up.
[Xposed Framework Modules] dk_zero-cool:
@themadproducer I just made it easier for you. I have added a Logcat Monitor that will add any errors and warnings about XposedAdditions into a log file. I have also added a log viewer in the app part where you can view this log and a menu entry that allows you to easily send the log file by mail, with my email pre-assigned.

So just install, reboot, open the log viewer in the app, press the send button and I will have your log right away without any further work from your part :)

The package is in the attachment a few posts above.
[Xposed Framework Modules] themadproducer:
Awesome. Now we're talking. Great idea. Stay tuned.
[Xposed Framework Modules] themadproducer:
[MENTION=3147360]dk_zero-cool[/MENTION]

Here's what I did.

- downloaded pkg and installed

- enabled module and rebooted

- boot was successful but volume key wakes up device

- clicked "error log". It's blank.

- enabled debug (just in case) and rebooted

- successful reboot but volume key wakes screen

- checked error log...blank

Am I doing this correctly?
[Xposed Framework Modules] dk_zero-cool:
I also fixed a few bugs that I found, one of them is apparently what was causing so much problems on your ROM. Well then, now I can re-create the 4 test version for you.

B.t.w.

The error log is not connected to debug. The log only contains serious errors and warnings. The debug options just enabled informative debug output to logcat.

EDIT:

Okay, I have attached new test versions with different attempts to fix the volume wake issue.
[Xposed Framework Modules] themadproducer:
@dk_zero-cool

:crying:

Tested all 4

- installed and activated without issue

- experienced a single soft reboot on first launch of ui of v2 and 4

- random soft reboots while using ui but no error log of v2 and 4

- also tried assigning a disable value to the volume key during screen off

With all scenarios, unfortunately, screen is woken up by volume key press.

I am now performing one more test with all other modules disabled.

I will report back if this helps.

UPDATE: nope, no luck.
[Xposed Framework Modules] dk_zero-cool:
It's like I said, if the screen is woken from native code, then there is not much to do. And it would seam that this is the case. It can be your version of the native input handler or some flag set by the kernel. In any case, as long as it is not caused by the Java part, I cannot change the behaviour.
[Xposed Framework Modules] MgudFrn:
Ahh, in button section "Power" option turns off the screen. Is there a vice versa option for this action? I mean is there any option for this:

I want to turn my screen on with long pressing of home key or back key when the screen is off and/or locked.

Anyways this module is great and very much useful. :)
[Xposed Framework Modules] dk_zero-cool:
Power is a keycode (A.K.A. your power key). When screen is off, it will turn it on and is on, it will turn it off.
[Xposed Framework Modules] MgudFrn:
Oh But i changed my back key to power on long pressing but it does turn off the screen when its on but doesn't act reverse. what might be the problem?
[Xposed Framework Modules] dk_zero-cool:
Well I would guess that this is a Capacitive button? Those are not buttons, they are just a section of your screen, and when your screen if off, it does not register your touches. In other words, Capacitive buttons will not work when the screen is off. At least not without some additional kernel support, but that is up to the kernel developer of your ROM.
[Xposed Framework Modules] MgudFrn:
Okay that means I can turn on my screen on using volume button right? Thank You :)

Edit:
[MENTION=3147360]dk_zero-cool[/MENTION] its not working with the volume up/down buttons either. I guess those are not the capacitive buttons.
[Xposed Framework Modules] themadproducer:
Ironic...your trying to turn ON the screen with your volume hard keys...and I want the opposite. Roms and kernels have their code variances. :D
[Xposed Framework Modules] dk_zero-cool:
Yes manufacturers changes a lot more than just the UI in their ROM versions. A lot of the internal behavior is changed to, and a lot of the manufacturers does a pure job of this, Samsung especially. I don't care very much for Microsoft and especially not Apple, but as a developer, things would some times be a lot easier with more strict rules. I don't think that Nokia is even allowed to change the background color on their devices. At least not without a formal request and properly a well documented reason ;p
[Xposed Framework Modules] dk_zero-cool:
What device and ROM are you using?
[Xposed Framework Modules] MgudFrn:
I'm using Karbonn A1* (mt6575) and the Rom is stock.
[Xposed Framework Modules] heddkandi:
First of all thank you dk_zero-cool for building this kickass app. This eliminates the need for installing custom ROMs on my phone entirely, as I previously had to do that in order to get the "hold back key to kill app" function to work.

I'm using the app with my Alcatel Fierce phone, and everything was going fine until earlier today when I decided to change the button remap settings that I had set on the app a week ago. To my surprise none of the button remaps I had set showed up. Hence, I decided to remap all soft keys in my navigation bar. These modifications includes:

1) Holding "Back" key > Kill foreground application

2) Holding "Home" key > Google search

Both of these worked wonderfully. However, a weird thing happened with my "Recent Apps" key (key 220 on my keyboard). By factory default, a single click on the button pops up the settings menu, while a hold shows the recent app list. With Additions enabled, even though I have set no remapping for the recent apps key, the single click on the button apparently registered as a long hold because every time I clicked on that button (in order to pull up the settings menu), the recent app list shows up regardless of how long--or short--I press on the button.

What's weirder: occasionally the setting menu did show up after a single click, but only for a moment before the recent app list popped up over it. This makes me suspect--thoughI I might be wrong--that Additions caused the pressing the "Recent Apps" button to register as both a single click and a long press!

I have explicitly remapped the button with Additions (where i assigned single press > settings menu, and long press > recent apps) but the problem did not go away. The only way to solve the problem was to disable Additions, which is fine, but I'd lose the wonderful benefits of Additions for the other buttons.

I'm using the stock ROM (4.2.2) of the phone--Alcatel Fierce. I thought Additions might conflict with other Xposed module so I disabled all modules except for Additions but the problem persisted. I have also tried uninstalling and reinstalling the app but that did not work either; the problem reappeared after the reinstall. Is there any way that I could fix this problem?

PS: Thank you for your help in advance. Again I really appreciate all the effort that you've done for Android users worldwide. Please keep up the good work dk_zero-cool.
[Xposed Framework Modules] killoid:
[MENTION=3147360]dk_zero-cool[/MENTION] latest version fc's when i attempt to assign action to a key.log attached.

W/XPrivacy/XApplication

Uncaught exception uid=10007: java.lang.RuntimeException: Unable to resume activity {com.spazedog.xposed.additionsgb/com.spazedog.xposed.additionsgb.ActivityScreenRemapKey}: java.lang.NullPointerException

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

E/AndroidRuntime

FATAL EXCEPTION: main

java.lang.RuntimeException: Unable to resume activity {com.spazedog.xposed.additionsgb/com.spazedog.xposed.additionsgb.ActivityScreenRemapKey}: java.lang.NullPointerException

at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2124)

at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:2139)

at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1672)

at android.app.ActivityThread.access$1500(ActivityThread.java:117)

at android.app.ActivityThread$H.handleMessage(ActivityThread.java:935)

at android.os.Handler.dispatchMessage(Handler.java:99)

at android.os.Looper.loop(Looper.java:130)

at android.app.ActivityThread.main(ActivityThread.java:3687)

at java.lang.reflect.Method.invokeNative(Native Method)

at java.lang.reflect.Method.invoke(Method.java:507)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:867)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:625)

at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:126)

at dalvik.system.NativeStart.main(Native Method)

Caused by: java.lang.NullPointerException

at com.spazedog.xposed.additionsgb.ActivityScreenRemapKey.setup(ActivityScreenRemapKey.java:116)

at com.spazedog.xposed.additionsgb.ActivityScreenRemapKey.onResume(ActivityScreenRemapKey.java:75)

at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1150)

at android.app.Activity.performResume(Activity.java:3843)

at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2114)

... 13 more
[Xposed Framework Modules] dk_zero-cool:
I will have a look, in the mean time, please try with XPrivacy disabled, because that one is the first in log and I don't want to waste time on locating an issue that might not be my issue to begin with.

Have you tried with the latest released from today?
[Xposed Framework Modules] killoid:
i've used it earlier with xprivacy enabled but no problem occured.however xprivacy disabled,it still fc's.btw i've assigned action for menu key succesfully but for other keys it fc's.
[Xposed Framework Modules] dk_zero-cool:
When does this happen? When you try to go into the key settings or when you have selected an action?
[Xposed Framework Modules] killoid:
when i try to go into a key settings.such as home>pressed it to configure>fc's.
[Xposed Framework Modules] dk_zero-cool:
Okay, try the below attachment. (Remember to reboot after install)
[Xposed Framework Modules] killoid:
now it worked! :good:
[Xposed Framework Modules] dk_zero-cool:
Great. Then I will wait a few ours and see what else comes in of errors, and then I better upload this to the official sites. But it is strange, the error that you got, should not be possible, which is why I did not make any conditional checks for it.
[Xposed Framework Modules] a.fontenele:
AFAIK it does.
[Xposed Framework Modules] blackbearblanc:
I'm trying to get tap power button for camera to work. It doesn't. It vibrates but doesn't open camera. All other apps seems to work but not this. I tried default shortcuts and Application list. Anyone tried this?
[Xposed Framework Modules] jacolguz:
FC in Samsung Galaxy Note 3 when open Xposed Additions
[Xposed Framework Modules] dk_zero-cool:
Come on please, I really need more information than that if I am to have any chance of correcting it. When does it FC? That would be a good place to start, seen as there are 7 different activities. Also, can you get a log of the crash? The app has an Error Log Viewer, if the app itself can open.
[Xposed Framework Modules] dk_zero-cool:
Vibrate means nothing, that is done long before any actions is considered. Does the log say anything? Also, seen as the camera is the only one, not sure it's a bug with the module.

An there is no default camera action. There is a default re-map as camera key, but that is something completely different. It just emulates itself as a camera hard button, which does not mean that it will open any camera apps.
[Xposed Framework Modules] coronanlime:
Using a Droid Maxx. Great app and is working except for one thing. All I did was add kill for long press of back button. For some reason when module is active it makes the tasks button do a double vibration when only pressed once.
[Xposed Framework Modules] dk_zero-cool:
That is an error in some ROM's, something that I am actually sitting and working on a solution for as we speak.
[Xposed Framework Modules] blackbearblanc:
Log send
[Xposed Framework Modules] dk_zero-cool:
Yes, but it is kind of difficult to read without line breaks. Can you send this over mail instead. In the app, there is an Error Log Viewer. In the top, there is a send button. The mail, log, device info and everything is predefined. you don't have to type anything.
[Xposed Framework Modules] blackbearblanc:
Ok
[Xposed Framework Modules] dk_zero-cool:
Yes that was much better, and the log does contain some application launch errors, so I will have a look at that and get this issue resolved.
[Xposed Framework Modules] blackbearblanc:
Thanks. It's not because I'm on KitKat?