Database Info

[Q] the telephone...

So now lets talk real world experience of the phone interface
When it blanks the phone buttons seem to operate...
I mean a number of occasions I have lost people because I have mysteriously put them on hold...with the phone to my ear.
People are always complaining to me that I am quiet even though the phone is in the correct place on my face and incall volume is at max
Often I cannot pick up calls ...I hit the answer icon to no avail...if I flick it upscreen it works but pressing the icon is only recognised intermittently
What is it like for you?

PianoSam said:
So now lets talk real world experience of the phone interface
When it blanks the phone buttons seem to operate...
I mean a number of occasions I have lost people because I have mysteriously put them on hold...with the phone to my ear.
People are always complaining to me that I am quiet even though the phone is in the correct place on my face and incall volume is at max
Often I cannot pick up calls ...I hit the answer icon to no avail...if I flick it upscreen it works but pressing the icon is only recognised intermittently
What is it like for you?
Click to expand...
Click to collapse
have to tried to factory data reset the phone to see if that helps?

This is called the incall/proximity sensor issue and the reasons have not yet been found by xda people.
There are few fixing attempts available though which involve different strategies.
Someone lately suggested to the ViperOne team to make a tweak that allows for automatically locking the phone on call pick up as a permanent workaround fix. There was no developer response on this yet though. Its a good idea though.
The same sensor is causing another issue which is quite frustrating. On some occasions the normal method of simulated battery pull (press power for more than 15 seconds to force reboot) does not do anything unless shining a really bright light into the sensor. Apparently the prox sensor, not the light sensor.
It seems there are a few units out there which have issues with this sensor.
Another theory is that its jut the user tilting the phone until it recognizes landscape orientation and then the sensor is switched off...

[Q] Galaxy S5 turns display on randomly

Was anyone experiencing the display randomly turning on & won't dim itself off. I am using the fingerprint lock so it stays on the screen asking for the alternate password. This happens while charging & when idle. The phone stays on until you press the power button. I am testing if is something to do with the fingerprint lock, switching to pattern lock. any ideas?

I also use fingerprint unlock and have noticed that the display will randomly turn on and ask for the alternative password. I just got the phone this past Sunday (6/8) and all I've really done to it is add the fingerprint security.

what ROM are you running?

youdoofus said:
what ROM are you running?
Click to expand...
Click to collapse
Stock ROM, no changes.

I've also seen this. Usually happens to me at night for some reason. Screen turns on and when I hit the side button to turn off the screen it goes out for a few seconds then lights up again. Have to reboot to fix it.

Mine does it during the day at work quite a bit, I think it is from the home button being pushed in my pocket. It really should be associated with the light/proximity sensor as to when the button will work.

Having the same problem with both swipe and fingerprint unlock. I can understand swipe, fingerprint works better in my pocket then with my finger

Mine is constantly turning on in my pocket now. I have an otterbox commuter on it and edges are raised pretty good, doesn't seem like my leg would hit the home button but it's hard to tell

Only happens to me when connectivity state changes, or music skips for a notification
Sent from my SM-G900P using Tapatalk

I am having this problem on stock unrooted ND2 as well as RDDT. I also noticed on both that I get notification sounds with NO notifications showing up. So I have my notification sound going off a few times each hour for no reason unless I leave my phone on silent.
As far as the screen coming on randomly, I found that disabling air wake has helped a little bit. Especially overnight, I leave my phone next to my pillow (yea, I am a junkie...) and the screen would turn itself on every time I rolled over, and the screen would stay on after that until I woke up and turned it off. I know it was staying on because a couple of times I reached over the phone, screen turned on and I watched it for about 5 minutes (screen time out is set to 15 seconds) and it didn't shut off.
TL;DR Turn off air wake - Need help figuring out phantom notifications (still exist after multiple factory resets and almost no apps installed)

My issue stopped once I installed a glass screen saver. Home button is now countersunk with the 0.33 mm. Cover & review.
http://www.amazon.com/Tech-Armor-Samsung-Ballistic-Protector/dp/B00IGISUTG/ref=cm_cr_pr_product_top
http://www.amazon.com/Tech-Armor-Sa...tBy=bySubmissionDateDescending#R1R8876D8WLXE3

I installed the same one, lol. It still does it, not as often though

I was using standard pattern lock screen on stock rooted and had this issue. It was the wave to wakeup feature that was causing it. I turned it off and it went away. 3 days with no waking by itself.

I've never had that turned on.

looks like you guys turn on air wake and it's working sensetively. on the contrary, mine is numb

yueyejinghun said:
looks like you guys turn on air wake and it's working sensetively. on the contrary, mine is numb
Click to expand...
Click to collapse
It was numb for me too when it wasn't being awakened by ghosts. The other guy said he didn't have that feature on so not sure what the other issue(s) is/are.

GorillaPimp said:
It was numb for me too when it wasn't being awakened by ghosts. The other guy said he didn't have that feature on so not sure what the other issue(s) is/are.
Click to expand...
Click to collapse
air wake is a nice feature to extend the lives of home & power button, except it always makes me look like an idiot when I am waving my palm over the phone again and again.
I tried to set the mode to unlock by fingerprint and keep air wake on for a whole day, but I didn't encounter that problem. maybe it just affects some devices, maybe it's not air wake.

Anybody found a real solution for this inconvenient?!
This only happens at Lollipop... 2 months ago I updated and because this annoying issue that was draining my battery I downgraded to Kit Kat...
Last weekend I decided to give another shot to Lollipop, but the issue remains...
I tried all settings relative to screen and lock screen and nothing worked!

andreluigo said:
Anybody found a real solution for this inconvenient?!
This only happens at Lollipop... 2 months ago I updated and because this annoying issue that was draining my battery I downgraded to Kit Kat...
Last weekend I decided to give another shot to Lollipop, but the issue remains...
I tried all settings relative to screen and lock screen and nothing worked!
Click to expand...
Click to collapse
I have the same problem. My battery has been life does not even last me until the end of work. Trying a fix now that I just thought of though. This problem is incredibly frustrating at night too.
I believe its the connection optimizer. Go to Settings > More networks > Mobile networks > Connections optimizer:
Then Uncheck "Connections Optimizer"
Seems to be working so far! So hopefully this helps the rest of you!
This Fix did not work still perplexed by this problem.

After rooting and removing a lot of bloat, I got rid of it. I have no idea which app it is though. Maybe an xposed module logging screen wakes could be of assistance. But I too noticed it immediately after flashing a lollipop ROM.

Improve face unlock

Anyone have problem with face unlock about bad angles or not working under bright sunlight! Just set up face unlock under direct sunlight! make sure sunlight sight direct into your face when setting up. Hope that's helpful, it works for me at least
Ps: if you are wearing glasses, put them on when setup.

My biggest issue with face unlock is random challenge to unlock with PIN for "added security".
I say random because I've not rebooted the phone. The message is different when rebooting. I've sent numerous feedback with logs to Google but Google doesn't respond to feedback. I have no idea why this happens. It's annoying. This can happen as often as once a day at random unless I'm missing the reason for it. Maybe it works for days without error. Maybe this is required at intervals I've not recognized?
Patterns I've noticed otherwise include a pause to unlock when I grab my phone and it's upside down. It usually gives me time to recognize this and get screen upright. My phone is usually on a stand upright in portrait mode so it's rare that I pick it up with screen not orientated correctly.
I've not tried setting up face unlock in bright setting though.
Sent from my Pixel 4 XL using Tapatalk

samep said:
My biggest issue with face unlock is random challenge to unlock with PIN for "added security".
I say random because I've not rebooted the phone. The message is different when rebooting. I've sent numerous feedback with logs to Google but Google doesn't respond to feedback. I have no idea why this happens. It's annoying. This can happen as often as once a day at random unless I'm missing the reason for it. Maybe it works for days without error. Maybe this is required at intervals I've not recognized?
Patterns I've noticed otherwise include a pause to unlock when I grab my phone and it's upside down. It usually gives me time to recognize this and get screen upright. My phone is usually on a stand upright in portrait mode so it's rare that I pick it up with screen not orientated correctly.
I've not tried setting up face unlock in bright setting though.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
your problems is totally different with what I mean to. However, It think your problem could be from software or setting. you would reset your phone. And if that keep going, using google warranty is best choice.

nguaogioi said:
your problems is totally different with what I mean to. However, It think your problem could be from software or setting. you would reset your phone. And if that keep going, using google warranty is best choice.
Click to expand...
Click to collapse
Thanks. I should talk to Google Pixel support again. I've been reluctant since they couldn't resolve an issue with Google Home app. They referred me to Google Home app support but they kept getting stuck on the fact they support hardware, not the app. I could link Google and Philips Hue but couldn't add Philips Hue to Google Home app. Failing every time.
Long story but the mobile apps kept telling me that that there was an issue getting provider information for Philips Hue. Yet it went through all the steps and failed at the end, never adding Philips Hue. This once worked until it stopped; nothing I was doing was working, even asking Google and Philips for support was pointless with them refusing to talk to each other or continue support with me until resolution. One day my phone had a notification to control my lights and the linking and final step worked that time. I followed the notification and seemingly skipped several steps I've went through to failure but this time everything went as expected and I can control my lights again. Finally! What was the issue? Google won't say but I suspect they discovered it long after I gave up. Months!
I've seen face unlock improvements in the notes of the monthly updates so I've thought Google is aware but like before, not on my timetable. Low priority. With my past slate now clean, start a new one.
Sent from my Pixel 4 XL using Tapatalk

samep said:
My biggest issue with face unlock is random challenge to unlock with PIN for "added security".
I say random because I've not rebooted the phone. The message is different when rebooting. I've sent numerous feedback with logs to Google but Google doesn't respond to feedback. I have no idea why this happens. It's annoying. This can happen as often as once a day at random unless I'm missing the reason for it. Maybe it works for days without error. Maybe this is required at intervals I've not recognized?
Patterns I've noticed otherwise include a pause to unlock when I grab my phone and it's upside down. It usually gives me time to recognize this and get screen upright. My phone is usually on a stand upright in portrait mode so it's rare that I pick it up with screen not orientated correctly.
I've not tried setting up face unlock in bright setting though.
Click to expand...
Click to collapse
The issue you explained about the seemingly random pin requirement is actually not an issue at all. It's coded into the software as an extra security measure. If you lock your phone and do not unlock it for XXX amount of time (eg. 1 hour) then the phone requires your pin or pattern to verify its still you and your phone hasn't been physically compromised. The other trigger for this happening is at or around 6 hours since the last time your pin was physically entered, it will require you to enter it for the same reasons I listed before. Using face unlock doesn't reset the 6 hours, only physically entering your pin code will.
Hope this helps you understand a little better what's going on with your phone. We all have the same thing happen to us, just most don't notice it when it happens.

1dopewrx05 said:
The issue you explained about the seemingly random pin requirement is actually not an issue at all. It's coded into the software as an extra security measure. If you lock your phone and do not unlock it for XXX amount of time (eg. 1 hour) then the phone requires your pin or pattern to verify its still you and your phone hasn't been physically compromised. The other trigger for this happening is at or around 6 hours since the last time your pin was physically entered, it will require you to enter it for the same reasons I listed before. Using face unlock doesn't reset the 6 hours, only physically entering your pin code will.
Hope this helps you understand a little better what's going on with your phone. We all have the same thing happen to us, just most don't notice it when it happens.
Click to expand...
Click to collapse
Your hour or six a guess, estimation or actual?
What you described seems true but my use would likely indicate more quiring for PIN than I experience. Just asking.
But if this is intent, I don't agree PIN is added security. Sure face ID can be duped in many ways but at the very least what I'd prefer is safe zone like home where face unlock never dupes to PIN or added security. As I recall, total unlock is only option for designated safe zone like home, unless considering Bluetooth device which I don't prefer unless it can distinguish my Fitbit Versa 2 watch is very near and worn?
Surely there's less invasive methods users can deploy to not be so inconvenienced at home. I've even seen this at work with my wife's iPhone X. More choices seems a logical approach to consider. Why hasn't it?
Phone on charger just now, after just talking to Google Assistant, give a smart home command it interprets correctly, the smart assistant says sure, after you unlock your phone. I dismiss the Google Assistant and promptly unlock my phone without the stupid PIN. Not being very user friendly. I'm under the impression many developers don't just use the device and rethink their intents to be most user friendly.
Sent from my Pixel 4 XL using Tapatalk

I feel like I don't see this message more than twice a week... which certainly goes against the every 6 hours idea. My impression was that sometimes movement or Soli will wake it up and it sees something it thinks is a face but it can't unlock with it. If it sees this enough, it may prompt for a PIN unlock with the different message. But sometimes, I think I see this message taking it out of my pocket... where it can't possibly see a face. But maybe it saw part of my face as I was putting it in. It would be interesting to know what the actual rules are regarding this.

I know that when I have the screen upside down, the screen wakes but gives me time to get it upright. Seconds. I don't recall seeing this fail me, thankfully.
I don't have much or any of the Soli features enabled but have screen tap to wake and skip unlock screen enabled.
I've wondered if having the generic stand was causing random face unlock errors but reach for phone is disabled. And I've tried placing my screen down flat instead of the stand and still got prompts to unlock with PIN.
Sometimes I grab my phone and tap to wake doesn't work. But it doesn't mean I get a prompt for PIN every time either. Yesterday, I tapped on the screen repeatedly and it woke and unlocked when it recognized my face. Maybe it's a latent response but I'm usually using the power button to wake by then.
Sent from my Pixel 4 XL using Tapatalk

So I did a chat with Pixel support today.
For the issues with frequent queries for PIN and Voice Assistant asking me to unlock my phone first, the agent had me delete storage and cache for Google and Phone app, delete face unlock and add it back. Reboot phone and get back with them if this doesn't help.
The agent indicated there's not a timer that cannot be reset with unlock that would naturally challenge for PIN after counting down. His advice is to do the above for that issue. The face unlock is suspect. I hadn't done this until today. For kicks, I tried it outside in daylight though the agent didn't recommend this idea. Fwiw, I can unlock my phone in the dark but maybe daylight helps better see contours of the face.
I have a case number to chat again if this continues. Agent says it shouldn't reoccur.
Sent from my Pixel 4 XL using Tapatalk

I only have a basic understanding of how face unlock works... but from what I understand it uses an IR dot projector and two IR cameras to stereoscopically sense the depth of your face. This is why it works in the dark to begin with and based on this, I would think direct sunlight would be a detriment rather than a boon in this sensing method. But it may not have any effect at all as I don't know exactly how the sun and the dot projector overlap in wavelength and strength.
Having a "bad" face calibration might explain it as the phone is more often unconfident about it being your face. So it triggers more failures which prompts the increased security message.

jljtgr said:
I only have a basic understanding of how face unlock works... but from what I understand it uses an IR dot projector and two IR cameras to stereoscopically sense the depth of your face. This is why it works in the dark to begin with and based on this, I would think direct sunlight would be a detriment rather than a boon in this sensing method. But it may not have any effect at all as I don't know exactly how the sun and the dot projector overlap in wavelength and strength.
Having a "bad" face calibration might explain it as the phone is more often unconfident about it being your face. So it triggers more failures which prompts the increased security message.
Click to expand...
Click to collapse
Agreed. It's unknown if added light is a help, hindrance or placebo. But the agent seemed confident just replacing the face unlock would solve my issues.
Not all of my issues sounded familiar was the reason for suggested extra storage wipes and reboot.
Sent from my Pixel 4 XL using Tapatalk

I spoke from my experience. Before that if i will to unlock i have to keep it direct to my face as the right distance or angles and it hardly work with changing light conditions like under direct sunlight. But after set up with aid from sunlight i could say it work quick and more reliable as my iphone xr even in dark or direct sunlight.
I dont know if that is hardware or software problems.

73 hours of uptime. Random PIN for added security prompt has returned when Google Pixel support said it shouldn't after deleting and adding face unlock.
Taking my case ID back to Pixel support. I'm not sure the agent was right about face unlock not occasionally duping to PIN unlock. Very annoying if this is intended or not.
72 hour bug?
Sent from my Pixel 4 XL using Tapatalk

So my Pixel 4 XL face unlock did the same prompt for pin after another 72 hours. No reboot; no error or explanation why other than added security. I'm at 146 hours uptime.
I asked Pixel support again about this. They're researching but want me to do a factory reset now and get back to them.
Sent from my PH-1 using Tapatalk

Proximity Sensor Location/Issues

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.

Question USB-C to headphone adapter music stops with locked screen...and can cause an OS crash?

Would some of you smarter people please help figure out what's going on? I/you can then file a bug report which won't result in it being closed due to their misunderstanding.
The primary issue is that music stops playback when a USB-C adapter is used, once the screen locks. I've used three different ones, which I can't identify the differences between with my skillset of linux, but they all produce the issues and one does treat the microphone differently.
It's not related to screen off timeout, only lock screen timeout. If I lock the screen, music stops. If I set the lock timeout 30 seconds after the screen off timeout, music stops 30 seconds after the screen is off.
The secondary and deeper issue is that if fingerprint or face unlock are enabled, it causes a 7+ second delay in unlocking, or it "breaks" screen unlocking entirely (until the adapter is removed), or can even result in a hard crash or "soft" (yeah?) crash of the OS. However, this is only if a certain type of audio session is running with Android (which I don't understand anything about), until the headphone adapter is removed. If left in, it can cause the phone not to unlock or even crash and reboot.
The broken lock screen does not occur if using an app such as Simple Music Player, although the music does still stop when the screen locks. It doesn't do the same type of audio session with the operating system that Amazon Music, Audible, or Podcast Addict do. I know this only because Wavelet doesn't detect the audio session, so it's very likely not an app issue but an OS issue with how the audio session type causes this problem.
The broken or delayed lock screen does not occur if I turn off face and fingerprint unlocking. It works normally with entering a PIN and there's no delay.
The fingerprint scanner is broken, no matter what, if face unlock is also enabled.
If I delete the stored face scan, the fingerprint scanner works but with the big delay.
After playing music and locking the screen, if I turn on the screen and wait about 7 seconds, it will unlock the screen using my face. If I try to use the fingerprint reader, it'll often, but not always, break unlocking entirely until it crashes or I remove the adapter.
If I successfully unlock it, the music is shown to be "still playing", although it's silent. If I lock it again, it's definitely broken and cannot be unlocked via fingerprint or face, and will not fallback to PIN.
If I let it sit a while (not more than 90 seconds) after that, it becomes unresponsive and the screen will not turn on again. It doesn't hard crash all the way to the bootloader, but when I unplug the adapter, the "G" loading logo is shown and then the lock screen asks me for my PIN.
I can't say how I managed to get it to hard crash to the bootloader twice, but I think those times I was quickly using the fingerprint scanner numerous times, turning the screen on and off, and I don't THINK I had a successful unlock first, during the hard crashes to bootloader.
EDIT:
Enabling "allow wired headset requests with device locked" in the Google App doesn't resolve the issue. The headset doesn't work then, either, and gets disconnected. I guess I could file a bug report on that alone and maybe the fix would trickle down to everything else...but I'd rather not.
Sorry for the wall of text, but it's not a simple scenario since I don't know what's actually going on and what's important. Hopefully one of you can help figure out the stuck process and reduce it down to two sentences for a bug report. I don't recall having this issue with my Pixel 6 Pro, but the times I used a USB-C headphone adapter with it was probably only in the first few months it was released, if at all, so a specific Android update may be to blame, but I don't know which/when.

Solved.
Yikes. So if I change my "default USB configuration" in developer options to "no data transfer", then it works normally, music doesn't stop, lock screen works normally.
Well, that solves that part, but I've loved just plugging my phone into my computer and it being ready to go without intervention. Maybe Tasker can be my savior and change the usb configuration type.
EDIT:
Tasker: Set USB for file transfer automatically - NotEnoughTech
One of the most annoying things in new Android is the inability to trust USB devices permamently
notenoughtech.com

That's odd... Did you have a bad adapter or something?
For me most of them works fine. I've tested multiple Chipsets on these (I make custom cables), like:
ES9280C
ALC5686
CS43131
All works fine on March Update....

yurishouse said:
That's odd... Did you have a bad adapter or something?
For me most of them works fine. I've tested multiple Chipsets on these (I make custom cables), like:
ES9280C
ALC5686
CS43131
All works fine on March Update....
Click to expand...
Click to collapse
I've seen multiple reports of this through several forums. Google is aware of it and working on a fix.

xunholyx said:
I've seen multiple reports of this through several forums. Google is aware of it and working on a fix.
Click to expand...
Click to collapse
Interesting guess we'll see. It's weird that it only happens to some and not others

yurishouse said:
Interesting guess we'll see. It's weird that it only happens to some and not others
Click to expand...
Click to collapse
I think it depends on what you have set up for USB in developer options

Having recently purchased a Pixel 7 Pro, I immediately set the developer option for USB to file transfer (it's even more of a chore in A13 to use the popup than it was in previous versions).
I also picked up a Jsaux USB-C DAC for use with the P7P as, unlike my P20 Pro, it doesn't support USB analogue audio (making my old adapters useless, sadly). As soon as the screen is locked, if the default setting is USB File Transfer, the music stops. If the phone is then unlocked, the app playing will hang.
I was going to return the adapter (thinking it was incompatible or faulty) but decided to check if others had a similar issue. As I only need to use wired audio occasionally, I will just have to manually switch the default setting when needed (far more common that I need the USB file transfer - I usually listen to music with my M&D MW07 earbuds).