Closed GoogleCodeExporter closed 8 years ago
I am having the exact same problem. If I wipe and reflash to an earlier
version, or another ROM altogether, I have access to WiFi, but this install of
0.04-10.11.20 does not allow me to access WiFi on any router whatsoever.
Original comment by ubermoo...@gmail.com
on 21 Nov 2010 at 1:45
I'm having same issue, with the 0.04-10.11.20, I'm going back to 0.04-10.11.16.
Original comment by cae.agui...@gmail.com
on 22 Nov 2010 at 1:41
I am having some troubles with WiFi too - wifi engages, but doesn't see
networks and fails to connect. After 1-2 disable/enable it usually picks up and
connects fine. This behaviour I started observing since the 0.04-2010.11.16
Original comment by ivan5...@gmail.com
on 22 Nov 2010 at 2:12
Thanks for the reports.
As I'm not facing any wifi issues, I will need you to make some tests to find
the cause of your problems.
Changes between 0.04-10.11.15/16 and 0.04-10.11.20:
in /etc/wifi/tiwlan.ini
- HT_Enable changed from 1 to 0 (N mode disabled)
Changes between 0.03 and 0.04:
/etc/wifi/tiwlan.ini
- WiFiAdhoc changed from 0 to 1 (to enable connection to AdHoc networks)
- many other changes in the whole tiwlan.ini (it's taken from a new Motorola's build)
/etc/wifi/wpa_supplicant.conf
- file from a new Motorola's build
Attached are both files from the 0.03-10.11.14 release.
To test the possible wpa_supplicant.conf influence, you should probably delete
your /data/misc/wifi/wpa_supplicant.conf file.
Original comment by kabal...@gmail.com
on 22 Nov 2010 at 7:02
Attachments:
I'll try to make this test, even changing between versions 0.03-11.14,
0.04-10.11.15/16, 0.04-10.11.20 doesn't change anything, even turning on/off
the wifi.
I cannot get RootExplorer, it just FC. I'll try to mod files in ADB mode (have
to learn how :) )
Original comment by cae.agui...@gmail.com
on 22 Nov 2010 at 2:09
Having same issue. replacing wpa_supplicant.conf and tiwlan.ini didn't solve
the problem.
Original comment by bleim...@googlemail.com
on 22 Nov 2010 at 7:46
Reverting HT_Enable to 1 has fixed this problem for me, and I am able to once
again connect to WiFi networks.
Original comment by ubermoo...@gmail.com
on 22 Nov 2010 at 7:52
For me deleting wpa_supplicant.conf and replacing tiwlan.ini with the attached
one solved the problem. Maybe jsut needed delete wpa_supplicant.conf. In the
tiwlan.ini HT_Enable = 0 and WiFiAdhoc = 0. I hope it help.
Original comment by cae.agui...@gmail.com
on 22 Nov 2010 at 8:06
thx for help. but HT_Enable on 1 doesnt fix it and both (HT_Enable and
WiFiAdhoc) to 0 doesnt help. (Also deleted the wpa_supplicant.conf)
Original comment by bleim...@googlemail.com
on 22 Nov 2010 at 8:31
Have you check if after deleting the wpa_supplicant.conf and restart the phone
the wpa_supplicant.conf file is recreated? BTW i'm using version 04-11.20 AFAIK
(not sure because i've installed and re-installed different versions)
I'm attaching my files
Original comment by cae.agui...@gmail.com
on 22 Nov 2010 at 9:34
Attachments:
ok..the wpa_supplicant.conf wasnt recreated. restarted 2 times. Now im trying
the new update-0.04-10.11.22 file.
Original comment by bleim...@googlemail.com
on 22 Nov 2010 at 10:16
Having same issue in 10.11.22. wpa_supplicant.conf isnt recreated and there is
no wifi connection. Also copied a downloaded wpa_supplicant in the directory
with no effect (restarted phone also)
Original comment by bleim...@googlemail.com
on 22 Nov 2010 at 10:38
If the wpa_supplicant.conf wasn't recreated there's something different wrong.
I'll test the new update later, at home so i can make more tests.
Original comment by cae.agui...@gmail.com
on 22 Nov 2010 at 11:25
reverting tiwlan.ini to the provided previous version and changing HT_Enable
from 1 to 0 (N mode disabled), has the wifi working correctly for me
Original comment by scottand...@gmail.com
on 23 Nov 2010 at 2:46
well updating to update-0.04-10.11.22 have no negative effect, Wifi still
working without changing any file. As mentioned before I had Wifi working after
deleting wpa_supplicant.conf file and restarting, this file was automatically
created with default values by the OS.
Original comment by cae.agui...@gmail.com
on 23 Nov 2010 at 5:22
Ok wifi works for me without wpa encryption. Have to test wpe when im at home.
but i want to work with wpa. anybody an idea whats the problem with the
wpa_supplicant. had made 2 fresh installs. Am i able to install
update-0.04-10.11.22 on a clean 2.1 system? One more way i could try.
Original comment by bleim...@googlemail.com
on 23 Nov 2010 at 7:58
Delete your saved Networks and readd it, then the Problem is gone.
Tested with WPA2 and WEP
Original comment by rene.bensch@gmail.com
on 23 Nov 2010 at 12:33
didnt work for me. Wifi still cycles between scanning, connecting and
disconnected on WPA Connections. Tried it 3-4 times
Original comment by bleim...@googlemail.com
on 23 Nov 2010 at 12:54
Oh I forget one step before, delete or rename the wpa_supplicant.conf. This
worked for me.
Original comment by rene.bensch@gmail.com
on 23 Nov 2010 at 1:33
tried it with another wpa wifi and it works a little bit better. Have a
connection for 2-3 minutes. But the wpa_supplicant.conf isnt recreated (with
reboot). And my old Wifi still not working. with 2.1 it worked flawless.
Original comment by bleim...@googlemail.com
on 23 Nov 2010 at 2:40
ok now its working..tried some different things, but thinks the solutn was to
set the permissions of the manually inserted wpa_supplicant.conf to the same
like the original tiwlan.ini.
Original comment by bleim...@googlemail.com
on 23 Nov 2010 at 4:49
Issue 241 has been merged into this issue.
Original comment by kabal...@gmail.com
on 25 Nov 2010 at 12:02
with latest release (update-0.04-10.12.03) wi-fi stopped working again
(WPA2-PSK encryption). Furthermore, reverting to older versions of tiwlan.ini &
/etc/wifi/wpa_supplicant.conf does not seem to fix the problem.
Original comment by Martin.R...@gmail.com
on 4 Dec 2010 at 7:36
I think, that the problem has something to do with:
https://forum.openwrt.org/viewtopic.php?pid=114504
"...The cause is that the wireless driver in many of the custom ROMs is
WiLink_Driver_6.1.0.0.131, which incorrectly sends two WPA2 RSN IEs that are
different. It uses the value of the PTKSA from the AP to generate the PTKSA and
GTKSA settings in the RSN capabilities section for the first RSN IE, but just
uses 0 for the second. If WMM/WME is enabled on the AP, the AP sets its PTKSA
to > 0, causing the Droid to respond with one RSN IE with non-zero values. But,
hostapd uses the second RSN IE, notices the mismatch, and drops the
connection..."
My logs on my wifi router confirm the problem:
Apr 14 06:00:45 apa daemon.info hostapd: wlan0: STA a4:ed:4e:d4:xx:xx IEEE
802.11: authenticated
Apr 14 06:00:45 apa daemon.info hostapd: wlan0: STA a4:ed:4e:d4:xx:xx IEEE
802.11: associated (aid 3)
Apr 14 06:00:45 apa daemon.info hostapd: wlan0: STA a4:ed:4e:d4:xx:xx WPA: WPA
IE from (Re)AssocReq did not match with msg 2/4
Apr 14 06:00:45 apa daemon.info hostapd: wlan0: STA a4:ed:4e:d4:xx:xx IEEE
802.11: deauthenticated due to local deauth request
Apr 14 06:00:48 apa daemon.info hostapd: wlan0: STA a4:ed:4e:d4:xx:xx IEEE
802.11: authenticated
Apr 14 06:00:48 apa daemon.info hostapd: wlan0: STA a4:ed:4e:d4:xx:xx IEEE
802.11: associated (aid 3)
Apr 14 06:00:48 apa daemon.info hostapd: wlan0: STA a4:ed:4e:d4:xx:xx WPA: WPA
IE from (Re)AssocReq did not match with msg 2/4
Apr 14 06:00:48 apa daemon.info hostapd: wlan0: STA a4:ed:4e:d4:xx:xx IEEE
802.11: deauthenticated due to local deauth request
Original comment by artem.ma...@gmail.com
on 6 Dec 2010 at 8:24
Probably just a side note; I had the same symptoms where Wifi cycles between
scanning, connecting and disconnected. I looked at the log and it was saying
"Failed to authenticate, disabling network". Even though I was putting the
correct password in /etc/wifi/wpa_supplicant.conf wasn't getting updated, even
after choosing Forget Network. I had to edit the password in the file to be
able to connect to the WPA-TKIP AP again.
Original comment by dean.lor...@gmail.com
on 17 Dec 2010 at 10:10
hm..strange. I can not connect to my router, when it it is in mode 802.11b/g/n.
It works fine if i choose 802.11g only mode.
Original comment by Martin.R...@gmail.com
on 18 Dec 2010 at 10:14
I can confirm that I'm unable to connect to APs that support n-draft...
Original comment by hello.ti...@googlemail.com
on 18 Dec 2010 at 6:11
Having the same problems as Dean, Wifi loops between Scanning, Connecting and
Disconnected. Worked fine with Moto stock 2.1.
Tried it with deleting /data/misc/wifi/wpa_supplicant.conf - didn't help.
Original comment by nap...@gmail.com
on 13 Jan 2011 at 6:01
napsty, check if the password/encryption settings are correct by looking at the
wpa_supplicant.conf file. To me it seemed like updating the password from the
Wireless & Networks settings menu wasn't updating the wpa_supplicant.conf file.
Once I updated the setting in that file from the console it connected right
away.
Original comment by dean.lor...@gmail.com
on 13 Jan 2011 at 7:06
Yes, I actually did check that and the information was updated and correct.
Original comment by nap...@gmail.com
on 13 Jan 2011 at 8:10
[deleted comment]
Update 14.01.2011: At work I am able to connect to an Ad-Hoc WiFi which is
protected by WEP. At home I tried it with WPA and WPA2 PSK, didn't work there.
Update 15.01.2011: So at home I changed the encryption on the AP to WEP -
Milestone was still not able to connect. I changed the AP back to WPA2 PSK and
restarted the AP - now suddenly my milestone could connect to it and reconnects
to it.
It's possible that my AP has a problem, difficult to say if it's the Milestone
or the AP.
Original comment by nap...@gmail.com
on 15 Jan 2011 at 11:02
I'm unable to connect to my dlink router (haven't check the router logs or
channel yet) since the driver update in 0.05. I can connect at work to the WPA2
Enterprise network without a problem.
Original comment by sde...@gmail.com
on 18 Jan 2011 at 4:55
Original comment by kabal...@gmail.com
on 1 Mar 2011 at 2:43
[deleted comment]
Wifi works only on 802.11g mode! No matter if I delete that file or no...
Original comment by abaza.an...@gmail.com
on 21 May 2011 at 6:38
Original issue reported on code.google.com by
scottand...@gmail.com
on 20 Nov 2010 at 5:00