android-debug | 易学教程

Google Maps works fine on Android but I still get an error “Could not find class 'maps.i.k', referenced from method maps.z.ag.a”

阅读更多关于 Google Maps works fine on Android but I still get an error “Could not find class 'maps.i.k', referenced from method maps.z.ag.a”

问题 I got Google Maps Android API v2 to work perfectly on my Android Application by downloading the library, adding it to workspace, then referencing it as a library. But I still get this error as soon as the activity containing the Map Fragment starts Could not find class 'maps.i.k', referenced from method maps.z.ag.a By the way I'm using support map fragment This error does not seem to affect me in anyway nor crash the application nor anything, should I bother fixing it ? Added the manifest P.S

Android Logcat is empty when debug with device in android studio

阅读更多关于 Android Logcat is empty when debug with device in android studio

问题 When I try to debug using android device in android studio Logcat shows nothing. But when I use emulator LogCat shows all the messages. How should view the Logcat messages when debugging on actual device? Thank You ! 回答1: In Android studio 0.8.0 you should enable ADB integration through Tools -> Android, before run your app. Then the log cat will work correctly. Notice that if you make ADB integration disabled while your app is running and again make it enable, then the log cat dosen't show

'Source code does not match the bytecode' when debugging on a device

阅读更多关于 'Source code does not match the bytecode' when debugging on a device

问题 I have an app which I am compiling against API level 21: and then debug it on a real device with API level 23: The problem is when I try debugging through the Android OS's own classes, I get 'Source code does not match the bytecode'. Why is this happening? The test device the app is running on is API level 23, and the source file being debugged is level 23 as well. I am really confused. Can anyone explain why I am seeing this message and how I can fix it? 回答1: There's an open issue for this

How to use ADB Shell when Multiple Devices are connected? Fails with “error: more than one device and emulator”

阅读更多关于 How to use ADB Shell when Multiple Devices are connected? Fails with “error: more than one device and emulator”

$ adb --help ... -s SERIAL use device with given serial (overrides $ANDROID_SERIAL) ... $ adb devices List of devices attached emulator-5554 device 7f1c864e device ... $ adb shell -s 7f1c864e error: more than one device and emulator ? janot Use the -s option BEFORE the command to specify the device, for example: adb -s 7f1c864e shell See also http://developer.android.com/tools/help/adb.html#directingcommands Sazzad Hissain Khan adb -d shell (or adb -e shell if you're connecting to an emulator). This command will help you in most of the cases, if you are too lazy to type the full ID. From http:

Android app crashes when launched in debug mode

阅读更多关于 Android app crashes when launched in debug mode

When I run in debug mode the app crashes, but when I just run it normally it works. I think the problem happens when the debugger is attached. Log: A/art: art/runtime/jdwp/jdwp_event.cc:661] Check failed: Thread::Current() != GetDebugThread() (Thread::Current()=0x7f44a18400, GetDebugThread()=0x7f44a18400) Expected event thread A/art: art/runtime/runtime.cc:422] Runtime aborting... A/art: art/runtime/runtime.cc:422] Aborting thread: A/art: art/runtime/runtime.cc:422] "JDWP" prio=5 tid=4 WaitingForDebuggerSend A/art: art/runtime/runtime.cc:422] | group="" sCount=0 dsCount=0 obj=0x12c60280 self

Android app crashes when launched in debug mode

阅读更多关于 Android app crashes when launched in debug mode

问题 When I run in debug mode the app crashes, but when I just run it normally it works. I think the problem happens when the debugger is attached. Log: A/art: art/runtime/jdwp/jdwp_event.cc:661] Check failed: Thread::Current() != GetDebugThread() (Thread::Current()=0x7f44a18400, GetDebugThread()=0x7f44a18400) Expected event thread A/art: art/runtime/runtime.cc:422] Runtime aborting... A/art: art/runtime/runtime.cc:422] Aborting thread: A/art: art/runtime/runtime.cc:422] \"JDWP\" prio=5 tid=4

How to use ADB Shell when Multiple Devices are connected? Fails with “error: more than one device and emulator”

阅读更多关于 How to use ADB Shell when Multiple Devices are connected? Fails with “error: more than one device and emulator”

问题 $ adb --help ... -s SERIAL use device with given serial (overrides $ANDROID_SERIAL) ... $ adb devices List of devices attached emulator-5554 device 7f1c864e device ... $ adb shell -s 7f1c864e error: more than one device and emulator ? 回答1: Use the -s option BEFORE the command to specify the device, for example: adb -s 7f1c864e shell See also http://developer.android.com/tools/help/adb.html#directingcommands 回答2: adb -d shell (or adb -e shell if you're connecting to an emulator). This command