As the title may indicate, I'm getting really frustrated with my phone constantly waking in my pocket. I do like using DTTW when it actually works correctly, and carry the display side in against the leg to prevent damage... But i'm getting pretty freaking mad samsung over the pocket dialing, pocket setting changes, pocket flashlight activation, etc... I know this forum used to have all kinds of threads about this, some reporting faulty proximity sensors and such. I'm starting to wonder if mine has a hardware issue with the sensor because it was one of the first wave of phones produced, so the initial hardware revision, and my problem has never been fixed by a system update.
So does anybody have any ideas that could help? I always have accidental touch protection" enabled, and don't use lift to wake or any other gestures. I'm on the newest system version, I've cleared the caches multiple times... I'm just about mad enough to go demand a replacement, no BS, because losing a function like this should not happen on a freaking thousand dollar phone.
BranC85 said:
As the title may indicate, I'm getting really frustrated with my phone constantly waking in my pocket. I do like using DTTW when it actually works correctly, and carry the display side in against the leg to prevent damage... But i'm getting pretty freaking mad samsung over the pocket dialing, pocket setting changes, pocket flashlight activation, etc... I know this forum used to have all kinds of threads about this, some reporting faulty proximity sensors and such. I'm starting to wonder if mine has a hardware issue with the sensor because it was one of the first wave of phones produced, so the initial hardware revision, and my problem has never been fixed by a system update.
So does anybody have any ideas that could help? I always have accidental touch protection" enabled, and don't use lift to wake or any other gestures. I'm on the newest system version, I've cleared the caches multiple times... I'm just about mad enough to go demand a replacement, no BS, because losing a function like this should not happen on a freaking thousand dollar phone.
Click to expand...
Click to collapse
The gen 1 proximity sensor used on our devices is trash.
Sent from my SM-G975U using Tapatalk
Limeybastard said:
The gen 1 proximity sensor used on our devices is trash.
Sent from my SM-G975U using Tapatalk
Click to expand...
Click to collapse
Do you have any idea what revision it is on now? I can't find anything by googling it, I just know my about phone section shows a hardware revision of 1.0.
BranC85 said:
Do you have any idea what revision it is on now? I can't find anything by googling it, I just know my about phone section shows a hardware revision of 1.0.
Click to expand...
Click to collapse
I don't sorry, but perhaps they'll fix it for the N10 or S11. Joy's of first generation beta hardware.
Sent from my SM-G975U using Tapatalk
Glad I'm not the only one with this problem. Butt dialing, butt texting, butt email sending....this is the worst issue with this phone by far.
BranC85 said:
As the title may indicate, I'm getting really frustrated with my phone constantly waking in my pocket. I do like using DTTW when it actually works correctly, and carry the display side in against the leg to prevent damage... But i'm getting pretty freaking mad samsung over the pocket dialing, pocket setting changes, pocket flashlight activation, etc... I know this forum used to have all kinds of threads about this, some reporting faulty proximity sensors and such. I'm starting to wonder if mine has a hardware issue with the sensor because it was one of the first wave of phones produced, so the initial hardware revision, and my problem has never been fixed by a system update.
So does anybody have any ideas that could help? I always have accidental touch protection" enabled, and don't use lift to wake or any other gestures. I'm on the newest system version, I've cleared the caches multiple times... I'm just about mad enough to go demand a replacement, no BS, because losing a function like this should not happen on a freaking thousand dollar phone.
Click to expand...
Click to collapse
Honestly, your issue, and the fact they got rid of the led notification light, are my only 2 issues with this phone.
I was having all the same problems as you are to an extent, until I just gave up cut off DTTW altogether. Now I just use tap to wake AOD and I'm actually just as pleased. But yeah, the proximity sensor is busted with this phone for sure.
mistermidas said:
Honestly, your issue, and the fact they got rid of the led notification light, are my only 2 issues with this phone.
I was having all the same problems as you are to an extent, until I just gave up cut off DTTW altogether. Now I just use tap to wake AOD and I'm actually just as pleased. But yeah, the proximity sensor is busted with this phone for sure.
Click to expand...
Click to collapse
I probably would do the same if I didn't have the plus model and also wouldn't be so bothered by this... But the position of our power button is just terrible for one handed use, especially if you use your left. That's why I'm in the habit of DTTW on then using the one handed operation + app to turn off. It's a decent bandaid for the otherwise out-of-reach button. The other thing is that it really isn't a compromise we should have to make in such an expensive, "luxury-priced" phone... I mean this wake gesture has been around for at least five years and I don't think it's ever been implemented so badly... I mean this was never an issue with my old HTC one or my pixel.
BranC85 said:
I probably would do the same if I didn't have the plus model and also wouldn't be so bothered by this... But the position of our power button is just terrible for one handed use, especially if you use your left. That's why I'm in the habit of DTTW on then using the one handed operation + app to turn off. It's a decent bandaid for the otherwise out-of-reach button. The other thing is that it really isn't a compromise we should have to make in such an expensive, "luxury-priced" phone... I mean this wake gesture has been around for at least five years and I don't think it's ever been implemented so badly... I mean this was never an issue with my old HTC one or my pixel.
Click to expand...
Click to collapse
And added to the fact is they removed that pressure sensitive or whatever it's called home button and moved the power button to the top - not as easy to use as it used to be with previous Galaxy devices now.
Sent from my SM-G975U using Tapatalk
Related
This is to get an idea about Touchscreen calibration issue with nexus one. I am trying to figure out if those of us who have faced this problem need to get replacement or just wait for software update.
Calibration of the battery or the touchscreen?... Very vague post... Give us the issues.
Paul22000 said:
Calibration of the battery or the touchscreen?... Very vague post... Give us the issues.
Click to expand...
Click to collapse
Touch Screen calibration. The lower 3/4 part of the screen starts acting crazy and registers touch below what you are touching. Needs a soft-reset; solves the issue temporarily.
Used to experience them semi-regularly. Seldom after switching to custom ROMs; both Cyanogen's and Modaco's Desire seem to have lessened the problem somewhat, though I can't imagine why as I don't think either developer poked around with the drivers or anything. And since I've been on custom ROMs for quite a while now, I'm certain it's not a placebo effect. I simply very rarely experience the problem anymore.
I too rarely experience this anymore after switching to Desire.
Also, soft-reset is not necessary. Turn the screen off for 3 seconds.
Damn it. It happen to me today again. I was browsing my email with one finger on the screen in the middle flipping through. Then all of sudden the phone kept vibrating as if I was touching the icons below. Then the search box pop up, a voice search came up and a task screen as if pressed those buttons!! I should have recorded it. Anyway I put the phone to sleep and wake it again and all is well for now. Anyone think this is a hardware problem???
never have had this happen, only thing i have noticed is when another part of my hand is touching the edge of the screen..
I talked with Google customer service today. She acknowledged that it is fairly common issue and insisted that it is not a hardware issue and even her phone has the same behavior. Whatever it is, they will cover it under warranty. So, i will wait for a month and if problem is unsolved, I will ask for replacement.
malicious85 said:
never have had this happen, only thing i have noticed is when another part of my hand is touching the edge of the screen..
Click to expand...
Click to collapse
Same here. Learned to hold my phone more effectively.
uberingram said:
Same here. Learned to hold my phone more effectively.
Click to expand...
Click to collapse
My other hand is not even on the phone. I'm only using one finger!
The ONLY calibration issue I have seen is when I am on my BT Hands free in the truck and go to hit the Mute button, it registers and presses the 0 (zero) key instead.
Hitting power (to turn off the screen) and turning it back on again (after a 2-3 second pause) fixes it...
Annoying, but not unusable...
Talderon said:
The ONLY calibration issue I have seen is when I am on my BT Hands free in the truck and go to hit the Mute button, it registers and presses the 0 (zero) key instead.
Hitting power (to turn off the screen) and turning it back on again (after a 2-3 second pause) fixes it...
Annoying, but not unusable...
Click to expand...
Click to collapse
yow you make it seem natural for a phone that cost 500+!!
ram130 said:
yow you make it seem natural for a phone that cost 500+!!
Click to expand...
Click to collapse
Eh? This makes no sense...
My point was, I am having calibration issues. I stated my case, stated my opinion and moved on. Responses like these are useless and need to be purged.
Talderon said:
Eh? This makes no sense...
My point was, I am having calibration issues. I stated my case, stated my opinion and moved on. Responses like these are useless and need to be purged.
Click to expand...
Click to collapse
As in you take it simple. You spent money on the phone and it has problems like those, you making seem normal for a phone that cost 500 plus. Almost like your giving permission to other manufactures that says its okay to have these problems.
ram130 said:
As in you take it simple. You spent money on the phone and it has problems like those, you making seem normal for a phone that cost 500 plus. Almost like your giving permission to other manufactures that says its okay to have these problems.
Click to expand...
Click to collapse
I don't see why being $500+ should matter. FYI, the price range this handset falls into is the typical, NORMAL price being not subsidized to a network.
erikku said:
I don't see why being $500+ should matter. FYI, the price range this handset falls into is the typical, NORMAL price being not subsidized to a network.
Click to expand...
Click to collapse
Kool then. Lets just hope this is a software issue. Because of Google silence on the matter, I cannot decide whether or not to return or swap the phone. Mainly because I don't know for a fact if its software and my 14days ends this Thursday
Maybe its a app installed causing the issue...
maybe its a design issue, arn't the antennas down in that part of the phone? If it happens with the desire ROMs too?
If it was easy to fix surely it would be fixed by now as its quite widely reported
scote said:
maybe its a design issue, arn't the antennas down in that part of the phone? If it happens with the desire ROMs too?
If it was easy to fix surely it would be fixed by now as its quite widely reported
Click to expand...
Click to collapse
Thats what I believed until I saw someone here said they were having touchscreen problems before but not anymore on a leak rom. So now I'm half sided in what to believe.
temperbad said:
Maybe its a app installed causing the issue...
Click to expand...
Click to collapse
Hell no.
ram130 said:
Thats what I believed until I saw someone here said they were having touchscreen problems before but not anymore on a leak rom. So now I'm half sided in what to believe.
Hell no.
Click to expand...
Click to collapse
What makes you a genius, maybe we all have a app that causes our **** to go buggy when Its open or something... could easily be the dealio.... I don't have the problem so I don't care, but I know apps can make things very buggy....
I doubt it is a app, but it could be, and others that flashed roms that don't have the problem anymore well, maybe the new rom and app aren't conflicting, just a guess....
Looks like it was my generic charger causing all the problems all along...
Too high output (6.5VDC where it should be 5VDC)
Ordered a replacement, hoping for the best.
Thanks for all the help!
Sometimes my touchscreen is just perfect. Lately, it's driving me nuts!
When I hold my finger on the screen, the touch screen registers rapid multiple touches. Possibly as many as 10 per second.
This makes dragging and long-press actions almost impossible. Scrolling is very hard and typing is a PitA.
The problem goes away at times but keeps returning. I'm not sure if I had it before the recent update.
At first, it seemed like rebooting helped but today it proved useless.
Anybody, please help!!!!
(phone was used and has no warranty coverage )
dfan said:
Sometimes my touchscreen is just perfect. Lately, it's driving me nuts!
When I hold my finger on the screen, the touch screen registers rapid multiple touches. Possibly as many as 10 per second.
This makes dragging and long-press actions almost impossible. Scrolling is very hard and typing is a PitA.
The problem goes away at times but keeps returning. I'm not sure if I had it before the recent update.
At first, it seemed like rebooting helped but today it proved useless.
Anybody, please help!!!!
(phone was used and has no warranty coverage )
Click to expand...
Click to collapse
Do you have a screen protector on the screen? Sometimes the cheaper ones are too thick and the screen doesn't register touch like it should.
Talonnb said:
Do you have a screen protector on the screen? Sometimes the cheaper ones are too thick and the screen doesn't register touch like it should.
Click to expand...
Click to collapse
Just the one that came on the phone.
Like I said, the phone works beautifully some of the time but registers multiple contacts other times.
I suspect software but it seems I'm the only person with the problem...
do you have a warranty.... sounds like a hardware fault to me.... the only way you can prove it's software (or not).. is to do a factory data reset and then run it with the standard basic build for a few days.. see if you still have problems when you don't have any other apps on the phone.
Do you have wet fingers when you experiment this behaviors?
Happens to me too. I figure its due to gunk on the screen like water, sweat your gf's makeup (a major one)
Sent from my X10a using XDA App
This happens to me too.
Only started happening since the last update so I just assumed it was a bug in the new firmware. It's like the phone lags and then catches up with itself, very annoying.
bushbox browser said:
This happens to me too.
Only started happening since the last update so I just assumed it was a bug in the new firmware. It's like the phone lags and then catches up with itself, very annoying.
Click to expand...
Click to collapse
I think it is since the update. I'd better reset the phone using SEUS and see what happens.
@ everybody, believe me, I have had the problem through a variety of circumstances and no problem with sweaty fingers etc. It seems pretty random!
I don't have a warranty so re-install here I come!
I would definetly try the factory reset first. I have had similiar issues but its only been while typing quickly. It lags a bit and then it all shows up on the screen plus a few extras of whatever the last character I typed was.
I did read somewhere, can't remember exactly where, that because our screens are capacitive they can malfunction. What I mean is this:
"Surface Capacitive touch panels: a layer that can store an electrical charge is created on the glass panel. When a user touches the monitor with his or her ungloved finger, a portion of the charge is transferred to the grounded user reducing the charge on the capacitive layer. The controller calculates, from the differences in charge at each corner and determines where the touch occurred."
Sooooo if say the ground for the screen is damaged then it will not register your touch appropriately. Hopefully it just requires a reset, cause the latter I think would be a tougher fix.
Let us know
dfan, is it happen only when you charge your phone? What charger are you use? Original?
I did a restore but no change, issue still there, it doesn't happen often though.
Dose seem like a bug and it never happened to me before the last update.
Also it happens to me when not charging.
Sent from my X10i using XDA App
very bad.. you cannot drink a cold coke and use the phone. I think that it is a hardware related problem. I was trying to reproduce the same with N1 and Legend (with my fingers flooded) without problems. So.. guys with hyperdrosis keep away from this phone!
No it's not a hardware problem as it only started happening with the last update.
Remember the x10 uses different software to nexus one or desire so can't compare with them.
I believe it's the software lagging, this update is faster overall but just lags occasionally, maybe the next software update will fix it, and if not the 2.1 update should definitely fix the issue.
Sent from my X10i using XDA App
bushbox browser said:
No it's not a hardware problem as it only started happening with the last update.
Remember the x10 uses different software to nexus one or desire so can't compare with them.
I believe it's the software lagging, this update is faster overall but just lags occasionally, maybe the next software update will fix it, and if not the 2.1 update should definitely fix the issue.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Are you pretty sure?
Tested... it is present on old roms
Well the old roms were laggy as hell anyway. It seems like classic software lag so I still think it's software.
Maybe when 2.1 is released we will find out, or even better when we get stock android running though root, that would clear it up once and for all.
My iPhone 3g also suffered from similar lag issues.
Sent from my X10i using XDA App
brunswick000 said:
I would definetly try the factory reset first. I have had similiar issues but its only been while typing quickly. It lags a bit and then it all shows up on the screen plus a few extras of whatever the last character I typed was.
...
Sooooo if say the ground for the screen is damaged then it will not register your touch appropriately. Hopefully it just requires a reset, cause the latter I think would be a tougher fix.
Let us know
Click to expand...
Click to collapse
Hells yeah I don't want a defective screen or this thing is done!
regarding your first comment, this is not lag. It is like I had a turbo button. If I touch for more than 1/15 sec, I get 2, 3 or 4 letters.
instead of one long press, the screen continually registers new presses, no matter how firm my touch is.
Imagine how much fun it is drawing the unlock pattern when my phone's in a bad mood...
That dose sound different to the small lag I occasionally experience, very odd.
Sent from my X10i using XDA App
I've reinstalled the FW and it didn't fix it.
The other day I had 5 straight hours of rapid-fire screen during which I couldn't even unlock the phone.
Gonna have to send it in for repair. Anybody know how expensive S-E are for repairs? Is it even worth doing?
I have narrowed the suspects down to my generic charger.
The charger I bought outputs over 5V (claims 6.5V) which seems to be the problem since I don't experience the issue when charging from a USB port.
New charger ordered, fingers crossed.
Thanks for all the suggestions!
I've noticed that on my NS, I don't have to actually touch the screen to tap keys. I can keep my finger slightly hovering over the glass and it still recognizes my input. Sometimes it actually causes me to mistype at a higher rate than other phones.
Are you guys seeing this too?
Sent from my Nexus S using XDA App
Glad to see I'm not the only one who's experienced this....I thought I was going crazy. It's sporadic at best, but when it happens it is annoying. I can't say for sure what causes it, but I'd love to hear other people's opinions.
I've been getting this as well.
same here. Guess they have the capacitance set a bit too high.....
yup, me too. infact. my home button gets phatom long pressed and the light is off on it...have to power it off/ turn the screen off and on muliple times. that insanity has occured about 4 times thought.
Thanks for the replies. I went back into Best Buy and tried their demo phone. So either it's supposed to be this way or they messed up a whole batch of phones. I wish I could remember whether the vibrant did this or not, but it's not standing out.
Sometimes touchscreen nonresponsive too. This is not relating to partial outer border touching either.
Sent from my Nexus S using XDA App
kjy112 said:
Sometimes touchscreen nonresponsive too. This is not relating to partial outer border touching either.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I believe Engadget did mention did this during their review @ http://www.engadget.com/2010/12/10/nexus-s-review/.
Their exact quote: "One other thing of note -- we noticed a few missed or latent presses on the touchscreen which occasionally led to stuttery behavior or an opened item that we didn't mean to tap. It's hard to say if this was a software or hardware issue (and we know that sometimes Android devices can be particularly finicky when syncing). It wasn't a deal-breaker by any means, but we saw the issue rear its head a handful of times, and felt it was worth mentioning."
it's nothing ,, the Samsung galaxy S does that too D:
that happens due to the static on your finger.
Hi
I opened a thread (http://forum.xda-developers.com/showthread.php?t=879872) because I definitely have a problem on the back capacitive button, just wondering how many people are affected?
In fact I have seen this in four devices now, it looks that there is a batch of defective Nexus S phones out there affected by this problem?
It's normal. My Nexus One is like that too. It's magic.
So, it is normal to have un-responsive back button after some times?
Damn ... this is bad. I hope I can cope with it. I really hate hardware problem.
And still could not understand why Google cannot fix it.
Last time from HTC ...
And now from Samsung ...
*Still waiting Nexus S from UK*
nxt said:
It's normal. My Nexus One is like that too. It's magic.
Click to expand...
Click to collapse
gogol said:
So, it is normal to have un-responsive back button after some times?
Damn ... this is bad. I hope I can cope with it. I really hate hardware problem.
And still could not understand why Google cannot fix it.
Last time from HTC ...
And now from Samsung ...
*Still waiting Nexus S from UK*
Click to expand...
Click to collapse
There's a thread for the back button, that's a real issue. Some people have the Back button issue, some the Home button issue. Both of those buttons are on the outer edge of the phone, so something may be messed up when the phone was being assembled.
Multitouch Visible Test
With that app, 1-finger touch is alright, no issues.2 Fingers seems alright too. Adding up to 4 fingers seems to be alright and moving them around the screen.
Sometimes with 5 fingers though, they'll all show on the program, and then immediately vanish. If I keep moving my fingers across the screen, they'll pop in and out, but won't actually stay on screen and follow. But this only happens sometimes. Other times, 5-finger input works fine.
My other camera is dead at the moment and I have to run and get batteries for it tomorrow, so I can't actually upload video of what I mean. I was hoping to get some input from other people about how their multi-touch seems to be with that app. Not entirely sure if this is just a rare defect, widespread, or working as intended maybe (not entirely sure if there's anything saying how much multi-touch this screen is; figured it was 10 though)
Some things to try:
- Use 1 finger, drag it all over the screen
- Keep adding fingers 1 by one after dragging them across the screen (add finger, drag it around, add next finger, etc.)
- Don't touch the screen for about 3 seconds, then just have all 5 fingers come in-contact with the screen, and keep them in one spot (on mine most of the time, the points appear then immediately vanish)
Could it just be the app your using?
Try using this one...
Check out "MultiTouch Tester"
https://play.google.com/store/apps/details?id=com.the511plus.MultiTouchTester
See if it does the same thing.
Sent from my SPH-L710 using xda app-developers app
jjdevega said:
Could it just be the app your using?
Try using this one...
Check out "MultiTouch Tester"
https://play.google.com/store/apps/details?id=com.the511plus.MultiTouchTester
See if it does the same thing.
Click to expand...
Click to collapse
Yea it still does the same thing :/ Here's a video:
It could be as simple as compatibility issues with the app...
Sent from my SPH-L710 using xda app-developers app
Called up Google and it doesn't seem to be widespread (or at least the person didn't say it was), and I could get a replacement under warranty. I don't have the funds to put on hold currently so it'll have to wait if I do decide to do it.
Although I wonder if I really should, I mean I highly doubt I'm going to do anything requiring more then 2 fingers on the screen at any point (nor can I really think of anything), and aside from multitouch, everything else seems great. No dead pixels, back doesn't flex, screen is alright quality-wise.
Would be nice if some other people can try out multitouch though just to see if it really might be widespread or not though. The thing is though, it works fine sometimes, and other times it doesn't. Perhaps software might fix it in time, but I don't know. I thought I heard of the Nexus 7 having a similar issue, but I can't recall...
jjdevega said:
It could be as simple as compatibility issues with the app...
Click to expand...
Click to collapse
It seems to do the same even with the "Show touches" option enabled in Developer options (tried it on an empty homescreen).
Bump
Anyone? It only takes a minute or two at the most to test this... and the apps available to do so are free and light.
Doing the tests you described never caused anything on my tablet. But if I put my hand down on the tablet flat then put my five fingers on I get your issue. Then wait three seconds and try again and everything is fine till I put my palm back on.
Might be a badly configured palm detection algorithme? Op, do you have fat fingers? Sorry if that sounds rude
Chluz said:
Might be a badly configured palm detection algorithme? Op, do you have fat fingers? Sorry if that sounds rude
Click to expand...
Click to collapse
Lol, hmm, na I don't think I have fat fingers
How about fruit ninja, does that work properly? It's true that if show touches doesn't work, it's not a good sign. Unless it's a system firmware bug
1 and 2 fingers seems to work great in Fruit Ninja; 3+ randomly works or doesn't work, and when it does work it seems to cut-out at some point and then just show slashes delayed from where my finger is currently
Any idea if its hardware or software related? I have the same issue with my N10 and don't know if I should get a replacement or not.
Got mine today, same issue. Actually, that too bad since everything works fine, and i only got a minimal light bleed. I hope my replacement won't be worst regarding light bleed :/
Same issue on mine. Considering a replacement now with this and wakeup lag + battery issue (indicator not updating % at all!?)
Don't know if I wasn't lucky or just poor QA.
I'm pretty sure it is a software thing because when the problem occurs and I tab on the multitasking button twice (so it shows the multitasking menu and switches back to the app) the touchscreen acts normal again until I put more than three fingers on screen.
But if its a software problem, shouldn't it happen to on every N10 running the same Android version?
I have the same issue. If I slowly add one touch at a time, it usually works. But if I touch down 3+ fingers at once it gets very confused and bounces between zero and N touches. I have a Galaxy Tab 10.1 (first generation) and multitouch seems to work much better on it than the Nexus10. However, I did notice that the Nexus10 is better at distinguishing 2 very close touches than the GTab. On the Nexus10 I can have my fingers as close as 1/2 inch or so before the touches merge. On the GTab it is more like 3/4".
Hmm, kind of interesting to see that others are also having a similar issue.
I noticed that when I tried a custom ROM (latest Kernel sources + 4.2.1), the multitouch seemed to work, slightly better (the issue still occurs, just maybe not as much). Not too sure if it was placebo or what though.
I called the support and will replace mine with a new one. It might be just a software issue thats solved with an update but I don't want to risk it.
just got my replacement today, same issue (and also worst light bleed ). Third replacement on this way...
I really love this feature on the phone. So much that i have found myself doing it on my Nexus 7 and other devices thinking they'll wake too. Nope! Have any of you been knocking other things around? he
With so many other people that do not have a G2, they seemed to be concerned over the buttons on the back. with knock-on I really do not use the buttons on the back unless I need to reboot.
pilot85 said:
I really love this feature on the phone. So much that i have found myself doing it on my Nexus 7 and other devices thinking they'll wake too. Nope! Have any of you been knocking other things around? he
Click to expand...
Click to collapse
I actually caught myself doing it on my Nexus 7 today.
pilot85 said:
I really love this feature on the phone. So much that i have found myself doing it on my Nexus 7 and other devices thinking they'll wake too. Nope! Have any of you been knocking other things around? he
Click to expand...
Click to collapse
If you hack the N7 and if there are any PGM kernels available for it, you can have essentially the same thing (I think PGM uses a swiping action rather than knock knock, but its the same principle)
I rarely use the power button on the back, I love the knock on feature!
Theres been kernels since when I had an Htc Evo that had the slide to awake feature, couple of kernels for the One have it along with a knock on and off feature but it has a very small sweet spot, still it was the only thing that kept me sane since I had to strain and fumble my One to get to the power button. The most reliable method was the logo to sleep and awake, you had to actually press down just above the Htc logo and half the time you would end up hitting the application drawer icon. I didn't care for the swipe over the capacitative keys function.
G2 you can knock on and off anywhere which is what sets this function apart, yes you can tap up top on the status bar to have it work every time otherwise you just need to get your timing down on the double knock elsewhere. I love this feature from LG, it just makes sense regardless of where the power key is located but honestly I find myself using the power key sometimes just because I like the way it feels, its one of the best buttons I've ever pushed lol for lack of a better word.
geoff5093 said:
I rarely use the power button on the back, I love the knock on feature!
Click to expand...
Click to collapse
The knock on has worked for my about 99% of the time and I haven complaints. At most I tap a third time and never use the power button other then to reboot.
pilot85 said:
I really love this feature on the phone. So much that i have found myself doing it on my Nexus 7 and other devices thinking they'll wake too. Nope! Have any of you been knocking other things around? he
Click to expand...
Click to collapse
I love it!!!
pilot85 said:
I really love this feature on the phone. So much that i have found myself doing it on my Nexus 7 and other devices thinking they'll wake too. Nope! Have any of you been knocking other things around? he
Click to expand...
Click to collapse
i was actually at barnes and nobles earlier getting my niece a cheap nook tablet to use and tried to knock on the display model as im so used to it now. the clerk was looking at me funny so i had to pull out the phone and show her lol
Knock-on and it's counterpart Knock-off are a very convenient feature that I'm confident to say is the MOST convenient method of turning on a phone as of September 2013. If other companies don't follow suit in either a very similar fashion or something better, I would be surpr..... No, I'm sure other companies will do something very similar. It's really that good. Only thing I can imagine would be superior is having the phone read my thoughts. Err, wait!
xyltha said:
Knock-on and it's counterpart Knock-off are a very convenient feature that I'm confident to say is the MOST convenient method of turning on a phone as of September 2013. If other companies don't follow suit in either a very similar fashion or something better, I would be surpr..... No, I'm sure other companies will do something very similar. It's really that good. Only thing I can imagine would be superior is having the phone read my thoughts. Err, wait!
Click to expand...
Click to collapse
I can only think of one con of the knock on feature. I find that if I put my hand in my pocket or handle the phone without the intention of turning it on, sometimes part of my hand hits the screen twice and it will randomly turn on in my pocket or while in my hand. Not a big deal, I'm sure some software tweaks could fix the sensitivity.
geoff5093 said:
I can only think of one con of the knock on feature. I find that if I put my hand in my pocket or handle the phone without the intention of turning it on, sometimes part of my hand hits the screen twice and it will randomly turn on in my pocket or while in my hand. Not a big deal, I'm sure some software tweaks could fix the sensitivity.
Click to expand...
Click to collapse
If the phone is in the pocket the proximity sensor should still notice it's covered and knock on wouldn't work. At least that's the premise.
geoff5093 said:
I can only think of one con of the knock on feature. I find that if I put my hand in my pocket or handle the phone without the intention of turning it on, sometimes part of my hand hits the screen twice and it will randomly turn on in my pocket or while in my hand. Not a big deal, I'm sure some software tweaks could fix the sensitivity.
Click to expand...
Click to collapse
I have the exact same problem..
Not really when it's in the pocket but sometimes when I unmount my device from the car mount and put it in my pocket, I hold it with my thumb on the screen, leave the car and then dump it into my pocket. With my thumb on the screen, the screen turns on. The screen is especially sensitive since it's just been unplugged from the car charger.
This sucks, coz then it uses the capacitive screen sensor instead of the gyro sensor. It's not knockON. It's more like touchON.
Really hope someone or LG will come up with the tweaking of this.