Related
as a user of power strip, i was extremely frustrated when i realized that the native double-tap function overrides whatever you set power strip to. coming from a droid 1 and cyanogenmod, i knew that there must be a way to take this function over.
after doing a lot of searching i came across this:
http://forum.androidcentral.com/motorola-droid-x/33482-disabling-customizing-double-tap-home.html#post349645
in that post zlandau mentions to edit a line in a database table in /data/data/com.motorola.android.providers.settings/databases/settings.db
line 352 has a value of 'double_tap'.
zlandau mentions to change that value to "<program>/<activity>"
assuming that this method will work for what i want to do [restore double tap to power strip], i'm not sure how to call the app properly.
if someone's able to help me out with this i'm pretty sure it will benefit everyone, as it will finally provide a means to disable/customize the function.
[btw i posted this over at droidforums, but figured i'd throw it up here for a quicker response]
also, once this is figured out, maybe someone could make an app to modify this and throw it on the market. i'm sure it would help a lot of people out. droid 2 and X users alike
after messing around i figured it out, with the help of launcher pro activities.
i didn't realize that the table extended to the right and when i saw the action that was set through the system i realized what i was missing.
i was looking for this
'mobi.intuitit.android.p.powerstrip/mobi.intuitit.android.p.powerstrip.PowerStrip'
however, if i set launcher pro as my default launcher and change the doubletap action to power strip, when i double tap it goes home then launches power strip.
i'm going to try just removing the value all together.
I like where this is headed!
Sent from my DROID2 using XDA App
ecnahc said:
after messing around i figured it out, with the help of launcher pro activities.
i didn't realize that the table extended to the right and when i saw the action that was set through the system i realized what i was missing.
i was looking for this
'mobi.intuitit.android.p.powerstrip/mobi.intuitit.android.p.powerstrip.PowerStrip'
however, if i set launcher pro as my default launcher and change the doubletap action to power strip, when i double tap it goes home then launches power strip.
i'm going to try just removing the value all together.
Click to expand...
Click to collapse
Just set the home key settings to do nothing in launcherpro
MotoBoy said:
Just set the home key settings to do nothing in launcherpro
Click to expand...
Click to collapse
yea that's what i already had it set to.
i guess getting power strip to work properly is another story..
but the instructions i posted above do accomplish setting the double home tap to whateve you want
ecnahc said:
yea that's what i already had it set to.
i guess getting power strip to work properly is another story..
but the instructions i posted above do accomplish setting the double home tap to whateve you want
Click to expand...
Click to collapse
That was a good find. I am thinking of what I want my home double tap to be
The problem is that it still takes you home before launching power strip, when it would be best to have it just launch power strip in the current program you are in... I ran into the same problem with quick desk. I settled on using smart taskbar instead because it can be launched by a swipe action, floating icon, or the notification area. And it launches over your current app window. The developer is very responsive to suggestions as well.
Sent from my DROID2 using Tapatalk
activity name?
I would like the double tap to launch google voice
how do I figure out what the name of the startup activity is?
I know the app is com.google.android.apps.googlevoice and I've guessed some generic activity names like com.google.android.apps.googlevoice.GoogleVoice but no luck so far
you can change the double tap home key by going into settings then applications then it will be the last option. not sure on the camera button
Hi
Thanks to the forum, I have rooted my Nook touch. I can access my emails and the market. But nothing is protected.
Is it a way to add a password to the Nook? or how can I set up the apps so they asked for a password.
Thanks
Secure your hacked Nook
There seems no solution to this at this moment but there are some workaround security mitigations.
1. Do not connect public Wifi to use your Nook. Use your own private Wifi and turn on AP isolation (i.e. Wifi clients on the same WLAN are isolated)
2. Install on Nook adbWireless and control adb ON/OFF over wireless
hxxp:// www .appbrain .com /app /adbwireless-(widget-version)/siir.es.adbWireless
SC Leung
Securing after TouchNooter 1.6.24
Would reverting to the original uRamdisk of the stock Nook touch make it secure?... i know it would make adb over wifi unavailable but if that is fine with me...
Somewhere on the forum is attached ramdisk that should enable adb over usb. The topic is something like "adb over usb"..
If you wish to lock single apps, I have had great luck with Protector. You can define any apps you want to be locked and when you try to open these apps, they ask for a password.
https://market.android.com/details?id=com.androidpassword.core&feature=search_result
I have not tried it on the new Nook myself but give it a try.
Lock
Use GoLocker
Go locker does really add number lock (iphone style) or connect-the-dots lock (android style) but they tend to leave a shadow on the screen, which was bothersome enough for me to stop using, and the number lock would show the number before becoming a *, so someone could look over your shoulder and pick it up...
Almost good! But the best choice so far for entire NST locking so far!
GO Locker: so far, little luck
Downloaded Go Locker.
It detected an outdated Go Launcher; I approved the download.
Enabled Go Locker and specified a PIN.
Cycled power on the Nook.
Behavior change: I can select among Go Launcher, Go Locker and Home when I press the Home soft button on the right of the screen. Makes sense.
But no request for a PIN.
Perhaps I missed one or more configurations steps?
Any suggestions?
Best regards,
drjekyll said:
Downloaded Go Locker.
It detected an outdated Go Launcher; I approved the download.
Enabled Go Locker and specified a PIN.
Cycled power on the Nook.
Behavior change: I can select among Go Launcher, Go Locker and Home when I press the Home soft button on the right of the screen. Makes sense.
But no request for a PIN.
Perhaps I missed one or more configurations steps?
Any suggestions?
Best regards,
Click to expand...
Click to collapse
You need to set GO Locker as the default so you can't just press home to bypass the lock, and when you reboot it doesn't start immediately unfortunately. But next time you lock the screen it should be there.
Thanks. I set the Go Locker as the default, but I did not see the locking work after reboot, nor how to lock the screen manually.
But my main concern is that approximately 40% of the screen was going grey, making icons and text in that area unusable.
So I removed Go Locker for now.
Is documentation available somewhere? With a quick check of the developer site I did not see enough.
Hi
Excuse me for my bad English writing.
......
I active internal android pass code on may NST. but I can't remove it !!!
however i like it .
for do it you need install ADW louncher . but you don't need any additional program and after uninstalling this launcher , pass code still exist .
in " ADW launcher desktop " do this steps :
Menu > Add > Custom Shortcut > Pick your activity > Activities >
next find "Settings" and collapse it . ( it is your android settings )
next find " Passcode(.ChooseLockPin) " > OK
Click on Shortcut you create ........ WOW !
select passcode.
remember you can't back to previous state !!!
if anyone could remove passcode please notify me .
hshsh said:
Hi
Excuse me for my bad English writing.
......
I active internal android pass code on may NST. but I can't remove it !!!
however i like it .
for do it you need install ADW louncher . but you don't need any additional program and after uninstalling this launcher , pass code still exist .
in " ADW launcher desktop " do this steps :
Menu > Add > Custom Shortcut > Pick your activity > Activities >
next find "Settings" and collapse it . ( it is your android settings )
next find " Passcode(.ChooseLockPin) " > OK
Click on Shortcut you create ........ WOW !
select passcode.
remember you can't back to previous state !!!
if anyone could remove passcode please notify me .
Click to expand...
Click to collapse
Solution by Gabrial http://forum.xda-developers.com/showpost.php?p=22110415&postcount=5
ok.
I edit my post too:
Solution by Gabrial : http://forum.xda-developers.com/showpost.php?p=22110415&postcount=5
Hi everybody. I'm not sure if this is the right forum for asking this.
I'm developing an app that behaves like a kiosk mode, so I have a variable that indicates if I'm on kiosk mode or "normal mode". I have an Activity registered as category.HOME, which manages what should the app do, depending on the "kiosk mode" variable.
Manifest sample:
Code:
<activity
android:name="com.stuff.kiosklauncher.MainActivity"
android:exported="false"
android:label="@string/app_name"
android:launchMode="singleInstance"
android:stateNotNeeded="true" >
<!-- This tag indicates the initial activity -->
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.HOME" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
If I press the Home button on my Android phone, my MainActivity is called, and there if we are in kiosk mode, I do nothing, but if I I have the kiosk mode set to off, I look for the preferred launcher (stored in a variable called defaultlauncher), and call it at the onResume() with:
Code:
if(!kioskMode){
Intent startApp = new Intent();
ComponentName component = new ComponentName(
defaultLauncher.getPackageName(),
defaultLauncher.getClassName());
startApp.setComponent(component);
startApp.addCategory(Intent.CATEGORY_HOME);
startApp.setAction(Intent.ACTION_MAIN);
startActivity(startApp);
}
Seems to work ok, but it has some issues, as the "standard" launcher doesn't behave as it should (it doesn't scroll back to the main page when I'm on the desktop, for example... or flicks a little like trying to load my app's layout when pressing continuously the home button). So I'm not sure if I'm doing this right, maybe an Activity shouldn't be the place to lad or not the launcher, but I don't know if I can make a service or a broadcast receiver to be called when the home button is pressed.
I've seen a lot of apps that behave this way (like a launcher on top of another one), but I don't know how they do it.
Again, sorry if this is not the place to seek this kind of help, if that's the case, I'd love to know where should I go. If this is the place, please help. Thanks!
I think that you will not be able to start a service or broadcast receiver.
One idea (I do not know whether it works): Try overriding the onKeyDown and onKeyUp methods for the home button and return true.
Look at this: http://stackoverflow.com/questions/2079691/overriding-the-home-button-how-do-i-get-rid-of-the-choice (especially the second answer)
Thanks, I'll take a look to that!
I had made a kiosk browser app, and it worked perfectly.
My trick was using <activity-alias> tag, as well as some notifications to user mention that, they must select the app as default home launcher if they were in "kiosk" mode.
Moon.lSd said:
I had made a kiosk browser app, and it worked perfectly.
My trick was using <activity-alias> tag, as well as some notifications to user mention that, they must select the app as default home launcher if they were in "kiosk" mode.
Click to expand...
Click to collapse
In your kiosk mode, you had some way to "exit" from it without forcing the user to change the launcher? This would be exactly what I'm trying to achieve, could you provide a little more info? I'm not sure how I could use <activity-alias> here :/
Thanks
pnikosis said:
In your kiosk mode, you had some way to "exit" from it without forcing the user to change the launcher? This would be exactly what I'm trying to achieve, could you provide a little more info? I'm not sure how I could use <activity-alias> here :/
Thanks
Click to expand...
Click to collapse
Well, you can't change an activity intent filter, so you are unable to make a activity from launcher to non-launcher.
But if you are using activity-alias instead of activity, you can disable or enable intent filter of that alias, and thus, by using a shortcut key (like press back 5 times continously), you can exit kiosk mode, disable filter of the alias and default launcher will be automatically called without ask user to do that.
FYI: <activitiy-alias> is a tag in AndroidManifest, just like <activity>, but if <activity> points to a real Activity class, <activity-alias> point to another <activity> tag.
Moon.lSd said:
Well, you can't change an activity intent filter, so you are unable to make a activity from launcher to non-launcher.
But if you are using activity-alias instead of activity, you can disable or enable intent filter of that alias, and thus, by using a shortcut key (like press back 5 times continously), you can exit kiosk mode, disable filter of the alias and default launcher will be automatically called without ask user to do that.
FYI: <activitiy-alias> is a tag in AndroidManifest, just like <activity>, but if <activity> points to a real Activity class, <activity-alias> point to another <activity> tag.
Click to expand...
Click to collapse
Thanks! I'll take a look to that solution, I think I'm getting the idea.
what you can do is get the default launcher as soon as installing the app and store it locally then when the user fires your launcher activity just do what you want to and fire up the home intent directed to the package of previous default launcher this should do it .
If you are doing some heavy duty work then launch a service from the activity and dump your work there this i guess should do it
sak-venom1997 said:
what you can do is get the default launcher as soon as installing the app and store it locally then when the user fires your launcher activity just do what you want to and fire up the home intent directed to the package of previous default launcher this should do it .
If you are doing some heavy duty work then launch a service from the activity and dump your work there this i guess should do it
Click to expand...
Click to collapse
Thanks!
A quick question though, what do you mean by dumping the work in a service? I don't understand completely why and how should I do that.
My first approach was indeed, once I launch my app look for the current default launcher. I even added an option in my app in case the user wants to change the "regular" launcher (looking for the installed packages with the ACTIVITY_HOME filter). The problem is, when I call the intent to the previous launcher, it works ok but not completely. For example, if I'm on the "regular" desktop and I call the home button, it should display the desktop thumbails, or go back to the default desktop, but instead of that, it does nothing (a quick flicker sometimes, I guess because its calling again the activity).
pnikosis said:
Thanks!
A quick question though, what do you mean by dumping the work in a service? I don't understand completely why and how should I do that.
My first approach was indeed, once I launch my app look for the current default launcher. I even added an option in my app in case the user wants to change the "regular" launcher (looking for the installed packages with the ACTIVITY_HOME filter). The problem is, when I call the intent to the previous launcher, it works ok but not completely. For example, if I'm on the "regular" desktop and I call the home button, it should display the desktop thumbails, or go back to the default desktop, but instead of that, it does nothing (a quick flicker sometimes, I guess because its calling again the activity).
Click to expand...
Click to collapse
Working in activities is not proffered as it causes lag on low activity devices
Flickr is probably due the reason you gave that it's being called again and again from the activity
Sent from my GT-S5302 using Tapatalk 2
Hit Thanx Button if i helped you!
sak-venom1997 said:
Working in activities is not proffered as it causes lag on low activity devices
Flickr is probably due the reason you gave that it's being called again and again from the activity
Sent from my GT-S5302 using Tapatalk 2
Hit Thanx Button if i helped you!
Click to expand...
Click to collapse
I see. I think I have an idea on how I can approach this. Thank you all guys, lots of great ideas, you helped me a lot. Sorry I can hit the thanks button only once per message
Hi,
I have a small problem..
In my app I have activity A and activity B. A is the main activity..
when working in normal state, A is opened, I can call B and return to A and everything is OK.
Also I have a widget that all it does is to call activity B or to finish activity B.
my problem is that if A is running at the background and I pressed the widget to call B and then, again to turn off B
A is suddenly appears on screen..
I'm trying to turn off A when B is turned off from the widget (using intent) without a success
when A resumed is getting a whole different intent from what I've sent..
can anyone please help..???
Hi I just got a Nexus 6p and its been great but I have low vision and if I keep the option turned on the phone, it becomes very laggy so I would like to only use it when I need to.
Help would be greatly appreciated!
Thank you .
This isn't exactly what you wanted, but it's kind of close...
I use ADW as my launcher, which allows me to set custom shortcuts on my home screen. Other launchers might offer the same functionality.
I long pressed on my home screen and selected the Add tab on the popup. I then tapped Custom Shortcut, and tapped "Pick your activity." Next, I tapped Activities, scrolled down to Settings and expanded the list. It's rather long, but in that list there is one called "Accessibility(.Settings$AccessibilitySettingsActivity)". I selected that one, gave it a name (what it displays under the icon), and pressed OK. This created a settings gear icon on my home screen that when tapped goes straight to the accessibility options in the settings menu, and then you can tap the toggle for Magnification.
Alternatively, you should be able to do the same thing with Tasker if you have it installed and it's a bit easier. Make a new Task, give it a title (anything) and press the plus to add a step. Select Settings, then Accessibility settings (first option). There is some "if" options, but you can just tap your back button to go back to the step list. Create a widget for Tasker (1x1 task) and select the name of the task you just created. You then need to select an icon for the "widget" by tapping the icon in the lower right that looks like 9 squares in a grid. There are a bunch of built in icons you can choose from, or use your own. The result will be an icon on your desktop that goes to the accessibility options screen, allowing you to quickly toggle the magnification gesture.
Again, sorry this isn't exactly what you asked for, but it would save some taps. Luckily the mag gesture toggle is high enough in the list of options that it should always be on the screen when you open the accessibility settings, so you won't need to scroll.
Lastly, if you are rooted, you could use Tasker to also hit the toggle for you. If you want instructions for that, please do let me know and I'd be happy to share how to do that. It would allow you to tap the "widget" and it would then launch the accessibility settings, wait a second and then tap the toggle, and go back to the home screen. That way you wouldn't need to toggle it yourself.
fury683 said:
This isn't exactly what you wanted, but it's kind of close...
I use ADW as my launcher, which allows me to set custom shortcuts on my home screen. Other launchers might offer the same functionality.
I long pressed on my home screen and selected the Add tab on the popup. I then tapped Custom Shortcut, and tapped "Pick your activity." Next, I tapped Activities, scrolled down to Settings and expanded the list. It's rather long, but in that list there is one called "Accessibility(.Settings$AccessibilitySettingsActivity)". I selected that one, gave it a name (what it displays under the icon), and pressed OK. This created a settings gear icon on my home screen that when tapped goes straight to the accessibility options in the settings menu, and then you can tap the toggle for Magnification.
Alternatively, you should be able to do the same thing with Tasker if you have it installed and it's a bit easier. Make a new Task, give it a title (anything) and press the plus to add a step. Select Settings, then Accessibility settings (first option). There is some "if" options, but you can just tap your back button to go back to the step list. Create a widget for Tasker (1x1 task) and select the name of the task you just created. You then need to select an icon for the "widget" by tapping the icon in the lower right that looks like 9 squares in a grid. There are a bunch of built in icons you can choose from, or use your own. The result will be an icon on your desktop that goes to the accessibility options screen, allowing you to quickly toggle the magnification gesture.
Again, sorry this isn't exactly what you asked for, but it would save some taps. Luckily the mag gesture toggle is high enough in the list of options that it should always be on the screen when you open the accessibility settings, so you won't need to scroll.
Lastly, if you are rooted, you could use Tasker to also hit the toggle for you. If you want instructions for that, please do let me know and I'd be happy to share how to do that. It would allow you to tap the "widget" and it would then launch the accessibility settings, wait a second and then tap the toggle, and go back to the home screen. That way you wouldn't need to toggle it yourself.
Click to expand...
Click to collapse
Thanks a lot!
So it sounds like theres no way to make a widget the will toggle it specifically, without rooting my device.
And if I do root it and use Tasker it will take almost the same time as if I didn't.
If thats no other way then I guess I should root it even though Id prefer not too.
Unless theres another way, Instructions would be great! Thanks again!
Are you familiar with Tasker? It's a paid app, but it's absolutely worth it and you'll find lots of uses for it. I use it to auto reply to text messages while I'm driving, mute my phone when I'm at work (calendar based) turn on wifi when I'm at home (location based), etc.
First thing you need to do is find the location of the toggle on the screen. Go to Developer Settings and turn on "Show Pointer Location". This will make a gray bar at the top of your screen that lists your X and Y coordinates at the top when you are touching the screen. Go to the accessibility settings and touch the toggle, taking note of what the X and Y coordinates are for that touch input.
To simulate touch input, can make a task that opens the accessibility settings as I described above, then add a "wait" command (Task > Wait), enter a value of 1 second. Next enter a command for Code and select Run Shell. Under the command, type "input tap x y" where x and y are the x and y coordinates that you found for the toggle. Make sure the "use root" box is checked. Lastly, add a Tasker command to go to the home screen (back to where you started with the "widget").
Back all the way out of Tasker to save that task, then go back in and press the play button at the bottom left side to test your setup. You should see it launch the accessibility settings, wait a second, toggle, and go home. The first time you run it you will need to grant Tasker root permissions, so be ready for that. If you're not quick to approve it, the task may proceed and go to your home screen before you press approve, so you might need to run it again a second time after you approve it.
If you need more help with, or have any questions, please do let me know. Happy to help.
fury683 said:
Are you familiar with Tasker? It's a paid app, but it's absolutely worth it and you'll find lots of uses for it. I use it to auto reply to text messages while I'm driving, mute my phone when I'm at work (calendar based) turn on wifi when I'm at home (location based), etc.
First thing you need to do is find the location of the toggle on the screen. Go to Developer Settings and turn on "Show Pointer Location". This will make a gray bar at the top of your screen that lists your X and Y coordinates at the top when you are touching the screen. Go to the accessibility settings and touch the toggle, taking note of what the X and Y coordinates are for that touch input.
To simulate touch input, can make a task that opens the accessibility settings as I described above, then add a "wait" command (Task > Wait), enter a value of 1 second. Next enter a command for Code and select Run Shell. Under the command, type "input tap x y" where x and y are the x and y coordinates that you found for the toggle. Make sure the "use root" box is checked. Lastly, add a Tasker command to go to the home screen (back to where you started with the "widget").
Back all the way out of Tasker to save that task, then go back in and press the play button at the bottom left side to test your setup. You should see it launch the accessibility settings, wait a second, toggle, and go home. The first time you run it you will need to grant Tasker root permissions, so be ready for that. If you're not quick to approve it, the task may proceed and go to your home screen before you press approve, so you might need to run it again a second time after you approve it.
If you need more help with, or have any questions, please do let me know. Happy to help.
Click to expand...
Click to collapse
I just realized I need to buy an adapter for that USB C lol.
Before I go ahead with all of this work, your completely sure there is no other way to toggle magnification without rooting?
Thanks!
drewtass said:
I just realized I need to buy an adapter for that USB C lol.
Before I go ahead with all of this work, your completely sure there is no other way to toggle magnification without rooting?
Thanks!
Click to expand...
Click to collapse
Sorry for the delay. I am not aware of any widgets. I couldn't find a widget on the Play Store or light Google searching.
Regarding the adapter, the 6p should have come with a short USB A to USB C cable specifically for connecting to a PC.
drewtass said:
Hi I just got a Nexus 6p and its been great but I have low vision and if I keep the option turned on the phone, it becomes very laggy so I would like to only use it when I need to.
Help would be greatly appreciated!
Thank you .
Click to expand...
Click to collapse
Have you used the built in magnification gesture? You turn it on in accessibility settings, then when you need something to be bigger, just tap the screen 3 times rapidly. You can use pinch to zoom to adjust the text size. When you're finished with it, tap the screen 3 times again. I use it when an app's text is just too small.
EMcTx said:
Have you used the built in magnification gesture? You turn it on in accessibility settings, then when you need something to be bigger, just tap the screen 3 times rapidly. You can use pinch to zoom to adjust the text size. When you're finished with it, tap the screen 3 times again. I use it when an app's text is just too small.
Click to expand...
Click to collapse
Haha Yes I have tried it you have to tap your finger 3 times to magnify which means every time you tap something once it waits to see if you will tap more times and cause slight lag.
Niceeee idea bro, i will try it
moqueet said:
Niceeee idea bro, i will try it
Click to expand...
Click to collapse
Are you saying you will try to make a widget like this?
fury683 said:
Sorry for the delay. I am not aware of any widgets. I couldn't find a widget on the Play Store or light Google searching.
Regarding the adapter, the 6p should have come with a short USB A to USB C cable specifically for connecting to a PC.
Click to expand...
Click to collapse
No problem!
Lol I was so excited for my new phone I never checked but I found it !
Thanks I will root it when I get the chance.
i have the same exact problem,i absolutely love the feature as i wouldn't be able to use any phone with out it but it also gets frustrating sometimes (the touch delay) for example in the dialer app or Instagram.
a toggle in the notification panel would be great or an app through which you specifically enable/disable the gestures for each individual app.
any other alternative would be appreciated, somebody posted the same issue here with a possible fix (which i am not exactly sure how to implement) https://code.google.com/p/android/issues/detail?id=39685
hassanabid94 said:
i have the same exact problem,i absolutely love the feature as i wouldn't be able to use any phone with out it but it also gets frustrating sometimes (the touch delay) for example in the dialer app or Instagram.
a toggle in the notification panel would be great or an app through which you specifically enable/disable the gestures for each individual app.
any other alternative would be appreciated, somebody posted the same issue here with a possible fix (which i am not exactly sure how to implement) https://code.google.com/p/android/issues/detail?id=39685
Click to expand...
Click to collapse
Nice to know I'm not the only one.
Sorry for the late reply been busy with school. It would be nice to have this option maybe like a button shortcut .
Hey guys so that way of using tasker is very slow and not feasible.
Is there any other way of making a quick toggle magnification gestures. It would be nice if I could hold the menu button to enable it. (IPhone tripple tap home button to toggle)
Thanks again.
I have low vision as well and have also found that leaving the magnification gesture turned on causes the phone to be laggy even when I don't actually have the magnification turned on. Instead of using that, I rooted my phone, changed the global DPI and I use App Settings (an Xposed module) to increase the font size in some apps or force the standard DPI in apps that have issues with the custom one.
There's a gestural workaround I've employed: if instead of just putting down my finger I drag my finger slightly (in any direction) then the lag almost disappears. Doing this helps a lot but obviously its a bit of an awkward gesture.
Al--g said:
There's a gestural workaround I've employed: if instead of just putting down my finger I drag my finger slightly (in any direction) then the lag almost disappears. Doing this helps a lot but obviously its a bit of an awkward gesture.
Click to expand...
Click to collapse
How did you set it up?
There's no set up. I just do that gesture to get the scrolling to stop when I have magnification enabled.
GuinnessX said:
How did you set it up?
Click to expand...
Click to collapse