Firefox OS/2014 Foxtrot
Jump to navigation
Jump to search
|
Program Summary
The 2014 FxOS Foxtrot Program is open to Mozilla employees only (this may change depending on program requirements).
- Goal: Increase quality and usability by gathering usage data from an internal audience audience
- Dogfooders: Mozilla employess who will use the reference phone as their primay phone and report any problems or issues on a timely basis.
Foxtrot Lessons
- How to sign up for Foxtrot emails
- Go to https://mail.mozilla.org/listinfo/foxtrot
- Fill out the subscription details and click subscribe.
- An email will be sent to you asking for confirmation of your subscription request.
- The list moderator will approve the subscritpion once the the confirmation has been received.
- How to load nightly builds
Links
Etherpads:
Wikis:
TIMELINE
| Name of pending task | Likely ETA for completion | Owner of the task |
|---|---|---|
| Getting Smoke tests on Flame device | Start date unknown | B2G QA - Tony |
| Current Perf stats | Start date unknown | Unknown |
Random notes
ABOUT FLAME REFERENCE DEVICE
- General info:
- Flame is based on v1.3 for shipping
- 2K units shipping date has changed to TBD, Frankie is still in discussion with T2M
- Upgrade to Android 4.4 (Kitkat) is out of original scope (as KitKat was not announced then), and now under discussion w/ Thundersoft.
- T2M is also checking with QCT for their release plan
- Build status:
- build storage link: https://mozilla.app.box.com/s/v87dfnez9q4bh4g78pb5
- latest build: foxphone-v107-3.zip shared on 3/6
- need to use fastboot to flash device
- Next build schedule is TBD due to white screen issue still exists
- Issues:
- Blocker: white screen issue
- QCT has provided a new modem image on 3/12
- White screen issue is still reproduced in Taipei, ramdump has been provided to T2M.
- T2M also made their own fix in modem image on 3/12
- White screen issue is still reproduced in Taipei, ramdump has been provided to T2M.
- Bugzilla issue list: http://goo.gl/9uuEb4
- 7/15 bugs are Mozilla's own issue.
- 8 bugs for T2M
- 975264, #967944 are related to DSDS
- Taipei QA team starts to test DSDS with a manual set-up: change quad-band to 2-band, in order to avoid white screen issue
- 973737 is related to white screen
- 975739 can't be reproduced from both T2M and Taipei QA. will be verified in next image in USA.
- 972962 needs new PVT sample to fix.
- 981964 fix ready, will be included in T2M's next release.
- 975297 is under clarifying with T2M, it could be NFC antenna problem
- 969254 T2M is checking why nfcd is missing after v107
- Blocker: white screen issue
- Source code sharing:
- T2M provided another time source code on 3/11, since the one provide on 3/5 has build error.
- Build success. Taipei team is trying to set up a local build environment. (Owner: Thomas Tsai)
- T2M will provide a list of proprietary/binary blobs which has legal concern.
- legal review took longer than expected.
- Targeted date: 3/17 (Monday)
- this is for preparing how to create build manually: https://bugzilla.mozilla.org/show_bug.cgi?id=978888
- Mozilla is taking care extract.sh which pulls those proprietary/binary files from device in order to repro (Owner: Thomas Tsai)
- on-going.
- T2M is working on code sharing environment (ex. github)
- T2M is waiting for their top management's approval
- Target schedule: TBD. this is a daily check item.
- Nightly build/OTA preparation:
- Preparation: once how to create build manually is completed, nightly build for Flame can be created: https://bugzilla.mozilla.org/show_bug.cgi?id=978888
- AE team is preparing device, manifest, config in order to resolve #978888. (Owner: Thomas Tsai)
- Nightly FOTA will be discussed internally in drivers' meeting. (3/18)
- Flame box packaging:
- White box + minimum design will be used for first 2K shipment.
- T2M will provide deadline for final box design ( any order after the first 2K shipment)
- DSDS:
- T2M is focusing on fixing modern crash issue (white screen), then T2M will confirm if DSDS is working perfectly (HW perspective) on Flame.
- NFC:
- vibrating issue: https://bugzilla.mozilla.org/show_bug.cgi?id=975297
- Found same issue with 2 Flame with Android version. Suspect its NFC antenna issue, its HW related.
- T2M is working on including new NFC firmware to Flame build.
- T2M provided another time source code on 3/11, since the one provide on 3/5 has build error.
FOTA
- Stable builds (of FxOS version release): QA verified, will have full ROM for download, and will have FOTA (firmware over-the-air) update.
- Frequency could be one quarter or longer.
- Weekly builds (of master): QA verified, will have full ROM for download, and will have FOTA update. Frequency could be one week or longer.
- Nightly: will have full ROM for download only, NO FOTA update. Not QA verified. Question: how many nightly builds do we need to keep?
- [n-1] build: Both stable and weekly builds above come from master (1.4 or above in this case). We should also provide the latest 1.3 (stable) build.
- Though not included in original scope, we learned that there is voice asking for nightly FOTA builds. After discussing w/ vendor, the only feasible way while remaining cost effective is to have nightly FOTA builds w/ conditions listed below.
- As T2M is leveraging TCL's FOTA infrastructure, FOTA builds may have 1~2 days of delay. That is, nightly builds could be 1 or 2 days old.
- As keeping delta for nightly builds will be a management nightmare, providing full ROM FOTA seems to be the only feasible way. That is, no matter which nightly build you’re on, you’ll always get FOTA updated to the latest nightly build, w/ all user data wiped out. It’s basically the same as downloading the ROM build and flash the device.
- With conditions above, we don’t see the clear benefit of having nightly FOTA. Therefore we propose to NOT have nightly FOTA, and stick to the proposal of the 4 bullets in the upper half of this mail. Thank you very much.