• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Random unresponsive screen after JB?

I have tried all the suggestions in this thread and I am still having the problem of the screen going unresponsive. I called Samsung and talked with a tech who says he hasn't heard of the issue with the Reverb and 4.1.2 and as expected could only offer flow chart suggestions on how to fix the issue.

I wanted to ask others here if they are running their phone encrypted or not. I don't want to do the hard reset again if that isn't a common thread among other users here.

Thanks for any help you can offer

JP
 
jaypet said:
I have tried all the suggestions in this thread and I am still having the problem of the screen going unresponsive. I called Samsung and talked with a tech who says he hasn't heard of the issue with the Reverb and 4.1.2 and as expected could only offer flow chart suggestions on how to fix the issue.

I wanted to ask others here if they are running their phone encrypted or not. I don't want to do the hard reset again if that isn't a common thread among other users here.

Thanks for any help you can offer

JP
Click to expand...
I'm not running encryption and I've still got the problem once or twice a day. At this point, I'll probably learn to live with it until the phone kicks the bucket completely. I have Google Now disabled, but the problem still occurs. Also have disabled hotword detection in the google search preferences. Still got a frozen lock screen not long after.
I suppose disabling the lock screen as mentioned by sheureka could be worth a try. But the lock screen probably does keep me from dialing random numbers, etc...
 
I actually decided to go back to ICS. The problem with gps lock and the random unresponsive screen was just too much. I liked JB otherwise.
 
Hey Madmikess, How did it work out? I'd like to follow your lead and go back to ICS. Would you be kind enough to break down the steps (which rom, etc.) you used?
 
I am also experiencing the super annoying unresponsive screen issue after upgrading my Galaxy Reverb to Jelly Bean. I contacted Virgin Mobile technical support today and all they had to say was "we are aware of the issues with the upgrade and we are working on a fix..." blah blah blah.

Does anyone have a clue what could be causing the phone to lock-up? All of the suggestions in this forum (and other sources online) do not seem to resolve this issue at all.

Since it is software related, could it be one of the new Google services (like Google Now) or possibly Mobile ID or even TouchWiz?
 
As of Monday night, I've added a couple more changes that seem to have helped. No freezing Tuesday or Wednesday (phone had frozen 2-3 times Monday during the day). And apps are working better.
Overall, as someone above mentioned, it would appear the single core (or overall lack of processing power) of this phone doesn't lend it to handling some of jelly bean's features.
I had already tried everything above: 1) Nova launcher may have helped a wee bit. 2) Disabling Google Now (I never activated it, and checked to make sure it was off). 3) Turning off hotword detection: not sure if that helped.

New attempts:
Google Music -- always running in the background since the jelly bean update. Also, since the update made this app run terribly, I force quit it, uninstalled its updates, and disabled the app. Seems to have helped some.

Using Live Wallpaper -- On a Galaxy Nexus forum (sure, many steps above a Reverb), some users had indicated that using a live wallpaper could improve smoothness. So I tried it, for the Homescreen and Lock Screen. Seems to have helped as well. I have no idea why, seems counterintuitive.

Also, in general, clearing the RAM with the task manager obsessively likely helped too.

That's all folks. Let me know what you think. Any other tips out there?
 
I disabled swiftkey and used the default touchwiz and that didn't change anything. Installed the recently released Google default jellybean keyboard and haven't had an issue for over 3 days. Previously I was getting at least two screen freezeups / day.
 
I also have been getting multiple freezes at the lockscreen when I received texts after updating to 4.1.2. At first I disabled sounds, not sure why other than I thought the mp3 might be an issue. Didn't help. Then I removed the check from the preview text option in the notification bar. Nothing. Then I remembered that I turned on google now, so I disabled that. Seemed ok for a day, phone more responsive, then freezing came back again. Got on here and found a couple things to try, nothing seemed to work. I was already using Nova, so I thought maybe it was the stock lockscreen. I installed Go locker. Seemed to help for a day, then more freezes at the lockscreen. So I turned off the lockscreen altogether (think I saw that here too), which seemed to help for a day, then more freezes and power button rebooting. Found the hotword detection "fix" - but back to frozen lockscreen after a short time.
So what I'm left with is someone mentioned they disabled swiftkey, so I downloaded the jelly bean keyboard and stopped using swiftkey (which I paid for). So far, have not had the screen lock up on my phone in over a day and the phone seems a little more responsive. I have re-enabled notif sounds and also the stock samsung lock screen. There has to be something going on with Swiftkey and this phone/ android 4.1.2 - which sucks. Anyone still having issues after trying everything else - are you using Swiftkey?
and no sooner did I post this that my phone has locked up - again! at wits end, anyone have any idea what the deal is?
 
I think there were actually two things that stopped my lockup (and I haven't had one in more than a week). One was unchecking "Hotword Detection" and the other was hibernating almost everything with Greenify. The only problem is you have to be rooted to use Greenify (but it's worth it for that app alone). Hope this helps someone.
 
I'd like to report that I haven't had a single lock up for a week now...the only thing I did was disable the lock screen completely (even swipe to unlock).

Also, I know some people have suggested SwiftKey is causing problems, but I have been using SwiftKey (paid version) all along and so far no freezing.

I am starting to believe it is the lock screen that is fundamentally broken in Jelly Bean. Do others have the lock screen enabled? I would like to see a fix for this soon, but I'm not holding my breath... ;)
 
I called VM last night and I told them about this problem. They were going to send me back the same phone, but I told them it was a common problem and that I dont want the same phone back. After complaining for a couple hours they gave me a $55 credit to any new phone and I get to keep the old one. So i bought the Victory because it was already on sale.
 
kfisher said:
Yes, and I want to throw it out the window!!!!
Click to expand...

Call VM and complain, but ask to speak to a technical supervisor. Tell them your problem. This is the only way they will realize that there is a MAJOR bug, that is ruining the customers experience
 
I saw a fix on YouTube. Go to Google Search / Settings / Voice and deselect Hotword detection. Apparently the Hotword Detection works at the lock screen and is causing the phone to freeze and use extra memory. I just tried the fix because my phone has been freezing at least twice a day. I'll post again next week if the fix worked.
 
So I've noticed that during long phone conversations (such as waiting on hold) my screen will become unresponsive. However, the phone behaves as if it's still on, because if I push the power button it will hang up rather than turn the screen on.

1. Has anyone else experienced this?

2. Does anyone know how I can set my phone to force the screen to stay on continuously during phone calls?
 
I have been experiencing this problem since updating to jb and using all the hotfixes posted so far in this thread. I am going to flash stock ICS again when I have the time. The reverb is much, much more responsive with stock ICS.

I believe that the unresponsiveness of the reverb on jb is due to 3 main things: drivers for the hardware, lack of sufficient RAM (mine is only showing 585mb, that is barely enough to run jb basic features and services let alone background cache processes), and the fact that this is a single-core powered phone so it just doesn't have the adequate processing power for the background cache processes & services either.

If there was a few custom ROMs for the reverb, I believe that the phone's full potential could be utilized. Don't see much of a chance on that happening.

I will post again when I revert back to stock ICS and experiment. I really believe this is mostly due to insufficient RAM. I expect stock ICS will use a bit less but we will see.
 
I'm experiencing the same issues since upgrading to JB so I'm tempted to go back to ICS also. The phone was much more responsive on ICS.

The problem is I really like having Google Now so I'd like to find a way to get that on ICS.

There are some custom ROM's showing up on the All Things Root forum that I'd like to look into as an option too.
 
I moved to the Partytime ROM found on this forum, and it is 100x better than Jellybean. The only problem I'm having on the new ROM is getting a GPS lock.

No screen unresponsiveness of any kind though! and that was the biggest issue for me before. The Partytime ROM is a lot more fluid and responsive than Jellybean.
 
I have had the same problem but I also have a gps problem where it always says searching for gps and cannot find gps is that just me.
 
You must log in or register to reply here.
Back
Top Bottom