[Q] Wifi Not Working On Cyanogenmod 11 - T98… | T-Mobile Samsung Galaxy S II SGH-T989

19th December 2013, 05:08 PM | #1

OP Junior Member

Thanks Meter: 0

2 posts

Join Date:Joined: Dec 2013

I was able to install CM11. Flashed cm11 on 12/7 and everything has been working great. I was able to update everything. On next morning, wifi signal was there but no access to internet. Wifi is on but it picks up no wifi signals. If I turn on/ off wifi doesn't find anything else. And receive WPS has failed error... if I click in refresh.
I have already daily upgrade nightly builds to up to date build (20131217), but success. same issue. Any idea?
If I do a full wipe and then restore a backup it work for a day, then stops again.

15th January 2014, 11:20 AM | #2

Member

Thanks Meter: 11

45 posts

Join Date:Joined: Feb 2013

I have the same problem. I dropped the phone on the wooden floor, and thought the wifi just broke, but now I'm confident it's because of bugs in cm11
Considering returning to cm10.3

LE:
Installed BeanStalk with no data/cache wipe and WiFi is still not working.

Last edited by adrscu; 15th January 2014 at 12:06 PM.

15th January 2014, 01:45 PM | #3

Junior Member

Thanks Meter: 0

1 posts

Join Date:Joined: Jun 2011

Quote:

Originally Posted by gust989

I updated mine to 1/14/2014 CM11 Nightly and still no Wifi. Anyone have the same experience?

19th January 2014, 01:36 AM | #4

Member

Thanks Meter: 8

31 posts

Join Date:Joined: Jan 2014

I had the same problem. You can try wiping all data, reinstalling ROM and gapps. Everything but the camcorder works!

Sent from my SAMSUNG-SGH-T989 using xda app-developers app

17th February 2014, 06:36 AM | #5

Junior Member

Thanks Meter: 4

1 posts

Join Date:Joined: Feb 2014

it solved !!!! ...

Hi to all
I had this problem and i could fix it.
afret install CM 11, go to this address : settings/wi-fi/advanced/wi-fi region code
and change it to fix. for me it works on Europe.
I hope it be useful.

If it works for you, give me Thanks ...

Last edited by SAHRSOFT; 17th February 2014 at 06:44 AM.

The Following 4 Users Say Thank You to SAHRSOFT For This Useful Post: [ View ]

17th February 2014, 06:55 PM | #6

Member

Thanks Meter: 11

45 posts

Join Date:Joined: Feb 2013

Will try as we speak. Thanks for sharing.

---------- Post added at 08:55 PM ---------- Previous post was at 08:13 PM ----------

I just upgraded to cm 11 build .17 and Wifi just doesnt turn on.
It says turning on... and just hangs.
I've set region to Europe to no avail..

17th February 2014, 08:18 PM | #7

Member

Thanks Meter: 11

45 posts

Join Date:Joined: Feb 2013

I found a solution. Download SQlite debugger from Play Store. Open the app, then open Setting Storage, then setttings.db, then Global, then scroll down to wifi_display_on and edit the value, change it to 0. Reboot and then you should have wifi working again.

The Following User Says Thank You to adrscu For This Useful Post: [ View ]

29th May 2014, 04:49 PM | #8

Junior Member

Thanks Meter: 0

1 posts

Join Date:Joined: May 2014

value

Quote:

Originally Posted by adrscu

Thanks, that worked great. but the setting reverted back to "1" on its own

, i changed it back to "0" working again but any idea how to keep it from reverting back?

The value only reverted the one time, hasn't been an issue again.

Last edited by Rydermuff; 1st June 2014 at 06:46 PM. Reason: issue hasn't continued

4th June 2014, 09:45 AM | #9

Junior Member

Thanks Meter: 0

6 posts

Join Date:Joined: Jan 2013

Samsung Galaxy S Advance - Cyanogenmod 11 wifi connection problem

Quote:

Originally Posted by adrscu

Downloaded SQlite debugger. Cannot find Setting Storage. Please help.

25th July 2014, 11:33 PM | #10

Member

Thanks Meter: 12

69 posts

Join Date:Joined: Nov 2011

Quote:

Originally Posted by adrscu

I found a solution. Download SQlite debugger from Play Store. Open the app, then open Setting Storage, then setttings.db, then Global, then scroll down to wifi_display_on and edit the value, change it to 1. Reboot and then you should have wifi working again.

This totally worked for me. But it stops, and the problem is back again. Checking the settings.db shows it has returned to 0. (wtf!)

Not sure what to do at this point. It's nice to know it's not hardware.