I’m just this guy, you know?

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

help-circle



  • “Restricted” means the app has been limited by your Android on the amount of data it may transmit/receive as a background app. The app settings assume you’re on a meterd or low-volume data plan, and so they don’t transmit data except when they’re active, or up on your screen.

    Their upload/download tallies will still count in your Network accounting. Frankly, your screenshot looks like something I’d expect. Nothing untoward seems to be occurring.

    Let those other restricted apps 'run in background" (an app permission) and you’ll see a different picture.











  • If you’d bought a 2TB you could just dd image the windows disk to the new drive. If you can convince Windows to downsize its partition and then use a partition editor on a USB liveboot to identify the drive sectors you could maybe still image the windows disk. Big “if.”

    As to the second question, use block IDs-- the filesystem’s UUID. Grub is lazy and assumes a single root (the first found) partition so if you want a particular boot entry to use a specific root slice, you’ll need to ensure each OS entry in grub uses the right UUID for its kernel root parameter. Loading the right root gets you the rigjt /etc/fstab to mount that root’s expected partitions

    Honestly you’d be better off running your stuff in VMs. Dual-boot is a nightmare.