Open Benjamin-Loison opened 10 months ago
It seems that Wireless debugging turns off on its own after a few seconds to tens of seconds. Well maybe it is due to wifi lost. Maybe related to Benjamin-Loison/android/issues/46.
adb pair 192.168.1.XXX:XXXXX XXXXXX
Successfully paired to 192.168.1.XXX:XXXXX [guid=adb-XXXXXXXX-XXXXXX]
Source: the Android Stack Exchange answer 247618
with my Fairphone 4 LineageOS just restarted.
However, then:
adb devices
List of devices attached
benigumocom/a6a87fc1cb690c3c4e3a7642ebf2be6f
Source: the Android Stack Exchange answer 249230
On Debian 12 GNOME Pegasus.
https://github.com/LineageOS/android_frameworks_base/blob/56a6587c4ef2f34d7290752b16bb1ee50931978e/packages/SettingsLib/res/values-en-rAU/strings.xml#L246
Unclear if
adb tcpip 5555
requires the phone to be connected.Source: stackoverflow.com/a/3623727
It seems to need to:
Can only execute
adb tcpip 5555
when the phone is connected and then it is fine. Ifadb disconnect
and then try to reconnect, it succeeds (I verified multiple times in a row). Is it still the same after a phone reboot? After a reboot reconnecting does not work anymore.When phone running as usually
/default.prop
does not exist from adb root and/system/build.prop
is read-only,w!
does not work.To reboot to recovery I used
Advanced restart
fromSettings
.I tried
Recovery
>Advanced
>Enable ADB
, thenadb pull /prop.default
, edit, thenadb push prop.default /
and finally reboot but it does not work and after rebooting to recovery/prop.default
is as before the edit.I tried manipulating
/system/build.prop
from recovery but the file does not exist even afterRecovery
>Advanced
>Mount/unmount system
. Fastbootd does not look interesting as adb does not work and the possibilities are not interesting.Related to #4.