Flakey Wifi

[Guest sonofveritas]

Like most other people I suspect, I dip in and out of my Vega throughout the day. When not in use I put it in sleep mode. I have tried backlight killer app to keep wifi active but using this drains the battery too much for the Vega to last a complete day, given the amount I use it.

My problem is that around 70-80% of the time when switching back on from sleep the wifi connection is not re-established. It seems to stick in 'getting IP address'. I have tried allocating a fixed IP address for the Vega but it still sticks at this point. The only solution seems to be to go into settings and disable and re-enable wifi.

This is really really annoying and is driving me mad. Do other people have the same problem & is there a solution I am missing here ?

Running on MoDaCo r8 rom & wifi signal very strong.

[Guest simonta]

Not ranting, but the developers of this forum software sure wasted their time on the search feature.

All flavours of Linux have a history of Wifi problems and the Vega is no different.

Use Wifi Static to use a static IP on the Vega.

Use Wifi Analyser to find a clean channel, signal strength is not enough, change your router to that channel.

Use Wifi Buddy, Settings->Advanced->Regulatory domain (from memory) to set the Vega to use 14 channels.

[Guest sonofveritas]

Not ranting, but the developers of this forum software sure wasted their time on the search feature.

All flavours of Linux have a history of Wifi problems and the Vega is no different.

Use Wifi Static to use a static IP on the Vega.

Use Wifi Analyser to find a clean channel, signal strength is not enough, change your router to that channel.

Use Wifi Buddy, Settings->Advanced->Regulatory domain (from memory) to set the Vega to use 14 channels.

I did search and I have tried all of the solutions listed above.

[Guest trevor432990]

Did you allocate the static IP on the router itself using router admin function, and what sort of router is it?

[Guest sonofveritas]

Did you allocate the static IP on the router itself using router admin function, and what sort of router is it?

Yep. Router is an EchoLife HG520b provided by TalkTalk.

[Guest simonta]

I did search and I have tried all of the solutions listed above.

Then I apologise, although that would have been useful to know in your OP :D

I'm guessing that you've tried this but have you removed the connection (long press then forget) and logged on again? Are you using WEP or WPA? I believe that some people have also had success with updating the router firmware.

Edited March 22, 2011 by simonta

[Guest trevor432990]

Yep. Router is an EchoLife HG520b provided by TalkTalk.

Which internal IP address did you give it and do you have many other devices using the wi-fi?

[Guest zzleezz]

I had similar problems but since installing one of Buzz's new kernels it seems to have disappeared.

You say you are running r8, how about the new kernel? Dont forget to nandroid before you start if you do try, Link

[Guest sonofveritas]

Then I apologise, although that would have been useful to know in your OP :D

I'm guessing that you've tried this but have you removed the connection (long press then forget) and logged on again? Are you using WEP or WPA? I believe that some people have also had success with updating the router firmware.

No problem. Yes have tried removing, etc. Firmware is up to date.

[Guest newbe5]

I had similar problems but since installing one of Buzz's new kernels it seems to have disappeared.

You say you are running r8, how about the new kernel? Dont forget to nandroid before you start if you do try, Link

+1 for this. The Buzz kernel is working perfectly for me and the WiFi is better than on other Kernels I have tried, it might just sort your problem.

[Guest sonofveritas]

Which internal IP address did you give it and do you have many other devices using the wi-fi?

192.168.1.4

This is the only device using wifi, got another two that use homeplugs.

[Guest sonofveritas]

+1 for this. The Buzz kernel is working perfectly for me and the WiFi is better than on other Kernels I have tried, it might just sort your problem.

ok thanks will try this if other solutions fail, would need to install clockwork recovery etc.

Strangely, I have just changed to a channel that shows as slightly weaker according to wifi analyser and it seems to be working better. Will play with it for a while and see if it continues to be better.

[Guest trevor432990]

192.168.1.4

This is the only device using wifi, got another two that use homeplugs.

My router states internal IP addresses should be in the range 192.168.0.2 and 192.168.0.254 so it might be worth you changing it to 192.168.0.4 and see if it makes any difference.

EDIT:- Just checked your router documentation and it seems they do start from 192.168.1.xx so rather than 192.168.0.4 that I suggested try 192.168.1.200 as it's far enough down the range not to conflict with anything else. You say it's the only device using wi-fi but do you have any games consoles, mobile phones as well which use wi-fi too?

Edited March 22, 2011 by trevor432990

[Guest sonofveritas]

My router states internal IP addresses should be in the range 192.168.0.2 and 192.168.0.254 so it might be worth you changing it to 192.168.0.4 and see if it makes any difference.

Ok thanks, will try that.

[Guest Dav0]

would echo Simon's fixes they generally worked for me

interested in buzz kernel though, I see it includes new WiFi driver, is there any way to get this without installing the whole kernel?

it would appear this could make a big difference

as an aside I can understand ppls frustration about posters searching, however there is a lot of different advice spread over different ROM's and it is confusing to know what works

the mcr's seem to act differently for different Vega and setups, I also suspect there are a lot of Windows user's not used to android?

[Guest sonofveritas]

My router states internal IP addresses should be in the range 192.168.0.2 and 192.168.0.254 so it might be worth you changing it to 192.168.0.4 and see if it makes any difference.

EDIT:- Just checked your router documentation and it seems they do start from 192.168.1.xx so rather than 192.168.0.4 that I suggested try 192.168.1.200 as it's far enough down the range not to conflict with anything else. You say it's the only device using wi-fi but do you have any games consoles, mobile phones as well which use wi-fi too?

Changing the channel has worked, it reconnects every time now. Strange really because I hadn't used this channel before because wifi analyser recommended different channels.

I am able to see some neighbours wifi hotspots and even checked that I wasn't using the same channel as them.

Anyway, working well now, thanks to everyone for their input.

[Guest sonofveritas]

+1 for this. The Buzz kernel is working perfectly for me and the WiFi is better than on other Kernels I have tried, it might just sort your problem.

working well now thanks, changing wifi channel sorted it.

BTW like the vids re Vega/iPad. Notice in one that you say it takes about 10 secs to connect to wifi, mine only takes a couple of seconds, if that. Suggest you try allocating a fixed IP address to see if that helps.