How I remotely access my Windows PC from my Android phone


Ever wanted to quickly check something on your PC while you’re away? Or maybe grab that one file you forgot to transfer to your phone? Here’s what I use to seamlessly access my Windows PC from my Android phone, no matter where I am.

Chrome Remote Desktop lets me access my PC from anywhere

Full control, superior convienence

Windows PC remote desktop landscape view on Android smartphone.

Chrome Remote Desktop offers an elegant and straightforward way to access my Windows PC from my Android smartphone. All I need to do is open the Chrome Remote Desktop app on my phone, and it shows me a list of all the connected devices—which, in my case, is my Windows desktop. With a single tap, I’m connected to my Windows PC.

The interface is clean and intuitive, with a dropdown options panel at the top that provides quick and easy access to all essential features without cluttering the screen. One aspect I particularly appreciate is how the options panel can be pinned or unpinned—I usually keep it unpinned to maximize screen real estate, especially when working on my phone’s relatively small display.

Here’s a quick overview of the key features to give you an idea of what’s possible:

Touch input: Trackpad or touch screen

Once you gain remote access to your Windows PC, you can technically use your phone’s display as a touch screen, aka direct touch (default option) to control your Windows PC, or you can turn it into a trackpad.

If you decide to use direct touch, any place you tap your phone’s screen will register as a click. So if you tap on an app icon it will start the app icon. Even though the icons and interface elements are very small, the touch accuracy is surprisingly good. I was almost always able to hit the right icon or app on the first go.

That said, cramming a full desktop interface into a 6-something-inch display will make the icons hard to click and some text difficult to read. Thankfully, you can easily pinch to zoom in and out of the desktop to get a clear view of what’s going on.

Furthermore, you can also turn the screen into a trackpad. This way, you drag your finger across the screen to move the cursor, which you can then use to click on icons and interface elements. This works exactly like a laptop trackpad where you can press and hold to select something, and use two-fingers scrolling.


A person using an Android phone as a computer mouse.


How to Use Your Android Phone as a Bluetooth Mouse or Keyboard

You can use your Android phone as a keyboard or mouse without installing software on your computer.

Keyboard integration

You can trigger the keyboard functionality from the options panels. It allows you to use your phone’s virtual keyboard to type directly into any application on your PC.

You can also hit the three-dot button to enter the advanced menu. From here, you can trigger system-wide keyboard shortcuts like Ctrl+Alt+Del just by tapping on the specific buttons. You can also configure key mapping and keyboard shortcuts.

Advanced settings

Here’s a quick look at the advanced settings in the three-dot menu:

  • Video codec selection (AV1, VP8, VP9) for optimizing performance based on your connection
  • Full-resolution color encoding
  • Smooth scrolling for better navigation
  • Frame rate control from 15fps to 60fps (I usually stick to 30fps for the best balance of responsiveness and performance)
  • System key commands for administrative tasks (as discussed in the previous section)
  • Option to upload and download files between devices
  • Clipboard synchronization between devices

In my experience, the default AV1 codec works best for most situations, but I occasionally switch to VP8 when on a slower connection. I’ve also found that disabling high-quality color mode reduces lag without significantly impacting usability.

How I set up Chrome Remote Desktop

It’s easier than you’d expect

Out of all the various remote access tools I have used, Chrome Remote Desktop is probably the simplest and quickest to set up. On your Windows PC, open Google Chrome, and go to the Remote Access website. and hit the download button (arrow pointing down icon). This will download the ChromeRemoteDesktopHost setup file.

Google Chrome Remote Desktop dowload setup tool.

Remember to use Google Chrome for a seamless experience—and not a Chrome-based browser like Edge or Brave. I learned this the hard way after troubleshooting connection issues with other browsers.

Once downloaded, run the setup file to install the host. After the installation is completed, go back to the Chrome Browser window and refresh it. You should now see an option which asks you to Set Up Remote Access. Click Turn On > Choose a name for your PC > Set a Pin, and voilà! You have successfully installed and set up Chrome Remote Desktop on your Windows PC.

Now, on your Android device, visit the Google Play Store and download the Chrome Remote Desktop app. Open the app and make sure you’re logged in using the same Google account as in your Google Chrome browser on your Windows PC.

You should see a list of all remotely accessible devices connected with your account. Pick your Windows device from the list, enter the corresponding pin, and within a few seconds you should have remote access to your Windows PC from your Android phone.

Why I chose Chrome Remote Desktop

There are other options, but this one’s the best

I’ve settled on Chrome Remote Desktop for several reasons. It’s completely free to use, covers all the essential features you’d expect from a remote access software, and it’s super easy to set up. As I just demonstrated, it barely takes more than five minutes to get it up and running on your Windows PC and Android smartphone.

Furthermore, it’s exceptionally lightweight and doesn’t tax the CPU or RAM. This means you can potentially turn on a low-specced Android phone to access your Windows PC when you’re traveling and need to access a file or run a program. This works exceptionally well if you have an Android tablet and want to turn it into a Windows tablet.

My Issues With Other Alternatives

I’ve tried other remote access solutions, but each has its drawbacks. TeamViewer works, but I found it laggy with noticeable performance issues. AnyDesk is another great option, but its latest version, at the time of writing, is super buggy and randomly disconnects in the middle of a connection.

RustDesk is probably the best alternative if you’re looking for an open-source, privacy-focused solution that you can control. However, it’s not available in the Play Store—you’ll need F-Droid, and setting it up can be complicated compared to Chrome Remote Desktop.


Keep things breezy with Chrome Remote Desktop

Chrome Remote Desktop has become my go-to solution for accessing my Windows PC from my Android phone. It’s secure, reliable, and offers all the features I need without unnecessary complexity.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


TL;DR

Meta stripped NameTag facial recognition code from its AI app one day after WIRED exposed it on 50 million phones. Meta says no decision has been made.

Meta removed nearly all traces of an unreleased facial recognition system from its smart glasses companion app on Friday, one day after WIRED reported that the software had been quietly embedded in an app installed on more than 50 million phones. The feature, which Meta internally called NameTag, was designed to convert faces captured by the company’s Ray-Ban smart glasses into unique biometric signatures and compare them against a database stored on the user’s device. WIRED also found that faces the system failed to recognise were cropped, indexed, and stored locally for future processing.

Andy Stone, Meta’s vice president of communications, told WIRED on Monday that the feature is “purely exploratory,” adding that no final decision has been made on what to do with it. That characterisation sits uneasily with the evidence WIRED documented. The version of Meta AI published the day of WIRED’s Thursday report contained several code libraries explicitly named for face recognition, a process for running the NameTag recognition pipeline, and a “Person recognised” alert the app would have shown if someone were identified.

Friday’s release stripped all of it out, along with a folder where the app would have stored the cropped images and biometric signatures of unrecognised faces. Meta did not answer WIRED’s questions about why the code was removed or whether the changes were planned before the story was published. A few fragments remain in the latest version, including an internal debug menu label and a dormant link meant to open a recognised person’s profile, pointing to parts of the system that are no longer there.

The 💜 of EU tech

The latest rumblings from the EU tech scene, a story from our wise ol’ founder Boris, and some questionable AI art. It’s free, every week, in your inbox. Sign up now!

The gap between Meta’s public statements and the code WIRED found is the central tension. Before the Thursday report, Stone dismissed the findings by writing that the company could not answer questions about how the system would work because “the feature does not exist.” Andrew Bosworth, Meta’s chief technology officer, called the reporting “incredibly misleading” and “absolutely dishonest.” Yet the code was functional enough to include three AI models, one to detect faces, another to crop them, and a third to encode them as biometric data, all embedded in the companion app for a product already at the centre of a mounting privacy crisis.

Meta declined to answer ten questions WIRED posed before publishing, including whether it had already created the database of face profiles NameTag uses, how long the app retains photographs and biometric data of unrecognised people, and whether that data would ever be sent back to Meta’s servers. The company also did not respond to questions about whether it was building NameTag for blind or low-vision users, or to criticism from privacy advocates who warned the system could let stalkers and abusers identify strangers in public.

NameTag first surfaced in February, when The New York Times, citing internal Meta documents, reported that the company was developing face recognition for its smart glasses and considering a launch as early as this year. One internal memo reportedly described releasing the feature during a “dynamic political environment” when privacy and civil liberties advocates would be distracted by other concerns. WIRED subsequently found that much of NameTag’s machinery had been built into the Meta AI app as early as January, months before any public acknowledgement, adding another layer to the company’s pattern of shipping first and disclosing later when it comes to its smart glasses.

Kade Crockford, director of the technology for liberty programme at the American Civil Liberties Union of Massachusetts, said the removal does not undo the original decision to ship the code and pointed to it as evidence that consumer privacy needs stronger legal protection than Congress has been willing to provide. The Massachusetts House of Representatives last week unanimously passed a consumer privacy bill that, if enacted as written, would impose strong enforcement provisions including a private right of action allowing aggrieved users to sue. “State lawmakers need to do their job and step up to protect consumer privacy,” Crockford said.

Meta’s sneaky tactics in slipping the face-recognition code into its smart glasses show exactly why data privacy bills need the teeth of strong enforcement,” Crockford added. “Companies like Meta prioritise their bottom line, so lawmakers need to speak in the only language its C-suite understands.” Whether a code removal prompted by investigative reporting constitutes a victory or merely a tactical retreat depends on what Meta does next, and on whether the regulatory pressure building on both sides of the Atlantic produces enforceable consequences before the feature quietly returns under a different name.



Source link