Better the devil you know :(

[Anonymous]

Not particularly O2 related per se.... left O2 after many many years when iPhone 5 came out due to ongoing issues which didn't seem to be improving...

Went to EE (T-Mob at the time) and boy am i suffering buyers remorse ... 2 sim cards and 2 iPhone5's later (Apple replacements for probably working handsets) later and i'm still stuck with a service thats dropping all the time (Going no-service) and support tech's that are just saying 'Have you tried switching it off and on?'

My number is stuck with T-Mob for 12 months now .... grass isn't as green elsewhere as it seems 😞

[perksie]

Oh dear sorry to hear that but thanks for letting us know.

Have you tried getting an Apple store to check things for you?

[Liquid]

Sorry to hear that:(

[Anonymous]

Tried all these:
1. Updated to iOS6.0.1
2. Replaced iP5 by Apple (despite them saying the handset was fine - thanks for that one)
3. Replaced Nano Sim by T-Mob (they credited my account the £10 fee at least)
4. Setup phone as new (restore sw without backup) meaning inconveinice to me as i had to set everything back up and i lost some data inevitably
5. Contacted T-Mob support several times and been told to:
a. Network Settings Reset
b. All settings reset
c. Network reprovisioning on Sim

Right now i'm getting 0.12 mbit speeds and crappy call quality .... using an iPhone5 with that speed isn't great

And to think i gave up my o2 unlimited iPhone simplicity tariff for this

[Liquid]

How long have you been with them for?

[Anonymous]

To long for 'cooling off'
Just coming up on 2 months ... stupidly i waited for iOS6.0.1 thinking it might be an Apple bug/issue

[Liquid]

😞 dang.

I wonder if you could claim breech of contract due to the inability of actually using the contract your paying for.

[jonsie]

I would get the phone checked out at your nearest Apple store. Sorry you're having problems with the new network.

[Anonymous]

@jonsie: I did ... it was a problem on my original iP5, i went to apple, they said the phone was fine but they replaced it anyway
Same issue on replacement

[Anonymous]

Is it anything on t-mobiles side that may be at fault