> Hello; > After I synced Celadon Q, I noticed adb over wifi does not seem to work > anymore. When trying to connect, I get 'connection refused'. > > Does someone know if there are some build options or perhaps > modifications to security options to make it work? Try the following commands. adb shell setprop service.adb.tcp.port 5555 go to CarSetting developer, re-start usb-debug adb connect <ip>:5555

On 9/24/19 4:51 AM, Chih-Wei Huang wrote: > Badrappan, Jeevaka <jeevaka.badrappan(a)intel.com&gt; 於 2019年9月23日 週一 > 下午10:31寫道： >>> Hello; >>> After I synced Celadon Q, I noticed adb over wifi does not seem to >>> work anymore. When trying to connect, I get 'connection refused'. >>> >>> Does someone know if there are some build options or perhaps >>> modifications to security options to make it work? >> >> Try the following commands. >> >> adb shell setprop service.adb.tcp.port 5555 go to CarSetting >> developer, re-start usb-debug adb connect <ip>:5555 > > Have you really tested it?

> > Actually the property has already been set in current init.*.rc: > > on boot > ... > # adb over ethernet > setprop service.adb.tcp.port 5555 > > > But it still doesn't work.

I tried re-starting usb-debug in 'developer options' to see if it matters but it still gives 'connection refused'. I could not do the 'adb shell' step command since that requires a working adb connection.

> > > On 9/24/19 4:51 AM, Chih-Wei Huang wrote: >> Badrappan, Jeevaka <jeevaka.badrappan(a)intel.com&gt; 於 2019年9月23日 > 週一 >> 下午10:31寫道： >>>> Hello; >>>> After I synced Celadon Q, I noticed adb over wifi does not seem to >>>> work anymore. When trying to connect, I get 'connection refused'. >>>> >>>> Does someone know if there are some build options or perhaps >>>> modifications to security options to make it work? >>> >>> Try the following commands. >>> >>> adb shell setprop service.adb.tcp.port 5555 go to CarSetting >>> developer, re-start usb-debug adb connect <ip>:5555 >> >> Have you really tested it? Yes tested on KBL NUC commercial device which has adb over usb working. >> >> Actually the property has already been set in current init.*.rc: >> >> on boot >> ... >> # adb over ethernet >> setprop service.adb.tcp.port 5555 >> >> >> But it still doesn't work. Vendor init can't set the system property. So, even if it is set in service.adb.tcp.port, it won't be set properly. You can confirm that by querying the property value adb shell getprop > > I tried re-starting usb-debug in 'developer options' to see if it matters but it > still gives 'connection refused'. I could not do the 'adb shell' step command > since that requires a working adb connection. Could you share the device you are using and also the BIOS version?