1039141 - [FFOS V 1.4] fail to show the APN setting inside Tethering & IMS

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Settings, defect)

Description

[ting.yang]

[1.Hardware Version ]: 7715 Firefox/#1443
[2.Project Build    ]: FIREFOXOS_V1.4_W14.28.1_SP7715/sp7715ga_gonk4.4
[3.Network          ]: GSM
[4.Storage Card     ]: 4 GB
[5.SIM Card         ]: SIM1:-Robi, SIM2:- Teletalk
Test on :              SIM1:-Robi
[6.Testing Location ]: Static
[7.Testing Steps    ]:

a) Flash 7715Firefox with the latest version.
b) Open Cellular & Data Setting
c) Open Sim1.
d) Check Tethering & IMS setting.
e) No APN.

Comment 1

[ting.yang]

Attachment: 0-main-23-54-58.log

Comment 2

[ting.yang]

Check Tethering and IMS settings,no APN show in the mobile phone.There no type about Tethering and IMS apn in the apn.json.

Comment 3

[ting.yang]

HI peipei:
1)In the test operators，eg:Vodafone,there no type about "dun" and "ims" in the apn.json.
2)the setting about "dun" and "ims" is used for what??
3)Is it because operators do not support “dun” and "ims" settings ? If the operators do not support,can we remove the settings??
4)The Flame also can not show the Tethering & IMS setting APN.

Comment 4

[Rachelle Yang [:ryang][[e-mail]]]

Hi Arthur, Could you please kindly help with this? Thank you very much.

Comment 5

[Arthur Chen [:arthurcc][inactive after 6/30]]

Which operator you are using for testing? If the operators do support dun and ims but not listed on apn.json, we can consider to add the apn settings to apn.json. As for removing the settings when they are not supported, we should leave the decision to the UX designers.

Comment 6

[ting.yang]

HI Arthur:
1)The india tester use Vodafone and Airtel operator for test,DUT Shows APN name as Blank spaces " ".they want the tethering show the APN as "www" for the Vodafone and "airtelgprs.com" for the Airtel operator.
2)I would like to know the design intent of dun APN and what role it make in the phone??
thank you very much.

Comment 7

[ting.yang]

Hi Arthur:
In the Airtel operators,there no type about dun,but in the dun APN,it Shows APN name as "www".do the dun APN show mechanism have problem??
If you want more information,you can check sprd_bug327676.

Comment 8

[Arthur Chen [:arthurcc][inactive after 6/30]]

May I know the mcc and mnc number of the operator that you are using?

Comment 9

[ting.yang]

Hi Arthur:
there are three bugs related this issue,here is the india tester used the operator information.
1)In sprd_Bug 327676
 "operator":{"rilMessageType":"operatorchange","longName":"AirTel","shortName":"AirTel","mcc":"404","mnc":"10","rilMessageClientId":0}
2)In Sprd_Bug 327687
"operator":{"rilMessageType":"operatorchange","longName":"Vodafone","shortName":"Vodafone","mcc":"404","mnc":"11"},
3)In sprd_Bug 331522
"longName":"BGD AKTEL","shortName":"AKTEL","mcc":"470","mnc":"02"

Comment 10

[Peipei Cheng (needinfo if you need my action)]

Just checked with partner QA, Android has no such settings,tt does not distinguish between business types，they all use a APN.

Comment 11

[Arthur Chen [:arthurcc][inactive after 6/30]]

There are no default apn settings for the three operators in apn.json. To display the apn settings by default, we should consider to add the settings to apn.json. Please provide the apn settings then I can help write a patch.

Comment 12

[ting.yang]

Hi Arthur：
we have modify the apn.json according to the customer information，so in apn.json there are apn settings about the AIRTEL operator.but they just provide three types,without dun and ims.for example:
mcc:404,mnc:10  carrier         type
               AIRTEL MMS      mms
               AIRTEL LIVE     default
               Mobile Office   default,supl
you can just see the APN name in data,message and A_GPS settings.
so I think if the operator have no type about dun and ims,could you help remove the dun and ims settings in the gaia??

Comment 13

[Arthur Chen [:arthurcc][inactive after 6/30]]

This depends on the UX design, flagging Jenny for her opinion.

Comment 14

[Jenny Lee]

Hello, please take a look at the latest APN setting spec attachment 8450055 [details]. The APN setting is covered in cellular and data setting page. Thanks!

Comment 15

[ting.yang]

Hi Jenny:
   In the FFOS 1.4,It does not support the latest APN setting.When the operator do not support the dun and ims,we should remove the dun and ims settings in the gaia.
   Besides in the latest APN settings,It does not consider this situation either.When the operators do not support the dun and ims,it will show nothing in the tethering settings and ims settings.This may make the user and tester confused .
thank you!

Comment 16

[Wayne Chang [:wchang]]

According to comments this is the UX on 1.4. Change requests should be considered for upcoming releases but not 1.4 or 2.0.

Request: when certain apn types are not used by an operator, do not show such options.

Comment 17

[Jenny Lee]

(In reply to ting.yang from comment #15)

I think it is ok to not show APN names when there's no support for the certain service since there will always be a "add new APN" button on the page. It is clear that there's no APN to choose from and user can only add new APN if he wants use the service. Removing the option will also remove the function for user to add APN. Furthermore, operator may change service type anytime. If we remove the options that are not supported by operator now and the operator starts support the service in the future, we might not be able to add back the UI. Hope this makes sense, tks!

Comment 18

[ting.yang]

Hi Jenny:
   I do not mean to remove the ims and dun settings completely，It all depends on the operators,if the operators do not have the ims and dun type,then wo should not show the ims and dun settings.thank you.

Comment 19

[Jenny Lee]

(In reply to ting.yang from comment #18)
> Hi Jenny:
>    I do not mean to remove the ims and dun settings completely，It all
> depends on the operators,if the operators do not have the ims and dun
> type,then wo should not show the ims and dun settings.thank you.

Hello ting, as I mentioned in comment 17, we cannot "not show" the options, because if we remove the options that are not supported by operator now and the operator starts support the service in the future, we might not be able to add back the UI. Another case is that if user wants to use a second SIM card that does support ims and dun type later on, they won't be able to access the UI for the option either.
Thanks!

Comment 20

[Arthur Chen [:arthurcc][inactive after 6/30]]

Agree with Jenny. We should always provide the UI in case users would like to create an APN settings that is not listed in our apn database.

Comment 21

[ting.yang]

(In reply to Arthur Chen [:arthurcc] from comment #20)
> Agree with Jenny. We should always provide the UI in case users would like
> to create an APN settings that is not listed in our apn database.

Hi Arthur:
   In FFOS 1.4,It does not support the users to create an APN settings.The latest APN setting does not used in 1.4.to the FFOS 1.4 users,the ims and dun settings is a blank options，that will make confused,and I think which UI to be showed should depend on the operators, if operators have no type about the settings,we can hidden such options.if the operators have such type,we show such options.
Thank you very much.

Comment 22

[Arthur Chen [:arthurcc][inactive after 6/30]]

The thing is we cannot guarantee that the operators won't support the types in the future. If we hide the settings UI based on the current APN database, users won't be able to set the apn manually when the operators start to support the types.

Comment 23

[ting.yang]

(In reply to Arthur Chen [:arthurcc] from comment #22)
> The thing is we cannot guarantee that the operators won't support the types
> in the future. If we hide the settings UI based on the current APN database,
> users won't be able to set the apn manually when the operators start to
> support the types.

HI Artuhur:

1) I agreen with your opinion in comment 22 'If we hide the settings UI based on the current APN 
   database, users won't be able to set the apn manually when the operators start to support the 
   types.'it is a new feature in master.

2) But In FFOS 1.3 and 1.4,it does not support set the apn manually.

3) the operators do not support the ims and dun type,it shows blank space,that will make users
   confused.this is a bad user experience.

4) we advice that in the FFOS 1.3 and 1.4 we had better to show the dun and ims settings according to
  the supporting type of operators.  
  
thank you very much!

Comment 24

[Wayne Chang [:wchang]]

Ting,

Your comments will be considered by our UX team, thank you very much. However it is way past our the time for any UX change on 1.4 on our end.

Comment 25

[Jenny Lee]

Agree with Wayne. Thank you for your understanding!

Comment 26

[孟宪茂]

For the apn of india operators,we make sure they support tethering,and add the type "dun" to the related apns. But for the ims,these operators does not support ims,so it still leaves the black ims settings.
Thanks!

Comment 27

[BMO Automation]

Firefox OS is not being worked on