official O2 Eclair - problems with swipe to unlock

[Guest miker71]

I've noticed this seems to have gotten worse over time (I rarely reboot my phone):

Swiping to unlock gets a bit fussy, leading to miss calls or (right now) inability to get to my phone without the removing the battery first.

Same thing happens with WidgetLocker (though there you can assign unlock to the back key and such, so not so bad)

Don't think there's a problem with my screen because once the damned thing is unlocked everything is fine and immediately afterwards so is unlocking.

This problem only seems to manifest after some time with the phone asleep. I don't remember seeing this on donut or beta eclair but then I didn't keep them installed for long ...

I've done a screen calibration, made no difference.

Want to avoid another wipe of the device because that gets old real quick (what is this, Microsoft?! ;-) ) - but I guess if no one else is seeing this behaviour then a factory default it is.

[Guest Mirrdhyn]

I had this behavior on 2.1 beta.

I had also this behavior to answer a call.

So I think that is a bug on a swipe unlock.

[Guest Loconinja]

I don't like swipe to unlock. I preferred the 1.6 method of pressing the Home key. Is there any way to change it?

[Guest spences10]

I had this issue, screen calibration worked out ok for me

it's still a bit flaky but much better than it was

go to fastboot [power off device> turn on holding camera button+power]

select screen calibration> for me i tapped it and nothing happened, tapped it again, and again eventually it came up with something like calibration complete or complete

all you can do is give it a go, if it dosent work your options are either go back to 1.6 or wait for a custom rom to be released :lol:

[Guest DeathOfAllThings]

If you're talking about the problem where you go to slide the unlock and it just moves a little bit and then snaps back over and over again, I've had this problem. I've used a little trick to unlock it... you need two fingers though, so it's a bit annoying. Basically touch the unlock icon and hold it down, then with another finger, press the area to the right of it where the end of your swipe normally would be, then lift your first finger that was touching the unlock icon. It pretty much just tricks the phone into thinking you've swiped all the way over. Strangely enough, I had this problem for awhile... then it mysteriously went away, not sure why, I've made no changes to the phone.

Edited September 21, 2010 by DeathOfAllThings

[Guest RedSlug]

Just to say I also get this problem occasionally.

Quite annoying

2.1 official O2 release.

[Guest jamezwarner]

Same issue here - it'll often stop drawing at the first dot, multiple tries and waits - then it'll just magically work. There's definitely a bug...

James

[Guest miker71]

I don't like swipe to unlock. I preferred the 1.6 method of pressing the Home key. Is there any way to change it?

if you're rooted there's a Market App to disable the lock screen completely - I'd be paranoid about it waking in my pocket and doing weird stuff.

i've settled with WidgetLocker for now which allows you to customise, by default you don't have to slide, it also allows you to press the back key. it doesn't replace the slider for incoming calls though, so won't address that (AFAIK)

anyway, glad it's not just me seeing this issue :-)

[Guest MikeF74]

This has been driving me nuts the last 5 days or so. It started happening a few days after applying the modified build.prop (for hardware OS GUI acceleration and higher density LCD). But, I can't say with any certainty it had anything to do with it because I've also installed and updated a dozen or so apps since then (including Universal Androot to help deliver the build.prop).

What is odd is that even though the slide-to-unlock won't register a press, 8 out of 10 times I can grab the Slide-To-Silence-Ringer slider.

It's difficult to diagnose because when you re-lock the device, it takes a while for the behavior to start up again. I've been trying to kill active programs and locking the device and waiting several minutes, but I've not quite been able to narrow it down to a specific 3rd-part app yet (I really hope it's not an OS glitch).

-Mike

Edited September 21, 2010 by MikeF74

[Guest spences10]

I had this issue before the performance hacks were implamented

Since i used the calibration tool in fastboot i havent really had any issues, i htink it has happened once or twice over the past 4 days or so and then i just pulled the mute slider down first then the unlock slider worked ok- when it was happening all the time i found that turning the screen off again then holding it an landscape mode seemed to help

IMO deffo seems to be a system bug

[Guest miker71]

This has been driving me nuts the last 5 days or so. It started happening a few days after applying the modified build.prop (for hardware OS GUI acceleration and higher density LCD). But, I can't say with any certainty it had anything to do with it because I've also installed and updated a dozen or so apps since then (including Universal Androot to help deliver the build.prop).

What is odd is that even though the slide-to-unlock won't register a press, 8 out of 10 times I can grab the Slide-To-Silence-Ringer slider.

It's difficult to diagnose because when you re-lock the device, it takes a while for the behavior to start up again. I've been trying to kill active programs and locking the device and waiting several minutes, but I've not quite been able to narrow it down to a specific 3rd-part app yet (I really hope it's not an OS glitch).

-Mike

Good point about the Slide-to-Silence - that indeed is easier to grab most times.

I've also got the modified build.prop, but my Streak was doing this before it was updated.

I used a Modaco Kitchen version of the ROM, so pre-rooted etc

I don't know if it exhibits the same behaviour on a non-rooted non-modaco ROM (so I guess I lied when I said I'm running official O2 - it's official O2 + modaco)

Like I say, WidgetLocker gives me a workaround and I'd rather save my next factory wipe for a significant update like, say, Froyo ... or Cyanogen (always the dreamer, me!)

[Guest zoidster]

I am finding it all a bit strange TBH

I have run all the builds of 2.1 , never had a problem until the last few days , I cannot explain why , I certainly haven't introduced a new piece of software or anything that I wasn't using before - all started sunday (running 6941 (I think ? ) )

Got a call , and was completely unable to answer or get the phone to respond in any way - I ended up taking the battery out .

Booted the phone again , and dialed the number of the caller (it was actually a very impartant call !) ... went through to voicemail , but when I went to hang up , again , totally unresponsive (grrrrr !) I left a voicemail message of " grrr ,oh FFS whats wrong with this thing !?" :lol: followed by the clattering of me dropping the battery out AGAIN !!

I decided this may be remedied by flashing back to the official 2.1 (8105 is it ? ) - which I had only removed a week or so ago , due to the menu lag , which was annoying , but not as annoying as missed calls !

I have notice that the keyboard becomes laggy from time to time , I'll be typing and all of a sudden the keyboard will stop responding , or will slow to the point that there is a two second gap between touching a key ,and it appearing on the screen.

Going to try a reset , then I'll seriously consider flashing back to 1.6

[Guest MikeF74]

Just wondering, did everyone start having this problem around the same time? I think I first noticed it on Saturday morning.

[Guest the_didge]

ive been having this problem since... well i think the 1.6 beta.

A screen calibration usually fixes it but it returns a few days later.

I find that if i wipe the screen (getting rid of all and every fingerprint and smudge) it makes it better.

My guess is that the physical design of the device is causing some sort of misalignment for the touch panel. what makes me think this is that it also happens within other programs, but always on the right hand side of the screen.

Anything with scrolling or select something on the last 1/4 of the screen seems to mis-press. my common most issue is with the call log under dialer.

will be sending in the device for repair soon as also experiencing speaker crackle at high volumes. Hopefully they can take a look at it.

[Guest johnh123]

Just wondering, did everyone start having this problem around the same time? I think I first noticed it on Saturday morning.

I had this problem on the o2 2.1. Took it back to stock AT&T, still had the problem. Had it replaced by Dell.

[Guest Phylar]

Yeah this has been happening to me alot. The other day I missed a call because it still wouldn't unlock after the 7th or so swipe - SOOO frustrating. I'll give the fastboot re-calibration a try. I'm really tempted to install No Lock at this point too. I bought WidgetLocker too and pressing home helps a ton, but doesn't solve the call issue.

Anyone know how No Lock works with calls? I'd hate to randomly answer and end incoming calls when my phone is in my pocket, which is what I think would happen.

[Guest zoidster]

Just wondering, did everyone start having this problem around the same time? I think I first noticed it on Saturday morning.

this is certainly the case for me , that's what I find strange ! strange that I had no previous problem , then since last weekend it appears to be a problem on whatever build I use . maybe just coincidence , but I can't help wondering if an app update has caused this ?

[Guest RedSlug]

I don't think its a calibration problem because if you use an LCD testing program directly after seeing the problem there is no problem. Its only on the unlocking screen.

[Guest zoidster]

This morning I was typing into the browser , when the text input slowed , then stopped completely , about 20 seconds later I got z's all over the place as if a key was stuck ! Pressing home took me back to the home screen , but the screen was unresponsive.

I let the screen time out , and then was left in a position where I could not unlock the screen ( I.e. Screen unresponsive ) so once again , took the battery out and everything is fine for now.

This suggests perhaps that my issue is a different one from the one the rest of you have ? I think if I have to drop the battery once more today I am going to roll back to 1.6 !

[Guest kibcom]

I'm on 2.1 unofficial and can say that the swipe unlock problem has happened now and again ever since the day it was made available so it's not a recent development.

I've only recalibrated twice, which fixed it when it first happened but now I just make sure the screen is wiped clean and my fingers are not too sweaty/sticky. Then it works great without problem.

[Guest MikeF74]

My swipe-to-unlock is back to normal. I did a handful of things, so any one of the following might have done the trick. Sorry I can't narrow it down more precisely.

Uninstalled Angry Birds (it had a recent update that may have coincided with onset of issues)

Uninstalled Paper Toss (it had a recent update that may have coincided with onset of issues)

Uninstalled SleepTimer ((it had a recent update that may have coincided with onset of issues, it also interacts with device sleep/wake)

Uninstalled Dolphin Browser HD beta

Removed Widget From Desktop: Wireless Signal Widget

Removed Widget From Desktop: Beautiful Home Weather (it had a recent update that may have coincided with onset of issues)

Removed Widget From Desktop: NY Times

[EDIT TO ADD: PLEASE DISREGARD THE FINDINGS IN THIS POSTING. THE PROBLEM PERSISTS FOR ME -- THESE UNINSTALLS / WIDGET REMOVALS DID NOT SOLVE ANYTHING]

Edited September 22, 2010 by MikeF74

[Guest zoidster]

My swipe-to-unlock is back to normal. I did a handful of things, so any one of the following might have done the trick. Sorry I can't narrow it down more precisely.

Uninstalled Angry Birds (it had a recent update that may have coincided with onset of issues)

Uninstalled Paper Toss (it had a recent update that may have coincided with onset of issues)

Uninstalled SleepTimer ((it had a recent update that may have coincided with onset of issues, it also interacts with device sleep/wake)

Uninstalled Dolphin Browser HD beta

Removed Widget From Desktop: Wireless Signal Widget

Removed Widget From Desktop: Beautiful Home Weather (it had a recent update that may have coincided with onset of issues)

Removed Widget From Desktop: NY Times

Of that list , I have Angry Birds , Dolphin Browser HD and Beautiful Home -

I'll try removing these three one at a time and see what happens

[Guest kibcom]

My swipe-to-unlock is back to normal. I did a handful of things, so any one of the following might have done the trick. Sorry I can't narrow it down more precisely.

Uninstalled Angry Birds (it had a recent update that may have coincided with onset of issues)

Uninstalled Paper Toss (it had a recent update that may have coincided with onset of issues)

Uninstalled SleepTimer ((it had a recent update that may have coincided with onset of issues, it also interacts with device sleep/wake)

Uninstalled Dolphin Browser HD beta

Removed Widget From Desktop: Wireless Signal Widget

Removed Widget From Desktop: Beautiful Home Weather (it had a recent update that may have coincided with onset of issues)

Removed Widget From Desktop: NY Times

I can almost guarantee that it is nothing to do with any of the above. Pure coincidence in my opinion....

[Guest MikeF74]

I can almost guarantee that it is nothing to do with any of the above. Pure coincidence in my opinion....

Yes, it was coincidence. The problem is back. It had exhibited itself consistently for so long, but I had 3/4ths of a problem-free day today that I thought I had solved it. I guess it was a little premature of me to post my results.

I figure however that it's more likely to be interference from a 3rd-party app than it is to be a screen calibration issue as suggested by some.

This problem is driving me nuts. Caused me to miss one important call today.

Edited September 22, 2010 by MikeF74

[Guest johnh123]

Yes, it was coincidence. The problem is back. It had exhibited itself consistently for so long, but I had 3/4ths of a problem-free day today that I thought I had solved it. I guess it was a little premature of me to post my results.

I figure however that it's more likely to be interference from a 3rd-party app than it is to be a screen calibration issue as suggested by some.

This problem is driving me nuts. Caused me to miss one important call today.

Call Dell, they'll send you another one. This is a problem they need to fix.