hlzs_01

android-电磁笔input输入引起ANR

08-11 14:14:18.611 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:18.889 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:18.891 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:18.891 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:18.891 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:18.891 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:18.971 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:18.971 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:19.018 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:19.018 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:19.018 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:19.018 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:19.115 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:19.115 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds

08-11 14:14:24.903 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:24.903 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:24.904 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:24.904 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:24.982 E/NetlinkHandler( 247): devicesIsUsb false
08-11 14:14:25.008 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:25.009 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:25.065 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:25.354 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds

08-11 14:14:30.137 I/InputDispatcher( 644): Application is not responding: Window{e00c7e7 u0 com.custom.read/com.custom.read.ui.activity.MainActivity}. It has been 5004.4ms since event, 5004.2ms since wait started. Reason: Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 26. Wait queue head age: 5506.7ms.
08-11 14:14:30.293 I/WindowManager( 644): Input event dispatching timed out sending to com.custom.read/com.custom.read.ui.activity.MainActivity. Reason: Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 26. Wait queue head age: 5506.7ms.
08-11 14:14:30.293 I/InputReader( 644): Detected input event buffer overrun for device Wacom I2C Digitizer.
08-11 14:14:30.301 D/ViewRootImpl[MainActivity]( 4547): updatePointerIcon called with position out of bounds
08-11 14:14:30.319 I/Process ( 644): Sending signal. PID: 4547 SIG: 3
08-11 14:14:30.319 I/art     ( 4547): Thread[3,tid=4553,WaitingInMainSignalCatcherLoop,Thread*=0xdebbce00,peer=0x12c17280,"Signal Catcher"]: reacting to signal 3
08-11 14:14:30.319 I/art     ( 4547):
08-11 14:14:30.421 I/art     ( 4547): Wrote stack traces to '/data/anr/traces.txt'
08-11 14:14:30.421 I/Process ( 644): Sending signal. PID: 644 SIG: 3
08-11 14:14:30.421 I/art     ( 644): Thread[2,tid=649,WaitingInMainSignalCatcherLoop,Thread*=0x769820d000,peer=0x12c010d0,"Signal Catcher"]: reacting to signal 3
08-11 14:14:30.421 I/art     ( 644):
08-11 14:14:30.777 I/art     ( 644): Wrote stack traces to '/data/anr/traces.txt'
08-11 14:14:30.777 I/Process ( 644): Sending signal. PID: 1243 SIG: 3
08-11 14:14:30.777 I/art     ( 1243): Thread[3,tid=1250,WaitingInMainSignalCatcherLoop,Thread*=0x76a0e96400,peer=0x12c1eb80,"Signal Catcher"]: reacting to signal 3
08-11 14:14:30.777 I/art     ( 1243):
08-11 14:14:30.821 I/art     ( 1243): Wrote stack traces to '/data/anr/traces.txt'
08-11 14:14:30.821 I/Process ( 644): Sending signal. PID: 1230 SIG: 3
08-11 14:14:30.821 I/art     ( 1230): Thread[3,tid=1236,WaitingInMainSignalCatcherLoop,Thread*=0x76a0e96400,peer=0x12c1e940,"Signal Catcher"]: reacting to signal 3
08-11 14:14:30.821 I/art     ( 1230):
08-11 14:14:30.863 I/Process ( 644): Sending signal. PID: 1214 SIG: 3
08-11 14:14:30.864 I/art     ( 1214): Thread[3,tid=1221,WaitingInMainSignalCatcherLoop,Thread*=0x76a0e96400,peer=0x12c1e700,"Signal Catcher"]: reacting to signal 3
08-11 14:14:30.864 I/art     ( 1214):
08-11 14:14:30.864 I/art     ( 1230): Wrote stack traces to '/data/anr/traces.txt'
08-11 14:14:30.905 I/art     ( 1214): Wrote stack traces to '/data/anr/traces.txt'
08-11 14:14:30.905 I/Process ( 644): Sending signal. PID: 1201 SIG: 3
08-11 14:14:30.905 I/art     ( 1201): Thread[3,tid=1207,WaitingInMainSignalCatcherLoop,Thread*=0x76a0e96400,peer=0x12c1e4c0,"Signal Catcher"]: reacting to signal 3
08-11 14:14:30.906 I/art     ( 1201):
08-11 14:14:30.962 I/art     ( 1201): Wrote stack traces to '/data/anr/traces.txt'
08-11 14:14:30.962 I/Process ( 644): Sending signal. PID: 768 SIG: 3
08-11 14:14:30.962 I/art     ( 768): Thread[3,tid=780,WaitingInMainSignalCatcherLoop,Thread*=0x76a0e96400,peer=0x12c005e0,"Signal Catcher"]: reacting to signal 3
08-11 14:14:30.962 I/art     ( 768):
08-11 14:14:31.056 I/art     ( 768): Wrote stack traces to '/data/anr/traces.txt'
08-11 14:14:31.056 I/Process ( 644): Sending signal. PID: 760 SIG: 3
08-11 14:14:31.056 I/art     ( 760): Thread[3,tid=766,WaitingInMainSignalCatcherLoop,Thread*=0x76a0e96400,peer=0x12c003a0,"Signal Catcher"]: reacting to signal 3
08-11 14:14:31.056 I/art     ( 760):
08-11 14:14:31.133 I/art     ( 760): Wrote stack traces to '/data/anr/traces.txt'
08-11 14:14:31.145 W/        ( 246): debuggerd: handling request: pid=261 uid=1000 gid=1003 tid=261
08-11 14:14:31.216 W/        ( 246): debuggerd: resuming target 261
08-11 14:14:31.217 W/        ( 246): debuggerd: handling request: pid=366 uid=1041 gid=1005 tid=366
08-11 14:14:31.218 W/        ( 245): debuggerd: handling request: pid=366 uid=1041 gid=1005 tid=366
08-11 14:14:31.247 W/        ( 245): debuggerd: resuming target 366
08-11 14:14:31.248 W/        ( 246): debuggerd: handling request: pid=367 uid=1047 gid=1005 tid=367
08-11 14:14:31.248 W/        ( 245): debuggerd: handling request: pid=367 uid=1047 gid=1005 tid=367
08-11 14:14:31.270 W/        ( 245): debuggerd: resuming target 367
08-11 14:14:31.270 W/        ( 246): debuggerd: handling request: pid=369 uid=1019 gid=1019 tid=369
08-11 14:14:31.271 W/        ( 245): debuggerd: handling request: pid=369 uid=1019 gid=1019 tid=369
08-11 14:14:31.285 W/        ( 245): debuggerd: resuming target 369
08-11 14:14:31.286 W/        ( 246): debuggerd: handling request: pid=373 uid=1046 gid=1006 tid=373
08-11 14:14:31.286 W/        ( 245): debuggerd: handling request: pid=373 uid=1046 gid=1006 tid=373
08-11 14:14:31.308 W/        ( 245): debuggerd: resuming target 373
08-11 14:14:31.309 W/        ( 246): debuggerd: handling request: pid=374 uid=1013 gid=1031 tid=374
08-11 14:14:31.309 W/        ( 245): debuggerd: handling request: pid=374 uid=1013 gid=1031 tid=374
08-11 14:14:31.323 W/        ( 245): debuggerd: resuming target 374
08-11 14:14:31.324 W/        ( 246): debuggerd: handling request: pid=375 uid=1040 gid=1026 tid=375
08-11 14:14:31.325 W/        ( 245): debuggerd: handling request: pid=375 uid=1040 gid=1026 tid=375
08-11 14:14:31.352 W/        ( 245): debuggerd: resuming target 375
08-11 14:14:31.352 W/        ( 246): debuggerd: handling request: pid=376 uid=1013 gid=1005 tid=376
08-11 14:14:31.353 W/        ( 245): debuggerd: handling request: pid=376 uid=1013 gid=1005 tid=376
08-11 14:14:31.436 W/        ( 245): debuggerd: resuming target 376
08-11 14:14:32.148 E/ActivityManager( 644): ANR in com.custom.read (com.custom.read/.ui.activity.MainActivity)
08-11 14:14:32.148 E/ActivityManager( 644): PID: 4547
08-11 14:14:32.148 E/ActivityManager( 644): Reason: Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 26. Wait queue head age: 5506.7ms.)
08-11 14:14:32.148 E/ActivityManager( 644): Load: 1.74 / 1.07 / 1.19
08-11 14:14:32.148 E/ActivityManager( 644): CPU usage from 5318ms to 0ms ago (2020-08-11 14:14:24.983 to 2020-08-11 14:14:30.301):
08-11 14:14:32.148 E/ActivityManager( 644):   196% 4547/com.custom.read: 165% user + 30% kernel / faults: 2071 minor
08-11 14:14:32.148 E/ActivityManager( 644):   12% 644/system_server: 9.2% user + 3.3% kernel / faults: 1501 minor 1 major
08-11 14:14:32.148 E/ActivityManager( 644):   9.7% 376/mediaserver: 4.1% user + 5.6% kernel
08-11 14:14:32.148 E/ActivityManager( 644):   5% 261/surfaceflinger: 3.3% user + 1.6% kernel / faults: 46 minor
08-11 14:14:32.148 E/ActivityManager( 644):   4.7% 170/mmcqd/1: 0% user + 4.7% kernel
08-11 14:14:32.148 E/ActivityManager( 644):   4.5% 4430/kworker/u13:1: 0% user + 4.5% kernel
08-11 14:14:32.148 E/ActivityManager( 644):   4.1% 4509/kworker/u13:5: 0% user + 4.1% kernel
08-11 14:14:32.148 E/ActivityManager( 644):   2% 4632/kworker/u12:3: 0% user + 2% kernel
08-11 14:14:32.148 E/ActivityManager( 644):   1.8% 149/irq/172-wacom_i: 0% user + 1.8% kernel
08-11 14:14:32.148 E/ActivityManager( 644):   1.6% 232/jbd2/mmcblk1p17: 0% user + 1.6% kernel
08-11 14:14:32.148 E/ActivityManager( 644):   0.1% 7/rcu_preempt: 0% user + 0.1% kernel
08-11 14:14:32.148 E/ActivityManager( 644):   0.1% 674/kworker/1:1H: 0% user + 0.1% kernel
08-11 14:14:32.148 E/ActivityManager( 644):   0.1% 768/com.android.systemui: 0.1% user + 0% kernel / faults: 63 minor
08-11 14:14:32.148 E/ActivityManager( 644):   0.1% 4419/kworker/4:0: 0% user + 0.1% kernel
08-11 14:14:32.148 E/ActivityManager( 644):   0.1% 4423/adbd: 0% user + 0.1% kernel / faults: 26 minor
08-11 14:14:32.148 E/ActivityManager( 644):   0.1% 4457/kworker/0:0: 0% user + 0.1% kernel
08-11 14:14:32.148 E/ActivityManager( 644): 41% TOTAL: 30% user + 9.8% kernel + 1% iowait + 0% softirq
08-11 14:14:32.148 E/ActivityManager( 644): CPU usage from 1310ms to 1827ms later (2020-08-11 14:14:31.611 to 2020-08-11 14:14:32.128):
08-11 14:14:32.148 E/ActivityManager( 644):   193% 4547/com.custom.read: 156% user + 36% kernel / faults: 73 minor
08-11 14:14:32.148 E/ActivityManager( 644):     98% 4669/Thread-39: 69% user + 29% kernel
08-11 14:14:32.148 E/ActivityManager( 644):     92% 4547/com.custom.read: 85% user + 7.7% kernel
08-11 14:14:32.148 E/ActivityManager( 644):     1.9% 4573/mali-cmar-backe: 0% user + 1.9% kernel
08-11 14:14:32.148 E/ActivityManager( 644):    +0% 4679/Binder:4547_5: 0% user + 0% kernel
08-11 14:14:32.148 E/ActivityManager( 644):   23% 644/system_server: 13% user + 9.6% kernel / faults: 93 minor
08-11 14:14:32.148 E/ActivityManager( 644):     7.7% 654/HeapTaskDaemon: 7.7% user + 0% kernel
08-11 14:14:32.148 E/ActivityManager( 644):     5.8% 704/InputReader: 3.8% user + 1.9% kernel
08-11 14:14:32.148 E/ActivityManager( 644):     3.8% 659/android.ui: 1.9% user + 1.9% kernel
08-11 14:14:32.148 E/ActivityManager( 644):     1.9% 652/FinalizerDaemon: 0% user + 1.9% kernel
08-11 14:14:32.148 E/ActivityManager( 644):     1.9% 658/ActivityManager: 0% user + 1.9% kernel
08-11 14:14:32.148 E/ActivityManager( 644):     1.9% 665/android.display: 1.9% user + 0% kernel
08-11 14:14:32.148 E/ActivityManager( 644):   9.6% 376/mediaserver: 3.8% user + 5.8% kernel
08-11 14:14:32.148 E/ActivityManager( 644):     3.8% 4603/FFParser: 1.9% user + 1.9% kernel
08-11 14:14:32.148 E/ActivityManager( 644):     1.9% 4588/FFParser: 1.9% user + 0% kernel
08-11 14:14:32.148 E/ActivityManager( 644):   9.2% 4509/kworker/u13:5: 0% user + 9.2% kernel
08-11 14:14:32.148 E/ActivityManager( 644):   5.8% 261/surfaceflinger: 1.9% user + 3.8% kernel / faults: 6 minor
08-11 14:14:32.148 E/ActivityManager( 644):     1.9% 261/surfaceflinger: 1.9% user + 0% kernel
08-11 14:14:32.148 E/ActivityManager( 644):     1.9% 287/mali-cmar-backe: 0% user + 1.9% kernel
08-11 14:14:32.148 E/ActivityManager( 644):   1.9% 149/irq/172-wacom_i: 0% user + 1.9% kernel
08-11 14:14:32.148 E/ActivityManager( 644):   1.9% 170/mmcqd/1: 0% user + 1.9% kernel
08-11 14:14:32.148 E/ActivityManager( 644):   1.6% 343/f2fs_discard-25: 0% user + 1.6% kernel
08-11 14:14:32.148 E/ActivityManager( 644):   1.8% 4430/kworker/u13:1: 0% user + 1.8% kernel
08-11 14:14:32.148 E/ActivityManager( 644): 42% TOTAL: 30% user + 11% kernel + 0.3% softirq
08-11 14:14:32.180 V/WindowManager( 644): Checking app orientation: AppWindowToken{2ca3d69 token=Token{b8243f0 ActivityRecord{3a9c433 u0 com.custom.read/.ui.activity.MainActivity t101}}}
08-11 14:14:32.191 V/WindowManager( 644): Checking app orientation: AppWindowToken{2ca3d69 token=Token{b8243f0 ActivityRecord{3a9c433 u0 com.custom.read/.ui.activity.MainActivity t101}}}
08-11 14:14:32.223 D/GRALLOC-ROCKCHIP( 261): enter, w : 1299, h : 455, format : 0x1, usage : 0x900.
08-11 14:14:32.224 I/OpenGLRenderer( 644): Initialized EGL, version 1.4
08-11 14:14:32.224 D/OpenGLRenderer( 644): Swap behavior 1
08-11 14:14:32.227 D/GRALLOC-ROCKCHIP( 261): enter, w : 1299, h : 455, format : 0x1, usage : 0x900.
08-11 14:14:32.231 D/GRALLOC-ROCKCHIP( 261): enter, w : 1299, h : 455, format : 0x1, usage : 0x900.
08-11 14:14:32.235 D/GRALLOC-ROCKCHIP( 261): enter, w : 1299, h : 455, format : 0x1, usage : 0x900.
08-11 14:14:32.239 E/BufferQueueProducer( 261): [Application Not Responding: com.custom.read] connect: already connected (cur=1 req=1)
08-11 14:14:32.240 D/mali_winsys( 644): EGLint new_window_surface(egl_winsys_display*, void*, EGLSurface, EGLConfig, egl_winsys_surface**, egl_color_buffer_format*, EGLBoolean) returns 0x3000
08-11 14:14:32.240 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.241 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.241 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.242 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.251 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.261 D/GRALLOC-ROCKCHIP( 261): enter, w : 1299, h : 455, format : 0x1, usage : 0xb00.
08-11 14:14:32.266 D/GRALLOC-ROCKCHIP( 644): enter, w : 1299, h : 455, format : 0x1, usage : 0xb00.
08-11 14:14:32.282 D/GRALLOC-ROCKCHIP( 261): enter, w : 1299, h : 455, format : 0x1, usage : 0xb00.
08-11 14:14:32.287 D/GRALLOC-ROCKCHIP( 644): enter, w : 1299, h : 455, format : 0x1, usage : 0xb00.
08-11 14:14:32.292 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.302 D/GRALLOC-ROCKCHIP( 261): enter, w : 1299, h : 455, format : 0x1, usage : 0xb00.
08-11 14:14:32.307 D/GRALLOC-ROCKCHIP( 644): enter, w : 1299, h : 455, format : 0x1, usage : 0xb00.
08-11 14:14:32.328 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.344 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.360 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.370 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.371 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.371 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.371 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.372 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.372 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.377 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.380 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.381 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.382 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.382 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.382 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.383 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.384 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.386 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.388 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.389 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.398 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.416 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.416 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.417 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.418 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.418 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.419 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.427 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.430 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.431 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.432 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.432 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.432 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.433 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.433 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.434 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.434 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.435 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.437 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.438 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.439 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.440 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.440 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.441 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.442 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.443 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.443 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.445 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.446 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.447 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.448 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.448 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.449 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.449 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.450 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.450 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.451 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.452 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.453 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.454 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.455 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.456 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.457 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.458 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.459 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.460 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.462 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.464 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.483 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.499 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.516 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.534 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.551 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.569 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.586 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.603 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.617 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.618 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.618 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.618 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.638 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.655 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.673 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.690 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.708 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.725 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.742 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:32.748 D/ViewRootImpl[read]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:35.008 E/NetlinkHandler( 247): devicesIsUsb false
08-11 14:14:36.447 I/art     ( 4547): Background sticky concurrent mark sweep GC freed 369245(13MB) AllocSpace objects, 0(0B) LOS objects, 27% free, 35MB/48MB, paused 1.013ms total 107.083ms
08-11 14:14:38.511 I/InputDispatcher( 644): Application is not responding: Window{89b1465 u0 Application Not Responding: com.custom.read}. It has been 5006.1ms since event, 5005.5ms since wait started. Reason: Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 215. Wait queue head age: 6160.1ms.
08-11 14:14:38.634 I/WindowManager( 644): Input event dispatching timed out sending to Application Not Responding: com.custom.read. Reason: Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 215. Wait queue head age: 6160.1ms.
08-11 14:14:38.660 I/Process ( 644): Sending signal. PID: 644 SIG: 3
08-11 14:14:38.660 I/art     ( 644): Thread[2,tid=649,WaitingInMainSignalCatcherLoop,Thread*=0x769820d000,peer=0x12c010d0,"Signal Catcher"]: reacting to signal 3
08-11 14:14:38.660 I/art     ( 644):
08-11 14:14:38.674 W/art     ( 644): Suspending all threads took: 9.984ms
08-11 14:14:38.689 I/art     ( 644): Background sticky concurrent mark sweep GC freed 5882(414KB) AllocSpace objects, 13(3MB) LOS objects, 31% free, 8MB/12MB, paused 12.056ms total 41.583ms
08-11 14:14:39.045 I/art     ( 644): Wrote stack traces to '/data/anr/traces.txt'
08-11 14:14:39.045 I/Process ( 644): Sending signal. PID: 1243 SIG: 3
08-11 14:14:39.045 I/art     ( 1243): Thread[3,tid=1250,WaitingInMainSignalCatcherLoop,Thread*=0x76a0e96400,peer=0x12c1eb80,"Signal Catcher"]: reacting to signal 3
08-11 14:14:39.046 I/art     ( 1243):
08-11 14:14:39.090 I/art     ( 1243): Wrote stack traces to '/data/anr/traces.txt'
08-11 14:14:39.090 I/Process ( 644): Sending signal. PID: 1230 SIG: 3
08-11 14:14:39.090 I/art     ( 1230): Thread[3,tid=1236,WaitingInMainSignalCatcherLoop,Thread*=0x76a0e96400,peer=0x12c1e940,"Signal Catcher"]: reacting to signal 3
08-11 14:14:39.090 I/art     ( 1230):
08-11 14:14:39.124 I/art     ( 1230): Wrote stack traces to '/data/anr/traces.txt'
08-11 14:14:39.124 I/Process ( 644): Sending signal. PID: 1214 SIG: 3
08-11 14:14:39.124 I/art     ( 1214): Thread[3,tid=1221,WaitingInMainSignalCatcherLoop,Thread*=0x76a0e96400,peer=0x12c1e700,"Signal Catcher"]: reacting to signal 3
08-11 14:14:39.124 I/art     ( 1214):
08-11 14:14:39.158 I/art     ( 1214): Wrote stack traces to '/data/anr/traces.txt'
08-11 14:14:39.158 I/Process ( 644): Sending signal. PID: 1201 SIG: 3
08-11 14:14:39.158 I/art     ( 1201): Thread[3,tid=1207,WaitingInMainSignalCatcherLoop,Thread*=0x76a0e96400,peer=0x12c1e4c0,"Signal Catcher"]: reacting to signal 3
08-11 14:14:39.158 I/art     ( 1201):
08-11 14:14:39.197 I/art     ( 1201): Wrote stack traces to '/data/anr/traces.txt'
08-11 14:14:39.198 I/Process ( 644): Sending signal. PID: 768 SIG: 3
08-11 14:14:39.198 I/art     ( 768): Thread[3,tid=780,WaitingInMainSignalCatcherLoop,Thread*=0x76a0e96400,peer=0x12c005e0,"Signal Catcher"]: reacting to signal 3
08-11 14:14:39.198 I/art     ( 768):
08-11 14:14:39.294 I/art     ( 768): Wrote stack traces to '/data/anr/traces.txt'
08-11 14:14:39.295 I/Process ( 644): Sending signal. PID: 760 SIG: 3
08-11 14:14:39.295 I/art     ( 760): Thread[3,tid=766,WaitingInMainSignalCatcherLoop,Thread*=0x76a0e96400,peer=0x12c003a0,"Signal Catcher"]: reacting to signal 3
08-11 14:14:39.295 I/art     ( 760):
08-11 14:14:39.358 I/art     ( 760): Wrote stack traces to '/data/anr/traces.txt'
08-11 14:14:39.367 W/        ( 246): debuggerd: handling request: pid=261 uid=1000 gid=1003 tid=261
08-11 14:14:39.434 W/        ( 246): debuggerd: resuming target 261
08-11 14:14:39.435 W/        ( 246): debuggerd: handling request: pid=366 uid=1041 gid=1005 tid=366
08-11 14:14:39.435 W/        ( 245): debuggerd: handling request: pid=366 uid=1041 gid=1005 tid=366
08-11 14:14:39.464 W/        ( 245): debuggerd: resuming target 366
08-11 14:14:39.465 W/        ( 246): debuggerd: handling request: pid=367 uid=1047 gid=1005 tid=367
08-11 14:14:39.466 W/        ( 245): debuggerd: handling request: pid=367 uid=1047 gid=1005 tid=367
08-11 14:14:39.483 W/        ( 245): debuggerd: resuming target 367
08-11 14:14:39.483 W/        ( 246): debuggerd: handling request: pid=369 uid=1019 gid=1019 tid=369
08-11 14:14:39.484 W/        ( 245): debuggerd: handling request: pid=369 uid=1019 gid=1019 tid=369
08-11 14:14:39.495 W/        ( 245): debuggerd: resuming target 369
08-11 14:14:39.496 W/        ( 246): debuggerd: handling request: pid=373 uid=1046 gid=1006 tid=373
08-11 14:14:39.496 W/        ( 245): debuggerd: handling request: pid=373 uid=1046 gid=1006 tid=373
08-11 14:14:39.516 W/        ( 245): debuggerd: resuming target 373
08-11 14:14:39.517 W/        ( 246): debuggerd: handling request: pid=374 uid=1013 gid=1031 tid=374
08-11 14:14:39.517 W/        ( 245): debuggerd: handling request: pid=374 uid=1013 gid=1031 tid=374
08-11 14:14:39.531 W/        ( 245): debuggerd: resuming target 374
08-11 14:14:39.532 W/        ( 246): debuggerd: handling request: pid=375 uid=1040 gid=1026 tid=375
08-11 14:14:39.532 W/        ( 245): debuggerd: handling request: pid=375 uid=1040 gid=1026 tid=375
08-11 14:14:39.557 W/        ( 245): debuggerd: resuming target 375
08-11 14:14:39.557 W/        ( 246): debuggerd: handling request: pid=376 uid=1013 gid=1005 tid=376
08-11 14:14:39.558 W/        ( 245): debuggerd: handling request: pid=376 uid=1013 gid=1005 tid=376
08-11 14:14:39.631 W/        ( 245): debuggerd: resuming target 376
08-11 14:14:40.334 I/Process ( 644): Sending signal. PID: 4547 SIG: 3
08-11 14:14:40.334 I/art     ( 4547): Thread[3,tid=4553,WaitingInMainSignalCatcherLoop,Thread*=0xdebbce00,peer=0x12c17280,"Signal Catcher"]: reacting to signal 3
08-11 14:14:40.334 I/art     ( 4547):
08-11 14:14:40.429 I/art     ( 4547): Wrote stack traces to '/data/anr/traces.txt'
08-11 14:14:40.433 E/ActivityManager( 644): ANR in system
08-11 14:14:40.433 E/ActivityManager( 644): PID: 644
08-11 14:14:40.433 E/ActivityManager( 644): Reason: Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 215. Wait queue head age: 6160.1ms.)
08-11 14:14:40.433 E/ActivityManager( 644): Load: 1.78 / 1.1 / 1.2
08-11 14:14:40.433 E/ActivityManager( 644): CPU usage from 8338ms to 0ms ago (2020-08-11 14:14:30.301 to 2020-08-11 14:14:38.639):
08-11 14:14:40.433 E/ActivityManager( 644):   196% 4547/com.custom.read: 165% user + 30% kernel / faults: 2636 minor 1 major
08-11 14:14:40.433 E/ActivityManager( 644):   22% 644/system_server: 17% user + 5.3% kernel / faults: 3196 minor
08-11 14:14:40.433 E/ActivityManager( 644):   16% 376/mediaserver: 7.1% user + 8.8% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   10% 261/surfaceflinger: 5.2% user + 5.1% kernel / faults: 151 minor
08-11 14:14:40.433 E/ActivityManager( 644):   7.5% 4509/kworker/u13:5: 0% user + 7.5% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   7.4% 170/mmcqd/1: 0% user + 7.4% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   4.1% 4430/kworker/u13:1: 0% user + 4.1% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   2.1% 4514/kworker/u13:7: 0% user + 2.1% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   2.2% 4632/kworker/u12:3: 0% user + 2.2% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   0% 69/kswapd0: 0% user + 0% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   1.4% 4423/adbd: 0.3% user + 1% kernel / faults: 315 minor
08-11 14:14:40.433 E/ActivityManager( 644):   1.3% 768/com.android.systemui: 1% user + 0.2% kernel / faults: 299 minor
08-11 14:14:40.433 E/ActivityManager( 644):   0.8% 4421/kworker/u12:1: 0% user + 0.8% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   0.9% 232/jbd2/mmcblk1p17: 0% user + 0.9% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   0.8% 149/irq/172-wacom_i: 0% user + 0.8% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   0% 760/com.android.phone: 0% user + 0% kernel / faults: 88 minor
08-11 14:14:40.433 E/ActivityManager( 644):   0.3% 235/logd: 0.1% user + 0.2% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   0.4% 7/rcu_preempt: 0% user + 0.4% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   0% 1201/com.jide.analytics: 0% user + 0% kernel / faults: 90 minor
08-11 14:14:40.433 E/ActivityManager( 644):   0% 1230/com.jide.apiservice: 0% user + 0% kernel / faults: 130 minor
08-11 14:14:40.433 E/ActivityManager( 644):   0% 1243/com.jide.dvdcmdservice: 0% user + 0% kernel / faults: 87 minor
08-11 14:14:40.433 E/ActivityManager( 644):   0.4% 4457/kworker/0:0: 0% user + 0.4% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   0% 1214/com.jide.externalstorage: 0% user + 0% kernel / faults: 93 minor
08-11 14:14:40.433 E/ActivityManager( 644):   0% 343/f2fs_discard-25: 0% user + 0% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   0.1% 385/logcatext: 0.1% user + 0% kernel / faults: 1 minor
08-11 14:14:40.433 E/ActivityManager( 644):   0.2% 674/kworker/1:1H: 0% user + 0.2% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   0.1% 675/kworker/0:1H: 0% user + 0.1% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   0.1% 4452/logcat: 0.1% user + 0% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   0.1% 4665/logcat: 0% user + 0.1% kernel / faults: 1 minor
08-11 14:14:40.433 E/ActivityManager( 644):   0% 18/migration/2: 0% user + 0% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   0% 151/irq/177-fts: 0% user + 0% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   0% 245/debuggerd: 0% user + 0% kernel / faults: 182 minor
08-11 14:14:40.433 E/ActivityManager( 644):   0% 246/debuggerd64: 0% user + 0% kernel / faults: 15 minor
08-11 14:14:40.433 E/ActivityManager( 644):   0% 366/audioserver: 0% user + 0% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   0.1% 4419/kworker/4:0: 0% user + 0.1% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   0% 4426/irq/232-dwc3: 0% user + 0% kernel
08-11 14:14:40.433 E/ActivityManager( 644): 49% TOTAL: 33% user + 14% kernel + 1% iowait + 0.1% softirq
08-11 14:14:40.433 E/ActivityManager( 644): CPU usage from 1163ms to 1679ms later (2020-08-11 14:14:39.802 to 2020-08-11 14:14:40.318):
08-11 14:14:40.433 E/ActivityManager( 644):   197% 4547/com.custom.read: 164% user + 32% kernel / faults: 70 minor
08-11 14:14:40.433 E/ActivityManager( 644):     96% 4669/Thread-39: 69% user + 27% kernel
08-11 14:14:40.433 E/ActivityManager( 644):     94% 4547/com.custom.read: 90% user + 3.8% kernel
08-11 14:14:40.433 E/ActivityManager( 644):     1.9% 4564/RenderThread: 0% user + 1.9% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   24% 4514/kworker/u13:7: 0% user + 24% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   21% 376/mediaserver: 7.7% user + 13% kernel
08-11 14:14:40.433 E/ActivityManager( 644):     7.7% 4603/FFParser: 0% user + 7.7% kernel
08-11 14:14:40.433 E/ActivityManager( 644):     1.9% 4588/FFParser: 1.9% user + 0% kernel
08-11 14:14:40.433 E/ActivityManager( 644):     1.9% 4593/FFParser: 0% user + 1.9% kernel
08-11 14:14:40.433 E/ActivityManager( 644):     1.9% 4598/FFParser: 0% user + 1.9% kernel
08-11 14:14:40.433 E/ActivityManager( 644):     1.9% 4606/VsyncReciver: 1.9% user + 0% kernel
08-11 14:14:40.433 E/ActivityManager( 644):     1.9% 4608/FFParser: 1.9% user + 0% kernel
08-11 14:14:40.433 E/ActivityManager( 644):     1.9% 4613/FFParser: 1.9% user + 0% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   7.9% 232/jbd2/mmcblk1p17: 0% user + 7.9% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   9.7% 261/surfaceflinger: 5.8% user + 3.8% kernel / faults: 4 minor
08-11 14:14:40.433 E/ActivityManager( 644):     1.9% 261/surfaceflinger: 1.9% user + 0% kernel
08-11 14:14:40.433 E/ActivityManager( 644):     1.9% 276/Binder:261_1: 0% user + 1.9% kernel
08-11 14:14:40.433 E/ActivityManager( 644):     1.9% 287/mali-cmar-backe: 0% user + 1.9% kernel
08-11 14:14:40.433 E/ActivityManager( 644):     1.9% 290/EventThread: 0% user + 1.9% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   7.7% 644/system_server: 1.9% user + 5.8% kernel
08-11 14:14:40.433 E/ActivityManager( 644):     3.8% 658/ActivityManager: 0% user + 3.8% kernel
08-11 14:14:40.433 E/ActivityManager( 644):     1.9% 659/android.ui: 1.9% user + 0% kernel
08-11 14:14:40.433 E/ActivityManager( 644):     1.9% 680/SensorService: 1.9% user + 0% kernel
08-11 14:14:40.433 E/ActivityManager( 644):     1.9% 4518/Binder:644_1F: 1.9% user + 0% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   5.8% 69/kswapd0: 0% user + 5.8% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   5.8% 170/mmcqd/1: 0% user + 5.8% kernel
08-11 14:14:40.433 E/ActivityManager( 644):   1.4% 7/rcu_preempt: 0% user + 1.4% kernel
08-11 14:14:40.433 E/ActivityManager( 644): 48% TOTAL: 31% user + 17% kernel
08-11 14:14:40.477 V/WindowManager( 644): Checking app orientation: AppWindowToken{2ca3d69 token=Token{b8243f0 ActivityRecord{3a9c433 u0 com.custom.read/.ui.activity.MainActivity t101}}}
08-11 14:14:40.489 V/WindowManager( 644): Checking app orientation: AppWindowToken{2ca3d69 token=Token{b8243f0 ActivityRecord{3a9c433 u0 com.custom.read/.ui.activity.MainActivity t101}}}
08-11 14:14:40.520 D/GRALLOC-ROCKCHIP( 261): enter, w : 1299, h : 455, format : 0x1, usage : 0x900.
08-11 14:14:40.527 D/GRALLOC-ROCKCHIP( 261): enter, w : 1299, h : 455, format : 0x1, usage : 0x900.
08-11 14:14:40.541 D/GRALLOC-ROCKCHIP( 261): enter, w : 1299, h : 455, format : 0x1, usage : 0x900.
08-11 14:14:40.547 D/GRALLOC-ROCKCHIP( 261): enter, w : 1299, h : 455, format : 0x1, usage : 0x900.
08-11 14:14:40.552 E/BufferQueueProducer( 261): [Application Not Responding: system] connect: already connected (cur=1 req=1)
08-11 14:14:40.552 D/mali_winsys( 644): EGLint new_window_surface(egl_winsys_display*, void*, EGLSurface, EGLConfig, egl_winsys_surface**, egl_color_buffer_format*, EGLBoolean) returns 0x3000
08-11 14:14:40.552 D/ViewRootImpl[Application Not Responding: system]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:40.553 D/ViewRootImpl[Application Not Responding: system]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:40.553 D/ViewRootImpl[Application Not Responding: system]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:40.553 D/ViewRootImpl[Application Not Responding: system]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:40.554 D/ViewRootImpl[Application Not Responding: system]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:40.554 D/ViewRootImpl[Application Not Responding: system]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:40.554 D/ViewRootImpl[Application Not Responding: system]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:40.555 D/ViewRootImpl[Application Not Responding: system]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:40.560 D/ViewRootImpl[Application Not Responding: system]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:40.560 D/ViewRootImpl[Application Not Responding: system]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:40.565 D/ViewRootImpl[Application Not Responding: system]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:40.565 D/ViewRootImpl[Application Not Responding: system]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:40.566 D/ViewRootImpl[Application Not Responding: system]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:40.566 D/ViewRootImpl[Application Not Responding: system]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:40.573 D/ViewRootImpl[Application Not Responding: system]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:40.582 D/GRALLOC-ROCKCHIP( 261): enter, w : 1299, h : 455, format : 0x1, usage : 0xb00.
08-11 14:14:40.585 D/GRALLOC-ROCKCHIP( 644): enter, w : 1299, h : 455, format : 0x1, usage : 0xb00.
08-11 14:14:40.594 D/GRALLOC-ROCKCHIP( 261): enter, w : 1299, h : 455, format : 0x1, usage : 0xb00.
08-11 14:14:40.597 D/GRALLOC-ROCKCHIP( 644): enter, w : 1299, h : 455, format : 0x1, usage : 0xb00.
08-11 14:14:40.608 D/ViewRootImpl[Application Not Responding: system]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:40.616 D/GRALLOC-ROCKCHIP( 261): enter, w : 1299, h : 455, format : 0x1, usage : 0xb00.
08-11 14:14:40.622 D/GRALLOC-ROCKCHIP( 644): enter, w : 1299, h : 455, format : 0x1, usage : 0xb00.
08-11 14:14:40.628 D/ViewRootImpl[Application Not Responding: system]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:40.639 D/ViewRootImpl[Application Not Responding: system]( 644): updatePointerIcon called with position out of bounds
08-11 14:14:40.640 D/ViewRootImpl[Application Not Responding: system]( 644): updatePointerIcon called with position out of bounds

1、解决方法在主线程Handler操作事件太平凡和繁琐

2、减少主线程占用CPU耗时操作

你可能感兴趣的:(android-app)

Android 获取app启动来源（是被谁启动的、被哪个第三方app启动？） yayayaiii android android开发 android app启动来源 app是被谁启动的
1、需求：需要知道当前app或者当前app的指定页面是被谁启动的，被哪个第三方app启动的，来判断是否允许对方启动，如果不被允许的第三方，则不启动app或者不启动app的指定页面。2、直接上代码。第一种方式：//结果：android-app://com.google.agetReferrer();第二种方式：/***通过反射获取referrer.*@return:com.google.a*/pri
Docker-Jenkins编译android-app的两种方案 Lucas.Deng DevOps docker jenkins android
Docker-Jenkins编译android-app的两种方案android开发使用jenkins编译，自动集成修改点/自动命名/自动备份，将修改的apk发布到测试服务器+发布网盘，而不需要用通讯工具传来传去。jenkins用在互联网开发编译比较常见，如果android开发也想用，该怎么设计呢？由于用jenkins开发androidapp的文章比较多，本文只提炼了干货。关键点1在app端需要做哪
Shopro商城，多平台移动商城（微信公众号、微信小程序、H5网页、Android-App、IOS-App购物商城） michael311 微信微信小程序小程序 android
基于Uniapp进行开发的多平台（微信公众号、维信小程序、H5网页、Android-App、IOS-App）购物商城，拥有强大的店铺装修、小程序直播、自定义模板、路由同步、多端支付（威信，支付宝）、多规格商品、运费模板、多地区邮费、库存管理、全端分享等功能。提供全部Uniapp+后台无加密源代码
Android-APP安全（一）测试子曰小玖 Android
Android系统由于其开源的属性，市场上针对开源代码定制的ROM参差不齐，在系统层面的安全防范和易损性都不一样，Android应用市场对app的审核相对iOS来说也比较宽泛，为很多漏洞提供了可乘之机。市场上一些主流的app虽然多少都做了一些安全防范，但由于大部分app不涉及资金安全，所以对安全的重视程度不够；而且由于安全是门系统学科，大部分app层的开发人员缺乏安全技术的积累，措施相对有限。据了
Android-app控制gpio Paper_Love Android linux android
android-app控制gpio该文档以操控gpio104为实验编写实验目的：操控GPIO3_B00实验现象：控制led灯开关。android测试app已提供。1、android-app必须添加签名文件。app添加如下代码：android:sharedUserId="android.uid.system"2、修改/OK3568-android11-source/device/rockchip/c
Android-APP启动流程迦乐v android
引言Android系统非常庞大、错综复杂，其底层是采用Linux作为基底，上层采用包含虚拟机的Java层以及Native层，通过系统调用(Syscall)连通系统的内核空间与用户空间。用户空间主要采用C++和Java代码，通过JNI技术打通用户空间的Java层和Native层(C++/C)，从而融为一体。Google官方提供了一张经典的四层架构图，从下往上依次分为Linux内核、系统库和Andro
android 全面屏适配，最全导航攻略蔡振辉
Android-APP适配全面屏手机的技术要点https://windysha.github.io/2018/02/07/Android-APP适配全面屏手机的技术要点/Android状态栏微技巧，带你真正理解沉浸式模式https://blog.csdn.net/guolin_blog/article/details/51763825Android手机全面屏（18：9屏幕）适配指南https://
Android-App开发之ANR异常的原因分析及处理总结 C1R2
ANR的全称是applicationnotresponding，根据它的意思我们就能看出来是应用程序未响应，就像是我们在电脑上碰到的程序未响应，一般电脑出现这种情况，可能是由于我们打开了很多应用程序，占用了大量的内存，或者CPU时间片被一个应用程序长时间占用，不够分配，导致部分应用程序出现了无响应。Android和Windows基本一样，接下来我们就分析一下Android是怎么产生的这个问题。下图
Android-APP启动时间-for Python 沈宥
一、获取APP启动时间1、adb命令行获取adbshellamstart-S-Wcom.xxxx.xxxx/com.xxxx.biz.main.ui.activity.SplashPageActivity-S：表示每次启动前先强行停止2、python执行adb命令importsubprocessres=subprocess.Popen('adbshellamstart-S-Wcom.xxxx.xx
Android-App的设计架构经验谈，聪明人已经收藏了！ clhcowboy 程序员 android
前言伟人曾经说过：书是人类进步的阶梯书中自有黄金屋，书中自有颜如玉读书破万卷，下笔如有神书是唯一不死的东西。书籍是伟大的天才留给人类的遗产。最近有很多朋友在我的公众号上提问“Android开发的经典入门教材和学习路线？”、“Android开发入门教程有哪些推荐？”等类似的问题，我们不断重复回答这些问题，这让我萌生了做2020ndroid开发爆款书籍推荐：从小白—Android高级工程师系列学习路线
Android开发技巧！Android-App的设计架构经验谈，已开源程序员Sunbu 程序员 Android
写在前面1月初失业，找了近2个多月的工作了，还没找到心仪的工作，感觉心好慌，不知道该怎么办了？找不到工作的时候压力很大，有人说自信会很受打击，还有人说会很绝望，是人生的低谷……尽管很多时候我们自己知道，我不是找不到工作，只是找不到理想中的好工作。但这也不能改变你的空白期正在一天一天变长，不妥协的那份坚定正在一天一天动摇的事实。朋友推荐给我这份文档，狂刷五遍之后，最近刚刚获得字节跳动等多家公司的of
android app怎么优化,Android-App性能优化 weixin_39556064 android app怎么优化
上一篇我们讲了java的引用机制，今天我们来一下和它有关的app性能优化(其实也不是很大)。性能优化的目标在网上也看到过很多相关的文章，他们基本总结为：快,稳,省,小,描述的很准确.如下图快如何让app在运行过程过不卡顿，运行流畅，速度快,也就是说如何解决卡顿呢？我们先看看那些因素影响卡顿？1.UI,包括ui的绘制,刷新等2.启动,包括冷启动,热启动,温启动等3.跳转,页面跳转,前后天切换4.及时
Android-app自动更新总结（已适配9-0），浅谈Android消息机制原理 m0_66264630 程序员面试移动开发 android
Manifest.permission.WRITE_EXTERNAL_STORAGE,Manifest.permission.REQUEST_INSTALL_PACKAGES})protectedvoidcheckUpdate(){showLoadingDialog(“检测更新中…”);version=AppUpdateUtil.getAppVersionCode(this);//检查当前版本号/
Android-App性能优化薛之涛
上一篇我们讲了java的引用机制，今天我们来一下和它有关的app性能优化(其实也不是很大)。性能优化的目标在网上也看到过很多相关的文章，他们基本总结为：快,稳,省,小,描述的很准确.如下图(注：此图不知道啥时候收集的人，如有侵权，立删)：快如何让app在运行过程过不卡顿，运行流畅，速度快,也就是说如何解决卡顿呢？我们先看看那些因素影响卡顿？1.UI,包括ui的绘制,刷新等2.启动,包括冷启动,热启
Android-App的设计架构经验谈，终获offer web大美女程序员 android 移动开发面试
前言想要成为一名优秀的Android开发，你需要一份完备的知识体系，在这里，让我们一起成长为自己所想的那样~。学算法真的很痛苦，虽然大数据现在很火，但找到适合自己定位的职业也未尝不是一种合理选择。投百度的经历非常坎坷，想写出来和大家分享一下，希望能带给和我一样准备不是非常充分(无对口项目、无实习经历、渣硕算法中途转Android开发)的同学一些信心。百度一开始是想找学弟内推的，但是我投的比较早(8
android-app进阶实战篇-组件化+Flutter混编 StevenHu_Sir
架构分析该项目采用组件化方式进行编程开发语言KotlinJavaDart开发收藏和推荐模块入口类HiApplicationlogic将MainActivity的一些逻辑内聚在这，让MainActivity更加清爽UI公共组件/基类(common)HiBaseActivityHiBaseFragmentHiBaseApplicationHiFragmentTabViewUI组件库(hi-ui)HiT
Jetpack—LiveData组件的缺陷以及应对策略
一、前言为了解决Android-App开发以来一直存在的架构设计混乱的问题，谷歌推出了Jetpack-MVVM的全家桶解决方案。作为整个解决方案的核心-LiveData，以其生命周期安全，内存安全等优点，甚至有逐步取代EventBus，RxJava作为Android端状态分发组件的趋势。官网商城app团队在深度使用LiveData的过程中，也遇到了一些困难，尤其是在LiveData的观察者使用上踩
一个有趣的死循环问题思考着自己的未来
问题引出最近在工作过程中，遇到一个很有意思的bug，问题出现概率很小，很难复现，但是特别严重，直接导致用户无法使用App，属于不可容忍的问题，因此必须解决。问题出现在Android-App跑压测的过程中，我们提供的第三方库会突然停止工作，但是App的UI还是能正常的运转，于是我以我的职业敏感性当即做出判断（害羞360)dAngle-=360;}这段代码，通过两个while循环将输入角度归化到0~3
构建一个react项目并用cordova打包生成apk admin_rdc
创建一个cordova项目((项目名称:android-appapp包名:com.test.appapp名称:testapp)cordovacreateandroid-appcom.test.apptestapp进入到新建的android-app文件夹中,添加安卓开发平台cordovaplatformaddandroid--save创建一个react项目(报错请传送)creat-react-app
Android-APP之Monkey压力测试海盗谈测试 Monkey
安装屏幕分享工具：Totalcontrolcmd切换到adbshell命令下输入adbshellmonkey切换到查看所有的apk包名adbshellpmlistpackages>adbshell>monkey-pcom.xuehu365.xuehu-v-v-v-s10000100000--throttle300>D:\monkey_test.txt上面这种方式会出现以下错误>adbshellmo
使用git克隆指定分支的代码 Seven7707 git
今天想学习一下开源中国Android客户端的app源码，源码的Git地址：http://git.oschina.net/oschina/android-app，如下图所示：由于Master主分支上没有放置源码，因此需要切换到指定的Tag分支去查看，如下图所示：切换到v2.8.1这个分支就可以看到具体的代码了，如下图所示：获取的Git地址是https协议如果使用ssh协议，需要添加ssh码进入到在指
简易机顶盒launcher开发技术积累积跬步以致千里工作学习记录
最近花了一个多星期的时间做了一个android机顶盒的简易launcher,实现的功能及用到的相关Android-APP开发技术如下：1.布局相关知识的积累——嵌套多层级layout以及控件；通过xml配置改变控件的选中与否状态；2.字体与图片滚动实现；3.音视频播放技术；（launcher首页播放IPTV中的直播节目）4.倒影效果的实现；主要是一些API的熟悉与应用，同时要注意是否有内存泄露的风
java.lang.IllegalArgumentException: AppIndex: The URI scheme must be 'android-app' and follow the fo jyp123123 AS
找到Causedby所只的类，删除里面系统自动生成的代码，即下图中的三个方法，全部删除，就可以恢复正常
android-App Widget Host desaco Android 编程
bindAppWidgetIdIfAllowed(),allocateAppWidgetId().AppWidgetHostViewupdateAppWidgetOptions()andupdateAppWidgetSize()RegardlessoftheversionofAndroidyouaretargeting,allhostshavethefollowingresponsibilitie
Android-APP内存优化 Cry_Kill Android小技巧 Android
为什么要进行内存优化APP运行内存限制，OOM导致APP崩溃APP性能：流畅性、响应速度和用户体验查看APP内存的方法和工具我们先获取系统服务，我们通过getSystemService传入什么参数呢？下面就先说下各个参数代表的是什么吧：参数名获取了什么系统服务WINDOW_SERVICE窗口管理器LAYOUT_INFLATER_SERVICE布局管理ACTIVITY_SERVICE活动管理POWE
Android开发之深度项目设计探索（一）骑小猪看流星
如何快速高效构建一款优雅的Android-app架构是大家常聊的话题，本系列文章旨在分析研究探讨基于巨人的肩膀上搭建一款app项目架构。不仅是为了加深对知识点的学习以使用，而且也为了后面的准备。目前已经有很多开发者贡献了他们的架构轮子，为他们的开源精神点赞。另外，一些优秀的架构涉及到的知识点也值得我们学习和研究（优秀的框架当然可以直接拿来用嘛，这就是开源的灵魂，人人为我，我为人人）下面是深度项目用
Activity.onSaveInstanceState(); 和onRestoreInstanceState()的使用 Android移动开发者 Activity
android-APP长期运行于后台，重启后如何避免异常问题的详细描述是这样的：android中，当我们按home键（一般指手机的物理按钮的中间那个键）回到手机桌面，此时app并没有退出，而是一直运行与后台中，此时如果我们点击app图标，还是会进入刚刚的界面之中。但是这存在一个问题，就是如果内存紧张或者当我们回到桌面，点击了别的应用造成内存紧张，此时再通过点击图标进入app，此时会出现异常。这样造
Android-App前台进程监听ActivityLifecycleCallbacks zhanf
在开发中会遇到判断App是否是前台进程，其实方法挺多，比如RunningTask(5.0之前)、UsageStatsManager(5.0之后适用)、RunningProcess(不能有效识别，比如三星手机)、ActivityLifecycleCallbacks，其中最有效的方法是通过ActivityLifecycleCallbacks进行监听，本文只介绍这种。先了解下ActivityLifecy
渗透测试-Android-App渗透测试测试流程 weixin_33919950
渗透测试-Android-App渗透测试测试流程0x01：前言：仅作为记录以供参考0x02：漏洞测试方法以及修复方案一、组件以及源码安全1、签名校验命令：//test.apk为要检测的包jarsigner.exe-verifytest.apk-verbose–certs如果显示jar已验证即为已做了签名校验修复方案：增加验证签名机制。2、任意调试漏洞通过对apk文件进行解包，检测AndroidMa
Android-APP启动优化倾尽杯中酒 Android 性能优化 Android启动优化 android app 安卓
Android-APP启动优化伪优化案例占位图方案总结（修改全局的主题）修改局部的主题真正的优化优化真正优化的总结黑白屏问题优化黑白屏在商业APP中的价值如何使用Traceview工具对优化定位处理伪优化用于用户体验，用来给到用户体验，没有实质性的优化案例注意看这一块（parent=“Theme.AppCompat.Light”）如果没写这一块，启动时会是一个黑屏，写了这一块，启动时会是一个白屏；
多线程编程之join()方法周凡杨 java JOIN 多线程编程线程
现实生活中，有些工作是需要团队中成员依次完成的，这就涉及到了一个顺序问题。现在有T1、T2、T3三个工人，如何保证T2在T1执行完后执行，T3在T2执行完后执行？问题分析：首先问题中有三个实体，T1、T2、T3，因为是多线程编程，所以都要设计成线程类。关键是怎么保证线程能依次执行完呢？ Java实现过程如下： public class T1 implements Runnabl
java中switch的使用 bingyingao java enum break continue
java中的switch仅支持case条件仅支持int、enum两种类型。用enum的时候，不能直接写下列形式。 switch (timeType) { case ProdtransTimeTypeEnum.DAILY: break; default: br
hive having count 不能去重 daizj hive 去重 having count 计数
hive在使用having count()是，不支持去重计数 hive (default)> select imei from t_test_phonenum where ds=20150701 group by imei having count(distinct phone_num)>1 limit 10; FAILED: SemanticExcep
WebSphere对JSP的缓存周凡杨 WAS JSP 缓存
对于线网上的工程，更新JSP到WebSphere后，有时会出现修改的jsp没有起作用，特别是改变了某jsp的样式后，在页面中没看到效果，这主要就是由于websphere中缓存的缘故，这就要清除WebSphere中jsp缓存。要清除WebSphere中JSP的缓存，就要找到WAS安装后的根目录。现服务
设计模式总结朱辉辉33 java 设计模式
1.工厂模式 1.1 工厂方法模式 (由一个工厂类管理构造方法) 1.1.1普通工厂模式(一个工厂类中只有一个方法) 1.1.2多工厂模式(一个工厂类中有多个方法) 1.1.3静态工厂模式(将工厂类中的方法变成静态方法) &n
实例：供应商管理报表需求调研报告老A不折腾 finereport 报表系统报表软件信息化选型
引言随着企业集团的生产规模扩张，为支撑全球供应链管理，对于供应商的管理和采购过程的监控已经不局限于简单的交付以及价格的管理，目前采购及供应商管理各个环节的操作分别在不同的系统下进行，而各个数据源都独立存在，无法提供统一的数据支持；因此，为了实现对于数据分析以提供采购决策，建立报表体系成为必须。业务目标 1、通过报表为采购决策提供数据分析与支撑 2、对供应商进行综合评估以及管理，合理管理和
mysql 林鹤霄
转载源：http://blog.sina.com.cn/s/blog_4f925fc30100rx5l.html mysql -uroot -p ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES) [root@centos var]# service mysql
Linux下多线程堆栈查看工具(pstree、ps、pstack) aigo linux
原文：http://blog.csdn.net/yfkiss/article/details/6729364 1. pstree pstree以树结构显示进程$ pstree -p work | grep adsshd(22669)---bash(22670)---ad_preprocess(4551)-+-{ad_preprocess}(4552) &n
html input与textarea 值改变事件 alxw4616 JavaScript
// 文本输入框(input) 文本域(textarea)值改变事件 // onpropertychange(IE) oninput(w3c) $('input,textarea').on('propertychange input', function(event) { console.log($(this).val()) });
String类的基本用法百合不是茶 String
字符串的用法; // 根据字节数组创建字符串 byte[] by = { 'a', 'b', 'c', 'd' }; String newByteString = new String(by); 1,length() 获取字符串的长度 &nbs
JDK1.5 Semaphore实例 bijian1013 java thread java多线程 Semaphore
Semaphore类一个计数信号量。从概念上讲，信号量维护了一个许可集合。如有必要，在许可可用前会阻塞每一个 acquire()，然后再获取该许可。每个 release() 添加一个许可，从而可能释放一个正在阻塞的获取者。但是，不使用实际的许可对象，Semaphore 只对可用许可的号码进行计数，并采取相应的行动。 S
使用GZip来压缩传输量 bijian1013 java GZip
启动GZip压缩要用到一个开源的Filter：PJL Compressing Filter。这个Filter自1.5.0开始该工程开始构建于JDK5.0，因此在JDK1.4环境下只能使用1.4.6。 PJL Compressi
【Java范型三】Java范型详解之范型类型通配符 bit1129 java
定义如下一个简单的范型类， package com.tom.lang.generics; public class Generics<T> { private T value; public Generics(T value) { this.value = value; } }
【Hadoop十二】HDFS常用命令 bit1129 hadoop
1. 修改日志文件查看器 hdfs oev -i edits_0000000000000000081-0000000000000000089 -o edits.xml cat edits.xml 修改日志文件转储为xml格式的edits.xml文件，其中每条RECORD就是一个操作事务日志 2. fsimage查看HDFS中的块信息等 &nb
怎样区别nginx中rewrite时break和last ronin47
在使用nginx配置rewrite中经常会遇到有的地方用last并不能工作，换成break就可以，其中的原理是对于根目录的理解有所区别，按我的测试结果大致是这样的。 location / { proxy_pass http://test;
java-21.中兴面试题输入两个整数 n 和 m ，从数列 1 ， 2 ， 3.......n 中随意取几个数 , 使其和等于 m bylijinnan java
import java.util.ArrayList; import java.util.List; import java.util.Stack; public class CombinationToSum { /* 第21 题 2010 年中兴面试题编程求解：输入两个整数 n 和 m ，从数列 1 ， 2 ， 3.......n 中随意取几个数 , 使其和等
eclipse svn 帐号密码修改问题开窍的石头 eclipse SVN svn帐号密码修改
问题描述： Eclipse的SVN插件Subclipse做得很好，在svn操作方面提供了很强大丰富的功能。但到目前为止，该插件对svn用户的概念极为淡薄，不但不能方便地切换用户，而且一旦用户的帐号、密码保存之后，就无法再变更了。解决思路：删除subclipse记录的帐号、密码信息，重新输入
[电子商务]传统商务活动与互联网的结合 comsci 电子商务
某一个传统名牌产品，过去销售的地点就在某些特定的地区和阶层，现在进入互联网之后，用户的数量群突然扩大了无数倍，但是，这种产品潜在的劣势也被放大了无数倍，这种销售利润与经营风险同步放大的效应，在最近几年将会频繁出现。。。。如何避免销售量和利润率增加的
java 解析 properties-使用 Properties-可以指定配置文件路径 cuityang java properties
#mq xdr.mq.url=tcp://192.168.100.15:61618; import java.io.IOException; import java.util.Properties; public class Test { String conf = "log4j.properties"; private static final
Java核心问题集锦 darrenzhu java 基础核心难点
注意，这里的参考文章基本来自Effective Java和jdk源码 1)ConcurrentModificationException 当你用for each遍历一个list时，如果你在循环主体代码中修改list中的元素，将会得到这个Exception，解决的办法是： 1)用listIterator, 它支持在遍历的过程中修改元素， 2)不用listIterator, new一个
1分钟学会Markdown语法 dcj3sjt126com markdown
markdown 简明语法基本符号 *,-,+ 3个符号效果都一样，这3个符号被称为 Markdown符号空白行表示另起一个段落 `是表示inline代码，tab是用来标记代码段，分别对应html的code，pre标签换行单一段落( <p>) 用一个空白行连续两个空格会变成一个 <br> 连续3个符号，然后是空行
Gson使用二（GsonBuilder） eksliang json gson GsonBuilder
转载请出自出处：http://eksliang.iteye.com/blog/2175473 一.概述 GsonBuilder用来定制java跟json之间的转换格式二.基本使用实体测试类：温馨提示：默认情况下@Expose注解是不起作用的,除非你用GsonBuilder创建Gson的时候调用了GsonBuilder.excludeField
报ClassNotFoundException: Didn't find class "...Activity" on path: DexPathList gundumw100 android
有一个工程，本来运行是正常的，我想把它移植到另一台PC上，结果报： java.lang.RuntimeException: Unable to instantiate activity ComponentInfo{com.mobovip.bgr/com.mobovip.bgr.MainActivity}: java.lang.ClassNotFoundException: Didn't f
JavaWeb之JSP指令 ihuning javaweb
要点 JSP指令简介 page指令 include指令 JSP指令简介 JSP指令（directive）是为JSP引擎而设计的，它们并不直接产生任何可见输出，而只是告诉引擎如何处理JSP页面中的其余部分。 JSP指令的基本语法格式： <%@ 指令属性名="
mac上编译FFmpeg跑ios 啸笑天 ffmpeg
1、下载文件：https://github.com/libav/gas-preprocessor，复制gas-preprocessor.pl到/usr/local/bin/下，修改文件权限：chmod 777 /usr/local/bin/gas-preprocessor.pl 2、安装yasm-1.2.0 curl http://www.tortall.net/projects/yasm
sql mysql oracle中字符串连接 macroli oracle sql mysql SQL Server
有的时候，我们有需要将由不同栏位获得的资料串连在一起。每一种资料库都有提供方法来达到这个目的： MySQL: CONCAT() Oracle: CONCAT(), || SQL Server: + CONCAT() 的语法如下： Mysql 中 CONCAT(字串1, 字串2, 字串3, ...): 将字串1、字串2、字串3，等字串连在一起。请注意，Oracle的CON
Git fatal: unab SSL certificate problem: unable to get local issuer ce rtificate qiaolevip 学习永无止境每天进步一点点 git 纵观千象
// 报错如下： $ git pull origin master fatal: unable to access 'https://git.xxx.com/': SSL certificate problem: unable to get local issuer ce rtificate // 原因：由于git最新版默认使用ssl安全验证，但是我们是使用的git未设
windows命令行设置wifi surfingll windows wifi 笔记本wifi
还没有讨厌无线wifi的无尽广告么，还在耐心等待它慢慢启动么教你命令行设置笔记本电脑wifi： 1、开启wifi命令 netsh wlan set hostednetwork mode=allow ssid=surf8 key=bb123456 netsh wlan start hostednetwork pause 其中pause是等待输入，可以去掉 2、
Linux（Ubuntu）下安装sysv-rc-conf wmlJava linux ubuntu sysv-rc-conf
安装：sudo apt-get install sysv-rc-conf 使用：sudo sysv-rc-conf 操作界面十分简洁，你可以用鼠标点击，也可以用键盘方向键定位，用空格键选择，用Ctrl+N翻下一页，用Ctrl+P翻上一页，用Q退出。背景知识 sysv-rc-conf是一个强大的服务管理程序，群众的意见是sysv-rc-conf比chkconf
svn切换环境，重发布应用多了javaee标签前缀 zengshaotao javaee
更换了开发环境，从杭州，改变到了上海。svn的地址肯定要切换的，切换之前需要将原svn自带的.svn文件信息删除，可手动删除，也可通过废弃原来的svn位置提示删除.svn时删除。然后就是按照最新的svn地址和规范建立相关的目录信息，再将原来的纯代码信息上传到新的环境。然后再重新检出，这样每次修改后就可以看到哪些文件被修改过，这对于增量发布的规范特别有用。检出