Android 4.0.2 streaming disconnect and reconnect

Thanks for the report. Will take a look to see what is causing the issue.

Just got a Galaxy Nexus / 4.0.2, also encountered this problem, and would like to add some information :

- I notice that whenever the screen is turned off, pinging GN on a local network varies between 60-1200ms. Once the screen is turned back on, ping is back to < 10ms instantly.

- WiFi connection remains intact throughout the process. Just very bad ping when the screen is turned off.

Look forward to seeing a fix for this problem soon. I have to fall back to my N1 for XiiaLive needs.

Thanks for your feedback! I might have to purchase one of these phones so that I can test this fully...

I was able to reproduce a similar issue on XOOM tablet but my case it disconnects after 1hr of playback.  The connection timeout.  I'm still looking into it.

Had XiiaLive on DroidX for 18 months and never had a problem.  I too recently upgraded to Galaxy Nexus 4.0.2 and experiencing problems.  Only mine totally freezes.  The widget doesn't respond, stop/start controls do not respond and cannot close the app.  Happens after a few minutes of playing.  It might be during sleep as mentioned above.

Thanks for your feedback in regards to this issue.  We are almost done with Beta release.  After 1-2 weeks of the beta being out we will release officially...

Thanks for the report. Will take a look to see what is causing the issue.

Same issue here. Galaxy Nexus Wifi performance becomes very bad when the screen is off. It disrupts streaming, but also any other traffic - downloads stall or fail, Market updates stall or fail etc. Very annoying. There's a bug at Google: http://www.google.com/support/forum/p/Google+Mobile/thread?tid=1bbb6dcd335d9525&hl=en

I am using 128+kbps streams, lower bitrates might work better (haven't tested). Sometimes it will play for some time (the best I've done is 20 minutes or so) before having to rebuffer, but most of the time it only plays for a minute or two before reconnecting.

I have noticed this issue as well when using the beta internal streaming engine.
I think I know what is going on here..

This device has issues with the radio and handoffs in particular do not work well especially when going from LTE to CDMA/eHRPD.

The internal streaming engine in particular seems to get stuck in a 'connecting' phase when it tries to reconnect.
When you look at dmesg you see stuff like this:
"[MODEM_IF] LTE CRASHED!! LTE DUMP START!!"
Followed by attempts for it to restart the LTE radio and change to the CDMA radio.

I think this is a hardware issue.
After exchanging the device 3 times I finally got one that the LTE radio does not crash on but the handoff between LTE and CDMA is quite poor and often you lose data for over a minute or more before it hands off correctly.

The internal stream engine sits in a hung state for quite some time (over 10 minutes) and I have had to reboot the device to free it up.

There are probably issues in the RIL as well because surely there is some event that is sent when data drops, but I don't know enough about the internals of Android.

I don't know if this helps or not.

Edit: as a sidenote the leaked radios for this device do help with handoffs and data loss and the internal stream engine is not as prone to freezing up.

Also I do not recommend that anyone reading this attempt to root their device and install unofficial updates unless you are willing to accept the consequences of those actions.

Hey Mark, great stuff. Thanks! This might be another issue added to the Android 4.x.  I was using a XOOM WiFi tablet and this issue was seen with the disconnections when the screen shutdown.  In regards to the internal stream engine hung-up I will need to figure out a bit more to see if the sockets aren't timing out... which means Android is not making the sockets timeout properly and that would kinda suck...  In regards to having to restart your device could you just try long pressing the stop button?  This actually kills the streaming process, so it should clear out the entire resources being used by the internal stream engine.

I did not know about the long press on stop.
There is a particular location that I can cause this to happen so I will give it a shot.

As far as the sockets getting closed, no I don't think they are being closed properly in some cases. This is likely a framework issue or something goes wrong in the RIL.
They made a lot of RIL changes to properly support LTE so I would not be surprised if there is a problem in there someplace exacerbated by the bad handoffs from LTE to CDMA.

With the leaked radios on this device the situation is improved and I would imagine the reason this has not been sent out as an OTA to this device is because there are more issues they are working on.

is it possible to check the status of the thread that is hung in connect() and kill it?
I suspect that connect() is waiting for an error to be returned but the hardware layer is busy trying to figure itself out.
(yours is not the only application that I have seen hang like this)

I will try to pay special attention to it when it does this to see what it is actually saying on the screen during this hang. I could have sworn it says it's connecting and I know if you hit stop it tries to stop but never actually stops.

The issue still prevails for me on my SGN after the 4.04 upgrade *argh*

Have you tried the beta version see if issue still happens? I have tested on Motorola Xoom after 4.04 update and things are working now it seems... However I think Nexus phones have gotten worse with this 4.04 update.

The beta version on 4.0.4 is unfortunately a disaster.

:( Crash all the time? I got a new update with bunch crash fixes for today I hope...