-
ABOUT
ULTRA KEYBOARD has many features designed to give you a better Android keyboard experience.
Only $2.49 on Google Play! There is a free (48 hour) demo available.
https://play.google.com/store/apps/details?id=com.binarybulge.android.apps.keyboard.full
Look for us on AndroidPIT too, if you prefer (they accept PayPal!).
http://www.androidpit.com/en/android/market/apps/app/com.binarybulge.android.apps.keyboard.full
-
FEATURES
Choose your favorite way to type.
Touch-type like usual, or combine adjacent keys into COMPACT KEYS so they're easier to press. Slide your finger over words using WORD TRACING (instead of touching each individual letter).
The SUGGESTION BAR is smart and easy to use.
Choose words with just one swipe, even if they're not visible at first. A built-in English LANGUAGE DICTIONARY is included (and many other languages are available for download). Add new words to your personal CUSTOM DICTIONARY. BLACK LIST words you don't want to show up anymore.
Use WORD REPLACEMENTS to automatically expand abbreviations.
Tired of always typing "be right there"? Try "brt". You can even create your own.
The TOOL BAR provides a ton of functionality in a small amount of space.
You can scroll, drag, or flick through the available buttons.
Use SPEECH-TO-TEXT to transform your spoken words into text.
TRANSLATE your text to dozens of different languages.
CUT, COPY, and PASTE with a built-in CLIPBOARD.
Text you copy is saved so you can access it later. Remove anything you don't want to keep.
FULL-SCREEN MODE provides TEXT SELECTION HANDLES and a MAGNIFIER.
Accurately select portions of text to edit or copy.
The CHARACTER MAP makes more Unicode characters accessible.
Set up your own list of favorites for easy access. Includes Emoji on Android 4.1 devices.
Use the CAMERA OVERLAY* to see where you're going.
Watch what's in front of you while you type on the go. (* Android 2.3 or newer only.)
Create custom ACTIONS triggered by GESTURES or device buttons.
Want to swipe left to delete the previous word? Want your device's search button to activate the camera overlay? Do all this and more.
A DYNAMIC UI means you can customize the keyboard so it's perfect for you.
Are the keys too tall for your liking? Make them shorter. Don't like the ARROW KEYS? Hide them. Many things can be tweaked directly from the tool bar.
Change the keyboard's look with downloadable THEMES.
You can use the built-in THEME EDITOR to create your own themes, or customize existing themes with your chosen fonts and colors. You can even use themes designed for other keyboards!
-
CHANGE LOG
7.4.3 (1/31/2014)
Fixes:
Crashes involving the clipboard feature
Lag when updating the suggestion bar
Activity stack state issues when visiting settings/help from keyboard/tool bar
7.4.2 (1/30/2014)
Fixes:
Regression preventing lock screens from working
Problems with new word list interface
Clipboard tool wasn't honoring max entry setting
7.4 (1/29/2014)
Additions:
Customizable actions for long pressing modifier keys
Show the current dictionary on the space bar when multiple dictionaries are installed
A Done button in the full-screen editor
Improvements:
New interface for word lists (custom dictionary, replacements, clipboard entries, black list)
Made tool bar smoother and more predictable
The original suggestions are restored when undoing a selected traced word
Made it easier to cancel popup keyboards by dragging away from them
Only made certain dialogs transparent (the tool bar's Themes button for example)
Fixes:
Palette overlay in color picker didn't work
Character Map font color was wrong for light themes
The Done button didn't always dismiss the keyboard
Fixed crashes
7.3 (1/8/2014)
Additions:
"Character Map" feature (with Emoji for 4.1+ devices)
"Show Watermark" setting
Fixes:
Improved word tracing
Suggestion bar location was too low on 4.4 tablets
Couldn't always type in URL fields after tracing a word
Backspace didn't always work with selected text on 4.1+
Couldn't undo word corrections in some instances
Disabling "Typing->Capitalize Sentences" didn't work
Shift key wasn't always being updated after turning screen back on
Jumpy tool bar popup text
Fixed crashes on older versions of Android
7.2.1 (10/15/2013)
Suggestions:
Cursor position was sometimes incorrect when correcting existing words
Non-lowercase blacklisted words didn't persist
Typing:
Backspace deleted recently pasted text even after typing
Keys:
Previews could get stuck if keys were pressed as the keyboard was closing
Enter key long-press "take the default action" didn't work correctly
Tool Bar:
Position wasn't saved after a scroll
Emotes didn't show properly on certain versions of Android
Full-screen:
Cursor handles/magnifier could get stuck showing after leaving full-screen
Sentence capitalization didn't always work
Editor text didn't always get cleared when sending messages
Other:
Forced status bar to be shown when the keyboard is showing (avoids positioning issues)
Added direct app links to Facebook and Twitter profiles
7.2 (10/10/2013)
Suggestions:
Improved accuracy and speed (especially while tracing)
Undoing a suggestion sometimes mangled the text
Backspace deleted too many characters at times
Expanding the bar no longer steals focus from the current app
Typing:
Fixed capitals and symbols for shell/remote access apps
Prevented arrow keys from being triggered while typing
Improved popup key animations
Enter Key:
Fixed "Take the default action" behavior
Line break wasn't working on Android 4.3
Other:
Added "General->Show Automatically" setting
Worked around Android 4.3 clipboard crash
Popups (key previews, magnifiers, cursor handles) could get stuck on-screen
Tool bar item text size was too small for certain screen sizes
Increased heap size for extra-high-resolution screens
Crash fixes
7.1.1 (9/19/2013)
Fixes:
Enter key regressions (can't get past security/password lock; "Insert Line Break" broken)
Various crashes
7.1 (9/16/2013)
Additions:
Any selected text can be shifted
"Show/Hide Suggestions" action
Hidden characters on dedicated digit keys
Set default menu action to "none"
Theme names up to 32 characters
Updated key sounds
Fixes:
Editor button issues
Suggestions close when toggling full-screen mode
Compact popup keys close incorrectly
Compact alpha layout issues
Suggestion text size for small bar heights
Selected theme not migrated from demo
Inconsistencies in settings
7.0.1 (9/1/2013)
Fixes:
Issue deleting characters on Galaxy devices
Various crashes
7.0 (9/1/2013)
Additions:
Full-screen mode
New tracing animation
Physical key actions
Improved camera mode (with front-facing support)
New theme styles
Fixes:
Got rid of HUGE memory leak. Memory usage will be much lower now.
Many crash fixes.
LOTS MORE! Way too many to list here.
-
like this
good job I really like this app use it all the time
Hi, i have galaxy mini running stock 2.3.4 and market said its not compatible...why? and when i tried leaked version it was function but i cannot download language packs or skins...i really want to use it so ill buy it, but without support for my device...you know
i likeee...
Nice. I like this keyboard. It works really well. I tried the trial and purchased the full app today. Thanks OP.
Updated to v6.1.03.
· Added new built-in themes (Froyo, Gingerbread, Ice Cream Sandwich).
· Added new "Recent Apps" tool bar button.
· Added "Translate" option to dictionary button.
· Fixed performance issues.
· Enabled tracing (portrait) and disabled compact keys by default.
HI can you make it compatible with LDPI phones such as GALAXY MINI?Id like to use it on my phone...and does it support czech language ? if no dont bother with reply to compatibility issues
6.1.04:
· Fixed regressions (capitalization being ignored, full keyboard using compact suggestions).
Gnaver said:
HI can you make it compatible with LDPI phones such as GALAXY MINI?Id like to use it on my phone...and does it support czech language ? if no dont bother with reply to compatibility issues
Click to expand...
Click to collapse
I guess I was sort of hoping the LDPI phones have gone the way of the dinosaur. ;-) Was also thinking maybe Ultra is a little too heavy weight for lower-spec'd phones.
I'll definitely look into this. The medium DPI images should be scaled down on-the-fly on LDPI devices, but I think keeping Android 1.5 (Cupcake) support broke this.
I like to use forever !!!!! Link ?
Looks like a nice app
Updated to 6.1.06.
· Added an "Exit/Unload" option to the status bar menu.
· Fix: Word tracing crashes sometimes from native code.
· Fix: Certain black-listed words come back after restarts.
· Fix: Suggested words are incorrectly accepted when long-pressed.
· Fix: Suggested words stop working when editing a theme name.
· Fix: Suggested words stop showing at times, until the device is restarted.
· Fix: Clicking the status bar notification switches activities when the keyboard is open.
I linke!
Inviato dal mio Nexus S usando Tapatalk
Plz add option to change 'multi-tap interval' in t9
Sent from my GT-I9000 using Tapatalk
good, i will buy if there is russian language
Like this
Hi, got the Trial from the market...
Where can I change the Dictionary? Or is it disabled in the trial? I found Settings-Gestures-Dictionaries but it only offers me English.
And btw: can I migrate my old HTC personal Dictionary to the german one?
like this.
Updated to 6.2b.
· Increased performance and stability.
· Dictionary/tracing code completely rewritten.
· New theme features: can now stylize the suggestion bar.
· Almost too many fixes to count!
Table of Contents
Preface
Requirements
Difficulty
How it works!
Uses
Autorun
Demo, screenshots, TaskerNet & project backup
Tips
Why not those easy to use apps from PlayStore?
End note.
1. PrefaceBefore getting my hands on Pixel 6, I was using a Samsung Galaxy S8 running on an Android 10 custom ROM. Samsung provides an advanced, and very useful app called Good Lock, in which the "One Hand Operation +" feature helps us to set up upto freaking 36 number of swipe gesture shortcuts, from the left and right (top, center and bottom) sides of the screen, irrespective of which screen or app is currently active on the screen.
The only thing that I was sure about missing in Pixel 6 was this swipe gestures. That's why I did my research even before receiving my Pixel. Now I've successfully implemented a replica of the Samsung's swipe gesture into my Google Pixel.
These gestures makes it very easy to use this big and heavy smartphone.
This gesture setup made it easy for me to pull up my Control Panel created in Tasker, whenever I need, irrespective of which app or screen I'm in.
2. Requirements
Tasker
Tasker terms to understand (Only for those who are new to Tasker)
TASK : An action or set of actions which will be later run by Tasker by itself, when defined conditions are met. Can also be run manually via the Tasker app.
Examples: Launch an app, change ringer volume, toggle WiFI, disable auto rotation etc.
PROJECT : An individual Tasker set up, where we define the conditions to meet, and the tasks to be performed when the defined conditions are met.
Example 1: A profile which automatically enables the auto-rotation (task), when YouTube is opened (condition), and disables auto-rotation when you leave YouTube.
Example 2: A profile which automatically enables mobile data (task), when your device is connected to your car WiFi (condition) or Android Auto.
SCENE : A visible, or invisible shape which will be displayed on the screen, and can be configured to respond to a swipe, tap or long tap on it, and then accordingly perform a pre-defined task. A scene can only be enabled (show) and disabled (destroy) through a task or a project.
Example 1: A visible button that can be displayed on the screen, or an invisible location on the screen, which disables WiFi when we long tap on it.
Example 2: A visible button that can be displayed on the screen, or an invisible location on the screen, which opens recent apps list when we swipe on it.
"If" variables to be used in scenes for assigning shortcuts, to each combination of a swipe length and a swipe direction:
%stroke_len : Defines the length of the swipe in pixels.
%stroke_dir : Defines the direction of the swipe. (Read How It Works! section)
Actions that can be performed on a scene:
Tap: A single touch ON the scene.
Long tap: Single touch & holding, ON the scene.
Stroke: A regular swipe started FROM the scene, and ended anywhere on the screen.
Don't get confused, there are NO different swipe types like long swipe, or short swipe in Tasker by default. For this project, we can mention a swipe with %stroke_len more than a user specified number as a long swipe, and a swipe shorter than that as a short swipe.
3. DifficultyYou only need to know the basics of Tasker app and scenes. If you are okay with creating, editing, showing and destroying scenes, then it's just a cakewalk.
You just need to create scenes wherever you want, then inside the tap, or long tap, or stroke tabs of your scene, add the if statements with any one of %stroke_len > or %stroke_len <, AND, %stroke_dir ~ as two conditions, and then your desired set of actions inside each if statement, between If and EndIf. (Refer Demo, Screenshots & Project Backup section)
If you are not comfortable with creating, editing, showing and destroying scenes, it will take maximum 1-2 hours to understand the same.
It is time consuming, only during the initial setup from the scratch.
After that, it is editing or adding conditions and shortcuts, again, it's just a cakewalk.
4. How it works!Using the scenes inside Tasker, we are setting up three different areas on the screen, which are, top (horizontal), left and right (vertical). Inside each scene, we can make small multiple shapes, where we can add different tasks to each portion, when we do a swipe, tap or long tap on it.
When it comes to swipe, we can define the swipe length (using %stroke_len) and the swipe direction (using %stroke_dir), where we can assign different tasks to each conditions, which are made with a pair of a swipe length and a swipe direction.
What is more interesting is that the swipe directions can be any of vertical or horizontal directions like Up, Down, Left, or Right, and also diagonal directions like UpLeft, UpRight, DownLeft and DownRight. (But try not to use vertical and diagonal directions together at a single location, as it might bring conflicts and may end up giving you wrong response because of failing to read your swipe correctly).
These gestures are NOT restricted to homescreen, but works irrespective of which screen or app is currently active on the screen (Exception: To make scenes work in Settings app, you need to Allow Screen Overlays in Settings through developer options).
5. UsesFor instance, a task (set of actions) can be assigned into a swipe gesture like short swipe to UpLeft direction, and another task to another swipe long swipe to UpRight direction, etc.
Examples:
Short swipe from left center edge in UpRight direction, opens YouTube.
Short swipe from right center edge in DownLeft direction, jump to last app.
Long tap on the top middle (1st scene) of the screen, toggles WiFi.
Long tap on the top middle (2nd scene) of the screen, toggles mobile data.
Long swipe from right top edge in Up direction, takes a screenshot.
Long swipe from right bottom edge in Down direction, kill foreground app.
6. AutorunYou can assign the same task (which is set up to show the scene), to a new profile which gets triggered on the device boot. This will make these swipe gestures enable automatically few seconds (or so) after booting your smartphone.
However, you can always open the task inside Tasker app, and click on the play button (⏵) to run the task manually, which will show the scene (or enable the swipe gestures).
Since I'm using Nova Launcher, I also added the same task to a Nova's homescreen gesture, so that I can easily restart this swipe gesture from homescreen itself, whenever required, or just after editing the scene via Tasker. This is very helpful because whenever we edit a scene via Tasker, the scene will get automatically destroyed. So every time you modify a scene, we have to manually re-enable it.
7. Demo, screenshots, TaskerNet & project backup
Demo:
Google Pixel: In this screenshot, I have mentioned all of the possibilities we have for the Pixel 6, which doesn't get into conflict with the existing system gestures provided by Google.
Others: I suggest using these kind of directions in other android devices which doesn't have native gestures like left swipe from the right edge, and right swipe from the left side edge.
Screenshots: This is the screen where we edit or add set of tasks to be performed, using if statements with conditions %stroke_len > (or %stroke_len <), AND %stroke_dir ~.
TaskerNet: Projects for Pixel 6 and Galaxy S8.
Project Backup: To start with setting up this project, if you want, you can also refer to these regularly updated backup of my setup where I included all the scenes, required task to activate the scene, and the project to autorun this setup on device boot. The folder includes files for both Galaxy S8 and Google Pixel 6. (You can refer here for assistance on how to import task and scene into your Tasker)
8. Tips
If your device (like Google Pixel) already got a native swipe gesture like left swipe from the right screen edge, and right swipe from the left screen side edge, you should not create a similar gesture via Tasker, which will conflict with your existing system gestures.
Swipe direction Down from a top horizontal scene might also end up in issues since most of the Android devices natively use the same gesture to pull down notification panel.
Try not to use vertical directions and diagonal directions together. For example, in right side, don't use Up or Down series AND UpLeft, DownLeft series together. Both these series at a single location might bring conflicts and it may end up giving you wrong response because of failing to read your swipe correctly.
Try not to avoid using tap. Instead, use long tap, to avoid accidental touches.
Always keep the size of the scenes thin, because these scene are blocking scenes which makes area behind it untouchable. So anything below the scene is, impossible to touch. (Refer tip number 8 along with this)
Always re-activate (show) the scene after making any changes, because making changes disables (destroy) the scene.
Assign the (scene enabling) task to any swipe gestures of your launcher (if any) to make restarting the gesture easy. However, you can always open the task inside Tasker app, and click on the play button (⏵) to run the task manually.
This is a workaround to make these blocking scenes hide temporarily so that we can touch whatever was behind the scene. (Thanks to user ActivateGuacamole for this idea)
Few other valuable tips for choosing the right swipe length for tasks considering their frequency of usage. (Thanks to user ActivateGuacamole for this idea)
9. Why not those easy to use apps from PlayStore?
Because Tasker is powerful. Period.
I have tried few popular gesture setting apps but I always came back to Tasker itself because of the level of control, and customization we have here. Tasker can do impressive automations, which can also be implemented into this swipe gestures, something that can't be achieved with other easy to use and ready-made gesture apps.
With this method, I can add a set of actions (not just one single action), one by one, to be performed, into one single gesture. So if I wanted to do a swipe on the screen, and then another direction swipe, and then a click on a specific area, all these automatically, I can easily do with Tasker.
Examples:
Kill and remove foreground app from recent: You can watch this screen record video which shows my simple swipe gesture running the task where Tasker automates actions (a) open recent apps list, (b) a swipe action to swipe away the app, and (c) another swipe action to go to home screen. All this within a fraction of second. Impressive. isn't it?
Clear all recent apps: In Pixel 6, clear all button is placed at the end of the list. But watch this one, a simple gesture is enough. Tasker will take care of the rest. Again, Impressive. Isn't it?
For implementing such complicated automations, advanced settings and toggling, into a swipe gesture, Tasker is the best solution.
10. End note.It took days of questions, answers, trail and errors to first understand, and then to make this thing work flawless. Me and my couple of friends really find this useful in our smartphones, so I decided to share it with you also. If you find this useful for you, go ahead. And if you think this is not worth the time and effort required, you can kindly ignore.
I, a noob, wouldn't have made this possible without receiving a help from another person. So, a big thanks to u/adbenj for the initial guide and idea.
Always remember that there is nothing in the world like suitable for everyone, so stick to whatever is suitable for you.
Click to expand...
Click to collapse
.
UPDATE 1: Added TaskerNet in section "7. Demo, screenshots, TaskerNet & project backup".
Awesome information and Guide!
Thank you for taking the time to put all of this together from the Taker files themselves and then a complete and detailed write up!
.
coffee-turtle said:
Awesome information and Guide!
Thank you for taking the time to put all of this together from the Taker files themselves and then a complete and detailed write up!
Click to expand...
Click to collapse
I know this is not something that everyone considers worthy, because of the time and effort required for the initial setup. Most of the people might go with those free ready to use applications from Play Store. But I thought at least Tasker uses might consider this useful because they are already using the Tasker and automating lot of things like a power user, or a techie (like I pretend )
I did enjoy the whole process from research, trial & error, finishing and finally this write up.
Anyway, thanks for the nice words. It took half a day to finish this write up, after numerous editing formatting and reformatting.
Happy to know that the time that I spent for this write up didn't get wasted by mere replies like "not worthy".
Thanks
Actually, now I am replacing some apps! Tasker is great and nice to have everything under one roof with greater customizing! You should also post this on Joas main Tasker Reddit forum and consider adding the demos to TaskerNet. Not only will this get greater visibility, but a lot of action happens there especially when Joas comes up with new updates. One of his last videos really highlighted scenes because he made them even able to appear on the lock screen, navigation bar, and status bar. This will even add more power to what you present here.
Not everyone explains in such detail as you did here and you've inspired some ideas to make using my phone even easier.
Keep up your good work!
coffee-turtle said:
Not everyone explains in such detail as you did here and you've inspired some ideas to make using my phone even easier.
Click to expand...
Click to collapse
For the past 3 moths, I explained this briefly to many people in Reddit via comments. So I already know what all questions may pop up when explaining this, which helped me to make this final post very detailed.
consider adding the demos to TaskerNet
Click to expand...
Click to collapse
The thing is, I don't think there is a way to share the scenes via TaskerNet URLs. Only project and task can be shared via that. That's why I exported the project, required tasks and scenes, and uploaded to a shared Google Drive folder.
Will do post in Tasker subreddit also.
Anyway, thank you for your kind words
coffee-turtle said:
...and consider adding the demos to TaskerNet.
Click to expand...
Click to collapse
Hi.
To be honest, today only I learned how to move (rather than exporting, deleting & importing) a profile, task and relevant scenes into a new project.
So finally I updated the post with TaskerNet links in section "7. Demo, screenshots, TaskerNet & project backup"
Great work Thanks!
ShebeerPrince said:
Table of Contents
Preface
Requirements
Difficulty
How it works!
Uses
Autorun
Demo, screenshots, TaskerNet & project backup
Tips
Why not those easy to use apps from PlayStore?
End note.
1. PrefaceBefore getting my hands on Pixel 6, I was using a Samsung Galaxy S8 running on an Android 10 custom ROM. Samsung provides an advanced, and very useful app called Good Lock, in which the "One Hand Operation +" feature helps us to set up upto freaking 36 number of swipe gesture shortcuts, from the left and right (top, center and bottom) sides of the screen, irrespective of which screen or app is currently active on the screen.
The only thing that I was sure about missing in Pixel 6 was this swipe gestures. That's why I did my research even before receiving my Pixel. Now I've successfully implemented a replica of the Samsung's swipe gesture into my Google Pixel.
These gestures makes it very easy to use this big and heavy smartphone.
This gesture setup made it easy for me to pull up my Control Panel created in Tasker, whenever I need, irrespective of which app or screen I'm in.
2. Requirements
Tasker
Tasker terms to understand (Only for those who are new to Tasker)
TASK : An action or set of actions which will be later run by Tasker by itself, when defined conditions are met. Can also be run manually via the Tasker app.
Examples: Launch an app, change ringer volume, toggle WiFI, disable auto rotation etc.
PROJECT : An individual Tasker set up, where we define the conditions to meet, and the tasks to be performed when the defined conditions are met.
Example 1: A profile which automatically enables the auto-rotation (task), when YouTube is opened (condition), and disables auto-rotation when you leave YouTube.
Example 2: A profile which automatically enables mobile data (task), when your device is connected to your car WiFi (condition) or Android Auto.
SCENE : A visible, or invisible shape which will be displayed on the screen, and can be configured to respond to a swipe, tap or long tap on it, and then accordingly perform a pre-defined task. A scene can only be enabled (show) and disabled (destroy) through a task or a project.
Example 1: A visible button that can be displayed on the screen, or an invisible location on the screen, which disables WiFi when we long tap on it.
Example 2: A visible button that can be displayed on the screen, or an invisible location on the screen, which opens recent apps list when we swipe on it.
"If" variables to be used in scenes for assigning shortcuts, to each combination of a swipe length and a swipe direction:
%stroke_len : Defines the length of the swipe in pixels.
%stroke_dir : Defines the direction of the swipe. (Read How It Works! section)
Actions that can be performed on a scene:
Tap: A single touch ON the scene.
Long tap: Single touch & holding, ON the scene.
Stroke: A regular swipe started FROM the scene, and ended anywhere on the screen.
Don't get confused, there are NO different swipe types like long swipe, or short swipe in Tasker by default. For this project, we can mention a swipe with %stroke_len more than a user specified number as a long swipe, and a swipe shorter than that as a short swipe.
3. DifficultyYou only need to know the basics of Tasker app and scenes. If you are okay with creating, editing, showing and destroying scenes, then it's just a cakewalk.
You just need to create scenes wherever you want, then inside the tap, or long tap, or stroke tabs of your scene, add the if statements with any one of %stroke_len > or %stroke_len <, AND, %stroke_dir ~ as two conditions, and then your desired set of actions inside each if statement, between If and EndIf. (Refer Demo, Screenshots & Project Backup section)
If you are not comfortable with creating, editing, showing and destroying scenes, it will take maximum 1-2 hours to understand the same.
It is time consuming, only during the initial setup from the scratch.
After that, it is editing or adding conditions and shortcuts, again, it's just a cakewalk.
4. How it works!Using the scenes inside Tasker, we are setting up three different areas on the screen, which are, top (horizontal), left and right (vertical). Inside each scene, we can make small multiple shapes, where we can add different tasks to each portion, when we do a swipe, tap or long tap on it.
When it comes to swipe, we can define the swipe length (using %stroke_len) and the swipe direction (using %stroke_dir), where we can assign different tasks to each conditions, which are made with a pair of a swipe length and a swipe direction.
What is more interesting is that the swipe directions can be any of vertical or horizontal directions like Up, Down, Left, or Right, and also diagonal directions like UpLeft, UpRight, DownLeft and DownRight. (But try not to use vertical and diagonal directions together at a single location, as it might bring conflicts and may end up giving you wrong response because of failing to read your swipe correctly).
These gestures are NOT restricted to homescreen, but works irrespective of which screen or app is currently active on the screen (Exception: To make scenes work in Settings app, you need to Allow Screen Overlays in Settings through developer options).
5. UsesFor instance, a task (set of actions) can be assigned into a swipe gesture like short swipe to UpLeft direction, and another task to another swipe long swipe to UpRight direction, etc.
Examples:
Short swipe from left center edge in UpRight direction, opens YouTube.
Short swipe from right center edge in DownLeft direction, jump to last app.
Long tap on the top middle (1st scene) of the screen, toggles WiFi.
Long tap on the top middle (2nd scene) of the screen, toggles mobile data.
Long swipe from right top edge in Up direction, takes a screenshot.
Long swipe from right bottom edge in Down direction, kill foreground app.
6. AutorunYou can assign the same task (which is set up to show the scene), to a new profile which gets triggered on the device boot. This will make these swipe gestures enable automatically few seconds (or so) after booting your smartphone.
However, you can always open the task inside Tasker app, and click on the play button (⏵) to run the task manually, which will show the scene (or enable the swipe gestures).
Since I'm using Nova Launcher, I also added the same task to a Nova's homescreen gesture, so that I can easily restart this swipe gesture from homescreen itself, whenever required, or just after editing the scene via Tasker. This is very helpful because whenever we edit a scene via Tasker, the scene will get automatically destroyed. So every time you modify a scene, we have to manually re-enable it.
7. Demo, screenshots, TaskerNet & project backup
Demo:
Google Pixel: In this screenshot, I have mentioned all of the possibilities we have for the Pixel 6, which doesn't get into conflict with the existing system gestures provided by Google.
Others: I suggest using these kind of directions in other android devices which doesn't have native gestures like left swipe from the right edge, and right swipe from the left side edge.
Screenshots: This is the screen where we edit or add set of tasks to be performed, using if statements with conditions %stroke_len > (or %stroke_len <), AND %stroke_dir ~.
TaskerNet: Projects for Pixel 6 and Galaxy S8.
Project Backup: To start with setting up this project, if you want, you can also refer to these regularly updated backup of my setup where I included all the scenes, required task to activate the scene, and the project to autorun this setup on device boot. The folder includes files for both Galaxy S8 and Google Pixel 6. (You can refer here for assistance on how to import task and scene into your Tasker)
8. Tips
If your device (like Google Pixel) already got a native swipe gesture like left swipe from the right screen edge, and right swipe from the left screen side edge, you should not create a similar gesture via Tasker, which will conflict with your existing system gestures.
Swipe direction Down from a top horizontal scene might also end up in issues since most of the Android devices natively use the same gesture to pull down notification panel.
Try not to use vertical directions and diagonal directions together. For example, in right side, don't use Up or Down series AND UpLeft, DownLeft series together. Both these series at a single location might bring conflicts and it may end up giving you wrong response because of failing to read your swipe correctly.
Try not to avoid using tap. Instead, use long tap, to avoid accidental touches.
Always keep the size of the scenes thin, because these scene are blocking scenes which makes area behind it untouchable. So anything below the scene is, impossible to touch. (Refer tip number 8 along with this)
Always re-activate (show) the scene after making any changes, because making changes disables (destroy) the scene.
Assign the (scene enabling) task to any swipe gestures of your launcher (if any) to make restarting the gesture easy. However, you can always open the task inside Tasker app, and click on the play button (⏵) to run the task manually.
This is a workaround to make these blocking scenes hide temporarily so that we can touch whatever was behind the scene. (Thanks to user ActivateGuacamole for this idea)
Few other valuable tips for choosing the right swipe length for tasks considering their frequency of usage. (Thanks to user ActivateGuacamole for this idea)
9. Why not those easy to use apps from PlayStore?
Because Tasker is powerful. Period.
I have tried few popular gesture setting apps but I always came back to Tasker itself because of the level of control, and customization we have here. Tasker can do impressive automations, which can also be implemented into this swipe gestures, something that can't be achieved with other easy to use and ready-made gesture apps.
With this method, I can add a set of actions (not just one single action), one by one, to be performed, into one single gesture. So if I wanted to do a swipe on the screen, and then another direction swipe, and then a click on a specific area, all these automatically, I can easily do with Tasker.
Examples:
Kill and remove foreground app from recent: You can watch this screen record video which shows my simple swipe gesture running the task where Tasker automates actions (a) open recent apps list, (b) a swipe action to swipe away the app, and (c) another swipe action to go to home screen. All this within a fraction of second. Impressive. isn't it?
Clear all recent apps: In Pixel 6, clear all button is placed at the end of the list. But watch this one, a simple gesture is enough. Tasker will take care of the rest. Again, Impressive. Isn't it?
For implementing such complicated automations, advanced settings and toggling, into a swipe gesture, Tasker is the best solution.
10. End note.It took days of questions, answers, trail and errors to first understand, and then to make this thing work flawless. Me and my couple of friends really find this useful in our smartphones, so I decided to share it with you also. If you find this useful for you, go ahead. And if you think this is not worth the time and effort required, you can kindly ignore.
I, a noob, wouldn't have made this possible without receiving a help from another person. So, a big thanks to u/adbenj for the initial guide and idea.
.
UPDATE 1: Added TaskerNet in section "7. Demo, screenshots, TaskerNet & project backup".
Click to expand...
Click to collapse
hey so i want to know how much extra battery this costs running.
And also i want to make some sort of simillar gesture swipe thing. i am wondering if via tasker i could do the following: keeping the regular side swipe horizontal to be back, and long swipe for previous app. but then also having the side gest. to be an app shortcut based on the current app running. so maybe like when youtube is running i can swipe up to open notes and write something down and then via previous app i am back to youtube. but when i am on the work app i can vertically swipe to bring the time tracker app. or a swipe down for the google maps route to home. etc. etc.
how would i manage to do this?
I am using a poco f2 pro if that matters and not rooted.