Re: [b2g] B2G stuck at bootanimation, services died

[Marco Chen]

Hi Subin,

Maybe you just need to run "run-gdb.sh" in the b2g repo and see where is
the crash point.

Sincerely yours.

On Wed, Apr 29, 2015 at 1:07 AM, Alexandre Lissy  wrote:

> Le 28/04/2015 13:49, Subin PT a écrit :
> > Hi,
> >
> > I am new to B2G. Trying to port it on to a development board. I am able
> to reach till boot animation and then the services are stopping. I am not
> able to see what caused this. Can someone please help me analyzing the
> problem? Some pointers on what to check.
> >
> > This is what I see in the log.
> >
> > I/GeckoDump( 1192): XXX FIXME : Got a mozContentEvent:
> system-message-listener-ready
> > I/Gecko   ( 1192): Attempting load of libEGL.so
> > D/libEGL  ( 1192): loaded /system/lib/egl/libEGL_mali.so
> > D/libEGL  ( 1192): loaded /system/lib/egl/libGLESv1_CM_mali.so
> > D/libEGL  ( 1192): loaded /system/lib/egl/libGLESv2_mali.so
> > I/GeckoConsole( 1192): OpenGL compositor Initialized Succesfully.
> > I/GeckoConsole( 1192): Version: OpenGL ES 2.0
> > I/GeckoConsole( 1192): Vendor: ARM
> > I/GeckoConsole( 1192): Renderer: Mali-400 MP
> > I/GeckoConsole( 1192): FBO Texture Target: TEXTURE_2D
> > I/ServiceManager( 1180): service 'media.resource_manager' died
> > I/ServiceManager( 1180): service 'SurfaceFlinger' died
> > I/ServiceManager( 1180): service 'permission' died
> > I/ServiceManager( 1180): service 'android.security.keystore' died
> > I/ServiceManager( 1180): service 'media.audio_flinger' died
> > I/ServiceManager( 1180): service 'media.player' died
> > I/ServiceManager( 1180): service 'media.camera' died
> > I/ServiceManager( 1180): service 'media.audio_policy' died
>
> Gecko is crashing.
>
> >
> > Full logcat output is at: http://pastebin.com/kk22ArHh
>
> I see gralloc errors, so it's not surprising ... You're a bit on your
> own if gralloc do not works on your board.
>
> >
> > When I try to run b2g.sh manually, I get the following
> > [32392] WARNING: Tried to RegisterCallback without an AtExitManager:
> file ../../../gecko/ipc/chromium/src/base/at_exit.cc, line 40
> > *
> > ***
> > *** This is stdout. Most of the useful output will be in logcat.
> > ***
> > *
> > JavaScript error:
> jar:file:///system/b2g/omni.ja!/components/XULStore.js, line 66:
> NS_ERROR_FAILURE: Component returned failure code: 0x80004005
> (NS_ERROR_FAILURE) [nsIProperties.get]
> > [Parent 32381] WARNING: pipe error (73): Connection reset by peer: file
> ../../../gecko/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 456
> > [Child 32392] WARNING: pipe error (11): Connection reset by peer: file
> ../../../gecko/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 456
> >
> > b2g-info shows
> >  | megabytes |
> >   NAME  PID PPID CPU(s) NICE  USS  PSS  RSS SWAP VSIZE OOM_ADJ USER
> >b2g 29211   22.20 44.7 52.3 61.2  0.0 144.7   0 root
> > (Nuwa) 2953 29211.40  8.0 14.8 21.8  0.0  64.5 -16 root
> >
> > System memory info:
> >
> > Total 354.1 MB
> > SwapTotal   0.0 MB
> >  Used - cache  73.8 MB
> >   B2G procs (PSS)  67.1 MB
> > Non-B2G procs   6.7 MB
> >  Free + cache 280.3 MB
> >  Free 175.1 MB
> > Cache 105.3 MB
> >  SwapFree   0.0 MB
> >
> > Low-memory killer parameters:
> >
> >   notify_trigger -1 KB
> >
> >   oom_adj min_free
> >     0  4096 KB
> > 1  5120 KB
> > 2  6144 KB
> > 6  7168 KB
> > 8  8192 KB
> >10 20480 KB
> > Thanks and Regards,
> > Subin
> > ___
> > 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
>



-- 
-
Marco Chen
Engineering Manager
Connected Device, Firefox OS Devices
Mozilla Corporation
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

Re: [b2g] New peers for Bluetooth module

[Marco Chen]

\o/ It is great to hear this and you really deserve it.

Congratulation!

On Mon, Apr 13, 2015 at 11:46 AM, Aaron Wu  wrote:

> Jocelyn,
>
> Congratulation!!
>
>
> Aaron Wu
> Engineering Project Manager, Mobile Device
> Mozilla Corporation
>
>
>
> On Mon, Apr 13, 2015 at 11:41 AM, Shawn Huang  wrote:
>
>> Hi B2G folks,
>>
>> I am glad to announce Jocelyn Liu (:jocelyn) is now a peer for the
>> Bluetooth module [1].
>>
>> Jocelyn has been dedicated to the module since the first day she joined
>> Mozilla. She did a great job of bug fixing, new Bluetooth API V2 design and
>> implementation[2], Low energy GATT API  feature implementation [3]. She has
>> been proving her knowledge, passion, insights for the module. She truly
>> deserves this glory. I believe with her expertise, we can continuously make
>> Bluetooth module improve significantly!
>>
>> Thank you Jocelyn for the fantastic work. :)
>>
>> [1] https://wiki.mozilla.org/Modules/FirefoxOS#Bluetooth
>> [2] https://wiki.mozilla.org/B2G/Bluetooth/WebBluetooth-v2
>> [3]
>> https://groups.google.com/forum/#!topic/mozilla.dev.bluetooth/M68qNLdWJGk
>> <https://groups.google.com/forum/#%21msg/mozilla.dev.b2g/MVwLCASwFF8/X3hhGycCobcJ>
>>
>> --
>> Regards,
>> Shawn
>>
>> ___
>> 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
>
>


-- 
-
Marco Chen
Engineering Manager
Connected Device, Firefox OS Devices
Mozilla Corporation
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

[b2g] 64 bits CPU on mobile industry and towards to TV

[Marco Chen]

Hi,

Since Apple A7 64 bit iphone came to the world, mobile industry started to
catch up 64 bits CPU. And it becomes a marketing term to promote the
product [1]. Not only mobile but also TV industry is joining this trend for
giving their product more advertising point. Based on this direction I
would like to know how FxOS is preparing for it and what benefit FxOS can
get from 64 bits CPU.

Q1: Is Firefox ready for 64 bit platform like Win 64 and linux 64? (I think
we already have release for 64 bits platform) And what is the downside or
benefit compared to 32 bits CPU? (ex: memory consumption / JIT performance)

Q2: [1] also mentioned the more important change on mobile chip set is from
armv7 to armv8. And it needs some works to optimize codes for leveraging
new instructions. May I know the status of Firefox optimized for armv8 64
bits? (ex: JIT, Graphics and SW Codes)

[1]
http://www.greenbot.com/article/2686007/why-you-will-and-won-t-want-a-64-bit-android-phone.html

Thanks,
Sincerely yours.

-
Marco Chen
Engineering Manager
Connected Device, Firefox OS Devices
Mozilla Corporation
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

Re: [b2g] For v2.2: distributable certified apps

[Marco Chen]

Hi all, 

I would like to echo this requirement from James because it is also requested 
by partners. 
And the reasons are 

1. Partners would like to build their own pre-installed and certified apps for 
differentiating their own product. 
And they need a way to upgrade these apps (the tied schedule may push them to 
ship first with small bugs). 
The cost of the only way now - FOTA/OTA is expensive then just doing a single 
application upgrade. 

2. In order to co-work with other service providers in the world, partners may 
need to create their own APIs for fulfilling various requirements. 
And partners also want to keep Web consistency so their APIs will be certified 
type only. 
Due to this vision, their apps can not be installed or upgraded from market 
place because our capability now. 

3. I also think that in the emerging market the narrow bandwidth is not 
suitable for doing FOTA/OTA. 
But an upgrade per app may be more easy there. 

So vote to this requirement. 

Thanks, 
Sincerely yours. 
- Original Message -

From: "James Burke"  
To: dev-b2g@lists.mozilla.org 
Sent: Thursday, October 23, 2014 3:07:54 AM 
Subject: [b2g] For v2.2: distributable certified apps 

For 2.2, I would like to see an exploration into allowing Gaia apps, and apps 
that can use certified APIs, to be distributed via marketplace channels, and 
updated outside full OS updates. 

That could take a few forms, including just pushing more/all certified APIs to 
"privileged" status. However, I expect that may not be feasible, so right now I 
am assuming there will be a continued need for "certified" apps. 

I wrote up something about this capability here: 

https://github.com/jrburke/certified-marketplace 

Feel free to file issues in that repo if you have questions about it. Happy to 
move the info elsewhere, just wanted to get something up. 

More importantly, it would be good to figure out the relative priority of this 
sort of feature for 2.2, which is the primary point of this thread. 

This sort of capability could be in opposition to some of the UX or product 
features. 

For example, I am thinking of the "themeable" feature, to allow apps to be 
themed, and to have that theming coordinated across apps, and for apps to have 
a specific dependency on a theme.gaiamobile.org "app". 

However, this type of app distribution capability is very fitting for our 
mission, as it allows more people to make certified apps (after being vetted in 
some way) and to allow those apps to get updates outside of full OS updates. 

--- 

If this is just too big of a project for 2.2, then I would like to get an 
awareness or some sort of agreement for allowing individual apps to follow this 
path, and to realize it may mean those apps are not able to meet some other 
goals if they pursue this route. 

Specifically, I work on the email app, and I believe we could still get to a 
"updatable via marketplace", and I would like to try for that for 2.2: 

Email app goes privileged, and the app just lives with what is available to 
privileged apps. I think this is possible and still have a great, usuable email 
app. 

However, it means email not picking up any gaia-wide efforts that my require 
certified stuff. For 2.2, that could mean things like theming and if custom 
elements are not fully enabled for non-certified use, any common building 
blocks. 

Even if custom elements are available for 2.2, I am sure there will be other 
things in other releases, just pointing out the need to get wider agreement 
this pathway is OK for some apps that may be seen as part of "gaia". 

It also means possible modifications to the l10n.js capability to load 
localizations from app storage, and to do downloads of localization bundles 
from somewhere. While I am willing to do the modifications, it would still 
require some impact on reviewers' time, and likely some server work. 

To clarify: I want to preserve the existing localizer workflow, just want to 
modify how an app pulls in the final localizations, see above link for some 
more background. 

--- 

In summary: I would like this “certified” capability considered for 2.2. I am 
not expecting an immediate resolution, as all the 2.2 work needs to be balanced 
in total, and is still in planning. 

This is just to get it on the radar and to call out some of the tensions. Also, 
dev could start some plumbing now while planning is still in progress, and 
where it makes sense for the email app, I will start exploring in these areas. 

James 

(sending to dev-b2g, as it seems the most appropriate for what this capability 
spans, and want to avoid cross posting to multiple lists) 


___ 
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] Application scopes

[Marco Chen]

Hi, 

> It will be mapped to the real package on the host side. The end goal is 
> to get rid of app:// urls. We can't do that right away so we'll have a 
> transition period where we support both app:// and !// packages. 

Since app:// will be got rid of, there will be no installed packaged apps in 
the future. (no app:// to point local packaged app) 
Because http://XXX!// will always point to real package on the host side. 

Q1-1 Am I right of getting rid of app:// equals to get rid of installed 
packaged app? 

Q1-2 If answer is no, how do we plan to map packaged app on the device? 

Q1-3 if answer is yes, from permission point of view, the hosted (and packaged) 
app can not get more permissions then installed packaged app. 
Because we can't guarantee package which is located on remote host and not 
controlled by us will never be altered as malicious intent. 
Then how does developer build a hosted app which needs permissions belonged to 
installed packaged (privileged) app? 

Thanks for your kindly response. 
Sincerely yours. 

- Original Message -

From: "Fabrice Desré"  
To: "Marco Chen"  
Cc: "Jonas Sicking" , "Ben Francis" , 
"dev-webapi" , dev-b2g@lists.mozilla.org, "Marcos 
Caceres"  
Sent: Tuesday, August 19, 2014 9:02:41 AM 
Subject: Re: Application scopes 

On 08/18/2014 04:04 AM, Marco Chen wrote: 
> Hi Fabrice, 
> 
> Thanks for your answer and allow me to explain more about question 2 & 3. 
> 
> (It seems that I am talking about installed app but you mention hosted app) 
> 
> 1. In case that I submitted two apps into market place. 
> For the first app A I set origin into manifest (ex: 
> game.testmobile.org). 
> For the second app B I didn't set origin into it. 
> 
> 2. After installing into device, the origin of first app A will be 
> "game.testmobile.org". (ex: app://game.testmobile.org) 
> And the second app B will be "uuid". (uuid is a random number 
> generated by system) (ex: app://uuid) 
> 
> Q2-1, is URL of "http://game.testmobile.org/package.zip!//index.html"; 
> mapped to installed & privileged app A on device or 
> the real package on remote host side? 

It will be mapped to the real package on the host side. The end goal is 
to get rid of app:// urls. We can't do that right away so we'll have a 
transition period where we support both app:// and !// packages. 

> Q2-2, if game.testmobile.org is set as the scope attribute in app A's 
> manifest, does it still act like what hosted app will be? 

scopes need to be same origin, so this will not match. 

> Q3-1, According to origin of app B is "uuid", could we really use 
> "http://uuid/package.zip!//index.html"; to represent it? 

No, we want http urls to point to real resources. 

> Even the answer is yes, it seems to be unique identifier in 
> this device only but not a universal one across devices. 
> Based the conclusion here, could I say app scheme still can't 
> be eliminated by "http://XXX/package.zip!//index.html 
> <http://game.testmobile.org/package.zip%21//index.html>"? 

In general, we won't try to make app:// and http:// urls work together. 
We will deprecate app:// and I don't see any use case we support with 
app:// that we can't achieve with !// 

Fabrice 
-- 
Fabrice Desré 
b2g team 
Mozilla Corporation 

___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

Re: [b2g] Application scopes

[Marco Chen]

Hi Fabrice, 

Thanks for your answer and allow me to explain more about question 2 & 3. 

(It seems that I am talking about installed app but you mention hosted app) 

1. In case that I submitted two apps into market place. 
For the first app A I set origin into manifest (ex: game.testmobile.org). 
For the second app B I didn't set origin into it. 

2. After installing into device, the origin of first app A will be 
"game.testmobile.org". (ex: app://game.testmobile.org) 
And the second app B will be "uuid". (uuid is a random number generated by 
system) (ex: app://uuid) 

Q2-1, is URL of " http://game.testmobile.org/package.zip!//index.html " mapped 
to installed & privileged app A on device or 
the real package on remote host side? 

Q2-2, if game.testmobile.org is set as the scope attribute in app A's manifest, 
does it still act like what hosted app will be? 

Q3-1, According to origin of app B is "uuid", could we really use 
"http://uuid/package.zip!//index.html"; to represent it? 
Even the answer is yes, it seems to be unique identifier in this device only 
but not a universal one across devices. 
Based the conclusion here, could I say app scheme still can't be eliminated by 
" http://XXX/package.zip!//index.html "? 

Thanks, 
Sincerely yours. 


- Original Message -

From: "Fabrice Desré"  
To: "Marco Chen" , "Jonas Sicking"  
Cc: "Ben Francis" , "dev-webapi" 
, dev-b2g@lists.mozilla.org, "Marcos Caceres" 
 
Sent: Saturday, August 16, 2014 12:29:35 AM 
Subject: Re: Application scopes 

Hi Marco, 

I'm not Jonas, but I think I know some of the answers. 

On 08/15/2014 12:24 AM, Marco Chen wrote: 
> Hi Jonas, 
> 
>> Once we implement the "http://foo.com/package.zip!//file.html"; URLs 
>> for packaged apps, it should work just like for hosted apps. 
> 
> Q1: May I know Firefox already has the decision to support it or not? 
> If answer is yes, does it only support by Firefox or other browser 
> vendors also? 

The plan is for now to enable that only on b2g. We'll need to get the 
!// vetted by standards bodies like w3c and ietf, which is likely a long 
road. 

> Q2: For hosted apps, system always looks for the resources from app 
> cache first then external web site. 
> For privileged apps, do we need "app scope" been supported first or 
> looking for resources inside the device then external one in default? 

I'm not sure to understand you question. With or without app scopes 
(which are mostly fancy redirects) we will got the cached version 
whenever it's available - in the http://foo.com/package.zip!//file.html 
case we keep the zip around. 

> Q3: How about the support of these privileged apps without origin 
> definition in their manifest? 
> Their origin will be the UUID generated by device then how do we 
> use http scheme to represent them? 

With http://foo.com/package.zip!//file.html we don't need origin support 
in the manifest anymore. These apps get their origin from the manifest 
url. For some use cases like checking csp we need to consider 
http://foo.com/package.zip as the 'self' scope though, and there are 
other issues around origins that Jonas and Paul are figuring out. 

Fabrice 
-- 
Fabrice Desré 
b2g team 
Mozilla Corporation 

___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

Re: [b2g] Application scopes

[Marco Chen]

Hi Jonas, 

> Once we implement the "http://foo.com/package.zip!//file.html"; URLs 
> for packaged apps, it should work just like for hosted apps. 

Q1: May I know Firefox already has the decision to support it or not? 
If answer is yes, does it only support by Firefox or other browser vendors 
also? 

Q2: For hosted apps, system always looks for the resources from app cache first 
then external web site. 
For privileged apps, do we need "app scope" been supported first or 
looking for resources inside the device then external one in default? 

Q3: How about the support of these privileged apps without origin definition in 
their manifest? 
Their origin will be the UUID generated by device then how do we use http 
scheme to represent them? 

Thanks, 
Sincerely yours. 
- Original Message -

From: "Jonas Sicking"  
To: "Ben Francis"  
Cc: "dev-webapi" , "Fabrice Desré" 
, dev-b2g@lists.mozilla.org, "Marcos Caceres" 
 
Sent: Friday, August 15, 2014 2:39:49 AM 
Subject: Re: Application scopes 

On Thu, Aug 14, 2014 at 6:16 AM, Ben Francis  wrote: 
> On Wed, Aug 13, 2014 at 11:19 PM, Jonas Sicking  wrote: 
>> 
>> How will scopes solve that? Say that App A navigates to URL X which is 
>> not in A's "scope", but is in A's "open-in-app", then X will be loaded 
>> within A. 
>> 
>> The user then goes to app B which also navigates to X, and X is not in 
>> B's "scope", but is in B's "open-in-app". 
>> 
>> Finally the user opens pulls down the rocketbar and types the X URL. 
>> Do we now open X in A, in B or in the system browser? 
> 
> I would say that URL X is still not in the "scope" of any app so in the case 
> of being manually entered into the Rocketbar it should open in a browser 
> window, regardless of what app(s) it has previously been opened in. 
> 
>> Another edge case is if the user brings up the rocketbar, which 
>> contains the current URL of the current page, and that page is outside 
>> of "scope", but inside of "open-in-app" of the current page, and then 
>> simply presses "enter". Does that reload the current page within the 
>> current app. Or does it switch to the browser app. 
> 
> That is a good question. I would say it also opens a browser window, but 
> that may feel a little strange in practice. Currently we don't display URLs 
> in the Rocketbar for hosted apps so that isn't a problem. 
> 
> 
> Another question which was brought up in bug 996039 was how application 
> scope should work for packaged apps. 

Once we implement the "http://foo.com/package.zip!//file.html"; URLs 
for packaged apps, it should work just like for hosted apps. 

The only thing that's special is that we should somehow default the 
scope for a packaged app to be just the package itself. Not the whole 
package's origin. 

/ Jonas 
___ 
dev-webapi mailing list 
dev-web...@lists.mozilla.org 
https://lists.mozilla.org/listinfo/dev-webapi 

___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

Re: [b2g] New peers for Bluetooth module

[Marco Chen]

Congrats to Shawn, Ben and Thomas. 
And wearable device on FxOS will expect and rely on all your works. 

- Original Message -

From: "Eric Chou"  
To: dev-b2g@lists.mozilla.org 
Cc: "Shawn Huang" , "Ben Tian" , "Kyle 
Machulis" , "Thomas Zimmermann" 
, "Gina Yeh"  
Sent: Friday, May 9, 2014 10:43:52 AM 
Subject: [b2g] New peers for Bluetooth module 

Hi B2G folks, 

For the past two years, Bluetooth module has been developed 
from nothing. Now we have supported essential Bluetooth 
profiles from Firefox OS 1.2 and have a Bluetooth team which 
is working on making Bluetooth module more integrated and 
more stable[1]. Moreover, for the next half year, we have a 
plan to refine WebBluetooth API and would like to expose it[2]. 

Our original module peers, Kyle Machulis and Gina Yeh, both 
dedicated more than one year to Bluetooth module and had done 
a fantastic job. Since they have switched to other areas, with 
the growth of features and issues, I think it's time to have 
new module peers so that I won't be the bottleneck of the 
review process. 

After discussed with Kyle and Gina, I would like to announce a 
change to the Bluetooth module peer list: Ben Tian, Shawn Huang 
and Thomas Zimmermann are now new Bluetooth peers. They have 
not only shown their passion for writing good code and making 
Bluetooth module better -- each of them has contributed more 
than 50 patches for the module, but also gave us so many useful 
advices and feedback on patches, codes and strategy. In addition, 
Kyle and Gina will 'retire' from the team. Thank you so much for 
your excellent work! 

>From now on you can ask Ben, Shawn and Thomas for their help to 
review your Bluetooth patch. Since there are different layers and 
components inside the module, according to the code your patch 
modifies, you can refer to [3] to find the most appropriate reviewer. 

Many thanks! 

Eric Chou (Hung-Jen Chou) 
Sr. Software Engineer 
Mozilla Taiwan 

[1] https://wiki.mozilla.org/B2G/Bluetooth 
[2] https://groups.google.com/forum/#!topic/mozilla.dev.webapi/SSVxpdq_lfQ 
[3] https://wiki.mozilla.org/B2G/Bluetooth#Team_Members 
___ 
dev-b2g mailing list 
dev-b2g@lists.mozilla.org 
https://lists.mozilla.org/listinfo/dev-b2g 

___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

[b2g] Features Implemented by Standard but not Common V.S. None Standard but Popular in Market

[Marco Chen]

Hi all, 

As a web platform, FxOS always follow the standard and join to create the 
standard. 
As a mobile OS, FxOS always tries to give user more great experience and enrich 
their live then bringing in more devices and people into web. 
As a device partner using mobile OS, I would like FxOS to support more popular 
and common features in the market not the feature came or implemented by 
standard but not be supported in the market. 
As a user, I would expect my device and OS can perform most of popular service 
in the market now. (and actually user don't care it's standard or not) 

My question is 
For a new feature, firstly people would like to find any current standards 
which can be combined to achieve the feature even this combination is more 
complicated. 
But why don't we investigate a new one to let things go easily or leverage the 
existing way in the market now? 

Example 1: HTTP Live Streaming 
According to MSE, gecko removed to support DASH and move it to be a dash.js + 
MSE. 
Then people expected that HLS should be implemented by something like hls.js + 
MSE because it can be adapted to standard and scalable on different manifest 
mechanisms. 
But the practical fact is that the current content providers and their apps 
expected m3u8 URL can be put into src of video tag then starting to enjoy 
video. 
Therefore the ideal way using standard to support HLS is no useful for many 
popular content services in the market. 
Force them to adapt our way or let things to easily since there is no standard 
on HLS to push hls.js + MSE. 

Example 2: DLNA 
Opera introduced Network Device Discovery API (working draft) and there are 
UDP/TCP Web Socket are introduced too. 
So people started to think DLNA can be adapted by these Web API and some 
implementation on Web Content (ex:upnp_av_profile.js + UDP/TCP Web Socket). 
But the practical fact is that device partner want to leverage a 3rd party 
library into their platform which is confirmed to pass the certification and 
guaranteed stability. 
Also 3rd party library can cover others like DTCP which is no standard web api 
announced to cover yet. (maybe can be covered by some combination) 
Force device partner to take back the effort or let them have a way to leverage 
existing way in the market now? 

>From my point of view, to support m3u8 in video tag and propose a new DLNA web 
>api which allow user agent to leverage 3rd library are my hope. 

Thanks, 
Sincerely yours 
----- 
Marco Chen 
Engineering Manager 
Emerging Device, Device Engineering 
Mozilla Taipei 

Tel: +886-2-87861100 # 352 
mail: mc...@mozilla.com 

___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

Re: [b2g] Porting guide for Firefox OS

[Marco Chen]

Hi Chris, 

> I would be happy to help place some of this content on MDN Marco, but you’ll 
> have to help me place it. 
Of course, that is what we should do. 

> Is this better placed under architecture, or developing? Do you think this is 
> useful for external contributors, or more just background information? 
Giving my opinion first. Under developing and for external contributors. 

The initial goal of this is to provide our potential and existing partners a 
view about the porting effort of FxOS on different platform conditions. 
So it is useful for external contributors I think. 

Thanks. 
Sincerely yours. 

- 原始郵件 -

寄件者: "Chris Mills"  
收件者: "Marco Chen"  
副本: "Thomas Zimmermann" , "Gina Yeh" 
, dev-b2g@lists.mozilla.org 
寄件備份: 2014 3 月 21 星期五 下午 10:36:32 
主旨: Re: [b2g] Porting guide for Firefox OS 

I would be happy to help place some of this content on MDN Marco, but you’ll 
have to help me place it. 

Is this better placed under architecture, or developing? Do you think this is 
useful for external contributors, or more just background information? 

On 16 Mar 2014, at 14:08, Marco Chen  wrote: 

> Hi Thomas and Chris, 
> 
> Thanks for your useful input and great support on writing the MDN. 
> 
> Another info we can provide are 
> 1. To list AOSP properties which Gecko relied on. 
> 2. To show what modification made for repos outside the Gecko/Gaia are 
> necessary. 
> 3. To show what pixel formats (YUV variation) Gecko can support. 
> 
> One example are listed at the link as below. 
> https://wiki.mozilla.org/TPESystem/Media/DevicePortingIssues 
> (Thanks for Bruce Sun's contribution.) 
> 
> Sincerely yours. 
> 寄件者: "Chris Mills"  
> 收件者: "Thomas Zimmermann" , "Gina Yeh" 
>  
> 副本: dev-b2g@lists.mozilla.org 
> 寄件備份: 2014 3 月 12 星期三 下午 4:59:51 
> 主旨: Re: [b2g] Porting guide for Firefox OS 
> 
> This is a fantastic initiative! I have been thinking about this recently, as 
> the MDN build instructions, phone information, B2G release notes and Gaia 
> contribution info are all getting there, but we still have woefully little on 
> the Gonk/other porting targets layer. 
> 
> I’d love to help write this up and publish it, and in turn get some more 
> input into what should be put on 
> https://developer.mozilla.org/en-US/Firefox_OS/Platform/Gonk, and other 
> related pages. 
> 
> best, 
> 
> Chris Mills 
> Senior tech writer || Mozilla 
> developer.mozilla.org || MDN 
> cmi...@mozilla.com || @chrisdavidmills 
> 
> 
> 
> On 12 Mar 2014, at 08:52, Thomas Zimmermann  wrote: 
> 
> > Hi Gina 
> > 
> > On 11.03.2014 07:27, Gina Yeh wrote: 
> >> Hi, 
> >> 
> >> We're preparing documents for analyzing porting efforts of Firefox OS, 
> >> and I'm writing this e-mail up to organize these thoughts and get input 
> >> from everyone on various parts. Any feedback is welcomed. 
> > 
> > Sounds great. 
> > 
> > 
> >> We think that it could be roughly separated into three types: 
> >> 
> >> *1. Devices with Gonk, consisting of a Linux kernel and userspace 
> >> hardware abstraction layer (HAL)* [1]. 
> >> 
> >> For these devices, all hardware-related backends should be ready and no 
> >> porting effort should be taken. 
> > 
> > On most systems, some of the system libraries are proprietary, and only 
> > available in binary form. One thing I noticed is that these libraries 
> > are sometimes not compatible with the open-source components because 
> > vendors add their own modifications to the binaries. Finding the correct 
> > revisions for open-source components that actually build and work at 
> > runtime with the binary blobs can be hard. 
> > 
> > 
> >> Here are the mapping of Gecko and Gonk components. 
> >> 
> >> Gecko | Gonk 
> >> - 
> >> Display | Gralloc HAL and HWC HAL 
> >> Audio | OpenSL ES + AudioFlinger 
> >> AudioSystem | HAL of Audio HW and Audio Policy 
> >> Manager 
> >> Wifi | dhcp client, dhcp server, tethering, 
> >> wpa_supplicant, hostapd, DNS server(property_set) 
> >> Bluetooth | bluez+dbus, bluedroid 
> >> Sensor | Sensor HAL 
> >> Mounter | vold 
> >> Power | Power HAL 
> >> Camera | Camera Service in MediaService Process 
> >> RTSP | (*It links share libraries in Gonk) 
> >> GPS | Geolocation HAL 
> >> Backlight/LED | light HAL 
> >> RIL | rild, netd, dhcpd 
> >> Platform Decoder Module | MediaCodec 
> &

Re: [b2g] Porting guide for Firefox OS

[Marco Chen]

Hi Thomas and Chris, 

Thanks for your useful input and great support on writing the MDN. 

Another info we can provide are 
1. To list AOSP properties which Gecko relied on. 
2. To show what modification made for repos outside the Gecko/Gaia are 
necessary. 
3. To show what pixel formats (YUV variation) Gecko can support. 

One example are listed at the link as below. 
https://wiki.mozilla.org/TPESystem/Media/DevicePortingIssues 
(Thanks for Bruce Sun's contribution.) 

Sincerely yours. 
- 原始郵件 -

寄件者: "Chris Mills"  
收件者: "Thomas Zimmermann" , "Gina Yeh" 
 
副本: dev-b2g@lists.mozilla.org 
寄件備份: 2014 3 月 12 星期三 下午 4:59:51 
主旨: Re: [b2g] Porting guide for Firefox OS 

This is a fantastic initiative! I have been thinking about this recently, as 
the MDN build instructions, phone information, B2G release notes and Gaia 
contribution info are all getting there, but we still have woefully little on 
the Gonk/other porting targets layer. 

I’d love to help write this up and publish it, and in turn get some more input 
into what should be put on 
https://developer.mozilla.org/en-US/Firefox_OS/Platform/Gonk, and other related 
pages. 

best, 

Chris Mills 
Senior tech writer || Mozilla 
developer.mozilla.org || MDN 
cmi...@mozilla.com || @chrisdavidmills 



On 12 Mar 2014, at 08:52, Thomas Zimmermann  wrote: 

> Hi Gina 
> 
> On 11.03.2014 07:27, Gina Yeh wrote: 
>> Hi, 
>> 
>> We're preparing documents for analyzing porting efforts of Firefox OS, 
>> and I'm writing this e-mail up to organize these thoughts and get input 
>> from everyone on various parts. Any feedback is welcomed. 
> 
> Sounds great. 
> 
> 
>> We think that it could be roughly separated into three types: 
>> 
>> *1. Devices with Gonk, consisting of a Linux kernel and userspace 
>> hardware abstraction layer (HAL)* [1]. 
>> 
>> For these devices, all hardware-related backends should be ready and no 
>> porting effort should be taken. 
> 
> On most systems, some of the system libraries are proprietary, and only 
> available in binary form. One thing I noticed is that these libraries 
> are sometimes not compatible with the open-source components because 
> vendors add their own modifications to the binaries. Finding the correct 
> revisions for open-source components that actually build and work at 
> runtime with the binary blobs can be hard. 
> 
> 
>> Here are the mapping of Gecko and Gonk components. 
>> 
>> Gecko | Gonk 
>> - 
>> Display | Gralloc HAL and HWC HAL 
>> Audio | OpenSL ES + AudioFlinger 
>> AudioSystem | HAL of Audio HW and Audio Policy 
>> Manager 
>> Wifi | dhcp client, dhcp server, tethering, 
>> wpa_supplicant, hostapd, DNS server(property_set) 
>> Bluetooth | bluez+dbus, bluedroid 
>> Sensor | Sensor HAL 
>> Mounter | vold 
>> Power | Power HAL 
>> Camera | Camera Service in MediaService Process 
>> RTSP | (*It links share libraries in Gonk) 
>> GPS | Geolocation HAL 
>> Backlight/LED | light HAL 
>> RIL | rild, netd, dhcpd 
>> Platform Decoder Module | MediaCodec 
>> External Media Framework | OpenMax (libstagefright) 
>> ResourceManager | WakeLock 
>> Low Memory Killer | Linux Kernel Configuration 
>> Memory Pressure notification | Linux Kernel Configuration 
> 
> The memory-pressure notification is a feature specifically for FFOS 
> IIRC. So you won't find it on generic Android devices. OTOH, it's not 
> absolutely necessary. 
> 
> 
>> Nuwa | pthread, libc 
>> 
>> *2. Devices with ARM/x86 architectures but no Gonk.* 
>> 
>> For these devices, porting efforts of all components listed in the above 
>> table should be taken into accounted. 
>> 
>> *3. Devices with CPU architectures which is neither ARM nor x86.* 
>> 
>> For these devices, porting above all components are necessary, and we 
>> need to put the following items on the radar: 
>> 
>> - Crash reporting (toolkit/crashreporter/google-breakpad) and stack 
>> walking (for assertion reporting/debugging, xpcom/base/nsStackWalk.cpp) [2] 
>> - JIT 
>> - All of the optimized assembly/architecture specific intrinsics spread 
>> throughout the tree including [2]: 
>> - Assembly for various media/graphics libraries (libjpeg, libvpx, etc) 
>> - Architecture specific SIMD intrinsics for various things (SSE2 
>> based graphics operations, SSE2 based charset conversions, cairo, skia, 
>> thebes, etc) 
>> - Hard-Floating/Soft-Floating 
> 
> Recently there was a discussion about page sizes in bug 979913. [1] That 
> might become relevant as well. 
> 
> 
>> 
>> (Thanks Kyle Huey for providing the above information. ) 
>> 
>> Besides, we went through m-c code base quickly and found some inline 
>> assembly [3], and we're not sure if the functionalities of the following 
>> components are still working without these inline assembly. (If they are 
>> used for acceleration, the functionality should be fine but with poor 
>> performance. Or, the component might be broken due to the lack of the 
>> inline assembly

Re: [b2g] Master hamachi build failure

[Marco Chen]

>> It's not a good way to patch gecko code
I agree with Shawn.
And for my experience, I had tried to propose the "patch" mechanism and 
reviewer strongly rejected it.
The reason is that "all patch should be reviewed well then commit into 
repository"
Then I kept this principle when I reviewed other devices manifest.

If this is a case we allowed then I can't say no for following requests from 
partner.
Do we allow it?

- 原始郵件 -
寄件者: "Shawn Huang" 
收件者: dev-b2g@lists.mozilla.org
寄件備份: 2014 3 月 8 星期六 上午 12:37:43
主旨: Re: [b2g] Master hamachi build failure

On Saturday, March 1, 2014 12:19:06 AM UTC+8, Shawn Huang wrote:
> On Friday, February 28, 2014 11:09:48 PM UTC+8, Sotaro Ikeda wrote:
> 
> I don't know why. Since hamachi is ICS based and still uses bluez as the 
> bluetooth stack. This patch is not necessary for hamachi, now only JB/KK uses 
> bluedroid as the bt stack. I think you can delete the patch locally. It looks 
> like caf has their own modification for bluetooth HAL header files, and since 
> we followed AOSP bluetooth HAL (at least I think we shall follow aosp HAL), 
> caf tries to patch our gecko code to match their HAL headers. Auto patch 
> failed because recently change file path in bug 972732.
> 
It's not a good way to patch gecko code, especially HAL headers changed and 
patches are under device/qcom/b2g_common/patch/all/gecko. How do we handle this 
kind of HAL changes? Can anyone please enlighten me? How do we choose to 
support AOSP HAL or CAF HAL?
___
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] Improve audio competing policy and user experience

[Marco Chen]

Hi all,

It seems that this thread didn't attract much attention so I tried put more 
issues which is waited to be fixed.

Bug 911238 - [AudioChannel] Consider to let normal channel play in the 
background.  
 Or listen music from 
third party web site will not be allowed to perform in the background.
Bug 871467 - [AudioChannel] To generate alert tone during in_call state when 
alarm/notification is fired.
 Or during phone call 
user doesn't have chance to notice any alart or notification coming.
Bug 918626 - [Fugu][Buri][Camera][Music]When taking pictures,music intermittent
 Or user can't hear 
shutter sound because music volume is too big.
Bug 946556 - Music app in foreground can play the music now but components 
underlying Gecko will block music stream during phone call.

The section of audio competing policy in [1] give the brief introduction of 
what we have now.
And actually we didn't have any UX spec to show our audio competing policy, we 
only collect each UX's reply in each bugs then implement it in each patches.
So every time someone argue about this, we need to find out the decision made 
by which bug then show to him/her.

[1] https://wiki.mozilla.org/WebAPI/AudioChannels 

Thanks,
Sincerely yours.
- 原始郵件 -
寄件者: "Dominic Kuo" 
收件者: dev-b2g@lists.mozilla.org, dev-g...@lists.mozilla.org, 
firefoxos-ux-t...@mozilla.com
副本: "Rob MacDonald" , "Christopher Lam" 
, "Jacqueline Savory" , "Casey (Kok 
Ching) Yee" , "Marco Chen" , "Andrea 
Marchesini" , "Alive Kuo" , "Hema 
Koka" 
寄件備份: 2013 12 月 20 星期五 上午 10:22:14
主旨: Improve audio competing policy and user experience

Hi folks, 

Recently Gaia has encountered some audio issues that the current audio channel 
API [1] did not 
consider of, such as pick an audio file then preview it in mms while music is 
playing in the 
background(bug 894744), or talking in a call and listen to the music at the 
same time via bluetooth 
headset(bug 946556). These scenarios are not so common but let us know there 
are spaces we can 
improve for our audio channel policy/API, so I am sending this email to start a 
thread. 

From the perspective of audio channel API, the behaviours in the above bugs are 
expected, but it 
confuses our users and probably also mess up the ux that we are trying to keep 
in the firefox os. I 
have discussed with Marco and Casey about how we can solve this gap, and we 
thought it might be 
a good idea to start a discussion between devs and ux team to make sure we are 
on the same page. 

As an author of the music app, I believe the original audio c ompeting policy 
was intended not to let 
the apps involve the competing too much, and the apps can focus on the features 
and don't have to 
write some extra logic. But due to new features are making new issues, we can 
probably provide 
more api or information for the apps to handle the competing. This depends on 
how our ui looks/feels 
like and what ux we want to give to our users, so it might be better that ux 
team can provide the policy 
or rules from ux perspective, especially for the existing bugs [2][3] to help 
the devs to design/implement 
the new API if needed. 

And since there are several audio competing bugs are first filed in 
Gaia::Music, this inspired me to 
do some investigations on the audio competing issues on the mainstream mobile 
OSes. I just picked 
two simple scenarios to test and the results are listed in the table below. 

Scenario 1 : The user answered a call and tried to bring the music app to the 
foreground then play music. 
Scenario 2 : The user is listening to the music, then go the settings to change 
the ringtone. 

OS 
Scenario 1  Scenario 2 
Android 
1. The music will pause during the call. 
2. The play controls in the music app will be disabled. 
3. If the user try to resume the music, a prompt will come out and let the user 
know it's disabled because of some reasons. 
4. After the call ends, the music will resume automatically. 

1. When previewing the ringtone, music still plays in the background. 
2. The previewing ringtone and music will be mixed together. 

iOS 
1. The music will pause during the call. 
2. We can still play the music during a call. 
3. Music will be mute.(playing without sound) 
4. After the call ends, the music will resume automatically. 

1. When previewing the ringtone, music will pause. 
2. When the user brings the music to the foreground, then music will resume 
automatically. 

Windows Phone   
1. The music will pause during the call. 
2. We can still play the music during a call. 
3. Music will be mute.(playing without sound) 
4. After the call ends, the music will resume automatically. 

Re: [b2g] FxOS how it detects the usb connection to PC?

[Marco Chen]

Hi Paul,

As I know that we didn't have Web API for this purpose now but just had some 
similar but not accurate ones.

Ex:
  1. USB Mass Storage. (Need to get result by enabling it)
  2. Battery Charging. (Not sure that charging is came from PC or Wall Charger)
(Once device's loaded current is bigger 
then charging current, it becomes not thing)

Also we are collecting the use case for proposing the new Web API for detecting 
such kind of things.
What we got are

  1. As a user, I want to choose the preferred USB functionality when USB is 
plugged in. (ex: Mass Storage / MTP / Charging Only)   
  2. As a user, I want to get a pop up message for notifying PC didn't provide 
USB tethering function.
  3. As a user, I want to know charger is connected or not no matter charging 
current can be enough for device's loaded current or not.

May I know your use case?

Thanks,
Sincerely yours.

- 原始郵件 -
寄件者: "Paul Tsvika" 
收件者: dev-b2g@lists.mozilla.org
寄件備份: 2013 12 月 10 星期二 下午 2:56:39
主旨: Re: [b2g] FxOS how it detects the usb connection to PC?

Hi Jan,

Your approach will only work when enabling USB storage.

My intention is to detect pc usb connection event without enabling USB storage.

Do you have any idea about this?
___
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 proximity sensor

[Marco Chen]

Hi,

Could you check whether "/data/misc/prox/prox_threshold.txt" is exist or not?
This is the file recorded calibration data and prox sensor can't work well 
without it.

Thanks,
Sincerely yours.

- 原始郵件 -
寄件者: "an" 
收件者: dev-b2g@lists.mozilla.org
寄件備份: 2013 12 月 8 星期日 下午 5:10:40
主旨: Re: [b2g] zte open proximity sensor

On Thursday, December 5, 2013 10:30:17 AM UTC+2, an wrote:
> Is it a known issue with zte open + v1.2 and proximity sensor? As soon as I 
> finish a call the screen is black instead of showing the UI where I can hang 
> up.

It turns out this is not a bug but the result of the splendid collaboration 
between Mozilla and zte for providing a "developer" device, the sensor works 
but only with the OS provided by zte. If you do your own build per Mozilla 
instructions for supported devices you loose the proximity sensor functionality.
J Wajsberg was wrong, I should thank Mozilla for this device not zte, it's 
worth every penny.
___
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] Per device Gecko configure options

[Marco Chen]

Hi,

The example I considered is just what you said - NFC.
Even NFC modules can be dynamically loaded into DRAM (giving the chance for 
saving DRAM), we still can't save the physical storage space (NAND or eMMC).
Any unnecessary modules/codes removed from binary can give End User more spaces 
for installing their applications without external SD Card. 

Sincerely yours.

- 原始郵件 -
寄件者: "Andreas Gal" 
收件者: "Marco Chen" 
副本: "Vicamo Yang" , mozilla-dev-...@lists.mozilla.org, "Dimi 
Lee" , "Garner Lee" , "Michael Wu" 

寄件備份: 2013 12 月 2 星期一 下午 3:36:33
主旨: Re: [b2g] Per device Gecko configure options


Lets discuss which modules you want to remove and how we want to do that. For 
example, we should not load the NFC module/worker if the device is not NFC 
capable. I am pretty sure we can do that at runtime in a way that doesn't have 
a memory overhead. What other modules are you considering? Avoiding loading 
unnecessary code is always great, so we should do this as a general 
optimization everywhere.

Andreas

On Dec 1, 2013, at 9:56 PM, Marco Chen  wrote:

> Hi,
> 
> For Tarako, we are considering to remove some modules for saving the space.
> So is this not a right direction based on Andreas's comment?
> 
> Thanks,
> Sincerely yours.
> - 原始郵件 -----
> 寄件者: "Andreas Gal" 
> 收件者: "Vicamo Yang" 
> 副本: mozilla-dev-...@lists.mozilla.org, "Marco Chen" , 
> "Dimi Lee" , "Garner Lee" , "Michael 
> Wu" 
> 寄件備份: 2013 12 月 2 星期一 下午 1:45:20
> 主旨: Re: [b2g] Per device Gecko configure options
> 
> 
> For security updates its critical to not develop a diverging zoo of Gecko 
> binaries. Originally we had one binary that was bit-for-bit identical on all 
> devices. We at some point reduced that constraint to binary-identical for all 
> devices with the same gonk version (ICS vs JB etc). Anything beyond that 
> should be detected by reading props the OEM can set. Please don't further 
> fork Gecko on a per-device basis. It would dramatically worsen our security 
> story.
> 
> Thanks,
> 
> Andreas
> 
> On Dec 1, 2013, at 9:15 PM, Vicamo Yang  wrote:
> 
>> Hi all,
>> 
>> Recently we have a few bugs regarding the variety of features of different 
>> devices/platforms.  See bug 920551 [1] and bug 939056  [2]. The problem is: 
>> shall we allow --disable-foo in per device configuration?
>> 
>> Right now we have a file named 'default-gecko-config' inside gonk-misc/.  
>> The file contains 23 default |ac_add_options ...| lines and several of them 
>> are further controlled by environment variables exported in '.config' and/or 
>> '.userconfig'.
>> 
>> Besides, there is also another way to inject such compile time options.  The 
>> 'Android.mk' file in same gonk-misk/ directory suggests one may assign 
>> "GECKO_CONFIGURE_ARGS" in any other "Android.mk" files, and the value will 
>> be passed as "CONFIGURE_ARGS" env variable to Gecko during the configure 
>> stage.  The best home for this variable is per device 'BoardConfig.mk' for 
>> sure.
>> 
>> So back to the original problem: shall we allow --disable-foo in per device 
>> configuration?  That is: shall we allow assigning "GECKO_CONFIGURE_ARGS" in 
>> per device 'BoardConfig.mk'?
>> 
>> I would say YES.  My 2 cents:
>> 
>> 1) Code size.
>> 
>> Back to bug 864485 [3], migrating Telephony IPC from frame messaging to 
>> IPDL, Telephony DOM code was then built on ALL platforms just like what we 
>> have for MobileMessage.  By ALL, I mean it's compiled even on Windows.  Then 
>> I got a regression mail saying the built binary size grew 1% after that 
>> patch on platforms didn't have WebTelephony before. Taking current 
>> /system/lib/libxul.so for example, 1% means 230KB.  I heard there is some 
>> kind of delayed loading tech in use, but this still comes to my mind first 
>> when we were to built-in some dead code in final executables.
>> 
>> 2) Runtime detection may lead to a certain problem.
>> 
>> The two bugs, 920551 and 939056, are for enabling/disabling a certain B2G 
>> feature(s) on different devices.  These features come with DOM APIs for 
>> sure.  For now we're to hide APIs from user content when it's not available. 
>>  Runtime detection is suggested but it takes time.  It follows the first 
>> call to retrieve the availability of such feature should only be made after 
>> we're fully confident/determined there is no such feature on that device.  
>

Re: [b2g] Per device Gecko configure options

[Marco Chen]

Hi,

For Tarako, we are considering to remove some modules for saving the space.
So is this not a right direction based on Andreas's comment?

Thanks,
Sincerely yours.
- 原始郵件 -
寄件者: "Andreas Gal" 
收件者: "Vicamo Yang" 
副本: mozilla-dev-...@lists.mozilla.org, "Marco Chen" , "Dimi 
Lee" , "Garner Lee" , "Michael Wu" 

寄件備份: 2013 12 月 2 星期一 下午 1:45:20
主旨: Re: [b2g] Per device Gecko configure options


For security updates its critical to not develop a diverging zoo of Gecko 
binaries. Originally we had one binary that was bit-for-bit identical on all 
devices. We at some point reduced that constraint to binary-identical for all 
devices with the same gonk version (ICS vs JB etc). Anything beyond that should 
be detected by reading props the OEM can set. Please don't further fork Gecko 
on a per-device basis. It would dramatically worsen our security story.

Thanks,

Andreas

On Dec 1, 2013, at 9:15 PM, Vicamo Yang  wrote:

> Hi all,
> 
> Recently we have a few bugs regarding the variety of features of different 
> devices/platforms.  See bug 920551 [1] and bug 939056  [2]. The problem is: 
> shall we allow --disable-foo in per device configuration?
> 
> Right now we have a file named 'default-gecko-config' inside gonk-misc/.  The 
> file contains 23 default |ac_add_options ...| lines and several of them are 
> further controlled by environment variables exported in '.config' and/or 
> '.userconfig'.
> 
> Besides, there is also another way to inject such compile time options.  The 
> 'Android.mk' file in same gonk-misk/ directory suggests one may assign 
> "GECKO_CONFIGURE_ARGS" in any other "Android.mk" files, and the value will be 
> passed as "CONFIGURE_ARGS" env variable to Gecko during the configure stage.  
> The best home for this variable is per device 'BoardConfig.mk' for sure.
> 
> So back to the original problem: shall we allow --disable-foo in per device 
> configuration?  That is: shall we allow assigning "GECKO_CONFIGURE_ARGS" in 
> per device 'BoardConfig.mk'?
> 
> I would say YES.  My 2 cents:
> 
> 1) Code size.
> 
> Back to bug 864485 [3], migrating Telephony IPC from frame messaging to IPDL, 
> Telephony DOM code was then built on ALL platforms just like what we have for 
> MobileMessage.  By ALL, I mean it's compiled even on Windows.  Then I got a 
> regression mail saying the built binary size grew 1% after that patch on 
> platforms didn't have WebTelephony before. Taking current 
> /system/lib/libxul.so for example, 1% means 230KB.  I heard there is some 
> kind of delayed loading tech in use, but this still comes to my mind first 
> when we were to built-in some dead code in final executables.
> 
> 2) Runtime detection may lead to a certain problem.
> 
> The two bugs, 920551 and 939056, are for enabling/disabling a certain B2G 
> feature(s) on different devices.  These features come with DOM APIs for sure. 
>  For now we're to hide APIs from user content when it's not available.  
> Runtime detection is suggested but it takes time.  It follows the first call 
> to retrieve the availability of such feature should only be made after we're 
> fully confident/determined there is no such feature on that device.  For 
> example, FTU need to know whether does the device implement RIL APIs or not 
> before it's to display a menu item for "Import SIM contacts".  Such calls 
> have to be delayed after runtime detection is done, and again these 
> detections take some time.  Why not just skip these detections on devices 
> that have no such feature at all?
> 
> 3) How and why
> 
> Till now, all devices have their own Gecko binaries.  They're built directly 
> from the source code and each of them is basically different from each other. 
>  No any devices share Gecko binaries at the time at all.  Some devices have 
> even additional patches to Gecko applied, and some replaces built-in 
> components with their own.  Mozilla just can't stop device makers from 
> compiling Gecko by their own.  And we just shouldn't do so, either.  The 
> thing we should only care is to provide unified Web API interfaces to users, 
> not binary monopoly to device makers.
> 
> So, what would you say?
> 
> [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=920551
> [2]: https://bugzilla.mozilla.org/show_bug.cgi?id=939056
> [3]: https://bugzilla.mozilla.org/show_bug.cgi?id=864485
> ___
> 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] [WebAPI] The Naming of PowerManager.screenEnabled Misleads the Gaia Developers

[Marco Chen]

Hi Kan-Ru,

>> 1. Changing PowerManager.screenEnabled is THE ONLY WAY to trigger the 
>> suspend.
> This is not true. The android kernel could call suspend at anytime when
> the wake lock count in kernel hits zero.  When design power management
> API we must remember that the user space has to cooperate with the
> kernel.  Wake up events could come from device drivers or user space.

Basically it is true of system will go into real suspend state when wake lock 
count is 0.
But please refer to the link as below

http://code.google.com/p/bricked/source/browse/kernel/power/earlysuspend.c?repo=tenderloin&name=2a47e396d5&r=2a47e396d569c069bf7023202e336ec19bbf615c#168

When Gecko set "/sys/power/state" to "on", there is a wakelock created by 
kernel - main_wake_lock.
So there is no chance of wakelock count is 0 until 

  PowerManager.screenEnabled = false -> Gecko set "/sys/power/state" to "mem" 
-> check wakelock is 0 or not.

If the statement as below is still true then we don't need 
PowerManager.cpuSleepAllowed and just handled by system app itself.

  "1. Changing PowerManager.screenEnabled is THE ONLY WAY to trigger the 
suspend."

> Please define powerLevel. Currently the Resource Lock API

Honestly to say, I have no strong reason to change this.
But just focus on rename the PowerManager.screenEnabled and split it to two 
functions - Suspend & Screen.

> 1. System app can collect the minimal power level requests from each apps 
> then decide what is the minimal power level now.
> 2. Then calling setPowerLevel() when any condition is triggered. (ex: power 
> key handling, idle time out or proximity event during phone call).
> 3. App can really request screen to off by calling screenEnabled attribute.
>>
>>The third step does not depend on the first and second change.  

Yes, the third step didn't depends on first and second.
What I want to mention is "suspend and screen off can be split into two 
different things"

Thanks,
Sincerely yours.
- 原始郵件 -
寄件者: "Kan-Ru Chen (陳侃如)" 
收件者: "Marco Chen" 
副本: dev-b2g@lists.mozilla.org, dev-web...@lists.mozilla.org
寄件備份: 2013 11 月 27 星期三 下午 7:29:23
主旨: Re: [b2g] [WebAPI] The Naming of PowerManager.screenEnabled Misleads the 
Gaia Developers

[ +dev-webapi You could find the original thread here:
https://groups.google.com/forum/#!msg/mozilla.dev.b2g/UP5h_a3QAHE/i3S3aCwNPTUJ ]

Marco Chen  writes:

> Hi Kan-Ru,
>
> Thanks for your reply first.
>
>> Changing PowerManager.screenEnabled is just one way to trigger the suspend.
>
> As I knew,
> 1. Changing PowerManager.screenEnabled is THE ONLY WAY to trigger the suspend.

This is not true. The android kernel could call suspend at anytime when
the wake lock count in kernel hits zero.  When design power management
API we must remember that the user space has to cooperate with the
kernel.  Wake up events could come from device drivers or user space.

>> and remove the cpuSleepAllowed attribute from PowerManager
>
> 1. Currently PowerManager.cpuSleepAllowed is set by System app and depends on 
> any apps tried to call  navigator.requestWakeLock or not.
> 2. Then gonk implementation will help to acquire a wakelock from linux kernel 
> corresponding to value of cpuSleepAllowed.
> 3. Then this mechanism can prevent system go into suspend from setting  
> PowerManager.screenEnabled to false.

Yes. This describes how the system works currently. But note that the
PowerManager is a certified only API.

> I agree that PowerManager.cpuSleepAllowed can be removed and system app can 
> take care this state by itself.
>
> partial interface navigator {
> boolean requestMinPowerLevel(DOMString powerLevel)
>   };

Please define powerLevel. Currently the Resource Lock API[1] (aka
WakeLock) allow apps to request the resource they need to accomplish a
task and the power required for the resource may vary on different
platforms.  For example the e-ink screen consumes no power when the cpu
is off.

> partial interface PowerManager {
> // Ask the system to suspend. Return true on success, false otherwise.
> boolean setPowerLevel(DOMString powerLevel);
>
> voidaddPowerLevelListener(MozPowerLevelListener aListener);
> voidremovePowerLevelListener(MozPowerLevelListener aListener);
>
> // Is the device's screen currently enabled?
> attribute boolean screenEnabled;
>
> // removed
> //voidaddWakeLockListener(MozWakeLockListener aListener);
> //voidremoveWakeLockListener(MozWakeLockListener aListener);
>
> // removed
> // attribute boolean cpuSleepAllowed
>   };
>
> 1. System app can collect the minimal power level requests from each apps 
> then decide what is the minimal power level now.
&g

Re: [b2g] [WebAPI] The Naming of PowerManager.screenEnabled Misleads the Gaia Developers

[Marco Chen]

Hi Kan-Ru,

Thanks for your reply first.

> Changing PowerManager.screenEnabled is just one way to trigger the suspend.

As I knew,
1. Changing PowerManager.screenEnabled is THE ONLY WAY to trigger the suspend.

> and remove the cpuSleepAllowed attribute from PowerManager

1. Currently PowerManager.cpuSleepAllowed is set by System app and depends on 
any apps tried to call  navigator.requestWakeLock or not.
2. Then gonk implementation will help to acquire a wakelock from linux kernel 
corresponding to value of cpuSleepAllowed.
3. Then this mechanism can prevent system go into suspend from setting  
PowerManager.screenEnabled to false.

I agree that PowerManager.cpuSleepAllowed can be removed and system app can 
take care this state by itself.

partial interface navigator {
boolean requestMinPowerLevel(DOMString powerLevel)
  };

partial interface PowerManager {
// Ask the system to suspend. Return true on success, false otherwise.
boolean setPowerLevel(DOMString powerLevel);

voidaddPowerLevelListener(MozPowerLevelListener aListener);
voidremovePowerLevelListener(MozPowerLevelListener aListener);

// Is the device's screen currently enabled?
attribute boolean screenEnabled;

// removed
//voidaddWakeLockListener(MozWakeLockListener aListener);
//voidremoveWakeLockListener(MozWakeLockListener aListener);

// removed
// attribute boolean cpuSleepAllowed
  };

1. System app can collect the minimal power level requests from each apps then 
decide what is the minimal power level now.
2. Then calling setPowerLevel() when any condition is triggered. (ex: power key 
handling, idle time out or proximity event during phone call).
3. App can really request screen to off by calling screenEnabled attribute.

Sincerely yours.

- 原始郵件 -
寄件者: "Kan-Ru Chen (陳侃如)" 
收件者: "Marco Chen" 
副本: "Thomas Zimmermann" , "Mozilla mailing list" 

寄件備份: 2013 11 月 26 星期二 下午 4:11:03
主旨: Re: [b2g] [WebAPI] The Naming of PowerManager.screenEnabled Misleads the 
Gaia Developers

Marco Chen  writes:

> Hi Thomas,
>
>>> There is already PowerManager.cpuSleepAllowed for keeping the CPU running.
> Yes, you are right. But does PowerManager.screenEnabled API told developers
> that "you should request a wakelock first or system will go into sleep not
> just turn off the screen"?  It didn't make sense for this naming.  As a
> developer or as a Web API, "screenEnabled" should be acted like what it
> shows. (for screen only and not related to others) (Currently developers
> should lock a wakelock by navigator.requestWakeLock instead of touching
> PowerManager.cpuSleepAllowed directly.)

Developers also don't use PowerManager.screenEnabled directly but I get your
point.  The original API design is tightly coupled to the underlying power
management method, but we should design the API for the API users not the
ease of implementors.

>>> If we want to change the API, I'd suggest to expose different levels of
>>> power saving, as described in [1].
> Based on the types of wakelocks in [1]. I would suggest
>
>   1. Rename the PowerManager.screenEnabled to the one which focuses on asking
>  system go into power saving mode.
>   2. Consider to extend the types of wakelock for apps to choose the minimal
>  power levels they required. (Maybe rename navigator.requestWakeLock to
>  navigator.requestMinPowerLevel too.)

The current design is based on the opportunistic suspend method. When
PowerManager.cpuSleepAllowed is true, the device could suspend at anytime.
Changing PowerManager.screenEnabled is just one way to trigger the suspend.

If we want the system app has more control over when to suspend, how about
adding a suspend method and remove the cpuSleepAllowed attribute from 
PowerManager?

  partial interface PowerManager {
// Ask the system to suspend. Return true on success, false otherwise.
boolean suspend();

// Is the device's screen currently enabled?
attribute boolean screenEnabled;

// removed
// attribute boolean cpuSleepAllowed
  };

The gaia power manager could then try to suspend after the cpu wake lock count
hits zero (maybe wait a few seconds).

Kanru
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

Re: [b2g] Touch not working

[Marco Chen]

Hi,

Maybe you hit the compatibility issue on touch event between kernel driver and 
Gecko.
You can try to merge the removed codes from link as below.
https://bugzilla.mozilla.org/page.cgi?id=splinter.html&bug=852400&attachment=737078

Sincerely yours.

- 原始郵件 -
寄件者: "Manjunatha M" 
收件者: dev-b2g@lists.mozilla.org
寄件備份: 2013 11 月 15 星期五 下午 12:51:04
主旨: [b2g] Touch not working

Hi,

I have a device working with FFOS 1.1 and Android ICS 4.0.4. Now that I
moved to FFOS 1.2 with the same Android ICS 4.0.4. The device is booting,
but has touch issues. Most of the times touch doesn't work and few times,
touch anywhere on the screen, the input goes to the single point on the
screen (Example/- After the first time boot, touch anywhere on the screen,
the input goes to the next button)

I need inputs to fix this issue.

Thanks

-- 
Regards,
Manjunatha
___
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] [WebAPI] The Naming of PowerManager.screenEnabled Misleads the Gaia Developers

[Marco Chen]

Hi Thomas,

>> There is already PowerManager.cpuSleepAllowed for keeping the CPU running.
Yes, you are right. But does PowerManager.screenEnabled API told developers 
that "you should request a wakelock first or system will go into sleep not just 
turn off the screen"?
It didn't make sense for this naming.
As a developer or as a Web API, "screenEnabled" should be acted like what it 
shows. (for screen only and not related to others)
(Currently developers should lock a wakelock by navigator.requestWakeLock 
instead of touching  PowerManager.cpuSleepAllowed directly.)

>> If we want to change the API, I'd suggest to expose different levels of
>> power saving, as described in [1].
Based on the types of wakelocks in [1]. I would suggest

  1. Rename the PowerManager.screenEnabled to the one which focuses on asking 
system go into power saving mode.
  2. Consider to extend the types of wakelock for apps to choose the minimal 
power levels they required.
  (Maybe rename navigator.requestWakeLock to navigator.requestMinPowerLevel 
too.)

How about this?
Sincerely yours.

- 原始郵件 -
寄件者: "Thomas Zimmermann" 
收件者: "Marco Chen" 
副本: "Mozilla mailing list" 
寄件備份: 2013 11 月 12 星期二 下午 8:11:13
主旨: Re: [b2g] [WebAPI] The Naming of PowerManager.screenEnabled Misleads the 
Gaia Developers

Hi Marco

On 12.11.2013 12:49, Marco Chen wrote:
> Hi all,
> 
> [1] shows the properties of power manager (WebAPI) and 
> PowerManager.screenEnabled didn't have a suitable name and explanation.
> 
> This property didn't only control enable/disable of the device screen but 
> also the device's power state ("on" or "mem").
> When gaia developer called this API for turning off the screen but he didn't 
> know the system is going to suspend mode too.
> This will cause entire system go into frozen state so the following work that 
> developer expected will not be performed until device is woken up by any 
> wakup source.
> 
> So I suggest to rename this property and split it to two for power state and 
> screen state if necessary.
> ex: PowerManager.requestToSleep (just an example and welcome to new word)

There is already PowerManager.cpuSleepAllowed for keeping the CPU
running. And screen and CPU states are not independent from each other,
so having two completely separate interfaces might be hard to implement.

If we want to change the API, I'd suggest to expose different levels of
power saving, as described in [1].

Best regards
Thomas

[1] http://developer.android.com/reference/android/os/PowerManager.html

> May I know your suggestion?
> 
> [1] https://developer.mozilla.org/en-US/docs/Web/API/PowerManager
> 
> Sincerely yours.
> 
> -
> Marco Chen
> Engineering Manager
> System Team, Device Engineering
> Mozilla Taiwan
> 
> Tel: +886-2-87861100 # 352
> mail: mc...@mozilla.com
> 
> ___
> 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] [WebAPI] The Naming of PowerManager.screenEnabled Misleads the Gaia Developers

[Marco Chen]

Hi Ehsan,

Actually GonkDisplayJB.cpp did the same thing as GonkDisplayICS.cpp and 
additionally request screen to off.
http://dxr.mozilla.org/mozilla-central/source/widget/gonk/libdisplay/GonkDisplayJB.cpp#169
The link as above is the way GonkDisplayJB asked system to suspend.

So both of JB and ICS will ask system to suspend when 
PowerManager.screenEnabled is set to false and no wakelocks there.

Sincerely yours.

- 原始郵件 -
寄件者: "Ehsan Akhgari" 
收件者: "Marco Chen" , "Mozilla mailing list" 

寄件備份: 2013 11 月 12 星期二 下午 11:49:06
主旨: Re: [b2g] [WebAPI] The Naming of PowerManager.screenEnabled Misleads the 
Gaia Developers

Is this on ICS or JB?  Reading this code, I think the JB code path ends 
up here 
<http://dxr.mozilla.org/mozilla-central/source/widget/gonk/libdisplay/GonkDisplayJB.cpp#153>
 
which seems like it's turning the screen on and off.  However, the ICS 
version of this function 
<http://dxr.mozilla.org/mozilla-central/source/widget/gonk/libdisplay/GonkDisplayICS.cpp#137>
 
calls set_screen_state.  Assuming that this code is the implementation 
of that function 
<https://android.googlesource.com/platform/hardware/libhardware_legacy/+/ics-mr0/power/power.c>
 
then it's writing "mem" to /sys/power/state if you pass false to it, 
which suspends the device.  That seems like a bug to me.

Cheers,
Ehsan

On 2013-11-12 6:49 AM, Marco Chen wrote:
> Hi all,
>
> [1] shows the properties of power manager (WebAPI) and 
> PowerManager.screenEnabled didn't have a suitable name and explanation.
>
> This property didn't only control enable/disable of the device screen but 
> also the device's power state ("on" or "mem").
> When gaia developer called this API for turning off the screen but he didn't 
> know the system is going to suspend mode too.
> This will cause entire system go into frozen state so the following work that 
> developer expected will not be performed until device is woken up by any 
> wakup source.
>
> So I suggest to rename this property and split it to two for power state and 
> screen state if necessary.
> ex: PowerManager.requestToSleep (just an example and welcome to new word)
>
> May I know your suggestion?
>
> [1] https://developer.mozilla.org/en-US/docs/Web/API/PowerManager
>
> Sincerely yours.
>
> -
> Marco Chen
> Engineering Manager
> System Team, Device Engineering
> Mozilla Taiwan
>
> Tel: +886-2-87861100 # 352
> mail: mc...@mozilla.com
>
> ___
> dev-b2g mailing list
> dev-b2g@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-b2g
>

___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

[b2g] [WebAPI] The Naming of PowerManager.screenEnabled Misleads the Gaia Developers

[Marco Chen]

Hi all,

[1] shows the properties of power manager (WebAPI) and 
PowerManager.screenEnabled didn't have a suitable name and explanation.

This property didn't only control enable/disable of the device screen but also 
the device's power state ("on" or "mem").
When gaia developer called this API for turning off the screen but he didn't 
know the system is going to suspend mode too.
This will cause entire system go into frozen state so the following work that 
developer expected will not be performed until device is woken up by any wakup 
source.

So I suggest to rename this property and split it to two for power state and 
screen state if necessary.
ex: PowerManager.requestToSleep (just an example and welcome to new word)

May I know your suggestion?

[1] https://developer.mozilla.org/en-US/docs/Web/API/PowerManager

Sincerely yours.

-----
Marco Chen
Engineering Manager
System Team, Device Engineering
Mozilla Taiwan

Tel: +886-2-87861100 # 352
mail: mc...@mozilla.com

___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

Re: [b2g] About leo as a dev phone

[Marco Chen]

Hi Caio,

If you want develop gaia with master branch then you need to use Gecko with 
master branch too.
But currently the touch driver of leo had some compatible issue with Gecko 
master branch.

So if you want to use master on Leo please refer to the link as below for 
patching workaround back or touch will be not workable.
https://bugzilla.mozilla.org/page.cgi?id=splinter.html&bug=852400&attachment=737078

Sincerely yours.
- 原始郵件 -
寄件者: "Caio Lima" 
收件者: dev-b2g@lists.mozilla.org
寄件備份: 2013 10 月 29 星期二 下午 12:57:01
主旨: [b2g] About leo as a dev phone

Hey guys,

I'm from Brazil and here we have the LG Fireweb(leo) as a choice to use the
Firefox OS.
I would like to have a device to develop for gaia and for B2G. Thus, I want
to know if it's possible(I mean, in a easy way) flash "mozilla-central/gaia
master" on this device. Do you recommend me?

Best regards,
-- 
Caio Lima
___
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] The funciton of AssertMainThread()

[Marco Chen]

Hi,

The "b2g process" mentioned by Mike including chrome (or parent) process and 
content (or app) process.
Both parent or content processes have their own main thread.

Sincerely yours.

- Original Message -
From: mozloverin...@gmail.com
To: dev-b2g@lists.mozilla.org
Sent: Wednesday, October 23, 2013 1:45:50 PM
Subject: Re: [b2g] The funciton of AssertMainThread()

Hi Mike,

By reading again your post,

Each b2g process (parent or app) has a Main Thread[1].
--

I thought the system only has a b2g process [chrome process]. And this b2g 
process has a main thread. Is my understanding incorrect?
___
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] DeviceLightEvent.webidl from xpcom to sensor app

[Marco Chen]

Hi,

Please refer to the link as below which location tried to initialize a dom 
event for light.
http://mxr.mozilla.org/mozilla-central/source/dom/system/nsDeviceSensors.cpp#239

Then refer to "objdir-gonk/dom/bindings/DeviceLightEvent.cpp" to know what it's 
constructor function did.

Sincerely yours.

- Original Message -
From: mozloverin...@gmail.com
To: dev-b2g@lists.mozilla.org
Sent: Wednesday, October 23, 2013 5:40:21 AM
Subject: Re: [b2g] DeviceLightEvent.webidl from xpcom to sensor app

mozlov...@gmail.com於 2013年10月23日星期三UTC+8上午4時42分29秒寫道：
> In the sensor system (such as light sensor for example), there is a webidl 
> file called DeviceLightEvent.webidl in gecko/dom/webidl/.
> 
> 
> 
> From what I have known, the nsDeviceSensor (which is a xpcom component) will 
> send the light value to this dom event and then to sensor app.
> 
> 
> 
> Here are my questions:
> 
> 
> 
> 1. how does DeviceLightEvent.webidl receive light value from nsDeviceSensor?
> 
>I know gecko tool generates DeviceLightEventBinding.cpp automatically from
> 
>webidl. Does this play a role for receiving sensor data come from 
> nsDeviceSensor?
> 
>
> 
> 
> 
> 2. how does DeviceLightEvent.webidl play a role as a dom event to send the 
> sensor data to sensor app? how does this talk to sensor app?
> 
> 
> 
> 
> 
> Thanks for any reply.

I have been searching around the answer for the questions as I posted above. 
However, there is no clear reply yet.

Any feedback will be very welcome. Thanks.
___
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] Sensor data flow for light sensor

[Marco Chen]

Hi,

>> 2. In page 5, I still dont understand who played the role of 
>> "nsDOMDevicexxxEvent" in light sensor case.
If you want to discuss the case before change by WebIDL then you can refer to 
the link as below from b2g18 branch.
http://mxr.mozilla.org/mozilla-b2g18/source/js/xpconnect/src/event_impl_gen.conf.in#23

>> 1. In page 5 of the pdf you refer to, nsDOMDevicexxxEvent should be changed 
>> to nsIDOMDevicexxxEvent.
nsDOMDevicexxxEvent is a class inherited from nsIDOMDevicexxxEvent.

Sincerely yours.

- 原始郵件 -
寄件者: mozloverin...@gmail.com
收件者: dev-b2g@lists.mozilla.org
寄件備份: 2013 10 月 12 星期六 上午 7:23:05
主旨: Re: [b2g] Sensor data flow for light sensor

Hi,

(Let us discuss "before webidl" topic for now.)
When I searched "nsIDOMDevicexxxEvent" in the source. I only found 3 events 
which are nsIDOMDeviceMotionEvent.idl, nsIDOMDeviceOrientationEvent.idl and 
nsIDOMDeviceStorage.idl. I assume these are not related to the light sensor 
event which will not play a role for receiving the data from nsDeviceSensors 
and send it to the app layer (please correct me if i am wrong here). In this 
file (event_impl_gen.conf.in), I also did not find any clue about the light 
sensor. 

so here is a notice and a quesion

1. In page 5 of the pdf you refer to, nsDOMDevicexxxEvent should be changed to 
nsIDOMDevicexxxEvent.

2. In page 5, I still dont understand who played the role of 
"nsDOMDevicexxxEvent" in light sensor case.
___
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] Sensor data flow for light sensor

[Marco Chen]

Hi,

You can refer to Bug 915813 which transferred some sensor events to 
GENERATED_EVENTS_WEBIDL_FILES.
Before webidl, we declared nsIDOMDeviceXXXEvent then generated simple event by 
event_impl_gen.conf.in.
After webidl, we can remove nsIDOMDeviceXXXEvent and use the way of 
GENERATED_EVENTS_WEBIDL_FILES.

Sincerely yours.

- 原始郵件 -
寄件者: mozloverin...@gmail.com
收件者: dev-b2g@lists.mozilla.org
寄件備份: 2013 10 月 9 星期三 上午 11:31:26
主旨: Re: [b2g] Sensor data flow for light sensor

Marco Chen於 2013年10月9日星期三UTC+8上午10時21分55秒寫道：
> Hi,
> 
> 
> 
> You can refer to the document here.
> 
> https://docs.google.com/file/d/0BxKpB0y8NZSHSkRxRHdpRkp5bTg/edit?usp=sharing
> 
> 
> 
> Thanks,
> 
> Sincerely yours.
> 
> 
> 
> - 原始郵件 -
> 
> 寄件者: mozloverin...@gmail.com
> 
> 收件者: dev-b2g@lists.mozilla.org
> 
> 寄件備份: 2013 10 月 9 星期三 上午 6:14:04
> 
> 主旨: [b2g] Sensor data flow for light sensor
> 
> 
> 
> Is there any dom for Sensor apps (Devicelight sensor for example) to receive 
> the data?
> 
> 
> 
> nsDOMDeviceMotionEvent works for some sensors but for device light sensor.
> 
> 
> 
> I am curious to know the data flow about how  light value to be received from 
> 
> 
> 
> nsDeviceSensors.cpp
> 
> 
> 
> 
> 
> Thanks for any clue.
> 
> ___
> 
> dev-b2g mailing list
> 
> dev-b2g@lists.mozilla.org
> 
> https://lists.mozilla.org/listinfo/dev-b2g

Thanks Marco. I actually went through the document before.

I did not find any DOM behind the app layer and above nsDeviceSensors.cpp.

I tried to find the nsDOMDevicexxxEvent but only nsDOMDeviceMotionEvent.

This DOM should only work for motion related sensors.

Do you have any idea about this?  Thanks.
___
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] Audio architecture in B2g gecko 1.2

[Marco Chen]

Hi,

You can refer to the link as below.
https://docs.google.com/file/d/0BxKpB0y8NZSHY1NFcEZ2V19SdVE/edit?usp=sharing

And that document is out of date about libsydney and it should be libcubeb now.

Sincerely yours.

- 原始郵件 -
寄件者: hsaxen...@gmail.com
收件者: dev-b2g@lists.mozilla.org
寄件備份: 2013 10 月 7 星期一 下午 12:48:02
主旨: Re: [b2g] Audio architecture in B2g gecko 1.2

On Monday, 30 September 2013 19:26:00 UTC+5:30, hsax...@gmail.com  wrote:
> Please provide me the audio  architecture of B2g gecko 1.2 ..which i need to 
> port gecko 1.2

Dear Matt.

thanx For quick response . Actually i want to understand the code flow for Mp3 
playback In B2g 1.2 ,As we know in B2g libsydneyaudio was getting used ,which 
used to interact with Android framework(i.e AudioFlinger ..),but in B2g 1.2 
Libsydneyaudio is been replaced with liubcucbeb , so i want to understand the 
code flow and architecture ,which been changed wrt to libcubeb and exactly how 
libcubeb  interacts with Android Audio Framework ?? any flow diagram or Audio 
Architecture Diagram if i cud get w.r.t B2g1.2 then it will be very helpful.
Thanx in Advance
___
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] Sensor data flow for light sensor

[Marco Chen]

Hi,

You can refer to the document here.
https://docs.google.com/file/d/0BxKpB0y8NZSHSkRxRHdpRkp5bTg/edit?usp=sharing

Thanks,
Sincerely yours.

- 原始郵件 -
寄件者: mozloverin...@gmail.com
收件者: dev-b2g@lists.mozilla.org
寄件備份: 2013 10 月 9 星期三 上午 6:14:04
主旨: [b2g] Sensor data flow for light sensor

Is there any dom for Sensor apps (Devicelight sensor for example) to receive 
the data?

nsDOMDeviceMotionEvent works for some sensors but for device light sensor.

I am curious to know the data flow about how  light value to be received from 

nsDeviceSensors.cpp


Thanks for any clue.
___
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] Problem with sd-card API in Geeksphone Peak with Firefox OS 1.1

[Marco Chen]

Hi,

In V1.1, there are some changes on the DeviceStorage API and that is in order 
to support internal/external storage.
V1.1 introduced a new "navigator.getDeviceStorages(...)" which will return an 
array of device storages.
And old one "navigator.getDeviceStorage()" will return a preferred storage or 
the first storage in volume list.

I think your problem is related to this change.

Sincerely yours.


- Original Message -
From: "Igor Leturia" 
To: dev-b2g@lists.mozilla.org
Sent: Saturday, September 14, 2013 2:23:51 AM
Subject: [b2g] Problem with sd-card API in Geeksphone Peak with Firefox OS  
1.1

Hello,

I recently flashed my Geeksphone Peak with a Firefox OS 1.1 downloaded from 
they website, and an app I made that was working all right with Firefox OS 1.0 
(it is in the marketplace, https://marketplace.firefox.com/app/hiking-guide) 
stopped working.

The problem is that the sd-card API does not find any files in the card... And 
other apps seem to be having the same problem: for example, EPUBReader 
(https://marketplace.firefox.com/app/epubreader) seems to be having the same 
problem (it does not find any files in the SD card, although there are some 
epubs there.

However, preinstalled apps (like Gallery, Videos...) find those files in the SD 
card all right. So could there be a problem with privileged apps that try to 
have access to the SD card? Maybe some change in the API? Or is there any known 
general issue regarding this? Or is it an issue of the Peak only?

Any help will be appreciated. Thansk in advance,

  Igor Leturia
___
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] Moving Power Key Handling from Gaia to Gecko According to Bug 898707

[Marco Chen]

Hi,

In order to minimize the power consumption it is a correct way to hold wakelock 
by each components of Gecko & Gaia.
My only concern is that if we do power key handling in gecko then there is no 
necessary to handle this kind of problem.
Or is there a key reason of we need to keep this handling in Gaia ?

Sincerely yours.

- 原始郵件 -
寄件者: "Andreas Gal" 
收件者: "Marco Chen" 
副本: "Tim Chien" , "Julien Wajsberg" 
, "Alive Kuo" , "Mozilla mailing 
list" 
寄件備份: 2013 9 月 6 星期五 下午 2:17:39
主旨: Re: [b2g] Moving Power Key Handling from Gaia to Gecko According to Bug 
898707


When the event fires, and if an event handler is installed, can we take 
a wake lock for each installed event handler and release it only after 
the event has executed? The rest is then handled in Gaia.

Andreas

Marco Chen wrote:
> Hi Tim,
>
>>> The power key didn't always mean "go into suspend", we still need to handle 
>>> "sleep menu" by long pressing power key.
>>> So we can't use the approach you proposed.
>
> I gave the first reason of why don't I prefer "get temporary wakelock then 
> find a suitable point to release " in previous mail already.
> And the second reason is Gecko can't guarantee how Gaia will process power 
> key event, so there is no suitable way to hook the ending point of wakelock.
>
> Generally to say, each component should take care their usage of wakelock by 
> themselves so we can reduce the life cycle of each wakelock.
> But this is hard to do when power key is flowing between Gaia and Gecko.
>
> By the other way, there is two purpose of power keys only. One is for 
> suspend/resume and the other is for sleep_menu.js.
> For first one, I think it is no necessary to be handled by Gaia or is there 
> any benefit of handling by gaia?
> For second one, gecko can decide to send sleep_menu event to gaia or not.
>
> Thanks,
> Sincerely yours.
>
> - 原始郵件 -
> 寄件者: "Tim Chien"
> 收件者: "Marco Chen"
> 副本: "Alive Kuo", "Julien Wajsberg", 
> "Mozilla mailing list"
> 寄件備份: 2013 9 月 6 星期五 下午 12:11:54
> 主旨: Re: [b2g] Moving Power Key Handling from Gaia to Gecko According to Bug 
> 898707
>
> On Fri, Sep 6, 2013 at 11:52 AM, Marco Chen  wrote:
>> Hi all,
>>
>>> Before system message is dispatched, it would acquire a 30s cpu wake lock. 
>>> (http://mxr.mozilla.org/mozilla-central/source/dom/messages/SystemMessageInternal.js#120)
>>> And then sms app on getting the message, it would acquire another 30s cpu 
>>> wake lock and do the notification.
>> I don't think this is a good approach because it brings more power 
>> consumption on the mobile device.
>> Image that when user put the device in suspend state, it will be wake up at 
>> least 30 seconds when SMS is coming before going back to suspend.
>>
>> If every one used this kind of solution to solve their problem then I can 
>> expect that the time of "Day of Use" on FxOS will become bad.
>>
>>> For macro's use case, what if we do the same thing from gecko: acquire a 
>>> wake lock before power button event is dispatching?
>>> And release the wake lock when 'sizemodechange' is notified?
>> The power key didn't always mean "go into suspend", we still need to handle 
>> "sleep menu" by long pressing power key.
>> So we can't use the approach you proposed.
>>
>
> Marco, I thought you are only talking about problems with "press a key
> to wake up a phone" scenario?
>
> Can Gecko implements a temporary wakelock until the key event returns
> from the Gaia system app context? We don't really need 30 sec for that
> if you could determine when the function call returns exactly.
>
> If Gaia ended up waking up the phone, it will do so *within* the function 
> call.
>
>> Thanks,
>> Sincerely yours.
>>
>> - 原始郵件 -
>> 寄件者: "Alive Kuo"
>> 收件者: "Julien Wajsberg"
>> 副本: "Marco Chen", "Mozilla mailing 
>> list"
>> 寄件備份: 2013 9 月 6 星期五 上午 12:38:43
>> 主旨: Re: [b2g] Moving Power Key Handling from Gaia to Gecko According to Bug 
>> 898707
>>
>>
>> Julien Wajsberg 於 2013/9/6 上午12:00 寫道：
>>> What about other things ? For example I can think of when we receive a
>>> SMS. There are Wakelocks in Gaia and in Gecko, but we still have a
>>> problem sometimes (we have a bug for this, I don't remember the number)
>>> and as a result we don't get the notification.
>> AFAIK, this shall

Re: [b2g] Moving Power Key Handling from Gaia to Gecko According to Bug 898707

[Marco Chen]

Hi Tim,

>> The power key didn't always mean "go into suspend", we still need to handle 
>> "sleep menu" by long pressing power key.
>> So we can't use the approach you proposed. 

I gave the first reason of why don't I prefer "get temporary wakelock then find 
a suitable point to release " in previous mail already.
And the second reason is Gecko can't guarantee how Gaia will process power key 
event, so there is no suitable way to hook the ending point of wakelock.
 
Generally to say, each component should take care their usage of wakelock by 
themselves so we can reduce the life cycle of each wakelock.
But this is hard to do when power key is flowing between Gaia and Gecko.

By the other way, there is two purpose of power keys only. One is for 
suspend/resume and the other is for sleep_menu.js.
For first one, I think it is no necessary to be handled by Gaia or is there any 
benefit of handling by gaia?
For second one, gecko can decide to send sleep_menu event to gaia or not.

Thanks,
Sincerely yours.

- 原始郵件 -
寄件者: "Tim Chien" 
收件者: "Marco Chen" 
副本: "Alive Kuo" , "Julien Wajsberg" , 
"Mozilla mailing list" 
寄件備份: 2013 9 月 6 星期五 下午 12:11:54
主旨: Re: [b2g] Moving Power Key Handling from Gaia to Gecko According to Bug 
898707

On Fri, Sep 6, 2013 at 11:52 AM, Marco Chen  wrote:
> Hi all,
>
>> Before system message is dispatched, it would acquire a 30s cpu wake lock. 
>> (http://mxr.mozilla.org/mozilla-central/source/dom/messages/SystemMessageInternal.js#120)
>> And then sms app on getting the message, it would acquire another 30s cpu 
>> wake lock and do the notification.
>
> I don't think this is a good approach because it brings more power 
> consumption on the mobile device.
> Image that when user put the device in suspend state, it will be wake up at 
> least 30 seconds when SMS is coming before going back to suspend.
>
> If every one used this kind of solution to solve their problem then I can 
> expect that the time of "Day of Use" on FxOS will become bad.
>
>> For macro's use case, what if we do the same thing from gecko: acquire a 
>> wake lock before power button event is dispatching?
>> And release the wake lock when 'sizemodechange' is notified?
>
> The power key didn't always mean "go into suspend", we still need to handle 
> "sleep menu" by long pressing power key.
> So we can't use the approach you proposed.
>

Marco, I thought you are only talking about problems with "press a key
to wake up a phone" scenario?

Can Gecko implements a temporary wakelock until the key event returns
from the Gaia system app context? We don't really need 30 sec for that
if you could determine when the function call returns exactly.

If Gaia ended up waking up the phone, it will do so *within* the function call.

> Thanks,
> Sincerely yours.
>
> - 原始郵件 -
> 寄件者: "Alive Kuo" 
> 收件者: "Julien Wajsberg" 
> 副本: "Marco Chen" , "Mozilla mailing list" 
> 
> 寄件備份: 2013 9 月 6 星期五 上午 12:38:43
> 主旨: Re: [b2g] Moving Power Key Handling from Gaia to Gecko According to Bug 
> 898707
>
>
> Julien Wajsberg 於 2013/9/6 上午12:00 寫道：
>> What about other things ? For example I can think of when we receive a
>> SMS. There are Wakelocks in Gaia and in Gecko, but we still have a
>> problem sometimes (we have a bug for this, I don't remember the number)
>> and as a result we don't get the notification.
>
> AFAIK, this shall not be the same case.
> Get sms -> Fire System Message -> sms app's mozSetMessageHandler -> sms 
> requireWakeLock
> Before system message is dispatched, it would acquire a 30s cpu wake lock. 
> (http://mxr.mozilla.org/mozilla-central/source/dom/messages/SystemMessageInternal.js#120)
> And then sms app on getting the message, it would acquire another 30s cpu 
> wake lock and do the notification.
>
> Unless we're so unlucky to get all thing done in 30s + 30s…
>
>
> For macro's use case, what if we do the same thing from gecko: acquire a wake 
> lock before power button event is dispatching?
> And release the wake lock when 'sizemodechange' is notified?
>
>> So I think this problem is more general and can't be solved (generally,
>> I mean) by moving things from gaia to gecko. (even if in the power case
>> this could fix the problem).
>>
>> ___
>> dev-b2g mailing list
>> dev-b2g@lists.mozilla.org
>> https://lists.mozilla.org/listinfo/dev-b2g
>
> Alive C. Kuo, Front end engineer, Mozilla Taiwan
> al...@mozilla.com
>
>
>
>
> ___
> dev-b2g mailing list
> dev-b2g@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-b2g



-- 
Tim Guan-tin Chien, Engineering Manager and Front-end Lead, Firefox
OS, Mozilla Corp. (Taiwan)
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

Re: [b2g] Moving Power Key Handling from Gaia to Gecko According to Bug 898707

[Marco Chen]

Hi all,

> Before system message is dispatched, it would acquire a 30s cpu wake lock. 
> (http://mxr.mozilla.org/mozilla-central/source/dom/messages/SystemMessageInternal.js#120)
> And then sms app on getting the message, it would acquire another 30s cpu 
> wake lock and do the notification.

I don't think this is a good approach because it brings more power consumption 
on the mobile device.
Image that when user put the device in suspend state, it will be wake up at 
least 30 seconds when SMS is coming before going back to suspend.

If every one used this kind of solution to solve their problem then I can 
expect that the time of "Day of Use" on FxOS will become bad.

> For macro's use case, what if we do the same thing from gecko: acquire a wake 
> lock before power button event is dispatching?
> And release the wake lock when 'sizemodechange' is notified?

The power key didn't always mean "go into suspend", we still need to handle 
"sleep menu" by long pressing power key.
So we can't use the approach you proposed. 
 
Thanks,
Sincerely yours.

- 原始郵件 -
寄件者: "Alive Kuo" 
收件者: "Julien Wajsberg" 
副本: "Marco Chen" , "Mozilla mailing list" 

寄件備份: 2013 9 月 6 星期五 上午 12:38:43
主旨: Re: [b2g] Moving Power Key Handling from Gaia to Gecko According to Bug 
898707


Julien Wajsberg 於 2013/9/6 上午12:00 寫道：
> What about other things ? For example I can think of when we receive a
> SMS. There are Wakelocks in Gaia and in Gecko, but we still have a
> problem sometimes (we have a bug for this, I don't remember the number)
> and as a result we don't get the notification.

AFAIK, this shall not be the same case.
Get sms -> Fire System Message -> sms app's mozSetMessageHandler -> sms 
requireWakeLock
Before system message is dispatched, it would acquire a 30s cpu wake lock. 
(http://mxr.mozilla.org/mozilla-central/source/dom/messages/SystemMessageInternal.js#120)
And then sms app on getting the message, it would acquire another 30s cpu wake 
lock and do the notification.

Unless we're so unlucky to get all thing done in 30s + 30s…


For macro's use case, what if we do the same thing from gecko: acquire a wake 
lock before power button event is dispatching?
And release the wake lock when 'sizemodechange' is notified?

> So I think this problem is more general and can't be solved (generally,
> I mean) by moving things from gaia to gecko. (even if in the power case
> this could fix the problem).
> 
> ___
> dev-b2g mailing list
> dev-b2g@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-b2g

Alive C. Kuo, Front end engineer, Mozilla Taiwan
al...@mozilla.com




___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

Re: [b2g] Any plans to support Wayland (or MIR) as a display server on Firefox OS?

[Marco Chen]

Hi,

No, Zygote didn't be used in FxOS.

Sincerely yours.

- 原始郵件 -
寄件者: "Arun Kumar Singh" 
收件者: "Andreas Gal" , "arky" 
副本: mozilla-dev-...@lists.mozilla.org
寄件備份: 2013 9 月 4 星期三 下午 5:28:48
主旨: Re: [b2g] Any plans to support Wayland (or MIR) as a display server on 
Firefox OS?

Hello Andreas,

I also wanted to check if zygote is used in  FFOS

-Arun
-Original Message-
From: dev-b2g 
[mailto:dev-b2g-bounces+arun.kumar.singh=intel@lists.mozilla.org] On Behalf 
Of Andreas Gal
Sent: Saturday, August 31, 2013 9:20 PM
To: arky
Cc: mozilla-dev-...@lists.mozilla.org
Subject: Re: [b2g] Any plans to support Wayland (or MIR) as a display server on 
Firefox OS?


We are not using SurfaceFlinger in FFOS. Our rendering engine (Gecko) acts as 
display server, and directly composites into the framebuffer using OpenGL ES. 
There is no benefit FFOS could derive from SurfaceFlinger or Wayland.

Andreas

arky wrote:
> On 08/31/2013 04:03 PM, Oliver Propst wrote:
>> Hi,
>> To my understanding Firefox OS today uses the Android graphics stack 
>> including SurfaceFlinger as its display server. Is there any plans to
> implement a compositor that support the Wayland protocol or maybe 
> rather investigate/research the benefits of that approach, or possibly 
> explore the possibility to use Ubuntu's new display server MIR?
>
> +1
>
> Thanks posting the question Oliver, I wondering the same after looking 
> at the Philipp's heavily patched release[1] for Raspberry Pi.
>
> Cheers
>
> --arky
>
>
> [1]
> https://www.philipp-wagner.com/blog/2013/04/firefox-os-for-raspberry-p
> i-now-available/
>
>
>
> ___
> 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] Moving Power Key Handling from Gaia to Gecko According to Bug 898707

[Marco Chen]

Hi all,

I do a cross post to dev-gaia because there is no response from gecko.
And the current power handling mechanism is on Gaia.

Sincerely yours.

- 原始郵件 -
寄件者: "Marco Chen" 
收件者: "Mozilla" 
寄件備份: 2013 8 月 28 星期三 下午 6:56:34
主旨: [b2g] Moving Power Key Handling from Gaia to Gecko According to Bug 898707

Hi all,

This mail is used to discuss the motivation on moving power key handling from 
Gaia to Gecko (according to Bug 898707).
Please refer to the link as below for what I mentioned here.

https://docs.google.com/a/mozilla.com/drawings/d/1nT0WOW-Xgxp0oNzgRx7BOdxMBrDKf0cxDVfLXMeziA8/edit

The blue/pink/purple arrows are used to indicate flows of handling power key 
between kernel driver, gecko and gaia.
And only blue arrows are protected by WakeLock.
So there may be a chance that kernel will go back to suspend state before FxOS 
finished to process the power key then change power state from 3 -> 0.

  "In order to avoid this issue, we should guarantee that whole flows of power 
key handling are protected by WakeLock."

But you can see the flows now it goes through layers between Gaia & Gecko, that 
is hard to protect by WakeLock.
So I proposed to move power key handling from Gaia to Gecko as well as the idle 
timer management.
Then it becomes more easy to deal with this issue and process power more 
quickly and in time (ex: race condition between power key & idle timer).

Why does current other devices didn't have this issue? 
Because there is a WakeLock with N second timeout requested from kernel when 
every time device is woken up from suspend state.
That wakelock with timeout covered the time for power key handling.
But actually it introduced more power consumption when device is woken up by 
the reason which didn't need to bring the power state back to 0.
Ex: network signal strength change or network status change.

Please give some feedback for this.
Thanks,
Sincerely yours.
-
Marco Chen
Engineering Manager
System Team, Device Engineering
Mozilla Taiwan

Tel: +886-2-87861100 # 352
mail: mc...@mozilla.com

___
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] Wake-up phone

[Marco Chen]

Hi,

There are two reasons for this issue we found until now.

1. Bug 904544 - hold wakelock to make sure input devices event can be handle 
before suspend

2. 
https://docs.google.com/a/mozilla.com/drawings/d/1nT0WOW-Xgxp0oNzgRx7BOdxMBrDKf0cxDVfLXMeziA8/edit
a. The power key handling from Gecko/Gaia didn't do wakelock protection 
well. (The pink and purple arrows didn't be protected by wakeloc,.)
b. So if kernel didn't help to hold a wakelock with constant timeout during 
resuming state then power key handling may not be done before re-entering to 
suspend.

Thanks,
Sincerely yours.

- 原始郵件 -
寄件者: "an" 
收件者: dev-b2g@lists.mozilla.org
寄件備份: 2013 9 月 4 星期三 上午 11:46:12
主旨: Re: [b2g] Wake-up phone

If it's of any help, I just figured out that the phone wakes every time if I 
press the volume button immediately after the power button.

On Wednesday, September 4, 2013 5:21:57 AM UTC+3, Marco Chen wrote:
> - 原始郵件 -
> 

> 
> Any news on this issue?
> 
> 
> 
> On Monday, August 5, 2013 10:18:20 PM UTC+3, an wrote:
> 
> > On Monday, August 5, 2013 5:25:17 AM UTC+3, Marco Chen wrote:
> 
> > 
> 
> > > Hi,
> 
> > 
> 
> > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > We are trying to look this bug on Helix project now.
> 
> > 
> 
> > > 
> 
> > 
> 
> > > And the initial idea is that FxOS didn't have sufficient time for 
> > > changing the power state from 3 to 0 within 0.5 seconds.
> 
> > 
> 
> > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > The suspect flow is
> 
> > 
> 
> > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > >   a. Apps processor got a RPC message for power key event.
> 
> > 
> 
> > > 
> 
> > 
> 
> > >   b. Linux kernel is woken up and processed the early resuming process. 
> 
> > 
> 
> > > 
> 
> > 
> 
> > >   c. During step b kernel hold a wake lock for 0.5 seconds and expect any 
> > > one to decide whether system should be woken up from power state 3 to 0.
> 
> > 
> 
> > > 
> 
> > 
> 
> > >   d. Gecko's input widget received a power key event from input device 
> > > then throw a runnable event to main thread for following works.
> 
> > 
> 
> > > 
> 
> > 
> 
> > >   e. Before main thread got this power key event ( then sending to 
> > > shell.js -> chrome event -> system app -> power Web API -> Gecko -> 
> > > Changing power state ),
> 
> > 
> 
> > > 
> 
> > 
> 
> > >the 0.5 seconds is time out and system go into suspend again.
> 
> > 
> 
> > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > So what we saw will be
> 
> > 
> 
> > > 
> 
> > 
> 
> > >   1. pressing power key multi-times then device can be woken up.
> 
> > 
> 
> > > 
> 
> > 
> 
> > >   2. Pluggin USB then device can be woken up.
> 
> > 
> 
> > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > We tried to prove this and figure out the solution.
> 
> > 
> 
> > 
> 
> > 
> 
> > That's the behavior I'm seeing and that's what I imagined it might happen 
> > as you describe it. Not being a developer the whole chain of events was a 
> > more abstract one ;) to me but when I press the power key the soft buttons 
> > light up for a second as if the phone wants to wake up but it somehow 
> > looses steam.
> 
> > 
> 
> > Please keep me posted with your findings and eventual solutions.
> 
> > 
> 
> > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > Sincerely yours.
> 
> 
> 
___
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] Wake-up phone

[Marco Chen]

- 原始郵件 -
寄件者: "an" 
收件者: dev-b2g@lists.mozilla.org
寄件備份: 2013 9 月 4 星期三 上午 12:04:08
主旨: Re: [b2g] Wake-up phone

Any news on this issue?

On Monday, August 5, 2013 10:18:20 PM UTC+3, an wrote:
> On Monday, August 5, 2013 5:25:17 AM UTC+3, Marco Chen wrote:
> 
> > Hi,
> 
> > 
> 
> > 
> 
> > 
> 
> > We are trying to look this bug on Helix project now.
> 
> > 
> 
> > And the initial idea is that FxOS didn't have sufficient time for changing 
> > the power state from 3 to 0 within 0.5 seconds.
> 
> > 
> 
> > 
> 
> > 
> 
> > The suspect flow is
> 
> > 
> 
> > 
> 
> > 
> 
> >   a. Apps processor got a RPC message for power key event.
> 
> > 
> 
> >   b. Linux kernel is woken up and processed the early resuming process. 
> 
> > 
> 
> >   c. During step b kernel hold a wake lock for 0.5 seconds and expect any 
> > one to decide whether system should be woken up from power state 3 to 0.
> 
> > 
> 
> >   d. Gecko's input widget received a power key event from input device then 
> > throw a runnable event to main thread for following works.
> 
> > 
> 
> >   e. Before main thread got this power key event ( then sending to shell.js 
> > -> chrome event -> system app -> power Web API -> Gecko -> Changing power 
> > state ),
> 
> > 
> 
> >the 0.5 seconds is time out and system go into suspend again.
> 
> > 
> 
> > 
> 
> > 
> 
> > So what we saw will be
> 
> > 
> 
> >   1. pressing power key multi-times then device can be woken up.
> 
> > 
> 
> >   2. Pluggin USB then device can be woken up.
> 
> > 
> 
> > 
> 
> > 
> 
> > We tried to prove this and figure out the solution.
> 
> 
> 
> That's the behavior I'm seeing and that's what I imagined it might happen as 
> you describe it. Not being a developer the whole chain of events was a more 
> abstract one ;) to me but when I press the power key the soft buttons light 
> up for a second as if the phone wants to wake up but it somehow looses steam.
> 
> Please keep me posted with your findings and eventual solutions.
> 
> 
> 
> > 
> 
> > 
> 
> > 
> 
> > Sincerely yours.

___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

[b2g] Moving Power Key Handling from Gaia to Gecko According to Bug 898707

[Marco Chen]

Hi all,

This mail is used to discuss the motivation on moving power key handling from 
Gaia to Gecko (according to Bug 898707).
Please refer to the link as below for what I mentioned here.

https://docs.google.com/a/mozilla.com/drawings/d/1nT0WOW-Xgxp0oNzgRx7BOdxMBrDKf0cxDVfLXMeziA8/edit

The blue/pink/purple arrows are used to indicate flows of handling power key 
between kernel driver, gecko and gaia.
And only blue arrows are protected by WakeLock.
So there may be a chance that kernel will go back to suspend state before FxOS 
finished to process the power key then change power state from 3 -> 0.

  "In order to avoid this issue, we should guarantee that whole flows of power 
key handling are protected by WakeLock."

But you can see the flows now it goes through layers between Gaia & Gecko, that 
is hard to protect by WakeLock.
So I proposed to move power key handling from Gaia to Gecko as well as the idle 
timer management.
Then it becomes more easy to deal with this issue and process power more 
quickly and in time (ex: race condition between power key & idle timer).

Why does current other devices didn't have this issue? 
Because there is a WakeLock with N second timeout requested from kernel when 
every time device is woken up from suspend state.
That wakelock with timeout covered the time for power key handling.
But actually it introduced more power consumption when device is woken up by 
the reason which didn't need to bring the power state back to 0.
Ex: network signal strength change or network status change.

Please give some feedback for this.
Thanks,
Sincerely yours.
-----
Marco Chen
Engineering Manager
System Team, Device Engineering
Mozilla Taiwan

Tel: +886-2-87861100 # 352
mail: mc...@mozilla.com

___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

Re: [b2g] Bluetooth and gamepad API?

[Marco Chen]

Hi Kyle,

(The discuss here now is focused on Gamepad thought USB not BT HID profile)

As my experience, mobile device normally acted as a USB client mode and it 
should be changed to USB Host mode for servicing the GamePad device.
And USB OTG is a feature on most current device now.

Then once USB OTG is enabled, a USB mouse can be used on Tablet device. 
According to this I think HID manager is supported by Android kernel.

Thanks,
Sincerely yours.

- 原始郵件 -
寄件者: "Kyle Machulis" 
收件者: "Marco Chen" 
副本: "jose llopis" , "Mozilla" 
寄件備份: 2013 8 月 20 星期二 上午 2:58:38
主旨: Re: [b2g] Bluetooth and gamepad API?

Other relevant bugs:

Bug 852944 - Add content process support to Gamepad backend
Bug 852945 - Gonk gamepad backend

I've got both assigned to me at the moment, as well as the gamepad haptics 
bugs. Would love to take a look at them soon, but that hasn't happened yet. If 
someone has cycles and wants to help out, lemme know.

I think the big question for usb is the current HID manager support in our 
android kernel. If that exists, we don't need the bluetooth hid layer to be 
done before implementing this. We could just put code in HAL that uses the hid 
manager (similar to what we do with the desktop platforms for joysticks). I'll 
poke around in the 4.3 build and see what the state of that is.

- Original Message -
> From: "Marco Chen" 
> To: "jose llopis" 
> Cc: "Mozilla" 
> Sent: Monday, August 19, 2013 7:56:06 AM
> Subject: Re: [b2g] Bluetooth and gamepad API?
> 
> Hi,
> 
> If you mean HID profile of Bluetooth, please refer to "Bug 880759 -
> [Bluetooth][meta] Implement HID profile feature".
> And it is still on going.
> 
> Sincerely yours.
> 
> - 原始郵件 -
> 寄件者: "jose llopis" 
> 收件者: "Mozilla" 
> 寄件備份: 2013 8 月 19 星期一 下午 7:52:35
> 主旨: [b2g] Bluetooth and gamepad API?
> 
> is there any way to use a bluetooth gamepad on firefox os?
> ___
> 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] SerialPort communication?

[Marco Chen]

Hi Kyle,

What I image about WebUSB is just there is a way for communicating between 
external device and Web Apps.
So there will be 

  1. a generic USB driver for exposing USB dev node to userspace.
  2. a Gecko component / Web API to provide a way for connecting Web Apps & USB 
dev node.
  3. a communicating protocol through exposed dev node.

Then the data flow will just be happened between external device and Web Apps 
and what function will be provided by Web Apps is through standard Web API too.
Based on this model, may I know what security issue needed to be considered.

Ex: A USB camera can be connected to Fx OS device and a corresponding Web Apps 
can act as a camera app by WebUSB and other Web APIs (media stream, canvas, 
image and others).

--

About the libusb and libusbhost you mentioned is about whether FxOS device acts 
as a USB Host or Client mode.
And it is related to the power source and enumeration control, I think it is 
not directly related to WebUSB.

Thanks,
Sincerely yours. 


- 原始郵件 -
寄件者: "Kyle Machulis" 
收件者: "Fabrice Desre" 
副本: "Marco Chen" , "jose llopis" , 
"Mozilla" 
寄件備份: 2013 8 月 20 星期二 上午 2:50:05
主旨: Re: [b2g] SerialPort communication?

Profiles are bluetooth, not USB. While there are device classes in USB (HID, 
USB Audio, storage, etc), it's still different than BT profiles.

WebUSB did have some initial implementation in summer of 2011, but that's all 
seriously bitrotted now and was aimed for desktop. For generic USB on FxOS, 
we'd need a OOP'd DOM API, then a layer to hook it up to Android's libusbhost 
library (which looks like libusb but not quite). This is by no means trivial 
work, since we'd need to figure out exactly what parts of USB we wanted to 
support (Just simple interrupt/bulk? Full isochronous support to write frames 
to a canvas? Supporting some device classes across the whole system?), security 
would be a nightmare, etc. Not saying it can't be done, it's just a long way 
off.

- Original Message -
> From: "Fabrice Desre" 
> To: "Marco Chen" 
> Cc: "jose llopis" , "Mozilla" 
> 
> Sent: Monday, August 19, 2013 8:38:01 AM
> Subject: Re: [b2g] SerialPort communication?
> 
> Hi Marco,
> 
> On 08/19/2013 07:54 AM, Marco Chen wrote:
> > Hi Jose,
> > 
> > There is a "Bug 674718 - (webusb) WebUSB" for what you want, but it is
> > pending now.
> > 
> > Hi all,
> > 
> > I saw some discussion on the development for userspace.
> > May I know whether we need a generic USB driver with generic Mozilla
> > protocol for communicating between web app and external USB device?
> 
> I think we need a way to let profiles be implemented in content JS, if
> this is what you mean or is this covered by bug 674718 ?
> 
>   Fabrice
> --
> Fabrice Desré
> b2g team
> Mozilla Corporation
> ___
> dev-b2g mailing list
> dev-b2g@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-b2g
> 
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

Re: [b2g] Bluetooth and gamepad API?

[Marco Chen]

Hi,

If you mean HID profile of Bluetooth, please refer to "Bug 880759 - 
[Bluetooth][meta] Implement HID profile feature".
And it is still on going.

Sincerely yours.

- 原始郵件 -
寄件者: "jose llopis" 
收件者: "Mozilla" 
寄件備份: 2013 8 月 19 星期一 下午 7:52:35
主旨: [b2g] Bluetooth and gamepad API?

is there any way to use a bluetooth gamepad on firefox os?
___
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] SerialPort communication?

[Marco Chen]

Hi Jose,

There is a "Bug 674718 - (webusb) WebUSB" for what you want, but it is pending 
now.

Hi all,

I saw some discussion on the development for userspace.
May I know whether we need a generic USB driver with generic Mozilla protocol 
for communicating between web app and external USB device?

Thanks,
Sincerely yours.

- 原始郵件 -
寄件者: "jose llopis" 
收件者: "Mozilla" 
寄件備份: 2013 8 月 19 星期一 下午 7:34:23
主旨: [b2g] SerialPort communication?

How can i use my phone to communicate with an usb accesory?
___
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] LED API?

[Marco Chen]

Hi all,

There is already a light HAL in Gecko for enabling the LEDs.

Here shows that how many types of light we can use.
http://mxr.mozilla.org/mozilla-central/source/hal/HalTypes.h#28

Here is a sample of we try to light a LED for use case of battery.
http://mxr.mozilla.org/mozilla-central/source/hal/gonk/GonkHal.cpp#283

Sincerely yours.
- 原始郵件 -
寄件者: "Alexandre Lissy" 
收件者: dev-b2g@lists.mozilla.org
寄件備份: 2013 8 月 6 星期二 下午 5:10:46
主旨: Re: [b2g] LED API?

Le 06/08/2013 10:47, Jonas Sicking a écrit :
> On Aug 6, 2013 12:54 AM, "Jordano Francisco (UK)" <
> francisco.jord...@telefonica.com> wrote:
>>
>> Hi all,
>>
>>
>> On 06/08/2013 07:43, "Jonas Sicking"  wrote:
>>
>>> On Aug 5, 2013 11:07 PM, "Karim Geiger"  wrote:

 On 08/05/2013 07:26 PM, Jonas Sicking wrote:
> No. Do we need any?

 I think that's an important point. There are some cases you want to
 control the LED separately.
>>>
>>> I think we need a bit more detail than that in order to spend time on
> this
>>> :-)
>>>
>>> / Jonas
>>
>> Typical use case for this api could be notifications, like FB
>> notifications in android,
>> use this API to setup the led blue.
>>
>> Other use cases (in samsung android phones):
>>
>> Red when plugged in - Charging
>> Green when plugged in - Charging complete.
>> Red when not plugged in - Low battery warning
>> Blue - Audio is recording or you have a notification waiting.
> 
> Is the LED usually in control of system level logic, or is it more commonly
> handled by drivers?
> 
> I.e. would we be able to implement a LED API on most platforms?

On a kernel level they appear to be part of the 'leds' class.

For example, on Inari, you have:
# ls -l /sys/class/leds/
lrwxrwxrwx root root  2013-08-06 10:45 button-backlight
-> ../../devices/platform/leds-gpio/leds/button-backlight
lrwxrwxrwx root root  2013-08-06 10:45 green ->
../../devices/platform/pmic-leds/leds/green
lrwxrwxrwx root root  2013-08-06 10:45 lcd-backlight ->
../../devices/platform/msm_fb.524801/leds/lcd-backlight
lrwxrwxrwx root root  2013-08-06 10:45 red ->
../../devices/platform/pmic-leds/leds/red

If you echo 1 to /sys/class/leds/green/brightness and to
/sys/class/leds/red/brightness, you get an orange led notification on
Inari :)

Cross checking, I get similar behavior on Desire Z running Android 2.3.3.

> 
> Either way, implementing an API which is exposed to only the system app
> sounds like it would make sense. Though we would likely need the API to
> expose which colors the hardware is able to support.
> 
> / Jonas
> ___
> 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] Wake-up phone

[Marco Chen]

Hi,

We are trying to look this bug on Helix project now.
And the initial idea is that FxOS didn't have sufficient time for changing the 
power state from 3 to 0 within 0.5 seconds.

The suspect flow is

  a. Apps processor got a RPC message for power key event.
  b. Linux kernel is woken up and processed the early resuming process. 
  c. During step b kernel hold a wake lock for 0.5 seconds and expect any one 
to decide whether system should be woken up from power state 3 to 0.
  d. Gecko's input widget received a power key event from input device then 
throw a runnable event to main thread for following works.
  e. Before main thread got this power key event ( then sending to shell.js -> 
chrome event -> system app -> power Web API -> Gecko -> Changing power state ),
   the 0.5 seconds is time out and system go into suspend again.

So what we saw will be
  1. pressing power key multi-times then device can be woken up.
  2. Pluggin USB then device can be woken up.

We tried to prove this and figure out the solution.

Sincerely yours.

- 原始郵件 -
寄件者: "Alexandre Lissy" 
收件者: dev-b2g@lists.mozilla.org
寄件備份: 2013 8 月 4 星期日 下午 10:51:46
主旨: Re: [b2g] Wake-up phone

Le 04/08/2013 16:47, an a écrit :
> 
>> This clearly sounds like a bug that has been already fixed a while ago.
>>
>> Confere https://bugzilla.mozilla.org/show_bug.cgi?id=865570
> 
> That wasn't it unfortunately because the alarm clock works.

Yeah, well, sorry, I got mislead by your title and reply, and mixed up
bugs :).

The bug I linked is totally irrelevant, but I'm sometimes experiencing
the behavior you describe.

> 
> ___
> 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] boot-2-gecko on telechip based devices how-tos

[Marco Chen]

Hi,

Please refer to the link as below for the basic steps to port Fx OS into your 
device.

https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Porting

Sincerely yours.

- 原始郵件 -
寄件者: "Towfique anam" 
收件者: dev-b2g@lists.mozilla.org
寄件備份: 2013 7 月 23 星期二 下午 11:28:41
主旨: [b2g] boot-2-gecko on telechip based devices how-tos

hi,I own a coby kryos mid 7015 that is based on telechip 8902 chipset,I want to 
port boot2gecko on that.any help regarding how to port?device is rooted.

Towfique Anam Rine
E-mail:anamtowfi...@gmail.com
Mozillian Profile:https://mozillians.org/en-US/u/towfiqueanam/
about.me:http://about.me/towfiqueanam
Blogger:http://121n3.blogspot.com
Prezi:http://prezi.com/user/121n3
Twitter is @121n3  & Facebook is fb.me/121n3,
Website:http://www.121n3.com(currently out of service)


  
___
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] No files can be accessed in external storages

[Marco Chen]

Hi Hiro,

Gaia used DeviceStorage Web API for accessing the file system.
and according to the security issue currently we limited Gaia apps to access 
media files in "/sdcard" folder only.

On the other way the availability of "/sdcard" device storage is mapped to 
storages from Vold so your new block device can't be automatically mounted.

Sincerely yours.

- 原始郵件 -
寄件者: "Hiroyuki KOHARA" 
收件者: dev-b2g@lists.mozilla.org
寄件備份: 2013 6 月 24 星期一 下午 12:56:07
主旨: Re: [b2g] No files can be accessed in external storages

Hi Marco,

Thanks for your response.

> 1. Does the board & BSP you used support USB OTG function and is it enabled?

- The Pandaboard I use supports the USB OTG function and it is 
enabled in my environment.

> 2. FxOS now doesn't monitor the new partitions from USB OTG, so new 
partition will not be mounted automatically.

- I mount a new partition manually every time, however I don't 
know how to access any files from API (that is an application 
level). Would you give me some advice?

Best regards,
Hiro
___
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] No files can be accessed in external storages

[Marco Chen]

Hi Hiro,

1. Does the board & BSP you used support USB OTG function and is it enabled?
(You would check that whether there is a new block device appeared.)

2. FxOS now doesn't monitor the new partitions from USB OTG, so new partition 
will not be mounted automatically.

Thanks,
Sincerely yours.

- 原始郵件 -
寄件者: "Hiroyuki KOHARA" 
收件者: dev-b2g@lists.mozilla.org
寄件備份: 2013 6 月 24 星期一 上午 10:32:37
主旨: Re: [b2g] No files can be accessed in external storages

Hi there,

For your information, I can't read or write any files in 
external USB storages such as USB memories, USB HDDs and USB 
cameras. I would like to determine whether or not it is the 
Pandaboard-dependent problem.

Would you give me any information on the external USB storage's 
access?

Thanks.

Hiro
___
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] catching volume events

[Marco Chen]

Hi,

Actually the event of HW button is limited to access by Chrome (B2G) process 
only.
And Gecko didn't send it via IPC into other content process.
This is why your app (in content process) can't listen any event from HW buttom.

Sincerely yours.

- Original Message -
From: "Rodrigue Villetard" 
To: "Alive Kuo" 
Cc: dev-b2g@lists.mozilla.org
Sent: 2013年6月13日 星期四 21:12:29
Subject: Re: [b2g] catching volume events



Hi,

Thanks for your answer and sorry for my own long answering delay…

I’ve read the issues on bugzilla  thate Alive (is this your firstname ? 
sorry for asking…) pointed me out, unfortunately, that didn’t solve my 
problem.


After that, I’ve found in GAIA code those two files :

https://github.com/mozilla-b2g/gaia/blob/979126f56c6ad3608770049f5ba71cf3e0c3857f/apps/system/js/hardware_buttons.js
https://github.com/mozilla-b2g/gaia/blob/979126f56c6ad3608770049f5ba71cf3e0c3857f/apps/system/js/sound_manager.js

As far as i understand, some events should be triggered on window 
object, such as "volumeup", "volumedown", "home", etc. But, in my code,  
my listener never call the callback :

window.addEventListener('volumeup', callback); // callback is never 
called…


Does anybody have a clue ?

Note I am working with a peak OS Version : 1.0.1.0 prerelease (standard 
OTA version)

best regards,
Rodrigue


On 2013-05-28 04:29, Alive Kuo wrote:
> Hi,
>
> Unfortunately you couldn't access any hardware button now from your 
> app.
> See this for reference:
> https://bugzilla.mozilla.org/show_bug.cgi?id=839446 [3] Implement
> DOM3 KeyboardEvent types for media
>
> --
> Alive C. Kuo, Front-end Eng., Mozilla Corp. (Taiwan, Taipei)
>
> Rodrigue Villetard  於 2013/5/28 
> 上午2:13 寫道：
>
>> Hi all!
>>
>> Is there a way to access volume buttons event ?
>>
>> I’m currently developping a FirefoxOS mpd client (http://musicpd.org 
>> [1] && http://hgrepos.sacristi.fr/barosofts/foxympd [2]) and I would 
>> like to propose (as an option) volume button mapping to adjust server 
>> volume instead of emulate with html buttons.
>>
>> regards,
>> Rodrigue.
>> ___
>> dev-b2g mailing list
>> dev-b2g@lists.mozilla.org
>> https://lists.mozilla.org/listinfo/dev-b2g
>
>
>
> Links:
> --
> [1] http://musicpd.org
> [2] http://hgrepos.sacristi.fr/barosofts/foxympd
> [3] https://bugzilla.mozilla.org/show_bug.cgi?id=839446
___
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] Video-play Problems on the Firefox OS enabled PandaboardES

[Marco Chen]

Hi,

About 1), the log (adb logcat or dmesg) may help to find out some clue.

About 2), WebM is only decoded by SW codec now and for MP4 you can refer to the 
link
  as below. Currently we force video decoding to be done by HW codec 
only.
  You can set that flag to SW for testing.

  
https://mxr.mozilla.org/mozilla-central/source/content/media/omx/OmxDecoder.cpp#283

Sincerely yours.
- Original Message -
From: "Hiroyuki KOHARA" 
To: dev-b2g@lists.mozilla.org
Sent: 2013年6月7日 星期五 9:52:37
Subject: Re: [b2g] Video-play Problems on the Firefox OS enabled PandaboardES

Hi Thomas,

Thanks for your quick response. I have some relative questions.

1) Regarding MP4 files, I confirmed that there were some 
libraries relative to H.264 decoders as follows;
  B2G/out/target/product/panda/system/lib
   - libOMX.TI.DUCATI1.VIDEO.H264E.so
   - libstagefright_soft_h264dec.so

I would like to know the reason why MP4 files can't be played on
 the "Firefox OS" enabled Pandaboard, but on the "Android" 
enabled Pandaboard successfully and smoothly.

2) Please teach me how to switch back and forth between the 
hardware decoder and the software decoder on Firefox OS enabled 
devices such as the phones and the Pandaboard.

For your information, I tried to play the following video files 
in B2G/gaia/test_media/Movies;
   - elephants-dream.webm
 - Google/On2's V8 Video(VP80)
 - 540x360
 - Vorbis Audio(vorb)

   - gizmo2.mp4
 - H264-MPEG4-AVC(part10) (avc1)
 - 320x240
 - MPEG AAC Audio(mp4a)

Best regards,
Hiro


On Thu, 06 Jun 2013 10:19:42 +0200
Thomas Zimmermann  wrote:
> Hi Hiro,
> 
> Thanks for the feedback. WebM files are software decoded (afaik) and the 
> graphics on the Pandaboard is quite slow. Maybe the board just cannot 
> handle the amount of data. Does it improve if you reduce the resolution 
> of the video?
> 
> MP4 is just the container format. I guess that the video codec is not 
> supported on Pandaboard. For some video codecs, we can use the decoder 
> libraries that come with the phones. But we don't have such support 
> available on the pandas.
> 
> Best regards
> Thomas
> 
> 
> On 06.06.2013 08:29, Hiroyuki KOHARA wrote:
> > Hi there,
> >
> > I have some video-play problems on the Firefox OS enabled
> > Pandaboard ES. The problems are both that I can't replay any
> > WebM files "smoothly" and that I can't replay any MP4 files at
> > all. Would you teach me how to resolve the problems?
> >
> > In comparison, I confirmed the logs in the two following
> > conditions.
> > 1) When I started the "CrystalSkull" application on the same "
> > Firefox OS" enabled Pandaboard ES;
> > D/libEGL  ( 1543): loaded /system/lib/egl/libGLES_android.so
> > D/libEGL  ( 1543): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_
> > 120.so
> > D/libEGL  ( 1543): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_
> > SGX540_120.so
> > D/libEGL  ( 1543): loaded /vendor/lib/egl/libGLESv2_POWERVR_
> > SGX540_120.so
> >
> > 2) When I started to play the "WebM file" with the video player
> > on the "Android" enabled Pandaboard ES;
> > D/libEGL  (  842): loaded /system/lib/egl/libGLES_android.so
> > D/libEGL  (  842): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_
> > 120.so
> > D/libEGL  (  842): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_
> > SGX540_120.so
> > D/libEGL  (  842): loaded /vendor/lib/egl/libGLESv2_POWERVR_
> > SGX540_120.so
> >
> > On the other hand, I couldn't find any loaded logs when starting
> >   to play the "WebM file" with the video player on the same "
> > Firefox OS" enabled Pandaboard ES.
> >
> > Thank you.
> > Hiro
> > ___
> > 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] Getting the source code for Gonk

[Marco Chen]

Hi,

>> Android source code ( version 3.0)  Is it possible to port the firefox over 
>> this version.

FxOS now fully supported porting on Android ICS (4.0.4) and is ongoing to port 
on JB (4.2.2 r1).
There is no plan to do it on HC (3.X) until now.

>> What is the purpose of adding the new device in the config.sh ?

1. This config.sh will be used to list what devices are supported now.
2. Based on device name (ex: ./config.sh unagi), this script will download the 
whole source tree via repo init & sync from a manifest file.
3. Then you can build the image.

>> What is the purpose of changing the manifest file

1. According to explanation above, you need a manifest file for downloading 
device's source tree.
2. The modification from original manifest file is for 
 a. Add git repo for Gaia, Gecko, gonk-misc ...etc which is came from B2G 
project.
 b. Replace build repo from Android by mozilla's which hacks something to 
build B2G.
 c. Remove unnecessary folders which are not used by B2G. 

Thanks,
Sincerely yours.
- Original Message -
From: "SobinX Thomas" 
To: dev-b2g@lists.mozilla.org
Cc: "dev-gaia" , b2g-release-driv...@mozilla.org
Sent: 2013年6月5日 星期三 13:01:12
Subject: Re: [b2g] Getting the source code for Gonk

Hi Firefox team,

I was going through the webpage 

https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Porting

I want to port the Firefox over Android Platform. I have got the Android source 
code ( version 3.0) 
Is it possible to port the firefox over this version.

I have got additional questions that I have specified below.


I could not understand below points

1. 
=
Add a new device to config.sh

The next step is to add a new device to config.sh; you can use the existing 
ones as a template. This basically involves providing the instructions for 
fetching the correct files to do the build.

=

What is the purpose of adding the new device in the config.sh ?

2. 

Create the manifest file for the new device

Now you need to add the required repos to the manifest file for the new device; 
this manifest file is called default.xml. Refer to the b2g-manifest file on 
github for a template. Each device has its own branch; you can use the 
galaxy-s2 branch as a reference.

=
What is the purpose of changing the manifest file

Thanks
Regards
Sobin Thomas




-Original Message-
From: Gregor Wagner [mailto:gwag...@mozilla.com] 
Sent: Tuesday, June 04, 2013 4:32 PM
To: Thomas, SobinX
Cc: dev-gaia; dev-b2g@lists.mozilla.org; b2g-release-driv...@mozilla.org
Subject: Re: Getting the source code for Gonk

Hi Thomas,

there is no single folder containing all gonk code. You can grep for gonk 
folders and some of the code is in gecko/dom/system or in gecko/hal for example.
Various files also contain gonk specific code. You can find it via 
MOZ_WIDGET_GONK.
afaik we are using version 3.0.21

hth,
-Gregor

On Jun 4, 2013, at 12:12 PM, "Thomas, SobinX"  wrote:

> Hi All,
> 
> I recently downloaded the B2G code. But I could not find the source 
> code for the Gonk Please help in getting the source code for Gonk. 
> Also please update what is the linux version used in the Gonk
> 
> Thanks
> Regards
> Sobin Thomas
> 
> ___
> dev-gaia mailing list
> 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
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

Re: [b2g] Getting the source code for Gonk

[Marco Chen]

Hi,

You can refer to the link as below.
It contains the manifest files, so you can find all sources from it.

https://github.com/mozilla-b2g/b2g-manifest

Or do you need other information?

Sincerely yours.
- Original Message -
From: "SobinX Thomas" 
To: "dev-gaia" , dev-b2g@lists.mozilla.org, 
b2g-release-driv...@mozilla.org
Sent: 2013年6月4日 星期二 18:12:26
Subject: [b2g] Getting the source code for Gonk

Hi All,

I recently downloaded the B2G code. But I could not find the source code for 
the Gonk
Please help in getting the source code for Gonk. Also please update what is the 
linux version used in the Gonk

Thanks
Regards
Sobin Thomas

___
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] Speaker is not working while WiFi or data is on

[Marco Chen]

Hi,

Maybe you can fire a bug on bugzilla 
(https://bugzilla.mozilla.org/enter_bug.cgi?product=Boot2Gecko).
And give us your reproducing steps and any logs (ex: adb logcat, kmsg).
That will help developers to distinguish the issue.

Thanks.

- Original Message -
From: "Ashickur Rahman Noor" 
To: "dev-b2g" 
Sent: 2013年5月28日 星期二 1:57:47
Subject: [b2g] Speaker is not working while WiFi or data is on

Hi Mozillians

I am using b2g 1.1.0.0 . Today I notice that, if I enable wifi or data,
speaker not works. I have to restart the device again. I think it is a bug.

--
Dedicated Linux Forum in Bangladesh 
2048R/89C932E1 
Mozilla Reps 
01199151550, 01551151550
___
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] Alarm volume can't be modified

[Marco Chen]

Hi,

May I know the way you used to set the volume for alarm type?

Q1: From HW volume keys or slider bars in settings app?

Q2: Do you adjust alarm volume during alarm is fired or before it?

Thanks.

- Original Message -
From: "Fernando Guillen" 
To: dev-b2g@lists.mozilla.org
Sent: 2013年5月25日 星期六 19:00:39
Subject: [b2g] Alarm volume can't be modified

Device: Keon (qcom)
SO: Boot2Gecko 1.1.0.0-prerelease

To reproduce the issue I set an alarm and set the volume to only one point.

The sound is noisy as hell, while the alarm is sounding I try to add
more volume and the sound remains the same, only when I remove all the
sound points (silent mode) I can feel the difference which is the
sound disappears.

This make me think that the alarm sound is not properly matched with
my actual volume settings.

f.

-- 
Fernando Guillén
Freelance Web Developer
http://www.fernandoguillen.info
http://spainrb.org/fernando-guillen
___
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] Orientation Webapi.

[Marco Chen]

Hi,

You can refer to the link as below. Which is used to test orientation sensor on 
gaia app.
https://github.com/mozilla-b2g/gaia/blob/master/test_apps/test-sensors/js/physical-events.js#L23

Sincerely yours.



- Original Message -
From: "A. Crespo" 
To: "Dev B2G List" 
Sent: 2013年5月26日 星期日 22:43:12
Subject: [b2g] Orientation Webapi.

Hi there,

Could you help me with this easy example about how to use the Orientation
WebApi on FirefoxOS?
http://pastebin.com/kvUypMhL

What am I doing wrong? The event doesn't seem to be triggered when the
orientation is changed. I haven even tried:
screen.addEventListener("orientationchange", show, false);
But I was out of luck.

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

Re: [b2g] [B2G] Audio path routing

[Marco Chen]

Hi all,

To re-post the idea on creating new Web API for Audio Routing on mobile device 
from dev-b2g mail list since there are no much responses.
And the content as below is the original mail content from Randy Lin.

-

Hi All,
Recently, we have several implementation which related to the audio routing.
1. Feature request:
[Bug 854753] [FMRadio][User Story] Implement the FM Radio SpeakerOn function
2. add ConnectSco(), DisconnectSco() DOM API on bluetooth , 
landed:https://bugzilla.mozilla.org/show_bug.cgi?id=830213
3. telephony has speakerEnabled API for forcing voice sound from receiver to 
speaker
4. headphone switch event on AudioChannelManager

For the design of cellphone, the audio routing should be considered in system 
level.

Q: Is it possible for b2g to have a routing manager which be responsible to 
manage the device's routing stuff, such as
1. Provide audio path switch API
2. Broadcast routing change event.
3. Handle the application switch case, i.e one application want speaker on with 
headphone pluged-in, switch to another one, but there is no option for users to 
switch back to headphone. this object may need to tracking the application 
usage and recover it.

Randy

- Original Message -
From: "Randy Lin" 
To: "Alive Kuo" 
Cc: dev-b2g@lists.mozilla.org
Sent: 2013年5月13日 星期一 18:28:06
Subject: Re: [b2g] [B2G] Audio path routing

For the API level, we may have an API like this setSpeakerOn(bool en) and 
isSpeakerOn
The application switch case may be complicated because...with headphone 
pluged-in case and playback on speaker:
1. app A use content channel and playing on speaker, another app B use normal, 
should output on speaker or headphone? I prefer speaker. 
2. app A use content/normal and playing on speaker, another app B use higher 
channel than before, like dialer, which output path do we want to have? 
receiver? speaker? *headphone? After ended the app B with higher channel, the 
audio sound can back output on speaker.

==
3. Handle the application switch case, i.e one application want speaker on with 
headphone pluged-in, switch to another one, but there is no option for users to 
switch back to headphone. this object may need to tracking the application 
usage and recover it. 



If you have a speakerOn function I assume that you will also have a speakerOff 
function. 
Then in those app who wants to control the state of speaker, 
they should listen to 'visibilitychange' event to know the 
foreground/background state change(application switch you mean), 
and then according to that, enable or disable speaker. 


The only thing I wonder: there may exist one race condition, if App A is 
brought to background after App B is brought to foreground. 
When that happens, the speaker(I guess it's global?) will be disabled by App A 
when it gets notified it's now background after App A enables 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] branch of b2g that tracks Jelly Bean 4.1.2 ?

[Marco Chen]

Hi,

Currently we have a bug for tracking JB4.2 as below which is initiated by 
Michael Wu.

Bug 784227 - (gonk-jb) JB Gonk Support (Android 4.2)

Sincerely yours.

- Original Message -
From: "Jeremy Reeve" 
To: dev-b2g@lists.mozilla.org
Sent: 2013年5月10日 星期五 22:48:18
Subject: [b2g] branch of b2g that tracks Jelly Bean 4.1.2 ?



Hi there,

Is there a branch of b2g source that is tracking Jelly Bean 4.1.2?

What is master tracking?

Regards...Jeremy
___
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] [Media] The media filter between Gaia - music app and Gecko - nsMediaSniffer & nsExternalHelperAppService

[Marco Chen]

Hi,

After discussing with Paul, we found there is no Web API for exposing 
functionality of nsMediaSniffer.
Currently,
  1. Music app got blobs from Device Storage, which will get MimeType from 
blob.type by GetTypeFromExtension() & GetTypeFromExtras() in 
nsExternalHelperAppService.cpp.
  2. Music app performed it's own filter algorithem.
  3. If 2 is failed, then call audio.canPlayType(blob.type). (This only checks 
whether the mimetype can be accepted by which decoder)
  4 If 3 is failed, then try to play then listen "canplay" event.

So in order to keep more robust filter by music app, 2 is a necessary step to 
be performed by Gaia.
Then I think we should keep synchronization of filter algorithm between Gecko & 
Gaia.

Paul fired bug 868333 to discuss this, if you are interesting please join it.
Of couse, I added Dominic into cc list already.

Thanks,
Sincerely yours.
- Original Message -
From: "Dominic Kuo" 
To: "Marco Chen" 
Cc: "Paul Adenot" , "dev-b2g" 
Sent: Monday, May 6, 2013 5:39:08 PM
Subject: Re: [b2g] [Media] The media filter between Gaia - music app and Gecko 
- nsMediaSniffer & nsExternalHelperAppService

Marco,

> 2. error handling ui is a good choice.
>   Marco: This is a good following item too. May I know the bug number about 
> this?

We don't have a bug filed yet cause currently we think the unplayable audio 
files
shouldn't be listed in music app, and the error handling ui needs new localized
strings so we probably cannot have it in v1.0.1, v1.1 is possible I think. But 
we
still need UX to comment on this.

> step a. To find signatures which is mapped to some media file spec by music 
> app itself.
> step b. If a is failed then using audio.canPlayType() to judge.
> step c. If b is still failed then try set up audio tag and wait "canplay" 
> event. (this will really create a decoder)

>   What I want to clarify here is focused on step a & b not step c. One role 
> in audio.canPlayType() is nsMediaSniffer and 
>   it did the same thing with what Music app did on step a. Also 
> audio.canPlayType() doesn't really create a decoder and try to decode it.

It's my misunderstanding on "audio.canPlayType()" and "canplay" event, sorry 
about that.
I was talking about the canplay event.

Actually works in step a is to parse the metadata of the various formats, if we
can't recognize the metadata, then we will try to test it with step b and step 
c,
because the metadata parser doesn't cover all the supported formats and the 
files
that with unparseable metadata might be still playable.

So if audio.canPlayType() does the same work with step a and reports the trusty
supported formats, then it would be nice to move step b before step a since we
don't have to duplicate some works, and the metadata parser can concentrate on
the parsing works.

But what's the correct way to judge the the return string of 
audio.canPlayType()?
I have looked on https://developer.mozilla.org/en-US/docs/DOM/HTMLMediaElement
and the canPlayType section says there will be three kinds of the strings:

1. probably
2. maybe
3. empty string

>From these three words I can only tell that "empty string" is unplayable for 
>sure,
but for "probably" and "maybe", it might still be unplayable so we will get 
errors
when we try to play files with an  tag? or we still need step c to 
confirm?

Thanks,
Dominic

- Original Message -
From: "Marco Chen" 
To: "Dominic Kuo" 
Cc: "Paul Adenot" , "dev-b2g" 
Sent: Monday, May 6, 2013 12:12:39 PM
Subject: Re: [b2g] [Media] The media filter between Gaia - music app and Gecko 
- nsMediaSniffer & nsExternalHelperAppService

Hi Dominic,

Thanks for your reply and I split your reply into separate items then continue 
to discuss them.

1. About syncing between DeviceStorage.properties, nsMediaSniffer and 
nsExternalHelperAppService.

  Marco: Good suggestion and we already tried to discuss it on Bug 859711. 
Welcome to join there.

2. error handling ui is a good choice.

  Marco: This is a good following item too. May I know the bug number about 
this?


3. About filtering whether audio file can be playable or not?

  Marco: I tried to trace the filtering flow of Music app and it will be
step a. To find signatures which is mapped to some media file spec by music 
app itself.
step b. If a is failed then using audio.canPlayType() to judge.
step c. If b is still failed then try set up audio tag and wait "canplay" 
event. (this will really create a decoder)

What I want to clarify here is focused on step a & b not step c. One role 
in audio.canPlayType() is nsMediaSniffer and 
it did the same thing with what Music app did on step a. Also 
audio.canPlayType() doesn't really create a decoder 

Re: [b2g] [Media] The media filter between Gaia - music app and Gecko - nsMediaSniffer & nsExternalHelperAppService

[Marco Chen]

Hi Dominic,

Thanks for your reply and I split your reply into separate items then continue 
to discuss them.

1. About syncing between DeviceStorage.properties, nsMediaSniffer and 
nsExternalHelperAppService.

  Marco: Good suggestion and we already tried to discuss it on Bug 859711. 
Welcome to join there.

2. error handling ui is a good choice.

  Marco: This is a good following item too. May I know the bug number about 
this?


3. About filtering whether audio file can be playable or not?

  Marco: I tried to trace the filtering flow of Music app and it will be
step a. To find signatures which is mapped to some media file spec by music 
app itself.
step b. If a is failed then using audio.canPlayType() to judge.
step c. If b is still failed then try set up audio tag and wait "canplay" 
event. (this will really create a decoder)

What I want to clarify here is focused on step a & b not step c. One role 
in audio.canPlayType() is nsMediaSniffer and 
it did the same thing with what Music app did on step a. Also 
audio.canPlayType() doesn't really create a decoder and try to decode it.

So if there is no performance issue between step a & b 
3-Q:May I know is there any other reason we need to duplicate step b as 
step a and do it again by Music app?

Thanks,
Sincerely yours.

- Original Message -
From: "Dominic Kuo" 
To: "Marco Chen" 
Cc: "Paul Adenot" , "dev-b2g" 
Sent: Friday, May 3, 2013 8:28:46 PM
Subject: Re: [b2g] [Media] The media filter between Gaia - music app and Gecko 
- nsMediaSniffer & nsExternalHelperAppService

Hi Marco,

I think before synchronizing the supported formats in Gaia and Gecko, maybe 
Gecko can 
first sync with DeviceStorage.properties, nsMediaSniffer and 
nsExternalHelperAppService.

Music app uses MediaDB which integrates the DeviceStorage API and the IndexedDB 
API, 
and DeviceStorage will return files to be parsed with metadata parser in Music 
app. 
Because DeviceStorage returns formats base on DeviceStorage.properties, if we 
already 
know some formats are not supported in Gecko, we shouldn't pass them to the 
metadata 
parser, also MediaDB will not record them and not to mention they will not be 
listed 
in Music app. And for the known supported formats, nsExternalHelperAppService 
should 
not block them, right?

If we filter out the unsupported formats with the first step, it's still 
possible that 
some supported formats/containers with unsupported encodings will be recorded 
in MediaDB,
and when Music app tries to play them, we might still encounter the error of 
"Warning: HTTP "Content-Type" of "audio/xxx" is not supported."

But does using only the logic of audio.canPlayType() to judge files can 
playable or not 
solve this problem? I guess probably, but the metadata parsing time will take 
even longer 
because we have to try to decode every files before we parse the metadata, I am 
not sure 
how long it takes to decode one audio file, but certainly it saves time if we 
parse files
without decoding them first.

I am thinking that maybe error handling ui is a good choice if we cannot 
guarantee the 
so-called "audio" files listed in Music app can be playable or not.

Cheers,
Dominic

- Original Message -
From: "Marco Chen" 
To: "dev-b2g" 
Cc: "Paul Adenot" 
Sent: Friday, May 3, 2013 6:46:00 PM
Subject: [b2g] [Media] The media filter between Gaia - music app and Gecko - 
nsMediaSniffer & nsExternalHelperAppService

Hi all,

Even this topic seems to be related to media (dev-media) but according it also 
related to Gaia and b2g I post it to dev-b2g first.

Issue:
  Currently, we met a bug about some files which can be listed by Music app but 
can't play by Gecko.
  The main reason is that there are two media sniffer mechanism performed by 
Gaia and Gecko separately. 

Detail:
  Gaia: Music app used media sniffer mechanism from metadata.js which will try 
to parse metadata by itself in first.
If first step is failed then fall into Gecko's mechanism 
(audio.canPlayType())
  Gecko:nsMediaSniffer implemented metadata parsing for some media type too.
If nsMediaSniffer is failed then check into 
nsExternalHelperAppService's mimetype entries.

  So if Gaia's metadata.js is implemented with different way then Gecko's then 
issue mentioned by this mail will be occurred.

Discussion Item:
  Do we really need Gaia to do filter by itself or just to use Gecko's 
mechanism (audio.canPlayType()) is enough?
  Then this way can avoid the in-consistent filter capability between Gaia & 
Gecko.

Thanks,
Sincerely yours
-
Marco Chen
System Engineer in Firefox OS
Mozilla Taiwan

Tel: +886-2-87861100 # 352
mail: mc...@mozilla.com

___
dev-b2g mailing list
dev-b2g@lists.moz

[b2g] [Media] The media filter between Gaia - music app and Gecko - nsMediaSniffer & nsExternalHelperAppService

[Marco Chen]

Hi all,

Even this topic seems to be related to media (dev-media) but according it also 
related to Gaia and b2g I post it to dev-b2g first.

Issue:
  Currently, we met a bug about some files which can be listed by Music app but 
can't play by Gecko.
  The main reason is that there are two media sniffer mechanism performed by 
Gaia and Gecko separately. 

Detail:
  Gaia: Music app used media sniffer mechanism from metadata.js which will try 
to parse metadata by itself in first.
If first step is failed then fall into Gecko's mechanism 
(audio.canPlayType())
  Gecko:nsMediaSniffer implemented metadata parsing for some media type too.
If nsMediaSniffer is failed then check into 
nsExternalHelperAppService's mimetype entries.

  So if Gaia's metadata.js is implemented with different way then Gecko's then 
issue mentioned by this mail will be occurred.

Discussion Item:
  Do we really need Gaia to do filter by itself or just to use Gecko's 
mechanism (audio.canPlayType()) is enough?
  Then this way can avoid the in-consistent filter capability between Gaia & 
Gecko.

Thanks,
Sincerely yours
-----
Marco Chen
System Engineer in Firefox OS
Mozilla Taiwan

Tel: +886-2-87861100 # 352
mail: mc...@mozilla.com

___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

Re: [b2g] error "./build.sh -j1"

[Marco Chen]

Hi Lap,

It seems that there are two modules defined as the same name.
From unagi build tree, there is no folder - "hardware/qcom/gps/libloc_api".
So you can try to remove it.

Sincerely yours.

- Original Message -
From: "lap" 
To: dev-b2g@lists.mozilla.org
Sent: Tuesday, April 9, 2013 12:40:39 AM
Subject: Re: [b2g] error "./build.sh -j1"

On 2013年04月08日 23:20, Dave Hylands wrote:
> Hi lap,
>
> - Original Message -
>> From: "lap" 
>> To: dev-b2g@lists.mozilla.org
>> Sent: Monday, April 8, 2013 7:09:28 AM
>> Subject: Re: [b2g] error "./build.sh -j1"
>>
>> On 2013?04?07? 00:00, lap wrote:
>>> Hey guys
>>>
>>> when i ran "./build.sh -j1" , i got this error message.
>>>
>>> build/core/base_rules.mk:170: ***
>>> hardware/qcom/gps/loc_api/libloc_api_50001:
>>> MODULE.TARGET.SHARED_LIBRARIES.gps.msm7627a already defined by
>>> hardware/qcom/gps/libloc_api?stop
>>>
>>> can someone help me? thanks:-D
> Near the end of your log I see:
>
> Hardware/qcom/gps/loc_api/Android.mk:26:hardware/qcom/gps/loc_api/libloc_api-rpc/Android.mk:
>  no file or directory
> Hardware/qcom/gps/loc_api/Android.mk:26:hardware/qcom/gps/loc_api/libloc_api/Android.mk:
>  no file or directory
>
> In my unagi tree, those files exist (i.e. came from git). Do they exist for 
> you? perhaps you need to check your repository?
>
> Dave Hylands
Hi Dave

yeah, you are right, and i solved this missing files's problem , but it 
still said that

build/core/base_rules.mk:170: *** hardware/qcom/gps/loc_api/libloc_api: 
MODULE.TARGET.SHARED_LIBRARIES.gps.msm7627a already defined by 
hardware/qcom/gps/libloc_api。 stop.

And why this happen? how can i solve it?

lap

___
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] B2G - stuck at boot animation

[Marco Chen]

Hi,

Did you install gaia too?

Sincerely yours.

- Original Message -
From: "samir mehta" 
To: dev-b2g@lists.mozilla.org
Sent: Monday, April 1, 2013 3:32:27 PM
Subject: [b2g] B2G - stuck at boot animation

Hi,

I'm trying to port B2G to my hardware running Android ICS, I have
tried compiling the code for galaxyS2/crespo(nexus 4) and just pushing
the B2G binaries to my hardware start the B2G via the shell. But the
B2G is stuck at the bootanimation. Could you please help?

Log snippet:
root@android:/ # /system/b2g/b2g
1364559274051   Marionette  INFOMarionetteComponent loaded
1364559274059   Marionette  INFOmarionette enabled
xport_open(218) xport_open[58]: max_rx_len=0
xport_lookup(310) Lookup: type=228 instance=1
reader_thread(148) reader_thread: wakeup_pipe[0]=1 ch=a
xport_lookup(310) Lookup: type=228 instance=1
xport_lookup(310) Lookup: type=228 instance=1
xport_open(218) xport_open[62]: max_rx_len=536
xport_lookup(310) Lookup: type=228 instance=1
reader_thread(148) reader_thread: wakeup_pipe[0]=1 ch=a
xport_lookup(310) Lookup: type=228 instance=1
encode_and_send(225) QMI_CCI_TX: cntl_flag - 00, txn_id - 0001, msg_id
- 0001, msg_len - 000e
xport_send(261) Sent[62]: 21 bytes to port 768
reader_thread(104) reader_thread: Received 543 bytes from 62
qmi_cci_xport_recv(404) QMI_CCI_RX: cntl_flag - 02, txn_id - 0001,
msg_id - 0001, msg_len - 0218
reader_thread(148) reader_thread: wakeup_pipe[0]=1 ch=d
reader_thread(153) reader_thread exiting
xport_close(286) Close[62]
reader_thread(148) reader_thread: wakeup_pipe[0]=1 ch=d
reader_thread(153) reader_thread exiting
xport_close(286) Close[58]
xport_open(218) xport_open[58]: max_rx_len=0
xport_lookup(310) Lookup: type=228 instance=1
reader_thread(148) reader_thread: wakeup_pipe[0]=1 ch=a
xport_lookup(310) Lookup: type=228 instance=1
xport_lookup(310) Lookup: type=228 instance=1
xport_open(218) xport_open[62]: max_rx_len=536
xport_lookup(310) Lookup: type=228 instance=1
reader_thread(148) reader_thread: wakeup_pipe[0]=1 ch=a
xport_lookup(310) Lookup: type=228 instance=1
encode_and_send(225) QMI_CCI_TX: cntl_flag - 00, txn_id - 0001, msg_id
- 0001, msg_len - 000e
xport_send(261) Sent[62]: 21 bytes to port 768
reader_thread(104) reader_thread: Received 543 bytes from 62
qmi_cci_xport_recv(404) QMI_CCI_RX: cntl_flag - 02, txn_id - 0001,
msg_id - 0001, msg_len - 0218
reader_thread(148) reader_thread: wakeup_pipe[0]=1 ch=d
reader_thread(153) reader_thread exiting
xport_close(286) Close[62]
reader_thread(148) reader_thread: wakeup_pipe[0]=1 ch=d
reader_thread(153) reader_thread exiting
xport_close(286) Close[58]
xport_open(218) xport_open[58]: max_rx_len=0
xport_lookup(310) Lookup: type=228 instance=1
reader_thread(148) reader_thread: wakeup_pipe[0]=1 ch=a
xport_lookup(310) Lookup: type=228 instance=1
xport_lookup(310) Lookup: type=228 instance=1
xport_open(218) xport_open[62]: max_rx_len=536
xport_lookup(310) Lookup: type=228 instance=1
xport_lookup(310) Lookup: type=228 instance=1
encode_and_send(225) QMI_CCI_TX: cntl_flag - 00, txn_id - 0001, msg_id
- 0001, msg_len - 000e
xport_send(261) Sent[62]: 21 bytes to port 768
reader_thread(148) reader_thread: wakeup_pipe[0]=1 ch=a
reader_thread(104) reader_thread: Received 543 bytes from 62
qmi_cci_xport_recv(404) QMI_CCI_RX: cntl_flag - 02, txn_id - 0001,
msg_id - 0001, msg_len - 0218
reader_thread(148) reader_thread: wakeup_pipe[0]=1 ch=d
reader_thread(153) reader_thread exiting
xport_close(286) Close[62]
reader_thread(148) reader_thread: wakeup_pipe[0]=1 ch=d
reader_thread(153) reader_thread exiting
xport_close(286) Close[58]
xport_open(218) xport_open[58]: max_rx_len=0
xport_lookup(310) Lookup: type=228 instance=1
reader_thread(148) reader_thread: wakeup_pipe[0]=1 ch=a
xport_lookup(310) Lookup: type=228 instance=1
xport_lookup(310) Lookup: type=228 instance=1
xport_open(218) xport_open[62]: max_rx_len=536
xport_lookup(310) Lookup: type=228 instance=1
reader_thread(148) reader_thread: wakeup_pipe[0]=1 ch=a
xport_lookup(310) Lookup: type=228 instance=1
encode_and_send(225) QMI_CCI_TX: cntl_flag - 00, txn_id - 0001, msg_id
- 0001, msg_len - 000e
xport_send(261) Sent[62]: 21 bytes to port 768
reader_thread(104) reader_thread: Received 543 bytes from 62
qmi_cci_xport_recv(404) QMI_CCI_RX: cntl_flag - 02, txn_id - 0001,
msg_id - 0001, msg_len - 0218
reader_thread(148) reader_thread: wakeup_pipe[0]=1 ch=d
reader_thread(153) reader_thread exiting
xport_close(286) Close[62]
reader_thread(148) reader_thread: wakeup_pipe[0]=1 ch=d
reader_thread(153) reader_thread exiting
xport_close(286) Close[58]
xport_open(218) xport_open[58]: max_rx_len=0
xport_lookup(310) Lookup: type=228 instance=1
reader_thread(148) reader_thread: wakeup_pipe[0]=1 ch=a
xport_lookup(310) Lookup: type=228 instance=1
xport_lookup(310) Lookup: type=228 instance=1
xport_open(218) xport_open[62]: max_rx_len=536
xport_lookup(310) Lookup: type=228 instance=1
reader_thread(148) reader_thread: wakeup_pipe[0]=1 ch=a
xport_lookup(310) Lookup: type

Re: [b2g] "Cannot allocate memory" linker error building with GECKO_PATH=m-c

[Marco Chen]

Hi,

Maybe you can try the way from link as below.
http://code.google.com/p/android/issues/detail?id=42913

That seems to be similar issue with yours.

Sincerely yours.

- Original Message -
From: "Jonathan Watt" 
To: mozilla-dev-...@lists.mozilla.org
Cc: "Dave Hylands" 
Sent: 2013年3月25日 星期一 23:50:14
Subject: Re: [b2g] "Cannot allocate memory" linker error building with  
GECKO_PATH=m-c

Hi Dave,

On 25/03/2013 15:47, Dave Hylands wrote:
> Hi Jonathan,
>
> What does uname -a show? (on your build machine)

It shows:

Darwin JonathanWatts-MacBook-Pro.local 12.3.0 Darwin Kernel Version 12.3.0: Sun 
Jan  6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64 x86_64

___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

[b2g] [Device Storage] How does App show pictures which recived or created by itself?

[Marco Chen]

Hi all,

In the case of Line app in Android, Line can show up the pictures received or 
created by itself to user.
And Line search these pictures on a specific folders.

As I know that Gaia can only call DeviceStorage to save files but can't 
indicate the path.
If an app want to do this, it can't rely on a specific folders.
So how do app achieve this feature? ex: filter by name or ...

Thanks.
Sincerely yours. 

-----
Marco Chen
System Engineer in Firefox OS
Mozilla Taiwan

Tel: +886-2-87861100 # 352
mail: mc...@mozilla.com

___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

Re: [b2g] about “image too large”

[Marco Chen]

Hi,

Another way is to use "dd" command in adb shell,
but you need to check your image 
  a. doesn't larger then system partition size.
  b. doesn't a sparse image.

1. Boot into Android.
2. adb shell
3. mount (find out your system is mounted in which partition. Ex: mmcblk0p20 or 
mtdblock5)
4. adb push system.img /sdcard
5. dd if=/sdcard/system.img of=/dev/block/XXX (depend on step 3).

Done.
Sincerely yours.

- Original Message -
From: "lap song" 
To: dev-b2g@lists.mozilla.org
Sent: 2013年3月17日 星期日 10:19:51
Subject: [b2g] about “image too large”

hey guys,

i want to ask why my device already be rooted, but still can't not flash.
i want to know how can i solve this problem.

sincerely yours
___
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] Some diagrams of Firefox OS

[Marco Chen]

It is very helpful to me.
Thanks for the great sharing.

Sincerely yours.

- Original Message -
From: "Sotaro Ikeda" 
To: "Eric Shepherd" 
Cc: mozilla-dev-...@lists.mozilla.org
Sent: 2013年3月13日 星期三 21:13:52
Subject: Re: [b2g] Some diagrams of Firefox OS


>> Can I make use of these in the documentation on MDN as needed/useful?
>
>No problem to use the diagrams on MDN.

I wrote the diagrams with visio 2013 professional. Original files are also 
pushed to there. There is no problem to modify and reuse them for your 
necessity.


Regards,
Sotaro

- Original Message -
From: "Sotaro Ikeda" 
To: "Eric Shepherd" 
Cc: mozilla-dev-...@lists.mozilla.org
Sent: Wednesday, March 13, 2013 9:09:52 AM
Subject: Re: [b2g] Some diagrams of Firefox OS


> Can I make use of these in the documentation on MDN as needed/useful?

No problem to use the diagrams on MDN.

Regards,
Sotaro

- Original Message -
From: "Eric Shepherd" 
To: mozilla-dev-...@lists.mozilla.org
Sent: Wednesday, March 13, 2013 8:40:07 AM
Subject: Re: [b2g] Some diagrams of Firefox OS

On 2013-03-12 15:23:29 +, Sotaro Ikeda said:

> I wrote some diagrams of Firefox OS around camera and codecs. I wrote 
> them to complement my bad memory and wrote them from my point of view 
> and necessity. Though, they could be useful for others.
> 
> https://github.com/sotaroikeda/firefox-diagrams/wiki/Firefox-Diagrams
> https://github.com/sotaroikeda/firefox-diagrams

Can I make use of these in the documentation on MDN as needed/useful?

Thanks,

-- 
Eric Shepherd
Developer Documentation Lead
Mozilla
Blog: http://www.bitstampede.com/
Twitter: @sheppy

___
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] about the "./build.sh -j1"

[Marco Chen]

Hi,

You can try to put it into "out/target/product/n880e/obj/lib".

Sincerely yours.

- Original Message -
From: "lap" 
To: dev-b2g@lists.mozilla.org
Sent: 2013年3月12日 星期二 23:44:02
Subject: [b2g] about the "./build.sh -j1"

can somebody tell me how to fix it?
i am running "./build.sh -j1",and got this

Make:*** no rule can create 
"out/target/product/n880e/obj/SHARED_LIBRARIES/libstagefright_intermediates/LINKED/libstagefright.so"
 
need to target "out/target/product/n880e/obj/STATIC_ 
LIBRARIES/libstagefright_chromium_http_intermediates 
/libstagefright_chromium_http.a"? Stops.

i don't have this "libstagefright_chromium_http.a' but i have the 
"libstagefright.so",what should i do now?

i have try to put the "libstagefright.so" into the 
"out/target/product/n880e/obj/SHARED_LIBRARIES/libstagefright_intermediates/LINKED",
 
but it not work

please give me a faver. Thank you so much.
___
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.sh [error message]

[Marco Chen]

Hi,

It indicated that you have two module name called libjpeg in you build tree.
One is external/qemu/distrib/jpeg-6b and the other is external/jpeg.
You can choose one to disable.

Sincerely yours.

- Original Message -
From: "lap" 
To: dev-b2g@lists.mozilla.org
Sent: Tuesday, March 12, 2013 6:58:34 PM
Subject: [b2g] ./build.sh [error message]

hey guys, can somebody tell me what's going on with this error message? 
i am going to build the B2G


*** external/qemu/distrib/jpeg-6b: 
MODULE.TARGET.SHARED_LIBRARIES.libjpeg already defined by external/jpeg? 
stop.
___
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] libsystem_server.so required on compiling B2G for u8815 (Huawei ascend g300)

[Marco Chen]

Hi Vadim,

It seems that folder - build from link as below added libsystem_server module 
into OPTIONAL_USER_MODULES.
https://github.com/mozilla-b2g/platform_build

You can try to move libsysterm_server from OPTIONAL_USER_MODULES into 
GRANDFATHERED_USER_MODULES in build/core/user_tags.mk.

Sincerely yours.

- Original Message -
From: "Vadim Rutkovsky" 
To: dev-b2g@lists.mozilla.org
Sent: Monday, February 25, 2013 10:19:14 PM
Subject: [b2g] libsystem_server.so required on compiling B2G for u8815 (Huawei 
ascend g300)

Hi all,

I'm trying to compile B2G for Huawei Ascend G300 (codename u8815), but I
get the following error on compiling gecko:

make: *** No rule to make target
`out/target/product/u8815/obj/lib/libsystem_server.so', needed by
`out/target/product/u8815/obj/SHARED_LIBRARIES/libanalogradiobroadcasting_intermediates/LINKED/libanalogradiobroadcasting.so'.

I presume this is related to FM Radio functions - is there any way to fix
this / disable this support?
I use a modified branch for B2G manifest - see
https://github.com/Dazzozo/B2G. I'll post complete build logs on request.

Thanks in advance,
  Vadim
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

[b2g] [Audio] Audio Competing Policy

[Marco Chen]

Dear all,

This mail is used to raise our proposal on bug as below.

Bug 805333 - Need a Policy & Mechanism for Audio Competing & Control 

And it may block at least 4 bugs which already listed in above link.
Give an two example for what we want to solve in this proposal.

Ex: 1. a. Music player is on playing.
   b. Phone call is coming.
   c. Music player is stopped.
2. a. Game with music is on playing
   b. screen is off due to timeout or fall into background by home key.
   c. The music from game is stopped.

Please refer to link as below for more detail.
https://docs.google.com/open?id=0BxKpB0y8NZSHYjhJeUtQUkRQVUU
Also welcome and appreciate your feedback & discussion in advance.
Sincerely yours.

-----
Marco Chen
System Engineer in Firefox OS
Mozilla Taiwan

Tel: +886-2-87861100 # 352
mail: mc...@mozilla.com

___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

Re: [b2g] Getting build failure for B2G ARM emulator build

[Marco Chen]

It shows that run-mozilla.sh was missing on your folder of xulrunner-sdk.
I met before and I tried to

1. Delete entire Gaia folder
2. repo sync Gaia
3. ./build.sh -j16

Then you will find xulrunner-sdk is updated to newest one and built 
successfully.

Sincerely yours.

- Original Message -
From: "Pramod Korti" 
To: mozilla-dev-...@lists.mozilla.org
Sent: Wednesday, October 17, 2012 4:53:35 PM
Subject: [b2g] Getting build failure for B2G ARM emulator build

Hi,

I am trying to build b2g emulator for ARM.
Followed guide in below link:

https://developer.mozilla.org/en-US/docs/Mozilla/Boot_to_Gecko/Preparing_for_your_first_B2G_build#Configuring_to_build_an_emulator

when i do build ./build.sh -j1, build is failing with below error


/bin/bash: ./xulrunner-sdk/bin/run-mozilla.sh: No such file or directory
make[1]: *** [applications-data] Error 127
make[1]: Leaving directory `/u/prakot/emulator/B2G/gaia'
make: *** [gaia/profile.tar.gz] Error 2

real11m57.776s
user8m43.420s
sys 1m25.890s

> Build failed! <

can i get some help here, couldn't figure aout error 127 and Error2
___
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] Alternative solution for running b2g on LG optimus L5

[Marco Chen]

Dear Rubin,

You can remove the "app_process" in folder of /system/bin.
This is a temporarily solution.

Sincerely yours. 

- Original Message -
From: "bin guo" 
To: "dev-b2g" 
Sent: Friday, October 12, 2012 10:43:03 AM
Subject: [b2g] Alternative solution for running b2g on LG optimus L5

Dear all,
I have built LG optimus L5 image from source code, and flash system.img to
my phone. But because LG optimus L5 has security check, It show "Security
Error" when booting.
Then I decided to change the method. I push b2g binaries and webapps to
system and data partitions respectively. Then started b2g process through
adb tool. Now the problem comes. Android UI and b2g process are running at
the same time. They both response to the touch and key event. The screen
show Android UI and firefox os UI alternately. I have tried to stop Android
UI process, but the screen froze when android UI process stoped.
Who can help me to make b2g running on my L5 phone?

BR,
rubin
___
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