Analysis on Android mobile assistant recognition models

Analysis on Android mobile assistant recognition models

 

Recently, in the PAD project, QA submitted a bug. When iTools is used to manage the PAD, the device Models displayed by iTools are different from those of the target model. In other pods, baidu and other mobile assistants have not encountered this problem. To solve this problem, first check whether the device description in prop. build under the system directory of the machine has an impact. It mainly includes:

Ro. product. model = model _ modle

Ro. product. brand = brand _ brand

Ro. product. name = Mobile Phone name_name

......

Ro. product. cpu. abi = armeabi-v7a

Ro. product. cpu. abi2 = armeabi

Ro. product. manufacturer = manufacturer _ manufacturer

However, if the device name is identified by another brand, you can confirm that this brand is not obtained through the prop. build File. In addition, during the test, it is found that if the network is disconnected, the device name is equivalent to the model name, so you can know that iTools will be based on an ID, find the corresponding device model in your online database.

View the usb VID and PID by using usblayzer, and. Therefore, we changed the original vid pid to the VID and pid of the power pad, because the identification of the power station is consistent with the model name when the network is disconnected and connected. Through the query we can know that VID = 18d1 is google, pid is 0007. So modify android4.4/device/softwinner/fiber-a31stm init. sun6i. usb. rc file:

On property: sys. usb. config = mtp

Write/sys/class/android_usb/android0/enable 0

Write/sys/class/android_usb/android0/idVendor 18d1

Write/sys/class/android_usb/android0/idProduct 0007

Write/sys/class/android_usb/android0/functions $ {sys. usb. config}

Write/sys/class/android_usb/android0/enable 1

Setprop sys. usb. state $ {sys. usb. config}

.......
All vids in this file must be modified to the same 18d1. The PID can be staggered, but it cannot conflict with the registered Device of google. As follows:

VID-> 18d1 Google Inc.

PID-> 0d02 Celkon A88

2d00 Android-powered device in accessory mode

2d01 Android-powered device in accessory mode withADB support

4e11 Nexus One

4e12 Nexus One (debug)

4e13 Nexus One (tether)

4e20 Nexus S (fastboot)

4e21 Nexus S

4e22 Nexus S (debug)

4e24 Nexus S (tether)

4e40 Nexus 7 (fastboot)

4e41 Nexus 7 (MTP)

4e42 Nexus 7 (debug)

4e43 Nexus 7 (PTP)

4ee1 Nexus 1 4/10

4ee2 Nexus 4 (debug)

4ee3 Nexus 4 (tether)

4ee4 Nexus 4 (debug + tether)

7102 Toshiba Thrive tablet

B004 Pandigital/B & N Novel 9 "tablet

D109 LG G2x MTP

D10a LG G2x MTP (debug)

After modification, the device name is the same as the model name.

Summary: when connecting to iTools, you will first use the USB vid PID to match the device name with your network database. If there is a network and the database has data, you will use the network data, if there is no network or network, but the database does not have the corresponding vid pid, there is a model consistent model.