Closed Bug 890325 Opened 11 years ago Closed 11 years ago

[User story][CDMA] Signal notification

Categories

(Firefox OS Graveyard :: RIL, defect, P1)

x86
macOS
defect

Tracking

(blocking-b2g:koi+, firefox26 fixed)

RESOLVED FIXED
blocking-b2g koi+
Tracking Status
firefox26 --- fixed

People

(Reporter: khu, Unassigned)

References

()

Details

(Whiteboard: [ucid:CDMA1, FT:RIL, KOI:P1], [Test case ETA:9/9])

User story: 

"As a user / OEM / carrier, we should be able to see the signal strength notification (RSSI) function for CDMA/EVDO network"

Acceptance criteria: 

Use can see signal strength of network.
Depends on: 842220
Depends on: 835237
blocking-b2g: --- → koi+
Flags: in-moztrap?
QA Contact: echu
Hi Sandip,

Could you provide more acceptance criteria for this user story?

Here is my suggestion:
1. User can see "1x" and "EV" indictors depending on network connecting status.
2. User should see no service indicator.
3. User can distinguish signal strength from clear x bar indicators. (x might be 4 or 5 depends on requirements)

Thanks,
Enpei
Flags: needinfo?(skamat)
> 1. User can see "1x" and "EV" indictors depending on network connecting
> status.

Anshul - Please confirm 8x26 will have only these 2 (user facing) states?

> 2. User should see no service indicator.
Agree.

> 3. User can distinguish signal strength from clear x bar indicators. (x
> might be 4 or 5 depends on requirements)

Anshul - Please confirm 8x26 will provide the "strength translation algorithm?" If it is same as GSM (5bars), I am not sure if the RIL APIs are same?
Flags: needinfo?(skamat) → needinfo?(anshulj)
Sandip, I think the gaia should only care about how many signal strength bars to be shown and the logic to come up with strength translation should reside in RIL. The bug 835237 updates the interface to pass all the signal strength value from RIL to gaia and have the logic in gaia, which might be an overkill for gaia when RIL can make the decision and send the "relSignalStrength" instead.
Flags: needinfo?(anshulj)
Talked with UX and related members. 
1. Agreed to have one signal icon.  
2. With data call, it will show: 
EV
1X 
3. No data call, only signal bar.
Priority: -- → P1
Hi Sandip and Kevin,

How about data call dormant and active cases? What the UX behavior should be?
Flags: needinfo?
Flags: needinfo?
Flags: in-moztrap?(echu)
Flags: in-moztrap?
I think Neo could be the best one to answer this question?
Whiteboard: [ucid:CDMA1] → [ucid:CDMA1], [FT:RIL]
Whiteboard: [ucid:CDMA1], [FT:RIL] → [ucid:CDMA1, FT:RIL, KOI:P1]
Whiteboard: [ucid:CDMA1, FT:RIL, KOI:P1] → [ucid:CDMA1, FT:RIL, KOI:P1], [Test case ETA:9/9]
Confirmed with Dev, current design will depend on Rx power only. Will base on this requirement to create test cases.
* >= -76,    level 5
* -77 ~ -83, level 4
* -84 ~ -90, level 3
* -91 ~ -97, level 2
* -98 ~ -104,level 1
* <= -105,   level 0
Update test case URL, yet some minor revise will be needed when UX is ready.
Flags: in-moztrap?(echu) → in-moztrap+
Blocks: 890828
Blocks: 890823
QA can verify this user story now.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Depends on: 911642
Test completed, failed. Issues are in depend on field. (Wasabi master 20130830172300)
Component: General → RIL
Depends on: 909689
Depends on: 931670
Depends on: 933673
Depends on: 941511
You need to log in before you can comment on or make changes to this bug.