Miracast disconnect in moto g7 play - Moto G7 Play Questions & Answers

Hi.
I have moto g7 play root with the instructions of the xda forum.
My tv is a lg smart tv with miracast option. Miracast work fine in the tv with my old moto g 1 lte, but no with mi moto g7 play.
In moto g7 play I had edit build.prop adding the line:
persist.debug.wfd.enable=1
I try to connect the smartphone with miracast to mirroring the screen on tv.
The connection is directly between smartphone and tv. Smartphone and tv are not connected to my local wifi.
Moto g7 play starts the connection, the tv recognice moto g7 play, but finally is disconnected from the tv. The mirroring never succeced. Sometimes the smartphone reboot itself.
At the bottom I attached log of the connection.
Any ideas about what could be the problem, and the possible solution?
Thanks in advance.
Here is the log of the moto g7 play. We can see the error connection:
***********************************************************************
12-07 00:56:30.155 W/wificond(21649): No handler for scan result notification from interface with index: 33
12-07 00:56:30.414 I/WifiDisplayController(21746): Connecting to Wifi display: [TV][LG]32LF5800-ZA
12-07 00:56:30.435 I/WifiDisplayController(21746): Initiated connection to Wifi display: [TV][LG]32LF5800-ZA
12-07 00:56:34.422 W/wificond(21649): No handler for scan result notification from interface with index: 33
12-07 00:56:34.819 W/wificond(21649): No handler for scan result notification from interface with index: 33
12-07 00:56:34.868 W/ViewRootImpl[[TV][LG]32LF5800-ZA](24065): Dropping event due to root view being removed: MotionEvent { action=ACTION_MOVE, actionButton=0, id[0]=0, x[0]=462.3329, y[0]=440.30798, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=2618298, downTime=2618291, deviceId=4, source=0x1002 }
12-07 00:56:35.218 W/wificond(21649): No handler for scan result notification from interface with index: 33
12-07 00:56:38.725 I/WifiDisplayController(21746): Connected to Wifi display: [TV][LG]32LF5800-ZA
12-07 00:56:38.725 I/WifiDisplayController(21746): Stopping Wifi display scan.
12-07 00:56:38.737 I/WifiDisplayController(21746): Listening for RTSP connection on 192.168.16.20:7236 from Wifi display: [TV][LG]32LF5800-ZA
--------- beginning of crash
12-07 00:56:38.742 E/AndroidRuntime(21746): *** FATAL EXCEPTION IN SYSTEM PROCESS: android.display
12-07 00:56:38.742 E/AndroidRuntime(21746): java.lang.IllegalStateException: Could not start listening for remote display connection on "192.168.16.20:7236"
12-07 00:56:38.742 E/AndroidRuntime(21746): at android.media.RemoteDisplay.startListening(RemoteDisplay.java:121)
12-07 00:56:38.742 E/AndroidRuntime(21746): at android.media.RemoteDisplay.listen(RemoteDisplay.java:84)
12-07 00:56:38.742 E/AndroidRuntime(21746): at com.android.server.display.WifiDisplayController.updateConnection(WifiDisplayController.java:738)
12-07 00:56:38.742 E/AndroidRuntime(21746): at com.android.server.display.WifiDisplayController.access$1200(WifiDisplayController.java:70)
12-07 00:56:38.742 E/AndroidRuntime(21746): at com.android.server.display.WifiDisplayController$15.onGroupInfoAvailable(WifiDisplayController.java:867)
12-07 00:56:38.742 E/AndroidRuntime(21746): at android.net.wifi.p2p.WifiP2pManager$Channel$P2pHandler.handleMessage(WifiP2pManager.java:878)
12-07 00:56:38.742 E/AndroidRuntime(21746): at android.os.Handler.dispatchMessage(Handler.java:106)
12-07 00:56:38.742 E/AndroidRuntime(21746): at android.os.Looper.loop(Looper.java:193)
12-07 00:56:38.742 E/AndroidRuntime(21746): at android.os.HandlerThread.run(HandlerThread.java:65)
12-07 00:56:38.742 E/AndroidRuntime(21746): at com.android.server.ServiceThread.run(ServiceThread.java:44)
12-07 00:56:39.338 I/wificond(1657): wificond is starting up...
******************************************************************

Miracast added to Revvlry+
I have rooted my Revvlry + and have added the command "persist.debug.wfd.enable=1" and my phone reboots after mirroring to Samsung TV.

Since Android Pie it's not possible to connect your phone via miracast. Google removed the libaries for it. Maybe to force the use of chromecast...

Related

[AOSP Wifi Issue] Wifi drops signal and won't reconnect

Hi everyone,
I recently moved to AOSP Roms since I'm sick of Sense and since that I'm experiencing this very weird Wifi-glitch. First of all, here's a logcat of what I get:
Code:
12-07 14:24:20.896 174 732 V WifiMonitor: Event [CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys]
12-07 14:24:20.906 174 272 V WifiStateTracker: New network state is DISCONNECTED
12-07 14:24:20.906 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:00:00:00:00:00]
12-07 14:24:20.906 174 272 V WifiStateTracker: Changing supplicant state: COMPLETED ==> DISCONNECTED
12-07 14:24:21.006 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=2 BSSID=00:00:00:00:00:00]
12-07 14:24:21.006 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> SCANNING
12-07 14:24:21.926 174 732 V WifiMonitor: Event [Trying to associate with 00:11:6b:15:9a:4a (SSID='default' freq=2457 MHz)]
12-07 14:24:21.926 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=3 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:21.936 174 272 V WifiStateTracker: Changing supplicant state: SCANNING ==> ASSOCIATING
12-07 14:24:25.686 174 732 V WifiMonitor: Event [CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys]
12-07 14:24:25.686 174 272 V WifiStateTracker: New network state is DISCONNECTED
12-07 14:24:25.716 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:25.716 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATING ==> DISCONNECTED
12-07 14:24:25.906 174 272 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:24:26.916 174 272 D WifiStateTracker: Disabling interface
12-07 14:24:31.936 174 732 V WifiMonitor: Event [Authentication with 00:00:00:00:00:00 timed out.]
12-07 14:24:31.936 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:00:00:00:00:00]
12-07 14:24:31.936 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
12-07 14:24:31.936 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> DISCONNECTED
12-07 14:24:31.936 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> SCANNING
12-07 14:24:32.866 174 732 V WifiMonitor: Event [Trying to associate with 00:11:6b:15:9a:4a (SSID='default' freq=2457 MHz)]
12-07 14:24:32.866 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:32.876 174 272 V WifiStateTracker: Changing supplicant state: SCANNING ==> ASSOCIATING
12-07 14:24:42.846 174 732 V WifiMonitor: Event [Authentication with 00:11:6b:15:9a:4a timed out.]
12-07 14:24:42.856 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:42.876 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATING ==> DISCONNECTED
12-07 14:24:42.876 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
12-07 14:24:42.876 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> SCANNING
12-07 14:24:43.716 174 732 V WifiMonitor: Event [Trying to associate with 00:11:6b:15:9a:4a (SSID='default' freq=2457 MHz)]
12-07 14:24:43.716 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:43.736 174 272 V WifiStateTracker: Changing supplicant state: SCANNING ==> ASSOCIATING
12-07 14:24:47.886 174 272 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:24:48.886 174 272 D WifiStateTracker: Disabling interface
So, from what I understand, the Wifi all of a sudden disconnects and then loops in a DHCP reset process not calling for a new ip adress. I tried using a static ip - no luck either. Anyway, when I set my wifi policy to sleep on screen off this changes the wifi state to DORMANT and when I then wake it up, it starts the DHCPhandler and grabs a new ip. Completely turning wifi off in the settings and then switching it back on has the same effect. logcat:
Code:
12-07 14:28:59.966 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATING ==> DISCONNECTED
12-07 14:28:59.966 174 272 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:29:00.966 174 272 D WifiStateTracker: Disabling interface
12-07 14:29:00.976 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> DORMANT
12-07 14:29:00.976 174 272 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:29:01.976 174 272 D WifiStateTracker: Disabling interface
12-07 14:29:02.296 174 732 V WifiMonitor: Event [CTRL-EVENT-DRIVER-STATE STOPPED]
12-07 14:29:02.306 174 272 V WifiStateTracker: Changing supplicant state: DORMANT ==> DORMANT
12-07 14:31:58.526 174 273 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:31:59.536 174 273 D WifiStateTracker: Disabling interface
12-07 14:32:00.306 174 732 V WifiMonitor: Event [CTRL-EVENT-DRIVER-STATE STARTED]
12-07 14:32:00.306 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
12-07 14:32:00.306 174 272 V WifiStateTracker: Changing supplicant state: DORMANT ==> SCANNING
12-07 14:32:00.976 174 732 V WifiMonitor: Event [Trying to associate with 00:11:6b:15:9a:4a (SSID='default' freq=2457 MHz)]
12-07 14:32:00.976 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:11:6b:15:9a:4a]
12-07 14:32:00.976 174 272 V WifiStateTracker: Changing supplicant state: SCANNING ==> ASSOCIATING
12-07 14:32:00.986 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=4 BSSID=00:11:6b:15:9a:4a]
12-07 14:32:00.996 174 732 V WifiMonitor: Event [Associated with 00:11:6b:15:9a:4a]
12-07 14:32:00.996 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=5 BSSID=00:00:00:00:00:00]
12-07 14:32:00.996 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATING ==> ASSOCIATED
12-07 14:32:00.996 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=5 BSSID=00:00:00:00:00:00]
12-07 14:32:01.006 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=6 BSSID=00:00:00:00:00:00]
12-07 14:32:01.006 174 732 V WifiMonitor: Event [WPA: Key negotiation completed with 00:11:6b:15:9a:4a [PTK=CCMP GTK=CCMP]]
12-07 14:32:01.006 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=7 BSSID=00:00:00:00:00:00]
12-07 14:32:01.006 174 732 V WifiMonitor: Event [CTRL-EVENT-CONNECTED - Connection to 00:11:6b:15:9a:4a completed (reauth) [id=0 id_str=]]
12-07 14:32:01.006 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATED ==> FOUR_WAY_HANDSHAKE
12-07 14:32:01.006 174 272 V WifiStateTracker: Changing supplicant state: FOUR_WAY_HANDSHAKE ==> FOUR_WAY_HANDSHAKE
12-07 14:32:01.006 174 272 V WifiStateTracker: Changing supplicant state: FOUR_WAY_HANDSHAKE ==> GROUP_HANDSHAKE
12-07 14:32:01.006 174 272 V WifiStateTracker: Changing supplicant state: GROUP_HANDSHAKE ==> COMPLETED
12-07 14:32:01.006 174 272 V WifiStateTracker: New network state is CONNECTED
12-07 14:32:01.026 174 734 D WifiStateTracker: DhcpHandler: DHCP request started
12-07 14:32:06.026 174 734 V WifiStateTracker: DhcpHandler: DHCP request succeeded
12-07 14:32:06.036 174 272 V WifiStateTracker: IP configuration: ipaddr 192.168.178.42 gateway 192.168.178.1 netmask 255.255.255.0 dns1 192.168.178.1 dns2 0.0.0.0 DHCP server 192.168.178.1 lease 864000 seconds
12-07 14:32:06.036 174 272 V NetworkStateTracker: Setting TCP values: [4095,87380,110208,4096,16384,110208] which comes from [net.tcp.buffersize.wifi]
I searched the interwebs myself for quite a while and came across pretty similar posts, but none of the threads contained a solution to the problem.
So, as I'm not even close to being a linux/android dev myself I kindly ask you geniuses to lent me a hand on this one, because I really started to love the clean look and amazing speed of AOSP ROMs.
Thanks in advance!
d0msen
Different behaviors on different ROMs:
CM 6, DeFrost: Connection dropping after a couple of seconds/minutes, regardless of the screen being on or off
CM 6 nightly with Vorkkernel: same as Oxygen, looks like it might be kernel related
CM 6 nightly 216 with 2.6.35.9-cyanogenmod [email protected] #10 kernel, no drops so far!
Oxygen: Connection drops after some minutes, regardless of the screen being on or off, comes back to life when DORMANT state is reached in between connection attempts, though
MUIU, Ultimate Droid: Connection stays on pretty long, can even take more than in hour till it drops, DORMANT gets it back on, WIFI is never dropping whilst the screen is on.
Sense ROMs: no reported issue till date
d0msen said:
First of all, if this isn't the right subforum to post this please move the thread to the right one, in my opinion it rather is a dev thing, as it seems to be somehow related to the core of the AOSP.
Hi everyone,
I recently moved to AOSP Roms since I'm sick of Sense and since that I'm experiencing this very weird Wifi-glitch. First of all, here's a logcat of what I get:
Code:
12-07 14:24:20.896 174 732 V WifiMonitor: Event [CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys]
12-07 14:24:20.906 174 272 V WifiStateTracker: New network state is DISCONNECTED
12-07 14:24:20.906 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:00:00:00:00:00]
12-07 14:24:20.906 174 272 V WifiStateTracker: Changing supplicant state: COMPLETED ==> DISCONNECTED
12-07 14:24:21.006 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=2 BSSID=00:00:00:00:00:00]
12-07 14:24:21.006 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> SCANNING
12-07 14:24:21.926 174 732 V WifiMonitor: Event [Trying to associate with 00:11:6b:15:9a:4a (SSID='default' freq=2457 MHz)]
12-07 14:24:21.926 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=3 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:21.936 174 272 V WifiStateTracker: Changing supplicant state: SCANNING ==> ASSOCIATING
12-07 14:24:25.686 174 732 V WifiMonitor: Event [CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys]
12-07 14:24:25.686 174 272 V WifiStateTracker: New network state is DISCONNECTED
12-07 14:24:25.716 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:25.716 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATING ==> DISCONNECTED
12-07 14:24:25.906 174 272 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:24:26.916 174 272 D WifiStateTracker: Disabling interface
12-07 14:24:31.936 174 732 V WifiMonitor: Event [Authentication with 00:00:00:00:00:00 timed out.]
12-07 14:24:31.936 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:00:00:00:00:00]
12-07 14:24:31.936 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
12-07 14:24:31.936 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> DISCONNECTED
12-07 14:24:31.936 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> SCANNING
12-07 14:24:32.866 174 732 V WifiMonitor: Event [Trying to associate with 00:11:6b:15:9a:4a (SSID='default' freq=2457 MHz)]
12-07 14:24:32.866 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:32.876 174 272 V WifiStateTracker: Changing supplicant state: SCANNING ==> ASSOCIATING
12-07 14:24:42.846 174 732 V WifiMonitor: Event [Authentication with 00:11:6b:15:9a:4a timed out.]
12-07 14:24:42.856 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:42.876 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATING ==> DISCONNECTED
12-07 14:24:42.876 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
12-07 14:24:42.876 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> SCANNING
12-07 14:24:43.716 174 732 V WifiMonitor: Event [Trying to associate with 00:11:6b:15:9a:4a (SSID='default' freq=2457 MHz)]
12-07 14:24:43.716 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:43.736 174 272 V WifiStateTracker: Changing supplicant state: SCANNING ==> ASSOCIATING
12-07 14:24:47.886 174 272 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:24:48.886 174 272 D WifiStateTracker: Disabling interface
So, from what I understand, the Wifi all of a sudden disconnects and then loops in a DHCP reset process not calling for a new ip adress. I tried using a static ip - no luck either. Anyway, when I set my wifi policy to sleep on screen off this changes the wifi state to DORMANT and when I then wake it up, it starts the DHCPhandler and grabs a new ip. Completely turning wifi off in the settings and then switching it back on has the same effect. logcat:
Code:
12-07 14:28:59.966 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATING ==> DISCONNECTED
12-07 14:28:59.966 174 272 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:29:00.966 174 272 D WifiStateTracker: Disabling interface
12-07 14:29:00.976 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> DORMANT
12-07 14:29:00.976 174 272 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:29:01.976 174 272 D WifiStateTracker: Disabling interface
12-07 14:29:02.296 174 732 V WifiMonitor: Event [CTRL-EVENT-DRIVER-STATE STOPPED]
12-07 14:29:02.306 174 272 V WifiStateTracker: Changing supplicant state: DORMANT ==> DORMANT
12-07 14:31:58.526 174 273 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:31:59.536 174 273 D WifiStateTracker: Disabling interface
12-07 14:32:00.306 174 732 V WifiMonitor: Event [CTRL-EVENT-DRIVER-STATE STARTED]
12-07 14:32:00.306 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
12-07 14:32:00.306 174 272 V WifiStateTracker: Changing supplicant state: DORMANT ==> SCANNING
12-07 14:32:00.976 174 732 V WifiMonitor: Event [Trying to associate with 00:11:6b:15:9a:4a (SSID='default' freq=2457 MHz)]
12-07 14:32:00.976 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:11:6b:15:9a:4a]
12-07 14:32:00.976 174 272 V WifiStateTracker: Changing supplicant state: SCANNING ==> ASSOCIATING
12-07 14:32:00.986 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=4 BSSID=00:11:6b:15:9a:4a]
12-07 14:32:00.996 174 732 V WifiMonitor: Event [Associated with 00:11:6b:15:9a:4a]
12-07 14:32:00.996 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=5 BSSID=00:00:00:00:00:00]
12-07 14:32:00.996 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATING ==> ASSOCIATED
12-07 14:32:00.996 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=5 BSSID=00:00:00:00:00:00]
12-07 14:32:01.006 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=6 BSSID=00:00:00:00:00:00]
12-07 14:32:01.006 174 732 V WifiMonitor: Event [WPA: Key negotiation completed with 00:11:6b:15:9a:4a [PTK=CCMP GTK=CCMP]]
12-07 14:32:01.006 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=7 BSSID=00:00:00:00:00:00]
12-07 14:32:01.006 174 732 V WifiMonitor: Event [CTRL-EVENT-CONNECTED - Connection to 00:11:6b:15:9a:4a completed (reauth) [id=0 id_str=]]
12-07 14:32:01.006 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATED ==> FOUR_WAY_HANDSHAKE
12-07 14:32:01.006 174 272 V WifiStateTracker: Changing supplicant state: FOUR_WAY_HANDSHAKE ==> FOUR_WAY_HANDSHAKE
12-07 14:32:01.006 174 272 V WifiStateTracker: Changing supplicant state: FOUR_WAY_HANDSHAKE ==> GROUP_HANDSHAKE
12-07 14:32:01.006 174 272 V WifiStateTracker: Changing supplicant state: GROUP_HANDSHAKE ==> COMPLETED
12-07 14:32:01.006 174 272 V WifiStateTracker: New network state is CONNECTED
12-07 14:32:01.026 174 734 D WifiStateTracker: DhcpHandler: DHCP request started
12-07 14:32:06.026 174 734 V WifiStateTracker: DhcpHandler: DHCP request succeeded
12-07 14:32:06.036 174 272 V WifiStateTracker: IP configuration: ipaddr 192.168.178.42 gateway 192.168.178.1 netmask 255.255.255.0 dns1 192.168.178.1 dns2 0.0.0.0 DHCP server 192.168.178.1 lease 864000 seconds
12-07 14:32:06.036 174 272 V NetworkStateTracker: Setting TCP values: [4095,87380,110208,4096,16384,110208] which comes from [net.tcp.buffersize.wifi]
I searched the interwebs myself for quite a while and came across pretty similar posts, but none of the threads contained a solution to the problem.
So, as I'm not even close to being a linux/android dev myself I kindly ask you geniuses to lent me a hand on this one, because I really started to love the clean look and amazing speed of AOSP ROMs.
Thanks in advance!
d0msen
Click to expand...
Click to collapse
+1, getting this issue on Oxygen and CM ROM but not with Ultimate Droid.
getting the same since i changed to supervillain hd rom. before that, everything was ok.
Alright so I tried some other ROMs this afternoon and can confirm that Ultimate Droid does not have these wifi glitches.
Apart from that, MIUI has the problem, but somehow manages to stay connected longer than Oxygen or CM and it never occurred to me, that MIUI would drop the connection, while the screen is on.
Tested both ROMs with Wifi policy set to sleep on screen off and dynamic ip. Hope this helps
EDIT: Ultimate Droid just dropped the connection as well, looks like it's pretty similar to MIUI network-wise.
I have had this happen constantly since the earliest CM6 builds on my university (eduroam; wpa2 enterprise) network. If data's not being used constantly, wifi will die in 2-20 minutes and then needs to be toggled off and on before it reconnects again. Massive pain in the bum. My home wifi is fine.
The stock 2.1 ROM did not seem to have this problem. I've seen these issues brought up several times in here and on IRC - they appear to occur on non-standard network setups. I vaguely recall someone saying it had to do with Android trying to re-establish an idling connection after the security token had expired but, rather than re-authenticating properly, the system just keeps making requests with the invalid token. Someone also suggested it's something to do with migrating between access points on a multi-AP network. Not sure if this is at all accurate, but it would be nice to see this issue fixed.
Kinda not diggin my thread being moved without even giving a reason for that.
because maybe it doesn't belong in android development.. you're not developing anything?
Anyone else feel like this started some time around 2.2.1?
I'm having a similar glitch on Eduroam (PEAP + MSCHAPv2) networks...
since only few people have this problem, i suggest checking if its connected to your wlan access points. if you got a linux box with wlan card (or boot from a live cd), enter
Code:
iwlist [wlan device] scanning
to get a list of wlan devices, type
Code:
iwconfig
here is the output for my wlan, which does NOT drop (policy wifi never off - the battery killer)
Code:
Cell 03 - Address: ***DELETED***
Channel:10
Frequency:2.457 GHz (Channel 10)
Quality=67/70 Signal level=-43 dBm
Encryption key:on
ESSID:"wtf"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=00000000061f3181
Extra: Last beacon: 348ms ago
IE: Unknown: 0003777466
IE: Unknown: 010882848B0C12961824
IE: Unknown: 03010A
IE: Unknown: 2A0100
IE: Unknown: 32043048606C
IE: Unknown: DD180050F20201010A0002A3400027A4000042435E0062322F00
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: Unknown: DD0900037F01010024FF7F
breakdown: WPA2 with CCMP, max 54MBit on channel 10
reported a similir bug by me to cyanogen at october 29
http://code.google.com/p/cyanogenmod/issues/detail?id=2431
but no solution yet
I no longer have this issue with CM-216 but I did have it with about CM-200 and earlier (didn't use in between).
My iwlist output is:
Code:
Cell 01 - Address: ---------
Protocol:802.11b/g/n
ESSID:"Epa"
Mode:Managed
Channel:8
Quality:86/100 Signal level:-56 dBm Noise level:-81 dBm
Encryption key:on
Bit Rates:18 Mb/s
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PS
My radio is 32.49.00.32U_5.11.05.27
After two days of testing I can confirm that Wifi works flawlessly with the CM nightly 216! Something must have been changed in between 215 and 216 =)

Wifi acting very weird on my Desire

Hi,
I'm having wifi problems on my Desire. I can no longer connect to wifi. When i turn my wifi on it turns itself off after about 15 seconds.
Sometimes i see the message: Obtaining IP address and then it turns itself off.
I've tried the "FXR WiFi fix and rescue" app and sometimes it fixes my wifi and i'm gold. But the next day or a couple of hours later the wifi no longer works.
Flashing a new radio doesn't help, deleting the wpa_supplicant.conf file sometimes works.
I'm currently running Mildwild CM 4.5. Have tried many other roms but to no avail.
Anyone experiencing the same problems?
thank you !
Tried rebooting your wifi hotspot or router?
What is your current radio? You could maybe change your ril? Do you have good 3G, calls signal etc?
Also, check your WiFi sleep policy, and set it to never. Perhaps try changing channels on your router.
Spierbal said:
Tried rebooting your wifi hotspot or router?
What is your current radio? You could maybe change your ril? Do you have good 3G, calls signal etc?
Also, check your WiFi sleep policy, and set it to never. Perhaps try changing channels on your router.
Click to expand...
Click to collapse
Rebooted my router, tried another router, have the same problem at work or at my parents.
I have radio 5.11.05.27, have tried numerous other radio's too. Wifi sleep policy is set to never.
I have good reception on 3g and call signal.
Is there a way you view a detailed log to find out where the wifi flips?
sypack said:
Rebooted my router, tried another router, have the same problem at work or at my parents.
I have radio 5.11.05.27, have tried numerous other radio's too. Wifi sleep policy is set to never.
I have good reception on 3g and call signal.
Is there a way you view a detailed log to find out where the wifi flips?
Click to expand...
Click to collapse
On the day of the occurence did something change? your router, your phone, new tariff, reach the maximum number of connections. Did you do any updates, flashing new rom etc. Maybe there was a update to your router ISP?
In terms of logging, this can be really good way to find out what happening behind the scenes.
If you got ADB installed, plug your phone in usb, enable usb debugging mode. Once this is done, type the following command:
adb logcat
This should initiate the logcat and your command prompt will begin to fill with a bunch of text.
Once the logcat is running, please RECREATE the wifi issue you are having. to stop the logcat on your keyboard press ctrl+c.
If you don't understand the text, you can right click, choose select all then press enter on your keyboard, this will copy the entire log to the clipboard. Once this is complete visit www.pastebin.com and paste your log there and submit. Then grab the link from the address bar and paste it on xda forum with your bug.
Finally, if you are not comfortable with command prompt, install alogcat or logcat app in the play store.
I'll try logcat when i get home tonight.
OK, ran logcat on my computer here at work.
This is what it spat out:
Code:
--------- beginning of /dev/log/main
D/dalvikvm( 597): GC_EXPLICIT freed <1K, 45% free 3897K/6983K, external 0K/0K, paused 74ms
D/dalvikvm( 364): GC_EXPLICIT freed 14K, 51% free 2818K/5639K, external 0K/0K, paused 68ms
D/SettingsAppWidgetProvider( 668): Widget is from a previous version... Let's update
D/SettingsAppWidgetProvider( 668): No instances yet... Wait for at least one instance to exist before adding global settings
E/wpa_supplicant( 2723): ioctl[SIOCGIFFLAGS]
E/wpa_supplicant( 2723): ioctl[SIOCSIWPMKSA]
E/wpa_supplicant( 2723): ioctl[SIOCSIWMODE]
E/wpa_supplicant( 2723): ioctl[SIOCGIRANGE]
E/wpa_supplicant( 2723): ioctl[SIOCGIWMODE]
E/wpa_supplicant( 2723): ioctl[SIOCSIWAP]
E/wpa_supplicant( 2723): ioctl[SIOCSIWENCODEEXT]
E/wpa_supplicant( 2723): ioctl[SIOCSIWENCODE]
E/wpa_supplicant( 2723): ioctl[SIOCSIWENCODEEXT]
E/wpa_supplicant( 2723): ioctl[SIOCSIWENCODE]
E/wpa_supplicant( 2723): ioctl[SIOCSIWENCODEEXT]
E/wpa_supplicant( 2723): ioctl[SIOCSIWENCODE]
E/wpa_supplicant( 2723): ioctl[SIOCSIWENCODEEXT]
E/wpa_supplicant( 2723): ioctl[SIOCSIWENCODE]
I/wpa_supplicant( 2723): CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00:00:00
E/wpa_supplicant( 2723): Failed to disable WPA in the driver.
E/wpa_supplicant( 2723): ioctl[SIOCGIWMODE]
E/wpa_supplicant( 2723): ioctl[SIOCSIWAP]
E/wpa_supplicant( 2723): ioctl[SIOCGIFFLAGS]
D/wifi ( 235): wifi doCommand: ret=-1
D/WifiStateTracker( 235): Reset connections and stopping DHCP
--------- beginning of /dev/log/system
W/ActivityManager( 235): Timeout of broadcast BroadcastRecord{40b46b48 android.net.wifi.WIFI_STATE_CHANGED} - [email protected], started 10007ms ago
W/ActivityManager( 235): Receiver during timeout: ResolveInfo{4069aa50 com.android.settings.widget.SettingsAppWidgetProvider p=0 o=0 m=0x108000}
I/Process ( 235): Sending signal. PID: 668 SIG: 3
I/dalvikvm( 668): threadid=4: reacting to signal 3
I/dalvikvm( 668): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 235): Sending signal. PID: 235 SIG: 3
I/dalvikvm( 235): threadid=4: reacting to signal 3
I/dalvikvm( 235): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 235): Sending signal. PID: 327 SIG: 3
I/dalvikvm( 327): threadid=4: reacting to signal 3
I/dalvikvm( 327): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 235): Sending signal. PID: 308 SIG: 3
I/dalvikvm( 308): threadid=4: reacting to signal 3
I/dalvikvm( 308): Wrote stack traces to '/data/anr/traces.txt'
D/dalvikvm( 235): GC_EXPLICIT freed 958K, 43% free 6285K/10887K, external 6395K/7516K, paused 69ms
E/ActivityManager( 235): ANR in com.android.settings
E/ActivityManager( 235): Reason: Broadcast of Intent { act=android.net.wifi.WIFI_STATE_CHANGED flg=0x10000000 cmp=com.android.settings/.widget.SettingsAppWidgetProvider (has extras) }
E/ActivityManager( 235): Load: 2.36 / 2.18 / 2.14
E/ActivityManager( 235): CPU usage from 9090ms to 0ms ago:
E/ActivityManager( 235): 1.6% 191/akmd: 0% user + 1.6% kernel
E/ActivityManager( 235): 0.8% 235/system_server: 0.3% user + 0.5% kernel / faults: 3 minor
E/ActivityManager( 235): 0.2% 2705/kworker/0:1: 0% user + 0.2% kernel
E/ActivityManager( 235): 0% 6/rcu_kthread: 0% user + 0% kernel
E/ActivityManager( 235): 0% 68/yaffs-bg-1: 0% user + 0% kernel
E/ActivityManager( 235): 0.1% 327/com.android.phone: 0% user + 0.1% kernel
E/ActivityManager( 235): 2.8% TOTAL: 0% user + 2.8% kernel
E/ActivityManager( 235): CPU usage from 367ms to 882ms later:
E/ActivityManager( 235): 3.8% 235/system_server: 3.8% user + 0% kernel
E/ActivityManager( 235): 5.7% 253/ActivityManager: 5.7% user + 0% kernel
E/ActivityManager( 235): 1.4% 191/akmd: 0% user + 1.4% kernel
E/ActivityManager( 235): 1.4% 2715/akmd: 0% user + 1.4% kernel
E/ActivityManager( 235): 1.9% TOTAL: 1.9% user + 0% kernel
D/WifiStateTracker( 235): Disabling interface
D/dalvikvm( 235): GC_FOR_MALLOC freed 542K, 45% free 6089K/10887K, external 4578K/5716K, paused 94ms
D/wifi ( 235): wifi doCommand: ret=-1
D/wifi ( 235): wifi doCommand: ret=-1
D/wifi ( 235): wifi doCommand: ret=-1
D/SettingsAppWidgetProvider( 668): Widget is from a previous version... Let's update
D/SettingsAppWidgetProvider( 668): No instances yet... Wait for at least one instance to exist before adding global settings
I/dalvikvm( 668): Jit: resizing JitTable from 4096 to 8192
W/ActivityManager( 235): finishReceiver called but no pending broadcasts
D/wifi ( 235): wifi doCommand: ret=-1
D/wifi ( 235): wifi doCommand: ret=-1
D/wifi ( 235): wifi doCommand: ret=-1
D/wifi ( 235): wifi doCommand: ret=-1
W/InputManagerService( 235): Window already focused, ignoring focus gain of: [email protected]
E/WifiHW ( 235): Supplicant not running, cannot connect
D/wifi ( 235): wifi doCommand: ret=-1
D/wifi ( 235): wifi doCommand: ret=-1
D/wifi ( 235): wifi doCommand: ret=-1
D/wifi ( 235): wifi doCommand: ret=-1
E/WifiHW ( 235): Supplicant not running, cannot connect
D/wifi ( 235): wifi doCommand: ret=-1
D/wifi ( 235): wifi doCommand: ret=-1
D/wifi ( 235): wifi doCommand: ret=-1
D/wifi ( 235): wifi doCommand: ret=-1
E/WifiHW ( 235): Supplicant not running, cannot connect
V/WifiStateTracker( 235): Supplicant died unexpectedly
D/WifiStateTracker( 235): Reset connections and stopping DHCP
D/WifiStateTracker( 235): Disabling interface
W/MessageQueue( 235): null sending message to a Handler on a dead thread
W/MessageQueue( 235): java.lang.RuntimeException: null sending message to a Handler on a dead thread
W/MessageQueue( 235): at android.os.MessageQueue.enqueueMessage(MessageQueue.java:196)
W/MessageQueue( 235): at android.os.Looper.quit(Looper.java:192)
W/MessageQueue( 235): at android.net.wifi.WifiStateTracker.handleMessage(WifiStateTracker.java:986)
W/MessageQueue( 235): at android.os.Handler.dispatchMessage(Handler.java:99)
W/MessageQueue( 235): at android.os.Looper.loop(Looper.java:130)
W/MessageQueue( 235): at com.android.server.ConnectivityService$ConnectivityThread.run(ConnectivityService.java:234)
D/WifiStateTracker( 235): Reset connections and stopping DHCP
D/SettingsAppWidgetProvider( 668): Widget is from a previous version... Let's update
D/SettingsAppWidgetProvider( 668): No instances yet... Wait for at least one instance to exist before adding global settings
D/WifiStateTracker( 235): Disabling interface
D/SettingsAppWidgetProvider( 668): Widget is from a previous version... Let's update
D/SettingsAppWidgetProvider( 668): No instances yet... Wait for at least one instance to exist before adding global settings
Looks like "E/WifiHW ( 235): Supplicant not running, cannot connect" is what causing the trouble....
If you already tried different kernels, I am afraid you might have to reflash back to stock, if it still happens, lock your bootloader and send it back. I am sorry I could not be of more assistance.
Your help is much appreciated.
Sending it back is no option, cannot live without a smartphone
Going to stick with the mobile connection and buy a new Nexus round christmass.

Screen Cast resolution

So today I noticed on my sammy tv it accepts wifi screen mirroring at 720p 30hz/fps but via slimport I get 1080p at 60hz/fps no lag, the wifi screen mirroring lags / skips like crazy rendering it useless for movies or gaming it's only good for pictures and music, i'm guessing this is a bandwidth issue, is their anyway to transmit in 480p instead?
Anybody? i'm still non the wiser other than it using something called wifidisplaysource.
08-23 10:53:38.994 I/WifiDisplayController(596): Starting Wifi display scan.
08-23 10:53:39.014 D/PhoneStatusBar(676): disable: < expand icons alerts ticker* system_info* back home recent clock search >
08-23 10:53:39.254 I/wpa_supplicant(685): P2P-DEVICE-FOUND 92:f1:aa:32:93:d9 p2p_dev_addr=92:f1:aa:32:93:d9 pri_dev_type=7-0050F204-1 name='[TV] Samsung' config_methods=0x188 dev_capab=0x25 group_capab=0x0 wfd_dev_info=0x00000601110000012c
08-23 10:53:40.435 I/wpa_supplicant(685): P2P-FIND-STOPPED
08-23 10:53:40.435 I/WifiDisplayController(596): Connecting to Wifi display: [TV] Samsung
08-23 10:53:40.455 I/wpa_supplicant(685): P2P-INVITATION-RESULT status=0
08-23 10:53:40.465 I/WifiDisplayController(596): Initiated connection to Wifi display: [TV] Samsung
08-23 10:53:40.525 V/PhoneStatusBar(676): setLightsOn(true)
08-23 10:53:40.555 I/wpa_supplicant(685): rfkill: Cannot open RFKILL control device
08-23 10:53:40.655 E/wpa_supplicant(685): Using interface p2p-p2p0-0 with hwaddr ae:22:0b:9f:f4:f3 and ssid "DIRECT-2L-Android_c095"
08-23 10:53:40.655 W/wpa_supplicant(685): Device is trying to offload WPS Probe Response while not supporting this
08-23 10:53:40.655 W/wpa_supplicant(685): Device is trying to offload P2P Probe Response while not supporting this
08-23 10:53:40.685 I/wpa_supplicant(685): p2p-p2p0-0: CTRL-EVENT-CONNECTED - Connection to ae:22:0b:9f:f4:f3 completed (auth) [id=0 id_str=]
08-23 10:53:40.685 I/wpa_supplicant(685): P2P-GROUP-STARTED p2p-p2p0-0 GO ssid="DIRECT-2L-Android_c095" freq=2412 passphrase="nomx4mdA" go_dev_addr=ae:22:0b:9f:74:f3 [PERSISTENT]
08-23 10:53:40.695 D/CommandListener(176): Setting iface cfg
08-23 10:53:40.695 D/CommandListener(176): Trying to bring up p2p-p2p0-0
08-23 10:53:40.705 D/TetherController(176): Starting tethering services
08-23 10:53:40.705 D/TetherController(176): Tethering services running
08-23 10:53:40.705 D/WifiP2pService(596): Started Dhcp server on p2p-p2p0-0
08-23 10:53:40.705 I/dnsmasq (524): started, version 2.51 cachesize 150
08-23 10:53:40.705 I/dnsmasq (524): compile time options: no-IPv6 GNU-getopt no-DBus no-I18N DHCP no-scripts no-TFTP
08-23 10:53:40.705 W/dnsmasq (524): warning: no upstream servers configured
08-23 10:53:40.705 I/dnsmasq (524): DHCP, IP range 192.168.49.2 -- 192.168.49.254, lease time 1h
08-23 10:53:40.705 I/dnsmasq (524): read /etc/hosts - 1 addresses
08-23 10:53:41.006 D/dalvikvm(32756): GC_CONCURRENT freed 10866K, 52% free 10169K/21072K, paused 1ms+4ms, total 30ms
08-23 10:53:50.625 W/wpa_supplicant(685): Device is trying to offload WPS Probe Response while not supporting this
08-23 10:53:50.625 W/wpa_supplicant(685): Device is trying to offload P2P Probe Response while not supporting this
08-23 10:53:50.635 I/wpa_supplicant(685): p2p-p2p0-0: AP-STA-CONNECTED 92:f1:aa:32:93:d9 p2p_dev_addr=92:f1:aa:32:93:d9
08-23 10:53:50.635 I/wpa_supplicant(685): AP-STA-CONNECTED 92:f1:aa:32:93:d9 p2p_dev_addr=92:f1:aa:32:93:d9
08-23 10:53:50.635 I/WifiDisplayController(596): Connected to Wifi display: [TV] Samsung
08-23 10:53:50.635 I/WifiDisplayController(596): Stopping Wifi display scan.
08-23 10:53:50.645 I/WifiDisplayController(596): Listening for RTSP connection on 192.168.49.1:7236 from Wifi display: [TV] Samsung
08-23 10:53:53.218 I/dnsmasq (524): DHCPDISCOVER(p2p-p2p0-0) 92:f1:aa:32:93:d9
08-23 10:53:53.218 I/dnsmasq (524): DHCPOFFER(p2p-p2p0-0) 192.168.49.228 92:f1:aa:32:93:d9
08-23 10:53:53.288 I/dnsmasq (524): DHCPREQUEST(p2p-p2p0-0) 192.168.49.228 92:f1:aa:32:93:d9
08-23 10:53:53.288 I/dnsmasq (524): DHCPACK(p2p-p2p0-0) 192.168.49.228 92:f1:aa:32:93:d9
08-23 10:53:53.768 I/NetworkSession(181): incoming connection from 192.168.49.228:46286 (socket 48)
08-23 10:53:53.768 I/NetworkSession(181): added clientSession 2
08-23 10:53:53.768 I/WifiDisplaySource(181): We now have a client (2) connected.
08-23 10:53:53.958 I/WifiDisplaySource(181): Picked video resolution 1280 x 720 p30
08-23 10:53:53.958 I/WifiDisplaySource(181): Picked AVC profile 1, level 1
08-23 10:53:53.958 I/WifiDisplaySource(181): Using AAC audio.
08-23 10:53:53.988 W/linker (181): libDxHdcp.so has text relocations. This is wasting memory and is a security risk. Please fix.
08-23 10:53:53.988 I/WifiDisplaySource(181): Initiating HDCP negotiation w/ host 192.168.49.228:9999
08-23 10:53:53.988 I/WifiDisplaySource(181): Deferring SETUP trigger until HDCP initialization completes.
08-23 10:53:54.008 D/QSEECOMAPI: (181): QSEECom_start_app sb_length = 0x1000
08-23 10:53:54.008 D/QSEECOMAPI: (181): App is not loaded in QSEE
08-23 10:53:54.028 D/QSEECOMAPI: (181): Loaded image: APP id = 2
08-23 10:53:54.068 I/DxHDCPModule(181): Session opened
08-23 10:53:54.078 D/dalvikvm(32756): GC_CONCURRENT freed 581K, 53% free 9987K/21072K, paused 2ms+4ms, total 34ms
08-23 10:53:54.369 I/DxHDCPModule(181): Tsmt connected
08-23 10:53:57.372 I/DxHDCPModule(181): Success initing lib
08-23 10:53:57.372 I/WifiDisplaySource(181): Saw HDCP notification code 0, ext1 0, ext2 0
08-23 10:53:57.462 E/OMX-VENC-720p(181):
08-23 10:53:57.462 E/OMX-VENC-720p(181): Is component secure 0
08-23 10:53:57.492 I/Converter(181): using audio bitrate of 128000 bps, video bitrate of 5000000 bps
08-23 10:53:57.492 E/OMX-VENC-720p(181): set_parameter: metamode is valid for input port only
08-23 10:53:57.492 E/OMXNodeInstance(181): OMX_SetParameter() failed for StoreMetaDataInBuffers: 0x80001019
08-23 10:53:57.492 E/ACodec (181): [OMX.qcom.video.encoder.avc] storeMetaDataInBuffers (output) failed w/ err -2147483648
08-23 10:53:57.492 E/OMX-VENC-720p(181):
08-23 10:53:57.492 E/OMX-VENC-720p(181): WARNING: Unsupported Color format [2130708361]
08-23 10:53:57.492 E/OMX-VENC-720p(181):
08-23 10:53:57.492 E/OMX-VENC-720p(181): C2D init is successful
08-23 10:53:57.492 E/OMX-VENC-720p(181):
08-23 10:53:57.492 E/OMX-VENC-720p(181): WARNING: Unsupported Color format [2130708361]
08-23 10:53:57.492 E/OMX-VENC-720p(181):
08-23 10:53:57.492 E/OMX-VENC-720p(181): venc_set_intra_period: nPFrames = 450 nBFrames = 0
08-23 10:53:57.492 I/ACodec (181): setupVideoEncoder succeeded
08-23 10:53:57.512 I/r_submix(181): adev_open_input_stream()
08-23 10:53:57.512 E/OMX-VENC-720p(181):
08-23 10:53:57.512 E/OMX-VENC-720p(181): Allocated virt:0xb2491000, FD: 83 of size 1433600 at index: 0
08-23 10:53:57.512 E/OMX-VENC-720p(181):
08-23 10:53:57.512 E/OMX-VENC-720p(181): Allocated virt:0xb2333000, FD: 85 of size 1433600 at index: 1
08-23 10:53:57.522 I/r_submix(181): in_standby()
08-23 10:53:57.522 I/r_submix(181): in_standby()
08-23 10:53:57.522 I/Converter(181): using audio bitrate of 128000 bps, video bitrate of 5000000 bps
08-23 10:53:57.552 E/MonoPipe(181): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
08-23 10:53:57.552 I/AudioFlinger(181): HAL output buffer size 1024 frames, normal mix buffer size 1024 frames
08-23 10:53:57.552 I/AudioMixer(181): found effect "Downmixer" from Fraunhofer IIS
08-23 10:53:57.552 I/AudioFlinger(181): HAL output buffer size 1024 frames, normal mix buffer size 1024 frames
08-23 10:53:57.552 I/AudioMixer(181): found effect "Downmixer" from Fraunhofer IIS
08-23 10:53:57.552 I/AudioFlinger(181): AudioFlinger's thread 0xb1ea9008 ready to run
08-23 10:53:57.552 I/AudioFlinger(181): AudioFlinger's thread 0xb1fe8008 ready to run
08-23 10:53:57.552 I/r_submix(181): out_standby()
08-23 10:53:57.562 D/audio_hw_primary(181): out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=0
08-23 10:53:57.562 D/audio_hw_primary(181): out_set_parameters: enter: usecase(0: deep-buffer-playback) kvpairs: routing=0
08-23 10:53:57.592 I/WifiDisplaySource(181): Received PLAY request.
08-23 10:53:57.592 I/WifiDisplaySource(181): deferring PLAY request until session established.
08-23 10:53:57.592 I/WifiDisplayController(596): Opened RTSP connection with Wifi display: [TV] Samsung
08-23 10:53:57.602 I/DisplayManagerService(596): Display device added: DisplayDeviceInfo{"[TV] Samsung": 1280 x 720, 60.0 fps, density 213, 213.0 x 213.0 dpi, touch EXTERNAL, rotation 0, type WIFI, address 92:f1:aa:32:93:d9, FLAG_SECURE, FLAG_PRESENTATION}
08-23 10:53:57.622 I/InputReader(596): Reconfiguring input devices. changes=0x00000004
08-23 10:53:57.622 E/OMX-VENC-720p(181):
08-23 10:53:57.622 E/OMX-VENC-720p(181): open Color conv for RGBA888
I have had the same problem before. I think Google has not added support for 480p 1080p Casting so you will have to wait till they update it sadly.
I found a reference to some fallback resolution of 360p, hmmm
https://android.googlesource.com/pl...efright/wifi-display/sink/WifiDisplaySink.cpp
http://forum.xda-developers.com/showpost.php?p=47216957&postcount=6
this guy managed to enable a few extra options including 1080p

[Q] Wifi association (CyanogenMod)

Hi,
I have a strange problem occuring only on my university wifi whereas everything works fine at home.
I can't associate with the SSID, I see it but can't connect.
Here is a logcat but i don't see anything useful:
I/wpa_supplicant(16369): wlan0: CTRL-EVENT-SCAN-STARTED
I/wpa_supplicant(16369): wlan0: CTRL-EVENT-SSID-REENABLED id=4 ssid="WIFI-UP"
I/wpa_supplicant(16369): wlan0: Trying to associate with SSID 'WIFI-UP'
D/CommandListener( 233): Clearing all IP addresses on wlan0I/wpa_supplicant(16369): wlan0: CTRL-EVENT-ASSOC-REJECT bssid=00:15:70:ab:6a:c9 status_code=1
I/wpa_supplicant(16369): wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=4 ssid="WIFI-UP" auth_failures=1 duration=10
This is a hotspot SSID and I get the exact same error with an authenticated SSID.

WiFi frequently drops

Running MicroG/LineageOS 16 on H4113 (dual SIM), WiFi generally works ok but frequently drops out when the system is under load; eg. connecting a call. Making a WhatsApp call I experience this every 5-10 minutes.
I was able to capture a log. NL8022_CMD_DISCONNECT seems to be what sets the whole thing off, but I don't have any experience with this. This originates from the hardware? Or is some part of Android telling the wifi to switch off? It seems fairly explicit rather than loss of signal etc.
Code:
RTM_NEWLINK: ifi_index=26 ifname=wlan0 wext ifi_family=0 ifi_flags=0x1043 ([UP][RUNNING])
RTM_NEWLINK: ifi_index=26 ifname=wlan0 operstate=2 linkmode=1 ifi_family=0 ifi_flags=0x1003 ([UP])
nl80211: Drv Event 48 (NL80211_CMD_DISCONNECT) received for wlan0
nl80211: Disconnect event
wlan0: Event DEAUTH (11) received
wlan0: Deauthentication notification
wlan0: * reason 1
Deauthentication frame IE(s) - hexdump(len=0): [NULL]
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:1e:2a:10:e8:5b reason=1
wlan0: Auto connect disabled: do not try to re-connect
wlan0: Ignore connection failure indication since interface has been put into disconnected state
TDLS: Remove peers on disassociation
wlan0: WPA: Clear old PMK and PTK
Notifying disconnect reason to hidl control: 1
wlan0: Disconnect event - remove keys
nl80211: Data frame filter flags=0x0
nl80211: Failed to open /proc/sys/net/ipv4/conf/wlan0/drop_unicast_in_l2_multicast: No such file or directory
nl80211: Failed to set IPv4 unicast in multicast filter
wlan0: State: COMPLETED -> DISCONNECTED
nl80211: Set wlan0 operstate 1->0 (DORMANT)
netlink: Operstate: ifindex=26 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
Notifying state change event to hidl control: 0
Notifying bssid changed to hidl control
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
nl80211: Skip set_supp_port(unauthorized) while not associated
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
nl80211: set_p2p_powersave (legacy_ps=1 opp_ps=-1 ctwindow=-1)
...
Other devices play fine on the WiFi network and signal strength is good. I've experimented with the various WiFi settings in the Android UI and they don't seem to have an effect.

Categories

Resources