Because
this seemingly-inocuous patch (which postdates Android 1.5, and thus fixes a bug affecting several of the earlier Android phones) reveals an alarming mess.
Before that patch, making an emergency call on some networks (e.g.
Rogers in Canada, and T-Mobile in the USA) would cause a system service to throw a NullPointerException, and the phone
(
Read more... )
Comments 7
Reply
Reply
Reply
About the only thing I can think of to say in mitigation is that emergency calls are just about the only code path you can't reasonably test on a real network: what do you say to the emergency operator, "sorry, just testing a new mobile phone"?
But surely someone in Google has a dummy base station and some magic SIM cards that use it?
Reply
Reply
Unreferenced footnote: '*'
But, yes, that is a bug so critical that it should never have made it through testing - a real show-stopper. It's not the first one, either - remember the hidden root terminal permanently bound to the keypad?
I'm inclined to say that this is because Android is open source (amplified by the culture inside Google). Testing, particularly certification testing, is incredibly dull. It's not what 'real programmers' do. And, like usable documentation and user interface design, it most certainly doesn't get done if you leave it up to people to choose their own tasks.
Reply
Reply
Leave a comment