Develop Bugs

Is this par for the course?

So picked this phone up yesterday and so far the major issues i've come across are:
Random touch screen issue - I'll use the phone normally for a while but sometimes when i'm playing a game (NOVA... which i deleted now) or strolling through a menu (happened in olive tree reader and the amazon store) a small area of the screen will spaz out... it's also happened on the stock lock screen and then persisted a few seconds after I rebooted to get rid of the issue. It's annoying because just as soon as I'm ready to chalk it up as a fluke or some random app issue... it shows up again somewhere else. Now.. this isn't during "one handed operation".. the device is in my left hand.. no fingers on the screen... using my right index finger to do the navigating.
Quite a few apps just don't work - all of my gameloft stuff, Age of Zombies, the video creator app (Samsung... your own freeking app?!?), and a handfull of others either crash immediately, don't start, or crash after seemingly opening just fine. Sidenote... so after a night off it's feet Age of Zombies is working this morning.
signal issues - the reception on this phone it utterly attrocious. I'll go from 5 bars (never the full 6) down to 2 without moving... which means it's a grip issue. I've cupped the bottom portion of the phone (around where the capacitive buttons and the back "lip" are) and watch my signal degrade while removing my hands brings that signal right back... also.. i'm ONE ROOM over from my wireless router and the signal hovers around none to 2 bars on the wifi indicator... HOWEVER... now that I'm at work.. i'm on my corporate wifi.. great reception... cell strength? 5 or 6 bars.... what the feezy.
So.. in a nutshell are these issues normal? should I return this for another unit? I absolutely LOVE this phone... as a pda. It's fast, i dig the large screen, i heart android and touchwiz is actually kinda cool so i may not root this thing with all that said it's just been a little unreliable and I need to be sure that this device will work when i need it to.
Thanks for the input guys.

Reception is a known problem that sprint has acknowledged, they say they are working on a fix.
The screen spazzes out when charging, if it is spazzing out at other times your phone is not normal.
Apps crash sometimes when I start then, but restarting the app usually works fine.
All mobile OS's are beta because they are young. In the 90s windows was even more unstable, and became more stable with time.
Sent from my SPH-D710 using Tapatalk

Ok.. so the only REAL issue i have is the crashing apps... which will hopefully get better over time then?
Your response was helpful! Thanks for taking the time to address my concerns

The screen spazz thing ( if not on stock charger ) is enough to make me go in and exchange it. Mine has none of the probs you have

btate0121 said:
Ok.. so the only REAL issue i have is the crashing apps... which will hopefully get better over time then?
Your response was helpful! Thanks for taking the time to address my concerns
Click to expand...
Click to collapse
If you have probs with apps crashing, try a factory restore. Also check when the app was last updated by the dev, it may just be out of date and written for 2.1
Sent from my SPH-D710 using Tapatalk

kingsway8605 said:
If you have probs with apps crashing, try a factory restore. Also check when the app was last updated by the dev, it may just be out of date and written for 2.1
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
It's not likely to be an outdated app, these were all apps I was using (successfully) on my G2x, until I sold it and bought the GS2 the same day.
I'm glad to know these are KNOWN issues that either have reasonable workarounds or are being worked on. I can deal without games, all of my essentials (productivity apps) are working. Thanks people.

ilostmypistons said:
The screen spazz thing ( if not on stock charger ) is enough to make me go in and exchange it. Mine has none of the probs you have
Click to expand...
Click to collapse
oh yeah... also, heading to the local sprint store in a minute to test out this theory.. i do remember that i was charging while playing deathworms when it spazzed on me... the lock screen as well, but whenever i messed with the in store demo units... no problems. I may get an exchange anyway though. Thanks!

[Q] Bluetooth A2DP audio occasionally drops out for a second on custom ROMs

Hello all,
I have a very odd problem that I'm hoping others may have run into and solved. When I'm playing audio over the A2DP data path to my car, the audio randomly will drop for half a second, then gradually comes back to full volume over perhaps a second of time. Speaking like a programmer, it's almost like something mutes the audio and then slides the volume up in a loop or something.
This problem did not occur on Bombaridier and the older Synergy Kernel, however it is happening with the newer kernel on Juggernaut v5, Paradox and SlickMOD, leading me to believe something in the kernel or newer system binaries might be causing it. This behavior happens in Pandora, Amazon MP3 and also the stock Music app.
Thinking that maybe a stray notification was the problem, I've tried disabling notifications in all of the apps I know of that notify, I've also tried switching the phone into vibrate and finally into full-silent, but it does not seem to affect the behavior. I have found no likely cause. I wish I was able to log alsa changes; maybe a script running constantly with something like:
Code:
while (true)
do cat /proc/alsa/some_alsa_status_entry >> /tmp/alsalog
sleep 1
done
Does anyone else have any ideas as to what this might be? It's really annoying!
Thanks in advance,
Pete

Dirty Pete said:
Hello all,
I have a very odd problem that I'm hoping others may have run into and solved. When I'm playing audio over the A2DP data path to my car, the audio randomly will drop for half a second, then gradually comes back to full volume over perhaps a second of time. Speaking like a programmer, it's almost like something mutes the audio and then slides the volume up in a loop or something.
This problem did not occur on Bombaridier and the older Synergy Kernel, however it is happening with the newer kernel on Juggernaut v5, Paradox and SlickMOD, leading me to believe something in the kernel or newer system binaries might be causing it. This behavior happens in Pandora, Amazon MP3 and also the stock Music app.
Thinking that maybe a stray notification was the problem, I've tried disabling notifications in all of the apps I know of that notify, I've also tried switching the phone into vibrate and finally into full-silent, but it does not seem to affect the behavior. I have found no likely cause. I wish I was able to log alsa changes; maybe a script running constantly with something like:
Code:
while (true)
do cat /proc/alsa/some_alsa_status_entry >> /tmp/alsalog
sleep 1
done
Does anyone else have any ideas as to what this might be? It's really annoying!
Thanks in advance,
Pete
Click to expand...
Click to collapse
I second this as an issue that I have run across quite often. I use this BT for music in my car on a daily basis. I usually get a .5 second audio drop out at lest twice each song. Seems to be about every 2 minutes if I would have to guess.
I have just learned to get used to it but it would be fantastic if this could be resolved.

I've also tried fiddling with the CPU governor ant the IO scheduler, but to no avail. Im wondering if there is a bug in the bluetooth module introduced in the latest kernel.
Sent from my SGH-T989 using xda premium

Works great for me and I've tried just about every rom and kernel over clocked and under clocked. I had it skip once before, I rebooted and it was fine.
Sent from my SGH-T989 using Tapatalk

I'll give this a bump, because I have the exact same problem. Never had this problem on my Blackberry (sad), in the same car. OP has described the issue better than I could have.

scotty-dont said:
I'll give this a bump, because I have the exact same problem. Never had this problem on my Blackberry (sad), in the same car. OP has described the issue better than I could have.
Click to expand...
Click to collapse
Thanks for posting, out of curiosity, what ROM and kernel are you running? Maybe we can find some sort of similarities...
My phone's currently running SlickMOD 3.1 with kernel "2.6.35.14"
-Pete

I've tried black edition and warfare, never had any issues

tomasitoc said:
I've tried black edition and warfare, never had any issues
Click to expand...
Click to collapse
What version of the kernel on your warfare mod? SlickMOD uses the Darkside 2.6.35.14 kernel.

Dirty Pete said:
Thanks for posting, out of curiosity, what ROM and kernel are you running? Maybe we can find some sort of similarities...
My phone's currently running SlickMOD 3.1 with kernel "2.6.35.14"
-Pete
Click to expand...
Click to collapse
Hi Pete,
I've noticed it on Digital Warfare 2.5.1 and BeastMOD 5.0 ("Test 13"), using TDJ's personal kernel and the same 2.6.35.14 above, respectively.
I'll post to Melvin on rootzwiki in the hopes that he can investigate maybe.
It might be better to bring this up in other sections as well. I came across this post by accident while researching extended batteries.

scotty-dont said:
It might be better to bring this up in other sections as well. I came across this post by accident while researching extended batteries.
Click to expand...
Click to collapse
I originally posted it in a different forum, but a moderator kicked it over here. It's not really an accessories question as I'm pretty sure it's a kernel bug, but I wasn't about to argue with site moderators on a forum like this where I'm definitely the new kid on the block.
That being said, if you have some other suggestions as to where we can ask about this, I'm all ears and would be more than willing to help debug/diagnose. I've been a Linux user since '96, so I'm unafraid of poking around in the kernel's guts to get answers.
Pete

Yeah that's the problem with this place... and why I have less than 10 posts.
On second thought, I'm tempted to just wait. It sounds like we will have a proper ICS rom and true kernel on about April 25th, to coincide with the launch of the HTC One S on T-Mobile. I can't find the threads. Hopefully then it will be an issue of the past.
I'm glad I'm not the only one though.

Just a thought....I don’t think this has anything to do with CPU performance
Hi, I have a Galaxy 2s with this exact problem but I wonder if I might offer a suggestion as to what could potentially be the cause. I have no idea how to fix it but I’m hoping that what I share here might help someone who knows more about the way these things work to be able to solve the problem.
I have spent much of my career working in Broadcast Radio, the problem I have heard my phone have with audio dropouts followed by either a ramp up of volume back to the previous level OR an audio dropouts followed by a momentary slight speed shift in the audio playback (sounds a bit like an old cassette recorded when the batteries are starting to fail) many people would probably not notice the later problem because it is very subtle and you have to know what you’re listening for.
Anyway, I believe this could be caused because of a lack of word clock sync between the phone and the bluetooth receiver. I say this because there have been times when I have had digital audio devices such as CD players that are connected to an audio console or digital amplifier and with both devices free running in terms of their clock synchronisation exhibit almost exactly the same symptoms.
You see all digital audio devices require that the audio data be put into frames much the same as regular Ethernet data is transmitted around a network is put into frames, however in order for the audio to be at the correct pitch and speed generally speaking both the playback device (Phone) and the receiving device (Bluetooth receiver) need to have the same word clock, otherwise you end up with the two devices running freely and the audio frames wont by in sync.
Depending on the Error correction implemented (sample rate conversion) on the receiver you can get really odd audio results. I think that this is what is causing this problem. Basically the Bluetooth receiver and the phone aren’t in sync so every few minutes you get a drop out.
It doesn’t seem to happen when you are talking on the phone which makes me think that when you have a call connection as this is bi-directional, the phone is probably synchronised to the Bluetooth device word clock. But when you are listing to music the connection is mono-directional so there is no sync.
Anyway just a thought. Maybe someone out there who understands the way these units synchronise can figure out a fix.

Mine has random just disconnects from the phone altogether. I have Jawbone Era, Voyager Pro Plus, and a Jabra Wave + and all will just randomly disconnect and have a hard time connecting back to phone audio. It will reconnect to media pretty much first time but won't show coonected to phone audio for some reason unleass I turn off BT, turn off headset, and sometimes even re-boot phone.

I am sure you guys have ruled this out, but this was a common problem with bluetooth audio on android. I haven't had the problem for a long time, but I used to have to disable wifi during my commute due to this dropout. Can you turn off wifi and see if the issue still happens? I was able to identify it by changing the time between wifi scan. If you had custom rom settings you could push it out and sure enough, my bluetooth dropouts happened on the same schedule (2s, 10s, more)
Just a thought.

I had this issue when I tried out juggernaut, so I went right back to Bombardier with Synergy kernel. Anyone have this on any if the ICS roms?
Sent from my beastly Galaxy S 2.

Shane_pcs said:
I am sure you guys have ruled this out, but this was a common problem with bluetooth audio on android. I haven't had the problem for a long time, but I used to have to disable wifi during my commute due to this dropout. Can you turn off wifi and see if the issue still happens? I was able to identify it by changing the time between wifi scan. If you had custom rom settings you could push it out and sure enough, my bluetooth dropouts happened on the same schedule (2s, 10s, more)
Just a thought.
Click to expand...
Click to collapse
I disable my wifi while I'm in the car, so this wasn't my issue. Thanks for the suggestion though!

I used to have occasional a2dp problems, however I have not had them since I started using various ICS releasese. The problems I would occasionally have would be a total loss of bluetooth till I rebooted the phone.
Since using Infamous I haven't had the problem other then for some odd reason occasionally having to reenter the PIN #
I'm using a Scoche Bluefusion in my car.

It had to be the fuse.
Sent from my SGH-T959 using xda premium

After upgrading to DARKSIDE's latest ICS rom, this problem has not recurred. I'm assuming that my early thought was correct in that it was some kind of kernel bug.

Dirty Pete said:
After upgrading to DARKSIDE's latest ICS rom, this problem has not recurred. I'm assuming that my early thought was correct in that it was some kind of kernel bug.
Click to expand...
Click to collapse
With Darkside and the stock ROM I have not only this problem, but crackly/staticy audio and my phone and car won't communicate once I've shut the car off. I have to completely re-pair the phone. They're bugs in 4.0.3, which Samsung dumped off on us.
4.0.4 via CM9 already doesn't exhibit the connection issue (I have to turn Bluetooth on and then off though) but I'm not sure about the others yet.

Horrible Outgoing Audio - Mic problem?

Everyone is complaining that my outgoing audio is horrible. They hear me, but it is muffled, with an echo, and not very clear.
I'm not sure if it started when I installed AOKP, or whether it started after I installed the new skin.
Ideas anyone????

Can anyone specify where the two microphones are? I know that one is on the bottom. But I can't find the other one (unless it is on top under the back cover)...?

try turning down the ear piece volume the mic can pick it up

This happened to mine as well. I had to factory reset it, but that fixed the problem. Obviously some update (most likely) or program caused it. Backup everything first (apps media and data). I then reinstalled my apps from the app store then recovered my data from the backup.
Remember, the reset will erase EVERYTHING on the phone -- including "SD" memory.

IMWarthog said:
This happened to mine as well. I had to factory reset it, but that fixed the problem. Obviously some update (most likely) or program caused it. Backup everything first (apps media and data). I then reinstalled my apps from the app store then recovered my data from the backup.
Remember, the reset will erase EVERYTHING on the phone -- including "SD" memory.
Click to expand...
Click to collapse
A couple of questions:
1. which ROM are you on? Are you on stock ROM or AOKP?
2. I did a factory reset before upgrading to AOKP Build 28. A factory reset DOES NOT wipe the SD card. It only wipes app data and rom data. What reset are you talking about?
I'm wondering whether this problem is due to something simple as a modem change. Feedback anyone?

IMWarthog said:
This happened to mine as well. I had to factory reset it, but that fixed the problem. Obviously some update (most likely) or program caused it. Backup everything first (apps media and data). I then reinstalled my apps from the app store then recovered my data from the backup.
Remember, the reset will erase EVERYTHING on the phone -- including "SD" memory.
Click to expand...
Click to collapse
Well I did a factory reset and installed AOKP Build 31 and I still have the same problem.
The factory reset DID NOT format the SD drive, so I have no idea what you are talking about.
Is anyone else experiencing bad outgoing audio?

montrealguy said:
Well I did a factory reset and installed AOKP Build 31 and I still have the same problem.
The factory reset DID NOT format the SD drive, so I have no idea what you are talking about.
Is anyone else experiencing bad outgoing audio?
Click to expand...
Click to collapse
First of all, I am sorry to hear that you are having this problem. We welcome you to our lives. A lot of CDMA Gnex and a few GSM GNex users had this issue arise more than 4 months ago.
Second of all, I don't think you searched for this issue yet, or you just haven't found it, so I'll do the search for you. This issue is somewhat prevalent.
1) the post I made about this issue:
http://forum.xda-developers.com/showthread.php?t=1604730&highlight=microphone
2) the post most of us with this issue have been following here on XDA:
http://forum.xda-developers.com/showthread.php?t=1403051
3) And the location map (Although, I personally believe location doesn't even matter because even according to this post, it pretty much happens everywhere):
http://forum.xda-developers.com/showthread.php?t=1545621
4) Google Issue Report:
http://code.google.com/p/android/issues/detail?id=24019
The bottom line:
1) there's no fix as of yet, even if some users naively recommend you to get custom ROMs, Radio, Factory Reset, the chances are, none of will work.
2) due to severe variations among devices, some have whole lot worse than others (happening as soong as 5 sec into a call on every other call), some have it better than others (never had it happen for weeks, but infrequent enough for it to be any "issue" per say.)
3) I have noticed many of the members here at XDA don't even use GNex as a phone that much but rather a very nifty computer you can flash OSs on. Hence, the issue might be a little bit more prevalent than users report simply because many of us don't use this phone as a phone.
4) When you hear from problem free users "You are covering mic with your finger", "It's probabaly user issues, check out the apps that you installed."
Stay calm, just realize that some hasn't seen this issue and do not understand what we are going through.
5) In the mean time, I recommend you not using this phone for business purposes (e.g. try landline or second phone for conference calls, etc). Or even use a flip phone for business purposes. You may also try to get a replacement hoping the other one will have less issue. But it will have it most likely as well.
Let the other party know if your voice becomes robotic sounding and starts breaking up, let them know you'll call them back as soon as you call them.
6) Contact your carrier, and let them know. Many of them actually have been telling all of us the fix is on the way since January, so who knows..
Hope this post saved your time understanding this issue in depth.
Thank you for reading my 4 months of investigation regarding this issue.

Charlescom: I read through your posts and I am doubting whether I have the same problem as you.
My OP stated that people hear me, but it is muffled, with an echo, and not very clear. Your posts state that the microphone cuts out entirely or sound turns robotic. My microphone has never cut out.
Is this really the same problem?

montrealguy said:
Charlescom: I read through your posts and I am doubting whether I have the same problem as you.
My OP stated that people hear me, but it is muffled, with an echo, and not very clear. Your posts state that the microphone cuts out entirely or sound turns robotic.
Is this really the same problem?
Click to expand...
Click to collapse
In a broader scheme of things, it is a similar problem or even a same problem.
I had people tell me 1) my voice turned into a static robot that chops up 2) muffled with an echo...as well..

see post 1199 here
http://forum.xda-developers.com/showthread.php?t=1557606&page=120
but before you slam me--
i am not sure if these two audio issues are even related and if the N1 fix can be adapted to the GN--just fyi for the real techies

rugmankc said:
see post 1199 here
http://forum.xda-developers.com/showthread.php?t=1557606&page=120
but before you slam me--
i am not sure if these two audio issues are even related and if the N1 fix can be adapted to the GN--just fyi for the real techies
Click to expand...
Click to collapse
Well it seems that the fix works for some people on the Desire and on the Nexus One on a 4.04 ICS ROM!
Can one of you tech experts check it out???

It was the only fix that worked for me--my issues were no onboard working mike and overdriven audio to listener as well as echo. I am on that rom--bcmics 4.0.4

rugmankc said:
It was the only fix that worked for me--my issues were no onboard working mike and overdriven audio to listener as well as echo. I am on that rom--bcmics 4.0.4
Click to expand...
Click to collapse
Now we need to know whether it works on the Galaxy Nexus GSM and AOKP...
And can someone create the fix in the form of a CWM zip? Most of us have no idea how to use ADB.

montrealguy said:
Now we need to know whether it works on the Galaxy Nexus GSM and AOKP...
And can someone create the fix in the form of a CWM zip? Most of us have no idea how to use ADB.
Click to expand...
Click to collapse
Cwm zip is a good idea. Learn how to use adb. It's actually pretty damn easy.
Sent from my i9250 using Forum Runner

Can someone with expertise here create a CWM version of the audio fix for us? And comment on whether it actually works on the Galaxy Nexus GSM? And AOKP?
I'd love to find out whether it works!
Sent from my Galaxy Nexus using XDA

I got this issue while running AOKP.
Yup. Never changed ROMs faster.
Solution: Different ROM
Sent from my Galaxy Nexus using XDA

Smokeey said:
I got this issue while running AOKP.
Yup. Never changed ROMs faster.
Solution: Different ROM
Click to expand...
Click to collapse
Which ROM are you using now on your GNex GSM? I think that AOKP is based on CyanogenMod so I don't think CM9 would work either.

Are you having this problem with calls only or does it happen when you record audio with the mic (I.e. a video or voice recording)?
Personally, I'd stick with stock rom and kernel as the custom stuff often introduce issues here and there and troubleshooting them can be a nightmare.

montrealguy said:
Well it seems that the fix works for some people on the Desire and on the Nexus One on a 4.04 ICS ROM!
Can one of you tech experts check it out???
Click to expand...
Click to collapse
Different audio chipset.
No bueno.

EP2008 said:
Are you having this problem with calls only or does it happen when you record audio with the mic (I.e. a video or voice recording)?
Personally, I'd stick with stock rom and kernel as the custom stuff often introduce issues here and there and troubleshooting them can be a nightmare.
Click to expand...
Click to collapse
I just tried a video recording with the front camera and the audio is great. Sound recording in the same conditions with Tape-a-Talk sounds pretty bad (robotic). And calls sound pretty bad too.
Could it be that the stock camera is using/not using the second microphone for noise cancellation, and the calls feature isn't?

[Q] Nexus mic problems.

Since moving to Jellybean (when it first got released) and attempting to use Google Now, I noticed that the it wasn't doing or understanding what I was saying. It appeared that there was a lot of static noise before it would recognise what I was trying to say.
I loaded some recording software to make sure it wasn't just Google Now, but it turns out that it just hisses for that first 5 seconds before it comes good. It does not happen in phone calls, just when recording/talking to Google Now. Changing ROMs, kernels and radios has not changed the problem. Even moving up to the new 4.1.1 hasn't rectified the problem.
Has anyone else had this problem? Has it ever been fixed?
Any help would be fantastic!

Bumping.
Still can't seem to find an answer anywhere for this.

This is a real problem. It makes the new Voice Search unusable.
There's a bug on it but it hasn't had any real attention - http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=29092
Edit: interesting that yours is a Telstra phone too. Wonder if its build/baseband related?

galapogos01 said:
This is a real problem. It makes the new Voice Search unusable.
There's a bug on it but it hasn't had any real attention - http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=29092
Edit: interesting that yours is a Telstra phone too. Wonder if its build/baseband related?
Click to expand...
Click to collapse
I've tried different basebands, ROMs etc. Still suffers from the 2 seconds of hissing/not working microphone before it comes good and is usable.

Interesting. I too am on Telstra, tried few 4.1 and 4.1.1, CM10 and the same issue. Not to mention, even after the hiss is over, the volume is very low and rubbish in general.

Interesting that it affects a lot of Telstra phone owners.
Anyone reverted to the stock Telstra rom/baseband to test? Does it affect voice search in 4.0.x as well?

Same problem!
I have this exact problem!! I've had difficulty finding any others with this problem until I found this thread.
Grr, mine shows static for about 4 seconds and it struggles to understand anything at all! After those 4 seconds, it dies down, then I can speak and it is better but far from perfect with recognising my speech!
FYI mine is a yakjudv Telstra phone from Australia which I flashed to yakju 4.0.4 and then did a JB update OTA......
It was on the stock DVKK6 but am now on the XXLF1 radio that came with JB....
Argh, whats going on, i was so pumped for google now voice actions!!! Now its basically useless!!
Mines almost spot on 4 seconds every single time.....
Any solution to this would be greatly appreciated!

+1 again on my gnex
factory installed yakjudv i think, from vodafone.
I have had it since ICS, tried to record lectures in class, and the first few seconds is always static.
Now that you mention it, when I activate voice search in google now, i see the grey circle voice indicator spazzes out for a few seconds before it goes back to normal. Maybe that's why I have to speak loud for it to recognise my voice to make it distinct from the initial static, so it usually doesn't work that well.

Kinda weird that it appears to be Telstra gnex's. Still no luck in finding fixes yet.
Sent from my Galaxy Nexus

Any workaround or fix for this?
It seems like Santaria has already tried a variety of different radios with no luck.
Is this a case of sit and hope that Google fixes this?
So what exactly is the problem? There's 2 mics in the phone, but its picking up the wrong one?
Since when were there 2 mics? one for phone call and one for speakerphone? I didn't even know this. How could this happen and why is it only on Aussie phones? The hardware should be the same across the board?
I'm so confused

One is for noise reduction.
Cheers,
Jason

I wonder if there's a way to enable/disable the noise reduction mic?
Sent from my Galaxy Nexus

galapogos01 said:
One is for noise reduction.
Cheers,
Jason
Click to expand...
Click to collapse
One is for calls the other one is for recording videos and video calls...The Galaxy Nexus do not have a noise reduction software on board neither the required hardware so no noise canceling feature!
Sent from my Nexus 7

Err...
http://www.slashgear.com/galaxy-nexus-review-21196912/
http://en.wikipedia.org/wiki/Galaxy_Nexus
There seems to be some debate about its effectiveness - probably related to the above bug disabling it in some cases.

For the record, same problem on my telstra Gnex, google now only works if I hold the mic right to my mouth.

I'm having the exact same issue. I just bought a new gn that was locked to Vodafone Australia. I unlocked it and went to yakju then got the OTA and then started having the exact same problem that everyone else has described. I get massive static and so far nothing I've said has been recognised. It just times out with the message "recognising...".
I've recorded my voice using an app but everything sounded fine and I didn't get any static. I have the same problem if I use a hands free kit too.

Seems this happened with ICS also
http://forum.xda-developers.com/showthread.php?t=1602840

Star this issue
Hey guys, a few of us seem to be having this problem, please star this issue so that Google will be aware of it.
http://code.google.com/p/android/issues/detail?id=29092
SIMPLY CLICK HERE AND STAR THE ISSUE.

Starred
Starred a long time ago...
No luck, even with 4.2.2
I take it they're never going to fix this problem

[Q] Call quality - other person cannot hear me

My T-mobile LG G3 has been working like a champ for many months. Now, call quality for person to whom I am speaking is very poor. It sounds like there is very faint speaking that drops in and out. This happens both on bluetooth and off, but is worse on bluetooth. There is no physical block to built-in or headset microphone. I know this because can record voice memo and do 'OK Google' dictation with ease. VOIP calls (Google hangout) are ok given my WiFi bandwidth.
T-mobile tier2 support tried to sell me on notion that lollipop might fix me (based on www_androidauthority_dot_com/lg-g3-problems-517832 ) but I'm skeptical and jumped at the offer of a handset replacement. Any other ideas out there?

steve.whisenhant said:
My T-mobile LG G3 has been working like a champ for many months. Now, call quality for person to whom I am speaking is very poor. It sounds like there is very faint speaking that drops in and out. This happens both on bluetooth and off, but is worse on bluetooth. There is no physical block to built-in or headset microphone. I know this because can record voice memo and do 'OK Google' dictation with ease. VOIP calls (Google hangout) are ok given my WiFi bandwidth.
T-mobile tier2 support tried to sell me on notion that lollipop might fix me (based on www_androidauthority_dot_com/lg-g3-problems-517832 ) but I'm skeptical and jumped at the offer of a handset replacement. Any other ideas out there?
Click to expand...
Click to collapse
try the replacement handset. I've had my G3 since it came out with no problems whatsoever.

steve.whisenhant said:
My T-mobile LG G3 has been working like a champ for many months. Now, call quality for person to whom I am speaking is very poor. It sounds like there is very faint speaking that drops in and out. This happens both on bluetooth and off, but is worse on bluetooth. There is no physical block to built-in or headset microphone. I know this because can record voice memo and do 'OK Google' dictation with ease. VOIP calls (Google hangout) are ok given my WiFi bandwidth.
T-mobile tier2 support tried to sell me on notion that lollipop might fix me (based on www_androidauthority_dot_com/lg-g3-problems-517832 ) but I'm skeptical and jumped at the offer of a handset replacement. Any other ideas out there?
Click to expand...
Click to collapse
Wow, my G3 just started doing this too. I've had it for 6 months and it's just been the past week that I've been having issues. It's hit or miss, but about 90% of the time I get complaints that the other person can't hear me or that I sound very faint. It's been driving me crazy. I've figured out that I can toggle speaker mode and it fixes it. Can you try that out see if it's the same for you?

I noticed this about a week ago, interesting. Wonder if it's something on tmobile's network.

This just happened to me as well on Tuesday, March 10th. I live in Los Angeles. A reboot seems to fix it for one call. This is kind of a big problem.
---------- Post added at 09:48 AM ---------- Previous post was at 09:04 AM ----------
madmanjsm said:
This just happened to me as well on Tuesday, March 10th. I live in Los Angeles. A reboot seems to fix it for one call. This is kind of a big problem.
Click to expand...
Click to collapse
I'm now running in safe mode and a couple test calls to my Google Hangout sound fine. Don't think it's a hardware issue.

I've started to experience this too. It's really annoying. I hope it gets fixed soon. Though, I am glad to know it's not just me. I really didn't want to dig around in my apps to find the offender.
Question: Do any of you guys have the Nova Launcher Beta running? I think I started having issues around then.
Sent from my LG-D851 using Tapatalk

I'm on Verizon with a G3, but try reading my post @ http://forum.xda-developers.com/showpost.php?p=59423187&postcount=25 and maybe it'll help some of you

bryanwny said:
I'm on Verizon with a G3, but try reading my post @ http://forum.xda-developers.com/showpost.php?p=59423187&postcount=25 and maybe it'll help some of you
Click to expand...
Click to collapse
Thanks! I downgraded and installed Google App 4.1.29 here http://www.apkmirror.com/apk/google-inc/google-search/google-app-4-1-29-1706998-arm-android-apk-download/. Also disabled auto-update for Google Apps so it doesn't update to 4.2.16.87075793. I'll test it out and see what happens.

I also have had the same problem lately, just twice. A reboot fixed it

This is affecting me as well. I'm also in Los Angeles and the phone was fine until some time last week. I'm trying to the google apps downgrade now...

I also am having the same issue in my D851. My phone worked fine for 2 weeks and now 75% of the time the caller on the other end says they cant hear me and I sound like I am a mile away. This does not happen when I used VOIP such as hangouts. I am thinking about flashing a AOSP ROM until the t-mobile 5.0 build comes out.

Lookatthemonkeys said:
I also am having the same issue in my D851. My phone worked fine for 2 weeks and now 75% of the time the caller on the other end says they cant hear me and I sound like I am a mile away. This does not happen when I used VOIP such as hangouts. I am thinking about flashing a AOSP ROM until the t-mobile 5.0 build comes out.
Click to expand...
Click to collapse
Try downgrading the Google app. Worked fine for me.

Downgraded, seems better. Are people also recommending not to use voice activated Google now?

How do I downgrade the google app? I tried turning off the "OK Google" way, but still have the same problem.

tippingvan said:
How do I downgrade the google app? I tried turning off the "OK Google" way, but still have the same problem.
Click to expand...
Click to collapse
In the play store for the Google search app click the uninstall button. That will return the app to it's factory version. Then just install the version that's linked earlier in this thread. Make sure you have automatic updates turned off for the app or it will keep updating.
Sent from my LG-D851 using Tapatalk

Same thing happens to me. I had my phone for about 2 months now and sometimes people cant hear me or i sound like a transformer. i restart my phone and it fixes the problem but still does it after a couple days. I'm not rooted or anything like that. I also have a problem when I'm on a call. my volume bare goes up and down if i wanna lower and or raise it and the volume sounds the same even on speaker phone it does it too..

I had the problem turn off ok google from any screen and reboot and problem with voice calls fixed

I had this same problem. Maybe I should have came here first. I got a replacement in the mail a couple of days ago. New one seems to be working fine. Hopefully the problem doesnt start happening again.

JohnnyDanger said:
I had this same problem. Maybe I should have came here first. I got a replacement in the mail a couple of days ago. New one seems to be working fine. Hopefully the problem doesnt start happening again.
Click to expand...
Click to collapse
I was gonna do a factory reset and if that didn't work i was gonna get a replacement . Hopefully this fixed the problem. The only issue I seem to be having is. when I'm on speaker phone or have it to my ear. and when i go to adjust the volume it doesn't change it. like i see the meter go up and down but the volume stays the same. its weird

I can confirm that after enabling voice activation for google now from any screen was the culprit of Mt audio issues. I was told I sounded far away or like a robot far away. Reset my device numerous times and reinstalled all apps and made calls. Once I enabled OK google from google now the issue came back. Disabled it and BOOM it worked fine. Haven't had an issue since.