Hacker Phone Manifesto

[MaSk]

I've spent a lot of time thinking about the friction of using a modern phone and I think it comes down to one thing: every device today stands alone, closed and fixed, telling you exactly what it is and how you're allowed to use it. Little to no expandability, in hardware or software.

I think it's time to challenge that. That belief led me to write a hacker phone manifesto — an attempt to revisit the values behind devices like the N900, and sketch what a phone that's open and hardware-expandable could actually look like.

I'd love to hear whether people think this is technically viable today, or whether the market killed that idea for good reasons. And if this is off-topic here, I apologize in advance, you can point me some place better.

https://beyondframe.ink/hacker-phone-the...-hardware/

[biketool]

I've spent a lot of time thinking about the friction of using a modern phone and I think it comes down to one thing: every device today stands alone, closed and fixed, telling you exactly what it is and how you're allowed to use it. Little to no expandability, in hardware or software.

I think it's time to challenge that. That belief led me to write a hacker phone manifesto — an attempt to revisit the values behind devices like the N900, and sketch what a phone that's open and hardware-expandable could actually look like.

I'd love to hear whether people think this is technically viable today, or whether the market killed that idea for good reasons. And if this is off-topic here, I apologize in advance, you can point me some place better.

https://beyondframe.ink/hacker-phone-the...-hardware/

Unfortunately the amount of useful discourse on the pine forum has dropped off to nearly nothing.  But just so you know both the pinephone and the librem have hacker interfaces, these were the other half to the hardware paranoia switches.  Initially I had wanted a soldered down POCSAG pager unit with a modem paranoia switch on the Neo900, Joerg(at GDC & maemo forums) responded with the hacker interface; so that we could be fully undetectable but still able to be contacted via pager signal.  Now you see that connection enabling pinephone keyboard, satellite messaging, IR cameras, LoRa, etc.  You can get a pogo-pin adapter ribbon form the pine64 store to interface with the i2c and power pins.

[goerge1]

Hello everyone, I have been having an issue with the PinePhone. It sometimes randomly freezes (the screen is unresponsive, but the phones still works) and then after 10 seconds, it forcibly reboots and makes a clicking/popping sound (same sound when the camera starts up). The phone seems to be still working as I have been in a call when that happened.

However, the logs don't get saved after the force reboot, so I don't know what's causing the issue. Does anyone have any idea what the issue may be?

I've spent a lot of time thinking about the friction of using a modern phone and I think it comes down to one thing: every device today stands alone, closed and fixed, telling you exactly what it is and how you're allowed to use it. Little to no expandability, in hardware or software.

I think it's time to challenge that. That belief led me to write a hacker phone manifesto — an attempt to revisit the values behind devices like the N900, and sketch what a phone that's open and hardware-expandable could actually look like.

I'd love to hear whether people think this is technically viable today, or whether the market killed that idea for good reasons. And if this is off-topic here, I apologize in advance, you can point me some place better.

https://beyondframe.ink/hacker-phone-the...-hardware/

I've spent a lot of time thinking about the friction of using a modern phone and I think it comes down to one thing: every device today stands alone, closed and fixed, telling you exactly what it is and how you're allowed to use it. Little to no expandability, in hardware or software.

I think it's time to challenge that. That belief led me to write a hacker phone manifesto — an attempt to revisit the values behind devices like the N900, and sketch what a phone that's open and hardware-expandable could actually look like.

I'd love to hear whether people think this is technically viable today, or whether the market killed that idea for good reasons. And if this is off-topic here, I apologize in advance, you can point me some place better.

https://beyondframe.ink/hacker-phone-the...-hardware/

Unfortunately the amount of useful discourse on the pine forum has dropped off to nearly nothing.  But just so you know both the pinephone and the librem have hacker interfaces, these were the other half to the hardware paranoia switches.  Initially I had wanted a soldered down POCSAG pager unit with a modem paranoia switch on the Neo900, Joerg(at GDC & maemo forums) responded with the hacker interface; so that we could be fully undetectable but still able to be contacted via pager signal.  Now you see that connection enabling pinephone keyboard, satellite messaging, IR cameras, LoRa, etc.  You can get a pogo-pin adapter ribbon form the pine64 store to interface with the i2c and power pins.

I think it's still technically viable, but the biggest challenge is economics rather than engineering. Most consumers prioritize thin designs, battery life, and low cost over modularity, which makes it difficult for truly open hardware phones to gain mass adoption. That said, there's definitely still a niche of developers, makers, and privacy enthusiasts who would appreciate a more expandable platform.

[MaSk]

I've spent a lot of time thinking about the friction of using a modern phone and I think it comes down to one thing: every device today stands alone, closed and fixed, telling you exactly what it is and how you're allowed to use it. Little to no expandability, in hardware or software.

I think it's time to challenge that. That belief led me to write a hacker phone manifesto — an attempt to revisit the values behind devices like the N900, and sketch what a phone that's open and hardware-expandable could actually look like.

I'd love to hear whether people think this is technically viable today, or whether the market killed that idea for good reasons. And if this is off-topic here, I apologize in advance, you can point me some place better.

https://beyondframe.ink/hacker-phone-the...-hardware/

Unfortunately the amount of useful discourse on the pine forum has dropped off to nearly nothing.  But just so you know both the pinephone and the librem have hacker interfaces, these were the other half to the hardware paranoia switches.  Initially I had wanted a soldered down POCSAG pager unit with a modem paranoia switch on the Neo900, Joerg(at GDC & maemo forums) responded with the hacker interface; so that we could be fully undetectable but still able to be contacted via pager signal.  Now you see that connection enabling pinephone keyboard, satellite messaging, IR cameras, LoRa, etc.  You can get a pogo-pin adapter ribbon form the pine64 store to interface with the i2c and power pins.

That is really unfortunate. I was hoping to open a discussion regarding technical challenges and possible solutions. I know of a few topics I haven't completely thought through. I suppose I will have to look elsewhere - I am open to suggestions, if you have any.

I have seen the PinePhone keyboard and the other modules that can be connected. I had no idea Librem has a hacker interface as well. I would say it is a good starting point and I suppose it could be a way to build a hacker phone prototype. Make a custom back module that would expose the hacker interface to the rail. This could work well for peripherals. For phone to phone connection a faster interface than I2C would be needed, however that is not necessary for step 1. This is a genuinely good idea.

---

Hello everyone, I have been having an issue with the PinePhone. It sometimes randomly freezes (the screen is unresponsive, but the phones still works) and then after 10 seconds, it forcibly reboots and makes a clicking/popping sound (same sound when the camera starts up). The phone seems to be still working as I have been in a call when that happened.

However, the logs don't get saved after the force reboot, so I don't know what's causing the issue. Does anyone have any idea what the issue may be?

I've spent a lot of time thinking about the friction of using a modern phone and I think it comes down to one thing: every device today stands alone, closed and fixed, telling you exactly what it is and how you're allowed to use it. Little to no expandability, in hardware or software.

I think it's time to challenge that. That belief led me to write a hacker phone manifesto — an attempt to revisit the values behind devices like the N900, and sketch what a phone that's open and hardware-expandable could actually look like.

I'd love to hear whether people think this is technically viable today, or whether the market killed that idea for good reasons. And if this is off-topic here, I apologize in advance, you can point me some place better.

https://beyondframe.ink/hacker-phone-the...-hardware/

I've spent a lot of time thinking about the friction of using a modern phone and I think it comes down to one thing: every device today stands alone, closed and fixed, telling you exactly what it is and how you're allowed to use it. Little to no expandability, in hardware or software.

I think it's time to challenge that. That belief led me to write a hacker phone manifesto — an attempt to revisit the values behind devices like the N900, and sketch what a phone that's open and hardware-expandable could actually look like.

I'd love to hear whether people think this is technically viable today, or whether the market killed that idea for good reasons. And if this is off-topic here, I apologize in advance, you can point me some place better.

https://beyondframe.ink/hacker-phone-the...-hardware/

Unfortunately the amount of useful discourse on the pine forum has dropped off to nearly nothing.  But just so you know both the pinephone and the librem have hacker interfaces, these were the other half to the hardware paranoia switches.  Initially I had wanted a soldered down POCSAG pager unit with a modem paranoia switch on the Neo900, Joerg(at GDC & maemo forums) responded with the hacker interface; so that we could be fully undetectable but still able to be contacted via pager signal.  Now you see that connection enabling pinephone keyboard, satellite messaging, IR cameras, LoRa, etc.  You can get a pogo-pin adapter ribbon form the pine64 store to interface with the i2c and power pins.

I think it's still technically viable, but the biggest challenge is economics rather than engineering. Most consumers prioritize thin designs, battery life, and low cost over modularity, which makes it difficult for truly open hardware phones to gain mass adoption. That said, there's definitely still a niche of developers, makers, and privacy enthusiasts who would appreciate a more expandable platform.

That may be true, but I never said a hacker phone is meant to be a device for everyone. It is meant to be for people who want more freedom and flexibility and are willing to make some trade-offs. Right now we don't even know what those trade-offs will be. It will probably not be as thin and as performant in terms of raw computational power. The cost may be higher, but if the rail connector carries over across models or even brands - in case it gets adopted as a standard - every accessory you buy carries over with it too, reducing cost over time. Which is not the case with mainstream devices. And if you can connect your old phone to your new phone, using them as a cluster, sharing whatever resources the old device can still offer, there can be an added value in that too.

It wasn't that long ago that the Flipper Zero sold in large numbers, despite being a hacking toy with no Wi-Fi or other network connectivity of its own (it does have an add-on Wi-Fi debugger, often used to work around that limitation). I believe a full-fledged phone with hacker capabilities would drive even higher interest than that.

[waitingpio]

Hi MaSk,

I support the modularity idea too. A device that stays useful long-term, instead of becoming e-waste after a few years, is worth working towards.
I read your article and the N900 framing resonates. I'm going to push on the technical side a bit, but that's because the idea deserves a real look, not because I think it's a bad one.

The Flipper Zero comparison is interesting, though I think the gap is bigger than it looks. The Flipper runs an STM32WB55: a 64 MHz Cortex-M4 with 256 KB RAM and 1 MB flash, running FreeRTOS, driving a 1.4-inch 128×64 monochrome LCD. That's a microcontroller with a mature, well-documented vendor stack. It sold well because it does a narrow job on hardware that ST had already finished and tuned.

A phone is a different problem entirely. You need an application processor, a modem, camera ISPs, a GPU, power management, and a display pipeline, plus drivers and a BSP for all of it. That's where the real difficulty sits.

Suspend and resume is the hardest part of it. Standby means every block on the SoC has to power down and come back cleanly, with its registers saved and restored correctly, and the wake path working through all of them. And it has to hold from the register level all the way up: hardware, drivers, kernel, userspace, applications. One driver that doesn't restore state properly and the phone either won't sleep or won't wake. It only takes a single break anywhere in that chain. This is exactly what has kept PinePhone battery life poor for years, and it's not a problem you can solve at the mechanical or connector level.

Big vendors put thousands of engineers and years of work into a single SoC and its software stack. A community group can't match that, and the chips keep moving. A large company iterates every year or two. The community typically needs six to ten years to fully support a platform, by which time the silicon is several generations old.

I'm not saying this to argue against the idea. I think it actually points at how a hacker phone should be designed: pick a chip that already has good mainline support, accept being a few generations behind, and put the effort into the rail connector and the modules instead. Performance ages badly, but a good expansion standard doesn't. The RK3399 boards are a decent example. Not fast by 2026 standards, but well supported and still perfectly usable.

Which leads to the question I'd most want answered: how do you make sure a module bought today is still worth using in five years?  still doing something useful on a device nobody has designed yet.
No idea what the answer is, but I'd like to see someone work it out. 
I think the forum still has people willing to have it.

[biketool]

(snip)I think the forum still has people willing to have it.

Forum participation is like neutron flux near critical mass in spontaneously fissioning neutron emitting isotopes, the closer to critical mass the more interaction which drives even more posts and interaction.

[matteorossi053]

Great points by @waitingpio on the SoC power management and BSP maintenance bottlenecks. To keep modules future-proof over a 5-year span, the rail bus would likely need to rely on standard, low-overhead protocols like USB/I2C alongside a basic power delivery contract. That way, modules act like class-compliant USB peripherals rather than depending on board-specific SoC drivers. Choosing a well-supported, mainlined SoC as the core host is definitely the most pragmatic starting point.