New rotate version
Vikas Saurabh
vikas.saurabh at gmail.com
Tue Oct 14 22:03:06 CEST 2008
The test application is blurting out lots of output, following is a
snippet(from the middle of the output) which sort of showed some difference
when I tapped the screen.
Types: a(2), b(2), c(2)
Codes: a(0), b(1), c(2)
Value: a(-18), b(-1152), c(-54)
vertical straight
Types: a(2), b(2), c(0)
Codes: a(1), b(2), c(0)
Value: a(-1062), b(-72), c(0)
left
Types: a(2), b(2), c(2)
Codes: a(0), b(1), c(2)
Value: a(72), b(-990), c(-216)
vertical straight
Types: a(2), b(2), c(2)
Codes: a(0), b(1), c(2)
Value: a(108), b(-990), c(-234)
vertical straight
Do, tell me if I need to get something specific from the output.
BTW, for restoration to sane state, I think we would like to maintain the
brightness value when we switched it off and then restore to this value if
the program was ended (normal exit, I understand kernel can force kill
without giving the process any chance to anything).
--Vikas
On Wed, Oct 15, 2008 at 1:06 AM, Rui Miguel Silva Seabra <rms at 1407.org>wrote:
> Hi,
>
> Thank you very much for your input. Can you try to run a bit of the
> 'test' I include? I'm starting to suspect different accelerometers might
> give different outputs and so the heuristics might not make sense
> anymore, I hope that's not the case.
>
> You can return the brightenss with
>
> echo 63 > /sys/class/backlight/pcf50633-bl/brightness
>
> ... in the meanwhile.
>
> As for terminating... only a few signals can be caught, I will try to
> set them up in order to stop in a sane state (xrandr -o 0, full
> brightness if it's currently 0, and so on).
>
> Rui
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openmoko.org/pipermail/community/attachments/20081015/bea6b2f1/attachment.htm
More information about the community
mailing list