I agree with Eric. Testing having a dev-only Flame configuration that is unlike any device that will actually ship is a recipe for wasting time.
Who knows how to make the 273 MiB Flame configuration more like a shipping phone? Nick On Wed, Jul 23, 2014 at 12:04 PM, Eric Rahm <[email protected]> wrote: > On 7/22/14 3:07 PM, Johan Lorenzo wrote: >> >> The following is a new meeting request: >> >> Subject: Bug bash - 2.0 on 273MB Flame >> Organizer: "Johan Lorenzo" <[email protected]> >> >> Location: "SFO-7B The Warfield" <[email protected]>; "MTV 203 Sanctuary" >> <[email protected]>; "TPE-4A Orange" <[email protected]> >> Resources: "SFO-7B The Warfield" <[email protected]>; "MTV 203 Sanctuary" >> <[email protected]>; "TPE-4A Orange" <[email protected]> >> Time: Thursday, July 24, 2014, 4:00:00 PM - 7:00:00 PM GMT -08:00 >> US/Canada Pacific >> >> Invitees: [email protected]; [email protected]; >> [email protected]; [email protected]; [email protected] >> >> >> *~*~*~*~*~*~*~*~*~* >> >> Hi everyone, >> >> QA needs your help to find bad bugs with 2.0 on 273MB Flame. We need >> everyone to join us in testing our product together at a bug bash to be held >> on July 24th from 4:00pm to 7:00pm PDT in the QA vidyo room (associated >> meeting rooms are Sanctuary in MTV, The Warfield in SF, and Orange in >> Taipei). >> >> Folks in different locations are encouraged to show up/stay earlier or >> later to fit their respective schedules. >> >> We want everyone who shows up to try to use 2.0 as a real user. That means >> locking your phone with Find My Device, using playing music in music player, >> browsing your favorite websites, using the calendar app with your Google >> Calendar, of course making phone calls and sending SMSes, sending emails >> with your email account in the email app, etc. >> >> Everyone is welcome to join. To participate, we recommend you to bring >> your Flame set to 273MB (some Flames will be able to be borrowed in MTV) to >> the bug bash with the latest 2.0 build running on it. Here is how to >> throttle down the memory: >> https://intranet.mozilla.org/QA/B2G_Tips_and_Tricks#Throttling_the_phone >> >> We'll provide free pizza for the Mountain View attendees during the bug >> bash. Additionally, we'll have prizes for the (1) most blocker bugs found, >> (2) highest number of bugs found during the bug bash, and (3) the most >> creative screenshot made out of the Gallery tiles. >> >> All of the details can be found here: >> https://etherpad.mozilla.org/b2g-qa-bug-bash-07242014. >> >> Hope to see you around! >> >> Jason Smith & Johan Lorenzo >> > > While I think the goals of this are laudable, I'm concerned that the bugs > we'll get (primarily of the MemShrink variety) won't be representative of a > true low end device, and we'll end up spending dev time fixing issues that > would not necessarily manifest on real hardware. > > The issue of doing a better job at simulating a low end device has been > raised in separate threads, but I'll reiterate a few points here: > * zram - the disk size needs to be lowered > * display - one recommendation was to set it to HVGA instead of FWVGA > * camera - in some way simulate a lower res camera > > It's not clear to me _how_ we do those things, but I'm sure other folks can > chime in. If we can figure that out for the bug bash I say go for it, if not > I think we should hold off. > > -e > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
