S3 on Orange, a spot of bother with the whole EE thing....

[Galaxynote_guy]

A friend on Orange with an S3 recieved a text last week telling her all about the wonders of the up and coming EE service and that she should turn her phone off and on so that her phone could be configured to take advantage of the service. This she duly did and now she cannot access the internet at all unless on a Wi-Fi basis.
The notifications bar shows full 3G signal but there is nothing...
Any ideas a) What was that text all about, it's not an LTE version and b) Anyone else affected?

 

[D-U-R-X]

A friend on Orange with an S3 recieved a text last week telling her all about the wonders of the up and coming EE service and that she should turn her phone off and on so that her phone could be configured to take advantage of the service. This she duly did and now she cannot access the internet at all unless on a Wi-Fi basis.
The notifications bar shows full 3G signal but there is nothing...
Any ideas a) What was that text all about, it's not an LTE version and b) Anyone else affected?

Both me and my wife have had the text and neither of us have had this issue.

dnapro should be able to offer some insight though

 

[Galaxynote_guy]

....again, I shall bait my breath and wait

 

[D-U-R-X]

I'm sure he'll get to it when he has chance

 

[dnapro]

Hi, only just finished work, I'm on my crappy late finish week!

The issue isn't related to the update which changes your network name on the phone, the only thing that the OMU contanined was a marker to change what name is displayed on the screen. You are still using the Orange/T-Mobile network which you have been using since the network sharing went live. Nothing changes until 4G launches and thats only if you have a 4G phone.

We have had very few customers facing issues after the OMU's and we are dealing with all issues regards faults as normal, If your friend hasn't sorted it yet please ask them to call us and we'll run a standard full diagnostic and fix the problem. It is co-incidental I agree but the issue has nothing to do with the update