[已回复] 请教MobileIMSDK在红米手机熄屏，过一会打开出现的异常的疑问

使用官方安卓demo，官方服务器，红米手机登录账号后，熄屏一会儿自动断开重连，亮屏后一直出现waring，但是不影响使用



日志信息：
2019-02-25 19:56:03.899 7132-7248/? W/zygote64: Current owner stack:
2019-02-25 19:56:03.900 7132-7248/? W/zygote64:     at java.net.DatagramPacket.setData(DatagramPacket.java:-1)
2019-02-25 19:56:03.900 7132-7248/? W/zygote64:     at java.net.DatagramPacket.<init>(DatagramPacket.java:79)
2019-02-25 19:56:03.900 7132-7248/? W/zygote64:     at java.net.DatagramPacket.<init>(DatagramPacket.java:95)
2019-02-25 19:56:03.900 7132-7248/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.udpListeningImpl(LocalUDPDataReciever.java:174)
2019-02-25 19:56:03.900 7132-7248/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:49)
2019-02-25 19:56:03.900 7132-7248/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:132)
2019-02-25 19:56:03.900 7132-7248/? W/zygote64:     at java.lang.Thread.run(Thread.java:764)
2019-02-25 19:56:03.900 7132-7248/? W/zygote64: Contender stack:
2019-02-25 19:56:03.900 7132-7248/? W/zygote64:     at java.net.DatagramSocket.receive(DatagramSocket.java:-1)
2019-02-25 19:56:03.900 7132-7248/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.udpListeningImpl(LocalUDPDataReciever.java:181)
2019-02-25 19:56:03.900 7132-7248/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:49)
2019-02-25 19:56:03.900 7132-7248/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:132)
2019-02-25 19:56:03.900 7132-7248/? W/zygote64:     at java.lang.Thread.run(Thread.java:764)
2019-02-25 19:56:04.799 622-634/? I/mmid: select timeout: wait for receiving msg
2019-02-25 19:56:06.842 7132-7162/? D/KeepAliveDaemon: 【IMCORE】心跳线程执行中...
2019-02-25 19:56:06.903 7132-7132/? D/LocalUDPDataReciever: 【IMCORE】收到服务端回过来的Keep Alive心跳响应包.
2019-02-25 19:56:06.904 7132-7250/? W/zygote64: Long monitor contention with owner Thread-2 (7194) at void java.net.DatagramSocket.receive(java.net.DatagramPacket)(DatagramSocket.java:-1) waiters=2 in void java.net.DatagramSocket.receive(java.net.DatagramPacket) for 9.011s
2019-02-25 19:56:06.904 7132-7250/? W/zygote64: Current owner stack:
2019-02-25 19:56:06.904 7132-7250/? W/zygote64:     at java.net.DatagramSocket.getImpl(DatagramSocket.java:371)
2019-02-25 19:56:06.904 7132-7250/? W/zygote64:     at java.net.DatagramSocket.receive(DatagramSocket.java:847)
2019-02-25 19:56:06.904 7132-7250/? W/zygote64:   - locked <0x0ae7fcf7> (a java.net.DatagramSocket)
2019-02-25 19:56:06.904 7132-7250/? W/zygote64:   - locked <0x07cde583> (a java.net.DatagramPacket)
2019-02-25 19:56:06.905 7132-7250/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.udpListeningImpl(LocalUDPDataReciever.java:181)
2019-02-25 19:56:06.905 7132-7250/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:49)
2019-02-25 19:56:06.905 7132-7250/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:132)
2019-02-25 19:56:06.905 7132-7250/? W/zygote64:     at java.lang.Thread.run(Thread.java:764)
2019-02-25 19:56:06.905 7132-7250/? W/zygote64: Contender stack:
2019-02-25 19:56:06.905 7132-7250/? W/zygote64:     at java.net.DatagramSocket.receive(DatagramSocket.java:-1)
2019-02-25 19:56:06.905 7132-7250/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.udpListeningImpl(LocalUDPDataReciever.java:181)
2019-02-25 19:56:06.905 7132-7250/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:49)
2019-02-25 19:56:06.905 7132-7250/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:132)
2019-02-25 19:56:06.905 7132-7250/? W/zygote64:     at java.lang.Thread.run(Thread.java:764)
2019-02-25 19:56:07.803 622-634/? I/mmid: select timeout: wait for receiving msg
2019-02-25 19:56:07.828 7132-7165/? D/QoS4SendDaemon: 【IMCORE】【QoS】=========== 消息发送质量保证线程运行中, 当前需要处理的列表长度为0...
2019-02-25 19:56:09.848 7132-7164/? D/KeepAliveDaemon: 【IMCORE】心跳线程执行中...
2019-02-25 19:56:09.911 7132-7132/? D/LocalUDPDataReciever: 【IMCORE】收到服务端回过来的Keep Alive心跳响应包.
2019-02-25 19:56:09.912 7132-7247/? W/zygote64: Long monitor contention with owner Thread-2 (7194) at void java.net.DatagramSocket.receive(java.net.DatagramPacket)(DatagramSocket.java:-1) waiters=2 in void java.net.DatagramSocket.receive(java.net.DatagramPacket) for 9.013s
2019-02-25 19:56:09.912 7132-7247/? W/zygote64: Current owner stack:
2019-02-25 19:56:09.912 7132-7247/? W/zygote64:     at java.net.DatagramSocket.getImpl(DatagramSocket.java:371)
2019-02-25 19:56:09.912 7132-7247/? W/zygote64:     at java.net.DatagramSocket.receive(DatagramSocket.java:847)
2019-02-25 19:56:09.912 7132-7247/? W/zygote64:   - locked <0x0ae7fcf7> (a java.net.DatagramSocket)
2019-02-25 19:56:09.912 7132-7247/? W/zygote64:   - locked <0x04ead300> (a java.net.DatagramPacket)
2019-02-25 19:56:09.912 7132-7247/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.udpListeningImpl(LocalUDPDataReciever.java:181)
2019-02-25 19:56:09.913 7132-7247/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:49)
2019-02-25 19:56:09.913 7132-7247/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:132)
2019-02-25 19:56:09.913 7132-7247/? W/zygote64:     at java.lang.Thread.run(Thread.java:764)
2019-02-25 19:56:09.913 7132-7247/? W/zygote64: Contender stack:
2019-02-25 19:56:09.913 7132-7247/? W/zygote64:     at java.net.DatagramSocket.receive(DatagramSocket.java:-1)
2019-02-25 19:56:09.913 7132-7247/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.udpListeningImpl(LocalUDPDataReciever.java:181)
2019-02-25 19:56:09.913 7132-7247/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:49)
2019-02-25 19:56:09.913 7132-7247/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:132)
2019-02-25 19:56:09.913 7132-7247/? W/zygote64:     at java.lang.Thread.run(Thread.java:764)
2019-02-25 19:56:10.808 622-634/? I/mmid: select timeout: wait for receiving msg
2019-02-25 19:56:12.831 7132-7163/? D/QoS4SendDaemon: 【IMCORE】【QoS】=========== 消息发送质量保证线程运行中, 当前需要处理的列表长度为0...
2019-02-25 19:56:12.854 7132-7162/? D/KeepAliveDaemon: 【IMCORE】心跳线程执行中...
2019-02-25 19:56:12.901 7132-7248/? W/zygote64: Long monitor contention with owner Thread-2 (7194) at void java.net.DatagramSocket.receive(java.net.DatagramPacket)(DatagramSocket.java:-1) waiters=2 in void java.net.DatagramSocket.receive(java.net.DatagramPacket) for 8.998s
2019-02-25 19:56:12.901 7132-7248/? W/zygote64: Current owner stack:
2019-02-25 19:56:12.901 7132-7132/? D/LocalUDPDataReciever: 【IMCORE】收到服务端回过来的Keep Alive心跳响应包.
2019-02-25 19:56:12.901 7132-7248/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPSocketProvider.getInstance(LocalUDPSocketProvider.java:52)
2019-02-25 19:56:12.901 7132-7248/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.udpListeningImpl(LocalUDPDataReciever.java:177)
2019-02-25 19:56:12.901 7132-7248/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:49)
2019-02-25 19:56:12.901 7132-7248/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:132)
2019-02-25 19:56:12.902 7132-7248/? W/zygote64:     at java.lang.Thread.run(Thread.java:764)
2019-02-25 19:56:12.902 7132-7248/? W/zygote64: Contender stack:
2019-02-25 19:56:12.902 7132-7248/? W/zygote64:     at java.net.DatagramSocket.receive(DatagramSocket.java:-1)
2019-02-25 19:56:12.902 7132-7248/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.udpListeningImpl(LocalUDPDataReciever.java:181)
2019-02-25 19:56:12.902 7132-7248/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever.access$100(LocalUDPDataReciever.java:49)
2019-02-25 19:56:12.902 7132-7248/? W/zygote64:     at net.openmob.mobileimsdk.android.core.LocalUDPDataReciever$1.run(LocalUDPDataReciever.java:132)
2019-02-25 19:56:12.902 7132-7248/? W/zygote64:     at java.lang.Thread.run(Thread.java:764)
2019-02-25 19:56:13.813 622-634/? I/mmid: select timeout: wait for receiving msg

有些手机（比如小米）熄屏的时候为了省电会把普通app的网络都给关闭，对于app来说网络已处于非正常脏现场中。

MobileIMSDK中的这些Log主要是给资深的网络编程程序员看的，一般情况下普通开发者不用理会，你只看APP算法的表现就可以了，因为app会在手机的网络恢复正常时自动恢复app层的网络通信现场（之前的异常脏现场，MobileIMSDK自身的算法会把它给扔掉的），不会正的陷入你看到的这些Log问题里。

所以，综上，忽略这些Log即可，以算法的健康表现为评价标准即可，不会有其它问题。