Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Investigate use of the Android property API instead of calling getprop #1231

Closed
bradgrantham-lunarg opened this issue Aug 21, 2023 · 1 comment · Fixed by #1233
Closed

Investigate use of the Android property API instead of calling getprop #1231

bradgrantham-lunarg opened this issue Aug 21, 2023 · 1 comment · Fixed by #1233
Assignees
@panos-lunarg

Comments

@bradgrantham-lunarg
Copy link
Contributor

If a continuous system query is performed, e.g. by Perfetto, and the capture trigger property is used, the process list will contain those calls to getprop command.
@bradgrantham-lunarg bradgrantham-lunarg mentioned this issue Aug 24, 2023
Merged
@panos-lunarg
Copy link
Contributor

Done as part of #1233

@panos-lunarg panos-lunarg reopened this Aug 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@panos-lunarg panos-lunarg

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use system_properties.h api instead of getprop panos-lunarg/gfxreconstruct
2 participants
@bradgrantham-lunarg @panos-lunarg