Hi all!
I have been using WFS up until 3 months ago and now my cousin uses it.
We both encountered the problem with unresponsive unlock screen (the ROM is stock): it will not unlock sometimes for several seconds and even worse, cannot answer a call.
It is a known problem, but is there a known solution for it? Maybe installing a new launcher or a new lockscreen widget or... Flashing a new custom rom would do the trick probably, but he's not up to it and would prefer a simpler method
Once you've turned the screen on, press on the left side of the screen for one or two seconds.
-----------
"You can overclock as much as you want, your phone will always seem too slow."
omnomnomkimiiee said:
Once you've turned the screen on, press on the left side of the screen for one or two seconds.
-----------
"You can overclock as much as you want, your phone will always seem too slow."
Click to expand...
Click to collapse
hmmm, any exact place, like the left edge of the screen, or lower left corner or just anywhere on the left? Also, is a firm press needed, or just tap and hold?
will let my cousin know anyway :fingers-crossed:
Anywhere on the left is good, a firm press.
It works for me, but I can't guarantee anything.
-----------
"You can overclock as much as you want, your phone will always seem too slow."
joriq said:
Hi all!
I have been using WFS up until 3 months ago and now my cousin uses it.
We both encountered the problem with unresponsive unlock screen (the ROM is stock): it will not unlock sometimes for several seconds and even worse, cannot answer a call.
It is a known problem, but is there a known solution for it? Maybe installing a new launcher or a new lockscreen widget or... Flashing a new custom rom would do the trick probably, but he's not up to it and would prefer a simpler method
Click to expand...
Click to collapse
Unfortunately I had this problem on stock too.
Did you try the new OTA update?? I saw somewhere that they have fixed this problem in new update.
If still you have this problem you should switch to new ROM.
Try this,work for me.
http://forum.xda-developers.com/showthread.php?t=1436314
Sent from my HTC Wildfire S A510e using xda premium
Related
Sometimes when my phone rings I can't get it out of lock to answer the phone. When the caller hangs up only then I can answer. This is intermitant. I don't know what to do.
Running the stock ROM, and rooted with unrevoked.
michelbites said:
Sometimes when my phone rings I can't get it out of lock to answer the phone. When the caller hangs up only then I can answer. This is intermitant. I don't know what to do.
Click to expand...
Click to collapse
What ROM are you running? Rooted or not rooted? These are things you should remember to post when you're having issues. Makes diagnostics much easier
All I have done was root it. I didn't install any rom or anything. I only rooted it to get the wifi tethering.
So screen turns on, but you are not able to press "answer" when a call is incoming?
Its telling you to hang up on stock rom and go custom. Plus you have better support specially being in this community.
Just saying
Sent from my ADR6300 using XDA App
nikon_rh50 said:
Its telling you to hang up on stock rom and go custom. Plus you have better support specially being in this community.
Just saying
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I'm inclined to agree. Custom ROMs definitely go waaaaay above and beyond the stock one. I use a combination of MyBackup Root and Titanium Backup free for contacts/messages and apps, respectively. Once you go custom, you never go back
What I was trying to say is that the screen is locked when the phone rings and then when I go to answer the phone it will not unlock until the phone stops ringing. But like I said in the first post this doesn't happen all the time. I would say about 25% of the time it does this. Sooo... Thats what I was trying to say.
Are you using Google Voice?
Are you using Google Voice to direct your calls? I have 3 phones that GV directs my calls to, and I've noticed that sometimes that causes one or the other of the phones to ring "late". Sometimes the Inc, sometimes not. I don't notice an issue when someone calls my direct line to any of the phones.
I am wondering what you would get if you use an app like No Lock that disables the lock screen.
I started using it when I had a roms lock screen fighting with a launcher's lock screen. I would get stacked lock screens, but only sometimes.
Running without a lock screen is not for everyone, so think about how you use your phone before disabling this great security feature. For me, my phone never leaves my side, and I mean NEVER. And if a "friend" starts poking at my phone I start poking in their face or purse... They learn after awhile.
reisa said:
Are you using Google Voice to direct your calls? I have 3 phones that GV directs my calls to, and I've noticed that sometimes that causes one or the other of the phones to ring "late". Sometimes the Inc, sometimes not. I don't notice an issue when someone calls my direct line to any of the phones.
Click to expand...
Click to collapse
I thought it was GV also but its not I uninstalled it and it would still do it.
Manitook said:
I am wondering what you would get if you use an app like No Lock that disables the lock screen.
I started using it when I had a roms lock screen fighting with a launcher's lock screen. I would get stacked lock screens, but only sometimes.
Running without a lock screen is not for everyone, so think about how you use your phone before disabling this great security feature. For me, my phone never leaves my side, and I mean NEVER. And if a "friend" starts poking at my phone I start poking in their face or purse... They learn after awhile.
Click to expand...
Click to collapse
I'm not sure if I would like the no lock because I tend to put my phone in my pocket all the time and it would just turn on and pocket dial people. LoL
Manitook said:
Running without a lock screen is not for everyone, so think about how you use your phone before disabling this great security feature. For me, my phone never leaves my side, and I mean NEVER. And if a "friend" starts poking at my phone I start poking in their face or purse... They learn after awhile.
Click to expand...
Click to collapse
App protector sounds like a good app for you.
Sent from my ADR6300
SetCPU?
Assuming screen is off when it cannot be unlocked - but...
Are you running SetCPU w/ a low screen off profile?
If not, maybe install SetCPU, and set a higher frequency in the screen off profile settings.
SetCPU is available in the market; it's also available as a free d/l for XDA members here on XDA.
smtom said:
Assuming screen is off when it cannot be unlocked - but...
Are you running SetCPU w/ a low screen off profile?
If not, maybe install SetCPU, and set a higher frequency in the screen off profile settings.
SetCPU is available in the market; it's also available as a free d/l for XDA members here on XDA.
Click to expand...
Click to collapse
Good call, I do remember when I was revving CPU way down with screen off. When it had been off for ~1-2 hours it'd be sluggish and take a bit for the CPU to rev back up. Never used it that long though because the Kernel I'm using now does this and using setCPU just chews up battery.
POQbum said:
Good call, I do remember when I was revving CPU way down with screen off. When it had been off for ~1-2 hours it'd be sluggish and take a bit for the CPU to rev back up. Never used it that long though because the Kernel I'm using now does this and using setCPU just chews up battery.
Click to expand...
Click to collapse
Well, there's something to try then - if the kernel is making the device slow to wake, use SetCPU to bump up the screen off profile and see if the issue persists.
Couple folk note just this issue in the kernel threads.
This is a known problem I struggle with myself. You may find that you can stroke up to deny the call but not unlock. It seems that this is some kind of grounding problem. Hearing that I tried setting the phone down and swiping while I wasn't touching it otherwise with some success. I've heard a quick cycle of the power button followed by an immediate swipe down can work. Some report pressing the screen firmly before swiping works. I usually just swipe up, call back and say "sorry about that, what's up?" After all, most people are used to drops and stuff because of Iphones.
I periodically goog "incredible can't answer" looking for the golden bullet.
Noticed something strange for the first time , screen is laggy and not responsive while charging the phone , I think it maybe is the kernel as its the first time to notice this , It happened after flashing franco-r6 kernel and iam using insert coin 6.3.1 Rom
Is this normal ?
Sent from my HTC One X using XDA
You flashed a ROM, You're not stock therefore you need to consult the dev of that Rom about the issue.
To be fair, I had this issue on stock.. so it probably isn't a problem with the ROM
Nit3m4re said:
To be fair, I had this issue on stock.. so it probably isn't a problem with the ROM
Click to expand...
Click to collapse
Is it still present ? What did u do about it ?
Sent from my HTC One X using XDA
Nit3m4re said:
To be fair, I had this issue on stock.. so it probably isn't a problem with the ROM
Click to expand...
Click to collapse
Yep I get this issue at times as well. Especially when I've left it to charge for a while and try to perform a pattern unlock. Happens about twice a week or so. Screen returns to normal after 10 seconds or so. Weird.
+1 this happens on stock roms all the time. it's intermittent, and often can be temporarily fixed by switching the screen off then on again.
I'm about to send my phone in for repair because of this problem. I actually have a dead patch on the screen which is intermittent. If I go to Developer Options > Pointer Location, and then trace my finger around the screen, I can see the patch where it's not picking up the input. Also sometimes the phone behaves erratically and can become completely unresponsive and flicks back and forth between home screens. Turning the screen off and then on again fixes it temporarily.
Hello. My haptic buttons (4 bottom touch buttons) are sometimes unresponsive. Sometimes when i'm using the browser I'll get stuck in it for a few seconds. And often after unlocking the phone they are also unresponsive. I just move my fender around the screen to make it come back. It's not a big issue but it is annoying.
Is there a fix? thanks!
running super galaxy 1.5 rom
bump. no one having this issue? =[
noahsarky said:
bump. no one having this issue? =[
Click to expand...
Click to collapse
Ive had it a few times when i start the phone back up in the morning, only seems to happen to me when in not usung it, i believe i read somewhere that this was an ics issue...ive found somewhat of a fix by going to settings/display and setting hardkeys to always on....drains a bit more battery but your problem will happen so rarely afterwards itll become a non issue..hope that helps! If it did, flash my rom and visit my thread!!!!
Sent from my SPH-D710 using xda premium
I've had this on ICS on occasion as well, after waking the phone up. I do the same thing - move my finger around to get them to come on.
I can't find hardkeys always on options. can be it same as tough key light always on?
noahsarky said:
I can't find hardkeys always on options. can be it same as tough key light always on?
Click to expand...
Click to collapse
This isn't an ICS issue. It happens on custom AND stock GB as well.
Often, you can make them responsive again by hitting one of the volume keys, too.
I doubt its a hardware issue... It must be a driver issue.
Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
The problem seems to be irrelevant to the Apps installed.
The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
I manually reboot my phone at most every two days.
Solutions tried, but don’t work
Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
Turning off the auto-brightness control, as suggested by some post on the Internet.
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.
Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.
I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL
I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.
NVM
Screen still goes dead.
Anyone find an actual fix to this?
isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)
I'm just trying to narrow down why randomly the fingerprint scanner does not wake the phone. It might happen once a day or not for a couple of days, but it seems to always come back. Not a huge deal since the power button will always work, but it is disconcerting when it happens. I'm not using any power widget or lock program although I do use Nova Launcher Pro. Does this happen to anyone else and if so have you narrowed it down?
Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.
jbdan said:
Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.
Click to expand...
Click to collapse
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk
bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo
SlimSnoopOS said:
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Smart lock, yes. Well smart unlock isn't it? I have a couple of BT unlock devices, Mi Band and car BT radio but that's it.
jbdan said:
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo
Click to expand...
Click to collapse
No mods.. well let me rephrase that. I have a bunch of programs running naturally, but the only "mod" I have is Cataclysm and systemless root along with Elemental X kernel. Cataclysm is considered a mod these days as it's just an overlay on stock 6.01. I know I'd have to go full stock to test for a few days but I'm so so trying to avoid that as I'm sure you know. Thanks for all the input guys, I know this can't just be me right? Hey wait a sec.. I do have a BT smart band unlock running. I'm going to take that off and see if that makes a difference. Maybe that is interfering with the fingerprint requirement.
Edit..nope not it. Gonna run stock kernel next.
The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.
tofuwrice said:
The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.
Click to expand...
Click to collapse
Too many people on Nova Pro for it to be an undocumented issue. I know it's been said that it is not the kernel, however, yesterday morning I flashed this one http://forum.xda-developers.com/nexus-5x/orig-development/jolla-kernelbullhead-t3271530 and I've not had the issue since. I usually have it at least once / day and none so far. That doesn't mean it's not going to happen in 5 minutes though. I went with stock kernel values if you're rooted and feel like giving it a try.
I was having this issue randomly when running custom hotplugging. Currently no issues with default cpu hotplug settings and ElementalX.
For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?
jgummeson said:
For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?
Click to expand...
Click to collapse
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.
bobby janow said:
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.
Click to expand...
Click to collapse
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)
morenoa48 said:
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)
Click to expand...
Click to collapse
Happened to me not charging, rooted with custom kernel. So it's across the board hit or miss. I have a feeling it will be fixed in an update or OTA. Not a deal breaker just odd is all. Oh well, if we didn't have a power button it would be major.
After 3 years of usage my Nexus 5X fingerprint scanner stopped working at all and i can't do anything about it apparently. The issues started when i sent the phone to LG to fix the bootloop