Purchase an OP3 for my sister when they were 1st released. For some reason, her phone frequently butt calls me. I can never get a straight answer from her what she is doing when it happens, but today she said her phone was just sitting in her purse. Can anybody think of what feature/setting/option she may have toggled on or off that is causing this? I believe she is on unrooted stock 3.2.7. Thanks
singlebyte said:
Purchase an OP3 for my sister when they were 1st released. For some reason, her phone frequently butt calls me. I can never get a straight answer from her what she is doing when it happens, but today she said her phone was just sitting in her purse. Can anybody think of what feature/setting/option she may have toggled on or off that is causing this? I believe she is on unrooted stock 3.2.7. Thanks
Click to expand...
Click to collapse
Turn on the pocket mode and probably ask her to put a password on her phone.
bonham1988 said:
Turn on the pocket mode and probably ask her to put a password on her phone.
Click to expand...
Click to collapse
To top it off, I think she has "Proximity Wake" also turned on. That will really cause issues in a purse...LOL
singlebyte said:
To top it off, I think she has "Proximity Wake" also turned on. That will really cause issues in a purse...LOL
Click to expand...
Click to collapse
Haha yes. Its a useful feature if your phone is usually on a desk otherwise it can be pretty annoying feature.
Sent from my OnePlus3 using XDA Labs
I just ran a styrofoam cup over my phone with proximity wake enabled and it woke up my phone, so depending on if it's stored during commuting around like pocket or purse, it's quite likely that's the culprit. Other user's suggestions would be a good call
Well, I tried the solutions recommended here but they did not work.
To recap,
1. Turned on Pocket Mode
2. Turned off Proximity Wake
These two setting did not solve problem. Any other suggestions to keep OP3 from Butt dialing?
Finger print lock screen security
daviss101 said:
Finger print lock screen security
Click to expand...
Click to collapse
Yes, we have that turned on.
Related
When i place a call and put the phone to my ear and then pull back away the screen does not "wake". It stays de-activated, no matter what i do. Eventually the only thing to do is to hold the power button down long enough for the phone to reboot.
Stock ROM, no root.
Thanks for any help anyone can offer.
WTF
I tested by laying the phone flat on a surface, placed a call, and then put my hand over the proximity sensor. The screen turned black as it should. When I removed my hand it did not come back on. Again, the only solution is to reboot the phone. So, the proximity sensor is not working correctly. Is this a known issue and is there a way to fix?
BUMP!
I'm in the self test module and am running the "sensors" test. I'm not sure when this ends if it ends at all or what values that proximity sensor field should have.
Anybody? Bueller?
Apparently Q&A isn't the place to post this? This is dissapointing coming from the E4GT forums which were super responsive.
Cool yer jets. It's only been a few hours. What ROM? Rooted? Any other mods that might affect it?
dkmdlb said:
Cool yer jets. It's only been a few hours. What ROM? Rooted? Any other mods that might affect it?
Click to expand...
Click to collapse
LOL
I said no root stock ROM
Anyway, I turned off the proximity sensor, verified that it was off, then turned it back on. It works now. Bizarre.
Sorry to get pissy.
oregondave said:
LOL
I said no root stock ROM
Anyway, I turned off the proximity sensor, verified that it was off, then turned it back on. It works now. Bizarre.
Sorry to get pissy.
Click to expand...
Click to collapse
Where is the sensor setting?
Edit. Found it.
Sent from my SGH-T999 using Tapatalk 2
NOT FIXED
So after a reboot the proximity sensor does not work on calls again. I turned it off and then back on and still no luck. I didn't actually make a call, but obviously I shouldn't have to do this every time i reboot the phone, so clearly there is an issue. It appears to be software since I got it to work once.
Any ideas? Thanks.
oregondave said:
So after a reboot the proximity sensor does not work on calls again. I turned it off and then back on and still no luck. I didn't actually make a call, but obviously I shouldn't have to do this every time i reboot the phone, so clearly there is an issue. It appears to be software since I got it to work once.
Any ideas? Thanks.
Click to expand...
Click to collapse
Your getting screen of death.. man thats so ****ty..
Uh, you can try this.. Settings - Accessibility - Call answering/ending - power button ends calls ?
aklyrical said:
Your getting screen of death.. man thats so ****ty..
Uh, you can try this.. Settings - Accessibility - Call answering/ending - power button ends calls ?
Click to expand...
Click to collapse
? Uh No. Thanks?
After insalling a new screen my phone acted the same. I opened it up again and found a tiny piece of plastic form the old screen inside the proximity sensor hole.
I know your problem is not this, just wanted to share
gberger42 said:
After insalling a new screen my phone acted the same. I opened it up again and found a tiny piece of plastic form the old screen inside the proximity sensor hole.
I know your problem is not this, just wanted to share
Click to expand...
Click to collapse
hmmm interesting. I think this is likely a software issue on mine. it would be dumb to have to return it since i'm confident there's a way to fix it.
oregondave said:
hmmm interesting. I think this is likely a software issue on mine. it would be dumb to have to return it since i'm confident there's a way to fix it.
Click to expand...
Click to collapse
That solution wasn't very good aha, what I would suggest you root your phone without tripping the flash counter and install a custom rom to see if the issue still exists, if yes you should return the phone.
aklyrical said:
That solution wasn't very good aha, what I would suggest you root your phone without tripping the flash counter and install a custom rom to see if the issue still exists, if yes you should return the phone.
Click to expand...
Click to collapse
thanks well it's brand new and it may be hardware related so i'd rather just get a fresh device then sweat dealing with root yet. this is why i waited to root it. I appreciate your effort though .
aklyrical said:
That solution wasn't very good aha, what I would suggest you root your phone without tripping the flash counter and install a custom rom to see if the issue still exists, if yes you should return the phone.
Click to expand...
Click to collapse
Plus I don't think just rooting it is a sound fix strategy.
Nobody has anything on this huh?
BTW, Wirefly sucks...
Have you already done a master reset?
sent from my SGS3... the envy of all many friends!
I've tried it with s voice both on and off. when I first turn it on after a reboot, it doesn't train the voice model, but it says it's on but doesn't work. It then turns itself off, and trying to turn it on results in the voice model training opening , then saying it completed successfully, then turning its self back off.
Help?
No one else has experienced this?
To shut it off...i think thats what u looking for?
Go to Google. .sertings...voice, then turn off voice detection
Sent from my SM-N910P using Tapatalk
same thing on mine, its grayed out and I've heard there is no fix for it yet.
Bloodgroup said:
same thing on mine, its grayed out and I've heard there is no fix for it yet.
Click to expand...
Click to collapse
Mine looks gray to me..but it still slides to shut off.
Mine too. Is anyone on stock kernel?
Gotta disable S voice
fatboypup said:
Gotta disable S voice
Click to expand...
Click to collapse
I disabled it. Works now thanks
ibcenu said:
To shut it off...i think thats what u looking for?
Go to Google. .sertings...voice, then turn off voice detection
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I'm trying to turn it on, but it turns it's self back off with no explanation. physically moves the slider back to the off position before my eyes. It's gone back to just being grey now, though
fatboypup said:
Gotta disable S voice
Click to expand...
Click to collapse
If you read the original post, it says I've tried with s voice and without
This really isn't unique to Lollipop, as it does this exact thing on mine which is still on kitkat. Sometimes I will hear the tone acknowledging the ok google, but will immediately hear another tone. Often the screen doesn't even turn on. Even more often it just never works, although it works pretty perfectly with the screen on.
It has nothing to do with disabling svoice, although it probably is related to Samsung's implementation of svoice. Once in a while, thE phone will fail to even acknowledge an ok google request, only to sometime later say, "if you're trying to say something I didn't get that." This seems to imply the microphone is locked in the listen position, but isn't working.
Hi. I bought the Note 8 (Verizon) last week, and everything seemed fine, but then 2 days ago the screen simply won't turn on when I have an incoming call. The phone rings, but the screen won't come on. I have to unlock the phone, and swipe down the notification bar just to answer the call. I've googled around but can't find an answer to this issue for this particular phone. Any suggestions/ideas?
Maybe give a factory reset a go.
moralesd66 said:
Maybe give a factory reset a go.
Click to expand...
Click to collapse
I was actually forced to do a hard reset this morning. The phone would NOT come on, no matter what I tried, couldn't even go into Safe Mode. Problem still persists. I'm actually thinking of exchanging it since I'm within the 14 day period.
tdetroit said:
I was actually forced to do a hard reset this morning. The phone would NOT come on, no matter what I tried, couldn't even go into Safe Mode. Problem still persists. I'm actually thinking of exchanging it since I'm within the 14 day period.
Click to expand...
Click to collapse
Hard reset....As in power off and on right? Try booting into recovery mode and deleting cache and data.
tdetroit said:
Hi. I bought the Note 8 (Verizon) last week, and everything seemed fine, but then 2 days ago the screen simply won't turn on when I have an incoming call. The phone rings, but the screen won't come on. I have to unlock the phone, and swipe down the notification bar just to answer the call. I've googled around but can't find an answer to this issue for this particular phone. Any suggestions/ideas?
Click to expand...
Click to collapse
My TMO one did that today, heard it ringing but screen remained off.
Sent from my SM-N950U using Tapatalk
I've now performed 2 factory resets, disabled AOD (for testing) and kept it on for other tests...same outcome. The screen will not come on when I have an Incoming call.
tdetroit said:
I've now performed 2 factory resets, disabled AOD (for testing) and kept it on for other tests...same outcome. The screen will not come on when I have an Incoming call.
Click to expand...
Click to collapse
You tried removing the screen protector and case?
Sent from my SM-N950U using Tapatalk
Maybe the setting for proximity...in pocket...turn off
Limeybastard said:
You tried removing the screen protector and case?
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
I've tossed the screen protector after 1 day because it kept making a clicking sound on the top corner. No case on it.
BlueFox721 said:
Maybe the setting for proximity...in pocket...turn off
Click to expand...
Click to collapse
Tried that-no change. It's hard to believe that this phone has pretty much everything going for it...except turning on the screen for an incoming call.
tdetroit said:
Tried that-no change. It's hard to believe that this phone has pretty much everything going for it...except turning on the screen for an incoming call.
Click to expand...
Click to collapse
Factory reset , if no go , replacement.
Sent from my SM-N950U using Tapatalk
3 Factory Resets later, booting into Safe Mode, not downloading ANYTHING else, same scenario. Verizon is shipping a replacement to my house, I should have it by Tuesday. The Tech at the Verizon Store actually called my phone so I could show him the lack of screen activation. He said he's never seen this before either.
FIGURED IT OUT! Settings--Display&Lights--Turn off double tap to wake-up to solve issue! ...
This was set somehow, I disabled that and now my phone properly lights up for calls and I can actually answer them.
tdetroit said:
3 Factory Resets later, booting into Safe Mode, not downloading ANYTHING else, same scenario. Verizon is shipping a replacement to my house, I should have it by Tuesday. The Tech at the Verizon Store actually called my phone so I could show him the lack of screen activation. He said he's never seen this before either.
Click to expand...
Click to collapse
they know absolutely **** about anything
I never use retail store
Another way to fix this is to call yourself on another phone while your Note 8 screen is on. When the call comes in, don't answer but slide down the notification bar and you will see your call. Adjust notifications to not block/be silent.
tdetroit said:
FIGURED IT OUT! Settings--Display&Lights--Turn off double tap to wake-up to solve issue! ...
This was set somehow, I disabled that and now my phone properly lights up for calls and I can actually answer them.
Click to expand...
Click to collapse
I went into Settings, Display, but nothing about double tap to wake-up. Samsung runs on AMOLED and that function is on other screens like Sony Xperias.
I do notice another thing going into Notifications settings and I see that the Phone app is Muted. I don't know how to get out of it.
The solution is the person who posted above. You call yourself, and swipe to unblock Silence notifications for your phone app. It's weird how it was set that way, but that's the best solution!
How do I unmute phone call notifications?
Thanks! My incomimg calls now appear on my screen!
I tired the unblock silence notifications and that still has not fixed it as well as a hard reset. Anyone else got any suggestions?
Thanks
Ian
Fix to dark screen on incoming call
Step 1: call youself
Step 2: swipe down on notification bar to view the call(usually how you would answer while dealing with this issue)
Step 3: swipe the call to the right and click the setting wheel.
Step 4: select "do not hide notifications"
Step 5: test call after doing this with the screen off, its should work.
BlueFox721 said:
Maybe the setting for proximity...in pocket...turn off
Click to expand...
Click to collapse
I turned "block accidental touches" off.
That worked for me!
THANKS
As the title indicates.* Always On Display now never goes off even when it is in my pocket or phone face is down at night.* AOD used to turn off as expected and believe this broke after the September security update.*
AOD remaining on when the phone is in pockets or face down is resulting in increase of battery use. I have unlocked Note 10+ on T-Mobile.
I posted this on Samsung support as well. Can you guys check and confirm if you are seeing the same issue?
Sent from my SM-N975U1 using Tapatalk
I've mentioned on another forum that I'm having this issue as well. I have the Note10+ T-Mobile with the September update. When I first got my phone before the September update, my phone's AOD used to turn off when I close my flip case. I checked this when I first got my phone because I was reading forums and people were saying it didn't work. Then after the September update, I noticed that the AOD will not turn off anymore when I close my flip case or even face down. Now it will just dim when the case is closed but never turn off.
Thanks for posting this on the Samsung forum as well. I hope they get back to you and give us an update to fix this issue.
Mine also is not working. I'm using tap-to-turn-on right now, and prefer it, but just chiming in here.
As a temporary solution you guys could set it to "show on tap", that's how I set mine from the beginning, so AOD is off unless you tap on it, or set it active during certain hours. If it was working and no more, probably bug in the update, what else is new, yawn.
Pinan said:
Mine also is not working. I'm using tap-to-turn-on right now, and prefer it, but just chiming in here.
Click to expand...
Click to collapse
pete4k said:
As a temporary solution you guys could set it to "show on tap", that's how I set mine from the beginning, so AOD is off unless you tap on it, or set it active during certain hours. If it was working and no more, probably bug in the update, what else is new, yawn.
Click to expand...
Click to collapse
Kind of disappointing. Pay $1,100 for a phone to only be forced to use it half ass LOL.
Sent from my SM-N975U1 using Tapatalk
Lepa79 said:
Kind of disappointing. Pay $1,100 for a phone to only be forced to use it half ass LOL.
Click to expand...
Click to collapse
This is not likely to ever change. Every new (rushed to market) device has issues. They'll fix it. I actually prefer the tap-on method now.
It is what it is.
If my phone is inside my pocket, I need to take it out and hold in my hand, same at night when sleeping, phone is laying down on night table, I need to pick it up to see the screen. If tapping the screen to activate AOD, when holding the phone in your hand is such a problem, I really would hate to see the drama, when real problems appear, like when you get a message or miss call and there is no notification light etc. LOL.
It's actually worse than just AOD not turning off because after the Sep update the proximity sensor doesn't work except when making a phone call. If I get a text message or email and my phone is in my pocket then the phone display turns on. At a minimum it's bad because the device wastes power turning on in the pocket, but depending what's on the screen it can also inadvertently clear notifications, open apps make a call all by accident. Needs a fix from Samsung ASAP.
sansnil said:
It's actually worse than just AOD not turning off because after the Sep update the proximity sensor doesn't work except when making a phone call. If I get a text message or email and my phone is in my pocket then the phone display turns on. At a minimum it's bad because the device wastes power turning on in the pocket, but depending what's on the screen it can also inadvertently clear notifications, open apps make a call all by accident. Needs a fix from Samsung ASAP.
Click to expand...
Click to collapse
It makes sense the problem is with the sensor post the security update since AOD depends on the sensor to turn off in pockets and when face down. Really crappy this gotten broken [emoji17]
Sent from my SM-N975U1 using Tapatalk
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.