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

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
  • 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

Reply
  • 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

Children
No data