I tried TeamViewer and VNC Connect with the same (bad) results as now with Armbian. According to my personal experience and information I got from reading their forum, I'm sure they have some unresolved issue there for quite a long time now.īTW: I tried to make it working on my board but different system (Ubuntu 16.04, kernel 4.4.7 from BPI team) one year ago already. I attached my complain to one of them that exactly describes my problems, see here. I found several posts complaining at similar problems in their forum. If someone already assigned the device to your TeamViewer account: Click Extras > Options > Security > under Unattended access, activate the checkbox Grant easy access > click OK.NFC (Near Field Communication) is a wireless technology allows contactless point-to-point data communication between devices within a short distance of 10 cm. It supports three communication interfaces: I2C, SPI, and UART. I tried all the available TeamViewer Host versions for armhf, i.e. This is a Raspberry Pi NFC HAT based on PN532 operating in the 13.56MHz frequency range. Yeah, you are right, TeamViewer should work on armhf. select a default resolution that is not the same as your monitor, save and exit raspi-config and reboot, You pi should now have a default resolution that will be used when you don't have a display connected so team viewer should now work with no display connected. I know it and went it already through earlier.

But it doesn't solve my need for remote access over the Internet, nor the thread you are pointing me at unfortunately. And I use TightVNC server for local access to remote desktop and I'm fine with it for that purpose.

Raspberry pi teamviewer not ready