1113654 - [ZTE Open C] USB Tethering is unavailable

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: General, defect)

Description

[lenaing]

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:34.0) Gecko/20100101 Firefox/34.0
Build ID: 20141125180439

Steps to reproduce:

Plugged in as USB, activated USB tethering through Internet Sharing -> USB Tethering.


Actual results:

No new NIC available in devices list.


Expected results:

New NIC available and usable in devices list.

Additional Info, built from master :
Model : qcom
Software : Boot2Gecko 2.2.0.0-prerelease
Build Number : eng..20140806.064432
Build Identifier : 20141218215855
Git Commit Info : 2014-12-18 20:01:18, 2650bae5

Comment 1

[Dud]

Hi

I'm facing the exact same issue under B2G 2.1.0.0-prerelease (latest commit : 2015-01-09, 64db236b).

dmesg on my host :
[32214.893305] usb 2-1.2: new high-speed USB device number 34 using ehci-pci
[32214.989030] usb 2-1.2: New USB device found, idVendor=19d2, idProduct=1350
[32214.989036] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[32214.989039] usb 2-1.2: Product: Android
[32214.989042] usb 2-1.2: Manufacturer: Android
[32214.989045] usb 2-1.2: SerialNumber: a14ee6
[32214.991104] usb-storage 2-1.2:1.3: USB Mass Storage device detected
[32214.991449] scsi30 : usb-storage 2-1.2:1.3
[32215.999986] scsi 30:0:0:0: Direct-Access     Linux    File-CD Gadget   0000 PQ: 0 ANSI: 2
[32216.000730] scsi 30:0:0:1: Direct-Access     Linux    File-CD Gadget   0000 PQ: 0 ANSI: 2
[32216.001392] sd 30:0:0:0: Attached scsi generic sg3 type 0
[32216.001902] sd 30:0:0:1: Attached scsi generic sg4 type 0
[32216.008260] sd 30:0:0:0: [sdc] Attached SCSI removable disk
[32216.009536] sd 30:0:0:1: [sdd] Attached SCSI removable disk


dud

Comment 2

[lenaing]

Hi,

I still have this issue, even with a new build from 2.2 master...

How can I help to debug this ?

Additionnal infos :
Model : qcom
Software : Boot2Gecko 2.2.0.0-prerelease
Build number : eng..20140806.064432
Build identifier : 20150412180546
Git commit info : 2015-04-10 21:41:12, cec00d64

Comment 3

[lenaing]

I also have this issue with the following configuration (other physical device) :

Phone : ZTE Open C (French, Darty (Previous were from Leclerc))
Model : qcom
Software : Boot2Gecko 2.2.0.0-prerelease
Build number : eng..20140806.064432
Platform Version : 37.0
Build identifier : 20150315100612
Git commit info : 2015-03-13 04:36:44, 4aefc3f6

Comment 4

[lenaing]

Got this via ADB :

W/GeckoConsole(  287): [JavaScript Error: "NS_ERROR_FAILURE: Failure arg 1 [nsINetworkService.enableUsbRndis]" {file: "jar:file:///system/b2g/omni.ja!/components/NetworkManager.js" line: 1012}]

The failure seems to occur in NetworkManager.js :

963   handleUSBTetheringToggle: function(enable) {
[...]
1012    gNetworkService.enableUsbRndis(true, this.enableUsbRndisResult.bind(this));

Call stack :

SettingsRequestManager.finalizeSets/<@resource://gre/modules/SettingsRequestManager.jsm:582:8
SettingsRequestManager.sendSettingsChange@resource://gre/modules/SettingsRequestManager.jsm:872:4
NetworkManager.prototype.observe@jar:file:///system/b2g/omni.ja!/components/NetworkManager.js:226:8
NetworkManager.prototype.handle@jar:file:///system/b2g/omni.ja!/components/NetworkManager.js:810:12
NetworkManager.prototype.handleLastUsbTetheringRequest@jar:file:///system/b2g/omni.ja!/components/NetworkManager.js:866:4
NetworkManager.prototype.handleUSBTetheringToggle@jar:file:///system/b2g/omni.ja!/components/NetworkManager.js:1012:4

Seems similar to https://bugzilla.mozilla.org/show_bug.cgi?id=1054191 , should I reopen it ?

Phone : ZTE Open C (French, Leclerc)
Model : qcom
Software : Boot2Gecko 2.2.0.0-prerelease
Build number : eng..20140806.064432
Platform Version : 37.0
Build identifier : 20150412180546
Git commit info : 2015-04-10 21:41:12, cec00d64

Comment 5

[comicbuchleser]

same here with my htc open c (eu version). tethering isn't working in the builds 2.1 and 2.2 from builds.firefoxos.mozfr.org/doc/en/devices/zte-open-c-eu
in the nightly version from 31.5.2015 it worked, but there my sim-card wasnt recognized (but the tethering connection with the pc was initiated).
can i help with anything to resolve the issue?

Comment 6

[u535950]

Hello,

I'm affected by the same issue on my ZTE Open C FR. USB Tethering works with FFOS ZTE build. Moreover, it works correctly with these gecko/gaia builds : 1.4, 2.0, and 3.0 (despite the fact that SIM is not detected anymore with this version).

So, only 2.1 and 2.2 gecko/gaia builds is problematical.

Comment 7

[u535950]

Attachment: Change the uuid of nsIEnableUsbRndisCallback

According to the bug 1054191 comment 2, I modified the UUID of nsIEnableUsbRndisCallback, rebuit, and now it works for me (tested on builds 2.1 and 2.2) !!!

Comment 8

[:gerard-majax]

Hsin-Yi, Jessica, maybe we should fix the UUID then ?

Comment 9

[Jessica Jong [:jessica] (inactive)]

(In reply to Alexandre LISSY :gerard-majax from comment #8)
> Hsin-Yi, Jessica, maybe we should fix the UUID then ?

According to bug 1054191 comment 11, the root cause in in hwcomposer (hardware/qcom/display) which corrupts the IID hash table.
Are we able to update hwcomposer revision so that it includes the fix on upstream?
I am fine with updating nsIEnableUsbRndisCallback UUID, I am just worried there would be other component affected afterwards.

Comment 10

[Hsin-Yi Tsai (she/her) [:hsinyi]]

(In reply to Jessica Jong [:jjong] [:jessica] from comment #9)
> (In reply to Alexandre LISSY :gerard-majax from comment #8)
> > Hsin-Yi, Jessica, maybe we should fix the UUID then ?
> 
> According to bug 1054191 comment 11, the root cause in in hwcomposer
> (hardware/qcom/display) which corrupts the IID hash table.
> Are we able to update hwcomposer revision so that it includes the fix on
> upstream?
> I am fine with updating nsIEnableUsbRndisCallback UUID, I am just worried
> there would be other component affected afterwards.

I am with Jessica for this. This quick workaround is okay for me, but I am concerned that we don't touch the real cause that leads to this issue appearing time to time.

Comment 11

[Hsin-Yi Tsai (she/her) [:hsinyi]]

(In reply to Hsin-Yi Tsai [:hsinyi] from comment #10)
> (In reply to Jessica Jong [:jjong] [:jessica] from comment #9)
> > (In reply to Alexandre LISSY :gerard-majax from comment #8)
> > > Hsin-Yi, Jessica, maybe we should fix the UUID then ?
> > 
> > According to bug 1054191 comment 11, the root cause in in hwcomposer
> > (hardware/qcom/display) which corrupts the IID hash table.
> > Are we able to update hwcomposer revision so that it includes the fix on
> > upstream?
> > I am fine with updating nsIEnableUsbRndisCallback UUID, I am just worried
> > there would be other component affected afterwards.
> 
> I am with Jessica for this. This quick workaround is okay for me, but I am
> concerned that we don't touch the real cause that leads to this issue
> appearing time to time.

Already commented. Clearing NI for now, feel free to pin me if more support needed from my side!

Comment 12

[Jessica Jong [:jessica] (inactive)]

Canceling NI for now, same as comment 11.

Comment 13

[BMO Automation]

Firefox OS is not being worked on