• State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 138 subscribers
  • Views 7233 views
  • Users 0 members are here
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

Performance Adviser error: cannot find any frames

Dmitry Artamonov

Hi,

I'm facing this issue when trying to get html report from Streamline capture using Performance Adviser tool:

Problems were found preparing html report:

WARNING: Build name not provided. You can add this as a command line argument (use --build-name).

WARNING: Build timestamp not provided. You can add this as a command line argument (use --build-timestamp).

WARNING: Device name not provided. You can add this as a command line argument (use --device-name).

WARNING: Cannot find draw calls counter. Use LWI or GA interceptor when creating your capture to obtain draw calls data.

ERROR: Cannot find any frames. Please refer to the user guide for methods of providing frame data to Performance Advisor.

WARNING: CPU cycles data was not used. Cycles data is missing or unreliable. Use --force-cycles to force usage of this data.

My Host OS is macOS Catalina 10.15.7, Android 9, OpenGL ES 32-bit

Also my script is:  

python3 lwi_me.py -v --lwi-mode=capture --lwi-fps-threshold=20 --32bit --lwi-out-dir=$HOME/Documents/Projects/slowFrames

PA command:
pa captureName.apc

libLWI.so file integrated in Unity project

Thanks,
Dmitry
Parents
  • 0 Arm Employee Badge

    Try renaming libLWI.so to libMGD.so - I don't think the Unity library loader will look for libLWI.so. 

    Note on newer Unity builds, the library load hook in-app has been removed so you will need to use an Android 10 device with OpenGL ES layers (Performance Advisor doesn't currently support injecting the GLES layers at run-time, although Graphics Analyzer does).

Reply
  • 0 Arm Employee Badge

    Try renaming libLWI.so to libMGD.so - I don't think the Unity library loader will look for libLWI.so. 

    Note on newer Unity builds, the library load hook in-app has been removed so you will need to use an Android 10 device with OpenGL ES layers (Performance Advisor doesn't currently support injecting the GLES layers at run-time, although Graphics Analyzer does).

Children
  • 0 in reply to Peter Harris

    Hi Peter,

    Thanks for the feedback! Will check it.

    Best,

    Dmitry

  • 0 in reply to Peter Harris

    Hello,

    I have almost the same problem.

    When I added libLWI.so as libMGD.so into the Unity project then I finally see "Frame Rate", "Draw Calls/Frame" and other lines in the Streamline. 

    "python3 lwi_me.py --lwi-mode=capture --32bit" starts and waits for the Streamline.

    But after finishing of capturing when I try to 

    "pa $HOME/Documents/Streamline/Capture_15.apc -p=com.XXXX" I got the next errors:

    Problems were found preparing html report:

    WARNING: Build name not provided. You can add this as a command line argument (use --build-name).

    WARNING: Build timestamp not provided. You can add this as a command line argument (use --build-timestamp).

    WARNING: Device name not provided. You can add this as a command line argument (use --device-name).

    ERROR: Cannot find GPU cycles. Ensure your capture includes 'Mali Job Manager Cycles - GPU active' / Mali Job Manager Cycles - GPU cycles' / Mali GPU Cycles - GPU active' / Mali GPU Cycles - GPU cycles'.

    ERROR: Cannot find Fragment cycles. Ensure your capture includes 'Mali Job Manager Cycles - Fragment active' / Mali Job Manager Cycles - JS0 cycles' / Mali Job Manager Cycles - Fragment queue active' / Mali Job Manager Cycles - Fragment queue utilization' / Mali GPU Cycles - Fragment active' / Mali GPU Cycles - JS0 cycles' / Mali GPU Cycles - Fragment queue active' / Mali GPU Cycles - Fragment queue utilization'.

    ERROR: Cannot find Non-fragment cycles. Ensure your capture includes 'Mali Job Manager Cycles - Non-fragment active' / Mali Job Manager Cycles - JS1 cycles' / Mali Job Manager Cycles - Non-fragment queue active' / Mali Job Manager Cycles - Non-fragment queue utilization' / Mali GPU Cycles - Non-fragment active' / Mali GPU Cycles - JS1 cycles' / Mali GPU Cycles - Non-fragment queue active' / Mali GPU Cycles - Non-fragment queue utilization'.

    WARNING: No overdraw data. Ensure you select the correct counter configuration template in streamline for your GPU before recording.

    WARNING: User regions not provided. You can add this using annotation instrumentation in the application. Consult the user guide for more information.

    ERROR: Cannot determine GPU type. Make sure you are using a supported device and included the GPU counters in the capture by setting the relevant template.

     

    The same list of errors I got when there was no "libLWI.so" in the project and I didn't see "Frame Rate" and other "XXXX/Frame" lines in the Streamline.

    So what more magic can I apply to resolve this problem?

  • 0 Arm Employee Badge in reply to Vladimir_BL

    Hi! Could you please tell us which version of Arm Mobile Studio you are using?

    Thanks! 

  • 0 in reply to Pavel Rudko

    I'm using the latest 2021.3 version and I'm trying it with the next devices:

    ZTE Blade A5 2020 (Android 9)

    Xiaomi Redmi 7A (Android 10)

    Xiaomi Redmi S2 (Android 9)

    Samsung Galaxy A12 (Android 10)

    No Mali GPU is found when I launch lwi_me.py.

    And looks like it is the main problem.

    The Streamline doesn't show any Mali/GPU cycles as shown on your videos. 

  • +1 in reply to Vladimir_BL

    None of the devices above are have Mali GPU