With every version of Android it seems to be harder and harder to get real time notifications anywhere near real time.

Twitch notifications, Signal, WhatsApp, I often get these ten to thirty minutes too late.

I’ve excluded them from battery optimisation but that doesn’t seem to do anything. And I can’t find anything else.

I don’t care about battery usage. I’m always near a charger.

Android 13 on a Fairphone 3.

Edit: I’ve disabled DOZE according to https://stackoverflow.com/questions/40204605/android-completely-disabling-deviceidle-doze-in-android-m Hopefully that helps.

  • Skull giver@popplesburger.hilciferous.nl
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    13 days ago

    Apply the steps on https://dontkillmyapp.com/ to Google Play Services and Google Play Messaging, that may help. Also check if you have an app running in the background that eats all of your RAM and forces the OS to clear up scheduleable tasks.

    Thirty minutes is way longer of a delay than I’ve ever seen. You may want to try a factory reset in case it’s a ROM issue. Fairphone has had its ups and downs over the years when it comes to the built in software.

      • WIPocket@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        14 days ago

        In that case, is Google Play Services allowed to run in the background / unrestricted / whatever? It is the means to delivering notifications for most apps.

          • WIPocket@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            14 days ago

            Honestly, no. Whenever I see late notifications its usually on a degoogled phone, so this was just my first guess. Good luck!

            • Avid Amoeba@lemmy.ca
              link
              fedilink
              English
              arrow-up
              1
              ·
              14 days ago

              Agreed. I’d factory reset and see whether it improves things.

              Under certain circumstances it’s possible that the service is getting killed due to lack of memory, but the FP3 has 4GB of RAM so that shouldn’t be happening. One could probably diagnose it with a detailed logcat. Unfortunately I don’t have the bandwidth to help.

  • darklamer@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    1
    ·
    14 days ago

    FWIW, this is not normal or expected, most users get their notifications more or less instantaneously. Maybe knowing this might help you search for information about whatever it may be that prevents this from working for you.