grow a plant, hug your dog, lift heavy, eat healthy, be a nerd, play a game and help each other out

  • 0 Posts
  • 113 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle



  • I appreciate that you’re trying to inform me but if you make such a claim, you should be able to prove it.

    A friend was able to provide some context, regardless:

    • The one binary I’m aware of microG downloading (assuming it still does) is the SafetyNet “DroidGuard” thing, which it only does if you explicitly enable SafetyNet, which is not on by default. There is no other way to provide it.

    • microG only has privileged access if you install it as a privileged app, which is up to you / your distribution, as microG works fine as a user app (provided signature spoofing is available to it). Also, being privileged itself really doesn’t mean giving privileges to “Google”.

    • Apps needing Google services may indeed contain all sorts of binaries, generally including Google ones, which doesn’t mean they contain Google services themselves. Anyway, they are proprietary apps and as such will certainly contain proprietary things, and it’s all to you to install them or not. It’s not like microG includes them.

    • Its also just a reimplementation of a small handful of useful Google services, such as push notifications, or the maps (not the spyware stuff like advertising) and each can be toggled on/off.

    • Also all apps on android are sandboxed


  • I appreciate the info. For my own learning, could you provide a link to some context around the types of official binaries leveraged by microG? The only firm info I have of its behaviour is that it will pseudonomise as much user information as possible.

    I’m familiar with sandboxed google play on grapheneOS and have used it in the past.














  • It’s not very intuitive but it isn’t so bad once you’re familiar; you can take a look at this whenever’s convenient for you.

    When you boot the system, you should briefly see your BIOS splash screen, along with the key combo to get into your BIOS setup menu. Let us know which mainboard vendor you have and we may be able to tell you in advance (For Asus, it’s usually F2, for Gigabyte its the Delete key, for MSI it might be F12 etc). I just mash the specified key when prompted until I’m in.

    There’s usually also a key that you can hit to select a temporary boot device (I.e. I can hit F12 on my gigabyte board to select any OS detected by the BIOS, not just boot into the top entry).

    Once you’re in, have a look for the ‘Boot’ section. You should have the capability to define your boot order. These entries can consist of traditional disks connected via SATA/SCSI/m.2, USB drives, network locations etc.

    You can arrange this boot order however you like.

    I would also recommended temporarily disconnecting any existing drives when installing an OS on your system (e.g.: Windows attempts to store its bootloader on SATA 0 by default, even if the OS isn’t destined for that drive).