ABD debugging, service lost at boot

Discussion in 'ZIDOO X9' started by DragonFly, Jun 14, 2015.

  1. DragonFly

    DragonFly Member

    A very handy option on the X9 is the ability to connect through ADB (Android Debug Bridge), using an USB, Wifi or LAN connection. There is one condition: USB debugging (under Developer options) must be ticked.

    Once enabled and because the device is rooted, you can view the entire filesystem using Total Commander and the "Android ADB Plugin". See http://www.uniqtec.eu/applications/android-adb.html for details. It looks something like this:

    [​IMG]

    This way you can easily install apps, copy files etc.
    There is NO NEED to install third-party apps for this to work on the X9, just enable USB debugging. When first connected you'll need to accept the connection and trust the computer you are connecting from.

    This works fine when manually enabling USB debugging. However, in the case of the X9, USB debugging over TCP settings are lost at boot. For this to work very WIFI and more importantly over LAN, at every boot, the user needs to manually disable and re-enable the USB debugging options.

    It seems the "adbd" service is not started (selectively) at boot. There are third party apps that start the adbd service at boot (like ADB Manager or Wifi ADB) using something like:
    Code:
    setprop service.abd.tcp.port 5555
    stop adbd
    start adbd
    
    but these will NOT work if the device is connected through LAN.

    So, my question is, how to start the adbd service automatically when connected through LAN? (mainly for testing purposes)
     
    Last edited: Jun 14, 2015
  2. warren_wh

    warren_wh Active Member Staff Member Zidoo TECH Supporter

    Dear DragonFly.

    Pls try

    Settings->System->About Box->Build number[Press until the out 'Develpoper options']

    Choose to[Seveloper options]

    Click on the [USB debugging] and Allow USB debugging is ok.

    After
    adb connect 192.168.xx.xx


    QQ图片20150615175237.png
     
  3. DragonFly

    DragonFly Member

    Perhaps, you misunderstand me.

    It's not that I don't know HOW to enable USB debugging, it's the fact that once enabled (and I want to connect through WIFI or LAN), I have to manually disable and then re-enable it after a reboot. Settings should be remembered (the adbd service should be started).

    In short: settings are lost at reboot.
    Perhaps there's something missing in either build prop or init.rc
    Code:
    
    06-15 16:52:59.110 E/UsbDebuggingManager( 1540): got -1 reading
    06-15 16:52:59.110 E/UsbDebuggingManager( 1540): Communication error:
    06-15 16:52:59.110 E/UsbDebuggingManager( 1540): java.io.IOException: No such file or directory
    06-15 16:52:59.110 E/UsbDebuggingManager( 1540):     at android.net.LocalSocketImpl.connectLocal(Native Method)
    06-15 16:52:59.110 E/UsbDebuggingManager( 1540):     at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:287)
    06-15 16:52:59.110 E/UsbDebuggingManager( 1540):     at android.net.LocalSocket.connect(LocalSocket.java:130)
    06-15 16:52:59.110 E/UsbDebuggingManager( 1540):     at com.android.server.usb.UsbDebuggingManager.listenToSocket(UsbDebuggingManager.java:75)
    06-15 16:52:59.110 E/UsbDebuggingManager( 1540):     at com.android.server.usb.UsbDebuggingManager.run(UsbDebuggingManager.java:111)
    06-15 16:52:59.110 E/UsbDebuggingManager( 1540):     at java.lang.Thread.run(Thread.java:841)
     
    Last edited: Jun 15, 2015

Share This Page