Destroying virtual display on Samsung Galaxy S4 (GT-I9500)

[AndreySkorkin]

Periodically (once every 3 runs) the minicap stops working on the Samsung Galaxy S4 (GT-I9500, API level 17). The service starts, but closes after a couple of seconds. The log contains only the following information:

INFO: Using projection 1080x1920@1080x1920/0
INFO: (external/MY_minicap/src/minicap_17.cpp:239) Creating SurfaceComposerClient
INFO: (external/MY_minicap/src/minicap_17.cpp:242) Performing SurfaceComposerClient init check
INFO: (external/MY_minicap/src/minicap_17.cpp:249) Creating virtual display
INFO: (external/MY_minicap/src/minicap_17.cpp:255) Creating CPU consumer
INFO: (external/MY_minicap/src/minicap_17.cpp:261) Creating buffer queue
INFO: (external/MY_minicap/src/minicap_17.cpp:267) Creating frame waiter
INFO: (external/MY_minicap/src/minicap_17.cpp:271) Publishing virtual display
INFO: (jni/minicap/JpgEncoder.cpp:64) Allocating 6268932 bytes for JPG encoder
INFO: (external/MY_minicap/src/minicap_17.cpp:286) Destroying virtual display

Also, other services not related to the minicap stop working. At such moments, the logcat contains a lot of the following messages:

D/SensorHubManager( 3815): onGetSensorHubDataLocked: library = 1, 1, 15, 17
D/Sensorhubs( 3543): readContextData: 1, 1, 15, 17
D/SensorHubManager( 3815): onGetSensorHubDataLocked: library = 1, 1, 15, 17
D/Sensorhubs( 3543): readContextData: 1, 1, 15, 17
D/SensorHubManager( 3815): onGetSensorHubDataLocked: library = 1, 1, 15, 17
D/Sensorhubs( 3543): readContextData: 1, 1, 15, 17

Such issues do not arise without running the minicap service on this device.

Have you encountered such issues on the GT-I9500? How can this be fixed?

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.93. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.