The title of this post is admittedly a little cryptic but let me go into scenario mode for you and try explaining what this bug is and how it happens.
Imagine dropping your iPhone and smashing the screen, already it’s one of the most annoying things in the world but then you realise that you need to pay between £55 and £65 to replace the screen via a repair centre unless you do it yourself and order the screen and tools from eBay costing around £20.
Of course you decide to take the cheaper option knowing that times are hard and if you don’t then the hamster goes without food for the month.
You remove the screen and battery then replace it all thinking everything is fine and you power on and make a call only to realise that when that call is done you can’t hang up or the phone shows searching for network even though you have full signal.
Oops, something has gone wrong!
So what was it? Well, the iPhone, when it has the battery removed, has a tendency to reset its date to January 1st 1970 (which is way before the phone was ever considered obviously) and as a result it causes the above bugs to occur.
How do you fix it?
There are two ways, either hope that your network supports auto time and date update and the phone resets itself to reflect the correct date and time OR manually set the date and time (a reboot may still be required).
It’s worth pointing out that we know this to be the case on iPhone 3GS, 4 and 4S, it hasn’t been tested on the iPhone 5 as yet.
If someone wants to set their date and time to January 1st 1970 and test the call functions then please let us know the the outcome, we’d be very interested to hear the results.
Thanks to our very own handset technician Chris Summerfield for pointing us to this bug.
Update: Thanks to our Twitter follower @CarlWoodfin we can reveal that the date change has the following effects on the iPhone 5
iPhone 5, it kills call functions, iMessage doesn’t send, goes to text, mail servers cannot identify…