On Thursday, February 6, 2014 1:24:59 PM UTC+8, Jose Vidal wrote:
But, this binary files (inside the device) are in Android repository ?. I
mean, How are generated these binary files ?
Regards.
jvidalsm
Some files are under /vendor folder, they are proprietary, so files depend on
how chipset
That's something that's been suggested the CC/Usage app does system-wide
for a long time, in relation with the whole offline experience.
On Thu, Feb 6, 2014 at 2:48 AM, Jonas Sicking jo...@sicking.cc wrote:
Do networks even signal to the device that it is offline due to
insufficient funds?
Hi All !
I'm looking for information regarding to those 2 branches :
remotes/origin/v1.3
remotes/origin/v1.3t
What are the difference and which one I have to choose in order to be
the most up to date ?
I looked for it in the bugzilla but i found nothing.
Thank you
Le 06/02/2014 10:10, BenNG a écrit :
Hi All !
I'm looking for information regarding to those 2 branches :
remotes/origin/v1.3
remotes/origin/v1.3t
What are the difference and which one I have to choose in order to be
the most up to date ?
I looked for it in the bugzilla but i found
I faced the same issue.
As a workaround, it's possible to install your own certificates on your
Firefox OS device.
There has been a discussion about that earlier on this same
mailing-list. See
https://groups.google.com/d/msg/mozilla.dev.b2g/vAImRu4r3n0/fWbCiYZ2lxEJ
Le 06/02/2014 05:06, jbc a
Le 06/02/2014 13:30, Mossroy a écrit :
I faced the same issue.
As a workaround, it's possible to install your own certificates on your
Firefox OS device.
I documented this a while back there:
http://wiki.mozfr.org/Adding_CA_to_FirefoxOS
There has been a discussion about that earlier on
Yes, see the link in the first email.
-Ryan
- Original Message -
From: Kyle Huey kh...@mozilla.com
To: Ryan VanderMeulen rvandermeu...@mozilla.com
Cc: dev-b2g dev-b2g@lists.mozilla.org, b2g-internal
b2g-inter...@mozilla.org
Sent: Thursday, February 6, 2014 12:09:06 AM
Subject: Re: B2G
Hi Fabrice,
On Thursday, February 6, 2014 3:05:49 AM UTC+8, Fabrice Desré wrote:
You can't do that from the browser for now.
OK, suppose I want to create a browser app specially to browse web pages stored
on my SD-card, what would my options be?
Thanks!
Hugh
Hi all,
Looks like we are still affected by *Bug 968501*
https://bugzilla.mozilla.org/show_bug.cgi?id=968501 -[Buri] Keyboard
doesn't show at all on latest nightly build
We can't generate a automation report today.
Sorry,
Bebe
___
dev-b2g mailing
Thank you for the responses.
The easy way, i think:
If the caldav server have public url. You can open browser. Visit the url.
Accept certificate. And caldav ok.
But. Why browsers always is so alarming with autosigned certificates?
In desktop, mobile devices is impossible to create a
Shawn is right, it does highly depend on the vendors. Almost all are
proprietary, we don't release the blobs. You have to supply them yourself and
that is why there's an extract script to extract those blobs from the device
themselves. You can look through the repository and find it.
- Original Message -
From: Ryan VanderMeulen rvandermeu...@mozilla.com
To: dev-b2g dev-b2g@lists.mozilla.org, b2g-internal
b2g-inter...@mozilla.org
Sent: Wednesday, February 5, 2014 6:52:53 PM
Subject: B2G branching reminder
As of Monday's uplift, the Gecko side of B2G v1.3 now
Hello,
This is Srinivasan.N,I am indie games
developer from India and working for Pixeldruids Studios Pvt ltd.I have
good experience in developing and publishing games for various platforms
like iOS ,Android, Samsung Store, Playfone Store,Windows phones,Amazon and
Hi,
Self-signed certs are currently not supported by the low level TCPSocket
implementation on Firefox OS, and there is no UI for allowing the user
to decide whether or not to trust a self-signed cert. We definitely want
to add this, but I searched and don't see a bug about implementing it.
Hello Srinivasan,
You might want to try Ebay for some ZTE open devices and Geeksphone for
peak and keon. But Ebay US sites should help you out.
*Prateek Jadhwani*
www.prateekjadhwani.com
On Thu, Feb 6, 2014 at 3:41 PM, Srini radnussr...@gmail.com wrote:
Hello,
Yesterday I submitted a bug about the keyboard keys in v1.2 always
displaying a CAPITAL letter even though the keypress will result in a
lower case letter. My bug was marked as invalid because someone made
the design decision that the keyboard keys should not display the
character that will result
The APC Paper comes with an SD Card browsing app called Prospector.
You could find it in their source code repository and see if it works
for you.
Donovan
On 2/6/14, 9:24 AM, Hugh Tay wrote:
Hi Fabrice,
On Thursday, February 6, 2014 3:05:49 AM UTC+8, Fabrice Desré wrote:
You can't do that
Hey Hugh!
I am the main developer of Prospector. If you would like to get
involved with the project, that would be great!
- Josh
On 2/6/14, 1:04 PM, Donovan Preston wrote:
The APC Paper comes with an SD Card browsing app called Prospector.
You could find it in their source code repository
Hi Daniel:
I was looking on your site GitHub you're having problems with the Bug #965180.
My question is Is there the same problem in the latest build of version 1.3? Is
that I got this file[1] and want to upgrade my ZTE.
Thanks
[1]
El jueves, 6 de febrero de 2014 14:28:01 UTC-5, Ernesto Acosta escribió:
Hi Daniel:
I was looking on your site GitHub you're having problems with the Bug
#965180. My question is Is there the same problem in the latest build of
version 1.3? Is that I got this file[1] and want to
Hello all. Is there a file list, or a variables file that is created when you
run build.sh, and if so, where is it so it can be removed?
I had a build with a specific rom. I then changed roms, deleted the build and
the backup-galaxys2 directories, then ran the build.sh again.
it failed with
Hey Daniel, in the compilations is available for 1.3 Is there any I can use?
Not if you have upgraded to the 1.1 ZTE firmware. The boot.img used in
the available download is based on the old 1.0 ZTE firmware, and I
can't seem to build a nightly (with or without the old custom
boot.img) that
45 out of 48 tests passed for the 2014-02-06 Buri v1.3.0 MOZ RIL Build.
There is one existing issue that kept the smoketests from fully passing.
MOZ RIL Build Smoketest Results:
Daily Smoke Test Logs:
45 out of 48 tests passed for the 2014-02-06 Buri Master M-C Mozilla RIL
Build. There are three existing issues that kept the smoketests from
fully passing. The issue with the keyboard not showing up still existed
in this build so we used the workaround
Jezra, I agree with your WYSIWYG keyboard preference, but there is a
major precedent for only displaying capital letters on the keys: iOS.
chris
On 2/6/14, 9:52 AM, jezra wrote:
Yesterday I submitted a bug about the keyboard keys in v1.2 always
displaying a CAPITAL letter even though the
How probably is it that the performance hit was caused by switching the
case of text as opposed to using complex borders and gradients on each
key? Not very.
Since late October, I've been using the ZTE Open as my sole mobile
phone and haven't noticed any significant improvements in the keyboard
On 07/02/14 13:51, Chris Peterson wrote:
Jezra, I agree with your WYSIWYG keyboard preference, but there is a
major precedent for only displaying capital letters on the keys: iOS.
Android
W
--
The only true evil is turning people into things
So FirefoxOS should just think different and copy iOS? ;)
Hard as it may be for some to believe, but just because Apple does
something, doesn't mean it is good for the users.
On Thu, 06 Feb 2014 16:51:06 -0800
Chris Peterson cpeter...@mozilla.com wrote:
Jezra, I agree with your WYSIWYG
On 06/02/14 12:52 PM, jezra wrote:
Yesterday I submitted a bug about the keyboard keys in v1.2 always
displaying a CAPITAL letter even though the keypress will result in a
lower case letter. My bug was marked as invalid because someone made
the design decision that the keyboard keys should not
You can find some background and bug links on this old thread
https://groups.google.com/d/topic/mozilla.dev.gaia/U9QNoya8HLk/discussion
TLDR is: there was a perceived performance issue with the old way, and
the new way feels faster.
That does not mean this decision is final.
Le 06/02/2014
On Friday, February 7, 2014 2:13:27 PM UTC+7, Julien Wajsberg wrote:
You can find some background and bug links on this old thread
https://groups.google.com/d/topic/mozilla.dev.gaia/U9QNoya8HLk/discussion
TLDR is: there was a perceived performance issue with the old way, and
the new
On 6 Feb 2014, at 22:01, Daniel Roesler diaf...@gmail.com wrote:
Hey Daniel, in the compilations is available for 1.3 Is there any I can use?
Not if you have upgraded to the 1.1 ZTE firmware. The boot.img used in
the available download is based on the old 1.0 ZTE firmware, and I
can't seem
32 matches
Mail list logo
