New WiFi bug

[Vexelius]

Greetings.

Yesterday, I had a strange problem with my Xiaomi: Out of the blue, websites stopped loading. Facebook and Twitter apps stopped updating. It seemed like my Internet connection had a problem, but every other device worked properly.

The Wireless icon was normal. The Network Details marked it as "Connected", with full signal strength. However, I had no Internet connection.

After a few tries, an app named WiFix helped me solve the issue.

However, today, the problem happened again, and this time, no app helped me. I even tried re-installing the ROM (WIUI-3.9.27) and it persists.

Help, please?

Phone: Xiaomi MI 2S. Bought 3 days ago.

 

[Vexelius]

More fixes that I have tried (to no avail).

-Wipe Cache/User Data/All Data
-Turn off the phone, take battery out
-Take SIM Card out
-Use another ROM: MIUIEs 3.9.27 (Spanish Port of MIUI)

 

[boojay]

Vex, try downloading/downgrading to WIUI 3.2.22 final version and see if that works for you. It's available in the WIUI thread we're participating in, first post.

Swyped from my Mi 2

 

[Vexelius]

Vex, try downloading/downgrading to WIUI 3.2.22 final version and see if that works for you. It's available in the WIUI thread we're participating in, first post.

Swyped from my Mi 2

Thanks for the suggestion. Downloading right now. However, I must first do some research on what "True Dual Boot" is, or how to use the Downgrade safely. Don't want to brick my phone...

 

[boojay]

Thanks for the suggestion. Downloading right now. However, I must first do some research on what "True Dual Boot" is, or how to use the Downgrade safely. Don't want to brick my phone...

Yup, always a prudent move to do your own due diligence.

TDB takes advantage of the fact that our phones are capable of booting from System 1 or System 2. With TDB disabled (default setting), both systems share all apps and data, which can cause conflict if you have different roms installed on either partition and try to load the other system.

With TDB enabled (from advanced settings in recovery), you can "truly" have a dual booting system where completely different roms can be installed and be run independently of each other without affecting the other one. The catch is, you'll have to install all apps/data separately so this uses up your internal storage twice as fast.

Beware, enabling and disabling TDB will wipe your data.

Swyped from my Mi 2

 

[Vexelius]

I have just finished installing ClockWorkMod Recovery, enabled TDB and installed WIUI 3.2.22 - Problem persists.

 

[qbert456]

I still get the Wifi problem months after it was first mentioned. Wifi fix app helps but still can't always fix it.
Its starting to make me possibly not get a xiaomi next time... Shame but it is soooo annoying!

 

[boojay]

I have just finished installing ClockWorkMod Recovery, enabled TDB and installed WIUI 3.2.22 - Problem persists.

Damn. That was going to be my last resort. Sorry man, I don't know what to tell you. I guess the search continues.

Swyped from my Mi 2

 

[Vexelius]

Tonight, I was very tired, and was unable to post something interesting: As for now, I have managed to get the WiFi working again by following these steps.

1) In ClockWorkMod Recovery, Enable TDB.
2) Immediately after the process ends, Disable TDB.
3) Install the newest WIUI using "Install update from sdcard"

After that, the phone restarted and it's still working... I'll report if something else happens.

By the way, any experts around here who can suggest me the best combination of OS for System 1 and System 2?

 

[Vexelius]

How can I make this message reach a developer? I have just found something truly interesting. The problem started again, just a few minutes ago. I checked everything back again, and just out of curiosity, looked at my router's logs. The following corresponds with the exact moment my WiFi stopped working...

Oct 11 16:39:58    DHCP: Server receive RELEASE from a4:c0:e1:6e:65:06.
Oct 11 16:39:43    DHCP: Server sending ACK to 192.168.2.103. (Lease time = 86400)
Oct 11 16:39:43    DHCP: Server receive REQUEST from a4:c0:e1:6e:65:06.
Oct 11 16:39:43    DHCP: Server sending ACK to 192.168.2.103. (Lease time = 86400)
Oct 11 16:39:43    DHCP: Server receive REQUEST from a4:c0:e1:6e:65:06.
Oct 11 16:39:43    DHCP: Server sending OFFER of 192.168.2.103.
Oct 11 16:39:43    DHCP: Server receive DISCOVER from a4:c0:e1:6e:65:06.
Oct 11 16:39:43    DHCP: Server sending OFFER of 192.168.2.103.
Oct 11 16:39:43    DHCP: Server receive DISCOVER from a4:c0:e1:6e:65:06.

I can find a relation between these events and the problem, but my knowledge ends there. Hope that can be a clue for you.

 

[boojay]

How can I make this message reach a developer? I have just found something truly interesting. The problem started again, just a few minutes ago. I checked everything back again, and just out of curiosity, looked at my router's logs. The following corresponds with the exact moment my WiFi stopped working...

Oct 11 16:39:58    DHCP: Server receive RELEASE from a4:c0:e1:6e:65:06.
Oct 11 16:39:43    DHCP: Server sending ACK to 192.168.2.103. (Lease time = 86400)
Oct 11 16:39:43    DHCP: Server receive REQUEST from a4:c0:e1:6e:65:06.
Oct 11 16:39:43    DHCP: Server sending ACK to 192.168.2.103. (Lease time = 86400)
Oct 11 16:39:43    DHCP: Server receive REQUEST from a4:c0:e1:6e:65:06.
Oct 11 16:39:43    DHCP: Server sending OFFER of 192.168.2.103.
Oct 11 16:39:43    DHCP: Server receive DISCOVER from a4:c0:e1:6e:65:06.
Oct 11 16:39:43    DHCP: Server sending OFFER of 192.168.2.103.
Oct 11 16:39:43    DHCP: Server receive DISCOVER from a4:c0:e1:6e:65:06.

I can find a relation between these events and the problem, but my knowledge ends there. Hope that can be a clue for you.

Your best bet is probably to share this info in one of the rom threads, in particular the one you're using, as those guys often check for bug reports in hopes of improving their roms.

Swyped from my Mi 2