This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Debug non-debuggable packages on Streamline

Based on this question, it seems that third-party apps are by default non-debuggable. It is mentioned, however, that the device needs to have a non-release version of android. I have purchased a Qualcomm development board that has a userdebug build on it. The only package that is debuggable is the telemetry service package from Qualcomm.

Are there any alternatives for other packages? How could I start a capture and get statistics for other programs like Geekbench and Spotify?

Thanks.

Parents
  • If I understand correctly the order of operations:

    1) Load gatord to the device and start it in system wide mode.

    2) Start the application via adb

    3) Start capture on Streamline

    Some questions:

    1) Would starting the application via the Android's GUI make any difference compared to adb shell?

    2) Is there any way to make Streamline automatically start the capture when the application starts running or does this step always has to be done manually?

    3) Are these complications basically the by-product of the application not being debuggable? Because it seems like that with a debuggable application all these steps are taken care of automatically by Streamline.

    Thanks.

Reply
  • If I understand correctly the order of operations:

    1) Load gatord to the device and start it in system wide mode.

    2) Start the application via adb

    3) Start capture on Streamline

    Some questions:

    1) Would starting the application via the Android's GUI make any difference compared to adb shell?

    2) Is there any way to make Streamline automatically start the capture when the application starts running or does this step always has to be done manually?

    3) Are these complications basically the by-product of the application not being debuggable? Because it seems like that with a debuggable application all these steps are taken care of automatically by Streamline.

    Thanks.

Children
  • 1) Would starting the application via the Android's GUI make any difference compared to adb shell?

    If you pick the right activity it shouldn't, as far as I know. 

    2) Is there any way to make Streamline automatically start the capture when the application starts running or does this step always has to be done manually?

    It's a system-wide capture, so in this mode it has no concept of a single "application". You'll need to start manually (but you can start the capture before the application starts).

    3) Are these complications basically the by-product of the application not being debuggable? Because it seems like that with a debuggable application all these steps are taken care of automatically by Streamline.

    The current method the Streamline GUI uses only works for debuggable applications. It's on our roadmap to add GUI support for  non-debuggable applications on Eng and UserDebug builds of Android, but it's not supported yet.

    Cheers, 
    Pete