Replies: 8 comments 11 replies
-
|
Same issue for me connecting toa Pixel 9 Pro XL. |
Beta Was this translation helpful? Give feedback.
-
Is that also running GrapheneOS or some other ROM? |
Beta Was this translation helpful? Give feedback.
-
|
Standard google OS. |
Beta Was this translation helpful? Give feedback.
-
|
change other codec |
Beta Was this translation helpful? Give feedback.
-
|
To expand on what @xlionjuan said above. I have figured you can leave hardware codec enabled on the device like I suggested and when connected change the client settings codec. |
Beta Was this translation helpful? Give feedback.
-
|
Oh mobile devices....you have no choices because those codec will not work. |
Beta Was this translation helpful? Give feedback.
-
|
@21pages follow it up, why is h265 not working? |
Beta Was this translation helpful? Give feedback.
-
|
Hi guys, to help us solve the "scrambled image" problem, could you please:
|
Beta Was this translation helpful? Give feedback.
-
@djgrazzy Thank you for your feedback. The recording should be made through the rustdesk menu |
Beta Was this translation helpful? Give feedback.
-
|
Started Rustdesk record using auto (h265) then switched to VP8 and it created a 2nd file |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, the reason may be that the resolution is 1008*2244, where 1008 is divisible by 16 and 2244 is divisible by 4. I will reply to you here later. |
Beta Was this translation helpful? Give feedback.
-
|
thanks. no rush in my part as the workaround is fine. |
Beta Was this translation helpful? Give feedback.
-
|
Could you please try this build: https://github.com/rustdesk/rustdesk/releases/download/1.2.6/rustdesk-1.2.6-aarch64-signed.apk? There was a historical fix related to this issue: #8121. I will also provide you with another android program to save the raw H.265 video frame later. If we find that the original encoded data is scrambled, I may consider disabling the Exynos MediaCodec, since according to https://lists.ffmpeg.org/pipermail/ffmpeg-trac/2024-December/072083.html, Pixel 8 devices appear to rely on Exynos as well. |
Beta Was this translation helpful? Give feedback.
-
|
I can confirm that version works with the default x265 codec. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I'll compile a nightly version with that fix later |
Beta Was this translation helpful? Give feedback.
-
|
Could you try out https://github.com/21pages/rustdesk/releases/download/nightly/rustdesk-1.4.2-aarch64-align-64.apk? This build includes the fix. |
Beta Was this translation helpful? Give feedback.
-
|
404 on that URL |
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/21pages/rustdesk/releases/download/nightly/rustdesk-1.4.2-aarch64-align-64.apk, updated |
Beta Was this translation helpful? Give feedback.
-
|
I can confirm 1.4.2 linked is also working all 5 codecs Cheers |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Today I tried to set up Rustdesk (from F-Droid) to allow remote access to a newly installed GrapheneOS installation on a Google Pixel 8 phone. I tried connecting from a Debian (Linux) computer and from an Android phone. What I found was that the image was scrambled as shown in the screenshot below. (The little Window saying "Connecting" appeared because the connection had been terminated from the GrapheneOS phone end and I don't think is relevant to my problem.) Does anyone have any idea what the problem might be?
Beta Was this translation helpful? Give feedback.
All reactions