Hi all,
I absolutely love my Gnex. I got it on launch day, and for the most part I have not had a ton of issues. However, there is one thing that I am having a hard time dealing with, and I'm hoping someone will be able to help me with it. When I dial a number with the stock dialer I have no issues at all. After I connect and when I need to bring up the number pad to enter extensions, voicemail, or whatever else, my number pad "short circuits." I only can describe it like a flickering everytime my fingers come close to push a number. It disappears when I go to push them and reappears when I take my finger away. I almost have to time it right when trying to access my voicemail just to push the numbers I need. I have tried holding the phone in different locations because I am aware that there is a proximity sensor....but it seems to me that what is happening really shouldn't be. Is there a setting I can change? Any assistance that can be provided would be greatly appreciated.....I really would like to clear this issue up as its the only thing from making my GNex close to perfect.
Thanks!
Is there a screen protector blocking the sensor? Some of the cheap ones block then sensor and screw with it.
Nope. No screen protector as of yet. I purchased the XO Skin but have yet to put it on.
I have hung up a few calls as well.
I think the proximity sensor works but it seems to be slower than the average phone. Hopefully this is something that could be fixed with a software patch.
Punchup- Is it anything like this?
http://www.guytechie.com/articles/2012/1/22/galaxy-nexus-slow-proximity-sensor.html
OP- Mine did that once but i couldnt reproduce it on the next reboot.
Naddie that is exactly what is happening!
It is good to know so I can avoid doing it but I do hope they fix it in a patch. Thanks!
Related
I know the proximity sensor is not functional with the Rhodium400. My wife and I are both running the newest version FRX 7.1 on the .27 kernel.
She had issues with Windows Mobile getting a data connection, and it would carry over to Android. So I dd a hard reset on Windows Mobile and started her Android from scratch (as it was having other slowness and issues also). Ever since then she tells me (and I have heard this in call) that every time she puts her cheek or face to the phone it will sound as if the call dropped but it doesn't drop really. She can't hear me and I can't hear her, but as soon as she takes her head away she and I can both hear again. This doesn't happen all the time, and is likely only happening when XDAndroid has not been rebooted in a few days.
I have not been able to confirm it by sitting right beside her and calling and confirming the problem, but I plan to do so tonight. At first I thought she was just muting me because she was ticked at me...don't ask , but she isn't smart enough to come up with something like this, because technically it sounds like the proximity sensor is mucking up the phone call which I thought was not possible from everything I have read. I even had her turn the power button off at the top to turn the screen off, to make sure she wasn't bumping any buttons. The way it looks, it almost sounds as if the phone is inadvertently trying to place another phone call and putting the first phone call on hold.
Has anyone else had this issue? Doe anyone think this is likely a proximity sensor issue, or have any advice for when I get home tonight and start playing with the phone?
Supposedly also this issue was going on with her in the car and the phone plugged into a car charger. She called me back with it not on the charger and it is not messing up anymore. I don't know if it is coincidence or not, since it wasn't always doing it to begin with.
Never heard of this, almost sounds like a hardware failure.
Run WinMo for a few days, see if you can recreate the problem there. If so, there's something going haywire with the physical hardware.
I get a situation kind of like this in Android, but not WinMo. Basically if I recieve a call it's about a 50/50 chance that this happens. I can't hear them and they can't hear me. There is no sound at all, like the speaker and mic don't even turn on. However, mine doesn't seem to have anything to do with the proximity sensor as it does it as soon as I hit the answer button and moving the phone away doesn't fix it. Also, it's only when recieving calls, outgoing calls work all the time.
I've had similar problems, but quite a bit in the past, making me think mine was software or settings. So don't discouraged!
My thinking is, since auto-mute to rear speaker/mic system is a 'feature', that maybe that system gets triggered. Check those settings, and that level/bubble calibration stuff.
Hello,
The screen of my moto 360 goes randomly off and vibrates at that moment, just like when you dim the screen with your hand., but now I'm using it. It's very frustrating because I can't even open an app normally or the screen goed of and I need to start over again. Does anyone know how to fix this?
Having same issues with mine.
Really strange and really annoying. Its like when u cover it with palm. It vibrates and screen goes off but ur in the middle of trying to do something. Anyone else having this problem?
Glad I'm not the only one having this issue, just got my Moto 360 today. I'll be in the Settings or other parts of the watch and it will just randomly turn off. It is really frustrating to deal with.
I have the same issue. I have pretty hairy arms so I wonder if the hairs are somehow triggering the capacitive touch screen.
you guys try to do a reset on the watch yet?? not just a reboot..
Any updates on this? I'm having the same issue
Any updates? I have the same issue I think it happend after udate to 5.0.2 but I'm not sure.
I'm also having the same problem. I picked up a new Moto 360 during the BBY sale rush of the last couple of days. At first it was buggy but the screen seemed to stay on while working with it. Then it had a system update, and since then most bug issues (like the faces not updating with the companion app changes) went away, however from that point the screen constantly shuts off, usually with a little buzz, while I'm interacting with the watch.
For instance, regarding the sensor used to turn off the watch if you palm it. I thought maybe that was it, so I was looking for a way to turn that off. I went into settings, and spend about 10 times of the screen shutting off before I could get to "accessibility settings" just to see if that might be there.
This problem occurs whether I'm wearing the watch or not (trying to eliminate arm hair or similar), and has occurred after a factory reset and re-pair with my phone (Note 4). Ambient sensor settings don't help, because all that does is make the screen go dark instead of off, but it still reverts back to the clock no matter what I was doing.
Any ideas? Any way to turn off a sensor perhaps, maybe in a custom ROM? Since this seems to be associated with an update near as I can tell, I wonder if a fix is coming from Moto or if it's too rare of an issue to be on their radar.
As an update, I replaced the watch with a new one, and this new watch is perfect. It started on outdated software which I left on for a bit to make sure it didn't show the problem, then I updated. Still no issues. I think there is a chance the problem is software regardless, but either way it must be a small portion of watches and isn't necessarily tied to any particular outside software influence (phone model or android version, or installed apps as NONE of those things changed). My advice to people reading this thread is to exchange the watch or get an RMA if possible.
Same Issue
Hi All,
I have the same issue. Sent it back for repair so let's see...
Same issue here as well
Hi,
I have a UK sim free model. It sometimes misinterprets a tap or adds a phantom tap. Its not terrible but I'm sure mine has a issue. A quick Google and a tweet tell me I am not alone. Anyone else seeing this? I could return but I'm dubious it's hardware related...just not sure if it's worth waiting for a software update...
RealEvil_UK said:
Hi,
I have a UK sim free model. It sometimes misinterprets a tap or adds a phantom tap. Its not terrible but I'm sure mine has a issue. A quick Google and a tweet tell me I am not alone. Anyone else seeing this? I could return but I'm dubious it's hardware related...just not sure if it's worth waiting for a software update...
Click to expand...
Click to collapse
I have same issues with my g4 here in the US.
Unfortunately same here, on a G4, korean model F500S.
I have the same issues on my G4. So probably returning it won't solve it. I notice it the most when I am scrolling in Facebook or web pages I will open a link accidently.
I have the same, occasionally it just won't respond to some taps, i find just pressing the standby on/off button quickly sorts it but it is very annoying.
same here in israel, sometimes do not respond to double tap on lock screen to wake the G4 up
im sure its a software issue, prolly the LP 5.1
Are so you guys using screen protectors? That was the issue for me with g3 and g2.
20degrees said:
Are so you guys using screen protectors? That was the issue for me with g3 and g2.
Click to expand...
Click to collapse
I am using the out-of-the-box protector on G4. So the thing u mentioned was it with this kinda protector or after-market glass protector?
Try...SGS Touchscreen Booster - Google Play Store
I have run into this same problem with my Verizon G4 (VS986). Many of my taps have gone unrecognized.
I did find this.... http://forum.xda-developers.com/g4/help/fix-touch-screen-registering-touches-t3128518
I tested the software that was recommended...and IT WORKED!
Give it a try...can't hurt!
nipun1110 said:
I am using the out-of-the-box protector on G4. So the thing u mentioned was it with this kinda protector or after-market glass protector?
Click to expand...
Click to collapse
After market but plastic.
Just started to get issues where taps on the far left-hand side of the screen don't work.
blackknightavalon said:
Just started to get issues where taps on the far left-hand side of the screen don't work.
Click to expand...
Click to collapse
Okay, I was able to replicate my bug. It happens after playing a game and stops after some time. Turning autorotate back on and switching back and forth from landscape view fixed it.
Hey guys.
I was searching the forums for a fix that solves the phantom/ghost touches I'm getting frequently on my LG G4, H815 model.
Sorry for the long post but my case looks a little more complex than the ones I've been seen in here.
In my case, that's how it happens:
I receive several multi-touches at the same time, usually when Data is enabled. Sometimes it starts right when I switch from Wi-Fi.
It happens often when I'm driving and using Location+Data as well, which drives me crazy. I does also happens (like another user mentioned in this thread) when scrolling down a feed (such as on Facebook) and it suddenly likes/shares a photo/post. It also drives me crazy! And there is also the case where it taps the keyboard and send crazy typos on chat apps when you are real-time texting someone! Another hassle is right after using the camera and opening the gallery to show someone the taken photo...it suddenly scrolls the gallery and open another photo. I just can't make it to see the taken pic. Therefore, I really wanna fix this so bad since it happens every time I need something right away.
A workaround that's been helping, though it's a pain:
I found that pressing the On/Off button and giving it a few seconds will return it to a normal state. The problem is when it happens while I'm driving and are supposed to take an exit/make a turn at the moment. There are some other cases where I'm into something and giving this few seconds is not an option.
Trying right now:
Someone suggested in this thread to use the SGS Touchscreen Booster. I'm giving it a try right now.
Important notes:
This issue has been happening since I got this phone on November, 2015. We got this 6.0 update recently and I was hoping that it would fix it. It didn't.
I have an after market screen protector that I applied in order to see if the issue would go away. It also didn't.
I have been searching about a digitizer replacement but I don't think is a hardware issue, since it just doesn't happens when I'm only on Wifi at home with Data disabled. I believe that the problem is the Data connection that triggers smth.
Any thoughts?
Does anyone have any idea or have experienced the same scenario before? Any thoughts on my guess of data enabling triggering the ghost touches?
Sorry for the long post and thank you so much for reading it.
I think it's both, its hardware and software, LG tried to fixed it but it makes it worst. You can solve the problem for few seconds putting your five fingers at the home menu, It goes crazy and after it stopped making ****. Anyway this phone is great but all the problems make it ****.
I am going to use this thread even though I think my problem is not as serious as yours are.
My problem is that touches are registered, but no action is taken.
For example. Quickly tapping on an icon on the home screen will highlight it, but it will not open the application. I enabled the option in Developer mode to display the touches and the touch is registered. It's just that the app will not load. If I click for a tad longer - it loads. Happens on both stock Launcher and Action Launcher. I have not noticed it happening outside the launcher.
I read something about a keyboard update, but in the Update Center I don't have anything related to the keyboard.
The icons I see it happening with are located in the lower part of the screen.
I am almost sure that this is a software problem, but several updates have not fixed it. Currently on v20d.
Any suggestions or ideas?
After a few more testing and monitoring, I found out that the ghost touches only take place when I'm on LTE.
And even more weird, while driving through some specific areas when I'm commuting.
It's just so weird to think that some towers may send a LTE signal that may cause the ghost touches.
At home, at work, wifi or data, it doesn't happen.
This has been annoying since I got the phone 7 months ago.
It doesn't turn off the screen when I take/make a call. I'm constantly putting my caller on hold or even hanging up with my ear or cheek. I've Googled the crap out of this and I've found MANY different settings to check/change - NONE of which exist on this phone.
So does anyone know? Is this simply not a feature of this phone?
Thank you.
bcsteeve said:
This has been annoying since I got the phone 7 months ago.
It doesn't turn off the screen when I take/make a call. I'm constantly putting my caller on hold or even hanging up with my ear or cheek. I've Googled the crap out of this and I've found MANY different settings to check/change - NONE of which exist on this phone.
Click to expand...
Click to collapse
I thought it was just me! I haven't looked for a solution as yet, but if you find one please post back here and share.
Actually I did resolve it finally! I installed a different dialer app and it worked with it. I hated the app though, so I uninstalled it. Before I had a chance to find a different app, a call came in (using the default app again) and it worked as it should. I can't explain why, but for me... installing a different app and then removing it got the default dialer to behave correctly.
Now that it works "correctly", I have noticed a quirk with it. I have to wait for an outgoing call to actually be ringing (which can take some time with some calls) before I put it up to my ear or the screen won't shut off until I bring the phone down and then back up. Now, it is *possible* that this was always the issue and I just never figured it out. So maybe the whole app install/uninstall thing is unnecessary. Not sure.
bcsteeve said:
Actually I did resolve it finally! I installed a different dialer app and it worked with it. I hated the app though, so I uninstalled it. Before I had a chance to find a different app, a call came in (using the default app again) and it worked as it should. I can't explain why, but for me... installing a different app and then removing it got the default dialer to behave correctly.
Now that it works "correctly", I have noticed a quirk with it. I have to wait for an outgoing call to actually be ringing (which can take some time with some calls) before I put it up to my ear or the screen won't shut off until I bring the phone down and then back up. Now, it is *possible* that this was always the issue and I just never figured it out. So maybe the whole app install/uninstall thing is unnecessary. Not sure.
Click to expand...
Click to collapse
I had a same problem too, but did resolved after factory reset. But I don't know where is the problem located, maybe the proximity sensor is very sensitive even with dust.
Sorry, bad English.
Your English is fine
I think you might be right, because my problem now seems to come and go. The screen definitely shuts off, but there's some times when my face will put the call on mute or other strangeness. I've even accidentally sent an email to my Mom, all with my cheek while on the phone with someone else! I had to click the back button 6 or 7 times to get back to the phone screen.
This phone was good value, but I do regret the purchase.
The proximity sensor is very sensitive, even with a very small string. I just test this when I call my second phone. And moving around my finger, and boom! My screen is turned off, but did turned on again after I moving away my finger. This is surprising me when I call my mom, and I force to turn off my device, and it's rebooted. After my device is successfully booted, I tried to call my Dad, and surprisingly the screen is not turned off. So I'll try to find the problem, and I founded them:
The proximity sensor is very sensitive, so be sure to wipe the proximity sensor until it gets clean completely.
That's it, so no matter if you use a different dialer or default dialer for your device, just keep in mind that I mentioned there.
Thank you. As always, sorry for my bad English.?
Been using the phone for the last 12 hours and I noticed something towards the end of my use last night.
The screen seemed to become unresponsive. And when it would work it would start to make its own input when scrolling and opening any app or link my finger would drag over while scrolling.
Changed refresh rates, changed resolutions, even seen if the blue light filter was the issue. Nothing.
Almost seems like the screen drops frames when scrolling, like it gets caught on something.
New development. Fingerprint sensor doesn't respond at all and inputting a pattern is damn near impossible. Going to try removing the screen protector to see if that could also be the issue
Did a factory reset
Issue seems to be where the finger print scanner is
It's almost like a dead or unresponsive zone.
Sounds like a factory defect, better have it replaced if resetting didn't worked.
Small video showing when scrolling over the fingerprint reader, the screen almost loses input
Defect.
Samsung has been little help lol. They want me to send it in for repair instead of an exchange. They also said to just order a whole new one and return the one I have now except the black 128 is sold out
imtjnotu said:
Samsung has been little help lol. They want me to send it in for repair instead of an exchange. They also said to just order a whole new one and return the one I have now except the black 128 is sold out
Click to expand...
Click to collapse
Sounds like Samsung support LOL...sorry you're having issues
Did you remove the factory installed screen protector? Maybe it's the cause of the issue
Return that pal, that doesn't sound good at all.
lovers74 said:
Did you remove the factory installed screen protector? Maybe it's the cause of the issue
Click to expand...
Click to collapse
one of the first things i did to trouble shoot. still having the issue. sometimes the screen completely loses all touch registration and it doesnt even know im trying to swipe or push on things. just realized it did this also after tmobiles new software update.
im still waiting here to hear back from samsung on how they are going to fix this issue
The same thing happens to me. Pulling down the notification shade seems to be the only thing that still works. It seems to goose the phone and it starts working again.
Test using the *#0*# diagnostic menu and use the Touch test.