yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] dk_zero-cool:
No there is no way. When I made this, my opinion was that a lock screen should always be able to rotate, if user enables rotation. The blacklist for apps was made because some applications really does not work with rotation. The lock screen does, since it's the same used on tablets and other devices where it is allowed to rotate. So no, I did not add any blacklist option for it.

However, the lock screen rotation has always been a bit unstable, since different devices implement their own lock screen and some users install 3'rd party versions. Some of these uses their own settings for rotation. So even if I made a blacklist, it would not work on all devices. But I can add one to the new version of the module, but no ETA on that one yet.
[Xposed Framework Modules] xmxm:
If anyone is interested in using additional keys (or swipes) from Xposed Additions, it could be easily done using Tasker. To do so, create a new task, add new Shell Action (Code -> Run shell) and put one of the following commands into command field:

for sending single key: input keyevent XX (for list of codes, see this pages: Link1, Link2

for sending text string: input text <string>

for swiping gesture: input swipe x1 y1 x2 y2

make sure you check "use root option".

After you created it, go to Xposed additions and link your key to Shortcut option, select Tasker from the list and select the task that you have created and that should be it.

If you need to find proper coordinates for swipe gesture, go to Settings -> Developer options -> Input and enable "pointer location" option. It would show a status bar at the top of screen with touch information. Tap and hold the area on the screen and that point coordinates will be shown in the status bar.

Here is a sample of scrolling tasks I've created, which also take screen orientation into consideration - you may need to tweak the values depending on your screen resolution:

Up
A1: Test Display [ Type:eek:rientation Data: Store Result In:%disporient ]
A2: Run Shell [ Command:input swipe 800 1250 800 500 Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: ] If [ %disporient ~ landscape* ]
A3: Run Shell [ Command:input swipe 800 1600 800 500 Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: ] If [ %disporient ~ portrait* ]

Down
A1: Test Display [ Type:eek:rientation Data: Store Result In:%disporient ]
A2: Run Shell [ Command:input swipe 800 500 800 1250 Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: ] If [ %disporient ~ landscape* ]
A3: Run Shell [ Command:input swipe 800 500 800 1600 Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: ] If [ %disporient ~ portrait* ]
[Xposed Framework Modules] yurividal:
[MENTION=3147360]dk_zero-cool[/MENTION], any chance to update this to work with Marshmallow?
[Xposed Framework Modules] dk_zero-cool:
Yes when Android 6 get's released by someone for my device so that I can test it.
[Xposed Framework Modules] yurividal:
Thanks for the answer! What device do you have?
[Xposed Framework Modules] dk_zero-cool:
Galaxy S III (I9300)
[Xposed Framework Modules] rogerinnyc:
Double-Click Home to Turn on Power while Screen Off

I'm having a similar problem on my rooted Note 4 (910C), running Lollipop 5.1.1. with Talexop kernel. I've got your pro module and want to remap a double click of my home button, screen off condition, to toggle power (I find a single click too often gets activated in my pocket and, because I bypass security in my home environment, I get unintentional actions). The double-click works right after a reboot to turn on power, but, eventually, it only works if another button has been pushed first -- e.g., volume down, then double-click of home or, more often, I double-click home, nothing happens, then I double-click again and the phone wakes. It's almost as though some screen off other action is needed to wake the phone (or, maybe, the kernel?) to some level where it can recognize the screen-off double-click. I didn't have this problem on my Note 3, but that was always running KitKat. As a side note, and probably unrelated, if I use Gravity Box to wake the phone using a wave over the proximity sensor, that always seems to work first try, so the proximity sensor doesn't seem to need any pre-wakeup, so to speak....

Any thoughts or advice would be appreciated.
[Xposed Framework Modules] dk_zero-cool:
First of all. I have never played with the proximity sensors on phones, but all have one thing in common. They all emits some sort of electromagnetic field/beam, or sound, although I do not think that they are used in phones and tablets. Now constantly throwing beams out and reading distances, would consume some amount of power, which is why I will bet that Android keeps this turned off when not in use. So if GravityBox uses it, it properly keeps a monitor service alive to read the sensor data. Doing so will also keep parts of the system alive. Xposed Additions does not have any background services of any sorts.

I don't know what this issue is caused by, but if you can get a log from when your double click fails to turn on the screen, while having debug enabled, I might be able to see what happens.
[Xposed Framework Modules] akamustang:
Woot, Marshmallow available on Galaxy S3 now ([ROM][6.0][i9300][ALPHA] Unofficial CyanogenMod 13)

My favourite and most used Xposed module, I wish you the best in getting it to work with Marshmallow!
[Xposed Framework Modules] dk_zero-cool:
Yes I'm already on it, but it might take awaile cause Android 6 has more build-in problems than any other Android update and I do not have much time to sort them out this week.
[Xposed Framework Modules] fndpena:
I was trying to make one of the capacitive buttons act like the power button, to wake the device.

I choose the button (Home), set the condition (screen off) and action (power) but when I test, nothing happens. The button doesn't respond when the screen is off.

Any tips?

I'm running CM 12.1, xposed v78 sdk22 and there are other modules working just fine.
[Xposed Framework Modules] My1xT:
might it not just be that the phone turns the capacitive buttons off to save power because in a sort they are like a touchscreen minus the screen.
[Xposed Framework Modules] rogerinnyc:
Unfortunately, even with debug enabled, no log is captured. I think the best explanation I can come up with is that the phone is somehow in a "deeper" sleep and some other button actions are needed first. What I have noticed is that if I set a long press of the home button to power on with screen off, that works more of the time than a double click does -- which is kind of consistent with that notion....
[Xposed Framework Modules] dk_zero-cool:
The capacitive buttons is nothing more than some specific (x, y) coordinates on your display. I think that is makes perfect sense that your screen does not capture touch when you turn it off. Now if you want to capture touch while the screen is off, you need to talk to your kernel developer. It is not something that can be changed with an Xposed Module

Not sure why this is. Without a log or the device in hand, I am out of options. Try another kernel and see if that should create a different result.
[Xposed Framework Modules] fndpena:
[MENTION=3147360]dk_zero-cool[/MENTION]

I mean the hardware capacitive keys, not the software navigation bar.
[Xposed Framework Modules] dk_zero-cool:
That's the one that I am talking about. Software Navigation is an app, Capacitive is "Hardware Keys" simulated on the display and Hardware keys are, well, Hardware Keys.
[Xposed Framework Modules] Kirrrr:
Hey there!

The wintrer is coming. Again.

We wear gloves and mittens.

Thus the mapping of the call answer/reject/end action onto hardware buttons became actual.

For the gods sake we have an ability to map the call answer and the call end (not reject!) onto Home and Power buttons correspondingly by the standard Android means in the Accessibility options.

But the call reject doesn't have such option. It can be mapped onto Volume buttons with some scenario I guess. E.g.: the Volume Up button is intercepted and treated as a Call End button during an incoming call only.

I know the only one app which is trying to do this — EZbutton (with it's senior brother EZanswer). It does the trick some way but it is buggy, old and unworkable on modern firmwares.

Well. Looks like the Xposed Additions is my only hope as for now. It has some options deal with Volume buttons, call status and call control but I can't see is there a shure way to achieve result described above with the subj?

Regards!

:)
[Xposed Framework Modules] dk_zero-cool:
Android 6

It took some doing this time, but Android 6 support is now added to the module. For now the updated version can only be found in the Beta section of Xposed Repo. This means that you need to enable Beta Review (Or whatever it is called) in your Xposed Installer app before you can see it. I had to make a lot of backend changes to get this support added, which could prove to affect prev. supported devices, so testing before official release.

Changelog can be read in the Xposed Installer App or Xposed Repo online, but headline is as mentioned above, Android 6 now supported.
[Xposed Framework Modules] robertogl:
Thanks! It works on android 5.1.1, but it seems to have an old problem: with this version and 3.5.9 I can't use 'media next' and ' media previous' with long press on volume button and screen off.

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed Framework Modules] dk_zero-cool:
There is no changes to the remap engine. There will be a new engine in the new 4.x version that I am working on. This is just an update for 3.x mostly to get Android 6 working. Hopefully the last update for this old version. The 4.x version is more than 70% done.
[Xposed Framework Modules] iamsparta:
The module works as intended on my Nexus 5 running stock 6.0.1. Thanks!

One problem that I found was that the module interferes with the double tap power button to open camera that was recently added by Google. I checked by disabling the module and rebooting. If you could add a workaround, that would be great!
[Xposed Framework Modules] akamustang:
Yep, beta is working fine for me on Nexus 6 CM13 , muchas gracias!
[Xposed Framework Modules] khoald92vn:
I have the same issue with both 3.5.9 and 3.6.0 version. 3.5.8 is the solution for me until now. Hope v4.x will fix this. Thanks dev.
[Xposed Framework Modules] VALRCIEL:
How can i make paste button? Any suggest?
[Xposed Framework Modules] gadget!:
Would it be possible to make some system functions available?

For example, the screen shot combination. On aosp roms it is [POWER] + [VOLUME DOWN], this is so much easier for one handed operation than [POWER] + [HOME].

Thanks in advance

sent from a Galaxy far far away.
[Xposed Framework Modules] SnipER.UA:
Hello, what about fix for mentioned before bug introduced in 3.5.9?

"When condition is Screen Off, some media actions are not working. Specifically, "Media Play/Pause" (Key 85). Other events, like Volume Up are working.

Same event works when Sceen On.

All works in 3.5.8.

Android 4.4.4, Samsung SM-G850F. Using preinstalled music audio player."
[Xposed Framework Modules] shinpil:
about haptic feedback

I remapped not long press, but short press menu key to recent app. And it does not get haptic feedback.
[Xposed Framework Modules] lmike6453:
I remapped my back key to double click is recent apps and no haptic feedback. Running stock tw 4.3 on note 3
[Xposed Framework Modules] gladson1976:
Can these be added ?
[Xposed Framework Modules] dbesoli:
Well, I think I have the logcat....

I've seen this in line 368:

D/com.spazedog.xposed.additionsgb$PowerManager( 1845): Adding Power Management hooks

I/Xposed ( 1845): de.robv.android.xposed.XposedHelpers$ClassNotFoundError: java.lang.ClassNotFoundException: com.android.server.power.PowerManagerService

I don't know if it have something to do with Xposed Additions but I hope it will be useful to you.
[Xposed Framework Modules] dk_zero-cool:
Hardware keys single click does not get feedback. That's the way it's meant to be.

Again, I send a notice to Android that I want a Long Press feedback. If you don't get that, then it's something with your ROM. I don't control it, I just call it.

I don't know. I have no idea where bluetooth headset buttons are controlled, and not sure I ever will. Maybe some time in the future, but at the moment I rather fix the current issues, add missing feature and look at adding Software Keys the right way.
[Xposed Framework Modules] dk_zero-cool:
Yes this is the problem that you are having. The class that I am trying to change does not exist on your ROM. What is your ROM? 4.0, 4.1 ?
[Xposed Framework Modules] dbesoli:
GT-I9100 with Android 4.1.2 on Stock ROM. Only rooted with Philz Kernel 5.15.9 (the last as for now too). No other modings, only Xposed
[Xposed Framework Modules] dk_zero-cool:
Well then that class should be available, has been since ICS. Not much to do as I cannot check where they put it and if it has been altered at the same time.
[Xposed Framework Modules] shinpil:
Can you add haptic feedback on single click?

Oh, only long click gets haptic feedback.

Can you add haptic feedback on sigle click and double click?

It would be better that I can select whether get haptic feedback or not.
[Xposed Framework Modules] dk_zero-cool:
Look, The Feedback is setup after Android Standards. I am not gonna change the behavior of it. They should work just like all non-remapped buttons and should be manageable via Android native settings.

B.t.w, Double Clicks already get haptic feedback on the second click when the action is invoked, just like with long press.
[Xposed Framework Modules] shinpil:
menu key and back key should get haptic feedback

Single clicking menu or back key get haptic feedback on stock rom...

Doesn't it?

I felt weird when it does not get haptic feedback after remap menu key.

Please consider it...:crying:
[Xposed Framework Modules] dk_zero-cool:
Don't know about stock ROM's, but stock Android does not and proper built Custom's neither. Virtual Keys get on single clicks, Hardware Keys does not. Why should it. Virtual keys can't be felt when clicking on them, Hardware keys can. When you can actually feel a button, you don't need vibrations to tell you whether or not you clicked on it.
[Xposed Framework Modules] dbesoli:
Ok, thanks for the help. Maybe I need to change to a custom rom after some time of non flashing
[Xposed Framework Modules] shinpil:
I'm using gt-i9500

I'm using gt-i9500.

I think gt-i9300 also gets haptic and sound feedback on single clicking menu or back key.

The menu and back key are touch key, so I can't feel clicking on them.

The home key, volume key do not get haptic feedback, and I also think it is reasonable because they are hardware keys.

However, menu and back key are different...

They should get haptic and sound feedback.
[Xposed Framework Modules] dk_zero-cool:
I have a GT-i9300 and the Back and Menu are Virtual Keys, not Hardware. And Feedback is working just fine on them with CM10.2. Only Home, Volume and Power does not get feedbacks on single click. So if you have Virtual keys without it, you should check your ROM settings or logcat while clicking to see if you get any errors, especially if you are using Samsung's Stock ROM as they have a tendency to break any compatibility with Original source.
[Xposed Framework Modules] shinpil:
I haven't used logcat

I haven't used logcat.

So I don't know how to see logcat.

But I found this error repeats when I click menu key which is remapped.

E/EnterpriseContainerManager: ContainerPolicy Service is not yet ready!!!
[Xposed Framework Modules] dk_zero-cool:
That's not about the module. Nothing is in that log.
[Xposed Framework Modules] shinpil:
I attached logs.

I attached log files.
[Xposed Framework Modules] dk_zero-cool:
Nothing, which means no errors.
[Xposed Framework Modules] shinpil:
Then why does soft keys not get haptic and sound feedback?

Then why does the touch keys(menu and back keys) not get haptic and sound feedback?

It works fine if I disable remapping.

What's the problem:crying:
[Xposed Framework Modules] dk_zero-cool:
Version 3.6.1

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

Screen Off, Volume Up = Next

Screen Off, Volume Down = Previous

Screen Off, Long Press Home = Play/Pause

Just tried this on my own device using Player Pro, and it is, as always, working just fine. I have stated this many times, Almost every single Stock player ever made, does not support media broadcasts. There is even an alert dialog in the app when you select this key as a remap option. So if this is indeed an issue on your device, you need to confirm this by using a third party Player from Play Store that supports this feature. In case it still does not work, I need a log, which can be grabbed using any Logcat app, while the screen is off and you use one of your media remap's. And debug needs to be enabled in the app, restart required.
[Xposed Framework Modules] SnipER.UA:
First of all, thank you for great application!

On bug, it's pretty plain and simple: It worked in version 3.5.8 AND below and stopped in 3.5.9 and above. Other environment (player/device/fw) was not changed, and this work/not work behavior is result of Additions version switch only. So it was supported, or, maybe, it was just pure luck, but then you removed this lucky code )

As another user mentioned, "Tryed with different music player, and combination. On screen on or double\triple click everythings works.", so really, not support problem.

Attaching logs for 3.6.1. Outputs for screen on and screen off are same unfortunately.
[Xposed Framework Modules] khoald92vn:
I tried version 3.6.1. Screen off, Long volume up = Next + poweramp music player but no lucky. Since version 3.5.9 until now i have the same problem like some people above. Maybe the ploblem is only for Samsung devices? Because i use samsung s3.
[Xposed Framework Modules] dk_zero-cool:
I have the SGS3 also. Do you use a complete Stock ROM, or a customized Stock that I can use to test with? I have found that ever Samsung ROM differ, so flashing just any version does guarantee that I can reproduce the problem.
[Xposed Framework Modules] robertogl:
Edit

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed Framework Modules] khoald92vn:
I'm using the latest Blekota note 5 Rom, android 4.4.4. And xposed additions 3.5.8 worked completely well for me.
[Xposed Framework Modules] SnipER.UA:
I have rooted stock 4.4.4 for my SM-G850F, G850FXXU1BOA2, don't know if it helps since it's not s3 )

I can provide more logs, or install some test apps from you, if needed.

Was so many changed in 358->359? Log states only "Fixed issue with latest Android 5.1 revisions", did you re-reviewed diff? Or maybe, another version of SDK was introduced at that time?
[Xposed Framework Modules] robertogl:
Well, I had the same problem with 3.5.9 and 3.6.0, but with 3.6.1 the long press for previous song (for example) works. I don't know if this is due to the update...

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed Framework Modules] dk_zero-cool:
I checked the code diff yesterday, and no there is not much changed between them. Nothing at all that would explain this.
[Xposed Framework Modules] dk_zero-cool:
I am going to compile a few different versions to narrow down the exact change that broke this and add a few additional log output as wel. I like your logs, they are simple and contain just what they need. So if you could test these once done, that would be great.
[Xposed Framework Modules] Wak7eeM:
Can you tell me which xposed version is comfortable for samsung galaxy s3 verizon android version 4.3 plzzz...?
[Xposed Framework Modules] dk_zero-cool:
Not really, I have the i9300 with CyanogenMod 13, and I have never had anything but CyanogenMod on this thing or any other device for that mater. AOSP lacks features and TW lacks performance and has to many security issues.
[Xposed Framework Modules] Wak7eeM:
I am scare from a bootloop
[Xposed Framework Modules] dk_zero-cool:
I don't know which Xposed Framework version has this feature, especially for TW base. But if you are running Android 4.3, you can install Cydia Substrate as a replacement for Xposed Framework and test one of the 3.6.x version of the module. If you get boot loop, simply pull the battery, turn it back on and press Volume Up until you see the lock screen. This will boot the device without loading the module. If you do not get any boot loops, just replace Cydia Substrate back to Xposed Framework (If you need other modules besides this one). Xposed Additions 3.6 supports both.
[Xposed Framework Modules] khoald92vn:
The latest version is always the best. However, if you use volume button when device is screen off and have issue with it, then try version 3.5.8.
[Xposed Framework Modules] Wak7eeM:
Are you sure...i am scare from a bootloop...?

---------- Post added at 04:23 PM ---------- Previous post was at 04:16 PM ----------

Can you tell me how to use cydia subtrate..?
[Xposed Framework Modules] madhad77777:
Ugh. Please fix the issue where you can't pause the media player with the screen off. This used to work. I use this all the time and miss it now that it's gone. I promise, if you fix it, I'll even finally register the app. :)
[Xposed Framework Modules] Kirrrr:
Looks like my prevous question was too long and flooded with details or my English is too bad. =(

Try to ask it again more straight.

Is it possible to setup "Skip incoming call with Volume Up button" and "Answer incoming call with Volume Down button"? The Volume Up/Down buttons must be intercepted only when phone is ringing, not during talk.

Regards! :)
[Xposed Framework Modules] egingell:
If you're afraid of boot loops, then don't use Xposed or any other system modifying software.

Ask them. This is Xposed Additions support - not Cydia Subtrate support.

Sent from: SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] dk_zero-cool:
It will be possible, but in the 3.x version. At the moment the closest you get is assigning a button as Call Button.
[Xposed Framework Modules] Kirrrr:
Will wait for it because I don't know any other working methods to achieve what I want. :good:

Thank you!
[Xposed Framework Modules] dk_zero-cool:
Okay people with Media remap issues. Version 3.6.2 should fix your problems (module related, other life problems is not included), at least for some of you.
[Xposed Framework Modules] Kirrrr:
[MENTION=3147360]dk_zero-cool[/MENTION], excuse me but I just realized I've lost the point. =( You said "It will be possible, but in the 3.x version ... " But the current version is 3.6.1. What did you mean?
[Xposed Framework Modules] egingell:
Look again. The latest/current it's 3.6.2.

Sent from: SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] Kirrrr:
[MENTION=4587767]egingell[/MENTION], errr... dk_zero-cool told about 3.x so there is no difference in this aspect I guess.
[Xposed Framework Modules] robertogl:
I think he means 4.x.

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed Framework Modules] dk_zero-cool:
Sorry, the new app/module currently being worked on is 4.x. This version will be a lot more abstract by adding event grouping and more conditions. It will be able to do what you want.
[Xposed Framework Modules] egingell:
I was merely correcting you about which is the latest. :)

Sent from: SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] Kirrrr:
Roger that.

Thanks!
[Xposed Framework Modules] mrrocketdog:
really hating to ask this but having issues finding xposed bridge. DL'd xposed additions from playstore.

also do i need xposed bridge jar ; and how to set up ?

promise i read OP :D but need a little hand holding if someone would be so kind/has the patience. thank you.

also , this is for lolli 5.1.1 only correct ?

thanks again.

"all i can really do is stay out of my own way and let the will of heaven be done"