---
title: #8: New Flipper One body design
slug: one/dev-log/8
docTags: 
createdAt: 2026-08-10T11:07:55.809Z
---

This is our Dev Log where we share how the development of Flipper One is going.

**In this Dev Log:** New Flipper One body design, key & touch events injection CLI for UI testing automation, and fixes in upstream U-Boot.

***

## New Flipper One body design

We've released a new Flipper One body design (revision B.1). It brings multiple UX improvements and adjustments to support the latest PCB revision. Check out the 3D models:

- [Onshape](https://cad.onshape.com/documents/32ee3b79861e4ff5fe28ee3b/w/8eca0dcb9e92b0271d434028/e/adb36e3c67cc1a734691cf20?renderMode=0\&uiState=699c4c5e57423b4a71d455b8) — the latest model of Flipper One body viewable directly in your browser
- [GitHub](https://github.com/flipperdevices/flipperone-mechanics/tree/dev/CURRENT/B.1) — the latest model in STP format

We announced some of these changes before, as soon as we added them to the future design revision. Now, with revision B.1 released, we'd like to reiterate on them. Let's take a deeper look at everything that was improved.

### Cable channels added to the antenna rail

The antenna rail now has cable management channels for routing SMA cables. The initial idea was proposed by our community contributor, and we've further improved it:

![3D model of the antenna rail's underside showing the new cable management channels](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/LpOtFbYs_LaAVFho-PKLh_antenna-rail-improved.jpg "Antenna rail improved with cable channels")

![3D model of the antenna rail's underside showing the new cable management channels](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/PKQQgNi38aaYgW2_Rbe21_antenna-rail-after.png "Internal and exit cable channels on the antenna rail's backside")

### Snap-fit notches moved to improve durability

Flipper One has snap-fit notches to attach external module covers. In revision A.2, the notches were located on the edges of the back cover and antenna rail, adjacent to the main body. We moved the notches further from the edges to reduce stress on the back cover and antenna rail when force is applied to a module cover.

![3D model of Flipper One's back cover corner with the relocated snap-fit notch highlighted in green](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/nElmlKS55cu-oNu-s-tXX_snap-fit-notch-cover.jpg "Snap-fit notch moved away from the back cover edge")

![3D model of Flipper One's antenna rail corner with the relocated snap-fit notch highlighted in orange](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/kMNWjfemCeEqoQPc1vK2k_snap-fit-notch-antenna.jpg "Snap-fit notch moved away from the antenna rail edge")

### Physical concentric circles on the touchpad

The touchpad was just flat in revision A.1. We've added concentric circles that are nice to the touch and just look good.

![Close-up 3D render of the touchpad with the newly added concentric circle texture](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/dHv-kCjPtSoANn3qR5CfV_touchpad-pattern.jpg "Touchpad with concentric circles in Rev. B.1")

### Loop enlarged to fit Ethernet and other cables

The loop in the top-right corner was enlarged, so you can now push Ethernet, HDMI, and USB-A cables through it more easily. Note that the loop doesn't extend to the right, so you can still place Flipper One vertically, like a walkie-talkie.

![3D model of Flipper One's top-right corner showing the enlarged cable loop next to the d-pad](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/fqXL-f8IIPafPbwF-V3kI_loop-improved.jpg "Enlarged loop for Ethernet, HDMI, and USB-A cables")

::embed[]{url="https://youtube.com/shorts/3yaHPyFixRU"}

### LAN port LEDs made visible

We've redesigned the LAN port openings so that the connector LEDs are now visible.

![Photo of a hand holding Flipper One, showing the two Ethernet ports with visible connector LEDs](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/dPvvAG3CuDaXyx4TQGb92_leds-visible.jpg "LAN port LEDs were covered in revision A.2 and are now visible")

![Photo of a hand holding Flipper One, showing the two Ethernet ports with visible connector LEDs](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/uDN5Eyh88d6MglZskFfSy_connector-leds.jpg "Device prototype in B.1 design revision with visible LEDs")

### Increased the App switcher button height

As we were using the previous version prototypes, we realized that the App switcher button was set too deep and inconvenient to press. We've raised it for 0.25mm, so it's on the same level as the other buttons.

![Close-up 3D render of the App switcher button raised to the same level as the other buttons](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/kbuPpQnlgkDy4RXWiQHXS_app-switcher.jpg "App switcher button raised to other buttons' level")

### Cable channels for the Wi-Fi and BLE cables

The area above the Wi-Fi module now has dedicated channels for Wi-Fi and BLE antenna cables going from the module.

![CAD wireframe view of Flipper One's internals showing the new cable routing area above the Wi-Fi module](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/I8u9T1wUVT7qOcSrrHQaS_wifi-cable-channels-large.png "New cable routing area above the Wi-Fi module")



### Audio jack port moved outwards

In the A.2 design revision, the audio jack 3.5 mm port was too deep in the enclosure, so that some plugs could not be fully inserted. We've discovered and fixed this issue, moving the port around 1.5 mm outwards.

![3D model of Flipper One's side profile showing the audio jack port moved outward](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/AHT0r5Wf5mFsn354a9YVu_jack-port.jpg "Audio jack port moved about 1.5 mm outwards")

### PH screws instead of hexagonal

We've changed the screws used with the Back plate and Antenna rail to PH (DIN 965H M2.5 × 6 mm). Now you won't need a hexagonal screwdriver to open the back plate and install a module.

![Close-up 3D render of a PH (Phillips head) screw securing the back plate](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/4WV9jZacTnyarss5ydhIt_ph-screws.jpg "PH screws replacing the previous hexagonal screws")

### Additional back plate screw

This one is simple. One of the back plate's corners was not entirely secured, so we decided to add another screw.

![3D model of Flipper One's back plate showing the added corner screw alongside the existing ones](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/5TtVOKrW3sZJJ_-VF60C4_extra-screw.jpg "Additional screw added to secure the back plate corner")

## Input emulation CLI for automated testing

A [new Flipper CLI command](https://github.com/flipperdevices/flipperone-mcu-firmware/pull/205) injects key and touch events directly over the debug console, without touching the physical buttons or screen. This means we'll be able to script input for automated tests, instead of relying on someone physically pressing buttons or touching the screen for every test run.

![Input emulation CLI over a serial console, injecting button presses and a touch gesture](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/yZMhXzJ0RitbGx-oElYP1_cli-input-emulation-log.png "`input send` and `input touch` commands injecting key presses and a touch drag")

The `input` command can inject button presses (`send <key> <type>`) and touch events (`touch <type> <x> <y> <pressure>`). In the log above, a sequence of `touch Start`/`Move`/`End` commands traces out a rectangle — and that same rectangle shows up on the Flipper One screen, in the on-device touchpad test tool:

![Flipper One's touchpad test screen showing a rectangle traced entirely by injected touch events](https://api.archbee.com/api/optimize/3StCFqarJkJQZV-7N79yY/y-lx99DlVGhjWKLqTCzMa_cli-input-emulation-gui.jpg "Touchpad Test screen showing the rectangle traced by the emulated touch input")

## Fixing Btrfs-related issues in upstream U-Boot

Contributor @munzzyy helped us fix two Btrfs related issues in upstream U-Boot:

Inline extents compressed with Zstd now [correctly decompress in U-Boot](https://patchwork.ozlabs.org/project/uboot/patch/f6ac2bbdb9b559041cb0c82efccf89ea7262cb43.1785545440.git.Munzzyy1@proton.me/) without hitting an error of destination buffer being too small. This enables us to keep the per-profile devicetrees directory compressed on-disk with the same settings as the rest of the root filesystem without breaking the boot and application of DT overlays.

Generic readdir calls now [correctly fill in the size information](https://patchwork.ozlabs.org/project/uboot/list/?series=516744) for each regular file listed on Btrfs. This helps visually inspect the contents of Btrfs directories with the ls command in U-Boot, and also ensures the EFI boot method doesn't think all files in the filesystem are empty.

***

## Join Flipper One development and make your contribution

- We have tasks open to the community! See the full list on the [🚧 Open tasks](https://docs.flipper.net/one/open-tasks) page.
- Building a project that helps test or improve Flipper One? Add it to the [community projects](docId\:Xqaz9ZzclnBl0Awu3zH6q) page.
- 3rd-party module contributions are welcome! Check out the [contribution guide](docId:0DDVbIoaWJaz2P653X569) and open a pull request in [flipperdevices/flipperone-mechanics](https://github.com/flipperdevices/flipperone-mechanics).

See you in the next Dev Log!
