Dear all,
I'm currently running a stock S9+ on android pie, on the Virgin (VMNP using EE network) in the UK. I experience delays with WhatsApp and push gmail notifications very regularly.
From searching on the internet I have come across two common reasons. One of which suggests this is a Samsung One UI induced issue and a combination of Samsungs implementation of doze not working properly in the android Pie update.
The other reason suggests that Virgin is just a garbage network piggy backing on EE and they are throttling data based notifications for whatever reason?
Does anyone else have similar experiences to this and have you come across any possible solutions?
I have resorted to using Samsung email to solve the push notification problem, I just have it syncing every 15 mins which works perfectly fine and I actually prefer the app to Gmail. Battery impact is negledgable as well.
Any input here will be greatly received so thanks in advance!
Related
I'm having a little (and simple to reproduce) problem with my Samsung Galaxy S2.
When on 3G data connection, about 5-6 minutes after the phone locks with the screen going off it will stop synching any kind of data. It won't receive any incoming messages from Google Talk, Gmail, Heytell or any other similars. Randomly after several minutes it's like the phone wakes up, checks, and receives all incoming messages all at once.
Also it will receive it all when I unlock the phone and I have noticed a little pattern in the antenna signal icons where they go from blu to white to blu again and then the magic happens.
Do you have any hints on how to fix this or make at least more bearable?
When on wifi there is no problem at all and all messages are synched instantly.
I have used a few custom roms (resurrection remix and revolt both with android 4.1.2). I have tried to change modems and kernels with no luck.
I believe it is a problem with jb 4.1.
Is anybody having the same experience or could give it a try?
Thanks in advance.
I have a Galaxy Nexus (GT-I9250) and a Galaxy S4 Google Edition (GT-I9505G). Both unlocked and rooted.
With JB 4.2.2, the native SIP dialer has always worked very well and I could place and receive calls (using my own Asterisk PBX server) without problems.
With the new JB 4.3 OTAs now, whenever I place or receive a call, the incoming audio is perfect but the outgoing voice sounds terrible: choppy and noisy to a point where the people on the other side can hardly understand what I'm saying.
I flashed both units back to JB 4.2.2 and the problem went away, no matter the configuration or the apps installed.
Conversely, I can always replicate the problem with JB 4.3, clean setup, no additional apps or services.
Anybody else experiencing the same problem? Any idea what might be causing the problem? I cannot believe 4.3 has such a glaring bug, must be me doing something wrong.
Thank you in advance!
Bump
Having the same issue, also using a Galaxy S4 Google Edition (GT-I9505G) on rooted stock 4.3.
If anyone has any info. Thanks!
I opened a ticket with Google 3 weeks ago. Every time I check they keep telling me that they forwarded the issue to the development team but so far I have not heard back from them.
I'm almost certain this has nothing to do with the Samsung Galaxy S4 GPE, and everything to do with the new Android 4.3, since I can replicate the same issue on my old Galaxy Nexus. With 4.2.2 both phones were working fine.
Anybody else experiencing the same issue?
---Mirco.
The same problem is also happening with CSipSimple, so I'm guessing it's not something strictly related to the native Android Sip dialer.
And it has nothing to do with the Sip account either. I can replicate the same problem with my own Asterisk server, but also using a callcentric.com and pbxes.org
Is Android generating a system/debug log every time i place a call?
If so, does anybody know where it's saved?
Hello,
Recently purchased an LG V10 with 5.1.1 stock, AT&T, and I've done absolutely no modding.
Scenario 1: sending hangouts data messages over LTE (for example; they are quick and easy to test with) work OK from my end. On receiving phone on different carrier, message arrives in about 5sec. Slower than I'm used to on every other phone I've used but not a big deal. SMS are sent faster and arrive in the normal amount of time which is still faster than hangouts.
Scenario 2: My phone is asleep\screen off and hangout messages are sent from the other phone to mine over LTE. My phone does nothing for as long as I let it stay asleep. But Incoming phone calls to my cell number notifies me instantly and
SMS sent to my phone notifies me instantly.
Scenario 1 and 2 are the same when using Wi-Fi, and with other apps that can trigger notifications when the screen is off. Those notifications only appear after I've unlocked the phone, and some appear only after I've opened the app. The notifications will have correct timestamps but the sounds and visuals only happen once I've picked up the phone and started using it; they all flood in at once.
I've made sure that my settings for allowing notifications (priority it's called on the LG ROM) is set to allow everything.
I've done a lot of searching online and people with various phones (Galaxy S6's most recently) appear to have this issue and it also appears to have a history as far back as Android 4.1. They say the fix is an app that changes the checking times from the stock Android 28minutes or something, down to like 5 minutes. I have tried one that doesn't require root and it has not changed any behaviour that I can measure.
My question is, is this a phone problem? Like a bad OS install from the factory (did i just get a bad unit?) or an APN setting issue (haven't messed with it from factory settings) or is it an Android problem that needs a bug submitted since I see it happening on Samsung phones too?
I've had many other phones, mostly Samsung and even a Note 4 with Android 5.1.1 but hangouts and emails and every other notification was practically instantaneous whether on Wi-Fi or cell network.
Thoughts?
USA TA-1085 here, had this issue since I've had the phone. I'm on an AT&T post-paid plan and I can't send or receive MMS, whether it's a picture or a group text, while connected to WiFi. If WiFi is switched off or not connected to a network, MMS functions seamlessly. If connected to a network, Android Messages will prompt me to download, and it'll spin for awhile and then time out. I've tried other messaging apps like Textra with no results. My APN settings are the same as my previous phone (Moto G5+)
Nokia Support had me delete a lot of system app data, toggle battery saver, and nothing worked. They only indicated that a solution may be presented through an app or system update, that they report bugs to Google with a request for resolution, that updates "usually come every month" and "most likely within November I should receive it." For what it's worth, that's a similar response I got to issues with Smart Lock, and those issues have since been resolved.
Has anyone else seen a similar issue and fixed it?
I just tried this on my 7.1 and had no issues. I sent an mms from a MintMobile device to my 7.1 on AT&T and it worked with the WiFi connected. I know this doesn't really help but I'm just letting you know as another data point.
I had issues with MMS in general. I removed all the APNs, created a new one with all the proper TMobile info, and installed Textra (which I own). No issues since then.
Oddly, I wasn't aware I may have been having MMS issues but while I was checking the APN for LTE connection I messed something up and lost connection completely and reset my APN's to default. This prompted an MMS message to be immediately delivered upon reconnecting which could have been a coincidence but after seeing this post and testing sending MMS messages to myself and friends, I have no issues now on T-Mobile on Wi-Fi or off.
Saw a thread in the Nokia 7.1 forum that links this behavior to WiFi calling. Is that enabled on your phone?
https://community.phones.nokia.com/support/discussions/topics/7000038488
I've got an Ulefone Armor 9 I recently purchased. As part of setting it up to work as desired, I swapped away from the default messaging app to one that supports dual SIM operation a bit more gracefully.
I've since noticed that after a prolonged idle, such as sleeping, the phone drops all SMS messages. It isn't that they don't send notifications -- they simply don't exist as far as I can tell. I tried a different messenger, and while it displayed the texts received with the other one, the missing messages weren't there either.
This doesn't appear to be an issue between the carrier and phone. Or, rather, if it is it's impacting both carriers at the same time, because sending text messages to both numbers when the problem is present results in neither being delivered. The carriers don't buffer the messages for later delivery as if the phone was offline, and calls come through okay but do not resolve the SMS issue.
I can reboot the phone or manually open the SMS app/bring it to the foreground, after which point I will start receiving messages again. Only ones sent after performing this activity, however. The prior ones are lost.
I've checked to ensure that the app itself is running in the background and Android says that it is. I've not got anything that should be pausing it (that I'm aware of), so I'm not sure why Android would stop sending it messages. I'm also not familiar enough with Android to know how the OS handles texts. Clearly there's some sort of storage & OS management, because the alternate app I tried as part of troubleshooting was able to pull my message history.
Has anyone got any ideas on further troubleshooting steps, or insight into how Android handles texts in general that might help narrow down the point of failure?
GV00 said:
I've got an Ulefone Armor 9 I recently purchased. As part of setting it up to work as desired, I swapped away from the default messaging app to one that supports dual SIM operation a bit more gracefully.
I've since noticed that after a prolonged idle, such as sleeping, the phone drops all SMS messages. It isn't that they don't send notifications -- they simply don't exist as far as I can tell. I tried a different messenger, and while it displayed the texts received with the other one, the missing messages weren't there either.
This doesn't appear to be an issue between the carrier and phone. Or, rather, if it is it's impacting both carriers at the same time, because sending text messages to both numbers when the problem is present results in neither being delivered. The carriers don't buffer the messages for later delivery as if the phone was offline, and calls come through okay but do not resolve the SMS issue.
I can reboot the phone or manually open the SMS app/bring it to the foreground, after which point I will start receiving messages again. Only ones sent after performing this activity, however. The prior ones are lost.
I've checked to ensure that the app itself is running in the background and Android says that it is. I've not got anything that should be pausing it (that I'm aware of), so I'm not sure why Android would stop sending it messages. I'm also not familiar enough with Android to know how the OS handles texts. Clearly there's some sort of storage & OS management, because the alternate app I tried as part of troubleshooting was able to pull my message history.
Has anyone got any ideas on further troubleshooting steps, or insight into how Android handles texts in general that might help narrow down the point of failure?
Click to expand...
Click to collapse
I'm not sure if this would help but try messing w/ "App Blocker's" settings for your SMS app or even disabling App Blocker altogether (in the settings menu under "smart assist" I think).
BigBossPlaya said:
I'm not sure if this would help but try messing w/ "App Blocker's" settings for your SMS app or even disabling App Blocker altogether (in the settings menu under "smart assist" I think).
Click to expand...
Click to collapse
Unfortunately, it was already off, so no dice there. Ulefone pushed an update I thought might have fixed it, but after about 18 hours of idle I sent a test message and it fell into the void. Opened up the messenger app again and sent another and that one arrived without issue, but no sign of the first.