Okay guys, I'm starting this thread to join forces on finally taking control of the Google Assistant key on the G7. I've read several posts here on XDA and elsewhere about this, and it seems LG has taken a great effort in NOT allowing a simple remap of this key (other phones have been offering some flexibility lately). The best workaround I've found (and personally used) is to use something like Automate or Tasker to catch when Google Assistant is launched, kill it and open something else. Not very clean and there's some delay, but it sort of works.
But now that I have rooted my phone, I decided to investigate it deeper. What I've found:
The keycode of this button is 165.
It is intercepted by WindowManager, LGPhoneWindowManager and HotKeyController.
Finally, the following package/class is invoked: com.google.android.googlequicksearchbox/com.google.android.apps.gsa.staticplugins.opa.OpaActivity
When we disable this button on the settings, it is still intercepted by the same processes, but HotKeyController and LGPhoneWindowManager flag the key as "disabled" and do nothing.
Since this keycode is being intercepted, other applications (such as KeyEvent) can't detect it.
These are the relevant logcat entries for when the button is enabled:
Code:
05-27 22:13:18.614 4175 4568 D InputReader: Key event: device=10 type=0x0001 value=0x00000001 when=28854380687000
05-27 22:13:18.615 4175 4568 D WindowManager: interceptKeyTq keycode=165 down=true injected=false mDisplayState=2 interactive=true keyguardActive=false flags=0x8 policyFlags=22000000
05-27 22:13:19.074 4175 4248 D LGPhoneWindowManager: hotKeyRelease count= : 1
05-27 22:13:19.075 4175 4248 D LGPhoneWindowManager: hotKeyActions : mode=11, interactive=true, type=1
05-27 22:13:19.075 4175 4248 D HotKeyController: launch Assist: 1
05-27 22:13:19.077 4175 4248 I HotKeyController: don't show Guide Dialog by HotKeyController.
05-27 22:13:19.128 4715 4734 V AssistManager: Voice open
05-27 22:13:19.136 24832 24845 I AssistStructure: Flattened final assist data: 11288 bytes, containing 1 windows, 111 views
05-27 22:13:19.198 4175 5072 I ActivityManager: START u0 {flg=0x10008000 cmp=com.google.android.googlequicksearchbox/com.google.android.apps.gsa.staticplugins.opa.OpaActivity (has extras)} from uid 10185
And these are the logcat entries for when the button is disabled:
Code:
05-29 12:43:46.816 4126 4557 D WindowManager: interceptKeyTq keycode=165 down=true injected=false mDisplayState=2 interactive=true keyguardActive=false flags=0x8 policyFlags=22000000
05-29 12:43:46.837 4126 4557 D HotKeyController: AI key setting disabled
05-29 12:43:46.838 4126 4557 I LGPhoneWindowManager: hotkey disabled
05-29 12:43:46.964 4126 4557 D InputReader: Key event: device=10 type=0x0001 value=0x00000000 when=11419706112000
05-29 12:43:46.966 4126 4557 D WindowManager: interceptKeyTq keycode=165 down=false injected=false mDisplayState=2 interactive=true keyguardActive=false flags=0x8 policyFlags=22000000
05-29 12:43:46.974 4126 4557 D HotKeyController: AI key setting disabled
05-29 12:43:46.974 4126 4557 I LGPhoneWindowManager: hotkey disabled
Any suggestions on where to go from here? Some ideas: somehow detect this button by monitoring logcat (probably not very efficient); spoof com.google.android.googlequicksearchbox/com.google.android.apps.gsa.staticplugins.opa.OpaActivity with something else (don't know if it's possible).
Since you're rooted you can assign quite any action you like to this button using xposed edge. I'm using it to toggle the flashlight, which also works flawlessly while the phone's in deep sleep.
drfranz said:
Since you're rooted you can assign quite any action you like to this button using xposed edge. I'm using it to toggle the flashlight, which also works flawlessly while the phone's in deep sleep.
Click to expand...
Click to collapse
This module is interesting, thanks. But I'm afraid it won't work, because that key event is intercepted by WindowManager and HotKeyController, so it's not exposed to the system as the other keys. I have an app installed that capture every key press and return the respective keycode, and it doesn't work for this particular button.
Perhaps something that hook into one of these classes (since we're talking about Xposed) would work, but that would imply a new module (AFAIK). I also tried using Tasker's AutoTools to react to the logcat events, but it didn't work well, and is not very performance/battery efficient. So far I'm using the other method I mentioned, in Automate: kill the Google Assistant app as soon as it's launched (just the part that is launched by this button), and launch something else.
We're getting our v40 rooted now, so I'll keep an eye here if it's OK
Any progress yet?
Thanks! I will try it on my V50ThinQ.
Automata
dbolivar said:
This module is interesting, thanks. But I'm afraid it won't work, because that key event is intercepted by WindowManager and HotKeyController, so it's not exposed to the system as the other keys. I have an app installed that capture every key press and return the respective keycode, and it doesn't work for this particular button.
Perhaps something that hook into one of these classes (since we're talking about Xposed) would work, but that would imply a new module (AFAIK). I also tried using Tasker's AutoTools to react to the logcat events, but it didn't work well, and is not very performance/battery efficient. So far I'm using the other method I mentioned, in Automate: kill the Google Assistant app as soon as it's launched (just the part that is launched by this button), and launch something else.
Click to expand...
Click to collapse
Can you please share your automate flow or the name of it if it's part of the automate library?
drfranz said:
Since you're rooted you can assign quite any action you like to this button using xposed edge. I'm using it to toggle the flashlight, which also works flawlessly while the phone's in deep sleep.
Click to expand...
Click to collapse
What module you use in xposed?
viruz187 said:
What module you use in xposed?
Click to expand...
Click to collapse
xposed edge pro:
https://play.google.com/store/apps/details?id=com.jozein.xedgepro&hl=en
I use this exposed module: PBMC Key chains. It works with every button of my rooted G7+, even in deep sleep.
zhlvf said:
I use this exposed module: PBMC Key chains. It works with every button of my rooted G7+, even in deep sleep.
Click to expand...
Click to collapse
Does it work on pie? Everytime I install it using edexposed it says framework not installed
dbolivar said:
So far I'm using the other method I mentioned, in Automate: kill the Google Assistant app as soon as it's launched (just the part that is launched by this button), and launch something else.
Click to expand...
Click to collapse
This workaround works to me only when the screen is on but not when it is in the always-on screen, that is the scenerario that would be more interesting (I'm thinking in having the phone in the pocket, to click the button and start doing the stuff). Did you achieve it to work this way?
drfranz said:
xposed edge pro:
https://play.google.com/store/apps/details?id=com.jozein.xedgepro&hl=en
Click to expand...
Click to collapse
zhlvf said:
I use this exposed module: PBMC Key chains. It works with every button of my rooted G7+, even in deep sleep.
Click to expand...
Click to collapse
Awesomeslayerg said:
Does it work on pie? Everytime I install it using edexposed it says framework not installed
Click to expand...
Click to collapse
Same question, does this work in Pie? Last time I tried to install Xposed module in Magisk it bootlooped my phone
For me it works.
Awesomeslayerg said:
Does it work on pie? Everytime I install it using edexposed it says framework not installed
Click to expand...
Click to collapse
I'd like the assistant button to display the following screen. Any suggestion?
drfranz said:
xposed edge pro:
https://play.google.com/store/apps/details?id=com.jozein.xedgepro&hl=en
Click to expand...
Click to collapse
I just used xposed edge (not pro yet) on my new LG V-40 with Pie. I had previously tried it to do similar on a Samsung S8+'s dedicated Bixby button and it worked there as well. Of course, you must be rooted and have xposed installed. But damn, that's nice!
whitedavidp said:
I just used xposed edge (not pro yet) on my new LG V-40 with Pie. I had previously tried it to do similar on a Samsung S8+'s dedicated Bixby button and it worked there as well. Of course, you must be rooted and have xposed installed. But damn, that's nice!
Click to expand...
Click to collapse
Please can you give me some more details how you did this? Last time I tried, my V40 bootlooped. Exact modules, what order did you install and reboot to make it work?
nyttliv7 said:
Please can you give me some more details how you did this? Last time I tried, my V40 bootlooped. Exact modules, what order did you install and reboot to make it work?
Click to expand...
Click to collapse
Happy to try and help...
On my V40 rooted with Magisk 20..4:
installed these Magisk modules: Riru-Core v. 19.8, Riru-EdXposed (Sandhook - I have no idea what the differences are between this and YAHFA - I just chose one) v0.4.6.1.
installed EdXposedManager-4.5.7-45700-org.meowcat.edxposed.manager-release.apk <https://github.com/ElderDrivers/EdXposedManager/releases/download/v4.5.7.0.0/EdXposedManager-4.5.7-45700-org.meowcat.edxposed.manager-release.apk>
installed com.jozein.xedge_v62_8a2004.apk <https://dl-xda.xposed.info/modules/com.jozein.xedge_v62_8a2004.apk>, enable it in EdXposedManager, reboot.
In the XposedEdge app, tap Key, tap +Add, press the google assist key. A new item is added KEYCODE_INFO. Check its box and press the down arrow. Choose what you want to do for Click, Double-click, and Long press events from the list shown when tapping each event entry. Do not think a reboot is needed at this point. Just exit Xposed Edge and try the assistant key to see if you get what you wanted.
Hope this helps.
This app works now ?
https://play.google.com/store/apps/details?id=flar2.homebutton
(paid version)
---------- Post added at 10:28 ---------- Previous post was at 10:25 ----------
whitedavidp said:
Happy to try and help...
On my V40 rooted with Magisk 20..4:
installed these Magisk modules: Riru-Core v. 19.8, Riru-EdXposed (Sandhook - I have no idea what the differences are between this and YAHFA - I just chose one) v0.4.6.1.
installed EdXposedManager-4.5.7-45700-org.meowcat.edxposed.manager-release.apk <https://github.com/ElderDrivers/EdXposedManager/releases/download/v4.5.7.0.0/EdXposedManager-4.5.7-45700-org.meowcat.edxposed.manager-release.apk>
installed com.jozein.xedge_v62_8a2004.apk <https://dl-xda.xposed.info/modules/com.jozein.xedge_v62_8a2004.apk>, enable it in EdXposedManager, reboot.
In the XposedEdge app, tap Key, tap +Add, press the google assist key. A new item is added KEYCODE_INFO. Check its box and press the down arrow. Choose what you want to do for Click, Double-click, and Long press events from the list shown when tapping each event entry. Do not think a reboot is needed at this point. Just exit Xposed Edge and try the assistant key to see if you get what you wanted.
Hope this helps.
Click to expand...
Click to collapse
Appreciated! But I choosed the app instead.
https://play.google.com/store/apps/details?id=flar2.homebutton
nyttliv7 said:
This app works now
https://play.google.com/store/apps/details?id=flar2.homebutton
(paid version)
---------- Post added at 10:28 ---------- Previous post was at 10:25 ----------
Appreciated! But I choosed the app instead.
https://play.google.com/store/apps/details?id=flar2.homebutton
Click to expand...
Click to collapse
This still requires root though right?
Related
I have found a nice Torch Light setting. If you set it 'on', when the screen is off, a long-press on the Volume-Up key starts the light. A press on the Volume-Down key turns it off, and there is a configurable time-out too.
Here's what's odd: I cannot find it in the settings anywhere, but found it though adding an 'Activity' shortcut through SSLauncher (my shell of choice). This one is named TocrhLight IIRC, in case anyone wants to install the free version and try it.
I have found these Activity settings to be a huge mine of hidden features, or at least shortcuts to deeply buried settings. In this case, I think the feature is actually hidden. Room for a dedicated app just to set this setting, I feel.
Apologies if this is obvious or posted elsewhere, but I could not find it anywhere.
Hello,
thank you very much, that was what i was missing from my note 2.
I used Activity-Launcher from Play-Store to start this Setting.
Regards
Robert
Nvm found it
Sent from my SM-N9005 using xda app-developers app
Can anyone talk me through the steps to set this up?
Download nova launcher. Long press on desktop and add shortcut. Then choose activities choose settings and from there torchlight. Thats it.
But its not working flawless. This morning i needed the flashlight but didnt work. I had to unlock my phone andnlock it again to make it work.
Sent from my SM-N9005 using xda app-developers app
Hm, might be useful.
Though personally I'll stick to Flashlight HD. It has a widget which is a flashlight toggle.
If you are rooted and have xposed framework installed, you can access the hidden setting via installing Wanam Xposed from the Google store.
Just a heads up.
Sent from my SM-N9005 using xda app-developers app
What I'd like to see is a super bright torch like in the CM roms but without root.
The difference is astounding.
Amdathlonuk said:
What I'd like to see is a super bright torch like in the CM roms but without root.
The difference is astounding.
Click to expand...
Click to collapse
Any experience with long term use and potential LED damage/overheating? Also does anyone know why I wouldn't have any torch setting or app? Using Verizon note 3 and would love this mod
SquirtingCherry said:
Download nova launcher. Long press on desktop and add shortcut. Then choose activities choose settings and from there torchlight. Thats it.
But its not working flawless. This morning i needed the flashlight but didnt work. I had to unlock my phone andnlock it again to make it work.
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I just tried and it worked for me. I have pin lock set and running widgetlocker.
Sent from my Nexus 7 using Tapatalk 4
lax_22 said:
Can anyone talk me through the steps to set this up?
Click to expand...
Click to collapse
You can download the Activity-Launcher app (as Rivendel noted) and open it. Scroll down to 'Settings'. This opens a loooooong list. Scroll waaaaay down to 'Torch Light' (there are two IIRC), and press it. The settings screen is shown. Sett the settings and 'back' to get out.
jeromepearce said:
You can download the Activity-Launcher app (as Rivendel noted) and open it. Scroll down to 'Settings'. This opens a loooooong list. Scroll waaaaay down to 'Torch Light' (there are two IIRC), and press it. The settings screen is shown. Sett the settings and 'back' to get out.
Click to expand...
Click to collapse
This is amazing! I missed this from my old rooted s3 and now no root required thanks alot!
Sent from my SM-N900P using Tapatalk 2
Is this working reliably for some people? For me it's not unfortunately. It usually works after I have just turned off the device, but when it's been idling for a while then I can't activate the flashlight this way. Bummer.
Torchlight
Since I upgraded to SM-N9005][NOTE3][KitKat 4.4.2][XXUENA6]_BoBCaTROM_EVO_v4.1 it does not work. Probably it is a bug and hopefully soon will be fixed. The corresponding setting appear in WanamXposed but does not work. Does anyone perhaps has a fix for it?
Hugmebear said:
Since I upgraded to SM-N9005][NOTE3][KitKat 4.4.2][XXUENA6]_BoBCaTROM_EVO_v4.1 it does not work. Probably it is a bug and hopefully soon will be fixed. The corresponding setting appear in WanamXposed but does not work. Does anyone perhaps has a fix for it?
Click to expand...
Click to collapse
What do you mean by "does not work"? The setting page does no longer show up?
Since on the actual "working" of the torchlight things are already complex on 4.3 - the torchlight only works if the CPU is not in deep sleep! (this however probably explains why that setting is hidded).
I am still using that torchlight with a trick - since only the Power and Home buttons can wake the CPU from seep sleep I press on Power twice SLOW, and only after that I press and hold Volume Up - that way I still get to start the torchlight with a single hand :good:
[hidden setting] flashlight settings
I mean that thoug setting page show up, switch on, but no results. I long-press volume-up and there is no torchlight. I reached the settings in WanamXposed [hidden setting] flashlight settings but no result. I use 4.4.2 Kitkat. Probably it is no linger supported in Kitkat.
xclub_101 said:
What do you mean by "does not work"? The setting page does no longer show up?
Since on the actual "working" of the torchlight things are already complex on 4.3 - the torchlight only works if the CPU is not in deep sleep! (this however probably explains why that setting is hidded).
I am still using that torchlight with a trick - since only the Power and Home buttons can wake the CPU from seep sleep I press on Power twice SLOW, and only after that I press and hold Volume Up - that way I still get to start the torchlight with a single hand :good:
Click to expand...
Click to collapse
I just added a widget through widget locker, which I can interact with. Works great, power button > tap widget :good:
Using an app called Torchie, just press both 'volume buttons' together to turn on/off torch anytime. It runs as a background service and just works anytime, even when screen off (if enabled from Torchie Settings). It kinda make your phone feel like a conventional battery operated torch.
https://play.google.com/store/apps/details?id=in.blogspot.anselmbros.torchie
XDA Thread here: http://forum.xda-developers.com/android/apps-games/app-torchie-torch-volume-buttons-anytime-t3270230
has anyone found a way to keep Tasker alive on resume.. when restating it starts ok, but when it resumes tasker is not resumed automatically..
Nomader0 said:
has anyone found a way to keep Tasker alive on resume.. when restating it starts ok, but when it resumes tasker is not resumed automatically..
Click to expand...
Click to collapse
What kind of hu?
Thanks an MTCD of course
I managed to whitelist it along other apps using MTC Manager xposed module on Malayks ROM. It is kept alive and kicking on sleep..
Nomader0 said:
Thanks an MTCD of course
I managed to whitelist it along other apps using MTC Manager xposed module on Malayks ROM. It is kept alive and kicking on sleep..
Click to expand...
Click to collapse
Hi.
Same problem here - could you write down the steps you made so i can give it a try?
Thanks
there is a whitelist.ini file (that is of you coppied the MTC Manager files like Malaysk says to do) inside you can just write down the tasker process (net.dinglisch.android.taskerm). it will be kept alive during sleep
while you are there also add poweramp process (com.maxmpz.audioplayer) (that is if you are using poweramp)
that will make poweramp resume playing automatically when resuming from sleep.
anyone know how to do this without xposed? PX5 units doesn't have xposed support yet.
I haven't found a way. I've been through every APK in /system looking for the task killer, no luck at all
Sent from my 2PS64
Hi,
I don't have a fix, but a short-cut. I've set a homescreen widget to launch a Tasker Task (which can just be a pop-up saying "Tasker is now running"), that way when I start up the unit it's one tap on the homescreen, Tasker loads, runs the task, and then remains in the background. This does save you opening the Tasker app and then backing out again.
This initial task can also be used to load up other items you'd rather have running all the time (I'm using Twilight and GMD Immersive) - if you do this it's worth putting in a slight delay between each (I've gone for 500 MS) and then launching the Home app as the last item to put you back where you were.
Ideally I'd want Tasker resuming after sleep, but until that's an option "one tap and it's there" will have to do.
So whenever I make a call with my s3 watch, my phone unlocks in my pocket and then stays unlocked, with the bright screen shining out of my pocket (and vulnerable to accidental key presses), until the lock timer kicks in.
Is there a way to make the phone stay locked if I'm using just the watch to make a call?
kurnis said:
Is there a way to make the phone stay locked if I'm using just the watch to make a call?
Click to expand...
Click to collapse
Genius! I don't know why I didn't think to include such functionality in my Tasker Project.
To achieve what you are looking to do, make a Tasker profile using the Phone Offhook + Proximity Sensor contexts, then, from there, choose one of the three following options for the task:
Run Code>Shell with the command "input keyevent 26" (requires root)
Run Display>System Lock (requires using pin code on next unlock)
Temporarily set screen timeout to 7 seconds, then set it back
MehStrongBadMeh said:
Genius! I don't know why I didn't think to include such functionality in my Tasker Project.
To achieve what you are looking to do, make a Tasker profile using the Phone Offhook + Proximity Sensor contexts, then, from there, choose one of the three following options for the task:
Run Code>Shell with the command "input keyevent 26" (requires root)
Run Display>System Lock (requires using pin code on next unlock)
Temporarily set screen timeout to 7 seconds, then set it back
Click to expand...
Click to collapse
Thanks for the tip! unfortunately I have an s8+ and it isn't rooted yet. Hopefully I can find a way to do it without root in the meantime.
kurnis said:
Thanks for the tip! unfortunately I have an s8+ and it isn't rooted yet. Hopefully I can find a way to do it without root in the meantime.
Click to expand...
Click to collapse
That is why I listed two options that don't require root.
MehStrongBadMeh said:
That is why I listed two options that don't require root.
Click to expand...
Click to collapse
oh my bad. thought they were 123 instructions on using the Tasker. I'll give it a shot, thank you!
Fingerprint Swipe (left,right,up for Back, Home, Recents/Sleep)
The third party custom fingerprint apps were not working after Pie update, which was so useful since this is a huge phone, so made a custom module inspired by rori's module.
UPDATE
Couldn't update for a long time since I moved to OP7T.
Anyway got some free time in lockdown, so here we go
Fingerprint_swipe v3 Magisk20+ Changelog
Support for Magisk 20+ (Tested on Magisk 20.4)
Uses Latest MMT-Ex from Zackptg5
Works on OOS10 Open Beta
INSTALLATION : Remove other old Modules and flash this in Magisk (Should work on OOS and Custom ROMs)
What it does?
Swipe left for BACK/Close notification
Swipe right for HOME
Swipe up for RECENTS
Swipe up twice for switching to LAST APP
Swipe down UNTOUCHED (Default notifications swipe)
Download Fingerprint_swipe v3 https://androidfilehost.com/?fid=4349826312261774266
ALT version - Incase home gesture doesn't work with the above normal version in OOS, ALT version uses Swipe right for Sleep instead of home. Later I'll try to figure if Oneplus has overrided HOME because other gesture navigation. (Home gesture reportedly work again on OOS10 Beta, so you can use first version)
Download Fingerprint_swipe v3 ALT https://androidfilehost.com/?fid=4349826312261774265
User Requested Variants like Swipe to Answer Call, Brightness in Post#3
Buy me a coffee if I had helped you!
__OLD__
____________________________________________________________________________
Fingerprint Swipe (left,right,up for Back, Home, Recents/Sleep)
The third party custom fingerprint apps were not working after Pie update, which was so useful since this is a huge phone, so made a custom module inspired by rori's module.
What it does?
Swipe left for BACK/Close notification
Swipe right for HOME
Swipe up for RECENTS
Swipe up twice for switching to LAST APP
Swipe down UNTOUCHED (Default notifications swipe)
Alternate Version :
Swipe UP to Sleep/Lock instead of Recents
Tested on OP5T PIE Open Beta 20 to 28/stable 9.x Magisk v17.3/ v18/v19
*Uninstall/disable module before system update and reinstall / enable after updating system.
Works in most Custom ROMs like Pixel experience, test and report.
( Edit : Not working in OP6, it reportedly uses a different FP sensor and it do not recognise swipe at all
Edit 2: OP5T only)
If anyone need any specific custom actions I can make in free time.
User Requested variants attached in POST 3
Click to expand...
Click to collapse
thank you for the module, can you guide us how to customise the gestures?
Sent from my OnePlus5T using XDA Labs
Fingerprint_swipev3 Magisk20+ ALT Call EndCall
Swipe right to answer call directly (Opens phone app when there is no call)
Swipe left to end call directly (Sleep device when there is no call)
Fingerprint_swipev3 Magisk20+ ALT Call
Swipe right to answer call directly (Opens phone app when there is no call)
No end Call option to avoid accidental call ends
DOWNLOAD HERE
Buy me a coffee if I had helped you!
_OLD_
Goutham Ganesh said:
thank you for the module, can you guide us how to customise the gestures?
Sent from my OnePlus5T using XDA Labs
Click to expand...
Click to collapse
You can't customize on the go. You can unzip the module zip and alter the key layout file to customise the swipe gesture values to the required one if you know the particular key value for that action.
For example, Key value for RECENTS menu = APP_SWITCH
Make sure you don't change the power button values.
__________________________________________________________
User Requested variants attached below - Remove my other swipe module and install this.
vA - Swipe UP to sleep (remaining untouched ie, Down for Notification)
vB - Swipe LEFT to LOWER BRIGHTNESS, Swipe RIGHT to INCREASE BRIGHTNESS (UP and DOWN untouched, ie, Notification open and close)
Instructions - READ first post
Click to expand...
Click to collapse
Working great, thanks for such an awesome module it is very useful. :good:
Aswin08 said:
Fingerprint Swipe (left,right,up for Back, Home, Recents)
The third party custom fingerprint apps were not working after Pie update, which was so useful since this is a huge phone, so made a custom module inspired by rori's module.
What it does?
Swipe left for BACK/Close notification
Swipe right for HOME
Swipe up for RECENTS
Swipe up twice for switching to LAST APP
Swipe down UNTOUCHED (Default notifications swipe)
Tested on OP5T PIE Open Beta 20 Magisk v18
(May work on op6, if not report. )
If anyone need any specific custom actions I can make in free time.
Click to expand...
Click to collapse
Thanks for the module man. Never really got into fingerprint gestures before but how you've done it I really like as it's very functional and convenient. Have already recommended this to some people who also seem to enjoy it. Thank you:good:
DEVILOPS 007 said:
Thanks for the module man. Never really got into fingerprint gestures before but how you've done it I really like as it's very functional and convenient. Have already recommended this to some people who also seem to enjoy it. Thank you:good:
Click to expand...
Click to collapse
Welcome.
True, this is so convenient since I started using it from nexus 6p days. One of the useful addition in Oreo.
Wow that's awesome ! Even apps on play store can't do that :good:
Aswin08 said:
Fingerprint Swipe (left,right,up for Back, Home, Recents)
The third party custom fingerprint apps were not working after Pie update, which was so useful since this is a huge phone, so made a custom module inspired by rori's module.
What it does?
Swipe left for BACK/Close notification
Swipe up for RECENTS
Swipe down UNTOUCHED (Default notifications swipe)
Tested on OP5T PIE Open Beta 20 Magisk v18
(May work on op6, if not report. )
If anyone need any specific custom actions I can make in free time.
Click to expand...
Click to collapse
Looking forward to trying this out. Thank You!
Aswin08 said:
You can't customize on the go. You can unzip the module zip and alter the key layout file to customise the swipe gesture values to the required one if you know the particular key value for that action.
For example, Key value for RECENTS menu = APP_SWITCH
Make sure you don't change the power button values.
Click to expand...
Click to collapse
I unzipped the file and I found where to configure the values, but there are 8 of them. I know "Up,Down,Left,Right" but what are the other four? Also how do you know which is which. I mean which one represents Up, represents Down, represents Left....
Please forgive me if this is obvious I'm new to this process.
Works flawlessly on ob21 | op5t
Many thanks OP for this ! Works flawlessly.
Great mod and I have you rep on the other thread!
So when I'm on the home screen and finger down it shows quick settings, but when I finger up to minimize quick settings it automatically shows recents. I know that that's how you designed it but would it be possible to make it so that it closes the quick settings back first and back to home screen? Then I can finger up again to show recents. I hope my explanation isn't confusing.
Thanks
kanekz said:
Great mod and I have you rep on the other thread!
So when I'm on the home screen and finger down it shows quick settings, but when I finger up to minimize quick settings it automatically shows recents. I know that that's how you designed it but would it be possible to make it so that it closes the quick settings back first and back to home screen? Then I can finger up again to show recents. I hope my explanation isn't confusing.
Thanks
Click to expand...
Click to collapse
As you can see in the op post, when you want to close the quick settings use swipe left (Back) or swipe right (Home). Else I can only make a separate module with swipe up making notification close and recents action removed.
And coming to the complex action you have request where a same gesture works differently based on the current situation, its not possible in the file I modified. I need to look into other files to understand how things work.
Eazii said:
Looking forward to trying this out. Thank You!
I unzipped the file and I found where to configure the values, but there are 8 of them. I know "Up,Down,Left,Right" but what are the other four? Also how do you know which is which. I mean which one represents Up, represents Down, represents Left....
Please forgive me if this is obvious I'm new to this process.
Click to expand...
Click to collapse
In the order
up
Left
Right
Down
Other values may represent something else, maybe like long pressing in camera clicks pics, long press from locked device open payment service. But am not sure yet.
Aswin08 said:
In the order
up
Left
Right
Down
Other values may represent something else, maybe like long pressing in camera clicks pics, long press from locked device open payment service. But am not sure yet.
Click to expand...
Click to collapse
One more question if I may. You mention to "make sure not to change the power button values" but why and also what does the"power button value" do?
Eazii said:
One more question if I may. You mention to "make sure not to change the power button values" but why and also what does the"power button value" do?
Click to expand...
Click to collapse
Again I am not sure but it maybe the value of power button, so changing it may cause issues.
Aswin08 said:
Again I am not sure but it maybe the value of power button, so changing it may cause issues.
Click to expand...
Click to collapse
Bet! Thank you for taking time out your day to answer my questions
Guess I'm the first to test on Oneplus 6 (9.0.2 stable). Unfortunately no luck here but thanks all the same. Willing to help test if you have any ideas
Can confirm doesn't work on OP6 OOS 9.0.2 Magisk v18
I would donate 100$ if you could make this work on 6T
Not working on op6
PhoenixTank said:
Guess I'm the first to test on Oneplus 6 (9.0.2 stable). Unfortunately no luck here but thanks all the same. Willing to help test if you have any ideas
Click to expand...
Click to collapse
pankspoo said:
Not working on op6
Click to expand...
Click to collapse
jnss98b said:
Can confirm doesn't work on OP6 OOS 9.0.2 Magisk v18
Click to expand...
Click to collapse
Please remove the module, restart and attach the following file.
System/usr/keylayout/gf_input.kl
I'll try to see what went wrong in op6.
Hello,
I'm curious I can get some help. I have an android box that hooks up to my TV. I have an app I use called "Key Mapper" that allows me to remap my keyboard keys so I can create shortcuts. One of the issues I find with the app is that sometimes I have to exit out of it and reopen it and re-enable accessibility within the App.
In Android Settings I already have accessibility enabled so it should be good, but when I reboot the device it seems to always stop working until I close out of the process and re-open it up.
My theory is that maybe I need to delay the auto boot of the application. It starts up with Android automatically but if I can have it delayed start that may resolve the issue. Is there an app or some way I can adjust the auto boo setting to delay it say 10 seconds after Android loads up?
m0d hipp¥ said:
Hello,
I'm curious I can get some help. I have an android box that hooks up to my TV. I have an app I use called "Key Mapper" that allows me to remap my keyboard keys so I can create shortcuts. One of the issues I find with the app is that sometimes I have to exit out of it and reopen it and re-enable accessibility within the App.
In Android Settings I already have accessibility enabled so it should be good, but when I reboot the device it seems to always stop working until I close out of the process and re-open it up.
My theory is that maybe I need to delay the auto boot of the application. It starts up with Android automatically but if I can have it delayed start that may resolve the issue. Is there an app or some way I can adjust the auto boo setting to delay it say 10 seconds after Android loads up?
Click to expand...
Click to collapse
After your OS finishes booting and loads the full OS stack, a system-wide message called Broadcast Intent will be sent to all apps, notifying them that your device has completed booting (this intent is called BOOT_COMPLETED). Then it's up to the individual app to use that broadcasted intent to pre-load in memory whatever they want (or simply not react at all).
The thing is you want to delay auto boot for that specific application, so there are 2 options for that:
you turn off auto boot in the App itself (if it provides such an option).
you block the app from receiving the intent broadcasted.
The second option is also achieved either by using a task killer to force kill the app (which defeats your point IMO) or it manipulate the app from receiving the intent entirely. Both of these options require root access.
If you have root I suggest The App: SD maid (pro version). Under app control you can modify which system Broadcasts that Keymapper recieves (among them could be boot_completed). See attached screenshot from my device for example.
Hope I helped somehow
Thank you for your response. That was super helpful! The device I am playing around with is a Mekotronics R58x, and it had some sort of modified root that was conflicting with Magisk. I read somewhere on these forums that someone suggested renaming the su file if it exists in /system/xbin/su; which it did. I renamed it and rebooted and after that everything worked wonderfully. Keymapper was still autobooting like previously, but this time all the services loaded right up and I didn't have to restart the app it just worked.
Basically I think the issue was this custom su file that was conflicting with Magisk and causing a headache with the keymapper. I'm glad I stumbled across the fix, but either way your post was also very helpful! Thank you!