android usb debugging not working

After connecting the Android device to the computer using a USB cable, you can run the Android Application on the device for debugging. My environment: Android 2.1 update1, HTC G7 Operating System The PC operating system is ubuntu9.10. IDE: eclipse3.5.1 (

Specify a debugging device for a Qt-based Android Application in Linux.Specify a debugging device for a Qt-based Android Application in Linux I recently installed Ubuntu Kylin with Chinese and foreign counterparts. Then I switched to the sogou input method, and the encoding felt much better than Microsoft's. Opening Q

Recently encountered a problem, no USB interface how to make Android device connected to the PC? Later colleagues told me that the original can use the network to connect it, so debugging up more convenient, fortunately there is a network port to provide connectivity. In fact, it is very simple, just add the following sentence to the System/build.prop file:servic

Android development can use Google's own simulator to debug, but the simulator is too slow to start, too time-consuming, but if we have an Android phone, we can directly debug on the phone, so that the speed is fast;The steps are as follows:(1) First set the phone to debug mode:Because I use the Meizu MX3 mobile phone, a start has not found its USB

1. connect to the USB data cable, Enable USB debugging, and use the Windows "run" command line method: (This method requires configuring the ADB environment variable, you can also directly go to the ADB tool directory and execute \ Android-SDK-Windows \ platform-tools \) Adb tcpip 5555 (Port Number) ADB connect 192.16

First step: View USB Device informationIn terminal input: System_profiler Spusbdatatype can view information for connected USB devicesFor example, my USB information is as follows (part of the content):View the vendor id:0x04e8 on my Android phone, which is a unique identifier for the phone associated with the computer

1. Set the android phone to USB debugging mode. Step: menu ---> Settings ---> application ---> development, select USB debugging] 2. Use USB to connect your phone and computer, and make sure the connection is successful. Step: Ru

Debug Android Java source code The back garden of the straw hat-Neo Previously written: This article mainly focuses on debugging the Java source code. It should be said that it is the source code after system_process. This is a powerful tool for debugging and modifying the frameworks layer, but why is it still analyzed after system_process? If there is any result

exit2.6 Test adb, open terminal, enter command, show "Android Debug Bridge version 1.0.39" For configuration success$ adb versionThe second step is to create and modify the Adb_usb.ini file, which is also divided into 2 small steps.1. Open terminal, enter command, view device information$ System_profiler Spusbdatatype1.2 get their corresponding device information, where the information in the vendor ID, need to be retained, etc under usesamsung_andro

wrong because the unity version and the Android SDK tools version is not, such as the lack of zipalign.exe,aapt.exe, such as hintsThe workaround is to copy the Zipalign.exe,aapt.exe to android-sdk-windows\tools\ directly from the \android-sdk-windows\build-tools\19.1.0\.Where zipalign.exe this file is only Build-tools 19.1. In more than 0 versionsAapt.exe This b

1. Set the Android phone to USB debugging mode. Step: menu ---> Settings ---> Application Program---> Development, select [USB debugging] 2. Connect the mobile phone and computer with USB, and ensure the success. Step: Run C:/ADB

The first step: viewing USB device information In terminal input: System_profiler Spusbdatatype can view information for connected USB devices For example, my USB information is as follows (part of the content): Android:Product id:0x2769Vendor id:0x22d9version:2.31Serial number:6e5d48a4Speed:up to 480 Mb/secManufacturer:androidLocation ID:0X1D110000/8Current Av

the above results that sudo does not work. Debugging on a real machine is simple: edit a configuration file, Set permissions, and restart the service: [luozhuang@luozhuangVM tools]$ sudo gedit /etc/udev/rules.d/70-android.rules[luozhuang@luozhuangVM tools]$ sudo chmod 777 /etc/udev/rules.d/70-android.rules[luozhuang@luozhuangVM tools]$ sudo service udev restartRedirecting to /bin/systemctl restart udev.service The content of the 70-android.rules fi

", "power_key", power_key) {pr_err ("% s: power_key script_get_item error. \ n ",__ func _); power_key = 0x4d;} if (SCIRPT_ITEM_VALUE_TYPE_INT! = Script_get_item ("ir_para", "ir_addr_code", ir_addr_code) {pr_err ("% s: ir_addr_code script_get_item error. \ n ",__ func _); ir_addr_code = 0xff00; // ---- the code is re-specified here. Therefore, the above IR_ADDR_CODE has been modified to take effect} 3.2.3 compile kernelRun #./build. sh-p sun7i_android to compile the kernel in the lichee direc

Debugging and remote display and control of the Headless Android Development Board, headlessandroid Recently, the msm8996 Development Board has been debugged. Because the motherboard and LCD sub-board have not yet come back, the first back core board is a Headless Android Device. The core board has independent power supply, as well as

[Excerpted from] http://zwkufo.blog.163.com/blog/static/2588251201126113638144/ In Linux, when debugging Android phones on a real machine, you often encounter insufficient permissions for device errors. In addition, ADB devices may be garbled and you are not authorized to perform any ADB operations. The following configuration method can solve this problem (the environment is UBUNTU ): 1. Enter terminal

H5 debugging way generally with chrome emulator is good, but encountered the app on the clumsy count. At this time also have to use remote debugging, remote debugging is to force, but at present there is no good article on the internet to explain, to properly configure it down or very difficult, today toss a half day, finally fix, share Configure requirements

Android 3G pppd debugging records. 1. Java SectionAndroid/development/data/etc/apns-conf_sdk.xml ---> system/etc/apns-conf.xmlNote the apns version,APN = "3 GNET"MCC = "460"MNC = "01"Proxy = ""Port = ""User = ""Server = ""Password = ""Type = "default, supl"/> Android/packages/providers/telephonyprovider/src/COM/Android

when it comes to mobile development, we often use Chrome's own simulator to simulate a variety of mobile devices. But simulation is simulation after all, when the development is complete, using the real machine to access the page problems when debugging?Here is a debugging method for Android1.Install the latest version of Chrome on both PC and Android phones2.Con

Step 1: lsusb check the USB ID Bus 002 device 004: ID 22b8 : 41db Motorola PCs Motorola Droid (USB Debug) Step 2: edit the configuration file Sudo Vim/etc/udev/rules. d/50-android.rulessubsystem = "USB", sysfs {idvendor }== "22b8", mode = "0666" sudo chmod 777/etc/udev/rules. d/50-android.rules Step 3: Enable ADB