submitted 1 day ago by [email protected] to c/[email protected]

23 comments fedilink hide all child comments

I am greatly displeased at the smartphone industry. I think it's time for a heavy handed crackdown about all the spying they're doing. The smartphone industry and in particular the company qualcomm I find an intolerable company in their practice, I believe they should be smashed, their equiment liquidated and their intellectual property destroyed.

The smartphone industry is a festering cancer on general computing, a persistent and pernicious assault on human rights. An invasion of our private spaces. A colonization of our lives.

I think it is past the point of reform, not that there are any regulator with to intelligence figure out what is wrong let alone the wherewithal to do anything about.

For those reasons, I think global thermonuclear war is our only realistic option for setting back the clock on this travesty.

I am willing to hear your alternative, I don't believe anything short of that has a snowball's chance in hell to change anything about this.

top 23 comments

sorted by: hot top new old

[-] [email protected] 2 points 10 hours ago

So OP doesn't know what the fuck they're talking about. Yes, I see...

[-] [email protected] 87 points 1 day ago* (last edited 1 day ago)

There's a reason pixels are preferred, it's not some kind of malicious conspiracy. The most common sense reason being that there's a lot of overlap and cross-pollination of devs in the android world. between Google and graphene os in particular.

Pixels are also targeted because it's a mass-produced flagship with decent specs that is the closest thing to being already rooted off the shelf. It's the path of least resistance. Plus the used market is robust. A used carrier unlocked pixel 1 or 2 models behind the latest one can be obtained for several hundred dollars cheaper than it originally retailed for.

It takes effort to support additional brands/models.

Most brands lock their bootloaders and make "owning" the device difficult.

[-] [email protected] 30 points 1 day ago

That answer is at best only partially right.

The real answer is that Pixels were, until very recently, Google's officially supported reference hardware in AOSP while everything else is a community port of some GPL compliance source code dump.

Community ROMs are Pixel first because Pixels just work.

It'll change now that Google decided to no longer release Pixel adaptions directly as AOSP and the community will have to port that the same way as for any other vendor, especially if a vendor decides to maintain their adaptions in LineageOS.

[-] [email protected] 4 points 14 hours ago* (last edited 14 hours ago)

Hey, that makes total sense. And thanks for filling in what I missed! Really too bad about those changes, too. Google set out to create an open mobile ecosystem in opposition to Apple (and, at the time, and to a lesser extent, M$oft). It was such an incredible success at the start. Lately though, it seems they want to run in the opposite direction by tightening their grip - not the best thing for the community of Android users at all.

Of course, the minority group of nerdy, early adopting users who are a dedicated bunch will bear the brunt of it (as always). It's no surprise they'll be facing backlash from those groups, which in part explains the surges in demand for better (yet somewhat adjacent) alternatives. I was all in when Google said "don't be evil". Now they seem to have abandoned that ethos. I'm still stuck in their ecosystem, have started looking for the exits and I'm definitely not alone in feeling that way.

[-] [email protected] 33 points 1 day ago

To add to this, the phones are consistent. With many other brands, it is common for two phones with the same advertised name (like "Galaxy Note 7") to be actually different depending on where you bought them. This makes supporting each model challenging. Also it is closest to AOSP.

[-] [email protected] 14 points 1 day ago

I mean, sure but, the absurdity of buying a google device to degoogle, to escape google ?
I just can't !

[-] [email protected] 37 points 1 day ago

But that's the thing: GrapheneOS doesn't exist to "escape google," it exists to give people privacy.

If it were designed to escape google, they wouldn't create a re-implementation of Google Play Services that you can optionally install for apps that need it and regularly maintain it with every OS update.

GrapheneOS doesn't remove Google services because "Google specifically bad," they remove Google services because they spy on you without consent, and GrapheneOS is meant to prevent spying.

Hell, if any ROM wanted to get away from Google, basing itself on Android, the thing developed by Google would then be the problem, and they would be better off trying to make an independent Linux distro.

It fundamentally makes sense for GrapheneOS to work on Google hardware first, because Google controls not just the hardware supply chain of the phones, but also the software supply chain. (AOSP)

Supporting, say, Samsung phones, would then mean not just, to a degree, relying on Google via AOSP, but also Samsung's hardware. Android-based ROMs can't really benefit from trying to get away from a particular company, because it's either Google, or Google + Phone Manufacturer that they then have to deal with. (not to mention the fact that Pixels run the best with stock android and are simply the most feasible device for a small development team to support with the lowest possible costs)

[-] [email protected] 7 points 1 day ago

Amazing responses, well written. Thank you!

[-] [email protected] 16 points 1 day ago

I bought a used Pixel 6 (for about $120 on Swappa) and installed GrapheneOS. I understand the irony of deGoogling and using a Pixel phone. From what I understand, the core reason GrapheneOS relies on Pixel phones is because they offer hardware security features (like the Titan M chip), an unlockable and re-lockable bootloader, and guaranteed long-term updates.

My favorite part of my phone (besides the ultimate security and privacy) is that my only "app store" (besides the GrapheneOS store) is Obtainium. There is nothing on F-Droid or Google Play that I can't find (that I use/need) with Obtainium and IronFox. If I absolutely need to access something that requires proprietary or unwanted applications, I use IronFox to browse the website (my bank for instance). I have complete control over what my phone does and I only have FOSS software installed. It is a lot more work than I think most people would be willing to do, but it is important to me, and I think it is the only way (for me, this is subjective) to be truly free of Google or Apple and still use a smart phone.

Other "privacy" ROMS still communicate with Google in some way. The other ROMS are moving in the right direction, though. /e/OS, for instance, switched to AOSP instead of LineageOS, but it uses microG. By its very nature, microG communicates with Google, so that is not something I am interested in using. Some of the GNU/Linux mobile projects are showing promise (check out postmarketOS ), but they are a ways away from actually being reasonably usable on a newer everyday main device.

In conclusion, yes, just end it all. The best I can come up with is to deGoogle and reject all big-tech.

[-] [email protected] 5 points 1 day ago

I feel like I should just learn how to fuck around with the OS/bootloader myself because this has been a bit of an issue for a while. Lots of custom ROMs, but not the ability to get them on every piece of hardware. And not even always because the hardware is locked down; just because it needs to be tweaked to work for a specific device and if the device you wanna put it on isn't super popular, no one would have made a thing to work for that device.

[-] [email protected] 7 points 22 hours ago

It's not hard at all. The real problem is that like 90% of hardware makers don't allow you to unlock your bootloader. And every year it becomes less and less common. Chinese phones used to be amazing, because you could just slap a good clean rom on amazing hardware. Nowadays (due to pressure by the ccp from what I gather) most of them do not allow bootloader unlocking anymore. Or they allow it only using insane requirements (100+ day active user in good standing on their Chinese support forum, only 100 unlocks/day, first come first served at 1am Beijing time, etc etc...)

And without an unlocked bootloader, you can do jack shit with your phone. Hence why pixel phones are so liked for custom roms. They unlock straight out of the box, no questions asked, no weird hoops to jump through.

[-] [email protected] 6 points 1 day ago

A crackdown by whom?

The people who have the power to change it are the people who want it the way that it is.

Protests don't matter. Boycotts don't matter. For one simple reason.

You're not their customer. The people buying the data they collect from you are. There will never be enough people willing to do away with their precious smartphones and tablets to make a dent in ithat.

[-] [email protected] 1 points 16 hours ago

If there is no one willing to step up and protect the interest and wellbeing of common people, it means democracy is dead and it can't be denied anymore. If there's going to be no effort made to force the hand of device manufacturer and carriers to provide a privacy respecting full featured smartphone at the regular price of any other phone while also constructing a society that demands everyone to have one. Then it must mean that society intends to spy on everyone in a way that would make Big Brother blush.

I don't see any solution other than "a vigorous nuclear exchange" as the last hope we have for a reset button before our feat is sealed as human cattle of the oligarchy. And yes, this is far from the only sign that this is happening, it's just the one undeniable smartphone aspect of this upcoming horror.

[-] [email protected] 5 points 1 day ago

Im out of the loop, did something happen with GrapheneOS?

[-] [email protected] 18 points 1 day ago* (last edited 1 day ago)

I think it's related to this

https://www.androidauthority.com/google-not-killing-aosp-3566882/

Google has made it harder to build custom Android ROMs for Pixel phones by omitting their device trees and driver binaries from the latest AOSP release.

The company says this is because it’s shifting its AOSP reference target from Pixel hardware to a virtual device called “Cuttlefish” to be more neutral.

While Google insists AOSP isn’t going away, developers must now reverse-engineer changes, making the process for supporting Pixel devices more difficult.

GrapheneOS says it won't be a big deal:

https://discuss.grapheneos.org/d/21315-explanation-of-recent-changes-to-aosp-and-the-lack-of-major-impact-on-grapheneos

Fairphone also recently released Fairphone 6, and so people are talking about having to pick between privacy (GrapheneOS) and ethical manufacturing (Fairphone)

https://www.howtogeek.com/fairphone-6-announcement/

[-] [email protected] 9 points 1 day ago* (last edited 1 day ago)

people are talking about having to pick between privacy (GrapheneOS) and ethical manufacturing (Fairphone)

GrapheneOS is far from the only ROM that can improve the user's privacy. Many other projects support Fairphone, and whilst they may not pass the Lemmy purity tests, they are objectively better in many ways than the default operating system. It frustrates me that people in the privacy space constantly frame decisions as binary trade-offs when in reality you can always take smaller steps to improve your privacy without giving up everything else you care about.

[-] [email protected] 4 points 1 day ago

The spying, as you call it, at the OS level is one thing, the data leakage at an App level is a different thing entirely. The lengths that the Google Play store goes to hide permissions and the poor level of granularity, let alone the wholesale outsourcing of service critical applications and their "required" permissions is beyond the pale and not regulated, let alone enforced, in any way.

For shits and giggles, you should check the permissions associated with your bank, telco, government, medical and other life essential applications, never mind the ones you use for entertainment.

[-] [email protected] 1 points 1 day ago* (last edited 1 day ago)

None of my apps have any permissions other than location when the app is open, camera, and file access.

What apps and permissions are you specifically talking about? Can you provide any specific examples?

[-] [email protected] 1 points 1 day ago

I recently explored the android app permissions for Telstra which requires so you can manage your phone. Then I checked Optus, Boost, CBA, NAB, ANZ, gmail, chrome and Tesla to name a few.

Privacy should not be optional.

Here's what I found:

https://docs.google.com/spreadsheets/d/e/2PACX-1vTl3_RWZmVNPmMYKF7Go2eHgvT6e1expOkbkXzjnRYY72L3RADKS-NaEX2eoDwN-ig0mWAmOogws3bx/pubhtml

[-] [email protected] 1 points 1 day ago

A long list without context is entirely unhelpful. The permissions need to be enabled and are likely to have features associated with them.

So your correct privacy shouldn't be optional. So which of these apps have features turned on that don't require a user accepting them or wanting the feature?

Frankly, almost all of these permissions are initiated my a user at first sight making some assumptions.

[-] [email protected] 1 points 23 hours ago

The long list is the permissions as the Google Play store presents it.

Below each app column shows empty if that permission is not required, or shows the permission if it is.

I'm not sure how else you feel that this information should be presented.

As far as vague goes, that's my point. We grant permissions to launch an app with often little or no thought as to their interactions, like calender contacts and internet, or files and internet, or system permissions.

[-] [email protected] 2 points 1 day ago

I feel your frustration... though a decent phone w/o locked Android shouldn't require global thermonuclear war I hope!

I stress about what phone, if any, I'll be able to install a non-bloatware, rooted, vanila OS on once the models my wife & I have become too 'obsolete'. (OnePlus 5T with LineageOS).

[-] [email protected] 1 points 20 hours ago

It's still a Pixel with an AOSP distro. Lineage is fine.

this post was submitted on 26 Jul 2025

87 points (100.0% liked)

Android

31265 readers

252 users here now

DROID DOES

Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules

1. All posts must be relevant to Android devices/operating system.

2. Posts cannot be illegal or NSFW material.

3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.

4. Non-whitelisted bots will be banned.

5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.

6. Memes are not allowed to be posts, but are allowed in the comments.

7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.

8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.

Community Resources:

We are Android girls*,

In our Lemmy.world.

The back is plastic,

It's fantastic.

*Well, not just girls: people of all gender identities are welcomed here.

Our Partner Communities:

[email protected]

founded 2 years ago

MODERATORS

[email protected]