On Dec 18, 2012, at 1:49 PM, Bruce A. Locke wrote:

> 
> The Nexus 4 doesn't have poor WiFi range from my experience.  My own device 
> is equivalent to my previous phones and my iPod Touch.
> 
> Android 4.2 however does have well known WiFi driver and Bluetooth issues 
> that affect all three devices where 4.2 is currently available.  This will 
> show up as the device connecting but being unable to send and receive traffic 
> or losing connection during sleep and not regaining it.  This seems to occur 
> with certain AP models far more often than others.  It's rock solid with my 
> Actiontec FIOS AP and whatever Frontier is using for their DSL models.  I've 
> also not had any issues on whatever gear AT&T is using for Starbucks, 
> McDonalds, etc.   However I did have issues with connecting to a Netgear 
> router at a friends house.
> 
> There is also a bug where if your enterprise wireless gear has 802.1k enabled 
> the WiFi stack seems to shoot itself in the head whenever the device goes to 
> sleep requiring a toggle of airplane mode to restore functionality.  Once I 
> turned this off on our gear at work the Nexus 4 and 7 are now happy.  This 
> shouldn't be an issue for consumer gear.
> 
> I'd link to the Google bug tracker entries but people are retarded when it 
> comes to wireless issues and the noise from people not knowing what they are 
> talking about has buried any signal on the topic.
> 
> Google has yet to do it's usual bugfix patches for 4.2.  4.2.1 was an 
> emergency quickfix for a UI issue involving the contacts app and didn't 
> really fix anything else.  We're all waiting for 4.2.2 but considering it's 
> the holidays I wouldn't expect it to be soon.
> 
> As for VOIP echoing it wouldn't surprise me.  It's not like any carrier 
> leaves it intact to get any use on the 99%+ of phones out there.  Perhaps try 
> another VOIP package?  It's it the job of software to filter out the echo and 
> feedback?
> 
> Good Luck.


Thanks for the reply.  I was really hoping to hear from a device owner.  

I'm connecting to my Asterisk PBX on my LAN.  I'm no quite ready to ditch 
Asterisk as it works fine with all other soft phones (Windows,  Mac) which
I have tried so far.  It also works well with my Cisco IP phones.  I have the 
echo issue even when calling local extensions, while using the Nexus 4.
I will look into what I can do to the PBX with noise cancellation without 
breaking current connections.

My first smart phone was the unlocked Nokia N95, which has native sip.  I only 
just tried the sip function last year, and the aging battery was not up to the 
task :)

I had a real disappointment today, while using WiFi on the Nexus 4.  I tried 
connecting the the Nexus 4 to my Nokia N95.  The N95 was running as a WiFi 
hotspot
using Joikuspot.  Many devices see this connection as peer to peer or AdHoc.  
The problem I had with the Nexus was it would not even
show up as an available network.  I tried manually adding the ESSID and WEP key 
but it still failed to connect.  I have never experienced this
with the large myriad of devices which have connected fine in the past.



> 
> 
> On Tue, Dec 18, 2012 at 8:30 AM, ew <[email protected]> wrote:
> 
> All in all this has been a frustrating change.  Aside from needing to learn a 
> new OS, the device has some issues.
> WiFi range is very poor.  I loose connection in my house both on 5Ghz and 
> 2.4Ghz bands.  I have no problems with
> any other handheld devices (less than 50' from Netgear WNDR3800).
> 
> The second issue is the built in VIOP/Internet phone function is nearly 
> useless.  There is horrible echo on the remote caller side.
> If I reduce my (Nexus4) earpiece volume to less than 50% it goes away, but 
> I'd have a hard time hearing the caller if I were anywhere
> but a quiet room.  If I put tape over the top mic hole I can increase volume 
> to nearly 75% before the echo becomes annoying.  I'm
> surprised to see a mic place so close to the earpiece, although it seems to 
> be a non-issue with cellular calls.
> 
> Anyone want to buy a near new Nexus4 16gig?
> 
> Well can anyone with this device confirm poor WiFi range?  Perhaps I have a 
> defective unit.
> _______________________________________________
> Mid-Hudson Valley Linux Users Group                  http://mhvlug.org
> http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug
> 
> Upcoming Meetings (6pm - 8pm)                         Vassar College
>  Jan 9 - High Performance Computing at a Small Scale
>  Feb 6 - Raspberry Pi
>  Mar 6 - 10th Anniversary Meeting!

_______________________________________________
Mid-Hudson Valley Linux Users Group                  http://mhvlug.org
http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug

Upcoming Meetings (6pm - 8pm)                         Vassar College
  Jan 9 - High Performance Computing at a Small Scale
  Feb 6 - Raspberry Pi
  Mar 6 - 10th Anniversary Meeting!

Reply via email to