-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
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.
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
Android 13 Release "getDisplayIds" function parameter change, cause scrcpy crash. #3446
Comments
Thank you for the report. Do you want to work on it and modify |
I have an avaliable workaround using another class DisplayManagerGlobal.java I put the code here for you reference.
And here is the change in
|
@DerekWuYD Thank you very much. I opened a PR: #3448, based on your work. Please test, and also provide a name and e-mail ( |
This branch works good!
my name is Derek Wu, Thank you. |
Use the client instance to communicate with the DisplayManager server. Fixes #3446 <#3446> Signed-off-by: Romain Vimont <[email protected]>
Thank you, I amended the commit in the PR.
Awesome, I'd like to have access to so many devices :) Could you also reproduce issue #3416? If so, does the PR #3448 also fix it? |
I can't reproduce issue #3416 in those phone, |
Thanks 👍 merged: 9c1722f |
Use the client instance to communicate with the DisplayManager server. Fixes #3446 <#3446> Signed-off-by: Romain Vimont <[email protected]>
Google Android13.0.0-r16 have reverted the new function DisplayManager.getDisplayIds() with bool parameter and change back to the function without parameter. |
Thank you very much ! |
Environment
Describe the bug
The function
IDisplayManager.getDisplayIds
use inDisplayManager.getDisplayIds()
.No longer exist in Android 13, the new function has a bool parameter.
This function cause scrcpy crash.
Please update the scrcpy to fit this issue.
scrcpy/server/src/main/java/com/genymobile/scrcpy/wrappers/DisplayManager.java
Line 36 in ed84e18
getDisplayIds detail in android code search
New method detail :
The text was updated successfully, but these errors were encountered: