I have generated the same bug as explained above using uuz3’s directions, but it does not happen every single time…

I tried a LOT, perhaps it’s harder with 4.7 Beta2 because the HUD fades out much quicker…?

Honestly, I don’t think I’ve experienced it after upgrading to Beta 2…

Is anyone using Beta 2 still experiencing the issue?

I’m on a 3GS, so does that make it less likely to happen than a standard 3G?

Yeah I used to be able to recreate it the same way but I just tried like a hundred times with beta2 and no dead spot so ltes hope its fixed

I used to get the untouchable area via the “HUD” area before I’d say 4.6 beta. I haven’t noticed the problem really in any 4.7 version.

I’ve tried multiple times to reproduce it and it hasn’t done it. Hope it’s fixed!

I’ve benn able to recreate it. But it’s very random when it happens and i’m not sure what the exact steps are. But if you do the method mentioned above. But also bring up QC in springboard and lock the phone, when you then unlock you’ll have to press home button twice for the QC window to disappear. Try doing these two multiple times and you might get it.

This happens to me every single time if you press the volume up/down button, and then immediately lock the phone. Once you unlock the entire HUD area is unresponsive to touch. The only way to fix it is to repress the Volume up/down button and let it fade away completely (or press the hud to invoke QC). After doing so it’ll return back to normal.

Do you guys also have the bug where sometimes when an incoming call comes, and you try to slide the “Slider to answer” bar and it just refuses to reach the end?

Haven’t experience that yet. Are you having that difficulty while a QC/QR window is open? Or does it just simply happen regardless of the circumstances?

Happens regardless of circumstances… Usually phone is in standby. I don’t have lockscreen stuff enabled though…

@Blightfire

I had that on my 2g. And know several people with or without jb that got it as well. When it happened I usually had to slide to answer maybe 20-30 times really fast before it did anything.

Hasn’t happened at all on my 3gs. 2g was on 3.0, 3gs 3.1.2. Not sure that has anything to so with it though.

I had it on my 3G (3.0 to 3.12) and now still have it on my 3GS (3.12). I really don’t know what causes it. Just curious if anyone managed to figure it out.

I started noticing it in the last week or so. Happened twice but cannot say if it was with B1 or B2 as I was not really paying attention to what caused it. Frustrating though as the dead spot just happens to be at exactly the same spot as the respring button of sbsettings, forcing me to do a full reboot. Will try the volume hud fix that mreakus suggests above if and when it happens next.

Dv. Move winterboard out of the dead spot so if it happens again you can use winterboard to respring. :)

When that happens I press power in sbsettings, safe mode, restart. You just have to press the edge of the safe mode button, as the center is dead. Is that ok? My phone is tethered btw, that’s why I don’t restart the phone.

Found a way to make it happen 100% for me. Locking the phone after pressing volume up/down does not work for me. But if I lock it as soon as the volume HUD starts fading then I will get it.

I think it has something to do with that when the HUD stars fading the HUD area will be inactive to touch. Try opening a app that’s behind the HUD when it stars fading. It won’t open the app and it won’t open QC either.

Disable QC and you can press things behind the HUD. So by locking your phone with a fading HUD with QC enabled you will get a inactive/dead area.

Have tried it on both a 3gs and a 2g running 3.1.2 bitesms 4.6 and 4.7 beta 2.

^yep thats whe way, I guess I must have just done that by accident b4 when recreating it my way. Works everytime when done that way now to get it solved :)

Exellent :). It just happened to me a couple of minutes ago and I remembered the thing with that you can’t touch behind the Hud with QC enabled and thought maybe that’s the reason. Hopefully it’s an easy fix.

urMiNE90, top man, thanks, we’ll fix it!!!

Great! :)

It’s fixed in Release 4.7 Beta3.