You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I have been using scrcpy with my current setup for days without issue, but today, in Windows PowerShell, in the correct directory, "./scrcpy -s [device serial #]" did not execute past "scrcpy 2.3.1 https://github.com/Genymobile/scrcpy".
Closed Windows PowerShell
Attempted to start from scrcpy.exe and received a message that Windows Defender SmartScreen blocked the application. Sorry, didn't think to get the exact message.
Actions I took without success: "Unblocking" all files in the file properties dialog box, adding exceptions by pointing to adb and scrcpy by path in "Windows 11 Settings > Privacy & security > Windows Security > App & browser control > Exploit protection settings > Program settings > Add program to customize > Choose exact file path" and and turning off all protection measures
I must have started a new PowerShell instance and tried to connect the Pixel 3 and when it similarly failed I did not close the instance. In my frustration went to the Microsoft Store app, searched for "scrcpy" hoping to find something there that might be an alternative or a Store app built on scrcpy. Installed the first result to try, AnLink, opened it, went through setup, and then the usual scrcpy instance open for the Pixel 3. Was able to start all my usual instances of scrcpy to display each of my connected phones. Uninstalled AnLink, closed all Windows Powershell instances, was able to start scrcpy as usual.
On errors, please provide the output of the console (and adb logcat if relevant).
There was no error in the console.
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows
PS C:\Users\Andrew\scrcpy\scrcpy-win64-v2.3.1-3\scrcpy-win64-v2.3.1> ./scrcpy -s 89LX0B6S5
scrcpy 2.3.1 <https://github.com/Genymobile/scrcpy>
Upon successful execution:
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows
PS C:\Users\Andrew\scrcpy\scrcpy-win64-v2.3.1-3\scrcpy-win64-v2.3.1> ./scrcpy -s 08031JECB01289
scrcpy 2.3.1 <https://github.com/Genymobile/scrcpy>
INFO: ADB device found:
INFO: --> (usb) 08031JECB01289 device Pixel_4a__5G_
INFO: (usb) 89LX0B6S5 device Pixel_3
INFO: (usb) R58N35ZZ0KS device SM_A205U
INFO: (usb) R5CT91R66VM device SM_S136DL
C:\Users\Andrew\scrcpy\scrcpy-win64-v2.3.1-3\scrcpy-win64-v2.3.1\scrcpy-server: 1 file pushed, 0 skipped. 50.4 MB/s (66007 bytes in 0.001s)
[server] INFO: Device: [Google] google Pixel 4a (5G) (Android 14)
INFO: Renderer: direct3d
INFO: Texture: 1080x2336
For privacy concerns I changed the name of the folder referenced as C:\Users\Andrew and changed the device serial numbers
Please do not post screenshots of your terminal, just post the content as text instead.
Hope this helps identify the issue and maybe how to improve documentation to help others in the same situation. Please note I am a technology enthusiast and hobbyist, I don't have a lot of experience fixing things, not sure there is much more I can do to help, rarely check my email, and am pretty busy. Just in case you're waiting for me to reply for more information. If I experience any development, I'll try to come back and provide more information, but this is my first contribution to GitHub. I am very grateful for scrcpy, the easiest way to control my Android devices from my Windows machines.
The text was updated successfully, but these errors were encountered:
Environment
Describe the bug
I have been using scrcpy with my current setup for days without issue, but today, in Windows PowerShell, in the correct directory, "./scrcpy -s [device serial #]" did not execute past "scrcpy 2.3.1 https://github.com/Genymobile/scrcpy".
Closed Windows PowerShell
Attempted to start from scrcpy.exe and received a message that Windows Defender SmartScreen blocked the application. Sorry, didn't think to get the exact message.
Actions I took without success: "Unblocking" all files in the file properties dialog box, adding exceptions by pointing to adb and scrcpy by path in "Windows 11 Settings > Privacy & security > Windows Security > App & browser control > Exploit protection settings > Program settings > Add program to customize > Choose exact file path" and and turning off all protection measures
I must have started a new PowerShell instance and tried to connect the Pixel 3 and when it similarly failed I did not close the instance. In my frustration went to the Microsoft Store app, searched for "scrcpy" hoping to find something there that might be an alternative or a Store app built on scrcpy. Installed the first result to try, AnLink, opened it, went through setup, and then the usual scrcpy instance open for the Pixel 3. Was able to start all my usual instances of scrcpy to display each of my connected phones. Uninstalled AnLink, closed all Windows Powershell instances, was able to start scrcpy as usual.
On errors, please provide the output of the console (and
adb logcat
if relevant).There was no error in the console.
Upon successful execution:
For privacy concerns I changed the name of the folder referenced as C:\Users\Andrew and changed the device serial numbers
Please do not post screenshots of your terminal, just post the content as text instead.
Hope this helps identify the issue and maybe how to improve documentation to help others in the same situation. Please note I am a technology enthusiast and hobbyist, I don't have a lot of experience fixing things, not sure there is much more I can do to help, rarely check my email, and am pretty busy. Just in case you're waiting for me to reply for more information. If I experience any development, I'll try to come back and provide more information, but this is my first contribution to GitHub. I am very grateful for scrcpy, the easiest way to control my Android devices from my Windows machines.
The text was updated successfully, but these errors were encountered: