Feature request: Mobile device friendly features

Can we improve KVM access on mobile devices? For example when I acess the KVM through my phone via webbrowser I cant double click, left click or even get my phones keyboard to popup when tapping a textbox.

3 Likes

What do you actually expect to be able to accomplish with such a tiny viewport? Are you going to update your spreadsheet while you 'buy the dip,' bro? /s

Well I don't disagree with OP.

Heres one use case:

When I'm away, I want to startup pc remotely, but my pc has bitlocker or veracrypt as bootloader meaning that all software based remote tools are out of the window.

Once logged in, I loadup my other encrypted steam drive, which also includes password manager stuff hidden in a file container, keeps untouched.

Now I also get 2-3 uac prompts since I don't use root user but a user without admin rights.

Now I can start steam, and finally disconnect to stream via artemis on a tablet through apollo.

Wether it is on a tv, or far further away abroad I can route it through wireguard through a MT3000, it's awesome.

Btw fyi, apollo is a fork of sunshine for remote game streaming, it can spawn virtual monitors which is awesome, then the jetkvm disconnects automaticly.

I agree in alot of situations its useless to use such tiny view, but if you need to prepare stuff then you absolutely want to.

But since the comet is not my main device, I don't know if the suggestion from OP is realistic, basicly it is just a video stream of the desktop simulating a touch canvas on top, things like using the android keyboard won't work, or right click mouse and maybe dragging also not, it would already be better if you could zoom on the page itself, like with photos on phones.

LOL! You're gonna try to stream a vidja game thru a hotel AP but you've not bothered to sync your passwords to your phone, are ya? Get real. Assign the right permissions to your user account, FFS.

... & get off that corporate made malware masquerading as a operating system.

Well, I think I wasn't clear.

Firstly I use the file container unused, of course via phone.

Secondly: I use MT3000 connected as wgclient, there is only access through the tunnel :slight_smile:

But the question remains: do you really do all this game streaming nonsense while abroad? I looked @ Sunshine's bandwidth requirements. Something tells me you don't.

I do, never have problems with it, except if I'm at a place with maybe 100mbps connections, in moonlight/artemis you can lower the bitrate.

1 Like

So you don't actually travel, then. I'm not talking sleep-overs & pajama parties, xize11.

I dont know what your talking about? Anyways I work from LATAM to US using KVM. Sometimes I want to work from my phone and need these features.

I can use my Windows remote computers through AnyDesk, TeamViever, RustDesk from any of my mobile phones (6.67" screens).
They all provide relatively good user experience, the computers can be controlled slower than on big screens, but still can access all Windows features.

I expect the same user experience from a KVM over IP, with the additional feature, that user can see even the BIOS screen of the computer & can RESET even on such hanging computer or Windows blue screen (BSOD) cases, which could not be handled by any software based remote desktop computer.

1 Like

Do you find yourself in a lot of break/fix unscheduled service windows/downtime? There are hardware watchdogs on the market if things are so brittle.

I would like to avoid automatic device restarts in case of a temporary system slowdown, I prefer to keep the decision in my hands.
I had several cases, when I just needed some patience to get back my unresponsive Windows.

same here

We are working on this, please follow us for updates.

3 Likes

There's also software-based watchdogs that can monitor, limit, kill, restart procs based on RTIO, RAM limits, etc. It's an easy way to get 110+ days uptime:

_header
nginx

IDK if any KVM is going to address the underlying problems of a runaway machine.

Why are you advocate against GLKVM?

1 Like

Criticism != against. I own three (3) GL.iNet devices. These aren't toys for me. I need them to work with the same expectation of reliability as my servers regardless if they're 'just' SBCs. I will not put them into production on a client site when left in a stock configuration by GL.iNet.

I know what they're not telling you. Feel free to go through my post history & take a peek.

1 Like