Closed xiaofengzhang777 closed 4 months ago
I'd like to bring to your attention that when I executed the same sample on a Pixel 4 XL
device (within Android 13
), it worked perfectly at 60 FPS as a charm. I hope this information may prove useful in resolving this issue at hand.
Hi, This is a current known issue due to the tracking failure regression on these devices. We're currently working with the Pixel camera team to solve this issue within the camera stack; hoping to get a fix in soon.
Late update, but this is now fixed, provided the device has the Android 14 update or later.
SPECIFIC ISSUE ENCOUNTERED
Having acquired the
Google Pixel 7 Pro
, which supports 60FPS, I endeavored to execute samplecomputer_vision_c
provided in the respective repository. Regrettably, the state of the texture rendering appeared far from achieving the desired 60FPS, hence necessitating this report.VERSIONS USED
Android Studio Electric Eel | 2022.1.1
1.38.0
Google / Pixel 7 Pro / Android 13
1.38.231530493
(updated on Jun 28, 2023)STEPS TO REPRODUCE THE ISSUE
computer_vision_c
sample provided in the respective repository using Android StudioWORKAROUNDS (IF ANY)
ADDITIONAL COMMENTS
void ComputerVisionApplication::obtainCameraConfigs()
within filecomputer_vision_application.cc
. Despite changing the arguments in functionArCameraConfigFilter_setTargetFps
withAR_CAMERA_CONFIG_TARGET_FPS_60
, the camera preview rendering seems to remain at 30FPS.It is my understanding that ARCore is advertised to support up to 60 frames per second (FPS), however, I am having difficulty achieving this performance. I'm unsure whether this is due to a fault in the device itself, a lack in the support of ARCore, or if it is a result of some errors in the usage of code. If indeed the support has been discontinued, it may be prudent to consider its removal from the official documentation for the sake of clarity and accuracy.