How To Make Anydesk Full Screen On Windows 10
Gema Shisila
I am using AnyDesk to mirror a Windows 7 laptop screen onto an Android Tablet. Until recently, everything was fine, but one day, and every time since, I connected as usual but could only see a black screen. I can still see the AnyDesk Settings button, but no laptop picture.
I've found this problem recently. I'm using Windows 10 on a HP Laptop with additional HDMI screen (the problem happend with or without the external screen).After a Windows update the problem appeared, so I imagined the problem could be a corrupt configuration related with the screen or something.I'm using the default HP Energy Plan (Recommended for HP), and fortunately I had another customized Energy plan with some parameters changed, and after changing it it worked fine.Let me explain what is the parameter responsible of the black screen issue.
It's happening when an RDP session is minimized or you're signed out. To make anydesk available as a service you need to install it rather than running as exe. When you run it you'll be seeing an option "Install Anydesk"
I had this issue in a Chromebook, and turning off Night light under settings > Device > Displays resolved my issue. I knew it was a problem with chromebook because I could otherwise connect to anydesk from another client computer and also from my mobile. So watch out for color correction feature on different client machines!
At least, it is my case.. :) another solution is using connecting by user account, then you put the user and password and you are in. I think it is also the case if more than one user is logged in the machine. Anythesk then doesn't know which desktop to connect.
Not true. While it's true that it's not accessible to us on the host side, we *can* start it and accept inbound connections, although the button to do that is hard to find because it's in among a lot of other things on a split screen. Access for Music makes use of Anydesk when helping its clients and customers with tasks a screenreader can't handle (see for more info if interested).
If I turn on my computer with the monitor off, the TV remote resolution is stuck at 640x480. There are no other resolutions offered. All I have to do is turn on my monitor and the remote resolution instantly changes to 3840x2160 (what I want).. The behavior occurs with my Windows laptop, iPad and iPhone.
Good news. The behavior is exclusive to the display port. Last night, I connected an HDMI cable to the monitor (disconnected DP) and the problem is gone.Now, I can leave the monitor off, boot the computer and get 3840x2160 remotely. Would prefer to keep the display port connection, but this will work..
Please be advised that unfortunately, TeamViewer is getting the resolution that the Windows OS on the PC is offering, and that usually depends on what Windows is able to gather regarding the monitor that is connected to the system, therefore, if the monitor is not being recognized when it is off, Windows won't be able to offer other resolutions to TeamViewer.
You could alternatively try to install, if available, the drivers for the 4K Monitor, and then try to update it on the Device Manager so that it is recognized correctly by Windows, and not as a standard monitor. This way, it would be possible that Windows assumes the resolutions that the monitor is able to handle even if it is off, although, we cannot guarantee this.
As AMD said, without a monitor attached, windows does not know what resolution to offer and we do not have the ability to force non-native resolutions. You need to find some way of forcing the OS to create the correct resolution.
This is definitely a software/driver based issue. Some update recently for me now cause the resolution to not only change, but reverse (eg: 1080x1920, 480x620 etc..) when my display (a TV in my case) was powered off. It almost looks formatted to fit on a mobile device?
Regardless, I deleted the driver (uninstall software option checked) and let Win10 use a generic driver and the problem was solved for TeamViewer. Granted I can't scale it properly on the TV with the software, but my remote session are now in 1920x1080 regardless of display power state.
The solution is that to connect a real monitor to the headless machine. Then the OS will see it. Then in the device manager you have to update the basic monitor (not the display adapter!) driver, just takes a minute. After that everythink will work. At least in my case.
What I did more is to bring all windows 10 machine to the latest windows 10 version actually to 1903. It can be important too, because of there were windows update issues with the RDP (Remote Desktop).
As I understand this failure regarding to usually AMD video cards, because of if there isn't a real monitor connected, then it sends somewhow just the basic, lowest resolution display, what will be later captured by Teamviewer or other remote desktops solutions. In our case the video card was a AMD FirePro.
Not an AMD specific issue, but what I noticed is that nvidia cards don't have this problem. I purchased 5 computers and connected them to network for remote configuration. 4 have AMD RP WX4100s and one has a quadro P1000. The quadro allows me to go up to 4K remotely with no monitor attached, and both cards have only 4 mini DP ports on them.
I don't use my remote system for anything other than mocked endpoints and proxying network traffic for development. Without the need for any robust video solution I was able to simply disable the AMD Radeon RX video card in my device and let the default Windows adapter handle the video. 2 benefits: 1) the resolution now defaults to 1024x768 and 2) there is no hardware acceleration so I'm not constantly presented with a black screen and having to hit refresh and/or (un)remove wallpaper in order to get the screen to stay up to date.
I just wanted to post here for anyone who might need a real solution to this problem. I run a headless Windows 10 server that has an NVIDIA Geforce 1050 Ti on my home network, so it's not only an AMD problem, and it's not only a display port problem because my system doesn't even have any. The other posts give helpful information, but no solutions without having to buy a dummy display emulator. There are software virtual monitor emulators which I don't think were even mentioned, and some of them do not offer high resolutions, so they are not all created equal.
There is free software called Amyuni USB Mobile Monitor that I found that took seconds to enable, then change the resolution in Windows Display settings, and the Teamviewer problem of showing 640 x 480 resolution was fixed. The post by the author of the software is here and has instructions and explains everything and has the link to download.
I am fighting with some remote control applications such as teamviewer or anydesk. In each case I can not get my laptops to be a server. I would like to be able to get a remote display (or control) to any other linux machine or android smartphone.
I got too much issues on my system with teamviewer and am now trying hard to get anydesk working.
some precisions:
- I observed this behavior on 2 different machine with same system
- anydesk works well as a server on an other machine with manjaro, so I guess I am missing a package or have a different config somewhere
- I installed and started the xrdp.service, no change
Indeed, anydesk run perfectly with Manjaro (KDE) and not on my system, so I guess a DE or something like this makes it working.
Do you have some advices on how I can find what is wrong with my session type?
Regarding the Manjaro part. No the actual DE is irrelevant, it matters whether your session is properly populated, if you use a display manager they will usually invoke relevant integrations with systemd themselves.
Hi 2ManyDogs,
Sorry for doing that. I have already searched during many days and am pretty sure there is a solution somewhere and you guys can help me. So, what am I supposed to do? (it's a real question)
Then I performed lots of tests. I do have the same issue with a new fresh user.
I tested another DE and a display manager.
KDE Plasma works fine but still have the same issues (remote control issue, xrandr, notify-send no effect with sudo)
V1del suggested me a DM, I enabled sddm.service and removed the autologin on systemd.
Then, I got a black screen at boot with the booting messages on the consol and a mouse that can move. But I can not do anything.
There is the Xorg.0.log corresponding at this attempt:
Yes you are not supposed to be able to use these commands with sudo plainly like that, they will not have the dbus session of your user available, nor the X environment of your users xorg server. In case this is actually relevant, you should not try to sledgehammer problems by prepending sudo to commands willy nilly, that will often not lead to success. Are you trying to run the standard anydesk client as root despite not needing to? Then just don't and this also would explain your issues.
I'm not familiar with anydesk, but e.g. in the case of teamviewer there is a systemd service for starting the background daemon, once that is started the actual teamspeaker client has to be launched as your normal user..
About anydesk, I run it as my user on my normal seesion, I precise that I can connect to another device from my system but I can not in the opposit way, e.g. I can connect to my android smartphone, but not the opposit.
d3342ee215