hi all now a day i am working air gesture app for android phone can any one suggest me for source code ....
On Tue, Nov 25, 2014 at 7:22 PM, <[email protected]> wrote: > Send dev-b2g mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.mozilla.org/listinfo/dev-b2g > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of dev-b2g digest..." > > Today's Topics: > > 1. Re: Flame completely dead (Andr? Jaenisch) > 2. Re: Is there any side effect holding a long lived > AudioContext? (Randy Lin) > 3. Re: Is there any side effect holding a long lived > AudioContext? (Tim Chien) > 4. Updates to "Firefox OS Development" section of MDN (Chris Mills) > 5. Fwd: Device Name and Codenames - ZTE Open 2 (Chris Mills) > 6. Symphony GoFox F15 page on MDN (Chris Mills) > 7. Re: Symphony GoFox F15 page on MDN (Aniruddha Adhikary) > 8. Re: Symphony GoFox F15 page on MDN (Chris Mills) > > > ---------- Forwarded message ---------- > From: "André Jaenisch" <[email protected]> > To: [email protected] > Cc: > Date: Tue, 25 Nov 2014 01:06:29 +0100 > Subject: Re: [b2g] Flame completely dead > Hello, > > I had a similiar behaviour on my Alcatel OneTouch Fire and contacted my > carrier > for repair. > However, as I checked it via Computer (lsusb and adb devices) it was > recognised. > Have you tried that? > That is, does it respond to your computer? > > Best regards, > > > André Jaenisch > > Tucker McKnight <[email protected]> schrieb am So, 23.Nov.14 > 22:22: > > A couple of days ago, my Flame turned off, and it won't turn on. I can't > get > > a boot screen or anything. > > > > It has done this a couple of times in the past; both times I took the > > battery out, then put the battery back in, and it was fine. This time > that > > didn't work. I've tried plugging in the USB cable, but there is no > > indication that it is charging. It also doesn't show up with adb devices > or > > fastboot devices. Holding volume up + power, or volume down + power > doesn't > > do anything, either. > > > > I'd had 2.0-prelease on it for a few weeks, and I hadn't recently changed > > anything about it. I'm hoping it's just the battery. Does anyone have any > > ideas as to what could be going wrong, or what I could do about it? > > > > _______________________________________________ > > dev-b2g mailing list > > [email protected] > > https://lists.mozilla.org/listinfo/dev-b2g > > > > ---------- Forwarded message ---------- > From: Randy Lin <[email protected]> > To: Tim Chien <[email protected]> > Cc: [email protected] > Date: Mon, 24 Nov 2014 21:59:22 -0800 (PST) > Subject: Re: [b2g] Is there any side effect holding a long lived > AudioContext? > Hi Tim. > That may cause power consumption problem on b2g device. > You can refer to this bug:1079810. > > ------------------------------------- > -rlin > > ----- 原始郵件 ----- > 寄件者: "Tim Chien" <[email protected]> > 收件者: [email protected] > 寄件備份: 2014 11 月 24 星期一 下午 9:49:36 > 主旨: [b2g] Is there any side effect holding a long lived AudioContext? > > Hi, > > I didn't find any documentation so that I figured I should ask. So in > bug 1103574 I changed the Keyboard app so that it would start using > Web Audio API instead of multiple <audio> to play that clicker sound, > but doing so I would hold an AudioContext instance (and two > AudioBuffer instances) whenever the clicker sound is enabled (even > when keyboard is not visible). Does that poses any side effect on B2G > or in general? > > Also, there are posts online saying AudioNodes are only GC'd when they > are disconnect()'d, I doubt that is the case (since the node is not > reachable from the context) but it seems to me there are no obvious > way to confirm that. Should I always disconnect the node after calling > start(0)? What's the definite way to find out questions like this? > > Thanks, > > -- > Tim Guan-tin Chien, Engineering Manager and Front-end Lead, Firefox > OS, Mozilla Corp. (Taiwan) > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g > > > > ---------- Forwarded message ---------- > From: Tim Chien <[email protected]> > To: Randy Lin <[email protected]> > Cc: [email protected] > Date: Tue, 25 Nov 2014 18:10:43 +0800 > Subject: Re: [b2g] Is there any side effect holding a long lived > AudioContext? > Thanks Randy, I will file a bug to fix the current implementation. > > On Tue, Nov 25, 2014 at 1:59 PM, Randy Lin <[email protected]> wrote: > > Hi Tim. > > That may cause power consumption problem on b2g device. > > You can refer to this bug:1079810. > > > > ------------------------------------- > > -rlin > > > > ----- 原始郵件 ----- > > 寄件者: "Tim Chien" <[email protected]> > > 收件者: [email protected] > > 寄件備份: 2014 11 月 24 星期一 下午 9:49:36 > > 主旨: [b2g] Is there any side effect holding a long lived AudioContext? > > > > Hi, > > > > I didn't find any documentation so that I figured I should ask. So in > > bug 1103574 I changed the Keyboard app so that it would start using > > Web Audio API instead of multiple <audio> to play that clicker sound, > > but doing so I would hold an AudioContext instance (and two > > AudioBuffer instances) whenever the clicker sound is enabled (even > > when keyboard is not visible). Does that poses any side effect on B2G > > or in general? > > > > Also, there are posts online saying AudioNodes are only GC'd when they > > are disconnect()'d, I doubt that is the case (since the node is not > > reachable from the context) but it seems to me there are no obvious > > way to confirm that. Should I always disconnect the node after calling > > start(0)? What's the definite way to find out questions like this? > > > > Thanks, > > > > -- > > Tim Guan-tin Chien, Engineering Manager and Front-end Lead, Firefox > > OS, Mozilla Corp. (Taiwan) > > _______________________________________________ > > dev-b2g mailing list > > [email protected] > > https://lists.mozilla.org/listinfo/dev-b2g > > > > -- > Tim Guan-tin Chien, Engineering Manager and Front-end Lead, Firefox > OS, Mozilla Corp. (Taiwan) > > > > ---------- Forwarded message ---------- > From: Chris Mills <[email protected]> > To: [email protected] > Cc: > Date: Tue, 25 Nov 2014 11:34:06 +0000 > Subject: [b2g] Updates to "Firefox OS Development" section of MDN > Hi all, > > One project I have been working on for a long time is improving the > information we have available on contributing to Firefox OS, the non-Gaia > parts. It has been quite hard to find specific information on this, as: > > 1. A lot of it (such as fixing bugs, helping to implement APIs) is pretty > much the same process as contributing to regular Gecko. > 2. A lot of it (such as porting, Gonk modifications, build distribution) > isn’t really within the realm of stuff a regular Mozilla contributor would > be like to work on. > > To this end, I’ve done the following: > > 1. Added some material to the Developing Firefox OS landing page to give > an idea of what the contribution path should look like: > https://developer.mozilla.org/en-US/Firefox_OS/Developing_Firefox_OS > > 2. Added quite a bit of information to the Gonk landing page: > https://developer.mozilla.org/en-US/Firefox_OS/Platform/Gonk > > 3. Moved the porting guide into the Developing Firefox OS section and > added some more information: > https://developer.mozilla.org/en-US/Firefox_OS/Developing_Firefox_OS/Porting > > 4. Added quite a lot of useful info to the Firefox OS architecture guide: > https://developer.mozilla.org/en-US/Firefox_OS/Platform/Architecture > > Does this information look ok? I’d specifically like comment on 1. and 2. > Does it feel like there’s a lot of things missing? What else would we like > to see covered? > > Best, > > Chris Mills > Senior tech writer || Mozilla > developer.mozilla.org || MDN > [email protected] || @chrisdavidmills > > > > > > > ---------- Forwarded message ---------- > From: Chris Mills <[email protected]> > To: [email protected] > Cc: Ralph Daub <[email protected]> > Date: Tue, 25 Nov 2014 11:53:18 +0000 > Subject: [b2g] Fwd: Device Name and Codenames - ZTE Open 2 > Hi all, > > Does anyone know what device name should be used when building for the ZTE > Open 2/what issues or oddities exist with building for it? > > thanks! > > Chris Mills > Senior tech writer || Mozilla > developer.mozilla.org || MDN > [email protected] || @chrisdavidmills > > > > > Begin forwarded message: > > > > Subject: Re: Device Name and Codenames - ZTE Open 2 > > From: Chris Mills <[email protected]> > > Date: 25 November 2014 11:43:56 GMT > > To: Ralph Daub <[email protected]> > > Cc: [email protected] > > > > Hi Ralph, > > > > This is a good question; I’m not sure what the answer is. > > > > I’ll follow up on this mail separately, and cc some people who are more > likely to be able to help. I agree that this information needs to be > updated for some of the newer phones on the market. > > > > Best, > > > > Chris Mills > > Senior tech writer || Mozilla > > developer.mozilla.org || MDN > > [email protected] || @chrisdavidmills > > > > > > > >> On 25 Nov 2014, at 07:48, Ralph Daub <[email protected]> wrote: > >> > >> Hi, > >> > >> What is the codename of the ZTE Open 2? A user in the SUMO Forums is > looking to build Firefox OS and is asking about it: > >> > >> https://support.mozilla.org/en-US/questions/1032328 > >> > >> I also noticed that the devices page may need to be updated with the > new wave of devices: > >> > >> > https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Phone_specs > >> > >> Thanks in advance for any help or pointing me in the right direction! > >> > >> - Ralph Daub > >> User Success Team > >> Firefox OS Support Coordinator > >> | sumo | facebook | twitter | IRC: ralphdaub #sumo | > >> > >> _______________________________________________ > >> dev-mdc mailing list > >> [email protected] > >> https://lists.mozilla.org/listinfo/dev-mdc > >> MDN contributor guide: http://bit.ly/ContributorGuide > > > > _______________________________________________ > > dev-mdc mailing list > > [email protected] > > https://lists.mozilla.org/listinfo/dev-mdc > > MDN contributor guide: http://bit.ly/ContributorGuide > > > > > ---------- Forwarded message ---------- > From: Chris Mills <[email protected]> > To: [email protected] > Cc: > Date: Tue, 25 Nov 2014 13:09:00 +0000 > Subject: [b2g] Symphony GoFox F15 page on MDN > Hi there, > > I just came across this page on MDN: > > > https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Symphony_GoFox_F15 > > Thanks to the team that wrote it! I just had a couple of requests: > > 1. I gave the page a copy edit and tidied it up a bit. Can someone give it > a read just to make sure it still all makes sense? > 2. The first embedded image in the following section looks corrupted: > https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Symphony_GoFox_F15#Screen_reader_basic_gestures. > Can someone provide me with a fresh version? > > cheers, > > Chris Mills > Senior tech writer || Mozilla > developer.mozilla.org || MDN > [email protected] || @chrisdavidmills > > > > > > > ---------- Forwarded message ---------- > From: Aniruddha Adhikary <[email protected]> > To: Chris Mills <[email protected]> > Cc: [email protected] > Date: Tue, 25 Nov 2014 19:45:45 +0600 > Subject: Re: [b2g] Symphony GoFox F15 page on MDN > Hi Chris, > > I am one of the writers (I actually started this page on MDN) and just > went through the article. It looks good, and it needs some more technical > details. I will be filling in those details soon. The rest makes sense and > looks good. Thanks for the edit Chris! > > I am requesting the original creator of that image on Facebook to provide > you with a fresh copy. > > Cheers! > > On Tue, Nov 25, 2014 at 7:09 PM, Chris Mills <[email protected]> wrote: > >> Hi there, >> >> I just came across this page on MDN: >> >> >> https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Symphony_GoFox_F15 >> >> Thanks to the team that wrote it! I just had a couple of requests: >> >> 1. I gave the page a copy edit and tidied it up a bit. Can someone give >> it a read just to make sure it still all makes sense? >> 2. The first embedded image in the following section looks corrupted: >> https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Symphony_GoFox_F15#Screen_reader_basic_gestures. >> Can someone provide me with a fresh version? >> >> cheers, >> >> Chris Mills >> Senior tech writer || Mozilla >> developer.mozilla.org || MDN >> [email protected] || @chrisdavidmills >> >> >> >> _______________________________________________ >> dev-b2g mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-b2g >> > > > > -- > Aniruddha Adhikary (@tuxboy) > > > ---------- Forwarded message ---------- > From: Chris Mills <[email protected]> > To: Aniruddha Adhikary <[email protected]> > Cc: "[email protected]" <[email protected]> > Date: Tue, 25 Nov 2014 13:51:42 +0000 > Subject: Re: [b2g] Symphony GoFox F15 page on MDN > That’s great - thanks very much! Let me know when you add the rest of the > content, and I’ll give that a copy edit too. > > Chris Mills > Senior tech writer || Mozilla > developer.mozilla.org || MDN > [email protected] || @chrisdavidmills > > > > > On 25 Nov 2014, at 13:45, Aniruddha Adhikary <[email protected]> > wrote: > > > > Hi Chris, > > > > I am one of the writers (I actually started this page on MDN) and just > went through the article. It looks good, and it needs some more technical > details. I will be filling in those details soon. The rest makes sense and > looks good. Thanks for the edit Chris! > > > > I am requesting the original creator of that image on Facebook to > provide you with a fresh copy. > > > > Cheers! > > > > On Tue, Nov 25, 2014 at 7:09 PM, Chris Mills <[email protected]> wrote: > > Hi there, > > > > I just came across this page on MDN: > > > > > https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Symphony_GoFox_F15 > > > > Thanks to the team that wrote it! I just had a couple of requests: > > > > 1. I gave the page a copy edit and tidied it up a bit. Can someone give > it a read just to make sure it still all makes sense? > > 2. The first embedded image in the following section looks corrupted: > https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Symphony_GoFox_F15#Screen_reader_basic_gestures. > Can someone provide me with a fresh version? > > > > cheers, > > > > Chris Mills > > Senior tech writer || Mozilla > > developer.mozilla.org || MDN > > [email protected] || @chrisdavidmills > > > > > > > > _______________________________________________ > > dev-b2g mailing list > > [email protected] > > https://lists.mozilla.org/listinfo/dev-b2g > > > > > > > > -- > > Aniruddha Adhikary (@tuxboy) > > > > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g > >
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
