Related
I tried flipping the phone over to use speakerphone yesterday and found that it didn't work. I do have PocketShield and ChangeScreen installed - does anyone know if either of these apps can interfere with the flip-over speakerphone feature??
I at first thought the same. Just in case .. I found that the phone has to be perfectly level (g-sensor) and on top of a table or similar flat surface.
itm said:
... I do have PocketShield ...
Click to expand...
Click to collapse
Most probably it is cause by PocketSheild. I had it installed before, and causing lots of intermittent problem.. i know PocketShield said it support Tp2... but it dont really works well. end up i removed it and thing back to normal.
You might want to try to disable the "Gesture unlock feature" in PocketShield. Doing that will completely disable g-sensor usage which might be interfering with the flip action of the TP2.
Also try disabling ChangeScreen, as far I know this app will constanlty read the g-sensor to determine orientation, that could also be the cause.
I was checking voicemail today.. put in my password thru the keypad.. and then once i put the phone back next to my ear.. i kept pushing the keypad buttons with my cheek. until the promixity sensor caught on..
anyone else getting this prob? just an fyi.. i have the SGP Oleophobic Screen Protector on my phone.. i'm not sure if that decreases the reaction time for the sensor or not.. but its a pain..
No mine does that too. I've been using google voice to keep my old number, which asks to hit a 1 or 2 to accept/decline thus keeping the keypad up.
When I'm on a call and shufflin' (everyday I'm shufflin') sometimes the screen pops back on with my face on it and all of a sudden you'll hear a bunch of tones over the phone. lol. Everyone asks, "What was that?!" and I just giggle and say, "Don't worry about it" or "I didn't hear anything" lol.
But yea. It's a tad slow. Probably just a setting. I'm sure it'll get fixed soon.
I thought I was the only one experiencing this issue! I had this proximity sensor issue on my Iphone 4, but it was hardware related. This only appears to occur when the dialpad is still on during a voicemail or phone call. This is BEYOND ANNOYING and I hope that Google is able to address this via software fix. I'm surprised they let this one slip through the cracks.
Proximity sensor slow
Yep. Mine too.
I just found out why this is. The GNexus requires the phone to be upright before the proximity sensor will turn off the display. If it is laying flat, it won't work. Because of the complexity (the requirement to satisfy both conditions), it seems to react slower.
The hardware itself isn't the problem. It's the stock dialer.
To demonstrate, I made a video. I used the stock dialer and GrooVe IP (a dialer I use for Google Voice). GrooVe IP turns off the screen right away when I put my hand over the proximity sensor. Also, it does not cause accidental ear dialing.
I hope Google will fix this in the next update. It's certainly by design (a bad decision), and can be fixed by software.
http://www.youtube.com/watch?v=cjTGQaK1Qvw
This thread is pretty dead, and I haven't found too many other posts regarding this issue. I'm shocked to not see any replies, including the ones who already wrote in this thread. I was hoping to get some confirmation if their "slow" responding phones are also exhibiting this correlation with the accelerometer.
Is this not a wide spread issue? Is what I demonstrated not expected behavior? Do I need to exchange my phone?
I hope not - I bought this from a Amazon merchant, so I don't know how hard it is to get warranty work done (since it's imported).
I'm in the US, and this is a GSM version. We only have the CDMA version (Verizon) officially.
Forgot to post here regarding this issue. Not fixed, but I think it's more of a software issue than hardware. I wrote and made a video that might explain why I think it's a software issue:
http://www.guytechie.com/articles/2012/1/22/galaxy-nexus-slow-proximity-sensor.html
naddie said:
This thread is pretty dead, and I haven't found too many other posts regarding this issue.
Click to expand...
Click to collapse
Probably because no-one else has this problem? I know I don't anyway, mine is always instant and works flawlessly. Sounds like a hardware issue or your screen protector?
case0 said:
Probably because no-one else has this problem? I know I don't anyway, mine is always instant and works flawlessly. Sounds like a hardware issue or your screen protector?
Click to expand...
Click to collapse
It's an issue for me, no screen protector and the timing's almost sporadic when holding it naturally. But it could also be how I hold it as said earlier in the thread
I also have the same issue when checking voice mail. My damn cheek always hits a number or some button after putting in my pin.
Screen orientation in general seamed slow to me on 4.0.2. 4.0.4 speeds things up a bit, it's listed as one of the improvements.
Same issue here. I just tilt the phone so that the top (where the sensor and speaker are) touches my ear for a second, then flatten the phone against my cheek. This gives the sensor time to activate and never results in accidental keypresses.
Sent from my Transformer TF101 using xda premium
ericshmerick said:
Same issue here. I just tilt the phone so that the top (where the sensor and speaker are) touches my ear for a second, then flatten the phone against my cheek. This gives the sensor time to activate and never results in accidental keypresses.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
this is what i do too it's a pain though - i hope we get 4.0.4 in the UK on o2 soon! im tired of waiting for faster screen rotation and more responsive proximity sensing
All my P sensor issues were fixed after flashing the PrimeLA03 bootloader.
Hi people. I have the same issue on 4.0.4 (Stock OTA).
The proximity sensor shows no output after testing it with "Sensor List" and with "Elixir 2".
Any ideas? Thx.
I have this issue too!
I have it too, I just tilt the phone to touch the ear first and then bring it close to my face.
edit with a rom
If your using a Rom like AOKP, you can edit it to be faster and better in your desired ways.
Done it and it works the second I raise my phone to my ear when necessary.
Emergency Call from lock screen
Never had a problem GV or the stock phone but the orientation affecting the proximity sensor might explain why I am making emergency calls from the pattern lock screen.. wish there was at least a simple swipe needed to make the emergency call.
naddie said:
I just found out why this is. The GNexus requires the phone to be upright before the proximity sensor will turn off the display. If it is laying flat, it won't work. Because of the complexity (the requirement to satisfy both conditions), it seems to react slower.
The hardware itself isn't the problem. It's the stock dialer.
To demonstrate, I made a video. I used the stock dialer and GrooVe IP (a dialer I use for Google Voice). GrooVe IP turns off the screen right away when I put my hand over the proximity sensor. Also, it does not cause accidental ear dialing.
I hope Google will fix this in the next update. It's certainly by design (a bad decision), and can be fixed by software.
Click to expand...
Click to collapse
Not fix even on 4.1 ...
I've been smashing my head over this to no avail. Prior to side loading 8.1, when my phone rang the caller and swipe up/down would appear on the lock screen, now it rings, but nothing on the lock screen till I wake it with the fingerprint sensor. Did I miss something? Was this changed? I've been through the settings and still can't see anywhere that I missed. This a security feature so no one can see who's calling till you hit the sensor? Any feed back would be appreciated.
I agree surprised more are not annoyed...lol
Doublecore said:
Well it seems it's only happening when connected to Bluetooth. I hadn't noticed since I'm connected to my headset all day at work. Disconnected from Bluetooth and had my wife call me...screen popped right on. So it's another Bluetooth bug I guess.
Click to expand...
Click to collapse
I tested incoming phone calls with and without bluetooth, and came to the same result. Since it's very annoying for the screen to not turn on, I ended up making a macro with Macrodroid to turn the screen on when a call comes in. This workaround will be sufficient for me until Google fixes the bug.
I posted on this same issue last week. It's the last update to Google Phone app that broke this. I don't have the time to report it to them...so hopefully it gets fixed!
https://forum.xda-developers.com/pixel-2-xl/help/google-phone-update-bug-t3718424
*Edit- To fix(?), uninstall the phone app and it will remove the update. Should work then. Of course you won't be able to use Duo for video calling within the dialer...but I couldn't care less about that.
I just had this happen yesterday. Here is a work around with Tasker and Secure Task to wake screen on incoming call.
Import it in Profiles tab in Tasker and make sure you have Secure Task and have it configured with adb.
5150jpd said:
I've been smashing my head over this to no avail. Prior to side loading 8.1, when my phone rang the caller and swipe up/down would appear on the lock screen, now it rings, but nothing on the lock screen till I wake it with the fingerprint sensor. Did I miss something? Was this changed? I've been through the settings and still can't see anywhere that I missed. This a security feature so no one can see who's calling till you hit the sensor? Any feed back would be appreciated.
Click to expand...
Click to collapse
This may be related to the Proximity Sensor bug introduced with 8.1. Do you have a screen protector on your device? Does it cover the PS?
Nope.. No protector on phone at all.
v12xke said:
This may be related to the Proximity Sensor bug introduced with 8.1. Do you have a screen protector on your device? Does it cover the PS?
Click to expand...
Click to collapse
It started for me on the Google Phone update to version 15 on Dec. 14th. I never had this issue on 8.1 that I did the OTA sideload when I got my phone on Dec. 4.
My proximity sensor is fine. Even with always on display, AOD goes off in pocket and turns back on when I pull it out. On a phone call the screen blanks when I put it to my ear and wakes when I pull it away from my head.
Yep -- I just ran into the problem today as well. I've got 8.1.0 on my Pixel 2 XL, and I get this behavior (display not waking up for incoming call) when connected via Bluetooth -- to my car, headphones (Sennheiser PXC 550) or to my Jabra Speak 710 BT speakerphone.
I considered trying Drupe or Truecaller, but then I read that packet sniffing tests show them sending your contacts data off their servers...so I think I'll wait for a fix from Google. Really annoying. There are a couple of threads on this in Google's product forums / Pixel User Community:
https://productforums.google.com/fo...QEn6fH0OI;context-place=forum/phone-by-google
https://productforums.google.com/forum/#!topic/phone-by-google/hdmLGWSMhSM;context-place=topicsearchin/phone-by-google/category$3Adevice-performance%7Csort:relevance%7Cspell:false
So far, Google doesn't appear to be weighing in with any useful commentary. The only "fix" for now seems to be "uninstalling" the phone app (which just reverts back to the OEM installed version) and then not accepting updates to the app. But I've read that this can spin up other issues.
jonstrong said:
Yep -- I just ran into the problem today as well. I've got 8.1.0 on my Pixel 2 XL, and I get this behavior (display not waking up for incoming call) when connected via Bluetooth -- to my car, headphones (Sennheiser PXC 550) or to my Jabra Speak 710 BT speakerphone.
I considered trying Drupe or Truecaller, but then I read that packet sniffing tests show them sending your contacts data off their servers...so I think I'll wait for a fix from Google. Really annoying. There are a couple of threads on this in Google's product forums / Pixel User Community:
https://productforums.google.com/fo...QEn6fH0OI;context-place=forum/phone-by-google
https://productforums.google.com/forum/#!topic/phone-by-google/hdmLGWSMhSM;context-place=topicsearchin/phone-by-google/category$3Adevice-performance%7Csort:relevance%7Cspell:false
So far, Google doesn't appear to be weighing in with any useful commentary. The only "fix" for now seems to be "uninstalling" the phone app (which just reverts back to the OEM installed version) and then not accepting updates to the app. But I've read that this can spin up other issues.
Click to expand...
Click to collapse
Have you tried the tasker profile from post #7 by Pkt_Lnt? That fixed it for me.
JimSmith94 said:
Have you tried the tasker profile from post #7 by Pkt_Lnt? That fixed it for me.
Click to expand...
Click to collapse
Thanks. If this issue goes on much longer, I'll probably try that. Oddly enough, despite having played with custom Android ROMs and modding over the years, I never used Tasker -- concerned that having the add'l service(s) running in the background around the clock would be more of a battery drain.
I updated my phone app yesterday, and the screen lights up again upon receiving a phone call. I disabled the macro that I made in Macrodroid just to make sure.
EMcTx said:
I updated my phone app yesterday, and the screen lights up again upon receiving a phone call. I disabled the macro that I made in Macrodroid just to make sure.
Click to expand...
Click to collapse
Thanks for the info. My phone app updated too, so I'll disable the Tasker profile and see if it lights up without it for me too.
Is there a xposed module to disable the stupid proximity sensor? I'm having some issues with it. It does not wake my screen up when I pull it away from my face.
EMcTx said:
I updated my phone app yesterday, and the screen lights up again upon receiving a phone call. I disabled the macro that I made in Macrodroid just to make sure.
Click to expand...
Click to collapse
JimSmith94 said:
Thanks for the info. My phone app updated too, so I'll disable the Tasker profile and see if it lights up without it for me too.
Click to expand...
Click to collapse
Reports on G+ state it fixes the issue. I've not seen v.16 yet.
https://plus.google.com/u/0/+ArtemRussakovskii/posts/byEHovfFbMj
My last name starts with "S" too, not sure why Jim gets priority over me. I always get updates late, which is why apk mirror is bookmarked. :good:
Pkt_Lnt said:
Reports on G+ state it fixes the issue. I've not seen v.16 yet.
https://plus.google.com/u/0/+ArtemRussakovskii/posts/byEHovfFbMj
My last name starts with "S" too, not sure why Jim gets priority over me. I always get updates late, which is why apk mirror is bookmarked. :good:
Click to expand...
Click to collapse
Oops, mine was still on v15 so thanks to you, I just installed v16 from your link. See there, you're still da man! :good::highfive:
JimSmith94 said:
Oops, mine was still on v15 so thanks to you, I just installed v16 from your link. See there, you're still da man! :good::highfive:
Click to expand...
Click to collapse
I can confirm V16 fixes the phone app and resolves this issue. It's being rolled out gradually, in waves. If you don't see the update on the Play Store, you can download it from APKmirror. Start here:
https://www.apkmirror.com/apk/google-inc/google-phone/
My issue is the exact opposite..
I answer a call on my bluetooth headset while the phone is in my pocket and buttons start being pressed so I have to take the phone out to lock the screen.
Any quick fixes on this issue?
I'm late to the party, but I fixed this on a Pixel 2 XL in our household. In the system's app settings I force stopped the phone app and cleared the app cache, then I disabled the "Flip to Shhh" feature in the phone app settings. If that fix works for you, please leave a reply so we can validate.
Curious what some of you are doing as far as managing volume since Pie. And if my complaint below annoys anyone else.
My complaint about Pie is the fact that the notification volume is married to the ring volume. Typically I want my phone to ring at about 75% and notifications to sound off about 30%.
I've tried sound profile and macro droid. What I've discovered is that even though in both of those applications you can adjust notification volume separate from ring volume like with Samsung, but what ever was last to change is what both are set to. It's very frustrating having my phone blast notifications at 75% or my phone ring at 30% and not hear it. I've created a few macros that almost solve the issue, but the macros are not 100% all the time.
I've searched high and low and can hardly find anyone else complain about this. That makes me wonder, am I missing something really simple?
Sent from my Pixel 2 XL using Tapatalk
Nope, it's been tied together for years, not just with the Pie update. On Oreo and previous versions i was able to use xposed and Gravitybox to separate the notification and ringtone volume levels, or on some custom roms they have that option built in. I updated to Pie, and gave up xposed/gravitybox.. but I would still like the ability to set notification and ring volumes separate. One day maybe..
Scratching my head as to why I never noticed until Pie, I've had my Pixel 2xl since May.
Any other solutions people use that don't require root?
Sent from my Pixel 2 XL using Tapatalk
scott2ya said:
Scratching my head as to why I never noticed until Pie, I've had my Pixel 2xl since May.
Any other solutions people use that don't require root?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I am currently trying out an app called precise volume. See if it works for you.
Sent from my [device_name] using XDA-Developers Legacy app
houtx2 said:
I am currently trying out an app called precise volume. See if it works for you.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
installed precise volume.. haven't noticed a difference yet, and when i go back in and check the settings it seems the system changes the values..
Yeah I remember now, I was using sound profile to manage my sounds. After the pie update I couldn't get it to work well with my DND rules, kept missing important calls, so I ditched it and went all native.
The hack job in doing now is using macrodroid (user friendly tasker like app) monitor for incoming calls and set ringer to 75% unless silent or vibrate, then wait 20 seconds and set volume back to 30%. That makes sure my notifications don't scream at me all the time.
I also set up the DND schedule in macrodroid mainly because using the native DND, it would use the last set volume and not wake me up for important calls. This way when my schedule activates DND, it will also set the ring volume all the way up so the important calls and texts will wake me up while muting everyone else.
Too much work to make all this happen, I miss my Samsung.
Sent from my Pixel 2 XL using Tapatalk
So no solution yet on this, I remember back in the first galaxy days, when I rooted and installed ROM... that was one of the options almost every custom ROM had... hard to belief it never made it all the way into an official google release...
You can always use Automagic (preferred) or Tasker to set up shortcuts. It can adjust each individually. The newest Automagic beta (gotta purchase it) can even intercept your volume buttons. Get creative with it and can probably find a better solution than you previously had.
You can try Volume Butler app from playstore. It works for me.
pvtjoker42 said:
Nope, it's been tied together for years, not just with the Pie update. On Oreo and previous versions i was able to use xposed and Gravitybox to separate the notification and ringtone volume levels, or on some custom roms they have that option built in. I updated to Pie, and gave up xposed/gravitybox.. but I would still like the ability to set notification and ring volumes separate. One day maybe..
Click to expand...
Click to collapse
I just bought a OnePlus 6T after being on a Samsung Note5 since it came out and forgot about this "feature" of stock Android. I don't know why it's too much to ask for these to be separate. Now if I want to silence notifications at night but allow the phone to ring I have to use the Do Not Disturb settings. Should be so much easier than this.
I remember one version of Android had the two sliders for notifications and ringtone separate, and you could select a checkbox to sync them only if you wanted.
What the heck!
I've been on CyanogenMod/LineageOS for the past years and now that I'm on OxygenOS with the OnePlus 6T I'm noticing this nonsense!
What's the problem on having the option to link the ringer and notification volume togheter or NOT???
And at the same time, what't the problem on having the option to choose to use the volume buttons for media or for ringer?
It's a software, leave us the options!
Same here. Lineageos user now oneplus 6. No separate notifications volume. Very very annoying. ****, maybe put an expert mode to android if you think people are confused by so many options. ?
Notification volumee
scott2ya said:
Curious what some of you are doing as far as managing volume since Pie. And if my complaint below annoys anyone else.
My complaint about Pie is the fact that the notification volume is married to the ring volume. Typically I want my phone to ring at about 75% and notifications to sound off about 30%.
Click to expand...
Click to collapse
Yes! I find it really, really annoying. I like to have notifications only just audible but ring tone quite loud and the fact that this is now impossible, is incredibly irritating and frustrating. What on earth were the Android Pie developers thinking of....
I haven't found any fix for it at all but I'm not as au fait with development as you are. I'll keep looking though. Perhaps there'll be a fix from Android Pie developers soon.
I gave my pixel 2xl to my son and picked up a note 9. Forgot how much I missed Samsung. No longer have to deal with that asinine decision to marry ring tone and notification sounds. Love my note9. But miss the camera from the pixel
Sent from my SM-N960U1 using Tapatalk
The easiest way to reduce notification volume is to use Audacity or similar and supress the loudness of the audio file. No need to root the device just for that.
It seems like a huge conspiracy. Why oh why google cannot affort to make it a setting to choose different volumes. It must be that apple is paying them to make android suck.
I miss all most my calls now on my new phone. I just do not hear them with my notifications off. I just cannot have notification volume on at work. I get hundreds of those each day.
But I maybe get a phone call once a week during office our? Also when going to sleep or watching tv or what ever it is super super irritating to get those super loud notifications.
They say is like this since kitkat. Well I come from kitkat and my kitkat did not work that way. Maybe I fixed it years ago but I cannot remember.
Now there seems to be a solution called "Volume Butler" but hey! This is no longer on google play? You would think that google discovered that some people dared having difference volume for ringones and notifications. !!!!
I have a rooted phone I cannot believe it is this complicated to seperate the volumes. and I so do not understand why google is forceing this. what could possibly be their motivation not to make this optional? Sure link by default not problem if we can just turn it of.
okay I found volume buttler some where else but it totallay does not sepperate the 2.
It only shows 2 sliders but only one works and works for both.
I cannot believe this. make my phone useless. Since people cannot call me like most of the time.
I have to get a seperate phone dumb phone? ith a seprate databundle just to get calls and my new . How evil is that. And people will not understand thay canot whats app me on my calling nummbers. They have to whatsapp me on my notification number.
Als this because of a lazy developer at google?
Screw fingerprint scanning or face recognition give me my seperate volumes.
And then people say give feed back! just go to settings / tips /feedback? Well my stock android 9 does not have that.
Getting desperate.
Maybe install 10 versions of each notifications sound and have an app rename them based on the volume I need. But still think it is totally unnessary! This is not a feature it is a basic function of the stupid phone.
I agree it's bs with stock not having this feature. On most custom Roms it's included.
This is on lineage 16
anand_kumar said:
The easiest way to reduce notification volume is to use Audacity or similar and supress the loudness of the audio file. No need to root the device just for that.
Click to expand...
Click to collapse
A genius and elegant solution for a stupid problem that should not be. :highfive: :victory: :highfive:
I have been using my 3a xl for a couple weeks and very happy overall with the speed and performance. I am having one issue trying to overcome that's very disappointing. I do a lot of of walking with my phone in my pocket. When ever I get a call or notification while my phone is in any of my pockets it will either answer it or because it's moving around it will go thru the menus etc. Even if I don't pull my phone out it will always do this. The pocket dial/proximity programming is not good. If you test the prox sensor by covering it up you can open, unlock, make calls etc. with it covered. I am coming from a LeMax 2 and never ever had a single problem with that phone. It had a setting in there and wouldn't allow you to accidently open, unlock, do anything if the sensor was covered. Does anyone have any workarounds for this or insight. I should be able to carry it in my pocket without it doing this. Thanks for any input.
You must have a detective prox sensor or something else is not working correctly with your phone. When I cover my prox sensor (with my hand or in my pocket) the screen does not come on for notifications, calls, or when I tap to wake.
When I cover prox sensor and unlock phone with fingerprint the screen comes on too. Does yours do that as well?
retrov said:
When I cover prox sensor and unlock phone with fingerprint the screen comes on too. Does yours do that as well?
Click to expand...
Click to collapse
Yes
I just tested my phone today and my screen does wake for incoming calls even when the prox sensor is covered.
This is very annoying.
It does not wake for notifications.
Very annoying for me as well. I guess it's the software program. With that sensor covered like in your pocket it shouldn't allow that to happen. Thanks for letting me know at least I know my phone isn't defective.
My wife's Moto X4 behaves the same way.
If you want, you can install Xposed and GravityBox, it has an option to use the proximity sensor when deciding to wake the decide (see attached screenshot). It will keep the screen off for incoming calls when the sensor is covered.
creeve4 said:
My wife's Moto X4 behaves the same way.
If you want, you can install Xposed and GravityBox, it has an option to use the proximity sensor when deciding to wake the decide (see attached screenshot). It will keep the screen off for incoming calls when the sensor is covered.
Click to expand...
Click to collapse
I thought Xposed wasn't available for Pie except through some unofficial closed source buggy Magisk extensions. Are you running that? I'm not sure I trust closed source on a rooted phone....
duh1 said:
I thought Xposed wasn't available for Pie except through some unofficial closed source buggy Magisk extensions. Are you running that? I'm not sure I trust closed source on a rooted phone....
Click to expand...
Click to collapse
It's all open source now. I have not experienced any bugs, it's working really well for me.
Search the magisk repo for Riru - Exposed. I use the sandhook variant. You can find links to more information in the module description.
GravityBox Pie has a thread on XDA.
retrov said:
With that sensor covered like in your pocket it shouldn't allow that to happen. Thanks for letting me know at least I know my phone isn't defective.
Click to expand...
Click to collapse
Sounds like an annoying bug to me as well.
Google / Pixel has a bug reporting system...
https://support.google.com/pixelphone/answer/6398243/
If we all submit reports, hopefully they'll take notice and the issue will be fixed in an update...
Just submitted a report on the issue. Thanks
Try the gravity screen app & see if it fixes your issues. I use it & the phone doesn't wake in my pocket for text notifications - but I'm not sure how it will respond to phone calls/notifications; it has options for proximity sensor & a "pocket sensor" feature as well.
retrov said:
Just submitted a report on the issue. Thanks
Click to expand...
Click to collapse
If we want this bug fixed in future updates, everyone should send in a report, especially with Google, squeeky wheel gets their attention...
Anyone that has a pixel 3a 3axl please submit a report on this issue.
My Pixel 3a ja behaving the same way. Coming from a OnePlus 5 with a splendid pocket mode this phone is really getting on my nerves. I love everything about this phone but the constant pocket answering is really bad. Thinking about stop using it...
I've tried every app in Play named pocket mode but nothing seems to work properly.
I've submitted feedback report a couple times hopefully everyone on here can do the same. Won't get fixed until they update on there end. That's the only bad thing I don't like about this phone so far.
Sent.
FYI - for others looking to do this, you file the report under your phone's Settings/About Phone/"Send feedback about this device"
My biggest issue isn't answering in my pocket, but when it's ringing and I pull it out of my pocket, it will see a swipe down action this rejecting the call... Happens to me at least once a day. I really hope this is fixed in Android 10 next week.
acejavelin said:
My biggest issue isn't answering in my pocket, but when it's ringing and I pull it out of my pocket, it will see a swipe down action this rejecting the call... Happens to me at least once a day. I really hope this is fixed in Android 10 next week.
Click to expand...
Click to collapse
Android 10 didn't fix this. I really hate Google right now.
I keep my current N6 phone in a wallet like case with a front cover. Do you guys think that might help?