Hmm it seems like they approve proprietaey components under some exceptions, dunno how they could test for llm-slop. But either way, they tend to ask the developer for llm use disclosure, so a developer could lie and have their app passed (though if somehow it's proven they used llms in unwanted way, they'd have issue). Also I guess the developers woild have to justify a proprietary component and theyd have to hide that it's partial purpose is llm code. Shrug

https://izzyondroid.org/docs/general/AppInclusionPolicy/#code-and-license

1. License: The app and its code must be free (as in „free beer“ and as in „free speech“) and Open Source (see e.g. Four Freedoms for what this means). This includes using a libre license, approved by OSI/FSF (see SPDX).

2. The app's code must be freely accessible, preferably at Codeberg, GitLab, Github, or a similar platform (self-hosted Forgejo/Gitea/GitLab instances are supported as well, if they are „permanently“ online and openly accessible).

3. there should be no proprietary components. While some of them might be tolerable if they are essential for the app's core functionality, trackers (e.g. ads, analytics) are not. In addition to them not being F/LOSS, such modules are considered as too intrusive, and hence rejected in general.

Izzy allow non-open source apps. They say they will check, but how can they? Already with the source on hand it is not always easy to determine if the code is from am AI so on parts where sources are not available…

What definition of "vibe coded" are they using?

There is a microG compatibility table, it is only a limited subset but by far less invasive than google play services

That is not what I said?

I said Qualcomm only provides LTS for either their IoT chips or flagship chips and Motorola decided to splurge.

Good to know! I'll look into this.

Yeah maybe I don't need the whole suite of apps... Just the essentials

I read the article. That's why I said they had one job. They act as if unaware that the people who are looking for Graphene OS as a system to use have to resort to used Pixels for that; having to buy tomorrow's phone, even more overpriced, does not really factor in good into the decision.

You should read the article. The only chips that have the required security features (other than Google's tensor chips) are Qualcomm's flagship chips. That's what is driving the cost.

LTS of the chip does not imply flagshipness of the whole brick.

I was expecting a phone that was affordable to the people who care about this stuff in the economy where we exist. Doesn't have to be a flagship.

Heck, they could have arranged with Motorola to release the bootloader relock keys for older models that are no longer on sale but are still used for CROMs, to make them into better gateway phones to then shift into a Moto with Graphene.

Instead, what we have is basically the "attempts to be the left" equivalent of the Trump Phone.

I would generally not recommend running official google apps at all. MicroG works quite well for the things you actually need. I would research on how to flash microG with adb and add the correct elevated privileges.

Or if you need to flash gapps, use this file to only flash the needed apps like playstore and play services and nothing else.

Then afaik you can still disable them on the main profile and only use them in work profile (shelter, island), which would be a big privacy advantage

MKBHD might review this when it's released, or at least mention GrapheneOS. That could help with publicity.

There's always some dude who will shit on anything and everything, no matter how good or bad it is.

I think one of the requirements for Graphene security specs was LTS support for the chipset itself.

Fairphone had the same issue in finding a chipset with LTS which wasnt flagship tier and ended up going for one from the IoT side of Snapdragon.

Who asked for a flagship device?

Might pick one up if they're good. Otherwise I'll probably just stick with used Pixels.

I'm confused. Were you expecting a relatively small volume flagship device to be cheaper?

...They had one job.

I have my doubts about Graphene OS. Louis Rossman tried to talk to the man behind that OS and he turned out to be a creep. So yeah...

Interesting.

I might just install GApps instead. I really don't care if it turns it into a Googled phone. I already have a Googled phone with the Samsung default OS anyway.

Nope.

I've never had a good time with the install instructions. They are okay when the extremely finicky steps work, they are terrible for recovering from a mistake. It's all too easy to get your device into a worse state than you started. This is not something we can blame on the LineageOS project; most hardware manufacturers deliberately make it an awful, risky experience to change the operating system.

Having said that: All my mobile devices were on LineageOS (and earlier names for the same project years ago), and it has been far more stable, far more free from horrible user-hostile behaviours that I see people putting up with on Google-ified devices.

Bear in mind that a lot of the awful stuff is now part of the Google Play layer (the “gapps” bundle), which I strongly recommend you don't install. Installing that allows the creepy, anti-democratic surveillance and lack of user agency that you see in much of the proprietary world. Purge it with fire.

But without that, a lot of proprietary apps will not work properly. Doesn't bother me, I only ever install from F-Droid because I know they build from source, and ensure the source is free software.

(Why “were” on LineageOS? Not from anything wrong with LineageOS. Some of my devices are now on operating systems that don't support as wide a range of devices but are somewhat better suited to the purpose, like GrapheneOS.)

Well, I tried installing MicroG before and that doesnt just work. You need to flash it as privileged module and put an xml file somewhere to give it elevated permissions.

I found this issue, there seems to be a hole in the docs. The same user also opened another ignored issue that does seem to match my impression of very lacking docs and a low focus on security for microG too...

Does your job not provide a work phone? If you need stuff on your phone for work, it would be the employer's responsibility to provide a phone that it works on. Or is it just that you want everything in a single phone?

Be aware that “LineageOS for microG” is a separate distribution and only ships updates every second month.

Yeah, that's what I thought. I think I'll just install MicroG myself instead.

Thanks for all the recommendations. But it looks like LineageOS is the only one that officially supports my model. (Samsung S20 5G) And it looks like it would do the job just fine for my needs.