1139811 - [Cost Control] The device can't pop up the warn box when the data usage exceeds limit value.

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia::Cost Control, defect)

Description

[Lance（leave from Mozilla）]

Attachment: logcat_1403.txt

[1.Description]:
[Nexus 5 v2.2][Cost Control]After the data usage on device exceeds the limit value, device can't pop up warn box.
Found time:14:03
See attachment:1403.mp4 and logcat_1403.txt

[2.Testing Steps]: 
Prerequisite: You have inserted SIM cards.
1.Drop down the Notification, tap Data module shows area.
2.Tap "Next" -> "Next", turn on "Date yse alert".
3.Set the a value(ex: 0.1MB), then tap "Let's go".
4.Back to Home, launch Browser, and view some web pages.

Note:This bug only exist in first use Uage limit. If you reset the mobile data, when the data more than limit, device will pop up warn.

[3.Expected Result]: 
4.After the data more than limit value, device should pop up warn box immediately.

[4.Actual Result]: 
4.After the data more than limit value, device can't pop up the warn box.

[5.Reproduction build]: 
Nexus 5_2.2 version:
Build ID               20150304002529
Gaia Revision          8b4b3e4b7e7c308764f71542437fd60625ac6b75
Gaia Date              2015-03-03 15:01:17
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/2cb52b7cda5a
Gecko Version          37.0
Device Name            hammerhead
Firmware(Release)      5.0
Firmware(Incremental)  eng.cltbld.20150304.041943
Firmware Date          Wed Mar  4 04:19:58 EST 2015
Bootloader             HHZ12d

Nexus 5_3.0 version:

Build ID               20150304160447

Gaia Revision          eff3321ab4e65da3f906688ebb55ddf1e93d9452

Gaia Date              2015-03-04 17:42:47

Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/56492f7244a9

Gecko Version          39.0a1

Device Name            hammerhead

Firmware(Release)      5.0

Firmware(Incremental)  eng.cltbld.20150304.192817

Firmware Date          Wed Mar  4 19:28:34 EST 2015

Bootloader             HHZ12d

Flame 2.2 version:
Build ID               20150304002529
Gaia Revision          8b4b3e4b7e7c308764f71542437fd60625ac6b75
Gaia Date              2015-03-03 15:01:17
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/2cb52b7cda5a
Gecko Version          37.0
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150304.042036
Firmware Date          Wed Mar  4 04:20:47 EST 2015
Bootloader             L1TC000118D0

Flame 3.0 version:
Build ID               20150304010324
Gaia Revision          3fc0ac309f5fb0c1fe82c12223b955a4efce27e6
Gaia Date              2015-03-03 21:58:43
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/c5b90c003be8
Gecko Version          39.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150304.041952
Firmware Date          Wed Mar  4 04:20:03 EST 2015
Bootloader             L1TC000118D0

[6.Reproduction Frequency]: 
Always Recurrence,5/5

[7.TCID]: 
Free Test

[8. Note]
The bug does not exist in Flame 2.2.

Comment 1

[Lance（leave from Mozilla）]

Attachment: 1403.MP4

Comment 2

[Marina Rodríguez [:mai]]

Hi,
   I can see the following error on the logs: 

    Content JS ERROR: Error, when trying to addAlarm to the interfaceId: 898600402210090132 and limit: 100000 

    03-05 14:02:39.208 E/Usage   ( 2971):     at error (app://costcontrol.gaiamobile.org/gaia_build_defer_message_handler.js:3:0)

  In my experince testing the App, this error is produced when you try to put an alarm when the traffic limit is exceeded. I don't know if the root of the problem could be in the initialization of the network inteface (https://bugzilla.mozilla.org/show_bug.cgi?id=1117454#c26) or in the residual traffic (Bug 1083680 - [Usage][Cost Control] (Follow up to fix root cause) Noticeable difference between by application breakdown totals and the total displayed in chart and widget).

Ethan, would you mind taking a look to this bug?

Comment 3

[Ethan Tseng [:ethan]]

(In reply to Marina Rodríguez [:mai] from comment #2)
> Ethan, would you mind taking a look to this bug?

I would be glad to help.
But Albert is quite familiar with NetworkStats alarm code, maybe he can identify the root cause quickly.

Albert, could you take a quick look at this bug?
If you don't have time for now, or the root cause is not so trivial to be found, I'll come back to look into it.

Comment 4

[Albert [:albert]]

Only affects nexus 5?

Comment 5

[Lance（leave from Mozilla）]

This bug still exist on Nexus 5_2.2, but it can't be found on latest Flame 2.1, 2.2, 3.0 and Nexus 5_3.0.

Steps:
Prerequisite: You have inserted SIM cards(ex:CMCC).
1.Drop down the Notification, tap Data module shows area.
2.Tap "Next" -> "Next", turn on "Date yse alert".
3.Set the a value(ex: 0.1MB), then tap "Let's go".
4.Back to Home, launch Browser, and view some web pages.

Note:This bug only exist in first use Uage limit. If you reset the mobile data, when the data more than limit, device will pop up warn.

Expected Result: 
4.After the data more than limit value, device should pop up warn box immediately.

Actual Result: 
Nexus 5_2.2: 4.After the data more than limit value, device can't pop up the warn box.
Other device: 4.After the data more than limit value, device will pop up warn box immediately.

Fail rate: 3/5

================ Build Information (Issue could be found on this build) ================
Nexus 5_2.2 version:
Build ID               20150309162503
Gaia Revision          166491b92278dc9e648f8d49ab02d9ca00d74421
Gaia Date              2015-03-06 18:26:27
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/9ae4bcc9b5f2
Gecko Version          37.0
Device Name            hammerhead
Firmware(Release)      5.0
Firmware(Incremental)  eng.cltbld.20150309.195940
Firmware Date          Mon Mar  9 19:59:53 EDT 2015
Bootloader             HHZ12d

==================== Build Information (Without this issue) ====================
Flame 2.1 version:
Build ID               20150309001219
Gaia Revision          ea97a87048a4c1e2a479bbea1d75e0a182b2c4c9
Gaia Date              2015-03-05 16:30:05
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/0443f2e951dc
Gecko Version          34.0
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150309.040008
Firmware Date          Mon Mar  9 04:00:19 EDT 2015
Bootloader             L1TC000118D0

Flame 2.2 version:
Build ID               20150309002506
Gaia Revision          166491b92278dc9e648f8d49ab02d9ca00d74421
Gaia Date              2015-03-06 18:26:27
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/91b7aa6a3243
Gecko Version          37.0
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150309.040114
Firmware Date          Mon Mar  9 04:01:25 EDT 2015
Bootloader             L1TC000118D0

Flame 3.0 version:
Build ID               20150309160227
Gaia Revision          4ef1fa9b2870499fc9c77cac4a15f62e12a3ad2c
Gaia Date              2015-03-09 02:53:49
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/23f1f0369df5
Gecko Version          39.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150309.192301
Firmware Date          Mon Mar  9 19:23:12 EDT 2015
Bootloader             L1TC000118D0

Nexus 5_3.0 version:
Build ID               20150309160227
Gaia Revision          4ef1fa9b2870499fc9c77cac4a15f62e12a3ad2c
Gaia Date              2015-03-09 02:53:49
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/23f1f0369df5
Gecko Version          39.0a1
Device Name            hammerhead
Firmware(Release)      5.0
Firmware(Incremental)  eng.cltbld.20150309.193257
Firmware Date          Mon Mar  9 19:33:14 EDT 2015
Bootloader             HHZ12d

Comment 6

[Ethan Tseng [:ethan]]

Albert doesn't have a Nexus 5 in hand, and cannot reproduce this bug on Flame.
I'll try to reproduce it on Nexus 5 v2.2.

Comment 7

[Ethan Tseng [:ethan]]

Attachment: 20150318_nexus5L_costcontrolapp.png

Comment 8

[Ethan Tseng [:ethan]]

Attachment: 20150318_nexus5L_notification.png

Comment 9

[Ethan Tseng [:ethan]]

I followed the reproduction steps in comment 5 and attachment 8573144 [details] on Nexus-5-L v2.2. But I cannot reproduce this bug either.

===== Build Info =====
Gaia-Rev        306772a58335ac4cad285d27c3805090a8cc6886
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/83251e534b33
Build-ID        20150317162504
Version         37.0
Device-Name     hammerhead
FW-Release      5.0
FW-Incremental  eng.cltbld.20150317.195033
FW-Date         Tue Mar 17 19:50:47 EDT 2015
Bootloader      HHZ11k

As attachment 8579260 [details] shows, the notification of exceeding data limit appears as expected, and I saw the warning pop-up as well (but it flashed quickly that I couldn't capture it by screenshot).

Lance, what if you adjust the data limit to a higher value, such as 10MB? Would you still encounter this issue?
I say this because I think 0.1MB is not a practical setting in real use cases. If this issue only occurs in such corner case, I suggest we could ignore it.

Comment 10

[Lance（leave from Mozilla）]

When you set the limit to a value higher than 1M, device will pop up warn. But when we set to 0.1MB, sometimes, it will pop up, and sometimes, it will not. And this bug only exists when we use Usage app for the first time.

Comment 11

[Albert [:albert]]

(In reply to Lance from comment #10)
> When you set the limit to a value higher than 1M, device will pop up warn.
> But when we set to 0.1MB, sometimes, it will pop up, and sometimes, it will
> not. And this bug only exists when we use Usage app for the first time.

Usually there is some traffic when turning on the mobile data, maybe the threshold is lower than the current traffic and for that reason the warning is not shown. You can check internal counters with the command 'adb shell cat /proc/net/dev'.

Can you try to run that command and then set the alarm? add the output when the warning is not shown and what is the threshold.

Comment 12

[Lance（leave from Mozilla）]

(In reply to Albert [:albert] from comment #11)
> (In reply to Lance from comment #10)
> > When you set the limit to a value higher than 1M, device will pop up warn.
> > But when we set to 0.1MB, sometimes, it will pop up, and sometimes, it will
> > not. And this bug only exists when we use Usage app for the first time.
> 
> Usually there is some traffic when turning on the mobile data, maybe the
> threshold is lower than the current traffic and for that reason the warning
> is not shown. You can check internal counters with the command 'adb shell
> cat /proc/net/dev'.
> 
> Can you try to run that command and then set the alarm? add the output when
> the warning is not shown and what is the threshold.

Hi Albert,

I have reprodeuce this bug on latest Nexus 5-2.2.

Steps:
Prerequisite: You have inserted SIM cards(ex:CU).
1.Drop down the Notification, tap Data module shows area.
2.Tap "Next" -> "Next", turn on "Date yse alert".
3.Set the a value(ex: 0.1MB), then tap "Let's go".
4.Back to Home, launch Browser, and view some web pages.

Expected Result: 
4.After the data more than limit value, device should pop up warn box immediately.

Actual Result: 
4.After the data more than limit value, device can't pop up the warn box.

Fail rate: 1/8
Found time:16:22
See attachment:100KB.txt, 2015-03-20-16-22-58.png, logcat_1622.txt and 2015-03-20-16-24-21.png(We continue to surf the internet)

Nexus 5_2.2 version:
Build ID               20150319002500
Gaia Revision          9043c11f699c15bb6072422d1dad6518d1b5ddda
Gaia Date              2015-03-19 01:40:44
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/c0442d170bec
Gecko Version          37.0
Device Name            hammerhead
Firmware(Release)      5.0
Firmware(Incremental)  eng.cltbld.20150319.042430
Firmware Date          Thu Mar 19 04:24:46 EDT 2015
Bootloader             HHZ12d

Comment 13

[Lance（leave from Mozilla）]

Attachment: 100KB.txt

Comment 14

[Lance（leave from Mozilla）]

Attachment: 2015-03-20-16-22-58.png

Comment 15

[Lance（leave from Mozilla）]

Attachment: 2015-03-20-16-24-21.png

Comment 16

[Lance（leave from Mozilla）]

Attachment: logcat_1622.txt

Comment 17

[Albert [:albert]]

Attachment: Enable debug for NetworkStats API

Comment 18

[Albert [:albert]]

The patch enables logs for network stats API in order to be able to see what is happening. Please, make a build with the patch and provide the logcat output.

Comment 19

[Lance（leave from Mozilla）]

(In reply to Albert [:albert] from comment #18)
> The patch enables logs for network stats API in order to be able to see what
> is happening. Please, make a build with the patch and provide the logcat
> output.

Hi Albert,

I have reproduced this bug in Image with patch from Comment17.

Steps:
Prerequisite: You have inserted SIM cards(ex:CMCC).
1.Drop down the Notification, tap Data module shows area.
2.Tap "Next" -> "Next", turn on "Date yse alert".
3.Set the a value(ex: 0.1MB), then tap "Let's go".
4.Back to Home, launch Browser, and view some web pages.

Expected Result: 
4.After the data more than limit value, device should pop up warn box immediately.

Actual Result: 
4.After the data more than limit value, device can't pop up the warn box.

Fail rate: 1/80
Found time:17:16
See attachment:2015-03-25-17-16-25.png, 2015-03-25-17-16-42.png and logcat_1716.txt

Build ID               20150324235316
Gaia Revision          d225db9622d6e308af02880f43628dcf2f3f9bbe
Gaia Date              2015-03-25 01:37:45
Gecko Revision         n/a
Gecko Version          37.0
Device Name            hammerhead
Firmware(Release)      5.0
Firmware(Incremental)  eng.rose64.20150323.231521
Firmware Date          Mon Mar 23 23:16:05 EDT 2015
Bootloader             HHZ12d

Comment 20

[Lance（leave from Mozilla）]

Attachment: 2015-03-25-17-16-25.png

Comment 21

[Lance（leave from Mozilla）]

Attachment: 2015-03-25-17-16-42.png

Comment 22

[Lance（leave from Mozilla）]

Attachment: logcat_1716.txt

Comment 23

[Ethan Tseng [:ethan]]

(In reply to Lance from comment #19)
> Steps:
> Prerequisite: You have inserted SIM cards(ex:CMCC).
> 1.Drop down the Notification, tap Data module shows area.
> 2.Tap "Next" -> "Next", turn on "Date yse alert".
> 3.Set the a value(ex: 0.1MB), then tap "Let's go".
> 4.Back to Home, launch Browser, and view some web pages.
> Expected Result: 
> 4.After the data more than limit value, device should pop up warn box
> immediately.
> Actual Result: 
> 4.After the data more than limit value, device can't pop up the warn box.

Hi Lance,
A suggestion for you.
If the steps to reproduce are the same, I suggest you don't have to paste them again and again. Just say "STR as comment 0" would be clear enough.

Comment 24

[Ethan Tseng [:ethan]]

Attachment: adb.log

Okay. Thanks to Albert's advice offline, I can reproduce this bug on Flame.
This is an issue in Cost Control app, rather than a Nexus-5-specific bug. It can be easily reproduced by raising the alarm threshold.

STR is almost the same:
1. Reset the whole phone (such as flashing an image to it).
2. Enable data network and disable Wi-Fi.
3. Open the browser to navigate Web and make sure data consumption is at least several MBs. (I played two to three videos on Youtube).
4. Launch Cost Control app for the first time.
5. Enable alert and set the threshold as 1MB.
6. Cost Control app shows the data consumption is 8.56MB;
   scroll down the screen to open the utility tray,
   and it says "Data Limit (1.00MB) / 8.56MB over limit".

We expect user should see a notification alarm in step 5, but it does not happen.

Line 631 of the attached log says:
I/Gecko   ( 5779): -*- NetworkStatsService: Alarm set to a threshold lower than current rx/tx bytes
It means NetworkStatsService invokes callback with InvalidStateError. This is the clue we could start to trace the issue.

Comment 25

[Albert [:albert]]

(In reply to Ethan Tseng [:ethan] from comment #24)
> Created attachment 8583740 [details]
> adb.log
> 
> Okay. Thanks to Albert's advice offline, I can reproduce this bug on Flame.
> This is an issue in Cost Control app, rather than a Nexus-5-specific bug. It
> can be easily reproduced by raising the alarm threshold.
> 
> STR is almost the same:
> 1. Reset the whole phone (such as flashing an image to it).
> 2. Enable data network and disable Wi-Fi.
> 3. Open the browser to navigate Web and make sure data consumption is at
> least several MBs. (I played two to three videos on Youtube).
> 4. Launch Cost Control app for the first time.
> 5. Enable alert and set the threshold as 1MB.
> 6. Cost Control app shows the data consumption is 8.56MB;
>    scroll down the screen to open the utility tray,
>    and it says "Data Limit (1.00MB) / 8.56MB over limit".
> 
> We expect user should see a notification alarm in step 5, but it does not
> happen.
> 
> Line 631 of the attached log says:
> I/Gecko   ( 5779): -*- NetworkStatsService: Alarm set to a threshold lower
> than current rx/tx bytes
> It means NetworkStatsService invokes callback with InvalidStateError. This
> is the clue we could start to trace the issue.

IMHO gecko's behaviour is the expected. We should clarify with the UX team what to do when the user sets an alarm to a threshold lower than the current traffic, from my point of view, at least gaia should manage the error coming from gecko and notify the user somehow.

Comment 26

[Ethan Tseng [:ethan]]

(In reply to Ethan Tseng [:ethan] from comment #24)
> STR is almost the same:
> 3. Open the browser to navigate Web and make sure data consumption is at
> least several MBs. (I played two to three videos on Youtube).
> 4. Launch Cost Control app for the first time.
> 5. Enable alert and set the threshold as 1MB.

I forgot to mention a critical difference between Lance's STR and mines.

Lance opens Cost Control app and enables alert first, and then starts to navigate network.
But I reversed these two steps.
Because the point is -- "the data consumption is already over the limit while setting the alert".

As Albert said in comment 11, little data consumption happens after data network is enabled.
If data consumed is already over 0.1MB before opening Cost Control app, then user will not see notification while setting the data limit as 0.1MB.

Comment 27

[Ethan Tseng [:ethan]]

After realizing the root cause of this bug, personally I think this is not a bug. Instead, it is an issue that maybe we could do something to improve user experience.

Juwei, could you provide your suggestion for this issue?

Comment 28

[Juwei Huang[:juwei]]

Hi,
In ux perspective I don't consider it as an issue since users will know the red hint on dashboard after they back from settings view and they would know the current data exceeds the limit.
However, notification can also be provided when users tap on "done" on settings view.

Comment 29

[Ethan Tseng [:ethan]]

(In reply to Juwei Huang from comment #28)
> In ux perspective I don't consider it as an issue since users will know the
> red hint on dashboard after they back from settings view and they would know
> the current data exceeds the limit.
> However, notification can also be provided when users tap on "done" on
> settings view.
Thank you, Juwei. :)

Hi Marina,

According to Albert's and Juwei's opinions (comment 25 and comment 28), could you add a pop-up notification if the data consumption is over limit when clicking the "Done" button in [Data user alert] settings page?

Comment 30

[Ethan Tseng [:ethan]]

Remove "[2.2-nexus-5-l]" from whiteboard since this is not a Nexus-5-specific issue (see comment 24).

Comment 31

[Marina Rodríguez [:mai]]

Hi Juwei,
What message do you think we should show to the users?

Regards

Comment 32

[GitHub Autolander Bot]

Attachment: [gaia] gitmai:bug-1139811-usage-check-data-limit-when-add-alarm-fails > mozilla-b2g:master

Comment 33

[Juwei Huang[:juwei]]

Hi Marina,
The message would be the same as ordinary notification: 
XX MB of data used.
You've reached the limit you selected.

Comment 34

[Salvador de la Puente González [:salva]]

Comment on attachment 8588543 [details] [review]
[gaia] gitmai:bug-1139811-usage-check-data-limit-when-add-alarm-fails > mozilla-b2g:master

Check the comments on GitHub and ask for my review again. Thank you Mai for taking care of this bug.

Comment 35

[Marina Rodríguez [:mai]]

Comment on attachment 8588543 [details] [review]
[gaia] gitmai:bug-1139811-usage-check-data-limit-when-add-alarm-fails > mozilla-b2g:master

Salva, 
would you mind to review the patch?
Regards,
Mai

Comment 36

[Salvador de la Puente González [:salva]]

Comment on attachment 8588543 [details] [review]
[gaia] gitmai:bug-1139811-usage-check-data-limit-when-add-alarm-fails > mozilla-b2g:master

See my comment on GitHub and you can merge. Thank you!

Comment 37

[Ryan VanderMeulen [:RyanVM]]

Master: https://github.com/mozilla-b2g/gaia/commit/79720f064f8e4a357bb67b6b9a6516e470535b0d

Comment 38

[sunny]

Attachment: 1757.3gp

**Case 1:According to STR as comment 0, this bug has been verified as pass on latest Nightly Nexus5 3.0, but it has been verified fail on latest Nightly Flame v3.0

See attachments: 1719.3gp
Flame 3.0 Reproduce rate: 3/10
Nexus5 3.0 Reproduce rate: 0/10
STR as comment 0

[Actual Result]: 
[Flame 3.0]4.When the data traffic you've used exceeds the limit value, device does not pop up the warn box.
[Nexus5 3.0]4.When the data traffic you've used exceeds the limit value, device pops up warn box immediately.

**Case 2:According to the STR of Comment 26,this bug has been verified as pass on latest Nightly Nexus5 3.0 and Flame v3.0
See attachments: 1757.3gp and logcat_1757.txt
Flame 3.0 Reproduce rate: 0/10
Nexus5 3.0 Reproduce rate: 0/10
[Actual Result]: 
4.When you tap done, device pops up warn box immediately.


Device: Flame 3.0 build(Case 1 Fail, Case 2 Pass)
Build ID               20150616010205
Gaia Revision          62ba52866f4e5ca9120dad5bfe62fc5df981dc39
Gaia Date              2015-06-15 19:09:24
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/ce863f9d8864
Gecko Version          41.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150616.060924
Firmware Date          Tue Jun 16 06:09:36 EDT 2015
Bootloader             L1TC000118D0

Device: Nexus5 3.0 build(Case 1 Pass, Case 2 Pass)
Build ID               20150616160206
Gaia Revision          9d42e94446f2dc01b519172b6d75d81d4d435bdc
Gaia Date              2015-06-16 16:16:47
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/27caa5299f9f
Gecko Version          41.0a1
Device Name            hammerhead
Firmware(Release)      5.1
Firmware(Incremental)  eng.cltbld.20150616.193221
Firmware Date          Tue Jun 16 19:32:40 EDT 2015
Bootloader             HHZ12f

Comment 39

[sunny]

Attachment: logcat_1757.txt

Comment 40

[sunny]

Attachment: 1719.3gp

Comment 41

[Norry.L.F(Leave from Mozilla)]

Hi Marina,

According to comment 38, this bug still can be repro on flame 3.0 using the STR on comment 0, could you have a look?  or should we file a new bug to track? 
Thanks :)

Comment 42

[Marina Rodríguez [:mai]]

Hi,
the error reported in this bug occurs when exist data mobile traffic before the FTE is launched. The STR followed on the video is different. Please, report a new bug with the video STR.

Regards,
Marina

Comment 43

[sunny]

According to comment 42, we file a new bug, link to bug 1175861

Comment 44

[sunny]

Attachment: 1427.3gp

According to your comment 42, I turn on the data mobile traffic before the FTE is launched, then retry the case 1 and case 2, and I can repro the issue in case 1. Actually, the result is same as comment 38(just exists on flame 3.0, the repro rate is 2/10), please see attachment : logcat_1427.txt and 1427.3gp.
Device: Flame 3.0 build(Case 1 Fail, Case 2 Pass)
Build ID               20150623010204
Gaia Revision          311c4e59936a407e64509f54fecb440d8a78e3c8
Gaia Date              2015-06-20 20:21:42
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/be81b8d6fae9
Gecko Version          41.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150623.043033
Firmware Date          Tue Jun 23 04:30:44 EDT 2015
Bootloader             L1TC000118D0

Comment 45

[sunny]

Attachment: logcat_1427.txt

Comment 46

[sunny]

Hi Marina, 
Could you help to check this issue again,thanks.