11-22-2010 12:38 PM
01-11-2011 07:31 AM
I have been having the same problem. My only self diagnosed solution is to clean the screen. It appears that over time persperation plays havoc with the sensor screen. It seems to solve the problem for me.
01-12-2011 02:09 AM
Without more details it would be well nigh impossible to assist you. What OS and platform are you using, what carrier are you with, what applications (generally it would be the third party and add-on that would be problematic) are you running.
There are simply too many variables to try a shotgun approach.
There is one common thread through this problem "Storm2"!!!
I've deleted all the 3rd party app and even removed some of the RIM functions but still my 9520 hangs!
02-23-2011 12:19 PM
08-15-2013 07:33 AM
Anyone Please help me. I have the same problem
Blackberry - 9520 v188.8.131.520(Platform 184.108.40.206).
When ever i make a call i cannot end the call until removing the battery. Sometime my screen unable to press.
This is very hactic.. Can anyone having the same issue. Please reply me.
Also i update the Blackberry desktop manager it doesn't help.
08-15-2013 07:48 AM
I'm having issues with my Storm 2 9520 - Touch Screen freezing after making call unable to end the call or unable to dial other number until i remove the battery and restart again. This is very hactic. In case of some emergency call.... Can any help me how to solve this issue.
08-15-2013 10:23 AM
Hi and Welcome to the Community!
I recommend that you attempt to boot into Safe Mode:
It may take you multiple attempts to get the ESC key sequence (press/release/hold) correct, so be patient. When successfully into Safe Mode, see what happens.
If the behavior ceases, then think carefully...what happened just before this behavior started? A new app? An update? A Theme? Something else? Think carefully as the smallest change could be causal...and attempt to undo whatever that was.
But if the behavior continues in Safe Mode, then you may need to consider more drastic actions -- WIPE, OS Reload, BBSAK Wipe/Reload, and the "Bare Bones" OS Reload Process. To prepare, you should be sure that you have a full backup to your PC...please review the Backup link in my auto-sig on this post for instructions.
Once you have a full backup, then you are ready to proceed...
Please refer to this official download portal as you proceed. It is sorted first by carrier -- so if all you want are the OS levels your carrier supports, your search will be quick. However, some carriers are much slower than others to release updates. To truly seek out the most up-to-date OS package for your BB, you must dig through and find all carriers that support your specific model BB, and then compare the OS levels that they support.
From a PC, you can install any compatible (e.g., for your exact BB Model Number) OS package to a BB via this procedure:
Note that while written for "reload" and the Storm, it can be used to upgrade, downgrade, or reload any BB device model -- it all depends on the OS package you download and install to your PC. After installing the OS package to your PC, please remeber to delete, on your PC, all copies of VENDOR.XML...there will be at least one, and perhaps 2, and they will be located in or similarly to (it changes based on your Windows version) these folders:
Be sure that you remove, from your PC, any other BB device OS packages as having more than one installed to the PC can cause conflicts with this procedure.
You may also want to investigate the use of BBSAK (bbsak.org) to perform the wipe it is capable of.
You may also want to try the "Bare Bones OS Reload Procedure" to attempt to narrow down the precise causal item:
When the behavior presents, you know the culprit...the last thing you loaded.
If the behavior does not re-present, then you know that either step 1 or 2 cured it.
If the behavior presents no matter what, then you likely have a hardware level issue for which no amount of OS or software can cure.
You may also need the use of these tricks:
If you are on MAC, you are limited to only your carriers sanctioned OS packages...but can still use any levels that they currently sanction. See this procedure:
Good luck and let us know!