"Select Play Partners" can block unofficial installation of their apps.

You might sideload an Android app, or manually install its APK package, if you’re using a custom version of Android that doesn’t include Google’s Play Store. Alternately, the app might be experimental, under development, or perhaps no longer maintained and offered by its developer. Until now, the existence of sideload-ready APKs on the web was something that seemed to be tolerated, if warned against, by Google.

This quiet standstill is being shaken up by a new feature in Google’s Play Integrity API. As reported by Android Authority, developer tools to push “remediation” dialogs during sideloading debuted at Google’s I/O conference in May, have begun showing up on users’ phones. Sideloaders of apps from the British shop Tesco, fandom app BeyBlade X, and ChatGPT have reported “Get this app from Play” prompts, which cannot be worked around. An Android gaming handheld user encountered a similarly worded prompt from Diablo Immortal on their device three months ago.

Google’s Play Integrity API is how apps have previously blocked access when loaded onto phones that are in some way modified from a stock OS with all Google Play integrations intact. Recently, a popular two-factor authentication app blocked access on rooted phones, including the security-minded GrapheneOS. Apps can call the Play Integrity API and get back an “integrity verdict,” relaying if the phone has a “trustworthy” software environment, has Google Play Protect enabled, and passes other software checks.

Graphene has questioned the veracity of Google’s Integrity API and SafetyNet Attestation systems, recommending instead standard Android hardware attestation. Rahman notes that apps do not have to take an all-or-nothing approach to integrity checking. Rather than block installation entirely, apps could call on the API only during sensitive actions, issuing a warning there. But not having a Play Store connection can also deprive developers of metrics, allow for installation on incompatible devices (and resulting bad reviews), and, of course, open the door to paid app piracy.

  • Vik@lemmy.worldEnglish
    37·
    2 months ago

    As much as I want that to be the case, I don’t think full mobile gnu+Linux is really ready to use daily?

    I haven’t exactly been keeping up with things, mind you

    • timbuck2themoon@sh.itjust.worksEnglish
      10·
      2 months ago

      I sub to a few mobile Linux feeds and I want but don’t at all think mobile Linux is ready, even for tech devotees. Too battery hungry, not enough ease of use, missing functions, etc. And that’s not including lack of apps.

      Sailfish gets closest so far I think. But yes, not ready. Ubuntu touch last time I tried is fine but still a bit out of sorts.

    • IllNess@infosec.pubEnglish
      51·
      2 months ago

      Yes. I think a huge issue is Linux doesn’t handle other app activities like how Android’s Intent or Broadcast does.

    • kspatlas@lemm.eeEnglish
      2·
      2 months ago

      Just a note, one of if not the most popular mobile Linux distro is PostmarketOS, which is not GNU (it’s based on Alpine)

      • Vik@lemmy.worldEnglish
        1·
        2 months ago

        Good to know, that’s not the one I had in mind, however.

        For whatever reason I thought PMOS was based on Manjaro. Could be something as silly as associating one green logo with another.

    • klymilark@scribe.disroot.orgEnglish
      2·
      26 days ago

      I used it as my daily phone for months, and… well, I’m willing to deal with the problems. Without pretty careful battery management it’s not feasible, and it’s hard to manage your battery given the glitches. I often found my phone dead after a couple hours because it woke the screen immediately after I locked it because… reasons, and then kept it awake until the battery died. The biggest issue aside stuff like that (small issues that cause big problems), the biggest issue was I couldn’t get a map app working. There are some distros with working maps, none for my phone. Also call quality was horrendous. Like. I’m known for being able to tolerate bad quality, but this was, at times, about as bad as I remember my firefly phone being when I was 12, and I could not feasibly understand people at times with that thing.

      But the only reason I stopped using it was because the wifi isn’t working on it. Once I get that back up and running I’ll likely switch back to it. As bad as it can be at times, I still feel more comfortable having that as my primary phone than my Android.