this post was submitted on 15 Nov 2025
600 points (98.1% liked)

Linux

10254 readers
492 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
 

Hello all!

Due to the recent statements by Google (as well as their track record the last few years) I've decided I do not want to use Android as a phone operating system anymore. But Apple is just as bad, if not worse. So I've decided to build my own custom device.

I am working on building a phone using a single board computer, right now I'm using the raspberry pi 5. This is still a proof of concept, but I want to share my ideas with others, so like minded individuals can start messing around with this idea in their own homes to further this goal.

You can view more images of the device here, as well as the step by step instructions here (these are still very rough and incomplete) https://github.com/muhammadmanwar/cheaphone OR https://codeberg.org/muhammadmanwar/cheaphone

Right now it just runs raspberry pi OS, with a different desktop look and feel. Everything that normally works in a pi 5 works on this device, additionally I am experimenting with a Mobile Broadband modem, to allow the device to text and call, as well as access internet, like a normal phone off wifi

The total cost is around 200 dollars, not including the 3d printer to make the custom case.

This project is barely off the ground, and I've got a lot to learn before I can stop relying strictly on the raspberry pi 5, my end goal is to custom design SBCs, and release those designs for free alongside the plans for the device, so that interested parties can select their own System on a Chip to use for the device. I need to get into designing boards, I'm interested in trying Stephen Hawes' Lumen PnP (https://www.youtube.com/watch?v=JlkTcxh-9gA) for that phase.

But that's for the future, for now, I'm hoping to get more people interested in the prototype so that I'm not the only one noodling around on this idea. I'd love some feedback, and if anyone was willing to put one together for testing, I would appreciate it greatly!

top 50 comments
sorted by: hot top controversial new old
[–] balsoft@lemmy.ml 83 points 1 week ago (4 children)

I'm sure you are already aware, but just in case, there's a lot of prior work in getting a truly Linux mobile phone.

There are ready-made devices like PinePhone (the PinePhone Pro looks the most promising one of the bunch), Librem 5, and Liberux Nexx. I think at least some of those companies publish schematics for their boards, you should probably check those out if you want to design your own.

There is also another direction, taken by postmarketOS and the like, to install Linux on a phone that shipped with Android out of the box.

It should be easy enough to install postmarketOS on your device, since it seems to have support for raspberry pi. The benefit of postmarketOS here is that it makes it really easy to install mobile Linux UI shells, like phosh, gnome-mobile, plasma-mobile, or sxmo. This will let you try all of them out and maybe pick one as a starting point for your software stack.

[–] hendrik@palaver.p3x.de 38 points 1 week ago* (last edited 1 week ago) (6 children)

And the software side of it is the really annoying part. We're missing so many components: Connected standby, an app lifecycle management, maybe sandboxing and a detailed, user-facing permission system. And then we need to go ahead and rewrite all the important Linux software to use these (not yet existing) interfaces.

I own a Pinephone, and I feel the Linux phone is within reach since the Nokia 900 (and its predecessors) and that was in 2009, so 16 years now. I believe any effort is very welcome, though. We badly need a good and free operating systems for this important device we all carry around and use hundreds of times each day.

[–] yyprum@lemmy.dbzer0.com 13 points 1 week ago (1 children)

Let's not forget all the software that was done and kinda ready for the openmoko device. There were a few distros for that alone. Some were pretty stable but the biggest issue came down always to phone call quality and connectivity. I'm completely out of the loop but back then all the chips were so closed in themselves that they were basically black boxes. A huge effort was made to try and get them to work as well as possible, with varying degrees of success. I wonder if it continues being the same nowadays.

The N900 was such an amazing device, I still have it around and the UX was the best I've had in a phone, Maemo was truly great and way advanced to its time. That UX with the screen sizes we have today... I keep dreaming.

[–] hendrik@palaver.p3x.de 4 points 1 week ago

Phone quality on my Pinephone is nice except when it isn't. We have a largely Free Software baseband running on the modem. You can tell it to run a high samplerate and it does VoIP and 4G. On the flipside it doesn't always work and there were issues with additional stuff like echo cancellation, which then takes away from the experience. Openmoko was great as well. I think it was so very open, people could do silly things with the phone network. But then it's old tech by now and the 2G (GSM) phone network is obsolete and they turned off the cell towers in most areas by now. And I think the software on it didn't really translate to the phone generations after that. Afaik the entire software stack didn't carry over and we're using different dialers, messengers, calendars etc now.

[–] balsoft@lemmy.ml 8 points 1 week ago (1 children)
  • Connected standby is already somewhat possible (it's actually done on the hardware/firmware side on most phones), it can work with something like ntfy with a fairly simple script IIRC
  • We have sandboxing and permissions figured out pretty well with Flatpak (there are improvements to be had for sure, but all the basics are there)

The one main remaining barrier (apart from thousands of paper cuts everywhere and lack of apps), is indeed process lifecycle management. It's the most complicated one to do, because in order to work well it requires apps to cooperate in some way, either by completely and honestly shutting down when not doing any work, or by providing ways to check if there's any work to be done without running the rest of the app, or both ideally. None of the apps currently do that, so the only options are (1) just let apps do whatever they want, draining the battery, or (2) send SIGSTP to apps that are not in the foreground, losing background notifications and such.

load more comments (1 replies)
load more comments (4 replies)
[–] Resonosity@lemmy.dbzer0.com 5 points 1 week ago

Pine64 discontinued the PinePhone Pro unfortunately

[–] jcs@lemmy.world 5 points 1 week ago (4 children)

the PinePhone Pro looks the most promising one of the bunch

I'll have to advocate for the Librem 5 over the Pinephone Pro for the following reasons:

  1. The Pinephone Pro has officially been discontinued as of August 2025 [source].
  2. The Librem 5 and Liberty phones are still in production [source].
  3. Librem 5 PCB board design files are also available - not just schematics [source].
  4. Purism is already working on a Librem 5 version 2.
  5. Purism is pushing toward FSF RYF certification for the Librem 5 and future models.
[–] balsoft@lemmy.ml 6 points 1 week ago (2 children)

I own a Librem5, and let me tell ya, it's not a daily phone, hardware is just way too slow. Even with sxmo it lags a lot, opening a browser is a whole ordeal for it. Meanwhile when I tried my friend's PinePhone Pro, it felt a lot better. Oh, and for context, I'm currently semi-dailying a OnePlus 6 with NixOS.

load more comments (2 replies)
load more comments (3 replies)
load more comments (1 replies)
[–] Kraiden@piefed.social 47 points 1 week ago (12 children)

What I wouldn't give (or pay) for a 1. sleek, modern smartphone 2. running a pure Linux distro 3. that's feature complete enough to daily drive

All of the current options available fall down in one of the three areas. Usually 2. and 3... mostly 3.

[–] leavemealone@sh.itjust.works 24 points 1 week ago (4 children)

Considering their recent hardware reveals, I want a valve steamphone with a fully open system and modularity a la fair phone (or like their new VR headset) One model every 4/5 years would be perfectly ok for me.

[–] kuhli@lemmy.dbzer0.com 12 points 1 week ago (1 children)

A valve / framework / fairphone teamup would be a dream. It'll never happen but I'd pay unreasonable amounts of money to see it

load more comments (1 replies)
load more comments (3 replies)
load more comments (10 replies)
[–] biotin7@sopuli.xyz 47 points 1 week ago* (last edited 1 week ago) (1 children)

This is a sexy device. But can I ask you to make a repo on codeberg ? Github has been taking down repos that might be a threat to Big-Tech monopoly

[–] digitalRights4All@lemmy.zip 45 points 1 week ago (1 children)

Thanks for the suggestion, I mirrored the repo here: https://codeberg.org/muhammadmanwar/cheaphone

I may end up switching entirely to code berg, but I'll see how bothersome it is to push changes to both before I fully migrate. Thanks again!

[–] Ghoelian@piefed.social 16 points 1 week ago

I'm not sure if you can do it the other way around, but you can set up a push mirror on codeberg so you only have to push to one forge.

[–] cupcakezealot@piefed.blahaj.zone 43 points 1 week ago (11 children)

i just want a linux phone with a slide out physical keyboard.

[–] pinball_wizard@lemmy.zip 13 points 1 week ago (1 children)
[–] DmMacniel@feddit.org 6 points 1 week ago (1 children)
[–] bjoern_tantau@swg-empire.de 6 points 1 week ago (1 children)

This is the way.

I mean, so say we all.

load more comments (1 replies)
[–] nailbar@sopuli.xyz 11 points 1 week ago

Bring back the Nokia N900!

[–] Lucidlethargy@sh.itjust.works 10 points 1 week ago* (last edited 1 week ago)

I don't care about this at all. This is a niche interest.

I just want a phone that isn't backed by assholes that want to sell my data.

[–] Valmond@lemmy.world 5 points 1 week ago (12 children)

Phones nowadays are so powerful I'd switch out my home PC if I could.

load more comments (12 replies)
load more comments (7 replies)
[–] wiki_me@lemmy.ml 22 points 1 week ago (2 children)

I suggest adding a license . i recommend a copyleft license (there are copyleft licenses for hardware. for example the cern licenses).

I also suggest setting up a open collective. i suspect people might be more inclined to donate to a non profit then to for profit companies like purism and Pine64.

[–] digitalRights4All@lemmy.zip 12 points 1 week ago (3 children)

Thanks for the suggestions! I'm not actually looking for any donations though. It probably sounds weird, but I don't want to derive value from this, or even assign value to it, in the interest of keeping the information as freely accessible as possible. Not too get too ideological, seeking money often causes people to make a good idea bad, or to make a simple process inefficient, to make more money from it. I'm thankfully in a position where I can keep (slowly) working on this project in my free time, while still keeping my head above water.

That isn't to say that no one else should make money from this idea. I just don't want to personally.

I do like the idea of a copyleft license. I'll have to look into it a bit more. Thanks again for your suggestions!

load more comments (3 replies)
[–] Korhaka@sopuli.xyz 9 points 1 week ago (1 children)

Why would you donate to pine64? They are selling things, just buy their stuff. Its like a donation but you get stuff out of it too!

[–] wiki_me@lemmy.ml 6 points 1 week ago (3 children)

When dealing with stuff like kickstarter campaigns. some people might not to risk the full amount (something like 600$), they might be interested in donating something like 10$ to help the project put out a product. then read up on reviews and decide if to go for it.

load more comments (3 replies)
[–] xtools@programming.dev 20 points 1 week ago (1 children)

there's a youtuber working on something similar, maybe yous can join forces: https://youtu.be/OgMdO0ckICg

[–] digitalRights4All@lemmy.zip 14 points 1 week ago

Wow! That does seem really similar to what I'm doing. And they seem further along than I am. I'll have to look into this project some more. Thank you!

[–] umbrella@lemmy.ml 11 points 1 week ago (2 children)

can't see from the pic (more of them appreciated), but it looks like you can desolder the ports to save on space.

load more comments (2 replies)
[–] winni@lemmy.world 11 points 1 week ago (1 children)
[–] digitalRights4All@lemmy.zip 5 points 1 week ago

This is a very helpful suggestion, thank you! I have been having some issues figuring out spacing, the battery sticks out like a sore thumb right now, so if this can save me some space I may end up moving in this direction for further prototyping. Thanks!

[–] rontosaurus@lemmy.world 11 points 1 week ago

Happy to see this out there, love the idea. Watching the repo may mess around with this at some point when I have more time.

[–] TheMightyCat@ani.social 10 points 1 week ago (1 children)

I think everyone has once thought of the idea of taking an sbc and a touchscreen and making a linux phone, cool to actually see one!

load more comments (1 replies)
[–] GalacticGrapefruit@lemmy.world 10 points 1 week ago

OMG, what?!? Holy fuck, this is amazing! This is incredible! Way to go!

[–] quick_snail@feddit.nl 9 points 1 week ago (1 children)

Ah, the thicc phone.

What are the dimensions of the case?

load more comments (1 replies)
[–] lefthandeddude@lemmy.dbzer0.com 8 points 1 week ago* (last edited 1 week ago) (3 children)

This is a really cool idea. Any work in the direction of more linux phone technology is always good. There are some linux phones out there already, and these devices have had some problems which is why there hasn't been more adoption. If there is a way to do this with RISC and have decent battery life, that would be really exciting. Have you tried installing Phosh on it?

The newest, and most exciting, option right now is flx1s (https://furilabs.com/flx1s-update-2/).

One of the biggest problems is that, to my knowledge, there is no standard linux mobile App standard or, if there is, it's not often used. There is a group working on this issue right now (https://www.fierce-network.com/wireless/mobile-linux-standards-group-formed).

For example, if I am using mobian or something similar and download thunar using sudo apt install thunar, then if I run thunar, it will run, but certain menus won't display easily. In phosh, any sub-menu boxes will also pop up as a smaller pop-up box and to close it, you have to scroll through Apps to find the pop-up box and then close it. Generally I may be able to see the file structure on the left in Thunar but have a hard time seeing what's on the right.

There are also things that can happen in which default panels (like the side panel) take up so much room that you can't see what's going on. For instance, if you try running gimp in phosh, you can barely see the image panel by default.

There are some Apps designated as mobile-friendly but even these sometimes don't display correctly. Perhaps there should be a way to make it harder for Apps to be installed that don't meet mobile standards and have weird menu glitches, such as making it harder to download Apps from repositories that are not mobile.

I'd really like to be able to run something like "flatpak-mobile install librewolf" and just get something that at least had a file with it to tell phosh how to display menus in the best way, if not a slightly altered librewolf.

Many people who used phosh would say "well just use waydroid" but the problem is that with play integrity api, many of those Apps won't work.

In order for banking Apps and other Apps to run on linux and people to develop software, there really needs to be more adoption of mobile linux.

And yes, battery life was atrociously bad and completely unusable on the linux mobile devices I tested, which were a few years ago. It also got way too hot when just not doing anything, which was terrible. (In other words, if I took the device with me to Starbucks and got a coffee, it might get way too hot in my pocket; if I took it out and used the Internet for 20 minutes, the battery could die, and even if it didn't, if I were waiting for a call during that time there was a good chance I wouldn't get it. After getting back home, it would be totally dead and need a full recharge.)

Right now also, the main competitor to linux phones is Graphene OS with FOSS Apps and Graphene OS has better security features if someone is worried about their phone being stolen or seized. Data security is important to me and Graphene OS has a rate-limiting throttle to the password entry that even cellebrite can't easily bypass and a function to auto-reboot. If the political situation in my country deteriorated even more, and arbitrary arrests started to happen more often, I would much rather be arrested with a Graphene phone than a typical linux mobile phone. Mobile linux for certain distros such as Mobian still offers robust encryption in before first unlock (bfu) if the password can withstand brute force attempts, but since there's no hardware rate-limiter, the password has to be much more complex. Also, most people who use their phone frequently are not in BFU mode.

Graphene OS also requires a Pixel which does not have hardware switches and so a person must trust that there's no exploit allowing certain components to be turned on or off which can be concerning when there is no way to definitively measure what the cellular modem is transmitting. Call me paranoid, but given what I know about how easy it is for someone smart to exploit computers, I actually don't want a cell phone microphone to have power when I am talking about sensitive things or inputting passwords into computer systems and I do not want a camera that is built into the lcd part of the glass screen and can't be easily covered because of the need to swipe up nor turned off without a switch, even if the cell phone has an incredible operating system that is very secure. Graphene, unlike most mobile linux distributions, is mostly very usable with no battery life issues, no weird display problems where Apps don't display correctly and menus don't work correctly, and no random reliability problems, mostly. I understand not wanting to rely on anything involving Android, however, given Google's recent aggressive anti-privacy stances.

I'm excited about FuriPhone (https://furilabs.com/) and Purism's Librem 5v2.

The thing that I believe would help Mobile Linux most right now is people having conferences and getting to know each other and discussing standards, specifically on user experience, linux mobile app standards, battery life, and reliability.

There are so many smart people in mobile linux and eventually it will get great but right now there are major problems with the user experience because of how Apps are displayed and battery life as well as things like reliability.

So any way to gather people to discuss the mobile linux user experience and to come up with standards to reduce these issues would help, or even to help list all the different problems so that they can just be enumerated and acknowledged and worked on would help.

Another way that would help is to have a mobile linux security group or conference to discuss things like standards for making mobile linux more secure from brute-force attacks if stolen or seized after being unlocked.

load more comments (3 replies)
[–] fartographer@lemmy.world 7 points 1 week ago

This seems like a very ambitious project and a great learning experience for someone working on their own. For a similarly ambitious project, check out the Liberux NEXX. The project didn't reach its crowdfunding goal, but they did make some progress before rolling up the rugs.

I don't know if they're looking for contributors or if you're in a place to contribute, but most of the project is open source. You could probably get in touch with them and ask for any advice, successes and failures, and even if they have parts (such as their dev-board) that they can give you access to.

[–] buddascrayon@lemmy.world 6 points 1 week ago (6 children)

If you're really going to do this you need a RISC-V processor SOC. If you look around online there's a few places where you can obtain these.

load more comments (6 replies)
[–] just_another_person@lemmy.world 6 points 1 week ago (1 children)

Not trying to dump on your efforts or anything here, but you'd be better off first defining a scope of what you're trying to do, and then work off an existing hardware or software platform.

You can get phone dev kits for cheaper than $200 if you just want to build something that works without Android, but if you intend to take that further and design some of the software experience, you'd be better off just working or contributing to something that already exists.

A single person can't even begin to touch on the fundamentals of what it takes to run a phone experience in that that we currently understand and use them. Touch UX, software<>hardware integration, peripherals like cameras...it's A LOT. Doing it well as a single developer is just not going to happen.

If your goal is simply to not have to buy another shit Google-infested phone, you can get a cheap that runs other things right now.

[–] communism@lemmy.ml 10 points 1 week ago (1 children)

From the sounds of it, it's just a hobby project for fun for OP. I don't think there's anything wrong with doing something just for the sake of it.

[–] PokerChips@programming.dev 8 points 1 week ago (1 children)

Plus, if OP's project catches steam, it provides more competition and cult followings which adds to the flair of hobby phones and its attraction thus helping to pave the way for more adoption and development.

[–] digitalRights4All@lemmy.zip 7 points 1 week ago

This is definitely the angle I'm trying to work. The more people who know how to build these sorts of devices, the more software and hardware will be supported, and standard custom software/hardware pairings can be documented. But we won't know what works till we try it

load more comments
view more: next ›