thepyphone VS rpi-open-firmware

>> Modern smartphones however, seem like walled gardens in which I have no control at all.

By design, I think.

>> I am locked into a single OS on my smartphone, which either spies on you or is locked down even more. Every iteration a bit more control is taken away from the user.

I got so fed up with this, I abandoned the whole mobile infrastructure and built my own phone with a Raspberry Pi 3B+. The Raspberry Pi is pretty open hardware (yes, I'm aware it's not perfect). For software I used Python 3, C and GTK. It does voice and SMS/MMS only, but that is enough for me.

I built it for myself. It's stable enough that I use it as my daily driver.

I am in the process of open sourcing the code and putting" rel="nofollow">https://github.com/another2020githubuser/thepyphone">putting it out on github.

I truly hope an open hardware smart phone becomes available soon. Until then, I'll use my home grown PyPhone to get by.

I agree that general purpose

If you are going to take a stand for open computing, you are going to have to make sacrifices. You will have to give up a lot of conveniences. As a technologist you will have to give both time and money. Apple and Google are not going to give up their billion dollar industries voluntarily. You will have to stop giving them money. And you will have to stop using their services.

My solution? I built myself a phone out of a Raspberry Pi 3 with a Touch Screen and a Logitech Headset. It does SMS/MMS and voice only. I've been using it for over a year now as my daily driver.

I'm going to open source the code. Check out https://github.com/another2020githubuser/thepyphone for more details. Right now there is just a README out there, the real code exists in a private git repo. I'm reviewing the code and stripping out private details so I don't end up doxxing myself :)

If you like the idea, please star the github project. I could use the encouragement. Thanks.

> Please correct me if I'm wrong.

My memory told me it was the GPU that needed the blobs. So I asked at DDG

https://duckduckgo.com/?t=ftsa&q=binary+blobs+and+the+Raspbe...

Turned up this: https://wiki.debian.org/RaspberryPi and it says...

> All Raspberry Pi models before the 4 (1A, 1B, 1A+, 1B+, Zero, Zero W, 2, 3, Zero 2 W) boot from their GPU (not from the CPU!), so they require a non-free binary blob to boot

So the 4 (and I suppose the 5, if it ever actually comes...)

Goes on to say:

> Since then, Broadcom publicly released some code, licensed as 3-Clause BSD, to aid the making of an open source GPU driver. The "rpi-open-firmware" effort to replace the VPU firmware blob started in 2016. See more at https://news.ycombinator.com/item?id=11703842 . Unfortunately development of rpi-open-firmware is currently (2021-06) stalled.

So there you are. Not wrong, are you, but not strictly correct, depending on "...to run properly" definition

https://github.com/librerpi/rpi-open-firmware has updates 3-months ago

many of those demos work on the the entire pi model range

pi3 support is only broken due to arm side problems, which could be fixed by just using a different bootloader

and the https://github.com/librerpi/rpi-open-firmware codebase can already boot linux headlessly on both pi2 and pi3, it uses a different arm bootloader

Yes, and some folks are reverse engineering their stuff:

https://github.com/librerpi/rpi-open-firmware/

rpi-open-firmware: open-source VPU side bootloader for Raspberry Pi\ (35 comments)

There is work being done on the RPi4, for example the SHA1 HMAC protecting the boot on the RPi4 had to be cracked (and was easily), I hear future versions have RSA signing support, so the proprietary firmware might become mandatory at some point.

https://github.com/librerpi/rpi-open-firmware/blob/master/do...

There is a project to create an open source version of the proprietary GPU firmware that boots into the ARM processor:

https://github.com/librerpi/rpi-open-firmware

I note that even the Raspberry Pi is moving towards locked down devices, the RPi4 has an (easily cracked) HMAC blocking booting into the open source firmware and I hear more recent hardware editions have RSA signing support in the bootrom code.

https://github.com/librerpi/rpi-open-firmware/blob/master/do...