Hi all,
I've got a Moto G5 Plus running Android 7.0 running stock firmware. Every day between 22:00-23:00 the phone is unusably slow, looking at the developer options and Tinycore resource information the memory is exhausted but CPU is pretty much idle. Rebooting the phone doesn't resolve the issue, only waiting until after 23:00.
Investigating the issue I've used SD Maid to examine what is running. Killing running tasks one by one doesn't help, nor does killing background services. I can't pin the issue to a rogue app or background service, the slowdown occurs independently of intensive background tasks (Google Photos backup, device backup, built in Play Store security scan). It seems like the issue is a low level OS one. I'm posting here rather than the device specific forum to check if this is a known issue with early Android Nougat builds. I'm at the mercy of Lenovo and still waiting for updates to bug fix point releases.
This has happened since day one of having the phone and I can't see any of the typical causes applying. I don't have any silly apps installed - Cheetah Mobile task killers, anti virus or any apps from nasty sources. I don't use task killers regularly, I only have SD Maid for monthly cleanup and this issue happens every night. Writing this now the phone is doing fine, 20 minutes before 22:00. Around 2.3 GB of memory used according to Tinycore but as we cross 22:00 it will shoot up. At first I thought this was uptime related but it's 22:00 which is the trigger.
Is there anything I'm missing? I've tried searching but the majority of posts relate to a rogue app, the time related trigger seems to be special. Apologies if I'm being silly. As an aside I've switched from iPhone to Android, I had a Nexus One back in the day (Android 2.2) and had years of free iPhones from work. Android has been busy in the intervening years and it's a great platform!
Thanks in advance.
Switch the net off, to check it's not internet related, like updates
Sent from this galaxy
pr1jker said:
Switch the net off, to check it's not internet related, like updates
Sent from this galaxy
Click to expand...
Click to collapse
Thanks for the reply. I've tried switching off mobile data and wifi, and turning on aeroplane mode, they don't make any difference. Forgot about this in my post, sorry.
I have disabled Google Play Store auto app updates. Even if this was the cause I'd expect to see something in my process list showing background activity / services gobbling memory.
Maybe it's something that has been fixed in Android 7.0.1.
Posting just in case anybody else has the same issue...
I'd activated the hidden Night Mode in Android 7.0 using Night Mode Enabler / System UI Tuner. Turning off Night Mode fixes this. Presumably this is why Night Mode didn't ship in 7.0!
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
MJFox78 said:
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
Click to expand...
Click to collapse
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
nabbed said:
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
Click to expand...
Click to collapse
if Google's code is garbage, I suggest you stop using android and start making your own good code!
nabbed said:
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
Click to expand...
Click to collapse
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
kewlest22 said:
if Google's code is garbage, I suggest you stop using android and start making your own good code!
Click to expand...
Click to collapse
I had a Pixel XL for over a year. Only kept it for Project FI. Bug ridden POS.
Sold it for half going price just so I could feel clean again.
Even if Samsung *used* to have sluggish Touchwiz in the past, at least it didn't have deal breaking bugs.
Don't even have to make my own code - some XDA roms had fixed this bug, as opposed to Google.
MJFox78 said:
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
Click to expand...
Click to collapse
I am almost positive that if you had a somewhat similar problem on a Note 8, it's probably Google's fault.
I don't really use the 2 BT phone functionality for more than 30 min on average, but I've never had any problems on Note 7, GS6 or GS9, or even on a Pixel pre 7.0.2 android, when this bug was first introduced.
After 7.0.2, bluetooth stuff just broke everywhere. This bug, constant disconnects and reconnects, for some people music skips, for some doesn't even work, BT UI in Settings just crashing etc.
It's like Google replaced their BT programmer with a monkey at that point, or even a monkey's nephew.
So just because you cannot use 2 Bluetooth devices simultaneously to make phone calls, it's a deal breaker??? Lmao please please please go back to Samsung so we don't have to hear the whining anymore. Good luck with those bootloaders
The very first Android phone I purchased was in 2010, and it was an HTC Desire. I have been a huge fan of Android ever since, owning literally hundreds of phones and tablets from various manufacturers such as Samsung, Huawei, Motorola, Xiaomi, LG, Sony....the list goes on and on. I've tried iOS a few times, but I simply just didn't like iOS. In recent years my loyalty to Android was severely tested because of an issue that many may think is inconsequential and even petty, but to me it was ultimately a deal-breaker - delayed push notifications (predominantly when the screen is locked and off)
So picture this - I'm sat at home with three other members of my family who also own Android phones, and we have a group chat (FB Messenger) going with other members of the family. Every time someone posts a comment *PING*...but wait, four android phones, and only two went *PING*...then a few seconds later another goes *PING*, then a few seconds later the fourth goes *PING*.
I'm not exactly sure when this issue first arose, but I only really started to notice around the time Oreo was mainstream, and I've been obsessed with trying to figure out a cure ever since. Of course I've tried literally everything that's been suggested, hard resets, turning off battery optimisations, locking the affected app in the recents, disabling Doze with ADB, clearing the cache, custom roms, different routers, different networks, heartbeat fixing apps for GCM/FCM, bla bla bla...none of it works. Now I have finally accepted there is a flaw in the way the Android OS handles push notifications, a flaw that affects every single Android device, at least since Oreo, and maybe even before. It's a strange one because the issue doesn't seem to occur when the screen is awake, only when it is locked and off. At one stage I was hopeful features like AOD on AMOLED devices might be a solution, but alas, even with AOD active, the problem persists.
Now before you say "I've never had a problem with push notifications on my Android device", are you sure. Have you ever really been in a situation where you would notice? Try it for yourself, perform a test using a similar scenario to the one I mentioned in the second paragraph. Create a group chat in any messaging app you like, and have several of the group members with Android devices sit in the same room with their screens locked and off, then have one person send a message in the group chat, then watch as some get the messages immediately, some with a slight delay, and some not at all until they wake the screen. Do it a few times and you will soon notice there is no pattern at all, sometimes you will get the notifications immediately while others are delayed, then sometimes others will get the notifications immediately and yours will be delayed.
My most recent (and very last) Android purchase was the Samsung Galaxy S21 Ultra 5G (outright, not on contract, so you know roughly how much I paid). When I'm paying that amount of money for a mobile phone, I expect timely push notifications as a given, but no, the same issue occurs even with one of the very latest and greatest. I contacted Samsung Tech Support and the guy admitted it's the most common complaint he deals with every single day. I was previously given a similar story by Motorola and Huawei support too, and a little digging around online shows that thousands of Android users are complaining about the very same issue. Needless to say they now have that phone back.
I know I know, something this trivial shouldn't really bother me this much, but it does, it's just who I am. I can accept there is no such thing as a perfect mobile phone, I can live with an average camera, a budget processor, a dull screen, lifeless aesthetics etc. but there are some compromises I just won't make. Apart from the obvious (the ability to make and receive calls and texts), my requirements are quite simple - I require a phone with stable WiFi, Bluetooth and NFC, a decent battery life and of course timely push notifications. With no Android device currently able to fulfil my very simple requirements, it really did only leave me with one option - joining the dark side....so I bought an iPhone.
I have owned an iPhone for just over a month (that's two weeks longer than my last three Android devices), and thus far my delayed push notification woes have vanished. Now when someone in the family posts in our group, *PING* immediately every single time. The battery life is acceptable for someone like me who isn't the most demanding user, WiFi, Bluetooth and NFC have presented no issues, and it makes and receives calls and texts without a problem. I can honestly say the only thing I miss so far is my Android App Drawer. I know iOS introduced their App Library in iOS 14, and it's a start, but it's just not the same. There is probably an app in Cydia that would give me an app drawer, but I'm not quite ready to get into the world of jailbreaking just yet (I'm not that brave).
So after my big rant, here's a summary - Android push notifications are broken, they've been broken for some time and Google don't seem interested in fixing the problem. If someone told me tomorrow that Google had finally fixed push notifications, I would drop iOS like a hot potato and rekindle my love for Android. Please Google, help bring me back from the dark side, it's really cold out here!
Des
energy6uk said:
The very first Android phone I purchased was in 2010, and it was an HTC Desire. I have been a huge fan of Android ever since, owning literally hundreds of phones and tablets from various manufacturers such as Samsung, Huawei, Motorola, Xiaomi, LG, Sony....the list goes on and on. I've tried iOS a few times, but I simply just didn't like iOS. In recent years my loyalty to Android was severely tested because of an issue that many may think is inconsequential and even petty, but to me it was ultimately a deal-breaker - delayed push notifications (predominantly when the screen is locked and off)
So picture this - I'm sat at home with three other members of my family who also own Android phones, and we have a group chat (FB Messenger) going with other members of the family. Every time someone posts a comment *PING*...but wait, four android phones, and only two went *PING*...then a few seconds later another goes *PING*, then a few seconds later the fourth goes *PING*.
I'm not exactly sure when this issue first arose, but I only really started to notice around the time Oreo was mainstream, and I've been obsessed with trying to figure out a cure ever since. Of course I've tried literally everything that's been suggested, hard resets, turning off battery optimisations, locking the affected app in the recents, disabling Doze with ADB, clearing the cache, custom roms, different routers, different networks, heartbeat fixing apps for GCM/FCM, bla bla bla...none of it works. Now I have finally accepted there is a flaw in the way the Android OS handles push notifications, a flaw that affects every single Android device, at least since Oreo, and maybe even before. It's a strange one because the issue doesn't seem to occur when the screen is awake, only when it is locked and off. At one stage I was hopeful features like AOD on AMOLED devices might be a solution, but alas, even with AOD active, the problem persists.
Now before you say "I've never had a problem with push notifications on my Android device", are you sure. Have you ever really been in a situation where you would notice? Try it for yourself, perform a test using a similar scenario to the one I mentioned in the second paragraph. Create a group chat in any messaging app you like, and have several of the group members with Android devices sit in the same room with their screens locked and off, then have one person send a message in the group chat, then watch as some get the messages immediately, some with a slight delay, and some not at all until they wake the screen. Do it a few times and you will soon notice there is no pattern at all, sometimes you will get the notifications immediately while others are delayed, then sometimes others will get the notifications immediately and yours will be delayed.
My most recent (and very last) Android purchase was the Samsung Galaxy S21 Ultra 5G (outright, not on contract, so you know roughly how much I paid). When I'm paying that amount of money for a mobile phone, I expect timely push notifications as a given, but no, the same issue occurs even with one of the very latest and greatest. I contacted Samsung Tech Support and the guy admitted it's the most common complaint he deals with every single day. I was previously given a similar story by Motorola and Huawei support too, and a little digging around online shows that thousands of Android users are complaining about the very same issue. Needless to say they now have that phone back.
I know I know, something this trivial shouldn't really bother me this much, but it does, it's just who I am. I can accept there is no such thing as a perfect mobile phone, I can live with an average camera, a budget processor, a dull screen, lifeless aesthetics etc. but there are some compromises I just won't make. Apart from the obvious (the ability to make and receive calls and texts), my requirements are quite simple - I require a phone with stable WiFi, Bluetooth and NFC, a decent battery life and of course timely push notifications. With no Android device currently able to fulfil my very simple requirements, it really did only leave me with one option - joining the dark side....so I bought an iPhone.
I have owned an iPhone for just over a month (that's two weeks longer than my last three Android devices), and thus far my delayed push notification woes have vanished. Now when someone in the family posts in our group, *PING* immediately every single time. The battery life is acceptable for someone like me who isn't the most demanding user, WiFi, Bluetooth and NFC have presented no issues, and it makes and receives calls and texts without a problem. I can honestly say the only thing I miss so far is my Android App Drawer. I know iOS introduced their App Library in iOS 14, and it's a start, but it's just not the same. There is probably an app in Cydia that would give me an app drawer, but I'm not quite ready to get into the world of jailbreaking just yet (I'm not that brave).
So after my big rant, here's a summary - Android push notifications are broken, they've been broken for some time and Google don't seem interested in fixing the problem. If someone told me tomorrow that Google had finally fixed push notifications, I would drop iOS like a hot potato and rekindle my love for Android. Please Google, help bring me back from the dark side, it's really cold out here!
Des
Click to expand...
Click to collapse
Now that's what I call a structured rant!
But what type of phone did you owned ?
I know this problem from samsung phones, and other phones I've tested. usually it's because of the OEM's aggressive take on battery management. They freeze apps in the background, and run them periodically to check notifications.
I know that's frustrating, but with your story I could feel the social isolation you've felt. And even with all the perks in the world, I wouldn't want a phone that makes me the third wheel.
But I'm much more radical than you, I don't want to change my phone, so I changed my friends. Way better now you should try it, those Apple "cool kids" pigeons weren't good friends anyway.
Obviously I'm just kidding, but I think the issue can be solved by using a ROM to espace your OEM's restrictions, or try another brand. If you ever want to come back to the light (which I'm sure you will because I couldn't bare iPhones after using an android all this time, seriously wtf if that file manager of them, and wtf is the "Other" memory partitions that increases without me having any control over it!), ask in various xda sections if users experience notifications latency, and if they don't know suggest them your little experiment you described in this post.
Hope you'll come back from your journey in the shadow,
Have a great day
Interesting rant.
Were all the phones that your friends had on the same networks? It could easily be a network latency issue
affecting how fast each message was distributed. Given that the passage of a message, say a Whatsapp message is at least: :
from phone screen
to
Whatapp encryption software
to
wi-fi-switch
to
domestic router
to
domestic ISP
to
internet backbone
to
commercial ISP
to
Whatsapp run cloud server
to
Whatsapp redirection processes
to
commercial ISP
to
internet backbone
to
domestic ISP
to
domestic router
to
wifi-switch software
to
friend phone
to
Whatsapp decryption software
to
phone notification sub-routine
to
phone screen
I'd say a small discrepancy in arrival times would be expected.....
I only mention this because it seems that you've tested massive of phones - but did you take into account different networks?
Just got update notification on op9 phone for android 12
Just wondering if anyone has android 12 and any issues etc with watch synch, notifications etc or anything
Have not updated phone yet
no issues on my note 20 ultra
My op9pro no issues
I read several articles about 12 being more buggy than previous releases. I have no experience with it yet. And I am not enthusiastic about losing Android Auto, which I use on the motorcycle and for which their replacement "solution" is not a solution (from what I surmise).
My months-old Samsung phone is still on 11 (because it is not an overpriced "flagship") and my old Samsung tablet is now stuck (permanently) on 10.
No issues with my flip 3.
I recently upgraded from my trusty Note 8 and am finding the new Android version to be completely underwhelming (a common theme, I'm finding). I can't really think of any actual improvements to my daily user experience and two things have gotten worse enough that I have been researching solutions to them to no avail. The first is the main topic of this thread. My older Bluetooth car stereo (not Android auto, but apparently that is equally as broken) sends an "autoplay on connect" request. No individual app autoplay setting seems to matter, it is a system problem. On the Note 8 this was also the case, however it would only actually play if the app was open (present in the task switch windows). This was occasionally annoying but now it is much much worse. What happens now on the S22U is that apps I have long since closed will just appear to open zombielike and autoplay. Even when I am in the middle of opening a music app, e.g. a podcast that I was listening to yesterday will just start playing because it was the last used app.
I can't believe that it's 2022 and Android doesn't just have this fixed yet it has been underdeveloped for YEARS now. Why can't it just be a system wide setting? And why on earth does it insist on playing audio even if it was PAUSED before Bluetooth is disconnected? I have a feeling there is nothing I can do about this, but I wanted to vent.
I mentioned there was a second most annoying issue with the new version of Android. This is that the "double tap to switch" to previous app window is inexplicably slower than it used to be, to the point you might as well not use it. I used to do that constantly and it was very effective. Why on earth they removed this feature is beyond me.
If anyone has a current solution to either of these problems please lmk.
I've also have this issue... Both with the Pixel 6 Pro and same thing when I switched to the S22 Ultra. I'm inclined to think it's an issue specific with Android 12. On my Pixel 5 (using Android 11), autoplay when connecting to bluetooth worked every time. Even with having setup a Bixby routine to autoplay upon connecting to a specific bluetooth device, it does not always work... It's frustrating.