-
-
Notifications
You must be signed in to change notification settings - Fork 7.2k
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
Incorrect Auto codec selection Android 14 phone #8101
Comments
@mikekgr Thanks for your feedback, could you give the related log here? Here are steps:
|
OK I sent you the log from my email : bWlrZWtAb3BlbmZvcmFsbC5jb20= Tell me if you need anything more. Thanks |
Well, in case of manual codec selection e.g. VP9 or AV1, (not the case of log file that was the try of H265) then the fsp IS NOT zero although I did not tried to play video. If you need more testing, I will try anything you need but after 1-1,5 hours. |
Take your time, there's no rush. |
@21pages That's all I can report. Thanks and Best Regards. |
Thanks for your feedback, when the previous pc is available, could you provide the file |
Yes, tomorrow I will do it and I will report here |
Here are some debug tips: |
According to https://en.wikipedia.org/wiki/Intel_Graphics_Technology#Capabilities_(GPU_video_acceleration), i7-3770 CPU (Ivy Bridge) doesn't support H265. The reason may be that the current detection mistakenly think that d3d11 h265 decode acceleration is supported. Please provide old And try https://github.com/21pages/rustdesk/releases/download/nightly/rustdesk-1.2.4-x86_64-more-hwcodec-check.exe, maybe this version will make h265 normal. If not, please give |
Well the result of running decode_check.exe is: [ERROR], sts=MFX_ERR_UNSUPPORTED(-3), `anonymous-namespace'::VplDecoder::init, Query at D:\rustdesk\hwcodec\cpp\mfx\mfx_decode.cpp:110 The test programm: rustdesk-1.2.4-x86_64-more-hwcodec-check.exe still does not work, still get H265 in the Auto place The content of: %appdata%/rustdesk/config/RustDesk_hwcodec.toml is: Am I forgot something useful to you, don't hesitate to ask me, thanks |
Could you provide the content of
If you connect your phone with the new RustDesk.exe with H265, the image is still not normal? Only software h265 decoder is available now. |
Help me to install the nightly release, after having rustdesk-1.2.4-x86_64-more-hwcodec-check.exe installed, tring to install the nightly release does not give me the known update gui button. How to do it ? |
Uninstall the current one, and installation is not needed, let's test with portable.
|
I am trying to install the nightly release (after having installed your test release) and I can't . I am pretty sure that this one Build date: 2024-05-21 02:47 is your testy release. Am I right ? |
Uninstall with windows setting, or uninstall with |
Now the fix has not been merged to the ngihtly build, with the nightly build you have installed now, could you provide the content of |
Here is: ram = ''' |
So the contents of |
I did and I got connection with screen but with chaos as the screens repeat itself |
Sorry, I provide wrong method, your computer doesn't support h265 encoding, could you connect to my computer with public server? I have sent my RustDesk ID to your email. |
Please sent me your email here: bWlrZS5rcmFuaWRpc0BnbWFpbC5jb20= |
in your connection I had H265 in working condition ! |
Did i5-7300U and i7-3770 CPU connect to the same phone? If i5-7300U not connect to the same phone, the problem should still be that the android h265 encoding failed |
Yes these are connecting to my personal OnePlus 9 pro Android phone |
Yes it remained at Connected, waiting for image... |
i5-7300U connect to android with H265: good Seems not reasonable, did you remember i5-7300U connect to android with H265 or other codec? Connect to your phone, and enable file transfer,
|
Ok. connect to your phone with i7-3770 CPU , and enable file transfer, If you control it while it's playing video, will there be hundreds of Error encode: -1 in the android log? If there are, the reason is android encoding failed. |
I can do these tests after returned home (8+ hours), where the Dell laptop is. Then I will be happy to send you the information you asked. |
Thanks, take your time. |
I can do this test because I am in front of this pc. Just tell me, using what coder? Obviously not H265 that is not working... |
Use H265, because H264 is working, I want to know why H265 is not working, |
To understand well, you instruct me to connect from my pc having with i7-3770 CPU to my phone using H265 correct? |
Yes
Playing video is the method to let android encode many times to see whether it can encode successfully, showing correct image on i7-3770 CPU is not required. After connection, could you send the android log and the computer log |
email with the requested Android phone log sent |
Thanks, found the reason, I'll try to fix it. |
@21pages |
@21pages |
Thanks |
@21pages |
Thank you for your help, no further help is needed and I will let you know when the issue is resolved. |
Try next nightly The i7-3770 should be able to connect to with H265, the i5-7300U's image should not have a green bottom. |
Nightly build is under building, will be ready soon. |
@21pages Many thanks for your exceptional work ! |
Nightly build is ready now, take your time. This fix only affects android build, nothing to do with controlling side. |
Bug Description
Using the today nightly release (20-05-2024) I discover an error.
When I am trying to connect to my Android 14 phone from Windows 10, Windows 11 PC then in the Auto possition it select codec H265. Using this Auto codec I get not image. If I manually change to let's say VP9, AV1, H264 etc then I have normal image again.
Please see the Auto codec logic.
Thanks and Best
How to Reproduce
Just follow my steps above
Expected Behavior
To be working fine in the Auto codec possition
Operating system(s) on local side and remote side
Windows 10/11 => Android 14 phone
RustDesk Version(s) on local side and remote side
nightly release 20-05-2024
Screenshots
no
Additional Context
No response
The text was updated successfully, but these errors were encountered: