Hi,

The general consensus amongst the Android community is that rooting is detrimental to privacy. In a sense, I agree with them since privilege escalation because of human error becomes a much bigger threat if the user has root access.

Android has a big privacy problem encapsulated in one word: “baseband”. Your modem and other hardware running in your device don’t run FOSS firmware and are likely actively malicious towards your privacy.

I am a Linux user, and I understand that concepts do not necessarily transfer well between the two. With that in mind:

  1. If I wanted to be absolutely certain that sensistive hardware like Camera, Microphone and Modem were truly off, would shutting them off as root hold any real significance?
    • I do not know what the equivalent of Intel ME is called in the Android space, but I doubt that a highly complex OS is running beneath general Android as we know it. I think it’s just the firmware of the individual device that we need to worry about.
  2. Is it possible to replace the bootloader on some Android devices/prevent it from loading unwanted firmware?

With Google taking Android behind closed doors, I suspect we will start seeing some suspicious snippets of code here and there with questionable purpose, but which might be missed by FOSS volunteers because of the sheer volume of work that is. I’m thinking of ways we can try to evade this blatant grab of our personal data.

  • drkt@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 days ago

    I may have misunderstood, but Google isn’t doing Android behind closed doors; it’s just development. The released versions will still be as open as they are now, as far as I’ve understood.

    • shortwavesurfer@lemmy.zip
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      3 days ago

      That’s my understanding as well. It’s to keep people like the media from being able to determine upcoming functionality by looking at code snippets. So the development would go on in secret, and then once per year, all the final code would be pushed to AOSP. However, OP does make a good point because if you have to examine all the final code at once, you might miss something that would be privacy detrimental.

      • zwekihoyy@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        3 days ago

        aosp code used to be released all in one lump sum at new version launch and Google has actually changed that to being quarterly releases which takes a lot of burden off android based os devs. so things are actively going in the opposite direction you’ve hypothesized here.

    • quickenparalysespunk@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      3 days ago

      i think OP is implying the extra time that will be needed on foss volunteers part to review the code at the time [edit: ‘of’] release.

      it’s like pouring liquid into a flimsy plastic cup. drop by drop, the cup can handle it. pour a lot all at once and the cup may tip over and spill.