Related
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
Hey all, so this afternoon I was sitting in my living room and somehow my 4G got turned on, and I happen to look at my phone and it was popping up 4G Network Avail. I was like no way, something is wrong. So I looked some more and sure enough it was trying to connect. It would say "Connecting to Sprint" for about 1 -2 seconds then a real quick disconnted, and back to scanning and it just repeats this over and over. I had to go out and about this evening and left the 4G on and it kept doing it out and about too. At one point it stayed on the "Connecting to Sprint" for like 10 seconds and then went back to scanning.
So I'm thinking there is a site nearby and maybe it is not accepting users yet, but man this is exciting. If anyone lives in the IE, let me know if you found any spots. My location is off the 71 fwy and Phillips. Also off of the 71 and Rio Rancho it woudl see it there as well.
--Steve
PS - Here is a logcat of when it is trying to connect.
D/CIQ ( 729): throwUI12
D/WimaxStateTracker( 262): wimaxRescan
D/WimaxStateTracker( 262): wimaxRescan: set force scan flag
D/WimaxStateTracker( 262): wimaxRescan : CBES::forceScanning reset-state=0
W/InputManagerService( 262): Window already focused, ignoring focus gain of: co
[email protected]
D/WimaxStateTracker( 262): GetAvailableMs
I/Wimax ( 262): Ndss: ScanRoundCompleted
I/WimaxStateTracker( 262): NdsRoundCompleteNotification +-
D/WimaxStateTracker( 262): NdsRoundCompleteNotification: BsFound: 0
D/WimaxStateTracker( 262): GetAvailableMs
I/Wimax ( 262): Ndss: Scan Bs Found (Ext Band)
I/WimaxStateTracker( 262): NdsBsFoundExtBandNotification: bandIdx:3 freqIdx:1 p
bIdx:64 napId:2 rssi:-7698 cinr:2374 cinrR1:1606 cinrR3:2107
D/WimaxStateTracker( 262): NdsBsFoundNotification: no data connection or only h
ave 1xRTT or force scan, connect to WIMAX ASAP
D/WimaxStateTracker( 262): Wimax.ConnectToNetworkExt(bandId=3, freqId=1, pbId=6
4, napId=2)
V/WimaxStateTracker( 262): NdsAutodetectEnterCriteriaExtBandNotification: bandI
dx:3 freqIdx:1 pbIdx:64 napId:2 rssi:-7698 cinrR1:1606
V/WimaxStateTracker( 262): add Meet Entry BS into List
D/WimaxStateTracker( 262): GetAvailableMs
D/dalvikvm( 361): GC_EXPLICIT freed 262 objects / 10736 bytes in 67ms
I/Wimax ( 262): Ndss: NdsStateChange, state = 2
V/WimaxStateTracker( 262): NdsStateNotification, state = 2
I/WimaxStateTracker( 262): Ssstate = UL_ACQUISITION
D/WimaxInfo( 262): getDetailedStateBySsState: ssState=DL_SYNCHRONIZATION dState
=SCANNING
D/WimaxInfo( 262): getDetailedStateBySsState: ssState=UL_ACQUISITION dState=CON
NECTING
D/WimaxStateTracker( 262): setDetailedState = CONNECTING
D/WimaxStateTracker( 262): isAvailable
D/WimaxInfo( 262): getDetailedStateBySsState: ssState=UL_ACQUISITION dState=CON
NECTING
I/Wimax ( 262): Dbg: >>>> 0560.820 s - SPY/Ss - UL ACQUISITION
D/HtcWimaxStatusBar( 262): receiver intent, aciton:com.htc.net.wimax.STATE_CHAN
GE
D/HtcWimaxStatusBar( 262): WiMAX Signal Strength changed: 0
D/HtcWimaxStatusBar( 262): WiMAX State:CONNECTING
V/HtcWimaxStatusBar( 262): info.getDetailedState():CONNECTING
D/HtcWimaxStatusBar( 262): Update WiMAX Signal Status Bar, Signal = 0
D/WimaxSettings( 729): received NETWORK_STATE_CHANGED_ACTION, getDetailedState:
CONNECTING
V/WimaxEnabler( 729): onReceive: com.htc.net.wimax.STATE_CHANGE
D/WimaxEnabler( 729): handle Network State Changed Action
I/WimaxEnabler( 729): DetailedState: CONNECTING
D/WimaxStateTracker( 262): set idle timer to 60s
D/WimaxStateTracker( 262): psms:changeidleautodelay 60sec
D/WimaxStateTracker( 262): disableDhcp
D/NetUtils( 262): ifc_get_info addr=0 !
D/ ( 262): <jni> com_htc_net_wimax_StopDhcpWimax
D/ ( 262): <dhcp> startDhcpWimaxDaemon daemon is stopped
D/ConnectivityService( 262): ConnectivityChange for WIMAX: CONNECTING/CONNECTIN
G
V/WimaxReceiver( 729): onReceive(), action:com.htc.net.wimax.STATE_CHANGE
V/WimaxReceiver( 729): Settings.Secure.WIMAX_NETWORKS_AVAILABLE_NOTIFICATION_ON
:1
V/WimaxReceiver( 729): detailedState:CONNECTING
I/LSState ( 262): EventReceiver:android.intent.action.NOTIFICATION_ADD
I/WimaxStateTracker( 262): Ssstate = RANGING
D/WimaxInfo( 262): getDetailedStateBySsState: ssState=UL_ACQUISITION dState=CON
NECTING
D/WimaxInfo( 262): getDetailedStateBySsState: ssState=RANGING dState=CONNECTING
D/WimaxStateTracker( 262): isAvailable
D/WimaxInfo( 262): getDetailedStateBySsState: ssState=RANGING dState=CONNECTING
I/Wimax ( 262): Dbg: >>>> 0562.330 s - SPY/Ss - RANGING
D/HtcWimaxStatusBar( 262): receiver intent, aciton:com.htc.net.wimax.STATE_CHAN
GE
D/HtcWimaxStatusBar( 262): WiMAX Signal Strength changed: 0
D/HtcWimaxStatusBar( 262): WiMAX State:CONNECTING
V/HtcWimaxStatusBar( 262): info.getDetailedState():CONNECTING
D/HtcWimaxStatusBar( 262): Update WiMAX Signal Status Bar, Signal = 0
D/WimaxSettings( 729): received NETWORK_STATE_CHANGED_ACTION, getDetailedState:
CONNECTING
V/WimaxEnabler( 729): onReceive: com.htc.net.wimax.STATE_CHANGE
D/WimaxEnabler( 729): handle Network State Changed Action
I/WimaxEnabler( 729): DetailedState: CONNECTING
D/WimaxStateTracker( 262): set idle timer to 60s
D/WimaxStateTracker( 262): psms:changeidleautodelay 60sec
D/WimaxStateTracker( 262): disableDhcp
D/NetUtils( 262): ifc_get_info addr=0 !
D/ ( 262): <jni> com_htc_net_wimax_StopDhcpWimax
D/ ( 262): <dhcp> startDhcpWimaxDaemon daemon is stopped
V/WimaxReceiver( 729): onReceive(), action:com.htc.net.wimax.STATE_CHANGE
V/WimaxReceiver( 729): Settings.Secure.WIMAX_NETWORKS_AVAILABLE_NOTIFICATION_ON
:1
V/WimaxReceiver( 729): detailedState:CONNECTING
I/Wimax ( 262): Dbg: >>>> 0562.420 s - SPY/Sf - bidirectional basic SF add: s
fid=0 cid=723 bcid=723 said=65535 state=active
I/LSState ( 262): EventReceiver:android.intent.action.NOTIFICATION_UPDATE
I/Wimax ( 262): Dbg: >>>> 0562.430 s - SPY/Sf - bidirectional primary SF add:
sfid=0 cid=979 bcid=723 said=65535 state=active
I/WimaxStateTracker( 262): Ssstate = CAPABILITIES_NEGOTIATION
D/WimaxInfo( 262): getDetailedStateBySsState: ssState=RANGING dState=CONNECTING
D/WimaxInfo( 262): getDetailedStateBySsState: ssState=CAPABILITIES_NEGOTIATION
dState=CONNECTING
D/WimaxStateTracker( 262): isAvailable
I/Wimax ( 262): Dbg: #!!# WARN: 0562.440 s - RNGS/Ss - Unknown DIUC 0
I/Wimax ( 262): Dbg: >>>> 0562.440 s - SPY/Ss - CAPABILITIES NEGOTIATION
D/WimaxStateTracker( 262): GetAvailableMs
D/WimaxStateTracker( 262): newSignalStrength=-77
D/HtcWimaxStatusBar( 262): receiver intent, aciton:com.htc.net.wimax.RSSI_CHANG
ED
D/HtcWimaxStatusBar( 262): WiMAX Signal Strength changed: 2
V/HtcWimaxStatusBar( 262): info.getDetailedState():CONNECTING
D/HtcWimaxStatusBar( 262): Update WiMAX Signal Status Bar, Signal = 2
V/WimaxReceiver( 729): onReceive(), action:com.htc.net.wimax.RSSI_CHANGED
V/WimaxReceiver( 729): Settings.Secure.WIMAX_NETWORKS_AVAILABLE_NOTIFICATION_ON
:1
D/dalvikvm( 262): GC_FOR_MALLOC freed 19437 objects / 1530528 bytes in 130ms
I/Wimax ( 262): Dbg: #!!# WARN: 0562.980 s - RNGS/Ss - Ranging response with
ABORT status => abort
I/Wimax ( 262): Ndss: NdsStateChange, state = 0
V/WimaxStateTracker( 262): NdsStateNotification, state = 0
I/Wimax ( 262): Ndss: NdsStateChange, state = 1
V/WimaxStateTracker( 262): NdsStateNotification, state = 1
I/WimaxStateTracker( 262): Ssstate = ABORTED
D/WimaxInfo( 262): getDetailedStateBySsState: ssState=CAPABILITIES_NEGOTIATION
dState=CONNECTING
D/WimaxInfo( 262): getDetailedStateBySsState: ssState=ABORTED dState=DISCONNECT
ED
D/WimaxStateTracker( 262): setDetailedState = DISCONNECTED
D/WimaxStateTracker( 262): DISCONNECTED: reset socket on wimax0
D/NetUtils( 262): ifc_get_info addr=0 !
I/WimaxStateTracker( 262): Ssstate = DL_SYNCHRONIZATION
I/Wimax ( 262): Dbg: >>>> 0563.040 s - SPY/Sf - bidirectional primary SF dele
te: sfid=0 cid=979 bcid=723 said=65535 state=active
D/WimaxStateTracker( 262): isAvailable
I/Wimax ( 262): Dbg: >>>> 0563.040 s - SPY/Sf - bidirectional basic SF delete
: sfid=0 cid=723 bcid=723 said=65535 state=active
D/WimaxStateTracker( 262): disableDhcp
E/WimaxStateTracker( 262): skip release Dhcp
D/NetUtils( 262): ifc_get_info addr=0 !
I/Wimax ( 262): Dbg: >>>> 0563.040 s - SPY/Ss - ABORTED
I/Wimax ( 262): Dbg: >>>> 0563.040 s - SPY/Ss - DL SYNCHRONIZATION
D/ ( 262): <jni> com_htc_net_wimax_StopDhcpWimax
D/ ( 262): <dhcp> startDhcpWimaxDaemon daemon is stopped
D/WimaxStateTracker( 262): set idle timer to 60s
D/WimaxStateTracker( 262): psms:changeidleautodelay 60sec
D/WimaxInfo( 262): getDetailedStateBySsState: ssState=ABORTED dState=DISCONNECT
ED
D/HtcWimaxStatusBar( 262): receiver intent, aciton:com.htc.net.wimax.STATE_CHAN
GE
D/HtcWimaxStatusBar( 262): WiMAX Signal Strength changed: 2
D/HtcWimaxStatusBar( 262): WiMAX StateISCONNECTED
V/HtcWimaxStatusBar( 262): info.getDetailedState()ISCONNECTED
D/HtcWimaxStatusBar( 262): Update WiMAX Signal Status Bar, Signal = 2
D/WimaxSettings( 729): received NETWORK_STATE_CHANGED_ACTION, getDetailedState:
DISCONNECTED
V/WimaxEnabler( 729): onReceive: com.htc.net.wimax.STATE_CHANGE
D/WimaxEnabler( 729): handle Network State Changed Action
I/WimaxEnabler( 729): DetailedState: DISCONNECTED
D/ConnectivityService( 262): ConnectivityChange for WIMAX: DISCONNECTED/DISCONN
ECTED
D/ConnectivityService( 262): getMobileDataEnabled returning true
D/ConnectivityService( 262): adding dns 68.28.58.92 for mobile
D/WimaxService( 262): onReceive ConnectivityService CONNECTIVITY_ACTION type=WI
MAX[], state=DISCONNECTED
D/Tethering( 262): Tethering got CONNECTIVITY_ACTION
E/Tethering( 262): >>>>>connectivity changed<<<<<
E/Tethering( 262): type: WIMAX, connected: false
D/ConnectivityService( 262): adding dns 68.28.50.91 for mobile
D/Tethering( 262): MasterInitialState.processMessage what=3
E/HierarchicalStateMachine( 262): TetherMaster - unhandledMessage: msg.what=3
D/WimaxInfo( 262): getDetailedStateBySsState: ssState=ABORTED dState=DISCONNECT
ED
D/WimaxInfo( 262): getDetailedStateBySsState: ssState=DL_SYNCHRONIZATION dState
=SCANNING
D/WimaxStateTracker( 262): isAvailable
D/WimaxInfo( 262): getDetailedStateBySsState: ssState=DL_SYNCHRONIZATION dState
=SCANNING
V/htcCheckinService( 262): Connectivity changed, scheduling alarm
V/htcCheckinService( 262): Network down, checkin is disabled
D/Tethering( 262): Tethering got CONNECTIVITY_ACTION
E/Tethering( 262): >>>>>connectivity changed<<<<<
E/Tethering( 262): type: mobile, connected: true
D/Tethering( 262): MasterInitialState.processMessage what=3
E/HierarchicalStateMachine( 262): TetherMaster - unhandledMessage: msg.what=3
V/htcCheckinService( 262): Connectivity changed, scheduling alarm
V/htcCheckinService( 262): Network up, next checkin in 1205086s, repeating ever
y 1206000s
D/HtcWimaxStatusBar( 262): receiver intent, aciton:com.htc.net.wimax.RSSI_CHANG
ED
D/HtcWimaxStatusBar( 262): WiMAX Signal Strength changed: 0
V/HtcWimaxStatusBar( 262): info.getDetailedState():SCANNING
D/HtcWimaxStatusBar( 262): Update WiMAX Signal Status Bar, Signal = 0
D/HtcWimaxStatusBar( 262): receiver intent, aciton:com.htc.net.wimax.STATE_CHAN
GE
D/HtcWimaxStatusBar( 262): WiMAX Signal Strength changed: 0
D/HtcWimaxStatusBar( 262): WiMAX State:SCANNING
V/HtcWimaxStatusBar( 262): info.getDetailedState():SCANNING
D/HtcWimaxStatusBar( 262): Update WiMAX Signal Status Bar, Signal = 0
V/AlarmManager( 262): Adding Alarm{46745800 type 0 com.android.providers.htcChe
ckin} Aug 31 09:17:35 pm
V/WimaxReceiver( 729): onReceive(), action:com.htc.net.wimax.STATE_CHANGE
V/WimaxReceiver( 729): Settings.Secure.WIMAX_NETWORKS_AVAILABLE_NOTIFICATION_ON
:1
V/WimaxReceiver( 729): detailedStateISCONNECTED
V/NotificationService( 262): Charging for Hero ...
E/lights ( 262): write ok string=1,len=1
E/lights ( 262): write ok string=0,len=1
E/lights ( 262): write ok string=0 0,len=3
E/lights ( 262): write ok string=0,len=1
E/lights ( 262): write ok string=0,len=1
V/ConnLib ( 597): isConnected:false
E/lights ( 262): write ok string=0 0,len=3
I/LSState ( 262): EventReceiver:android.intent.action.NOTIFICATION_REMOVE
D/NotificationService( 262): cancelNotification, ACTION_NOTIFICATION_REMOVE,pkg
=com.android.settings,id=2130837626
D/WimaxSettings( 729): received NETWORK_STATE_CHANGED_ACTION, getDetailedState:
SCANNING
V/WimaxEnabler( 729): onReceive: com.htc.net.wimax.STATE_CHANGE
D/WimaxEnabler( 729): handle Network State Changed Action
I/WimaxEnabler( 729): DetailedState: SCANNING
V/ConnLib ( 597): isConnectedOrConnecting:false
I/GTalkService( 412): [ServiceAutoStarter] --- connectivity changed
I/GTalkService( 412): [ServiceAutoStarter] --- start GTalk service ---
D/GTalkService( 412): [GTalkService.1] onStartCommand: found 0 connections, for
ce audit connections...
V/ConnLib ( 597): getExtraInfo:null
V/ConnLib ( 597): getSubtype:0
V/htcMessageUploader( 604): [UploadMessageReceiver] UploadMessageReceiver() con
structor !!!
I/htcMessageUploader( 604): Start thread to upload fota event message:com.htc.h
tcMessageUploader.UploadMessageReceiver
I/MediaUploader( 747): No need to wake up
D/GoogleLoginService( 412): onBind: Intent { act=android.accounts.AccountAuthen
ticator cmp=com.google.android.gsf/.loginservice.GoogleLoginService }
W/GoogleLoginService( 412): Device has no accounts: sending Intent { act=com.go
ogle.android.gsf.LOGIN_ACCOUNTS_MISSING }
V/ConnLib ( 597): getSubtypeName:
D/GTalkService( 412): [GTalkService.46] account missing
V/ConnLib ( 597): getReason:null
V/ConnLib ( 597): getType:6
D/NetSharing_NSReceiver( 729): onReceive : android.net.conn.CONNECTIVITY_CHANGE
V/AutoSetting( 506): receiver - ***onReceive: android.net.conn.CONNECTIVITY_CHA
NGE
D/NetSharing_NSReceiver( 729): netinfo : NetworkInfo: type: mobile[CDMA - EvDo
rev. A], state: CONNECTED/CONNECTED, reason: apnSwitched, extra: (none), roaming
: false, failover: true, isAvailable: true, if: rmnet0
D/AutoSetting( 506): receiver - ***Data call is avaiable
V/ConnLib ( 597): getTypeName:WIMAX
D/AutoSetting( 506): *****fireNow=false
V/AutoSetting( 506): receiver - scheduleLocation, action: android.net.conn.CONN
ECTIVITY_CHANGE, runImmediately: false
V/ConnLib ( 597): isConnected:true
D/SocialUpdate( 506): Start SocialUpdate service with android.net.conn.CONNECTI
VITY_CHANGE
V/AutoSetting( 506): receiver - Next check location in 10135s, repeating every
10800s
V/AlarmManager( 262): Adding Alarm{4673aba8 type 0 com.htc.htclocationservice}
Aug 18 01:21:44 am
D/SocialUpdate( 506): UpdateService onCreate START. time: 2010-08-17 22:32:49
D/UploadManager( 497): Action android.net.conn.CONNECTIVITY_CHANGE
D/SocialUpdate( 506): UpdateService onCreate END. time: 2010-08-17 22:32:49
V/WimaxReceiver( 729): onReceive(), action:com.htc.net.wimax.RSSI_CHANGED
V/WimaxReceiver( 729): Settings.Secure.WIMAX_NETWORKS_AVAILABLE_NOTIFICATION_ON
:1
V/ConnLib ( 597): isConnectedOrConnecting:true
V/WimaxReceiver( 729): onReceive(), action:com.htc.net.wimax.STATE_CHANGE
V/WimaxReceiver( 729): Settings.Secure.WIMAX_NETWORKS_AVAILABLE_NOTIFICATION_ON
:1
V/WimaxReceiver( 729): detailedState:SCANNING
I/htcMessageUploader( 604): == UploadMessageReceiver finished ==
V/ConnLib ( 597): getExtraInfo:null
V/ConnLib ( 597): getSubtype:6
V/ConnLib ( 597): getSubtypeName:CDMA - EvDo rev. A
V/ConnLib ( 597): getReason:apnSwitched
V/ConnLib ( 597): getType:0
V/ConnLib ( 597): getTypeName:mobile
I/ConnLib ( 597): default data call is connected
D/GpsLocationProvider( 262): updateNetworkState available info: NetworkInfo: ty
pe: mobile[CDMA - EvDo rev. A], state: CONNECTED/CONNECTED, reason: apnSwitched,
extra: (none), roaming: false, failover: true, isAvailable: true, if: rmnet0
D/UploadNotification( 497): updateNotification1
D/UploadNotification( 497): item =null
D/UploadService( 497): UpdateThread is looping
V/AlarmManager( 262): Adding Alarm{468218f8 type 0 com.google.android.gsf} Aug
23 11:02:02 pm
D/UploadService( 497): mUpload.size 0
D/UploadService( 497): 2updateNotification no batch id
D/UploadNotification( 497): updateNotification1
D/UploadNotification( 497): item =null
D/UploadService( 497): UpdateThread is looping
D/UploadService( 497): mUpload.size 0
D/UploadService( 497): 2updateNotification no batch id
D/UploadNotification( 497): updateNotification1
D/UploadNotification( 497): item =null
D/UploadService( 497): UpdateThread is looping
^C
Click to expand...
Click to collapse
It should connect in the next week to two weeks... same happened where I live in oc...
Sent from my second wife using swype on xda app
That would be nice......
Sent from my PC36100 using XDA App
I'm in Fontana I haven't tried it yet because I'm using cm6 and it has no 4g but last time I went to West Covina and I picked up 4g there
Sent from my PC36100 using XDA App
So I was able to connect to 4g. I kinda think the tower is on the hills where the 57 and 10 are. Where I live in Pomona, we are up on a hill that over looks pomona and we have a road that circles the entire hill, I drove around it and on one point right near the 71 fwy It connected. I did a few speed tests and the fastest one was over 7Mbps down...however going back to my house a few hundred yards away it just see's it but will not connect....
I was driving through Pomona a couple weeks ago on the 71 and got 9mbps down on 4G.
Yeah I think Sprint is rolling out WiMax in greater LA area.
It used to be I won't get WiMax until I get close to downtown, now at home in SoPa/Alhambra, I get decent WiMax signal. And there is actually no signal in Pasadena lol.
Earlier this week when I was in San Gabriel, my Evo sticked in WiMax most of the time.
It's good to hear and see WiMax being rolled out in greater LA!
A friend of mine claims to have 4G in Anaheim down to Santa Ana, but not in Irvine yet.
I can confirm i've picked up 4g several times as I drive through pomona on the 10freeway between fairplex and like gary. Could be you're picking it up from this area but the signal is just weak.
When i do pick it up in that area its full bars. I'm running Cyanogen ROM currently with no 4G so havent tested it in like a month..
i picked up 4G near john wayne airport down to south coast plaza driving down the 405
Gary and foothill has 4g
Sent from my PC36100 using XDA App
verse187 said:
I'm in Fontana I haven't tried it yet because I'm using cm6 and it has no 4g but last time I went to West Covina and I picked up 4g there
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Hello, we're neighbors! I'm in Southridge. I haven't begun testing 4G yet, but I am now. I'll subscribe this thread and try to look out for the IE.
About two months ago, our company's Sprint rep told us 4g would be available to us within the next few months...I thought he was full of crap.....Hesperia. So far no 4g yet, but I'd imagine if the I.E. is starting to get it, were not far behind.
I'm now able to get the 4g in my house....man its fast...over 10Mbps....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nothing off of Jurupa and Cherry in Fontucky! Waiting ever so patiently...
bigrushdog said:
Hello, we're neighbors! I'm in Southridge. I haven't begun testing 4G yet, but I am now. I'll subscribe this thread and try to look out for the IE.
Click to expand...
Click to collapse
That's good too know neighboureno lol
Sent from my PC36100 using XDA App
4G
I picked up 4g in pomona by South Campus Dr and Temple. Speedtest 7mbs and I also picked up 4g in campus of cal poly pomona.
Three is 4g in the long beach and westwood area.
Sent from my PC36100 using XDA App
Nothing in Redlands yet. C'mon Sprint,
still no damn signal in Pasadena, but i'm moving to San Diego tomorrow, anyone know if there's 4g there?
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
Hi all,
I was wondering what was killing my battery so I used adb logcat and found that it has something to do with GoogleTagManager. Take a look here:
Code:
03-02 21:15:15.149 28959 29036 W GoogleTagManager: Connection refused
03-02 21:15:15.151 28959 29036 W GoogleTagManager: Exception sending hit: ConnectException
03-02 21:15:15.151 28959 29036 W GoogleTagManager: Connection refused
03-02 21:15:15.152 28959 29036 W GoogleTagManager: Exception sending hit: ConnectException
03-02 21:15:15.152 28959 29036 W GoogleTagManager: Connection refused
03-02 21:15:15.153 28959 29036 W GoogleTagManager: Exception sending hit: ConnectException
03-02 21:15:15.153 28959 29036 W GoogleTagManager: Connection refused
03-02 21:15:15.154 28959 29036 W GoogleTagManager: Exception sending hit: ConnectException
03-02 21:15:15.154 28959 29036 W GoogleTagManager: Connection refused
It goes on like that for thousands of lines.
I've noticed that disabling ad blocking fixes the issue, and that force stopping Allo will cause it to temporarily stop until Allo is reopened. Does anyone have any idea what's going on or how to fix it?
Thanks!
https://forum.xda-developers.com/v20/how-to/adaway-results-googletagmanager-t3537046
Whitelist googletagmanager.com and/or googletagservices.com in AdAway, kill the Allo process (if it has a background process) and it should go away. Looks like Google Play Music (which I had issues with, and Allo) have hooks that send some kind of data back to Google when they're being used, but when AdAway blocks them it just keeps trying to reconnect indefinitely, causing high CPU usage/battery drain.
Hello,
I got the following phone:
Moto G Pure | 2021 | 2-Day battery | Unlocked | Made for US by Motorola | 3/32GB | 13MP Camera | Deep Indigo
https://www.amazon.com/gp/product/B09BTB5MKT/
It has an Android 11 installed. The phone is typically connected to the local WiFi network and can reach 300mbps download/20mbps upload speeds when running the speedtest app.
I noticed that sometimes (once every few days or couple of weeks) the phone stops reacting to downloading new data from the internet.
So If I try to go to chrome browser and load a page, it would load the page forever. The WiFi icon will still show as it's connected to the WiFi and connected to the network. If I try to do a speedtest, the app would be stuck and not start downloading everything.
If I try to toggle the WiFi on and off, or use the cellular it doesn't seem to resolve the issue always, typically this would require a reboot of the phone.
I also noticed that sometimes this issue is even worst, when the cellular would stop working too, so if I send text messages to the phone, and go to the messages app, the new messages wouldn't show, neither the cellular internet would work or it will be really slow.
One time, I ran into this issue with the "internet freeze" when I configured a VPN (software-defined mesh virtual private network), and I set the VPN to always be on in settings, the internet still worked, but when I tried to reboot the phone, although the VPN got automatically connected as expected after reboot, it went into the "internet freeze", and only way I was able to resolve it is when I turned the VPN off. Still, the VPN by itself shouldn't be an issue with the internet still working, as evident when I turned on the VPN when the internet was already working and no problem there, but somehow the turn VPN always might have been the trigger point to the get "internet freeze" issue. Previous times the issue happened, I didn't run any VPNs so I'm suspecting there could be multiple trigger points that could cause this issue.
When I spoke with Motorola tech support, there wasn't really much troubleshooting other than making sure the software is up to date and keeping track of when the issue happens or how often. They did show me how to generate a bug report, so when the issue happens again, I could send it to them for further investigation. I was able to get bug report when the issue happened today - Actually Android automatically identified that there was an issue and generated the report. I know it might have some private sensitive information so I might not want to share it, but are there parts in it that I could safely share? For example, in the file dumpstate_log.txt when I search for the word "wifi" I can see this message repeatedly:
######################################################################
Warning: Skipping "[email protected]::ISupplicant/default": cannot be fetched from service manager (null)
and similar messages to it such as:
Warning: Skipping "[email protected]::IAllocator/ashmem": cannot be fetched from service manager (null)
######################################################################
Here are some other suspicious lines:
######################################################################
*** command 'lshal debug -E [email protected]::ISupplicant/default' failed: exit code 128
[email protected]::IAllocator/ashmem does not exist, or no permission to connect.
*** command 'lshal debug -E [email protected]::IMtkRadioEx/mtkRsu1' failed: exit code 128
[email protected]::IMtkRadioEx/mtkSe1 does not exist, or no permission to connect.
######################################################################
In file bugreport-ellis_retail-RRHS31.Q3-46-123-5-2-2023-05-28-20-41-03 I'm seeing these suspicious lines:
######################################################################
05-28 20:19:43.501 1000 1431 1459 W ActivityManager: Slow operation: 88ms so far, now at startProcess: returned from zygote!
05-28 20:19:43.501 1000 1431 1459 W ActivityManager: Slow operation: 88ms so far, now at startProcess: done updating battery stats
05-28 20:19:43.501 1000 1431 1459 W ActivityManager: Slow operation: 88ms so far, now at startProcess: building log message
05-28 20:19:45.625 1000 1431 1431 W Looper : Slow dispatch took 104ms main h=com.android.server.job.JobSchedulerService$JobHandler c=null m=4
05-28 20:20:34.311 1000 1431 1459 W ActivityManager: Slow operation: 272ms so far, now at startProcess: starting to update pids map
05-28 20:20:34.314 1000 1431 1459 W ActivityManager: Slow operation: 275ms so far, now at startProcess: done updating pids ma
######################################################################
Is there anything in particular in the log I should look for? I see there are additional folders such as FS, lshal-debug, proto.
I'm mostly interested to know what causes the phone to go into "internet freeze" issue - How can this issue be prevented all together, is there some setting or something? Is this a common issue with this phone or with Android? Did this happen with your phone too?
Thanks.