Closed
Bug 850112
Opened 12 years ago
Closed 12 years ago
Enable A-GPS prefs
Categories
(Firefox OS Graveyard :: Gaia, defect)
Tracking
(blocking-b2g:tef+, b2g18 fixed, b2g18-v1.0.0 wontfix, b2g18-v1.0.1 fixed)
RESOLVED
FIXED
blocking-b2g | tef+ |
People
(Reporter: kanru, Assigned: kanru)
References
Details
(Whiteboard: [QARegressExclude][qa?])
Attachments
(1 file)
Enable default A-GPS settings for all builds. Like gaia/build/payment-prefs.js, it should be customized as needed.
Assignee | ||
Comment 1•12 years ago
|
||
Attachment #723794 -
Flags: review?(fabrice)
Updated•12 years ago
|
Attachment #723794 -
Flags: review?(fabrice) → review+
Comment 2•12 years ago
|
||
Assignee | ||
Updated•12 years ago
|
blocking-b2g: --- → tef?
Comment 3•12 years ago
|
||
(tef- as this is not required for v1.0.1. A-GPS configuration is not configured in this mannor in the commercial v1.0.1 builds)
blocking-b2g: tef? → -
Comment 4•12 years ago
|
||
(In reply to Michael Vines [:m1] [:evilmachines] from comment #3)
> (tef- as this is not required for v1.0.1. A-GPS configuration is not
> configured in this mannor in the commercial v1.0.1 builds)
Can you provide more details on how it's going to be configured for tef?
Andreas requested this to be landed to all branches today. LEO+ first
blocking-b2g: - → leo+
Comment 5•12 years ago
|
||
We use /system/etc/gps.conf for this, and other location, configuration items
Comment 6•12 years ago
|
||
Michael, can we get your changes landed in our tree then? Our dogfooders can't test this right now, and we are running out of time to get this some test coverage.
Comment 7•12 years ago
|
||
Touched base with our partners. The patch can land on 1.0.1/TEF, they don't mind. They don't really need it since they overwrite the config with their own stuff, but we should land this right now so we can test on our end. So please uplift. Marking TEF+ for convenience, this is not really a blocker.
blocking-b2g: leo+ → tef+
Comment 8•12 years ago
|
||
Comment 9•12 years ago
|
||
Marking the bug as resolved based in the branch status
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 11•12 years ago
|
||
Can you please provide steps to verify this fix - as we will blackbox test from the UI?
Assignee | ||
Comment 12•12 years ago
|
||
This can't be verified from the UI..
Comment 13•12 years ago
|
||
(In reply to Kan-Ru Chen [:kanru] from comment #12)
> This can't be verified from the UI..
is there a config we can set to point to a a-gps station? i think we can verify from the UI, at least by comparing location speed, something like one phone on NOkia maps using AGPS, and the other phone using geolcation.
keep in mind we're in the US. Thanks.
Updated•12 years ago
|
Flags: needinfo?(kchen)
Updated•12 years ago
|
Whiteboard: QARegressExclude → [QARegressExclude][qa?]
Assignee | ||
Comment 14•12 years ago
|
||
(In reply to Tony Chung [:tchung] from comment #13)
> (In reply to Kan-Ru Chen [:kanru] from comment #12)
> > This can't be verified from the UI..
>
> is there a config we can set to point to a a-gps station? i think we can
> verify from the UI, at least by comparing location speed, something like one
> phone on NOkia maps using AGPS, and the other phone using geolcation.
>
> keep in mind we're in the US. Thanks.
You could change the config in B2G/gaia/build/gps-prefs.js
Yes, location speed should be improved with a-gps on, but sometimes it doesn't due to poor signal condition. I'm afraid there might be false alarms using this method.
Flags: needinfo?(kchen)
You need to log in
before you can comment on or make changes to this bug.
Description
•