New issue
Advanced search Search tips

Issue 811003 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 811501
Owner:
Closed: Feb 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Phantom mobile network in the list of networks. Inconsistent network selection behavior.

Project Member Reported by alemate@chromium.org, Feb 10 2018

Issue description

Setup:

1) ToT chrome. OOBE, network selection screen.
2) Mobile dongle connected to the device.
3) Observe that mobile network is in the list of networks.
4) Disable mobile networks from the status tray menu.
Observe that mobile network disappeared from the list of OOBE networks.

5) Disable WiFi networks. Observe that WiFi networks disappeared from the screen, but last known mobile network came back (even though mobile network is disabled.).

6) Enable mobile connections from the status tray menu. Mobile network is still on the screen.

7) Connect to the mobile network from the status tray menu. OOBE network screen will not change even when mobile network is actually connected.

8) Clicking on the mobile network on the OOBE Network selection screen will bring "Network details" dialog. When you press "Connect" button in that dialog, WiFi networks will be unblocked (and will automatically connect to some WiFi network if it was known to shill before disabling WiFi).

I believe this is also true for M65.
 
chrome-phantom-Mobile-Network.jpg
2.4 MB View Download
Cc: benchan@chromium.org
This sounds related to issue 780443.

I can investigate some more to confirm and clarify the repros.

Labels: -Pri-1 M-66 Pri-2
I can not reproduce any of this as described.

Could you do the following:
1. Reboot
2. Reproduce the issue
3. Log in and file a feedback report

That will at least allow me to look at the device event logs to see if I can figure out what is going on there.

Also, can you clarify (8)? Did you enable WiFi at some point, or do you mean that connecting to a Cellular network is enabling WiFi?

There is full video in the  issue 811006 .
I think it requires mobile dongle to reproduce.
Re #2:
Video: https://drive.google.com/file/d/1hUXNSp_fID3KdTERLbItvf2-pTuVQxrO/view?usp=sharing
Feedback report: 85059053573
Not related to issue 780443.

I have addressed the "phantom Cellular network" in  issue 811501 .

Unfortunately the latest video is difficult to see and the feedback report does not show a wifi network connecting, it starts with a connected wifi network. Do you maybe have some about://flags set? That causes the browser to restart so we loose any events during login. (In fact, looking at network_event_log that does seem to be the case).

The only suspicious thing I see on the video is when the Cellular initializing (I think) UI appears at the same time as the WiFi network connects. It also looks like either:
a) Cellular modem initialization happened around the same time that the WiFi network connected (less likely if this occurred multiple times with different times before starting WiFi connect).
b) Shill is somehow not triggering or sending a Cellular device update until the WiFi state changes.
c) The UI is not receiving an update when the Cellular device becomes available. 
d) The UI was scrolled and then scrolled to the top when the WiFi network connected, showing the Cellular section.

(c) seems unlikely because the Cellular network shows up after the device does and I would expect them to show up at the same time if there was a missing notification.

So, from what I can tell:
* The "phantom network" issue is fixed as  issue 811501 
* I also don't see any sign of (8) in the second video
* The timing of the Cellular enable toggle showing up is suspicious but not necessarily a bug; I can not reproduce this.

Is there anything I am missing? Any more details you can provide?

Re #5: Unfortunately the latest video is difficult to see...

Focus becomes sharp at 1:17. I think all the details are visible.
Mergedinto: 811501
Status: Duplicate (was: Assigned)
I believe that everything here has been either resolved by one of the issues described in issue 811006#2 or in  issue 811501 .

Please re-open with specifics if I missed anything.

Sign in to add a comment