On 09/29/2014 12:27 AM, Fabrice Desré wrote:
One issue is that the android HAL doesn't expose what the device LED
supports - it's really best effort, see
http://androidxref.com/4.4.4_r1/xref/hardware/libhardware/include/hardware/lights.h#92
So I think it would be quite hard to implement this 'col
On Monday, 29 September 2014 06:39:48 UTC+2, Sebastián Enrique Becerra Cancino
wrote:
> Guys, finally I could update to v180 but the only problem that stills is on
> dab log cat, can anyone explain what is Logcat? and how I can know that the
> flash of v180 is correct and there's no problem?
>
Le 29/09/2014 00:28, Dietrich Ayala a écrit :
> While flashing a Flame to the new KK base image, the script exited partway
> through flashing fsg, saying couldn't detect device.
>
> Now the device will not turn on at all. If I remove the battery, then hold
> voldown+sleep and plug in USB, I can
Instead of having a system that manages the LED when there is a notification
must be an API LED available with Javascript. Everyone can use it for make an
app.
An 0-255 RGB values is cool and probably the most understandable by amateur.
Au lieu d'avoir un système qui gère la LED quand il ya une
The main issues I have noticed with the v180 base image are pretty bad.
1 - No fonts when we had previous base images which had fonts bundled.
2 - Engineering apps are installed by default - this is not ideal for end users
because a lot of them can not be removed.
I think that these are P1 issue
But Kevin, Flame devices are not intended for end users, actually as a base
image should have the engineer apps and then update to 2.0 with non-engineer
apps.--
Atte.
Sebastián Enrique Becerra Cancino
Facebook: SebaEBC
Twitter: @SebaEBC
Tel.: +56 9 9169 0521
On Mon, Sep 29, 2014 at 2:58 PM, Kev
Sebastian is correct, v180 is originally intended for the development crowd to
use. Notice its also rooted, with whatever configurations are set by default.
Francis and Wesley from the TAMs team will communicate the wish list of what
should be fixed in the next version of the flame base image.
Most of these testing apps are not even needed for developers besides when we
are developing the feature. We should probably do a better job of removing old
testing apps, or opting into installing them.
They should not be on the base image though as they are not useful for
development in most c
+1 bundling with test apps is annoying and reminded me to file
https://bugzilla.mozilla.org/show_bug.cgi?id=1031961 a while ago, anyone
wanna give me a pointer and hopefully I can get round to fixing it, its
mostly the test apps, but seeing as they are reference devices that dont go
through certifi
So I wanted to see if our infrastructure caught
https://bugzilla.mozilla.org/show_bug.cgi?id=1071359#c9 but the
archives of this list are not public and are also basically impossible
to read because the attachments are scrubbed.
Can we please move this to dev-tree-management?
- Kyle
On Mon, Apr
Loop in Wesly Huang (TAM)
(I’m figuring out how to avoid this confusion.)
On Sep 30, 2014, at 2:24 AM, Tony Chung wrote:
> Sebastian is correct, v180 is originally intended for the development crowd
> to use. Notice its also rooted, with whatever configurations are set by
> default.
>
> Fr
11 matches
Mail list logo
