![]() ![]() There’s lots of VNC clients available in the Raspbian repositories. Popular ones such as VNC Viewer (realvnc), Remmina, TigerVNC, TightVNC, Vinagre are all present.īut the host Windows machines only had TeamViewer installed, and I never force ‘alien’ software on my (dinosaur) mates. TeamViewer offers remote access to a wide variety of operating systems including Linux distributions. It’s proprietary software, so you won’t find the source code available. #Remote control raspberry pi teamviewer code But you can use the software free of charge to access private computers. For the RPI4 (and earlier versions) TeamViewer is only available for the RPI4 in a host edition. This means that the software is designed to receive connections and act as a server. Unsurprisingly, TeamViewer isn’t present in the Raspbian repositories. Point your web browser to the download site and grab a package (.deb) for TeamViewer Host for Raspberry Pi (it’s somewhat tucked away on the right hand side of the page). There’s a few more jumps to clear before the software is ready to use. Choose a password, connect the device to your TeamViewer account, accept the license agreement, associate your RPI4 with your TeamViewer account (you can connect via the TeamViewer ID instead), grant easy access, and assign your account. My friends already have TeamViewer running on their Windows machines. Connecting to my RPI4 was straightforward. To start with, I opened a terminal remotely on the RPI4, and ran top. On the host machine (RPI4), CPU usage is minimal when the host machine is idle. The software consumes about 7% CPU of 1 core for the TeamViewer_Desktop process, around 2.6% CPU for the TeamViewer daemon, and less than 1% for the TeamViewer process. ![]() Here’s the memory consumption for the 3 processes:Ī pretty hefty memory footprint. I wouldn’t recommend using the software on the 1GB RAM model of the RPI4. #Remote control raspberry pi teamviewer software Interactivity with the RPI4 host was very good even with 2 monitors running at 2560×1440 resolution. I tried various custom settings ranging from the highest quality (colors set to true color and quality set to highest quality), to the quickest setting (grayscale and the quality slider set to highest speed). Dragging windows around the desktop is a bit laggy even with quality settings set fairly low, but that’s more of a limitation with remote ‘desktoping’. For example, simply moving a window around the desktop consumes almost the entire CPU of one of the 4 cores. There’s no noticeable lag navigating desktop menus, and performing basic GUI tasks such as moving files between directories works like a charm. Of course, if you tax the X server (Xorg) to any significant degree, interactivity isn’t perfect, but again there’s always limitations with remote desktops.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |