如何在OTG上对Android进行以太网工作? -- networking 领域 和 usb-connection-mode 领域 和 kernel 领域 和 usb-on-the-go 领域 和 usb-drivers 领域 android 相关 的问题

How to make Ethernet work on Android over OTG?


简体版||繁體版
2
vote

问题

中文

我正在尝试在OTG电缆上使用连接到Android 7设备的LTE调制解调器。内核识别设备并使用 cdc_ether 注册它,但我无法使用设备的连接。这是因为它随后安装为USB存储?

设备在Android UI /状态栏中显示为设备。

如果我禁用MTP支持,那么设备不会寄存 cdc_ether

dmesg

  [10946.408785] usb 1-1.3: new high-speed USB device number 21 using msm_hsusb_host [10946.525287] usb 1-1.3: New USB device found, idVendor=19d2, idProduct=1225 [10946.525306] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [10946.525316] usb 1-1.3: Product: ZTE Mobile Broadband [10946.525325] usb 1-1.3: Manufacturer: ZTE,Incorporated [10946.525335] usb 1-1.3: SerialNumber: MF8610ZTED000000 [10946.529662] usb-storage 1-1.3:1.0: USB Mass Storage device detected [10946.532702] scsi host19: usb-storage 1-1.3:1.0 [10947.538579] scsi 19:0:0:0: CD-ROM            ZTE      USB SCSI CD-ROM  2.31 PQ: 0 ANSI: 2 [10952.740595] usb 1-1.3: USB disconnect, device number 21 [10953.087891] usb 1-1.3: new high-speed USB device number 22 using msm_hsusb_host [10953.232955] usb 1-1.3: New USB device found, idVendor=19d2, idProduct=1405 [10953.232969] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [10953.232977] usb 1-1.3: Product: ZTE Mobile Broadband [10953.232984] usb 1-1.3: Manufacturer: ZTE,Incorporated [10953.232991] usb 1-1.3: SerialNumber: MF8610ZTED000000 [10953.260856] cdc_ether 1-1.3:1.0 usb0: register 'cdc_ether' at usb-msm_hsusb_host-1.3, CDC Ethernet Device, 36:4b:50:b7:ef:da [10953.262322] usb-storage 1-1.3:1.2: USB Mass Storage device detected [10953.262652] scsi host20: usb-storage 1-1.3:1.2 [10954.261139] scsi 20:0:0:0: CD-ROM            ZTE      USB SCSI CD-ROM  2.31 PQ: 0 ANSI: 2   

dmesg 使用mtp禁用:

  [10664.987934] usb 1-1.3: new high-speed USB device number 19 using msm_hsusb_host [10665.105272] usb 1-1.3: New USB device found, idVendor=19d2, idProduct=1225 [10665.105291] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [10665.105301] usb 1-1.3: Product: ZTE Mobile Broadband [10665.105310] usb 1-1.3: Manufacturer: ZTE,Incorporated [10665.105320] usb 1-1.3: SerialNumber: MF8610ZTED000000 [10665.110339] usb-storage 1-1.3:1.0: USB Mass Storage device detected [10665.111320] scsi host17: usb-storage 1-1.3:1.0 [10666.110748] scsi 17:0:0:0: CD-ROM            ZTE      USB SCSI CD-ROM  2.31 PQ: 0 ANSI: 2 [10671.223090] usb 1-1.3: USB disconnect, device number 19 [10671.407859] msm_otg 78db000.usb: OTG runtime idle [10671.407887] msm_otg 78db000.usb: OTG runtime suspend   

ifconfig

  adb push0  

adb push1

  adb push2  

设备确实显示为 adb push3 ,其中mac地址在 adb push4 中列出。

english

I am trying to use an LTE modem connected to an Android 7 device over an OTG cable. The kernel recognizes the device and registers it with cdc_ether, but I am unable to use the connection from the device. Is this because it is subsequently mounted as USB storage?

The device does not show up as a device in the Android UI / status bar.

If I disable MTP support, then the device wont register cdc_ether at all.

dmesg:

[10946.408785] usb 1-1.3: new high-speed USB device number 21 using msm_hsusb_host [10946.525287] usb 1-1.3: New USB device found, idVendor=19d2, idProduct=1225 [10946.525306] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [10946.525316] usb 1-1.3: Product: ZTE Mobile Broadband [10946.525325] usb 1-1.3: Manufacturer: ZTE,Incorporated [10946.525335] usb 1-1.3: SerialNumber: MF8610ZTED000000 [10946.529662] usb-storage 1-1.3:1.0: USB Mass Storage device detected [10946.532702] scsi host19: usb-storage 1-1.3:1.0 [10947.538579] scsi 19:0:0:0: CD-ROM            ZTE      USB SCSI CD-ROM  2.31 PQ: 0 ANSI: 2 [10952.740595] usb 1-1.3: USB disconnect, device number 21 [10953.087891] usb 1-1.3: new high-speed USB device number 22 using msm_hsusb_host [10953.232955] usb 1-1.3: New USB device found, idVendor=19d2, idProduct=1405 [10953.232969] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [10953.232977] usb 1-1.3: Product: ZTE Mobile Broadband [10953.232984] usb 1-1.3: Manufacturer: ZTE,Incorporated [10953.232991] usb 1-1.3: SerialNumber: MF8610ZTED000000 [10953.260856] cdc_ether 1-1.3:1.0 usb0: register 'cdc_ether' at usb-msm_hsusb_host-1.3, CDC Ethernet Device, 36:4b:50:b7:ef:da [10953.262322] usb-storage 1-1.3:1.2: USB Mass Storage device detected [10953.262652] scsi host20: usb-storage 1-1.3:1.2 [10954.261139] scsi 20:0:0:0: CD-ROM            ZTE      USB SCSI CD-ROM  2.31 PQ: 0 ANSI: 2 

dmesg with MTP disabled:

[10664.987934] usb 1-1.3: new high-speed USB device number 19 using msm_hsusb_host [10665.105272] usb 1-1.3: New USB device found, idVendor=19d2, idProduct=1225 [10665.105291] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [10665.105301] usb 1-1.3: Product: ZTE Mobile Broadband [10665.105310] usb 1-1.3: Manufacturer: ZTE,Incorporated [10665.105320] usb 1-1.3: SerialNumber: MF8610ZTED000000 [10665.110339] usb-storage 1-1.3:1.0: USB Mass Storage device detected [10665.111320] scsi host17: usb-storage 1-1.3:1.0 [10666.110748] scsi 17:0:0:0: CD-ROM            ZTE      USB SCSI CD-ROM  2.31 PQ: 0 ANSI: 2 [10671.223090] usb 1-1.3: USB disconnect, device number 19 [10671.407859] msm_otg 78db000.usb: OTG runtime idle [10671.407887] msm_otg 78db000.usb: OTG runtime suspend 

ifconfig:

TB-8504F:/ # ifconfig                                                                                                                   wlan0     Link encap:Ethernet  HWaddr 40:a1:08:36:5b:0d           inet addr:192.168.1.133  Bcast:192.168.1.255  Mask:255.255.255.0            inet6 addr: 2605:a601:ab2b:9900:b19e:4f2e:5d28:5fa9/64 Scope: Global           inet6 addr: fe80::42a1:8ff:fe36:5b0d/64 Scope: Link           inet6 addr: 2605:a601:ab2b:9900:42a1:8ff:fe36:5b0d/64 Scope: Global           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1           RX packets:27906 errors:0 dropped:4 overruns:0 frame:0            TX packets:17795 errors:0 dropped:0 overruns:0 carrier:0            collisions:0 txqueuelen:1000            RX bytes:14342222 TX bytes:8697917   dummy0    Link encap:Ethernet  HWaddr c6:b9:c8:82:8f:7e           inet6 addr: fe80::c4b9:c8ff:fe82:8f7e/64 Scope: Link           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1           RX packets:0 errors:0 dropped:0 overruns:0 frame:0            TX packets:3 errors:0 dropped:0 overruns:0 carrier:0            collisions:0 txqueuelen:0            RX bytes:0 TX bytes:210   p2p0      Link encap:Ethernet  HWaddr 42:a1:08:36:5b:0d           UP BROADCAST MULTICAST  MTU:1500  Metric:1           RX packets:0 errors:0 dropped:0 overruns:0 frame:0            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0            collisions:0 txqueuelen:1000            RX bytes:0 TX bytes:0   lo        Link encap:Local Loopback             inet addr:127.0.0.1  Mask:255.0.0.0            inet6 addr: ::1/128 Scope: Host           UP LOOPBACK RUNNING  MTU:65536  Metric:1           RX packets:0 errors:0 dropped:0 overruns:0 frame:0            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0            collisions:0 txqueuelen:0            RX bytes:0 TX bytes:0  

ip l:

255|TB-8504F:/ # ip l 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default      link/ether c6:b9:c8:82:8f:7e brd ff:ff:ff:ff:ff:ff 3: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default      link/sit 0.0.0.0 brd 0.0.0.0 20: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000     link/ether 40:a1:08:36:5b:0d brd ff:ff:ff:ff:ff:ff 21: p2p0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000     link/ether 42:a1:08:36:5b:0d brd ff:ff:ff:ff:ff:ff 31: usb0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000     link/ether 36:4b:50:b7:ef:da brd ff:ff:ff:ff:ff:ff 

The device does show up as usb0 with the MAC address that was listed in dmesg.

              
       
       

回答列表

3
 
vote
vote
最佳答案
 

有很长的以太网相关问题列表,但没有全面的答案涵盖了所有方面。我概括了你的问题,以便分享我的知识。

这是您需要做的事情,以便在Android上进行以太网:

  • 确保OTG支持可用
  • 内核必须使用以太网(和USB以太网)支持
  • 处理USB模式开关和内核模块加载(如果适用)
  • 使Android框架进行网络配置或手动进行

注意: 下面描述的所有内容都需要 rooted设备,或者至少有一个解锁引导加载程序。
您应该熟悉CommandLine界面。


OTG支持

您的设备必须能够在USB主机模式下运行。 EthernetService 是仅当设备支持usb主机( android.hardware.usb.host )或以太网( android.hardware.ethernet )。如果Android的USB电源不足以连接设备,您可能还需要使用Powered USB集线器。相关问题:

  • 有没有明确的方式知道我的手机是否支持USB-OTG?

内核配置

为了使用以太网通过USB (适配器或调制解调器类似的设备)内核必须用 CONFIG_USB_USBNET < / code> 和其他配置如 USB_NET_CDCETHER USB_NET_HUAWEI_CDC_NCM USB_NET_CDC_MBIM 等,具体取决于连接设备的类型和协议会谈。相关问题:

  • 安装了内核模块?
  • 在不闪烁的新内核
  • 的情况下为内核添加驱动程序
  • 加载一个未签名的内核模块到签名enforcing kernel

USB模式开关和加载内核模块

许多USB网络设备是多模式或触发器设备。它们显示为USB大容量存储设备(也称为 zerocd 模式)切换到以太网/ PPP模式。 usb_modeswitch 是一个常用于此目的的Linux工具。查看一些细节这里的工作。您需要为您的设备构建此工具,或者可以下载这个二进制 aarch64 < /代码>。获取这里

为了在设备连接到Android时自动切换模式,我们需要通过 hotplug helper 或用户栏守护程序(如 udev 在linux和 ueventd 上的Android)。另外,内核模块也可以自动加载/卸载。我是定义一个 android.hardware.usb.host0 service 在此实现这一点,您可以手动执行此操作也。

注意:有一个Android应用程序 ppp窗口小部件(由USB_ModesWitch的开发人员,我没有自动处理模式切换并需要"无内核驱动程序模块," 驱动程序"实现基于Android USB主机API" 。 您可能对此感兴趣。

  android.hardware.usb.host1  

*如果hotpl g您需要定义自定义selinux策略,让内核进行更改(请参阅此答案详细信息)。

  android.hardware.usb.host2  

网络配置

Android框架具有以太网接口的硬编码名称(默认是 android.hardware.usb.host3 android.hardware.usb.host4 ,......)。每当出现以太网接口时,它名称匹配具有硬编码值。之后重命名界面不起作用,因为只有内核提供接口名称是跟踪。

因此,您需要通过修改两者之一(如果需要)进行内核和AOP之间的此命名约定。可以使用 android.hardware.usb.host5 工具来查看esernel提供的名称(如在您的情况下,它是 android.hardware.usb.host6 )。使用 android.hardware.usb.host7 或de-compile android.hardware.usb.host8 使用 apktool 查看AOSP值。

  android.hardware.usb.host9  

一旦出现了以太网接口,Android会自动配置它,<代码> ABCDefghijklmnabCdefghijklmn20 验证连接和 android.hardware.ethernet1 关闭wifi和移动数据(如果它是开启的)。涉及配置的其他服务和组件包括<代码> android.hardware.ethernet2 ,<代码> android.hardware.ethernet3 ,<代码> android.hardware.ethernet4 ,<代码> android.hardware.ethernet5 ,<代码> android.hardware.ethernet6 android.hardware.ethernet7 android.hardware.ethernet8

ethernetservice 添加在Android 5中。在该AOSP被修补以进行以太网工作之前(例如,请参阅这个和这个)。仍然库存android为以太网提供GUI设置,但有些自定义ROM开发人员和OEM DO(例如,请参阅 )。 android.hardware.ethernet9 类用于设置并保存手动IP配置(到 CONFIG_USB_USBNET0 )隐藏。默认是要使用硬编码配置(请参阅" ip配置"下使用 CONFIG_USB_USBNET1 )或 DHCP提供配置< / a>。

手动配置

您可能希望执行手动网络配置。 如果:

  • Android框架不配置以太网接口(在旧设备上或由于接口名称不一致)。
  • 要设置静态IP地址或不同的DNS服务器。
  • 您希望使用以太网以及WiFi或移动数据,或者希望在其中任何一个中共享互联网。

但在这种情况下,Android的Java网络堆栈保持下降,因此某些根据Android API的应用程序可能不会正常行为。 有关相关详细信息,请参阅通过adb shell连接到wifi 。

  CONFIG_USB_USBNET2  
  CONFIG_USB_USBNET3  

不要忘记在 CONFIG_USB_USBNET4 文件和shell脚本上设置适当的权限。 一旦设置,以太网就在连接USB适配器时立即工作。

 

There is a long list of Ethernet related questions but none has a comprehensive answer covering all aspects. I'm generalizing your question in order to share my knowledge on this.

This is what you need to do in order to make Ethernet work on Android:

  • Make sure OTG support is available
  • Kernel must be built with Ethernet (and USB Ethernet) support
  • Handle USB mode switch and kernel module loading (if applicable)
  • Make Android framework do network configuration or do it manually

Note: Everything described below requires a rooted device, or at least the one with unlocked bootloader.
You should be familiar with commandline interface.


OTG SUPPORT

Your device must be able to operate in USB host mode.EthernetService is started only if device supports feature USB host (android.hardware.usb.host) or Ethernet (android.hardware.ethernet). You may also need to use a powered USB hub if Android's USB power supply is not enough for connected device. Related question:

  • Is there a definite way to know if my phone supports USB-OTG or not?

KERNEL CONFIGURATION

In order to use Ethernet over USB (adapters or modem-like devices) kernel must be built with CONFIG_USB_USBNET and other configurations like USB_NET_CDCETHER, USB_NET_HUAWEI_CDC_NCM, USB_NET_CDC_MBIM etc. depending on the type of connected device and the protocol it talks. Related questions:

  • Where kernel modules are installed?
  • Add a driver to kernel without flashing a new kernel
  • Load an unsigned Kernel Module to signature enforcing Kernel

USB MODE SWITCH AND LOADING KERNEL MODULE

Many USB network devices are multi-mode or flip flop devices. They appear as USB Mass Storage device (also called ZeroCD mode) when inserted and need to be switched to Ethernet/PPP mode. USB_ModeSwitch is a Linux tool commonly used for this purpose. See some details here how it works. You need to build this tool for your device, or may download this binary for aarch64. Get device database from here.

In order to automatically switch mode whenever the device is connected to Android, we need to listen to kernel USB uevents, either through hotplug helper or a userspace daemon (like udev on Linux and ueventd on Android). Additionally the kernel module can also be loaded/unloaded automatically. I'm defining an init service here to achieve this, you can do it manually too.

Note: There is an Android app PPP Widget (by the developer of USB_ModeSwitch, I have no affiliation) which handles mode switching automatically and needs "no kernel driver modules, the 'driver' implementation is based on the Android USB host API". You might be interested in that too.

# /system/etc/init/custom.rc  # kernel hotplug or uevent daemon service service cust.udevd /system/sbin/busybox uevent /system/sbin/udev.sh     seclabel u:r:magisk:s0     disabled     writepid /dev/cpuset/system-background/tasks  # set kernel hotplug helper or start uevent daemon on boot on property:sys.boot_completed=1     #write /proc/sys/kernel/hotplug /system/sbin/udev.sh     start cust.udevd 

* In case of hotplug you need to define custom SELinux policies to let kernel make changes (see this answer for details).

#!/system/bin/sh  # /system/sbin/udev.sh script is executed from kernel hotplug or uevent daemon  # set PATH where you placed binaries export PATH=/system/bin  # save log exec >>/dev/udev.log 2>&1  # don't execute multiple instances exec 200<>/dev/udev.lock flock 200  VID="12d1"          # USB vendor ID of a Huawei devcie PID_UMS="1f01"      # product ID in ZeroCD mode PID_ETH="14db"      # product ID in Ethernet mode MODULE="cdc_ether"  # kernel module for USB Ethernet IFACE="usb0"        # Ethernet interface name  matches() {     [ -e "/sys/$DEVPATH/$1" ] || return 1     [ "$(cat "/sys/$DEVPATH/$1")" = "$2" ] || return 1     return 0 }  # check if a new USB device is added or removed if [ "$SUBSYSTEM" = "usb" ] then     # check if a USB device is added, then match VID and PID for mode switching     # also device must belong to UMS class: https://www.usb.org/defined-class-codes#anchor_BaseClass08h     if [ "$ACTION" = "add" ] && echo "$PRODUCT" | grep -q "$VID/$PID_UMS/" &&         matches bInterfaceClass 08 && matches bInterfaceNumber 00     then         echo "Switching USB mode..."          # USB mode switching of flip flop devices (USB modems, routers etc.)         # usb_modeswitch_dispatcher needs /system/sbin/usb_modeswitch binary and configuration files in /etc         # so you need to modify the hard-coded paths in source code as per your requirement         usb_modeswitch_dispatcher --switch-mode "$(basename "$DEVPATH")"     fi      # match VID and PID for module loading     # modprobe should be built with the hard-coded path to where you place modules e.g. /system/lib     if echo "$PRODUCT" | grep -q "$VID/$PID_ETH/"     then         if [ "$ACTION" = "add" ] && ! grep -q "^$MODULE " /proc/modules         then             echo "Loading $MODULE module..."             modprobe "$MODULE"          elif [ "$ACTION" = "remove" ] && grep -q "^$MODULE " /proc/modules         then             echo "Removing $MODULE module..."             modprobe -r "$MODULE"         fi     fi fi  # on network interface event if [ "$SUBSYSTEM" = "net" ] && [ "$INTERFACE" = "$IFACE" ] then     if [ "$ACTION" = "add" ]     then         echo "Starting cust.eth_config service..."         #start cust.eth_config    # uncomment if you want to do manual network configuration     fi      if [ "$ACTION" = "remove" ]     then         echo "Stopping cust.eth_config service..."         #stop cust.eth_config    # uncomment if you want to do manual network configuration     fi fi 

NETWORK CONFIGURATION

Android framework has a hard-coded name for Ethernet interface (default is eth0, eth1, ...). Whenever an Ethernet interface appears, its name is matched with the hard-coded value. Renaming interface afterwards doesn't work because only kernel provided interface name is tracked.

So you need to make this naming convention consistent between kernel and AOSP by modifying one of the both (if needed). Kernel provided name can be seen using ip tool (as in your case it's usb0). Use dumpsys or de-compile /system/framework/framework-res.apk using apktool to see the AOSP value.

~$ dumpsys ethernet ...   Ethernet interface name filter: eth\d ... 

As soon as an Ethernet interface appears, Android configures it automatically, NetworkMonitor validates the connectivity and ConnectivityService turns off WiFi and Mobile Data (if it's ON). Other services and components involved in configuration include UsbHostManager, EthernetTracker, EthernetNetworkFactory, IpClient.eth0, DhcpClient, DnsManager and Netd.

EthernetService was added in Android 5. Before that AOSP was patched to make Ethernet work (e.g. see this and this). Still stock Android provides no GUI settings for Ethernet, but some custom ROM developers and OEMs do (e.g. see this). EthernetManager class which is used to set and save manual IP configuration (to /data/misc/ethernet/ipconfig.txt) is hidden. Default is to use a hard-coded configuration (see using dumpsys ethernet under "IP Configurations:") or DHCP provided configuration.

MANUAL CONFIGURATION

You might want to do manual network configuration e.g. if:

  • Android framework doesn't configure the Ethernet interface (on older devices or due to interface name inconsistency).
  • You want to set static IP address or different DNS server.
  • You want to use Ethernet along with WiFi or Mobile Data, or want to share internet among any of these.

But in this case Android's Java network stack remains down, so some apps depending on Android APIs may not behave normally. For related details see Connecting to WiFi via ADB Shell.

# /system/etc/init/custom.rc  # Ethernet IP configuration service service cust.eth_config /system/sbin/eth_config.sh     seclabel u:r:magisk:s0     disabled     writepid /dev/cpuset/system-background/tasks  # clear routing and DNS on property:init.svc.cust.eth_config=stopped     exec u:r:magisk:s0 -- /system/sbin/eth_config.sh stop 
#!/system/bin/sh  # /system/sbin/eth_config.sh script is executed from eth_config init service  # set PATH where you placed binaries export PATH=/system/bin  IFACE=usb0                    # Ethernet interface name DIR=/data/local/tmp/ethernet  # temporary directory mkdir -p $DIR  # save log exec >$DIR/eth_config.log 2>&1  if [ "$1" = stop ] then     echo "Clearing configuration..."     ip ru del lookup main     ip r f table main     ndc resolver setnetdns 0 '' 0.0.0.0     exit fi  # destroy set network if any ndc network default set 0  # turn WiFi and Mobile Data off svc wifi disable svc data disable  # set interfaces up ip link set dev lo up ip link set dev $IFACE up  # Android doesn't use main table by default ip rule add lookup main  # set IP, route and DNS manually here # or add any other IP/routing configuration # or run a minimal DHCP client as follows  # create 'udhcpc' script <<-'SCRIPT' cat >$DIR/udhcpc_default.script #!/system/bin/sh  case $1 in     bound|renew)         echo "Setting IP address, gateway route and DNS for $interface..."         ip address f dev $interface         ip route f table main         ip address add $ip/$mask dev $interface         ip route add default via $router dev $interface         ndc resolver setnetdns 0 '' $dns     ;;     *)         echo "Ignoring $1"     ;; esac SCRIPT  # start DHCP client to obtain IP from server chmod 0755 $DIR/udhcpc_default.script exec busybox udhcpc -v -f -i $IFACE -s $DIR/udhcpc_default.script 

Do not forget to set proper permissions on .rc file and shell scripts. Once setup, Ethernet works as soon as you connect USB adapter.

 
 
 
 

相关问题

2  如何在OTG上对Android进行以太网工作?  ( How to make ethernet work on android over otg ) 
我正在尝试在OTG电缆上使用连接到Android 7设备的LTE调制解调器。内核识别设备并使用 cdc_ether 注册它,但我无法使用设备的连接。这是因为它随后安装为USB存储? 设备在Android UI /状态栏中显示为设备。 如果我禁用MTP支持,那么设备不会寄存 cdc_ether 。 dmesg : ...

-1  如何将摩托罗拉Xoom 2 ME(MZ607)连接到PC的FastBoot模式?  ( How to connect a motorola xoom 2 me mz607 on fastboot mode to a pc ) 
我正在尝试将FastBoot模式的摩托罗拉Xoom 2 Me(MZ607)连接到我的笔记本电脑运行Windows 10,如下所述: https://goo.gl/ln57px 当系统加载时,Windows识别设备。不过,不在Fastboot上。安装和更新摩托罗拉USB驱动程序和Android SDK。 是正常...

3  Aoson M19 - 需要设备驱动程序  ( Aoson m19 need device drivers ) 
我自己和其他一些人手头有额外的Aoson M19 Android平板电脑,但似乎无法找到任何USB设备驱动程序。我认为这是因为它不是一个过于流行的平板电脑。 有谁知道可以找到一些驱动程序的位置吗?也许有人写过自己的? ...

1  如何将SuperPad II P041连接到PC  ( How to connect superpad ii p041 to pc ) 
我是一个superpad II P041,我想将它连接到我的电脑。我想使用logcat来检查我的应用程序抛出的异常。 问题是,当我将其与USB电缆连接时,PC无法识别平板电脑。我已经启用了调试USB。 我可以试图让PC与平板电脑通信吗?也许我需要司机? 谢谢你的帮助。 ...

0  使用WiFi加密狗监控网络  ( Using a wifi dongle to monitor network ) 
我有一个带内置WiFi的Android智能盒,我想向盒子添加一个加密狗,以便我可以监控网络。我找到了类似的问题,有点模糊答案(至少对我); Android作为WiFi桥与AP 我此刻我有3个wifi congles。设备可以检测其中2(使用DMESG从shell运行,也是获取连接的USB设备的VendorID和...

-2  制造商是否为其新的Android Runned设备编写驱动程序?  ( Do manufacturers write the drivers for their new android runned devices ) 
您注意三星Galaxy S4与MetroPCS Z500不同。 制造商根据调整的硬件更新驱动程序。 for,i.e.,不同的支持驱动程序。这个问题并不关心政策,但软件Android在具有不同硬件的不同运行平台上运行。 例如,必须映射额外的硬件,以便访问,因此必须写入新的Linix驱动程序? ...

1  尽管安装了LG Universal Mobile Drivers,但仍未检测到LG Nexus 5  ( Lg nexus 5 is not detected despite having installed lg universal mobile drivers ) 
我使用Windows 8,adb似乎无法找到我的LG Nexus 5(D821),尽管已经安装了LG Universal Mobile驱动程序(LgunitedMobileDriver_S498MA22_WHQL_ML_VER_2.2)。 adb reboot bootloader 无法找到设备。 我已在USB调试...

1  OEM USB Drivers Lenovo [已关闭]  ( Oem usb drivers lenovo ) 
关闭。这个问题是 off-topic 。它目前不接受答案。 想要改进这个问题?更新这个问题,所以它是关于android爱好者堆栈交换的主题。 关闭 ...

5  如何在Windows / Ubuntu上获取adb以正确识别Alcatel One Touch 995设备?  ( How can i get adb to properly recognize an alcatel one touch 995 device on windo ) 
问题 我正在尝试将自定义应用程序部署到Alcatel One Touch 995运行Android 2.3.6。我使用Eclipse来编译源代码并将其推到手机上。 Eclipse中的Android设备选择器启动并列出设备,但它无法识别制作者或模型。设备显示为问号为序列号(见屏幕截图)。 我能够将应用程序安装到三...

1  索尼xperia u与我的Windows XP笔记本电脑  ( Sony xperia u with my windows xp laptop ) 
我有Windows XP,每次我连接我的xperia u时,电脑都认为它是一个相机。我认为这是一个司机问题,所以我在索尼网站上找到了司机,但我不确定如何安装它们吗? 我安装了驱动程序,但我的电脑仍然认为这是一台相机。任何帮助? ...




© 2022 it.wenda123.org All Rights Reserved. 问答之家 版权所有