[Following provided by Javier Flores Assad, AKA MTTF Dude]
Hopper, as a random UI stress tool, can cause some real world problems like dialing emergency numbers … well as some OEMs have been asking for a solution of the hopper emergency calling scenario we have created a solution with an override mechanism available for OEMs.
Three new files are available at jetstream: dialrequest.dll, noemesetup.exe and restoreEME.lnk; these two binaries will make your runs safe of dialing emergency numbers.
[Warning: The override will block emergency calling; please don’t apply it on a device that is not intended to be used for hopper testing. If you apply the override your will be unable to make emergency calls until you remove the override as explained in this document]
Steps to apply the override
Steps to remove the override
[Another option would be to wipe your device by reflashing it or by cleaning its registry]
OEMs can create their own dial-request override if needed?
Yes, there is a public override mechanism that allows OEMs to be asked if a dial request should proceed or should be blocked. This mechanism is called: PreprocessDialRequest and is fully documented for OEMs to use in (public\ossvcs\oak\inc\dpext.h).
For more information regarding technical information about this override functionality, please refer to public\ossvcs\oak\inc\dpext.h.
Could you share your idea of this requirement?