[b2g] The timing for mozbrowserloadstart event in shell.js
Hi all, When tracking the following issue, *Bug 909124* https://bugzilla.mozilla.org/show_bug.cgi?id=909124 - [b2g desktop] shell.js did not get correct mozbrowserloadstart event to send Gaia the pending chromeEvents I found that shell.js may not get the correct mozbrowserloadstart event for the loading of Gaia system app, if running Gaia in b2g desktop. From my test, most of the time, shell.js would receive 2 times of mozbrowserloadstart event, but document.location would still be about:blank. This would make shell.js fail to do the correct initialization for Gaia. So, I was wondering what is the correct behavior for mozbrowserloadstart about its timing and when it occurs, if the document.location would have been changed or not? Thanks. -- Rudy, Mozilla Taiwan ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
[b2g] loading web pages while FTU is running
Hi, so, I've been working on bug 891443 [1] for some time now, and I think I've tried everything I could. Let me explain what's happening: * While running the First Time Experience we want to display some web pages in some situations if the user has configured some way to access Internet * one of these web pages is the Firefox OS Privacy Page at https://www.mozilla.org/privacy/firefox-os/ (which gets eventually redirected (twice) to https://www.mozilla.org/en-US/privacy/policies/firefox-os/ for english users) * we used to display these web pages using an embedded mozbrowser iframe, the FTU is inside the communications webapp which has the browser permission. * all web pages except the Firefox OS privacy page are displayed correctly. * the same page on allizom works fine * this is true for 1.1 and master builds, but _not_ for 1.0.1 builds (ie: it works in 1.0.1). However, flashing a full 1.0.1 build, and _then_ a 1.1 gecko, or a gaia master or 1.1, and it still works. * same behavior whether FTU is loaded after first reset, or later from the Settings app. Here is what I tried * replacing the internal mozbrowser iframe with a call to window.open: same bug. Strangely, the same code and same URL in a normal app works fine. * I added Necko logs and replaced the initial URL with the second or third redirected URL. Basically, we're doing one redirect and stop here without displaying anything. Using directly the third URL works fine. See the comment 41 [2] for the details. Now I'm lost, and I'm ready to try any foolish idea you may have. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=891443 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=891443#c41 -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
[b2g] unagi transition plan
There have been rumblings of the unagi devices no longer being supported in the near future for 1.2 work. There are a few people within and without Mozilla that only have an unagi devices. What devices are suggested for people that currently have unagi devices? This is my current understanding, but it has been pieced together, hoping to get confirmation of this guidance: 1) A developer doing daily gaia development: try to get a hamachi. You need a phone that is close to what is shipping for making sure changes do not affect performance. Caveat seems to be that they may be hard to get. 2) A developer that wants to start making apps for firefoxos: the nexus 4 may be an option. It could also be used for main gaia work, but note: while the build settings for nexus 4 try to throttle it to look more like the kinds of devices that may ship in the near term, it is not an exact match, so use with caution. I have ordered a Nexus 4 as backstop to make sure I can keep working in case my unagi stops working, but I believe I should also acquire a more realistic shipping device for any performance work. To me that implies hamachi, but it will be good to know if there are other options. James ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] unagi transition plan
Please do not order Nexus 4 devices except if you are working on JellyBean-related platform work. Its simply not a good abstraction of the kind of device we are targeting. If you are concerned about what device to use, please talk to your manager. If you don't work for Mozilla, we are trying to make sure shipping devices from ZTE and TCL are easily available for anyone to buy cheaply (eBay), and we will try to keep them up-to-date with FFOS for quite some time. Andreas James Burke wrote: There have been rumblings of the unagi devices no longer being supported in the near future for 1.2 work. There are a few people within and without Mozilla that only have an unagi devices. What devices are suggested for people that currently have unagi devices? This is my current understanding, but it has been pieced together, hoping to get confirmation of this guidance: 1) A developer doing daily gaia development: try to get a hamachi. You need a phone that is close to what is shipping for making sure changes do not affect performance. Caveat seems to be that they may be hard to get. 2) A developer that wants to start making apps for firefoxos: the nexus 4 may be an option. It could also be used for main gaia work, but note: while the build settings for nexus 4 try to throttle it to look more like the kinds of devices that may ship in the near term, it is not an exact match, so use with caution. I have ordered a Nexus 4 as backstop to make sure I can keep working in case my unagi stops working, but I believe I should also acquire a more realistic shipping device for any performance work. To me that implies hamachi, but it will be good to know if there are other options. James ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
[b2g] devices for 1.2
1.2 release does not have a single device to develop for. plain and simple. if... • you're working on JB version of android your best bet is a nexus 4. but only a few people are in that camp and they already have a device. so talk to your manager if you really really need one. • if your work is based off of 1.1HD -- meaning you're in need of a WVGA device -- then the helix device is your best bet. again, you probably have one and if you don't, we'll try our best to get you one so you don't have to go the funny route of mucking with a nexus 4 to get it there. • otherwise, you're still developing on either a TCL or a ZTE device. our taipei team is working with these vendors to get us the latest ICS strawberry update for these phones. why? because the previous versions (which are on our unagi as well) don't play well with WebGL and we have no choice but to move to ICS strawberry. that's why the unagi is getting deprecated anyway. • last but not least, QA should have a few devices of each of what's mentioned above. that's cause they have to test for all the different combos (a difficult task). so don't steal from them unless if you talk to tony and have his okay. i know this is less than ideal, but for the time being it's what we have to do until things get cleared up. thanks! faramarz ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Emulator upside down and reversed?
This was a bug in an older version of the Android emulator. See if you can update it to a newer version. http://stackoverflow.com/a/14477654 Cheers, Jim On 8/26/13 9:04 PM, 平田修樹 (Naoki Hirata) wrote: Hi Taichi-san, Thank you for the email message! That is exactly what I am seeing as well. I just spoke with a colleague of mine and he stated he hasn't run into that issue with a MacBook Pro Retina because he's been using ubuntu on a Virtual Machine to compile it. I may end up going that route to see if that might resolve the issue. Regards, Naoki On 8/26/13 5:55 PM, Taichi Matsuura wrote: Hi Naoki san exactly same problem here. I also tested couple of PCs on this problem below: 1.iMac Lion - worked properly 2.iMac Mountain Lion(previously Lion) - worked properly 3.Makbook Pro Retina(Mountain Lion) - upside down and reversed The link is screenshot of upside down image. https://github.com/YusukeYamamoto/garage/blob/master/20130827_fxos_simulator_disp_reverse/simulator_disp_reverse_02.png Thanks, Taichi 2013年8月27日火曜日 5時46分08秒 UTC+9 平田修樹 (Naoki Hirata): Hi all, When compiling for the emulator, I'm showing the emulator displaying upside down and reversed. Is anyone else seeing something similar to that? I turned off the hw emulation and if I do that it doesn't show anything. If someone has figured that out, I would really appreciate the help. Regards, Naoki ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Emulator upside down and reversed?
Thanks Jim, I'm on 22.0.5 on the retina. Unfortunately that didn't resolve my issue. Regards, Naoki On 8/27/13 12:38 PM, Jim Chen wrote: This was a bug in an older version of the Android emulator. See if you can update it to a newer version. http://stackoverflow.com/a/14477654 Cheers, Jim On 8/26/13 9:04 PM, 平田修樹 (Naoki Hirata) wrote: Hi Taichi-san, Thank you for the email message! That is exactly what I am seeing as well. I just spoke with a colleague of mine and he stated he hasn't run into that issue with a MacBook Pro Retina because he's been using ubuntu on a Virtual Machine to compile it. I may end up going that route to see if that might resolve the issue. Regards, Naoki On 8/26/13 5:55 PM, Taichi Matsuura wrote: Hi Naoki san exactly same problem here. I also tested couple of PCs on this problem below: 1.iMac Lion - worked properly 2.iMac Mountain Lion(previously Lion) - worked properly 3.Makbook Pro Retina(Mountain Lion) - upside down and reversed The link is screenshot of upside down image. https://github.com/YusukeYamamoto/garage/blob/master/20130827_fxos_simulator_disp_reverse/simulator_disp_reverse_02.png Thanks, Taichi 2013年8月27日火曜日 5時46分08秒 UTC+9 平田修樹 (Naoki Hirata): Hi all, When compiling for the emulator, I'm showing the emulator displaying upside down and reversed. Is anyone else seeing something similar to that? I turned off the hw emulation and if I do that it doesn't show anything. If someone has figured that out, I would really appreciate the help. Regards, Naoki ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Flashing ZTE Open on Mac OS w/ flash.sh
James Kruth schrieb: Can anyone provide any insight as to what's going on here? Thanks! I saw the same when I did get a device with a locked bootloader, you might have the same issue. I could only solve that with internal tools, not sure if there's any public way to do this. Robert Kaiser ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
[b2g] Commercial RIL 08/27/2013 Leo v1.1 Smoke Test Results - 46/47 tests passed, 1 untested
46 out of 47 tests passed for the 2013-08-27 Leo v1.1.0 Commercial RIL Build. There are no major issues that prevented the smoketests from passing. Commercial RIL Build Smoketest Results: Daily Smoke Test Logs: https://docs.google.com/a/qanalydocs.com/spreadsheet/ccc?key=0AjRc6aVFoOW9dGZLdVdiWGZLbVdORlFpUGt5XzZ3Znc Moztrap link: https://moztrap.mozilla.org/runtests/run/2101/env/314/ Tests Were Performed With: Builds ID: 20130827041201 Gecko: 328b3b8158ee Gaia: 4b2f1a103d046c92d201e8fcfb1ae224f59e7cf1 Firmware Revision: D300f08o 0 reboots 0 crashes Build Updated From: - No OTA performed. New Bugs Breaking the Smoketests: - None reported. Existing Bugs Breaking the Smoketests: - None reported. New Issues Not Breaking the Smoketests: - None reported. Sincerely, Mozilla QA Team -- Call me on my B2G phone: 650-450-0173. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
[b2g] Mozilla RIL 08/27/2013 Buri 1.2 Smoketest Results - 33/47 tests passed, 3 new blockers
33 out of 47 tests passed for the 2013-08-27 Buri v1.2.0 Mozilla RIL Build. Since this came up yesterday as a question via email, during testing we are still hitting the crash stack in https://bugzilla.mozilla.org/show_bug.cgi?id=900012 Although that bug is resolved fixed, there are several spin off bugs at the bottom of the comments that indicate that it will take several other fixes to resolve other instances of this crash. Note that this crash causes the entire phone to reboot, and can usually be triggered by just playing a youtube video and then hitting the home button. Here are the major issues that prevented the smoketests from passing. Mozilla RIL Build Smoketest Results: Daily Smoke Test Logs: https://docs.google.com/a/qanalydocs.com/spreadsheet/ccc?key=0AjRc6aVFoOW9dGZLdVdiWGZLbVdORlFpUGt5XzZ3Znc Moztrap link: https://moztrap.mozilla.org/runtests/run/2102/env/347/ Tests Were Performed With: Builds ID: 20130827040201 Gecko: e42dce3209da Gaia: 599214a0f41eece076dc83cd85f5b27f8cfe67f2 0 reboots 2 crashes Build Updated From: - No OTA performed. New Bugs Breaking the Smoketests: - [New] [B2G] [Buri] [1.2] [Bluetooth] Unable to pair with other devices no error message shown https://bugzilla.mozilla.org/show_bug.cgi?id=909879 - [New] Importing contacts from facebook displays Error message:'Invalid App ID: 123456' https://bugzilla.mozilla.org/show_bug.cgi?id=909906 - [New] Camera app hangs and doesn't start https://bugzilla.mozilla.org/show_bug.cgi?id=909746 Existing Bugs Breaking the Smoketests: - [Existing] Blank crop page appears when attempting to add a gallery photo to a contact https://bugzilla.mozilla.org/show_bug.cgi?id=908449 - [Existing] [B2G] [Buri] [1.2] [Dialer] Keypad is unresponsive during phone call https://bugzilla.mozilla.org/show_bug.cgi?id=907443 - [Existing] [B2G][Buri][1.2][Marketplace] Packaged apps fail to install from the marketplace https://bugzilla.mozilla.org/show_bug.cgi?id=908892 - [Existing] [B2G] [Buri] [1.2] [YouTube] Videos stutter almost to the point of unplayability https://bugzilla.mozilla.org/show_bug.cgi?id=909564 - [Existing] Fail - crash in mozilla::layers::GrallocBufferActor::ActorDestroy(mozilla::ipc::IProtocolManagermozilla::ipc::RPCChannel::RPCListener::ActorDestroyReason) https://bugzilla.mozilla.org/show_bug.cgi?id=900012 New Issues Not Breaking the Smoketests: - None reported. Sincerely Mozilla QA Team -- Call me on my B2G phone: 650-450-0173. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Flashing ZTE Open on Mac OS w/ flash.sh
On Sunday, August 25, 2013 2:47:05 PM UTC-5, James Kruth wrote: I've been following the instructions to build and flash the latest version of b2g for my newly acquired ZTE Open and I've run into some issues. The first was that I found was that flash.sh will just seemingly sit in a loop: scout:B2G artlogic$ ./flash.sh adb server is out of date. killing... * daemon started successfully * error: device not found ERROR: could not get pipe properties ERROR: could not get pipe properties waiting for device ERROR: could not get pipe properties ERROR: could not get pipe properties ERROR: could not get pipe properties ERROR: could not get pipe properties ... I found that running the command as root produced more interesting results, but still a failure: scout:B2G artlogic$ sudo ./flash.sh Password: * daemon not running. starting it now on port 5037 * * daemon started successfully * ERROR: could not get pipe properties ERROR: could not get pipe properties waiting for device ERROR: could not get pipe properties erasing 'cache'... OKAY [ 0.523s] finished. total time: 0.523s ERROR: could not get pipe properties erasing 'userdata'... OKAY [ 1.385s] finished. total time: 1.385s ERROR: could not get pipe properties sending 'userdata' (67563 KB)... OKAY [ 6.369s] writing 'userdata'... ERROR: usb_read failed with status e2ed FAILED (status read failed (No such file or directory)) finished. total time: 6.743s Can anyone provide any insight as to what's going on here? Thanks! - James Same here on a Fedora 19 32-bit machine. It seems the device is locked although claimed otherwise. Here's the output: [alex@core2duo B2G]$ adb devices * daemon not running. starting it now on port 5037 * * daemon started successfully * List of devices attached roamer2 device [alex@core2duo B2G]$ ./flash.sh waiting for device erasing 'cache'... OKAY [ 0.519s] finished. total time: 0.519s erasing 'userdata'... OKAY [ 1.399s] finished. total time: 1.399s sending 'userdata' (67563 KB)... OKAY [ 6.173s] writing 'userdata'... FAILED (status read failed (No such device)) finished. total time: 11.501s [alex@core2duo B2G]$ ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Flashing ZTE Open on Mac OS w/ flash.sh
The USERDATA partition size is different from what is on there to what is compiled. I can't recall the size/fix for it at this moment. On 8/27/13 5:21 PM, yfy...@gmail.com wrote: On Sunday, August 25, 2013 2:47:05 PM UTC-5, James Kruth wrote: I've been following the instructions to build and flash the latest version of b2g for my newly acquired ZTE Open and I've run into some issues. The first was that I found was that flash.sh will just seemingly sit in a loop: scout:B2G artlogic$ ./flash.sh adb server is out of date. killing... * daemon started successfully * error: device not found ERROR: could not get pipe properties ERROR: could not get pipe properties waiting for device ERROR: could not get pipe properties ERROR: could not get pipe properties ERROR: could not get pipe properties ERROR: could not get pipe properties ... I found that running the command as root produced more interesting results, but still a failure: scout:B2G artlogic$ sudo ./flash.sh Password: * daemon not running. starting it now on port 5037 * * daemon started successfully * ERROR: could not get pipe properties ERROR: could not get pipe properties waiting for device ERROR: could not get pipe properties erasing 'cache'... OKAY [ 0.523s] finished. total time: 0.523s ERROR: could not get pipe properties erasing 'userdata'... OKAY [ 1.385s] finished. total time: 1.385s ERROR: could not get pipe properties sending 'userdata' (67563 KB)... OKAY [ 6.369s] writing 'userdata'... ERROR: usb_read failed with status e2ed FAILED (status read failed (No such file or directory)) finished. total time: 6.743s Can anyone provide any insight as to what's going on here? Thanks! - James Same here on a Fedora 19 32-bit machine. It seems the device is locked although claimed otherwise. Here's the output: [alex@core2duo B2G]$ adb devices * daemon not running. starting it now on port 5037 * * daemon started successfully * List of devices attached roamer2 device [alex@core2duo B2G]$ ./flash.sh waiting for device erasing 'cache'... OKAY [ 0.519s] finished. total time: 0.519s erasing 'userdata'... OKAY [ 1.399s] finished. total time: 1.399s sending 'userdata' (67563 KB)... OKAY [ 6.173s] writing 'userdata'... FAILED (status read failed (No such device)) finished. total time: 11.501s [alex@core2duo B2G]$ ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
[b2g] unagi update EOL
At today's cross-functional B2G meeting, I asked whether it made sense to point the old unagi update channels at the new ones, so older builds would get updated to the latest: https://bugzilla.mozilla.org/show_bug.cgi?id=909311 However, it turns out that we're phasing out unagi as a testing platform. Would it make sense to turn off unagi updates (and potentially releng-supported unagi builds, as well)? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] unagi update EOL
On 08/27/2013 06:38 PM, Aki Sasaki wrote: At today's cross-functional B2G meeting, I asked whether it made sense to point the old unagi update channels at the new ones, so older builds would get updated to the latest: https://bugzilla.mozilla.org/show_bug.cgi?id=909311 However, it turns out that we're phasing out unagi as a testing platform. Would it make sense to turn off unagi updates (and potentially releng-supported unagi builds, as well)? Does that mean that we will remove it from the sources, or that we will stop making builds for it on TBPL? Do we still want to support compiling for it? What is the ETA for that, and what is the spec of the substitute hardware of reference for benchmarking? -- Nicolas B. Pierron ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
[b2g] wifi changes
Hi All, The rewrite of wifi workers in c++ has landed on mozilla-central and should be in the next nighly builds. There should be no regressions, but let me know if anything looks off in this area, especially on JB. Fabrice -- Fabrice Desré b2g team Mozilla Corporation ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] wifi changes
https://bugzilla.mozilla.org/show_bug.cgi?id=864932 Fabrice is selling himself a little short here: The result of this work was a substantial decrease in main-process memory usage (more than 3mb in one instance), freeing up roughly an additional 2% of the 150mb available to Gecko on our 256mb phones for use by apps. Thanks, Fabrice! On Tue, Aug 27, 2013 at 10:36 PM, Fabrice Desre fabr...@mozilla.com wrote: Hi All, The rewrite of wifi workers in c++ has landed on mozilla-central and should be in the next nighly builds. There should be no regressions, but let me know if anything looks off in this area, especially on JB. Fabrice -- Fabrice Desré b2g team Mozilla Corporation ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
