Network error, data 'freezes' for a bit

[ChillingSilence]

So I've been noticing an issue where the data on the wifi just "stops" or "freees" for a bit. Noticed it specifically some times when watching YouTube videos.
Same for G+, sometimes as I scroll up and down the list it won't pull the images from the posts. This is what happened at the end here, was using G+, noticed it stopped, so switched to 3G and it worked fine. Switched back to Wifi and it was fine again:
http://pastebin.ca/2160365

See from Line 945-ish

I can confirm that my Galaxy Nexus (Running latest official Google AOSP build) was working at the same time, not an issue with the wifi...

[tgascoigne]

Yeah, I've noticed that "error -13" thing before too

[ChillingSilence]

Happened also when using MIUI which AFAIK is based on official Sense ROMs.
Happened to me a week ago, flashed / factory reset and went to MIUI. Still happens. Flashed and went back to this ROM, factory reset, still happens.
Happened on Trips, I think they were initially blaming the Chrome Beta and it's sync which stops, but right now I don't have Chrome (Haven't installed it since coming back from MIUI) and it's still buggered...

[tgascoigne]

Would be nice to get a logcat if possible

On Wed, Jun 13, 2012 at 2:44 AM, ChillingSilence
reply@reply.github.com
wrote:

Happened also when using MIUI which AFAIK is based on official Sense ROMs.
Happened to me a week ago, flashed / factory reset and went to MIUI. Still happens. Flashed and went back to this ROM, factory reset, still happens.
Happened on Trips, I think they were initially blaming the Chrome Beta and it's sync which stops, but right now I don't have Chrome (Haven't installed it since coming back from MIUI) and it's still buggered...

---

Reply to this email directly or view it on GitHub:
#51 (comment)

[ChillingSilence]

There was one in the first post? I'm doing some flashing this afternoon, will send another example shortly.

[tgascoigne]

My bad, didn't see it
On Jun 15, 2012 3:43 AM, "ChillingSilence" <
reply@reply.github.com>
wrote:

There was one in the first post? I'm doing some flashing this afternoon,
will send another example shortly.

---

Reply to this email directly or view it on GitHub:

#51 (comment)

[ChillingSilence]

No worries :)

Another one from earlier today finally came through (Email to myself):
http://pastebin.ca/2161481

Was trying to post on Wifi on G+, didn't work. Dropped back to 3G, didn't work...

[ChillingSilence]

Took Build #57
Flashed boot.img followed by fastboot erase cache
Flashed Build #57
Factory reset from recovery
Flashed gapps-ics-20120429-signed.zip
Rebooted

Told it I didn't wanna use my Google account during initial setup
Connected to Wifi
Went in to Settings --> Accounts & Sync --> Google Account --> Added my google details
As soon as I did this I got an error in the notification bar:
"sign in error for josiah@%mydomain%.co.nz" (Replace %mydomain% with my domain name, I've removed it for spam reasons)
If I do what it says and "Touch to sign into your account", nothing happens.
I was able to fire up the Play Store just fine and immediately install alogcat, dump the logs and we now have:
http://pastebin.ca/2162717
It seems to be OK at the moment (I'm posting the logcat for future reference partly for myself), but I'm about to install SMS Backup & Restore, Gmail, G+, YouTube and Chrome Beta and will see if the results continue. Those will be the only apps I'll install for now, just for testing purposes, as I notice the issues a lot when using G+ / Chrome.

[tgascoigne]

Thanks for all your help testing @ChillingSilence :) I'll leave this one open for the time being until we're sure

[ChillingSilence]

I'm surprised, doing it this way around seems significantly better? The "tap here to login" didn't disappear from my notification bar until I rebooted.

Still, if this is how it has to be "done" in order to resolve the issue, then I'm more than happy to do it this way...

Happy to help @tgascoigne , any time :)

[ChillingSilence]

Logcat one:
G+ not updating (Was on 3G at the time) - http://pastebin.ca/2162786

Logcat two:
Gmail inbox on the app not updating when manually pushing the "refresh" button (I had another email I'd read 10 minutes earlier on my Desktop I was expecting) -
(Search for %REMOVEDFORUPLOADTOPASTEBIN% for the parts where it fails)

Logcat three:
Taken 23 seconds later, still on 3G, tested Chrome Beta to make sure it wasn't just 3G being stupid. Definitely worked fine:
http://pastebin.ca/2162790

You should see most of Logcat two is also in Logcat three coz they were taken so close together :)

[tbalden]

This g+ issue seems to be present in TeamNDVRu tree as well, im still testing this. may be a generic issue wtih G+ and current cm9 tree?
@ChillingSilence do you have your gnex with latest nightly? is g+ notification working with that?

[tgascoigne]

I doubt this is app dependant, the logcat suggests that the system just cannot contact the server. I'm still curious as to whether this might just be an SSL issue. I'll try and replicate this and have a play around.

[tgascoigne]

So I've managed to replicate it, and I think I've found where the problem might be. Could you try this boot.img for a while and see if you still notice it?
http://tom.gascoigne.me/boot.img
I think the issue is resolved for me. It didn't work after first boot, but after a second boot I haven't been able to replicate the issue.

[tbalden]

what gave you the idea that changing a read only device to writeable might help? it's a device to be read from userspace, afaik

[tgascoigne]

The problem is that qtaguid can't untag the sockets, to do that it needs write access to /proc/net/xt_qtaguid/ctrl, which it doesn't have, as its throwing permission errors to the logcat which coincides with this issue. By giving it permission, the logcat error messages disappear and it looks like the problem is solved.