[zffos1.1][FOTA] Package should NOT be downloaded in 2G network.

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
5 years ago
7 months ago

People

(Reporter: hlu, Assigned: zhang.baisheng)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
Created attachment 812958 [details]
FOTA_2G_logcat.txt

* Build Info (Both Gecko and Gaia)
Gaia:     e089ed6095489f3ffd1a891bab70619ab3316c20
Gecko:    
BuildID   20130621133927
Version   18.0

* Reproduce Steps
1. Turn off WiFi and turn on data connection.
2. Settings->Cellular & Data->Network operator->Network type, switch the type to 2G only.
3. Perform Check now in Settings/Device information
4. Pull the notification down and select to download System update only.

* Actual results:
1. The package could be downloaded via 2G network.

* Expected results:
1. The package should NOT be downloaded in 2G network. Since the 2G data connection speed is very slow and user will not receive the phone call during downloading.
(Reporter)

Updated

5 years ago
Assignee: nobody → zhang.baisheng
Blocks: 899451
Whiteboard: POVB
Did you confirm that this doesn't reproduce on a non-vendor build? That will confirm if this is POVB. Removing until we confirm this.
Flags: needinfo?(hlu)
Whiteboard: POVB
(Reporter)

Updated

5 years ago
Flags: needinfo?(hlu)
Summary: [zffos 1.1][FOTA] Package should NOT be downloaded in 2G network. → [zffos1.1][FOTA] Package should NOT be downloaded in 2G network.
(Reporter)

Comment 2

5 years ago
Hi Jason,
    Thanks for your remind. I have discussed with Ivan_Tasy, Engineering Project Manager , and we are support ZTE to verify partner build and will add "POVB" firstly if we can't identify the issue owner. If we know the issue should be handled by Mozilla, we will not add POVB.
(In reply to hlu from comment #2)
> Hi Jason,
>     Thanks for your remind. I have discussed with Ivan_Tasy, Engineering
> Project Manager , and we are support ZTE to verify partner build and will
> add "POVB" firstly if we can't identify the issue owner. If we know the
> issue should be handled by Mozilla, we will not add POVB.

Shouldn't you do the opposite here? It doesn't exactly look good when we go to a partner complaining about a bug that we end up finding out is our end. Something like this should be easy enough to figure out on our end by using a reference server, potentially only OTA if that's only workflow possible, and see what happens. Ask Askeing if he has a path to testing OTA or FOTA on our side without relying on a partner workflow. If that's the case, verify first what happens in our side. That can help give you an indicator if it's our codebase or not.
(Reporter)

Updated

5 years ago
blocking-b2g: --- → 1.3?
Not a blocker for 1.3 - this problem has been present on multiple releases, so this won't block
blocking-b2g: 1.3? → ---

Comment 5

7 months ago
Firefox OS is not being worked on
Status: NEW → RESOLVED
Last Resolved: 7 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.