Database Develop

Gmail always has delayed notifications (Android 8.0)

Hello everyone,
So I've got an XZ1 Compact with Android 8.0 (build 47.1.A.16.20), and the only thing which I can't fix and is very annoying is that, no matter what I do, Gmail notifications almost always come delayed.
Gmail is in power-saving exceptions:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also it has unrestricted data usage:
Also I even disabled Stamina whatsoever.
Still, it often happens that notifications aren't delivered, and then I hit the power button, phone wakes up, and after a few seconds throws a lot of notifications, for all those emails which were sent since the last time I woken it up.
The problem is the same independently of whether I'm on mobile network on wifi.
It's only Gmail; other apps (like Viber, Telegram, etc, don't have those problems, they sync perfectly well).
Any chance it could be fixed? Is there anything else I could do, besides adding Gmail to power-saving exceptions and giving it unrestricted data usage? Anyone else has this problem?
Thanks!

Ok it looks like finally there is a solution: https://forum.xda-developers.com/oneplus-6t/how-to/guide-notification-fix-100-t3865551
Related links:
- https://www.androidauthority.com/delayed-gmail-notifications-1052389/
- https://www.reddit.com/r/Android/comments/dtdldo/androids_gmail_notification_bug/
- https://www.reddit.com/r/Android/comments/dtx84u/androids_gmail_notification_bug_or_is_it_update/

[Question/StockROM] Found Battery drain Culprit Xiaomi Push Service,how to disable?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Flashed Stock Android 10, May 2020 patch using unofficial fastboot (V11.0.8.0) and I'm getting really good battery life throughout the day.
- I already have 1.5%/hr drain during standby which is not bad but I analyzed the adb bugreport on Battery Historian tool and found out that a service integrated into Android System called Xiaomi Push Service is waking the device multiple times, even during the night when device is supposed to be dozing off in deep sleep. This alarm reflects in WLAN_CE_2 wakelock which keeps my phone awake (and probably yours too).
Apart from battery life, I'm also concerned about privacy - I just want to disable this. How do I go about disabling it? Last year in Android Pie, I went on to install EdExposed to disable Alarms, etc. but i don't want to go down to that pathway, I'm looking for an easier solution.

Question AOD drain battery but it is disable

Hi everyone.
Yesterday, I made a clean install on my phone.
I never use AOD but it drain my battery despite having deactivated this option...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is it a bug ?
I try to enable then disable but it does make any difference.
Anyone have the same problem ?

Probably being misreported as another app.
This isn't unheard of.
WhatsApp (trashware), Goggle play Services, Playstore, Google backup Transport, Framework and any cloud services are likely suspects.
Also try clearing the system cache and running in Safe mode at night (to see if it's a 3rd party app).

What is your rom 12 MIUI ? EEA ? 12.XXXX
On your screen our battery usage log are falses because you have -31% Batterie Drain for 69% charged and if you count all detailed apps they have consumed more 67.77%.
So i think your drain is finished and only AOD log (when it has been used) is displayed. When you apply a theme he ask if you want also active by default AOD, if you click fast you don't see the popup and AOD is active.
Show your log in 4/6 hours and look if AOD usage has increase or same.

I'm on miuimix 12.6 (21.7.21)
Thx for your answer.
I will look after next charge the log.

SAMSUNG S20 FE EXYNOS 990 ANDROID 12 EXPERIANCE!

hello guys! what is your experience with android 12?
i cant force gpu anymore when i play games!
when i disable GOS FPS is more unstable and lower!
can somebody tell me what they added so i can disable that and play games like on android 11!
on android 11 when i disable GOS fps is almost locked on 60 FPS all the time, temperature is much bigger but performace is best!

Never update especially when new phones come out. They are just slowing down the phone so you will be obligated to get new ones.

abdellahboughrom said:
Never update especially when new phones come out. They are just slowing down the phone so you will be obligated to get new ones.
Click to expand...
Click to collapse
it may feel that way to you but it's not true.

Nothing much, almost no new functions except the privacy centre and those useless color palletes.
Phone feels laggy if you have animations disabled. The 120Hz while powersave hack no longer works and I miss this menu (OneUI2).​
I'm waiting for lineage OS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Question System UI crash and stuck screen cutout overlays

Upgraded to Android 12 and noticed some ugly bugs with system ui.
Occasionally, during camera ring animation or landscape mode (youtube for example), the overlays for cutouts and camera ring/hole remain active.
They are not visible in the screenshots so it must be an overlay. The only way to get rid of this is if the System UI crashes and restarts or I restart the phone.
It can be days or hours between this behaviour.
Is there a way to crash/force restart system ui without rebooting the phone? What could surely trigger the crash?
This problem has been documented on zentalk - https://zentalk.asus.com/en/discussion/57673/system-ui-stopped-working/p1
thanks!
View attachment img-4625c4d664a2672b71a48faf3537690d-v-1.webp

This problem started occuring in ANdroid 12 betas. THe Zentalk beta forum has 3 or 4 threads about this bug. Actually Asus seems not wanting to fix it.

Have you disabled System UI from accessibility settings? It should fix the issue.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Was never enabled.

Fixed it for me after being a beta tester and still experiencing it until a week or so ago. A factory reset was the solution, it's a bit of a bruteforce way to do it, but hey, if it works it works right?