Activity
We constantly build and release new, bleeding edge versions of Haiku for testing purposes. You can download and install these versions to check out the latest features and bug fixes.
Be aware that nightly images may be unstable. Additionally, some packages included with official releases need to be installed separately.
If you're OK with this, you can find further instructions at our Nightly image page.
This report covers hrev60193 through hrev60317.
Haiku used to have coding sprints once or even twice a year. Unfortunately, after the end of the
BeGeistert conference, we have lost the habit of doing that. The previous ones in 2025 and 2022,
organized just after FOSDEM, were not hugely successful, with few people attending or staying for
only part of the week, and, as you can see from the date, they have not been a regular occurrence.
This report covers hrev60060 through hrev60192.
This report covers hrev59922 through hrev60059.
The main news, of course, is that R1/beta6 was released last month. You can read the announcement for more details. Many of the changes in this report made it into R1/beta6 (but not all of them.)
Hello! Finally, GSoC is done for me. This is the final report for my project. The project was focused on improving the Bluetooth stack and making it useful. Hopefully, the Bluetooth stack is now in a much better state than before GSoC 2026. It still needs much work to be fully developed. However, currently Bluetooth mice and keyboards are functioning. In addition, the core of the stack is ready for implementing other profiles.
After about two years since the last beta, and only about a week after Haiku’s 25th birthday, Haiku R1/beta6 has been released! See “Release Notes” for the release notes, “Press contact”, for press inquiries … and “Get Haiku!” to skip all that and just download the release (or upgrade to it from an existing install.)
Introduction
The goal of this post is to document the changes I made during the GSoC period and the current state of the project.
I would also like to thank waddlesplash for his continued support throughout the project.
Progress So Far
RFCOMM Protocol
RFCOMM is now almost ready to be merged. It acts as the control channel required by HFP.
The implementation includes:
- RFCOMM socket addressing and connection management
- DLCI multiplexing over a shared L2CAP connection
- SABM, UA, DM, DISC, and UIH frame handling
- MCC commands
- Credit-based flow control
USB and xHCI Improvements
During implementation, I found that the xHCI driver assumed all isochronous packets had the same size, which is not always true.
The xHCI driver now supports variable-length isochronous packets and processes completed transfers in FIFO order instead of LIFO order.
Hello everyone! As Google Summer of Code 2026 comes to a close, it’s time to summarize the work I’ve done over the summer on expanding the functionality of the Haiku Devices application.
Overview
Haiku’s Devices application previously provided a basic list of connected hardware, but lacked the features necessary to function as a true management utility. My project aimed to transform Devices into a more capable hardware manager, allowing users to view detailed technical specifications and perform administrative tasks directly from the GUI. Over the course of the summer, I focused on implementing new visualization features, improving the user experience, and pulling more detailed hardware information directly from the system.
This report covers hrev59821 through hrev59921.
Hello! The GSoC’s midterm (at least for me) has just passed, so I thought of making a recap post about the improvements I’ve made so far. I’ll try to keep the post brief to make it easier for readers (foreshadowing: I realized that’s impossible :P). I’ve already posted an introduction about me and the project. You can read it here if you haven’t already.
Host-Controller Interface (HCI) Commands and Events
The Host-Controller Interface (HCI) is the specification for how the operating system (the host, in our case, is Haiku) communicates with the Bluetooth controller. The Bluetooth controller is basically the firmware on the Bluetooth chip. So, it’s vital to implement at least most of the mandatory HCI commands and events from the Bluetooth specification for Bluetooth to function properly. HCI commands and events were mostly outdated, dating back to version 2.0 or 2.1, so updating them was the first step to get the Bluetooth stack back to life.
