Closed Bug 959506 Opened 10 years ago Closed 10 years ago

To use a different APN for tethering forcibly, another network interface (e.g. rmnet1) is necessary.

Categories

(Firefox OS Graveyard :: RIL, defect)

Product:
Firefox OS Graveyard
Component:
RIL
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: da-yokota, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:26.0) Gecko/20100101 Firefox/26.0 (Beta/Release)
Build ID: 20131205075310

Steps to reproduce:

Android provide the feature that switch APN for tethering forcibly by [1].

[1]system/etc/customization/settings/com/android/settings/custom_settings.xml".
＜setting key="tether_dun_required" runtime="false"＞1＜/setting＞
＜setting key="tether_dun_apn" runtime="false"＞xxx.com,id,password,,,,＜/setting＞

I think Firefox OS should have this feature.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: To switch APN for tethering forcibly → To use a different APN for tethering forcibly, another network interface (e.g. rmnet1) is necessary.
Blocks: 960865
Here is our mechanism.
If users enter a DUP apn setting, that means tether_dun_required is true.
If users don't enter a DUP apn setting, that means tether_dun_required is false.
I think it is sufficient for the purpose of this bug. Close this bug. If you don't agree, please reopen it.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Hi Ken
We know that it's been implemented on 1.4 by Jesicca.
as you know, we have discussed that at last month at Tokyo.
However, I have missed to close this bug.

Thanks Ken!
You need to log in before you can comment on or make changes to this bug.