Related
I've been digging as much as I can on this issue, and so far I haven't been able to find any official acknowledgement or diagnosis of this issue. Please forgive me if this has been discussed before, but I simply cannot find the thread.
So far, I have had 2 Nexus 5's. Both of them had the exact same issue. When I am on a call, occasionally the volume from the other side will drop to a level where I cannot hear it. This happens most often when I am listening through the earpiece, thought it has happened while using speakerphone and multiple bluetooth headsets (plus my car). There doesn't seem to be a specific thing that triggers the issue, the area or type of phone I am calling doesn't seem to matter.
The phone is stock, I've never messed with the OS and the only apps I've downloaded were basic free ones, too many to list but if an app could be causing it I can post a list.
So far, I've tried the following to resolve the issue.
1. Factory reset both phones
2. Change sim card
3. Contacted my wireless provider (AT&T)
4. Contacted LG
5. Contacted google
Changing phones didn't help, Factory reset seemed to fix the problem for a bit but it came back. Changing sim did nothing. AT&T told me that because the device was third party, it wouldn't work properly. (I don't believe that for a second) LG just wanted me to ship the phone to them. (Not an option as they will take 2 weeks to get it back to me) And google just gave me some basic troubleshooting tips that I had already tried.
I cannot RMA the phone, i bought it used off of Swappa. I do not want to pay LG for a repair as this is a software issue and it should be solvable on my own. (though I will send the phone to them if it comes to that)
Has anyone had this issue, or at least heard about it? The only possible explanation I've found is that there's a problem with the noise cancellation software, but no one seems to have any solutions other than send it to LG, which really isn't an option for me at this point.
Thanks a crap load in advance to anyone who can shed any light onto this.
Bump for help please.
We are in the same boat
detailedvenom said:
I've been digging as much as I can on this issue, and so far I haven't been able to find any official acknowledgement or diagnosis of this issue. Please forgive me if this has been discussed before, but I simply cannot find the thread.
So far, I have had 2 Nexus 5's. Both of them had the exact same issue. When I am on a call, occasionally the volume from the other side will drop to a level where I cannot hear it. This happens most often when I am listening through the earpiece, thought it has happened while using speakerphone and multiple bluetooth headsets (plus my car). There doesn't seem to be a specific thing that triggers the issue, the area or type of phone I am calling doesn't seem to matter.
The phone is stock, I've never messed with the OS and the only apps I've downloaded were basic free ones, too many to list but if an app could be causing it I can post a list.
So far, I've tried the following to resolve the issue.
1. Factory reset both phones
2. Change sim card
3. Contacted my wireless provider (AT&T)
4. Contacted LG
5. Contacted google
Changing phones didn't help, Factory reset seemed to fix the problem for a bit but it came back. Changing sim did nothing. AT&T told me that because the device was third party, it wouldn't work properly. (I don't believe that for a second) LG just wanted me to ship the phone to them. (Not an option as they will take 2 weeks to get it back to me) And google just gave me some basic troubleshooting tips that I had already tried.
I cannot RMA the phone, i bought it used off of Swappa. I do not want to pay LG for a repair as this is a software issue and it should be solvable on my own. (though I will send the phone to them if it comes to that)
Has anyone had this issue, or at least heard about it? The only possible explanation I've found is that there's a problem with the noise cancellation software, but no one seems to have any solutions other than send it to LG, which really isn't an option for me at this point.
Thanks a crap load in advance to anyone who can shed any light onto this.
Click to expand...
Click to collapse
I'm being searching a lot to find a solution to this problem, but no luck.
I am using a Nexus 5 from the past 15 days and have the same problem of low to no volume from the speaker (voice of the other party). I initially though that it happens when I am outdoors, but no, it happens indoors too; and this does not happen always, sometimes it is loud and clear sometimes it is not. So I suspect that this has got something to do with the software rather than the software.
Even I don't have an option to send it back to LG cause I bought this in a different country.
My phone is Stock OS, updated to 4.4.4, rooted has Xposed Framework on it.
I also modified the build.prop and set the persist.audio.fluence.voicecall from true to false, but even this did not help.
Please, please, please, if anyone has found a solution to his please let us know.
If you press the back of the phone slightly, does it lower the sound? when i do not apply pressure to any back part of the phone, the sound is clear. with even slight pressure the sound dims on the other side. just noticed this today after trying to troubleshoot the problem. really bad design
IINexusII said:
If you press the back of the phone slightly, does it lower the sound? when i do not apply pressure to any back part of the phone, the sound is clear. with even slight pressure the sound dims on the other side. just noticed this today after trying to troubleshoot the problem. really bad design
Click to expand...
Click to collapse
So far I haven't been able to try that. For some reason the phone has started behaving, though there are a few issues here and there. I'll try this out next time it happens and report back.
Phone: Samsung Galaxy S6
Android 6.0.1 - 2 updates since issue bagan
I had the issue where I could not revert to a standard swipe unlock after using a pin, and was told a solution was to clear credentials/certificates.
This solved my problem, but created another. As it stands, about 75% of unlocks it plays one/both of two sounds, which granted do sound like some sort of unlock sound, however not standard to the way the phone shipped. It also happens at random, sometimes as a response to a touch, or just whenever it feels like it. It is one of or both of the same two sounds presented with at unlock. They are ridiculous and am preventing me from using the phone whilst not on silent. The phone has a mind of its own.
NFC is turned off.
I am not tech illiterate and thought I could fix it, however it has beaten me. Any help would be appreciated.
Well ,
Could you post ur question on s6 forum
http://forum.xda-developers.com/galaxy-s6/help
& register on the forum ok
Good luck ,,
Phone: Samsung Galaxy S6
Android 6.0.1 - 2 updates since issue bagan
I had the issue where I could not revert to a standard swipe unlock after using a pin, and was told a solution was to clear credentials/certificates.
This solved my problem, but created another. As it stands, about 75% of unlocks it plays one/both of two sounds, which granted do sound like some sort of unlock sound, however not standard to the way the phone shipped. It also happens at random, sometimes as a response to a touch, or just whenever it feels like it. It is one of or both of the same two sounds presented with at unlock. They are ridiculous and am preventing me from using the phone whilst not on silent. The phone has a mind of its own.
NFC is turned off.
I am not tech illiterate and thought I could fix it, however it has beaten me. Any help would be appreciated.
My fingerprint sensor will just stop working and I need to reboot it in order to make it work again. It doesn't detect my finger at all , it's like its dead. I have the Verizon s8+, pre ordered it and got it on 4/20. I don't suffer from the dqa issue but i have another s8 plus, also pre ordered that does suffer from the issue. Anyone know of a fix or know how we can bring this to light in order to get it fixed
Edit: I believe the fix is to go into lock screen and security, after which go to secure lock settings and select the lock automatically option, and set it to immediately. I tested it when my fingerprint sensor wasn't working, and it fixed it for me
Edit #2: That did not fix it forever , issue came back within 30 minutes, from my testing it appears that fidgeting with the following (1. Screen Timeout 2. The Automatic lock timer 3. Lock instantly with power key) causes the issue to disappear or appear. I have contacted Samsung about it and they suggested a factory reset, not giving 2 ****s about the issue, they couldn't even tell me if they were working on a fix.
Edit #3: wow, didn't expect this page to become so popular as I didn't think this was such a big issue, my final solution was turning off fingerprint gestures, haven't experienced the issue after that, I've tried to factory reset the phone multiple times.
P. S. I have been able to achieve better speeds with the Iris scanner, a key trick to getting it to unlock faster is to look right into the sensor, which is the smaller circle next to the camera in the top right corner
Should've clarified the dqa issue is not what i'm worried about, just wanted to point out the weirdness of these bugs, It's the fingerprint issue i'm worried about
Mine does the same thing....TMobile version....It works great, and then randomly won't work at all and I have to reboot
I have the same problem here.
Weird, I noticed this issue today
Posted in the other thread about the same problem. I noticed this today as well. Most of the time significantly moving the phone and scanning my finger again seems to work. I am yet to encounter this issue when the phone is actually unlocked authenticating to an app or something. So far it all seems to be limited to the lock screen in that the phone does not want to register a scan of the finger at all, as though the scanner is not there.
Same
GGgamer16 said:
My fingerprint sensor will just stop working and I need to reboot it in order to make it work again. It doesn't detect my finger at all , it's like its dead. I have the Verizon s8+, pre ordered it and got it on 4/20. I don't suffer from the dqa issue but i have another s8 plus, also pre ordered that does suffer from the issue. Anyone know of a fix or know how we can bring this to light in order to get it fixed
Click to expand...
Click to collapse
Same, I really dont want to get a new one. I need a answer and your the only post of source that has the same problem as me.
Same issues here, very annoying. T-Mobile version. We have two S8 and one of them is working fine, the other one it's having fingerprint issues. Any ideas on how to fix this? I hope is a software issue.
johnminea said:
Same issues here, very annoying. T-Mobile version. We have two S8 and one of them is working fine, the other one it's having fingerprint issues. Any ideas on how to fix this? I hope is a software issue.
Click to expand...
Click to collapse
I think it is software related. It seems to intermittent and in my case seems to be related to limited movement before scanning the finger as I only see this when trying to unlock. In other words, it seems the unlock needs an accelerator event before unlock event to work, and no movement such as a finger resting on the screen doesn't detect.
Have you tried disabling Optimize Battery Usage for the Fingerprint system app?
Mine is doing the same thing. It's almost completey random as to when the fingerprint sensor works. It's not as if it isn't recognizing my fingerprint, it's as if the sensor is completely dead or inactive. I'm tempted to return the phone and re-order but I have a trip coming up that I would like the phone for but if I wait until I return I will be past my 20 days.
Very frustrating after having to return my Note 7 like 3 times.
Does this seem software related?
Not sure it is software related. I have another S8, same carrier (T-Mobile) same firmware same software updates, version etc. Both came on April 19. Mine is having issues since I got it, the other one 7 days later no issues at all. I called Samsung and they told me if a factory reset does not solve the issue, to go to the store and get a new one. I will get a replacement tomorrow. I am on the edge with Samsung coming from a Note 7 user....
johnminea said:
Not sure it is software related. I have another S8, same carrier (T-Mobile) same firmware same software updates, version etc. Both came on April 19. Mine is having issues since I got it, the other one 7 days later no issues at all. I called Samsung and they told me if a factory reset does not solve the issue, to go to the store and get a new one. I will get a replacement tomorrow. I am on the edge with Samsung coming from a Note 7 user....
Click to expand...
Click to collapse
That's good to know. I ordered mine online through T-Mobile and they require me to send it back through the mail. They won't let me exchange it in store. So dumb. They also won't send me out the replacement before I send the broken one back. Looks like I will be without a phone for a few days.
I'm getting real sick of this loss of quality control with Samsung.
'
Yeah same here, but. You can call customer service and ask them to send the replacement phone at a store near you. This is what they have done for me. I will go tomorrow to pick up the replacement phone and I will give them back the old one. Is stupid but it is what it is. I think because the stores are individual franchises, maybe. who the heck knows. If the second one does the same I am pretty much done with Samsung. I had enough with my Note 7, now this. grrr
So this morning I once again had the sensor shut down. It's not just on the lock screen. After unlocking with the pin I was unable to use the fingerprint sensor to bring the notification menu down either.
I'm going to go to Verizon after work today and get a replacement.
I had no time to go and get the replacement today. However, no issues in the last 48 hours. For some reason is just working. I might go tomorrow and get a new one just to be on the safe side, I hope.
johnminea said:
I had no time to go and get the replacement today. However, no issues in the last 48 hours. For some reason is just working. I might go tomorrow and get a new one just to be on the safe side, I hope.
Click to expand...
Click to collapse
Mine happened first on 4/20 and it had not done it again until today. So I'm just going to go in and exchange it.
Gary02468 said:
Have you tried disabling Optimize Battery Usage for the Fingerprint system app?
Click to expand...
Click to collapse
Where is that setting
Well I took the phone into Verizon and they refused to exchange it. They said it's a software problem.
Gary02468 said:
Have you tried disabling Optimize Battery Usage for the Fingerprint system app?
Click to expand...
Click to collapse
I just did it, when Imade the thread I didn't know where to find the option, upon looking further I found it.
For anyone wondering, go to apps, then app manager, then in the upper right corner click on the option icon , then click on special access, then click on optimize battery usage, then click on "Apps not optimized" and then select "All apps", then scroll down and look for Fingerprint app(I don't know if this is the only app having to do with the fingerprint sensor) and untoggle it.
P.S. I dont know if this works or not, as I have not experienced the bug for over 36 hours
Edit: this did not work, I just experienced the bug again, the fix is to go to
lock screen and security, then to secure lock settings, and set the automatic lock to immediately.
Edit #2: This did not work , see OP for more info
Since I got the phone, while in pocket, I reject/answer 80% of the calls. I was under the effect of "yay nexus is back, google finally gave us a cheapster" so didn't really got bothered. But days are passing by and it's getting quite annoying, so to the point, could anybody tell me why this phone wakes up the screen on incoming calls when the proximity sensor is covered (ie. in pocket?) (if it's "normal" to do so, then why?). Proxi switch is fine, it triggers during calls and shows activity on sensor testing apps and whatnot. Default calls screen and whatsapp incoming calls, (heck I can unlock the phone with the fingerprint reader in my pocket without taking it out, now explain that.) ... Cherry on top the "slide to answer" thingy is vertical, so yeah there is the problem (while sliding it out from the pocket, it answers or rejects the call). I'm considering throwing it out lol it's so annoying lately. Android 9 was the same? (I had 3 android one phones to fill the superexpensive 3 generation pixel gap) Was I living under a rock? Can anyone try it? Thanks for the helpful inputs in advance.
strapabiro said:
Since I got the phone, while in pocket, I reject/answer 80% of the calls. I was under the effect of "yay nexus is back, google finally gave us a cheapster" so didn't really got bothered. But days are passing by and it's getting quite annoying, so to the point, could anybody tell me why this phone wakes up the screen on incoming calls when the proximity sensor is covered (ie. in pocket?) (if it's "normal" to do so, then why?). Proxi switch is fine, it triggers during calls and shows activity on sensor testing apps and whatnot. Default calls screen and whatsapp incoming calls, (heck I can unlock the phone with the fingerprint reader in my pocket without taking it out, now explain that.) ... Cherry on top the "slide to answer" thingy is vertical, so yeah there is the problem (while sliding it out from the pocket, it answers or rejects the call). I'm considering throwing it out lol it's so annoying lately. Android 9 was the same? (I had 3 android one phones to fill the superexpensive 3 generation pixel gap) Was I living under a rock? Can anyone try it? Thanks for the helpful inputs in advance.
Click to expand...
Click to collapse
There is no pocket mode on stock firmware. If you'd like to add one you can use Edxposed and the dark tricks module.
Sent from my Google Pixel 3a XL using XDA Labs
As hard as I'm trying, I start to see it's nearly impossible to be completely satisfied with the stock android experience. I gave up rooting, flashing, modding long time ago. Ain't got time for that. This leaves one choice, a sad but with time will get used to it.
strapabiro said:
As hard as I'm trying, I start to see it's nearly impossible to be completely satisfied with the stock android experience. I gave up rooting, flashing, modding long time ago. Ain't got time for that. This leaves one choice, a sad but with time will get used to it.
Click to expand...
Click to collapse
Do all 3a do this? I am looking into buying one but don't want to deal with something like that. This is exactly the reason I decided not to buy Galaxy S10e - just try to Google "S10 proximity sensor". It was never officially acknowledged/fixed by Samsung and over the time people just seem to "get used to it" and stop talking about it.
I don't know mate, that's why I asked others to try it please, it's really getting on my nerves and funny thing is, these kind of problems are a hit or miss on warranty claims ... doesn't even worth to try ... and I don't want to take this to reddit either because it'll only get downvoted to a lower than hell level by biased fanboys not to mention the google product forums with the "platinum product experts" and their generic "try this and try that" answers.
So yeah I'm angry.
strapabiro said:
I don't know mate, that's why I asked others to try it please, it's really getting on my nerves and funny thing is, these kind of problems are a hit or miss on warranty claims ... doesn't even worth to try ... and I don't want to take this to reddit either because it'll only get downvoted to a lower than hell level by biased fanboys not to mention the google product forums with the "platinum product experts" and their generic "try this and try that" answers.
So yeah I'm angry.
Click to expand...
Click to collapse
I never had issues, but probably I don't understand the issue yet, so I have a question: how do you know screen is waking up in pocket? For sure it's waking up if you move the device, i.e. take is off the table or turn it around. Are you sure screen switches on in the pocket and not while you are taking it out?
AndDiSa said:
I never had issues, but probably I don't understand the issue yet, so I have a question: how do you know screen is waking up in pocket? For sure it's waking up if you move the device, i.e. take is off the table or turn it around. Are you sure screen switches on in the pocket and not while you are taking it out?
Click to expand...
Click to collapse
You can test by trying to unlock the device while covering the proximity sensor.
Without any mods it'll unlock.
But like that's the main benefit to a Google phone running stock firmware. It's a perfect base for mods.
Sent from my Google Pixel 3a XL using XDA Labs
Skittles9823 said:
You can test by trying to unlock the device while covering the proximity sensor.
Without any mods it'll unlock.
But like that's the main benefit to a Google phone running stock firmware. It's a perfect base for mods.
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
This ... Or cover like 80% of the screen, leave only a small bar uncovered on the lower part of the phone (usbc port side) and ask someone to call you. You'll see on the remaining uncovered part that the screen woke up which is hilarious. Honestly at this point I don't understand how a feature like this can be overlooked by r&d.
Sadly modding is no option for me, for safety and other reasons.
There is another thread about this in the 3a xl section, hope it doesn't count as duplicate.
strapabiro said:
Sadly modding is no option for me, for safety and other reasons.
Click to expand...
Click to collapse
What reasons? This is a Google phone. You're allowed to unlock the bootloader and flash modified software without breaking warrantee.
If you have issues, it's easy to just flash the factory image back to completely stock and relock the bootloader.
Sent from my Google Pixel 3a XL using XDA Labs
@strapabiro,
Have you tried this app?
Skittles9823 said:
What reasons? This is a Google phone. You're allowed to unlock the bootloader and flash modified software without breaking warrantee.
If you have issues, it's easy to just flash the factory image back to completely stock and relock the bootloader.
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
You're shifting the subject, but the short answer is, imagine I never had an apple product in my life but I rather buy an iphone than start doing that But that's me and that's another topic like I said, thanks though.
strapabiro said:
You're shifting the subject, but the short answer is, imagine I never had an apple product in my life but I rather buy an iphone than start doing that But that's me and that's another topic like I said, thanks though.
Click to expand...
Click to collapse
Fair argument.
Sent from my Google Pixel 3a XL using XDA Labs
Today I had my phone in my coat pocket at an appointment for about an hour hanging on a coat rack not even being touched. When I came back to, the screen was on, on the lock screen, and if was pretty warm with battery down a good 25 percent. I'm wondering if what you're talking about here has something to do with this? I was confused why or what was going on with it. No unusual apps were in memory in developer settings.
kc6wke said:
@strapabiro,
Have you tried this app?
Click to expand...
Click to collapse
I have found this "feature" annoying as well on my 3a XL. However I tired the app that you suggested and it seems to work fine. Thanks for providing a decent solution to the OPs question.