Tagged: chromebook android
January 31, 2019 at 09:34 #21225
I’m evaluating the NoMachine Android app on a Chromebook (Pixelbook), but it runs very slowly. Not just connection or network speed, but drawing the screen and typing feel super slow. The laptop is new and not under-powered by any measure. Is this normal? Is there a better option for using NoMachine on a Chromebook?January 31, 2019 at 10:50 #21232
Hi. What is the Chrome OS version installed on your Pixelbook?February 21, 2019 at 13:06 #21522
I’m running Chrome OS 72 (latest stable version, all updates have been applied). Unfortunately, the Android version of NoMachine currently in the Play Store no longer runs on Chrome at all.February 21, 2019 at 13:15 #21533
Unluckily Chrome OS 72’s new Android is not (yet?) available on all Chromebooks, so this makes the debugging a little bit harder. What do you see when trying to start the NoMachine application?February 21, 2019 at 19:30 #21540
I’m on a Pixelbook so it’s not surprising that I got it sooner. The new behavior is that it loaded fine the first time, and even got past authentication to the NX server. Then it froze when trying to connect to my virtual desktop. Now I can’t do anything besides launch the app; it just shows a black window until I kill it.
Does the web/browser client work well on Chrome OS? The issue I’ve had with other web-based remote desktop solutions is that certain keyboard shortcuts (like alt-tab) aren’t captured, so you can’t use them on the remote end.February 22, 2019 at 20:01 #21568
We have been testing Chromebooks heavily with success. We have found that the speed of the NX client is greatly influenced by the resolution of the screen. HD (1920×1080) is fast and responsive. But when the resolution goes higher, the client gets slow. Plugging in an external monitor at 3440×1440 runs about at 1/2 speed of HD. You can type much faster than it can render the keystrokes.
We also received a tip from support that helped with this:
Seems to have improved speed, especially on higher resolution monitors.February 25, 2019 at 12:24 #21576
The new behavior is that it loaded fine the first time, and even got past authentication to the NX server. Then it froze when trying to connect to my virtual desktop. Now I can’t do anything besides launch the app; it just shows a black window until I kill it.
Could you please check the CPU usage when this problem occurs?
Does the web/browser client work well on Chrome OS? The issue I’ve had with other web-based remote desktop solutions is that certain keyboard shortcuts (like alt-tab) aren’t captured, so you can’t use them on the remote end.
Yes, it does work, but capturing the system keyboard shortcuts is a limitation for us as well. You can work around it by using the virtual keyboard, which is far from being handy but I had to mention it anyway. 🙂February 25, 2019 at 17:43 #21582
@protoclown: if your server is Linux, what you can do is put in a /usr/bin/xterm in Xsession right before your desired desktop appears. That’s a great debugging tool to see what’s happening if you just get the “black screen”. You can then use the xterm window to run the desktop on the command line and watch what’s happening.
I’d be curious to see if your performance got better if you lower the resolution of the Chromebook.February 26, 2019 at 10:22 #21588
CPU for NX goes to zero when it’s locked up. Today I got a “this app has stopped responding” dialog.May 7, 2019 at 08:02 #22233
Is this likely to get resolved fairly soon, or is it a major issue that will take some time to figure out?
Thanks for keeping us updated!June 1, 2019 at 09:23 #21899
To everyone following this topic, we are aware of issues on certain models of Chromebook (it is not limited to Pixelbooks as we previously thought) and we are continuing investigations. Until we are able to reproduce the same strange behaviour which will allow us to open a Trouble Report, we prefer to keep this topic open.
You must be logged in to reply to this topic.