On Feb 5, 2013, at 8:11 AM, Marcio Galli <[email protected]> wrote:

>> This is a developer phone that is not meant to be a commercial product
>> or commercial quality.
> 
> And as a developer phone is fine — see my CSS3 3d effect in the
> background clock:
> http://www.flickr.com/photos/98393462@N00/8448211300/in/photostream

Cool effect :)

> 
> Also, we don't fully support the build on it
>> yet. I am pretty sure we will fix the touch screen issues with an
>> upcoming patch. But thanks for the feedback.
> 
> You are welcome — BTW the screen in this device sometimes paints with
> an interesting effect that is probably associated with a hardware

I have no idea what could be going on here, but this sounds like some sort of 
hardware issue/interference (best guess).

> refresh — a wave passes from top to bottom but I am not sure the
> conditions. I also noticed the screen is not as dark as other devices
> when the cellphone is turned off.

Can you compare sleep with battery-removed. If there is a brightness 
difference, we aren't turning off the LCD backlight properly, which is a 
battery drain. Thanks!

Andreas

> 
> m
> 
>> Andreas
>> 
>> Sent from Mobile.
>> 
>> On Feb 5, 2013, at 3:20, Marcio Galli <[email protected]> wrote:
>> 
>>> Fabricio attended Campus Party and was able to grab a Keon phone for
>>> me from Mozilla+Telefonica with no strings attached ;) So it works but
>>> I have some notes I wanted to point:
>>> 
>>> a) Buttons on the left are difficult to type – not always you can get
>>> traction so you need to try again. This seems to be both related to
>>> the fact the screen is not as "touchable" as a high-end phone and the
>>> fact the UI buttons are small. The reason I mentioned "on the left" is
>>> because it's clearly a left to right metaphor;
>>> 
>>> b) Power button won't feedback the "click". I went to Fabricio's labs
>>> and looked others and we noticed that some of other Keons have a
>>> better power button;
>>> 
>>> c) Volume up/down + power internal rubber detaches from the plastic
>>> easily when you take the plastic out for battery exchange — which is a
>>> must since the power gets stuck and/or device gets stuck in a state I
>>> am not sure yet when it happens but it might be due to developer
>>> condition;
>>> 
>>> This is so far 24 hours. I do not know which is the phone that Mozilla
>>> is going to go for real, and I respect this one as being "developer
>>> preview" but I wish for Mozilla internal folks, the ones that are
>>> validating a product to market condition, to use and abuse your phones
>>> hardware too. I am assuming that Mozilla folks are experts in abusing
>>> the open web API or locking it if they know it's not safe.
>>> 
>>> m
>>> 
>>> --
>>> www.telasocial.com
>>> _______________________________________________
>>> dev-b2g mailing list
>>> [email protected]
>>> https://lists.mozilla.org/listinfo/dev-b2g
> 
> 
> 
> -- 
> www.telasocial.com

_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to