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
    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
    Scott McWhirter
    @konobi
    howdy
    Andrey Sidorov
    @sidorares
    Hi
    Scott McWhirter
    @konobi
    how goes? any luck?
    Andrey Sidorov
    @sidorares
    no luck - kids sick, had to stay home today
    Scott McWhirter
    @konobi
    oh... boo... hope they're feeling better
    Scott McWhirter
    @konobi
    how goes?
    Andrey Sidorov
    @sidorares
    hey. No news about module. But kids are getting better :)
    How are you?
    Scott McWhirter
    @konobi
    a bit tired
    we had a product launch recently, so still winding down from that
    thankfully worked out what the issue is with usb... but my brane is a little fried for now to think about it ^_^
    Scott McWhirter
    @konobi
    howdy!
    how's things?
    Andrey Sidorov
    @sidorares
    Hey! Sorry, got distracted from this project with other things
    Haven't checked yet but they might have pure python crypto handshake stuff in there
    And it is probably using libusb the same way you are using it - would be interesting to compare
    Scott McWhirter
    @konobi
    i know what's going on the the usb stuff, i just haven't had time to look at it
    essentially usb comms need to be one-way at any one time
    so write write write, then read read read... so need to do some marshalling of the usb stream
    Andrey Sidorov
    @sidorares
    So its not duplex??
    Scott McWhirter
    @konobi
    kinda
    it's duplex, but you need to do the entire convo in chunks
    and... that's based on the adb protocol
    Andrey Sidorov
    @sidorares
    but not write and read at the same time?
    Scott McWhirter
    @konobi
    yup
    and then usb has maximum chunk sizes too, so you have to follow that rule too
    Andrey Sidorov
    @sidorares
    what do you mean by protocol? afaik I was able to write and read simultaneously over tcp