OnePlus Issues OxygenOS 4.5.6 Hotfix Update to Fix Reboot When Calling 911
We use our phones for a lot of things, and every once in a while, we use our phones as, well, phones. Most people probably hope they’re never in a situation where they need to call an emergency number, but if you ever are, you’d expect your phone to call it without any issues.
Yesterday, a user on Reddit reported that when trying to call 911 on his OnePlus 5, the phone would start to make the call but then begin to reboot itself. Shortly after this initial report was made, several other users commented on the original Reddit post to say that they were experiencing similar issues.
The issue also gained traction on the Android subreddit, where other users chimed in claiming the same issue on other devices as well. Reported devices ranged from the Verizon Galaxy S7 Edge to the Motorola G5. To complicate matters, the issue could not be consistently replicated on most devices, including on the OnePlus 5. So mileage varied by a large margin, which should never be the case with something as important as an emergency call.
9to5Google reached out to OnePlus specifically, following all of this, and the company responded by saying that it has “been in touch with the customer and have tested a software update that has resolved the issue.” It is suspected that the reboot issue is a result of the OnePlus 5 sending your location information when calling either 911 in the US or 999 in the UK, but OnePlus has yet to confirm whether or not this is the case. Speculation in the Android subreddit points to this being an issue in AOSP itself because of its random occurrence across devices, but OnePlus seems to be the only one who is pushing out an update to fix this, or that has publicly addressed the issue for that matter.
OnePlus has begun rolling out a hotfix update for the OnePlus 5. The OxygenOS 4.5.6 hotfix update specifically targets the 911-reboot issue and users so far have been reporting success on the patch on the OnePlus 5. Nonetheless, with how randomly the problem has been occurring in other devices, one can only hope to never run into this issue especially at a time where you really need your phone to function.
We hope other OEMs also acknowledge the existence of this issue (if reports we’ve seen so far are valid) and work towards rolling out a fix at the earliest keeping in mind its rather serious nature.