Database Develop

Diamond Wi-Fi Problem

I have recently procured an HTC Diamond mobile and is facing the following problem:
I have a Linksys Router at home. When I switch on the Wi-Fi in my Diamond, it gets connected to the router. In the status, I can see the signal strength, Tx, Rx rate etc. But when I open the browser (both opera & IE), the web pages does not open. Error message stating check the url or does any other programme using the internet works? appears. Even my weather does not get updated. Using the same router, I am able to connect my laptop as well as my desktop to Internet.
When my diamond is synced using active sync, my mobile is able to connect to the Internet & Weather application also get updated.
Kindly help me to resolve this issue and make diamond connect to net using wi-fi.
Thank you in advance.

I have the same problem sometimes
I just changed parameter in settings -> connections -> wireless lan -> power mode -> "best performance" instead of "best battery" and it seems to work now.
I'm new to WM, so I don't know if it's a bug: when I don't use my phone I press the power button, or I wait it to go to "sleep mode" in 40s.
When I press power button to reactivate the screen, I can see in the first seconds that the wlan was disconnected and connects again.
So it seems that wifi is always disconnected when the phone is in sleep mode? That means no mails can be received ? Can anyone confirm?
Thanks

Hi there for both of you!
I had a connection problem with my Diamond at home. It was almost the same as tkak just I couldn't figure out whether ActiveSync connects or not. I managed to bypass this to set my routers DHCP timeout from 1 week to 3 hours and it all went away. The network status showed periodic connect/reconnect during the problem so it might be a different prob than yours.
Peio64:
WM6 keeps WiFi connection asleep during sleep mode. Imagine the battery usage if it was connected to WiFi all the time. So be happy with that and beside it is usable. WiFi automatically tries to connect to the closest hot-spot if it was connected before each time you switch on. Normally it shouldn't take more than 5-10 seconds and the whole process can be followed on the top bar.
Mails: Use DirectPush and GPRS connection and e-mails will arrive instantly. Google for setting this up. With Wifi I dunno - if you schedule ActiveSync for a periodic check whether your WiFi will be used or a new GPRS connection. I think GPRS can be used while the device is asleep but I'm not sure. Someone should test this. Probably whichever is quicker to build up a connection will be used for data transfer. (Note: on some forum I read that if you disable GPRS auto check with a tweak battery will last longer so I guess this means that GPRS is always connected.
Regs, Cina.

Does your diamond obtain an IP adress from your router, and is the connection setup as 'connects to internet'?

cina said:
Hi there for both of you!
Peio64:
WM6 keeps WiFi connection asleep during sleep mode. Imagine the battery usage if it was connected to WiFi all the time. So be happy with that and beside it is usable. WiFi automatically tries to connect to the closest hot-spot if it was connected before each time you switch on. Normally it shouldn't take more than 5-10 seconds and the whole process can be followed on the top bar.
Mails: Use DirectPush and GPRS connection and e-mails will arrive instantly. Google for setting this up. With Wifi I dunno - if you schedule ActiveSync for a periodic check whether your WiFi will be used or a new GPRS connection. I think GPRS can be used while the device is asleep but I'm not sure. Someone should test this. Probably whichever is quicker to build up a connection will be used for data transfer. (Note: on some forum I read that if you disable GPRS auto check with a tweak battery will last longer so I guess this means that GPRS is always connected.
Regs, Cina.
Click to expand...
Click to collapse
Thank you for your answer,
I had a SE P1i before, and wifi was connected all the time with push mail. With the diamond and its weaker battery, I set up my mails schedule to connect every 15 min so wifi only needs to be active every 15min, even in sleep mode, I don't want it to be connected all the time this is of course a battery waste.
HSDPA is connecting in sleep mode there's no problem with that, I just wish to use wifi for mails when I'm at home as my data plan is unlimited for web surfing but only 10Mo/month for pop/imap connections.
BTW I don't use the "keylock" option, is it different from sleep mode in this case? I can't see the advantage of keylock versus sleep mode

I had an ETEN M600 for ages before and I found that for sync it always used GPRS even if WiFi was available. The cause for this was GPRS was available while device is asleep so it can start syncing immediately after wake up (does it needs to wake up for sync?). So you probably have to switch GPRS (HSDPA) off while you're at home.
Keylock is for locking hardware buttons and touchscreen while it is active. (You won't dial up anyone from your pocket). It has nothing to do with sleeping just if you set up the registry tweak the device get locked (Keylock software is started) if you press power to send it to sleep. (I've almost written "off" but it is obviously not true - you can switch it off with a long press on power = soft reset).
Hope this helped a bit.
Cina

Okay thank you, I checked and HSDPA is connecting every 15min in sleep mode even with wifi ON. If I switch data off I suppose nothing connects and no mail is received, which is I think it's a weird behaviour.
By the way, I have set my data connection to swich off 10 seconds after not being used, and it works perfectly and reconnects automatiquely when it needs to. But for the wifi I can find that option, it's stays connected all the time when I use the phone, even if I don't need to. Is it possible?
Maybe it's due to the fact that it's always checking if there are new networks? On Symbian UIQ3, you can pre-configure networks, give manually priorities for each networks (1.Wlan work, 2.Wlan home, 3.3G etc..) and for each application (web, mail, etc). When the phone connects it checks if the network "1" is available, if it's not it checks the network "2", and once it's connected it doesn't check anymore. Is there a WM6 advanced network tool like that?
(Sorry for my english)

I did the following and now it gets connected to the web:
I just changed parameter in settings -> connections -> wireless lan -> power mode -> "best performance" instead of "best battery".
I do not know why this needs to be done like this.
Thankyou all for resolving my problem

I'm experiencing problems connecting to my WL Router (DrayTek 2820n) using WiFi when the router is set to Auto instead of to a specific channel. I've noticed from some threads for other mobiles that people are exprience similar problems. Does anybody knows what is the story around which channels are supported on WiFi: 1-11, 1-12 or 1-13. My router is set to 13 by default. In addtion to that Diamond has problem to connect to some channels even in the 1-11 range. So how can I check, which channels are supported and for which region?
Edit: I did further testing and it became obvious that when using Auto channel selection on the router, Diamond wouldn't connect. When selecting manually any channel between 1-11 it works OK, but when selection channels 12-13 it stops working, which makes me believe that the Diamond doesn't have support for the channels for non-US regions.

Does anybody have any idea how to change wifi region to support 12-13 channels as well? So far I couldn't find anything on the net that would help me doing it. Is it possible that it might be WM 6.1 issue and not Diamond?

HI I am actually having a diffirent issue but still related to wi-fi. When my phone awakes from sleep, it promts me to connect to my wi-fi server at home, when it was already connected jus minutes before. I have to re-enter the pass phrase everytime it awakes from sleep. This does not seem normal as my 6.0 touch didnt do that.
Any takers on this?

For more channels, it depend of US version or EU version. You need to changer your firmware but the problem is that in France for Internet you use PPoA and Belgium PPoE and I do not know if in the US they use the same so you will probebly losse your ability to connect to the Internet. Having more channels is not interesting because you need a hope of 5 between channels ( ex : ch1 + 5 = ch 6 and ch6 + 5 = ch11) between ch1 and ch6 place a ch11 for avoiding interferances. In 802.11g that is a question of scheme.
Sorry for my poor English.

Problem connecting to home network wifi
Hi, i've been using diamond to connect to my wifi home network but since few days is not possible anymore even if nothing was changed in the settings of the router.
The phone recognize the network as available, i push connect, it comes connecting but instead of connecting to the netwok it goes back to available.
Password is correct and the setting are the same as few days ago.
Any idea which setting should be modified?
Thanks in advance!
Panco76

Hello everyone,
I have one problem with my diamond. I disabled the "data transfer" with the improved comm manager. I usually use wifi when i'm home, however, i've seen that even though wifi is active, HSDPA connection is activated as well so i got charged, this sometimes happens when updating weather data or downloading emails.
Anyone with the same problem?

Yes - having he same problem.
I have WIFI at home and at work - so i want to use GPRS only when i am outside. never managed to do this - except when i kill GPRS fully - and even then Opera, the weather and push-mail wont work. :-(

WiFi Channels 12-13?
I need to bump up this issue again.
I can't find anywhere in this forum how would you change your WiFi channel range from US to EU (i.e. 1-11 to 1-13). My Diamond was purchased in Australia and I was hoping that the new SW upgrade would rectify that, but it looks to me that's not the case. Any idea if that can be done in registry?
Thanks.

Change Channel range from 1-11 to 1-13
***Bump***
Has anybody got any ideas how to increase the channel range from 1-11 to 1-13?

Hi, I am having a seperate problem from all that are listed. I have the linksys rangeplus router, and my Diamond wont even detect my network when it searches, yet my computer and PS3 do fine. Can anyone help me?

another problem...
Hi,
i have a problem with the wifi on my Diamond aswell..
I have a router at home which is encrypted. When I try to connect to it, I type the encryption key and it says Connected but i cant surf any pages. When i go back to wifi settings my home network switches between Not available and Connecting...
However, when i remove the encryption, everything seems to work fine. Since i dont want to treat my neighbors with free internet, does anyone have any tips for me?
(it is set to Best performance... +i'm sure i enter the right key...)
Thanx

The same over here... I found out, that some of cooked ROMs had this problem, but official worked. Before I couldn't connect via WPA2-PSK AES, all other encryptions worked. Until now... I tried to flash official ROM and RADIO, but it doesn't work anymore. I'm pretty sure it must be hardware problem. I need to send my Diamond to get fixed, but... The closest repair centre is in Prague (GSMobile)
!!!!!!!!!!!!!BUT BE AWARE!!!!!!!!!!!
I owned previously Qtek8310. After I send them my Qtek to replace the joystick, it came back with broken motherboard... This repeated 3 times and everytime they broke something else. I've got my Qtek8310 back as a total crap, destroyed and scratched... I called and send a claim to HTC Europe in London, but nothing happened since then. I don't believe them anymore. If you love your Diamond avoid to get it fixed in GSMobile!

wifi sleep policy not work correctly?

My wifi seems to disconnect from my wifi when the screen turns off, despite me having changed my settings to never sleep. When I look at the wifi settings it says "Unsuccessful Connection". I didn't have this problem with my MT3G.
Anyone having similiar issues or a fix?

wifi Reconnection issues
I'm having the same problems with mine.
It initially connects to wifi fine but when the screen goes off it sometimes drops the connection and will not reconnect without a reboot.
I have tried setting it to keep the wifi when sleeping but it makes no difference.
I found a few similar reports elsewhere and followed most of the suggestions, like changing routers, changing wifi channels, setting an IP address instead of DHCP etc. Nothing seems to make any difference so far.

Mine never seems to reconnect after waking up, but I just go into the Wireless settings/Wifi settings window (where it lists all the Wifi networks in the area) and press on the network name and it brings up a dialog allowing me to connect again. I press the Connect button and it instantly reconnects. No reboot required...

Try increase your router's "Group Key Update Interval". I had the same problem with my D-Link DIR-655. I changed mine to 10 hours and it's working fine for me now.

i have the issus that my wifi is "connected" i mean i see the logo at the top bar but after a few minutes i don't get any update from the internet like gmail oder twitter when is wake up the device from sleep i get them back again
maybe it something with the Group Key Intervall but i can't switch it on my speedport w700v router

I just tried switching mine, highest it can go is 7200 seconds, so I bumped it to two hours instead of one. linksys
my wifi reconnects when I wake the screen almost 100% but it's not reliable.
I have to go to wifi list and reconnect. Sometimes I disable wifi and then re enable, conects no problem. Irritating

i heared that switching the encryption from wpa/wpa2 to only wpa2 will solve this issues, will try it when i am at home

...seems like almost everybody got this problem.

for example with my Hero i don't had this problems so it's something with the W-Lan card of the Nexus

Got this problem too but will try the suggested work arounds when I get home tonight

found out that my encryption is wpa2 not wpa/wpa2 ... damn so thats not the reason
and my router cant configure the group key intervall

I don't have this issue, running CM5.0.3.1, mine is set to Never Sleep and it does not. My connection does not time out either. I connect to two Trendnet TEW-637AP's at home, in mixed b/g/n mode with WPA2-PSK mode security.

Could it be, that this prob exists just for nonrooted phones?!

i've got mcr 1.6 which is rooted and don't work
i think it's a problem with the wifi card and the wifi router
rooting just means that you get read/write access to all folders
doesn't change anything on your wifi connection

qvert said:
i've got mcr 1.6 which is rooted and don't work
i think it's a problem with the wifi card and the wifi router
rooting just means that you get read/write access to all folders
doesn't change anything on your wifi connection
Click to expand...
Click to collapse
Not exactly, it means also modified system files, which could include those that interface with the wifi chip and those that control the sleep state of the device.
Also, Cyanogen (and most other custom roms now) are running on a different (newer) kernel.

yes i know
but mcr is although running on different kernel and it's not working there
i don't think its an issue bei the stock rom and mcr
maybe here is someone with CM where the wifi drops?
edit:
okay i tried it with the desire rom version from modaco, the same failures, maybe i try a CM built now, and see if it changes
Code:
[B]Rom [/B] [B]Router / Access Point[/B]
MCR 1.6 | Speedport w700v | not working
Desire MCR | Speedport w700v | not working
CM 5.0.3.1 | Speedport w700v | not working
i think this means it's not a rom issue, its something with the routers and access points in combination of the wifi card from the nexus

That´s strange..perhaps just accidentally, but: yesterday I installed "Task Manager" , which has an auto-kill function.....since then my Wifi reconnects perfectly

maybe because it automatically does anything inside of the 10 minutes which keeps the wifi active?
which one did you install?
there are a lot of them on the market
which developer?
edit:
ah i found a strange issue, today i was at the wifi of my girlfriend, she has the same router BUT i don't have the wifi problems there, with the same model of router thats very strange

i found another work around, i set my twitter client to 5 minutes update intervall, this means every 5 minutes is network traffic and the connection won't drop after my 10 minutes public key intervall change
don't know how much battery is used while setting from 10 to 5 minutes but i think it should be okay

Try a different WiFi channel
I've seen reports of WiFi connection problems being solved by changing channels on the AP. Channel 10 seems to be a consistently reliable choice.

Problems with switching from wlan to 3g

There is the following problem with my LG Optimus 2x, but the problem happens on many other devices with differnet roms, too:
If you start your phone, everything is ok and you can easily switch from wlan to 3g without any problems. But after a few hours in wlan mode, 3g mode doesn't start correctly if you deactivate wlan. It seems as if 3g freezes after a few hours in wlan mode. To solve this problem, you have to switch in airplane mode or restart your cell phone.
Does anybody know, whats the reason for this problem and how to solve it?
Thx.

The aLogcat error report is:
E/WifiStateMachine( 1559): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg wlan0 0.0.0.0 0 [down broadcast running multicast]} failed with code 501 : {Flag unsupported}
D/NetworkManagementService( 1559): rsp <213 78:d6:f0:6a:90:cc 0.0.0.0 0 [up broadcast running multicast]>
E/WifiStateMachine( 1207): Unable to change interface settings: java.lang.IllegalStateException: Unable to
communicate with native daemon to interface setcfg – com.android.server.NativeDaemonConnectorException: Cmd {interface
setcfg wlan0 0.0.0.0 0 [down broadcast running multicast]} failed
with code 501 : {Flag unsupported}
E/ConnectivityService (1207): exeption trying to remove a route: java.lang.IllegalState ...

I`ve got the same problem as you are, only switching to airplane mode can help.
It`s hard to believe that only few people have this problem...
I think it`s something with BB and RiL but not for 100% sure....

I also have same problem. For me it all started after i flashed 20c and 20s basebands.
Enviado desde mi GT-N7000 usando Tapatalk 2

News for this problem?

i spend couple hours to testing this issue...and i'm almost pretty sure its simcard problem or internal baseband issue when change from 3G to H. I was change simcard to another one from other operator and the issue doesn't exist. On T-Mobile simcard when i change settings 3G/2G, turn data off/on, start GPS software, turn on/off airplane mode, sometimes the FC exist. On Play Operator simcard FC doesn't exist but Play don't have Fast Dormacy and Data still show H on status bar, 3G never appeard.
Sorry for my english...

It's a bad integration between BB and the Rom.. switch to cyanogenmod and you won't have this problem anymore
Inviato dal mio Optimus 2X

Byteater said:
It's a bad integration between BB and the Rom.. switch to cyanogenmod and you won't have this problem anymore
Click to expand...
Click to collapse
I have CM7 temasek 128...:/ I tested all roms, from stock to CM9...all the same issue...another problem is sometimes the gps can't take fix, and when i change mode from 3G to Edge, gps works again...and manual choosing network can't find any networks, on Edge works fine...

Try using the harsh karnel its the most stable kernel
And the lost signal are Low frequency.

Wifi network connectivity issues and a possible fix

4.3 Update: It looks like Android 4.3 (JWR66V) did not fix the Nexus 4 delayed notifications on wifi issue. New wifi drivers with ARP offload support are included but for some unknown reason, Google disabled ARP offload in this release (even though ARP offload was enabled in the leaked 4.3 version). Interestingly, ARP offload is now re-enabled in AOSP JSS15J.
If you are on JWR66V and still have delayed notifications on wifi, then check this post for instructions on how to enable ARP offload either manually or with a flashable ZIP: http://forum.xda-developers.com/showpost.php?p=43940926&postcount=601. Only do this if you are running 4.3 JWR66V.
An alternative option is to try disabling wifi optimization. Some people have found this fixes the delayed notification problem but also causes an increased battery drain.
----------------------------
Below is for Android 4.2 builds only
Update: Android 4.2.2 is out and despite a comment from a Google rep that this was fixed and the fix was scheduled to be included in 4.2.2, it appears that isn't the case. This same rep from Google just confirmed as much in post 34 - https://code.google.com/p/android/issues/detail?id=42272#c34.
I've confirmed the workaround described in this thread does still work on 4.2.2. Also, the ini file that this workaround changes was untouched between 4.2.1 and 4.2.2 so the same zip files posted here will work on either version.
Also, thanks to thesebastian for finding this - it looks like Qualcomm is finally getting ARP Offload fixed (http://forum.xda-developers.com/showpost.php?p=38598963&postcount=267). Hopefully they will get this pushed out sometime soon.
------------------
Since the Nexus 4 was released, there have been many reports of various problems with wifi. Everything from slow speeds to delayed notifications to not being able to connect to certain APs at all. With the release of Android 4.2.2, a lot of these problems have been fixed. Unfortunately, a number of issues still remain.
One issue that has yet to be fixed as of 4.2.2 is the ability for the phone to respond to ARP requests while the screen is off. This results in the phone being unable to receive network traffic over wifi under certain circumstances while asleep. The most noticeable effect of this issue is notifications being delayed for up to 15 minutes while the screen is off. During this time, turning the screen on will result in these delayed notifications flooding in all at once. You may also notice the wifi signal indicator turning gray immediately after turning the screen on followed a few seconds later by it turning blue. Another symptom that some have had is incoming VoIP calls not ringing the phone while the screen is off but working fine while the screen is on.
This issue has been confirmed by Google (https://code.google.com/p/android/issues/detail?id=42272) and is related to a buggy implementation of ARP Offload in the Nexus 4 wifi driver. Due to this, ARP Offload is disabled on the N4. In addition, the N4 wifi driver is set to filter all incoming broadcast and multicast traffic during sleep. Since ARP is broadcast (usually), the combination of these settings will prevent the phone from hearing and responding to ARP requests while the screen is off. If a neighboring network device (such as your router) is unable to obtain the MAC address of the phone, it will be unable to send any traffic to the phone.
Please note that this issue only affects the Nexus 4 (and possibly other devices with the Prima wifi chip). Wifi issues on other devices are not affected by this particular issue. Also note, this is one particular issue with the N4 wifi. There are lots of other issues. The workarounds described here will not help with those issues.
Also, even though all Nexus 4's are affected by this issue, not everyone will be affected in the same way. One of the main reasons for this is due to varying router configurations (in particular, the ARP cache timers). Some will even be lucky enough to have this problem completely masked due to their router configuration. If you are so lucky, you can still see the effect of this issue - turn the screen off, wait a few minutes, and ping the phone from your PC. While doing this run Wireshark and notice the unanswered ARP queries being sent to your phone.
----------------
Until Google releases a proper fix (ARP Offload), there are a couple of options to work around this issue.
Option 1 - Static ARP
The easiest fix is to add a static ARP entry for your N4 to your router. This allows the router to communicate with the phone without having to bother with the ARP process (thereby bypassing the issue completely). On some routers, there is an option to directly add a static ARP entry. On some, you have to do it via the CLI. On some, adding a static DHCP lease also adds a static ARP entry. And of course some just don't allow you to set this.
There are a couple of negatives. First, you may not have access to all routers that you connect to. Even if you do have access, you may not be able to set a static ARP depending on the firmware on the router. Also, you would have to add a static ARP to every device on the same network segment that you would want to communicate with. Say for example you used wireless ADB. In that case you would have to add a static ARP to both the router and the PC that you ran ADB on.
The positive to adding a static ARP entry is you don't have to muck with a system file on the phone and this option is the most battery efficient.
Option 2 - Disable filtering on the N4
Another solution is to disable the unicast and/or multicast filtering on your N4 by modifying an ini file on the phone. This will allow the phone to see all broadcast traffic (including ARP) during sleep. As a result the phone will be able to properly respond to ARP requests.
The positive is once you make this change, the phone will properly respond to ARP requests without having to make any other changes. It will work with any wifi network that you connect to.
The negative is making this change will cause a negative impact on battery life. How much of an impact depends entirely on how much broadcast and multicast traffic exists on your network. The more traffic, the more the phone is woken up, the more the battery hit will be. The only way to know how much of a battery impact you will have is to test it out.
To make the ini file change manually (see below for installable zip files):
Make sure your phone is rooted
Remount /system as RW
Make a backup of file /system/etc/wifi/WCNSS_qcom_cfg.ini
Edit the file /system/etc/wifi/WCNSS_qcom_cfg.ini
Change the line "McastBcastFilter=3" to "McastBcastFilter=0"
Save the file and double check file permissions (-rw-r--r-- root root)
Reboot the phone
To undo this change, simply change the "0" back to the original value of "3". If you want to prevent the the phone from hearing multicast traffic while the screen is off but still allow broadcast traffic, you could change the value to "1". This may help with battery life and will keep most things working.
Please remember, this changes a system file so 2 things. First, I'm not responsible if you break something. Second, this will likely prevent the phone from being able to get an OTA. You would need to revert the change before applying an OTA.
--------------------
One other router setting that can cause the same type of issue that some have run into is related to the TCP Established timer. If you are still having this problem after making the ini file change (or static ARP), make sure that the TCP Established timer on your router is set to at least 1200 seconds.
------------------------------------------
Edit 12/31: I attached CWM installable zip files to make changing the ini file easier and help prevent file permission problems, etc. I tested all 3 files with my Nexus 4 using CWM 6.0.2.3.
n4-wifi-sleepfix-restore-original.zip -- This restores the ini file to the original one from stock 4.2.1 JOP40D / 4.2.2 JDQ39.
n4-wifi-sleepfix-mcast_and_bcast.zip -- This sets McastBcastFilter to 0, allowing the phone to hear multicast and broadcast traffic during sleep. Only for 4.2.1 JOP40D / 4.2.2 JDQ39.
n4-wifi-sleepfix-bcast_only.zip -- This sets McastBcastFilter to 1, allowing the phone to hear broadcast traffic during sleep, but not multicast. Only for 4.2.1 JOP40D / 4.2.2 JDQ39.
Don't forget to make a CWM backup first!

bganley said:
Since getting the Nexus 4, I've had problems with wifi network connectivity while the screen is off. The phone will stay associated to the AP (as can be verified by looking at the AP itself), but after a couple minutes of screen-off time, incoming network traffic seems to be ignored by the phone. I also have a Nexus 7, a Galaxy Nexus, and an Atrix - none of which have this problem.
The symptoms are things like gmail notifications taking up to 15 minutes to arrive while the screen is off. Another symptom is seeing the wifi indicator turn gray followed a few seconds later by the indicator turning blue again immediately after turning the screen on.
An easy way to see the issue is to ping the phone from another device connected to the same network segment. Turn the screen on, ping the phone and you should get a response as expected. Turn the screen off, wait a few minutes and try to ping the phone again and you will likely get a timeout. The amount of time you have to wait depends on the OS of the device you are sending the ping from (more specifically the ARP cache timeout).
Doing a network capture, I found the issue that I've been having is the phone doesn't respond to ARP requests while the screen is off. One easy fix that I've been using for a couple of days is to add a static ARP entry. I added one to my router so that it doesn't need to perform an ARP request when sending traffic to the phone. Since doing this I've had 0 problems. Gmail notifications now come in faster on my Nexus 4 than any other android device I own. I also never see the wifi indicator turning gray any more.
I've been doing some more digging and I think I found a better solution to the issue. There is an ini file that allows you to set parameters for the wifi driver on the phone. One of these parameters controls the filtering of multicast and broadcast traffic during power save. The default on the Nexus 4 is to filter all broadcast and multicast traffic. Since ARP requests are broadcast, this is obviously an issue.
I tried changing the parameter to only filter multicast traffic and so far so good. The phone takes a couple of seconds to respond to ARP requests while the screen is off (which is expected during low power states) but it now does respond. Now I just need to run this for a couple of days and see what kind of impact it will have on the battery.
To make the ini file change:
Make sure your phone is rooted
Remount /system as RW
Make a backup of file /system/etc/wifi/WCNSS_qcom_cfg.ini
Edit the file /system/etc/wifi/WCNSS_qcom_cfg.ini
Change the line "McastBcastFilter=3" to "McastBcastFilter=1"
Save the file and reboot
To undo this change, simply change the "1" back to the original value of "3". If you want the phone to hear multicast traffic while the screen is off, you could change the value to "0".
Please remember, this changes a system file so 2 things. First, I'm not responsible if you break something. Second, this will likely prevent the phone from being able to get an OTA. You would need to revert the change before applying an OTA.
I just wanted to pass this along and see if anyone else has been experiencing this issue. If so, hopefully this info will help prevent others from wanting to smash their phone into a million bits.
Click to expand...
Click to collapse
You're my hero. I'm not rooted and don't want to mess with this yet but curious about static ARP. Assuming you do this by turning on Mac address filtering and adding the N4 Mac address to router. I don't see any way to edit the ARP table on my Cisco E4200
Sent from my Nexus 4 using Tapatalk 2

I recently got a Nexus 7 and i can definitely see a difference in wifi performance. I wish i could fix it

mobilehavoc said:
You're my hero. I'm not rooted and don't want to mess with this yet but curious about static ARP. Assuming you do this by turning on Mac address filtering and adding the N4 Mac address to router. I don't see any way to edit the ARP table on my Cisco E4200
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
MAC address filtering is different from a static ARP entry. MAC filtering just defines which MAC addresses are allowed to associate to an access point. A static ARP entry is a way to manually define the MAC address associated with a specific IP address. Normally, the ARP protocol takes care of this for you by broadcasting an ARP request. The device which has the IP address in question sees that broadcast and replies back with its MAC address. Since the phone isn't listening to broadcast traffic while the screen is off, it will never see the ARP request and thus will not respond to an ARP request while the screen is off. Setting a static ARP entry just bypasses the need for the normal ARP processing as the sending device will always know the MAC address of the device it is trying to send a packet to.
I don't have an E4200 so I'm not sure what options it has. On my router, I can telnet to a linux shell on it which allows me to add a static ARP entry with the command "arp -s ip-address mac-address". This adds a static entry to the ARP cache which will be lost on reboot. Of course, you could just add it to a startup script so that it would be added every time the router reboots.
I've heard reports that some routers will effectively add a static ARP entry if you define a static DHCP reservation. You could try that. Somewhere in your router you should be able to say that the MAC address of your phone should always get assigned a specific IP address from DHCP. Actually, I would highly recommend that anyone who wants to try the static ARP method do this regardless. If you specify IP address X equals MAC address Y, it would be a good idea that it always does
Let us know if you have any luck figuring out how to do this on an E4200.

bganley said:
Since getting the Nexus 4, I've had problems with wifi network connectivity while the screen is off. The phone will stay associated to the AP (as can be verified by looking at the AP itself), but after a couple minutes of screen-off time, incoming network traffic seems to be ignored by the phone. I also have a Nexus 7, a Galaxy Nexus, and an Atrix - none of which have this problem.
The symptoms are things like gmail notifications taking up to 15 minutes to arrive while the screen is off. Another symptom is seeing the wifi indicator turn gray followed a few seconds later by the indicator turning blue again immediately after turning the screen on.
An easy way to see the issue is to ping the phone from another device connected to the same network segment. Turn the screen on, ping the phone and you should get a response as expected. Turn the screen off, wait a few minutes and try to ping the phone again and you will likely get a timeout. The amount of time you have to wait depends on the OS of the device you are sending the ping from (more specifically the ARP cache timeout).
Doing a network capture, I found the issue that I've been having is the phone doesn't respond to ARP requests while the screen is off. One easy fix that I've been using for a couple of days is to add a static ARP entry. I added one to my router so that it doesn't need to perform an ARP request when sending traffic to the phone. Since doing this I've had 0 problems. Gmail notifications now come in faster on my Nexus 4 than any other android device I own. I also never see the wifi indicator turning gray any more.
I've been doing some more digging and I think I found a better solution to the issue. There is an ini file that allows you to set parameters for the wifi driver on the phone. One of these parameters controls the filtering of multicast and broadcast traffic during power save. The default on the Nexus 4 is to filter all broadcast and multicast traffic. Since ARP requests are broadcast, this is obviously an issue.
I tried changing the parameter to only filter multicast traffic and so far so good. The phone takes a couple of seconds to respond to ARP requests while the screen is off (which is expected during low power states) but it now does respond. Now I just need to run this for a couple of days and see what kind of impact it will have on the battery.
To make the ini file change:
Make sure your phone is rooted
Remount /system as RW
Make a backup of file /system/etc/wifi/WCNSS_qcom_cfg.ini
Edit the file /system/etc/wifi/WCNSS_qcom_cfg.ini
Change the line "McastBcastFilter=3" to "McastBcastFilter=1"
Save the file and reboot
To undo this change, simply change the "1" back to the original value of "3". If you want the phone to hear multicast traffic while the screen is off, you could change the value to "0".
Please remember, this changes a system file so 2 things. First, I'm not responsible if you break something. Second, this will likely prevent the phone from being able to get an OTA. You would need to revert the change before applying an OTA.
I just wanted to pass this along and see if anyone else has been experiencing this issue. If so, hopefully this info will help prevent others from wanting to smash their phone into a million bits.
Click to expand...
Click to collapse
Thank you, but edit "WCNSS_qcom_cfg.ini" not works for me. WiFi simbol nether apears, even when I return to option "3". I used cwm restore and it returned like before (conect but transfer data only for 15 seconds).
Enviado de meu Nexus 4 usando o Tapatalk 2

The ini change just made wifi fail to start for me, unfortunately.

Lucena04 said:
Thank you, but edit "WCNSS_qcom_cfg.ini" not works for me. WiFi simbol nether apears, even when I return to option "3". I used cwm restore and it returned like before (conect but transfer data only for 15 seconds).
Enviado de meu Nexus 4 usando o Tapatalk 2
Click to expand...
Click to collapse
adamase said:
The ini change just made wifi fail to start for me, unfortunately.
Click to expand...
Click to collapse
Sorry to hear you guys are having problems. Make sure the file editor you are using isn't changing the permissions. After modifying the file, it should look exactly like this:
[email protected]:/system/etc/wifi # ls -l WCNSS_qcom_cfg.ini
-rw-r--r-- root root 5577 2012-12-29 19:17 WCNSS_qcom_cfg.ini
Make sure the permissions (-rw-r--r--), the owner (root), and the group (root) are identical to this. If the permissions, owner, or group are different, you can reset them with:
chmod 644 WCNSS_qcom_cfg.ini
chown root.root WCNSS_qcom_cfg.ini
I've been running this change for 2 days and my wifi has been 100% stable. It has fixed all the problems I was having.

I just wanted to add that I've read about a lot of various wifi problems that people have been experiencing. This fix is specifically to address the problem with the phone not being able to properly maintain an active network connection while the screen is off. The most noticeable symptom is incoming notifications (like new gmail alerts) taking minutes (sometimes up to 15 in my case) instead of seconds to appear.
If you have other problems like slow wifi speeds or not being able to connect to wifi, this patch is still applicable to your Nexus 4 but there are additional problems you are likely encountering. I personally have not experienced any of these other issues.
Also just to clarify, how noticeable the problem is to you will depend on the settings of your router, in particular the ARP cache timeout. For example, enterprise level Cisco gear uses a 4 hour timeout by default whereas linux (which most home routers run) defaults to 60 seconds. The quicker the cache times out, the more noticeable the problem.

Updated first post with CWM installable files to make ini file changes. Please let me know if anyone has any problems installing these.

bganley said:
Updated first post with CWM installable files to make ini file changes. Please let me know if anyone has any problems installing these.
Click to expand...
Click to collapse
Please contact Google so they know about this. I'll be applying the patch tomorrow when I'm back home. Happy New Year!
Sent from my Nexus 7 using Tapatalk 2

How does this impact battery life e.g. will it cause wakeups when responding to broadcast/multicast requests?
Whilst my Nexus 4 seems to stop responding to pings when the screen is off I still seem to get notifications in a timely manner, even with mobile data turned off just to test

I flashed the n4-wifi-sleepfix-mcast_and_bcast.zip but the problem still exists. Gmail and whatsapp notification takes about 5 minutes...

How do the default settings on the N4 differ when it comes to this line in the INI when compared to other devices? Are other devices able to capture GMail messages almost instantly despite having a value of '3' in this line? I know that my One X was fantastic when it came to receiving messages quickly, whereas this N4 takes a long time to get messages.

defnz said:
How does this impact battery life e.g. will it cause wakeups when responding to broadcast/multicast requests?
Whilst my Nexus 4 seems to stop responding to pings when the screen is off I still seem to get notifications in a timely manner, even with mobile data turned off just to test
Click to expand...
Click to collapse
I've been testing the battery life impact the last few days and so far it appears the ini file patch has an impact. This is expected as the phone now has to process incoming broadcast/multicast packets. With the patch applied, it appears to really aggravate the msm_hsic_host wakelock nonsense and in turn cause the phone to spend less time in deep sleep according to BBS. In my case, this hasn't resulted in that much of a difference in battery life but I'm continuing to monitor.
I did try out Franco's latest kernel as he has some patches for the wakelock issue and with his kernel there was a huge improvement in deep sleep time both with and without this patch applied. Battery usage per hour also improved from about 1.2% with the stock kernel to about 0.5% with Franco's kernel.
Interesting that you still receive notifications in a timely manner. What amount of time do you consider timely? For me, it was taking anywhere from instant notification (rare) to 15 minutes at the worst without this patch. What router do you use? Are you running any custom firmware on your router? Is your phone assigned a static or DHCP address? Are you using a static DHCP reservation for your phone?

antih3ro said:
I flashed the n4-wifi-sleepfix-mcast_and_bcast.zip but the problem still exists. Gmail and whatsapp notification takes about 5 minutes...
Click to expand...
Click to collapse
Your sig says your are running CM? I'm not sure how this patch would work with that ROM. I've only tested with stock JOP40D.

floepie said:
How do the default settings on the N4 differ when it comes to this line in the INI when compared to other devices? Are other devices able to capture GMail messages almost instantly despite having a value of '3' in this line? I know that my One X was fantastic when it came to receiving messages quickly, whereas this N4 takes a long time to get messages.
Click to expand...
Click to collapse
The other devices I've looked at don't have the same wifi chip and therefore don't have this INI file. I did a bunch of testing with my Galaxy Nexus and Nexus 7 to try and determine how they were behaving in regards to multicast/broadcast traffic during sleep. I was able to show that both devices process and respond to both broadcast and multicast traffic during sleep.
This makes sense as certain network functions (such as ARP) rely on broadcast traffic. If a device isn't processing broadcast traffic, then those things break as we've seen with this phone.
I have a GNex, a N7, and an Atrix all running alongside the Nexus 4. All of those phones respond to incoming gmail notifications within seconds and now with this patch, so does my N4.

I've had the exact same issues with my nexus 4....thanks
Sent from my Nexus 7 using Tapatalk HD

bganley said:
Interesting that you still receive notifications in a timely manner. What amount of time do you consider timely? For me, it was taking anywhere from instant notification (rare) to 15 minutes at the worst without this patch. What router do you use? Are you running any custom firmware on your router? Is your phone assigned a static or DHCP address? Are you using a static DHCP reservation for your phone?
Click to expand...
Click to collapse
I've been doing comparisons with a SGS2 and sometimes the N4 receives it before the SGS2, sometimes after, it's anywhere from instant ~5 seconds for gmail, sometimes it can take longer but the delay is seen on both the N4 and the SGS2. However with gTalk its pretty much instant on both.
I'm running an Asus RT-N66U w/ Asuswrt-Merlin 3.0.0.4.264.22 firmware
DHCP, no DHCP reservations, no static arp entry either
In saying that, I don't disagree with your findings though. The phone should have multicast/broadcast enabled so that it doesn't break things like ARP.

I'd like to get this to work, but unfortunately, things haven't changed a bit. Permissions are correct, rebooted, etc. I'm running DD-WRT and have reserved a static IP at the router by MAC association, which I do for everything on the network by the way. I've even changed DHCP to static on the device. Gmails show instantly at the PC, but appear up to 15 minutes later on the device. The device is ping-able when the screen is off.

floepie said:
I'd like to get this to work, but unfortunately, things haven't changed a bit. Permissions are correct, rebooted, etc. I'm running DD-WRT and have reserved a static IP at the router by MAC association, which I do for everything on the network by the way. I've even changed DHCP to static on the device. Gmails show instantly at the PC, but appear up to 15 minutes later on the device. The device is ping-able when the screen is off.
Click to expand...
Click to collapse
Try changing to 0 so it is not filtering anything
Sent from my Nexus 4 using Tapatalk 2

MIUI 12.5 wifi issues

Hi, today I received the EU update to MIUI 12.5 - 12.5.1.0(RFAEUXM) . However, now my Mi 9 can't connect to wireless networks. I already tried restore the network defaults and then the factory reset without success. Any ideas?
The behavior is - I move the switch to turn on, seems like it is on but no networks are displayed. If I move away to other apps and then look again for wifi switch, it is off again. I feel some lag when I go into wifi settings pages and after turn the switch on.

Do you have some system apps disabled? I remember similar behaviour when I used to disable/remove system apps on Q.
If factory resetting did not help you, then it's definitely the OS has a problem. Wait for another update, or try to reflash the latest firmware using PC.

No, I don't :/
I already looked into logcat and seems related with the wifi driver the issue:
07-12 16:42:33.989 846 846 E [email protected]: Failed to write driver state control param: Invalid argument
07-12 16:42:33.989 846 846 E [email protected]: Failed to load WiFi driver
07-12 16:42:33.989 846 846 E [email protected]: Failed to initialize firmware mode controller
07-12 16:42:33.989 846 846 E [email protected]: Wifi HAL start failed
It's complicated just live with mobile data and a limited plan until a new update. I believe that I can't reflash because I don't have the Mi 9 unlocked and to unlock it I should wait (360h I believe). I already tried the "download latest package" from "about phone" but I still have the wifi issue.
Downgrade or flash another ROM should work but as I said I have the phone locked.

That's a lot like Kernel issue, small update should fix it. Send a report to Xiaomi regards the issue.
Since you're locked, you better wait this fortnight.

Same issue here, have tried to reset Wifi, Mobile network and Bluetooth settings but no improvements

Have restored MIUI 12.0.5.0 from Fastboot in order to get Wifi working again...
Very bad work from Xiaomi for this

AlexPinote said:
Hi, today I received the EU update to MIUI 12.5 - 12.5.1.0(RFAEUXM) . However, now my Mi 9 can't connect to wireless networks. I already tried restore the network defaults and then the factory reset without success. Any ideas?
The behavior is - I move the switch to turn on, seems like it is on but no networks are displayed. If I move away to other apps and then look again for wifi switch, it is off again. I feel some lag when I go into wifi settings pages and after turn the switch on.
Click to expand...
Click to collapse
I updated to the same version and have no problem with WiFi.

AlexPinote said:
Hi, today I received the EU update to MIUI 12.5 - 12.5.1.0(RFAEUXM) . However, now my Mi 9 can't connect to wireless networks. I already tried restore the network defaults and then the factory reset without success. Any ideas?
The behavior is - I move the switch to turn on, seems like it is on but no networks are displayed. If I move away to other apps and then look again for wifi switch, it is off again. I feel some lag when I go into wifi settings pages and after turn the switch on.
Click to expand...
Click to collapse
I first experienced this issue after updating my mi 10t global to 12.1.3. It's a known bug and has been discussed at greater length on the mi community website. It remains unfixed in the 12.5.1 update.
However, there is a temporary solution that will allow you to reconnect to your wifi network. You'd have to change your ip settings from dhcp to static, and enter the relevant digits. That's it.
On a separate a note, 12.1.3 also introduced a mobile data bug that remains unfixed in 12.5.1. If you've set a private dns provider hostname under private ip, you will no longer be able to use mobile data. You'd have to toggle this setting to off or auto to get mobile data working again.

Dagabix said:
I first experienced this issue after updating my mi 10t global to 12.1.3. It's a known bug and has been discussed at greater length on the mi community website. It remains unfixed in the 12.5.1 update.
However, there is a temporary solution that will allow you to reconnect to your wifi network. You'd have to change your ip settings from dhcp to static, and enter the relevant digits. That's it.
On a separate a note, 12.1.3 also introduced a mobile data bug that remains unfixed in 12.5.1. If you've set a private dns provider hostname under private ip, you will no longer be able to use mobile data. You'd have to toggle this setting to off or auto to get mobile data working again.
Click to expand...
Click to collapse
how did you do it? how did the wifi work?

Higorhg said:
how did you do it? how did the wifi work?
Click to expand...
Click to collapse
If you're able to see your wifi network name listed under wifi assistant or available networks, even if it's not active/connected you should be able to press the arrow on the right and enter the settings for that network. Here you'd have to change ip address from dhcp to static, then enter the relevant digits in the spaces that appear below (assuming you know what they are). Then press the tick up at the top right to save before exiting.

I have same problem
I found this on Youtube and its work for me

This is definitely not the same problem.
Our issue is about the Wifi that is not working at all, no wireless networks, no connection, phone constantly crashing when entering Wifi menu.
Also, there is an issue with GPS Localisation (maybe related to the wifi as the phone is using wifi to have more accurate result).
Have received again today the 12.5.1.0 update and the issue is still here...

john_matrix said:
This is definitely not the same problem.
Our issue is about the Wifi that is not working at all, no wireless networks, no connection, phone constantly crashing when entering Wifi menu.
Also, there is an issue with GPS Localisation (maybe related to the wifi as the phone is using wifi to have more accurate result).
Have received again today the 12.5.1.0 update and the issue is still here...
Click to expand...
Click to collapse
Same here, but the static IP roundabout don't works

My Xiaomi T10 could not connect only to *some* wifi, it has been so since when I purchased it.
I tried different solution and never worked.
Only few days ago I updated to MIUI 12.5 and I tried the first method here (basically reset the wifi settings)
Xiaomi: How to Fix Wi-Fi Problem When Updating to MIUI 12 | ITIGIC
Many of Xiaomi's phones are still updating to MIUI 12. The company's new layer integrates a large number of novelties at the aesthetic and functional level. However, as often happens on many occasions, there are problems that only arise when these new versions reach thousands and thousands of...
itigic.com
and it worked!
give it a try, hope this helps, it bothered me for such a long time!

The latest MIUI update automatically fixed all my wi-fi/data woes. It's about time.

Hello,
Got a Mi11 and ran into wifi problems, fought a bit...
My problem was that wifi kept disconnecting, just like in the video above (from nepal). I had noticed that it did not with all access points (specifically with mine !).
Having had the same problem a while back with an oculus go, I did the same : forcing a static ip.
Didn't work with the Mi but I [desperately] set the dns to "plain google" (8.8.8.8 / 8.8.4.4) and wifi sticked !
Then I checked my ap settings and noticed that my ap advertised its global dns (eg 192.169.0.254) and not itself as the dns provider, corrected that on the phone, that is putting the router adress as dns 1, and it works reliably now.
Looks like if android doesn't get a specific ip or address positively upon connecting an access point, it drops it to connect to the next, wich sounds like a good idea...
Hope that helps some of you...

Hello,
Thanks for your advice but this solution cannot be applied here as the Wifi cannot start at all and when you try to look at it after trying to activate it, system panel hang and crash.
I have tried to dig a little bit to see where this problem can come from but haven't found anything yet.
I have check the /persist partition as there is no way to check the Wifi MAC Address with MIUI 12.5.1.0 but no, the partition is still fine (as everything is working properly with MIUI 12.0.5.0)
I have opened 3 tickets by using the Xiaomi official reporting tool but nothing yet... I guess they have abandonned the Mi 9 as MIUI 12.5.1.0 is considered the latest MIUI for this phone.
It would be good to find some Mi 9 users that have successfully installed MIUI 12.5.1.0 (the EEA version) on their phone.

Anyone have tried the recent 12.5.2.0(RFAEUXM) on their Mi9?
In order to know if the wifi bug is still there or not.
Thanks!

I have the Xiaomi M11 lite 5G NE with Miui 12.5, when I exit the house, my WiFi turns off automically, so when I get back I have to toggle WiFi to turn it on again. I have seen some Adroid Advanced settings and one of them is Turn Off Wifi automatically. This seems to be activated, but I can't undo that setting.
Anyone else have this problem where your WiFi is turned off automatically?

Latest available MIUI 12.5 (12.5.2.0) fix the Wifi issue.