How do I Post to the Game Q&A Forum?

Welcome to the FTC Game Q&A Forum! If this is your first time here, please refer to the Instructions for Forum Use section before posting.

Thank you!

Posts created to sell a product or service are not permitted and will be deleted!

Results 1 to 3 of 3

Thread: Can't download TeamCode to one of our HTC phones

  1. #1
    Junior Member
    Join Date
    Sep 2011
    Posts
    11

    Can't download TeamCode to one of our HTC phones

    11/07 21:14:36: Launching TeamCode
    $ adb push C:\Users\Mark\GitHub\ftc_app\TeamCode\build\output s\apk\TeamCode-debug.apk /data/local/tmp/com.qualcomm.ftcrobotcontroller
    $ adb shell pm install -r "/data/local/tmp/com.qualcomm.ftcrobotcontroller"
    pkg: /data/local/tmp/com.qualcomm.ftcrobotcontroller
    Success


    $ adb shell am start -n "com.qualcomm.ftcrobotcontroller/org.firstinspires.ftc.robotcontroller.internal.Ftc RobotControllerActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
    Connected to process 5319 on device zte-n9130-3a2056d
    D/ActivityThread: handleBindApplication:com.qualcomm.ftcrobotcontrol ler
    D/ActivityThread: setTargetHeapUtilization:0.75
    D/ActivityThread: setTargetHeapMinFree:2097152
    I/InstantRun: Instant Run Runtime started. Android package is com.qualcomm.ftcrobotcontroller, real application class is org.firstinspires.ftc.robotcore.internal.RobotAppl ication.
    E/InstantRun: Could not find slices in APK; aborting.
    W/InstantRun: No instant run dex files added to classpath
    V/RCActivity: onCreate()
    V/WebViewChromiumFactoryProvider: Binding Chromium to main looper Looper (main, tid 1) {4188f648}
    I/LibraryLoader: Expected native library version number "",actual native library version number ""
    I/chromium: [INFO:library_loader_hooks.cc(116)] Chromium logging enabled: level = 0, default verbosity = 0
    I/BrowserStartupController: Initializing chromium process, renderers=0
    D/BluetoothAdapter: 1099880560: getState() : mService = null. Returning STATE_OFF
    I/Adreno-EGL: <qeglDrvAPI_eglInitialize:410>: EGL 1.4 QUALCOMM build: ()
    OpenGL ES Shader Compiler Version: E031.24.02.07
    Build Date: 10/29/14 Wed
    Local Branch:
    Remote Branch:
    Local Patches:
    Reconstruct Branch:
    W/chromium: [WARNINGroxy_service.cc(890)] PAC support disabled because there is no system implementation
    W/dalvikvm: Unable to resolve superclass of Lcom/vuforia/ar/pl/Camera2_Preview$1; (90)
    W/dalvikvm: Link of class 'Lcom/vuforia/ar/pl/Camera2_Preview$1;' failed
    D/dalvikvm: GC_FOR_ALLOC freed 6662K, 61% free 4360K/11104K, paused 36ms, total 36ms
    D/dalvikvm: GC_FOR_ALLOC freed 2007K, 61% free 4400K/11104K, paused 16ms, total 16ms
    D/dalvikvm: GC_FOR_ALLOC freed 1996K, 60% free 4451K/11104K, paused 16ms, total 16ms
    E/WifiManager: createWifiLock(), enter. lockType=3 tag= getNameForPid(5319)=com.qualcomm.ftcrobotcontrolle r
    V/RobotCore: saving logcat to /storage/emulated/0/com.qualcomm.ftcrobotcontroller.logcat
    D/dalvikvm: GC_FOR_ALLOC freed 839K, 61% free 4423K/11104K, paused 13ms, total 14ms
    I/dalvikvm-heap: Grow heap (frag case) to 6.898MB for 524304-byte allocation
    V/RobotCore: Network: inactive, disconnected
    V/RCActivity: onStart()
    V/RCActivity: onResume()
    V/RCActivity: onPause()
    V/RCActivity: onStop()
    D/AndroidRuntime: Shutting down VM
    W/dalvikvm: threadid=1: thread exiting with uncaught exception (group=0x415bdd58)
    E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.qualcomm.ftcrobotcontroller, PID: 5319
    java.lang.RuntimeException: Unable to stop activity {com.qualcomm.ftcrobotcontroller/org.firstinspires.ftc.robotcontroller.internal.Ftc RobotControllerActivity}: java.lang.NullPointerException
    at android.app.ActivityThread.handleSleeping(Activity Thread.java:3294)
    at android.app.ActivityThread.access$2900(ActivityThr ead.java:138)
    at android.app.ActivityThread$H.handleMessage(Activit yThread.java:1378)
    at android.os.Handler.dispatchMessage(Handler.java:10 2)
    at android.os.Looper.loop(Looper.java:136)
    at android.app.ActivityThread.main(ActivityThread.jav a:5095)
    at java.lang.reflect.Method.invokeNative(Native Method)
    at java.lang.reflect.Method.invoke(Method.java:515)
    at com.android.internal.os.ZygoteInit$MethodAndArgsCa ller.run(ZygoteInit.java:786)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit .java:602)
    at dalvik.system.NativeStart.main(Native Method)
    Caused by: java.lang.NullPointerException
    at org.firstinspires.ftc.robotcontroller.internal.Ftc RobotControllerActivity.onStop(FtcRobotControllerA ctivity.java:319)
    at android.app.Instrumentation.callActivityOnStop(Ins trumentation.java:1212)
    at android.app.Activity.performStop(Activity.java:537 6)
    at android.app.ActivityThread.handleSleeping(Activity Thread.java:3291)
    at android.app.ActivityThread.access$2900(ActivityThr ead.java:138)*
    at android.app.ActivityThread$H.handleMessage(Activit yThread.java:1378)*
    at android.os.Handler.dispatchMessage(Handler.java:10 2)*
    at android.os.Looper.loop(Looper.java:136)*
    at android.app.ActivityThread.main(ActivityThread.jav a:5095)*
    at java.lang.reflect.Method.invokeNative(Native Method)*
    at java.lang.reflect.Method.invoke(Method.java:515)*
    at com.android.internal.os.ZygoteInit$MethodAndArgsCa ller.run(ZygoteInit.java:786)*
    at com.android.internal.os.ZygoteInit.main(ZygoteInit .java:602)*
    at dalvik.system.NativeStart.main(Native Method)*
    I/Process: Sending signal. PID: 5319 SIG: 9
    Application terminated.

  2. #2
    Junior Member
    Join Date
    Sep 2011
    Posts
    11
    Problem is not fixed. It was definitely a phone settings problem.

    It looks like one of the students had changed the 'Connect to PC' configuration to 'Charge Only'
    Adb does not appear to be able to properly transfer the application to the phone in this mode. I set it to MTP and it now works.
    Note: I also changed some other settings to match our other phones; so, this might have not been the only issue.
    This does seem to have been the primary issue as changing 'Connect to PC' back to 'Charge Only' causes the problem to come back.

  3. #3
    Senior Member
    Join Date
    Jun 2015
    Location
    Massachusetts
    Posts
    380
    Is there a reason you aren't just downloading from Android Studio?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •