Desire Android 2.2 T-Mobile branded ROM no task killers installed This problem happens intermittently. When I get a text message, I take the phone out of standby, write a reply, send it, but it won't send. I then notice that (usually) H has been enabled by Juice Defender, as usual, but rather than connecting and syncing as usual, it seems to connect OK for a couple of seconds, but then gets stuck with only the up arrow highlighted. (The Mobile toggle switch appears as if it's connected.) Whilst this is happening, I can't send or receive text messages, make or receive calls, or use data, although Wifi still works. If I disable Mobile with the toggle widget, it doesn't make any difference at all, it still sits there trying to connect. It'll sit there for minutes at a time like that (not sure how long, I always get bored watching). Solving the problem is simple: just enable Airplane and disable it again. Everything resets. This is still a pain in the bum though and I shouldn't have to do this. My wife lives in my flat and her Desire is also on T-Mobile, although with stock unbranded ROM, and she also uses Juice Defender, and has never experienced (or never noticed) this issue. It happens with Juice Defender disabled and Mobile set always-on. It happens in every location in the UK, so it's not transmitter-specific. It has occasionally happened randomly whilst I'm sat using the internet, but not as often, so I wonder if it's a general reconnection failure problem, e.g. when switching between H and G. I can't say for sure whether I've ever noticed it happening on anything other than H. T-Mobile have been no help whatsoever, offering to send my phone off for repair (up to two weeks without a handset) but they've not offered to send me a new SIM, I can't see how that would be the problem anyway. I've checked a couple of settings mentioned in this thread but to no avail I've not tried calling HTC yet - I suspect they won't have a clue. I am planning to root my Desire at some point so I'll soon discover whether or not it's the T-Mobile ROM that's to blame (my wife's using the latest unbranded ROM) Anyone else experienced this?