Possible fix for wifi cm11

Prashanth Meesara:

Senior Member
Jan 15, 2013
608
262
0
Bellary
Please note this method worked for me it may or may not work on all devices

ive seen many people reporting that it gets stuck obtaining ip address so here is the solution for that

Don't kill me if it does not work

Here are the steps

long press the wifi connection and select modify network (if its password protected select forget and try)

check the Show advanced options

in the IP address field type the ip address of your network (for example my ip address is 192.168.0.1)

now connect it ... it shows connected (don't be too happy) but you cant browse internet

now again long press on the wifi network and select modify network and now remove the ip and select the DHCP and save

turn off and turn on wifi

it will automatically connect to the network

if still not connected delete the files in data/misc/wifi folder reboot device and try again

additionally try connecting using and apps like wifi fixer etc

hope so it works for all


thanks
 

prassi

New member
Sep 29, 2014
1
0
0
Tried But not working

on CM11 nightly build 5, I cant connect to connectify but it worked with stock ROM. It shows "obtaining ip address" and hangs there.. not getting connected.

MOTO E with CM11
 

Prashanth Meesara:

Senior Member
Jan 15, 2013
608
262
0
Bellary
on CM11 nightly build 5, I cant connect to connectify but it worked with stock ROM. It shows "obtaining ip address" and hangs there.. not getting connected.

MOTO E with CM11
Did you follow the above steps if yes then sorry I can't help you it worked perfectly for me

Sent from my XT1022 using XDA Free mobile app
 
P

pfoltyn

Guest
on CM11 nightly build 5, I cant connect to connectify but it worked with stock ROM. It shows "obtaining ip address" and hangs there.. not getting connected.

MOTO E with CM11
Have the same problem on Motorola Moto G 4G XT1039. Just flashed cm-11-20140929-NIGHTLY-peregrine.zip build and my WiFi is dead. It connects but then stays in "Obtaining IP address" forever. I've followed all the "fixing suggestions" mentioned in this thread but the problem persists. Any more ideas?