Hi Ted, Thanks for this information. I don't come from a technical background but care very much about IPv6 proliferation nonetheless (from a development standpoint). I'm happy to offer any resources or information I can that might help. I am also an Android user, so let me know if there's anything I can do to help test.
Best, -Michael On Wed, May 11, 2016 at 8:57 AM, Ted Mittelstaedt <[email protected]> wrote: > Michael, > > Just about all posters to those threads are end users not system admins > and just about everything they have posted is sheer speculation. None > have really tested in a lab. Most seem concentrated on app settings or > are convinced it's an app bug. > > They are reporting the issue on 6.x , 5.x and some earlier than that. > Some of what they are reporting is certainly app setting errors. > > It would be useful to ask some of the people posting on those threads > if they have tried turning off wifi on the phone for a day or so > and seeing if the push notifications all started working. That might > get us some useful data. If push notices work on their cell carriers > data but not their own wifi network then you can reasonably argue that > there is a problem with their wifi network. That would be the first > step to getting them to do some logical troubleshooting. > > Ted > > On 5/10/2016 8:10 AM, Michael Oghia wrote: > >> Hi everyone, >> >> I am an Android user (but not a developer) and an avid follower of >> AndroidPolice.com. AP has been reporting about a similar issue for some >> time (see: here >> < >> http://www.androidpolice.com/2016/01/02/some-nexus-owners-are-having-syncing-issues-in-gmail-inbox-and-other-apps/ >> >, >> here >> < >> http://www.androidpolice.com/2016/02/10/the-gmail-sync-bugs-fix-is-rolling-out-over-the-next-week-no-app-updates-necessary/ >> >, >> and here >> < >> http://www.androidpolice.com/2016/03/24/gmails-synchronization-bug-is-far-from-resolved-users-still-reporting-issues-despite-promised-fix/ >> >). >> The issue concerns Android push notifications for Gmail, and many Nexus >> users specifically had raised the issue on the Nexus Help Forums >> <https://productforums.google.com/forum/#!topic/nexus/Ayd_1TOemSE> as >> well as filed multiple bug reports on the Android Issue Tracker >> <https://code.google.com/p/android/issues/detail?id=197805>. As you can >> read in the third link, it was supposedly fixed in previous builds but >> the problem has persisted for some. I don't know if the issue raised in >> this thread is the same, but I figured it was prudent to bring it to >> your attention. >> >> Since Android Police were the ones who covered it, I also CC'd >> Artem Russakovskii, the editor-in-chief. The AP staff may be able to >> provide more information in addition to what has been discussed so far. >> >> Best, >> -Michael >> __________________ >> >> Michael J. Oghia >> Istanbul, Turkey >> Journalist & editor >> 2015 ISOC IGF Ambassador >> Skype: mikeoghia >> Twitter <https://www.twitter.com/MikeOghia> *|* LinkedIn >> <https://www.linkedin.com/in/mikeoghia> >> >> On Tue, May 10, 2016 at 4:48 PM, Mikael Abrahamsson <[email protected] >> <mailto:[email protected]>> wrote: >> >> On Tue, 10 May 2016, Erik Kline wrote: >> >> It's really not clear to me what that version of rdisc6 would >> print if >> it encounters options about which it did not know anything. A >> pcap of >> just an RA would be best. The adb commands I pasted should also >> suffice to show what the device thinks it has for DNS, routes, >> everything. >> >> >> The version of rdisc6 included in Ubuntu 14.04 displays recursive >> DNS server. >> >> This is also seen in "tcpdump -vvv -n -i eth0 icmp6" and I see it as: >> >> rdnss option (25), length 24 (3): >> >> >> -- >> Mikael Abrahamsson email: [email protected] <mailto: >> [email protected]> >> >> >>
