Arm Community
Site
Search
User
Site
Search
User
Groups
Education Hub
Open Source Software and Platforms
Research Collaboration and Enablement
Forums
AI and ML forum
Architectures and Processors forum
Arm Development Platforms forum
Arm Development Studio forum
Arm Virtual Hardware forum
Automotive forum
Compilers and Libraries forum
Graphics, Gaming, and VR forum
High Performance Computing (HPC) forum
Infrastructure Solutions forum
Internet of Things (IoT) forum
Keil forum
Morello forum
Operating Systems forum
SoC Design and Simulation forum
SystemReady Forum
Blogs
AI and ML blog
Announcements
Architectures and Processors blog
Automotive blog
Graphics, Gaming, and VR blog
High Performance Computing (HPC) blog
Infrastructure Solutions blog
Internet of Things (IoT) blog
Operating Systems blog
SoC Design and Simulation blog
Tools, Software and IDEs blog
Support
Arm Support Services
Documentation
Downloads
Training
Arm Approved program
Arm Design Reviews
Community Help
More
Cancel
Support forums
Graphics, Gaming, and VR forum
Arm Mobile Studio 2022.4 Graphics Analyzer fails to capture non-debuggable applications
Jump...
Cancel
State
Accepted Answer
+1
person also asked this
people also asked this
Locked
Locked
Replies
6 replies
Subscribers
136 subscribers
Views
1584 views
Users
0 members are here
Options
Share
More actions
Cancel
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
Arm Mobile Studio 2022.4 Graphics Analyzer fails to capture non-debuggable applications
Arm Mobile Studio 2022.4 Graphics Analyzer fails to capture non-
over 1 year ago
Hi guys,
Arm Mobile Studio 2022.4 Graphics Analyzer fails to capture non-debuggable applications.
Top replies
Peter Harris
over 1 year ago
in reply to
Arm Mobile Studio 2022.4 Graphics Analyzer fails to capture non-
+3
verified
You cannot follow the capture over adb instructions. It doesn't work. You need to connect using the TCIP/IP tab - the second of the links above. Connect to localhost:5002 (or whatever other port you used...