On 22/04/2014 09:02, Roland Lindner wrote:
so i was able to build v1.3 (without VARIANT=user)
This means that you did an engineering build. You'll find a ton of apps
used for testing on your phone, those are harmless and you can just
delete them, and you'll also have quite a few debugging
On 21/04/2014 22:49, buhory...@gmail.com wrote:
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
124 tests ran in 9744 seconds.
112 passed, 4 skipped, 1 failed, 5 errors.
5 expected failures, 1 unexpected passes.
Test failures:
test_browser_play_youtube_video.py - Bug 998896 - investigate the failure of
HTML5Player of gaiatest
test_sms_with_attachments.py - Intermittent failure.
so i updated to 1.1 and tried to build again, after moving the backup-inari
folder and configuring again with VARIANT=user.
builds ok, flash is the same as before, just without the error at the end (it
just waits forever)
this time also adb does not show the phone anymore.
recovery works, so i
so obviously its not possible to build and flash your own FFOS 1.3 without
altering the boot image, or is this conclusion wrong?
I think that's the case, apparently you need a modified boot image. Also
if the phone doesn't show up in adb (or fastboot) make sure that your
udev rules include
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?
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
El martes, 22 de abril de 2014 03:06:20 UTC-5, Gabriele Svelto escribió:
On 21/04/2014 22:49, buhory...@gmail.com wrote:
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
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
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. Although, the legal department from
Mozilla needs to take a look at it and confirm if arranging pixels in a
Hi all,
Here is todays Gaia automation results.
It looks like *Bug 987809*
https://bugzilla.mozilla.org/show_bug.cgi?id=987809 regressed again
and we see the Sift key enabled in our tests. We still have some one
blocking issue *Bug 997791*
Hi all,
Here is the automation report on Hamachi for today.
He had a green build, all tests behaved as expected.
Cheers,
Viorela
*Summary*
124 tests ran in 8262 seconds.
121 passed, 24 skipped, 0 failed, 0 errors.
3 expected failures, 0 unexpected passes.
*Test failures:*
None
*Build
Hi Roland,
Can you try checking to see if you have adb access yet via : adb devices
If you do even though you are stuck at the animation screen, can you try going
into the gaia directory and then doing a :
`make production` or a `make reset-gaia` please?
Regards,
Naoki
On Apr 22, 2014, at
I have both necessary UDEV rules, after the first v1.3 flash (with the old
1.0.B02 firmware still on it) it was still accessible via adb.
after the second v1.3 flash (reconfigure as user device, with firmware 1.1
installed) it was not accessible anymore, adb devices shows nothing.
its running on
In
https://github.com/mozilla-b2g/gaia/blob/master/apps/system/test/marionette/sim_dialog_test.jsI
would like to use one of the 3 mocks for mozMobileConnection
https://github.com/mozilla-b2g/gaia/blob/master/shared/test/unit/mocks/mock_navigator_moz_mobile_connection.jspreferably
Currently to use
Roland,
Check the Developer menu, and make sure the Remote Debugging option is
checked.
You can find it under Settings - Device Information - More Information
- Developer
That option is typically not set in user builds, and you need to set it before
the device will show up under adb
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
Mozilla doesn't need to worry for now. Apple is busy with Samsung. LOL
Kidding aside, it all boils down when Apple really sues Mozilla. And that's
the job Mozilla Legal has to deal with exclusively. But for now, it would
be best if we all just focus our efforts on the topics that would move
On 22/04/2014 17:02, Roland Lindner wrote:
is 1.3 such a big improvement over 1.1? (just checking if its all worth the
hassle)
The difference is night and day, I'd recommend giving it another try as
it's going to be well worth it. More importantly 1.3 will be shipping
soon on actual devices so
i saw the Flame reference phone.
But it's a TCL manufactured phone again - so i am not sure if it will be fully
user-upgradeable? did Mozilla make sure with TCL that we wont run into the same
problems like with the Alcatel Fire ZTE Open?
170USD is a bit steep for me for a device that i
Hi Roland and friends,
Yes, in my experience your boot issues are
Due to your stock boot.img. That seems to be the one stop everyone gets stuck
At with the Open. Look back at
Step 5 in my other post. If you follow
Edu's process for unpacking/repacking
The boot.img and make the modifications
That
Hah cool thanks, good catch
Same question applies :)
On 22 April 2014 17:02, Gabriele Svelto gsve...@mozilla.com wrote:
On 22/04/2014 17:08, Dale Harvey wrote:
https://github.com/mozilla-b2g/gaia/blob/master/apps/system/test/marionette/sim_dialog_test.js
I would like to use one of the 3
42 out of 48 tests passed for the 2014-04-22 Open_C v1.4.0 Build. There
is one existing issue involving the camera that kept the smoketests from
fully passing.
Smoketest Results:
Daily Smoke Test Logs:
48 out of 48 tests passed for the 2014-04-22 Open_C Master M-C Build.
There are no major issues preventing smoketest from passing.
Smoketest Results:
Daily Smoke Test Logs:
We'll be holding our ~30min weekly cross-functional B2G meeting today. To
participate, please join us in the B2G vidyo room and follow along with the
notes at https://etherpad.mozilla.org/b2g-meeting-notes. See
https://wiki.mozilla.org/B2G#Meetings for more info on joining the call.
Thanks,
42 out of 48 tests passed for the 2014-04-22 Tarako v1.3t Build. There are
three existing issues that kept the smoketests from fully passing.
Two invalid TCs:
- no Persona support for Tarako, see bug
https://bugzilla.mozilla.org/show_bug.cgi?id=990560#c18
- the usage widget in the
On 04/22/2014 03:23 AM, Gabriele Svelto wrote:
Once you did this you'll have to modify and reflash your boot image,
this link should help with that:
http://blog.chellinsky.net/putting-firefox-os-v1-4-on-a-zte-open/
(note that the author claims to have succeeded in getting 1.4 on his
phone, I
Haha followed the link to Andrew Chellinsky's blog, looks like he's got
a good summery already.
Wish I would've had that link weeks ago when I was struggling with my Open.
Nothing like reinventing the wheel I guess.
-Foo
On 04/22/2014 01:10 PM, Roland Lindner wrote:
thanks for the offer
Thank you Julien for your tips. I was hoping that the more experienced
folks on
the list would chime in about were my process needed refinement or was
in error
(after all I wrote in to help Roland avoid the frustration I ran into
not confuse him).
-Foo
On 04/22/2014 03:38 AM, Julien Wajsberg
On 19 Apr 2014, at 11:42 am, Jonas Sicking jo...@sicking.cc wrote:
On Thu, Apr 17, 2014 at 4:07 AM, Paul Theriault ptheria...@mozilla.com
wrote:
Both APIs have a similar prompt, and would likely have a similar name in the
settings app, possibly leading to confusion for the user. So I think
30 matches
Mail list logo
