Firefox os v1.1 Mozilla build ID:20130902041201 DEFECT DESCRIPTION: Manual network selection interrupted by automatic network selection REPRODUCING PROCEDURES: The device is in auto network selection mode and is camped on a network. The user then goes to the settings menu and selects "manual network selection". The device then performs a network search and presents a list of found networks to the user. The user can then select on of the networks. If the current network is lost during this process the device automatically selects one of the other networks instead of leaving the choice to the user. If the user makes a different choice the device then selects that other network. This is not correct as the device must be set to manual network selection before the network search begins. This is standard and is implemented like this in all other devices. Customer Impact Statement: The device can select an unwanted network during the manual selection process which may interfere with steering of roaming and manual selection against steering. EXPECTED BEHAVIOUR: When the user enters manual network selection the UE must be set into manual network selection mode before starting to search for alternative networks to prevent auto network selection during the process if the current network is lost. Note for TEs: re-testing can be done easily with test case G1.3.6 as this scenario can be nicely reproduced. ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT:High REPRODUCING RATE:5/5 For FT PR, Please list reference mobile's behavior:

>> If the current network is lost during this process This sound like a corner case. do you have logs? is this gecko/gaia bug base on your analysis? thanks

Dear Joe, This bug is reported by operator parterner. I can't reproduce this in my office and I need contact the parterner for help. IMHO, it's bug of ril. And I will file a SR if I got the logs. Thanks for your quick reply!

Minus for now. Please re-nom if Mozilla needs to do anything. Seems like QC needs to fix the issue.

reopen because customer will provide log soon.

The log is from operator, please help to check, thank you!

Dear Joe, I found that gaia and gecko do nothing to switch the network select mode to manual after the user disable automatic select but only get available networks and shown to user. So the Manual network selection interrupted by automatic network selection. In other words, IMHO, we didn't implement the manual select mode at all. Can you find some one to check this? Thank you.

(In reply to xiaokang.chen from comment #6) > Dear Joe, > I found that gaia and gecko do nothing to switch the network select mode to > manual after the user disable automatic select but only get available > networks and shown to user. > So the Manual network selection interrupted by automatic network selection. > In other words, IMHO, we didn't implement the manual select mode at all. > Can you find some one to check this? Thank you. Can you help test this on 1.0.1 and see if this is reproducible there ?

Dears, We can reproduce this on v1.0.1

Dear All, After check the code of qualcomm, I found that RIL.cpp of qualcomm will send RIL_REQUEST_SET_NETWORK_SELECTION_MANUAL after the user select a specific network. So though the user disable the select automatic in UI interface, the network selection mode still be automatic before the user select a network list and connected successfully. Do you think it is normal??

(In reply to xiaokang.chen from comment #8) > Dears, > We can reproduce this on v1.0.1 Since this isn't a regression, it doesn't meet the criteria to block v1.1. I've made it a 1.2 blocker nomination.

(In reply to xiaokang.chen from comment #9) > Dear All, > After check the code of qualcomm, I found that RIL.cpp of qualcomm will send > RIL_REQUEST_SET_NETWORK_SELECTION_MANUAL after the user select a specific > network. So though the user disable the select automatic in UI interface, > the network selection mode still be automatic before the user select a > network list and connected successfully. > > Do you think it is normal?? needinfo vicamo

I'm afraid that's a limitation from Android RIL Parcel design. We have four parcels related to network selections: 1) REQUEST_QUERY_NETWORK_SELECTION_MODE 2) REQUEST_QUERY_AVAILABLE_NETWORKS 3) REQUEST_SET_NETWORK_SELECTION_AUTOMATIC: Set to automatic. No additional parameter needed/available. 4) REQUEST_SET_NETWORK_SELECTION_MANUAL: Set network selection mode to manual AND select the specified network. Take a string parameter, which is concatenation of the MCC and MNC of the selected network. Obviously this function depends on "whether can we select a <null> network" -- pass an empty string to REQUEST_SET_NETWORK_SELECTION_MANUAL. However, as we can see from AOSP source[1], they're doing the same thing. Load available networks, select one and call |mPhone.selectNetworkManually|. I guess there's no much room for us to address the expectation of this bug. [1]: https://android.googlesource.com/platform/packages/apps/Phone/+/android-4.0.4_r1.2/src/com/android/phone/NetworkSetting.java

Vicamo, How do we go about fixing this bug? Can't be fixed by Moz is what I read. Minus for now till Moz has an action to fix this.

Firefox OS is not being worked on