Does not seems to work on Android 14
Closed this issue · 12 comments
I have installed the module on Magisk, but wirelss debugging status does not seem to be preserved and I have to manually turn on Wireless debugging after reboot. My device is Pixel Tablet Android 14
I have installed the module on Magisk, but wirelss debugging status does not seem to be preserved and I have to manually turn on Wireless debugging after reboot. My device is Pixel Tablet Android 14
It seems that WiFi adb in Android 14 requires the client to pair with it before connecting to it, and a random port is used. I'll check it out when I have a test device....
Yeah I have to use a tasker task which it will run commend in Termux to turn on the wireless debugging. Here is the link if you need for reference:
https://taskernet.com/shares/?user=AS35m8lyfRz0LQjeOnogH2mWAtM%2B%2BYGrKyboB3uwK0gLnPDzK0woCq2eOYCXmK8vB3YdObHjDO4%3D&id=Profile%3AEnable+ADB+Wifi+on+Boot
I have installed the module on Magisk, but wirelss debugging status does not seem to be preserved and I have to manually turn on Wireless debugging after reboot. My device is Pixel Tablet Android 14
Hi there! I'm currently working on the bug you mentioned earlier and I have also been able to reproduce the issue. It turns out that this bug is not related to the Android version; rather, the issue lies with the ADB status detection script in the module, which is not functioning correctly. I'll fix it soon. :)
please check if this issue is fixed in https://github.com/mrh929/magisk-wifiadb/releases/tag/alpha-1.0.2-07a7c99
please check if this issue is fixed in https://github.com/mrh929/magisk-wifiadb/releases/tag/alpha-1.0.2-07a7c99
not work on a15 pixel 6a. need manually turn on Wireless debugging after reboot.
@westruk have you tried connecting to the device by running adb connect deviceip:5555 ?
The checkbox in the settings will not be active, but remote adb debugging is actually enabled, and does not require pairing
The checkbox in the settings is an entirely separate new way of using adb remotely, and is not affected by this magisk module
@mrh929 I can confirm that the issue is fixed in the latest release running on LineageOS 21 (Android 14) on Samsung Galaxy S8+
@mrh929 btw why has the default maintain availability sleep duration been reduced from 5 seconds to 1?
Is there some particular reason on why 1 second is better than 5?
@mrh929 btw why has the default maintain availability sleep duration been reduced from 5 seconds to 1? Is there some particular reason on why 1 second is better than 5?
No particular reason... maybe it makes the adb status more quickly. One day I'll put it in the configuration so that can modify the duration yourself.
ooops, I have already written it
03ca76d#diff-0ede375d8e820613a388eb76649bc0de30f09f96b7c65f82b5ab880512e796c6R15
@mrh929 yeah, I've seen the option in the configuration - was wondering if there was some particular reason for the change.
Thanks for the quick response, and for creating this module - it has helped me a lot!