Edit: I figured it out. The problem wasn’t permissions or Firefox itself, but my launcher. I’m using OLauncher, 'cause I rather like it’s text-lookup interface, but as it doesn’t make use of a traditional “home screen” Firefox won’t allow me to create an entry there.

Apparently, it’s a much-desired feature request

I think it may have been renamed to “Install” in previous versions, but neither appear anymore, and I don’t see any permissions denied so I’m assuming that can’t be it.

A screenshot of my Firefox permissions, showing nothing denied

  • Nobilmantis@feddit.it
    3·
    7 days ago

    I have it on the latest version, both for websites that provide a web app instance (“install”/“add app to homescreen”?) or for generic web pages (“add website to hs”).

    The permissions you are looking at in the ss are the “dangerous” android permissions, and usually “add links to the homescreen” is not there. On my xiaomi to grant it (if it isnt by default) you long press the app to go into the app info, then something like “other permissions” or “special permissions”.

    • Daniel Quinn@lemmy.caOPEnglish
      1·
      7 days ago

      Weirdly, I do have a “special permissions” section in my phone (Fairphone 4, which basically runs stock Android 15), but there’s nothing about adding links to the homescreen in there, just:

      • device admin apps
      • Display over other apps
      • Do not disturb access
      • Media management apps
      • Modify system settings
      • Notification read, reply, and control
      • Change media output
      • Picture-in-picture
      • Premium SMS
      • Unrestricted mobile data
      • Install unknown apps (Firefox has this permission now, still no joy)
      • Alarms and reminders
      • Usage access
      • VR helper services
      • Wi-Fi control
      • Screen turn-on control
      • Full-screen notifications
      • Launch via NFC

      I actually went through all of these, enabling Firefox’s permissions wherever it came up, but still nothing. I’m starting to think that this might be an Android (b)locking rather than a Firefox shortcoming.