yashsingh1/xdaforums huggingface dataset:
[Galaxy S6 Q&A, Help & Troubleshooting] gsheremeta:
arf8, what kind of router do you have, are you running a custom firmware, and does it have IPv6 enabled?

I have solved my problems on wifi by switching out my router to an old Broadcom-based one running Tomato and no IPv6.

Still testing out 4G, but I think it's solved there as well. I disabled IPv6 on the phone's APN. So I'm suspecting IPv6 incompatibility at this point.
[Galaxy S6 Q&A, Help & Troubleshooting] arf8:
It has nothing to do with your router, it is a bug in the phone that samsung is aware of.

In fact my issue has nothing to do with wifi it's over mobile network and your issue was ipv6 and router config.

Samsung is working on the bug but it won't be fixed for a while as they allocate resources to fix issues per complaints they get. Plus most people don't even realize they have this problem Unless they depend on push email or other apps that use push. Not all but some apps are affected by same bug.
[Galaxy S6 Q&A, Help & Troubleshooting] gsheremeta:
I disagree. It's obviously a bug in the OS, but I believe the bug is related to IPv6. And so the router and the APN configuration would matter. If the router didn't matter, swapping my router wouldn't have helped. Anyway...

Does your router run IPv6? I bet it doesn't.

Can you try making a new APN and only allow IPv4 on it? Then see if you can get notifications over 4G. A beer says you will.
[Galaxy S6 Q&A, Help & Troubleshooting] arf8:
Lol, really. It has nothing to do with the router. Its a bug samsung is aware if thanks to me bringing it to their attention and my carrier. Google it I've been all over this since day 1. Your router has nothing to do with push notifications over mobile network. Just bc you had screwed up settings on your router it does not mean anything.

Move alonh
[Galaxy S6 Q&A, Help & Troubleshooting] gsheremeta:
I never said it did. Of course a router has nothing to do with 4G. You seem to think you're talking to an idiot? I'm a virtualization and distributed systems software engineer -- I know what I'm talking about.

I, and 90% of the people I've interacted with (mostly on reddit), have the issue on BOTH wifi and 4G. Several of us have fixed it *on wifi* by turning off IPv6 or swapping routers.

That implicates IPv6. IPv6 also runs over the new AT&T nxtgenphone APN, which could be the root cause for those of you having the issue on 4G. (Several people reported issues on only wifi, and 4G was fine for them.)

Therefore, I am trying to ask people to test that. So: would you please try to disable IPv6 in your APN?

Yes, you can wait for Samsung to fix it if you want, but I don't know why you wouldn't want to try a possible workaround.
[Galaxy S6 Q&A, Help & Troubleshooting] arf8:
From one Engineer to what ever title you give yourself, If you can't comprehend, I can't help you.

Let me repeat again, this problem is not related to ipv6

Lol, some people's kids
[Galaxy S6 Q&A, Help & Troubleshooting] arf8:
Lol, you would think I can't spell from my recent post with all those typos. Fat finger fun i guess on touchscreen, joy

Let me explain why this has nothing to do with ipv6. The phone once it goes into a sleep state sets a flag which prevents certain push notification from working, audible notification being an obvious one than followed by another state where even the led notification do not appear. If ipv6 was the culprit, which is not, than you would not get any notification at all using the mobile network, when the phone is working outside of those bug conditions. Hence this is not related to ipv6, it has everything to do with the way the software handles push notifications specifically email and some apps when the phone is unused after a specific amount of inactivity. Once the phone is woken up via user interaction or phone call or SMS than all the notifications start pouring in, audible or not.

Now with that said, I have tested 7 different S6E phones and repeated my tests 100% of the time. I can say that when on Wifi the phone does not exhibit these behaviors due to the fact it is keeping the connection to the router alive via TCP/KA messages, so if your router is setup correctly (ipv4) and phone is connected without any radio interference to prevent dropped connections, the phone is not going into this sleep state where the flag is inadvertently set to prevent audible notification.

So again while you may experience problems over wifi due to improper router settings, it has NOTHING to do with this bug!!!

Cheers
[Galaxy S6 Q&A, Help & Troubleshooting] ps0ps:
AT&T is timing out IPv6 GCM and other long poll tcp connections after 5 minutes

So the issue is with AT&T's published network timers(search for "developer.att.com network-timers"). They claim that you can keep a TCP connection open for 30 minutes without any activity before that session will get closed, but this isn't the case. On IPv6, which is currently limited to a handful of new Android devices, they connection times out at 305-310 seconds, while I have yet to ever have my IPv4 long poll connection time out. I wrote a simple test to run on my Galaxy S6 and HTC One M9 which opens a socket to any tcp ip, port and the server which accepts the connection will send down a periodic hello for the client to respond to echo back. The amount of time between hello's increases slowly at a rate of 1.3x the previous idle time and the server considers the client gone if it doesn't receive a response from the client after a few seconds. This is how I discovered that AT&T is reaping idle connections on IPv6 after 5 minutes, yet I have yet to get an IPv4 connection reaped after more than 1 hour of idle time.

Once the connection idles out of the AT&T session tables on their network devices, if GCM tries to send a notification to your phone, it fails, but your phone has no idea the connection is bad until GCM itself reconnects or the user roams onto wifi or starts using the app which has queued up notifications.

This is extremely terrible and while disabling the IPv6 APN will solve the problems for you, it's actually not the right solution as IPv6 is the way forward for the mobile internet and we've been measuring significant performance throughput gains (20-40%) on IPv6 over IPv4. What needs to happen is AT&T fix their network to stop reaping idle connections after 5 minutes.
[Galaxy S6 Q&A, Help & Troubleshooting] arf8:
I hate to tell you this but this is not limited to Att, other carriers are exhibiting this issue with the s6/s6e and other clients using IDLE IMAP and not GCM have this problem. I've tested other phones which absolutely do not exhibit this problem which are also on ATT both ivp4/6.

Again this is a known bug with the S6/S6e and it is an acknowledged bug by Samsung. At this point all we can do is wait for a fix. But to blame the carrier is false.

---------- Post added at 05:19 PM ---------- Previous post was at 05:07 PM ----------

Lets assume what you are saying is also true, the issue with that is that my phones running ipv4 apn can sit idle for more than an hour and if i get an email it is instant, so while it may be true that ATT is closing the socket to free up available sockets, it still has no bearing on this notification problem. Lets put GCM aside and focus on IMAP IDLE, again if the phone is inactive for a few hours my phone still gets instant notifications.

I'm still interested to hear how you correlate this available socket with a phone which has already timed out the port and still receives instant notification hours after on other phones using ipv4.

cheers
[Galaxy S6 Q&A, Help & Troubleshooting] ps0ps:
Actually, I have tested this on the HTC One M9 as well and my IPv6 connections idle out at exactly the same time on AT&T's network as they do on the S6, while my IPv4 connections have no problems at all. This is why I am blaming the carrier because this is obviously a problem with their timeouts since the tcp connection is still active on the phone. I'd like to know which phones you have tested, as I can easily test any of them.

Are you sure you're not comparing the IPv6 issues Samsung has where it drops all IPv6 connectivity on Wi-Fi when the display turns off as a way to save battery life?

I've never said that the ports are timed out. My IPv4 connections never time out as I'm able to continue to send data from my server to the phone without the phone having to reconnect after 1+ hour of the connection being idle. What I'm saying is a problem is I open a TCP connection to a random machine I control over the LTE network using IPv6. If I wait 301-310 seconds and then have the server send a "hello" to my phone and then wait for a response, my machine will never see the response as the phone never got the data. If I repeat the same experiment over IPv4, everything works just fine. This happens on the HTC One M9 as well. I've also tested the S6 on Verizon and there both IPv4 and IPv6 time out at the same time as they advertise.
[Galaxy S6 Q&A, Help & Troubleshooting] arf8:
Still how does the 1800sec timeout matter once the phone has been inactive for beyond 1 hour. It is not related to this issue or a separate matter on its own if you are trying to link the two issues together. Att will keep the address in the table as long the phone has a signal beyond the advertised time which they claim is subject to change, on ipv4 the same timeout rules are applied so lets assume you are right and ipv6 is cut short, it still does not make a difference when a phone using ipv4 apn is able to instantly receive notification beyond 1800sec posted timeout (which again is subject to change according to ATT).

You can test this on S5, S4, or any Blackberry 10 device (all on ipv4), on an M9 I tested there were no problems which is defaulted to ipv6

Please leave Wifi out of this.. we don't need to go there again, unless you are the same user and just changed your username...

---------- Post added at 06:40 PM ---------- Previous post was at 06:00 PM ----------

Sent you PM
[Galaxy S6 Q&A, Help & Troubleshooting] gsheremeta:
You don't own the internet, so if we want to discuss wifi, we will.

Many people have the issue on wifi. Here is one such post, and that person solved the issue by swapping his router. (Same for me.)

https://www.reddit.com/r/GalaxyS6/c...ation_delay_bug_anyone_else/csq8g4n?context=3

Yes, while is is probably an OS bug, there are ways to work around it. Clearly.

---------- Post added at 04:25 PM ---------- Previous post was at 04:18 PM ----------

Fantastic post, excellent debugging. Well done.

So, disabling IPv6 on the APN is not the proper fix, but it's certainly a viable workaround for those of us who want a working phone in the meantime. And it looks like disabling IPv6 is the fix for those having wifi issues as well :good:

[and I would ignore arf8 at this point. :) He's got some narcissism issues.]

Thanks man!
[Galaxy S6 Q&A, Help & Troubleshooting] ps0ps:
You can clearly see the wifi issue being reported else where and what Samsung's response on it is. (lists.cluenet.de/pipermail/ipv6-ops/2015-June/010634.html) The issue is similar to the cellular issue in that GCM connections are still established when the Wi-Fi radio disables IPv6 and won't refresh for a maximum of 28 minutes. Basically if GCM hasn't seen activity on it's established sockets, it will refresh/keep-alive the existing connection at around 28 minutes.

I really hope people don't keep IPv6 disabled. We've been working hard to push more IPv6 on the internet and the performance gains on v6 for mobile networks is pretty huge, so it would be a shame if a large percentage of people disable IPv6.
[Galaxy S6 Q&A, Help & Troubleshooting] gsheremeta:
Well, then I'm going to leave IPv6 off :(

I know almost nothing about IPv6. Is this a protocol issue?
[Galaxy S6 Q&A, Help & Troubleshooting] ps0ps:
No, it's done so that Samsung can get the battery life the carriers demand out of the devices. IPv6 has something called 'Router Advertisements' (RA) and they are sent down via a multicast packet every N seconds (between 4 and 9000 i believe) and if a network sends down RA's aggressively, the wifi radio can wake up process the request and then go back to sleep, but this causes battery drain. Samsung's approach is particularly bad because it doesn't tear down active TCP connections, so if there is a connection to GCM over IPv6 wifi, you'll miss notifications until you use your device again or GCM refreshes the connection. Hopefully we can convince Samsung that they should fix this since it's a terrible user experience.

The cellular radio problem is different in that ATT is removing the IPv6 TCP connection out of their firewall session table (or whatever they are using), which again will delay GCM notifications.
[Galaxy S6 Q&A, Help & Troubleshooting] gsheremeta:
All makes perfect sense.

Agreed. How can I help?
[Galaxy S6 Q&A, Help & Troubleshooting] ps0ps:
Probably show how notifications on kakao come in immediately on non-samsung devices while they are delayed on samsung devices. My HTC one M9 works perfectly when the display is off and on IPv6.
[Galaxy S6 Q&A, Help & Troubleshooting] gsheremeta:
Show where? http://developer.samsung.com/ ?
[Galaxy S6 Q&A, Help & Troubleshooting] arf8:
There are multiple issues with notifications, I'm the least bit concerned with wifi, and as I have PM back and forth with ps0ps we have shared our testing results, I have told him ipv6 enabled on my wifi did not cause any problems, while I'm not ruling out there might be issues for some the bigger problem is the mobile network.

Both him and myself are trying to get this issues resolved through various channels, I have posted my case numbers for those who want to reference them or create your own.

If you want to help

what you can do is call your carrier and Samsung. The more visibility this problem gets and the more calls they get, they will expedite the resolution.
[Galaxy S6 Q&A, Help & Troubleshooting] waoasis:
Using Sprint, got the latest update 5.1.1 and still having the issue. Only when I get to turn the screen on then a bunch of some missed notifications suddenly pop out which should have rang the phone minutes to hours ago.
[Galaxy S6 Q&A, Help & Troubleshooting] ps0ps:
LTE or Wi-Fi? If Wi-Fi, do you have IPv6? If yes, this is intentional behavior by Samsung. If no, I'll go pick up a sprint phone and see if I can reproduce the AT&T issues
[Galaxy S6 Q&A, Help & Troubleshooting] waoasis:
Yes on WiFi with ipv6
[Galaxy S6 Q&A, Help & Troubleshooting] ps0ps:
Known issue with Samsung. It's been raised with samsung and we just have to wait for a fix. They do this to "save battery" which has created a pretty poor user experience.
[Galaxy S6 Q&A, Help & Troubleshooting] allindaze:
This is so annoying and frustrating. I can't believe it's not being addressed already by Samsung and AT&T. I mean who in their right mind would think it's ok to miss notifications for up to 28 minutes?
[Galaxy S6 Q&A, Help & Troubleshooting] ps0ps:
Well, if you're not using IPv6 Wi-Fi, then AT&T is only to blame. The Wi-Fi IPv6 issues Samsung are being addressed via different channels
[Galaxy S6 Q&A, Help & Troubleshooting] allindaze:
I've just disabled IPv6 in my APN and it appears to have made a difference. Not sure though.
[Galaxy S6 Q&A, Help & Troubleshooting] ps0ps:
This is now fixed on AT&T in the bay area and rollout across the rest of the country should happen soon.
[Galaxy S6 Q&A, Help & Troubleshooting] riahim:
Wait, really?!?!?! Is there anything I can do to get this issue addressed faster where I am located (michigan). Both at&t and samsung had't even heard of this issue, or were playing dumb, when I called them (about 2 weeks ago). At&t ended up sending me a new phone and I still have the same problem. This is driving me nuts and I don't know what else to try.
[Galaxy S6 Q&A, Help & Troubleshooting] waoasis:
This is only when ur on WI fi. With data it doesn't happen
[Galaxy S6 Q&A, Help & Troubleshooting] riahim:
The issue happens whether I'm on data or wifi for me...
[Galaxy S6 Q&A, Help & Troubleshooting] ps0ps:
There are two issues.

1. The wifi issue on samsung is when the display goes to sleep, samsung will disable IPv6 to "conserve battery", but this breaks all notifications. Samsung has been made aware of the issue and it's being actively worked on. I don't know when this will get fixed, but they are being pressured so hopefully it is soon

2. AT&T is timing out long poll TCP connections on IPv6 after 5 minutes. The fix is being rolled out or completed by now in the bay area and once they are done here, it will slowly roll out nationwide.
[Galaxy S6 Q&A, Help & Troubleshooting] riahim:
This makes sense, but just to clarify. This also happens when I'm connected to data, in which case ipv6 wouldn't matter, right? Also, I went into my modem and turned ipv6 off temporally to see if it fixes the issue and it didn't help, so I ended up just re-enabling it. Its almost as though my phone is in deep sleep and nothing wakes it up until it is manually woken up by turning it on.

Also, not sure if related, but the first issue I had was not receiving calls. People would call me (after my phone goes into this deep sleep mode) and my phone will not ring. In addition, if they don't leave me a voicemail I don't even know that they called me since I don't receive a missed call. However, if they do leave me a voicemail, my phone will actually be able to wake its self up and notify me. I talked to at&t about this and they had no idea what the problem was so they sent me a new phone, but unfortunately it still hasn't fixed the issue. Btw, this issue does not happen every time someone calls me. I would guess about 50% of the time my phone will actually ring while the other 50% it acts like it's dead. And yes, I have signal.

So I seem to have 2 issues:

-notifications

-calls

Notification issue is definitely way more prevalent and happens multiple times a day.

Any recommendations on what I can do?

edit: Just as I was typing this, I didn't get notifications. I'm connected to 4g lte and once I unlocked my phone I got like 5 groupme messages what were sent like 20 min ago...
[Galaxy S6 Q&A, Help & Troubleshooting] ps0ps:
When you're on AT&T data (nextgenphone APN), you're using IPv6 and you suffer from the 5 minute timeout issue for IPv6 tcp connections. Again this fix will be rolled out in a couple of weeks nationwide. Wi-Fi IPv6 is another issue with samsung devices that are independent of the AT&T LTE/4g/3g etc IPv6 issues.
[Galaxy S6 Q&A, Help & Troubleshooting] riahim:
Gotcha. Thank you for clearing up these issues. So until att rolls out that update, there isn't anything I can do, right? And same thing with samsung
[Galaxy S6 Q&A, Help & Troubleshooting] ps0ps:
On AT&T you can disable the nextgenphone APN, but this is a bad idea since you'll use VoLTE and generally you're going to want IPv6 enabled on data. As for you wifi, I don't have an answer for you other than to disable IPv6, but that's also bad. IPv6 is needed for the internet to continue to grow and by disabling it you're just going to be causing yourself more problems in the future. I can tell you that Samsung is getting a lot of heat to fix this right now, so I expect it will get fixed as major US carriers are on them
[Galaxy S6 Q&A, Help & Troubleshooting] riahim:
Thank you very much for this help. I really appreciate it.

One other question. You talk about VoLTE. I currently have enhanced 4g lte services off. Should I leave this off or turn it on or will it not matter?
[Galaxy S6 Q&A, Help & Troubleshooting] ps0ps:
I don't know what 4g lte services are.. I don't really use AT&T, I just got a phone to debug this problem.. sorry
[Galaxy S6 Q&A, Help & Troubleshooting] Plecebo3:
I'm trying to report this issue to Samsung to hopefully get a resolution sooner. Is there a way to identify this issue to them so they can register that I too am experiencing this problem? So far the support person seems completely unaware of the issue and is having me try some odd things.

I have a Comcast router and they won't/can't disable IPv6 on the equipment. I've requested one of the cellspot routers from T-Mobile and think that will address the issue when it arrives but it isn't a fix it just avoids the problem on the network I use the most.

Samsung support via the website is a joke so far. They sent me a response but when I replied the email bounced. I've had much better luck using the [MENTION=5246982]SamsungSupport[/MENTION] twitter account.
[Galaxy S6 Q&A, Help & Troubleshooting] ps0ps:
Samsung is working on a fix for the wifi display off issues. no eta
[Galaxy S6 Q&A, Help & Troubleshooting] Plecebo3:
What is the best way to let them know that I suffer from this issue as well. I also tested this on an s5 and had the same problem. So that is an s5 and an s6. Seems kind of widespread. I think most people just don't realize they are missing the notifications since they mostly rely on SMS messages.
[Galaxy S6 Q&A, Help & Troubleshooting] ps0ps:
Honestly I don't know. Samsung doesn't seem to be taking this issue seriously and I wish they would. It's only if particular carriers complain that they come up with some solution, but it's really not a great solution.
[Galaxy S6 Q&A, Help & Troubleshooting] jetbruceli:
If it helps it only happens to my s6 and not my wife's s5. It really passes me off cuz I won't what's app messages till I unlock and use the phone.
[Galaxy S6 Q&A, Help & Troubleshooting] daruda:
Have a galaxy S6 since last week and experiencing the same issue. Only on wifi at home.

Anybody a solution yet? Not possible to turn ipv6 off on our router...
[Galaxy S6 Q&A, Help & Troubleshooting] waoasis:
Nope just bear with it
[Galaxy S6 Q&A, Help & Troubleshooting] dansoriano:
Any News about this issue? I'm from Brazil and my phone is having the same problem, when it stays with the LCD off for a while it stops notificating me. It happens on WIFI and 4G.
[Galaxy S6 Q&A, Help & Troubleshooting] jaswinky:
No yet. I was free issue for two or three weeks, but some days ago the issue returned again on my device sometimes...

Enviado desde mi SM-T520 usando Tapatalk 2
[Galaxy S6 Q&A, Help & Troubleshooting] ombadboy:
Same here.. comes and goes randomly...
[Galaxy S6 Q&A, Help & Troubleshooting] dansoriano:
Just talked to Samsung support via WebChat, and they told me they know nothing about this problem, and all I can do is a factory reset to see if it fix the problem, or send it to tech support.

Well, I already did a factory reset and I think that this problem won't be solved by sendind it to tech support, but I'll try it.