Anyone having success with Gemini 2.0 screen share?

Gemini API
1

It’ll work perfectly for the first five minutes of use, but will ultimately lock up…every …single …time I use it - disconnects, stalls, freezes

3

Hi @alexaaaaaander , Welcome to the forum.

The session duration is restricted to a maximum of 15 minutes for audio or up to 2 minutes for both audio and video.

Kindly refer the documentation link below for the limitations of Multimodal Live API.

Link

Thanks!!

1 Like
5

that’s a bummer, but I guess it clears up a lot of my questions… anyways to work around it or expectations for an update??

7

Yes. Here
In Gemini 2.0 the video feature works and also the share desktop also works. The main problem is, the Ai using tensor flow does not engage with your personal desktop, rather, the Ai in use is being borrowed from a device within Google so that you can test drive the Ai. Seriously, that lame.

So when tested, the Ai Gemini 2.0 will respond about what it is looking at as a blind dongle and will not report anything to do with your display. It is not tensor on your display because you are borrowing it as a display. Does that make sense? I tested this extensively and 100% of the time the Ai will respond to what is on their own display and not what I am showing it.

8

Makes sense, but I’m not having issues with what Gemini 2.0 is looking at/interacting with… it’s that it times out and disconnects after 10-15 minutes of use. I’ve been trying to use it to “handhold me” across some coding and network configurations with Stable Diffusion, but working under that time limit of functionality makes it kind of pointless

9

Its still the same issue, even when you glimpse at what is really going on here you figure out in the end that the idle timer is set at 1000ms on the server side but, the way the client login is managed is through a device that is a standalone capture port set to intercept the attempts of hackers. In other words, there is a box in front of the server that is handling logins that transports users to the server rather than an open face of the server being made publicly available. Alright so the idle timer is not set on the server but on the login pre-cursory device. At this point there is pretty much nothing you can do on a browser to avert this.