Exactly this (when nitpicking the phrasing). Is putting the finished unit in the box "assembly" of the delivered product?
OTOH, I'm not sure how much it matters. Apple products are "designed in California" (which is a bit of a lie to begin with), and very much assembled overseas.
Of more interest is how few units they've pre-sold compared to mainstream phones. I wish them well, but I doubt they'll change history.
Is putting the finished unit in the box "assembly" of the delivered product?
I've seen "Packaged in $country" on boxes before, so I suspect they are two different things.
Like food made in Canada that shows up in American chain stores being labeled "Distributed by QFC." There's lots of rules about this sort of thing.
Reminds me of back in the late 90's when Wal-Mart was all rah-rah about "Made in the USA!" on all of its products. Then my company bought every employee a Sam's Club membership and the cards were all marked "Litho en Mexico."
It's almost like a "ship of Theseus" problem. If something arrived in Finland for assembly that could theoretically be disassembled, does the final product count as being assembled in Finland? What even counts as "assembling"?
Stuff gets put together in Finland to form the final device they ship, even if the parts aren't made in Finland. I think a dictionary lookup for "assemble" might help if this explanation did not.
Well, assembly can mean that a pick and place machine is assembling individual capacitors onto a raw circuit board, or it can mean a teenager putting the battery in and putting the battery cover on before packaging it. That’s why “look it up in a dictionary” comments aren’t helpful. We aren’t confused about the word, we are confused what it means in this use because it can have a VERY broad definition.
Pick and place PCB assembly is very different from the final assembly of batteries in terms of who is capturing value and building a reasonable moat. Their sales angle is around European autonomy.
Low wage workers putting batteries in phones is not that, but PCB assembly is much closer to that.
Seems much more likely to me that the main board of the phone is assembled in China and the battery and the case, and perhaps the screen are added in Finland. But it would be nice to know for sure.
I don't know anything but I thought it's the opposite of that? I thought pick-and-place machines are like fancier 3D printers, and they can be bought and copied anywhere sufficiently advanced, but low-wage assembly workers are organic AGIs that require multi year culture building and prompt engineering know-hows accumulation to be able to achieve and maintain even usable yield rates and cannot be spun up overnight, especially after a workplace was once torn down.
Or am I just spoiled by apparent local regional abundance of cheap roboticists?
Pick a place machines are operated by experts, require supply chain planning to ensure you have the right parts with the right specs, the boards have to be tested, you have to diagnose issues. You have to understand solder bath temperature profiles. You have to have solder baths (large precision controlled vats of molten metal). It’s a complex problem.
Hiring people to put batteries in phones and phones in boxes? Never done that specifically, but other assembly line stuff like that does not require much. Certainly not a multi year culture building process. I used to work for a company that built food gift boxes. When we staffed up for the holiday season, it took about 20 minutes to train new hires. We once added an entire line in a day to make a custom product. I’m not saying that the managers and workers didn’t work hard, but it was not particularly complex work. Most of the difficulty was in finding ways to reduce packing times by a few percentage points.
Put this way: your company have a week to build one of the above processes for 1500 phones a week, and they get a $1mm bonus if they succeed. Do you choose pick and place assembly or battery assembly.
I really wanted the official Ubuntu phone to catch on. I gave to the IndieGoGo for it but sadly it wasn't funded, so I installed Ubuntu mobile on a different old phone (a OnePlus One I think?) like a decade ago.
I thought it was very cool. It felt a lot more like a "computer that I could use as a smartphone" than a "smartphone with some computer stuff". I thought the interface was clean and nice and it was fun to hack on.
I really should buy a compatible phone and play with it again...I'm sure they've done a lot of work on it.
Wanted to mention that Sailfish has a lot of closed-source components, especially UI-related, despite the overall marketing/"vibe" making it look very open. If anything, AOSP (Android) is more open than Sailfish. I don't think this has changed with Sailfish 5, see e.g.:
Huh. I really don't see the point of this, vs something like GrapheneOS.
Edit: I'm well aware of the differences between typical Linux and Android (especially the security architecture!), and I'm willing to make some sacrifices in the name of FOSS... but only if it's actually FOSS.
I read somewhere that the owners have ties to russia, but the most important thing is that they’re marketing very aggressively through posts that slander GraphenOS.
I know the people behind SailfishOS, they’re not like, friends or anything: just ex-Nokia developers who got fucked by Microsoft (like I did, btw, which is how I know of them).
I feel like the big tech smartphone duopoly would have a reason to spread such rubbish, but its so patently obvious that I doubt they are so stupid.
It’s a sensitive topic for the US because it is an an EU-backed and funded project to move away from US tech, which undermines US interests globally. which is why you might see some unusually intense anger/vitriol hurled their way and Goebbels-level fabrications
"It acquired new investors in 2016, among them the Russian company Votron. In March 2018 they were joined by Rostelecom (which is state owned) as investor, which took over Votron and OMP."
Note that was after 2014 russian invasion into Ukraine.
After the 2022 invasion of Ukraine, Jolla moved to cut ties.
It sought to disengage from any Russian ownership from early 2022, entered corporate restructuring at the Pirkanmaa District Court, and on 24 November 2023 the court approved a programme obligating a complete sale of the business.
In May 2024 the original Jolla company filed for bankruptcy, its activities having been taken over in 2023 by the Jollyboys company established by Jolla’s former management.
The current entity is owned by the management team, with no Russian stake. So as of now, the “Russian-owned” framing is substantially outdated.
The word to describe this is /законтачений/ . Some people are to be avoided even if they maintain the outward appearance of normalcy and not even realize themselves what the problem even is. Trust bit permanently burned, nothing to see here.
IIRC the company tried to become a major mobile operating system in the BRICS countries, which led to Rostelecom, the Russian state telecom operator, purchasing a majority state in the company in the mid-2010s. After Russia invaded Ukraine, the company's management started a new company and moved all their employees and IP over to it to escape the Russian ownership.
Russian Aurora OS was an official Sailfish OS offspring, focused on MDM devices, but Sailfish cut ties with Aurora in 2022, after the Russia-Ukraine war has emerged. It's now developed independently of Sailfish, although they share the same code since the codebase was unified before the split.
FWIW, as someone who is not in the phone OS development world at all but has been reviewing phones with alternative OSes for about the last 4 years...
My impression is that everyone else in the phone-OS and deGoogled-Android world hates the GrapheneOS folks, and it's mutual. They seem to be borderline impossible to work with, very arrogant and protectionist, and the project's own support lifetime is "when Google no longer supports your phone, we don't either."
Personally, I'd choose something else. Anything else, in fact.
They also do not post much on LineageOS and when they do it usually articulates the difference between both (with LineageOS focusing more on customizability, while being much less secure).
I think the strongest disagreement is with /e/OS, which is not surprising, because their founder goes around to various widely-viewed/read media insinuating that security hardening/GrapheneOS is only for pedophiles and spies.
They seem to be borderline impossible to work with, very arrogant and protectionist,
As a user, they seem to be responsive to bug reports and actively helping out people in their forums. Not sure what else I need.
and the project's own support lifetime is "when Google no longer supports your phone, we don't either."
But that makes sense, right? One of the main foci of GrapheneOS is security. If Google stops supporting a Pixel model, there will be no more updates of firmware bundles, etc. Most firmware has monthly CVEs, pretending that it doesn't would go counter one of the main goals of GrapheneOS. If you want to maintain such a phone as an insecure device after Google's update period, there are other options you could switch to.
I am also not sure how much this matters. Even Pixel budget devices (a-series) have 7 years of security updates now. It's not only one of the longest in the industry, it's probably beyond how long 95% of the population uses a phone.
Given how sensitive information most people have on their phones (banking, chats, and whatnot), it's a disaster in the making.
The typical answer is "but I'll only use open source apps that I trust". Sandboxing doesn't only protect you against rogue apps, it primarily protects you against 0-days in apps that you do trust.
Sorry, this does not make any sense. E.g. vanilla GrapheneOS does not have Google Play services and no analytics from big players at all.
Even if you choose not to install Play Services/Play Store, you will still have access to many more apps than on SailfishOS - from many open source Android apps to proprietary apps that you can download without the Play Store. Plus, with the Linux terminal support in Pixels (note: not all Android phones support this, e.g. Snapdragons don't support privileged virtualization), you can also run Linux desktop apps.
/etc configuration instead of the insanely bad system properties crap, glibc instead of bionic (which has even worse POSIX compliance than Windows), ld instead of linker, FHS, not having a batshit insane No-Sockets rule, not needing to port software that already compiles and runs on GNU/Linux, X11/Wayland/Arcan, system services aren't entangled with Java, normal IPC mechanisms instead whatever the fuck binder is. The list goes on.
Android (and by extension GrapheneOS) uses Linux as a kernel, but it lives in its own world and is completely unrecognizable. I'd say it's even more alien than macOS. For most users, the differences don't matter. If you're a programmer or a sysadmin with reasonable expectations, you feel like a fish out of water very fast. And I cannot honestly the changes are for the better.
The irony you fail to realize, the differences listed in fact would be typical of a random Unix system in the 80s, where it's just a mountain of bad and random opinions stapled on top of a Unix system. Some random and half-baked libc? You got it! Some bizarre and overly convoluted greenfield filesystem structure? It's right there! Completely different and frustrating custom linker behavior? Yep!
Everything I listed was an advantage. Now see, I don't think Unix is the be-all end-all of operating systems design. I don't particularly care for Linux, the BSDs, macOS, etc. But Android is a definite regression in the strongest terms. Give me a PIMOS or Genera or Squeak phone that works well. I'll be happier than I would with a Linux phone.
> /etc configuration instead of the insanely bad system properties crap, glibc instead of bionic [...]
The practical downside, however, is that this phone does not natively run Android apps, while GrapheneOS runs all Android apps bar those that require Play Integrity. Desktop GNU/Linux programs are either unusable or a terrible experience on a mobile device with a small screen and no mouse.
Also Play Integrity (if you run sandboxed Google Play Services), but it only passes at the basic level, which is enough for most apps that use Play Integrity.
That's true, but is contingent on you running those Android apps for it to be meaningful. I have a very small number of interactive things I do with my phone. For me what matters is that writing software isn't a pain in the ass, my usual expectations on storage (eg remote filesystems) works and works well, maintaining my system works, my non-interactive system scripts work, etc. Almost all of this is broken on Android, and it doesn't really make up for it by breaking it to make it better. I find much of the design choices of the operating system to be completely tasteless.
If you say, rely on google maps, banking apps, apps for your IoT appliances, etc. it's certainly relevant. I don't have any of that though.
For me the most and truest pressing issue is that cell modems are very, very tightly coupled with Android. It's still true for the Jolla Phone that it simply is a worse phone because the modem drivers are buggy. This is a complicated issue that isn't getting better, and is mostly to do with legislation legally mandating the tivoization of cell modems, a weird line in the sand on what responsibilities fall to the hardware or to what software, as well as the modem manufacturers themselves not really caring.
For me the most and truest pressing issue is that cell modems are very, very tightly coupled with Android. It's still true for the Jolla Phone that it simply is a worse phone because the modem drivers are buggy.
My impression (also for Ubuntu Touch, etc.) is that all these systems use the upstream vendors' Linux kernels trees and firmware blobs for Android.
Unfortunately, since we are not talking about Samsung or Google, but just some random Chinese ODMs, it's usually years old Linux versions and ancient firmware blobs full of known holes (e.g. the C2 is running a Linux tree from October 2022). It's only thanks to the tireless work of postmarketOS etc. that some devices boot on modern kernels.
> Desktop GNU/Linux programs are either unusable or a terrible experience on a mobile device with a small screen and no mouse.
Is this an assumption or coming from your experience? Because I'm typing this on a GNU/Linux phone in a desktop browser and use a bunch of desktop applications daily and haven't noticed.
Of course if you run GIMP or something like that it won't fit unless you plug an external screen and a mouse in, but all the applications I use daily are perfectly usable. There's a lot of Kirigami and libadwaita programs these days that just work well on a phone, and if I need to launch my bank's application there's always Waydroid.
Could you please elaborate, which software is usable on mobile Linux except for Firefox? I've seen multiple people using mobile Linux, and they were using Firefox and webapps for everything, no exceptions.
I can use most native GNU/Linux apps on my Librem 5 like gnome-calculator, gnome-calender, gnome-weather etc. I can run Android apps via Waydroid. F-Droid works fine, too. Its default app store (https://software.pureos.net/categories) provides things like music players, OTP app, and games. Flatpak works, too.
To add to others. You can tell Kimi or whatever these days to write you a GTK4 mobile apps for a lot of pet use cases and it will. The result will also be a few C files and a meson build file, that will build on the phone itself with just gcc/binutils (I run arch linux, so no separate dev packages for deps like gtk, etc. that I need to install). You can install opencode or whatnot on the phone itself, and tell the phone to build you an app, and it will. If you need it changed, you can just ask for the changes on the phone itself and agent will update the app's code and re-build it on the phone itself. It will not need the 30+ GiB monstrosity of whatever Adroid needs to just build a hello world app and a separate computer.
The app will also build and run on your desktop without any/many changes, if you need that.
I got a fairly nice linphone GTK4 phone frontend app this way. So it's not just for toy apps. FOSS/Linux phones are well positioned for this self-building/self-updating prompt based software development, because you don't need separate computer and shitton of SDKs and a permission from the overseer to build/install the apps, and while phone UI is shit for manual programming, it's not at all shit for writing prompts.
Well, can you take a picture that looks better than what I made 20 years ago on a flip phone?
I have a pinephone and try it out year after year.. Well, let's just say that there is so many areas of improvement to make "GNU/linux" run on a mobile device (that sorta includes laptops as well, even though I have done so for years) that we might as well start over from statch.
For example one can't just let everything run whenever it wants, wasting battery life. Android's "more complicated" system and binder was criticized in this thread, but that's exactly what ties together the whole thing to be able to run on a device that fits in your hand, with centrally managed "let's pause this app now" etc
Also, I'm perfectly capable of deciding whether I need an application to be running at a given moment myself, I don't need the OS to make dubious decisions for me.
Ehm, a Pixel 9a is currently 349 Euro here (10a 399 Euro). Given that the OS is free, that's only a 19 Euro difference. For a much better camera, much better SoC, much better pretty much everything.
Of course, if your goal is to run SailfishOS, there is currently not much of another option.
My phone is a couple of years old at this point. A Pixel 7 was the newest i think. I don't care about cameras, I don't care about specs. All I need is listed.
My phone would have a screen time of a few mins per day. I can't stand doing anything on these tiny touch screens or browsing the web on a phone screen.
The Pixel A lineup has always been affordable. Heck, the 4a was even $349 at introduction. The currently start a little higher, but are often around 350 Euro halfway the cycle.
and I don’t consider buying used and flashing “giving Google my money”.
Although it definitely enables the market for Pixels, they definitely don’t make much (if any) money selling Pixels, due to they’re being cheap-yet-flagship devices.
It might even hurt Google for you to buy them and not capture all your data with their OS!
If it has the "security" architecture of Linux (it's really more of a multi-tenant architecture) then that's a complete deal breaker. Wouldn't want it if it was 1000x faster/betterer than Android.
Our desktop OSes are just incompatible with running untrusted software, and you're gonna want to do that.
I don't think this is true at all? AOSP is completely open source modulo driver blobs (which Sailfish has too) and Google services.
One can make a fully functional system, modulo drivers, out of only open-source components using AOSP. It's not possible to do this using Sailfish; the compositor, UI libraries (Silica), and most of the "core" apps are still closed source.
I think people got too used to bundling by Apple and Google. For most of the core apps there are good and open source alternatives available.
The main point is that AOSP as a system (modulo firmware) is open source and SailfishOS is not. Also, even though Sailfish has an Android compatibility layer (though only for official devices), compatibility is most likely always going to be worse than 'real' Android.
That said, I hope that Jolla Phone becomes a success, more competition is good. Hopefully being funded better will move them to fully open source the base system.
Because no one was using them. Everyone was replacing them and shipping other apps. AOSP is very modular and customizable letting you configure what apps get included in the OS.
The Email app had been forked into K-9 Mail, which later became Thunderbird for Android. AOSP Browser no longer made sense to develop after Chromium was ported to Android. And so on. The barebones applications in AOSP have been succeeded by better open source apps outside the AOSP repos. It doesn't make sense to maintain them when nobody putting together an Android distribution would choose to use them over those alternatives.
Ahh, thanks for the correction, it's the window manager that's closed (lipstick-jolla-home). Regardless, I will stand by my statement that a fully open-source build of AOSP is significantly more complete and useful than a fully open-source build of Jolla.
If we're going to start counting forks, we get to count LineageOS and GrapheneOS for Android, and then the goalposts really move.
A pure AOSP distribution is now lacking a lot of basic apps. Distributions like LineageOS or GrapheneOS fill the gap with their own, but pure AOSP is totally unusable.
Googles been quietly chipping away at AOSP for years. There was a point where AOSP was actually decent, google made sure that wasn't the case for long.
It literally contains links to all the AOSP repos or GrapheneOS forks of them. You can clone these exact repos and build the OS from source. GrapheneOS provides instructions for it: https://grapheneos.org/build
If the openness is important to you, you may want to have a look at other GNU/Linux phones, Librem 5 and Pinephone. The former runs an FSF-endorsed Debian derivative.
Mal, from Jolla has ports to from the 2 till the 5, I believe. I used an FP2 for about a year. Big difference is andoid app support, not present on the fp ohones.
I like the idea of these new phones that might be a bit more privacy centered, and even with some different OSes but I think the biggest problem for a lot of adoption is the compatibility with things like banking apps, 2fa etc. It makes it quite an impossible daily driver thanks to some strange rules.
I think the challenges here exist but the reality is overblown to be honest, the vast majority of banking apps (everything that isn't struck through in that list) work just fine.
Fully agree the concern is discouraging adoption though. I would love to see more of a solution here, it seems like purely anti-competitive behaviour by Android that will block competitors emerging.
I don't think you NEED to open your online banking on your phone every day. Just use cash and cards.
That's an overgeneralization. In many countries online payments require approval through a smartphone. There are also banks that barely have a mobile banking website (e.g. Bunq last time I had it).
Yup. Which I like, but not the lock in. Anything over 100€ I have set to manually approve by the app. Also if I need to quickly transfer some cash to my current account, who I do regularly enough, I'm a bit out of luck.
I've not heard of a bank in the last while that doesn't have the restrictions, at least in Ireland and Italy.
2FA is not an issue. Many, but not all banking apps work fine. I have an android phone for 3 apps which I need about once a month. Daily driving a linux phone since 2016.
I get all my 2FA through SMS or a Yubikey. It took a bit of wrangling from corporate IT, but it was "Get my yubikey or SMS working or buy me a company phone and pay for service that I won't use for anything else"
I never really did a lot of banking on my phone before, but it really wasn't that hard to let that go. I'd say the biggest hangup is not having Venmo or something for splitting bills with friends, yard-sales, etc, but I've started carrying some amount of cash again for those instances and it's worked out alright.
Been daily driving a dumbphone since 2023. Yes it takes a bit of work, but it's so SO worth it.
I still can't take a device with a mid-range Mediatek seriously. Probably from my XDA days, where just its presence meant locked bootloaders and no kernel sources.
Congrats on selling them but "assembled in EU" can't be the main selling point.
OTOH, I'm not sure how much it matters. Apple products are "designed in California" (which is a bit of a lie to begin with), and very much assembled overseas.
Of more interest is how few units they've pre-sold compared to mainstream phones. I wish them well, but I doubt they'll change history.
I've seen "Packaged in $country" on boxes before, so I suspect they are two different things.
Like food made in Canada that shows up in American chain stores being labeled "Distributed by QFC." There's lots of rules about this sort of thing.
Reminds me of back in the late 90's when Wal-Mart was all rah-rah about "Made in the USA!" on all of its products. Then my company bought every employee a Sam's Club membership and the cards were all marked "Litho en Mexico."
Pick and place PCB assembly is very different from the final assembly of batteries in terms of who is capturing value and building a reasonable moat. Their sales angle is around European autonomy.
Low wage workers putting batteries in phones is not that, but PCB assembly is much closer to that.
Or am I just spoiled by apparent local regional abundance of cheap roboticists?
Hiring people to put batteries in phones and phones in boxes? Never done that specifically, but other assembly line stuff like that does not require much. Certainly not a multi year culture building process. I used to work for a company that built food gift boxes. When we staffed up for the holiday season, it took about 20 minutes to train new hires. We once added an entire line in a day to make a custom product. I’m not saying that the managers and workers didn’t work hard, but it was not particularly complex work. Most of the difficulty was in finding ways to reduce packing times by a few percentage points.
Put this way: your company have a week to build one of the above processes for 1500 phones a week, and they get a $1mm bonus if they succeed. Do you choose pick and place assembly or battery assembly.
I thought it was very cool. It felt a lot more like a "computer that I could use as a smartphone" than a "smartphone with some computer stuff". I thought the interface was clean and nice and it was fun to hack on.
I really should buy a compatible phone and play with it again...I'm sure they've done a lot of work on it.
...
- https://forum.sailfishos.org/t/sailfish-os-clarifying-claims...
- https://docs.sailfishos.org/Develop/Open_Source/
Edit: I'm well aware of the differences between typical Linux and Android (especially the security architecture!), and I'm willing to make some sacrifices in the name of FOSS... but only if it's actually FOSS.
I know the people behind SailfishOS, they’re not like, friends or anything: just ex-Nokia developers who got fucked by Microsoft (like I did, btw, which is how I know of them).
I feel like the big tech smartphone duopoly would have a reason to spread such rubbish, but its so patently obvious that I doubt they are so stupid.
"It acquired new investors in 2016, among them the Russian company Votron. In March 2018 they were joined by Rostelecom (which is state owned) as investor, which took over Votron and OMP."
Note that was after 2014 russian invasion into Ukraine.
It sought to disengage from any Russian ownership from early 2022, entered corporate restructuring at the Pirkanmaa District Court, and on 24 November 2023 the court approved a programme obligating a complete sale of the business.
In May 2024 the original Jolla company filed for bankruptcy, its activities having been taken over in 2023 by the Jollyboys company established by Jolla’s former management.
The current entity is owned by the management team, with no Russian stake. So as of now, the “Russian-owned” framing is substantially outdated.
I would really appreciate it if you could give some references - any at all - to back this claim.
All I have seen is GrapheneOS folks (or probably just a certain individual affiliated with the GrapheneOS org) accusing them of doing this.
FWIW, as someone who is not in the phone OS development world at all but has been reviewing phones with alternative OSes for about the last 4 years...
My impression is that everyone else in the phone-OS and deGoogled-Android world hates the GrapheneOS folks, and it's mutual. They seem to be borderline impossible to work with, very arrogant and protectionist, and the project's own support lifetime is "when Google no longer supports your phone, we don't either."
Personally, I'd choose something else. Anything else, in fact.
I don't think that is true. Team members regularly speak positively of iPhone security. E.g.:
https://grapheneos.social/@GrapheneOS/113874795519341571
They also do not post much on LineageOS and when they do it usually articulates the difference between both (with LineageOS focusing more on customizability, while being much less secure).
I think the strongest disagreement is with /e/OS, which is not surprising, because their founder goes around to various widely-viewed/read media insinuating that security hardening/GrapheneOS is only for pedophiles and spies.
They seem to be borderline impossible to work with, very arrogant and protectionist,
As a user, they seem to be responsive to bug reports and actively helping out people in their forums. Not sure what else I need.
and the project's own support lifetime is "when Google no longer supports your phone, we don't either."
But that makes sense, right? One of the main foci of GrapheneOS is security. If Google stops supporting a Pixel model, there will be no more updates of firmware bundles, etc. Most firmware has monthly CVEs, pretending that it doesn't would go counter one of the main goals of GrapheneOS. If you want to maintain such a phone as an insecure device after Google's update period, there are other options you could switch to.
I am also not sure how much this matters. Even Pixel budget devices (a-series) have 7 years of security updates now. It's not only one of the longest in the industry, it's probably beyond how long 95% of the population uses a phone.
Then again, SailfishOS is a linux with much of the usual linux stuff like userland with bash, coreutils, glibc, systemd, wayland, pulseaudio etc.
https://github.com/sailfishos/sailjail-permissions/blob/mast...
Given how sensitive information most people have on their phones (banking, chats, and whatnot), it's a disaster in the making.
The typical answer is "but I'll only use open source apps that I trust". Sandboxing doesn't only protect you against rogue apps, it primarily protects you against 0-days in apps that you do trust.
If you are worried about big players profiling you (hard to avoid, high likelihood of happening, low likelihood of damage), then you want Sailfish.
If you are worried about apps profiling you (easy to avoid, high likelihood of happening, moderate likelihood of damage), you want Android or iOS.
Graphene and Sailfish sit on different points on that spectrum, just like OpenBSD and Linux do.
Even if you choose not to install Play Services/Play Store, you will still have access to many more apps than on SailfishOS - from many open source Android apps to proprietary apps that you can download without the Play Store. Plus, with the Linux terminal support in Pixels (note: not all Android phones support this, e.g. Snapdragons don't support privileged virtualization), you can also run Linux desktop apps.
Android (and by extension GrapheneOS) uses Linux as a kernel, but it lives in its own world and is completely unrecognizable. I'd say it's even more alien than macOS. For most users, the differences don't matter. If you're a programmer or a sysadmin with reasonable expectations, you feel like a fish out of water very fast. And I cannot honestly the changes are for the better.
Everything I listed was an advantage. Now see, I don't think Unix is the be-all end-all of operating systems design. I don't particularly care for Linux, the BSDs, macOS, etc. But Android is a definite regression in the strongest terms. Give me a PIMOS or Genera or Squeak phone that works well. I'll be happier than I would with a Linux phone.
Only iOS comes anywhere close.
The practical downside, however, is that this phone does not natively run Android apps, while GrapheneOS runs all Android apps bar those that require Play Integrity. Desktop GNU/Linux programs are either unusable or a terrible experience on a mobile device with a small screen and no mouse.
If you say, rely on google maps, banking apps, apps for your IoT appliances, etc. it's certainly relevant. I don't have any of that though.
For me the most and truest pressing issue is that cell modems are very, very tightly coupled with Android. It's still true for the Jolla Phone that it simply is a worse phone because the modem drivers are buggy. This is a complicated issue that isn't getting better, and is mostly to do with legislation legally mandating the tivoization of cell modems, a weird line in the sand on what responsibilities fall to the hardware or to what software, as well as the modem manufacturers themselves not really caring.
My impression (also for Ubuntu Touch, etc.) is that all these systems use the upstream vendors' Linux kernels trees and firmware blobs for Android.
Unfortunately, since we are not talking about Samsung or Google, but just some random Chinese ODMs, it's usually years old Linux versions and ancient firmware blobs full of known holes (e.g. the C2 is running a Linux tree from October 2022). It's only thanks to the tireless work of postmarketOS etc. that some devices boot on modern kernels.
Is this an assumption or coming from your experience? Because I'm typing this on a GNU/Linux phone in a desktop browser and use a bunch of desktop applications daily and haven't noticed.
Of course if you run GIMP or something like that it won't fit unless you plug an external screen and a mouse in, but all the applications I use daily are perfectly usable. There's a lot of Kirigami and libadwaita programs these days that just work well on a phone, and if I need to launch my bank's application there's always Waydroid.
See also: https://linuxphoneapps.org/
There are more, not every application that works fine has metadata filled up (and not everything is on Flathub either).
I do use some webapps, but with Epiphany rather than Firefox.
The app will also build and run on your desktop without any/many changes, if you need that.
I got a fairly nice linphone GTK4 phone frontend app this way. So it's not just for toy apps. FOSS/Linux phones are well positioned for this self-building/self-updating prompt based software development, because you don't need separate computer and shitton of SDKs and a permission from the overseer to build/install the apps, and while phone UI is shit for manual programming, it's not at all shit for writing prompts.
I have a pinephone and try it out year after year.. Well, let's just say that there is so many areas of improvement to make "GNU/linux" run on a mobile device (that sorta includes laptops as well, even though I have done so for years) that we might as well start over from statch.
For example one can't just let everything run whenever it wants, wasting battery life. Android's "more complicated" system and binder was criticized in this thread, but that's exactly what ties together the whole thing to be able to run on a device that fits in your hand, with centrally managed "let's pause this app now" etc
Also, I'm perfectly capable of deciding whether I need an application to be running at a given moment myself, I don't need the OS to make dubious decisions for me.
But I hate phones. All I want is navigation, sms/call, signal, steam and firefox.
https://commodore.net/callback/
It's pretty cool looking! Very optimistic about it.
Of course, if your goal is to run SailfishOS, there is currently not much of another option.
My phone would have a screen time of a few mins per day. I can't stand doing anything on these tiny touch screens or browsing the web on a phone screen.
A cheaper 6a would be EOL next year.
They also came later vs 6/6Pro
6a is a 2022 phone, 7a is $150 on Swappa.
Where are we going with this?
All I can give you is my reasoning for picking it. Not giving google my money is always a plus in my book.
and I don’t consider buying used and flashing “giving Google my money”.
Although it definitely enables the market for Pixels, they definitely don’t make much (if any) money selling Pixels, due to they’re being cheap-yet-flagship devices.
It might even hurt Google for you to buy them and not capture all your data with their OS!
Compared to Samsungs, they seem to have comparable prices for less performing hardware, to me.
But what about all the other phones?
Are all Chinese manufacturers selling at a loss?
Pixels are manufactured in China, Vietnam and India.
Maybe their flash gates are made by hand, given how much more they ask for decent storage amounts...
so not sold at the same rate.
Price goes down when you do a run of 10 million boards
vs 1 million.
(and or the facility making them is yours!)
Not to mention that the Pixels were a lot more convenient years ago, when they sold a lot less.
I think you're clutching at straws here, Pixels were cheapish in the first versions, but are not anymore ;)
Most people will fill that up in a glimpse without using cloud services
Our desktop OSes are just incompatible with running untrusted software, and you're gonna want to do that.
So you're saying people should only use walled garden closed source OSes? Sounds like tyranny to me.
2) The point still stands, desktop operating systems like Windows and desktop Linux distributions are much less secure than Android or iOS. Read https://privsec.dev/posts/linux/linux-insecurities/
You should have a look at https://qubes-os.org
https://forum.sailfishos.org/t/open-sourcing-proceeding/2468...
https://github.com/sailfishos/sailfish-weather/
https://github.com/sailfishos/jolla-camera
It's still more open than AOSP
I don't think this is true at all? AOSP is completely open source modulo driver blobs (which Sailfish has too) and Google services.
One can make a fully functional system, modulo drivers, out of only open-source components using AOSP. It's not possible to do this using Sailfish; the compositor, UI libraries (Silica), and most of the "core" apps are still closed source.
A true AOPS image is missing most core Apps.
The main point is that AOSP as a system (modulo firmware) is open source and SailfishOS is not. Also, even though Sailfish has an Android compatibility layer (though only for official devices), compatibility is most likely always going to be worse than 'real' Android.
That said, I hope that Jolla Phone becomes a success, more competition is good. Hopefully being funded better will move them to fully open source the base system.
And OSS projet based on the SFOS core exist : https://nemomobile.net/, https://github.com/nemomobile-ux
If we're going to start counting forks, we get to count LineageOS and GrapheneOS for Android, and then the goalposts really move.
Uh, no? How are you getting this idea?
This is the manifest file for GrapheneOS: https://github.com/GrapheneOS/platform_manifest/blob/17/defa...
It literally contains links to all the AOSP repos or GrapheneOS forks of them. You can clone these exact repos and build the OS from source. GrapheneOS provides instructions for it: https://grapheneos.org/build
I think the challenges here exist but the reality is overblown to be honest, the vast majority of banking apps (everything that isn't struck through in that list) work just fine.
Fully agree the concern is discouraging adoption though. I would love to see more of a solution here, it seems like purely anti-competitive behaviour by Android that will block competitors emerging.
I don't think you NEED to open your online banking on your phone every day. Just use cash and cards.
2FA should be easily available on any OS
That's an overgeneralization. In many countries online payments require approval through a smartphone. There are also banks that barely have a mobile banking website (e.g. Bunq last time I had it).
I've not heard of a bank in the last while that doesn't have the restrictions, at least in Ireland and Italy.
I never really did a lot of banking on my phone before, but it really wasn't that hard to let that go. I'd say the biggest hangup is not having Venmo or something for splitting bills with friends, yard-sales, etc, but I've started carrying some amount of cash again for those instances and it's worked out alright.
Been daily driving a dumbphone since 2023. Yes it takes a bit of work, but it's so SO worth it.
Congrats on selling them but "assembled in EU" can't be the main selling point.
Currently Russia is sanctioned so it’s illegal to do business there. If it were legal they would be straight back.