Posted by sandebert 5 hours ago
However, I don't think they need to be prioritizing the local AI features, which are cool...but models get far smarter when you run them on a proper Mac/external GPU vs a small battery powered Flipper device. I think it might be helpful on the go, in the field, etc, but the usability with no dedicated keyboard will be rather poor.
However, I think they should keep focusing on the Zero for a possible Zero 2 to match the capabilities of this One device. I love my Zero, but I think it is missing key features like full support for garage door and RFID rolling codes, and some other protocols. The WiFi dev board is very limited, and there is no simple way to capture/playback BLE remotes IIRC. Of course, it depends on whether you consider BLE to be layer 0 or layer 1.
Are they upstreaming opensource HDMI 2.1 support? I mean I'm sure they're not, since they paid the toll, just feels they're not totally sticking to their guns. It's the kind of choice that shows if you really mean what you say. The more that won't license, the better chance of actually getting open drivers for common technology.
None of this takes away from how awesome this looks. Very excited by all this.
I sincerely hope I work out a way of getting someone else to buy the thing for me. And the push towards all in-tree source is fantastic. Genuinely impressed.
sewing and maintianing clothes was one of them, for example, so thats why it has a punch. They'd need to be able to open cans, as that was the most common long term ration, and they'd need to be able to maintain their rifles which had screws, thus screwdrivers.
a version with a wine bottle opener was made for officers and became common
To me it seems like the opposite, it has more connectivity and I/O than the Zero, but also scaled down, while using better materials, like they decided to outsource the project scope creep to the community, which makes sense to me.
Scope creep to hell and back. Could just let the device get turned off like literally any other device on earth, and not have to build a whole new fucking OS to get it running.
They even - for some reason - want to waste time "training their own AI model because general ones don't cut it" (which no one is likey to use). Could just build a normal RAG + context stuffing pipeline in an afternoon but nah, let's devote a few months to this completely unnecessary non-feature.
100 bucks say this doesn't see the light of day before 2030 (if it ever does!)
This is actually quite common in embedded devices and even elsewhere. Every Apple device does this, for example (the Secure Enclave is a completely separate OS running on a separate computer).
If you think about it, most laptops have been doing something like this for decades as well for things like brightness control etc., not with a different CPU but definitely an OS-like thing (i.e. the BIOS, using SMIs etc.)
The idea of the "single OS, single CPU computer" has been a myth for a while now.
At least since they started running Java on SIM cards.
Also why would you want/need someone else to purchase it for you? Because of your country's import laws, or reasons related to privacy/anonymity?
First one is simple and focused, the second one tries to be & do everything. And frequently never ships.
Their TUI[1] is planned to use react(!), to share logic with their BrowserUI[2]. In the repos you can see how they struggle to get anything gpu backed done (which is required by the browser). Then falling back to wayland to do it for them. (This all seems a mess that LLMs can't figure out.)
Anyway, it does seem to end up in a custom linux desktop environment, with lots of sharp edges that makes it less hackable.
[1] https://docs.flipper.net/one/cpu-software/flipctl [2] entirely unclear why a terminal is insufficient for networked TUIs
First time I've heard anyone call the Flipper Zero "simple" and "focused", most people seemed to have considered it a "swiss-knife" meant to just house a bunch of features and radios, meanwhile the One has less features but more connectivity and I/O.
But apparently you're not alone in feeling this, but I don't understand what from the submission makes you and others believe so, what exactly gave you this impression?
And this one is an 8-core Arm computer and the project has ambitions of some notoriously difficult things: no binary blobs, full mainline support (including a NPU), reinventing small-screen UI for more serious handheld computing, and supporting a ton of high-bandwidth interfaces.
This is not a simple step up in difficulty.
The "custom os" part could also be done easilly enough with the correct approach.
Specifically systemd has a less-known feature known as system extensions intended for basically exactly these sort of scenarios. These system-extensions are basically disk images containing files in /usr and/or /opt that can be dynamically overlaid on the existing filesystem (the intent is that these are purely additive). Systemd also intends that all os provided configuration live in /usr, with /etc existing only for machine specific or admin applied configuration. (And which should enabling overriding anything specified by the package or OS.)
System extensions when used default /opt and /usr to be read-only, but you can enable mutability if you having write routing directories or symlinks in the right spot.
So for userland this whole os profiles things could literally just be a set a of system-extensions, a distinct /etc folder, and distinct set of write redirect directories for each. An initramfs can simply bind mount the /etc directory, and add the correct write redirection symlnks before systemd starts. Rolling back a profile is simply wiping its write redirection and /etc folders. If you also want each to potentially have distinct device trees and/or customized kernels, that would need additional bootloader work on top, but nothing that feels too extreme.
Now in reality, since not everything support systemd style configuration, these OS profiles would probably need to construct an initial /etc by copying files from a base-os template, and then copying in anything included in the system extension images (which can have these as systemd will ignore such folders), but that is straightforward enough.
Don't underestimate the value of that integration.
With the hybrid architecture chips you get the vendor controls for managing the MCU with supporting documentation. ST is good at this.
This isn't the same thing. It's two chips running side by side. It's possible to set it all up so that the Linux chip can control everything you need to manage the MCU, but it's not easy. There are a lot of edge cases to think about and things that need to be handled manually.
Going with an SoC is much simpler than trying to set up custom communications between two processors, I'm not sure why they didn't think of that.
On the other hand, this has been working pretty well for the first few Raspberry Pis! (Although they had the benefit of leveraging an existing smart TV based platform for that.)
There's a big category of tools that people buy because they're cool and feel like they come with limitless possibilities, but then end up in a drawer. Raspberry Pi became this for a lot of people. It took a lot of years and a lot of market saturation before everyone realized that they're not a good deal if you have a specific need for a general purpose computer, despite their usefulness for specific applications.
The Flipper Zero felt like a tool with infinite possibilities, but it takes a while for most people to admit that they don't have infinite needs for a product and that application-specific hardware can often do a better job for less. But it's a cool product and it had a lot of viral marketing going in its favor.
They design a completely new product and suddenly announce a collaboration?
Not a fan but the new project looks cool.
Examples: - the cellphone (obviously) - my TV - my refrigerator - my oven - music players - tablet computers - laptops (well on their way) - cash registers->PoS sales machines - handheld game consoles
Carcinisation (https://en.wikipedia.org/wiki/Carcinisation)
The same seems to be true for trees too (arborescence).
The (EDIT2: maybe not) AI writing doesn’t help.
EDIT: looking more, it seems like the goal is to be a fun project like Playdate, except a Linux multi-tool instead of game console. Which is actually great, a step towards healing today’s corporatized tech culture. It’s unfortunate that the website non-explains this with AI and marketing speak.
EDIT2: I wrote too soon, AI is making me too cynical. My only remaining critique is that they explain the motive instead of just stating features and repeating “we’re doing something exciting and important [for reasons not really explained]”
They work at different layers, the Zero is physical, the One is network. There is almost no overlap between the two, so one doesn't have an advantage over the other.
> RPI
It has a battery, with attention given to power management, and is a complete unit, not just a board.
> Linux machine
You mean like a laptop? You can probably do all this on a Linux laptop PC, but the Flipper One is a smaller, more specialized device, with a firmware as open as the manufacturers will let them.
> My only remaining critique is that they explain the motive instead of just stating features
Go to this page for this: https://docs.flipper.net/one/general/features
As a current Zero user, I'd definitively get a One once available, just the addition of the PTT-button feels worth it to me, but almost all the other changes are good (IMO) as well, don't really see any drawbacks from the design they're aiming for now, besides the modularity will make things slightly more complicated, but also comes with a ton of obvious benefits.
What am I missing? What do you use yours for?
Mostly around debugging and troubleshooting networking (WiFi+Zigbee network) at home, which the Zero is nice for this as it's easy to bring with me to any area in the house/yard and test stuff wherever. I used to use a laptop+radio for this, but I no longer have any laptops and the Zero does the trick nicely enough.
I also tend (try) to duplicate any keyfobs/cards I come across too, as backups, which helped me just the other day as we've lost the card we got for the municipal trash, so now I'm using the Zero to unlock them as we still haven't recovered that card.
Some months ago I used it for moving a bunch of AC+IR remotes to be connected to my Home Assistant installation by first reverse-engineering the IR protocol then building my own hardware for it with a little IR transmitter, now I can remotely control the old AC unit regardless of where I am in the house. I'm pretty sure it's a fairly standard protocol I didn't need to reverse-engineer myself, probably well documented on the internet already, but way more fun to do so yourself.
If I didn't have the Flipper or some other SDR device I'd probably have assumed it was bad and left it at the recycling station. If I'd lose the original remote I can use the recordings on the Flipper to either control the sockets or create a new remote.
I've also looked into how the key fob to my car works and investigated tens of RFID and NFC cards, some of which I could probably have talked to with my phone but I like the format of the Flipper and it has very few distractions except Snake.
When traveling I sometimes bring it up just to check out what radio stuff I can find and think about what devices might be sending.
Why do you say there is AI writing?
> Flipper Zero and Flipper One operate at different protocol layers [below a graphic with features like "Power Bank". Do they know what a "protocol layer" is or do I not?]
> Flipper One isn't an upgrade to Flipper Zero — it's a completely different project with its own goals.
And lots of em-dashes.
But looking closer, I actually suspect it’s not AI, the author just integrated LLM-isms into their style.
Also, what's a "survival desktop"? I've never heard that term and I couldn't find it used elsewhere.
Flipper One's hardware designs and constraints are very compelling. I would have preferred an additional physical switch to disable all emissions.
That said, if they can pull of the initial software stack it will be a strong platform for a broad set of use cases.