Google offers a host of accessibility features on Android to help users with various disabilities, and the company keeps adding new features to the Accessibility Suite ever so often. This year in May, the company released Android Accessibility Suite v8.2, with a new TalkBack Braille keyboard for the visually impaired. Now, with Android Accessibility Suite v9.0, the company is rolling out multi-finger gesture support for better UI control.
The latest version of Android Accessibility Suite v9.0 has already started rolling out to users via the Play Store, and it includes support for multi-finger gestures. However, the feature is currently hidden within the TalkBack Developer settings.
To enable multi-finger gestures on your device, update to the latest version of the Android Accessibility Suite from the Play Store link below. Once you’ve installed the update, navigate to the Accessibility option in your device settings. Here, tap on TalkBack and then select Settings on the following page. Scroll down in the TalkBack settings and then tap on the Developer settings option. Then tap on the toggle next to “enable multi-finger gestures.”
After you’ve followed the steps mentioned above, you’ll be able to find the multi-finger gestures within “Gestures” under the “Navigation” option of the main TalkBack settings page. The feature supports a host of multi-finger gestures, including two/three-finger tap, two/three-finger double-tap, two/three-finger swipe (up, down, left, right), and more. The gestures will allow you to perform various actions, including pause feedback, play/pause media, scroll, open global context menu, start selection mode, and more.
Google offers a host of accessibility features on Android to help users with various disabilities, and the company keeps adding new features to the Accessibility Suite ever so often. This year in May, the company released Android Accessibility Suite v8.2, with a new TalkBack Braille keyboard for the visually impaired. Now, with Android Accessibility Suite v9.0, the company is rolling out multi-finger gesture support for better UI control.
The latest version of Android Accessibility Suite v9.0 has already started rolling out to users via the Play Store, and it includes support for multi-finger gestures. However, the feature is currently hidden within the TalkBack Developer settings.
To enable multi-finger gestures on your device, update to the latest version of the Android Accessibility Suite from the Play Store link below. Once you’ve installed the update, navigate to the Accessibility option in your device settings. Here, tap on TalkBack and then select Settings on the following page. Scroll down in the TalkBack settings and then tap on the Developer settings option. Then tap on the toggle next to “enable multi-finger gestures.”
After you’ve followed the steps mentioned above, you’ll be able to find the multi-finger gestures within “Gestures” under the “Navigation” option of the main TalkBack settings page. The feature supports a host of multi-finger gestures, including two/three-finger tap, two/three-finger double-tap, two/three-finger swipe (up, down, left, right), and more. The gestures will allow you to perform various actions, including pause feedback, play/pause media, scroll, open global context menu, start selection mode, and more.
Tasker developer joaomgcdshowcased an experimental plugin earlier this year in August, which allowed the automation app to hijack Android 11’s new power menu to trigger any event. The plugin was rolled out to users with Tasker 5.9.4 beta late last month, and it allowed users to add Tasker tiles to the power menu as clickable buttons. Now, the feature is finally available on the stable channel with the latest update.
As you can see in the attached video, the new Power Menu Action feature in Tasker lets you create tiles for the power menu in Android 11. These tiles can be customized to trigger every available task on Android 11 with just a tap. But they’re not limited to single tasks. The tiles can also be dynamic in nature, allowing you to perform different tasks based on various factors like your location, time of day, etc.
Along with the Power Menu Actions, Tasker 5.10 brings a new Action Command which lets you trigger the Command event with the AutoApps Command System, an Event Command that you can trigger with the Command action, and the ability to allow third-party apps to send commands that trigger the Command event. Check out the changelog section below to see everything new in the latest Tasker update.
Changelog
Added:
Added Action Power Menu Action which allows you to create tiles for the Android 11+ Power Menu.
Added the Power Menu Shown event which triggers when the Power Menu screen is shown on Android 11+
Added Power Menu tiles for every available task on Android 11+
Added Action Command which allows you to trigger the Command event with the AutoApps Command System
Added Event Command which can be triggered with the Command action
Added ability for third party apps to send commands that trigger the Command event but they have to explicitly ask the user for a permission to do so.
Added Phone Call permission to kid apps when they use Contact Via App action
Added text option to Signal and Telegram messages in the Contact Via App action
Added option to add to new project when importing a profile or task from Taskernet
Added option to disable number of enabled profiles in Tasker notification
Changes:
Changed the dialog where you choose an icon so that it shows an icon for each option
Don’t warn user about deprecated HTTP GET action if in kid app
Don’t execute actions in exit tasks of active profiles when shutting down: was previously executing all of them, even if disabled or in non-matching if conditions so it was unwanted behaviour. Tasks in profiles with the Device Shutdown event will still run.
Removed:
Removed option to insert SMS into messaging database since it wasn’t possible to do that anymore
Bugfixes:
Fixed situation where the same variable is set multiple times in a row to different values and the same value would be reported in the Variable Set event
Fixed %TETHER variable in some situations
Fixed long standing situation where Tasker would run disabled actions when the device is shutting down
Fixed keyboard automatically hiding in input fields on Scenes on Android 11+
Fixed Termux command so it’s compatible with upcoming Termux release
Fixed dialogs not cancelling when screen is rotated while they are showing
Fixed crash when reading a file too large to be read
Fixed copying/moving files with weird extensions to external SD cards
Fixed javascripts for devices that do not have recent webviews
Tasker developer joaomgcdshowcased an experimental plugin earlier this year in August, which allowed the automation app to hijack Android 11’s new power menu to trigger any event. The plugin was rolled out to users with Tasker 5.9.4 beta late last month, and it allowed users to add Tasker tiles to the power menu as clickable buttons. Now, the feature is finally available on the stable channel with the latest update.
As you can see in the attached video, the new Power Menu Action feature in Tasker lets you create tiles for the power menu in Android 11. These tiles can be customized to trigger every available task on Android 11 with just a tap. But they’re not limited to single tasks. The tiles can also be dynamic in nature, allowing you to perform different tasks based on various factors like your location, time of day, etc.
Along with the Power Menu Actions, Tasker 5.10 brings a new Action Command which lets you trigger the Command event with the AutoApps Command System, an Event Command that you can trigger with the Command action, and the ability to allow third-party apps to send commands that trigger the Command event. Check out the changelog section below to see everything new in the latest Tasker update.
Changelog
Added:
Added Action Power Menu Action which allows you to create tiles for the Android 11+ Power Menu.
Added the Power Menu Shown event which triggers when the Power Menu screen is shown on Android 11+
Added Power Menu tiles for every available task on Android 11+
Added Action Command which allows you to trigger the Command event with the AutoApps Command System
Added Event Command which can be triggered with the Command action
Added ability for third party apps to send commands that trigger the Command event but they have to explicitly ask the user for a permission to do so.
Added Phone Call permission to kid apps when they use Contact Via App action
Added text option to Signal and Telegram messages in the Contact Via App action
Added option to add to new project when importing a profile or task from Taskernet
Added option to disable number of enabled profiles in Tasker notification
Changes:
Changed the dialog where you choose an icon so that it shows an icon for each option
Don’t warn user about deprecated HTTP GET action if in kid app
Don’t execute actions in exit tasks of active profiles when shutting down: was previously executing all of them, even if disabled or in non-matching if conditions so it was unwanted behaviour. Tasks in profiles with the Device Shutdown event will still run.
Removed:
Removed option to insert SMS into messaging database since it wasn’t possible to do that anymore
Bugfixes:
Fixed situation where the same variable is set multiple times in a row to different values and the same value would be reported in the Variable Set event
Fixed %TETHER variable in some situations
Fixed long standing situation where Tasker would run disabled actions when the device is shutting down
Fixed keyboard automatically hiding in input fields on Scenes on Android 11+
Fixed Termux command so it’s compatible with upcoming Termux release
Fixed dialogs not cancelling when screen is rotated while they are showing
Fixed crash when reading a file too large to be read
Fixed copying/moving files with weird extensions to external SD cards
Fixed javascripts for devices that do not have recent webviews
Google Chrome is one of the most popular browsers around for both desktop and mobile devices, hovering around at 65% market share at any point in time. Chrome has a lot of focus on user security, and one of the newest features arriving to the browser on Android and iOS is the ability to spot compromised passwords within passwords saved on Chrome, and then offer users advice on how to fix them.
Improved Password Security
Google is rolling out improved password security on Google Chrome for Android and for iOS devices, promoting the same feature that we have seen previously in the Canary branch. The browser already offers the ability to save your passwords in an encrypted format. Google will now leverage this feature to offer the ability to crosscheck saved credentials against lists of credentials that are known to be compromised. Google claims that usernames and passwords are sent to the company using a special form of encryption, so even Google cannot derive your username or password from this encrypted copy. Once a compromised password has been spotted, Chrome will offer users an option to directly go to the right “change password” form.
Other improvements coming in Google Chrome 86
While compromised password checking rolls out today, Google also has a few more security-focused improvements in store for Chrome 86 release:
Chrome’s Safety Check feature will also be coming to mobile, making it easier for users to check for compromised passwords, enabling Safe Browsing, and checking whether the version of Chrome the user is running is up to date or not.
Chrome on iOS will also get the ability to autofill saved login details into other apps and browsers. This will be preceded with biometric authentication.
Enhanced Safe Browsing will be making its way to Android. Users can choose to be proactively protected against phishing, malware, and other dangerous sites by sharing real-time data with Google’s Safe Browsing service.
Mixed form warnings are coming to desktop and Android, warning users before submitting a non-secure form that is embedded in an HTTPS page. It will also block or warn on insecure downloads initiated by secure pages, but limiting itself currently to commonly abused file types. In the future, secure pages will only be able to initiate secure downloads of any type.
Almost two years ago, a little-known Chinese company named Royole grabbed tech headlines by launching the “world’s first foldable phone,” beating Samsung and Huawei to the market by months. The resulting product wasn’t very good, but for an upstart display panel maker making its first foray into the world of smartphones, the Royole FlexPai was at least interesting and noteworthy.
The company’s back with a sequel, the aptly named FlexPai 2, and I’ve been testing it for the past couple of days. Since the first FlexPai was launched, we’ve seen plenty of foldable devices launched so can Royole really compete with major competition like the Galaxy Z Fold 2, Huawei Mate XS, and more? Let’s find out!
Royole FlexPai 2: Specifications
Specification
Royole FlexPai 2
Dimensions & Weight
186.2 x 133.8 x 6.3 mm (unfolded)
89.4 x 133.8 x 12.8 (folded)
339g
Display
7.8-inch, 1920 x 1440, 4:3 aspect ratio (unfolded)
5.5-inch, 1440 x 900, 16:10 aspect ratio (folded, front)
5.4-inch, 1440 x 810, 16:9 aspect ratio (folded, back)
SoC
Qualcomm Snapdragon 865:
1x Kryo 585 (ARM Cortex-A77-based) Prime core @ 2.84GHz
Note: I received the Royole FlexPai 2 from Royole on October 4 and used it briefly for this hands-on ahead of our full review. Royole did not have any input into this article.
Design and hardware
Much has been said about how much the Galaxy Z Fold 2 improved over the first Fold. Well, I think FlexPai 2’s improvement over the first version could be even larger. Now, that’s not to say the Royole FlexPai 2’s hardware is better than the Fold 2’s – spoiler alert: it’s not – but rather the FlexPai 1 was quite a bit worse than the original Fold 1, so Royole had more room to improve.
I mean, just look at the photos below. The original FlexPai left a half-inch gap when folded, while the FlexPai 2’s hinge folds completely flat — noticeably more so than the Fold 2’s too. The FlexPai 1’s hinge was also covered in this weird kevlar fabric and held together by screws. The FlexPai 2’s hinge appears seamless — although I must say, it looks very similar to the Huawei Mate X’s hinge.
The hinge feels very sturdy, requiring a bit of force to unfold. It can stay open at various angles just like the Fold 2, too. When opened, the device is thin at 6.8mm, but not quite Microsoft Duo thin. When folded, the FlexPai 2’s thickness increases to 12.8mm.
The matte glass body with aluminum chassis gives it a sturdy construction, but at 339g and with measuring 89.4mm across horizontally in folded form, the FlexPai 2 is a bit wide and awkward to hold with one hand.
The FlexPai 2 has the same fundamental design as Huawei’s foldable: its large bendy screen folds backward/outwards so that when it’s closed in phone form the screen wraps around both front and back. This means the flexible plastic OLED screen is always exposed, which leaves me paranoid when handling the phone out-and-about in the real world.
I am of the belief that the supposed fragility of folding phones has been overblown
To be fair, I am of the belief that the supposed fragility of folding phones has been overblown; I used the Huawei Mate X and Mate XS as my daily drivers for a combined six to seven weeks and neither phone suffered any noticeable damage other than barely visible micro-scratches. Then again, I didn’t drop those devices, and six weeks is not quite long-term use.
The Royole FlexPai 2’s screen when fully opened is a 7.8-inch, 4:3 screen with a resolution of 1920 x 1440. It’s a solid-looking panel with enough brightness for outdoor use, but just like the displays of the FlexPai 1 or the first Fold, the screen feels very plasticky. The Galaxy Z Fold 2 and Z Flip have a display that Samsung markets as “ultra-thin glass,” and while the degree to which it really is glass has been up for debate, it does feel undeniably harder and less mushy than the screen of the FlexPai 2.
When the Royole FlexPai 2 is folded, the front side shows a 5.5-inch, 16:10 display, while the backside is a 5.4-inch, 16:9 panel. The difference in screen dimensions is due to the backside also accommodating a quad-camera module.
The four cameras consist of a 64MP, f/1.9, 1/1.72″ main camera; a 16MP ultra-wide-angle camera; 8MP telephoto; and a 32MP portrait lens designed for selfies. As there is a screen on both sides of the device, the main camera system doubles as the selfie camera system too.
Under the hood is a Snapdragon 865, with either 8GB or 12GB of RAM, paired with 256GB or 512GB storage. There’s a 4450 mAh battery that, from my limited testing so far, seems just enough to get through a typical 12-hour day.
Software: No Core GMS … I think
The FlexPai 2, unsurprisingly for a phone only sold in China right now, does not ship with Google apps. But unlike most other brands like Xiaomi or Vivo, in which Google apps can be side-loaded easily, it’s been trickier on the FlexPai 2. Within Royole’s native app store is a popular “Google Services Installer” that I’ve used successfully used on a dozen Chinese phones in the past. The app can successfully install Google Services Frameworks and Google Play store, but the latter will not load.
I initially chalked this up to Royole not having signed the Mobile Application Distribution Agreement (MADA), which basically means Royole did not pay Google a fee. This prevents Royole from installing a “stub” version of core Google apps for easy side-loading the way even China-only version of Xiaomi or Oppo phones can.
I thought the Royole FlexPai 2 simply won’t run any core Google apps the way post-entity list Huawei phones cannot. But to my surprise, YouTube loaded without issues. This should not be possible on a phone without support for Google’s frameworks (like post-entity list Huawei phones). Google Maps run fine too. But Google Docs, like the Play Store, won’t load. I’ll experiment further and see if I can indeed load core Google services. Other apps most of the world use, like Twitter, Instagram, and Facebook, all work fine, because they are not GMS-reliant.
The Royole FlexPai 2 runs a version of Android 10 named “Water OS.” Now in version 2, it’s behaved relatively smoothly thus far, most notably when transitioning from folded smartphone mode to unfolded tablet mode. I haven’t encountered many hiccups when doing trickier things like folding and unfolding the phone or rotating orientation.
As the screen is quite tall when unfolded and in landscape orientation, the extra vertical space makes it a good typing machine — there’s still plenty of room left even factoring in the on-screen keyboard.
Royole FlexPai 2 has two methods to handle multi-tasking. The first, which can only be used in the unfolded tablet form, is similar to the Galaxy Fold (both 1 & 2), meaning you can run up to three apps at once in a split-screen view.
The second way is in the way the FlexPai 2 handles the front and back screen when folded in phone mode. Essentially, each screen behaves like its own homescreen, and each screen can run its own app. For example, I can have Instagram running on the front screen, and WhatsApp running on the back screen. I can flip the device back and forth to quickly jump between those two apps.
Cameras
The camera system on the Royole FlexPai 2, at least from early testing, is solid but unremarkable. It’s worth noting that I’m testing a pre-production unit of the FlexPai 2 running non-final software, so the camera performance here may improve when retail units hit the streets.
The main lens actually produces detailed shots with punchy colors, but focusing is slow. The ultra-wide-angle camera is suffering from major color science issues right now as it has an overly warm shift that is jarring when viewed next to a 1X shot, and the telephoto camera is fine at 2X or 3X zoom but suffers beyond that. That final fourth camera is meant for selfies, and it’s okay, with decent bokeh effect and face detection. See the samples for yourself.
Other than the clearly broken color science of the ultra-wide lens, there are no major flaws with the camera. And for those wondering — the watermark can be turned off in settings.
Unfortunately for Royole, the Galaxy Z Fold 2 raised the bar too high
Other than the fact it can’t properly run Google services, I had no real gripes with the FlexPai 2 in a vacuum. I admire the efforts Royole has put in to improve hardware by this much in just a generation. The first FlexPai feels like a toy or prototype next to FlexPai 2. I genuinely enjoyed constantly jumping between two apps just flipping over the phone to the other side, and the way the hinge folds completely flat is very satisfying.
Unfortunately for Royole, Samsung raised the bar too high with the Galaxy Z Fold 2
However, I have two major issues (and I’m not including the Google stuff since it would be an easy fix if Royole ever tries to sell this outside China). The first is durability concerns: I mentioned this earlier already, but I am just not comfortable with the most expensive, important, and fragile part of the phone being exposed on three sides of the device. I prefer Samsung’s approach, in which the flexible bendy screen is covered when not in use.
The second problem is the Galaxy Z Fold 2 has set the bar too high. As I covered in my review, I love the thing and consider it a virtual lock for my phone of the year. Whether it’s camera performance, display refresh rate and texture, or in-hand feel the Galaxy Z Fold 2 tops the FlexPai 2.
The Royole FlexPai 2 is, however, $500 cheaper (it retails for 9,998 Chinese yuan, which is around $1,480), so this chunk of savings could even the playing field a bit for consumers. But ultimately, I think this phone is for collectors, enthusiasts, or someone who just likes supporting upstart smaller brands.
Google Chrome is one of the most popular browsers around for both desktop and mobile devices, hovering around at 65% market share at any point in time. Chrome has a lot of focus on user security, and one of the newest features arriving to the browser on Android and iOS is the ability to spot compromised passwords within passwords saved on Chrome, and then offer users advice on how to fix them.
Improved Password Security
Google is rolling out improved password security on Google Chrome for Android and for iOS devices, promoting the same feature that we have seen previously in the Canary branch. The browser already offers the ability to save your passwords in an encrypted format. Google will now leverage this feature to offer the ability to crosscheck saved credentials against lists of credentials that are known to be compromised. Google claims that usernames and passwords are sent to the company using a special form of encryption, so even Google cannot derive your username or password from this encrypted copy. Once a compromised password has been spotted, Chrome will offer users an option to directly go to the right “change password” form.
Other improvements coming in Google Chrome 86
While compromised password checking rolls out today, Google also has a few more security-focused improvements in store for Chrome 86 release:
Chrome’s Safety Check feature will also be coming to mobile, making it easier for users to check for compromised passwords, enabling Safe Browsing, and checking whether the version of Chrome the user is running is up to date or not.
Chrome on iOS will also get the ability to autofill saved login details into other apps and browsers. This will be preceded with biometric authentication.
Enhanced Safe Browsing will be making its way to Android. Users can choose to be proactively protected against phishing, malware, and other dangerous sites by sharing real-time data with Google’s Safe Browsing service.
Mixed form warnings are coming to desktop and Android, warning users before submitting a non-secure form that is embedded in an HTTPS page. It will also block or warn on insecure downloads initiated by secure pages, but limiting itself currently to commonly abused file types. In the future, secure pages will only be able to initiate secure downloads of any type.
