I bought a HTC Sensation 4G in the US, bundled with a T-Mobile USA contract, of course. Now I'm visiting a friend in Germany - she has a HTC Sensation 4G as well, with a German T-Mobile contract. A few days ago she received her Android 4.0 / ICS update for her German phone. Wow! I thought, let's see if I'll receive the upgrade as well.
At this time, I was still in Germany but had my Sensation equipped with a German T-Mobile prepaid SIM card (so I don't have to use roaming) - hm, "Check Update" did not show anything and I'm still on Android 2.3.4.
I inserted her German SIM card into my US phone - but this did not work at all, my phone was somehow locked with her SIM card in my US phone and I could not use "check for update".
Then I inserted my US SIM card (the one with my T-Mobile USA contract) into my US phone (while still being in Germany), activated "Mobile Network" (I guess data roaming fees would apply now) and checked again for any HTC updates - but still no luck.
Now I'm wondering why my phone does not receive the same ICS update as my friend's phone. Or, more precisely: how does "check for update" know where to look for a system update and what would have to be done (in theory) to convince "check for update" to think it's a normal German phone so that it'll receive the same update to ICS as my friend's phone?
One more detail: the bootloader from my US phone is unlocked and I have enabled root access too. Could this be a reason for "check for update" to not present any updates any more until these two things are reverted?
Well has nothing to do really with where it checks or where you are but what hardware it is. While yes, by name these are the same phones they are different hardware / software versions made.
You will not get the update for that phone until released for that specific model.
Also if you are unlocked bootloader and root access but stock rom and recovery you should still get updates to the phone.
Remember that the T-Mobile Sensation has some T-Mo specific features in the ROM, namely wifi calling (as well as bloatware). Supposedly HTC sent an update to T-Mobile, who was not satisfied with it (don't know if it had bugs, or just wasn't as smooth as it should be) and they sent it back. While the delay may be frustrating, it's much less so than a buggy update.
Thanks for the speedy reply, theartiszan. To be honest, I was suspecting something like this (different hardware models selling under the same name), but thanks for confirming that. Also good to know that tampering with the bootloader won't hinder any update mechanisms. The ROM is still a stock T-Mobile ROM.
@jaylanphnx: true, a buggy update might be even more frustrating.
Sorry for the confusion regarding the ICS update. Both theartiszan and jaylanphnx provided some great info for you here, but if you'd like to discuss the update more, you can post in the main ICS thread which I've linked below.
Software update (the Sensation ICS thread)
Retrieving data ...