On Thu, Aug 1, 2013 at 1:06 PM, Clint Talbert ctalb...@mozilla.com wrote:
All that said, this thread is much bigger than one automation bug.
There are several core issues here:
* Continual investigation into intermittent failures as they come up. If we
don't continue prioritizing these fixes,
hi;
To close the loop here, the only person who we found still using Otoro
builds was Kairo, who is returning his Otoro, and getting a replacement
Unagi or Keon phone instead. Therefore, I've filed bug#900846 to stop
generating automated Otoro builds.
If anyone has concerns, or reasons to keep
Thats awesome! Looking forward to see the Doom inspector, that will change my
life :)
Arnau
On Aug 2, 2013, at 12:50 AM, Alexandre poirot poirot.a...@gmail.com
wrote:
Hi,
We recently landed a patch to enable devtools against apps running on
devices
[bug 817580]. That patch enables you to
Hi Jonas,
I will explain pcsc_funcs first and then propose possible solution in current
architecture if we want to use
existing wifi worker.
pcsc stands for Personal Computer/Smartcard Interface.
The main usage of this component(pcsc_funcs.c) is it provide an interface for
No this was a full b2g build
2013/8/1 Ben Kelly bke...@mozilla.com
On Jul 31, 2013, at 5:56 AM, Jan Jongboom janjongb...@gmail.com wrote:
On Wednesday, July 31, 2013 11:32:31 AM UTC+2, Jan Jongboom wrote:
Anyone has any clue what could be the cause? Build of two weeks ago
worked fine...
Can you try to push the busybox binary and use the ping command to make
sure the network connection is available ?
If the ping is failed, check the routing table for the default route.
Many Thanks,
Vincent Chang,
Software Engineer of Mozilla Taiwan
2013/7/24 Shlomi Asaf neo...@gmail.com
My
But after tracing wpa_supplicant code, we found that we cannot retrieve the
notification socket in pcsc_funcs.c.
There is no API to get it and wpa_supplicant neither pass any information
through above APIs for pcsc_func to
retrieve the notification socket.
I already tried to pass UNIX
But iirc, stageright implement Mpeg2Ts for HLS support by AwesomePlayer at
first.
Stagefright can playback local mpeg2ts. I think it is just a side effect of HLS
support. Just simple mpeg2ts can not support seek efficiently.
Current JB support mpeg2ts on RTSP as AMPEG2TSAssembler. It is better
I'm pretty sure the long term plan for Youtube is WebM or Fragmented MP4
over MSE for Chrome/Web. Whether we should wait for that to save us, I
don't know.
Can we know about when youtube is going support youtube live by MSE?
Google already implemented Fragmented MP4 parser since JB.
Sotaro
Sorry, I am a little bit confuse.
We can said that StageFright support MPEG2TS playback, but supporting MPEG2TS
playback in RTSP is one thing, while supporting MPEG2TS playback in HLS is
another one.
I can see no reason that the problem in HLS can be resolved by turning on
MPEG2S playback in
Sorry, I am a little bit confuse.
We can said that StageFright support MPEG2TS playback, but supporting MPEG2TS
playback in RTSP is one thing, while supporting MPEG2TS playback in HLS is
another one.
I can see no reason that the problem in HLS can be resolved by turning on
MPEG2S playback in
How will it work with a virtual box?
On Friday, July 19, 2013, Alex Keybl ake...@mozilla.com wrote:
[please keep any replies on dev.b2g]
Mozilla and the community have been on a roll creating new products and
evolving existing ones. We now release multiple browsers across a multitude
of
Resent with link rather than HTML file:
http://qa-selenium.mv.mozilla.com:8080/job/b2g.unagi.mozril.gaia.master.ui/185/HTML_Report/index.html
Original Message
Subject:08/02/2013 Unagi/v1.2 Moz RIL Automation smoketest report
Date: Fri, 02 Aug 2013 18:52:37 +0100
I do not know js-ctypes enough to be of any help, but I know that you are
unlikely to find any help about that on the dev.b2g news group.
On 07/29/2013 11:30 PM, Kilcheon Kim wrote:
Hi, All,
Actually, I am studying how to port native application(made by C and C++) into
B2G.
Then you should
40 out of 47 tests passed for the 2013-08-02 Unagi v1.2.0 Mozilla RIL
Build. Here are the major issues that prevented the smoketests from passing.
Mozilla RIL Build Smoketest Results:
Daily Smoke Test Logs:
15 matches
Mail list logo