The main reason I stopped using Lineage is because I got a Pixel and wanted to keep maximum picture quality with it. Open-source photo applications, from what I understood, cannot access all of the hardware features to get photos as good as Google's app.
Is it enough to get the Google Camera APK somewhere else and use it? Or do I really need to keep the OS as Google intended, in order to get best picture quality? I don't have the time lately to do much tinkering and compare it by myself.
I think the same issue was had if you used an Xperia phone long ago (I think mine was an XZ1c). It was really disappointing that the camera was worse if not using official software due to DRM keys or what not.
> The main reason I stopped using Lineage is because I got a Pixel and wanted to keep maximum picture quality with it.
I think if you get a Pixel, then you should use either Stock Android or GrapheneOS. I don't see the point in using something else.
> Is it enough to get the Google Camera APK somewhere else and use it?
With GrapheneOS, you can install the Play Services, the Play Store and then the Google Camera. I would be surprised if that wasn't enough. In fact I would be surprised if you needed more than the Camera APK. But like you, I haven't made the comparison. Would be interesting!
>With GrapheneOS, you can install the Play Services, the Play Store
Why use GrapheneOS if you are going to install Google Services anyway? The whole point of Graphene is to have a fully locked down OS that still works as it should. A mobile fortress basically. Installing Google Services defeats the point imo as it opens multiple security holes in the fortress.
May as well just install the stock os. At the end of the day, once Google stops shipping sec updates for your phone, firmware updates stop so that's it really. Graphene cannot give you the firmware updates anyway. And at that point, you have a vulnerable phone. I think graphene os makes more sense if you go all in. Otherwise there is no much point really.
It doesn't open up any holes since google play services are not allowed any special access on grapheneOS and run as a regular sandboxed app. You can make a separate user profile just for google apps.
The google camera app should be enough. It's commonly done on GrapheneOS. But the GrapheneOS camera app uses some of the same hooks so it's not as far from Google Camera as some others.
A city I lived in had this, but when the restaurant owner retired, they explicitly forbade the ground floor from being used for some food-related business. It turns out the residents upstairs were always complaining about the smell. NIMBYism won.
A better solution would have been some mandatory grease/odor filters.
Just to point out that "restaurants in every corner" is not always easy to do, especially in residential blocks. I honestly think that "cooking your own food" (with the help of modern kitchen utensils, time-saving equipment, and the exception being collective canteens/cafeterias for specific groups such as students) is economically advantageous. Because even today in many European cities, many of those tending to restaurants are immigrant labor or somewhat disadvantaged groups who are implicitly pushed towards such jobs due to lack of alternatives.
I used to rent an apartment exactly like this in Vienna, the only problem was the somewhat loud and lively crowd late in the evening, never had any smell issues, and this was a 100 year old building
I'm increasingly pessimistic about everyday reach of Linux.
Around me, all I see are Windows users, volunteers teaching old people how to use several tools... on Windows. Public institutions relying on Windows, upgrading to Windows 11, doing everything despite Trump, despite Microsoft, despite all of the negatives associated with it.
When primary school students are given Windows laptops instead of Linux ones, there's not much hope in changing. But how can you amass enough momentum and volunteers to get enough manpower to at least try to move in the other direction?
KDE surely helps, but it's like, nowadays simply trying to explain what a non-mobile OS is useful for, seems like yet another uphill battle, and I cannot fix even my small town by myself.
Inertia is a hell of a drug. The US failed to break up Microsoft in the 90s, and never took antitrust action against them again after that. So the world built its entire tech infrastructure on top of Windows (as far as endpoints go, web facing servers are another matter).
But,
> When primary school students are given Windows laptops instead of Linux ones,
At least this is changing, although not true "desktop linux," students are mostly given Chromebooks, and grow up on google docs/g workspace so that early familiarity with Windows + Office is dissapearing.
It's not going to be a good thing long term though, I already see it with employees where I work (I'm in IT). We have plenty of younger employees that don't even have computers at home if they aren't gamers. They are familiar with iOS/iPad OS only. Windows + Office is a mystical black box, and file management/file systems are a foreign concept.
That, IMO, makes Linux desktop adoption that much more difficult. At least Windows->Linux you can take a lot of basic concepts with you. MobileOS->Not mobile OS is much more difficult.
We do have one main Linux kernel (while other open source like BSD is far less popular on PCs) and a bunch of tools like bash and git that are de facto default. Seems like Linux community actively avoids converging on a default DE though.
We have many, many Linux kernels. Many distros compile their own kernels. You aren't using "the" Linux kernel most likely, you're using your distros Linux kernel. It's just that nobody notices because the kernel has stable interfaces.
Thats also why you can run kernel 6.5 on a version of RHEL from 15 years ago.
By its nature as a community, the Linux community will never converge on a default DE.
The only reason Windows pulls it off is because it's not a community. It's a dictatorship and you're a serf. You use what Microsoft tells you to use.
But, even then, there is divergence. No doubt you've heard of people sticking to 10 even though Microsoft is abandoning it. Some people still use 7, or even XP.
I tried running the suggested code (curl -sL ...) but inadvertently did not check it was missing quotes around '\r'. So after a while I started seeing some errors:
[error] No valid link found according to patterns for 'aboad'
[error] No valid link found according to patterns for 'absob'
[error] No valid link found according to patterns for 'acoss'
I thought "well, there's quite a lot of words I need to learn in English", but after seeing 'addess' and 'adventue' I thought "wait, this is not ight".
Fixing it helps, but there are still missing expressions, such as "add up", "a couple", etc.
Thanks! Fixed that example. (In fish shell that I use, it didn't need those quotes that's why I didn't catch it)
>there are still missing expressions, such as "add up", "a couple", etc.
Googling "pronounce add up" does not show the google short answer box for me. Aside from that, the heuristic method I used may miss some words since it's not quite clear to me how the naming scheme works in that static stash. The 2024 stash is more straightforward but as I mentioned in readme, it sounds synthetic to me.
Did you mean "unrecoverable"? I first read your comment as "ok, the solution is trivially easy so the article is unnecessary", but the rest of your comment implies the opposite.
My data did get unrecoverable after running the command that was shown first when i didn't scroll or read about that command more and I just ran it and it just made it unrecoverable.
So yes it got unrecoverable.
And then I just deleted that drive by flashing nix-os in that and trying that for sometimes, so maybe there is good in every bad and I definitely learnt something to always be cautious about what commands you run
On the free side, you also have Frama-C (https://www.frama-c.com) and its Eva plug-in, based on abstract interpretation, and Mopsa (https://mopsa.lip6.fr), also based on abstract interpretation.
I immediately thought that it feels much easier to carry something with the pole in the picture because the weight rests more closely to a point on the y-axis going through your center of gravity, as opposed to carrying it at the side of your body, where your arms are.
Another possibility: how they carry the basket is different. Maybe when they were sharing the load, they could use both hands or rest some weight on their body, but when they're carrying their individual basket they can only use one hand or can't rest it on their body.
TVs back then supported a given standard (NTSC, PAL) and a lower resolution. CRTs couldn't "buffer" the image. Several aspects made it so that "cheating" was not possible.
It was either fast, or nothing. Image quality suffered, but speed was not a parameter.
With LCDs, lag became a trade-off parameter. Technology enabled something to become worse, so economically it was bound to happen.
The main reason I stopped using Lineage is because I got a Pixel and wanted to keep maximum picture quality with it. Open-source photo applications, from what I understood, cannot access all of the hardware features to get photos as good as Google's app.
Is it enough to get the Google Camera APK somewhere else and use it? Or do I really need to keep the OS as Google intended, in order to get best picture quality? I don't have the time lately to do much tinkering and compare it by myself.
reply