Closed
Bug 1116102
Opened 10 years ago
Closed 10 years ago
[FFOS2.0][Woodduck][wap][provison]the old APN is not overwritten by a new one which has the same name
Categories
(Firefox OS Graveyard :: Gaia, defect, P2)
Firefox OS Graveyard
Gaia
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: sync-1, Unassigned)
References
Details
DEFECT DESCRIPTION:
the old APN is not overwritten by a new one which has the same name.
REPRODUCING PROCEDURES:
send a provision message to MS, which include the same name APN with the preconfigered one APN.
like: when I insert a CMCC card to MS. then send a provison message which include a APN and the APN name is "CMNET" to MS.--KO
>the new one does not overwritte the old one.
EXPECTED BEHAVIOUR:
the new same name APN should overeritte the old one.
ASSOCIATE SPECIFICATION:
TEST PLAN REFERENCE:
TOOLS AND PLATFORMS USED:
USER IMPACT:
REPRODUCING RATE:
For FT PR, Please list reference mobile's behavior:
tel:0752+2639639
Comment 1•10 years ago
|
||
Hi Shawn,
I wonder is this by design?
Blocks: Woodduck, Woodduck_P2
Flags: needinfo?(sku)
Comment 3•10 years ago
|
||
I will claim this is by-design. But, more check is needed to see how Gaia get those values from db.
Comment 4•10 years ago
|
||
per issue review meeting:
1. this is a need for APN modification triggered from base station side, not from end user.
2. need related OMA spec. reference from partner for checking.
Comment 5•10 years ago
|
||
Per comment 4, please help provide OMA spec. for this requirement.
Flags: needinfo?(sync-1)
(In reply to comment #5)
> Comment from Mozilla:Per comment 4, please help provide OMA spec. for this
> requirement.
Comment From VAL:
1)安卓上如果当前配置信息的APN名称与已存在的APN一样,安装后是会覆盖的。
2)目前没有找到相关的协议规定说明如果名称一样,新安装的APN要覆盖已存在的APN。
3)但是从用户的角度看,如果存在两个名称一样的APN,会引起用户疑惑,无法区分要使用哪个APN,这样用户体验不是很好。
Comment 7•10 years ago
|
||
Hi Reporter,
Since there is no spec for this issue. We will claim this is by-design.
Hi Gary,
Can we provide suggestion for customer to customize this? Thanks!
Flags: needinfo?(gchen)
Comment 8•10 years ago
|
||
(In reply to sync-1 from comment #6)
>
> Comment From VAL:
> 2)目前没有找到相关的协议规定说明如果名称一样,新安装的APN要覆盖已存在的APN。
Hi reporter:
Per issue review meeting yesterday w/ SWPM DengWei, he mentioned that he remembers there is such OMA spec. about related requirement, would you help double confirm w/ him? I guess there will be some clue in that part for everyone's reference. Thank you.
Comment 9•10 years ago
|
||
Unless there is a clear picture on spec., I don't think we should get this request done because APN name (which is not unique) could be modified by user them-self.
Reporter | ||
Comment 10•10 years ago
|
||
(In reply to comment #8)
> Comment from Mozilla:(In reply to sync-1 from comment #6)
> >
> > Comment From VAL:
> > 2)目前没有找到相关的协议规定说明如果名称一样,新安装的APN要覆盖已存在的APN。
> Hi reporter:
> Per issue review meeting yesterday w/ SWPM DengWei, he mentioned that he
> remembers there is such OMA spec. about related requirement, would you help
> double confirm w/ him? I guess there will be some clue in that part for
> everyone's reference. Thank you.
He also can't find any OMA spec. Thanks!
Reporter | ||
Comment 11•10 years ago
|
||
Could you just make it like Android?
Comment 12•10 years ago
|
||
Per comment 9/10,
Please downgrade the severity on 2.0m, we can check this feature in next version.
Flags: needinfo?(sku)
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(sync-1)
Flags: needinfo?(gchen)
Resolution: --- → WONTFIX
Reporter | ||
Comment 13•10 years ago
|
||
Dear Mozilla,
If we want to make it like Android, where is the main code I should take care? Could you give me some advice. Thanks!
You need to log in
before you can comment on or make changes to this bug.
Description
•