This one really grinds my gears.
I use wired headphones a lot. and whenever I do and the phone is in my pants pocket, the thigh touching through the fabric of pocket turns on the screen many times. So I disable double tap to wake.
Every time I receive a call and phone is in my jeans front pocket, random buttons would be pressed. call would go on hold, or mute itself, or turn on speakerphone, or open keypad, turn on record etc.. and it is extremely frustrating. even more so when a business client calls me and I accidentally put him on hold because my phone is so stupid it does not understand not to turn on the screen touch. The proximity sensor works fine because when talking on call it will turn off the screen. just not the touch. My torch gets activated pretty often when pulling the phone out of pocket. this is so stupid infuriating.
The rest of the phone is amazing. I love the hardware. its pretty fast, runs games fine. camera is also very good. but the bloatware and the bugs are getting on my nerves.
This bug is from the day I got the phone.
Realme UI 3 update did not affect the bug but actually made it worse as the torch triggering issue has gotten worse.
I have not encountered any major bugs in the new update apart from a bluetooth volume fluctuation bug.
Am I alone having this issue?
PS: I forgot to mention that several times the quicksettings toggles are also triggered Like Data/Wifi turning off, VPN getting activated, Airplane mode turning on etc.
Related
is there anyway to lock this phone so when its in your pocket and you're jamming out to some tunes, the screen doesnt turn on or the volume doesnt change? I've had this phone unlock it self and its beyond annoying. Also the screen will be off, phone locked, and if i get an email or text or what ever, the screen comes on every time. It didnt bother me at first but its starting to get to me now.
Tell me about it. My Note 1 pocket dialed 911 recently; I noticed a stern voicemail an hour later telling me if it was a real emergency to dial back. For those who don't know, when you use a PIN lock, an "emergency dial" button shows up, and one swipe and a tap in the right place can dial 911 (the Note 2 / JellyBean helps by not having "911" as a single-tap choice).
Anyway, couple things you can try. The flip screen protector (from Samsung) will prevent inadvertent screen presses while in a pocket. It works very well, though I personally don't really like having to flip open a cover on top of a phone this size.
It might be possible to use another SMS app like Handcent that won't turn the screen on when you get a text, but I haven't verified that. I haven't figured out how to prevent the screen from lighting up when a text comes in using the stock app, but the flip cover would prevent any screen taps from happening when it does.
I tried a proximity lock (turns screen off when prox sensor is activated), which worked, but there is some odd behavior. When you get a text and the screen kicks on, the proximity sensor app doesn't know you want the phone to go back to sleep, so I think it prevents deep sleep after that (battery drain?). And it also interferes with the phone's ability to use the proximity sensor during phone calls, so after the first phone call and subsequent proximity lock, it no longer works at all during calls until the service is restarted. You might experiment with these though. There's one called "ProximityService 2.1" (Google it since it was released in a Droid forum IIRC) and others are available in the market.
No software tips on the volume buttons, but if you get a TPU style case the cutouts will make them less likely to get pressed. I wish they were recessed just a little more or harder to press. I don't like the TPU cases because they add bulk to the phone.
Looks like this will come to a hardware problem.
I noticed I was missing calls because the vibration on my G3 was not working.
I downloaded a vibrate test app and it has two options. One long vibration and one constant short vibration.
My phone refuses to vibrate sometimes, but if I shake it, it starts vibrating for a short time (testing the short vibration option)
If I use the long vibration and shake it, it vibrates "infinitely".
When it works properly, the vibration looks stronger.
In other words, it's look like a battery that it's not properly placed.
It's weak/not working but works sometimes.
TBH, it has been very weak/not working in the last few days.
Should I search for a assistance center and ask for a changing on my G3 vibrate motor,
or should I try anything special (Lollipop bug)?
Hey, I have the EXACT same problem. Everything you described... how you shake it on long vibrate it will vibrate infinitely regardless of shaking it afterwards. The app you're using is "Test Your Android" am I right? Well I have the exact same problem as you and it's causing me to miss calls and notifications every day.
I doubt it is a hardware problem because shaking it allows it to vibrate forever. I tried shaking it while vibrating to see if there is something loose or not well placed, but shaking as hard as I can while it was vibrating did nothing. Maybe software errors involving shaking the phone and vibrating?
Theory # 2: Maybe the "Long Vibration" allows it to constantly come "unloose" thus why when under long vibration it doesn't stop, but the short vibration stops because it pauses every so often.
G3 Vibrate not work - all answers including software and hardware
When I make or receive calls the screen turns black and the touchscreen is disabled. I assume this is to avoid accidental keypresses with my ear or something, but my phone doesn't leave this mode until call ends.. I assume it would switch on screen/touch when leveled horizontally, but it doesn't.
I cannot end the call or do anything while the screen is disabled.
The only thing that works sometimes is to double press power button to turn on camera (thus enabling screen/touch), but it is no reliable method.
Sometimes, if I call a person not taking the call, without mailbox or automatic termination of connection, I have to reboot to phone to end this.
Any idea what I can do? Can this supposedly helpful behavior be switched off or fixed?
I am on Android stock 8.1.0 (OPM6.171019.030.H1, Aug 2018), rooted with most recent Magisk.
This bug is driving me nuts, so Thank You for any ideas or help!
Is there anything blocking the proximity sensor (below the right of the speaker)?
nowster said:
Is there anything blocking the proximity sensor (below the right of the speaker)?
Click to expand...
Click to collapse
Not that I know of. All is as normal as can be.
But right now, it seems the "trick" with the camera double click works more reliably (>50%) than before. Whatever reason..
If you've had the phone apart recently ... check proximity sensor. There's a little rubber piece tends to fall out.
Did You applied a screen protector recently? I had the same issue because of screen protector was covering the proximity sensor
During phone calls while using the phone on my ear, the screen will dim like normal and touch is not responsive... But after the call, I move the phone away from my ear, the screen will not wake-up and requires waking with power button. I can only recall a handful of times where the phone acted normally after a call...
Anyone else experiencing this? I am rooted w/ magisk and I have verified the proximity sensor is working (using Droid Info app) -
I am turning off adaptive battery not only to see if it helps with this concern, but overall performance and will update w/ changes
Had this happen as well. Not rooted. Can't remember but i vaguely recall this with other versions of android
mcgleevn said:
During phone calls while using the phone on my ear, the screen will dim like normal and touch is not responsive... But after the call, I move the phone away from my ear, the screen will not wake-up and requires waking with power button. I can only recall a handful of times where the phone acted normally after a call...
Anyone else experiencing this? I am rooted w/ magisk and I have verified the proximity sensor is working (using Droid Info app) -
I am turning off adaptive battery not only to see if it helps with this concern, but overall performance and will update w/ changes
Click to expand...
Click to collapse
got a crappy screen protector? that'd be my guess
Nope nothing, naked
mcgleevn said:
Nope nothing, naked
Click to expand...
Click to collapse
Same. And it doesn't happen every time.
Right after I posted this, made a phone call and it blacked out again this time no power button, double tap, shake, twist, etc would wake the phone. Eventually after about 2 mins it woke up again...
Possibly unrelated, but about every 1 in 5 reboots my screen won't turn on. Stays black, no back light. The phone still responds to ADB and fastboot commands, but nothing will turn the screen on until I hold down power to restart.
Same here.its happened multiple times. naked Pixel here, not rooted. its annoying.
I've made/received 100 calls since Thursday, and it happened for the first time last night. I was able to get it out of black by accidentally doing a screenshot while trying to reboot.
Happened at least 4 times today. Just noticed an update to the Phone app was released, let's see if that makes a difference.
No screen protector, etc.
honestly after some more calls with this issue, i think my dirty ear and is causing the close proximity reading... after the most recent episode, i went to the droid info app and it was reading the sensor at 0 cm and after wiping the notch off, it started to read correctly (5.0 cm) >>> i dont really want to give the haters another reason to dog the notch but, in my case, i think its going to be an issue. i may switch the "power button to end call" on and see if that will alleviate my issue for now -
mcgleevn said:
Right after I posted this, made a phone call and it blacked out again this time no power button, double tap, shake, twist, etc would wake the phone. Eventually after about 2 mins it woke up again...
Click to expand...
Click to collapse
Same exact thing happened with me yesterday, could it be a RAM management issue?
Roll3r said:
I've made/received 100 calls since Thursday, and it happened for the first time last night. I was able to get it out of black by accidentally doing a screenshot while trying to reboot.
Happened at least 4 times today. Just noticed an update to the Phone app was released, let's see if that makes a difference.
No screen protector, etc.
Click to expand...
Click to collapse
Thanks for the heads up. I have unrooted and naked 3 XL. This screen off thing was affecting all calls. If the remote party hung up, I was fine. If I got into someones VM, I had to sit quietly until the call dropped.
I added myself to the Phone app Beta program and updated. After several test calls, I think it's fixed.
Is anyone else having issues recently with their pixel 2XL being able to detect their face against it on a call.
Sometimes I'll be on a call and feel my phone vibrate and when I peek at the screen, I can see the screen is on and it's on a random page like my alarm settings, because my cheek pushed against a button on the home screen for example.
Also, when pulling the unit away from my face sometimes the unit doesn't light back up and i have to push the physical on button to get it to turn on.
Or even worse this week, I've noticed that after my phone doesn't light back up when I pull it away from my face and I try to turn it back on with the on button, it doesn't work... the screen never turns back on, I have to double push the button to get the camera to pop up and then dismiss it to get back to the home screen.
It's getting pretty frustrating. Has anyone had this issue? Anything I can look into to fix this?
I`ve been having this random issues with the proximity sensor and my phone not able to charge with the stock charger.
The proximity sensor is right by the ear piece so if you have your ear touching first it should, in theory, turn off the screen before your cheek touches the screen. Personally, I don't have my cheek touching at all while on a call but I have a slim face.
Sent from my Pixel 2 XL using Tapatalk
Download a sensor test app and check for proximity sensor. I had a similar issue some time back. Reboot fixed it for me.