Technology
Which posts fit here?
Anything that is at least tangentially connected to the technology, social media platforms, informational technologies and tech policy.
Post guidelines
[Opinion] prefix
Opinion (op-ed) articles must use [Opinion] prefix before the title.
Rules
1. English only
Title and associated content has to be in English.
2. Use original link
Post URL should be the original link to the article (even if paywalled) and archived copies left in the body. It allows avoiding duplicate posts when cross-posting.
3. Respectful communication
All communication has to be respectful of differing opinions, viewpoints, and experiences.
4. Inclusivity
Everyone is welcome here regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
5. Ad hominem attacks
Any kind of personal attacks are expressly forbidden. If you can't argue your position without attacking a person's character, you already lost the argument.
6. Off-topic tangents
Stay on topic. Keep it relevant.
7. Instance rules may apply
If something is not covered by community rules, but are against lemmy.zip instance rules, they will be enforced.
Companion communities
!globalnews@lemmy.zip
!interestingshare@lemmy.zip
Icon attribution | Banner attribution
If someone is interested in moderating this community, message @brikox@lemmy.zip.
view the rest of the comments
Somebody convince me not to say fuck it and build my own brick of a phone with an rpi5
Maybe you'll be interested in this project: https://github.com/evanman83/OURS-project
Yeah, I saw that one the other day. Definitely a cool project. I might take a deeper look at it at some point.
There are a few projects already in existence that might be more convenient, than an rpi5 like fairphones, and I think the grapheneos team is looking to develop something too.
Yeah, that's the more realistic option. Though it would cost several hundred dollars more.
Not that I have a better idea, but Graphene os devs I think were found to be scummy by Louis Rossmann at some point.
Graphene is the currently most secure option, whatever drama Louis stirs up again.
Not contestintn that, but that wasn't drama stirred up by Louis.
Source? Not arguing, I'm just not informed.
https://youtu.be/Dl1x1Dy-ej4 This is something I could find real quick, I don't remember exactly what happened but ig you can see for yourself. Cheers
That's his second channel by the way, not some reposter.
The lead developer in question seems to have stepped down from the position.
Mobile telephony support just comes as a module, so that's actually the easy part.
The harder parts are to make the whole thing consume a low enough amount of power that you can keep it running from a non-monster-sized battery, and I suspect that an RPi 5 board isn't very good for that (hobbyist development boards tend to not have been designed to avoid wasting power, even when the underlying microcontroller/processors is actually decent at it), and integrating an OS with support for a touch interface, especially if you want to avoid Android.
I mean, it's not too hard to make a brick sized dumb phone and even have it be a mobile phone powered by AA batteries, but if you want a mobile smartphone, it gets more complex.
Unless you have the time and skills to take up the challenge you would probably be better of getting something like a Volla phone with Ubuntu Touch or a Pine phone.
What if you take the battery from a small laptop? It may still be bigger than a whole smartphone, but comparatively small and with some ten watt-hours.
Even a smallish LiPo battery will give you some time. The question is how little becomes too little.
And on the other size you can always give it more battery: after all the original mobile phones were the size of a briefcase.
Ultimatelly how bad it is to go with a Raspberry Pi depends on how much more it with the software it has consumes than what a custom circuit designed for saving power using software configured for that (for example, not running needless services). Further, how much would, say, the extra power used in an HDMI connection over other more lower level protocols of talking to a display really matter next to the power consumption of the display itself or the GSM module, both of which tend to be big power users?
I know for sure that if you design a custom board with a basic STM32 microprocessor and add a 2G GSM module to it, most of the consumption ends up being the 2G module anyway, so you could probably get away with just using some hobbyist board with it instead of designing your own with just what you need and a proper Voltage Converter. However I haven't really tried doing a battery powered smartphone with an ARM SBC so I don't really know for sure.
Good luck with that