Was trying to verify the Easy Mute motion (hand over screen or flip to mute calls or alarms), and it does not seem to work in either folded or unfolded configuration. I also tried running AndroSensor and that shows no change in sensor when I cover the top half of either screen. Anyone else having similar problems, or is it working as expected for them.
Vimes14 said:
Was trying to verify the Easy Mute motion (hand over screen or flip to mute calls or alarms), and it does not seem to work in either folded or unfolded configuration. I also tried running AndroSensor and that shows no change in sensor when I cover the top half of either screen. Anyone else having similar problems, or is it working as expected for them.
Click to expand...
Click to collapse
.
I just tried it myself and turning over the phone definitely muted the incoming call (with the phone open or closed) Also the palm gesture worked (cover screen only) but that was slightly more difficult as you really have to cover the whole screen for a couple of seconds.
I also used AndroSensor (and another app) and noted the proximity sensor was present but wasn't showing a reading. Obviously it is working (and works when holding phone to ear by turning screen off for example).
So I am not sure why it's not working for you.
.
apprentice said:
.
So I am not sure why it's not working for you.
.
Click to expand...
Click to collapse
Thanks for checking.
Did some more testing, the flip gesture seems to be working for incoming calls with the Google Phone app, and alarms created by the Samsung Clock app, but not the Google Clock app or Calendar notifications. Using the Google Phone app once the call is established, then the screen does turn off when held close to a head when folded. So seems like the sensor is working, in some situations, which means it is probably software related, rather a hardware defect. I really don't want have to reconfigure my setup up again.
The Google Phone app also has a setting flip to mute, which was not set. So I flipped that to true.
I had previously written a Tasker profile to mute everything (enter Do Not Disturb) on a Pixel 3XL, before Google implemented it at the OS level, so I may try that here.
Certainly seems like a conflict with the Google phone app. The gesture settings are OneUI features so they are unlikely to work with a different dialer.
.
apprentice said:
Certainly seems like a conflict with the Google phone app. The gesture settings are OneUI features so they are unlikely to work with a different dialer.
.
Click to expand...
Click to collapse
I think the problem is that the Samsung implementation is to hook into a small subset of their applications to do a local mute, where as Google implementation just invoked Do Not Disturb, which meant every application would mute, assuming they are compliant. I think DND was slightly flakey on OS9, but from OS10 onwards it was rock steady.
To bring clarity to my local behaviour, I enabled my Tasker method that engaged DND when the phone is flipped. Works in both folded and unfolded configurations. As a bonus with Join, I have a method that automatically distributes DND to my other devices.
Related
I'm running CM 7.0.3, and I'm having massive proximity sensor issues, t the point where the phone is becoming unusable. If I'm in a call and I don't manually shut the screen off, the following happens (constantly):
I'll feel some haptic feedback on my ear, and my voice will mute. When I look at the screen, the lock screen is up and when I unlock it, it's at the dialer screen. I'm not hitting the mute or hold button with my ear, it seems like once it gets away from the call screen, my voice is muted.
Needless to say, this is getting massively annoying. Later tonight I'm going to try to see if using a Sense based rom fixes this, but I'd much rather stick with CM. Has anyone else experienced this?
I believe there is another post on this.. you can also Google search for inspire proximity sensor adjustment - someone created an app to adjust the sensor
Sent from my Desire HD using XDA Premium App
The thread in question:
http://forum.xda-developers.com/showthread.php?t=1062561
EDIT: I haven't used the proximity sensor adjustment application that's linked in the thread as mine is working normally. If it doesn't work there's a possibility the sensor's faulty and should be replaced (I recently went through this whole thing with my old iphone 4).
Yeah, to be honest, I tried that app and it didn't seem to make much difference. I'll try calling HTC
Flashed to a sense based ROM, and the sensor seems to be working fine. Very odd, to be honest. I will say that after using AOSP for so long, I have no idea how you guys deal with Sense at all.
Well, now I have to decide: I can live with Sense, or I can ship my phone back to HTC and be without a device for 2 weeks. Going to try out the proximity sensor app again, but it didn't seem like any setting made a difference, but it could be that I just don't know what I'm doing with it.
Check under Settings>Call Settings and put a check mark in the "Always use proximity" box. It says it's to help with prox. sensor screen locking when the phone is horizontal, but the CM7-based ROM that I was using showed the same issues and I fixed my particular issue by checking that box.
Tested with a few calls and the screen is definitely shutting off when the phone is standing or lying down.
I read up on the proximity app, and I think I have it calibrated properly at 5/6. It certainly helps, but it's definitely not perfect. Night, thanks for the advice, but yeah, that option has been checked from the start. At least the issue is tolerable now, before it would do this 10 times per call.
Funny - mine was calibrated at 10/11 by default and works pretty well. Try going up to those values. I used a local time/temperature number here, and it worked well when my finger got 1/8" or so from the phone. While I admittedly haven't measured the depth of my ear or anything, it does seem to be working well at those settings.
I think the upper threshold is where you may want to adjust. From my playing with that app, changing the lower threshold too high will make it ignore things too close to the phone and so will an upper threshold that is too low. Try lower 5, upper 11 and see what happens. Anything between lower and upper apparently triggers the sensor. (<<< speculation without documentation)
Hi,
I just updated my Droud Ultra and it looks like there are missing two features:
1. in the 21.xxx sw if I approached with my hand the proximity sensor the phone shows the time/missed events. Now if I want to see the clock I have to move / to jog the phone it is not enough to go close with my palm to proximity sensor
2. in the 21.xxxx when the phone was charging a stripe/band was going up and down -- now it is missing, too (
How could I enable this features or they are turned off ?
For the first one. Yes, waving the hand over the phone no longer wakes it up. According to one of the moderators on the Moto support forum, the ability to display notifications with a wave of the hand was a bug that Moto fixed. I know..... So there is no way to reactivate it 23.3.24. Sorry.
Source:
https://forums.motorola.com/posts/fe26ceed34
Also stock messaging app no longer allows you to open the address book and multi select recipients. Hangouts is the same.
I could slap whomever decided to do this!
Touchless controls actually goes to speakerphone now when making a call if you have the setting checked, it was broken in the last update and wouldn't actually go to speakerphone even though it was checked but worked before that one. I'm so glad it works now.
Wondering if anyone has any advice for my weird mic issue - it's a little different to the others I've seen but willing to try anything at the moment. Here's what I've found so far:
*People can't hear me when I talk into the phone. I've tried calling my home phone and listening and I don't hear anything either.
*This problem seems to happen when I'm holding the phone normally (i.e. against my face - ear to the ear speaker and mouth near bottom of the phone's mic)
*If I talk right into the bottom of the speaker (as in have the bottom mic and speaker right in front of my mouth), it picks up audio fine on the other end.
*Speakerphone appears to be fine so secondary mic is working fine.
*Done the usual clean the mic hole with pin (and compressed air), made sure my finger wasn't covering the mic hole, removed any cases, etc.
My suspicion is maybe the proximity sensor is doing something to cause the audio to cut out? I can't imagine the bottom mic being that directional that it picks up nothing in one particular direction while works fine in another.
Phone is bone stock S6 - SM G920W8 running 6.0.1 (Build G920W8VLU3CPC8)
I've already done a factory reset so this thing is as clean as it gets and still no luck. Help!
Apps could be the issue.
Do you have any apps or had any apps in the past that use the proximity sensor on your Galaxy S6? I know that I have had these problems in the past where certain apps that use the proximity sensor, such as the wave your device on and off app that I frequently use interfere with how the microphone detects how far away your face is.
WSADKeysGaming said:
Do you have any apps or had any apps in the past that use the proximity sensor on your Galaxy S6? I know that I have had these problems in the past where certain apps that use the proximity sensor, such as the wave your device on and off app that I frequently use interfere with how the microphone detects how far away your face is.
Click to expand...
Click to collapse
Not that I recall. I did boot the device up in Safe Mode (which should stop any third party app from loading) and the problem still occurred. I also tried it again after I did a factory reset and before I loaded any apps but that didn't help either.
I don't use the gestures at all so I don't think it's that but maybe the factory reset turns it on. I'll see if I can find it to check.
syee said:
Not that I recall. I did boot the device up in Safe Mode (which should stop any third party app from loading) and the problem still occurred. I also tried it again after I did a factory reset and before I loaded any apps but that didn't help either.
I don't use the gestures at all so I don't think it's that but maybe the factory reset turns it on. I'll see if I can find it to check.
Click to expand...
Click to collapse
Well, it looks like gestures were turned on by default. Turned them all off and then turned them on one by one and made a test call and found it's the "Smart Alert" feature that caused the mic to not work when near my face.
Thanks WSADKeysGaming for the reminder about the gestures! I completely forgot about it because I never used them.
Don't mention it!
There are so many settings nowadays that its hard to remember whats on and off, left and right. Glad I could help!
syee said:
Well, it looks like gestures were turned on by default. Turned them all off and then turned them on one by one and made a test call and found it's the "Smart Alert" feature that caused the mic to not work when near my face.
Thanks WSADKeysGaming for the reminder about the gestures! I completely forgot about it because I never used them.
Click to expand...
Click to collapse
Sorry for bumping an old thread, are you familiar with why the Smart Alert feature would do this? Thanks!
So, what the title says, I just downloaded it from xpirifirm and Installed it using flashtool, am hoping to fix the problem with voice messages from WhatsApp and messenger as well (basically 1 in 10 voice messages I send go silent in the middle of the recording), there is not a changelog from Sony but they never give any so I hope this could be more than just a security patch, I want to know if any of you have installed it and if you have noticed any fix, thanks, If I find out something I will tell you. Thanks for reading.
Well, sadly I couldn't fix the issue with the voice notes, but I disabled the "ok Google" feature from the Google assistant and I haven't had any problem with voicenotes anymore, let's see if it stays like that.
It didnt solved the problem, I plan to go back to android 9
Does not feel any fix, but so frustrating 'couse battery capability is much much worse...
I think the fingerprint at least is faster and more reliable.
ferluna18 said:
So, what the title says, I just downloaded it from xpirifirm and Installed it using flashtool, am hoping to fix the problem with voice messages from WhatsApp and messenger as well (basically 1 in 10 voice messages I send go silent in the middle of the recording), there is not a changelog from Sony but they never give any so I hope this could be more than just a security patch, I want to know if any of you have installed it and if you have noticed any fix, thanks, If I find out something I will tell you. Thanks for reading.
Click to expand...
Click to collapse
I fixed the voice messages disabling the feedback tactile of 3 under screen buttons
Did the upgrade change your GPS functionality? Since the day I updated, my phone started drifting. I have 25 kilometers displacement on a day staying permanently at my home office. Compared to 0.5 kilometers before the update.
I didn't understand how you fixed the voice messages, can you be more specific?
Hey guys, it's July 9th and the last firmware released for xperia xz2 is 52.1.A.2.1, will Sony stop supporting this device or what? Btw my cellphone has now a ghost touch.
ferluna18 said:
Btw my cellphone has now a ghost touch.
Click to expand...
Click to collapse
Same for me! Just about a week or so, I am annoyed by the quick settings bar being occasionally pulled from top while typing on the keyboard or working in apps. With the "Show taps" option turned on from the developer settings, I can clearly see that the device sometimes detects an extra tap (draws the corresponding circle) at the very top of the screen right after I tap somewhere else. This activates the system bar and switches the focus from the app. This only happened before with the screen very dirty or wet (i.e. in the rain). However, this time cleaning it and rebooting the system didn't help. My initial idea was that I could have damaged the screen sensors or other hardware somehow. But this might be instead a planned action to support the upcoming models' sales Interestingly, there was no software update accompanying the behaviour change — seems like there are some remotely controlled sensor options their engineers could be playing around.
sersel2 said:
Same for me! Just about a week or so, I am annoyed by the quick settings bar being occasionally pulled from top while typing on the keyboard or working in apps. With the "Show taps" option turned on from the developer settings, I can clearly see that the device sometimes detects an extra tap (draws the corresponding circle) at the very top of the screen right after I tap somewhere else. This activates the system bar and switches the focus from the app. This only happened before with the screen very dirty or wet (i.e. in the rain). However, this time cleaning it and rebooting the system didn't help. My initial idea was that I could have damaged the screen sensors or other hardware somehow. But this might be instead a planned action to support the upcoming models' sales Interestingly, there was no software update accompanying the behaviour change — seems like there are some remotely controlled sensor options their engineers could be playing around.
Click to expand...
Click to collapse
Thanks for sharing your experience, well I still have the ghost touch but now occurs more often and I have had another issue since some months ago ad well and tje thing is that sometimes the proximity sensor "detects" it's being covered and makes the screen flash several times during a call or hearing voice notes in whatsap, sometimes the failure is as bad that I have to restart the phone, I don't know what could be causing this problem but I have to say that I have dropped some water in my cellphone in the past two or three times, and I don't know, maybe some of this water came into the phone through the earpiece and messed with the upper part of the screen and the other sensor up there, my phone os almost a year old now, Do you guys think it might mot be water resistant anymore? And btw, have you dropped water in the phone as well? Thanks for reading.
Hi guys,
It often happens to me that screens shuts off when I try to click on top tier of screen, it's really annoying especially with full screen apps.
I recently put on screen protector film but I don't know if it's due to this.
Anyone has this problem ?
Many thanks.
Are you rooted and using [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+'s option to double-tap the status bar to sleep? If so, it might be related to that setting. I was trying to reproduce a different bug, playing a full-screen landscape YouTube video and I found almost every time I tried to make the status bar appear and then drag it down, I accidentally shut the screen off.
Luckily for me, I rarely try to do something like that while in a full-screen landscape app, so I'm keeping that setting on.
If you're not rooted or not using that Magisk Module, then ignore this.
I'm not.
It happens even whith WhatsApp when I select a message in a conversation and try to click on delete icon located in top screen, screen shuts off.
Where is the promixity sensor ?
Cygnust said:
I'm not.
It happens even whith WhatsApp when I select a message in a conversation and try to click on delete icon located in top screen, screen shuts off.
Where is the promixity sensor ?
Click to expand...
Click to collapse
I'm not really sure. I just unlocked my P7P and ran my finger across the status bar, back and forth and I never found it.
https://9to5google.com/2022/10/07/p...nt-facing camera than last year’s Pro phone.
Meanwhile, the cutout for the proximity sensor has been slightly tweaked again and is more to the right of the front-facing camera than last year’s Pro phone.
Click to expand...
Click to collapse
I have the same problem. TMobile Visual Voicemail has its delete button just below and to the right of the front camera and the screen turns off before I can delete the playing voicemail. I have to go back to the full list of voicemails and delete from there.