The Librem 5 has been delayed for years and the behaviour of the company is kind of sketchy, however going by Purism's videos the software is pretty good and getting better rapidly (and they upstream their changes back to Gnome).
The PinePhone has shipped to some developers and the company has a history of actually making functional products, but the software is still a WIP, and Pine64's products are cheap (which is great for many people, but I would rather have a $400 phone than a <$150 phone, especially given that these ones won't suffer from software obsolescence).
I can't wait for these things to become at least somewhat functional - I personally will be buying one as soon as they get phone calling, SMS, and a web browser (the Librem has them, and other Gnome applications, but it's still in preorder).
Librem 5: https://puri.sm/products/librem-5/
- https://puri.sm/posts/librem-5-vs-android-which-boots-faster... (stupid comparison vs a 6 year old Android phone - how out of touch is their marketing team and CEO to allow this to happen???)
Unfortunately other than the hacker niche that's on this forum you won't get the average consumer using these devices/OSes and therefore you won't get the apps that attract people to use the devices in the first place.
So, while there will be some effort required to make gui programs work, libhandy supposedly makes this pretty easy. It's an order of magnitude less effort than porting an app from a different platform. Not to mention that everything CLI should Just Work -- this is not relevant to most mainstream users, but it's very relevant to the developer story; I think it's likely that FLOSS developers will start targeting these phones as soon as they become usable enough to developers. Personally, I'm planning to get a Librem 5 as soon as they're off backorder and there are reviews from non-affiliated parties (the latter might be now; I check every couple months and it's been about that long since I checked last).
If anything, it proves the point that GNU/Linux doesn't sell phones to make a sustainable business out of it.
The need is not going away anytime soon. I generally like what Apple and Google have done for the mobile phone market, but it’s time for folks to take back some control of their devices which the execs will likely not agree to.
The radios are too locked down and the software too. Despite good intentions, I’m concerned this gatekeeping could become corrupted/corrupting in the future.
If you support the rough and tumble world of open source and systems, you’ll plant a seed that a future generation can grow and compete with gatekeepers. This may reduce the corrupting forces from the gatekeepers. They could point to open systems and say, “Look government, your plan won’t work because 3% use an unrestricted phone, and more will follow if you force us to do X to everyone’s phone.”
They've got some funding from Google as well.
I also suspect that a phone with hardware closer to a ~$400 android phone would be much harder to support with open source software/drivers.
Can you elaborate?
There's a reason an old raspeberry pi, a device with a fraction of a smartphone power - and without a screen to booth, it an infinitely more valuable device.
You can buy used smartphones on ebay for nothing. They are being thrown out. Why don't we see those used for something other than alarm clocks and fancy picture frames?
The truth is that you can use a raspberry to do anything you want but converting an old, even unlocked, smartphone to something which is not a screen for a browser is incredibly, INCREDIBLY hard. Getting to run plain linux on these devices and take advantage of the screen or other peripherals is generally a waste of effort due to binary drivers. What you get in most of the cases will be serial access and a flash drive for storage. Keeping android on it only forces you to develop for an OS that doesn't want you to be in control OR get access to the system.
As soon as your typical smartphone gets out of support, it becomes e-waste.
What I miss, personally, is some kind of ecosystem along with guides, etc where I can learn how to build Android from sources, put some binary drivers from official image and run it on my phone. May be even some guides how to reverse engineer proprietary drivers and rewrite them as open source.
> learn how to build Android from sources
https://source.android.com/setup/start has instructions.
> put some binary drivers from official image
https://source.android.com/setup/build/gsi is a set of builds you can flash on any sufficiently modern Android device alongside their binary drivers.
> May be even some guides how to reverse engineer proprietary drivers and rewrite them as open source.
You're on your own for this, but given the kernel and HAL APIs are both open source you could theoretically figure out how to build a viable implementation, but no matter how you go about it, building something like a GPU driver is a substantial task. You could probably build things like the lights HAL without too much difficulty though.
- packet->len = partial_packet->len - partial_packet->offset;
+ packet->len =
+ (partial_packet->len - partial_packet->offset) + packet->offset;
Qualcomm stops supporting their processors after a few years, usually three. They can make more money by selling new chips. Although I say this cynically, Qualcomm is actually the best third party vendor in this regard.
Edit: J"ust like their predecessors, they'll get Android security updates for three years, until October 2022." says Android Police.
Considering most people don't buy it at launch, this amounts to 2-ish years of support on average.
I assume Google can afford a couple of lawyers.
At least Samsung is pretty good about updating patches. Not android versions, no, but at least I still get monthly patches. My S8 already has this one.
It's a cherry-pick (a copy of a commit from related code base, essentially) of this commit, https://android.googlesource.com/platform/system/bt/+/337bd4.... The bug has a different impact in Android 10 (DOS instead of RCE), which was relased in Septemer 2019. So maybe they sort of fixed it in Android 10 and somehow forgot the backport? I'm speculating.
You get a garbled binary SMS, and then the virus resends itself to every number in your phonebook.
> This virus first appeared in 1988 on earlier versions of Mac OS. Initially, the program displayed a message about Michael Dukakis (Democratic presidential candidate):
> I was created by mischievous 14 year old, and am completely harmless. Dukakis for president in ’88.
I assume via BTC or any crypto, it’s just a matter of running a “miniminer” of some sort across all effected machines?
If you need Bluetooth then check whether your phone has the same Broadcom driver - you might be fine depending on hardware. Or check if you can install open source firmware that includes a fixed driver.
There are other things you can do depending on device.
But it's less of a problem in iOS anyway, because Apple provides updates for iPhones much longer. They are still releasing security updates for the iPhone 5s and 6, which are from 2013 and 2014 respectively.
No wonder that Android 11 will require hardware memory tagging and is now introducing GWP-ASan for the devices without it.
I give up on technology.
So it is back to rotary phones and public booth.