Haven no longer writes hostnames, usernames or clipboard contents to the device log. If you have shared a log with anyone, it may contain more than you intended — worth checking. 🔒 Haven was writing private details into the device log. Connection details — username, hostname, IP address, port — and, worse, anything copied to the clipboard from a remote session were being recorded in Android's log. A password taken from a password manager, an API token, a private key: if it went through the clipboard in a terminal session, it was written down in plain text. (#518, thanks @skeezmoe) What this does and does not mean. Since Android 4.1 no other app on your phone can read Haven's log, so nothing was quietly harvesting this. The exposure is sharing: the log is captured by adb logcat and by system bug reports, Haven displays it in Settings, and Haven asks you to send logs when reporting a problem — including through the crash-report feature added in v5.87.3. The person who reported this had to edit their own details out of a log before it was safe to attach. If you have shared a Haven log with anyone — attached one to a bug report, sent one to someone helping you — it is worth going back and checking what was in it. Sorry; it should not have been there. Haven still logs enough to diagnose problems. Hostnames and names you chose are replaced with a short marker that stays consistent within one run, so a support log still shows which connection did what without saying where it went. Clipboard contents are simply never logged. A test now fails the build if anyone reintroduces this, in any of the fifty-odd places it could happen. If Haven closes unexpectedly, the crash report is now waiting for you in Settings → Connection log. Fixed a crash that a remote program could trigger just by setting a window title. 🐞 Haven can finally tell you why it crashed. Two open bug reports have been stuck for days on the same missing piece: the crash log stops at the moment of the crash, right before the part that says where. That was Haven's fault. It recorded its log from inside itself, so when it died the recorder died too, and the report the system writes afterwards arrived when Haven was no longer there to read it. Haven now picks that report up the next time it starts, and shows it in Settings → Connection log with a Copy report button. If Haven closes unexpectedly, please open that screen and paste what you find into a bug report — it names the exact place the crash happened, which is usually the difference between a fix and a guess. (#509, #517) Two caveats worth stating. It needs Android 11 or newer; on older versions the system simply doesn't offer this, and Haven says so rather than showing you an empty screen and letting you think nothing happened. And it only covers crashes of this specific low-level kind — the sort that close the app instantly, which is exactly the sort that has been hardest to diagnose. 🔡 Fixed a crash triggerable by a remote program. When a program on the far end set a window title — or sent one of several other routine terminal messages — containing text Haven couldn't interpret as valid Unicode, Haven closed instantly, with no error and nothing to catch. A window title from a Windows console not set to UTF-8 does this as a matter of course. Such text is now shown as � instead. A terminal that displays a replacement character for a mis-encoded title is behaving correctly; one that vanishes is not. This was found while investigating #517 and is not that crash — that one is still open, and the report above is now the fastest way to solve it. Toolbar arrows and other repeating keys no longer stop working after you hold one. The keyboard comes back when you switch back to Haven, instead of always hiding. Three new terminal colour schemes: Campbell, Modern Dark and Modern Light. ⌨️ Toolbar arrows could stop working until you closed the session. Hold an arrow to repeat, tap another one, and the first arrow was dead — it still lit up when you touched it, but nothing reached the shell. Only closing and reopening the session brought it back. (#515, thanks @paour) Two separate faults caused it, either one on its own enough. Haven was reading the wrong field from the touch event, so once a second finger was involved it never saw the release; and the flag that tells a tap from the tail of a hold was cleared in a place that a fast tap could skip entirely. Both are fixed, and the key-repeat logic now has tests covering the exact sequence that was reported — it had none before, which is how this shipped. Arrows are what got reported, but Home, End, PgUp, PgDn and custom symbol keys behaved the same way, as did the equivalent buttons on the VNC and RDP screens. All fixed together. ⌨️ Haven remembers whether the keyboard was up. Android hides the soft keyboard when an app goes to the background, and nothing brought it back — so returning to a session always found it down, even though you left it up. It now restores what you had, and survives Android killing Haven while it's away. (#515, thanks @paour) 🥽 The virtual keyboard no longer covers the screen when a real keyboard is attached. On a Meta Quest 3 with a physical keyboard, every keypress raised the on-screen keyboard over the session. Haven was explicitly overriding Android's own rule that a usable hardware keyboard suppresses the soft one. You can still raise it deliberately from the toolbar. (#511, thanks @sae13) 🎨 Three more terminal colour schemes, for anyone who wants a dark theme whose default text is plain grey rather than tinted: Campbell (Windows Terminal), Modern Dark and Modern Light (VS Code). Palettes taken from the upstream projects rather than approximated. Note that the 16 ANSI colours only apply if "Apply scheme palette" is switched on in settings — it's off by default so that full-screen terminal programs keep their own colours. (#516, thanks @connesc) 📄 Release pages now say what the two downloads are. Every release lists a full APK and a smaller Terminal one per CPU, and nothing on the page explained the difference. Each release now carries a short guide. (#514, thanks @jeyjai)

SSH终端、Wayland桌面、VNC/RDP、云存储和SFTP Android客户端 Haven是一款开源的Android SSH、VNC、RDP和SFTP客户端，内置原生Wayland桌面和云存储功能。 终端： - 支持Unicode、多标签页和6种配色方案的VT100/xterm终端模拟器 - 通过tmux、zellij、screen或byobu保持会话 - TUI应用鼠标模式（vim、htop、mc） - 可配置的键盘工具栏，支持Esc、Ctrl、Alt、方向键、功能键和自定义宏 - 文本选择，支持词语扩展、复制和URL检测 - 语音输入和自动补全 - Mosh和Eternal Terminal支持移动和持久连接 原生Wayland桌面： - GPU加速的labwc合成器，直接在设备上运行 - waybar面板、fuzzel应用启动器、thunar文件管理器、mousepad编辑器 - 入门包含Firefox、计算器、图片查看器 - XWayland支持X11应用兼容 - 多桌面管理——同时运行多个桌面 - 无需root（基于Alpine Linux的PRoot） VNC远程桌面： - VNC查看器，支持双指缩放、平移和全屏模式 - SSH隧道加密连接 RDP远程桌面： - 连接Windows远程桌面、xrdp和GNOME远程桌面 - 双指缩放，键盘扫描码映射 云存储： - 通过rclone支持60多个提供商——Google Drive、Dropbox、OneDrive、S3等 - 浏览器OAuth认证 - 文件夹同步，支持过滤器和带宽限制 - 通过本地HTTP服务器向VLC流媒体 - DLNA服务器，支持智能电视和Chromecast 文件传输： - SFTP浏览器，支持上传、下载、重命名、删除和文件夹传输 - SMB/Windows文件共享，可选SSH隧道 网络： - SSH自动重连、端口转发和ProxyJump多跳 - Tailscale节点自动发现 - 通过rnsh的Reticulum网状网络 安全： - SSH密钥生成（Ed25519、RSA、ECDSA）和加密存储 - FIDO2硬件密钥（ed25519-sk、ecdsa-sk），支持NFC或USB - 可配置超时的生物识别锁定 - 无广告、无追踪、无数据收集 Haven免费且开源（GPLv3）。