I’m a little jealous of the engineers who get to work on this project. It would be so exciting to build something like this from the ground up, improving it constantly. The challenge, scope, and meaning are compelling, no?
I've worked on smartphone electronics and it's not as exciting as you think. I'm pretty sure they chose the i.MX8 because they couldn't source Snapdragons so they got a little luckier with NXP, but the vast majority of the engineering done on a smartphone is in firmware and software with absolutely shitty support from the manufacturer. Bug fixes that only get distributed to customers after they've ran into the bug and struggled with it for weeks (instead of just putting the bug fix into the BSP), no version control or historical view of vendor drivers or modified kernels, firmware that has "hello world" levels of polish, documentation that is only available under three levels of NDAs, and few open source projects to learn from for what are usually almost-but-not-quite bespoke PCBs. Worst of all, consumer hardware products can sell at such scale that it's worth it to keep an engineer working on a single bug for months at a time only to find out that it was a bug in vendor silicon all along - it is soul crushing. Silicon manufacturers have very little respect for software and it really makes the entire process a lot more painful than it should be.
Iterations in electronics are really expensive (my last project cost $30k for 10 assembled prototypes not including of our labor) so most people just copy as much of the manufacturers' reference design as they need. They pour over PCB layout notes and look at how the manufacturer or other customers did and mostly just copy them. Most of my engineering decisions are based on about a dozen black box helper apps that take in my fab's capabilities and signal specs and spit out DRC rules. It gets a little trickier with antenna design but that's often outsourced because you need very specialized facilities for FCC certification anyway.
All in all, it's just like working on a complex distributed system. There are so many things to juggle like R&D budget, per unit COGS and space budget, suppliers and part availability, and supply chain orchestration that it ends up being lots of boring work just to coordinate between all the different experts involved with small bursts of productivity when everyone is properly aligned.
That's screen on, though, if you look at the title of the chart. That's probably no worse than my Pixel 3 (which is by no means an endurance athlete, but is probably fairly representative of the Android mass market).
The lack of screen off times in the article is definitely worrying, though. That's just as important a metric.
Edited to add: actually, the first graph is screen off, I think. Looks like it's a tick under 10 hours. Which is poor, so I hope there's more scope for software improvement, but I also think is a fairly significant improvement over where they were 6-12 months ago.
The pinephone recently got a 40% increase in idle battery life to ~100 hours with the modem off and ~24 with it on https://www.pine64.org/2020/07/15/july-updatepmos-ce-pre-ord... (control-f search for "crust"). I would hazard a guess that this might be portable to the Librem 5 (but maybe they already implemented it, IDK).
Edit: but my two sibling comments now seem to have more useful information than this one.
The key is probably this sentence: "In the future, we are also planning to support suspend to RAM." That is, the CPU is never being fully powered off, only clocked down.
AFAIK, Android uses suspend-to-RAM heavily (this is what a "wakelock" is all about: it prevents Android from suspending when held), and that has a large impact on battery life.
> Should I expect the Librem 5 developers to be able to achieve the same thing before they ship Evergreen?
It's unlikely it'll get as good as Samsung or Apple by that time but it should definitely improve. Unless they made some critical mistake in the hardware, they can make continuous improvements in the software.
It's no surprise that this is one of the last things they're focusing on. Idle power management on modern operating systems is hard and is very kernel and hardware specific because kernel interrupt and process scheduling comes into play. Hence why Apple is so good at battery life - they have such unilateral control over the hardware and software stack that they can make optimizations that Linux/Windows/Android really struggle with.
These are the kind of breakdowns I'd like on every phone out there. If they were to publicly release a standardized battery testing procedure with a list of all hardware used for testing, the would make it much easier to compare battery life across phones on the market.
Promising, but how close is it to being ready for consumer use? If all it can do is make/receive phone calls, SMS, and act as a WiFi hotspot, and cost less than USD$300 that would satisfy my list of desires.
Not mine. I need anki, authy, a calculator, a good podcast app, an audiobook app, a VPN, security/privacy, and then just a really long battery life.
An aside: if apple would stop making the new iOS updates so draining on older phones it would help - the last iOS update took my battery from 2.5 days without a charge to 1.7 days “overnight” - imagine what this did to people who didn’t buy the silly oversized model with the lower screeen resolution? It’s basically a malware attack on their users to force them to update
I just recently received my PinePhone Braveheart unit, which is by no means a similar device. However, I did try running Mobian, which runs a similar stack (including Librem’s innovative Phosh.) It actually is pretty impressive, and even though it is not aimed at consumer use it is pretty close to being usable as a basic phone with Linux.
There’s really two problems.
1. Speed. The CPUs are just underwhelming. It is not unusable by any means, but it definitely feels like many steps backwards. I think at least the PinePhone needs to be running lighter software; Wayland is certainly not an issue, but a lot of heavy GTK software is probably not a good idea. Web browsing is tricky and makes me wish there existed lightweight browser engines that implemented less of the web standard, but it is actually passable believe it or not.
2. Linux desktop software is just not designed for phones. I think Phosh is clever, and feels very nice to use... until you remember its a phone, and then realize the inherent differences. Normal phones have some kind of central push notification management, but not here. I assume when the device sleeps, you simply stop getting any notifications. I haven’t actually seen a notification pop up on the lockscreen yet, so I’m not sure. There’s an SMS and messaging app, and Telegram/tdesktop works really well, so there is that.
I think that both problems could be solved somehow, but it’s feeling like it could be a tough one. One of the things that both iOS and Android did right off the bat was dramatically change the model of execution that apps had, to orient them around the concept of constantly being swapped in and out. There’s really no obvious way you can support standard Linux desktop apps without some compromise here. I would actually be pretty happy if these devices were capable of just staying awake on a low frequency most of the time, because I think that would dramatically simplify things, but you would have to worry a lot about power draw from apps running and etc in ways that you don’t have to in most modern phones.
Some may view the lack of a good push notification story as a benefit, but for me there are definitely things where I want it to be reliable and timely... so I am left feeling a bit lost.
If I recall correctly, the last thread I saw on this, the biggest hurdle was the sheer size of the device. It looked like it was discovered in a time capsule from the 1990s
This phone is an embarrassment. Petty mismanagement https://www.phoronix.com/scan.php?page=news_item&px=Zlatan-T... , subpar products, and breakdowns like this are nice, but you know what's better? Getting a working phone then getting the behind the scenes look rather than 2 unfinished products. It has none of the charm of the n900, at least pinephone is much cheaper, although I don't see a point to a Linux phone when they're mainlining a bunch of snapdragons like the one in the s9, with full network support.
Once postmarketOS succeeds there's little reason to get these Linux phone as devices, and the main reason was good support before postmarketOS ported Linux but the hardware is pretty bad. Poor hardware and poor software for a hefty price, a phone that when sold wasn't even functional and is still rough around the edges.
You’re not wrong that the project has had issues and unforced errors. I’ve felt similar disappointment at the slow progress, misleading statements, and product limitations.
But they’re one of precious few companies with a fighting chance of bringing open software to mobile. For that reason alone, they’re still on the side of the angels in my opinion.
So root for the Pinephone and PostmarketOS, and continue to hold Purism accountable. But if Purism and the Librem have an outside shot at positively contributing to the mobile landscape if given the chance, then entirely-valid criticisms of the company and product should be tempered with that chance in mind.
[+] [-] gentleman11|5 years ago|reply
[+] [-] akiselev|5 years ago|reply
Iterations in electronics are really expensive (my last project cost $30k for 10 assembled prototypes not including of our labor) so most people just copy as much of the manufacturers' reference design as they need. They pour over PCB layout notes and look at how the manufacturer or other customers did and mostly just copy them. Most of my engineering decisions are based on about a dozen black box helper apps that take in my fab's capabilities and signal specs and spit out DRC rules. It gets a little trickier with antenna design but that's often outsourced because you need very specialized facilities for FCC certification anyway.
All in all, it's just like working on a complex distributed system. There are so many things to juggle like R&D budget, per unit COGS and space budget, suppliers and part availability, and supply chain orchestration that it ends up being lots of boring work just to coordinate between all the different experts involved with small bursts of productivity when everyone is properly aligned.
[+] [-] mac01021|5 years ago|reply
Any other consumer-grade phone gets something like 24-36 hours by sleeping a lot (or something).
Should I expect the Librem 5 developers to be able to achieve the same thing before they ship Evergreen?
[+] [-] LawnGnome|5 years ago|reply
The lack of screen off times in the article is definitely worrying, though. That's just as important a metric.
Edited to add: actually, the first graph is screen off, I think. Looks like it's a tick under 10 hours. Which is poor, so I hope there's more scope for software improvement, but I also think is a fairly significant improvement over where they were 6-12 months ago.
[+] [-] boogies|5 years ago|reply
Edit: but my two sibling comments now seem to have more useful information than this one.
[+] [-] cesarb|5 years ago|reply
AFAIK, Android uses suspend-to-RAM heavily (this is what a "wakelock" is all about: it prevents Android from suspending when held), and that has a large impact on battery life.
[+] [-] akiselev|5 years ago|reply
It's unlikely it'll get as good as Samsung or Apple by that time but it should definitely improve. Unless they made some critical mistake in the hardware, they can make continuous improvements in the software.
It's no surprise that this is one of the last things they're focusing on. Idle power management on modern operating systems is hard and is very kernel and hardware specific because kernel interrupt and process scheduling comes into play. Hence why Apple is so good at battery life - they have such unilateral control over the hardware and software stack that they can make optimizations that Linux/Windows/Android really struggle with.
[+] [-] unknown|5 years ago|reply
[deleted]
[+] [-] LockAndLol|5 years ago|reply
Good job.
[+] [-] mikece|5 years ago|reply
[+] [-] kop316|5 years ago|reply
https://wiki.mobian-project.org/doku.php?id=pinephone
How to set up a wifi HotSpot is here: https://wiki.mobian-project.org/doku.php?id=tweaks
Although note, as of now, neither the Pinephone nor the Librem 5 can do MMS (they both share ModemManager and it doesn't have MMS functionality)
[+] [-] gentleman11|5 years ago|reply
An aside: if apple would stop making the new iOS updates so draining on older phones it would help - the last iOS update took my battery from 2.5 days without a charge to 1.7 days “overnight” - imagine what this did to people who didn’t buy the silly oversized model with the lower screeen resolution? It’s basically a malware attack on their users to force them to update
[+] [-] jchw|5 years ago|reply
There’s really two problems.
1. Speed. The CPUs are just underwhelming. It is not unusable by any means, but it definitely feels like many steps backwards. I think at least the PinePhone needs to be running lighter software; Wayland is certainly not an issue, but a lot of heavy GTK software is probably not a good idea. Web browsing is tricky and makes me wish there existed lightweight browser engines that implemented less of the web standard, but it is actually passable believe it or not.
2. Linux desktop software is just not designed for phones. I think Phosh is clever, and feels very nice to use... until you remember its a phone, and then realize the inherent differences. Normal phones have some kind of central push notification management, but not here. I assume when the device sleeps, you simply stop getting any notifications. I haven’t actually seen a notification pop up on the lockscreen yet, so I’m not sure. There’s an SMS and messaging app, and Telegram/tdesktop works really well, so there is that.
I think that both problems could be solved somehow, but it’s feeling like it could be a tough one. One of the things that both iOS and Android did right off the bat was dramatically change the model of execution that apps had, to orient them around the concept of constantly being swapped in and out. There’s really no obvious way you can support standard Linux desktop apps without some compromise here. I would actually be pretty happy if these devices were capable of just staying awake on a low frequency most of the time, because I think that would dramatically simplify things, but you would have to worry a lot about power draw from apps running and etc in ways that you don’t have to in most modern phones.
Some may view the lack of a good push notification story as a benefit, but for me there are definitely things where I want it to be reliable and timely... so I am left feeling a bit lost.
[+] [-] airstrike|5 years ago|reply
[+] [-] Waterfall|5 years ago|reply
[+] [-] retpirato|5 years ago|reply
[+] [-] gibsonhouse|5 years ago|reply
[+] [-] ta17711771|5 years ago|reply
AOSP is one of the most secure consumer OS around right now, surprisingly.
[+] [-] Waterfall|5 years ago|reply
[+] [-] Townley|5 years ago|reply
But they’re one of precious few companies with a fighting chance of bringing open software to mobile. For that reason alone, they’re still on the side of the angels in my opinion.
So root for the Pinephone and PostmarketOS, and continue to hold Purism accountable. But if Purism and the Librem have an outside shot at positively contributing to the mobile landscape if given the chance, then entirely-valid criticisms of the company and product should be tempered with that chance in mind.
[+] [-] pcdoodle|5 years ago|reply
Also their desktop OS is pretty sweet. If they converge the two (texts, clipboard, calls), it will be worth the bumps in the road.
I will pick one up when 14nm is introduced. It's a damned server in your pocket.