[Andorid] Error connecting to debugger

[MikhailGorobets]

[Andorid] Error connecting to debugger

[Zorro666]

Thank you for the report. It might well be a device specific issue.
Are you able to test on a different Android device?
Can you check that this APK works on the device (this APK is known to be debugable on Android devices)

[MikhailGorobets]

@Zorro666
The APK file runs on the device, but I can't capture the frame
Unfortunately I don't have any other devices to check.

[MikhailGorobets]

@Zorro666
UPD:
I tried to capture a frame on Huawei Nova 5t, and I succeeded on this device.

[tjr-arm]

@MikhailGorobets

I tried to capture a frame on Huawei Nova 5t, and I succeeded on this device.

Could you clarify whether this was with your original APK or the test APK provided by Zorro666?
Separately, would you be able to share your original APK for testing?
Many thanks

[MikhailGorobets]

Could you clarify whether this was with your original APK or the test APK provided by Zorro666?
Separately, would you be able to share your original APK for testing?
Many thanks

The frame capture doesn't work in RenderDoc with either Zoro666's APK or my APK file on the OnePlus 10 Pro. On the Huawei Nova 5t, frame capture works with both APK files
My original APK:
https://drive.google.com/file/d/1cMSP3sil0bOFVnPFytpeO3OHkoJy5tAb

[tjr-arm]

Thank you for the info. I do not have a OnePlus on hand but have tried with an OPPO, which is their parent company - they share many quirks- but I have not been able to reproduce. It certainly looks device specific...

Could you attach Android logs around the time of a capture attempt on the OnePlus (adb logcat will suffice)?

This may yet be related to #3183, which is resolved in the latest nightly build. If you are able to rule out this possibility it would be helpful to our investigation https://renderdoc.org/builds#nightly

[zhanzhanfu]

I meet this problem too on K50

[baldurk]

Closing this due to lack of activity from the reporter and no further information to investigate.

If you are the reporter and this bug is still a problem for you, or you are someone finding this issue and you believe this bug is still a problem and you have more information to share, please do not comment here and instead please open a new issue. You can reference this issue if you wish, but opening a new issue prevents confusion of accidentally linking two unrelated bugs and means that each issue can be handled in a clean process.