I don't use the OS native sip functionality on it, but I do use GrooveIP and I have run into this issue. With GrooveIP you can work around it by fiddling with the various echo cancellation options GrooveIP supports at the cost of introducing a voice latency on your outgoing voice that is just long enough to be annoying (but usable once you acclimate to it), in my experience.
There are generally a lot of audio related issues with this phone with various users unable to get loud-enough volume from the device either on calls, from the speaker or via the headphones Seems to be a software bug as many people report if you root the phone and run alsamixer you can boost the audio up to decent levels, but this isn't a great fix because any time an app adjusts the volume at the SDK level the problem returns.
Google's stellar customer support consists of no-questions-asked replacing your device (which is great) with one that has exactly the same problems out of the box (which is not so great). Haven't seen any kind of official acknowledgement of this as an issue despite it being very commonly reported online (google: "nexus 4 volume too low")
An otherwise great phone hampered by a pretty serious fundamental issue.
I don't understand how bug reports can sit around for months with dozens (if not hundreds) of comments on them without a single response from somebody with an @google.com username. I feel like I've seen this happen for all kinds of Google products, not just Android. Or am I missing something here?
So how does Google get away with "legendarily bad" customer service while EA cannot? I guess in a way EA charges a good bit for the games and good support is expected, but still. I paid $300 for a Nexus 4, I should get something more than a message board.
You would think that Google could afford to hire some people to do bug triage. Users reporting bugs are trying to help Google (and themselves, admittedly). Presenting users with a "write-only" bug database is worse than no bug database.
The status is listed as "new." I suspect that were this bug to be reviewed, it would end up "not a bug" because it depends on software that's not part of Android. That is, like a phone that's missing a GPS driver, that function will fail for lack of what should be OEM provided drivers/firmware.
Yes, it is bad that this bug has lingered without attention. But I also see how it could fall to the bottom of the priority list for review.
Tl;dr: It doesn't work because it's not implemented.
Argh, this smells like the audio latency issue. An issue with 500 comments pleading Google to do something about it for 4 years. Ladies and gentlemen, I give you issue #3434:
This is one of the issues keeping Android from being an excellent platform for music applications. Coupled with the general hackability of Android devices (Accessory Development Kit, etc.), it could be an amazing platform for digital audio workstations, synthesizers, samplers, and audio effects processing.
iOS is better in this regard, but still not perfect. Audio routing between applications is a dicey affair (done through a 3rd party app that runs in the background), and it's not possible to charge while using USB accessories, like audio interfaces or MIDI keyboards.
I have a Nexus 10. It crashes about once a week restarting the gui (adb restore backup does so too). Playing audio via Bluetooth is choppy if the device hasn't been rebooted for a few days. It feels like several years ago when I had a Blackberry (no data service though) and a poll question was "which app do you use to daily reboot your phone?" I'm on the verge of writing one for Android.
I was sincerely thinking that buying an "official" phone mean't zero problems
(currently having a very bad experience with my LG O2X, where I'm still running CM7 - announced as the "world's first dual core smartphone" or something).
I bought a Nexus One and the only problems I never had the any unexpected problems with it. (The extremely limited memory for app storage seriously hampered its usefulness, but that was a design limitation that I knew going in.)
Normal calls work fine, of course. Zero problems is a pretty high bar. Audio manipulation that 3rd party apps require doesn't seem to be exposed by the device.
I had a Nexus S and it was really perfect in every way. I handed it off to another family member and, for a 2 year old phone, it still feels very "current."
I have not paid much attention to SIP recently but aren't the implementations of theAEC and other components up to the OEM to create or license, as much as, say, baseband firmware, graphics drivers, etc. are the OEM's responsibility?
If Google actually had their own unencumbered implementations, wouldn't they be in the AOSP source tree?
I guess that just as with the native email client, there's not much development happening on the native SIP dialer.
Instead of improving the core Android apps, which would benefit other phone manufacturers as well, Google is mostly working on their web service frontends (Gmail, Google Plus, probably Google Voice as well) nowadays. The result is a platform packed with features that only work half the time.
Did you know that the native Email client doesn't even set the In-Reply-To header, i.e. breaks threads?
As someone in the google thread point out, latest csipsimple nightly is worth a shot http://nightlies.csipsimple.com/trunk/ if you are experiencing this issue.
I have a N4 and I'm not noticing the issue at all. I've been using Vonage and GrooveIP.
I would normally pick up on it from the 3 years of VoIP and other real time audio work I did.
I didn't get a chance to read everything but as a I recall some of the codecs used could have some serious echo side effects. Did someone mention the codecs being used?
1) Software echo cancellation doesn't work as well as hardware echo cancellation.
2) The phone uses a second microphone to cancel out background noise during calls. This isn't used for any voip calls. I'm told it is extremely loud when a car drives by, and a little bit of wind make it sound like I'm in a hurricane.
Is there some hardware reason they can't open up access to this chip? Does audio for calls get routed directly to the gsm chip, so we don't have access or something?
I've a Galaxy Nexus and the cellular operator's 3G usage pop-ups in screen make my life hell. It just keeps on receiving them. Whenever there's a background transaction of data, even a kilobyte. That means if my phone is kept for 30 minutes and I get a call, I need to click through those 10-20 accumulated pop-up windows on my Android screen to receive the call or do anything on my phone. On mornings when there's no Wi-Fi I usually get some 70-100 such pop-ups. I counted. Sometimes I better switch off and then switch on the phone to avoid clicking through those pop-ups.
The cellular operator (Airtel India) says it's a feature and argues that every operator has it and that iPhone, BlackBerry and Windows (etc) users don't have this problem. True.
Samsung support says - this is Google feature and then is quick to add - but we never sold Galaxy Nexus in India. No support there. Sorry, bye-bye.
I go to raise a Google-code issue just like this. Well, there's one already logged - years old.
Of course without a fix or response from Google!
I'm an Android developer(day job) with a laaarge OEM but I doubt an Android is going to be my next phone. I am not comfortable with paying for anything very expansive then being on my own.
[+] [-] georgemcbay|13 years ago|reply
I don't use the OS native sip functionality on it, but I do use GrooveIP and I have run into this issue. With GrooveIP you can work around it by fiddling with the various echo cancellation options GrooveIP supports at the cost of introducing a voice latency on your outgoing voice that is just long enough to be annoying (but usable once you acclimate to it), in my experience.
There are generally a lot of audio related issues with this phone with various users unable to get loud-enough volume from the device either on calls, from the speaker or via the headphones Seems to be a software bug as many people report if you root the phone and run alsamixer you can boost the audio up to decent levels, but this isn't a great fix because any time an app adjusts the volume at the SDK level the problem returns.
https://code.google.com/p/android/issues/detail?id=41042
Google's stellar customer support consists of no-questions-asked replacing your device (which is great) with one that has exactly the same problems out of the box (which is not so great). Haven't seen any kind of official acknowledgement of this as an issue despite it being very commonly reported online (google: "nexus 4 volume too low")
An otherwise great phone hampered by a pretty serious fundamental issue.
[+] [-] general_failure|13 years ago|reply
But yes, GrooveIP is unusable. I bought it for 4 bucks or something and hardly use it since the voice quality is terrible.
[+] [-] fletchowns|13 years ago|reply
[+] [-] joshmlewis|13 years ago|reply
[+] [-] barry-cotter|13 years ago|reply
[+] [-] snaky|13 years ago|reply
https://code.google.com/p/android/issues/detail?id=18565
[+] [-] cpeterso|13 years ago|reply
[+] [-] Zigurd|13 years ago|reply
Yes, it is bad that this bug has lingered without attention. But I also see how it could fall to the bottom of the priority list for review.
Tl;dr: It doesn't work because it's not implemented.
[+] [-] rdtsc|13 years ago|reply
https://code.google.com/p/android/issues/detail?id=3434
There has been some improvement lately but it is hard to find devices that support the "special" low latency mode.
This sounds like a similar thing. Just pointing out the level or response and engagement you'd expect from Google (hint: almost none).
[+] [-] illicium|13 years ago|reply
iOS is better in this regard, but still not perfect. Audio routing between applications is a dicey affair (done through a 3rd party app that runs in the background), and it's not possible to charge while using USB accessories, like audio interfaces or MIDI keyboards.
[+] [-] rogerbinns|13 years ago|reply
[+] [-] snaky|13 years ago|reply
[+] [-] mik3y|13 years ago|reply
[1] https://android.googlesource.com/device/lge/mako/+show/f608d...
[+] [-] voltagex_|13 years ago|reply
[+] [-] swah|13 years ago|reply
(currently having a very bad experience with my LG O2X, where I'm still running CM7 - announced as the "world's first dual core smartphone" or something).
[+] [-] eli|13 years ago|reply
[+] [-] joseph_cooney|13 years ago|reply
[+] [-] epoxyhockey|13 years ago|reply
[+] [-] xur17|13 years ago|reply
https://code.google.com/p/android/issues/detail?id=41626#c20
[+] [-] Zigurd|13 years ago|reply
If Google actually had their own unencumbered implementations, wouldn't they be in the AOSP source tree?
[+] [-] epoxyhockey|13 years ago|reply
This would seem to explain all of the 'echoing' complaints I've been getting when using google voice on my N4.
[+] [-] ryanhuff|13 years ago|reply
[+] [-] andor|13 years ago|reply
Instead of improving the core Android apps, which would benefit other phone manufacturers as well, Google is mostly working on their web service frontends (Gmail, Google Plus, probably Google Voice as well) nowadays. The result is a platform packed with features that only work half the time.
Did you know that the native Email client doesn't even set the In-Reply-To header, i.e. breaks threads?
[+] [-] keda|13 years ago|reply
[+] [-] shakeel_mohamed|13 years ago|reply
[+] [-] snaky|13 years ago|reply
[+] [-] 3825|13 years ago|reply
[+] [-] grumps|13 years ago|reply
I would normally pick up on it from the 3 years of VoIP and other real time audio work I did.
I didn't get a chance to read everything but as a I recall some of the codecs used could have some serious echo side effects. Did someone mention the codecs being used?
[+] [-] snaky|13 years ago|reply
http://www.reddit.com/r/nexus4/comments/15ip1v/is_voip_just_...
[+] [-] xur17|13 years ago|reply
1) Software echo cancellation doesn't work as well as hardware echo cancellation.
2) The phone uses a second microphone to cancel out background noise during calls. This isn't used for any voip calls. I'm told it is extremely loud when a car drives by, and a little bit of wind make it sound like I'm in a hurricane.
Is there some hardware reason they can't open up access to this chip? Does audio for calls get routed directly to the gsm chip, so we don't have access or something?
[+] [-] dewiz|13 years ago|reply
Anyway, I have a Nexus 4, looks like a good suggestion never to rush with upgrades... if it works dont touch it?
[+] [-] TestingYourShit|13 years ago|reply
[deleted]
[+] [-] fiddly_bits|13 years ago|reply
[+] [-] dror|13 years ago|reply
[+] [-] imperialdrive|13 years ago|reply
http://code.google.com/p/android/issues/detail?id=41631
Can't use BT with WIFI at same time!!! all nexus 4, 4.22 OS, just plain sucks
[+] [-] ck2|13 years ago|reply
Because why not a bluetooth headset?
[+] [-] fakeer|13 years ago|reply
The cellular operator (Airtel India) says it's a feature and argues that every operator has it and that iPhone, BlackBerry and Windows (etc) users don't have this problem. True.
Samsung support says - this is Google feature and then is quick to add - but we never sold Galaxy Nexus in India. No support there. Sorry, bye-bye.
I go to raise a Google-code issue just like this. Well, there's one already logged - years old. Of course without a fix or response from Google!
I'm an Android developer(day job) with a laaarge OEM but I doubt an Android is going to be my next phone. I am not comfortable with paying for anything very expansive then being on my own.
This is how Google provides support. They don't.
[+] [-] hahainternet|13 years ago|reply
This is a completely unrelated issue caused by your carrier. Why are you posting it here?
[+] [-] xxiao|13 years ago|reply
[deleted]