Firefox OS/2014 Foxtrot

From MozillaWiki
Jump to: navigation, search
Foxtrot -The Dance


Program Summary

Please refer to Ladybug wiki for more detail on FxOS dogfooding program.

The 2014 FxOS Foxtrot Program is open to the Mozilla community.

  • Goal: Increase quality and usability by gathering usage data from an internal audience audience
  • Foxtrotters: Mozilla community members who will use the reference phone as their primay phone when possible and report any problems or issues on a timely basis.

Foxtrot Communities

Community Requirements Status
QA 1. Stable Hardware Green
Moz Developers 1. Stable Hardware Green
Early Adopters 1. Stable Hardware
2. Stable FxOS Release
3. FOTA Updates 		Blocked


Foxtrot Lessons

Turnstep -The turn

  • 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

TIMELINE CHART
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

3/31/14

  • General info:
    • Flame is based on v1.3 for shipping
    • 2K units shipping schedule:
    • T2M will ship out 500 units on 4/15, 1500 units on 4/20.
    • White box + min device information will be used for 2K shipment.
  • Build status:
  • Issues:
    • Bugzilla issue list: http://goo.gl/9uuEb4
      • 8/16 bugs are Mozilla's own issue.
      • 8 bugs for T2M (4 are single device issue)
        1. 975297 T2M updated new NFC firmware, but the sensitivity is really bad, investigation is on-going
        2. 972962 needs new PVT sample to fix.
        3. 989541 USB tethering does not detect network connection on Mac
        4. 989141 Camera preview is zoomed in
        5. 984300 T2M has received this problematic device on 3/28, investigation is on-going
        6. 987051 can not connect to 3G, this is one specific device problem, will send it back to T2M for investigation
        7. 987534 can not send SMS, this is one specific device problem (same device as issue above), will send it back to T2M for investigation
        8. 987528 can not dial out, this is one specific device problem (same device as issue above), will send it back to T2M for investigation
        9. 971163 --> resolved fixed
        10. 985725 --> resolved fixed
        11. 973737 --> resolved fixed
        12. 967944 --> resolved fixed
        13. 985798 --> resolved fixed
        14. 969254 --> resolved fixed
        15. 975739 --> resolved fixed
        16. 985774 --> resolved fixed
        17. 985768 --> resolved fixed
        18. 981964 --> resolved fixed
  • Source code sharing:
    • Mozilla Taipei team is working on build environment, target to finish by E/March (Owner: Thomas Tsai)
    • Gaia/gecko are able to be replace now.
    • This is for preparing how to create build manually: https://bugzilla.mozilla.org/show_bug.cgi?id=978888
    • Mozilla is based on T2M's proprietary list to make extract.sh (Owner: Thomas Tsai)
    • T2M is working on code sharing environment (ex. github)
    • Mozilla has instructed T2M how to set up github (Owner: Viral Wang)
    • 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)
    • To summarize our downloadable build/FOTA strategy, please refer to channels listed below:
      • Stable builds
      • Release quarterly or longer, ex. v1.3, v1.5, etc
      • FOTA/Downloadable full image are both available
      • both FOTA client/server are provided by T2M
      • QA verified
      • Foxtrot builds
      • Release weekly or longer, with master-c
      • FOTA/Downloadable full image are both available
      • both FOTA client/server are provided by T2M
      • QA verified
      • Nightly build
      • Release daily, with master-c
      • Downloadable full image is available
    • No FOTA
      • OTA client/server are provided by Mozilla, only gaia/gecko will be updated
    • No QA verified
      • [n-1] build: Also provide the latest 1.3 (stable) downloadable build.
    • NFC:
    • T2M updated new NFC firmware, but the sensitivity became really bad. Mozilla has provided video to T2M for further investigation.



3/24/14

  • General info:
    • Flame is based on v1.3 for shipping
    • 2K units shipping schedule:
    • T2M will ship out 500 units on 4/15, 1500 units on 4/22.
    • Upgrade to Android 4.4 (Kitkat) is out of original scope (as KitKat was not announced then), and now under discussion w/ Thundersoft.
      • it depends on QCT's release plan
      • QCT replied:
        • What we do not have right now is an official plan of record to commercialize v1.4 + Kitkat + 8210 at the product level. This means that until that happens, we would have no formal testing or be able to provide any customer support on such a branch.
    • Build status:
      • build storage link: https://mozilla.app.box.com/s/v87dfnez9q4bh4g78pb5
      • latest build: foxphone-v109-2.zip shared on 3/17
      • Rfcard patches shared on 3/24
      • please refer to the instruction to flash device in section #3 (white screen issue)
      • Next build will be provided to Moz on 3/25 late evening.
    • Issues:
      • Blocker: white screen issue
      • Now we have a combination build to resolve white screen problem.
      • Taipei QA team has verified this solution in Taiwan.
      • Build folder: https://mozilla.app.box.com/files/0/f/1708478428/Foxfone-One
        • (1)v109-2 (base build)
        • (2)v107-3 userdata
        • (3)Foxfone_US-new-rfcard.img
        • (4)NON-HLOS-new-rfcard.bin
    • At first, using v109-2 + v107-3's userdata.img to flash. Then follow below commands to flash new solution:
      • fastboot flash fsg Foxfone_US-new-rfcard.img
      • fastboot flash modem NON-HLOS-new-rfcard.bin
      • fastboot erase modemst1 // erase EFS file partition,so EFS can get NV item again from fsg partition after restarting
      • fastboot erase modemst2 fastboot reboot
    • USA QA team will also help to verify this build in USA.
      • Bugzilla issue list: http://goo.gl/9uuEb4
      • 9/22 bugs are Mozilla's own issue.
      • 13 bugs for T2M (8 issues already have solution)
        • 967944 is related to DSDS, wait for T2M's patch
        • 985798 GPS seems not working. T2M is clarifying this issue with Naoki.
        • 984300 T2M requested Moz to send the problematic device back to china for investigation. so far, this issue only happens on this specific device.
        • 971163 T2M is clarifying this issue.
        • 985725 T2M is clarifying this issue.
        • 973737 is related to white screen. We have a build which fixed the white screen issue, USA QA will verify it.
        • 975297 T2M updated new NFC firmware and claim this issue is fixed. will be verified by Moz QA.
        • 969254 verified fixed.
        • 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.
        • 985774 fix ready, will be included in T2M's next release.
        • 985768 fix ready, will be included in T2M's next release.
        • 981964 fix ready, will be included in T2M's next release.
    • Source code sharing:
      • Mozilla Taipei team is working on build environment, target to finish by E/March (Owner: Thomas Tsai)
      • T2M provided a list of proprietary/binary blobs which has legal concern.
      • 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)
      • T2M is working on code sharing environment (ex. github)
      • Mozilla will have a technical call with T2M to help them set up github (Owner: Viral Wang)
      • 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 is still under discussion with T2M. Alternative solution has been proposed and it's under internal discussion.
    • Flame box packaging:
    • NFC:


=======
  • 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:
  • 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
          1. 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
          1. 973737 is related to white screen
          2. 975739 can't be reproduced from both T2M and Taipei QA. will be verified in next image in USA.
          3. 972962 needs new PVT sample to fix.
          4. 981964 fix ready, will be included in T2M's next release.
          5. 975297 is under clarifying with T2M, it could be NFC antenna problem
          6. 969254 T2M is checking why nfcd is missing after v107
  • 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)
    • 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:


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.
Retrieved from "https://wiki.mozilla.org/index.php?title=Firefox_OS/2014_Foxtrot&oldid=1057142"