Missing minicap/shared/android-9 for SO-01C

171 views
Skip to first unread message

Junichi Chiba

unread,
Jul 15, 2015, 12:16:39 AM7/15/15
to ope...@googlegroups.com
Hi,

I faced with a problem with SO-01C Android 2.3.3.
When I connect it to a Mac Yosemite and Ubuntu 15.04 machine,
I get the following logs repeatedly, even after removing the device.
Looking at log [3] below, android-9 support seems to be missing from minicap directory.
Could you advise me how to setup the file?
This model is in your device-db so I believe it's supported.
As for log [1] and [2], do you think the cause is the same?

Logs:

[1] Connecting SO-01C, I get below until I remove the cable.
INF/provider 36021 [*] Cleaning up device worker "43423541314356515837"
ERR/provider 36021 [*] Device worker "43423541314356515837" died with code 1
INF/provider 36021 [*] Restarting device worker "43423541314356515837"
INF/device:support:push 83899 [43423541314356515837] Sending output to "tcp://127.0.0.1:7116"
INF/device 83899 [43423541314356515837] Preparing device
INF/device:support:sub 83899 [43423541314356515837] Receiving input from "tcp://127.0.0.1:7114"
INF/device:support:sub 83899 [43423541314356515837] Subscribing to permanent channel "*ALL"
FTL/device 83899 [43423541314356515837] Setup had an error FailError: Failure: 'device not found'
    at /Users/stfuser/git/stf/node_modules/adbkit/lib/adb/parser.js:226:31
From previous event:
    at Parser.readError (/Users/stfuser/git/stf/node_modules/adbkit/lib/adb/parser.js:225:31)
    at /Users/stfuser/git/stf/node_modules/adbkit/lib/adb/command/host/transport.js:25:35
From previous event:
    at HostTransportCommand.execute (/Users/stfuser/git/stf/node_modules/adbkit/lib/adb/command/host/transport.js:19:39)
    at /Users/stfuser/git/stf/node_modules/adbkit/lib/adb/client.js:257:47
    at processImmediate [as _immediateCallback] (timers.js:367:17)
From previous event:
    at Client.transport (/Users/stfuser/git/stf/node_modules/adbkit/lib/adb/client.js:256:32)
    at Client.waitBootComplete (/Users/stfuser/git/stf/node_modules/adbkit/lib/adb/client.js:531:19)
    at ensureBootComplete (/Users/stfuser/git/stf/lib/units/device/support/adb.js:19:15)
    at /Users/stfuser/git/stf/lib/units/device/support/adb.js:28:12
    at SerialSyrup.ParallelSyrup.invoke (/Users/stfuser/git/stf/node_modules/stf-syrup/lib/parallel.js:54:24)
    at /Users/stfuser/git/stf/node_modules/stf-syrup/lib/serial.js:43:33
    at process._tickCallback (node.js:355:11)
FTL/util:lifecycle 83899 [43423541314356515837] Shutting down due to fatal error
INF/provider 36021 [*] Cleaning up device worker "43423541314356515837"
ERR/provider 36021 [*] Device worker "43423541314356515837" died with code 1
INF/provider 36021 [*] Restarting device worker "43423541314356515837"

[2] After removing the cable, it still outputs ERR.
INF/provider 36021 [*] Cleaning up device worker "43423541314356515837"
ERR/provider 36021 [*] Device worker "43423541314356515837" died with code 1
INF/provider 36021 [*] Restarting device worker "43423541314356515837"
  error: missing required argument `--screen-port'
INF/provider 36021 [*] Cleaning up device worker "43423541314356515837"
ERR/provider 36021 [*] Device worker "43423541314356515837" died with code 1
INF/provider 36021 [*] Restarting device worker "43423541314356515837"
  error: missing required argument `--screen-port'

[3] After a few minutes, the log further becomes
INF/device:support:sub 87029 [43423541314356515837] Subscribing to permanent channel "*ALL"
INF/device:support:properties 87029 [43423541314356515837] Loading properties
INF/device:support:abi 87029 [43423541314356515837] Supports ABIs armeabi-v7a, armeabi
FTL/device 87029 [43423541314356515837] Setup had an error Error: At least one of these paths should exist: /Users/stfuser/git/stf/vendor/minicap/shared/android-2.3.2/armeabi-v7a/minicap.so, /Users/stfuser/git/stf/vendor/minicap/shared/android-9/armeabi-v7a/minicap.so, /Users/stfuser/git/stf/vendor/minicap/shared/android-2.3.2/armeabi/minicap.so, /Users/stfuser/git/stf/vendor/minicap/shared/android-9/armeabi/minicap.so
    at Object.module.exports.requiredMatch (/Users/stfuser/git/stf/lib/util/pathutil.js:33:9)
    at /Users/stfuser/git/stf/lib/units/device/resources/minicap.js:35:23
    at SerialSyrup.ParallelSyrup.invoke (/Users/stfuser/git/stf/node_modules/stf-syrup/lib/parallel.js:54:24)
    at /Users/stfuser/git/stf/node_modules/stf-syrup/lib/serial.js:43:33
    at tryCatch1 (/Users/stfuser/git/stf/node_modules/stf-syrup/node_modules/bluebird/js/main/util.js:63:19)
    at Promise$_callHandler [as _callHandler] (/Users/stfuser/git/stf/node_modules/stf-syrup/node_modules/bluebird/js/main/promise.js:708:13)
    at Promise$_settlePromiseFromHandler [as _settlePromiseFromHandler] (/Users/stfuser/git/stf/node_modules/stf-syrup/node_modules/bluebird/js/main/promise.js:724:18)
    at Promise$_settlePromiseAt [as _settlePromiseAt] (/Users/stfuser/git/stf/node_modules/stf-syrup/node_modules/bluebird/js/main/promise.js:896:14)
    at Promise$_fulfillPromises [as _fulfillPromises] (/Users/stfuser/git/stf/node_modules/stf-syrup/node_modules/bluebird/js/main/promise.js:1041:14)
    at Async$_consumeFunctionBuffer [as _consumeFunctionBuffer] (/Users/stfuser/git/stf/node_modules/stf-syrup/node_modules/bluebird/js/main/async.js:74:12)
    at Async$consumeFunctionBuffer (/Users/stfuser/git/stf/node_modules/stf-syrup/node_modules/bluebird/js/main/async.js:37:14)
    at process._tickCallback (node.js:355:11)
FTL/util:lifecycle 87029 [43423541314356515837] Shutting down due to fatal error
INF/provider 87007 [*] Cleaning up device worker "43423541314356515837"
ERR/provider 87007 [*] Device worker "43423541314356515837" died with code 1
INF/provider 87007 [*] Restarting device worker "43423541314356515837" 

Many thanks in advance.

Simo Kinnunen

unread,
Jul 15, 2015, 6:14:05 AM7/15/15
to ope...@googlegroups.com, junichi....@gmail.com
Hi,

As can be seen from the logs, your device is actually running Android 2.3.2, which is SDK level 9. STF requires 2.3.3 (SDK level 10) or newer.

The oldest device we have is Android 2.3.3, which means that we can't support lower levels even if we wanted to. If someone is willing to sponsor and send an older physical device to me, then I can promise to at least take a look, although I can't promise any results.

Simo

Simo Kinnunen

unread,
Jul 15, 2015, 7:16:58 AM7/15/15
to ope...@googlegroups.com, si...@shoqolate.com, junichi....@gmail.com
Hi,

Actually I just checked out the 2.3_r1 AOSP branch, and it seems like there are no changes to the APIs we use. So I compiled and added it to the latest master, but we don't actually have a device to test it with. Could you update your STF to the latest master and let me know if your device works now?

Thanks,

Simo

Junichi Chiba

unread,
Jul 16, 2015, 2:24:49 AM7/16/15
to ope...@googlegroups.com, si...@shoqolate.com, junichi....@gmail.com
Oh, my mistake. Yes, it's actually Android 2.3.2.
OK I will note that STF requires Android 2.3.3 or above.

I tried with the latest master.
I plugged in SO-01C 2.3.2 and it works with SFT perfectly.
Thank you very much:)
Reply all
Reply to author
Forward
0 new messages