Database Users

Microsoft Direct Push E-mail not working when phone suspended

Anyone else experiencing this problem? With Microsoft Direct Push e-mail configured to sync with Exchange 2003 and deliver items as they arrive, the phone works perfectly when powered on but when the phone goes into suspend/standby mode, after a few minutes it stops listening for the Exchange server ping that tells it to initiate a sync. The effect is that e-mails are not delivered when the phone is suspended. When the phone is brought out of suspend mode a sync is initiated and the e-mails arrive.
A section of the ActiveSync log file shows what's happening...
2008-12-09 08:03:28 AutdMode Old=Http (v1), New=Http (v1)
2008-12-09 08:03:28 Heartbeat Begin heartbeat series
2008-12-09 08:03:28 Scheduled 2008-12-09 23:59:28, handle=0x3c00009f, hr=0x0
2008-12-09 08:03:28 KeepAwake Off
2008-12-09 08:08:39 KeepAwake On
2008-12-09 08:08:40 EstConnection WOI requested
2008-12-09 08:08:40 EstablishConn hr=0x0, handle=0x29060d12, pri=0x200, status=0x10, flags=0x460200, wait=0
2008-12-09 08:08:40 ConnInfo Type=1, Subtype=2, Secure=0, Descr=O2 Mobile Web
2008-12-09 08:08:41 AutdPing Sending folder list. Folder count = 3
2008-12-09 08:08:41 AutdPing Ping sent. Heartbeat = 480
2008-12-09 08:08:43 DormantHint Dormant mode on [Ping]
2008-12-09 08:08:43 KeepAwake Off
2008-12-09 08:47:40 KeepAwake On
2008-12-09 08:47:40 AutdPing Ping received. HR = 85030021
2008-12-09 08:47:40 Heartbeat Heartbeat failed, hr = 0x85030021
2008-12-09 08:47:40 EstConnection WOI requested
2008-12-09 08:47:40 EstablishConn hr=0x0, handle=0xe9089f4e, pri=0x200, status=0x10, flags=0x460200, wait=0
2008-12-09 08:47:40 ConnInfo Type=1, Subtype=6, Secure=0, Descr=O2 Mobile Web
2008-12-09 08:47:40 AutdPing Sending folder list. Folder count = 3
2008-12-09 08:47:40 AutdPing Ping sent. Heartbeat = 480
2008-12-09 08:47:47 DormantHint Dormant mode on [Ping]
2008-12-09 08:47:47 KeepAwake Off
In this log, synchronisation and pings are working fine with the phone on, at around 08:10 the phone enters suspend mode - no further activity is logged until the phone is brought out of suspend at 08:47 - when it realises it's missed it's ping from Exchange and initiates an immediate sync. There should be pings and responses logged between these times (several test e-mails were sent to the exchange mailbox).
Looks like it could be a bug in the radio firmware - the radio not handling dormant ping mode correctly.
The same mailbox syncs perfectly with other HTC phones so I doubt it's related to the Exchange config (and the Touch 3G works perfectly if left powered on).
Can anyone else reproduce this - if it's a common fault then it's a big oversight by HTC.

It seems that there is a bug concerning suspend mode and some types of incoming data.
What ROM do you have?

It must be a bug. You should report this to HTC.
Same problem at the receiving sms and e-mails as the phone wake off.
Maybe, it should save battery.

Concerning SMS. I use GSM network and when SMS comes, device does not wake up, but it plays sound and starts to flash LED (I set it to infinite flashing). Actually I like this more.

This is with ROM 1.40.405.3 and Radio 0.27.30.09
Strangly, I have no issues with sms or incoming calls in suspend mode. I've reported the issue to htc but am still interested to know if anyone else can reproduce this problem with push email?

Camera Problems Since Flashing ROM

Ever since I first unlocked the bootloader and flashed the original Modaco Desire ROM onto my Nexus One, I haven't been able to use the camera. I believe camera functionality may not have been working in the initial Modaco Desire ROM(s), so I didn't think much of it at the time. I have since flashed a number of the newer Desire ROMs, the 2/27 CyanogenMod ROM, and then yesterday Enomther's 3/9 ROM. With all of these ROMs, when I launch the camera app (or any other app which uses the camera), the app hangs. In the case of the camera app, it seems to launch and display a black screen but never is able to initialize the camera. I have read/searched through the threads of each of the ROMs I've tried, and haven't heard of others having my same problems (i.e. if the camera was advertised as working in the ROM, others seem to at least be able to launch the camera app). Any thoughts?
Here's logcat output from me launching the camera app, waiting for it to time out, and then selecting force close:
I/ActivityManager( 67): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.camer
a/.Camera bnds=[125,586][235,704] }
I/WindowManager( 67): Setting rotation to 1, animFlags=0
I/ActivityManager( 67): Config changed: { scale=1.0 imsi=310/260 loc=en_US tou
ch=3 keys=1/1/2 nav=3/1 orien=2 layout=34}
V/RenderScript_jni( 412): surfaceChanged
V/RenderScript( 412): setSurface 800 442 0x5e85e0
E/Surface ( 412): surface (id=0, identity=77) is invalid, err=-19 (No such devi
ce)
E/Surface ( 412): surface (id=0, identity=77) is invalid, err=-19 (No such devi
ce)
E/Surface ( 412): invalid token (-1, identity=0) or client (0x0)
E/Adreno200-EGL( 412): egliGetNativeWindowSize: unable to dequeue native buffer
E/Surface ( 412): invalid token (-1, identity=0) or client (0x0)
E/Adreno200-EGL( 412): egliGetNativeWindowSize: unable to dequeue native buffer
E/RenderScript( 412): EGL/Surface mismatch EGL (0 x 0) SF (800 x 442)
E/RenderScript( 412): Pending GL Error, 0x3d3460
E/RenderScript( 412): Pending GL Error, 0x3d3460
V/RenderScript_jni( 412): surfaceDestroyed
V/RenderScript( 412): setSurface 0 0 0x0
D/ViewFlipper( 412): updateRunning() mVisible=false, mStarted=true, mUserPresen
t=true, mRunning=false
D/dalvikvm( 67): GC freed 2705 objects / 132680 bytes in 102ms
W/ActivityManager( 67): Launch timeout has expired, giving up wake lock!
W/ActivityManager( 67): Activity idle timeout for HistoryRecord{449fd288 com.a
ndroid.camera/.Camera}
W/WindowManager( 67): Key dispatching timed out sending to <null>
W/WindowManager( 67): Dispatch state: {{KeyEvent{action=1 code=82 repeat=0 met
a=0 scancode=139 mFlags=72} to Window{447955a8 com.android.launcher2/com.android
.launcher2.Launcher paused=false} @ 1268363968496 lw=Window{447955a8 com.android
.launcher2/com.android.launcher2.Launcher paused=false} lb=android.os.BinderProx
[email protected] fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=null}}
I/WindowManager( 67): focus null mToken is null at event dispatch!
W/WindowManager( 67): Current state: {{KeyEvent{action=0 code=4 repeat=0 meta
=0 scancode=158 mFlags=72} to null @ 1268364096773 lw=null lb=null fin=true gfw=
true ed=true tts=0 wf=false fp=false mcf=null}}
I/ActivityManager( 67): ANR in process: com.android.camera (last in com.androi
d.camera)
I/ActivityManager( 67): Annotation: keyDispatchingTimedOut
I/ActivityManager( 67): CPU usage:
I/ActivityManager( 67): Load: 1.54 / 1.61 / 1.03
I/ActivityManager( 67): CPU usage from 9308ms to 3309ms ago:
I/ActivityManager( 67): events/0: 4% = 0% user + 4% kernel
I/ActivityManager( 67): system_server: 2% = 0% user + 1% kernel / faults: 7
minor
I/ActivityManager( 67): synaptics_wq: 0% = 0% user + 0% kernel
I/ActivityManager( 67): akmd: 0% = 0% user + 0% kernel
I/ActivityManager( 67): TOTAL: 7% = 0% user + 6% kernel
I/ActivityManager( 67): Removing old ANR trace file from /data/anr/traces.txt
I/Process ( 67): Sending signal. PID: 467 SIG: 3
I/dalvikvm( 467): threadid=7: reacting to signal 3
I/dalvikvm( 467): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 67 SIG: 3
I/dalvikvm( 67): threadid=7: reacting to signal 3
I/dalvikvm( 67): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 437 SIG: 3
I/dalvikvm( 437): threadid=7: reacting to signal 3
I/dalvikvm( 437): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 412 SIG: 3
I/dalvikvm( 412): threadid=7: reacting to signal 3
I/dalvikvm( 412): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 526 SIG: 3
I/dalvikvm( 526): threadid=7: reacting to signal 3
I/dalvikvm( 526): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 194 SIG: 3
I/dalvikvm( 194): threadid=7: reacting to signal 3
I/dalvikvm( 194): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 157 SIG: 3
I/dalvikvm( 157): threadid=7: reacting to signal 3
I/dalvikvm( 157): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 323 SIG: 3
I/dalvikvm( 323): threadid=7: reacting to signal 3
I/dalvikvm( 323): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 292 SIG: 3
I/dalvikvm( 292): threadid=7: reacting to signal 3
I/dalvikvm( 292): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 428 SIG: 3
I/dalvikvm( 428): threadid=7: reacting to signal 3
I/dalvikvm( 428): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 299 SIG: 3
I/dalvikvm( 299): threadid=7: reacting to signal 3
I/dalvikvm( 299): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 398 SIG: 3
I/dalvikvm( 398): threadid=7: reacting to signal 3
I/dalvikvm( 398): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 287 SIG: 3
I/dalvikvm( 287): threadid=7: reacting to signal 3
I/dalvikvm( 287): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 389 SIG: 3
I/dalvikvm( 389): threadid=7: reacting to signal 3
I/dalvikvm( 389): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 378 SIG: 3
I/dalvikvm( 378): threadid=7: reacting to signal 3
I/dalvikvm( 378): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 220 SIG: 3
I/dalvikvm( 220): threadid=7: reacting to signal 3
I/dalvikvm( 220): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 202 SIG: 3
I/dalvikvm( 202): threadid=7: reacting to signal 3
I/dalvikvm( 202): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 276 SIG: 3
I/dalvikvm( 276): threadid=7: reacting to signal 3
I/dalvikvm( 276): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 305 SIG: 3
I/dalvikvm( 305): threadid=7: reacting to signal 3
I/dalvikvm( 305): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 268 SIG: 3
I/dalvikvm( 268): threadid=7: reacting to signal 3
I/dalvikvm( 268): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 238 SIG: 3
I/dalvikvm( 238): threadid=7: reacting to signal 3
I/dalvikvm( 238): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 213 SIG: 3
I/dalvikvm( 213): threadid=7: reacting to signal 3
I/dalvikvm( 213): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 142 SIG: 3
I/dalvikvm( 142): threadid=7: reacting to signal 3
I/dalvikvm( 142): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 162 SIG: 3
I/dalvikvm( 162): threadid=7: reacting to signal 3
I/dalvikvm( 162): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 141 SIG: 3
I/dalvikvm( 141): threadid=7: reacting to signal 3
I/dalvikvm( 141): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 67): Sending signal. PID: 136 SIG: 3
I/dalvikvm( 136): threadid=7: reacting to signal 3
I/dalvikvm( 136): Wrote stack trace to '/data/anr/traces.txt'
W/WindowManager( 67): No focus window, dropping: KeyEvent{action=0 code=4 repe
at=0 meta=0 scancode=158 mFlags=72}
I/ActivityManager( 67): Killing process com.android.camera (pid=467) at user's
request
I/Process ( 67): Sending signal. PID: 467 SIG: 9
I/ActivityManager( 67): Process com.android.camera (pid 467) has died.
I/WindowManager( 67): Setting rotation to 0, animFlags=0
W/WindowManager( 67): Rebuild removed 6 windows but added 5
I/ActivityManager( 67): Config changed: { scale=1.0 imsi=310/260 loc=en_US tou
ch=3 keys=1/1/2 nav=3/1 orien=1 layout=34}
I/UsageStats( 67): Unexpected resume of com.android.launcher2 while already re
sumed in com.android.camera
V/RenderScript_jni( 412): surfaceCreated
V/RenderScript_jni( 412): surfaceChanged
V/RenderScript( 412): setSurface 800 442 0x11e720
D/ViewFlipper( 412): updateRunning() mVisible=true, mStarted=true, mUserPresent
=true, mRunning=true
V/RenderScript_jni( 412): surfaceChanged
V/RenderScript( 412): setSurface 480 762 0x11e720
W/InputManagerService( 67): Window already focused, ignoring focus gain of: co
[email protected]
D/dalvikvm( 67): GC freed 4427 objects / 212984 bytes in 101ms

I have same issue
Wrong Thread

[Q] Android 2.2 Stock continuously authenticating wi-fi

Hi all,
So to start with, I am a total noob with android. I have a HTC Desire Z running stock Android/ Sense.
The problem I am having is that every so often I seem to lose my connection to my home wlan. The wireless symbol on the phone shows full strength but I can't connect/ sync with anything on the net. When I check the wireless & settings page on the phone, it shows that the phone is authenticating with my router. It stays like that till I turn wifi off and on.
This seems to happen whether I am using the net or not, I feel it may take longer to happen if I am using the net via the phone over the wlan but can't really say for sure.
I have set wi-fi to never sleep in case this was the issue, (previously had been set at never sleep when charging). Power saver is set to turn on at 15% but the problem happens even if the battery is full.
I don't know if the problem is my phone or my router. My wireless router is a Zyxel P-660HW-D1, does b and g. I am using WPA2-PSK and arm on channel 6. SSID is not hidden.
I have carried out a search here and the only post I could find mentioned something to do with PEAP. I have no idea what this is. Also read up on that but it lost me tbh.
Anyone got any ideas?
Thanks for any help guys.

H4rry said:
Hi all,
So to start with, I am a total noob with android. I have a HTC Desire Z running stock Android/ Sense.
The problem I am having is that every so often I seem to lose my connection to my home wlan. The wireless symbol on the phone shows full strength but I can't connect/ sync with anything on the net. When I check the wireless & settings page on the phone, it shows that the phone is authenticating with my router. It stays like that till I turn wifi off and on.
This seems to happen whether I am using the net or not, I feel it may take longer to happen if I am using the net via the phone over the wlan but can't really say for sure.
I have set wi-fi to never sleep in case this was the issue, (previously had been set at never sleep when charging). Power saver is set to turn on at 15% but the problem happens even if the battery is full.
I don't know if the problem is my phone or my router. My wireless router is a Zyxel P-660HW-D1, does b and g. I am using WPA2-PSK and arm on channel 6. SSID is not hidden.
I have carried out a search here and the only post I could find mentioned something to do with PEAP. I have no idea what this is. Also read up on that but it lost me tbh.
Anyone got any ideas?
Thanks for any help guys.
Click to expand...
Click to collapse
Hi there,
Just got a new HTC desire HD running 2.2. I have the same router and I have exactly the same issue.
If you find a fix please let me know.
Cheers

fingers crossed
hey chemjosh,
well I may have sorted the problem out. Currently running over three hours and no problems with browsing. Have left the phone on charge and the signal is there all the time. Although when I check the wireless settings it does say that the phone is authenticating with the router, this however does not stop my browsing!!
So I have made two changes, the answer could be either or maybe both. You can try one at a time and see how it works out for you.
The first and easiest change was to change the max frame burst. I increased it to 1000. I found it mentioned on some website that changing this might help. I tried lowering it to 300 but it made no difference, so I then increased it. Maximum Frame Burst sets the maximum time, in micro-seconds, that the ZyXEL device transmits IEEE 802.11g wireless traffic only.
This is found under network/ wireless LAN/ advanced setup.
The second change was perhaps the most obvious. I updated the firmware. This can be found on the zyxel website. I won't link as the version you use will depend on where you are. Updating is relatively easy. Just make sure you know what your ISP login details are in case you have to enter them again. I didn't, but it can't hurt to be prepared. The version I am using now is P-660HW-D1_3.40(AGL.9)C0, the router stats it is from the 12/07/2009.
To update your firmware extract the zip file you have downloaded. When on your router home/ status page, either click on ZyNOS Firmware Version: or go to Maintenance/ Tools. Just click browse and select the .bin file you have extracted from the new firmware zip file. Click upload and wait for about 5 minutes. That's it.
Since I've tried this the wireless and networks settings page on the phone still shows the phone in one of three states, either connected, authenticating or obtaining IP address. In any of these states I can still browse. Not really sure what's happening but hey it's working.
Hope this helps, I am no expert in all this but I am so hoping this is the answer. I'll post back if I have any problems. Hope it works for you too.

So as a kinda update. I am still having some issues. Occasionally I find that market or some of the sense widgets get stuck. Wifi shows it is still authenticating.
This doesn't happen when I browse the net. Can browsing reset the connection ?
Any way that's a good as I can get it for now.
If anyone has any ideas please chip in. Cheers.
Sent from my HTC Vision using XDA App

i like wifi on my phone

P-660HW-T1 v2
Man, this Post Office router have broke my heart, I swear.
I have two Samsung Galaxy S GT-i9000 devices in the house and both drop their connection with the router every couple of hours, sits at 'Authenticating'. It could be a setting in the router but geez there must be 1000 different network settings on the Router.
Here is some general router info:
Host Name: P-660HW-T1_v2
Model Number: P-660HW-T1 v2
MAC Address: xxxxxxxxxxxxx
ZyNOS Firmware Version: V3.40(BGQ.3) | 06/18/2009
WAN Information
- DSL Mode: ADSL_G.dmt
- DSL Noise Margin (Down/UP): 5 dB /19 dB
- IP Address: xxxxxxxxxxxx
- IP Subnet Mask: 255.255.255.255
- Default Gateway: N/A
- VPI/VCI: 0/38
LAN Information
- IP Address: 192.168.1.1
- IP Subnet Mask: 255.255.255.0
- DHCP: Server
WLAN Information
- SSID: xxxxxxxx
- Channel: 6
- Security: WPA2-PSK
Security
- Firewall: Enabled
- Content Filter: Disable
Might try a software upgrade as recommended above, maybe. I have a WRT300N-V1 (could flash to DD-WRT???) that I could use in bridge mode and shut wireless off on the ZyXEL.
Anyways, if anyone find a solution, other than binning the router, please let me know.
Pajo_16
BTW: I had a mate living here for a while and he a Toshiba laptop running Vista, that too had the exact same problem although there is no issues with my Dell C640 running Linux Mint Debian Edition.

OK... short one....
I have the prob as well with the zyxcel router p-660....
first a work around to make the problem less bad...
in the router config - Network->wirelessLan put the max value i.e.9999 in the field for "ReAuthentication Timer"
that makes the problem comes up "only" every 9999 sec - better than nothing...
Second:
I had the problem first back in Jan and begining of Feb than I put a CM6 nightly Rom on my HTC DHD... somehow the issue was gone I Upgraded my nightly rom from time to time and at some stage when I installed CM7 the problem came back.
Explaining the prob:
after enabling wifi it connects fine to my zyxcel router WPA2 encryption....
DHCP is running on the router and finally I would say the DHCP server/client is somehow the problem... because once the ReAuthentication Time is over the HTC DHD is ReAuthenticating all is working as expected but for some reason the HTC is not updating the status...
Result: after reauth is happening and the status not gets updated some apps still have network access - some not - some limited...
so the connection is up somehow but the DHCP lease is not valid somehow
next thing is this seems to be an issue of the combination of zyxcel and the android - also other few routers are affected by this... will try to get access to a router where I don't have this prob and pul log and see - maybe something can be figured out
sorry for this crappy explanation - I just state what I guess from seeing the log
here it is the Log - read from bottom to top:
Code:
06-01 22:02:53.010 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=7 BSSID=00:00:00:00:00:00\n
06-01 22:02:53.010 I/wpa_supplicant ( 2758): WPA: Key negotiation completed with xxxxxxxxxxxxxxxx [PTK=TKIP GTK=TKIP]\n
06-01 22:02:53.001 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=6 BSSID=00:00:00:00:00:00\n
06-01 22:02:51.120 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=6 BSSID=00:00:00:00:00:00\n
06-01 22:02:51.116 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=5 BSSID=00:00:00:00:00:00\n
06-01 22:02:49.165 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=5 BSSID=00:00:00:00:00:00\n
06-01 22:02:23.260 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=7 BSSID=00:00:00:00:00:00\n
06-01 22:02:23.260 I/wpa_supplicant ( 2758): WPA: Key negotiation completed with xxxxxxxxxxxxxxxx [PTK=TKIP GTK=TKIP]\n
06-01 22:02:23.258 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=6 BSSID=00:00:00:00:00:00\n
06-01 22:02:21.220 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=6 BSSID=00:00:00:00:00:00\n
06-01 22:02:21.210 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=5 BSSID=00:00:00:00:00:00\n
06-01 22:02:19.265 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=5 BSSID=00:00:00:00:00:00\n
[COLOR="Magenta"]Here I miss the line marked in red below[/COLOR]
06-01 22:01:53.260 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=7 BSSID=00:00:00:00:00:00\n
06-01 22:01:53.260 I/wpa_supplicant ( 2758): WPA: Key negotiation completed with xxxxxxxxxxxxxxxx [PTK=TKIP GTK=TKIP]\n
06-01 22:01:53.256 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=6 BSSID=00:00:00:00:00:00\n
06-01 22:01:51.170 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=6 BSSID=00:00:00:00:00:00\n
06-01 22:01:51.160 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=5 BSSID=00:00:00:00:00:00\n
06-01 22:01:49.365 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=5 BSSID=00:00:00:00:00:00\n
[COLOR="Red"]06-01 22:01:22.230 I/wpa_supplicant ( 2758): CTRL-EVENT-CONNECTED - Connection to 00:02:cf:95:f7:95 completed (auth) [id=0 id_str=]\n[/COLOR]
[COLOR="Magenta"]this line ^^ I miss 30 sec later when ReAuth is happening[/COLOR]
06-01 22:01:22.230 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=7 BSSID=00:00:00:00:00:00\n
06-01 22:01:22.230 I/wpa_supplicant ( 2758): WPA: Key negotiation completed with xxxxxxxxxxxxxxxx [PTK=TKIP GTK=TKIP]\n
06-01 22:01:22.230 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=6 BSSID=00:00:00:00:00:00\n
06-01 22:01:20.240 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=6 BSSID=00:00:00:00:00:00\n
06-01 22:01:20.237 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=5 BSSID=00:00:00:00:00:00\n
06-01 22:01:18.241 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=5 BSSID=00:00:00:00:00:00\n
06-01 22:01:17.020 I/wpa_supplicant ( 2758): CTRL-EVENT-DRIVER-STATE STARTED\n
06-01 22:01:16.680 I/wpa_supplicant ( 2758): Associated with 00:02:cf:95:f7:95\n
[COLOR="Magenta"]here I switch on the wifi[/COLOR]
06-01 22:01:16.680 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=0 state=4 BSSID=xxxxxxxxxxxxxxxx\n
06-01 22:01:16.560 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=xxxxxxxxxxxxxxxx\n
06-01 22:01:16.552 I/wpa_supplicant ( 2758): Trying to associate with 00:02:cf:95:f7:95 (SSID='blub' freq=2462 MHz)\n
06-01 22:01:16.065 I/wpa_supplicant ( 2758): CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00\n
Edit:
I will add a view links related to the problem...
http://code.google.com/p/android/issues/detail?id=12125
Edit: Also ich habe mich ein wenig mit der Sache.. oh english...
So I have made some tests on a different AP and so far I ruled out a few things...
As far as I understood it the wpa_supplicant is responsible/in error
The Zyxcel P-660... For the DHCP server of the router it is not possible to set the DHCP lease time
But you can set this ReAuthentication timer... as far as I understand that are 2 different things and these 2 events are handled in different way by wpa_supplicant.
if lease time is expired the client is requesting a full new lease from the DHCP server. The reauth is just a kind of confirmation that the WPA key is stil valid... somehow this way....
so wpa_supplicant handles correct if it needs a full new lease but somehow after the reauth it is not setting the Stat to connected (it is connected but it's state is still the authprocess so counted as offline) ...
Ideas: 1. I was trying to set the lease time smaller than the reauth time but in the Router I do not have the option (unable to test the idea) so if that can be setup this way, the client gets the new lease befor it is asked to reauth so if the time counter for reauth gets reseted when the client requests new lease, this should be an easy workaround
Also checked a bit if it is possible to overide the parameter for the lease/reauth time localy i.e. in the WPA_supplicant.conf - no success so far
a.t.m. i just try to get familar with the wpa_supplicant looking at it's code as this is causing the issue - I believe..
I'll update you -in case I find the problem in the code is someone here able to help me compiling it and test it? I'm a bit noob when it comes to that kind of stuff - thanks

MatteFugger said:
OK... short one....
Explaining the prob:
after enabling wifi it connects fine to my zyxcel router WPA2 encryption....
DHCP is running on the router and finally I would say the DHCP server/client is somehow the problem... because once the ReAuthentication Time is over the HTC DHD is ReAuthenticating all is working as expected but for some reason the HTC is not updating the status...
Result: after reauth is happening and the status not gets updated some apps still have network access - some not - some limited...
so the connection is up somehow but the DHCP lease is not valid somehow
Click to expand...
Click to collapse
This is it exactly. The sense apps wouldn't work for me but other apps seemed to, dolphin hd etc.
I ended up changing routers in the end. I picked up a Billion 7800N. Everything now works great, line connection speed has increased too. It's just, I now have one goddamn ugly router.

H4rry said:
This is it exactly. The sense apps wouldn't work for me but other apps seemed to, dolphin hd etc.
I ended up changing routers in the end. I picked up a Billion 7800N. Everything now works great, line connection speed has increased too. It's just, I now have one goddamn ugly router.
Click to expand...
Click to collapse
I was thinking about new router as well... fair enough the router is a peace of shine... but the router is not thr real problem - other WIFI devices i.g. my notebook is operating fine - problem is, as I think, the wpa_supplicant...
I looked a bit into the code... but it's quite huge one spread over multiple files
So far - I haven't given up yet

keeps saying 'obtaining ip addres
i installed Cyanogen Froyo CM6-Latest (based on MiniCM) - v3.03 + DualTouch
and it works every thing well but WiFi connectivity problem
it connect first time after disconnect next time It keeps saying 'obtaining ip addres from
and its never gets connected again It keeps saying 'obtaining ip addres
Google search results in many numbers of threads with this problem and no solution

mukptl said:
i installed Cyanogen Froyo CM6-Latest (based on MiniCM) - v3.03 + DualTouch
and it works every thing well but WiFi connectivity problem
it connect first time after disconnect next time It keeps saying 'obtaining ip addres from
and its never gets connected again It keeps saying 'obtaining ip addres
Google search results in many numbers of threads with this problem and no solution
Click to expand...
Click to collapse
Hi... question...
can you run the below command in a terminal window on your phone and post the output here please?
wpa_supplicant -v
it is supposed to give you the version of the wpa_supplicant installed on you phone
also please a link to/version of the rom you downloaded
Myself:
Desire HD
CM7 nightly 88 http://download.cyanogenmod.com/?type=nightly&device=ace
wpa_supplicant 6.10

MatteFugger said:
Hi... question...
can you run the below command in a terminal window on your phone and post the output here please?
wpa_supplicant -v
it is supposed to give you the version of the wpa_supplicant installed on you phone
also please a link to/version of the rom you downloaded
Myself:
Desire HD
CM7 nightly 88 http://download.cyanogenmod.com/?type=nightly&device=ace
wpa_supplicant 6.10
Click to expand...
Click to collapse
i cant run the command in a wpa_supplicant terminal window on phone
cause wen terminal window run i cant use on screen keyboard and on slide keyboard i didn't find key for _ (underscore )
i downloaded ROM from http://forum.xda-developers.com/showthread.php?t=1059361
installed version - MiniCM v3.0 with all hotfix of -v3
my is x10 mini pro

Love you to mutch guy

[Q] Bluetooth Disconnection

am connecting two external bluetooth devices to my mobile but after connecting properly one bluetooth is getting disconnected and i am getting log as
08-07 15:27:21.995: D/BLZ20_WRAPPER(4621): blz20_wrp_poll: return 1
08-07 15:27:21.995: D/BLZ20_WRAPPER(4621): blz20_wrp_read: read 0 bytes out of 1024 on fd 54
08-07 15:27:21.995: I/BLZ20_WRAPPER(4621): blz20_wrp_read: socket remotely disconnected
08-07 15:27:21.995: D/BLZ20_WRAPPER(4621): blz20_wrp_read: set errno 104 (Connection reset by peer) l.1889
08-07 15:27:22.005: E/BluetoothChatService(4621): disconnected
08-07 15:27:22.005: E/BluetoothChatService(4621): java.io.IOException: Connection reset by peer
08-07 15:27:22.005: E/BluetoothChatService(4621): at android.bluetooth.BluetoothSocket.readNative(Native Method)
08-07 15:27:22.005: E/BluetoothChatService(4621): at android.bluetooth.BluetoothSocket.read(BluetoothSocket.java:314)
08-07 15:27:22.005: E/BluetoothChatService(4621): at android.bluetooth.BluetoothInputStream.read(BluetoothInputStream.java:96)
08-07 15:27:22.005: E/BluetoothChatService(4621): at java.io.InputStream.read(InputStream.java:157)
08-07 15:27:22.005: E/BluetoothChatService(4621): at com.example.BluetoothChatService1$ConnectedThread.run(BluetoothChatService1.java:401)
Note : Recently i had this problem.. Earlier it was working good.

Netflix and Chromecast disconnect

I've just bought the Mi A1 a few days ago and so far it has been a great device. There is a major issue with Netflix and my Chromecast however.
As soon as I start casting Netflix to my Chromecast and I screen lock the A1, the Chromecast is disconnected after a bit more than one minute. The issue is also triggered when I cast from another device (which is supposed to work fine) but my Mi A1 is also connected to WiFi (and locked) during that time.
I'm on the february security update (but issue was also present with the januari security update). I've also tried setting Netflix to "Non optimized" in the battery settings and "Keep WiFi on during sleep" is set to always. Does anyone experience the same problem?
From the adb logcat it appears that Netflix is disconnected after the A1 loses its connection to WiFi.
Code:
03-03 19:21:50.897 1230 16834 E WakeLock: release without a matched acquire!
03-03 19:21:50.899 1215 1521 E CastSocket: [com.netflix.mediaclient] IOException encountered. Tearing down the socket.
03-03 19:21:50.899 1215 1521 E CastSocket: java.io.IOException: Software caused connection abort
03-03 19:21:50.899 1215 1521 E CastSocket: at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
03-03 19:21:50.899 1215 1521 E CastSocket: at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
03-03 19:21:50.899 1215 1521 E CastSocket: at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
03-03 19:21:50.899 1215 1521 E CastSocket: at sun.nio.ch.IOUtil.read(IOUtil.java:197)
03-03 19:21:50.899 1215 1521 E CastSocket: at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:419)
03-03 19:21:50.899 1215 1521 E CastSocket: at lbd.read(Unknown Source:2)
03-03 19:21:50.899 1215 1521 E CastSocket: at laa.j([email protected]@12.2.17 (448-186052348):5)
03-03 19:21:50.899 1215 1521 E CastSocket: at laj.run([email protected]@12.2.17 (448-186052348):44)
03-03 19:21:50.899 1215 1521 E CastSocket: at java.lang.Thread.run(Thread.java:764)
03-03 19:21:50.899 1230 16834 E GCM : Connection closed with errorCode 20
03-03 19:21:50.900 1215 15784 I CastDeviceController: [controller-0417-com.netflix.mediaclient API] finishDisconnecting; socketError="2 IO Error", mDisconnectStatusCode=SUCCESS
03-03 19:21:50.901 1215 15784 I CastDeviceController: [controller-0417-com.netflix.mediaclient API] listener.onDisconnected(NETWORK_ERROR)
03-03 19:21:50.901 1215 15784 I CastService: [instance-406] onDisconnected: package: com.netflix.mediaclient status=NETWORK_ERROR
03-03 19:21:50.901 2547 4623 D ConnectivityService: reportNetworkConnectivity(186, false) by 10013
03-03 19:21:50.901 2547 16786 I chatty : uid=1000 system_server expire 2 lines
03-03 19:21:50.902 1215 1521 E CastSocket: [gms_cast_mrp] IOException encountered. Tearing down the socket.
03-03 19:21:50.902 1215 1521 E CastSocket: java.io.IOException: Software caused connection abort
03-03 19:21:50.902 1215 1521 E CastSocket: at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
03-03 19:21:50.902 1215 1521 E CastSocket: at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
03-03 19:21:50.902 1215 1521 E CastSocket: at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
03-03 19:21:50.902 1215 1521 E CastSocket: at sun.nio.ch.IOUtil.read(IOUtil.java:197)
03-03 19:21:50.902 1215 1521 E CastSocket: at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:419)
03-03 19:21:50.902 1215 1521 E CastSocket: at lbd.read(Unknown Source:2)
03-03 19:21:50.902 1215 1521 E CastSocket: at laa.j([email protected]@12.2.17 (448-186052348):5)
03-03 19:21:50.902 1215 1521 E CastSocket: at laj.run([email protected]@12.2.17 (448-186052348):44)
03-03 19:21:50.902 1215 1521 E CastSocket: at java.lang.Thread.run(Thread.java:764)
03-03 19:21:50.903 2030 2234 I Netd : Destroyed 7 sockets on 2a02:1812:1d00:1f00:b81a:b8e0:d8fe:2de5 in 0.7 ms
03-03 19:21:50.903 1230 11526 V NativeCrypto: Read error: ssl=0x795a304d08: I/O error during system call, Software caused connection abort
03-03 19:21:50.904 1230 16834 E WakeLock: release without a matched acquire!
03-03 19:21:50.904 1215 1521 E CastSocket: [com.netflix.mediaclient] IOException encountered. Tearing down the socket.
03-03 19:21:50.904 1215 1521 E CastSocket: java.io.IOException: Software caused connection abort
03-03 19:21:50.904 1215 1521 E CastSocket: at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
03-03 19:21:50.904 1215 1521 E CastSocket: at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
03-03 19:21:50.904 1215 1521 E CastSocket: at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
03-03 19:21:50.904 1215 1521 E CastSocket: at sun.nio.ch.IOUtil.read(IOUtil.java:197)
03-03 19:21:50.904 1215 1521 E CastSocket: at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:419)
03-03 19:21:50.904 1215 1521 E CastSocket: at lbd.read(Unknown Source:2)
03-03 19:21:50.904 1215 1521 E CastSocket: at laa.j([email protected]@12.2.17 (448-186052348):5)
03-03 19:21:50.904 1215 1521 E CastSocket: at laj.run([email protected]@12.2.17 (448-186052348):44)
03-03 19:21:50.904 1215 1521 E CastSocket: at java.lang.Thread.run(Thread.java:764)
03-03 19:21:50.904 1215 1521 E WakeLock: release without a matched acquire!
03-03 19:21:50.907 2030 2242 D CommandListener: Clearing all IP addresses on wlan0
03-03 19:21:50.908 1215 1709 I CastService: [instance-407] Google Play services client: 11400000, Google Play services APK: 12217000
03-03 19:21:50.908 1215 1709 I CastService: [instance-407] acquireDeviceController by com.netflix.mediaclient
03-03 19:21:50.908 1215 15784 I CastDeviceController: [controller-0415-gms_cast_mrp MRP] finishDisconnecting; socketError="2 IO Error", mDisconnectStatusCode=SUCCESS
03-03 19:21:50.908 1230 13259 V NativeCrypto: Write error: ssl=0x795a304d08: I/O error during system call, Broken pipe
03-03 19:21:50.909 1215 15784 I CastDeviceController: [controller-0415-gms_cast_mrp MRP] listener.onDisconnected(NETWORK_ERROR)
I've also tried disabling battery optimization for the following apps, but it didn't have any effect.
Code:
Android Services Library
Android Shared Library
Android System
ANT HAL Service
CarrierDefaultApp
CarrierLoadService
com.qti.qualcomm.datastatusnotification
com.qualcomm.qcrilmsgtunnel
com.qualcomm.qti.networksetting
com.qualcomm.qti.qtisystemservice
com.quicinc.cne.CNEService.CNEServiceApp (probably this one, Qualcomm “Smarts” to 3G/4G Wi-Fi Seamless Interworking)
Google
Google Play Store
Google Services Framework
Home
LocationServices
Netflix
Phone and Messaging Storage
Phone Services
ProxyHandler

I have the same problem once in a while, but my wife also has the same issue with her Moto Z Play. I'm not sure this is a specific issue to the A1.

The problem is that it's almost continuous while my other Android devices don't have that issue?

Have the same issue. Did you find a solution?