Formerly @russjr08@outpost.zeuslink.net

  • 0 Posts
  • 86 Comments
Joined 10 months ago
cake
Cake day: December 7th, 2023

help-circle




  • I personally use Sleep as Android which comes with a bunch of options to help ensure you’ve actually woken up. I utilize the “captcha” option in which when I go to turn off the alarm, it displays a screen full of sheep and all of them but one are sleeping - you have to click the one that is “awake” in order to dismiss the alarm. I guess the process wakes up my brain just enough so that I don’t go back to sleep, whereas with a regular alarm that has just a simple dismiss button I’ll absolutely either hit dismiss or one of the volume buttons to turn off the alarm before I’ve fully woken up.

    I also have it set to buzz on my watch for 90 seconds before playing a sound on my phone (which escalates in volume) - I’ve not had a problem waking up with this in the years that I’ve been using it.

    There are other options too, such as answering math questions, scanning a QR code, pressing your phone to an NFC tag, heavily shaking the phone, one called “Say cheese!” that makes you smile as hard as you can and uses the camera to detect it, and one that you have to “laugh out loud”.















  • You’re thinking of install-time permissions, which technically does still exist, but pretty much most of the permissions you’d actually care about are runtime (or special) permissions - the application must request these from the user.

    There are three main types of permissions on Android:

    • Install-time, these are permissions granted to an application upon installation
      • In this group is also signature-level permissions, which are only granted to applications that are signed by the same party as the OS itself (usually your OEM)
    • Runtime permissions (also known as “Dangerous permissions” within Android internally), which are permissions that the application must request from the user. The system draws the permissions dialog, not the application itself. Permission can also be granted one-time only, or permanently (unless the user revokes the permission)
    • Special permissions, which also need to be requested by the application - except for these the system will not draw a permissions dialog, instead the application must send the user to the “Special App Access” menu within system settings, and the user must turn on the permission there. The best way I can describe these types of permissions is, “permission that the user really must think about before granting” - such as giving an app the ability to bypass DND rules, drawing over other apps, installing APKs from unknown sources, accessing all device files, etc. IIRC, Google also requires that developers provide justification for requesting these permissions when submitting to the Google Play Store as well.

    Runtime permissions were introduced in Android 6.0, which was released in 2015, I am not sure when the special permission system was implemented however.


  • Russ@bitforged.spacetoAsklemmy@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    10
    ·
    2 months ago

    Hate? No, I do not hate Google. I still use a Pixel phone (and photos/assistant on it), my Gmail is still my primary email (I also self-host a few other domains but those are primarily used for automation and a few other one-off things), I subscribe to YouTube Premium, I still utilize my Stadia controller as my primary game controller, I use a Google TV set top box, etc.

    I don’t use Search (I use Kagi instead), I don’t use Chrome (Firefox), I don’t really utilize Gemini all that much (I just run ollama for the few times I want to use an LLM).

    Really I just use their products that work well for me, and don’t use the ones that don’t. There’s no love/hate about it.