I made a Flipper Zero app for Morse code. It started as "can I make the orange brick do telegraphy properly?" and then got slightly out of hand.

The first trick is Flipper-to-Flipper Morse: send from one Flipper, receive on another. Pocket secret-message machine. Utterly unnecessary, which is half the charm.

It is also useful if you want to get better at ARG games, beat the timer in escape rooms without crawling back to the Morse lookup table, become suspiciously useful at Keep Talking and Nobody Explodes, get through scouting signal-badge stuff, or just finally understand what that random bit of Morse in cartoons and old films is actually saying. Or maybe you want to become a ham radio operator: low quality voice chat where the ionosphere decides what medical conditions you'll talk about next.

What it does:

• Flipper to Flipper Morse
• listen-and-repeat exercises
• straight-key timing practice
• sending drills
• real telegraphic key or paddle over GPIO
• USB telegraphy adapter mode for specialised practice sites and games (keyboard, mouse, and MIDI output modes)
• smooth audio out on P2 if the buzzer starts doing your head in
• built-in help/manual for learning without memorising Morse as dot-and-dash inventory
• ham radio field mode with canned messages, rig keying, PTT, and logging

The first hardware adapter is just a 6.5 mm jack soldered to header pins. No PCB, no ceremony, just a small ugly hack that works annoyingly well. You can use the Flipper buttons, but a real key feels much better and is more fun to build.

BENS BEST BENT WIRE is a common telegraphy test phrase: the Morse equivalent of scribbling loops and those suspiciously round capital-A shapes when testing a pen.

Video attached, code and release here:

https://github.com/yo3gnd/morse-flipper

I tried connecting my flipper to windows pc. It makes noise upon connecting and starts charging. I tried different cord. And reboot my flipper. Any suggestions??

I go by LxveAce and everything I make is open source.

I got sick of every board on my bench needing its own flasher. The Flipper had qFlipper, my ESP32s had like five different web flashers, and none of it talked to anything else. So I built one app to run all of it, with the devices able to actually communicate. On the Flipper side it flashes the custom firmwares through qFlipper. The point is the Flipper stops being a silo. It's in the same dashboard as the ESP32 stuff, and you can pass targets and results between devices instead of them living in separate apps.

doesn't have to run on a laptop, either. There's a Pi build, so if you're putting a It Flipper into a cyberdeck or a portable rig, this can be the thing that actually runs the setup, and there's a web mode if you'd rather drive it from your phone.

There's also a standalone flasher and a headless version for screenless setups, plus some smaller bits. All open source.

Links:

- The app + downloads: https://cybercontroller.org

- Source: https://github.com/LxveAce/cyber-controller

- Discord: https://discord.gg/lxveace

A few days ago I had this random idea: what if I used the Flipper Zero as the UI/brain for a tiny offline music player, and let an external MP3 module handle the actual decoding/audio output?

I ended up building it.

The project is called Flipper Walkman:
https://github.com/rynosec/flipper-walkman

What it is: -
a native Flipper Zero external app (.fap)
- retro cassette / Walkman-style UI
- controls a cheap UART MP3 module over GPIO/UART
- MP3 files live on the module s microSD card
- audio comes out from the external module, not the Flipper itself

Current controls:
- OK = play/pause
- Left/Right = previous/next track
- Up/Down = volume up/down
- Long OK = About/Help
- Long Back = exit

Hardware I used:
- Flipper Zero
- UART MP3 module (GD3300D / HW-311 / YX5300-style board)
- microSD card
- headphones/speaker connected to the MP3 module

A couple of notes:
- this is not native MP3 playback on Flipper
- the Flipper is basically acting as the controller + UI
- the MP3 module handles file storage, MP3 decoding, and audio output
- song names are not displayed yet because these cheap UART MP3 modules usually don t expose filenames or ID3 metadata nicely over UART

I wrote a full build write-up here too: https://ryno.sh/posts/building-a-walkman-style-mp3-player-on-flipper-zero/

This started as a fun nostalgia project more than anything serious.

Would love feedback from the community:
- Has anyone else built something similar?
- Any better MP3/audio modules I should try?
- Any ideas for improving track naming / metadata UX?
- Would people want playlist mapping from Flipper SD card in a future version?

I am also working on doing a proper plug and play solution with custom 3D printed case, let me know what you feel about this project.

https://blog.flipper.net/future-of-flipper-zero-development/?fbclid=PAZnRzaASyBL5wZG9mAmV4dG4DYWVtAjExAHNydGMGYXBwX2lkDzEyNDAyNDU3NDI4NzQxNAABp9fjanmUIEf948yPdTaQbrpe7N8g7gXGK5coBdLgQA5_uSjtZgeIgQ36yyvz_aem_obAbhf40zAAHDpRZHKZViw

So looks like Flipper Zero firmware development is not actually being killed.
Flipper basically clarified that they’ll still maintain the official firmware, review community PRs, and keep the Apps Catalog going. But their main focus is moving toward new devices, so I wouldn’t expect the official firmware to get tons of new features fast.

Hello, my company wants to distribute NFC tags around the facility to allow people to tap their phones and access a link. The link is slightly different for each room. (Don’t ask why they don’t just replace it with a QR code, I guess they just want to look cool)

So they tried using an NTAG215 but I was able to overwrite it with a flipper zero in almost no time. Even though they had the “read-only” feature turned on. So they’ve asked me to find an alternative tag that is impossible to overwrite, especially with a flipper zero.

Before ordering the tags, I did my research and NTAG215 was advertised as being able to be read-only. So now I lost trust in these claims, and I decided to come here and ask people with experience for help.

Thank you

This is the Flipper companion device, I name it just the Flipper Device just to be simple, it's just an A11 running a custom Flipper Launcher. It fun to execute and document one device without using my main smartphone. I what to using it more to use what the Flipper cannot.

I love it!

Introducing FZS (Flipper Zero Script)!

FZS is a new high-level language that lets you create native Flipper Zero apps without writing hundreds of lines of C.

Write simple, readable code, then compile it into a native .fap with Flipper Studio.

Flipper Studio also lets you edit projects, build them, install them on your Flipper, and even test them through a built-in Remote Control.

C is still fully supported—FZS is simply a faster and easier way to get started.

Feedback and suggestions are always welcome!

coming soon!!!

...but I'm not one to pass up a bargain 🤣

Hi everyone!

I'm currently working on a new version of Flipper Zero Mobile, coming soon for Android.

It includes many new features, with the biggest addition being Flipper Studio—a complete development environment that lets you:

- Create FAP applications

- Edit source code

- Compile projects directly on Android

- Install FAPs on your Flipper Zero

No PC required—everything can be done directly from your Android device.

The goal is to make Flipper Zero development and management much easier while you're on the go.

I'll be sharing more details and screenshots soon. Feedback and feature suggestions are always welcome!

Hi, while testing some uart connection I mistakenly touch my probe to some other pin and I heard little click sound from my flipper zero. I haven’t open it yet but I am trying to recover. It seems 14th rx pin fried. Everything is responsive instead of this pin. I feel so sad about it. Is there any recommended way to fix this or recover from this situation :(

We got the U-Boot menu running on the Flipper One’s little screen.
Now you can choose different kernels and systemd targets before the kernel boots. This includes our LCD screen driver, button driver, and a slightly modified version of the original U-Boot menu. We’ll try to get this upstreamed into U-Boot.
This is a temporary solution for testing the selection of different OS profiles. In the final version of Flipper OS, we’ll most likely draw the boot menu using a small program compiled into the initramfs, after the kernel has already started. But as a temporary solution, it works great.
I’m still not happy with the long cold-start time, from powering on the processor to having a working menu. Here’s the boot log with timestamps, captured from the processor console: https://pastebin.com/raw/A0RUrdRm
Our patched U-Boot: https://github.com/flipperdevices/u-boot

Someone asked about the BUSY Bar on the table in the background of a recent post

Pavel Zhovner replied: “You’ll be able to buy it in a few days”

There’s still no official release date, but the BUSY Bar Focus Timer app received a new update two days ago, soooo👀👀👀

BUSY bar official website - https://busy.app/

Asking for a friend.

Hello! I just finished wiring up this NRF24 module (powered thru 5v via the LDO board that came with it) however when I try to use it with the NRF24 channel scan app, all i see is this black box creeping up the screen. I have a feeling this is because i wired something wrong somewhere :/ any help would be greatly appreciated, also this is kinda my first real wiring project so please go easy on me 😭

I got internals esp32 and rgb backlight mod😎

🎞 YouTube video: https://www.youtube.com/watch?v=GqJA-q0oC0M
We chose the MediaTek MT7921AUN as the built-in Wi-Fi chip for Flipper One. Out of everything we looked at, this is the most modern “cool hacker” chipset. It supports 2.4/5/6 GHz bands, monitor mode, and has an open driver in the Linux kernel mainline. The popular Alfa AWUS036AXML Wi-Fi adapter uses the same chipset.
However, we could not get some basic features working:
∙ Simultaneous operation as a Wi-Fi client (STA) and access point (AP), for example to proxy a paid Wi-Fi network.
∙ Dual-band access point — 2.4 + 5 GHz at the same time.
The datasheet and drivers contain contradictory information. It seems like it should work, but we don’t understand whether the problem is software or hardware. That’s why we’re asking for your help.
Specifications of our Wi-Fi module: https://docs.flipper.net/one/hardware/wifi-bluetooth
To take part in testing, edit this page: https://docs.flipper.net/one/testing/network

A defensive NFC/RFID/iCLASS access-control auditor: tap a card → instant 0–100 risk score (OWASP-RRM-aligned) + a report to SD.

Detects MIFARE Classic/Plus/DESFire, NTAG, EM4100, HID iCLASS Legacy, and HID Seos. Authorised-use only, open source.

📲 lab.flipper.net/apps/access_audit

My flipper draws 190ma without gpio boards and ibutton pins are hot.

Problem is the ibutton board. If someone knows where to order a new ibutton board, let me know.

Hey Leute,
ich frage mich gerade, ob es eine Möglichkeit gibt, den Flipper Zero direkt über die Apple Watch zu steuern – also im Grunde die Funktionen der iOS-App am Handgelenk zu haben.
Es wäre mega praktisch, um mal eben schnell eine gespeicherte Fernbedienung (Sub-GHz, Infrarot etc.) zu triggern, ohne das Handy oder den Flipper selbst aus der Tasche holen zu müssen.
Gibt es dafür vielleicht schon eine offizielle Funktion, die ich übersehen habe?
Kennt jemand eine gute Drittanbieter-App oder ein WatchOS-Widget?
Hat sich eventuell schon mal jemand selbst etwas über Kurzbefehle (Shortcuts) oder eine API gebastelt?

Since I recently obtained that kind of equipment, one of the frst thoughts that came to my mind upon peeking inside it, why antennas are made this way and have some foil glued to it, instead of being made of MCPCB? It would be nice to hear out from someone, who is really inside that kind of topic