Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.os.linux > #82796 > unrolled thread

PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing

Back to article view | Back to alt.os.linux

Contents

  PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-10 02:07 -0600
    Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-11 21:49 -0500
      Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-12 16:17 -0500
        Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Hank Rogers <Hank@nospam.invalid> - 2026-06-12 16:32 -0500
          Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Give It A Try <try.it@invalid.invalid> - 2026-06-12 23:20 +0100
          Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-13 11:31 -0500
    Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing 🇵🇱Jacek Marcin Jaworski🇵🇱 <jmj@energokod.gda.pl> - 2026-06-15 11:08 +0200
      Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Paul <nospam@needed.invalid> - 2026-06-15 12:11 -0400
        Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing 🇵🇱Jacek Marcin Jaworski🇵🇱 <jmj@energokod.gda.pl> - 2026-06-15 19:24 +0200
          Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-15 14:10 -0500
            Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-15 14:43 -0500
            Re: PSA: Streamlined persistent ADB port over   Wi‑Fi without repeated pairing vallor <vallor@vallor.earth> - 2026-06-17 00:16 +0000
              Re: PSA: Streamlined persistent ADB port over   Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-16 23:23 -0500
        Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-15 13:56 -0500
          Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Warpinator <invalid@invalid.invalid> - 2026-06-16 00:23 +0100
            Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-15 19:18 -0500
              Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing "Carlos E. R." <robin_listas@es.invalid> - 2026-06-16 12:15 +0200
                Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-30 22:12 -0400
                  Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing "Carlos E. R." <robin_listas@es.invalid> - 2026-07-01 11:51 +0200
                    Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-07-01 13:57 -0400
      Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Chris <ithinkiam@gmail.com> - 2026-06-16 07:07 +0000
        Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-16 02:21 -0500
          Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing "Carlos E. R." <robin_listas@es.invalid> - 2026-06-16 12:30 +0200
            Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-16 12:07 -0500
              Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing "Carlos E. R." <robin_listas@es.invalid> - 2026-06-16 20:11 +0200
                Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-16 14:40 -0500
                  Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing "Carlos E. R." <robin_listas@es.invalid> - 2026-06-16 22:47 +0200
                    Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-16 15:51 -0500
                      Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing "Carlos E. R." <robin_listas@es.invalid> - 2026-06-18 00:45 +0200
                        Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Hank Rogers <Hank@nospam.invalid> - 2026-06-17 17:56 -0500
                          Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-30 21:46 -0400
                  Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing "....winston" <winstonmvp@gmail.com> - 2026-06-16 19:47 -0400
                    Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-16 23:26 -0500
          Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Chris <ithinkiam@gmail.com> - 2026-06-16 12:10 +0000
            Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-16 12:09 -0500
              Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-26 06:38 -0400
    Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-20 02:22 -0500
      Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-20 02:31 -0500
      Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-21 00:53 -0500
    Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-27 08:58 -0400
      Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Nadia Jarvis <invalid@invalid.invalid> - 2026-06-27 19:38 +0100
        Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Hank Rogers <Hank@nospam.invalid> - 2026-06-27 19:53 -0500
          Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-27 23:01 -0600
            Re: PSA: Streamlined persistent ADB port over Wi‑Fi without repeated pairing Maria Sophia <mariasophia@comprehension.com> - 2026-06-30 21:40 -0400

Page 3 of 3 — ← Prev page 1 2 [3]

#82866

On 27/06/2026 13:58, Maria Sophia wrote:
> Things have drastically changed for the better! Ports are not needed!

Does this mean that Israel won't require the ports of Haifa and Ashdod? 
Could you please explain?

It seems that Israel wasted money on creating a new port at Ashdod in 
1965. They could just use Android phones to transport cargo and run 
their economy.

[toc] | [prev] | [next] | [standalone]

#82868

Nadia Jarvis wrote on 6/27/2026 1:38 PM:
> On 27/06/2026 13:58, Maria Sophia wrote:
>> Things have drastically changed for the better! Ports are not needed!
> 
> Does this mean that Israel won't require the ports of Haifa and Ashdod?
> Could you please explain?
> 
> It seems that Israel wasted money on creating a new port at Ashdod in
> 1965. They could just use Android phones to transport cargo and run
> their economy.

Be patient.  Mary will fix all the ports for the poor long suffering 
jews.  Maybe she will even give them some money to make them happy.

[toc] | [prev] | [next] | [standalone]

#82871

Hank Rogers wrote:
>  fix all the ports

Good news. 
Thanks to the advice in this ng, I've removed all the ports completely.

There's now no need to look at the Wireless debugging ports ever again!

I'm overjoyed with the poorly documented new Android 12+ ability to connect
the phone to adb/scrcpy over Wi-Fi without needing to know any ports!

This may be the best documention on the planet for that, for all I know!

Below is a debug script to help others figure out their adb daemon status.
 adbdebugtls.bat (Linux/macOS will come later, after full testing is done)

This reports adb daemon status on the phone:
 $ adb devices
   a. device -> ADB daemon is alive and authenticated
   b. offline -> ADB daemon is alive but handshake failed
   c. unauthorized -> ADB daemon alive but waiting for authorization
   d. (empty) -> ADB daemon is asleep or not advertising
   e. adb-SERIAL._adb-tls-connect._tcp -> TLS advertiser is awake
   f. 192.168.x.x:5555 -> classic TCP/IP daemon is awake

This gives internal daemon state for reachable devices:
 $ adb shell getprop init.svc.adbd
   a. running -> ADB daemon is active
   b. stopped -> daemon is not running
   c. restarting -> daemon is restarting (rare)

This checks whether Android 12+ TCP mode is active:
 $ adb shell getprop service.adb.tcp.port
   a. 5555 -> classic TCP/IP mode active
   b. -1 or empty -> TCP mode off

This checks whether ADB is enabled:
 $ adb shell getprop ro.adb.secure
   a. 1 -> secure ADB enabled
   b. 0 -> insecure ADB (rare on modern devices	)

This checks whether the Android 12+ TLS advertiser is awake:
 $ adb mdns services
   adb-SERIAL-GUID._adb-tls-connect._tcp
    a. Entry present -> TLS daemon is awake
    b. Entry missing -> TLS daemon is asleep
    c. Entry present but adb devices empty -> TLS handshake failed
Note that is the most important check as it often falls asleep!

This tests whether the classic TCP/IP daemon is alive:
 $ adb connect 192.168.1.4:5555
   a. connected -> TCP daemon alive
   b. unable to connect -> TCP daemon not running
   c. no route to host -> phone not on LAN
   d. connection refused -> port 5555 closed

Here's a manual test of the commands while Android 12+ is connected.
  C:\> adbconnecttls.bat
  ============================================
  ADB-over-TLS to TCP/IP Launcher (Debug Mode)
  ============================================
  
  STEP 1: adb kill-server
  adb kill-server
  
  STEP 2: adb start-server
  adb start-server
  * daemon not running; starting now at tcp:5037
  * daemon started successfully
  
  STEP 3: adb disconnect (kills TLS ghost)
  adb disconnect
  disconnected everything
  
  STEP 4: adb connect 192.168.1.4:5555
  adb connect 192.168.1.4:5555
  connected to 192.168.1.4:5555
  
  STEP 5: Launch scrcpy silently
  Running: scrcpy.exe --tcpip=192.168.1.4 --keyboard=sdk
  
  Done.
    
  C:\> adb devices
       List of devices attached
       192.168.1.4:5555        device
  
  C:\> adb shell getprop init.svc.adbd
       running

  C:\> adb shell getprop service.adb.tcp.port
       5555
  
  C:\> adb shell getprop ro.adb.secure
       1
  
  C:\> adb mdns services
       List of discovered mdns services
       adb-SERIAL_adb._tcp       192.168.1.4:5555
       adb-SERIAL-GUID_adb-tls-connect._tcp   192.168.1.4:36401

Note that the TLS advertiser (_adb-tls-connect._tcp) is part of:
 com.android.adb.adbd
Which is flaky because this service goes idle on the phone when:
 a. Wireless Debugging hasn't been toggled recently
 b. The phone has been idle
 c. The system kills the advertiser to save power
 d. The ADB daemon restarts internally
 e. Wi-Fi reconnects
 f. The phone roams between APs

When the TLS advertiser sleeps, adb mdns services returns nothing.
When that happens there are 3 reliable ways to wake the TLS advertiser:
 a. Toggle Wireless Debugging OFF -> ON
 b. Restart the ADB daemon on the phone
    That works only if you already have a connection (USB or TCP)
 c. Force ADB to reconnect via TCP/IP

This is the trick the adbconnecttls.bat launcher uses:
 i. adb kill-server
 ii. adb start-server
 iii. adb disconnect
 iv. adb connect PHONE_IP:5555
     That does not wake TLS because it bypasses TLS entirely
     which is done because scrcpy can't use TLS as far as I know.

 This script below provides ADB-over-TLS, TCP/IP mode diagnostics
 including adbd state, Wireless Debugging state & scrcpy readiness.

  @echo off
  setlocal enabledelayedexpansion
  
  :: adbdebugtls.bat (Android 12+ ADB/TLS Diagnostic Tool)
  :: Runs a full diagnostic of ADB-over-TLS, TCP/IP mode, adbd state, 
  :: Wireless Debugging state, and scrcpy readiness for Android 12+.
  ::
  :: v1p0 20260627
  ::   Diagnose the state of Android's ADB daemon on Android 12+ devices,
  ::   including TLS advertiser status, TCP/IP mode, adbd internal state,
  ::   Wireless Debugging service state and scrcpy readiness.
  ::
  ::   Android 12+ introduced ADB-over-TLS Auto-Discovery, which broadcasts
  ::   on the LAN using mDNS as:
  ::       _adb-tls-connect._tcp
  ::   The desktop ADB server auto-connects to this TLS service as:
  ::       adb-SERIAL._adb-tls-connect._tcp
  ::   This TLS system:
  ::     a. bypasses pairing
  ::     b. bypasses USB authorization
  ::     c. bypasses debug ports
  ::     d. auto-connects whenever ADB restarts
  ::   But scrcpy cannot use TLS directly. It only supports:
  ::     a. USB
  ::     b. Classic TCP/IP ADB (port 5555)
  ::   Hence, this script checks:
  ::     1. TLS advertiser status (adb mdns services)
  ::     2. TCP/IP connectivity on port 5555
  ::     3. adbd internal state via getprop
  ::     4. Wireless Debugging service state via dumpsys
  ::        Note Samsung may hide or rename the Wireless Debugging service.
  ::     5. scrcpy readiness (device state)
  ::   Note the wake attempts when the phone TLS service goes asleep.
  ::     i. Restarting the PC ADB server
  ::     ii. Restarting adbd on the phone (if reachable)
  ::     iii. Forcing TCP/IP fallback on port 5555
  ::   Note Android does not expose a command to toggle Wireless Debugging.
  ::   So the TLS advertiser cannot be automaticaly awakened from ADB.
  ::   Hence, this script reports TLS sleep but cannot force it awake.
  :: 
  echo ============================================
  echo ADB Debug Tool (Android 12+ TLS Diagnostic)
  echo ============================================
  echo.
  
  :: Set your phone IP here
  set PHONE_IP=192.168.1.4
  
  echo.
  echo === 1. Restart PC ADB Server ===
  echo adb kill-server
  adb kill-server
  echo adb start-server
  adb start-server
  echo.
  
  echo.
  echo === 2. TLS Status (mDNS Advertiser) ===
  echo Command: adb mdns services
  adb mdns services | findstr /I "_adb-tls-connect._tcp"
  if errorlevel 1 (
      echo TLS advertiser is asleep or not broadcasting.
  ) else (
      echo TLS advertiser is active.
  )
  echo.
  
  echo.
  echo === 3. TCP/IP Status (Port 5555) ===
  echo Command: adb connect %PHONE_IP%:5555
  adb connect %PHONE_IP%:5555
  echo.
  
  echo Command: adb devices
  adb devices
  echo.
  
  echo.
  echo === 4. Attempting to Wake adbd (if reachable) ===
  echo Trying: adb shell stop adbd
  adb shell stop adbd 2>nul
  echo Trying: adb shell start adbd
  adb shell start adbd 2>nul
  echo.
  
  echo.
  echo === 5. adbd Internal State ===
  echo Command: adb shell getprop init.svc.adbd
  adb shell getprop init.svc.adbd
  echo.
  
  echo Command: adb shell getprop service.adb.tcp.port
  adb shell getprop service.adb.tcp.port
  echo.
  
  echo Command: adb shell getprop ro.adb.secure
  adb shell getprop ro.adb.secure
  echo.
  
  echo.
  echo === 6. Wireless Debugging State ===
  echo Command: adb shell dumpsys activity service ^
      com.android.adb.adbd
  adb shell dumpsys activity service com.android.adb.adbd
  echo.
  
  echo.
  echo === 7. scrcpy Readiness Check ===
  echo If device shows as "device", scrcpy can run.
  echo If port 5555 is active, scrcpy --tcpip works.
  echo.
  
  echo Command: adb devices
  adb devices
  echo.
  
  echo ============================================
  echo Diagnostics complete.
  echo ============================================
  
  endlocal
  exit /b

  :: end of adbdebugtls.bat
-- 
Usenet isn't for amusement - it allows intelligent people to share ideas.
Some invest seconds to post stupid jokes but it takes hours to add value.

	

[toc] | [prev] | [next] | [standalone]

#82883

In the beginning, I used USB to connect adb & scrcpy to the desktop PC.
Then in Android 11 I used Wi-Fi pairing with the pairing & debug port.
In Android 12, the ability to pair without knowing the ports was added.

In using the script to pair without knowing the ports, I've run into a bunch of situations depending on the state of the phone & the computer.

Hopefully I've added everything possible to this latest script for you.
Note it doesn't use TLS, per se, but TLS controls adb's reachability.

  :: adbconnecttls.bat 
  ::   Connects Android 12+ to adb & scrcpy WITHOUT needing any information!
  ::
  ::   This script launches scrcpy over classic TCPIP mode on Android 12 
  ::   and newer devices. It does not use TLS for the scrcpy connection, 
  ::   but it depends on the Wireless Debugging TLS service being awake 
  ::   because TLS controls whether adbd is reachable. The script resets 
  ::   the ADB server, removes stale TLS ghost sessions, checks TLS 
  ::   advertiser state, tests TCPIP reachability, verifies USB debugging 
  ::   authorization and attempts a direct connection to port 5555. It 
  ::   then launches scrcpy silently and detects whether the connection 
  ::   succeeded. If TLS is asleep, TCPIP is active but refusing 
  ::   connections, USB debugging is authorized and scrcpy fails, the 
  ::   script reports that the phone is in ADB Deep Sleep and instructs 
  ::   the user to toggle Wireless debugging or reboot the phone to wake 
  ::   adbd.
  ::
  :: v1p4 20260630
  ::   Added deep sleep detector
  ::
  :: v1p3 20260630
  ::   Added TCP/IP sleep detector and USB authorization detector
  ::
  :: v1p2 20260630
  ::   Added detection and reporting if scrcpy didn't launch
  ::
  :: v1p1 20260630
  ::   Added version string
  ::   Added TLS sleep detection
  ::   Added user guidance when TLS is asleep
  ::   Removed parentheses and arrows from comments
  ::   Cleaned formatting for stability
  ::
  :: v1p0 20260601
  ::   Simplest possible Wi-Fi scrcpy launcher for Android 12+ devices that
  ::   auto-advertise ADB-over-TLS. This script avoids pairing, avoids USB,
  ::   avoids debug ports, and avoids the TLS "ghost device" problem.
  ::   Android 12+ added a new ADB system called ADB-over-TLS Auto-Discovery.
  ::   It broadcasts on the LAN using mDNS as:
  ::       _adb-tls-connect._tcp
  ::   The desktop ADB server auto-connects to this TLS service with:
  ::       adb-SERIAL-GUID._adb-tls-connect._tcp
  ::   This TLS connection:
  ::     a. bypasses pairing
  ::     b. bypasses USB authorization
  ::     c. bypasses debug ports
  ::     d. auto-connects whenever ADB restarts
  ::   BUT scrcpy cannot use TLS directly. It only supports:
  ::     a. USB
  ::     b. Classic TCP/IP ADB (port 5555)
  ::  Note this script has no need for pairing or debug ports.
  ::  This script does not require USB nor does it depend on TLS being awake.
  ::  But Android's TLS ADB service is rather flaky in that it can:
  ::     a. go idle
  ::     b. stop advertising
  ::     c. return as "offline"
  ::     d. require Wireless Debugging toggle OFF->ON to wake up
  :: So this script avoids TLS entirely by connecting only to port 5555.
  ::   This script:
  ::   1. Kills the ADB server (removes stale TLS sessions)
  ::   2. Starts the ADB server cleanly
  ::   3. Disconnects all devices (removes TLS ghost device)
  ::   4. Connects directly to PHONE_IP:5555
  ::   5. Launches scrcpy silently using classic TCP/IP mode
  ::   Running "adb -s <tls-id> tcpip 5555" forces Android to open port 5555
  ::   even when Wireless Debugging is ON. Once opened, port 5555 stays active
  ::   until the PHONE reboots. This makes reconnections simple and stable.
  
  @echo off
  setlocal enabledelayedexpansion
  
  :: Version string
  set SCRIPT_VERSION=v1p4
  set SCRIPT_DATE=20260630
  
  echo ============================================
  echo ADB-over-TLS to TCPIP Launcher Debug Mode
  echo Running adbconnecttls.bat %SCRIPT_VERSION% %SCRIPT_DATE%
  echo ============================================
  echo.
  
  :: Set your phone IP here
  set PHONE_IP=192.168.1.4
  set SCRCPY_OPTS=--keyboard=sdk
  
  echo STEP 1: adb kill-server
  echo adb kill-server
  adb kill-server
  echo.
  
  echo STEP 2: adb start-server
  echo adb start-server
  adb start-server
  echo.
  
  echo STEP 3: adb disconnect to remove TLS ghost
  echo adb disconnect
  adb disconnect
  echo.
  
  echo STEP 4: Check TLS advertiser status
  echo Command: adb mdns services
  adb mdns services | findstr /I "_adb-tls-connect._tcp" >nul
  
  if errorlevel 1 (
      echo.
      echo TLS advertiser is ASLEEP.
      echo Wireless Debugging is ON but the phone is not broadcasting TLS.
      echo.
      echo Meaning:
      echo   The phone cannot auto-connect over TLS.
      echo   The PC cannot wake the phone via TLS.
      echo.
      echo Fix:
      echo   On the phone, toggle Wireless debugging OFF then ON.
      echo   Or reboot the phone to restart Wireless Debugging.
      echo.
      echo After waking TLS, re-run adbconnecttls.bat.
      echo.
  ) else (
      echo TLS advertiser is ACTIVE.
      echo The phone is broadcasting TLS normally.
  )
  
  echo.
  
  echo STEP 5: adb connect %PHONE_IP%:5555
  echo adb connect %PHONE_IP%:5555
  adb connect %PHONE_IP%:5555
  echo.
  
  echo Checking TCPIP mode...
  adb connect %PHONE_IP%:5555 >nul
  
  :: Added TCP/IP sleep detector and USB authorization detector in v1p3
  if errorlevel 1 (
      echo.
      echo TCPIP mode is ASLEEP.
      echo The phone refused the TCPIP connection.
      echo adbd is asleep or Wireless Debugging is asleep.
      echo.
      echo Fix:
      echo   On the phone, toggle Wireless debugging OFF then ON.
      echo   Or reboot the phone to restart Wireless Debugging.
      echo.
      echo After waking TLS, re-run adbconnecttls.bat.
      echo.
  ) else (
      echo TCPIP mode is ACTIVE.
  )
  
  echo Checking USB authorization...
  adb devices | findstr /I "device" | findstr /V ":" >nul
  
  if errorlevel 1 (
      echo.
      echo USB debugging is NOT authorized.
      echo USB is connected but the phone is not authorized for ADB.
      echo.
      echo Fix:
      echo   Unlock the phone and press Allow USB debugging.
      echo.
  ) else (
      echo USB debugging is authorized.
  )
  
  echo STEP 6: Launch scrcpy silently
  set VBS_TEMP=%TEMP%\scrcpy_tls_runner.vbs
  
  echo strCommand = "cmd /c scrcpy.exe --tcpip=%PHONE_IP% %SCRCPY_OPTS%" > "%VBS_TEMP%"
  echo CreateObject("Wscript.Shell").Run strCommand, 0, false >> "%VBS_TEMP%"
  
  echo Running: scrcpy.exe --tcpip=%PHONE_IP% %SCRCPY_OPTS%
  wscript.exe "%VBS_TEMP%"
  
  :: Detect if scrcpy didn't launch and suggest a fix v1p2
  echo Checking if scrcpy connected...
  adb devices | findstr /I "%PHONE_IP%" >nul
  
  if errorlevel 1 (
      echo.
      echo scrcpy did NOT connect.
      echo.
      echo Meaning:
      echo   The phone did not accept TCPIP connection.
      echo   adbd is asleep or Wireless Debugging is asleep.
      echo.
      echo Fix:
      echo   On the phone, toggle Wireless debugging OFF then ON.
      echo   Or reboot the phone to restart Wireless Debugging.
      echo.
      echo After waking TLS, re-run adbconnecttls.bat.
      echo.
  ) else (
      echo scrcpy connected successfully.
      echo.
      echo scrcpy is running over TCP/IP.
      echo Connection successful.
      echo.
      goto :EOF
  )
  
  echo.
  echo Done.
  echo.
  
  endlocal
  exit /b
  
  :: end of adbconnecttls.bat
-- 
For some people, Usenet is amusement, but for me, it's for adding value.

[toc] | [prev] | [standalone]

Page 3 of 3 — ← Prev page 1 2 [3]

Back to top | Article view | alt.os.linux

csiph-web