I was talking about WPA-EAP enterprise connections, they are the only ones that use certificates from the keystore
Sorry I'll have to read more carefully in the future
Clean install with data wipe or just clean install? Coz there is no difference between 0.2 and 0.6 regarding Wi-Fi stack.EDIT: It drops connection with clean install too. I don't know. Friends laptop is stable on my connectify ap. I will just have to live with that.
EDIT: BTW, CM 7 is got newer wpa_supplicant. You can try using it with my ROM. And report if it works.
Last edited:
Well, I notice one strange thing so maybe it will help You too!Yes, we know. In my experience it only need's credential storage for TTLS connections, it never asks me for it if I use wpa2.. I don't know what is up with connectify and 0.6. It was working fine before (0.2), it is stable on other wifis tho. Nevertheless this is the best rom so far.
EDIT: It drops connection with clean install too. I don't know. Friends laptop is stable on my connectify ap. I will just have to live with that.
After clean install of 0.6, have same issue with WiFi ... almost after every screen turn-off it lost connection...even both of my WiFi routers was "fully open"
then I put WPA/WPA2 PSK ... add pass ..but with no progress
then , I manually add both WiFi network w/WPA-WPA2 PSK with passwords...without broadcast SSID ...and have no problem at all. When I am in range > I was connected
So, like I said /even do not have common sense /, try it that way
Maybe it was 0.1. I formated my brain after exam, so I can't really tell
. It was clean install. I removed the file, pushed the new one (from cm7), gave it permission to launch, started connectify. I was almost happy, since wifi stayed up for like 2min, and then dropped again. Now I can't even reconnect, it just switches between connecting.. and scanning.. Start/Stop wifi seems to help with the issue. Is it possible that sync is dropping the connection, because it looks to go off, after the syncing starts? Or maybe it is just random. lol But honestly i think that it is more stable with the new supplicant (or again, it is just my imagination at work because wifi just dropped again while writing that last sentence). Logcat has some new info, that i did not see before.D/wpa_supplicant( 2108): rssi-approx command
D/wpa_supplicant( 2108): CMD: DRIVER LINKSPEED
D/wpa_supplicant( 2108): wpa_driver_tista_driver_cmd LINKSPEED
D/wpa_supplicant( 2108): Link Speed command
D/wpa_supplicant( 2108): buf LinkSpeed 54
D/wpa_supplicant( 2108): RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
D/wpa_supplicant( 2108): RTM_NEWLINK, IFLA_IFNAME: Interface 'tiwlan0' added
D/wpa_supplicant( 2108): Wireless event: cmd=0x8b19 len=8
D/wpa_supplicant( 2108): Received 4740 bytes of scan results (12 BSSes)
D/wpa_supplicant( 2108): Actual APs number 12
D/wpa_supplicant( 2108): After merge, APs number 13
D/wpa_supplicant( 2108): New scan results available
D/wpa_supplicant( 2108): Selecting BSS from priority group 20
D/wpa_supplicant( 2108): Try to find WPA-enabled AP
D/wpa_supplicant( 2108): 0: 00:1f:41:75:fa:98 ssid='' wpa_ie_len=0 rsn_ie_len=20
caps=0x11
D/wpa_supplicant( 2108): skip - SSID not known
D/wpa_supplicant( 2108): 1: 00:1c:26:c2:d9:3e ssid='wi-fi' wpa_ie_len=0 rsn_ie_l
en=20 caps=0x11
D/wpa_supplicant( 2108): skip - SSID mismatch
D/wpa_supplicant( 2108): 2: 9e:a9:0d:2c:e8:91 ssid='bobo' wpa_ie_len=0 rsn_ie_le
n=0 caps=0x12
D/wpa_supplicant( 2108): skip - no WPA/RSN IE
D/wpa_supplicant( 2108): 3: 66:2c:a5:b7:c8:46 ssid='Kosta' wpa_ie_len=0
D/wpa_supplicant( 2108): skip - SSID mismatch
D/wpa_supplicant( 2108): Selecting BSS from priority group 17
D/wpa_supplicant( 2108): Try to find WPA-enabled AP
D/wpa_supplicant( 2108): 0: 00:1f:41:75:fa:98 ssid='' wpa_ie_len=0 rsn_ie_len=20
n=0 caps=0x12
D/wpa_supplicant( 2108): skip - no WPA/RSN IE
D/wpa_supplicant( 2108): 3: 66:2c:a5:b7:c8:46 ssid='Kosta' wpa_ie_len=0
D/wpa_supplicant( 2108): 12: 00:18:4d:58:ab:6c ssid='TOMI-TEST' wpa_ie_len=0 rsn
_ie_len=0 caps=0x1
D/wpa_supplicant( 2108): skip - no WPA/RSN IE
D/wpa_supplicant( 2108): Try to find non-WPA AP
D/wpa_supplicant( 2108): 0: 00:1f:41:75:fa:98 ssid='' wpa_ie_len=0 rsn_ie_len=20
caps=0x11
D/wpa_supplicant( 2108): skip - SSID not known
D/wpa_supplicant( 2108): 1: 00:1c:26:c2:d9:3e ssid='wi-fi' wpa_ie_len=0 rsn_ie_l
en=20 caps=0x11
D/wpa_supplicant( 2108): skip - SSID mismatch
D/wpa_supplicant( 2108): 2: 9e:a9:0d:2c:e8:91 ssid='bobo' wpa_ie_len=0 rsn_ie_le
n=0 caps=0x12
D/wpa_supplicant( 2108): skip - SSID mismatch
D/wpa_supplicant( 2108): 3: 66:2c:a5:b7:c8:46 ssid='Kosta' wpa_ie_len=0 rsn_ie_l
en=0 caps=0x12
D/wpa_supplicant( 2108): skip - SSID mismatc
en=0 caps=0x1
D/wpa_supplicant( 2108): selected non-WPA AP 00:1f:41:f5:fa:99 ssid='TomiC'
I/wpa_supplicant( 2108): Trying to associate with 00:1f:41:f5:fa:99 (SSID='TomiC
' freq=2 MHz)
D/wpa_supplicant( 2108): Cancelling scan request
D/wpa_supplicant( 2108): WPA: clearing own WPA/RSN IE
D/wpa_supplicant( 2108): wpa_driver_tista_set_mode
D/wpa_supplicant( 2108): Automatic auth_alg selection: 0x1
D/wpa_supplicant( 2108): WPA: clearing AP WPA IE
D/wpa_supplicant( 2108): WPA: clearing AP RSN IE
D/wpa_supplicant( 2108): WPA: clearing own WPA/RSN IE
D/wpa_supplicant( 2108): No keys have been configured - skip key clearing
D/wpa_supplicant( 2108): wpa_driver_tista_set_drop_unencrypted
D/wpa_supplicant( 2108): State: SCANNING -> ASSOCIATING
I/wpa_supplicant( 2108): CTRL-EVENT-STATE-CHANGE id=7 state=3 BSSID=00:1f:41:f5:
fa:99
D/wpa_supplicant( 2108): wpa_driver_tista_set_operstate: operstate 0 (DORMANT)
D/wpa_supplicant( 2108): wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
D/wpa_supplicant( 2108): WEXT: Operstate: linkmode=-1, operstate=5
D/wpa_supplicant( 2108): wpa_driver_tista_associate
D/wpa_supplicant( 2108): wpa_driver_tista_associate: BSSID=00:1f:41:f5:fa:99
D/wpa_supplicant( 2108): Setting authentication timeout: 10 sec 0 usec
D/wpa_supplicant( 2108): EAPOL: External notification - EAP success=0
D/wpa_supplicant( 2108): EAPOL: External notification - EAP fail=0
D/wpa_supplicant( 2108): EAPOL: External notification - portControl=ForceAuthori
zed
D/wpa_supplicant( 2108): RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
D/wpa_supplicant( 2108): RTM_NEWLINK, IFLA_IFNAME: Interface 'tiwlan0' added
D/wpa_supplicant( 2108): Wireless event: cmd=0x8b06 len=8
D/wpa_supplicant( 2108): RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
D/wpa_supplicant( 2108): RTM_NEWLINK, IFLA_IFNAME: Interface 'tiwlan0' added
D/wpa_supplicant( 2108): Wireless event: cmd=0x8b04 len=12
D/wpa_supplicant( 2108): RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
D/wpa_supplicant( 2108): RTM_NEWLINK, IFLA_IFNAME: Interface 'tiwlan0' added
D/wpa_supplicant( 2108): Wireless event: cmd=0x8c02 len=164
D/wpa_supplicant( 2108): RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
D/wpa_supplicant( 2108): RTM_NEWLINK, IFLA_IFNAME: Interface 'tiwlan0' added
D/wpa_supplicant( 2108): Wireless event: cmd=0x8c02 len=164
D/wpa_supplicant( 2108): CMD: AP_SCAN 1
D/wpa_supplicant( 2108): ap_scan = 1
V/WifiMonitor( 171): Event [Trying to associate with 00:1f:41:f5:fa:99 (SSID='T
omiC' freq=2 MHz)]
V/WifiMonitor( 171): Event [CTRL-EVENT-STATE-CHANGE id=7 state=3 BSSID=00:1f:41
:f5:fa:99]
D/wpa_supplicant( 2108): CMD: SCAN_RESULTS
D/wpa_supplicant( 2108): CMD: SCAN_RESULTS
V/WifiStateTracker( 171): Changing supplicant state: SCANNING ==> ASSOCIATING
I/keystore( 149): uid: 1000 action: t -> 1 state: 1 -> 1 retry: 4
V/WifiStateTracker( 171): KeyStore.NO_ERROR
D/wpa_supplicant( 2108): CMD: ENABLE_80211X
D/wpa_supplicant( 2108): CMD: STATUS
D/wpa_supplicant( 2108): CMD: DRIVER RSSI-APPROX
D/wpa_supplicant( 2108): wpa_driver_tista_driver_cmd RSSI-APPROX
D/wpa_supplicant( 2108): rssi-approx command
D/wpa_supplicant( 2108): CMD: DRIVER LINKSPEED
D/wpa_supplicant( 2108): wpa_driver_tista_driver_cmd LINKSPEED
D/wpa_supplicant( 2108): Link Speed command
D/wpa_supplicant( 2108): buf LinkSpeed 54
Edit:
I tried that, it drops the same way. So that is not an issue with me. Friends Desire stays connected normally, so it must be an issue with this rom.. I can't think anything else to try. Wierd..Well, I notice one strange thing so maybe it will help You too!
After clean install of 0.6, have same issue with WiFi ... almost after every screen turn-off it lost connection...even both of my WiFi routers was "fully open"
then I put WPA/WPA2 PSK ... add pass ..but with no progress
then , I manually add both WiFi network w/WPA-WPA2 PSK with passwords...without broadcast SSID ...and have no problem at all. When I am in range > I was connected
So, like I said /even do not have common sense /, try it that way
Last edited:
i love this rom... i keep coming back to this from CM.. using a2sd, cache is in internal mem... everthing's smooth... im testing the wifi, i didnt flash the wifi fix.. i will flash it if i notice problems.. i got 1100 in quadrant without data2ext!!
G
GuestK00138
Guest
nope.. just 600 mhz or i think it was 786... i got it once only... it goes from 800+ to 900+ on 600mhz...
Maybe this is a stupid question so in that case I'm very sorry but I was just wondering something. When a2sd is enabled, phone memory is not used at all is it? I keep having 150+mb free. Isn't there something useful we can do with it?
then i try to uninstall quickoffice-htc with titanium backup my phone freezh and then reboot
Why do you need to uninstall it? It's on system partition anyways. It is enough if you just disable it.
Sent from my HTC Legend
Sent from my HTC Legend
I need urgent help.
Just flashed to Blay0 0.6
I couldn't get the A2SD up. I counter check with Titanium Backup, but My A2SD is not there.
I flashed using ROM Manager.
Partitioned the card using ROM Manager too.
I installed 'Better Terminal Emulator'
it comes out like this:
"$ export PATH=/data/local/bin:$PATH:.
$ a2sd --enable
Enabling a2sd...
touch: /data/local/doa2sd: Permission denied
Please reboot your phone for changes to take effect"
I rebooted, yet still nothing changes.
Please help.
I used to know how to use ADB, now totally forgot d. Any simplier way?
I think i became dumb.
enter su at first, and confirm root access.
then enter a2sd --enable after it
Thanks. Got it correct now.
However, it does not seem to appear in my Titanium Backup to show A2SD portion.
How can i check for that except using Terminal?
I just wrote about several ways of doing that. The easiest would be to download quick system info from the market.
Sent from my HTC Legend using Tapatalk
Sent from my HTC Legend using Tapatalk
Hi,
Do you know if it's possible to add a feature to unlock with trackball (same as Cyano ...) ?
thanks.
Do you know if it's possible to add a feature to unlock with trackball (same as Cyano ...) ?
thanks.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone