Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Scott McWhirter
    @konobi
    yeah, turns out there was a bug in node-usb itself
    Andrey Sidorov
    @sidorares
    Yeah, I can probably download vm from microsoft
    Scott McWhirter
    @konobi
    I also streamlined the mincrypt stuff, and added the 2 other dependencies
    but now one can actually talk to the usb device... though that's flakey as all hell, but it's progress at least
    the tcp version is working much better, but the AdbStream stuff isn't handling it all that well
    i encapsulated tcp/usb in a "link" stream
    so there's probably a better way to encapsulate it now
    i'm going to keep going with the usb stuff, but would you fancy having a look at the stuff over tcp?
    Andrey Sidorov
    @sidorares
    I'll try later today ( after flashing to 4.4.2 )
    Scott McWhirter
    @konobi
    cool
    Andrey Sidorov
    @sidorares
    Do you have your new usb code in master?
    Scott McWhirter
    @konobi
    yup
    Andrey Sidorov
    @sidorares
    cool, I'll try it now
    Andrey Sidorov
    @sidorares
    had to manually install "bindings" - need to add to package.json
    Scott McWhirter
    @konobi
    oh... doh... forgot about that one
    oh... and nan too
    Andrey Sidorov
    @sidorares
    USBDevice.is_adb_available return undefined for me
    ( and result is compared with null one line down - link.js:139 )
    Scott McWhirter
    @konobi
    the device is plugged in with usb debudding enabled?
    Andrey Sidorov
    @sidorares
    it seems that it was not connected properly
    Now I have LIBUSB_ERROR_ACCESS
    ( but check for null is still incorrect if no device connected )
    should I update node-usb somehow?
    Scott McWhirter
    @konobi
    nah, i worked around it
    Andrey Sidorov
    @sidorares
    I have usb: 0.3.11 in node_modules
    Scott McWhirter
    @konobi
    in usb.js, up at the top there's a debug level setting, enable that
    Andrey Sidorov
    @sidorares
    [ 0.230538] [00004f03] libusb: debug [libusb_release_interface] interface 1
    [ 0.231063] [00000707] libusb: debug [libusb_claim_interface] interface 1
    [ 0.231585] [00000707] libusb: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
    [ 0.231596] [00000707] libusb: debug [libusb_claim_interface] interface 1
    [ 0.231968] [00000707] libusb: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
    trying killall adb
    ...
    Scott McWhirter
    @konobi
    huh
    Andrey Sidorov
    @sidorares
    now it's different

    0.231483] [00004f03] libusb: debug [libusb_release_interface] interface 1
    [ 0.232074] [00000707] libusb: debug [libusb_claim_interface] interface 1
    [ 0.232757] [00000707] libusb: debug [get_endpoints] building table of endpoints.
    [ 0.232775] [00000707] libusb: debug [get_endpoints] interface: 1 pipe 1: dir: 1 number: 2
    [ 0.232787] [00000707] libusb: debug [get_endpoints] interface: 1 pipe 2: dir: 0 number: 2
    [ 0.232824] [00000707] libusb: debug [darwin_claim_interface] interface opened
    [ 0.232909] [00004d03] libusb: debug [libusb_set_interface_alt_setting] interface 1 altsetting 0
    [ 0.901005] [00004d03] libusb: error [darwin_reset_device] ResetDevice: unknown error (0xe00002bd)
    [ 0.901028] [00004d03] libusb: debug [get_endpoints] building table of endpoints.
    [ 0.901050] [00004d03] libusb: error [get_endpoints] error getting pipe information for pipe 1: unknown error (0xe0004061)
    [ 0.901270] [00004d03] libusb: error [darwin_set_interface_altsetting] could not build endpoint table
    [ 0.901595] [00000707] libusb: debug [libusb_claim_interface] interface 1

    /private/tmp/node-adbhost/lib/usb.js:96
    throw err;
    ^
    Error: LIBUSB_ERROR_OTHER

    Scott McWhirter
    @konobi
    oh... make sure you've killed off adbd
    Andrey Sidorov
    @sidorares
    I killed local adb daemon
    Scott McWhirter
    @konobi
    using example/screenshot.js?
    Andrey Sidorov
    @sidorares
    shell.js
    Scott McWhirter
    @konobi
    ah, i didn't change that one to match up
    Andrey Sidorov
    @sidorares
    var adbhost = require('../index.js');
    var adb = adbhost.createConnection({
    usb: true,
    pub_key_path: '/Users/locomote/.android/adbkey.pub'
    }, function (adb) {
    var shell = adb.createStream('shell:');
    process.stdin.pipe(shell);
    shell.pipe(process.stdout);
    });
    Scott McWhirter
    @konobi
    key_path too
    (private key)
    Andrey Sidorov
    @sidorares
    same LIBUSB_ERROR_OTHER
    Scott McWhirter
    @konobi
    yeah... it's still super flaky
    but at least the device is responding now
    Andrey Sidorov
    @sidorares
    sometimes it's LIBUSB_ERROR_NOT_FOUND
    [ 0.236091] [00000707] libusb: debug [libusb_get_device_list]
    [ 0.236125] [00000707] libusb: debug [discovered_devs_append] need to increase capacity
    [ 0.236185] [00000707] libusb: debug [libusb_get_device_descriptor]
    [ 0.236262] [00000707] libusb: debug [libusb_get_device_descriptor]
    [ 0.236289] [00000707] libusb: debug [libusb_get_device_descriptor]
    [ 0.236311] [00000707] libusb: debug [libusb_get_device_descriptor]
    [ 0.236342] [00000707] libusb: debug [libusb_get_device_descriptor]
    [ 0.236372] [00000707] libusb: debug [libusb_get_device_descriptor]
    [ 0.236402] [00000707] libusb: debug [libusb_get_device_descriptor]
    [ 0.236425] [00000707] libusb: debug [libusb_get_device_descriptor]
    [ 0.236441] [00000707] libusb: debug [libusb_get_device_descriptor]
    [ 0.236465] [00000707] libusb: debug [libusb_get_device_descriptor]
    [ 0.236710] [00000707] libusb: debug [libusb_open] open 29.7
    [ 0.236810] [00000707] libusb: debug [usbi_add_pollfd] add fd 41 events 1
    [ 0.236818] [00000707] libusb: debug [darwin_open] device open for access
    [ 0.236848] [00004c03] libusb: debug [handle_events] poll() returned 1
    [ 0.236861] [00004c03] libusb: debug [handle_events] caught a fish on the control pipe
    [ 0.236878] [00004c03] libusb: debug [libusb_get_next_timeout] no URBs, no timeout!
    [ 0.236884] [00004c03] libusb: debug [libusb_try_lock_events] someone else is modifying poll fds
    [ 0.236888] [00004c03] libusb: debug [libusb_handle_events_timeout_completed] event handler was active but went away, retrying
    [ 0.236892] [00004c03] libusb: debug [libusb_handle_events_timeout_completed] doing our own event handling
    [ 0.236898] [00004c03] libusb: debug [handle_events] poll() 3 fds with timeout in 60000ms
    Scott McWhirter
    @konobi
    yeah, lots of stuff to work on =0(
    tcp is acting much more nicely though, auth 'n all
    Andrey Sidorov
    @sidorares
    cool
    Scott McWhirter
    @konobi
    also invited kruton to join us
    kruton/adb-on-chrome#1