Closed
Bug 981994
Opened 12 years ago
Closed 8 years ago
[Tarako]Update correct invalid LTE signal strength values.
Categories
(Firefox OS Graveyard :: Vendcom, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: sku, Unassigned)
Details
By following AOSP definition, please update SPRD LTE_SS.signalStrength/LTE_SS.rsrp/LTE_SS.rsrq/LTE_SS.ssnr to below value to avoid any misleading on SignalStrength checking on 1.4 (or newer version) if there is any version upgrade.
LTE_SS.signalStrength: 99
LTE_SS.rsrp: 2147483647
LTE_SS.rsrq: 2147483647
LTE_SS.rssnr: 2147483647
(see [1])
// Tarako Log
06-10 21:04:03.550 93 330 D RILC : [0063]< SIGNAL_STRENGTH {[signalStrength=30,bitErrorRate=99, CDMA_SS.dbm=-1,CDMA_SSecio=-1, EVDO_SS.dbm=-1,EVDO_SS.ecio=-1, EVDO_SS.signalNoiseRatio=-1, LTE_SS.signalStrength=-1,LTE_SS.rsrp=-1,LTE_SS.rsrq=-1, LTE_SS.rssnr=-1,LTE_SS.cqi=-1]}
[1] AOSP definition - https://github.com/android/platform_hardware_ril/blob/master/include/telephony/ril.h#L713
| Reporter | ||
Comment 1•12 years ago
|
||
Hi Sam:
Please help update ril.so when you are available.
Flags: needinfo?(sam.hua)
Okay,i will change the initial value of LET signal to 0x7FFFFFFF.
Maybe we should check the difference of our RILC and Android new version.
which version do u reference the android, 4.4 or 4.3?
Flags: needinfo?(sam.hua)
| Reporter | ||
Comment 3•12 years ago
|
||
AOSP 4.3/4.4 share the same ril.h about LTE signal strength.
(ie: RIL_LTE_SignalStrength and RIL_LTE_SignalStrength_v8.)
typedef struct {
int signalStrength; /* Valid values are (0-31, 99) as defined in TS 27.007 8.5 */
int rsrp; /* The current Reference Signal Receive Power in dBm multipled by -1.
* Range: 44 to 140 dBm
* INT_MAX: 0x7FFFFFFF denotes invalid value.
* Reference: 3GPP TS 36.133 9.1.4 */
int rsrq; /* The current Reference Signal Receive Quality in dB multiplied by -1.
* Range: 20 to 3 dB.
* INT_MAX: 0x7FFFFFFF denotes invalid value.
* Reference: 3GPP TS 36.133 9.1.7 */
int rssnr; /* The current reference signal signal-to-noise ratio in 0.1 dB units.
* Range: -200 to +300 (-200 = -20.0 dB, +300 = 30dB).
* INT_MAX : 0x7FFFFFFF denotes invalid value.
* Reference: 3GPP TS 36.101 8.1.1 */
int cqi; /* The current Channel Quality Indicator.
* Range: 0 to 15.
* INT_MAX : 0x7FFFFFFF denotes invalid value.
* Reference: 3GPP TS 36.101 9.2, 9.3, A.4 */
} RIL_LTE_SignalStrength;
typedef struct {
int signalStrength; /* Valid values are (0-31, 99) as defined in TS 27.007 8.5 */
int rsrp; /* The current Reference Signal Receive Power in dBm multipled by -1.
* Range: 44 to 140 dBm
* INT_MAX: 0x7FFFFFFF denotes invalid value.
* Reference: 3GPP TS 36.133 9.1.4 */
int rsrq; /* The current Reference Signal Receive Quality in dB multiplied by -1.
* Range: 20 to 3 dB.
* INT_MAX: 0x7FFFFFFF denotes invalid value.
* Reference: 3GPP TS 36.133 9.1.7 */
int rssnr; /* The current reference signal signal-to-noise ratio in 0.1 dB units.
* Range: -200 to +300 (-200 = -20.0 dB, +300 = 30dB).
* INT_MAX : 0x7FFFFFFF denotes invalid value.
* Reference: 3GPP TS 36.101 8.1.1 */
int cqi; /* The current Channel Quality Indicator.
* Range: 0 to 15.
* INT_MAX : 0x7FFFFFFF denotes invalid value.
* Reference: 3GPP TS 36.101 9.2, 9.3, A.4 */
int timingAdvance; /* timing advance in micro seconds for a one way trip from cell to device.
* Approximate distance can be calculated using 300m/us * timingAdvance.
* Range: 0 to 0x7FFFFFFE
* INT_MAX : 0x7FFFFFFF denotes invalid value.
* Reference: 3GPP 36.321 section 6.1.3.5
* also: http://www.cellular-planningoptimization.com/2010/02/timing-advance-with-calculation.html */
} RIL_LTE_SignalStrength_v8;
Updated•12 years ago
|
Summary: Update correct invalid LTE signal strength values. → [Tarako]Update correct invalid LTE signal strength values.
Not sure if we need this for certification... noming.
blocking-b2g: --- → 1.3T?
undoing nom based on discussion with bajaj.
blocking-b2g: 1.3T? → ---
Comment 7•8 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•