xxx Thanks for the suggestion but the app works fine without, and i don't need notifications on that app. I mainly use this app once in a while for its music disovery feature. On my main profile i use finamp with my own music library.

  • xxx replied to this.

      r134a Sorry I thought deezer dosn t work without the play service?

      Nevermind I read your posts again -> it works without, so sure you don t need the google stuff.

        In my experience, WhatsApp notifications sometimes don't actually work without Google Play, even though under "Battery Usage" WhatsApp is clearly running in the background, and I allowed unrestricted background usage for it.
        Seems random whether or not a notification will show up (and unless I just switched to a different app without closing WhatsApp, they are delayed by at least 2-3 minutes).
        Since the upgrade to Android 15, I almost never get WhatsApp notifications (BTW, according to the people I chat with through WhatsApp, on their end it seems the messages aren't even being received on my end until I open the app when this happens).

          mrket Same here. And before anyone asks, Play Services was never installed. Seems to have become a real issue since Android 15. WhatsApp calls are missed now, too.

            5 days later

            I continuously receive messages with these settings on Android 15, (pixel 8a)
            Settings:
            (wprofile: user profile with WhatsApp, no g services)

            1. (owner profile) System -> Users -> wprofile -> Allow running in background:on
            2. System ->Users -> wprofile -> Set notifications to current user:on
            3. app info -> App battery usage -> Allow background usage:on
            4. app info -> App battery usage -> Allow background usage -> unrestricted:selected
            5. app info -> manage app if unused:off
            6. app info -> Notification - All notifications:on
            7. app info -> Background data:on
            8. Battery -> Battery saver:off

            If you force stopped whatsapp you need to open it once to receive data again.

            Some weird behavior in my case regarding calls and a way to switch users while being called:
            If you are called from the wprofile while at the owner profile, everything behaves like this:

            1. You can't interact with the call. 
            2. You can't switch to the wprofile to interact with the call. 
            3. You can't adjust the ringing sound with volume buttons.
            4. "Do not disturb" does not mute the call, but does if it was activated beforehand.
            5. You can only adjust the ringing sound in the settings or mute the call by clicking the power button.

            If you are a non-owner user and you are called by wprofile, you can do all of the above, but once you switch to wprofile, the ringing stops and you can't accept the call. The WhatsApp notification "accept/decline" does nothing and stays like this after the call. Nothing about the call in the app itself. You have then to force stop WhatsApp or get another call to get rid of the notification.

            However, if you don't switch the user but go to the lock screen via power button (or if you are already there) and click on "end session," you are transferred to the owner login screen, and you can now switch directly the user by sliding down the top panel and then accepting the call. This worked continuously, but then I tried to replicate it by creating another user, it now doesn't work for both; the notification just freezes after switching like described in the section before.

              9 days later

              frankenstein Sorry, I wish I could confirm your findings, but notifications really don't work as well as on Android 14 anymore.

              My settings:
              • Installed in main profile
              • No Play Services (never were installed)
              • Battery saver: off
              App settings:
              • Notifications -> All notifications: on
              • Permissions -> Pause app activity if unused: off
              • Mobile data usage -> Background data: allowed
              • App battery usage -> Allow background usage allowed -> on & unrestricted
              • Manage app if unused: off

              Everything you wrote about the work profile issues isn't relevant to my cases.

              Results since Android 15:
              • No notifications, for hours, basically until the users open WhatsApp themselves
              • No call notifications, sometimes even when WhatsApp is in the foreground, until the other user just stops trying (and then the receiving end gets a missed call message)
              • Also seeing GooglePlayServicesUtil: com.whatsapp requires the Google Play Store, but it is missing. logcat entries
              • Other curious logcat entries: 
                com.whatsapp: AIBinder_linkToDeath is being called with a non-null cookie and no onUnlink callback set. This might not be intended. AIBinder_DeathRecipient_setOnUnlinked should be called first.
WhatsAppJni: DetachThreadOnExit: detached current thread from JVM
JobService: onNetworkChanged() not implemented in androidx.work.impl.background.systemjob.SystemJobService. Must override in a subclass.

                  SovereignCopper same with Viber, message notifications worked fine, but with Android 15 not. Nothing changed under Viber App settings

                    SovereignCopper It seems on my device WhatsApp is creating new notification "groups" (not sure what they're called) with default settings.
                    It also seems to assign previously changed "Conversations" the "Silent Notifications" group.

                    I currently have 4 "Silent Notifications" groups, 3 "Message Notifications" and 2 "Group Notifications".
                    I'll keep an eye on it to see if more are added over time.

                    Is the same happening on your end?

                        mrket I now have 3 "Silent Notification" groups, one of them was reset to default settings, I changed it, re-opened settings and it reset to default again.