• State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 120 subscribers
  • Views 7332 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
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

ADB connection unstable, making Streamline/GA almost unusable

AndyYan

In both Streamline and Graphics Analyzer, when connecting to an Android device, the target device would briefly appear in the devices list, but then disappear, showing "No targets have been detected" (Streamline) / "Unable to validate ADB" (GA), and reappear after a few seconds - the cycle repeats, as if I have a loose connection.

In very rare occasions, the app was able to get through the "flashing" phase and show me the app to capture, and if I start capture then, the app works just fine afterwards, with constant output and no disconnections. However, it's nowhere near reliable.

I've tried different USB ports, cables and even target devices, but all of them exhibit the same behaviour. Also note that my ADB setup is fine all this time, as I can "adb shell" to my device and it stays connected.

Product: DS 2021.0 Gold Evaluation, with Streamline 7.6 / Graphics Analyzer 5.8

OS: Windows 10 64-bit

Parents
  • 0 Arm Employee Badge in reply to AndyYan

    Hi Andy

    We typically test Streamline against r30 so it is surprising you are having this issue. Additionally, I have tested with r31 platform tools and cannot reproduce this issue. Are you sure there are no other users of adb running at the same time (for example Android Studio).

    Assuming there are not, can you please provide us with the log output from the following steps. These commands will allow us to report the output from each 'adb' command that Streamline issues, hopefully to identify the specific command that is failing:

    From windows command prompt:

    CD C:\Program Files\Arm\Development Studio 2021.0\bin\    (or whatever the install path is + bin)
SET DEVTEST_LOG_TO_SCREEN=true
streamline.exe -consolelog > %USERPROFILE%\streamline.log     (or some other writable location)


    Then please send us the streamline.log file.

    NB: The file may (if it is able to get that far) contain output from running adb which contains the names of packages that are installed on the device, so please review if their is anything you would not like to share first. Mostly you will find lots of "adb forward --list" / "adb devices" and similar.

Reply
  • 0 Arm Employee Badge in reply to AndyYan

    Hi Andy

    We typically test Streamline against r30 so it is surprising you are having this issue. Additionally, I have tested with r31 platform tools and cannot reproduce this issue. Are you sure there are no other users of adb running at the same time (for example Android Studio).

    Assuming there are not, can you please provide us with the log output from the following steps. These commands will allow us to report the output from each 'adb' command that Streamline issues, hopefully to identify the specific command that is failing:

    From windows command prompt:

    CD C:\Program Files\Arm\Development Studio 2021.0\bin\    (or whatever the install path is + bin)
SET DEVTEST_LOG_TO_SCREEN=true
streamline.exe -consolelog > %USERPROFILE%\streamline.log     (or some other writable location)


    Then please send us the streamline.log file.

    NB: The file may (if it is able to get that far) contain output from running adb which contains the names of packages that are installed on the device, so please review if their is anything you would not like to share first. Mostly you will find lots of "adb forward --list" / "adb devices" and similar.

Children
  • 0 in reply to Ben Gainey

    Hi Ben,

    Log here (too large for forum attachment).

    While this log was captured...

    • The device was found and added to the devices list
    • The package list loads, but while doing so, both lists alternate a few times between empty and loading states
    • Towards the end of loading (~85%), the package list starts another loading procedure
    • The package list alternates between the two loading progress pies, until the latter finishes, and finally serves the result

    Is there a similar logging method for Graphics Analyzer? The symptoms are more pronounced there (e.g. app often stops responding).

    Side note: I just discovered ARM Mobile Studio which is free and comes with SL/GA as well (sharing the same problem). However, as MS Starter Edition doesn't come with support, I'll stick to using DS for debugging until the trial runs out.

    Thanks,
    Andy

  • 0 in reply to Ben Gainey

    Hi Ben, any discoveries from that log?

  • 0 Arm Employee Badge in reply to AndyYan

    Hi Andy, Thanks for the log. There's nothing particularly wrong in the log you sent, but it does look like it is doing eveything twice, which is unexpected. There were some changes in the package scanning and device enumeration in the very latest version of Streamline (version 7.7) which is available in Mobile Studio 2021.1 and will be released in the next version of Arm DS as well. Can you please give MS Starter Edition a quick try and see if you see the same results in the latest edition or not.

  • 0 in reply to Ben Gainey

    Hi Ben, same thing with MS. My DS trial license is expiring soon so I'll have to use MS to try out future advice from here on out.