1405218 - Web IDE not connecting to my Xiaomi Redmi Note 4X

Status: RESOLVED WONTFIX

(DevTools Graveyard :: WebIDE, defect, P3)

Description

[meir_anolick]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20170925150345
Firefox for Android

Steps to reproduce:

1. Turned on USB debugging from developer options on my Redmi Note.
2. Turned on Remote debugging via USB from Firefox settings.
3. Opened the WebIDE from Firefox on my desktop.


Actual results:

My phone did not show up on the list of USB devices.


Expected results:

My phone should have been listed as a USB device.
I purchased this phone just a week ago. Previously I had been using a Moto G 2nd Gen and the USB debugging worked as expected.

Comment 1

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

Do you happen to have the `adb` command line tool installed?

If you do, does `adb devices` show your phone when it's connected to the computer?

Comment 2

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

(For now, I'll assume the issue is device specific.)

Comment 3

[meir_anolick]

I downloaded adb and ran `adb devices` and my phone is showing up:
List of devices attached
VG****       device product:nikel model:Redmi_Note_4X device:nikel

While I was checking this and playing with options, my phone showed up for a split second in the Web IDE as I changed the USB connection type on my phone from "Charging Only" to "Transfer files (MTP)", but I couldn't get it to happen again.

Comment 4

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

(In reply to meir_anolick from comment #3)
> I downloaded adb and ran `adb devices` and my phone is showing up:
> List of devices attached
> VG****       device product:nikel model:Redmi_Note_4X device:nikel
> 
> While I was checking this and playing with options, my phone showed up for a
> split second in the Web IDE as I changed the USB connection type on my phone
> from "Charging Only" to "Transfer files (MTP)", but I couldn't get it to
> happen again.

Thanks for checking this.  I guess this implies that "USB debugging" in Android's Developer Options is already enabled.

What about USB debugging inside Firefox on the device, is this also enabled?

Please also check https://developer.mozilla.org/en-US/docs/Tools/WebIDE/Troubleshooting, there are additional steps to try.

Comment 5

[meir_anolick]

(In reply to J. Ryan Stinnett [:jryans] (use ni?) from comment #4)
> Thanks for checking this.  I guess this implies that "USB debugging" in
> Android's Developer Options is already enabled.
> 
> What about USB debugging inside Firefox on the device, is this also enabled?
> 
> Please also check
> https://developer.mozilla.org/en-US/docs/Tools/WebIDE/Troubleshooting, there
> are additional steps to try.

Yes, USB debugging inside Firefox on the device is enabled. I've tried toggling it on and off as well.

I've looked at the troubleshooting page but I'll review it again now:
My Firefox for Android version is 56, so that's not the problem.
I tried toggling Remote debugging.
I tried switching USB ports, and also using my old USB cable even though it's longer (I've been using the new one that came with this phone).
Only thing I'm not sure about is how to make sure my device is using the Google USB Driver.

Comment 6

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

If you look in the add-ons manager, what version do you see for ADB Helper?  The latest is 0.11.2, so please update if you have something else.

Since you have `adb` installed, try the following:

* Open Firefox on the device
* Connect to computer via USB
* On computer, run `adb shell cat /proc/net/unix` and attach the output to this bug

It's possible ADB Helper can't find Firefox socket for your device, so that should help diagnose the issue.

Comment 7

[meir_anolick]

Attachment: Result of `adb shell cat /proc/net/unix` command

I'm attaching the output from the `adb shell cat /proc/net/unix` command in a text file.

Comment 8

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

Hmm, that's very interesting.

So, the Firefox socket does appear in list, which is good to see.

I wonder if the various Unicode characters here are confusing things.

When you run `adb shell cat /proc/net/unix`, are lines like @mnld_main_socket really followed by many � (question mark) symbols in your terminal?  Or does something else appear on your end?

ADB doesn't seem to be best about Unicode handling, so I wonder if that is related here.

Comment 9

[meir_anolick]

(In reply to J. Ryan Stinnett [:jryans] (use ni?) from comment #8)
> Hmm, that's very interesting.
> 
> So, the Firefox socket does appear in list, which is good to see.
> 
> I wonder if the various Unicode characters here are confusing things.
> 
> When you run `adb shell cat /proc/net/unix`, are lines like
> @mnld_main_socket really followed by many � (question mark) symbols in your
> terminal?  Or does something else appear on your end?
> 
> ADB doesn't seem to be best about Unicode handling, so I wonder if that is
> related here.

I actually didn't notice those before I uploaded it. I had to open it in Notepad++ to see all those characters show up as NUL characters. In both notepad and the command prompt it just shows up as a bunch of empty spaces.

Admittedly I don't know what I'm looking at in this file. Since this is a Chinese phone, could those be Chinese characters and that's what's causing the problem? Is there anything that can be done about it?

Comment 10

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

(In reply to meir_anolick from comment #9)
> Admittedly I don't know what I'm looking at in this file. Since this is a
> Chinese phone, could those be Chinese characters and that's what's causing
> the problem? Is there anything that can be done about it?

I would like to help more here, but I'll have to think about the best way to proceed...

Maybe it would be best for me to create a special build of ADB Helper add-on with extra logging, which you could then try out and report back?

What Firefox channel do you use usually?  Release, Beta, Dev. Edition, or Nightly?

Comment 11

[meir_anolick]

I have no clue the best way to proceed. I'm out of my league in this area.
I use the WebIDE and all other developer tools exclusively from Dev. Edition.

Comment 12

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

Attachment: ADB Helper with Logging for Windows

Let's try the following steps.  You'll need to flip some prefs to allow this test add-on since it's not signed like Firefox expects for an official version.

1. Go to about:config
2. Set `xpinstall.signatures.required` to `false`
3. Set `extensions.legacy.enabled` to `true`
4. Download the test add-on attached to this bug
5. Open about:addons (Add-on Manager) and drop the the add-on file on the window, and agree to install in the popup
6. Open the Browser Console[1] (Tools menu -> Web Developer -> Browser Console)
7. Start Firefox on phone, connect phone via USB to computer
8. Open WebIDE

After all this, various logs should appear in the Browser Console window prefixed with "ADB Helper:".  Please copy these lines and attach them to this bug.

[1]: https://developer.mozilla.org/en-US/docs/Tools/Browser_Console

Comment 13

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

(I assumed from comment 0 that you are running Windows.  If you are on a different desktop OS, let me know so I can attach a different file.)

Comment 14

[meir_anolick]

Attachment: adb helper output.txt

Yes, I'm running Windows 10. Attached is the console output from ADB helper.

Comment 15

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

Interesting, that's not quite what I expected!  It seems to me that ADB isn't finding the device at all.

What version of Android is on the device?

It looks like this log used the external ADB server that was started by installing ADB (like I requested earlier in this bug).  Let's try forcing the add-on to use the copy of ADB that it has built in, which I think is also a newer version.

In your terminal where you've been running manual ADB commands, run `adb kill-server` so it stops its own server for now.

Then, try again with the steps in comment 12.  We should get different output that shows the ADB in the add-on was used.

Comment 16

[meir_anolick]

Android version is 6.0

I tried it again but got the same result. Maybe I did something wrong? I ran `adb kill-server` first and followed the instructions again.

Comment 17

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

Hmm.  Unfortunately, I am not sure what else to suggest for now.  

Maybe it's something related to the USB drivers for ADB?  But you are able to see in the terminal version of ADB...

Comment 18

[Julian Descottes [:jdescottes]]

WebIDE was completely removed in Bug 1539462 (Firefox 71). Closing all the bugs remaining in the component.