Received my new S25 Ultra yesterday, set it up via SmartSwitch. Everything transferred correctly but none of my notifications are working.
Zero.
I have gone though forum postings that other people have posted looking for solutions and most of those has been DND or a routine turned on blocking notifications.
Things I've checked:
Do Not Disturb is TURNED OFF.
No Modes or Routines are running (there aren't any setup).
Sound is on.
Vibrate is on.
No icons or app badges show up on the top.
The apps that I am testing with I have confirmed that notifications are turned on.
All the options are selected for the notification options (Lock Screen, App icon badge, Notification pop-up).
This happens if the phone is sleeping or awake.
My old phone is still using Wi-Fi and notifications work fine on that one (other than messages and phone cause that's tied to the SIM). Turning off the old phone and waiting a few minutes and trying on the new phone, same thing happens.
If I open the offending app, I can see the unread messages.
Other than wiping the phone, skipping the SmartSwitch and starting from scratch, I am not sure how to move forward.
Same thing, when screen off no notification... When screen on i have all notification... **bleep** Samsung in 2025 you have this problem. Fix this **bleep** immediately....
When I run the adb command it gives a response the first time to indicate deviceidle is disabled, but the same command again returns nothing I assume because it's already disabled. If I enable it gives a response to show it's enabled, and then the disable command also will give a response again. So if it's returning no response, maybe because it's already disabled?
Also, I suspect going into app info for an app and setting the battery mode to 'unrestricted " vs optimized is supposed to bypass doze. It seems like this might actually work on some apps, but confirmed that this alone doesn't work on all apps for me.
Run these two commands and see what you get in response:
adb shell dumpsys deviceidle get light
adb shell dumpsys deviceidle get deep
That will print the status of the commands, if it comes back ACTIVE, then the disable command is not working. Which is what is happening with my device. I run the disable, nothing returns. I run those to check the status, and they come back ACTIVE.
Both the "get light" and "get deep" commands come back active, but they both stay active regardless of if I use deviceidleness disable OR deviceidle enable. So I'm not sure this is really telling you if doze is disabled. All I know is that after using deviceidle disable, it definitely solved the main problem being described in this thread.
