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).
Related
I have tried Smart Lock using both an an NFC card and a bluetooth headset. Seems like it works some of the time, but most of the time I still have to enter the PIN code.
Anyone out there get this feature to work consistently?
ronwi2 said:
I have tried Smart Lock using both an an NFC card and a bluetooth headset. Seems like it works some of the time, but most of the time I still have to enter the PIN code.
Anyone out there get this feature to work consistently?
Click to expand...
Click to collapse
Smartlock is working well for me with my car bluetooth... very consistent. I don't have any NFC cards to test with so I don't have a comment on that.
So I know we're on the same page - "working well" means that there is no need to type PIN or enter any sort of code to unlock so long as the phone is paired with the bluetooth? Would that also mean if you pushed the power button to lock the phone while it is connected to the bluetooth you could unlock it just by swiping without entering a code?
gs111 said:
Smartlock is working well for me with my car bluetooth... very consistent. I don't have any NFC cards to test with so I don't have a comment on that.
Click to expand...
Click to collapse
Yes, we are on the same page. I've used Lollipop in the car a couple dozen times now and once the bluetooth connects, then it is like there is no PIN code on the phone. It doesn't matter if it is charging, running on battery, or if I use the button or the screen turns off on it's own. When I hit the button to light the screen, I only have to swipe up to use the phone (no pin code required).
I've tested it with my pebble and that seems to work just as well... although I removed the pebble after a few hours. If I'm in a restaurant, I don't want whoever is sitting at my table to get into my phone just because I'm looking away (and my watch is right there).
Face unlock... THAT is not quite so consistent!
I have no tags or Bluetooth items to pair with, but I can't get consistent result with face unlock. Everywhere I've read that as unreliable as it was on KitKat, it's x1,000 times better on Lollipop.
I've taken probably about 30 different shots of my face with the Improve recognized face button. Scruffy, clean shaven, different lighting, some closer, some further away, in a winter hat, with my hair before & after I cut it, in a baseball cap, eyes opened and closed, my head turned slightly to the left & right as well as slightly up and down.
I'll take a pic to improve it, lock the phone and it'll work. Then I can set the phone down and let it sleep for a bit. Try to unlock it again and nope, have to enter my pin. Didn't change the lighting at all, the angle of my face to the camera, the distance of the camera to my face, etc.
Very, very inconsistent here.
I'm not concerned so much with people at my table, as people stealing it.
Someone should market a tiny bluetooth device that you can put in your pocked solely for the purpose of Smart Lock. Presumably it could be pretty tiny, as it would have less functionality than a bluetooth headset.
gs111 said:
Yes, we are on the same page. I've used Lollipop in the car a couple dozen times now and once the bluetooth connects, then it is like there is no PIN code on the phone. It doesn't matter if it is charging, running on battery, or if I use the button or the screen turns off on it's own. When I hit the button to light the screen, I only have to swipe up to use the phone (no pin code required).
I've tested it with my pebble and that seems to work just as well... although I removed the pebble after a few hours. If I'm in a restaurant, I don't want whoever is sitting at my table to get into my phone just because I'm looking away (and my watch is right there).
Face unlock... THAT is not quite so consistent!
Click to expand...
Click to collapse
I started using smart lock yesterday with Bluetooth and on body detection on my Note Edge and been getting random notification sounds but don't know what for. It don't even show up on my notification bar. Anyone knows what's going on and what's it sounding off for? It's quite annoying. Other than that notification sound coming up randomly it seems to be working fine for me.
Sent from my SM-N915P using XDA Free mobile app
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!
Just thought i'd start a thread for owners of the P2 to share any bugs ( and hopefully cures ) that we've come across so far . And to tidy up other threads that may get clogged with these issues .
i've had mine now for just over 2 weeks and so far its been somewhat of a disappointment. The issues i've come across so far are ...
1 - Audio sync .. regardless of app used the audio sync is out with the video . It gets even worse when trying to steam a video through a web browser ( and i've tried a few different ones just to make sure its not a chrome issue ) . streaming audio from internet radio is bad too . After 20 minutes or so the sound breaks up completely .
2 - Low volume in recorded videos .. The noise suppression / noise cancellation kicks in within one second when you record a video . what sound you are left with is similar to an old gramophone record .
3 - Notifications .. Seems to be an issue with the phone going into deep sleep , no notifications come through . I've read a few people saying turning off app optimization for the affected apps helps , but i don't think it makes any difference .
4 - tap to wake .. tap the screen twice , sorry 22 times to wake up the phone .
5 - SD card formatting .. freezes every time i try to format a memory card ( which has worked perfectly in galaxy S5 ) as internal or external memory .
6 - high CPU usage at idle .. I've seen this on a few other forums too . cpu starts sticking at 1.6ghz after the phone has been running for a few days . I've done a clean wipe and installed no other apps or removed any and its still present .
And the most amazing thing is i haven't seen any of these issues raised in any reviews of the phone either
So feel free to add any comments or fixes if you come across them . This could be a fantastic phone if only the gremlins are fixed .
And could you please state which firmware version your phone is running .. I'm on P2_056_uk
1,3,4 are the problems which i am also facing ..
Thanks for this post , and i have some points to add
7) "Ok Google" Hot word Doesn't work
- i have tried GoogleNow Launcher with all set, but sadly Google assistant fails to respond every time
8) Some times Gyroscope/ Accelerometer sensor goes bonkers
-i noticed that while i was playing Asphalt extreme game.. my Steering goes Out of control
finally a very bad thing which isn't a bug but annoying me a lot is -
i've got an app which does the function of DOUBLE TAP TO SLEEP , ( we can put the same in Novalauncher also, under gestures) This is using Accessibility service so when i use FINGER PRINT or any kind of SMART LOCK it always asks me to put my PATTERN LOCK even after keeping my finger across the sensor ..
and this is very disturbing.. as a result i had to disable FINGERPRINT unlock and use DOBULE TAP TO WAKE in which i again face problems .....huh...
if there is anyway to overcome it.. please suggest me a way
1) I have heard about that issue from quite a few user but i have never faced that issue.
2) Not recorded video much so cant say
3) Not facing this issue
4) Yup it works only 5 out of 10 times
5) Never tried
6) Haven't paid attention to the CPU usage
I confirm no. 3:
"Notifications .. Seems to be an issue with the phone going into deep sleep , no notifications come through . "
- I noticed that when i unlock the phone emails and notifications are being pushed. I am still bench-marking the battery and as soon as i have done a couple of cycles to get a feel of the battery life i get i
will try and play around with the battery optimization settings in the settings.
These are working fine with my mobile, Made in china one (i know there are 2 types available):
4 - tap to wake .. tap the screen twice , sorry 22 times to wake up the phone .
- Do you by any chance use a thick screen protector that might not register the double tap?
- I don`t actually use this feature as i have the finger print unlock feature active and I use that to wake the phone.
5 - SD card formatting .. freezes every time i try to format a memory card which has worked perfectly in galaxy S5 as internal or external memory .
- I formatted an older SD card from my Xioami phone in the Lenovo and had no issues (it warned me that it might be slower and suggested to get a faster one) but i had no issues.
- From my past experience (also outside mobile device use) SD cards are verry sensible, i had some of them die out of a sudden or not being readable across devices.
Possible new bug, sometimes switching from Wifi to GSM or back i noticed i had no data connection, after toggling Airplane mode on and off it works fine.
Only noticed it once so take it with a grain of salt.
Interference noise when using headphones
When listening to music via headphones there is lots of electrical interference type noise. If I turn volume to zero it stops. It also stops once no sound is being fed to the headphones. Turning the volume up helps to drown the noise out. It's there between tracks most noticeably but also very audible when trying to listen to relaxation music at very low volume which I do a lot of to help me sleep.
It sounds like processor interference of some sort - beeps and electrical sounds but also machine gun 'pips'.
I have discovered that Bluetooth being on makes it WAY worse. If it is switched off it is barely audible - but still there. I need bluetooth on all the ktime for my smartwatch.
It happens on all apps: Spotify, Netflix, YouTube etc. I even hear it when I get notifications.
Anyone else noticed this issue. Would you mind testing for me??
---------- Post added at 11:21 AM ---------- Previous post was at 11:13 AM ----------
Oh re. the OP numbered issues:
1. I also get the audio sync issue but only on Youtube. Netflix, Amazon Video etc are fine for me.
2. My video's audio is fine so far.
3. Not had phone long enough to notice for sure but I have had notifications come through when it's asleep.
4. Tap to wake worked well for me but I turned it off.
5. I have had real problems with my micro SD cards too. My first card, the P2 said it was faulty or damaged and gave me the option to reformat it. It got to 20% and then the phone completely locked up with a black screen. I had to remove the card to get the phone working again. After that the card is toast and unreadable on any device. The card was fine in my previous phone.
Second card I tried I successfully formatted in the P2. However, after 24 hours without issue, the P2 is now reporting that the card is 'unsupported'?!
My device has a screen flicker problem, occasionally the screen brightness change for a fraction of a second, even with the off auto brightness, other online users have reported this problem.
Other point :
3 - Notifications .. Seems to be an issue with the phone going into deep sleep , no notifications come through . I've read a few people saying turning off app optimization for the affected apps helps , but i don't think it makes any difference .
Click to expand...
Click to collapse
This is a Android doze scheme problem, you install a "disable doze" app from play store to solve this issue, or use adb method ( This problem is present on several models including the OnePlus 3 ), adb method is temporary untile reboot phone.
adb shell dumpsys deviceidle disable
6 - high CPU usage at idle .. I've seen this on a few other forums too . cpu starts sticking at 1.6ghz after the phone has been running for a few days . I've done a clean wipe and installed no other apps or removed any and its still present .
Click to expand...
Click to collapse
I confirm, CPU-Z shows all eight core at 1689 Mhz fixed frequency
BritishBeefUK said:
When listening to music via headphones there is lots of electrical interference type noise. If I turn volume to zero it stops. It also stops once no sound is being fed to the headphones. Turning the volume up helps to drown the noise out. It's there between tracks most noticeably but also very audible when trying to listen to relaxation music at very low volume which I do a lot of to help me sleep.
It sounds like processor interference of some sort - beeps and electrical sounds but also machine gun 'pips'.
I have discovered that Bluetooth being on makes it WAY worse. If it is switched off it is barely audible - but still there. I need bluetooth on all the ktime for my smartwatch.
It happens on all apps: Spotify, Netflix, YouTube etc. I even hear it when I get notifications.
Anyone else noticed this issue. Would you mind testing for me??
---------- Post added at 11:21 AM ---------- Previous post was at 11:13 AM ----------
Oh re. the OP numbered issues:
1. I also get the audio sync issue but only on Youtube. Netflix, Amazon Video etc are fine for me.
2. My video's audio is fine so far.
3. Not had phone long enough to notice for sure but I have had notifications come through when it's asleep.
4. Tap to wake worked well for me but I turned it off.
5. I have had real problems with my micro SD cards too. My first card, the P2 said it was faulty or damaged and gave me the option to reformat it. It got to 20% and then the phone completely locked up with a black screen. I had to remove the card to get the phone working again. After that the card is toast and unreadable on any device. The card was fine in my previous phone.
Second card I tried I successfully formatted in the P2. However, after 24 hours without issue, the P2 is now reporting that the card is 'unsupported'?!
Click to expand...
Click to collapse
Someone said the buzzing issue with headphones seemed to calm down when the screen turned off , could be causing interference , but i remember my old moto G2 had the same issue and buzzing stopped once music started playing ( even on very quiet parts of a song you couldnt hear it )
can you confirm the sync issue on BBC Iplayer too BritishBeef . And I tried the card in the galaxy S5 again , formatted straight away . I Forgot to say it was a 64gb sandisk ultra , only a few months old . The strange thing is The P2 created a 15mb partition and that was all the samsung could see , had to remove it and all ok again
The Mero said:
Someone said the buzzing issue with headphones seemed to calm down when the screen turned off , could be causing interference , but i remember my old moto G2 had the same issue and buzzing stopped once music started playing ( even on very quiet parts of a song you couldnt hear it )
Click to expand...
Click to collapse
Screen off makes no difference unfortunately. It's not a buzz though, it's popping, and electrical chirps and pips.
BritishBeefUK said:
Screen off makes no difference unfortunately. It's not a buzz though, it's popping, and electrical chirps and pips.
Click to expand...
Click to collapse
I think its some form of noise suppresion that kicks in once the music starts playing , very annoying all the same though
You know i'm starting to wonder if the phones actually made by lenovo , awful lot of similarly specced devices coming out of china at the mo
Forgot to say if anyone comments could you also say which firmware version you have too .. I dont think the bugs are firmware specific , but its good to see if they are present in any updates
The Mero said:
Someone said the buzzing issue with headphones seemed to calm down when the screen turned off , could be causing interference , but i remember my old moto G2 had the same issue and buzzing stopped once music started playing ( even on very quiet parts of a song you couldnt hear it )
can you confirm the sync issue on BBC Iplayer too BritishBeef . And I tried the card in the galaxy S5 again , formatted straight away . I Forgot to say it was a 64gb sandisk ultra , only a few months old . The strange thing is The P2 created a 15mb partition and that was all the samsung could see , had to remove it and all ok again
Click to expand...
Click to collapse
Unable to for now I'm afraid as I have packaged it up to return it. Going to get another one but buy it in a store this time. I bought the original online from Three (UK) and just spent 90 minutes on the phone to an Indian call centre to arrange a return. One of the most painful calls of my life
I wonder how many returns 3 have had so far ???
Link23 said:
I confirm no. 3:
"Notifications .. Seems to be an issue with the phone going into deep sleep , no notifications come through . "
- I noticed that when i unlock the phone emails and notifications are being pushed. I am still bench-marking the battery and as soon as i have done a couple of cycles to get a feel of the battery life i get i
will try and play around with the battery optimization settings in the settings.
These are working fine with my mobile, Made in china one (i know there are 2 types available):
4 - tap to wake .. tap the screen twice , sorry 22 times to wake up the phone .
- Do you by any chance use a thick screen protector that might not register the double tap?
- I don`t actually use this feature as i have the finger print unlock feature active and I use that to wake the phone.
5 - SD card formatting .. freezes every time i try to format a memory card which has worked perfectly in galaxy S5 as internal or external memory .
- I formatted an older SD card from my Xioami phone in the Lenovo and had no issues (it warned me that it might be slower and suggested to get a faster one) but i had no issues.
- From my past experience (also outside mobile device use) SD cards are verry sensible, i had some of them die out of a sudden or not being readable across devices.
Possible new bug, sometimes switching from Wifi to GSM or back i noticed i had no data connection, after toggling Airplane mode on and off it works fine.
Only noticed it once so take it with a grain of salt.
Click to expand...
Click to collapse
I bought mine free of contract from an online shop, unbranded and unlocked.
Currently am on the latest build number available, P2a42_S062_170117_ROW.
Ran also CPU-Z and my CPU usage is when i start the app for 1 second at 1.6Ghz then goes down to 652Mhz, so no issues for now.
Link23 said:
I bought mine free of contract from an online shop, unbranded and unlocked.
Currently am on the latest build number available, P2a42_S062_170117_ROW.
Ran also CPU-Z and my CPU usage is when i start the app for 1 second at 1.6Ghz then goes down to 652Mhz, so no issues for now.
Click to expand...
Click to collapse
Same with me ..
CPUZ staying at 652Mhz, for reference i installed same app on my MotoG3, it had 800Mhz Constant which is 1.36ghz maxed
i am also on P2a42_S062_170117_ROW.
1) Double Tap to WAke - ON
2) Finger print UNLOCK - ON
3) Nav bar - ON
4) Smart Lock - ON
5) Wifi - ON
Single sim, Volte,5 Background apps all less intensive..
so.. i dont have problem in it :victory:
has anyone made a TWRP backup of a clean 062_ROW install , I wonder if it would flask ok on the UK version , I'd be happy to give it a go
https://forum.xda-developers.com/showpost.php?p=70435638&postcount=3
This is the official S048. Update to S062 will be offered via OTA again.
HaJeeEs said:
https://forum.xda-developers.com/showpost.php?p=70435638&postcount=3
This is the official S048. Update to S062 will be offered via OTA again.
Click to expand...
Click to collapse
Thanks HaJeeEs . All worked
hi, i have problem with the NFC...
apparently he is really very little sensitive and i cant use it on my bluetooth headset but bluetooth work fine if i connect it manually...
Same issue with my SRS-X77 but I manage to make it work with a lot of patience...
Have you already tried it?
Well you issues are not bad comparing to mine. Seems like my lateral button of the extreme saving mode is still ON! Never dropped the mobile, neither dropped in water or hit some hard surface. Looks like i can't go off that saving mode, even moving the button.
So, is like 4 days that i have a nice mobile with calls and text available, plus calculator and the basic features but no way to switch back to my apps :s
I asked the assistence cuz i still have the warranty and they'll let me know what to do, if they can fix it or i have to ship it back, ah i did already the wiping date of the mobile with a reset.
Stay tuned for more!
Teo
Fangstergangsta said:
hi, i have problem with the NFC...
apparently he is really very little sensitive and i cant use it on my bluetooth headset but bluetooth work fine if i connect it manually...
Same issue with my SRS-X77 but I manage to make it work with a lot of patience...
Have you already tried it?
Click to expand...
Click to collapse
I have not tried NFC but bluetooth works fine
I bought my second P2 today. It has the same sound interference issue as my first one
To reiterate, when listening on headphones and the volume is low (like listening to chillout or classical, meditation etc.) there is electrical type interference sound. I have been experimenting and have isolated to problem to WiFi. If I turn WiFi off on the phone it stops altogether. Also, I think that the more data that's transferring, the more interference.
It is there whatever is playing - music, Netflix etc. Even when notifications play it can be heard. Obviously if the volume is turned up it is far less/not noticeable but it is always there.
I have managed to capture a recording of the issue:
https://youtu.be/r0z6X7zB-pw
This was at low volume as it illustrates the problem best but it's clearly heard in the recording.
I captured this audio by using a 3.5mm audio cable to output the audio from my Lenovo P2 to the AUX-in on a speaker system. I then placed another phone next the speaker to record the audio using an audio recorder app. The uniform static background hiss is produced by the app.
I LOVE everything else about this phone but as someone that uses my phone for music for many hours a day I cannot ignore these sounds.
I find it hard to believe that I can be unlucky enough to get two faulty P2's so there must be many more with this issue if not all and no-one else has noticed the issue yet.
I have tried 4 different sets of headphones and the issue is the same.
Hello everyone, I have been searching for this specific issue and have found nothing, apologies if this has been addressed. First, I am on my second week of Android after 6 years of iOS so please bear with me, I may not have all the terminology down.
I am running a Nexus 5 (bootloader unlocked if that matters) with 6.0.1, otherwise stock. It was a new-in-box model with 4.4.3 loaded, I updated by flashing it rather than a side-load. I was having the following issues with Face Unlock:
1. First issue, Face Unlock would randomly stop working, when you go into the settings to 'Improve Face Matching' it would report that 'Google Play services has stopped'. This would be accompanied by an increase in processor demand from Trusted Face and a severe drain to the battery, I am assuming it was frequently trying to connect to Google Play. No issue in Safe Mode. This was resolved by disabling Google Play and reinstalling the latest version.
2. Second issue, Face Unlock would again randomly stop working, but this would be accompanied by the Camera also failing to function. I would either get a 'Camera cannot be accessed' report or just a blank screen (camera controls visible, but no picture in the viewfinder). Going to 'Improve Face Matching' would report a problem with the camera. No issue in Safe Mode, so I am assuming the camera hardware was fine. This was resolved by disabling the Camera app and reinstalling the latest version. I had to do this twice, along with the Google Play update, before it worked consistently. This would again result in a reported drain coming from both 'Trusted Face' and the Camera app, again I am assuming it was constantly trying to connect to the Camera.
3. Last issue, Face Unlock randomly stops working, with no issues reported in either the camera or Face Unlock settings. no change in battery life and no reported processor demand using System Monitor Lite. If I open 'Improve Face Matching' I get the white screen with white dots with a permanent "Starting up..." notice. This is easy to fix, a reboot always gets it working again. Usually it stops within 6-10 hours of use, sometimes shorter or longer. Rebooting into Safe Mode also fixes the problem, but I am not sure if that is just because of the reboot. I have not run Safe Mode long enough to replicate the issue.
Any thoughts on how to troubleshoot? I suppose I can just disable Face Unlock but I find it quite handy. It seems to be a little bit different than the plethora of other Nexus 5 camera / Smart Unlock problems I have been reading up on.
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