On January 6, 47 days after the initial bug report was posted, Google finally assigned a developer to the bug. Since then we have been told the following by the Google Device support Team, who are supposedly working with the developers on this issue:
- "No, we've never heard of anyone complaining about this, you're the first. Sounds like a hardware problem, send your phone back and we'll send you a new one." Did this twice.
- "No, it's not a hardware problem. Turning the wifi off during deep sleep is a feature. But if you don't like this feature, let us know. Google listens to its customers' feedback."
- "If you like, you can send your phone back, and we will send you a third replacement."
FINALLY, on January 14, the Google developer posted the following, here.
Regarding nexus 4: Qualcomm driver on nexus 4 has a known issue of not supporting ARP offload while filtering out broadcast packets. This causes issue with connectivity when device is in suspend. Fix planned for next update.
At about this time the Google developer began to acknowledge that there were additional wifi problems with Nexus 4, 7, and 10 devices that were not related to the buggy Qualcomm driver used by the Nexus 4. The implication being that there were additional wifi bugs in Android 4.2.1.
Since January 14 there have been 87 additional bug reports and comments added to the bug report thread. Six of these were from the Google developer requesting info regarding router model number and firmware rev. of those people with Nexus 4, 7, and 10 devices that were experiencing problems connecting to the router.
To date, we are told by the Google developer that there is no ETA for fix(s).
In the mean time, another, potentially-related bug with the Nexus 4 has been reported: data dropouts that occur over mobile carrier HSPA+ data network connections. No acknowledgement of this yet from Google.