Wifi Sleep Issue

September 28, 2010

Hi everyone.

I'm new on this forum. I'm experiencing a very strange problem. When I install a stock T-mobile ROM based on Android 1.5 Wifi works perfectly on my Pulse even when screen goes off. But If I install any other custom ROM or T-Mobile official 2.1 ROM wifi connection disconnects when screen goes off. I've changed the wifi settings to stay awake all the time (wifi sleep set to Never) but it doesn't change anything. FLB ROM is running perfectly on mu Pulse but this wifi issue is irritating me. Has anybody else noticed this problem?

September 28, 2010

Hi everyone.

I'm new on this forum. I'm experiencing a very strange problem. When I install a stock T-mobile ROM based on Android 1.5 Wifi works perfectly on my Pulse even when screen goes off. But If I install any other custom ROM or T-Mobile official 2.1 ROM wifi connection disconnects when screen goes off. I've changed the wifi settings to stay awake all the time (wifi sleep set to Never) but it doesn't change anything. FLB ROM is running perfectly on mu Pulse but this wifi issue is irritating me. Has anybody else noticed this problem?

When you set-up the Wifi sleep settings you have to press "menu" then "save" :lol:

That had me confused for a while

September 28, 2010

When you set-up the Wifi sleep settings you have to press "menu" then "save" :lol:
That had me confused for a while

Thanks for your help. I really didn't notice it. I'm now going to upgrade the ROM again to T-Mobile Official 2.1 and then FLB 1.6. Should I go through the whole process or I can check the above trick at first level i.e. T-Mobile Official 2.1.

But I'm wondering why it worked with 1.5 without even changing the settings at all. I think sleep settings don't trigger when screen goes off. Sleep triggers when there's no data transmission.

Another thing which is very peculiar to me is how come the system can save battery going into sleep mode. Because when wifi sleep triggers it opens connection to 3G or Edge etc and everybody know it consumes more battery as compared to wifi.

EDIT : After upgrading to T-Mobile Official 2.1. I changed wifi sleep policy and saved it. The result is as follows

When screen is on.

Pinging 192.168.1.64 with 32 bytes of data:

Reply from 192.168.1.64: bytes=32 time=256ms TTL=64

Reply from 192.168.1.64: bytes=32 time=64ms TTL=64

Reply from 192.168.1.64: bytes=32 time=92ms TTL=64

Reply from 192.168.1.64: bytes=32 time=9ms TTL=64

Ping statistics for 192.168.1.64:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 9ms, Maximum = 256ms, Average = 105ms

Pinging 192.168.1.64 with 32 bytes of data:

Reply from 192.168.1.64: bytes=32 time=63ms TTL=64

Reply from 192.168.1.64: bytes=32 time=2ms TTL=64 At this point I turned the screen off by tapping the power button.

Request timed out.

Ping statistics for 192.168.1.64:

Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

Approximate round trip times in milli-seconds:

Minimum = 2ms, Maximum = 63ms, Average = 32ms

Pinging 192.168.1.64 with 32 bytes of data:

Request timed out.

Reply from 192.168.1.64: bytes=32 time=31ms TTL=64

Reply from 192.168.1.64: bytes=32 time=37ms TTL=64

Ping statistics for 192.168.1.64:

Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

Approximate round trip times in milli-seconds:

Minimum = 31ms, Maximum = 37ms, Average = 34ms

Pinging 192.168.1.64 with 32 bytes of data:

Request timed out.

Reply from 192.168.1.70: Destination host unreachable.

Ping statistics for 192.168.1.64:

Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

Pinging 192.168.1.64 with 32 bytes of data:

Reply from 192.168.1.70: Destination host unreachable.

Ping statistics for 192.168.1.64:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

Edited September 28, 2010 by Android.Fan

September 28, 2010

Anybody else to share their experience about this issue? Please let me know if your pulse devices' wifi are working fine when screen is off.

September 28, 2010

You made me have to test it B)

So, after running a few tests wifi stays on but as you say is unreachable when the screen is off UNLESS:

The pulse itself is using the WIFI connection

When the pulse was downloading an app, refreshing a web page and performing a speed test I got ping results until it finished. So the pulse will use it's WIFI connection (when the wifi sleep policy is changed ofc) as and when it needs to.

Hope this clears things up :lol:

September 28, 2010

You made me have to test it B)
So, after running a few tests wifi stays on but as you say is unreachable when the screen is off UNLESS:
The pulse itself is using the WIFI connection

When the pulse was downloading an app, refreshing a web page and performing a speed test I got ping results until it finished. So the pulse will use it's WIFI connection (when the wifi sleep policy is changed ofc) as and when it needs to.

Hope this clears things up :lol:

Thanks again for being with me. I think this is not the case. I've some following points

1- Pulse behaves differently when running on Original Android 1.5. You always get ping responses no matter screen is off/on and/or if phone is downloading something or not. (This is desired behaviour)

2- On Official T-Mobile 2.1 or any other custom ROM based on 2.1 this behaviour changes as mentioned above EVEN I've changed sleep policy to Never which means wifi should never sleep. (I also tested after saving it as you suggested before)

3- If you are running any application which uses internet connection continuously it will stop responding when screen goes off. you can check it by installing Fring or SIPDroid. You wouldn't get Fring messages or calls. Even email notifications or Google Talk msgs are not delivered and/or notified.

4- With SIPDroid it has a very funny behaviour with screen off. When I call my SIPDroid number it doesn't ring and on the calling side i don't hear any ringing tone. Then I hang up and tap my Pulse's power button to wake it up and SIPDroid starts ringing. Although the caller had already hanged up.

Is there any difference between 1.5 kernal and 2.1 kernal or wifi drivers? Can't we biuld a custom ROM with files (Regarding Wifi) used in 1.5?

Chears

September 28, 2010

Good to see someone else is seeing the same thing I've always seen. I can confirm that via ping returns, the Pulse disappears the moment the screen goes off. More than that however, when the phone is turned on again it often cannot remake connection via the wifi to the net. It will state that wifi is active, but no connection is found if you try to use it. If you use something like Wifi Analyser you will see the AP that surround you, but no sign of your AP at all.

The only solution to this I've found is to turn off wifi, wait a while, then turn back on again. It doesn't always work, even then.

However, this behaviour is not always seen. Sometimes the phone will sleep, and then when woken it will reconnect properly and work fine. It seems to be something to do with the state the phone was in when the sleep kicked in, and I think maybe the degree of interference on the channel used.

It's a bleedin' nuisance.

BTW I'm using the Tomato firmware on a Linksys router.

September 29, 2010

OK, been doing a little digging around. See http://www.google.com/support/forum/p/andr...3a2fb&hl=en and in particular the last posting. Describes it perfectly and various approaches to kludged fixes. Seems like this is a driver issue.

Paging flibblesan, is there anything you can do? This comment from elsewhere might help:

It's basically an issue in the broadcomm driver.
Install CyanogenMod RC3 or a nightly build and your problems will be gone:
http://forum.cyanogenmod.com/forum/36-goog...perimental-mod/

Edited September 29, 2010 by sane?

September 29, 2010

To me just Nimbuzz can receive call after Screen go to sleep any other apps is not receiving the call.

Part from discussion on http://code.google.com/p/android/issues/detail?id=9781.

@Bond711

I've been talking to a few people on XDA-Developers about integrating the fix into Desire ROMs based on CyanogenMod (it's apparently really simple - yesterday a guy rewrote my bcm2439.ko module within like half an hour... all I had to do was replace the file via ADB in recovery and voila, CAM), but it seems like they actually WANT the WiFi to enter PSP mode when the screen is off.

Apparently it's not a bug, it's a feature.

So far I can confirm that power usage is higher: ~8mA idle vs. ~5mA in PSP mode. Translates to 175h of standby time instead of 250h...

However, since I use my phone as an actual smartphone and not just as a telephone, I need to be able to access the FTP and Wireless ADB servers while the screen is off... not to mention VoIP. SipDroid works fine with the screen off now, btw.

What we really need is a toggle switch for PSP vs. CAM in the Advanced Wireless Settings menu...

September 29, 2010

OK, been doing a little digging around. See http://www.google.com/support/forum/p/andr...3a2fb&hl=en and in particular the last posting. Describes it perfectly and various approaches to kludged fixes. Seems like this is a driver issue.

Paging flibblesan, is there anything you can do? This comment from elsewhere might help:

We don't use the broadcom driver (we have atheros hardware), so that fix won't help you.

September 29, 2010

Maybe this app can help - Wi Fi Keep Alive from the market.

Can't test now, I am on holiday and don't have wi-fi here.

September 29, 2010

Thanks a lot to all people sharing their experiences. I was wondering why people're not facing this problem. I thought may be there was something wrong with phone itself.

Now I'm feeling that this is a common problem but I don't know why people are not bothering.

As I mentioned earlier it works fine with original 1.5 ROM. Anybody with original 1.5 ROM give it try?

Is there anyway to use wifi related drivers and files in latest custom ROMs, used in 1.5?

Anybody who build Custom ROMs can have a look at it and try to fix it?

I love this device. I don't want to run it on 1.5 because that's crap. FLB is the best so far. If this problem is fixed I'll use this device for a long time otherwise I'll have to look for another device.

@Sane?

It reconnects automatically to Wifi when screen goes on but you need to give it some time. It can take up to 1minute to connect to wifi.

September 29, 2010

Anybody else facing the same issue?.

Please leave a post about your Pulse Wifi experience. It'll help to know how many people have the same problem then we can ask developers to fix it if they can.

Anybody with FLB Mod or any other Custom ROM based on 2.1 have their Pulse Wifi working perfectly in both modes (Screen ON and OFF)?

Stepts to check it are very simple.

1- Connect your Pulse to Wifi

2- Check the IP address assigned to your Pulse.

3- Ping that IP address from your Computer/Laptop (connected to the same Router) with your Pulse's Screen ON and then OFF.

Chears

September 29, 2010

Anybody else facing the same issue?.

Please leave a post about your Pulse Wifi experience. It'll help to know how many people have the same problem then we can ask developers to fix it if they can.

Anybody with FLB Mod or any other Custom ROM based on 2.1 have their Pulse Wifi working perfectly in both modes (Screen ON and OFF)?

Stepts to check it are very simple.

1- Connect your Pulse to Wifi
2- Check the IP address assigned to your Pulse.
3- Ping that IP address from your Computer/Laptop (connected to the same Router) with your Pulse's Screen ON and then OFF.

Chears

I tried a few times with froyo, results are:

Screen on, not connected to charger - 0% packet loss

Screen off, not connected to charger - 100% packet loss

Screen on, connected to charger - 0% packet loss

Screen off, connected to charger - 0% packet loss

So the packets only get lost when the screen is off and the charger is not connected.

Wifi is set to always on in the settings.

Sh4d0w940

September 29, 2010

@Sane?
It reconnects automatically to Wifi when screen goes on but you need to give it some time. It can take up to 1minute to connect to wifi.

If you read the first link I gave you'll see that appearing to still be connected on wake up, but actually not being and having to be cycled before it can reconnect; is one of the forms of bug that's been seen. They all seem to stem from the same basis, which is a fault (feature) of the driver code. This is fixed in Froyo v2.2.1 by Google, and also in CyanogenMod RC3 - which means the source for that fix should be available, even if chip-side code is different.

Wifi Keep Alive doesn't appear to fix it, but Wifi Fixer does. However it does this by killing the battery life and causing some other issues which means I've uninstalled it again.

Anyway, in short, it's been documented to hell and back and is a common feature of all codebases it seems. The only final fix is modification and recompilation of the driver code.

September 30, 2010

Anyway, in short, it's been documented to hell and back and is a common feature of all codebases it seems. The only final fix is modification and recompilation of the driver code.

I think it is true for codebases after android 1.5. I don't know if 1.6 or 2.0 was available for Pulse. I think everybody got 2.1 after 1.5. But 1.5 is running wifi perfectly even when screen is OFF.

My question is if it is possible to use wifi related files and drivers, used in 1.5, in 2.1?

I'll request Custom ROM builders to suggest if they can do so.

September 30, 2010

Anyway, in short, it's been documented to hell and back and is a common feature of all codebases it seems. The only final fix is modification and recompilation of the driver code.
I think it is true for codebases after android 1.5. I don't know if 1.6 or 2.0 was available for Pulse. I think everybody got 2.1 after 1.5. But 1.5 is running wifi perfectly even when screen is OFF.

My question is if it is possible to use wifi related files and drivers, used in 1.5, in 2.1?

I'll request Custom ROM builders to suggest if they can do so.

I'm not sure the 1.5 ROM was any better.

I'd suggest a better route would be to take the 2.2.1 version of the driver source code and the 2.2.0 and find the differences. Those changes could then be implemented in the driver code for the pulse. Also the CyanogenMod route offers an alternative.

All of which pre-supposes that the source for the driver code is available.

September 30, 2010

I'm not sure the 1.5 ROM was any better.

I 101% agree with you that is why I didn't like it and moved on to 2.1. I actually wanted to say to build a ROM based on 2.1 but taking wifi related things from 1.5. I don't know if this is a correct way to put it.

I'd suggest a better route would be to take the 2.2.1 version of the driver source code and the 2.2.0 and find the differences. Those changes could then be implemented in the driver code for the pulse. Also the CyanogenMod route offers an alternative.

Have you installed cyanogen MOD on Pulse? I've not seen anywhere cyanogen mod build for Pulse. Have you installed and tested it yourself? Any issues, bugs errors?

September 30, 2010

I 101% agree with you that is why I didn't like it and moved on to 2.1. I actually wanted to say to build a ROM based on 2.1 but taking wifi related things from 1.5. I don't know if this is a correct way to put it.
Have you installed cyanogen MOD on Pulse? I've not seen anywhere cyanogen mod build for Pulse. Have you installed and tested it yourself? Any issues, bugs errors?

You could also try to install an newer version of 1.5 and then flash an custom 2.1 or 2.2 rom over it.

The wifi drivers don't change with custom roms afaik only with update's from huwaei.

Sh4d0w940

September 30, 2010

Just to highlight, for those that haven't realised, but the wifi sleep situation can be improved by setting a static IP address. It's not a fix, but reducing the work needed to stay properly connected helps reduce the incidence of the problem (YMMV).

October 6, 2010

I was thinking of abandoning Pulse and buy Orange SF but I've noticed the same problem with it as well.

The main thing irritating me is none had complained about it on this forum. I don't know how people use android devices or how people expect these devices to work.

If they're using it as a normal mobile phone device there're very low cost solutions available or may be they use it to show off they got a very advanced device.

For me Mobile phone is a real communication station where a number of things are running related to SIP, Skype, Fring etc in parallel. So I need a continuous connection to Internet preferably through Wifi and alternatively through 3G.

I'd been using Nokia E-Series devices and they worked perfectly for communication. They never drop wifi connection when screen goes off and jump to 3G when wifi is not available.

Is there any fix expected in the near future regarding this problem?

October 11, 2010

I think I found solution.

The problem was in adsl modem. When I changed WPA-PSK Version to WPA2 and changed password wifi on my phone started to work :-) finally.

October 12, 2010

I think I found solution.
The problem was in adsl modem. When I changed WPA-PSK Version to WPA2 and changed password wifi on my phone started to work :-) finally.

:-(

Wake up, turn on the phone and the problem started again.It seams it has to do something with ADSL modem settings and Pulse setting.

Yesterday everything was working fine for 1 hour.

Sign In

Wifi Sleep Issue

Recommended Posts

Guest Android.Fan

Guest Azurren

Guest Android.Fan

Guest Android.Fan

Guest Azurren

Guest Android.Fan

Guest sane?

Guest sane?

Guest harrise

Guest Tom G

Guest harrise

Guest Android.Fan

Guest Android.Fan

Guest Sh4d0w940

Guest sane?

Guest Android.Fan

Guest sane?

Guest Android.Fan

Guest Sh4d0w940

Guest sane?

Guest Android.Fan

Guest harrise

Guest harrise

Please sign in to comment

Browse

Activity

Important Information