911652 - [wasabi] It took more than 1 minute to switch EVDO mode to CDMA mode

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Vendcom, defect)

Description

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

Attachment: adb_logat.log

Tested build: 20130830172300

Reproduce steps:
1. Start wasabi device
2. Go to settings to enable Data connection
3. Set Network Operator => Network type to "evdo" or "cdma/evdo"
   The signal bar will show 'EV'
4. Set Network Operator => Network type to "cdma"
   [issue] It will take over 1 minute for the signal bar to show '1X'

Comment 1

[Enpei]

This bug is tested under China Telecom.

Comment 2

[Enpei]

Build info:
Gaia:     15bdabeddd1b9356ff296a6550691c1427bf2589
  B-D     2013-08-30 16:14:54
Gecko:   c3e6d00ad8f63ed64ad334b55954da36b49d16d4
BuildID   20130830172300
Version   26.0a1

Comment 3

[Enpei]

Before device establishes 1x data call, the icon will still be "Ev" even it's in cdma only mode already.

Comment 4

[Ken Chang[:kenkai]]

Please provide the log with time stamp.(adb logcat -v time)

Comment 5

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

Attachment: 911652.log

The start time stamp is 09-25 17:23:59.777

Thanks!

Comment 6

[Preeti Raghunath(:Preeti)]

Aligning with 1.3 Sprint 3. Hence moved to 1.3?

Comment 7

[Jason Smith [:jsmith]]

(In reply to Preeti Raghunath(:Preeti) from comment #6)
> Aligning with 1.3 Sprint 3. Hence moved to 1.3?

I don't think that argues for this being moved to 1.3? - 1.3 sprints include fixing 1.2 blockers. That's at least what both functional teams I'm working with are doing from what I can tell.

Comment 8

[Enpei]

Hi Preeti,

Kevin use the target milestone just to represent the due date for this bug to be solved or clarified. So this is still a koi+ issue.

Thanks.

Comment 9

[Ken Chang[:kenkai]]

According to log.
//RIL receives a command selecting CDMA network.
09-25 17:24:35.765 I/Gecko   (  201): -*- RadioInterface[0]: 'ril.radio.preferredNetworkType' is now cdma
...
//About 991ms later, finding a CDMA network.
09-25 17:24:36.756 I/Gecko   (  201): RIL Worker[0]: signal strength: {"gsmSignalStrength":99,"gsmBitErrorRate":0,"cdmaDBM":64,"cdmaECIO":70,"evdoDBM":125,"
...
//About 308ms later, updating the network type and signal.
09-25 17:24:37.064 I/Gecko   (  201): -*- RILContentHelper: Received message 'RIL:VoiceInfoChanged': {"clientId":0,"data":{"connected":true,"emergencyCallsOnly":false,"roaming":false,"network":{"longName":"China Telecom","shortName":"China Telecom","mcc":"460","mnc":"03"},"cell":{"gsmLocationAreaCode":-1,"gsmCellId":-1,"cdmaBaseStationId":0,"cdmaBaseStationLatitude":0,"cdmaBaseStationLongitude":0,"cdmaSystemId":13824,"cdmaNetworkId":3},"type":"1xrtt","signalStrength":-64,"relSignalStrength":100,"state":"registered"}}
RIL only takes 1.299s to finish this action. 

Arthur, can you please provide comments for this bugs?

Comment 10

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

The system app listens to 'datachange' event of mozMobileConnection for updating the icon, is expected? Or we should listen to other events?

Comment 11

[Ken Chang[:kenkai]]

(In reply to Arthur Chen [:arthurcc] from comment #10)
> The system app listens to 'datachange' event of mozMobileConnection for
> updating the icon, is expected? Or we should listen to other events?
It is fine. 
Since 10ms later, the datachange was coming.
09-25 17:24:37.074 I/Gecko   (  690): -*- RILContentHelper: Received message 'RIL:DataInfoChanged': {"clientId":0,"data":{"connected":true,"emergencyCallsOnly":false,"roaming":false,"network":{"longName":"China Telecom","shortName":"China Telecom","mcc":"460","mnc":"03"},"cell"

Comment 12

[Francis Lee [:frlee]]

changed milestone tag, this is originally planned for v1.2, it needs to be fixed within v1.2 scope. according to triage result, change to koi+

Comment 13

[Ken Chang[:kenkai]]

(In reply to Ken Chang from comment #11)
However, modem change the network type after 1 minute and 24 seconds later.
It needs partner' help to check why the status change of data network is so long. 

09-25 17:26:59.536 I/Gecko   (  201): -*- RILContentHelper: Received message 'RIL:DataInfoChanged': {"clientId":0,"data":{"connected":true,"emergencyCallsOnly":false,"roaming":false,"network":{"longName":"China Telecom","shortName":"China Telecom","mcc":"460","mnc":"03"},"cell":{"gsmLocationAreaCode":-1,"gsmCellId":-1},"type":"1xrtt","signalStrength":null,"relSignalStrength":null,"state":"registered","apn":"ctnet"}}

Francis, could you please talk to partner?

Comment 14

[Enpei]

Hi Ken,

After Peipei’s great help running some tests, we found some crucial evidences that 932721 and 911652 may not be modem bug. I will update follow information on both bugs and remove POVB first. And please let us know any log you still need for further debugging.

1.	Bug 932721, 911652 Test step doesn’t include triggering data call after mode switch. But Android version has no such issue.
2.	Peipei run speed test after type changing and found that speed is correct but icon is wrong. (ex: after EVDO > CDMA, speed test is near 100k yet icon is EV)
3.	Both issues can be recovered by lock and unlock screen 10s after type switching. Doesn’t sound like still modem bug.

Comment 15

[Ken Chang[:kenkai]]

(In reply to Enpei from comment #14)
> Hi Ken,
> 
> After Peipei’s great help running some tests, we found some crucial
> evidences that 932721 and 911652 may not be modem bug. I will update follow
> information on both bugs and remove POVB first. And please let us know any
> log you still need for further debugging.
> 
> 1.	Bug 932721, 911652 Test step doesn’t include triggering data call after
> mode switch. But Android version has no such issue.
> 2.	Peipei run speed test after type changing and found that speed is correct
> but icon is wrong. (ex: after EVDO > CDMA, speed test is near 100k yet icon
> is EV)
> 3.	Both issues can be recovered by lock and unlock screen 10s after type
> switching. Doesn’t sound like still modem bug.
Interesting, can you provide a log?

Comment 16

[Ken Chang[:kenkai]]

(In reply to Ken Chang from comment #15)
Here are the reasons that I need log.
> > 1.	Bug 932721, 911652 Test step doesn’t include triggering data call after
> > mode switch. But Android version has no such issue.
Maybe, partner does a special mechanism for the network type recovery.
> > 2.	Peipei run speed test after type changing and found that speed is correct
> > but icon is wrong. (ex: after EVDO > CDMA, speed test is near 100k yet icon
> > is EV)
If modem is in EVDO network but it doesn't notify RIL, RIL won't know the network status updated.
> > 3.	Both issues can be recovered by lock and unlock screen 10s after type
> > switching. Doesn’t sound like still modem bug.
This kind of scenario will trigger RIL to issue a request to get current network status. I think RIL can get a real network type via this request.

So I need a log to make sure proceeding assumptions are true...:)

Comment 17

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

Attachment: adb logcat - 20131031

Steps:
1. Change mode from Automatic to CDMA
   Timestamp 10-31 16:20:10.732
   1x appears after about 1 minute
2. Change mode from CDMA to Automatic
   Time stamp 10-31 16:22:52.335
3. EV appears after about 50s. Change type from Automatic to CDMA again
   Time stamp: 10-31 16:23:49.928 
4. Wait for a while 1X does not appear. Lock screen
   Time stamp 10-31 16:24:55.368
5. unlock homescreen
   Time stamp 10-31 16:24:59.082 
   1x appears.

Comment 18

[Ken Chang[:kenkai]]

(In reply to pcheng from comment #17)
Thanks for your log. It's helpful. However, I am still sure this is the modem problem.
The following is detail comment.
https://bugzilla.mozilla.org/show_bug.cgi?id=932721#c10

Comment 19

[Enpei]

based on https://bugzilla.mozilla.org/show_bug.cgi?id=932721#c12 , add POVB in whiteboard.

Comment 20

[Preeti Raghunath(:Preeti)]

We do not block on POVB issues. Hence moving to koi?

Comment 21

[Jason Smith [:jsmith]]

Moving to minus for POVB

Comment 22

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

Attachment: qcril_adblogcat.log

Using QCRIL build, it also take a while to switch network type from EVDO to CDMA.

Test timestamp is: 11-21 18:46:30.675
Switch network mode from EVDO to CDMA

Comment 23

[Ken Chang[:kenkai]]

Edgar, we may need to query network type automatically to avoid this modem problem.

Comment 24

[Edgar Chen [:edgar]]

As comment #22, commercial RIL also takes a while to switch preferred network from EVDO to CDMA, it seems there is nothing we can do in MOZ RIL.

Comment 25

[BMO Automation]

Firefox OS is not being worked on