Re: [b2g] Try server and Blobfree
Le 20/08/2015 00:36, Naoki Hirata a écrit : One of the issues I heard is that the gecko folks aren’t able to test themselves or hear about on devices issues too late. I filed bug *Bug 1196487* https://bugzilla.mozilla.org/show_bug.cgi?id=1196487 -B2G blobfree builds on try server I think this would be one way we can test the gecko builds prior to on device. Since it doesn’t contain blobs, we should be able to have these publicly available even. At least that was my thought process. Would people find this helpful? Actually we should have on try the same image builds that we have for mozilla-central already (blobfree and not-blobfree -- the latter available only after LDAP login). It was a bit surprising to me to see we can't trigger an image build in try. -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
[b2g] Running gaia unit tests with gdb
(Cross-post to dev-platform and dev-b2g, reply-to dev-b2g) Hi, sometimes we need to track crashes, and sometimes those are crashes happening with unit tests. So I just landed in bug 1177165 a change so that you can to run the test runner in gdb. You can find more information on MDN [1]. Please tell me if you have any suggestion about this :) [1] https://developer.mozilla.org/en-US/Firefox_OS/Automated_testing/Gaia_unit_tests#Launching_the_test_runner_with_gdb -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Running gaia unit tests with gdb
Also note that now as part of this change, if you close the Firefox (or B2G (or Mulet)) runner, this will also stop the node server. TBH this was making me crazy for months :D Le 02/08/2015 11:57, Julien Wajsberg a écrit : (Cross-post to dev-platform and dev-b2g, reply-to dev-b2g) Hi, sometimes we need to track crashes, and sometimes those are crashes happening with unit tests. So I just landed in bug 1177165 a change so that you can to run the test runner in gdb. You can find more information on MDN [1]. Please tell me if you have any suggestion about this :) [1] https://developer.mozilla.org/en-US/Firefox_OS/Automated_testing/Gaia_unit_tests#Launching_the_test_runner_with_gdb signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] How can I modifiy devicePixelRatio?
Le 30/07/2015 19:12, Kartikaya Gupta a écrit : IIRC there's also a GAIA_DEV_PIXELS_PER_PX env variable for gaia and I'm not entirely sure what that does, it may or may not be related. AFAIK it only selects the right images/videos to push to the device, so that eg image-based backgrounds do not look blurry. signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] System (Others) is wasting my Data
Le 21/07/2015 09:18, Jovan Gerodetti a écrit : Hello, Last night I switched to a new SIM card. I setup the usage app and now after 4 hours (I changed the SIM at 5 am and now it's 9 am) The System or Others, what it's called in the usage app, used about 32 MB of data just in stand by. [1] This is an enormous waste of my data Can you somehow check with your carrier if this is accurate ? Also, what version of FxOS do you use ? signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] FXOS fork H5
Le 20/07/2015 14:45, Luna Jernberg a écrit : Heard about this in Linux Action Show http://linuxgizmos.com/firefox-os-fork-project-gets-a-100-million-boost/ any comments? Given our goal is to improve the diversity in the mobile space, a new OS is more than welcome to achieve this goal. It's even more welcome if they use our code (according to the code license of course) and decide to share their changes with us. -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] The Future of Building and Testing Firefox OS
Le 20/07/2015 18:12, Gareth Aye a écrit : - To get gecko logs when running in VERBOSE mode you need to apply the patch from https://github.com/mozilla-b2g/gaia/pull/30760. What's to prevent us from just landing that now? FYI, as of https://github.com/mozilla-b2g/gaia/commit/4fe0507781f3ed56c8ae5e66dd9489165d1ff68e, you can do HOST_LOG=stdout make test-integration (or HOST_LOG=stdout npm run marionette) to pipe gecko stdout to your nodejs stdout. Just a question: we used to be able to pipe the usual console.log messages to stdout -- is that the same here ? 1.) https://groups.google.com/forum/#!topic/mozilla.dev.gaia/kBUjgBfTAG4 https://groups.google.com/forum/#%21topic/mozilla.dev.gaia/kBUjgBfTAG4 On Fri, Jul 17, 2015 at 4:24 PM, Gareth Aye gareth@gmail.com mailto:gareth@gmail.com wrote: Hi Everybody! We're spinning up a small Firefox OS Automation team to focus on improving the way that we do builds and testing in gaia. Initially, the group will be composed of Aus and I along with some build support from Ricky and Greg in Taipei. I wrote a longer-form piece that will hopefully help elucidate what problems we're looking at here http://gaye.github.io/the-future-of-building-and-testing-firefox-os/. We're looking to put together some more documentation about the projects we're pursuing, but this should whet your appetite for what's to come (if you're the kind of person who can develop an appetite for automation...). Happy weekend! Gareth ___ dev-gaia mailing list dev-g...@lists.mozilla.org mailto:dev-g...@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-gaia ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] PSA: Please avoid landing risky patches on master/m-c for 3 weeks
This sounds like a great plan. Why can't you use it for the initial release ? :) Le 10/06/2015 19:08, Douglas Sherk a écrit : Hi Julien, Good question. Naoki can answer more questions about this, but I can provide a summary. We currently have 3 OTA channels: * *dogfood*: The main channel that Spark will point to by default. We will be rolling out updates here every 3-7 days. * *dogfood-test*: The staging channel for dogfood. Candidates for OTA updates go on here and are tested by a smaller set of QA people for a few days before moving to the dogfood channel. o If the build here doesn't pass our stability criteria, we discard it and move the current dogfood-latest to dogfood-test and try again. As a consequence, we can theoretically go for weeks without an OTA update, but this is better than breaking people. * *dogfood-latest*: The most up-to-date build at all times. Built and updated nightly. This plan is a bit rough at this stage, and we're going to use it as a framework while improving things as we go. Any feedback is welcome. Doug On 10 Jun 2015 9:12 am, Julien Wajsberg jwajsb...@mozilla.com mailto:jwajsb...@mozilla.com wrote: Hey Douglas, There is something I don't get properly here. I'm sure you intend to provide updates to dogfooders once they all get their shiny new phones. I guess you'll base these updates on master. Do you plan to ask the same thing each time you want to provide a new update ? Or do you plan to prepare candidate updates that someone (maybe you) will test for some days before rolling it to all users ? Cheers, Le 06/06/2015 02:21, Douglas Sherk a écrit : Hi all, Spark is launching soon. It's based on Gaia master and Gecko mozilla-central, so we'd appreciate it if you avoided landing risky patches for 3 weeks while we stabilize. Alternatively, you could have your patches tested very heavily before landing. You can see our current timelines here: https://wiki.mozilla.org/Release_Management/B2G_Landing#Versions_and_Scheduling Thanks for your patience and understanding. Doug ___ dev-gaia mailing list dev-g...@lists.mozilla.org mailto:dev-g...@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-gaia signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
[b2g] Activities in a world of URLs
(crossposting to dev-gaia, dev-b2g, dev-webapi,
reply-to: dev-webapi)
Hi,
In this crazy moment where we're allowed to reinvent everything, I'd
like that we take some time to think about activities.
From the start activities worked but never were quite satisfying,
especially because they use API instead of URLs, and use system messages.
Instead, we could use URLs and HTTP verbs.
We could use an URL like activity://activity/parameters. Gecko would
be responsible for transparently transforming this into eg
app://app_name/activities/activity/parameters (or a HTTP URL of course).
For example, instead of :
new MozActivity({
name: 'pick',
data: {
type: ['image/*', 'audio/*', 'video/*', 'text/vcard']
}
}).then(data = {
// do something with data
}).catch(e = {
// handle error
});
we could use:
fetch({
method: 'GET',
url: 'activity://pick/',
headers: new Headers({
Accept: ['image/*', 'audio/*', 'video/*', 'text/vcard'].join(',')
})
}).then(response = {
if (response.status === 404) {
// no handler for this activity
} else {
// do something with response.blob()
}
}).catch(e = {
// handle error
});
Similar things can happen for activities that share or open an element.
So instead of:
new MozActivity({
name: 'open',
data: {
type: mimetype,
filename: filename,
blob: blob,
allowSave: true
}
}).catch(e = {
// handle error
});
We could have:
fetch({
method: 'POST',
url: 'activity://open/',
headers: new Headers({
'Content-Type', mimetype
}),
parameters: new URLSearchParams({
filename: filename,
allowSave: 1
}), // I wish
body: blob
}).then(response = {
if (response.status === 404) {
// no handler for this activity
}
}).catch(e = {
// handle error
});
Then for the caller this is a lot similar.
Now for the callee this could be handled with a fetch event in a Service
Worker.
self.addEventListener('fetch', function(event) {
event.respondWith(new Promise((resolve, reject) = {
if (event.request.url.startsWith('/activity/pick')) {
resolve(ImagePicker.pickImage().then(blob = new Response(blob)));
}
}));
});
But this could just as well be handled by a server-side server.
Here are some issues I foresee:
* such a request could take long to fulfill and should not timeout,
because sometimes the request is handled by a user action.
* currently all activities come from a user action. I think we can keep
the same restriction in the ActivityProtocolHandler.
For Mozilla this would be great, because this would be a depart from
using a proprietary API.
What do you think ?
--
Julien
signature.asc
Description: OpenPGP digital signature
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Updating the ZTE Open C from Mozilla Nightly system images - Small Fonts issue
Le 16/05/2015 17:52, Michael Monreal a écrit : On Wednesday, January 21, 2015 at 2:42:57 AM UTC+1, Ralph Daub wrote: Hello people of B2G mailing lists, A user in the SUMO forums is having issues after manually updating a ZTE Open C device from v1.4 to v2.1 using the links provided in the MDN website. According to the user, everything is good except the font is tiny. He tried to apply the font fix but it doesn't seem to work. Has anyone experienced this with the ZTE Open C or any other device? Please feel free to point me in the right direction. Thanks, - Ralph I just ran into the same issue. Updated my Open C to KK, shallow flashed latest 2.1 flame-kk, it all works fine only the fonts are tiny. Also the controls on the lockscreen are smaller than before so maybe it is not the fonts but some kind of UI scaling bug? I cannot flash the fonts fix btw (Read-only file system). Did anyone ever find a solution? How did you update the open C to KK ? I don't know of a way to do this... signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Connecting to a Klif
You can know the right idVendor if you run dmesg after plugging in your
phone.
Le 16/05/2015 12:12, Guillaume Marty a écrit :
I'm trying to connect my laptop to a Klif (a device commercialised by
Orange in Senegal).
adb server returns the no permission message:
List of devices attached
no permissions
I'm on Ubuntu and my /etc/udev/rules.d/51-android.rules looks like this:
SUBSYSTEM==usb, ATTRS{idVendor}==1782, MODE=0666
SUBSYSTEM==usb, ATTR{idVendor}==18d1, MODE=0666, GROUP=plugdev
SUBSYSTEM==usb, ATTR{idVendor}==0bb4, MODE=0666, GROUP=plugdev
SUBSYSTEM==usb, ATTR{idVendor}==80ee, MODE=0666, GROUP=plugdev
SUBSYSTEM==usb, ATTR{idVendor}==08ee, MODE=0666, GROUP=plugdev
SUBSYSTEM==usb, ATTR{idVendor}==05c6, MODE=0666, GROUP=plugdev
Of course ADB and dev tools debugging by USB is enabled on the
developers menu.
The version running is Gaia 2.0 and Gecko 32.
Am I missing anything?
Thanks,
--
Guillaume Marty
@g_marty
http://gu.illau.me http://gu.illau.me/
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
signature.asc
Description: OpenPGP digital signature
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Problem with adb
Hey fredy, I filed the bug on Debian's bugtracker: http://bugs.debian.org/781256. Le 25/03/2015 18:31, Alfredos (fredy) Damkalis a écrit : I face the same bug with my laptop. I have also have the same setup, debian jessie and option, usb_wwan and qmi_wwan modules loaded. On my Desktop with the same version of Debian but without these modules works fine. An interesting work around was to enable USB tethering on the device. Please let me know via this list discussion or personal email when you file this bug. Thanks! On 03/25/2015 05:19 PM, Julien Wajsberg wrote: I managed to work around the issue. I'll explain the cause and the solution I found so that anybody getting this issue in the future could find a possible solution in the list's archives. It looks like my issues came from the linux kernel module option, which is a driver for some USB 3G dongles. It looks like that the Flame (and Buri which had the same issue) triggered the loading of this module. The downside is that the module didn't work at all, filled the kernel log with messages (especially its dependencies usb_wwan and qmi_wwan). Moreover when halting the computer there was very often a kernel crash stacktrace (I took a picture of it in case it could be useful). When running /sbin/lsmod | grep option you could also look at the Used by column to see that the number was constantly increasing. The solution I used is backlisting the module. I did this by adding a file /etc/modprobe.d/option.conf with the following content: install option /bin/false Simply using blacklist option did not seem to work. I think some Debian component changed the way to load modules recently and as a result the blacklist keyword does not work in this situation (and this could be what provoked my issues in the first place). Then I ran depmod -ae and update-initramfs -u as advised on websites (but I'm not that sure it's useful), and rebooted. And tada, the option module is not autoloaded anymore and adb devices works ! I'll file a bug to Debian soon, hopefully this can be fixed on their side. Thanks to all the people who helped me :) Le 25/03/2015 15:00, Julien Wajsberg a écrit : On the same computer, my Open C (v2.1) and a Z3 (master) work fine with adb. So this is somehow an incompatibility between the Flames' adb and my configuration. Le 25/03/2015 14:50, Julien Wajsberg a écrit : Additional info: using a Live USB version of Ubuntu, I could make adb work flawlessly. So something is really happening in Debian :/ Le 24/03/2015 19:54, Julien Wajsberg a écrit : I'd like to add that Mass Storage works fine on the same phone when it's plugged in. Fastboot works too. Only adb fails. Le 24/03/2015 19:41, Julien Wajsberg a écrit : Hi, I have a big issue with adb: it can't see any of my phones. adb devices returns an empty list. It came all of a sudden: I updated nothing, it just appeared today. This morning it worked, this afternoon it doesn't. The funniest (in a sense) is that it happens on both my computers, both running Debian Jessie. It stopped working on one of them last week, and on the second one only today. I already tried to do the usual checks: udev rules, run as root, kill-server, check that no other adb was running, reboot the computer, update Android SDK, try other phones, try other cables: no luck. (same phone, same cable, on another computer: works fine). I tried removing MTP support and ModemManager (thinking this might interfere) but it brought no improvement. Paul Adenot helped me debugging a little more using ADB_TRACE=1 and strace and looking at the source code for adb. Here are the logs for what I found: $ ADB_TRACE=1 adb -P 5037 fork-server server system/core/adb/adb.c::main():Handling commandline() system/core/adb/transport_local.c::local_init():transport: local client init system/core/adb/usb_linux.c::device_poll_thread():Created device thread system/core/adb/adb_auth_host.c::adb_auth_init():adb_auth_init system/core/adb/adb_auth_host.c::get_user_keyfilepath():home '/home/julien' system/core/adb/transport_local.c::client_socket_thread():transport: client_socket_thread() starting system/core/adb/adb_auth_host.c::get_user_key():user key '/home/julien/.android/adbkey' system/core/adb/adb_auth_host.c::read_key():read_key '/home/julien/.android/adbkey' system/core/adb/usb_linux.c::register_device():[ usb located new device /dev/bus/usb/001/100 (130/2/1) ] system/core/adb/usb_linux.c::register_device():[ usb open /dev/bus/usb/001/100 fd = 8] system/core/adb/usb_linux.c::register_device():[ usb open /dev/bus/usb/001/100 error=16, err_str = Device or resource busy] OK The error seems to happen when the code tries to run ioctl with USBDEVFS_CLAIMINTERFACE [1]. [1] http://androidxref.com/5.1.0_r1/xref/system/core/adb/usb_linux.c#609 This likely means that something else is already claiming this interface, but I don't
Re: [b2g] Problem with adb
On the same computer, my Open C (v2.1) and a Z3 (master) work fine with adb. So this is somehow an incompatibility between the Flames' adb and my configuration. Le 25/03/2015 14:50, Julien Wajsberg a écrit : Additional info: using a Live USB version of Ubuntu, I could make adb work flawlessly. So something is really happening in Debian :/ Le 24/03/2015 19:54, Julien Wajsberg a écrit : I'd like to add that Mass Storage works fine on the same phone when it's plugged in. Fastboot works too. Only adb fails. Le 24/03/2015 19:41, Julien Wajsberg a écrit : Hi, I have a big issue with adb: it can't see any of my phones. adb devices returns an empty list. It came all of a sudden: I updated nothing, it just appeared today. This morning it worked, this afternoon it doesn't. The funniest (in a sense) is that it happens on both my computers, both running Debian Jessie. It stopped working on one of them last week, and on the second one only today. I already tried to do the usual checks: udev rules, run as root, kill-server, check that no other adb was running, reboot the computer, update Android SDK, try other phones, try other cables: no luck. (same phone, same cable, on another computer: works fine). I tried removing MTP support and ModemManager (thinking this might interfere) but it brought no improvement. Paul Adenot helped me debugging a little more using ADB_TRACE=1 and strace and looking at the source code for adb. Here are the logs for what I found: $ ADB_TRACE=1 adb -P 5037 fork-server server system/core/adb/adb.c::main():Handling commandline() system/core/adb/transport_local.c::local_init():transport: local client init system/core/adb/usb_linux.c::device_poll_thread():Created device thread system/core/adb/adb_auth_host.c::adb_auth_init():adb_auth_init system/core/adb/adb_auth_host.c::get_user_keyfilepath():home '/home/julien' system/core/adb/transport_local.c::client_socket_thread():transport: client_socket_thread() starting system/core/adb/adb_auth_host.c::get_user_key():user key '/home/julien/.android/adbkey' system/core/adb/adb_auth_host.c::read_key():read_key '/home/julien/.android/adbkey' system/core/adb/usb_linux.c::register_device():[ usb located new device /dev/bus/usb/001/100 (130/2/1) ] system/core/adb/usb_linux.c::register_device():[ usb open /dev/bus/usb/001/100 fd = 8] system/core/adb/usb_linux.c::register_device():[ usb open /dev/bus/usb/001/100 error=16, err_str = Device or resource busy] OK The error seems to happen when the code tries to run ioctl with USBDEVFS_CLAIMINTERFACE [1]. [1] http://androidxref.com/5.1.0_r1/xref/system/core/adb/usb_linux.c#609 This likely means that something else is already claiming this interface, but I don't know how to find out where this comes from. For the record, here is the log when this works fine (from another computer -- you'll easily find out whose computer it is ;) ): $ ADB_TRACE=1 adb -P 5037 fork-server server adb.c::main():Handling commandline() transport_local.c::local_init():transport: local client init usb_linux.c::device_poll_thread():Created device thread adb_auth_host.c::adb_auth_init():adb_auth_init transport_local.c::client_socket_thread():transport: client_socket_thread() starting adb_auth_host.c::get_user_keyfilepath():home '/home/jlorenzo' adb_auth_host.c::get_user_key():user key '/home/jlorenzo/.android/adbkey' adb_auth_host.c::read_key():read_key '/home/jlorenzo/.android/adbkey' usb_linux.c::register_device():[ usb located new device /dev/bus/usb/002/124 (130/2/1) ] OK usb_linux.c::register_device():[ usb open /dev/bus/usb/002/124 fd = 10] So it's really comparable except there is no error. Hope someone will be able to help me here, I'm quite stuck :/ Regards, signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Problem with adb
Additional info: using a Live USB version of Ubuntu, I could make adb work flawlessly. So something is really happening in Debian :/ Le 24/03/2015 19:54, Julien Wajsberg a écrit : I'd like to add that Mass Storage works fine on the same phone when it's plugged in. Fastboot works too. Only adb fails. Le 24/03/2015 19:41, Julien Wajsberg a écrit : Hi, I have a big issue with adb: it can't see any of my phones. adb devices returns an empty list. It came all of a sudden: I updated nothing, it just appeared today. This morning it worked, this afternoon it doesn't. The funniest (in a sense) is that it happens on both my computers, both running Debian Jessie. It stopped working on one of them last week, and on the second one only today. I already tried to do the usual checks: udev rules, run as root, kill-server, check that no other adb was running, reboot the computer, update Android SDK, try other phones, try other cables: no luck. (same phone, same cable, on another computer: works fine). I tried removing MTP support and ModemManager (thinking this might interfere) but it brought no improvement. Paul Adenot helped me debugging a little more using ADB_TRACE=1 and strace and looking at the source code for adb. Here are the logs for what I found: $ ADB_TRACE=1 adb -P 5037 fork-server server system/core/adb/adb.c::main():Handling commandline() system/core/adb/transport_local.c::local_init():transport: local client init system/core/adb/usb_linux.c::device_poll_thread():Created device thread system/core/adb/adb_auth_host.c::adb_auth_init():adb_auth_init system/core/adb/adb_auth_host.c::get_user_keyfilepath():home '/home/julien' system/core/adb/transport_local.c::client_socket_thread():transport: client_socket_thread() starting system/core/adb/adb_auth_host.c::get_user_key():user key '/home/julien/.android/adbkey' system/core/adb/adb_auth_host.c::read_key():read_key '/home/julien/.android/adbkey' system/core/adb/usb_linux.c::register_device():[ usb located new device /dev/bus/usb/001/100 (130/2/1) ] system/core/adb/usb_linux.c::register_device():[ usb open /dev/bus/usb/001/100 fd = 8] system/core/adb/usb_linux.c::register_device():[ usb open /dev/bus/usb/001/100 error=16, err_str = Device or resource busy] OK The error seems to happen when the code tries to run ioctl with USBDEVFS_CLAIMINTERFACE [1]. [1] http://androidxref.com/5.1.0_r1/xref/system/core/adb/usb_linux.c#609 This likely means that something else is already claiming this interface, but I don't know how to find out where this comes from. For the record, here is the log when this works fine (from another computer -- you'll easily find out whose computer it is ;) ): $ ADB_TRACE=1 adb -P 5037 fork-server server adb.c::main():Handling commandline() transport_local.c::local_init():transport: local client init usb_linux.c::device_poll_thread():Created device thread adb_auth_host.c::adb_auth_init():adb_auth_init transport_local.c::client_socket_thread():transport: client_socket_thread() starting adb_auth_host.c::get_user_keyfilepath():home '/home/jlorenzo' adb_auth_host.c::get_user_key():user key '/home/jlorenzo/.android/adbkey' adb_auth_host.c::read_key():read_key '/home/jlorenzo/.android/adbkey' usb_linux.c::register_device():[ usb located new device /dev/bus/usb/002/124 (130/2/1) ] OK usb_linux.c::register_device():[ usb open /dev/bus/usb/002/124 fd = 10] So it's really comparable except there is no error. Hope someone will be able to help me here, I'm quite stuck :/ Regards, signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Problem with adb
I managed to work around the issue. I'll explain the cause and the solution I found so that anybody getting this issue in the future could find a possible solution in the list's archives. It looks like my issues came from the linux kernel module option, which is a driver for some USB 3G dongles. It looks like that the Flame (and Buri which had the same issue) triggered the loading of this module. The downside is that the module didn't work at all, filled the kernel log with messages (especially its dependencies usb_wwan and qmi_wwan). Moreover when halting the computer there was very often a kernel crash stacktrace (I took a picture of it in case it could be useful). When running /sbin/lsmod | grep option you could also look at the Used by column to see that the number was constantly increasing. The solution I used is backlisting the module. I did this by adding a file /etc/modprobe.d/option.conf with the following content: install option /bin/false Simply using blacklist option did not seem to work. I think some Debian component changed the way to load modules recently and as a result the blacklist keyword does not work in this situation (and this could be what provoked my issues in the first place). Then I ran depmod -ae and update-initramfs -u as advised on websites (but I'm not that sure it's useful), and rebooted. And tada, the option module is not autoloaded anymore and adb devices works ! I'll file a bug to Debian soon, hopefully this can be fixed on their side. Thanks to all the people who helped me :) Le 25/03/2015 15:00, Julien Wajsberg a écrit : On the same computer, my Open C (v2.1) and a Z3 (master) work fine with adb. So this is somehow an incompatibility between the Flames' adb and my configuration. Le 25/03/2015 14:50, Julien Wajsberg a écrit : Additional info: using a Live USB version of Ubuntu, I could make adb work flawlessly. So something is really happening in Debian :/ Le 24/03/2015 19:54, Julien Wajsberg a écrit : I'd like to add that Mass Storage works fine on the same phone when it's plugged in. Fastboot works too. Only adb fails. Le 24/03/2015 19:41, Julien Wajsberg a écrit : Hi, I have a big issue with adb: it can't see any of my phones. adb devices returns an empty list. It came all of a sudden: I updated nothing, it just appeared today. This morning it worked, this afternoon it doesn't. The funniest (in a sense) is that it happens on both my computers, both running Debian Jessie. It stopped working on one of them last week, and on the second one only today. I already tried to do the usual checks: udev rules, run as root, kill-server, check that no other adb was running, reboot the computer, update Android SDK, try other phones, try other cables: no luck. (same phone, same cable, on another computer: works fine). I tried removing MTP support and ModemManager (thinking this might interfere) but it brought no improvement. Paul Adenot helped me debugging a little more using ADB_TRACE=1 and strace and looking at the source code for adb. Here are the logs for what I found: $ ADB_TRACE=1 adb -P 5037 fork-server server system/core/adb/adb.c::main():Handling commandline() system/core/adb/transport_local.c::local_init():transport: local client init system/core/adb/usb_linux.c::device_poll_thread():Created device thread system/core/adb/adb_auth_host.c::adb_auth_init():adb_auth_init system/core/adb/adb_auth_host.c::get_user_keyfilepath():home '/home/julien' system/core/adb/transport_local.c::client_socket_thread():transport: client_socket_thread() starting system/core/adb/adb_auth_host.c::get_user_key():user key '/home/julien/.android/adbkey' system/core/adb/adb_auth_host.c::read_key():read_key '/home/julien/.android/adbkey' system/core/adb/usb_linux.c::register_device():[ usb located new device /dev/bus/usb/001/100 (130/2/1) ] system/core/adb/usb_linux.c::register_device():[ usb open /dev/bus/usb/001/100 fd = 8] system/core/adb/usb_linux.c::register_device():[ usb open /dev/bus/usb/001/100 error=16, err_str = Device or resource busy] OK The error seems to happen when the code tries to run ioctl with USBDEVFS_CLAIMINTERFACE [1]. [1] http://androidxref.com/5.1.0_r1/xref/system/core/adb/usb_linux.c#609 This likely means that something else is already claiming this interface, but I don't know how to find out where this comes from. For the record, here is the log when this works fine (from another computer -- you'll easily find out whose computer it is ;) ): $ ADB_TRACE=1 adb -P 5037 fork-server server adb.c::main():Handling commandline() transport_local.c::local_init():transport: local client init usb_linux.c::device_poll_thread():Created device thread adb_auth_host.c::adb_auth_init():adb_auth_init transport_local.c::client_socket_thread():transport: client_socket_thread() starting adb_auth_host.c::get_user_keyfilepath():home '/home/jlorenzo' adb_auth_host.c::get_user_key():user key '/home/jlorenzo
Re: [b2g] Problem with adb
Le 25/03/2015 17:20, Christof Meerwald a écrit : On Wed, 25 Mar 2015 16:19:38 +0100, Julien Wajsberg wrote: [...] It looks like my issues came from the linux kernel module option, which is a driver for some USB 3G dongles. It looks like that the Flame (and Buri which had the same issue) triggered the loading of this module. Do you have USB tethering enabled on these phones? No I didn't. But USB tethering is different than the option driver, from what I understand. USB tethering share the network connection established by the phone, while the option driver can access the SIM card directly. I don't know if that really works with our phones. signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Problem with adb
I'd like to add that Mass Storage works fine on the same phone when it's plugged in. Fastboot works too. Only adb fails. Le 24/03/2015 19:41, Julien Wajsberg a écrit : Hi, I have a big issue with adb: it can't see any of my phones. adb devices returns an empty list. It came all of a sudden: I updated nothing, it just appeared today. This morning it worked, this afternoon it doesn't. The funniest (in a sense) is that it happens on both my computers, both running Debian Jessie. It stopped working on one of them last week, and on the second one only today. I already tried to do the usual checks: udev rules, run as root, kill-server, check that no other adb was running, reboot the computer, update Android SDK, try other phones, try other cables: no luck. (same phone, same cable, on another computer: works fine). I tried removing MTP support and ModemManager (thinking this might interfere) but it brought no improvement. Paul Adenot helped me debugging a little more using ADB_TRACE=1 and strace and looking at the source code for adb. Here are the logs for what I found: $ ADB_TRACE=1 adb -P 5037 fork-server server system/core/adb/adb.c::main():Handling commandline() system/core/adb/transport_local.c::local_init():transport: local client init system/core/adb/usb_linux.c::device_poll_thread():Created device thread system/core/adb/adb_auth_host.c::adb_auth_init():adb_auth_init system/core/adb/adb_auth_host.c::get_user_keyfilepath():home '/home/julien' system/core/adb/transport_local.c::client_socket_thread():transport: client_socket_thread() starting system/core/adb/adb_auth_host.c::get_user_key():user key '/home/julien/.android/adbkey' system/core/adb/adb_auth_host.c::read_key():read_key '/home/julien/.android/adbkey' system/core/adb/usb_linux.c::register_device():[ usb located new device /dev/bus/usb/001/100 (130/2/1) ] system/core/adb/usb_linux.c::register_device():[ usb open /dev/bus/usb/001/100 fd = 8] system/core/adb/usb_linux.c::register_device():[ usb open /dev/bus/usb/001/100 error=16, err_str = Device or resource busy] OK The error seems to happen when the code tries to run ioctl with USBDEVFS_CLAIMINTERFACE [1]. [1] http://androidxref.com/5.1.0_r1/xref/system/core/adb/usb_linux.c#609 This likely means that something else is already claiming this interface, but I don't know how to find out where this comes from. For the record, here is the log when this works fine (from another computer -- you'll easily find out whose computer it is ;) ): $ ADB_TRACE=1 adb -P 5037 fork-server server adb.c::main():Handling commandline() transport_local.c::local_init():transport: local client init usb_linux.c::device_poll_thread():Created device thread adb_auth_host.c::adb_auth_init():adb_auth_init transport_local.c::client_socket_thread():transport: client_socket_thread() starting adb_auth_host.c::get_user_keyfilepath():home '/home/jlorenzo' adb_auth_host.c::get_user_key():user key '/home/jlorenzo/.android/adbkey' adb_auth_host.c::read_key():read_key '/home/jlorenzo/.android/adbkey' usb_linux.c::register_device():[ usb located new device /dev/bus/usb/002/124 (130/2/1) ] OK usb_linux.c::register_device():[ usb open /dev/bus/usb/002/124 fd = 10] So it's really comparable except there is no error. Hope someone will be able to help me here, I'm quite stuck :/ Regards, signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Problem with adb
Le 24/03/2015 20:12, kgu...@mozilla.com a écrit : On Tuesday, March 24, 2015 at 2:55:53 PM UTC-4, Julien Wajsberg wrote: I have a big issue with adb: it can't see any of my phones. adb devices returns an empty list. It came all of a sudden: I updated nothing, it just appeared today. This morning it worked, this afternoon it doesn't. The funniest (in a sense) is that it happens on both my computers, both running Debian Jessie. It stopped working on one of them last week, and on the second one only today. I've noticed problems where the ADB helper add-on installed/started by WebIDE interferes with my command-line ADB usage. In the end I just manually removed that add-on from all my Firefox profiles and do a manual port-forwarding when I want to use WebIDE. If you've been trying so far while Firefox is running, maybe try closing Firefox, doing an adb kill-server, and then trying again? Yep, I tried this too :) I disabled ADB Helper just to filter this as a possible issue (not that I got any issue with this recently). signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Update on Web Components
Hey, here is a little piece of feedback. I tried using HTML imports for Web Components recently [1], and it actually worked well and was quite nice to use without any framework. I can understand why React and such don't care about this, but if we want to stay closer to the metal it's a useful piece of spec. However there is a real performance impact when loading it: first we need to load the imported HTML file, then the JS and CSS files inside the import, then use registerElement on the main document, and only then the component is usable. Clearly the performance issue would need to be fixed for HTML Imports + Web Components to be adopted. [1] https://github.com/mozilla-b2g/gaia/compare/master...julienw:simple-header#diff-56289627d91906a9c3b0f834ef19f514 Le 05/03/2015 12:28, Anne van Kesteren a écrit : I thought it might be good to give a quick update. As announced https://hacks.mozilla.org/2014/12/mozilla-and-web-components/ we're not doing HTML imports. We have not found an internal need and feedback from Ember, React, and peers in the standards community suggest that iterating on JavaScript modules and new fetching primitives is sufficient for now. For custom elements and shadow DOM there's documents where we keep track of outstanding issues: * https://wiki.whatwg.org/wiki/Custom_Elements * https://github.com/w3c/webcomponents/wiki/Shadow-DOM:-Contentious-Bits Unfortunately it does not look like agreement will be found soon. The high-level bit of feedback that keeps coming back is that we need to find a way to get layout fast and code more manageable. How exactly we should get there is still unclear. There will be a meeting https://lists.w3.org/Archives/Public/public-webapps/2015JanMar/0661.html (April 24, Mountain View) to discuss shadow DOM in particular and perhaps http://lanyrd.com/2015/extwebsummit/ (April 19, San Francisco) can also be used as a discussion venue. We have had some discussions around within Mozilla in Portland. Perhaps we should have another one over Vidyo? Hearing from Gaia again now v3 is underway would be useful. (Tentative suggestion: Thursday March 12, 9AM PST.) signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Presentation on Dogfooding Program
Le 18/02/2015 11:46, Michael Henretty a écrit : On Wed, Feb 18, 2015 at 12:37 AM, Frederik Braun fbr...@mozilla.com mailto:fbr...@mozilla.com wrote: I had the impression a lot of components just don't have any people watching them. :/ Is triage a program manager job? I honestly wouldn't even know whom to poke.. The unfortunate truth here is that unless a bug get's nominated to block a release, it might never get looked out. There are some nice module owners that follow their component and triage the new bugs that come in (see Julien's email above), but this level of attention is not uniform across the FxOS components. I agree this is a huge problem and we need to fix it if dogfooding is to be effective. I'd argue that it's also important for our other users. Not only for dogfooding. As a corollary, if a bug does not get marked to block a release, the chances of it getting worked on/fixed are relatively small since resources are already constrained for blockers. The end result is we get a lot of papercut bugs [1] that everyone is aware of but nobody has the time to fix. Nobody has any time for anything. But the good thing is that time can be taken :) If you spend 1 week fixing an important performance bug, maybe you can take 2 hours in this week to fix this papercut bug. (and it will really take ~0.5 days including review and fixing review comments). If every member of the team fixes a papercut bug each week... we'll be in a good shape :) I don't think we need much more process to fix these. We only need to acknowledge that some bugs will fill in all the available time you have, regardless of how much time you have. So you need to reclaim part of this time to work on these bugs that don't work like this, and papercut bugs are these bugs. Leveraging the community with mentored bugs only solves part of the problem. The other part would be a greater focus on polishing our existing experience vs. adding new features. It's tough though, eg. do we take the time to add email thread grouping, or should we focus on list scrolling performance? We are already playing catch up to products that have vastly more resources, so the reality is we must both add new features and polishing existing ones simultaneously. This is why dogfooding across ALL of Mozilla (developers, UX, marketplacers, platformers, EVERYONE) is so important. Only with everyone feeling the pain can we make the most informed decision about what are the important polish bugs and features. Making far reaching decisions about the future of our device without intimate knowledge of what it's like to use our phone on a daily bases is the opposite of helpful. We need everyone dogfooding. Yes. -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Presentation on Dogfooding Program
Le 18/02/2015 09:37, Frederik Braun a écrit : I must admit that I have a backlog of screenshots which show bugs or misbehavior. Streamlining this into a dogfooding mode (could this be a (developer) setting?) would be highly appreciated from my side! Triage is another problem, I have observed while dogfooding. I think I am dogfooding for more than a year and most bugs never get touched. I had the impression a lot of components just don't have any people watching them. :/ Is triage a program manager job? I honestly wouldn't even know whom to poke.. And this is wrong. Every component should have someone (or a group) who triages on a regular basis. There are different ways to do this: * watching the component and handle the pile of mails (that's what I do) * having a triage session every week, looking at new bugs and new comments in a group Here is a flow chart I made that could help you triaging: https://wiki.mozilla.org/images/2/29/Sms-bug-handling-flow.svg It's far from perfect (and has some SMS-specific actions), but as you can see a pivotal brick in this chart is the brick named bug will not be forgotten. This is basically my main goal for my own empirical triaging process. On 17.02.2015 16:13, Dale Harvey wrote: Thanks to Julien for sending me a presentation some of the Paris team created about dogfooding https://slack-files.com/T033ZPYCR-F03E146ML-d7f0104d94 It touches on a lot of similiar things I mentioned previously about an easier bug reporting process etc ___ 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 signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Presentation on Dogfooding Program
Le 18/02/2015 18:12, Sebastian Hengst a écrit : Problem 2: communication (bug reporting activity per user) The suggested on-phone reporting can vastly improve the number of reports, but will lower the quality. People will likely write less on a phone, e.g. less steps for reproducing or regard the screenshot as obvious. So the marginal costs for the bug triage will go up (I also expect less efficiency when showing already filed bugs). Yeah, you're right, when writing the presentation we were not completely sure whether this should link directly to bugzilla or to another box, for this reason Problem 3: action As mentioned, the dominant impression is that bugs don't get touched because developers are busy with the cramped roadmap which doesn't leave enough time for fixing issues found later (and some of which can be regarded as blockers). It's noticeable when an organized bug triager gets assigned to a different tasks (e.g. nhirata, kgrandon). So, how should existing and new incoming bugs be managed better, in a way which encourages further contribution and that it's worth investing one's time into bug filing. I think we can try to leverage the community here. Triaging bugs is not very hard to do and takes as much time as you want to give. So it looks to be a good fit. What we (Mozilla) need to do is links to proper triaging buglists, and proper triaging rules (like I did in https://wiki.mozilla.org/images/2/29/Sms-bug-handling-flow.svg but that's a little too much SMS specific). -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Granting Permissions to the Web
Hey Paul, Le 09/02/2015 12:41, Paul Theriault a écrit : === SMS === SMS is risky mainly due to the cost involved. Risks include cost of sending SMS and also SMS are very sensitive - e.g. often used in 2-factor auth (e.g. banking) But there are different use cases. For example, many use cases just need the ability to receive SMS - instead of granting SMS permission, we could expose a read-only SMS datastore which other apps could observe changes on which removes the cost risk (but not the sensitive data risk). I don't understand how having a read only access would prevent a webpage from reading a 2-factor auth SMS. I wonder if we could have a permission as fine as giving access to a specific thread ? Or access to some properties (the phone numbers) but not others (the SMS content) ? I'm also not sure how a user can choose knowingly whether he should give access to such things from this webpage :/ signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] GCC version to build Firefox OS
I think GCC 4.6 is needed for ICS-based builds. Le 28/01/2015 11:07, Shian-Yow Wu a écrit : The MDN suggests setting gcc version to 4.6 to build Firefox OS. https://developer.mozilla.org/en-US/Firefox_OS/Firefox_OS_build_prerequisites https://developer.mozilla.org/en-US/Firefox_OS/Customization_with_the_.userconfig_file#Changing_the_default_host_compiler On latest mozilla central, however, when building gecko there could be error with this setting. Below is the error when building gecko on Ubuntu 14.04 using gcc 4.6. 0:09.19 ../../../../dist/include/GMPUtils.h:22:1: error: expected unqualified-id before ‘using’ To solve this, either use gcc 4.6 with --std=c++11 option, or upgrade to gcc 4.7 or later(thanks to Tommy Kuo for this info). Do we still need gcc 4.6 as Firefox OS build prerequisite? If not, probably we should remove this part from MDN. -- Shian-Yow ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Flame completely dead
Le 24/11/2014 06:22, Tucker McKnight a écrit : A couple of days ago, my Flame turned off, and it won't turn on. I can't get a boot screen or anything. It has done this a couple of times in the past; both times I took the battery out, then put the battery back in, and it was fine. This time that didn't work. I've tried plugging in the USB cable, but there is no indication that it is charging. It also doesn't show up with adb devices or fastboot devices. Holding volume up + power, or volume down + power doesn't do anything, either. I'd had 2.0-prelease on it for a few weeks, and I hadn't recently changed anything about it. I'm hoping it's just the battery. Does anyone have any ideas as to what could be going wrong, or what I could do about it? Here are my 2 cents: I know that if the battery is really _really_ empty, you need to charge it for some minutes before you can do anything with the phone. I think you don't even see the charging animation when the battery is that empty. -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Updated firmware for ZTE Open C?
Le 21/11/2014 21:15, Christof Meerwald a écrit : Hi, is there an easy way (that means not having to build it myself) to install an up-to-date firmware on the ZTE Open C? A few days ago I stumbled across http://paulrouget.com/e/openc/ which seems to suggest that you can just install Flame builds, but the builds linked from that page are now also a bit outdated - I guess this is because the Flame builds have moved to a KitKat base which isn't compatible with the ZTE Open C any more... Any ideas? If you use the ZTE Open C sold in France, there are some experimental builds made by the french community there: http://builds.firefoxos.mozfr.org/ I'm not aware of other similar experimentations for the EBay version. -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] getUserMedia front camera rotation issue
Le 13/11/2014 19:46, jorr...@gmail.com a écrit : Hello, When request video stream from gum on front camera I've noticed that image rotate in a weird way: - rotate 90 deg a put in landscape, the image is rotated 180 deg. - rotate 180 deg a put in portrait inverted, the image is rotated 360 deg. If you do the same operation with back camera all feels right. There is no rotation of image in the same way the Camera App does. Does anyone any clue if that is the expected behavior or it's a bug? I doubt this is expected, please file a bug on bugzilla :) Thanks, -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Flame loses language settings after OTA update
Le 15/11/2014 13:58, Paul a écrit : All, I updated my (completely stock 1.3) Flame this week to 2.0 with the OTA update. After booting I noticed that the language settings to choose from have been reduced to only 6 options (with English(US) as only acceptable option) and I was unable to choose Dutch. Since the auto-correct dictionaries and date-time settings are linked to the language the phone feels a bit awkward and less user friendly. (On a side note, I don't really understand the firm coupling between language and date/time settings but that's not my question ;-)) Is there a way to add languages? Or do I have to resort to manually flashing the phone to another 2.0 image? Please file a bug about this, I don't think this is appropriate to lose languages on an update if they were previously available :/ -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Accessing Disk in B2G Desktop client
Le 14/11/2014 19:35, sirajul muneer a écrit : Hi, I've built the B2G Desktop client using this documentation https://developer.mozilla.org/en-US/Firefox_OS/Building_the_B2G_desktop_client and its working good. I wish to modify the music app. When I open up the application it says 'Add Songs to the memory card'. I expected it to load or list music files in my hard-disk, at least from my home folder. But when I take up the Gallery app, it loads and lists the images files from the hard-disk. Is there a way to make both the apps to work in a similar way ? Which OS do you use? I think (but I'm not sure) that on Linux we use the default Music directory to list these files. -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Gaia is CLOSED
Le 13/11/2014 08:58, Kevin Grandon a écrit : Gaia is closed again as of this morning for Gij bustage. https://bugzilla.mozilla.org/show_bug.cgi?id=1098155 Getting Gij unhidden is our top priority right now, and it's getting close. This should avoid these closures in the future. And FWIW a yet-unknown change to Firefox broke running app://, and thus is breaking running the test-agent through bin/gaia-test, or running your apps in Firefox. In the mean time, you can use http://app.gaiamobile.org:8080 instead of app://app.gaiamobile.org. You could have weird behaviors though. (this is tracked in bug 1097912 https://bugzilla.mozilla.org/show_bug.cgi?id=1097912) signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] It maybe possible to fall into a state where mozSettings is broken for the entire phone
Le 13/11/2014 15:50, Tim Chien a écrit : I was working bug 1098124 today, and I encounter a situation where mozSettings simply breaks. For the entire phone for all apps. Probing with breakpoints in the app I found that all DOMRequests for set() and get() simply never resolves. Calling additional set() does not reproduce any logcat. Not being able to come out with anything useful, I eventually reboot the machine and bring it back to the normal state. The phone was running latest OTA version. This is pretty serious because in many apps Gaia rely on mozSettings to return before doing anything else. Without working mozSettings we will see issues like bug 1093121. Unfortunately this is not reproducible in any way. It might only because I keep |APP=keyboard make install-gaia| which kills the app from time to time during development. Since there is nothing useful here I decide to e-mail instead of filing a bug. The other thing to ask is whether or not Gaia should defend against this kind of API breakage. Should I wrap a setTimeout() around the set() request and recover when it never returns? The code is going to be ugly but at least the keyboard would show up I just want to note that there is an IndexedDB deadlock being worked on by Bent these days, see https://bugzilla.mozilla.org/show_bug.cgi?id=1078438. I don't know at all if this is related, but this could be. -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Roadmap
Le 12/11/2014 21:54, Marek Raida a écrit : I'd personally like to know what's next as well... but honestly, I see current 2.2 development in such a turmoil that I'd prefer some stability and performance phase rather than adding new features or more UX GUI refreshes. So simply stating we will focus on B/S/P only + Gecko upgrade will be ebough for me personally. UI is IMHO quite good enough already, but bugbashing/stabilityperf. is what is needed/FFOS suffering the most... Lately, OTA 2.2 updates happen with reboot without asking for SIM PIN again (very strange security behavior/decision), but STK menu/functions is completely inaccessible then, so I need another restart to enable it, hmm... This is a bug :) Could be https://bugzilla.mozilla.org/show_bug.cgi?id=1090859 And keyboard latency/issues I see as mayor thing to fix soon, because I'm in frustration sometimes (not able to write SMS/email) considering swapping FirefoxOS for something speedier and more stable Did you see regressions lately? Was it working better in the past? Which device do you use? -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] building emulator - /usr//bin/usr/ld:bin /cannotld :find -cannotlGL
you can do this, assuming you did a ./config.sh emulator-jb beforehand:
cd sdk ( curl
https://bug897727.bugzilla.mozilla.org/attachment.cgi?id=786280 | patch
-p1 )
it worked for me :)
Le 30/10/2014 06:55, Techno Buddha a écrit :
Hello Ryan,
Thanks for your time.
I would love to do #2, but I'm confused on how to use the patch!
I thought maybe patch -i {file}
but I get an error saying the files don't exist?
--- a/emulator/opengl/host/libs/GLESv1_dec/Android.mk
+++ b/emulator/opengl/host/libs/GLESv1_dec/Android.mk
so not to sure how to patch..
suggestions?
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
signature.asc
Description: OpenPGP digital signature
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] building emulator - /usr//bin/usr/ld:bin /cannotld :find -cannotlGL
note: the command is supposed to be on one line, sorry my mail agent
scrambled it ;)
Le 30/10/2014 12:18, Julien Wajsberg a écrit :
you can do this, assuming you did a ./config.sh emulator-jb beforehand:
cd sdk ( curl
https://bug897727.bugzilla.mozilla.org/attachment.cgi?id=786280 | patch
-p1 )
it worked for me :)
Le 30/10/2014 06:55, Techno Buddha a écrit :
Hello Ryan,
Thanks for your time.
I would love to do #2, but I'm confused on how to use the patch!
I thought maybe patch -i {file}
but I get an error saying the files don't exist?
--- a/emulator/opengl/host/libs/GLESv1_dec/Android.mk
+++ b/emulator/opengl/host/libs/GLESv1_dec/Android.mk
so not to sure how to patch..
suggestions?
___
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
signature.asc
Description: OpenPGP digital signature
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Firefox 2.0 on fresh Flame on MacOS 10.10 Yosemite?
Le 27/10/2014 19:11, Patrick a écrit : Hi there, I just got my Flame and want to flash it right away with FFOS 2.0. Downloaded Flame_2.0_v180_1.zip and followed the instructions https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame. My machine is already set up for Android development so adb was installed and working. $ adb devices List of devices attached 1b37c28f device $ sudo ./flash.sh Password: * daemon not running. starting it now on port 5037 * * daemon started successfully * List of devices attached error: device not found error: device not found Partition table... waiting for device $ adb devices List of devices attached Nothing ever happens on the device. I tried 3 different USB cables and I'm out of ideas. Any suggestions? So, when you start ./flash.sh, the first thing it does is that it uses adb to reboot the device in fastboot mode (adb reboot bootloader). So it's normal that you don't see the device with adb devices anymore but you should see it with fastboot devices instead. If you don't see it, it may mean that your udev rules are not complete. Another possibility is that I see you use sudo to run flash.sh. Really, this is not necessary if the udev rules are correctly setup. Do you often use sudo to run stuff you download on Internet? This is extra-dangerous... I just changed MDN with updated information for udev and the running the flash script, maybe you can have another look now. Regards, -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Flash application into emulator through termianl
Le 26/10/2014 14:33, Louis_Chang a écrit : As mention in title, do anyone know how can i flash my application into emulator through terminal(./flash.sh)? Now i have a b2g(built for emulator) and an application, but i don't know where to put my application in the b2g. (I'm now working on Ubuntu 12.04 64bits) The emulator works just like a normal device, so you should flash to it using adb. -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Flame OTA support
Le 28/10/2014 10:28, Stephen Murphy a écrit : Hey, IS there any support for the Flame to update via OTA? I have flashed 2.0 and keep getting a system update which does not update and prompts me to download the update over and over. Hey, I just want to know which 2.0 version you did flash? Where did you take the flash package? Thanks signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] AGPS on Open C
The fact is that some shallow flash scripts try to replace the RIL. I
think one reason is that QC RIL doesn't always work properly on
non-release branches.
Le 21/10/2014 12:55, Panos Astithas a écrit :
Interesting, I thought the RIL would be part of gonk and therefore
unaffected by shallow flash. Isn't there a build/configure time option
to select which RIL to use? Shouldn't there be? (I might try to add it
if so).
In the phones without QC silicon, don't we use AGPS for MLS? If not, I
suppose there must be a way to configure gecko to use MLS, right?
About the workaround to stick with the base image, ZTE comes with 1.3
and there is no 2.0 to the best of my knowledge. Did you perhaps mean
that flashing 2.0 won't stomp on QC RIL, whereas flashing 2.1 will? If
so, I will certainly try that.
Thanks,
Panos
On Tue, Oct 21, 2014 at 3:31 AM, Asa Dotzler a...@mozilla.com
mailto:a...@mozilla.com wrote:
I believe that this is an issue with how we shallow flash.
A shallow flash of Gecko/Gaia stomps on the QC RIL and A-GPS code,
replacing it with MozRIL (and no A-GPS alternative.)
There are two potential solutions here. One, we ask QC to move
that code to a different place in OS so it's not part of the RIL
stack that gets replaced. Two, we provide an alternative A-GPS
service.
The only workaround today I can think of is to stick with the base
image that includes the QC code, avoiding the move to nightly and
sticking with the 2.0 base image.
- A
On 10/20/14, 1:14 PM, Panos Astithas wrote:
Hi all,
I have an Open C shallow-flashed to latest v2.1 and everything
about it
seems fine, except for AGPS. When I'm indoors, HERE Maps
always fails to
find my location and logcat contains a bunch of these:
E/GeckoConsole( 286): [JavaScript Error:
NS_ERROR_XPC_CANT_CREATE_WN:
Component returned failure code: 0x80570019
(NS_ERROR_XPC_CANT_CREATE_WN) [nsIJSCID.getService] {file:
jar:file:///system/b2g/omni.ja!/components/NetworkGeolocationProvider.js
line: 332}]
E/LocSvc_eng( 286): I/=== int loc_eng_init(loc_eng_data_s_type,
LocCallbacks*, LOC_API_ADAPTER_EVENT_MASK_T,
loc_core::ContextBase*)
line 1463
E/LocSvc_api_v02( 286): I/--- locClientOpen line 1941 loc
client open
E/Diag_Lib( 286): Setting internal use port to rmnet0
E/LocSvc_eng( 286): I/=== void
loc_eng_agps_init(loc_eng_data_s_type,
AGpsExtCallbacks*) line 2004
E/LocSvc_eng( 286): I/=== int
loc_eng_set_server_proxy(loc_eng_data_s_type, LocServerType,
const
char*, int) line 2294
E/LocSvc_eng( 286): I/=== int
loc_eng_set_position_mode(loc_eng_data_s_type, LocPosMode)
line 1772
E/LocSvc_eng( 286): I/=== int
loc_eng_start(loc_eng_data_s_type) line
1648
E/LocSvc_api_v02( 286): I/--- locClientSendReq line 2144
QMI_LOC_REG_EVENTS_REQ_V02
E/LocSvc_ApiV02( 286): W/[ZTE-GPS] efs file doesn`t exist in
ARM9 need
to inject
E/LocSvc_ApiV02( 286): W/[ZTE-GPS] Create cert file
E/LocSvc_ApiV02( 286): W/[ZTE-GPS] certfilesize=0
E/LocSvc_ApiV02( 286): W/[ZTE-GPS] No cer file
Here is a pastebin with a more complete log; does anyone know
what the
problem is?
http://past.pastebin.mozilla.org/6829989
http://past..pastebin.mozilla.org/6829989
http://pastebin.mozilla.org/6829989
If the problem cannot be fixed by anyone but ZTE, how can I
make it use
the Mozilla Location Service? I've tried setting the following
prefs,
but that didn't help:
pref(geo.provider.use_mls, true);
pref(geo.cell.scan, true);
pref(geo.wifi.uri,
https://location.services.mozilla.com/v1/geolocate?key=%MOZILLA_API_KEY%;);
pref(geo.enabled, true);
In this case I am getting these errors:
E/GeckoConsole( 283): [JavaScript Error:
NS_ERROR_XPC_CANT_CREATE_WN:
Component returned failure code: 0x80570019
(NS_ERROR_XPC_CANT_CREATE_WN) [nsIJSCID.getService] {file:
jar:file:///system/b2g/omni.ja!/components/NetworkGeolocationProvider..js
line: 332}]
E/GeckoConsole( 283): [JavaScript Error:
NS_ERROR_XPC_CANT_CREATE_WN:
Component returned failure code: 0x80570019
(NS_ERROR_XPC_CANT_CREATE_WN) [nsIJSCID.getService] {file:
jar:file:///system/b2g/omni.ja!/components/NetworkGeolocationProvider..js
line: 307}]
I/Gecko ( 283): settings 'handle' callback threw an exception,
dropping: [Exception... Component returned failure code:
0x80570019
(NS_ERROR_XPC_CANT_CREATE_WN)
Re: [b2g] Which Phone to Upgrade?
Le 09/10/2014 18:09, Hubert Figuière a écrit : On 08/10/14 04:59 PM, Bob Thulfram wrote: Next I'll see how it likes a SIM card. Could there be any difference in SIM card acceptance because the Peak is European and the two ZTE phones are China/USA? The problem is not whether it likes the SIM card or not but rather whether the phone supports the frequencies used by the carrier you are on. Peak supports this: UMTS 850/1900/2100 (3G HSPA). GSM 850/900/1800/1900 (2G EDGE). Which is combo of EU and America that should work on major carriers. I think some carriers in US (esp T-Mobile) use other frequencies for 3G in some locations, and as a result you may not have 3G in some locations. -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Which Phone to Upgrade?
Le 08/10/2014 22:59, Bob Thulfram a écrit : OMG! I just upgraded my Geeksphone Peak from 1.2 to 2.1 and it happened really fast and without any hitches! I'm really interested to know if you see any graphics issue in this setup :) I stopped using the Peak because the new Graphics code in Gecko was not really supporting the kernel used for the Peak, but maybe Geeksphone did some work about this. -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Cannot wake up app from Simple Push notifications
Le 09/10/2014 15:15, michel.gutier...@gmail.com a écrit : Hi, I am trying to implement push notification in my turnbased-games apps. The simple push API itself works fine: i can register/deregister endpoints, see registered endpoints and receive notifications. BUT, this only works when the app is running. If the app is not running, nothing happens, while my app server keeps sending notifications every minute or so, incrementing the version number. 1/ am i right to assume the OS should launch the app upon receiving a notification ? I just want to make sure that you actually registered a system message handler as explained in https://developer.mozilla.org/en-US/docs/Web/API/Simple_Push_API ? 2/ i've read that there was a bug preventing the app to be woken up on a page that is different from the one that registered the notification. Is this still true in ffos 1.4 ? I think that's never been true :) What's true however is that the system message won't be sent if your app is already opened in any page (bug 818000). -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Gaia is ignoring my locales.
Le 02/10/2014 17:55, A. Crespo a écrit : Hi, I am wondering if any env variable is trolling me. Would you know if there is any variable related to it? Hey, Can you please explain a little more what you're doing ? Thanks! -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] You can debug your chrome JS code on your device using WebIDE! - Link
Le 07/10/2014 17:11, Malini Das a écrit : Of course, I was so excited I forgot to post a link: https://developer.mozilla.org/en-US/docs/Tools/WebIDE#Debugging_certified_apps I don't think this is the right information; this shows how to debug certified apps, but not the platform code. I'm not sure we have anything about this in MDN yet :) signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] How to update to the new Flame base image, gecko developer edition
Le 30/09/2014 16:06, Kartikaya Gupta a écrit : For those of you out there like me, using ./build.sh and ./flash.sh to do local dev builds and full-flashing the device: note that this doesn't update your base image, and so you might still be using the old JellyBean-based base image. As dhylands and viralwang explained to me, in order to actually switch to the new base KitKat-based image you need to the following: 1. Download and flash the Base Image v180.zip image from https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame 2. In your $B2G_DIR, |rm -rf out| and |rm -rf backup-flame| and here, I wonder why we don't have a backup-flame-kk ;) signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] bricked Flame
Le 29/09/2014 00:28, Dietrich Ayala a écrit : While flashing a Flame to the new KK base image, the script exited partway through flashing fsg, saying couldn't detect device. Now the device will not turn on at all. If I remove the battery, then hold voldown+sleep and plug in USB, I can see the LED next to the front-camera flash briefly. However, nothing ever happens after that. On the Flame, I successfully entered fastboot like this: * remove the battery, but then put it back in the device * hold voldown + press power until you get a vibration * plug in your USB cable = fastboot devices should show you the device. signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Major issue loading CSS, for a multi-platform app with 5+ million users
Le 18/09/2014 21:09, jonat...@callpod.com a écrit : Hey all how's it going? My name is Jonathan from https://keepersecurity.com. We're having a major issue on the Firefox OS. We have a web app that's not displaying the CSS to our webpage. It doesn't seem to work in the FF OS Web Browser either. Seems to work for me in the Browser. https://keepersecurity.com/ is the url. Here's a picture of the issue: http://i.imgur.com/XPgMmz5.png And if you check the source, it will show you that our CSS file is being hosted off of an amazon cloud front file. What might be causing this? Our web developers are scratching our heads on this and we get featured on the FF marketplace in a few days so we're trying to resolve this ASAP. Any help would be greatly greatly appreciated. Thanks! ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Flame Not Keeping Time
see https://bugzilla.mozilla.org/show_bug.cgi?id=1067269 as well Le 18/09/2014 10:16, Ralph Daub a écrit : Hi Ben, Here is the bug for the SMS issue that's unearthed by the wrong clock times: * Bug 1021326 - https://bugzilla.mozilla.org/show_bug.cgi?id=1021326 ** [SMS] - SMS thread is ordered according to the time configured in the phone instead of order received - Ralph - Original Message - From: Ben Francis bfran...@mozilla.com To: dev-b2g dev-b2g@lists.mozilla.org Sent: Tuesday, September 16, 2014 7:20:41 AM Subject: [b2g] Flame Not Keeping Time Hi, Does anyone else have problems with the system clock on their Flame getting set to a random time after a reboot? Mine does it all the time and it's quite frustrating, particularly because the SMS app uses the system clock to datestamp messages, so the messages all get out of order! The phone regularly gets turned off by accident whilst in my pocket because the power button is so sensitive so it happens to me quite a lot. Is it just my device, is there a software bug, or is it a hardware thing? I'm dogfooding the aurora channel. Ben ___ 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 signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
[b2g] Please announce your big potentially breaking changes on the list
Hey, some of the teams do a great job announcing potentially breaking changes on the list, but some others don't. We recently got bitten by some changes that could have been announced (I'm thinking of the mozSettings breakage here), and announcing it here would have made it easier for developers to know why their phone stopped working. So if you know your changes can cause ugly regressions accross the whole platform, it's a good idea to say it in advance :) Thanks! -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Flame Not Keeping Time
Le 16/09/2014 17:04, Alexandre Lissy a écrit : Le 16/09/2014 17:01, Frederik Braun a écrit : Same problem here - I think this was/is a known issue with v122: The time goes wild, sometimes, which of course means notifications, texts and emails are in the future so the text says in x hours or in y days. See these bugs: * https://bugzilla.mozilla.org/show_bug.cgi?id=1032233 ** After rebooting in airplane mode, time and date can be all wrong [Manual Time Setting] (resolved fixed) * https://bugzilla.mozilla.org/show_bug.cgi?id=1032101 ** [Flame] Date and Time on are frequently incorrect [When using/fiddling with Set Time Automatically] * https://bugzilla.mozilla.org/show_bug.cgi?id=1031573 ** [Flame][2.1] Alarm clock alarms at random times (edit) And https://bugzilla.mozilla.org/show_bug.cgi?id=1057589: [System] Time is not preserved after restarting device. Which is RESOLVED:FIXED with a vendor workaround. https://bugzilla.mozilla.org/show_bug.cgi?id=1057589#c14 Is there anything we need to do to use it, or installing latest base builld is enough? signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Zte Open C official build
Le 19/08/2014 14:40, gael.goin...@gmail.com a écrit : Hello, While reading this bug report : https://bugzilla.mozilla.org/show_bug.cgi?id=1016867 I was wondering if an official mozilla build for zte open c is planned ? Maybe because of some proprietary drivers, mozilla can't do it ? Please notice that a cyanogen mod fork has been developped for the zte open c, so the kernel sources for zte open c are available with proprietary drivers: http://www.modaco.com/topic/373214-devrom178-cyanogenmod-11-android-444-for-zte-open-c-kis-3/ The kernel sources of this fork are there : https://github.com/KonstaT/android_kernel_zte_msm8610 It's probably illegal, so Mozilla won't be able to distribute this. Sorry :( -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Where the f** is app manager?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 18/08/2014 14:56, Adrian Custer a écrit : On 8/18/14 6:01 AM, Jan Jongboom wrote: We realize that in all docs we write and demo's we gave we tell people to use the App Manager and now its gone from nightly? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g Ha! EXACTLY my reaction. It's still there. The homepage of my nightly points to about:app-manager and I am happily still using App Manager. The WebIDE is not yet up to snuff. When it works it's great, and I am sure, for all sorts of reasons, is the path of the future. But for the here and now, App Manager is the way to go. (I forget the details, either syncing didn't work or debugging was flakey.) Dropping the working for the new with no transition is BULL$*@! The developers were asked nicely when this first hit if they could allow both during a transition period. That has not happened. Such it goes. Just a note that you're all using Nightly here. Nightly is where no-transition changes happen, so that we can test new things in the wild. And sometimes we disable them after some days, or when it goes to aurora, or when it goes to beta. So, yeah, we used to say to use Nightly for Firefox OS development (because this is how we keep up with the changes) but obviously this also comes with such disagreements. To enable/disable webide, you can have a look to about:config, and look for the pref devtools.webide.enabled. Please report anything that you dislikes about WebIDE by filing bugs, before or instead of disabling it. That's basically your duty when using Nightly :) Maybe we should have a separate pref to enable/disable App manager so that we can have both side by side? My fear is that users don't use WebIDE at all once they disable it... - -- Julien -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJT8geZAAoJEHjtma/kG/DBKJoP/2UGVorgXOCM8NclNsyT316H eae1ZkKHDUEWfb7V55fN++4NAYjnIUOF9vd0bkomTE4bTQdD9jf4k1tWKNZduQZ/ KwaDRZ+oIymxL4eoTXjh5V4wA2a1FGCwRNaLT1wnLEGksYiMuVxlSVmM0yvFPuhn BjVHLoWsWWFV19DS4GEMUoJTOAe2oVTYr3lQu0RxkYUJdxZcwu+MEEtTofdO64xM QPqjef/iP9GZv8yWNHJzFsCRRQ6YZcHh0QLlosJw/u5KmmTpFqMGAXTdvCOUrhY9 PDNbYIqpqgcQpfO0ZcXN07tNWJEWbPHho9MZLQezjJXQ/IlelFVdJsxVeTE58Fke Mr8idbje4NVrpvHja5Ox7BlIoeXEg7l8zNwqnnPdIVQrdW19/xItaegxnBmFBS5C Xhk6atCg2cpc+5Y6V3bdHB3Ohym9+J34XPURsTV0ZnMhPXSmP/UiMjYiffvSLuL0 F7WOZWX5pvjwmorSMJT8WPW81/5jDnBUqT3SWSLBBp4qKSW1i1r+Z7MIult+C2y2 zEkxlxW4bU7qZ7wL6FrpCGSSjwUlKAj1COy2E20v333QXAb1qug9OgQ3XXjuayWS LKxU4R8ee8oAngT0CUs/YL0pR+WX69C5CuwWa/ilguDxSTQZIm5mSVsbtIqd/Vzi sfErin45CrP/PRBDlmFy =5a+t -END PGP SIGNATURE- ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Weird monospace font on Flame 2.1
Note that on Buri, I can't install an engineering build anymore if I have both set of fonts. Le 11/08/2014 11:05, Frederik Braun a écrit : On 11.08.2014 10:45, Jan Jongboom wrote: I've seen this a couple of times, and now I see it also in some issue in bz. https://bugzilla.mozilla.org/attachment.cgi?id=8466079 What's this weird monospace font? It's somewhere in Gecko, because flashing a fresh Gaia on an affected build doesn't help. This has been raised previously in this list with the subject Fira 3.109 has landed - Manual update required for shallow flashing, from Michael Wu. I will quote below: On 01.07.2014 15:51, Michael Wu wrote: Hi, We now have a new version of Fira Sans and Fira Mono. Unfortunately, the name of the font has changed again (Fira Sans OT - Fira Sans), and gecko will require fonts bearing the new name. If you use shallow flashing or get automatic updates, you'll need to manually add the new fonts in at the moment. I've put together a package with the fonts and a script to install the font on the device. https://people.mozilla.org/~mwu/fira-font-update.zip Run the script to push the new fonts on your device. adb probably needs to be in your path if you're not running Linux. This can also be done without the script - adb remount adb push fonts /system/fonts These fonts can coexist with the old Fira fonts, so switching between different gecko branches isn't an issue. Thanks, -Michael Wu ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Flame phone documentation, running adb as root
Le 07/08/2014 21:43, Chris Mills a écrit : Heh - now I feel silly. You are right Ryan, it was a permissions issue. chmod 777 on the shallow_flash.sh file made it work without needing sudo…phew! If I may add: chmod +x should be good enough :) no need to make it world executable/writable/readable. Can be even dangerous in some situations... signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
[b2g] Updating Flame without losing data
Hey, So I read [1] again and I think the instructions delete all the data. The reason is that we use QA's script, and for QA this is important to revert to a clean state. For us, users, it's important to keep the data. It should be possible to shallow flash gecko+gaia without removing the whole data. Backuping+restoring doesn't always work reliably (I just tried, I think maybe some prefs should not be restored) and anyway it's just longer than just flashing gecko+gaia. Same when we flash images: I think it's enough to _not_ flash userdata.img over the device. Any possibility the tools could be updated for this? Should I file a bug somewhere? [1] https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame#Updating_your_Flame_to_a_nightly_build Thanks ! -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Release candidates
Le 08/08/2014 07:32, Marek Raida a écrit : Thank you for your reply. It is new and interesting fact for me, that Flame is not to be fully supported for lower than v2.0 OS, so I can stop reporting bugs on 1.3 and focus on 2.0 instead. Well, once I'll be able to flash it to my device, that's it :-( However, what you're saying is in minor contradiction to what Chris writes on linked Flame page - you're providing binaries for latest builds on FTP, even for v1.4 But if it is recommended to rather avoid 1.4 on Flame, perhaps Chris can mention it there, make it not so obvious option to try 1.4. For most people, trying the next major release is tempting because of higher stability, but as you say, not so in case of Flame and v1.4 For sure we won't fix new bugs in v1.3, v1.4 (unless they are severe), but we will for v2.0. So reporting bugs for v2.0 is what makes the most sense right now. -- Julien ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Flame phone documentation, running adb as root
I really think we should try to do it without using sudo. I don't know enough of MacOS X to know how to make it see the device, but I'm sure there is a solution like udev on LInux. How does it work for other devices? Le 07/08/2014 09:29, Chris Mills a écrit : Hi there! I’ve now investigated the supplied instructions in the Flame article[1], tested them thoroughly, and updated them to make them clearer and more complete. Josh was right about needing to mention sudo: when I didn’t run flash.sh with sudo, the flash script seemed to fail to see the device, so it didn’t work; it just sat there saying “waiting for device”. When I did use sudo, it worked fine. Then when I ran shallow_flash.sh without using sudo, it gave me a “permission denied” error. When I did use use sudo, that error went away. However, I am still stuck on that bit. The current text includes the following instruction: 5. To install the build on your phone download the shallow flash script and run it like this: sudo ./shallow_flash.sh -g/path/to/gaia.zip -G/path/to/b2g-XX.XX.en-US.android-arm.tar.gz” I’ve got shallow_flash.sh, gaia.zip and b2g-34.0a1.en-US.android-arm.tar.gz downloaded into the same directory. I then go into that directory in terminal and run the above command, and it gives me the message sudo: ./shallow_flash.sh: command not found”. How do I fix this? ;-) Chris Mills Senior tech writer || Mozilla developer.mozilla.org || MDN cmi...@mozilla.com || @chrisdavidmills [1] https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame On 6 Aug 2014, at 20:34, Dave Hylands dhyla...@mozilla.com wrote: I'm a little confused by some of your statments. Whether you flash the base image as the root user or as a regular user will have NO impact on how adbd runs on the phone. Running commands using sudo on the build machine only affects access to the devices on the build machine. adb root relaunches the adbd on the phone under the root user (if the phone is configured to allow it). Dave Hylands From: Josh Aas josh...@gmail.com To: dev-b2g@lists.mozilla.org Sent: Wednesday, August 6, 2014 9:15:36 AM Subject: [b2g] Flame phone documentation, running adb as root I got a Flame phone and wanted to update it to 2.0 nightly so I could test/dogfood. Last week I couldn't figure out how to do that via the Flame home page, but someone has since added instructions. Thanks to whoever did that! https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame One issue with the instructions, though, at least on OS X - they only really work if both flash steps are run as root (sudo). Flashing the base doesn't require root, but the flash to 2.0 nightly requires the adb daemon to be running as root, and if you didn't flash the base as root adb will not be running as root. You'll need to do adb kill-server, which most people won't know how to do. If you didn't run the base flash as root, and you figured out how to kill the adb server, you then need to run the second flash as root to get adb to start as root. We should either recommend that people run the flash commands as root (prefix sudo), or explain how to get adb running as root first. Other than this, the page's information is much better than before. Still could be better organized, though. ___ 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 ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open C: Can't see own phone number on FFOS 2.1 build, for sending to others.
Le 06/08/2014 09:29, Rewarp a écrit : In Settings Devices, it says number unknown. That said, how would I go about sending my phone number and contact to another phone via FFOS? Knowing your own number depends on your SIM, looks like your SIM doesn't have this information. As far as I know, we don't have the functionality to send your own number/contact to another phone, but this would be a welcome addition. Can you please file a bug (I guess it could be in FirefoxOS/Gaia::Contacts)? Thanks ! -- Julien ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Backups for Firefox OS
Le 24/07/2014 14:31, Frederik Braun a écrit : Or maybe through a give me your backup data-call the app is responsible to support?) I like this idea. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Backups for Firefox OS
Le 05/08/2014 12:01, Frederik Braun a écrit : On 05.08.2014 11:49, Julien Wajsberg wrote: Le 24/07/2014 14:31, Frederik Braun a écrit : Or maybe through a give me your backup data-call the app is responsible to support?) I like this idea. But do you think it's likely, third-party apps will support this? We'll need to check how other OS are doing this, but I fail to see how to do it differently. Either the backup application knows about the internal format (and then it's application specific) or the application can save/restore its data in a generic way. I'm not saying it's easy, especially for forward compatibility... ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Backups for Firefox OS
Le 05/08/2014 17:15, Fabrice Desré a écrit : On 08/05/2014 04:12 AM, Julien Wajsberg wrote: We'll need to check how other OS are doing this, but I fail to see how to do it differently. Either the backup application knows about the internal format (and then it's application specific) or the application can save/restore its data in a generic way. I'm not saying it's easy, especially for forward compatibility... I thought a bit more abut that since I discussed with Frederik and I now believe that we should try to do something that is 1) user oriented (devs can already use the various scripts laying around) and 2) that doesn't need any application specific code. The way I see it is that all apps that are saving data locally do it through a storage mechanism that is known to the platform, be it cookies, localStorage or indexedDB. So we could provide platform-level application backup by exporting/importing data relevant to a given app. Anything else is likely managed in the cloud by the app itself. We also have some non-app content: chrome databases (like contacts, sms) and any data that is saved by web pages. It seems clear we want to backup the chrome ones when doing a system backup, but I'm not sure about the web ones. So, say, the user selects the Contacts app. How do you decide you need to take away the datastore for facebook contacts and the idb for mozContacts? Another question is: how do you manage restoring to an earlier version ? I don't think it would generally work without help from the app itself... ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Backups for Firefox OS
Le 05/08/2014 18:42, Fabrice Desré a écrit : Another question is: how do you manage restoring to an earlier version ? I don't think it would generally work without help from the app itself... I'm not sure to understand the use case here. Can you elaborate? In general we don't support downgrades, but starting from scratch with an older version will work thanks to the indexedDB upgrades. I thought this is in Frederik's initial requirements for restoring. I don't really mind. -- Julien ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
[b2g] ./build.sh gecko builds also Gaia
Hi, it's been quite a long time I worked on Gecko, and now I see that merely running ./build.sh gecko also runs the gaia build. Why is this happening? The gaia build takes a really _really_ long time (especially with the default environment variables used by build.sh) and it's quite painful. I didn't see which recent changes made this, but I don't know well how the build process work in the B2G repository. Any pointer? -- Julien ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ./build.sh gecko builds also Gaia
Le 05/08/2014 21:30, J. Ryan Stinnett a écrit : On Tue, Aug 5, 2014 at 2:25 PM, Julien Wajsberg jwajsb...@mozilla.com wrote: Hi, it's been quite a long time I worked on Gecko, and now I see that merely running ./build.sh gecko also runs the gaia build. Why is this happening? The gaia build takes a really _really_ long time (especially with the default environment variables used by build.sh) and it's quite painful. I didn't see which recent changes made this, but I don't know well how the build process work in the B2G repository. Any pointer? There's an open bug to resolve this: bug 1022728. Oh, thanks ! And there's a patch waiting for review for 1 month and a half. Could make sense to ping Michael Wu once again? -- Julien ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Compatibility layer required
Le 01/08/2014 11:54, jose llopis a écrit : We are reaching 2.0 and i think that its neccesary to get some kind of compatibility library to make the platform more robust what do you think? I'm not sure I understand what you have in mind. signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] flame sent message sound
Le 26/07/2014 01:28, lachlan-00 a écrit : Is it just me or does it sound like the phone is giggling at you? The sound has been changed in v2.0, so maybe you still have the old one ? :) signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] How to delete all contacts on SIM card
Hey, I think that we don't have anything to edit what's on the SIM Card. We can only import contacts from it and that's it. Hope this helps, -- Julien Le 22/07/2014 15:50, Rewarp a écrit : I am currently migrating contacts to the ZTE Open C, and I have a alot of contacts stuck in my old (downright ancient) phone, which doesn't allow one to select all contacts on the SIM card for deletion. The only easy solution is to delete all my contacts on the SIM card and use it as a primitive form of a memory card for transferring contact information. How do I delete all contacts on the SIM card using FirefoxOS? /-- Bitmessage http://bitmessage.org/ me/ *BM-2D97QV3Y4VRfjayrWahqE61XKuQw6dJvj6* ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] flash scripts sometimes don't deal with a disconnected devices (e.g. screen locked)
Le 10/07/2014 11:37, Frederik Braun a écrit : Hi, I noticed that a lot of flash scripts just fail because my device is locked or in another kind of unexpected state. I usually get this and unlock the device, but I'd also argue that this is a tiny bug in your scripts :) You could always do something like this: echo Waiting for device.. # this blocks your shell script until adb finds the device: adb wait-for-device but sometimes we use adb only to reboot the phone in fastboot mode :) If it's already in fastboot mode (for example: it's bricked and you want to unbrick), then maybe you don't want this. That said, it's also easy to edit the script and comment the line if necessary. signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Please update the latest Gecko and GAIA
Le 04/07/2014 04:35, Gary Chen a écrit : Hi All, Since the two preference names(browser.manifestURL and browser.homescreenURL) has been removed in bug 1014487 and the patch is already landed in GAIA master, the combination of the OLD gecko and NEW gaia will cause trouble. To avoid this, please keep your gecko and gaia both up to date. For more details, please refer to https://bugzilla.mozilla.org/show_bug.cgi?id=1014487 Hey Gary, Is it only used in the System app? (to know what need to be kept in sync here). ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Please update the latest Gecko and GAIA
ok, that means we need to have the correct pref with that Gecko. But what is the update story then? Le 04/07/2014 10:54, Gary Chen a écrit : Hi Julien, In my understand, Gecko use these two preference keys to launch 'first APP' when it star up. So I just want to sync this information here, sorry about for the confusion. Best regards - Gary Chen 陳柏宇 Mozilla Taiwan T: +886-2-87861100 # 206 M: +886-975151712 gc...@mozilla.com - Original Message - From: Julien Wajsberg jwajsb...@mozilla.com To: dev-b2g@lists.mozilla.org Sent: Friday, July 4, 2014 4:08:40 PM Subject: Re: [b2g] Please update the latest Gecko and GAIA Le 04/07/2014 04:35, Gary Chen a écrit : Hi All, Since the two preference names(browser.manifestURL and browser.homescreenURL) has been removed in bug 1014487 and the patch is already landed in GAIA master, the combination of the OLD gecko and NEW gaia will cause trouble. To avoid this, please keep your gecko and gaia both up to date. For more details, please refer to https://bugzilla.mozilla.org/show_bug.cgi?id=1014487 Hey Gary, Is it only used in the System app? (to know what need to be kept in sync here). ___ 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] Please update the latest Gecko and GAIA
ok, I think I get it now: newer Gecko does not need these prefs at all (and will ignore them if they're present). Thanks for your patience with me :) Le 04/07/2014 11:11, Julien Wajsberg a écrit : ok, that means we need to have the correct pref with that Gecko. But what is the update story then? Le 04/07/2014 10:54, Gary Chen a écrit : Hi Julien, In my understand, Gecko use these two preference keys to launch 'first APP' when it star up. So I just want to sync this information here, sorry about for the confusion. Best regards - Gary Chen 陳柏宇 Mozilla Taiwan T: +886-2-87861100 # 206 M: +886-975151712 gc...@mozilla.com - Original Message - From: Julien Wajsberg jwajsb...@mozilla.com To: dev-b2g@lists.mozilla.org Sent: Friday, July 4, 2014 4:08:40 PM Subject: Re: [b2g] Please update the latest Gecko and GAIA Le 04/07/2014 04:35, Gary Chen a écrit : Hi All, Since the two preference names(browser.manifestURL and browser.homescreenURL) has been removed in bug 1014487 and the patch is already landed in GAIA master, the combination of the OLD gecko and NEW gaia will cause trouble. To avoid this, please keep your gecko and gaia both up to date. For more details, please refer to https://bugzilla.mozilla.org/show_bug.cgi?id=1014487 Hey Gary, Is it only used in the System app? (to know what need to be kept in sync here). ___ 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] How to create release build for FxOS?
Le 10/06/2014 13:41, Johannes Bauer a écrit : On 10.06.2014 07:57, Yuren Ju wrote: you also can use MOZILLA_OFFICIAL=1 to get official icon for browser and power on images. |PRODUCTION=1 MOZILLA_OFFICIAL=1 make| So I've just now created a clean build of BRANCH=v1.3 with the above variables. Now my phone is blackscreening again, as described in the [b2g] v1.2 to v1.4 update - black screen on Alcatel One Touch Fire (hamachi) thread. I thought that was a 1.4 issue, but it's not. Apparently it's a more general problem. Can someone please look into this? If updating your phone bricks it every other time, this really should be blocker, shouldn't it? I've already provided a logcat (which apparently didn't show anything of interest). I think the main issue is that the hamachi storage is very low... yeah, this is painful. Try this: MOZILLA_OFFICIAL=1 make production If you want to make the marketplace removable, edit apps/marketplace.firefox.com/metadata.json and flip removable to true. -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] How to create release build for FxOS?
Le 10/06/2014 16:19, Johannes Bauer a écrit : On 10.06.2014 16:04, Julien Wajsberg wrote: I think the main issue is that the hamachi storage is very low... yeah, this is painful. Is there a way to confirm that this is indeed the problem? If complete images (that can be flashed via fastboot) were working then there'd be a way to check the complete image size before flashing without risking to break the phone due to the update. Try this: MOZILLA_OFFICIAL=1 make production Hm: GNUmakefile:2: *** Must source setup.sh or build/envsetup.sh to use make directly. Stop. So I sourced setup.sh and did it again. It built some things. When flashing the phone with the result, however, the result was still a blackscreening phone. Sorry, I meant from the gaia directory... From the B2G directory, I only ever build and flash gecko. (but that's because I'm a gaia developer and so I usually work on modified version of Gaia) Note that I've built the latest v1.3 branch with MOZILLA_OFFICIAL=1 and PRODUCTION=1. If you want to make the marketplace removable, edit apps/marketplace.firefox.com/metadata.json and flip removable to true. Is there a way to strip out all these apps before flashing them down? I can't remove them anymore when the phone is in blackscreen mode. Also, does adb update remove stuff that's unneeded anymore? not really, only make purge (from the gaia directory) deletes things (and I mean, deletes most of the things before installing) There are several things that I will never use and that I'd gladly remove if I knew how: video player, music player, radio, email stuff, marketplace. Is there a way to remove them? Just rm -rf them from your gaia directory before calling make production. signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Build instructions and tutorials out of date / manifest files broken
Just a quick note: Open C and Flame are still new devices and that's probably why the documentation is lacking a bit. Adrian is right about the fact that there is technical debt in the build system: it mostly works for our needs and so not much love is devoted to it right now. Thanks for the good feedback anyway ! Le 07/06/2014 01:06, LazerUnicorns Developers a écrit : Hey all, I have to say it's really hard to get started with building FirefoxOS by yourself. It's pretty impossible for a newbie in B2G development. Here's my feedback after around 10 hours of trying to get started - with no success at all. I mean, modifying and fixing the build setup is pain. You founded a repo for the config and setup stuff (B2G), why splitting up everything in b2g-manifests then? After 10 hours of googling all the information together ... other developers won't invest that much time to get started on development. Just sayin'. 1. I had to find a gist file that was building FirefoxOS 1.2 to find out the dependencies. I modified it in order to properly build v1.4 (which I still haven't getting managed to do). The gist is available at the following link. I build everything on Ubuntu Trusty Thar (14.04 stable) inside a VirtualBox VM in order to not fuck up my usual Android build system. Note: I'm still using the original B2G repo, but I need to fix that stuff - so I forked it together with the b2g-manifest repo. https://gist.github.com/martensms/a057224797238239ea99 2. Why are the Android building dependencies included for Darwin if you can build it only on Ubuntu anyways? 3. The manifest files are out of date. I can't get anything built due to the missing tinyxml / tinyxml2 repositories that are not existing (base-caf-jb.xml manifest file). So in order to fix that, I had to fork your repositories to get it run properly. That sucks hard if you haven't built anything at that time and you have no idea what to do as a newbie. 4. The wiki entries suck. No offense, but it's pretty impossible to gather all Compiler Setup instructions there. I own a ZTE Open C device, I had to google 15min just to find out that its codename can be treated as flame after using the Unlock tool that only runs on Windows that wasn't working anyways. I then had to use fastboot to unlock, because I realized the bootloader was capable of installing files via adb pushes ... no docs at all on the wiki / MDN pages / google results? Problems and Questions: - Why are all the necessary configurations not hosted in a single (namely the B2G) repository? - How can you build a flame variant properly? - How to overwrite the repository with the correct one in the manifest file? (I have no clue of the repo manifest files) === = TL;DR LOL = === config.sh call fails due to repo sync errors; here's the output (warning, huge txt file!): https://gist.github.com/martensms/011a7e4bd3646528ab69 Need to fix the tinyxml2 repository, how can I do that in the manifest files? Cheers and many thanks so far, CM ___ 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] Build instructions and tutorials out of date / manifest files broken
Le 07/06/2014 15:36, Adrian Custer a écrit : The biggest challenge for me is that the Firefox OS free software *project* does not exist. Right now Mozilla has all its developers working in little teams each doing great work on their piece of the puzzle. However, there is no real, effective, communicating leadership to which the core issues can be brought and who could provide a plan to resolve all the technical debt. Critically for us outsiders, the insiders do not have it as part of their work to build the community and pull us in. Individually they are each willing to help and enthusiastic but structurally this has not been stated as part of their responsibilities so the project is not forming as an effective collaboration of outsiders and Mozilla. Yes, this is sadly true. Thanks for saying it in such a clear way :) That said, it should be easier to contribute in a specific application (as opposed to the underlying system bits). Even if the documentation improved a lot (thanks to the huge work of Chris Mills and people like you), we still need to make it easier to find the first steps to do. Even for me, it's not always easy to know what to look first on MDN. -- Julien ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] User report: 6 months of Firefox phone
Hey Johannes, If I can summarize your thoughts, in my decreasing order of importance : 1. when I report bug, they basically get ignored - this is the #1 issue to have a sane community. The owners or peers of components should definitely triage their coming bugs at least once a week. Maybe different people in the team every week, pick your own process, but letting a user bug without an answer is really bad. And this must be done for every component; any component that has no specific owner needs to have one. 2. I want to upgrade my phone, what should I do, which repository can I take, what is safe ? - we need IMO 3 channels: release, beta, nightly-might-break-your-phone I think this is what we're preparing for Flame. Sadly it's more difficult to do for other phones because binary drivers suck. I mean, it's not even advisable to make you do this by building yourself... FWIW v2.0 is too much a moving target right now; some of our people are dogfooding it but this is dangerous if you're not in the team. v1.4 is definitely ok and quite pleasant though. 3. Browser is crashing - IMO what's really happening is that the webpage uses too much memory, and the page crashes because of out of memory condition. The Alcatel has only 256MB memory... Even on Peak (512MB) I have this issue sometimes too. We did huge improvements lately (that you don't have on 1.2) but still this issue happens sometimes. We desperately need something to distinguish a real crash from OOM conditions; we need something that says this page uses too much memory and we had to close it. We also desperately need to have a tracker blocker: preventing tracking scripts/images from even loading would definitely save memory. Hope this answers some of your questions... I guess I have more questions than you :) Le 03/06/2014 11:48, Johannes Bauer a écrit : Hey list, so I've been using Firefox OS on my Alcatel One Touch Fire since Nov 2013 as my only phone on a day-to-day basis. I'd like to share my feedback to give you an impression about what I like and dislike about it. I've been on branch 1.2 for pretty much the whole trip. Gernerally when I bought the phone I knew I was getting into a haphazard kind of development situation. I knew there was going to be fiddling involved and that's okay. The main reason I bought it was beacuse I was happy to see an alternative to Android on the market and was curious if it were possible to actually actively participate in the project. About the usage: One of the very very first things I noticed was that the phone had a irritating, annoyning and most of all completely useless vibration effect when pressing the home button. It's one of the first tickets I commented on and it was annoying enough for me to actually patch the relevant code (described solution in #885716). Six months later: I tried to pull a 1.4 branch only to realize this is still exactly the same code. A dev had the ticket assigned to himself only to disassign it a few days back saying this isn't going anywhere. I don't get it. You guys even have a user experience team. Those people should know how freakishly annoying vibration can be. Why can't you just comment out the two lines until it's implemented properly? Actually I don't think anyone would miss the vibration when pressing the home button at all. In any case, it's utterly frustrating to see that this is not something that is important enough to warrant attention. Other quirks: The phone has sometimes really weird behavior when dialing. Sometimes it dials the wrong number (i.e. I have three numers stored and I absolutely positively press the first one, but it dials up the third one). Data import and export is horrible (it was a real pain upgrading the phone because there was no option to delete all contacts). Also when the number that is dialed is busy it just goes back to the address book with no indication what went wrong whatsoever. This is pretty annoying (i.e. you have the phone on your ear for a few seconds and hear nothing, then you look at it again and it's stopped dialing as if you never dialed to begin with). Some random flickering/crashing issues too but not reproducible and seldomly enough to be considered okay. Ironically the worst thing about the phone is the browser. Wow, that browser sucks so much it's hard to put in words. It feels like Netscape Navigator again. Don't know why something with a Firefox label can have such a horrible browser (which effectively makes it not a smart phone anymore when Internet is practically unusable). Crashing *all* the time, display errors all over the place. Wow. In any case what I found most frustrating about it all is that I have got the feeling that feedback is not taken seriously. On this mailing list ironically people are super helpful and enthusiastic and nice, but once issues get in the bugtracker, they're just lost. Looking at the version history I couldn't even find out what version I was supposed to
Re: [b2g] Smoketest Regressions on Trunk are Out of Control
(answering on dev-b2g only, crossposting is painful) Le 03/06/2014 17:53, L. David Baron a écrit : On Tuesday 2014-06-03 08:13 -0700, Jason Smith wrote: I need this under control as soon as possible, as these regressions are causing the build to move towards being completely not functional. I'm also debating if we should close the Gaia tree at this point since there's now risk that we can end up with a non-functional build. Can we get this under control here? If closing the Gaia tree will help this, then let's do that. A somewhat radical proposal: 1. Close the tree, find the patches that caused the regressions, back them out, and reopen the tree. 2. Don't let the patches reland until a test has been added that is green without the patch, but would have caused orange when combined with the regression. If the regression was at a platform level or other lower level than the gaia app, the test could be too. But if that's the case it would also be good to have test coverage of the gaia apps. We're not always this strict about test coverage in Gecko-land, but it's been useful to be strict in areas with the problem of frequent regressions. Not getting tests added that catch these problems is an accumulation of technical debt. Perhaps now really is a bad time to deal with this, but there ought to be a time to do so. yes, this is exactly the path we try to follow nowadays. I hope it will make us more resilient in the future. -- Julien ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Smoketest Regressions on Trunk are Out of Control
Le 03/06/2014 18:24, Dave Hylands a écrit : Do we even have tests which run on a real device? We have some but they're not running on each commit, rather every day. There is an effort to have a fake RIL daemon so that we can simulate the network in the lowest level and experience all the RIL and API code in integration tests, but it's not finished yet. I don't have the bug number, somebody else will have it :) ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
[b2g] Buying ZTE Open C in France
Hi, just a note that it seems we can buy the ZTE Open C in France using the UK shop at: http://www.ebay.co.uk/itm/171301269724 Hope this helps somebody! -- Julien ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Unable to get to otoro bootloader (black and white striped screen)
I think otoro is not supported at all. You should try to get a replacement. Le 06/05/2014 21:21, Jonathan Watt a écrit : I have an otoro device with an old 1.0 version of b2g on it that I'm trying to update to a master branch build. I can start and run the old b2g on the devices, but I don't seem to be able to get to the bootloader in order to flash though. When I run flash.sh it reboots the phone but it instantly gets stuck on a screen showing black and white horizontal stripes, and |adb devices| and |fastboot devices| can no longer see it. The same thing happens if restart the phone so that the old b2g runs and hold down the volume up and power buttons as described here: https://developer.mozilla.org/es/docs/Mozilla/Firefox_OS/Troubleshooting#Bricked_Phone I've tried these steps before and after updating the kernel to kernelupdate11 and kernelupdate12 (which seem to flash the boot image successfully) but that makes no difference. Anyone got any ideas how I can recover this devices to use it for low spec device testing? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open - supported or not?
Just to check, have you tried the 1.2 version from ZTE?What's the result? some information in https://hacks.mozilla.org/2014/01/upgrading-your-zte-open-to-firefox-1-1-or-1-2-fastboot-enabled/ Le 07/05/2014 15:20, Roland Lindner a écrit : I agree on that, but it really is missing the point. I am not talking about end-user updates. It would be sufficient if it was possible to self build. No need to preserve data. Currently only 1.1 really works, as with 1.3 you experience a lot of browser crashes. So i wont even try to build 1.4. Since 1.3 is out and obviously working on the Open C, can we expect any changes for the Open anytime soon? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] is there any method i can use to kill child process after killing parent process in Js
Hey, You should send this function to dev-platform as this mailing list is only meant for Firefox OS development. Thanks ! Le 29/04/2014 04:47, 丛青彬 a écrit : i encountered a problem when programming with js api nsIProcess. could you help me to resolve it. i fork a process from his parent process using nsIProcess.runAsync() when i kill the parent process , the child process is untraceable. is there any method i can use to kill child process after killing parent process ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] is there any method i can use to kill child process after killing parent process in Js
Le 29/04/2014 16:53, Julien Wajsberg a écrit : Hey, You should send this function to dev-platform as this mailing list is only meant for Firefox OS development. Obviously, I meant question here. signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Device name of ZTE Open C?
Actually, you can always flash gecko to any device. For example, I flash a gecko built using a peak config to my buri without an issue. Le 28/04/2014 15:45, Ben Kelly a écrit : I believe it uses the flame build config. At least, I can build gecko for the open-c that way. No idea if that works for the gonk layer bits. ./config.sh flame ./build.sh gecko ./flash.sh gecko On 4/25/2014 2:54 PM, Chris Mills wrote: I’d love to find more out about this device, and help to document it. anyone? Chris Mills Senior tech writer || Mozilla developer.mozilla.org || MDN cmi...@mozilla.com || @chrisdavidmills On 21 Apr 2014, at 11:11, yfy...@gmail.com wrote: Now ZTE Open C is available for order on eBay. The vendor confirmed that the device is fastboot enabled. Anyone knows the device name of it to build FFOS? This information seems missing on MDN. Regards, ___ 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 signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Hamachi build
Le 28/04/2014 08:25, Gabriele Svelto a écrit : On 27/04/2014 23:59, Sándor Csendes wrote: But it can't recognise my SIM card, and it is full of testing apps. Can you help me to make a 1.4 build that is good for daily use? Thanks! I'm not sure about the SIM problem I'm quite sure the gonk is wrong, which is expected... signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Device name of ZTE Open C?
Ah, I wasn't aware of this, thanks ! Le 28/04/2014 17:33, Mike Habicher a écrit : You can flash any gecko that is built for the correct underlying version of Gonk (i.e. ICS, JB, or KK). On 14-04-28 11:28 AM, Julien Wajsberg wrote: Actually, you can always flash gecko to any device. For example, I flash a gecko built using a peak config to my buri without an issue. Le 28/04/2014 15:45, Ben Kelly a écrit : I believe it uses the flame build config. At least, I can build gecko for the open-c that way. No idea if that works for the gonk layer bits. ./config.sh flame ./build.sh gecko ./flash.sh gecko On 4/25/2014 2:54 PM, Chris Mills wrote: I'd love to find more out about this device, and help to document it. anyone? Chris Mills Senior tech writer || Mozilla developer.mozilla.org || MDN cmi...@mozilla.com || @chrisdavidmills On 21 Apr 2014, at 11:11, yfy...@gmail.com wrote: Now ZTE Open C is available for order on eBay. The vendor confirmed that the device is fastboot enabled. Anyone knows the device name of it to build FFOS? This information seems missing on MDN. Regards, ___ 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 ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Gaia linter tests now running in TBPL
Le 26/04/2014 01:50, Jonathan Griffin a écrit : Gaia linter tests are now running in TBPL; they appear as Li and belong to B2G Desktop Linux x64 Opt builds. You can include them in try runs by specifying -u gaia-linter (or -u all). And it's effectively the same as running make lint locally. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Using blobs to display images
Le 24/04/2014 08:34, Jonas Sicking a écrit : On Sat, Apr 19, 2014 at 6:49 AM, Julien Wajsberg jwajsb...@mozilla.com wrote: At the very least you can revoke the URL when we stop displaying the image. I.e. if we change the background to some other URL, or if that part of the UI is completely hidden Yes that's also a possibility I had in mind. Aren't we taking up valuable memory if you keep the blob url valid? Or is that memory used anyway, because the image is displayed, and as a result it would not take more than what's already taken? It uses valuable memory indeed. However releasing it once the image stops being displayed is better than not releasing it at all. But note that if you get the Blob from indexedDB or from DataStore, then the Blob and bloburl uses very little memory since it's basically just a pointer into the database. Okay, good to know, thanks. (I don't know what piece of UI that we're talking about here). We're doing this in 2 parts of the UI: * displaying contacts pictures. This currently comes from the mozContacts API only. But for Facebook contacts this will eventually come from a Datastore or a local IDB as well. We might even do a local IDB for all contact's source too, in the future. So there's a risk here that we'll display a large number of images at once here. As long as all those blobs point to data in an IDB database that should be ok. Currently they don't, but they should once we use background-size. * displaying attachments. Until very recently, we were generating thumbnails using the canvas API, and export them as data url, and use this as background-image. In bug 996516 we'll take advantage of the downsamping url feature to use directly the blob url in this. The data comes from the mozMobileMessage API, and from activities. We really should not use data urls for anything. They suck up a lot of memory. Not only does it keep the whole encoded image in memory. It likely keeps several copies of it. And each copy is in a very ineffective format (130-260% of binary size) We actually tried to get rid of it earlier (bug 889902 [1]) but using blobs proved to be worse than with dataurl (see comment 21). Probably we didn't try correctly, but anyway the new try using the samplesize and background-size should be way better. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=889902 Another solution here would be if we added support for URLs that map directly into indexedDB. See http://lists.w3.org/Archives/Public/public-webapps/2013JulSep/0081.html Would that cross process boundaries? I guess not, and so would not be that useful for us. Not sure what you mean by process boundaries. IndexedDB is always accessed through the parent process. As is any time that we load something from the network. So in that sense this would indeed work across process boundaries. But if you mean being able to load another application's IDB data that would not work. But that has nothing to do with process boundaries but rather is by design. oki, that's what I wanted to mean, thanks :) -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Wow, FireFox OS 2.0's UI looks really sleek...
Please contact our legal team if you have doubts; this mailing list is not the correct place to discuss legal stuff as nobody here is a lawyer (are you?). Here is the mailing list for the legal team: https://lists.mozilla.org/listinfo/legal. You can subscribe and then participate. The archives are public. Regards, -- Julien Le 24/04/2014 08:49, Hugh Tay a écrit : On Tuesday, April 22, 2014 10:57:38 PM UTC+8, Prateek Jadhwani wrote: From what I see, its all a bunch of pixels. And no one owns pixels. Flat design is everywhere. It was in the market even before Apple implemented in iOS. So, I would not worry about it. I have my doubts about that... 1st, Apple is suing Samsung even though Android is owned by Google, and they look like they're winning. 2nd, if Mozilla isn't too bothered whether OEM partners release their source code, I wouldn't be surprised if Mozilla leaves OEM partners to fend for themselves in lawsuits. On Wednesday, April 23, 2014 12:13:08 AM UTC+8, Aaron Cajes (Mozilla PHL) wrote: But for now, it would be best if we all just focus our efforts on the topics that would move Firefox OS and everyone working around it forward. :) Sure, Mozilla releasing FireFox OS is a good thing for the community, and naturally we should all rally behind it. But if those of us who wish to sell FireFox devices have to divert resources into undoing Mozilla's work to avoid legal problems instead of building better products that customers need, how would we still have the resources to help move FireFox OS forward? signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Using mocks in integration tests
Le 24/04/2014 11:30, Zac Campbell a écrit : Would this RIL simulator go inside desktopb2g or Mulet? (Perhaps Mulet is the publicly distributed emulator) Mulet is desktopb2g inside Firefox, nothing else. signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Missed Call List
Le 24/04/2014 17:17, Natalia Martinez-Winter a écrit : It might be same as or related to Bug 988726 https://bugzilla.mozilla.org/show_bug.cgi?id=988726 ? we're still trying to find a reliable STR... Probably not the same bug :) On Thu Apr 24 02:05:38 2014, gallomi...@gmail.com wrote: Hi all. I apologize as this should probably be in the bug reporting system, but I'm using an older version of the software so I'm not sure if this one is known or not, and there's no time today to search the tracker, but I want to write about it before I forget. So I've received several calls on my device: ZTE Open running FxOS 1.1r4 (I have to perform updates when I get a chance!) The calls showed up in the notifications, with number and time and all. Tapping this results in the phone app opening with the call log displayed. This number has left a voicemail and there's a notification for that as well. But the number in question does not appear in the log! What gives? Before I go ahead and file this as a bug, has anyone else seen this behavior, or is this known, or possibly even fixed in a newer version of this OS? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g -- Natalia Martinez-Winter Channel Marketing Manager Firefox OS +33 6 88811959 nataliamozi...@skype.com @martinezwinter ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Missed Call List
Le 24/04/2014 02:05, gallomi...@gmail.com a écrit : Hi all. I apologize as this should probably be in the bug reporting system, but I'm using an older version of the software so I'm not sure if this one is known or not, and there's no time today to search the tracker, but I want to write about it before I forget. So I've received several calls on my device: ZTE Open running FxOS 1.1r4 (I have to perform updates when I get a chance!) The calls showed up in the notifications, with number and time and all. Tapping this results in the phone app opening with the call log displayed. This number has left a voicemail and there's a notification for that as well. But the number in question does not appear in the log! What gives? Before I go ahead and file this as a bug, has anyone else seen this behavior, or is this known, or possibly even fixed in a newer version of this OS? All I know is that I've seen it as well (at least in 1.3), but I don't know if this is fixed in 1.4 or 1.5. signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open - supported or not?
I think you get it by flashing gaia with MOZILLA_OFFICIAL=1 Le 24/04/2014 22:33, Roland Lindner a écrit : if you want the cool Bootanimation back, you can extract it from the 1.1 update and push it on your phone. (its bootanimation.zip located in system/media) to push it on the phone /system has to be mounted read write - connect phone adb shell toolbox mount -o remount,rw /dev/block/mtdblock5 mkdir /system/media exit adb push path-to-extract/bootanimation.zip system/media/. then either reboot and enjoy the flaming/blazing tail of the fox or mount system back to read-only: adb shell toolbox mount -o remount,ro /dev/block/mtdblock5 exit enjoy ;) ___ 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] ZTE Open - supported or not?
Le 23/04/2014 11:26, Roland Lindner a écrit : Back to report success... like i said before i reconfigured and built v1.3 with VARIANT=user after i installed v1.1 from ZTE on my inari. then i changed the boot image as stated in the blogpost and bugzilla entry, but i did not want to install cwm recovery (no use since there are no custom roms anyway and i won't be installing Android...) i also entered the init.rc changes in line 111 or so, just after /system gets mounted rw, as it seems to be the right place to do that there. i made the changes to the boot.img from my official ZTE 1.1 UK update.zip and copied the resulting new boot image into the out/target/product/inari folder. used flash.sh as normal, but now also the boot.img was flashed in the process. might not be pretty or even designed that way, but it works ;) ( i admit that i peeked at flash.sh to make sure it would actually use the boot.img, so obviously it does flash a boot.img if it is present) a few minor details are present: the resulting build on the phone is Boot2Gecko 1.3.0.0-prerelease - i thought 1.3 is the latest stable version? do i have to build different than with BRANCH=v1.3 to receive a complete v1.3 build? It's what happens when you build from source. I don't know how to get the release version. while not proud or particularly pleased by the process, i am however glad i managed to get 1.3 going on the ZTE Open. now back to the building process to refine some stuff. - i want to change the date/time to the standard german/austrian/swiss format, while keeping english as the language. (don't know if that is even possible) Currently the date/time format is really tied to the language. But maybe a english (UK) language would do this? (I don't know if we have it already) here is also one area where i would suggest as an improvement to include the choice of date/time format in the respective settings. one other thing - the developer settings are really buggy. i turned on fps by mistake and it wont let me turn it off, and also i cannot turn on developer menu, whatever that might be. i could resolve this by leaving the settings and reentering a few times, finally i could turn off fps and turn on developer menu (although i don't see what that changed) The developer menu is only in 1.4, so I wonder what you see in 1.3 here... -- Julien ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Wow, FireFox OS 2.0's UI looks really sleek...
Le 22/04/2014 14:54, Hugh Tay a écrit : Yep, it -is- good, except there's 1 tiny problem - if Microsoft can collect royalties from Android, Apple might try the same with FireFox OS. Sure no one would come after Mozilla because you guys are a non-profit, but can Mozilla's OEM partners feel safe from the mighty fruit? There is no patent on style, so please stop spreading FUD, this is unnecessary. Thanks, -- Julien ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Wow, FireFox OS 2.0's UI looks really sleek...
I am not a lawyer. Le 22/04/2014 16:50, Hugh Tay a écrit : Well, Mr. Wajsberg, could you confirm that you are speaking on behalf of Mozilla? Many thanks. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Wow, FireFox OS 2.0's UI looks really sleek...
We're glad you like it :) Le 21/04/2014 14:39, Hugh Tay a écrit : ... And Apple's lawyers are going to love it! ___ 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] I can no longer access to ZTE Open nightly updates
Le 19/04/2014 18:37, lgg2l...@gmail.com a écrit : Hello, In that way, also You must anounce OFFICIALy the END of the ZTE Open (Inari) life (and support of course). That must be because neither ZTE nor Mozilla will take anymore account about it. I think that It si not the correct way, having problems in the 1.x terminals and jumping to 2.x without solve them. After the troubles that I had with ZTE Open and seeying this blocking position of ZTE and Mozilla I (and more people I think) have something clear: - I will no change the terminal after six month because the only by the ZTE and Mozilla faulty support of it. - I will no trust more (include buy) in ZTE or Mozilla. Note that 1.3 final version was just released, so it's difficult to require an update to v1.3 from ZTE. Remember that updates is more difficult than new installs because ZTE must test carefully that your precious data is not lost. (I'm not saying they plan to provide an update to v1.3, I really don't know anything about this). About v1.4 and v1.5, Naoki is right, it was doing more harm than benefit to provide the nightlies because the phone was crashing. We need a new gonk layer for this. Hope this makes some sense. I surely hope ZTE will provide a new gonk layer for users so that we can move forward, but I don't know if they will. Regards, -- Julien ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Unable to flash Peak
Le 21/04/2014 22:49, buhory...@gmail.com a écrit : Hi I have a problem with my GP Peak, after installing the Android 4.2.2 (Lite version for Peak) zip file that is on the revolution page on the download.geeksphone.com my cell doesn't charge the system properly, it freezes on the GeeksPhone image. I can only reach the recovery menu but my computer doesn´t recognize it. I don't think flashing Revolution's Android to Peak expected to work. You should flash a Firefox OS version. I think you can put the phone in fastboot mode by first powering down the phone, then keeping vol+ and vol- pressed and then longpress power. Then you'll be able to run geeksphone's flash script from the peak's images. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Changes to Device testing starting 4/21
Does it mean we stop supporting the Buri on v1.4 and later? Le 19/04/2014 00:58, Tony Chung a écrit : Hi all, Starting on Monday, Apr 21st, the mozilla QA team will be making some adjustments in daily device testing. v1.3 - we will discontinue gaia automation test reports.Any specific bug reproductions and verifications will be on a request only basis until end of April.The device will also be against a 1.3 build of the ZTE Open C. v1.3T - Testing against the Tarako device will continue as normal for this month and next. This includes manual smoketesting, functional testrun, and prioritzed bug activity on blockers. There is also automated b2g-perf runs ongoing, but no current plans to run gaia device automation at this time. v1.4 - we will be switching off the Buri onto the Open C next monday. This will include smoketesting, functional testrun, and bugwork. We are still awaiting for the Reference devices (aka Flame) to stabilize and fix the known vendor issues (Gonk based). It’s important to start transitioning off the Buri and onto a JB device in the next weeks. Gaia Automation will also begin transitioning to the Open C and eventual Flame. v2.0 - we will slowly switch off Buris as well to open C’s/Flames, but it 1.4 takes precedence first. Once 1.4 is completed (or if more extra devices arrive), then we’ll make the full switch off of buris then. 2.0 testing and development will be targeting the Flame. Let me know if there are any questions or concerns. Tony ___ 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] Using blobs to display images
In the Messages app, we don't have several times the same image displayed in the same time... yet. But this will eventually come if we display the contact's picture in the thread view. So thanks for this bit of advice ! Le 19/04/2014 03:09, L. David Baron a écrit : Another thing that's a bit dangerous about blobs that sicking and khuey and I were discussing in person that I think is worth bringing up: If you create two blob URLs for the same Blob (or, for that matter, for different Blob objects that represent the same data), the rest of the system doesn't know that these are the same. So, for example, if they're images, you'll end up with two (identical) decoded images in the image cache, which uses more memory, since imagelib has no idea that these two blob URLs lead to the same resource. So if you're going want to use the same blob as a URL in multiple places, it's best to use the same URL. If they're stylesheets (though I admit that sounds odd), you'd end up defeating a different pile of sharing optimizations (that propagate from failing to share the sheet structures through, as a result, failing to share computed style data). And probably similar things for other types of resources. (Yes, this API seems less than ideal.) -David ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
