Razer Phone 1 Dead Zone | Razer Insider

Razer Phone 1 Dead Zone

  • 23 January 2019
  • 2 replies
  • 17 views

To the community

First post so bare with me on this. Had the Razer Phone 1 for a little while and it's out of warranty. This phone has been looked after since purchase, no falls, software tweaks, water damage or back pocket pressure. It's had an official case since ownership and has worked flawlessly since Oct 18. Last week the top section of the screen became unresponsive, not completely but enough to be unuseable. Can't answer calls, change WiFi unless double swipe to bring the icons out of that zone. Looked online and can see this issue is common and not isolated indicating a manafacturing issue. Hardware not software issue! Or, could it be a software issue? Bring the question to the masses and interested to see if this issue is broad and if it potentially could be a software issue with a fix. As stated above, it worked and then didnt, simple as that, no reason at all. Thanks guys for any responses.

This topic has been closed for comments

2 Replies

Try to do a hard reset on your phone first. Simultaneously press and hold the Power Button and the Volume Up button for 7-10 seconds. The Phone should reboot automatically. Once the reboot is successful, try to test the phone if the issue still occurs. If so, please send me a PM together with the serial number of your Razer Phone. Let's continue from there.
I do
technoRedPigmentvoice394
To the community

First post so bare with me on this. Had the Razer Phone 1 for a little while and it's out of warranty. This phone has been looked after since purchase, no falls, software tweaks, water damage or back pocket pressure. It's had an official case since ownership and has worked flawlessly since Oct 18. Last week the top section of the screen became unresponsive, not completely but enough to be unuseable. Can't answer calls, change WiFi unless double swipe to bring the icons out of that zone. Looked online and can see this issue is common and not isolated indicating a manafacturing issue. Hardware not software issue! Or, could it be a software issue? Bring the question to the masses and interested to see if this issue is broad and if it potentially could be a software issue with a fix. As stated above, it worked and then didnt, simple as that, no reason at all. Thanks guys for any responses.


I do had the same problem!