Database Info

[Q] Intermittent call volume drop

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.

[Completed] Had to clear credentials due to lock screen issue, now phone makes a series of wierd

Can't edit title, forgive for lack of detail.
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.

BigDrewy1 said:
Can't edit title, forgive for lack of detail.
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.
Click to expand...
Click to collapse
Greetings and welcome to assist. It looks like you already found the correct place to ask your question here
http://forum.xda-developers.com/showthread.php?p=69454465#post69454465
so I'll close this one up
Good luck
Sawdoctor

cleared credentials/certificates, phone now makes series of odd unlock noises

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.

Watch only vibrates once and then no more until a reboot

I just got the Gear Fit2 Pro this week and began using it yesterday as I also have a Gear S3, so the first thing I noticed is that I was missing all my notifications. The watch doesn't have a speaker so we just rely on the vibration to know that we got a notification.
At some point yesterday I noticed that I had about 4 or 5 emails and other notifications pending but never felt the vibration, so I immediately went to the settings to see if there was a Vibration intensity or something but I just noticed that the only other option besides the vibration on and off is the long buzz, so it should vibrate longer for each notification. I decided to give that a try but the same thing, no vibration with the notification.
I decided to reboot the watch and then as soon as I received the first notification it vibrated but then no more vibration after that, so it seems that it only vibrates once after each reboot (I have tested it a couple of times now).
Looking around on Google and other forums I can't find another Gear Fit2 Pro with the same issue but there are dozens of similar reports from Gear Fit2 users, one of them worried me a little as he said that it was fixed only asking for service from Samsung, I think he mentioned that they replaced the vibration motor or something.
Problem for me is that I got this used on Swappa, no receipts, so no service from Samsung (I don't live in Continental US so here in Puerto Rico we don't exist for them) plus the seller, original owner, insists that it was working fine when he had it. I know that I can always open a claim on Paypal and ask for a full refund but I was just wondering if this is indeed a software issue and not hardware, I mean, it works after a reboot, that alone tells me that it may be software related. So I'm wondering if someone else is having or had a similar issue and if it was solved, somehow.
I've resetted it twice now and I'm currently testing it again, I just did a reset an hour ago, so I'm hoping for the best, but if you have any more details about this I'd really appreciate any help you may provide to me, thanks

I've the same issue it vibrates only one
Sent from my [device_name] using XDA-Developers Legacy app

erasat said:
I just got the Gear Fit2 Pro this week and began using it yesterday as I also have a Gear S3, so the first thing I noticed is that I was missing all my notifications. The watch doesn't have a speaker so we just rely on the vibration to know that we got a notification.
At some point yesterday I noticed that I had about 4 or 5 emails and other notifications pending but never felt the vibration, so I immediately went to the settings to see if there was a Vibration intensity or something but I just noticed that the only other option besides the vibration on and off is the long buzz, so it should vibrate longer for each notification. I decided to give that a try but the same thing, no vibration with the notification.
I decided to reboot the watch and then as soon as I received the first notification it vibrated but then no more vibration after that, so it seems that it only vibrates once after each reboot (I have tested it a couple of times now).
Looking around on Google and other forums I can't find another Gear Fit2 Pro with the same issue but there are dozens of similar reports from Gear Fit2 users, one of them worried me a little as he said that it was fixed only asking for service from Samsung, I think he mentioned that they replaced the vibration motor or something.
Problem for me is that I got this used on Swappa, no receipts, so no service from Samsung (I don't live in Continental US so here in Puerto Rico we don't exist for them) plus the seller, original owner, insists that it was working fine when he had it. I know that I can always open a claim on Paypal and ask for a full refund but I was just wondering if this is indeed a software issue and not hardware, I mean, it works after a reboot, that alone tells me that it may be software related. So I'm wondering if someone else is having or had a similar issue and if it was solved, somehow.
I've resetted it twice now and I'm currently testing it again, I just did a reset an hour ago, so I'm hoping for the best, but if you have any more details about this I'd really appreciate any help you may provide to me, thanks
Click to expand...
Click to collapse
It is good to listen!!!!!!!!!!!!!

Samsung S6 (Verizon) reactivation lock help

Hi all-
History of issue - wife & I upgraded phones, but we kept our old Samsung S6 phones for kids to use in school. These are SM-G920V (Verizon phones), but we had switched to T-mobile network. Son's S6 went fritzy - started freezing, randomly reloading, black screen w/flashing blue light until battery ran out, etc. It could boot, but wouldn't stay up. I think some update corrupted memory or something. I tried to factory reset it to get it back to beginning state, but was NOT aware I needed to remove the Samsung account associated with the phone. I'm not even sure I could have, it wouldn't stay up long enough w/o freezing or black screen. Regardless, factory reset didn't work, as when it booted, it eventually had the dead android show up. So I went online, found info about how to flash the phone with the correct Verizon file using Odin to download it, and now it boots android 7.0. However, then I hit the Samsung reactivation lock. It asks for an account/password, which I have, but it won't validate or go to the next step.
I talked to T-mobile tech support, and according to them, it's due to it being originally a Verizon phone on an account that is now deactivated since we switched to T-mobile. They can't do anything, but gave me contacts to 3rd party vendors that could fix/flash it if I could prove I originally bought it. As I used to be w/Verizon, I should be able to find the activation docs of the phone and provide proof, but the "fix" will probably cost upwards of 70+ (maybe closer to $100) for an old S6, which may or may not have as much life left to it. If I'm spending that much $$, I might as well get a cheaper new phone.
However, I'd rather not spend the $$ if I can help it, so am trying to figure out how to fix/flash this and remove the Samsung reactivation lock myself. My understanding is I need some sort of combo file that I can download using Odin, and that there's a process by which you can remove it that way. However, I can't seem to find the combo file for SM-G920V, and am not entirely sure of the steps. I've tried the emergency call method I saw online, but besides having a nice conversation with the 911 folks, I didn't see any of the buttons that the videos specified, maybe because it's android 7.0.
Does anyone have a good tutorial on how to get rid of this, so I can salvage the phone for son's use? I've read some of the XDA forums, but haven't been able to figure out the right steps. Any help would be greatly appreciated.
ET