Develop Bugs

Turn over to activate speaker phone?

I hear these AT&T commercials talking about this feature, my verizon TP2 does not do that. The speaker phone button on the back does not do anything either. Is it a setting?

In my stock HTC TP2, in Phone settings (Windows Mobile's, not TouchFlo's), last tab (should be "Advanced"). There's an option that said "when the phone is facing down during a call, use loudspeaker". Check if your phone has this setting?
I don't get all these modifications by providers... in Hongkong phones are sold as is, even when bundled to a certain provider's plan. Many of those modifications aren't really improvements either...

My AT&T Tilt 2 stock rom does this by default!
Cool little feature!!!

not to hijack the thread or anything, but im having the same problem except with the t-mobile version. when its flipped, the mute button lights up but the speaker doesnt activate. the windows option is checked. i messed with some registry settings to enable two way recording (didnt work btw). but that cant be the problem as my brother is having the same problem with his unmodified tmo tp2. his option is checked too.
any ideas?

bump bump, anyone know whats wrong?

Do you have ANY sound? I was using Resco Audio Recorder and I couldn't use the speakerphone when it was working either.. I uninstalled it and no problems since.

i turned this off. it came on once when i was on the couch and it was loud near my ear and freaked me the f out.

I posted about this about a week ago, my solution was to get a new one.
My new one has about 75 dead pixels, so it's going back too.
I'm not satisfied with the build quality at this point...

the speaker does work... when you click the speaker button once in a call. it's just that it doesn't automatically do that when turned over in the call. only the mute button lights up green.
EDIT-
nevermind, it works now. i read this on your thread.
MCbrian said:
I'd say that unless you've been setting it down on an uneven surface -- or not actually setting down at all as the other guy suggests-- there must be something wrong with your phone.
There's no setting/configuration that would cause the inconsistent erratic behavior you describe -- going on then off, vibrating, etc -- if it's setting on a flat table-top or similar.
Click to expand...
Click to collapse
apparently i wasn't lying it evenly face down. i was trying it on the couch so that doesn't help. i layed it evenly this time and it vibrated and the speaker went on. then i did a couple of other tests at angles and sure enough you have to have it evenly face down. at one angle, i had it vibrating like a maniac because it thought it was even and then uneven.
problem solved!

You have to make sure it is even on the surface. Also doing a g-sensor calibration may help as well.

lehmaj said:
you have to make sure it is even on the surface. Also doing a g-sensor calibration may help as well.
Click to expand...
Click to collapse
cheers mate! Workd :d:d

Proximity Sensor Slow?

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 ...

Unable to make or take calls properly on CM11

Please refer to this post:
http://forum.xda-developers.com/showpost.php?p=62828995&postcount=1432
Has anyone gotten this problem? The person who posted this has been the only one having this problem. This can't be a rare thing, is it? Is everyone just dealing with this issue until it gets fixed?

Here is a compilation of the comments made about this issue thus far. There seems to be a consensus that screen protectors are not causing this issue.
11th August 2015
AnotherContributor said:
One issue though I've been having is that when I'm making and receiving calls, sometimes the phone display goes black and will frankly not come back on. I press the App button and sometimes the display comes on, sends the call to the Status Bar, and the screen goes dark. So, I have to press the Application button again and draw down the menu to hang the call up. When I press the power button, the screen flashes on for maybe a quarter second then goes dark. It keeps doing that every time you press the power button. The worst case scenario that has happened a handful of times is that when I'm in a call, neither the power nor application button are responsive. When that happens, pretty much the only option is to power down the phone and reboot.
...
I'm not sure if I would be able to dial an extension with the way the phone is acting up. I feel like this was not an issue the first couple of weeks I had CM on the phone. Now, it seems to be happening with every call.
Click to expand...
Click to collapse
14th September 2015
samuraix21 said:
Hi, I have this issue. Were you able to fix this issue? You're the ONLY person that has posted this issue so I'm not sure if this is a rare hardware issue or everyone on this forum is somehow dealing with it until a fix comes up.
Click to expand...
Click to collapse
19th September 2015
hawk1500 said:
are people still experiencing the screen off during call problem? I am not talking about when you put it up to your face, but how the screen turns off and won't come back on?
Click to expand...
Click to collapse
20th September 2015
hawk1500 said:
Naw, no screen protector installed. tried the proximity sensor fix app as well as the xposed don't go to sleep during call module but it still does it.
Click to expand...
Click to collapse
20th September 2015
tonochito said:
i think that bugs should be listed more detailed:
front facing camera does not work well, if i want to take a selfie it crash. video camera also does not work equal it will crash. I had to install Google Camera and Open Camera in order to have both selfie and video options working, With Google Camera i take selfies and with Open Camera i record videos, As the guy talking about the scren off in calls is true, i don't have a screen protector and it has this behaivour, also as i mentioned there is kind of lag when i try to dial a number i have to do twice, it doesn't show up right away. The same goes when i am calling for example my carrier and i have to dial on the IVR i have to dial twice in order to get the dial keypad. I didn't have Google play crash.
Another thing that i notice was setting a wallpaper as screensaver does not fit in the middle or correctly i had to use Quick Pic and the option 768x1280 because with the stock gallery wallpapers are like aside of the middle
Click to expand...
Click to collapse

I think this issue needs some attention. I am having this problem as well (with and without screen protector). There are times that I need to enter extensions and codes during calls which has become impossible. I have two of these phones and they both behave this way. I recommend that people start posting screenshots of the app Proximity Sensor Finder which displays different distance numbers detected by the prox sensor. See my screenshot attachment which shows the proximity sensor always detecting a "covered" state of 0.0cm even when nothing is in front of the screen. Everyone should go try this and post their findings.
Other phones on CM11 were able to fix this problem in the past by adjusting the calibration which is unique for each phone, so I started searching around through the Fire Phone CM11 files and I found these:
/system/etc/permissions/android.hardware.sensor.proximity.xml
I could not discern anything of value from this .xml file.
/persist/sensor_calibration/SHCAL_DU20060142640727.csv
This file seemed promising. Its timestamp is back in 2014 so I assume that this comes straight from the original Fire Phone files. If this file is actively used to govern sensor behavior, I'm wondering if perhaps it is not being read correctly. It makes me wonder if there is a log out there somewhere that could shed more light on it. Anyways, you can open up that badboy in any spreadsheet to discover sensor IDs for a bunch of sensors along with calibration coefficients in the form of:
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=550.30
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=395.62
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=19262.26
You'll have to open it and analyze it in context of the other columns and other sensors. I've attached it (re-saved in xlsx format because .csv files are not permitted - if you don't trust my xlsx just retrieve the file from your phone). I highlighted the rows of interest. We could just mess with coefficient values, but without any guidance, it could just be a waste of time. Plus we don't know if this even governs the sensors or if it's just helpful documentation. If anyone has insight about this or even far fetched theories, please comment!
I'm thinking about doing a 'grep' on the entire file tree for some of these key words like SENSOR_ID=SI1143, SI1143, 4CCU1, COEFF0, SENSOR_TYPE=PROX etc etc - to see if any files use any of these terms. It may prove unfruitful due to the amount of compiled software that is no longer in text form. Any thoughts about any of this?

i have this screen always making a call with any cm11 i have used in the past, i have to press back and again the keypad and works normal, same when i have to dial a number

tonochito said:
i have this screen always making a call with any cm11 i have used in the past, i have to press back and again the keypad and works normal, same when i have to dial a number
Click to expand...
Click to collapse
But if the prox sensor is always detecting a "covered" state, then it completely disables the screen during a call and we are unable to press "back". Could you post your findings from running Proximity Sensor Finder from CM11 Fire Phone?

jdmillard said:
But if the prox sensor is always detecting a "covered" state, then it completely disables the screen during a call and we are unable to press "back". Could you post your findings from running Proximity Sensor Finder from CM11 Fire Phone?
Click to expand...
Click to collapse
i will give a shot, and post my result

In fact, it would be AWESOME if we could get someone (whose screen does behave perfectly during calls) to post their findings from Proximity Sensor Finder. If their screen works perfectly during calls and this app shows 0.0cm all the time for them too, then we can conclude that this app isn't functioning correctly and we know we need to find our root cause elsewhere.

tonochito said:
i will give a shot, and post my result
Click to expand...
Click to collapse
Available but why it doesn't work right?

tonochito said:
Available but why it doesn't work right?
Click to expand...
Click to collapse
Interesting. Is it stuck on 10.00061 even when you cover the front of your phone with your hand? Or does the number fluctuate?
Which ROM build are you on? (I should say, which publish date?)

jdmillard said:
Interesting. Is it stuck on 10.00061 even when you cover the front of your phone with your hand? Or does the number fluctuate?
Which ROM build are you on? (I should say, which publish date?)
Click to expand...
Click to collapse
yes weird it is stuck no matter what i do, well if i put my finger in the "first camera" of the phoen it goes to zero

tonochito said:
yes weird it is stuck no matter what i do, well if i put my finger in the "first camera" of the phoen it goes to zero
Click to expand...
Click to collapse
That suggests to me that the sensor is "all or none" meaning it doesn't bother detecting intermediate values, rather it just has a threshold that determines a covered or not covered state. That seems normal to me. I need to get mine to do that.
Does your screen behave normally during calls? Specifically, does the screen turn on when you pull the phone away from your face?

jdmillard said:
That suggests to me that the sensor is "all or none" meaning it doesn't bother detecting intermediate values, rather it just has a threshold that determines a covered or not covered state. That seems normal to me. I need to get mine to do that.
Does your screen behave normally during calls? Specifically, does the screen turn on when you pull the phone away from your face?
Click to expand...
Click to collapse
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls

I just removed my glass screen protector and now mine behaves just as yours. Which is good that it functions as expected, but also a disappointment about the screen protector. I just looked to request a refund and it appears that they have an excellent return policy so I'm not too worried about it. Now I just need to find a screen protector that doesn't cover the prox sensor. ... sigh.
I'm still interested to see what happens with what you were describing: like how the screen would still behave finicky. I'll keep an eye out for that behavior and I'll let you know if I discover anything about it.
---------- Post added at 01:26 PM ---------- Previous post was at 12:38 PM ----------
tonochito said:
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
Click to expand...
Click to collapse
I forgot to say thanks! You posting your results helped me figure out where I was going wrong. Gracias!

jdmillard said:
I just removed my glass screen protector and now mine behaves just as yours. Which is good that it functions as expected, but also a disappointment about the screen protector. I just looked to request a refund and it appears that they have an excellent return policy so I'm not too worried about it. Now I just need to find a screen protector that doesn't cover the prox sensor. ... sigh.
I'm still interested to see what happens with what you were describing: like how the screen would still behave finicky. I'll keep an eye out for that behavior and I'll let you know if I discover anything about it.
---------- Post added at 01:26 PM ---------- Previous post was at 12:38 PM ----------
I forgot to say thanks! You posting your results helped me figure out where I was going wrong. Gracias!
Click to expand...
Click to collapse
your welcome

I have a glass protector and i noticed over time that i developed a specific technique for answering the phone. I sort of slowly move it close to my ear and then the sound comes on (hear ringing, able to hear caller). If i press the answer button then put it to my ear, most of the time i cant hear the caller but they CAN hear me.
Never even considered it being a sensor issue. I thought it was CM bug triggered by my setup somehow. I flashed this rom and put the glass screen on within a couple of days after receiving it in the mail and since touch-wise the tempered glass works perfectly it was never even a thought. Dont mean to go on but is anyone else dealing with issues like the one i describe? Whats strange is i dont recall having that black screen issue others are experiencing.

KLit75 said:
I have a glass protector and i noticed over time that i developed a specific technique for answering the phone. I sort of slowly move it close to my ear and then the sound comes on (hear ringing, able to hear caller). If i press the answer button then put it to my ear, most of the time i cant hear the caller but they CAN hear me.
Never even considered it being a sensor issue. I thought it was CM bug triggered by my setup somehow. I flashed this rom and put the glass screen on within a couple of days after receiving it in the mail and since touch-wise the tempered glass works perfectly it was never even a thought. Dont mean to go on but is anyone else dealing with issues like the one i describe? Whats strange is i dont recall having that black screen issue others are experiencing.
Click to expand...
Click to collapse
I was lucky enough to have a good return policy on the glass screen protectors I recently got (for two Fire Phones). I'm returning them today and I've already ordered this as a replacement:
http://www.amazon.com/gp/product/B00WXY18WK?psc=1&redirect=true&ref_=od_aui_detailpages00
It has excellent reviews, decent price, very thin, and it is specifically mentioned many times in the reviews that there is a little cutout for the prox sensor (and you can see if if you look carefully at the pictures). I'm hoping that it will solve my black screen woes and protect my screen. There are reports from folks on these forums saying that there is still some strange behavior during calls (such as your example among others). I personally haven't encountered what you're describing, but I'll keep an eye out to see if I can be of any help.

jdmillard said:
Here is a compilation of the comments made about this issue thus far. There seems to be a consensus that screen protectors are not causing this issue.
11th August 2015
14th September 2015
19th September 2015
20th September 2015
20th September 2015
Click to expand...
Click to collapse
Hi. I like to get back about this since I've been quoted on this.
For me, the glass protector screen that I brought from XtremeGuard was the issue my dad had when he tried to make or take calls. After I removed it, it was back to normal.
The persistent issues now, based on what my dad is telling me, is that sometimes after you dial in a number and call a person, you don't hear the ringing tone to know if it went through or not. My dad would freak out when someone on the other line said something since the ringing tone is not working.

tonochito said:
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
Click to expand...
Click to collapse
hi
this is usually related to hardware composer.
cheers

superdragonpt said:
hi
this is usually related to hardware composer.
cheers
Click to expand...
Click to collapse
but why? does it matter with the bootloader, i mean i know the CM11 on the Fire phone still on beta with no NFC working and the camera too at least i am using Snap camera and everything works. But making calls is a bit annoying even i don't use the phone to make a lot of calls just for WhatsApp almost all the time

Phone calls on lock screen

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.

An issue with calls dropping on S20 Ultra - Proximity sensor issue?

So I have a very weird issue and I'll try to explain the best I can;
For some reason, ever since the S10+ I've had issues with Samsung phones, I think its something to do with the proximity sensor that's now under the glass, I'll explain as I'm getting similar and more issues on my S20 Ultra.
So last year when I had an S10+ and when I was on a call, which I mainly use my left ear (I think my right ear is a few db less so I use my left) I would quite frequently seem to activate the menu (top right) and therefore end up pressing things with my ear, unbeknown to me, sometimes I'd add a 2nd person to the call or simply put the other person on hold! This happened a lot and I was close to sending it off for repair even though I used apps to test to ensure the proximity sensor was working correctly but in the end, I sold it and got an OnePlus 7 Pro, which I didn't have an issue with. During my time with the S10+ I noticed that even though I held the earpiece to my ear I could see the screen light up and that's where I think I'd end up pressing the screen accidentally as I've just explained.
Roll on to now where I'm facing similar issues but also I'm finding if I need both of my hands and therefore use my left shoulder to keep my phone against my ear the call disconnects as if I'm hanging up. Now it seems a straightforward resolution which is not to do that but I've never had this issue before and I've tested it out quite a bit when I do this the screen isn't on and my face is nowhere near the end button!! It's really driving me crazy at the moment and annoying my other half who's normally on the phone to me when this happens!!
Anyone got any suggestions or thoughts, does it happen to anyone else or am I just being stupid??
I haven't gone down the route of resetting the phone yet but I'm going to consider it.
T.I.A

Hi..don't have such an issue, but when i talk with someone longer, i turn off the screen with the Power button and so it stays the whole time black during call....
S20U-Exynos

Xode said:
Hi..don't have such an issue, but when i talk with someone longer, i turn off the screen with the Power button and so it stays the whole time black during call....
S20U-Exynos
Click to expand...
Click to collapse
I did that the other day, however, when I moved the screen away I saw it light back up....

maverick1103 said:
I did that the other day, however, when I moved the screen away I saw it light back up....
Click to expand...
Click to collapse
Yeah,weird a bit, try to go into the secure lock screen settings and do as i did...maybe it helps ..... like i wrote before, my screen stays black whatever i do while i talk...
View attachment 5012913
S20U-Exynos

Xode said:
Yeah,weird a bit, try to go into the secure lock screen settings and do as i did...maybe it helps ..... like i wrote before, my screen stays black whatever i do while i talk...
S20U-Exynos
Click to expand...
Click to collapse
Thanks, I've already got that enabled, will just have a play around.

maverick1103 said:
Thanks, I've already got that enabled, will just have a play around.
Click to expand...
Click to collapse
Hi , do you make it work? I have the same problem with my Samsung A71, I have been using all kinds of apps a no one make it work.
Sent from my [device_name] using XDA-Developers Legacy app

vrgolin said:
Hi , do you make it work? I have the same problem with my Samsung A71, I have been using all kinds of apps a no one make it work.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Not yet, still having issues.