Glad to see development continuing on this. The jump from the Zero's microcontroller to a Linux environment opens up a lot of possibilities, but battery life will be the real test.
Flipper One – we need your help
461–470 of 501 posts
Re: Flipper One – we need your help
#462Can I use this tool to measure bit errors in high speed USB communications?
Re: Flipper One – we need your help
#463So basically this is:
"if we can make this project work with all of this software we could sell it for a ton of money, but we cannot make it work... so come do parts for free for us so we can profit"
a huge part of the problems they have are issues they set for themselves, they picked the hardware first and are now trying how to make it work, usually when making a hardware product you start backwards from which hardware you can actually support and then pick from there... rather than expect someone else to solve your problems....
if they would opensource the hardware and all of the software, I'd agree with the request for help... but they seem to want to have the cake and eat it too...
Re: Flipper One – we need your help
#464Re: Flipper One – we need your help
#465Almost feels like they should just build a dongle of sensors that can plug into existing Linux systems, such as a Steam Deck, laptop, or desktop. It's almost as if people are walking around with screens and batteries in there pockets already. It's too bad they can't just make it plug into an Android phone
Re: Flipper One – we need your help
#466Earlier quoted context omitted.
> The 256×144 px screen requires pixel-level rendering, which standard TUI libraries (ncurses, etc.) cannot provide. The proposed solution is an HTML/CSS rendering engine running as a background daemon — a lightweight browser-based renderer that draws menus, popups, and UI components. Truly, a design only an LLM could love.
What's a design an LLM would _loathe_?
Anything invented after 2024?
Re: Flipper One – we need your help
#467Sounds like the second system effect. (The Mythical Man Month) First one is simple and focused, the second one tries to be & do everything. And frequently never ships.
They're very explicit that Flipper 1 isn't a "v2", but a device that targets different use cases.
Thats terrible marketing then. Trying to leverage an unrelated device because it was popular is almost guaranteed to spurn those expecting the next flipper to be an improved flipper, not a "not-a-flipper"
Re: Flipper One – we need your help
#468Earlier quoted context omitted.
The odd thing is that this disguises as some bare metal, hackable device. 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 deskt…
> The 256×144 px screen requires pixel-level rendering, which standard TUI libraries (ncurses, etc.) cannot provide. The proposed solution is an HTML/CSS rendering engine running as a background daemon — a lightweight browser-based renderer that draws menus, popups, and UI components. Truly, a design only an LLM could love.
They should just use Trolley[0] which will ship their TUI inside Ghostty.
Re: Flipper One – we need your help
#469Earlier quoted context omitted.
The odd thing is that this disguises as some bare metal, hackable device. 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 deskt…
> The 256×144 px screen requires pixel-level rendering, which standard TUI libraries (ncurses, etc.) cannot provide. The proposed solution is an HTML/CSS rendering engine running as a background daemon — a lightweight browser-based renderer that draws menus, popups, and UI components. Truly, a design only an LLM could love.
Why not use Qt-embedded, which is specifically designed for this kind of thing and works well?
Re: Flipper One – we need your help
#470Earlier quoted context omitted.
The odd thing is that this disguises as some bare metal, hackable device. 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 deskt…
> The 256×144 px screen requires pixel-level rendering, which standard TUI libraries (ncurses, etc.) cannot provide. The proposed solution is an HTML/CSS rendering engine running as a background daemon — a lightweight browser-based renderer that draws menus, popups, and UI components. Truly, a design only an LLM could love.
What leightweight browser rendering?