What’s Bullseye going to do in 2021? There are no many noticeable improvement in the UI. But some improvements have occurred, for better and worse. Unfortunately, the new OS doesn’t work with libraries, which means that some existing projects and products are useless until developers have time to update their software. Some members of the Raspberry Pi community were infatuated by Bullseye. In a forum thread we see a problem with the new KMS video driver, which arouses certain resolutions. RPi trading got panned for making an alpha-grade PiOS released by people who depend on PIs for doing important work. RPiT should change some of its development processes, that might have been quite a bit late, but still resembles amateurs.November 12, 2021 – 2021 See more Bullseye is being seen as curiosity for now and not driving as a daily driver. If you have mission-critical projects, stick to Buster as it is tested with two years of updates and improvements. All your cameras and computers will work with Buster, as well as Bullseye might be the last to enable the software developers to do the same for the time they have to update their drivers, so many have not.

What’s new with the Raspberry Pi OS Bullseye?

The new window manager, Mutter, works only on Raspberry Pi models with 2GB or more RAM – Raspberry Pi 4, Pi 400, and Compute Module 4. Other Pis use Bullseye, even the old window-manager, Openbox. In the words of Simon Long, the director of Raspberry Pi OS releases Mutter is what is known as a compositing window manager, which means that instead of individually drawing the frames directly onto the existing windows on screen, it can draw all the windows to a memory buffer, where it creates an entire image on the whole screen. I was able to display the hardware. Using Mutter means that Raspberry Pi OS can finally add a little visual flair and special effects that Linux users have used to for a long time. Since we rebooted the Pi, we first noticed the new twist that was taking on the reboot window. Finally, we noticed that with 4GB of RAM, window management and open / closing speed were much better on our Raspberry Pi 4. Why do you change the manager of a window? A new feature introduced in this release is GTK+3, a user interface design kit that builds multiple applications’ components. The move to GTK+3 is a bit new to Raspberry Pi, but not to the larger Linux community. The Raspberry Pi OS versions used GTK+2 with some tweaks that were particularly effective for the Raspberry Pi. With GTK+3, we noticed a good look and feel, with some components like tabbed menus appearing slightly different. The Raspberry Pi OS team went to a great length and ensured the user interface was an equivalent to the previous release, and so some changes to the GTK+3 are hidden from view. 1 of 2 photos. 2 image of 2 Bullseye has developed alerts. The icon in the right corner of the screen shows them in chronological order, so that they will not turn into a ether. Give it a go, plug in a USB stick, then take it out, before unmounting, and you’ll get told off. Application built in works directly with the new notification area, and the application that was created can also be easily integrated. I think that the update plugin on the top right of the screen was a misstep by the user. The updater is a simple tool to update the software to your Raspberry Pi. It’s a little difficult for Unix–Linux users, but for the core demographic, learners, it’s a matter of luck to ensure that changes are timely and easy. The Pi checks the latest updates once it boots. Image 1 of 3. 2 of 3 images. 3 images of 3:20. I’m adding an update to the Chromium browser, too. Using the Raspberry Pi hardware acceleration, Chromium will also accelerate streaming video. YouTube is a great tool. With older Raspberry Pi OS releases anything above 720p is a slideshow, and full-screen 720p isn’t a good experience. With Chromium 92, we find that 720p video, windowed and full-screen, plays back exceptionally well, with only one percent of the frames dropping. When we played a Big Buck Bunny test video, we saw that 1080p 60 playback was still poor. It wasn’t a complete slideshow, but it wasn’t there, that isn’t that impressive. Nevertheless, the 1080p and 30 playback was very good. YouTube showed some frame drops in its Stats for Nerds menu, but we didn’t notice any disturbances with our naked eyes. Theoretically you may get the benefit of Chromium 92 on Buster as the new browser will install in the old computer. However, when I was testing, YouTube crashed on a loaded URL. That’s a bad sign. All kinds of browsing on Chromium 92 in Buster worked well, bbc.co.uk loaded flawlessly with a full-body experience. We ran Chromium via the terminal. To understand all the problems we had, we received a message with reference to an org.freedesktop.UPower service that we assumed that is automatically in Bullseye.

Performance of Raspberry Pi OS Bullseye vs. Buster.

When we test my Raspberry Pi 4 with 4GB of RAM, we put Bullseye and Buster to work and set the time to create a supercomputer. Buster is the clear winner, clocking in at 21.84 seconds, which makes sense since the older OS, has seen a lot of changes and changes to the boot process. Bullseye pushed up at 28,48 seconds, a delay that we were able to really feel. In order to identify how Bullseye runs applications, we opened a new chrome browser to a blank tab. Bullseye completed the task in seven92 seconds, while Buster performed it in seven74 seconds. Between the two, the difference between them is very small, that is not noticeable either at once or at all. Bullseye comes with a boost of speed for newer Pi 4, though on the bright side. The Pi4 has developed the Raspberry Pi 4 from the early generation so we don’t have any comments about the automatic speed boost, but we have conducted extensive overclocking experiments with the Pi 4 and found that with sufficient cooling, it’s easy to overclock the Pi to 2.14 GHz. The clock called Bullseye is an automatic transmission, which has built in the Pi 4 to 1.8 GHz speed, and the Raspberry Pi 400 is the same speed, and the new Pi 4 is in constant succession with the new Pi 400.

Where does Bullseye miss the Mark?

Without the GPIO (see Raspberry Pi pinout), the Raspberry Pi is a small Linux computer. The Raspberry Pi is a great example of the GPIO and the numerous opportunities that it offers us. We can build many kinds of Raspberry Pi projects with connectivity to electronic and add-on boards. Various approaches include simple robots, complex machine learning or computer vision applications. All of these come using the Raspberry Pi and many computers. We tested a Sense HAT, a Raspberry Pi board that worked with no problems. We compared two third-party boards: Pimoronis Explorer HAT Pro and the RasPiO Analog Zero. The Explorer HAT Pro has been around since 2014 and is an excellent board for projects. We’ve used an Inside-Bash script with Bullseye, and everything went well, until we had the included test script, which failed. After a little investigation, we traced the fault to I2C; normally this is enabled during the install process, but not with Bullseye. We used raspi-config to set up the I2C interface, and then went back to the prototype. We got a false error and encountered an update that relates to the ADC converter – Explorer HAT Pros. The new error had nothing to do with Bullseye. But this was a problem, both with the ADC library and Python 3.9, which were eventually completely deleted by their developers. However, there are still a lot of other HATs that need software which hasn’t yet been patched. For example we tried Adafruits Braincraft HAT, but it wasn’t expected to install because of the dependency issue. There is still no definitive list of boards that aren’t compatible with Bullseye. Over the coming weeks the number of boards with problems will gradually decline. We asked for an upcoming test. Analog Zero, from Raspio, is a solution for a MCP3008 ADC which connects to the Pi via SPI. After opening the interface via raspi-config, we opened a Python REPL and then went to Analog Zero using a ready-made tool.

Camera using tomeye.

Raspberry Pi customers will experience raspistill and raspivid, both terminal commands that take pictures and record videos using any camera that’s connected to you, including the Raspberry Pi HQ camera. For Bullseye, these commands have been replaced with libcamera, with alternative options, with the same syntax as raspistill and raspivid. The similarity is welcome as we can easily turn the commands out in our Bash-based camera script. There’s another camera related omission, and that’s PiCamera. PiCamera has been created by Dave Jones for many years since the de facto use of Python’s official camera. With Bullseye we lose PiCamera and with it several new projects have been broken, including many of them created by the Raspberry Pi Foundation, which is the educational outreach arm of Raspberry Pi. If your camera project is a Python powered project, then stick to Buster until PiCamera is offered.

Final Thoughts

Bullseye is a great release. It built on the foundation that Buster laid down and gives us the latest generation of Raspberry Pis, better suited for now higher-spec Raspberry Pis. A new chromium web browser has an impressive display performance and is almost comparable to a budget laptop. In our excitement, we have to be patient. If your project is dependent on the HAT or the Python Raspberry Pi Camera Library, then you will need to make sure your HAT is supported. We’ll wait for an updated PiCamera library to get started. If you need to deploy your project now, go along with Buster. Third party software and new HATs are currently being updated, but developers are playing catch up.