| Pronouns | he/him |
| Web | https://raqb.it |
| Github | https://github.com/raqbit |
It can be a draw when setting up a new device. Some info transfers, while some don’t. Learn how developers can ensure the best user experience when people backup and restore an Android device. Hosts Tor and Chet are joined by Graham and Piyush on the Android Consumer Experience team and Alon on the Android Studio team to discuss Android backup and restore. Chapters: 0:00 - Introduction & the user pain point 1:38 - Why backup fails: Developer challenges 4:00 - Evolution of backup testing: From scripts to Android Studio 7:15 - Beyond testing: Backup for developer workflow 8:50 - Cross-device backup & GMS core integration 10:55 - Understanding backup types: Devices vs. Cloud 14:55 - Data categories & developer control 16:05 - System-level backup: Permissions & credentials 18:35 - Default backup pitfalls & key-value agents 28:15 - Database migrations & backup stress testing 32:04 - Automated testing framework 41:02 - Recap & feedback channels
@dirk @kernellogger As far as I know HDMI 2.1 enables 4K 120Hz and 8K 60Hz output, as well as variable refresh rate (VRR).
The first two may not be interesting for the Steam Machine, but the last one would be.
@cnlohr As far as I know, all the main developers working on X11 are behind Wayland, and X11 itself is slowly withering away.
Waypipe is often the suggested alternative for X forwarding. Whether running nested compositors is supported depends on which compositor you run (but the Wayland protocol itself supports it)
