So yeah, Google totally just won the conference showdown by easily beating both Apple and Microsoft. Not only did Google announce Android 4.1 with some really cool new features, a cheap but non-crippled tablet, and a new Android device called the Nexus Q, but they also opened up pre-orders for Google Glass. So yeah.

Resume from sleep WiFi is less than five seconds. You are seriously an outlier there. Contact your carrier or get your device serviced. This just isn't happening on a widespread scale.

Your second issue is also peculiar and I've found no mention of it across the internet on a large scale. These may be isolated incidents, and again I'd suggest contacting your carrier and having your device checked. It is likely this and the prior issue are related.

Live Tiles is multifaceted. Some Live Tile data is pushed, thats instant. Some developers opt to not pay money to run push notification service so they periodically poll for Live Tile data which at best fires every 15 minutes.

All push notifications, background tasks, etc are disabled during low battery or low memory conditions. So it may impact how often you have fresh tile data.

Some developers just plain don't implement the functionality correctly which can cause duplicate notifications, old notifications, incorrect clearing of live tile badge counts, etc.

The only time any of net stuff impacts perf is if you're doing on UI thread data handling or image decoding which is bad practices and fault lies with the app developer. Setting Images to Delay and Background creation, as well as using an HttpWebRquest object or marshaling your WebClient fixes this

Your second issue is also peculiar and I've found no mention of it across the internet on a large scale. These may be isolated incidents, and again I'd suggest contacting your carrier and having your device checked. It is likely this and the prior issue are related.

That second issue was written by me, and I've since narrowed it down to a Sprint thing. Specifically, even though I have what appears to be a good signal at my house, the data part of the signal is simply too weak. It affects text messaging as well as EvDO data. At the same time, I found that my wireless router wasn't propagating to the side of the house where my office is, and the HTC Arrive seems to be really picky about staying connected to a weak WiFi signal. Moving within range of the router, or going across the yard for a better EvDO signal fixed my connection issues.

Further proof was discovered at work, where we have a femtocell (or whatever Sprint calls their repeaters) to better serve our officers who rely on their work phones in the building. I never have communication issues at work apart from Netflix streaming, which suffers from the femtocell being prioritized for voice over data.