VNC for Android via SCRCPY: Difference between revisions

Created page with "Android 1, iPhone 0. At least for FULL remote control. === Download SCRCPY === === Enable Necessary Settings on Android Device === First, good luck finding it as every manufacturer seems to hide the necessary settings in Developer Options in different places (plus obfuscating it by having Developer Options as sub-categories in other Major Categories listed before Developer Options as a main category when searching for it) Anyway, find Developer Options and enable USB..."
 
mNo edit summary
 
Line 1: Line 1:
Android 1, iPhone 0.  At least for FULL remote control.
Android 1, iPhone 0.  At least for FULL remote control.


=== Download SCRCPY ===
===Download SCRCPY===


=== Enable Necessary Settings on Android Device ===
===Enable Necessary Settings on Android Device===
First, good luck finding it as every manufacturer seems to hide the necessary settings in Developer Options in different places (plus obfuscating it by having Developer Options as sub-categories in other Major Categories listed before Developer Options as a main category when searching for it)
First, good luck finding it as every manufacturer seems to hide the necessary settings in Developer Options in different places (plus obfuscating it by having Developer Options as sub-categories in other Major Categories listed before Developer Options as a main category when searching for it)


Anyway, find Developer Options and enable USB Debugging.
Anyway, find Developer Options and enable USB Debugging.


=== Access via TCP/IP ===
===Access via TCP/IP===
Once functionality over USB is established and the devices IP Address is known;
Once functionality over USB is established and the devices IP Address is known;


Using a command prompt (probably from within the Folder where all the SCRCPY programs are)
Using a command prompt (probably from within the Folder where all the SCRCPY programs are)


* adb devices
*adb devices
<syntaxhighlight lang="text">
<syntaxhighlight lang="text">
adb devices
adb devices
Line 20: Line 20:
</syntaxhighlight>
</syntaxhighlight>


* adb tcpip 5555 (that's the default 'common' port)
*adb tcpip 5555 (that's the default 'common' port)
<syntaxhighlight lang="text">
<syntaxhighlight lang="text">
restarting in TCP mode port: 5555
restarting in TCP mode port: 5555
</syntaxhighlight>
</syntaxhighlight>


* adb connect W.X.Y.Z:5555
*adb connect W.X.Y.Z:5555
<syntaxhighlight lang="text">
<syntaxhighlight lang="text">
connected to W.X.Y.Z:5555
connected to W.X.Y.Z:5555
</syntaxhighlight>
</syntaxhighlight>


*  
*


* Disconnect the USB Cable, then...
*Disconnect the USB Cable, then...
** scrcpy
**scrcpy
** ...and  OR...
**...and  OR...
*


=== Troubleshooting ===
...per the later mentioned crash, no mother forking details, just look at the error output for when two devices are connected and use the correct switch, maybe --tcp-something.
 
*
 
===Troubleshooting===
Most issues occur on the phone.  "Resetting" the 'feature(s)' in Developer Options is the best option;
Most issues occur on the phone.  "Resetting" the 'feature(s)' in Developer Options is the best option;


* Turn USB Debugging off and on
*Turn USB Debugging off and on
* Revoke USB debugging authorizations (then unplug the USB adapter, and plug it back in, a message should appear for "...allowing...")
*Revoke USB debugging authorizations (then unplug the USB adapter, and plug it back in, a message should appear for "...allowing...")
 
ALL THE HELP FILES WOULD HAVE BEEN HERE, BUT THEY WON'T BE THANKS TO CHATGPT.
 
=== Final Thoughts (on ChatGPT, not SCRCPY) ===
Most of the stuff on this article just got lost because of ChatGPT crashing the computer this was being written on.  Anger is an understatement.  No foul words allowed here, so I'll sum up what the AI is these days: AI couldn't crash a plane into the ground, because it would already be on fire and have burned up before it got anywhere near the planet's surface.
 
*
*