Phone charges but is not detected
Charging does not prove that a cable carries data. Try a known data-capable cable and a different USB port; connect directly to the computer if possible. Unlock the phone and reconnect it before checking again.
LeapWay runs on Windows and connects to Android over USB. Use this checklist before choosing a test location. The current desktop interface is in Simplified Chinese.
Have these ready before opening the setup flow.
Android menu names vary by manufacturer and operating-system version.
Download the Windows installer from the LeapWay home page, then open the desktop client.
Unlock the phone and connect it to the computer with a data-capable USB cable.
In Android Settings, find Build number and tap it seven times to enable Developer options; you may be asked for your device PIN. Open Developer options and enable USB debugging. Menu paths vary by device; see Android's Developer options guide.
If Android asks whether to allow USB debugging, review the prompt and approve it for this computer. Then return to LeapWay.
Follow the Windows client’s setup instructions to install the Android assistant and grant its requested location permission.
When setup is ready, choose a point on the desktop map and check the result on your Android test device.
USB debugging gives a connected computer additional access to the device. Use a computer you trust and turn USB debugging off when you no longer need it.
Check the connection basics before repeating setup.
If the phone only charges or Windows shows no response, check the cable and port first. If Windows notices the phone but LeapWay does not, check USB debugging, the authorization prompt, and any device-driver errors. Seeing files in Windows alone does not confirm that USB debugging is authorized.
Charging does not prove that a cable carries data. Try a known data-capable cable and a different USB port; connect directly to the computer if possible. Unlock the phone and reconnect it before checking again.
Confirm Developer options and USB debugging are enabled. Disconnect and reconnect the cable so Android can show its authorization prompt again.
Keep the device unlocked, confirm USB debugging is enabled, and reconnect the cable. If the prompt appears, review it and approve only a computer you trust. See Android's USB debugging authorization guidance.
Open Device Manager and look for the connected device or a device with an error. Windows may need the appropriate USB driver for debugging; follow your device manufacturer's instructions or consult Android's OEM USB driver guide. Avoid installing drivers from untrusted download sites.
File access and USB debugging are different checks. Confirm debugging is enabled and the computer is authorized on the phone, then follow the client setup instructions again. If the problem remains, record the exact message and device details for support.
After setup, compare the location shown by a trusted location app with the point selected for the test. If they differ, check location permissions and any setup messages; results can vary by app and device.
A verified Android model and version compatibility list is not currently published. Record your device model and Android version before relying on LeapWay for a test.
Android's hardware-device troubleshooting guide covers USB connection checks and Windows drivers. Its Android Studio-specific steps may not apply to LeapWay.
Note your Windows version, Android model and version, cable type, and the exact error shown, then email tushikeji2@163.com for customer support.
Current product details and known limits.
The current Terms of Service say the service is offered free of charge. Any future paid features or subscriptions will be presented before a charge.
Root access is not listed as a requirement in the current setup instructions. LeapWay does require Developer options, USB debugging, and approval of the Android prompt for your computer. Follow the current client instructions if your device shows an additional requirement.
Yes. LeapWay includes a companion Android assistant. Start setup in the Windows client, follow its installation guidance, and grant the location permission it requests.
USB debugging lets the Windows client communicate with the Android device to complete setup. Approve only a computer you trust and turn USB debugging off when you no longer need it.
No verified device and Android-version matrix is currently published, so compatibility across models and versions is not guaranteed. Check the setup flow on the exact device you plan to test.
The current desktop interface is in Simplified Chinese. This website is in English.
Disconnecting ends the USB connection, but do not assume it automatically restores the device’s normal location. Stop the active location test in LeapWay first, then verify the device in a trusted location app.
Stop the active test in LeapWay, disconnect the device, and verify its location in a trusted app. If it still appears changed, restart the affected app or device and check Android’s mock-location setting; menu names vary by device and Android version. Turn USB debugging off when it is no longer needed.
Use location testing only where you have permission. Third-party apps may prohibit simulated or modified locations; review their rules before testing. See the Terms of Service.
Review the compatibility and USB debugging requirements before connecting your Android device. For test planning and verification, read the Android mock location guide.