Possible to keep wifi on while Vega in standby?

[Guest Pyr0x64]

you can probably find the settings to enter in your router screens

my dlink router shows me the primary and secondary dns server IPs

the router IP is your gateway IP

netmask is just 255.255.255.0

[Guest removed-14]

you can probably find the settings to enter in your router screens

my dlink router shows me the primary and secondary dns server IPs

the router IP is your gateway IP

netmask is just 255.255.255.0

He also needs to make sure he doesn't use an ip from the dhcp scope otherwise it may cause a conflict.

[Guest obb]

He also needs to make sure he doesn't use an ip from the dhcp scope otherwise it may cause a conflict.

Well yeah that was a given really ... ;)

[Guest removed-14]

Well yeah that was a given really ... ;)

A given to you but someone who doesn't know what to put in the input fields it isn't a given.

[Guest QLF]

Not a bad Idea - but I take mine between a few houses and have all their wi-fi's set-up and logged - unfortunately static wouldnt work in my scenario!

You SHOULD be able to specify a static IP address per WiFi connection. Unsure of how this works on Android, but certainly on laptops and computers this is easy enough.

Hopefully someone else will be able to advise on a step by step.....

*EDIT* Maybe try this http://www.androlib.com/android.applicatio...tatic-znDq.aspx

This replicates the functionality you would see in windows. Unsure of compatibility though, as yet to receive my Vega. Older posts from 2009 state there is no native ability to do this, however I would really hope that 2.2 or 2.3 brings this ability. Pretty damned simple i would thought!

Edited December 7, 2010 by QLF

[Guest warriorscot]

It would be easier to just assign a specific IP to the Vega on the router end. Most routers worth their salt can assign specific IP addresses to specific devices sometimes its as easy as a couple of click and on older or poorly featured routers you can manually enter the MAC address and assign an IP to it.

[Guest removed-14]

It would be easier to just assign a specific IP to the Vega on the router end. Most routers worth their salt can assign specific IP addresses to specific devices sometimes its as easy as a couple of click and on older or poorly featured routers you can manually enter the MAC address and assign an IP to it.

DHCP reservation. But the point of the static IP is to try and stop the request from the Vega for an IP. All the reservation does is makes sure the router gives out the same IP each time. If you assign a static IP to the device then no request is made speeding up the process of reconnecting. I'm not sure how much quicker it is but one thing to be wary of is that if you use multiple places and access points for your net access you will need to keep either changing the IP or changing it back to dynamic each time you use another access point.

[Guest obb]

DHCP reservation. But the point of the static IP is to try and stop the request from the Vega for an IP. All the reservation does is makes sure the router gives out the same IP each time. If you assign a static IP to the device then no request is made speeding up the process of reconnecting. I'm not sure how much quicker it is but one thing to be wary of is that if you use multiple places and access points for your net access you will need to keep either changing the IP or changing it back to dynamic each time you use another access point.

That was my point about the subnets on routers though .. most default to one or the other, so 50% chance most of the time

[Guest removed-14]

That was my point about the subnets on routers though .. most default to one or the other, so 50% chance most of the time

That is most likely the case but other pitfalls include picking an IP address that conflicts with something else on your network. Between the wife and I, we have:

* PS3

* PSP

* 2 x laptops

* Advent Vega

* HTC Desire

* Wii

* HTC Tattoo

* Router

Plus my friends and family have my WPA passkey so they hop onto my network when they visit! Best to let DHCP do it's job rather than trying to save a few seconds and possibly causing a problem that someone who lacks networking knowledge will struggle to track down. ;)

I'm hoping it can be fixed in a firmware update but I don't want to become one of those people who have a problem and instantly think it can be fixed in a patch or firmware update! Lol

[Guest warriorscot]

To be honest it doesn't take my Vega long to acquire and IP and if its reserved on the router it does take slightly less time and problems. Once I started doing it all my network devices connected faster with fewer issues. If you set a static IP on the device you usually have to reserve the same address for the device on the router anyway I just think setting a static IP is overkill and not worth the other problems it would cause.

[Guest morchuboo]

I asked my brother - he works for creative labs writing drivers for their android devices - apparently the ability to keep WIFI on during suspend is often a hardware decision.

To enable the WIFI to stay on they would need to link the WIFI chip to the 5v rail. Some manufactures do this some dont.

It saves a little bit of the cost to not do it so I imagine it has not been done on a device that is priced this competitively.

Also the reason it take 5-10 seconds to bring the WIFI back up, while maybe a second could be due to a DHCP renew, it is mostly down to the fact that the WIFI chip likely does not have ROM for its firmware.

When the devices wakes up it has to do a software upload of the firmware each time to the WIFI chip and then bring up the network stack.

Looks like setting a static IP will be of limited use - especially when considering the constraints it adds to roaming.

[Guest dukla2000]

Being an Android newb took a while to work out the implications of this problem, but in a nutshell if I set my screen to 1 minute then can leave the Vega playing music happily, even after the screen dies. However if I leave the radio (TuneIn Radio) on then it dies shortly after the screen cause the wifi goes down as well. Which is a PITA!

The speed of wifi re-connect is neither here nor there (IMHO) - then again in my case it seems to be 2 or 3 seconds sometimes, less than 10 most times.

The real issue is that screen timeout and wifi timeout should be independent from each other!

[Guest jasonic8]

That is most likely the case but other pitfalls include picking an IP address that conflicts with something else on your network.....

.....Plus my friends and family have my WPA passkey so they hop onto my network when they visit! Best to let DHCP do it's job rather than trying to save a few seconds and possibly causing a problem that someone who lacks networking knowledge will struggle to track down. :)

A lot of routers allow you to specify the range for DHCP, so you could start it at 192.168.0.10 and use 192.168.0.2-9 for static IPs (assuming your router takes 192.168.0.1). Your visiting devices and any others that aren't static will be assigned numbers greater than 10, so no conflict will occur.

Edited December 11, 2010 by jasonic8

[Guest removed-14]

A lot of routers allow you to specify the range for DHCP, so you could start it at 192.168.0.10 and use 192.168.0.2-9 for static IPs (assuming your router takes 192.168.0.1). Your visiting devices and any others that aren't static will be assigned numbers greater than 10, so no conflict will occur.

Thanks for that but if you'd have read the whole thread you would have seen i was advising someone who knows little or nothing about ip not to put in a static ip due to the possible conflicts with a dhcp server scope. As an mcp for windows server im fully aware of how dhcp works :)

[Guest obb]

As an mcp for windows server im fully aware of how dhcp works :)

That don't mean Jack these days mate. I've been in IT for 15 years and have every major accreditation under the sun. Doesn't mean I know what I'm talking about! :)

In the end a static IP at the back end of the range SHOULD be safe (240 to 250) .. 99% of the time.

[Guest removed-14]

That don't mean Jack these days mate. I've been in IT for 15 years and have every major accreditation under the sun. Doesn't mean I know what I'm talking about! :)

In the end a static IP at the back end of the range SHOULD be safe (240 to 250) .. 99% of the time.

I know but it often shuts people up! Lol :)

In summary my message is basically if you don't know what you are doing then best leave it alone.

[Guest arad85]

In the end a static IP at the back end of the range SHOULD be safe (240 to 250) .. 99% of the time.

Unless that's where you point your routers DMZ to... :)

[Guest obb]

Unless that's where you point your routers DMZ to... :)

Why would you do that?

[Guest removed-14]

Why would you do that?

I've noticed some out of the box similar to that.

[Guest arad85]

Why would you do that?

So that if any port is open that you don't know is open, it will get redirected to nothing...

[Guest jasonic8]

Tonyyeb, i had read the thread thanks and was just trying to help with the setup you described you had. Sorry if you felt it wasn't useful for you or for anyone else.

[Guest removed-14]

Tonyyeb, i had read the thread thanks and was just trying to help with the setup you described you had. Sorry if you felt it wasn't useful for you or for anyone else.

Yeah I know but I was only using my setup as an example of how a dhcp pool can soon fill with lots of wireless enabled devices in the home these days. By picking just an ip could cause issues should it be too close to existing ips. As obb says one towards the far end of the range/scope should be ok in 99% of cases, but my point was that if someone who has very little idea about these things hits that 1% it will be a nightmare to unpick for them. Just slapping in a static ip isn't a sound suggestion for a novice of which that same novice isn't comfortable with changing their router configuration.

[Guest AndyCr15]

The speed of wifi re-connect is neither here nor there (IMHO) - then again in my case it seems to be 2 or 3 seconds sometimes, less than 10 most times.

The real issue is that screen timeout and wifi timeout should be independent from each other!

I totally agree. This is a pretty big downer for an Android device I would say...

[Guest espariz]

I totally agree. This is a pretty big downer for an Android device I would say...

Hello all, I have a Mobii Tegra with advent vega firm 1.65 and Addons from Paul (thanks!!), and prior, with the Mobii firmware, the Wifi works with screen off, and now with the advent/Paul firm does not work. I tried some programs to put off the screen but instantly shoot down the Wifi too...

I think (because Wifi works with Mobii firm at screen off), that this can be a "software issue"? and can be fixed by Paul in next addons?, the same that he do with the Host/Slave USB question, can this be true?

Thanks for all your work, my Mobii tegra now works great!!!!

(sorry for my poor english)

Edited January 2, 2011 by espariz

[Guest MECX]

Paul can you comment on this, seems to be a showstopper to many people.....

Thanks :unsure: B)