Cloverplay adds touch screen controls to Google Stadia and Microsoft xCloud on rooted Android phones

With more people than ever staying at home due to COVID-19, there’s never been a better time to learn a new skill, work on your resume, catch up on the latest show, or play that new video game. If you’re itching to play some video games during all this downtime and you don’t already have a gaming PC or the latest consoles, then you may be interested in the cloud game streaming offerings from Google, Microsoft, and NVIDIA. For those of you with Google Stadia or Microsoft xCloud, we wanted to bring your attention to a cool new application developed by XDA Member refi64. Called Cloverplay, the app brings touch screen controls that overlay on top of the Android apps for Stadia and xCloud.

As you can see in the screenshots below, Cloverplay lets you play games from Stadia or xCloud on your Android phone without needing a physical controller. The app provides a set of on-screen controls that emulate button presses and joystick inputs from the Google Stadia controller (for Stadia) and Xbox One S controller (for xCloud). To demonstrate this, the developer published screenshots showing touch screen controls in Final Fantasy XV (on Google Stadia) and Totally Accurate Battle Simulator (on Microsoft xCloud)

We previously covered a tool called “TouchStadia” that also enables touch screen controls for Google’s cloud gaming service. While TouchStadia can work without root access, it only works when playing Stadia games through the mobile browser. In comparison, Cloverplay works with the official Google Stadia app, and it also works with Microsoft xCloud. The developer summarizes the advantages and disadvantages of Cloverplay versus TouchStadia as follows:

• TouchStadia advantages compared to Cloverplay:
  • Works on any device. (You can use Xtadia on Android to make Stadia run on non-approved devices, but Xposed is needed for that to work.)
  • No root access required.
  • Can be combined with Stadia+ if you use a browser with extension support (e.g. Yandex).
  • Supports custom control layouts.
• Cloverplay advantages compared to TouchStadia:
  • Allows you to use the official app (this tends to yield slightly better performance IME).
  • Works with xCloud.
  • Significantly easier to use (no copying scripts or custom extensions required).
  • Joysticks are visible without incurring extra lag.
  • Has support for the Stadia-specific assistant and screenshot buttons.

Here’s a screen recording from the developer demonstrating Cloverplay:

According to the developer, Cloverplay uses root access to set up a virtual joystick using uinput. As for the Accessibility Service, it appears the app uses it to create an overlay of TYPE_ACCESSIBILITY_OVERLAY.

The app is available for download on XDA Labs. The main app costs $1.99 but there’s a 2-day trial version of the app you can download to see if it’s worth it for you. The developer says they chose not to initially submit the app to Google Play because they believed that Google will remove the app for misusing Accessibility Services. As far as I’m aware, though, Google has yet to remove any application for using Accessibility Services outside of its intended use. After we informed the developer of this, they have submitted the app to the Play Store for review.

For more information on Cloverplay, visit the app’s website linked below. If you have feedback or want to ask a question, check out the app’s forum thread on XDA. You can also view the app’s source code on GitHub.

Cloverplay Website ||| XDA Forum Thread ||| Source Code

Cloverplay [ROOT] ($1.99, XDA Labs) →

Cloverplay [TRIAL][ROOT] (Free, XDA Labs) →

The post Cloverplay adds touch screen controls to Google Stadia and Microsoft xCloud on rooted Android phones appeared first on xda-developers.

from xda-developers https://ift.tt/2VlUWdo
via IFTTT

OnePlus 7 and 7 Pro get OxygenOS Open Beta 12 with April 2020 patches, camera lens dirt detection, and more

Earlier this week, OnePlus unveiled the OnePlus 8 series. Although the company’s attention is mostly focused on promoting its two new smartphones, the company is still providing support for its previous generation flagships as promised. Now, the 2019 OnePlus 7 and OnePlus 7 Pro are receiving OTA updates to OxygenOS Open Beta 12.

OnePlus 7 Forums ||| OnePlus 7 Pro Forums

OxygenOS Open Beta 12 brings the April 2020 Android Security Patch Level (SPL), a new feature in the OnePlus Camera app to detect dirt on the camera lens, ringing duration information for missed phone calls, and more. This update follows Open Beta 11 last month which brought the Android Security Patch Level to March 2020 and also added the Instant Translation feature. The stable update for the 7 series also rolled out last month with the March 2020 SPL.

Changelog – OxygenOS Open Beta 12 for the OnePlus 7 series

• System
  • Optimized the volume adjustment to improve user experience
  • Added the missing recording icon in call screen
  • Updated Android security patch to 2020.04
  • Fixed known issues and improved system stability
• Phone
  • Added the ringing duration info for missed calls
  • Now you can switch your mobile data on phone calls supported with VoLTE
• Camera
  • Added a feature which can now detect dirt on the camera lens, prompting a quick cleanup for better image and video quality.

The update is rolling out now for users. The incremental OTAs for both devices are about 316MB in size.

OxygenOS Open Beta 12 Downloads

If you don’t want to wait for the OTA to reach your device, you can download the incremental OTA file or the full OTA file from the links below. Simply download one of the files and then use the “local upgrade” option in the System Update screen under Settings to initiate the update.

Download OxygenOS Open Beta 12 for OnePlus 7: Incremental OTA from Open Beta 11 ||| Full OTA

Download OxygenOS Open Beta 12 for OnePlus 7 Pro: Incremental OTA from Open Beta 11 ||| Full OTA

Thanks to XDA Senior Member Some_Random_Username for providing some of the download links!

The post OnePlus 7 and 7 Pro get OxygenOS Open Beta 12 with April 2020 patches, camera lens dirt detection, and more appeared first on xda-developers.

from xda-developers https://ift.tt/2yt2Ete
via IFTTT

Kiwi Browser goes open source, allowing other Chromium-based browsers to add Extensions

The open-source Chromium project, based on the Blink engine, serves as the basis for dozens of web browsers. There’s the most popular, Google Chrome, along with others like Microsoft Edge, Vivaldi, Brave, and more. Most Chromium-based web browsers offer a handful of additional features not found in Google Chrome, but there are some that radically change the experience. Kiwi Browser by XDA Senior Member arnaud42 is one such web browser, and for the browser’s second anniversary, the developer has fully open-sourced the web browser and all its features.

Back in 2018, arnaud42 released the first version of his Chromium-based web browser. When we first covered the project several months later, we were impressed by the feature-set it offered at the time, which pales in comparison to what the browser offers today. It had features like a built-in content blocker, dark mode, background video playback, AMP skipper, and more. The browser got better and better with each update, but what really made it shine is the fact that it was the first Chromium-based browser for Android that supports Chrome Extensions.

Maintaining such an ambitious project has proven challenging for the lone developer. The latest version of Kiwi Browser on the Google Play Store is based on Chromium version 77.0.3865.92, which is far behind the upcoming Chromium version 83 release that Google is planning. Rather than let the project go to waste, arnaud42 has decided to release the source code for Kiwi Browser on GitHub. He says that “everything is released, including extensions code” with “no strings attached” (the browser is licensed under the BSD 3-Clause.) He encourages developers of other Chromium-based web browsers to integrate Kiwi’s code into their projects. He states that in the last few weeks, he worked with other browser developers to help them integrate some of Kiwi’s functionality, so we may hear some good news from other web browsers on Android soon.

Arnaud42 will continue to review code submissions on the project’s GitHub if you’re interested in contributing to the project. The code is written in Java and C++ and all dependencies are already included in the repository to help developers who face difficulties setting up the Chromium build system.

Kiwi Browser Source Code on GitHub ||| XDA Forum Thread

Kiwi Browser is one of the most impressive projects we’ve seen on our forums for some time. The developer, arnaud42, is also a friend of XDA, so we would like to thank him for his work on this project over the last two years. We hope that other Chromium-based browsers incorporate some of Kiwi’s features soon because I’m really missing the ability to use Extensions on mobile!

Kiwi Browser - Fast & Quiet (Free, Google Play) →

Kiwi Browser (Free, XDA Labs) →

The post Kiwi Browser goes open source, allowing other Chromium-based browsers to add Extensions appeared first on xda-developers.

from xda-developers https://ift.tt/2xEN6lV
via IFTTT

Leaked Google Pay screenshots reveal “Google Card” debit card

One of the surprising “tech” product launches last year was the Apple Card. The company pitched it as a way to help Apple customers make smarter financial decisions through the help of a more intuitive app. The Apple Card has some interesting ideas, but it’s basically just a cash-back credit card. A new report and leaked images reveal that Google is developing a similar product tentatively called “Google Card.”

The report comes out of TechCrunch and they refer to the Google Card as a “smart debit card.” Many of the concepts are similar to the Apple Card. This is a physical card that also exists as a virtual card in Google Pay, just like any other credit card you’ve added. The big difference between the Google Card and a different credit card will be integrated and detailed financial tracking.

Like any credit card, the Google Card will come with a checking account. Users will be able to access this account to check their balance, track purchases, lock, and other features in a new Google app. The card will be co-branded with bank partners such as CITI and Stanford Federal Credit Union. Leaked images give us a look at some of the other details.

The physical card itself is white with the logo of the partnered bank and Google. We can see that it’s a chip card on the Visa network, but there could be other networks included. The card design (which may not be final) also features a strange blue and green dot pattern. More important than the plastic, however, is the app experience, which is what should really set the Google Card apart from other credit cards.

The app will show recent transactions with merchant and date details. Since this is Google, there will be a wealth of information available as well. You will be able to see the location of the purchase on a map. If a card is lost or foul play is suspected, the user can lock the card immediately from the app and order a replacement. The virtual card will remain active as it has a different number than the physical card, so you won’t be completely out of luck. If the virtual card is the card in question, the user can rest it quickly.

In the app settings, we can see notification options and privacy controls. Users will be able to decide what information they want to share. Privacy is obviously going to be a big topic around the Google Card. People don’t have the same amount of trust for Google as they do for Apple. Many of us already give Google a lot of our personal information, but handing over the reigns on personal finance may be a bridge too far.

Some of this may sound familiar if you remember Google Wallet, which also had a physical component, but was ultimately replaced by Google Pay. Tech companies like Google and Apple are better suited for making software that’s easy to use and understand. That’s the appeal of signing up for an Apple Card or Google Card. TechCrunch did not give a timeline for when to expect the Google Card to become a reality. Are you interested in this product?

---

Source: TechCrunch

The post Leaked Google Pay screenshots reveal “Google Card” debit card appeared first on xda-developers.

from xda-developers https://ift.tt/2VH20zY
via IFTTT

Magisk Module enables Camera during call, Call Recording, AppLock, and more on Samsung Galaxy S20

OEM Android skins, such as Xiaomi’s MIUI or OnePlus’ OxygenOS, often feature multiple regional variants. While a few region-exclusive services can be controlled from the server side, some manufacturers prefer to ship a complete set of features inside the firmware, with selective access to regional features being controlled via hidden parameters that are not visible to regular users. In the case of Samsung, they define those features via their Consumer Software Customization file (CSC). Fiddling with the CSC is not everyone’s cup of tea, so XDA Senior Member Orphee has come up with an interesting Magisk Module named Decoded_CSC_Features_Files for the Samsung Galaxy S20 lineup that can unlock a bunch of features that are not otherwise available in certain regions.

XDA Forums for Samsung Galaxy: S20 || S20+ || S20 Ultra

Buy from Amazon.in — Samsung Galaxy: S20 || S20+ || S20 Ultra

As you may expect, this mod requires having an unlocked bootloader, thus it can only be installed on Exynos-powered variants of the Samsung Galaxy S20. The latest Canary version of Magisk is capable of patching the boot image of this phone, and the procedure is fairly similar to the Galaxy S10 rooting guide. Once you have Magisk up and ready, flashing the Decoded_CSC_Features_Files module can unlock the following features:

• Disable shutter sound menu
• Enable AppLock Protection menu
• Enable real-time network speed
• Enable camera during call
• Enable call recording (regular voice calls only)
• Data usage view on the quick panel
• Block call number menu
• Enable eSIM support

This module is based on work by XDA Senior Member m8980, but Orphee has further expanded upon it by adding numerous other features, such as support for eSIM. The package is compatible with the latest official firmware for the Galaxy S20 series (G98xFXXU1ATCT) and should work with future software revisions with little to no modification. The operator software version might be changed to “G981B” after installing this mod, but this is a harmless side-effect and can be ignored.

Download Decoded_CSC_Features_Files Magisk Module — XDA Thread

This post contains affiliate commerce links that will earn XDA a commission if you purchase through them.

The post Magisk Module enables Camera during call, Call Recording, AppLock, and more on Samsung Galaxy S20 appeared first on xda-developers.

from xda-developers https://ift.tt/3bkK2Kj
via IFTTT

Samsung launches a handwashing app for Galaxy watches

Proper handwashing techniques have received a lot of attention in recent months due to the COVID-19 pandemic. The simple act of washing your hands plays an important role in preventing the spread of the virus. Hot on the heels of Google’s handwashing timer for Wear OS, Samsung is doing its part and releasing a similar app for Galaxy smartwatches.

Samsung’s app is a little different from Google’s. Simply named “Hand Wash,” this is a stand-alone app rather than an extra feature tacked on to the existing Clock app. Users have to manually seek it out and install the app from the Galaxy Store, which, unfortunately, means fewer people will know about it. On the plus side, this allows the app to have more features.

The “Hand Wash” app can be set as your watch face, making it much easier to launch quickly. The watch face shows how many times you have washed your hands and how long it has been since your last wash. While Google’s app has a 40-second timer, Samsung is going with a less aggressive 25 seconds (still longer than the CDC recommends). The watch will vibrate when the time is up.

CDC’s handwashing instructions:

1. Wet your hands with clean, running water (warm or cold), turn off the tap, and apply soap.
2. Lather your hands by rubbing them together with the soap. Lather the backs of your hands, between your fingers, and under your nails.
3. Scrub your hands for at least 20 seconds. Need a timer? Hum the “Happy Birthday” song from beginning to end twice.
4. Rinse your hands well under clean, running water.
5. Dry your hands using a clean towel or air dry them.

Launching the app from the app carousel will allow you to manually enter how many times you have washed your hands. There is also a chart that shows how many times you washed your hands each day and the week’s average. The Hand Wash app will also remind you to wash your hands periodically. There are 8 reminders by default, but you can add more or delete up to 3 of the reminders.

The Hand Wash app seems to be available for all Samsung watches in the Galaxy Store. Samsung only mentions “Galaxy Watch” users, but I was able to download it on my non-Galaxy branded Gear Sport as well. Open the Galaxy Store and search for “Hand Wash” by Samsung Electronics to see if it’s available for your smartwatch.

---

Source: Samsung

The post Samsung launches a handwashing app for Galaxy watches appeared first on xda-developers.

from xda-developers https://ift.tt/3ag6ZNA
via IFTTT

Google Calendar prepares to add cross-profile support for work and personal calendars

Work profiles in Android isolate all applications and synced account information from the personal profile so users don’t accidentally mix information from their work and personal lives. While work profiles can help employees manage their work-life balance and avoid accidentally leaking information, there are a few inconveniences that they introduce. For example, many work-managed calendar applications don’t support cross-profile calendar sync, meaning users have to check their calendar app in both their personal and work profiles to make sure they don’t miss an important meeting or event. Even Google Calendar doesn’t support cross-profile calendar visibility yet.

In Android 10, however, Google added support for showing work calendar details in the personal calendar and vice versa. With cross-profile calendar visibility, you can see work events in your personal calendar, and if you attempt to edit an event created in your work calendar, you are directed to edit the event in the calendar app from your work profile. This maintains proper separation between personal and work profiles while also making things more convenient for workers. However, in order to support cross-profile calendar visibility, calendar applications have to be updated to support the new APIs. There’s evidence in the latest version of the Google Calendar app for Android that Google is preparing to enable cross-profile calendar support.

An APK teardown can often predict features that may arrive in a future update of an application, but it is possible that any of the features we mention here may not make it in a future release. This is because these features are currently unimplemented in the live build and may be pulled at any time by the developers in a future build.

In the latest version of Google Calendar, version 2020.14-1, we spotted new strings that hint at cross-profile calendar connections. One set of strings will appear as part of a promo message informing the user that they can “see all [their] events here, including [their] personal calendars.” Another set of strings describes the preference in Settings that the user must enable to show calendar events from their personal Calendar app in their work Calendar app. Enabling this preference will “[let] you see your work events alongside your personal events.” Once enabled, “you can then quickly jump to your personal Calendar app to change events.” To maintain privacy, “your calendars are still stored separately.”

<string name="cross_profile_drawer_promo_text">To see all your events here, include your personal calendars</string>
<string name="cross_profile_drawer_promo_title">Add your personal calendars</string>
<string name="cross_profile_learn_more">Learn more</string>
<string name="cross_profile_promo_dismiss">Dismiss</string>
<string name="crossprofile_connection_off">Not connected</string>
<string name="crossprofile_connection_on">Connected</string>
<string name="crossprofile_preference_activate_info">"Turning this on lets your work Calendar app show the calendar events from your personal Calendar app. This lets you see your work events alongside your personal events. You can then quickly jump to your personal Calendar app to change them. To Protect your privacy, your calendars are still stored separately."</string>
<string name="crossprofile_preference_activate_link">Turn on in Settings</string>
<string name="crossprofile_preference_deactivate_info">To keep your calendars separate across apps, update access in Settings. Once turned off, your personal Calendar events will stop showing in your work Calendar app.</string>
<string name="crossprofile_preference_deactivate_link">Turn off in Settings</string>
<string name="menu_crossprofile_preferences">Personal calendars</string>
<string name="work_profile_header_title">Work profile</string>

I set up a local work profile using the Island app, but I was unable to get cross-profile calendar visibility working. It’s likely this feature will roll out in a future update of the Google Calendar app or will be enabled via a server-side configuration change. Once the feature rolls out, we’ll let you all know.

Work Profile on a Google Pixel 4 running Android 10

Google Calendar (Free, Google Play) →

The post Google Calendar prepares to add cross-profile support for work and personal calendars appeared first on xda-developers.

from xda-developers https://ift.tt/2yqjhW5
via IFTTT