Related
Sometimes the Galaxy S II seems to have a slight delay when waking it by pressing the Home or Power button.
I saw a Thread about it in a german Phone forum where a lot of people reported this. I myself noticed it too. I'm running KE2 with Widgetlocker. I can disable Widgetlocker, it still happens.
If you wake it just after locking, it will be instant. If you wait a couple of seconds you will get a delay when waking the device. But it doesn't behave the same all the time, sometimes it's even instantly when waiting for a few minutes.
Can you guys confirm this?
yeah same problem here. I thought the latest update had fixed it but it still seems to be there
Oh and something other that I noticed, while having the phone connected to my pc, it always wakes up instantly.
prob coz its clock the CPU down while screen is off.
domazdk said:
prob coz its clock the CPU down while screen is off.
Click to expand...
Click to collapse
Either that or its the power management when its not being charged.
My lg 2x do not have this delay, should be able to fix in a kernel mod
DocRambone said:
My lg 2x do not have this delay, should be able to fix in a kernel mod
Click to expand...
Click to collapse
Great to hear that! I didn't have this either on my Desire and it was clocked down to 200Mhz...
Oh and another thing, can you disable the double Home button press? Because if you press it 1 time you are getting a slight delay because it has to wait if there will be a second press. I don't need the double-press voice Feature.
Hey. 1st post. Been reading for a while, but the wake issue annoyed me too, so I tried WidgetLocker with not much change. PowerAmp's lock widget seems to make it faster, but I found if you lower the res of the wallpaper on your lock screen, the waking is instant, which I recently realised.
I go to interfacelift.com and choose a wallpaper at 1400x900 (or so. Usually a good one for the actual background, so it doesnt really matter much for the lockscreen) save it and open to allow you to change the lock screen wallpaper. It does mean it won't be the nicest image, but it's made my phone waking sooooo much faster.
Cheers
Thanks for that, it appears to work.
http://forum.xda-developers.com/showthread.php?t=1095371
have you tried this?
I have tried copying over the modified framework and a low resolution (800x480) solid black wallpaper but no luck.
This is starting to agitate me to be honest. I’ve been telling the guy opposite me at work that S2 is the best phone available at the moment for a couple of weeks now. He ignored me and brought the sensation.
Now he has a phone that switches on immediately when he presses the power, immediately switches to his home screen when he presses the home button and his battery is lasting twice as long as mine.
Don’t get me wrong, I’d still rather have the S2. But as the new toy feeling starts to where off the little things are starting to bother me.
i have the same issue.
Well, i had the same lag at power on.
what i did :
1 change wall paper to a standard one, in the samsung gallery wallpaper. Chose one screen WP... ans applied it to both on lock and screen wallpaper
test, switch it of and on.... No lag
I applied back my large customized wallpaper i had before and applied on screen, didn't touch lock screen cause i use Widgetlock...
Now, no more lag....
It's not a cpu sleep issue, just a bug in lock screen wallpaper in my opinion....
Thanks for the suggestions Cuspide but it didn't help me unfortunatley. I even brought widgetlocker in case it was that.
It is true, it may be a minor problem but it is so annoying.
When using my HD2 with Windows Mobile, the wake up was instant, in fact even with Latitude, Email and Facebook syncs, the battery life was fantastic. HD2 with Android obviously reduced battery life and there was the wake up lag - I thought all these niggles would go with an 'actual' Android phone, but it doesn't seem that way...
I have tried the following with no luck;
- modified framework and CRT animation
- installing SetCPU and putting the governor to performance (and min 1200Mhz)
- setting a lower resolution lockscreen picture (800x480)
I'm hoping it is only software related, and something Samsung will fix very soon.
I believe that it is a mere software issue.
My Desire clocks down to 245Mhz when it's sleeping. And it wakes instantly and clocks back up to 998Mhz. The change is completely unnoticeable.
And the GSII with 1.2Ghz and 1GB of RAM - hopefully this will be fixed in a future update.
This seems to just be a kernel sleep issue.
I would imagine it's fixable in a kernel update.
I've noticed that the delay isn't apparent when the phone is on AC power. Plug your charger in and wake the phone up and it's instant, take it off charge and wake it up and there's the delay again.
it's the sleep policy. open an IM like ebuddy (it voids device to get in sleep policy) and no delay at all
update
hi Guys
has anyone found a way around this. The wakeup delay is very annoying..........
Hi guys just wondering if you noticed this strange behaviour.
I noticed a quite frustrating delay after a call when i take the phone away from my ear, it takes 2-3 sec for the screen to turn back on.
Has anybody experienced the same?
Do you know if there is a solution for this?
Sent from my GT-I9100 using XDA App
yes, think its normal. looks like the same delay when pushing power button for screen on.
sent from my SGSII via T*patalk
Thank you.
That seems strange as it is something really basic that you expect to work in a phone of this price range. Moreover it's something you come across quite often.
Do you know if the latest firmware improves this?
Sent from my GT-I9100 using XDA App
i am on ke7, so no.
sent from my SGSII via T*patalk
Cuz80 said:
Thank you.
That seems strange as it is something really basic that you expect to work in a phone of this price range. Moreover it's something you come across quite often.
Do you know if the latest firmware improves this?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
You can just turn off the sensor in the call app, if you want your screen to be available just after a call.. I don't see the problem.. but my delay is also just around a second or so.
mljjlm said:
You can just turn off the sensor in the call app, if you want your screen to be available just after a call.. I don't see the problem.. but my delay is also just around a second or so.
Click to expand...
Click to collapse
But if I do that i will drain battery unnecessarily. I don't know you guys but I find it really annoying having to wait 2sec after a call for the screen to wake up. I want to be able to hang up immediately i think I'm not asking something ridiculous.
Sent from my GT-I9100 using XDA App
you can also set the power button to terminate the call and you will not have to wait for the screen to turn on...
Reading the data from an analogue sensor (such as the proximity one) is always tricky... You need time to level out the values coming back from it, then determine that, over a period of time, the distance is suitable to enable the screen.
Only then can it be turned on etc
dfi2k5 said:
you can also set the power button to terminate the call and you will not have to wait for the screen to turn on...
Click to expand...
Click to collapse
How do you go about doing this? Can it be changed in the setting sor does it require a separate App?
xiga said:
How do you go about doing this? Can it be changed in the setting sor does it require a separate App?
Click to expand...
Click to collapse
Pls go to settings then call then calls answering ending and tick power key ends calls
Yes i find this very annoying too!
Especially when on a call center, press 2 (wait for screen) then press 4 (wait for screen) you get the idea
this is actually the only problem i have with the SGS2 since ke7
Sent from my GT-P1000 using XDA App
pulser_g2 said:
Reading the data from an analogue sensor (such as the proximity one) is always tricky... You need time to level out the values coming back from it, then determine that, over a period of time, the distance is suitable to enable the screen.
Only then can it be turned on etc
Click to expand...
Click to collapse
sgs 1 managed it fine though?....or am i missing something
Yeh my i8000 had no delay with the proximity censor.
But the screen delay seems to be everywhere. Turning on from sleep, time to adjust to ambient light and obviously the proximity sensor after pulling it away from your face.
Its not a major drama for me but I agree that it would be good to not have the delay.
I just noticed that when I use Skype the sensor works really well, meaning there is almost no lag.
I'm confused..
Sent from my GT-I9100 using XDA App
Yes! Very annoying.
Yep! I was commenting on this the other day. To be honest, I make and receive very few calls from my phone but when i do, I feel the rage rising inside me everytime because of the sensor delay.
It's the small things that annoy you the most.
As mentioned, you can opt to have the power button hang up the phone. It also does not turn the screen off, so you can continue working on the phone.
This is actually under accessibility settings, not call settings.
Menu -> Settings -> Accessibility -> Cancel the prompt -> Tick 'The power key ends calls'.
I also find the lag on waking up very annoying. Even once the screen has woken up, it takes a second for the touch input to be recognised so the pattern unlock only registers my last two or three inputs depending on how quickly I start swiping. I have to enter the pattern again. Very annoying.
pulser_g2 said:
Reading the data from an analogue sensor (such as the proximity one) is always tricky... You need time to level out the values coming back from it, then determine that, over a period of time, the distance is suitable to enable the screen.
Only then can it be turned on etc
Click to expand...
Click to collapse
I also have this problem, although I'd estimate it only takes about 1-1.5 seconds for the screen to come on.
I do however not think that this is a sensor problem, but rather a software problem.
Type *#0*# in the dialer, and press Sensor.
The phone will now vibrate once you trigger the proximity sensor. And it seems to be very fast and responsive here.
i have the problem using Skype...when i start a call it turns automatically the screen off ! i need then to push on home button to get out of skype...very ennoying...
last time i made an order online, my bank sent me a code by phone and following the instruction, the voice asked me to push the number i hear...i simply could not !! the screen was completely off ! and i could not succefully purchase online, my order was cancelled !.....due to this problem of screen..i think it is seriously ennoying and must be fixed in an update firm or something .
Agreed, this is a very annoying and unnecessary delay. Especially coming from an iPhone, where the screen turns on instantaneously when removed from the ear.
Hoping for a fix.
im ready to pay to get this fixed
Sometimes I have to knock knock twice in a row to turn on the device. It works well turning off, but on half of the times it won't turn on. Gotta do it twice. Anyone else encounter this?
Sent from my LG-D803 using Tapatalk 4
Brava27 said:
Sometimes I have to knock knock twice in a row to turn on the device. It works well turning off, but on half of the times it won't turn on. Gotta do it twice. Anyone else encounter this?
Sent from my LG-D803 using Tapatalk 4
Click to expand...
Click to collapse
I do not have that issue, but I have read in a few posts that it can be dependent on where you are knocking on the screen.
hd-renegade said:
I do not have that issue, but I have read in a few posts that it can be dependent on where you are knocking on the screen.
Click to expand...
Click to collapse
Yes! Excellent advice
Sent from my LG-D803 using Tapatalk 4
Brava27 said:
Yes! Excellent advice
Sent from my LG-D803 using Tapatalk 4
Click to expand...
Click to collapse
I think the biggest issue is knock speed.... mine works damn near 100% when I slowed down some, and knock slower like it showes at the end of the G2 commercials....
I think it's partially related to the proximity sensor. There are times when I can't get the knock on to work at all and when I hit the power button the screen shuts right back off.
Usually a few swipes over the sensor makes it work again. Sometimes I'll go in and turn the Knock On gesture off and back on and then it seems to work great for a while too.
csmith8507 said:
I think it's partially related to the proximity sensor. There are times when I can't get the knock on to work at all and when I hit the power button the screen shuts right back off.
Usually a few swipes over the sensor makes it work again. Sometimes I'll go in and turn the Knock On gesture off and back on and then it seems to work great for a while too.
Click to expand...
Click to collapse
This is my exact problem. The phone just decides it doesn't want to wake up with knock-on...but after I press the power button, it only turns on for half a second and it's out again. I never tried swiping over the sensor, but hopefully it works because it's mighty annoying when it does it during a call!
I wonder if there's a fix for this?
canecbr600 said:
I think the biggest issue is knock speed.... mine works damn near 100% when I slowed down some, and knock slower like it showes at the end of the G2 commercials....
Click to expand...
Click to collapse
this, if you are trying to do it like you did on the nokia n9 or nokia 8800 then it won't work
slow deliberate knocks are the only way
waiting on the g2 to arrive, but on my review unit, knock knock wouldn't respond correctly if i left the phone on the table, but if i picked it up, it would work nothing scientific here just an experience of one person and one prototype
I had the same issue... What fixed it is: 1. I found that the screen protector was hindering it somewhat. 2. Go to settings->display->screen-off effect-> and change it to simple. This REALLY seemed to help. Let us know!
in_dmand said:
I had the same issue... What fixed it is: 1. I found that the screen protector was hindering it somewhat. 2. Go to settings->display->screen-off effect-> and change it to simple. This REALLY seemed to help. Let us know!
Click to expand...
Click to collapse
I did notice it does seem to behave better when set to simple for the screen off animation.
My screen protector does have a cutout around the sensors. Keeping the sensor area clean enough to qualify as having OCD does seem to make it work properly the first time, every time. Maybe it's overly sensitive?
Edit: Scratch that. 30 seconds later it's behaving erratically again. Maybe it's not the fact that it's clean, but the swiping over the sensor that temporarily resolves it.
it also seems to work much better when knocking at the top of the screen where the statusbar would be.
So I ended up swapping the phone out over the weekend for a new one and now everything seems to work just fine. Seems to indicate that it's not a software problem, but rather a hardware issue with the proximity sensor.
Guys if your covering the sensors when turing the device screen on it will turn right back of on you. It's a feature LG implemented so the device wouldnt wake up in your pockets. Don't cover the sensors.
Need a little example? Grab your phone and cover the sensors and knock knock knock.You can knock till the cows come home but it will not turn on. Same thing goes for the power button but its a little delayed and will turn the screen on for half a sec and turn right back off. Practice not to do this because your phone isn't broken. There is actually a thread on this deep in the forums somewhere but its been forgotten now.
Walter21026 said:
Guys if your covering the sensors when turing the device screen on it will turn right back of on you. It's a feature LG implemented so the device wouldnt wake up in your pockets. Don't cover the sensors.
Need a little example? Grab your phone and cover the sensors and knock knock knock.You can knock till the cows come home but it will not turn on. Same thing goes for the power button but its a little delayed and will turn the screen on for half a sec and turn right back off. Practice not to do this because your phone isn't broken. There is actually a thread on this deep in the forums somewhere but its been forgotten now.
Click to expand...
Click to collapse
This is true however there are indications of problems with the proximity sensor as well. Some of the devices are behaving as if tree sensor is covered even when it's not.
Walter21026 said:
Guys if your covering the sensors when turing the device screen on it will turn right back of on you. It's a feature LG implemented so the device wouldnt wake up in your pockets. Don't cover the sensors.
Need a little example? Grab your phone and cover the sensors and knock knock knock.You can knock till the cows come home but it will not turn on. Same thing goes for the power button but its a little delayed and will turn the screen on for half a sec and turn right back off. Practice not to do this because your phone isn't broken. There is actually a thread on this deep in the forums somewhere but its been forgotten now.
Click to expand...
Click to collapse
Thanks for this.. Very insightful.. I tried it immediately LOL
I had the same issue. I have no case or screen protector on, and was not covering the sensor when trying to wake the phone. For some reason though, knocking wouldn't wake the phone, and pressing the power button would only turn the screen on for a few seconds. I want even given enough time to get past the unlock screen. I went into the store and they are sending me a replacement that should come in later this week. It doesn't happen all the time. It is much more noticeable after receiving a call though.
Sent from my VS980 4G using Tapatalk
Definitely is dependent on the proximity sensor. If i just have my thumb on the edge of the phone by the sensor it will display this problem. Even with my finger a half to one inch above it will do this. I will be paying close attention to the proximity sensor from now on when it doesn't work. Still have a few days to return and thought i had an issue but maybe not.
Sent from my VS980 4G using xda app-developers app
sometimes its also greasy fingers, at least in my case, rarely though
As long as you tap twice the same place it's working fine. If distance between first and second tap is greater than 1 - 1.5 cm it won't work.
Got the same problem on my d802...when i left the phone on my table for 2-3min it wont wake up on first knock knock even power key wake it up for 1sec after auto turn off again....even with no screen protector....i noticed that sometimes there is a delay about 5-10sec after knock knock and screen turns on....other thing i noticed when i knock on immediently after turning off it works 100%....BUT i also noticed when i knock on after a while it turns on and i can unlock got vibration and sound of the unlock but i cant see anything. Screen looks like its off but when i look closely i can hardly see widgets and when i set effect to tv out i can see the effect by pressing the power button...when i press the power button again screen turns on like normal...i noticed sometimes on a rerboot the lg bootlogo disapears the led is working an showing all colors but the boot animation is gone like the screen is off at the bootup...dont know why after the bootup the pin lock screen is showing up normal....sorry for my english^^
Right I have now had this issue several times and it has become a big problem. I put the phone in my pocket, get a call/message/text/ which turns the screen on, and somehow the touch screen buttons keep getting pressed. So far I have lost all my paid for credits in a game when I paused it and put it in my pocket to get off a train, had it start skipping tracks when listening to music when a message arrived and it started pressing the lockscreen music buttons while in my pocket....twice.
I never EVER had anything like this with the S3 that it replaced. Somehow the screen is obviously being pressed by my leg THROUGH my trousers and activating the buttons on the touchscreen whenever the screen is on. Obviously this may have serious consequences if it starts calling contacts or even emergency numbers while in my pocket.
I am looking for a way to reduce the sensitivity so it doesnt do this but so far all I can find in the settings is a single tickbox to INCREASE the sensitivity so you can use it with gloves on (which suggests to me it must also be possible to reduce it).
Yup
Sent from GT-I9500
ewokuk said:
Right I have now had this issue several times and it has become a big problem. I put the phone in my pocket, get a call/message/text/ which turns the screen on, and somehow the touch screen buttons keep getting pressed. So far I have lost all my paid for credits in a game when I paused it and put it in my pocket to get off a train, had it start skipping tracks when listening to music when a message arrived and it started pressing the lockscreen music buttons while in my pocket....twice.
I never EVER had anything like this with the S3 that it replaced. Somehow the screen is obviously being pressed by my leg THROUGH my trousers and activating the buttons on the touchscreen whenever the screen is on. Obviously this may have serious consequences if it starts calling contacts or even emergency numbers while in my pocket.
I am looking for a way to reduce the sensitivity so it doesnt do this but so far all I can find in the settings is a single tickbox to INCREASE the sensitivity so you can use it with gloves on (which suggests to me it must also be possible to reduce it).
Click to expand...
Click to collapse
You may have a faulty handset as I don't have these problems on mine.
Sent from my SM-G900F using Tapatalk
I doubt it. Friend has one as well, does exactly the same, rub phone on chest to clean it and it is pressing buttons/icons etc on the touchscreen if the screen is on.
Did you turn out that thing in settings that makes the screen more sensitive so that you can use it with gloves on?
There's the air wakeup setting too
Sent from my SM-G900I using Tapatalk
I've owned the S2, S3, S4 and never had this problem. Now I have a G900F. The S5 screen is ridiculously sensitive and I have the exact same problem as the OP.
Try to add a pattern lock screen, it should prevent the phone from launching anything even if the screen wakes up.
Yeah I've been having the same problems I switched the touch sensitivity toggle off and it's been ok
Sent from my SM-G900F using xda app-developers app
kthz said:
Try to add a pattern lock screen, it should prevent the phone from launching anything even if the screen wakes up.
Click to expand...
Click to collapse
It' on pattern lock. That doesnt stop notifications coming up for anyone that has it set up like that, and it doesnt stop it pressing the emergency calls button!
Air View is off, Increase Touch Sensitivity is off (as already mentioned). Infact I tried the Increase Touch Sensitivity option to see what effect it has and I can't see any difference to it with it turned on, it is just as sensitive, I can literally put my finger inside my shirt and move the screen around and I can do this just as well with the touch sensitivity on or off. Perhaps there is a bug which is causing the increased touch sensitivity to be on ALL the time even when the box is not ticked. Seems to be a problem many are having anyway.
ewokuk said:
It' on pattern lock. That doesnt stop notifications coming up for anyone that has it set up like that, and it doesnt stop it pressing the emergency calls button!
Air View is off, Increase Touch Sensitivity is off (as already mentioned). Infact I tried the Increase Touch Sensitivity option to see what effect it has and I can't see any difference to it with it turned on, it is just as sensitive, I can literally put my finger inside my shirt and move the screen around and I can do this just as well with the touch sensitivity on or off. Perhaps there is a bug which is causing the increased touch sensitivity to be on ALL the time even when the box is not ticked. Seems to be a problem many are having anyway.
Click to expand...
Click to collapse
Not had any problems whilst in my pocket, but I tried using the screen through my T-SHIRT and it does the same thing for me with touch sensitivity off or on. Just tried with gloves though and it doesn't work unless you switch touch sensitivity on, so it does make some kind of difference to the screen.
Sent from my SM-G900F using Tapatalk
In that case ewokuk, 2 solutions, since your phone is brand new, maybe you should take it back to your store and get another unit.
Or wait for maybe a fix with next firmware update.. which may happen anytime. For helping you, you could get a protection / front cover for your phone
I registered just to post here. This has been driving me absolutely nuts. Every time I have a call when in the car and the phone is in my pocket (talking through bluetooth), if my leg so much as twitches I end up muting myself or hanging up. I went from an S3 to the S5. If I get a text while walking and I have music playing or something, any and every button available will be pressed. I have had random gibberish created on my calendar while walking (screen lock hadn't activated yet because I had just put it in my pocket).
ewokuk, any word on what you did? I have played around with as many settings as I can but nothing seems to do the trick. It's a nice phone, but unfortunately this one thing drives me up a wall
The screens can still be used through simple fabrics .. it can be done so since the S2. If the screen is in the pocket facing down (against your thigh) it still can be triggered. I can only suggest to put the screen facing outwards or well not against your skin or body
Sent from my GT-I9505 using XDA Free mobile app
deathst said:
The screens can still be used through simple fabrics .. it can be done so since the S2. If the screen is in the pocket facing down (against your thigh) it still can be triggered. I can only suggest to put the screen facing outwards or well not against your skin or body
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
The difference in sensitivity between the S3 and S5 is pretty astounding though. Yes, I could use the S3 through a shirt if needed, but I never had it hang up phone calls constantly and go through all my apps randomly.
I think the proximity sensor is just not the greatest as it doesn't detect that it's in a pocket. Again, no real idea, but that is my guess.
Same problems here. Phone pocket dials people, replies to texts. Pattern lock helped..but I prefer not using it. Maybe it's because the phone wakes with text messages received. Annoying as heck
Sent from my SM-G900V using XDA Premium 4 mobile app
Rippley05 said:
Same problems here. Phone pocket dials people, replies to texts. Pattern lock helped..but I prefer not using it. Maybe it's because the phone wakes with text messages received. Annoying as heck
Sent from my SM-G900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm glad I'm not the only one because I really did think it was just me. All of the issues listed in this thread happen to me all the time. Tracks skip, the phone hangs up.. I even find my typing is less accurate unless I really slow myself down (it seems prone to picking up extra key presses although this might just be mel. I did not have these issues with my s3.
---------- Post added at 12:36 AM ---------- Previous post was at 12:32 AM ----------
Forum wouldn't let me edit my previous message so here goes:
No its just me. See here http://phandroid.com/2014/04/19/8-things-i-hate-about-the-samsung-galaxy-s5/:
Hey all, i am facing the same problem with the sensitivity of my screen!
ewokuk said:
Right I have now had this issue several times and it has become a big problem. I put the phone in my pocket, get a call/message/text/ which turns the screen on, and somehow the touch screen buttons keep getting pressed. So far I have lost all my paid for credits in a game when I paused it and put it in my pocket to get off a train, had it start skipping tracks when listening to music when a message arrived and it started pressing the lockscreen music buttons while in my pocket....twice.
I never EVER had anything like this with the S3 that it replaced. Somehow the screen is obviously being pressed by my leg THROUGH my trousers and activating the buttons on the touchscreen whenever the screen is on. Obviously this may have serious consequences if it starts calling contacts or even emergency numbers while in my pocket.
I am looking for a way to reduce the sensitivity so it doesnt do this but so far all I can find in the settings is a single tickbox to INCREASE the sensitivity so you can use it with gloves on (which suggests to me it must also be possible to reduce it).
Click to expand...
Click to collapse
i am ahvind the same issue with the sensitivity of the screen!!!something wrong is happening for sure cause i tested another Samsung S5 and it didnt have any problem!Its has warranty so i dont care!do the same!
---------- Post added at 10:23 PM ---------- Previous post was at 10:15 PM ----------
ewokuk said:
Right I have now had this issue several times and it has become a big problem. I put the phone in my pocket, get a call/message/text/ which turns the screen on, and somehow the touch screen buttons keep getting pressed. So far I have lost all my paid for credits in a game when I paused it and put it in my pocket to get off a train, had it start skipping tracks when listening to music when a message arrived and it started pressing the lockscreen music buttons while in my pocket....twice.
I never EVER had anything like this with the S3 that it replaced. Somehow the screen is obviously being pressed by my leg THROUGH my trousers and activating the buttons on the touchscreen whenever the screen is on. Obviously this may have serious consequences if it starts calling contacts or even emergency numbers while in my pocket.
I am looking for a way to reduce the sensitivity so it doesnt do this but so far all I can find in the settings is a single tickbox to INCREASE the sensitivity so you can use it with gloves on (which suggests to me it must also be possible to reduce it).
Click to expand...
Click to collapse
i am having the same issue about the sensitivity of the screen!!!something wrong is happening for sure cause i tested another Samsung S5 and it didnt have any problem!Its has warranty so i dont care!do the same!
s series sensitivity
I have had that problem with the s3 s4 and now s5 i just put my phone in my pocket with the screen facing out that way my leg cant activate it and my pants doesnt press the unlock button when i move.
Ditto, never so bad as this phone, I put it in my pocket now screen out, and put my wallet over the screen so I don't accidentally crack it.
Often in games when I am "hovering" over the screen it will trigger the action anyway. I've tested this to nearly 1 full cm away from the screen. If I hover on the same spot for 2+ seconds at ~1cm it initiates a touch at that point.
I also did not notice a difference switching increased sensitivity on or off.
Rarely, but sometimes during calls the screen turns on briefly when I pull the phone away as it starts making my face sweat, it will the "hover" hang up or mute, or launch some app (often one that has force screen on permissions) and send people gibberish email or text messages, set alarms or calendar events. I even had it start a conference call, adding an old boss to my conversation (I keep the number handy for references) once.
I have used the finger print lock since the first time I turned the phone on. Most annoying is the sensorly app, only works with the screen on even when running in the background...
I have also had to modify my typing to accommodate this sensitivity, I have to tap slightly above and right of the keys to make sure I hit the right ones.
Hey, guys. I'm a huge fan of this phone.. I can't get over what a good value it is for the money. I have almost zero issues with it. The one issue I do have is the inconsistency with tap to wake. It seems like after it has been in my pocket for a while, it just fails to work. This happens periodically throughout the day, to the point where I just can't rely on it. It drives me mad because that's kind of a must have feature for me. To be fair, the only device I have never had tap to wake issues with is LG phones. They just seem to work all the time.
I did raise the sensitivity following the guide found on these forums. It's something else, like the pocket protection is stuck on or something. Anyone else experience something similar? I don't want to use the fingerprint reader. Is there something I don't know? Some setting I'm not seeing? Or is this just how it is?
Still a great phone otherwise. I wish I could fix this one little thing.
Is your screen clean or dirty? Have you tried wiping it down with 70% isopropyl alcohol and seeing if that improves the responsiveness. Is the phone hot when it's not responding? Are your fingers dirty?
It's not very sensitive, you definitely need to give it a couple of thumps unlike the taps on an LG phone.
There's a learning curve with this phone. I nearly dislocated my shoulder trying to shake the flashlight awake before I realized you had to wake the screen first
ludovicien said:
It's not very sensitive, you definitely need to give it a couple of thumps unlike the taps on an LG phone.
There's a learning curve with this phone. I nearly dislocated my shoulder trying to shake the flashlight awake before I realized you had to wake the screen first
Click to expand...
Click to collapse
I mean, this only happens when I take it out of my pocket. Tap to wake works fine the rest of the time and my screen is definitely clean.
Sent from my ZTE A2017U using Tapatalk
greyhulk said:
I mean, this only happens when I take it out of my pocket. Tap to wake works fine the rest of the time and my screen is definitely clean.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I'm coming from an lg phone as well, I have found the taps must be slower. The pause between taps needs to be just a little longer and it works for me almost every time.
Double tap to wake doesn't work when the phone has gone into doze mode. ZTE knows about this issue and is working on a fix.
xxBrun0xx said:
Double tap to wake doesn't work when the phone has gone into doze mode. ZTE knows about this issue and is working on a fix.
Click to expand...
Click to collapse
That actually explains a lot. Thanks!
Doze seems to break a lot, including notifications on other phones.
Sent from my ZTE A2017U using Tapatalk
greyhulk said:
That actually explains a lot. Thanks!
Doze seems to break a lot, including notifications on other phones.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
The doze should not kick in if the phone is moving. One of the conditions is that phone should be static for a while. More likely it's something based on proximity sensor to prevent accidental turn ons. I found that i would have to tap several times to wake it up most time i have to do it twice. The force touch is buggy
Sent from my shieldtablet using XDA-Developers mobile app
peramikic said:
The doze should not kick in if the phone is moving. One of the conditions is that phone should be static for a while. More likely it's something based on proximity sensor to prevent accidental turn ons. I found that i would have to tap several times to wake it up most time i have to do it twice. The force touch is buggy
Sent from my shieldtablet using XDA-Developers mobile app
Click to expand...
Click to collapse
Well, I haven't had any issues since I disabled doze and I doubt that's a coincidence.
I agree that doze shouldn't kick on in your pocket, which is why I originally suspected the proximity sensor, but it could be a bug in ZTE's ROM.
My Mate 8 had a malfunctioning doze mode that would cause all notifications to stop as soon as the screen went off, even if the phone was moving. I fixed that by disabling doze also.
Sent from my ZTE A2017U using Tapatalk
The same issue I'm having on both colors I'm having .
Most of the time when picking the device from my jeans pocket refuses to open with double tap even after several attempts.
I have to unlock by pressing with power button and then when holding my phone it stating to work fine.
It's really annoying and frustrating.
Only double tap to sleep with nova prime or 3D next launcher working 100% perfect in all situations from home screen.
Also I'm using glimpse notification and enable the option to double tap to sleep from lock screen and works perfect all time.
Another feature having is it wakes up the screen automatically every time having notification alert and after screen being off continuous the led to be on as a reminder.
Sent from my iPad Air 2
So, I was wrong. Disabling doze didn't fix it. I went back to my OnePlus 3 for a day to get perspective. That phone pretty much never misses a tap-to-wake. It just works. Conversely, the Axon regularly "goes to sleep" when it's in my pocket and I can tap on the screen as many times as I want and it will never come on until I hit the power button. It's definitely not working like it should, at least not for me.
I'm not sure how anyone can say that it's working fine. I like everything else about the phone. This is just annoying because I can't rely on using tap-to-wake. I spend more time tapping on the screen when it's not working than I would if it just didn't have the feature and I had to use other methods. If ZTE could fix this to work as reliably as an LG or the OnePlus 3, I'd be in heaven.
greyhulk said:
So, I was wrong. Disabling doze didn't fix it. I went back to my OnePlus 3 for a day to get perspective. That phone pretty much never misses a tap-to-wake. It just works. Conversely, the Axon regularly "goes to sleep" when it's in my pocket and I can tap on the screen as many times as I want and it will never come on until I hit the power button. It's definitely not working like it should, at least not for me.
I'm not sure how anyone can say that it's working fine. I like everything else about the phone. This is just annoying because I can't rely on using tap-to-wake. I spend more time tapping on the screen when it's not working than I would if it just didn't have the feature and I had to use other methods. If ZTE could fix this to work as reliably as an LG or the OnePlus 3, I'd be in heaven.
Click to expand...
Click to collapse
Totally agree.
Hope ZTE makes improvements on that very useful feature to become just like LG.
Sent from my iPad Air 2