Related
Ok im running Froyo-Stone Sense v3.2 and I havn't had any problems with it till now,it's been running perfect otherwise,Now it doesn't want to connect to the internet for some reason.It says connection failed and I have tried toggling airplane mode,toggling wifi,etc.My APN settings are correct.Just not sure why all of a sudden it won't work.Any Ideas?Aside from that I am extremely satisfied with this build and I use it daily.
Hi
i had the same issue with the internet in France & I changed the build.prop (under /system) to change to the right DNS addresses.
At the end of this file, i changed to 62.201.129.99 all of the ip adresses
I don't if it'll work for you but this is the only good fix which works 100%
Regards,
Christophe P.
im not sure how to do what your talkin about.lol
Follow this link
www . carson.alittlekitchen.com / changing-android-mobile-data-dns-server-settings
Quit opening new threads in the wrong section!
Hi!
I Cannot find solution to connect to company's hidden Wifi 802.1x network
I tried almost anything to make it work .... but without success
I have had various wpa_supplicant bin files.
I have edited 100x wpa_supplicant.conf file.
I was reading forums with "SOLVED" solutions ... for other phones ... but cannot find solution to work on Huawei IDEOS X5 U8800.
I also have tried it with various ROMs: MIUI 1.8.x and 1.9.x, VOID, B135, B136,B160, cm7-100911, Oxygen ...
But every time with no success ...
Hints:
a) All other colleagues connect without problem (they have HTCs, Samsung Galaxy S I,II, iPhones 3,4 ...) while my friend and i cannot connect
b) I connect to my home Wifi (WPA/PSK) without a problem!
Anyone have similar problem?
BTW: MY wpa_supplicant.conf file looks like:
ctrl_interface=wlan0
update_config=1
network={
ssid="mySSID"
scan_ssid=1
key_mgmt=IEEE8021X
group=WEP104 WEP40
auth_alg=OPEN SHARED
eap=PEAP
identity="[email protected]"
password="zzzzzz"
phase2="auth=MSCHAPV2"
}
Brgds,
S.
HELPPPPP
Have had sporadic issues myself, and found that setting ap_scan=2 in /system/etc/wifi/wpa_supplicant.conf was helpful but not flawless. I reverted back to a CWM of MIUI 1.8.19 which I recalled seemed to connect without issues. On reviewing the wpa_supplicant.conf files in system and data, I noticed that the ctrl_interface was different.
ctrl_interface=DIR=/data/misc/wifi/wpa_supplicant GROUP=system
rather than ctrl_interface=wlan0
I haven't yet tried moving back to the latest version of MIUI to test these changes, but will do so when I get the time.
Modify below files and ensure permissions dont change
Both /data/misc/wifi/wpa_supplicant.conf
and /system/etc/wifi/wpa_supplicant.conf
also create a new folder wpa_supplicant in /data/misc/wifi/
mkdir /data/misc/wifi/wpa_supplicant -m 750
haydnlj said:
Have had sporadic issues myself, and found that setting ap_scan=2 in /system/etc/wifi/wpa_supplicant.conf was helpful but not flawless. I reverted back to a CWM of MIUI 1.8.19 which I recalled seemed to connect without issues. On reviewing the wpa_supplicant.conf files in system and data, I noticed that the ctrl_interface was different.
ctrl_interface=DIR=/data/misc/wifi/wpa_supplicant GROUP=system
rather than ctrl_interface=wlan0
I haven't yet tried moving back to the latest version of MIUI to test these changes, but will do so when I get the time.
Modify below files and ensure permissions dont change
Both /data/misc/wifi/wpa_supplicant.conf
and /system/etc/wifi/wpa_supplicant.conf
also create a new folder wpa_supplicant in /data/misc/wifi/
mkdir /data/misc/wifi/wpa_supplicant -m 750
Click to expand...
Click to collapse
The control interface is changed so that it works with other versions of wpa_supplicant. If you change it to the way it was in the older Miui then wifi won't work at all.
If it never worked (even on stock) then the issue probably isn't with wpa supplicant, and could be a problem with the wifi driver, or the hardware itself. This really needs someone who knows what they're doing and access to a hidden 802.1x network to look into it.
stockwell said:
If it never worked (even on stock) then the issue probably isn't with wpa supplicant, and could be a problem with the wifi driver, or the hardware itself.
Click to expand...
Click to collapse
Was there a driver change between 1.8.19 and later MIUI versions? The supplicant seems like the same version (v 0.6.10)?
On returning to 1.8.19 have had 3 days without issues. When on 1.9.30 the change to ap_scan=2 definitely improved and seemed to make a connection on reboot flawless, but reconnection from sleep was sporadic (probably <30%). Watching wpa_cli output when waking phone from screen off on 1.9.30 showed a failed connection attempt, and then a series of timed scans (CTRL-EVENT-SCAN-RESULTS) - these continued after CTRL-EVENT-CONNECTED (something that didn't occur after toggling wifi on/off/on and connecting).
stockwell said:
This really needs someone who knows what they're doing and access to a hidden 802.1x network to look into it.
Click to expand...
Click to collapse
Agree
haydnlj said:
Was there a driver change between 1.8.19 and later MIUI versions? The supplicant seems like the same version (v 0.6.10)?
On returning to 1.8.19 have had 3 days without issues. When on 1.9.30 the change to ap_scan=2 definitely improved and seemed to make a connection on reboot flawless, but reconnection from sleep was sporadic (probably <30%). Watching wpa_cli output when waking phone from screen off on 1.9.30 showed a failed connection attempt, and then a series of timed scans (CTRL-EVENT-SCAN-RESULTS) - these continued after CTRL-EVENT-CONNECTED (something that didn't occur after toggling wifi on/off/on and connecting).
Agree
Click to expand...
Click to collapse
Thanks for you feedback, that really helps. Even though the version number is the same they aren't the same file.
I'll get in contact with you via pm to try and sort this out.
Thanks guys for trying!
So there is no solution yet?
Any news ?
Thanks!
Any news ?
I have same problem with that.
I also have the same problem, and looking for a solution. I am using Redmi 4a MIUI 8.2.6.0
Hello,
To start off, I have a USCellular S4 w/ CM10.1, currently the 7/9 nightly. I am running baseband version R970VXUAMDL and have not modified the kernel.
I am unable to enable WiFi at all on CM10.1 and haven't been able to since initially flashing CM10.1.
Under the Settings menu, I am unable to enable WiFi - it's greyed out.
Under the WiFi menu, I can enable the toggle but it does nothing.
Under the Advanced menu, MAC address shows 'unavailable' and the Wi-Fi region code is set to 'Europe' and will not remember changes.
sylvisj said:
Hello,
To start off, I have a USCellular S4 w/ CM10.1, currently the 7/9 nightly. I am running baseband version R970VXUAMDL and have not modified the kernel.
I am unable to enable WiFi at all on CM10.1 and haven't been able to since initially flashing CM10.1.
Under the Settings menu, I am unable to enable WiFi - it's greyed out.
Under the WiFi menu, I can enable the toggle but it does nothing.
Under the Advanced menu, MAC address shows 'unavailable' and the Wi-Fi region code is set to 'Europe' and will not remember changes.
Click to expand...
Click to collapse
Have you tried removing the .cid.info file ?
Using a terminal app type the following:
Code:
su
rm /data/.cid.info
On some ROM's have have to do this after every time I have rebooted the phone, not quite sure why but it works for me.
TrallaP said:
Have you tried removing the .cid.info file ?
Using a terminal app type the following:
Code:
su
rm /data/.cid.info
On some ROM's have have to do this after every time I have rebooted the phone, not quite sure why but it works for me.
Click to expand...
Click to collapse
Hello,
Thanks for the suggestion. I fired up Terminal Emulator, su'd, and it doesn't look like there is a .cid.info in /data/. There is a .psm.info, though, and .npswifi_stream - I don't know if they're related at all.
sylvisj said:
Hello,
Thanks for the suggestion. I fired up Terminal Emulator, su'd, and it doesn't look like there is a .cid.info in /data/. There is a .psm.info, though, and .npswifi_stream - I don't know if they're related at all.
Click to expand...
Click to collapse
Here's the 'ls -a' output for /data:
Code:
[email protected]:/data # ls -a
.container_1
.container_2
.container_3
.layout_version
.mtp_stream
.npswifi_stream
.pcsync_stream
.psm.info
.socket_stream
.ssh
anr
app
app-asec
app-lib
app-private
audio
backup
bcmnfc
bluetooth
cam_socket0
cam_socket1
container
dalvik-cache
data
dontpanic
drm
fota
hostapd
local
log
lost+found
media
misc
nfc
property
qcks
radio
resource-cache
security
shared
ssh
system
time
tombstones
user
wiper
wpstiles
Bump.
I have the same problem......
ninne1 said:
I have the same problem......
Click to expand...
Click to collapse
Bump again.
i think it's missing IMEI and EFS. Try this http://forum.xda-developers.com/showthread.php?t=1264021
r47z said:
i think it's missing IMEI and EFS. Try this http://forum.xda-developers.com/showthread.php?t=1264021
Click to expand...
Click to collapse
I dunno about EFS, but I know the IMEI is already correct - *#06* is showing the same IMEI as the label on the back of my phone.
My phone is work well after flashing CM, but no WIFI.
No /data/.cid.info file!
*#06# - show IMEI.
Did we ever get to the bottom of this?
Im having exactly the same problem, so bump. Its been like that for 6 months, my workaround so far was getting a bigger data subscribtion since 4g is working fine
sylvisj said:
Hello,
To start off, I have a USCellular S4 w/ CM10.1, currently the 7/9 nightly. I am running baseband version R970VXUAMDL and have not modified the kernel.
I am unable to enable WiFi at all on CM10.1 and haven't been able to since initially flashing CM10.1.
Under the Settings menu, I am unable to enable WiFi - it's greyed out.
Under the WiFi menu, I can enable the toggle but it does nothing.
Under the Advanced menu, MAC address shows 'unavailable' and the Wi-Fi region code is set to 'Europe' and will not remember changes.
Click to expand...
Click to collapse
Hi sylvis,
I realize that this is an old post. However. perhaps this thread will help someone else:
I flashed a Samsung Galaxy S4 (T-mobile SGH-M919) to CyanogenMod (CM11) this weekend. It worked ok for a couple days. The owner then said that they can't get any WI-FI. I found your post here and read with optimism that I might be able to fix this problem. Our problem was exactly "word for word" the same problem as you described in your original post. (Well almost exactly; we couldn't get "USA" to stick as the region code)
Before flashing the phone, I did install Philz ClockworkMod and did do a backup of the OEM ROM before flashing to CM11. That said, I found that I did not have to go down the road of restoring a missing IMEI file (as other threaders here describe). Here's what worked for me:
I dialed *#06# on the phone to see if there was an IMEI number present, and there was. I wrote down that number. So I decide to see if that number matched the printed number on the phone, that we can find under the battery.
Before I do a power off of the phone, I recall that I had turned OFF both Bluetooth and Mobile Networks. WI-FI was still turned ON, but in it's non-functional "greyed out" state like you and I both experienced.
Now I power off the phone, take off the back cover, and take out the battery to have a look at the printed IMEI number. Yes, it does march the number that I saw via *#06#.
I had to get up to do something, then returned a couple minutes later. I popped in the battery and restarted the phone. To my utter surprise, WI-FI was back up! In "Advanced" I now see the MAC address and the region is locked on USA
I turn on Mobile Networks, and WI-FI's still working. Being the fool that I am, I have to test this further. So I power off the phone again and just let it sit there for a couple minutes. I power back on and there is still JOY. Problem resolved and happy customer.
In closing: I don't think that the removal and reinsertion of the battery was the total solution, because the owner had already tried that. However, the owner did not let the phone sit with the battery removed for very long. They just popped it out, waited a couple seconds, then popped it back in. I think the total solution was having WI-FI enabled, Bluetooth and Mobile disabled, then doing a power off, with an extended wait time before reinserting the battery.
Hope that helps.
Regards,
Brcobrem
Is anyone having issues with WIFI passwords not being remembered?
After updating to MJ4, passwords to wifi have to be reentered every time to connect.
Yea same here but it was happening on mine prior as well. Guess the last update didn't help that.
sent from - At&t Note3 - still stock
SOLUTION:
kevg77 said:
I have seen that others are having the same issue that I am having where my phone forgets WiFi settings after every reboot since MJ4 update. What is the fix for this?
Thanks
Click to expand...
Click to collapse
kevg77 said:
WiFi problems?
Try this:
Due to "securestorage" being set to true in build.prop, changes to the ROM or kernel that aren't reflected in the ss_id file in /system/etc/secure_storage/.system.bin.wpa_supplicant/ can cause issues with WiFi among other things. You can set this to false yourself, or simply flash the zip file below.
Download: Set Secure Storage to False
For those that prefer to do it manually, simply change this line ro.securestorage.support=true to false in /system/build.prop.
Click to expand...
Click to collapse
Why was [ ro.securestorage.support=true] set to true? --Is this by ROM's default?
What functionality do we lose once it's set to "false"?
Thanks for the solution. Unfortunately I'm not rooted yet. But with all the problems I'm having I might just root it to load a custom rom
sent from - At&t Note3 - still stock
From another post, worket for me:
Quote:
Originally Posted by kevg77
WiFi problems?
Try this:
Due to "securestorage" being set to true in build.prop, changes to the ROM or kernel that aren't reflected in the ss_id file in /system/etc/secure_storage/.system.bin.wpa_supplicant/ can cause issues with WiFi among other things. You can set this to false yourself, or simply flash the zip file below.
Download: Set Secure Storage to False
For those that prefer to do it manually, simply change this line ro.securestorage.support=true to false in /system/build.prop.
Had this problem for months and solved it just now by deleting some old networks from the list of remembered networks. It seems that the problem was due to exceeding the number of networks kept in memory. Hope this helps someone, I have not seen this suggestion anywhere.
OK i seem to have this extremely bizzare wifi issue.
I can connect to wifi access points fine, if i turn off wifi and turn it back on i am unable to auto connect and have to re-enter credentials for it to connect. Before doing so i checked my wifi ap to see if my ap were listed and they were not.
If i re-enter everything is fine but having to do this to wifi ap is annoying. After i have entered and check the wifi ap files i can see the credentials are saved etc.
If i do not re-enter the credentials and restart the phone with wifi enabled it connects to AP fine.
If i leave wifi connected and connect to to wifi aps that require certs its fine also without the need to re-enter creds.
At first i thought maybe i had a corruption in the wifi config files but i dont see any, no duplicate aps at all, no fancy characters i can see.
Does anyone have any thoughts as my wifi config with aps is many years old and has a massive amount of APs listed.
It doesnt matter what ROM i try as soon as i restore all my APs the issues start, is there a way to bulk export, wipe wifi aps and re-import them all again?
Do wifi aps with spaces in or length cause issues with 5.1.1?
1 root ur phone if you are unrooted 2 download any build prop editor from playstore 3 change this line ro.securestorage.support=true to false in /system/build.prop 4 if it doesnt work try a different build prop editor cz the changes might not be sticking 5) hit the thanks button if it helped
dork997 said:
1 root ur phone if you are unrooted 2 download any build prop editor from playstore 3 change this line ro.securestorage.support=true to false in /system/build.prop 4 if it doesnt work try a different build prop editor cz the changes might not be sticking 5) hit the thanks button if it helped
Click to expand...
Click to collapse
ro.securestorage.support=false
already