yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Q&A, Help & Troubleshooting] Nikon5400:
Your microphone must not be next to your lips.

I'm not saying you'll be happy with Nexus, because that issue DOES exist for everyone. People just don't know about it. The sound quality coming out from this mic is not on par with Samsungs. But, in my experience if you hold the mic next to your lips, you will be heard, but no matter what you do, it won't be as good as if you had samsung... except maybe for speakerphone where your voice is picked up pretty good, maybe on par or better than samsung, maybe not-not sure on that one

hopefully 4.4.3 will fix it. if not, then headset maybe the way to go. IMO, if call quality is the most important thing - samsung, but the background noise may be trade off with samsung
[Nexus 5 Q&A, Help & Troubleshooting] Wutang200:
If I hold the phone any closer to my lips, I'd be kissing it! Trust me I'm holding it as close to me as is physically possible.

I'm hoping the Moto X gives me the clear call quality of the Samsung with a properly working noise cancellation system instead of the broken one on the Nexus 5.

There's nothing in the release notes for 4.4.3 that tells us that they've fixed this issue which is why I've decided to just get a full refund from Google. If it was added to this update, the Google rep would have advised me to hang on until I've had the 4.4.3 update.
[Nexus 5 Q&A, Help & Troubleshooting] Nikon5400:
Google reps don't know anything. Talking to them for anything other than rma or refund is a waste of time.

I hope mic issue falls into "miscellaneous fixes" category. I think this issue is huge and am surprised not many people notice it.
[Nexus 5 Q&A, Help & Troubleshooting] ContextM:
If you go on skype call (with loud speaker), you will notice that the the other party will start hear echoing, the only way to stop this is to put it off the loud speaker
[Nexus 5 Q&A, Help & Troubleshooting] drago10029:
Has great call quality, no dev support like the N5 though. My Moto has some bugs too so beware hahahahaha!! #evil laugh but seriously. Plus side is Moto engineers will actually talk with you about your problem if you tag them on Google +! I think that's a win!
[Nexus 5 Q&A, Help & Troubleshooting] Wutang200:
Fully understand and thanks for your feedback of the Moto X. I'm not bothered about rooting and trying different ROM's etc as I feel they just clutter the o/s with loads of extra settings all over the place.

That makes me a lot happier knowing that I can get in touch with Moto engineers. That's one thing that I've not managed to do at all with Google. It's like talking to a robot who only ever gives you 2 replies lol (replacement or refund).

Being able to make proper phone calls will be a big relief.
[Nexus 5 Q&A, Help & Troubleshooting] drago10029:
Well that replacement or refund thing does happen when I call in about the issues I'm having. I didin't feel like reaching out the those guys, I been lazy lol

But I made a post once about a warranty request and they actually responded!!
[Nexus 5 Q&A, Help & Troubleshooting] Wutang200:
Finally got my Moto X 16GB.

Specs wise, I wouldn't say it's an upgrade from the Nexus 5 but not a downgrade either.

The O/S is nice and clean with just a few useful features added by Motorola.

Absolutely loving the Active Notifications, Motorola Connect (text from my Chrome), Motorola Assist etc. They're so useful.

Best feature is the voice recognition. It's so accurate it's scary lol. Much more accurate than the Nexus 5.

Best of all, call quality is superb!

The screen is smaller but my thumb used to often struggle to reach certain parts of the Nexus 5 screen which I don't have to worry about any more. I think it's a good balance between size and comfort.

The speaker is miles louder than the one in my N5. Massive difference!!

The phone feels fluid as the N5.

There's only one area I've noticed any slowness so far. That's in restoring my 16000+ text messages. It took a fair bit longer than my N5 did. Not a big deal though as only needed to do it once.

I've got a usable phone and some money in my pocket on top. Can't complain :laugh:

---------- Post added at 11:16 PM ---------- Previous post was at 11:12 PM ----------

Oh that Motorola Migrate feature didn't work for me when I tried it. Only tried it once though.

Most of my stuff is in the cloud anyway.

Used SMS Backup & Restore app to transfer text messages across. Highly recommended SMS management app.
[Nexus 5 Q&A, Help & Troubleshooting] rockknee:
Someone is talking s**t now.. Google's support guy Paul told on their own forum ( https://productforums.google.com/forum/m/#!topic/nexus/0hvTK4eMVGk[126-150-false]) couple months ago that they have reproduced the issue and they are working on it and James on your messages says that your issue is unique. That sounds very weird to me, like they wouldn't know or tell everything. Basically google's forum is about bad audio quality on videos but some people seem to have also problems on phone calls. I have only had video issues, but after flashing camera MOD V1.5 issue has been way smaller. Never had issues with phone calls.. Or then I'm just speaking louder than others :D Anyways apart from little mic problems I'm very happy with this device.
[Nexus 5 Q&A, Help & Troubleshooting] Wutang200:
I couldn't care less note that I've got my Moto X. Not had a single issue with phone quality.
[Nexus 5 Q&A, Help & Troubleshooting] Jur1nator:
Cool story bro... Nice to rub it in :p
[Nexus 5 Q&A, Help & Troubleshooting] Globespy:
I've also began my 'process' with Google Play Store, followed the usual 'script' read steps - stock phone, safe mode, turn off Bluetooth, turn up all volumes, see if problem is resolved!!?? If the problem isn't resolved (of course it won't be), then they want to send me a new device, which will be the latest build. I advised the dude if this thread and that others have gone through up to 9 devices, all with the same issue - it's clearly an inherent issue with the phone and I tried to impress this upon them. But they don't care, I guess I will have to go through multiple RMA's until they eventually give me a full refund. It's a smart approach by them, similar to most other large companies - wear down the customer as most will 'fold' and just accept that the number 1 function of their device is dysfunctional!

Would love to find enough people with this problem and then create a basic website where people can see how this situation will play out and have Google simply bombarded by RMA's at such a massive volume that they will quickly realize the cumulative cost of replacing hundreds if not thousands of devices and the associated paid return postage is simply to much to handle and will either provide an actual solution (microphone hardware update) or just give people their money back.

The publicity would be extremely damaging and ensure that in the future they pay much more attention to design and customer feedback.

But, most people are simply to lazy to follow through with this kind of determination and that's why these companies screw people over every day.
[Nexus 5 Q&A, Help & Troubleshooting] Wutang200:
I very much doubt anything will happen now regarding a fix for this issue as the Nexus 6 will be announced in just a few months and all the attention will be on that.

It makes me feel like I definitely made the right decision in changing to another phone.

The mic quality on my Moto X is so good, I can have it on my suction holder thing on my cars windscreen and get it to make phone calls using my voice then put it on speakerphone and the call quality is so good that nobody can tell that I'm using it in speakerphone mode!
[Nexus 5 Q&A, Help & Troubleshooting] rockknee:
Mic quality great here as well on Nexus 5, absolutely zero problems with call quality. Let me remind you: every N5 doesn't have that miserable call quality like you had... But I have to say video audio quality could be better.
[Nexus 5 Q&A, Help & Troubleshooting] bblzd:
If 100% of Nexus 5 couldn't make phone calls, you'd know about it. There's only one person in this 8 page thread who claims so.

Most users don't even know this bug exists. It's not as widespread as you might think.
[Nexus 5 Q&A, Help & Troubleshooting] sam1forever:
It is a widespread issue. Just not posted on XDA but on Google forums.

https://productforums.google.com/forum/m/#!topic/nexus/JZGA5p-VX1A
[Nexus 5 Q&A, Help & Troubleshooting] bblzd:
How many of them claim the microphone is faulty 100% of the time? I'm guessing not many.
[Nexus 5 Q&A, Help & Troubleshooting] sam1forever:
Just to clarify it is an issue. Just not 100% of the time. It happens on and off. I completely agree with you lol.:angel:

Non the less. Can't wait for 4.4.3 :D
[Nexus 5 Q&A, Help & Troubleshooting] bblzd:
Agreed. I actually didn't mean to imply many people weren't experiencing it to some degree, just that the vast majority of users are unaffected by it in their daily operations.

I've met a few N5 users "in the wild" and none are aware of microphone issues during calls. To claim it's unusable as a phone is pretty ridiculous.
[Nexus 5 Q&A, Help & Troubleshooting] Wutang200:
The 11 Nexus 5's that Google sent me were all unusable as a phone. My definition of 'usable as a phone' is when a call comes in, I slide the thing on the screen to answer it and place the phone against my ear holding the phone like you'd expect it to be held. Loudspeaker isn't really classed as using it as a phone neither is shouting down the phone or talking into the top of the phone etc. Things I already tried when I had mine.

There's only so much us as a consumer can do to get around this issue.

It wasn't just the microphone for me. The audio used to massively break up too to the point where my contacts would get very pi$$ed off after I kept asking them to repeat every single sentence several times. I'm sure you would too.

Google failed to acknowledge there was any problem with the phone. So far I've not met anyone who hasn't got this issue. My sister has the Nexus 4 which also has this issue but not as bad as my Nexus 5 did.
[Nexus 5 Q&A, Help & Troubleshooting] Globespy:
Of course not! Mine isn't problematic 100% of the time either. But happens every other day, and over a week of calls it's annoying enough to realize that there is something wrong. I would bet that there are more people who have experienced this than you think but just put it down to a poor call connection.

The fact still remains that it does and probably will continue to happen to the majority of owners at one time or another and they just don't mention it. I would bet that the majority of N5 owners don't post on XDA, so the problem is much more widespread than you are assuming. The majority of people who buy phones don't frequent these types of forums and aren't geeky critical thinkers like many on here. That way a problem remains hidden.

It would be interesting to see the results of a poll that millions of people saw online or on their Facebook page asking if they have ever had this mic problem.... Quite astounding I would think.
[Nexus 5 Q&A, Help & Troubleshooting] bblzd:
So if some one was to say they've had 9 or 10 phones, none of which were ever able to make a single working call, from a trouble shooting standpoint we could safely assume it's a different issue than the intermittent noise cancelation issue which we can all agree is fairly common.
[Nexus 5 Q&A, Help & Troubleshooting] PhilipTD:
Maybe Google didn't send you eleven phones. Maybe they sent you one phone eleven times. Otherwise, it's a statistical miracle.
[Nexus 5 Q&A, Help & Troubleshooting] *system error*:
Hi guys. I had in call mic problems on my N4.

Try this... Rooted, edit the line in your build prop that says persist.audi.mic.type. change from digital to analog. Worked like a charm for me on the N4 flashing different roms.

Also if that doesn't work try the app called soundabout

Sorry for the bad luck hope it helps you out.
[Nexus 5 Q&A, Help & Troubleshooting] jlmcr87:
Eleven phones:eek:? Are you crazy?:silly::silly::silly:
[Nexus 5 Q&A, Help & Troubleshooting] Globespy:
If a phone has even intermittent issues with the number one most basic function (talking to other people), it's a huge fail. My $25 pre paid flip phone NEVER has this issue. It's a functionality that's simply not ok to be problematic.... It shouldn't have these issues, period.

Not sure why you would want to justify that even intermittent problems with calls is acceptable?

If your car didn't start a few times a week, would you feel the same way and just accept it?

Before all these fancy features that these phones have, the main purpose was to talk to other people and expect that they could hear you and you could hear them. One would think that this feature should be pretty much fault free.

It's embarrassing when a client can't hear you and since most of us consider our cellphone to be an essential tool, it's not acceptable. Some of us don't spend our days playing angry birds or texting every 10 seconds. There's more important uses that have to work 100% of the time. I can accept a poor signal or dropped call, but not a known issue that's being ignored by Google.
[Nexus 5 Q&A, Help & Troubleshooting] bblzd:
Personally I put up with the "issue" because its blocked out only a couple words (which I repeated and was then heard) in 5 months. All those times I was lying down and its not happened since.

The phone must've thought that guys voice is noise there's not really any other explanation. That or his network has issues with the phone.
[Nexus 5 Q&A, Help & Troubleshooting] deamonix:
Workaround confirmed

This issue has finally been resolved on my phone, and I couldn't be happier with the results.

Root is required for this modification so... PROCEED AT YOUR OWN RISK!

1: Replace the following lines in your build.prop using an editor. I used Rom Toolbox Pro, but many free build.prop editors are available in the play store.

persist.audio.handset.mic.type=digital --> replace digital with analog

persist.audio.dualmic.config=endfire -- replace endfire with false

2: Reboot & enjoy clean call audio.

I have not had any detrimental effects to implementing this change. Google Now voice commands, VOIP calling were unaffected by this change.
[Nexus 5 Q&A, Help & Troubleshooting] vertas2:
persist.audio.dualmic.config=endfire -- replace endfire with false

if i replace "endfire" with "false" than is it close-deactivate the second mic (Noise-canceling microphone) thank you..
[Nexus 5 Q&A, Help & Troubleshooting] niteowl360:
Very eloquent.

Exactly the crux of the matter.

And why I had to return the device I actually really loved using.

Htc One M8 will be the replacement.

I've used Htc devices for nearly a decade, and will continue.

My experiment with Nexus 5 was mainly to enjoy the latest Android devices and to test my Play Store clocks on the most up to date Android release.
[Nexus 5 Q&A, Help & Troubleshooting] *system error*:
That's so awesome! Glad it worked. Lol I recall one time I installed PA. Late for work on the way called... "Hello... Hello" edited build prop rebooted immediately worked.

I personally do not have the issue on my N5 knock on wood.
[Nexus 5 Q&A, Help & Troubleshooting] deamonix:
As far as I can tell that is in fact what it is doing, although when using a VOIP app with noise cancelling it works just fine.
[Nexus 5 Q&A, Help & Troubleshooting] Keigi:
Wow man... This definitely works! Finally a decent solution, hope Google fix it in 4.4.3
[Nexus 5 Q&A, Help & Troubleshooting] Nikon5400:
What are the side effects of this fix?

Can anyone who has access to two nexus 5s do this test:

1. Make the changes above to one of the phones

2. Place a call from both phones at the same time to a 3rd line and leave a voice mail (This way you'll end up with 2 identical messages)

3. try to talk with mics 2 inches away from you mouth, then 4 inches, 6 inches, etc

4. Make some background noise while leaving a message (tv or something)

Nexus 5 is good at suppressing background noise. How's the background noise now? If it's tolerable and the voicemail message is a lot clearer, then the issue i's solved!

Thanks

P.S. If you could also upload the 2 messages for us, it'd be awesome. Thanks
[Nexus 5 Q&A, Help & Troubleshooting] *system error*:
I don't think you need to cancel out the other mic. Endfire false.

I always only changed the digital to analog.
[Nexus 5 Q&A, Help & Troubleshooting] Keigi:
I will test this. Thanks
[Nexus 5 Q&A, Help & Troubleshooting] markdapimp:
I hate to bring Android 4.4.3 discussion into this but it may seem they have fixed this on that update

the Nexus 5 and the LG g2 has the same microphones but the G2 has 1 more mic for Audio Zoom. Recently LG released a patched where some people have reported the Hissing noise has been removed (I will research on this further)

But on my experience try this have a phone call while in a car (Not driving lol, Stay safe) roll down the windows and do a call, I call this the Window test.. The Nexus 5 immediately has some issues with the Microphone gain and it actually picks up your own voice and echo's it into the earpeice.

I have 2 other devices to test with my Note 2 and a Moto G both passed with flying colors. The next day I tested with the LG g2 and Nexus 5

Both showed similar issues but the G2 has a bit more of like a hissing sound with slight echo into the earpeice.

Now here comes the scary part it's Looking ALOT like a hardware issue, take this thing into concerts the Audio is Un usable. Just like with the Sony Xperia Z and yet no peep has been said from sony about that issue and same with the galaxy s3 being on 4.3 already and it still shows the audio problem in concerts and loud environments.

Just face it LG placed a horrible mic into the G2 and the Nexus 5 (Cough cough same OEM)

in environments where there is no bass present the nexus 5 and G2 outshine competitors with crystal clear audio, Turn the tables around and "raise the roof" :good: and you get something that is very unpleasing.

Heres the Galaxy S3 with the same Audio gain control problem https://www.youtube.com/watch?v=qYRPWPfcCqg compared with a Nokia Phone

in this environment the phones I listed above with the problem have no issue with this.

https://www.youtube.com/watch?v=ZekzZH23GtI

Galaxy S3 and HTC One (HTC one has a proper microphone setup)

https://www.youtube.com/watch?v=SaL87kEqZ4Y

https://www.youtube.com/watch?v=vlzotUTrd1Q (Nexus 5) Sound's alot like the S3 in that video above

https://www.youtube.com/watch?v=S4408BIegsk

Here's the Nexus 4

https://www.youtube.com/watch?v=iISFyYC5tvE

Hmm the Nexus 4 is atleast a year old and started with Android 4.2 has been Updated to 4.3 then 4.4 then 4.4.2 and still shows this problem clearly a software update isn't going to fix the nexus 4.

So what were possibly looking at here is possibly hardware and will continue to stick with the phone for the rest of its life

Sure a software update will improve it (possibly) but it will show the same problem sadly

Only time will tell from now, What I'm predicting is Google will add a Menu like on the LG g2 to toggle on/off the Noise cancellation microphone within settings. Who know's they might even fix it after all LG and Google work closely on the Nexus Line :highfive:

HTC clearly knows what they're doing when it comes to Sound related (High Quality DAC,Good Microphones,Boomsound)

HTC has also one thing deployed from other smartphone makes even apple

they know what's up with sound!

Lets hope HTC will get a turn in the Nexus line again.
[Nexus 5 Q&A, Help & Troubleshooting] Jishnu Sur™:
I really don't think its a hardware issue. I have adjusted the mic gain to a certain value and this microphone issue is gone actually to a certain limit. The noise cancellation mic kicks in more than the normal mic so that is the issue. I couldn't find the lib for it as well..
[Nexus 5 Q&A, Help & Troubleshooting] markdapimp:
Well We will see when 4.4.3 comes out I hope it falls under Internet telephony fix or miscellaneous fixes in the change log
[Nexus 4 Q&A, Help & Troubleshooting] ykram:
Kit-Kat OTA came out for my Nexus 4 today and I went to apply it but during the install it errored out and the phone subsequently enters a boot loop. I can get into a recovery shell and attempt to push the update via sideload but I get an error:

Symlinks and permissions...

set_metadata_recursive: some changes failed

E:Error in /tmp/update.zip

(Status 7)

Installation aborted

I'm 99% sure there's a binary in /system/xbin/ or /system/bin/ thats set immutable (chattr +i) causing this to fail but I can't launch an adb shell from recovery to fix this. Can anybody help me out here?
[Nexus 4 Q&A, Help & Troubleshooting] eksasol:
Are you using stock recovery to do this?

You pretty much explained why, but if you had rooted the phone it could fail due to other reasons too.

If you have an unlocked bootloader then you can boot TWRP (not install, but boot by fastboot boot twrp.img), it have its own terminal and you can go in and chattr -i that file.

Or with unlocked bootloader you just "fastboot format system" and flash the full system.img from the factory image. Or use TWRP to flash a stock rom.

I don't see how else you could have ran a chattr command to the /system without root. But without an unlocked bootloader you pretty much only have the choice of factory reset or unlock the bootloader in which both will wipe all data. But I'm pretty sure beside fastboot erase and format, not even factory reset in recovery could get rid of an immutable file. There is no adb access in stock recovery beside adb sideload signed packages (otherwise every android phones will be very unsecure).
[Nexus 4 Q&A, Help & Troubleshooting] ykram:
Unfortunately, you're correct. I was rooted at one point and had an old 'su' binary around that was immutable, completely forgotten about. My bootloader is stock atm and I'm still stuck on 'no command' I'm accepting the inevitability that I'll have to wipe and start over but I'm not even sure how to flash the factory firmware now since I'm either stuck in a 'Google' boot loop or I get 'no command'.

Any suggestions?
[Nexus 4 Q&A, Help & Troubleshooting] eksasol:
When you see no command that is normal. To bring up the stock recovery menu, while holding Power first, press Volume Up.

Google bootloop have nothing to do with flashing factory image since it required using fastboot in fastboot mode (not in recovery), aka the bootloader menu. Links in my signature have instructions to flash factory image.
[Nexus 4 Q&A, Help & Troubleshooting] ykram:
Cool, gotch ya. Many thanks for the response and help.
[Samsung Galaxy Mega] maburgess81:
I have had my Mega since release day in US in August. I am starting to get little small lines on the screen both horizontal and vertical. It looks like little lines of pixels acting up.

Any ideas of what's going on?
[Windows Phone 8 Q&A, Help & Troubleshooting] danmarce:
I was reading this thread about how to install Stock ROMs in the Lumia phones.

The process seems pretty easy. But since I'm a lurker the system did not allow me to make my question there. So here it goes.

If the phone was from a carrier, say AT&T, and it was unlocked by them to be used in any network, will the installation of a stock ROM:

1) Keep the phone unlocked because, DUH! is stock firmware

2) Keep the phone unlocked because it was unlocked before

3) Lock the phone again because some setting is lost

So, any idea about this? The installation of a stock ROM would be a solution to unlock a Lumia phone?
[Windows Phone 8 Q&A, Help & Troubleshooting] thals1992:
No. To SIM unlock one the only way is to enter the code given from the MO that branded the device. Now... if the device has been previously been unlocked, it will persist flashing because the cellular settings are untouched when flashing. (Unless its stuff relating to the MMS and internet APNs, that will be overwritten when it is reflashed.)
[Android Q&A, Help & Troubleshooting] TimmyP:
Or no grid. I would love this, its gotta exist somewhere.

Anyone provide any insight? All I can find is info about old modded versions of Go launcher, not even a download to try it out.