Files
project-iphone-unlock-app/README_ETHERNET_FIX.md
2026-10-29 13:29:14 +06:00

33 lines
3.0 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Ethernet Tethering Diagnostics and Status Patch
This project patch repairs misleading connection-state handling and makes the dashboard report the actual Ethernet/tethering state as far as the Android platform permits.
## Changes in this patch
- Replaced the old `SYSTEM_TETHERING` branch that marked routing `ACTIVE` without a system callback.
- Updated routing stop handling so it does not report `STOPPED` before a stop is confirmed. The Ethernet tethering type is used rather than the Wi-Fi type.
- The dashboard now labels the physical link as `Ethernet Interface`, shows a real connection-state label, and displays the current tethering result message.
- Removed the previous dashboard instruction to open Android Settings. Settings navigation callbacks remain in-app only and show an explanation instead.
- Replaced the old scripted iPhone-unlock terminal log view with actual network/tethering diagnostic logs. This patch does not implement or claim to bypass iPhone Activation Lock.
- Moved Ethernet refresh and ARP scanning work away from the UI thread and retained root-check work on IO.
- Added English and Simplified Chinese strings for the new status and error messages.
- The device model card continues to show only the dynamically detected model.
## Important platform limit
This is still a normal third-party Android application. It cannot grant itself `TETHER_PRIVILEGED`. On Android 13–15, the platform may accept a tethering request only when the required system access is already available; this patch does not open Settings automatically. On Android 16, the public SDK does not expose a universal Ethernet tethering request for ordinary apps. Some models therefore will show `Unavailable` rather than a false `Connected` status. OEM-authorized system integration may be required for direct control.
The screenshot supplied with the project also showed `Ethernet Interface: Disconnected`. A compatible physical Ethernet adapter/cable and an active link are required for link status to become connected; software cannot manufacture a physical link.
## Build and verification status
Static resource checks passed: both language XML files parse, contain no duplicate string keys, and include every `R.string` referenced by Kotlin source. A Gradle build could not be completed in this environment because the Gradle wrapper distribution was not cached and `services.gradle.org` was unreachable; no Android SDK `android.jar` is installed here. Therefore this is a source patch, not a newly built or device-tested APK.
## Build on your computer
1. Extract this ZIP to a new folder.
2. Open that folder in Android Studio.
3. Let Android Studio select your local Android SDK; the Windows-specific `local.properties` from the uploaded project was intentionally omitted.
4. Sync Gradle and run **Build > Make Project**.
5. Test on the real device with a supported Ethernet adapter and cable. If Android reports that the required control permission is unavailable, the normal APK cannot force the system to enable Ethernet tethering.