what is anland fr?

Anland Display Protocol V3 is a low-level C library and set of binaries that let a Linux desktop compositor share its GPU-rendered frames with an Android device over a Unix domain socket. The practical use case is displaying a Linux desktop on an Android screen in real time, without going through a network connection or video encoder. The system has three components. A small daemon process sits in the middle and brokers the connection between the other two. The producer is the Linux side: a compositor like KWin or Weston renders the desktop into shared GPU memory buffers. The consumer is the Android side: it owns the GPU memory, allocates the shared buffers, and presents the frames to the display. Because the consumer controls the memory, it manages all the file descriptor passing between processes using a Linux feature called SCM_RIGHTS. Version 3 adds bidirectional clipboard exchange, which V2 did not have. Both the producer and the consumer can now push clipboard text to each other over a data channel. This involves a variable-length message format: clipboard events have a header followed by a payload of varying size. This is an intentional breaking change from V2. A V2 client that reads fixed-size events will leave leftover bytes in the socket buffer after a clipboard message, corrupting all subsequent messages. Callers upgrading from V2 must handle or drain every event type, including ones they do not use. Communication uses four channels: a control socket to the daemon for the handshake, a data socket pair for events and clipboard content, an eventfd for signaling that a buffer is ready to render, and a socket pair for the render-done fence. The daemon socket lives at a fixed path on the device. This is a niche, systems-level project targeting developers who work on Linux-to-Android display bridging or compositor backends.