Re: ventura upgrades

[Richard Kralovic]

Hello,

I guess the modifications comes from me (I didn't know that google hides
my mail so well ;-) ). It was basically just a quick hack to make
ventura more comfortable according to my opinion. You can use the menu
to hide the buttons at the bottom of the screen, so you are able to
access links below them.

Greets
Richard

c_c wrote:
> Hi,
> 
> Ben Thompson-3 wrote:
>>  I liked the uncluttered screen before and the menu button was larger and
>> easier to use with my fingers. Also, I don't like that fact that more
>> of the web page is now obscured by icons.
>>
>I've been thinking of moving the buttons to the top of the screen -
> seeing that most websites have the topmost part without any links.
>I think the pg dn and pg up buttons actually make scrolling a lot simpler
> since the openmoko's graphics subsystem can't really cope up with the
> scrolling.
> 
>Actually, the edj file can be improved to hide the buttons when not in
> use. Perhaps someone with greater edj experience can help.
> 
>I'll update the edj file soon.
> 
> 


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [SHR-U] Transparent qwo

[Richard Kralovic]

Hello,

I am using transparent qwo, but I haven't upgraded my FR since I wrote
the instructions (it's on my todo list, but... :-) ). So, I am not very
sure about the current state of packages, but to the best of my
knowledge, situation is as follows:

1) 2) Nobody maintains Xglamo, last commit at git.openmoko.org was 7
months ago. Glamo driver for xorg is under active development, so maybe
it just works by now. Nevertheless, the patch on Xglamo was accepted to
SHR quite long time ago, so if you use SHR+Xglamo, part of my patch
should be included. (It is the part that fixes crashing; the second part
of the patch that improves motion event handling has not been included
afaik).

3) No idea if the composite extension is enabled by default in any
distribution, but this is just a configuration issue...

4) Xcompmgr is in openembedded, but I do not know if the binary is
provided by the standard opkg feeds of any distribution.

5) You do not really have to patch qwo; an alternative is to use
transset utility to set the transparency manually. However, the patch
improves usability significantly imho. The transparency patch has not
been accepted upstream yet. (Actually, last commit to qwo git repository
is from 28 May).

6) I am not aware of any inclusions of the illume patch anywhere.

Greets
Richard


Dan Staley wrote:
> I really like the idea of qwo and want to try out the transparent
> version mentioned at [1].
> However, the instructions were written months ago, and involve patching
> xglamo and illume...so I am hesitant to try given that the changes may
> not be relevant as the packages may have changed (perhaps even
> implemented the patches!).
> 
> Given that literki seems to be very quick and handles transparency very
> well, has anyone recently tried a transparent qwo?  If so, are the
> patches and install process at [1] still applicable?
> If soare there any plans to merge the patches in so that a
> transparent binary of qwo could be provided?
> 
> Thanks in advance,
> -Dan Staley
> 
> [1] http://kedrigern.dcs.fmph.uniba.sk/~riso/Openmoko/qwo/
> 
> 
> 
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [OM2009] airplane mode

[Richard Kralovic]

> window seat makes no difference : )
> in fact for several minuets i was holding my freerunner against the
> window and got nothing...

I used gps on my freerunner successfully on several flights :-). I just
pushed FR against the window and got a fix within few minutes.
Afterwards, everything worked nicely.

I am using an old FSO milestone 5 build; to enable "airplane mode" there
it is sufficient to close zhone ;-).

Greets
Richard

> 
> On Fri, Jun 19, 2009 at 2:35 PM, Jakob  > wrote:
> 
> On Fri, Jun 19, 2009 at 11:26 PM, jeremy
> jozwikmailto:jerjoz.for...@gmail.com>> wrote:
> > you might be allowed to. but i have yet to actually get a gps lock
> after
> > leaving the terminal. so whats the point?
> > i tried on several occasions to get it to work. even with a lock
> in the
> > terminal, after sitting in the plane waiting to taxi i loose the
> signal
> 
> I tried to track a flight once, too. The problem is probably that
> airplanes are a faraday cage as they're usually made of some kind of
> metal. I didn't have a window seat to test if one has a signal there.
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org 
> http://lists.openmoko.org/mailman/listinfo/community
> 
> 
> 
> 
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: illume keyboard force on/off

[Richard Kralovic]

> thank you for the workaround. the trouble is that showing the keyboard 
> always requires time to redraw the window than needs to be resized
> if it stayed as is the response would be faster. i am surprised nobody

This is one of the benefits of using transparent keyboard :-). Although
the transparency itself is not very fast, there is no need to resize the
application window when displaying/hiding the keyboard, so the overall
responsiveness is much better imho.

I implemented the transparency for qwo (and it was discussed quite a lot
here). Afaik nobody made it usable for the illume keyboard so far, but
it shouldn't be hard to do it...

Greets
Richard


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: illume keyboard force on/off

[Richard Kralovic]

Hello,

> it doesn't remember i have made it show once i switch windows and this
> gets really annoying. is there a way for it to remember it's state for
> a window?

I do not know how hard is it to add this feature into illume, but maybe
a useful workaround is to modify the illume theme to have the keyboard
toggle button directly accessible? Then you can (de)activate keyboard
with one click at any time. (I have done that and am quite happy about
it; it's quite hackish, but you can see the sources at
http://kedrigern.dcs.fmph.uniba.sk/~riso/e-wm-theme-illume-a.tar.gz
)

Greets
Richard

> 
> imagine a typical situation - retyping from one window to another:
> 
> open terminal, reach up, get keyboard, type
> open web browser, reach up, get keyboard, type
> read up some stuff
> switch back to terminal - keyboard is off, go up, get keyboard, type
> switch to browser, read up some more
> switch back to terminal - keyboard is off, go up, get keyboard, type
> 
> thanks for any hints...
> 
> Petr
> 
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Transparent keyboard in illume

[Richard Kralovic]

> * I can only write numbers with this version. the move from the center

I have just fixed that (a small bug that sneaked in just before I
released the patch...). Should be working now, try to reinstall qwo.

Greets
Richard

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Transparent keyboard in illume

[Richard Kralovic]

Hello,

> * you changed the yellow "shapes". Could you tell us why ? By the way,

I changed it for better recognition accuracy. It is claimed by original
author of quikwriting (Ken Perlin), and my experience confirms it. For
me, it is _much_ easier to write with the new layout when using fingers.
(If you are using stylus, it shouldn't matter much.)

> they seem to be drawn with the mouse (not regular). Is it art ? (joking,
> light tone)

No. They are quite regular (should be symetric), I basically copied them
from the shapes of the original java quikwriting appliction by Ken
Perlin and tweaked a bit manually (no drawing with mouse :-) ).

> * I can only write numbers with this version. the move from the center
> to one zone and back to the center do not work anymore (as more complex
> ones). Instead theses moves write numbers. Am I the only one with this bug ?

Which package did you install? I can try to check it on my phone

Greets
Richard

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Transparent keyboard in illume

[Richard Kralovic]

Hello,

> When patch will be more flexible, I will add it to SHR (patch for
> compositing with Xglamo is already in SHR for some time)

Ok, so it should be a bit more flexible now. A new version (see updated
http://kedrigern.dcs.fmph.uniba.sk/~Openmoko/qwo) does not break the
builtin keyboard any more. Basicaly illume with this patch distinguish
between applications with name "Keyboard" and "TransparentKeyboard", the
latter one is handled differently.

In default configuration, this patch should have no effect. You need a
newly patched qwo to use it, though.

Greets
Richard

> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Transparent keyboard in illume

[Richard Kralovic]

Hello,

> Thanks anyway

You are welcome :-)

> I will try to write a wiki page on this, if you don't mind

Sure, I will be happy about that.

Greets
Richard

P.S. I am testing just now some ideas how to enhance the accuracy of
qwo, so hopefully it will be even more finger-friendly soon ;-)

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Transparent keyboard in illume

[Richard Kralovic]

Hello,

> I got nothing

So it looks like the qwo can not be configured because of dependency
problems with imlib2. Which version of imlib2 do you use? Maybe you
could try to remove imlib2 (with -force-depends) and install it again
from the repository on meru? Or maybe you can try the shr-unstable feed
(i.e. modify your /etc/opkg/meru.conf to use shr-unstable, opkg update,
and opkg install qwo)?

Richard

>  
> 
> Or you can just reinstall qwo (I have recompiled it now to be sure
> that the version is correct).
> 
> 
> --> I tried and could not (the -force-depends did not help)
>  
> r...@om-gta02 ~ $ opkg install -force-depends
> http://kedrigern.dcs.fmph.uniba.sk
> /~riso/Openmoko/qwo/qwo_0.4-r0_armv4t.ipk
> Downloading
> http://kedrigern.dcs.fmph.uniba.sk/~riso/Openmoko/qwo/qwo_0.4-r0_armv4t.ipk
> Multiple packages (qwo and qwo) providing same name marked HOLD or
> PREFER.  Using latest.
> Multiple packages (qwo and qwo) providing same name marked HOLD or
> PREFER.  Using latest.
> Multiple packages (qwo and qwo) providing same name marked HOLD or
> PREFER.  Using latest.
> Multiple packages (qwo and qwo) providing same name marked HOLD or
> PREFER.  Using latest.
> Upgrading qwo on root from 0.4 to 0.4-r0...
> Installing libimlib2-loaders (2:1.4.2.001+svnr38274-r0) to root...
> Downloading
> http://meru.inf.ethz.ch/~rkralovi/shr/ipk/armv4t/libimlib2-loaders_1.4.2.001+svnr38274-r0_armv4t.ipk
> Collected errors:
>  * Package libimlib2-loaders wants to install file
> /usr/lib/imlib2/loaders/tiff.so
> But that file is already provided by package  * imlib2
>  * Package libimlib2-loaders wants to install file
> /usr/lib/imlib2/loaders/bz2.so
> But that file is already provided by package  * imlib2
>  * Package libimlib2-loaders wants to install file
> /usr/lib/imlib2/loaders/bmp.so
> But that file is already provided by package  * imlib2
>  * Package libimlib2-loaders wants to install file
> /usr/lib/imlib2/loaders/png.so
> But that file is already provided by package  * imlib2
>  * Package libimlib2-loaders wants to install file
> /usr/lib/imlib2/loaders/xpm.so
> But that file is already provided by package  * imlib2
>  * Package libimlib2-loaders wants to install file
> /usr/lib/imlib2/loaders/pnm.so
> But that file is already provided by package  * imlib2
>  * Package libimlib2-loaders wants to install file
> /usr/lib/imlib2/loaders/tga.so
> But that file is already provided by package  * imlib2
>  * Package libimlib2-loaders wants to install file
> /usr/lib/imlib2/loaders/lbm.so
> But that file is already provided by package  * imlib2
>  * Package libimlib2-loaders wants to install file
> /usr/lib/imlib2/loaders/jpeg.so
> But that file is already provided by package  * imlib2
>  * Package libimlib2-loaders wants to install file
> /usr/lib/imlib2/loaders/argb.so
> But that file is already provided by package  * imlib2
>  * Package libimlib2-loaders wants to install file
> /usr/lib/imlib2/loaders/zlib.so
> But that file is already provided by package  * imlib2
> 
> 
> If you want to test if the transparency works at all, you can try
> opkg upgrade
> opkg install transset
> transset
> and click any window - it should be transparent afterwards.
> 
> 
> --> it worked well !
>  
> 
> Thanks for your patience :D
> 
> 
> 
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Transparent keyboard in illume

[Richard Kralovic]

> Then I restarted, and lead the xcom script. It runs ok (no errors).
> But when I "open" the keyboard, it is not transparent, and the circles
> from "u..." clockwise or the way back just change the size. Have I
> really installed "your" qwo package ? How can I check please

Hmmm... you can e.g. check if /usr/bin/qwo contains string
NET_WM_WINDOW_OPACITY (run
strings /usr/bin/qwo | grep NET_WM_WINDOW_OPACITY
). Or you can just reinstall qwo (I have recompiled it now to be sure
that the version is correct).

If you want to test if the transparency works at all, you can try
opkg upgrade
opkg install transset
transset
and click any window - it should be transparent afterwards.

Greets
Richard

> 
> Thanks again
> 
> 
> 
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Transparent keyboard in illume

[Richard Kralovic]

Hello,

> thanks for you reply. I would need some more help before running the
> installation process. I will write a wiki page on openmoko.org

Ok, I try to be more verbose. If you have more questions, just ask :-):

> There are also feeds for shr testing
> http://meru.inf.ethz.ch/~rkralovi/shr
> 
> 
> 
> I will use this since I run SHR testing

Most of the packages was compiled on 19 March. So, if SHR testing didn't
change too much since then, it might be a good choice. If it doesn't
work, let me know an I try to recompile for recent SHR testing.

> I think SHR testing uses FSO5, so I have nothing to install, right ?

Shr uses FSO, but FSO-M5 is basically a different distribution, with
different versions of packages. So I am not sure if versions for FSO-M5
are ok to install into SHR testing.

> So, basically it should just work if you add this to your opkg feeds:

You have to create a file /etc/opkg/meru.conf with the following content:

src/gz meru-all http://meru.inf.ethz.ch/~rkralovi/shr/ipk/all
src/gz meru-armv4t http://meru.inf.ethz.ch/~rkralovi/shr/ipk/armv4t
src/gz meru-om-gta02 http://meru.inf.ethz.ch/~rkralovi/shr/ipk/om-gta02

> After this, I will run opkg update

Yes.

> Is this correct (or do I need to add some more command lines ?):

Try just
opkg update
opkg install xserver-kdrive-glamo xcompmgr qwo e-wm

I am not sure if xserver and e-wm will be reinstalled - if not, try
opkg -force-depends remove xserver-kdrive-glamo
opkg -force-depends remove e-wm
and then opkg install ...

> #modifiy the file */etc/X11/Xserver
> nano **/etc/X11/Xserver
> And add *ARGS="$ARGS +extension Composite"
> 
> #creating a file to launch xcompmgr and load it
> echo "xcompmgr &" > /etc/X11/Xsession.d/xcompmgr_start
> chmod +x /etc/X11/Xsession.d/xcompmgr_start
> /etc/X11/Xsession.d/xcompmgr_start

Yes.

After restarting illume and selecting qwo as the keyboard, everything
_should_ work. But please be aware that if the packages versions from
shr-testing of my repository are not compatible with your version of
shr-testing (which may well be the case), you can end up with quite
broken system. So I recommend you to have backup (maybe whole image of
rootfs).

> This is all I understoof reading your email and the webpage. Can you
> please comment / modify it ?

If you have more questions, just ask :-)

Greets
Richard

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Transparent keyboard in illume

[Richard Kralovic]

> I would like to know if there were some progress on easily installing
> the transparent keyboard (qwo or anyone else) on SHR distribution.
> I think the SHR distro could really benefit on this !

Well, not much of progress. Some time ago, I set up an ipk feed for
shr-unstable that I compiled myself, with all the patched stuff:
http://meru.inf.ethz.ch/~rkralovi/shr-unstable

There are also feeds for shr testing
http://meru.inf.ethz.ch/~rkralovi/shr

and FSO milestone 5 (which is what I am currently using, so it's
probably in a best shape):
http://meru.inf.ethz.ch/~rkralovi/fso-ms5

So, basically it should just work if you add this to your opkg feeds:

src/gz meru-all http://meru.inf.ethz.ch/~rkralovi/shr-unstable/ipk/all
src/gz meru-armv4t http://meru.inf.ethz.ch/~rkralovi/shr-unstable/ipk/armv4t
src/gz meru-om-gta02
http://meru.inf.ethz.ch/~rkralovi/shr-unstable/ipk/om-gta02

Then you can just follow the instructions at
http://kedrigern.dcs.fmph.uniba.sk/~riso/Openmoko/qwo/index.html
and install all packages just by opkg install.

But beware, the patch for illume breaks the default keyboard (since it
does not set the width of it and does not resize the application area).
So be ready to install the old version of e-wm if you do not like
transparent qwo. I didn't find time to make a nicer patch on e-wm yet
(it is on my todolist, but quite deep, so patches are welcome)...

Greets
Richard

> 
> Thanks for any news
> 
> Kimaidou
> 
> 2009/3/12 Richard Kralovic mailto:r...@om.ksp.sk>>
> 
> > ... so it's working in 2008.12 - I can supply my patched build of
> > illume.ipk if anyone wants it - the only problem being the qtopia
> 
> Great :-). If you wish, send it to me and I can add it to my webpage...
> 
> > "Options" and "Back" buttons etc attached to the display bottom always
> > show on top of...
> 
> I know next to nothing about illume internals, but I'd try to change the
> parameter of e_border_layer_set in illume.c from 100 to something
> higher.
> 
> > Now gotta figure out how to prevent that, or bring qwo even further
> > forward...
> 
> The illume patches are really just nasty hacks, I'd love to have some
> neat patch on illume that automatically checks the X11 atoms of the
> keyboard and adjusts its behaviour according to that. With that, we
> might be able to persuade the SHR guys (or even Raster) to accept it.
> But I do not have much time for that right now :-(.
> 
> Greets
>Richard
> 
> 
> >
> > Rich
> >
> >
> >
> 
> >
> > ___
> > Openmoko community mailing list
> > community@lists.openmoko.org <mailto:community@lists.openmoko.org>
> > http://lists.openmoko.org/mailman/listinfo/community
> 
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org <mailto:community@lists.openmoko.org>
> http://lists.openmoko.org/mailman/listinfo/community
> 
> 
> 
> 
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: High CPU usage of Frameworkd

[Richard Kralovic]

> GYPSY, frameworkd is using permanently 50% of CPU which seems very high to 
> me. 
> Is this normal? Due to python? Or am I doing something wrong. I'm using SHR 
> testing but with FSO it's the same.

For me, GPS always causes very high load, too. I think it is due to
python (but maybe it is possible to optimize it somehow anyway?),
hopefully we will see the vala reimplementation some day :-)

Richard

> 
> Code Snippets:
> 
> 
> /// create proxy objects for method calls 
> QString ServiceBusName = "org.freedesktop.Gypsy";
> QString ObjectPath = "/org/freedesktop/Gypsy" ;
> QString MethodPath = "";
> GPSInterface = new QDBusInterface(ServiceBusName,
>   ObjectPath,
>   MethodPath, 
>   
> QDBusConnection::systemBus() );
>   
> GPSRescourceInterface = new QDBusInterface( ServiceBusName,
>
> ObjectPath,
>
> "org.freesmartphone.Resource",
>
> QDBusConnection::systemBus() );
>   
>  
> GPSDeviceInterface = new QDBusInterface( ServiceBusName,
>
> ObjectPath,
>
> "org.freedesktop.Gypsy.Device",
>
> QDBusConnection::systemBus() );
> 
> GPSOusagedInterface = new QDBusInterface( ServiceBusName,
>
> "/org/freesmartphone/Usage",
>
> "org.freesmartphone.Usage",
>
> QDBusConnection::systemBus() );
> 
> /// enable GPS
> void MokoGPS::StartDevice()
> {
>   GPSDeviceInterface->call("Start");
>   GPSRescourceInterface->call("Enable");
>   qDebug()<<"GPS device started \n";
> }
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: test result of battery current against display brightness and GPS power mode

[Richard Kralovic]

Rask Ingemann Lambertsen wrote:
> On Sat, Mar 28, 2009 at 07:32:24PM +0100, Richard Kralovic wrote:
>> It may be the case that the fixes for the current leak were introduced
>> in devel branch (linux-openmoko-devel). On kernel 2.6.29-rc3, my tests
>> show a drop from cca 80mA to cca 47mA.
> 
>Do you know which git revision that kernel is? Alternatively, where did

I am using gitr1e257a0e99817a338e3706708ebb5036518e46d8, I compiled it
myself.
Richard

> you get that kernel from?
> 



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: test result of battery current against display brightness and GPS power mode

[Richard Kralovic]

Hello,

> With "echo > /sys/bus/spi/devices/spi2.0/state sleep", the current drops 
> from 82.125 mA to 81.562 mA within 10 minutes. The battery is fully charged 
> before test.
> 
> My kernel:
> # uname -a
> Linux om-gta02 2.6.28-rc4 #1 PREEMPT Sun Feb 8 19:53:16 CET 2009 armv4tl 
> unknown

It may be the case that the fixes for the current leak were introduced
in devel branch (linux-openmoko-devel). On kernel 2.6.29-rc3, my tests
show a drop from cca 80mA to cca 47mA.

Richard

> 
> Before read your reply, I get nothing by removing SD card, ifdown usb0, power 
> off backlight.
> 
> Here is the new script I used:
> 
> #!/bin/bash
> 
> # for exit SSH shell, unplug USB
> sleep 5 
> 
> # strange, 1 to power of backlight
> echo > /sys/class/backlight/gta02-bl/bl_power 1
> 
> echo > /sys/bus/spi/devices/spi2.0/state sleep
> 
> for ((i=0; i<20; i++)); do
>   echo "i = $i:"
>   cat /sys/class/power_supply/battery/{current_now,capacity,voltage_now}
>   sleep 30 
> done
> 
> echo > /sys/class/backlight/gta02-bl/bl_power 0
> echo > /sys/bus/spi/devices/spi2.0/state normal
> 
> But comparing to your ~50 mA, 82 mA is still too large :)
> 
> Could anybody who has latest SHR installation on GTA02, give a test to verify?
> 
> Before start this script, please make sure:
> 1. `/sys/bus/platform/devices/neo1973-pm-gps.0/pwron` output 0, else you can 
> echo 0 into it.
> 2. disable GSM/WIFI/Bluetooth in SHR settings
> 3. SSH to FR through USB if you haven't connect to it.
> 4. stop /etc/init.d/xserver-nodm, /etc/init.d/frameworkd
> 5. killall batget; killall wakerd;
> 6. start the above script, e.g. `power.sh > output_power.txt &` , exit SSH 
> shell, unplug USB
> 
> 10 minutes later, you can plug USB and SSH into FR again. If you can't wait 
> for 10 minutes, 
> modify "sleep 30" to "sleep 5" or something else.
> 
> I'd like to say "thank you" to Rask Ingemann Lambertsen again :)
> 
> 
> On Fri, Mar 27, 2009 at 05:21:59AM +0800, Qingyou Meng wrote:
> 
>> To set brightness: write (brightness_percent / 100 * 255) to file
>> "/sys/class/backlight/gta02-bl/brightness"
> 
>I think that's why you get so high currents. This
> 
> # echo >/sys/class/backlight/gta02-bl/brightness 0
> 
> doesn't do what you hope it does. You should try
> 
> # echo 
> >/sys/class/i2c-adapter/i2c-0/0-0073/pcf50633-regltr.9/glamo3362.0/glamo-spi-gpio.0/spi2.0/state
>  sleep
> 
> also. A shorthand for that file is /sys/bus/spi/devices/spi2.0/state. When
> the display isn't blanked, it reads 'normal'.
> 
>But, IMHO, consider using a higher-level interface (such as
> freesmartphone.org) to turn off the display instead of trying to find all
> the places to mess with under /sys yourself.
> 


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: How to record calls

[Richard Kralovic]

>   I was under the impression that audio for calls bypasses the CPU and 
> operating system entirely, going straight from the sound chip to the GSM 
> chip; if this is the case then such a recording wouldn't be possible.

That's true, but it should be possible to configure alsa mixer settings
in such a way that the GSM audio is routed both to the speaker and to
the ADC converter of the soundcard. It shouldn't be too hard, I guess
you just need to study the mixer settings a bit:

http://wiki.openmoko.org/wiki/Neo_1973_audio_subsystem
http://people.openmoko.org/joerg/ALSA/doc/WM8753_control_diag.pdf

Greets
Richard

> 
> Cheers,
>   Mike.
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Transparent keyboard in illume

[Richard Kralovic]

> ... so it's working in 2008.12 - I can supply my patched build of
> illume.ipk if anyone wants it - the only problem being the qtopia

Great :-). If you wish, send it to me and I can add it to my webpage...

> "Options" and "Back" buttons etc attached to the display bottom always
> show on top of...

I know next to nothing about illume internals, but I'd try to change the
parameter of e_border_layer_set in illume.c from 100 to something higher.

> Now gotta figure out how to prevent that, or bring qwo even further
> forward...

The illume patches are really just nasty hacks, I'd love to have some
neat patch on illume that automatically checks the X11 atoms of the
keyboard and adjusts its behaviour according to that. With that, we
might be able to persuade the SHR guys (or even Raster) to accept it.
But I do not have much time for that right now :-(.

Greets
Richard


> 
> Rich
> 
> 
> 
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [FSO M5] Enable Wlan

[Richard Kralovic]

> I read somewhere that i must enable with framework? But how i can do this?

You need to request the wlan resource, e.g. by calling

mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage
org.freesmartphone.Usage.SetResourcePolicy WiFi enabled

Afterwards you have interface eth0 available; I had to manually set up
essid (iwconfig eth0 essid blabla) to get it working.

Greets
Richard

> 
> 
> Thanks,
> Samuel
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Transparent keyboard in illume

[Richard Kralovic]

Hello,

> Unfortunately the link to the Xglamo binary on your site is broken. 

Should be fixed now, I'm sorry about that.

Richard

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Transparent keyboard in illume

[Richard Kralovic]

> Any way we can get a package for this? I can't compile for my FR.

All binary packages that I have built are available at the howto page:
http://kedrigern.dcs.fmph.uniba.sk/~riso/Openmoko/qwo/
If you are using FSO milestone 5, they should work. If you are using
different distribution, they _might_ work, but they might break your
system as well, so use on your own risk. I have only a compile
environment set up for FSO, so I can not easily provide other packages
just now...

Richard

> 
> 
> 
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Transparent keyboard in illume

[Richard Kralovic]

> but any plans on making a transparent large "normal" keyboard?
> btw: it seems great!

Actually, it is quite easy to make the default illume keyboard
transparent. It should work with the same method as for qwo, except that
you need to revert the first hunk of e-wm-hack.patch, i.e., illume had
to set the width of keyboard to be equal to the width of the screen.

Afterwards, you can use the transset utility (I just added it to my
webpage) to change the transparency of the keyboard (and also
transparency of any other window). Surely, this is very rough and for
normal usage some decent support in illume would be nice. But I guess
this should be discussed with Raster...

Richard

> 
> y
> 
> On Sun, Mar 8, 2009 at 8:49 PM, kimaidou  wrote:
>> Waou, THIS IS GREAT ! I am very happy to find someone with the same will,
>> but skilled ! For me, qwo is also the fastest keyboard, and making it
>> fullscreen + transparent will make it the killer keyboard. Congratulation
>> for sharing your method. I will try it asap.
>>
>> Kimaidou
>>
>> 2009/3/8 Richard Kralovic 
>>> Hello,
>>>
>>> despite some skepticism about having transparent keyboard in illume, I
>>> decided to try it. After some work, I got it working. More precisely, I
>>> am using the qwo external keyboard (an implementation of quikwriting
>>> technique); imho it's great with stylus, and also quite finger-friendly
>>> when the keyboard is large enough. I think it's quite usable. As for
>>> speed, displaying/hiding the keyboard is quicker than displaying/hiding
>>> the default keyboard, since the application window is not resized (which
>>> is usually quite slow).
>>>
>>> I wrote a small howto about it, it's (together with screenshots) here:
>>> http://kedrigern.dcs.fmph.uniba.sk/~riso/Openmoko/qwo/
>>>
>>> Actually, to get it work, I had to fix some bugs/annoying features of
>>> Xglamo. I reported these (together with patches) as ticket #2242 and
>>> #2243 at docs.openmoko.org about one week ago. Unfortunately, I got no
>>> answer regarding these patches. Would it be possible to accept them to
>>> the openembedded repository and close the tickets?
>>>
>>> Next, I had to force illume not to resize the running application when
>>> displaying keyboard, and also not to force the width of the keyboard to
>>> be equal to the width of the screen. Currently, I have only very ugly
>>> hack to do this and I am not quite sure how to do it right. I am
>>> thinking of making illume look for the _NET_WM_WINDOW_OPACITY property
>>> on external keyboards, and behave in above-described way if this
>>> property is set. Would this be acceptable for including upstream?
>>>
>>> Greets
>>>Richard
>>>
>>> ___
>>> Openmoko community mailing list
>>> community@lists.openmoko.org
>>> http://lists.openmoko.org/mailman/listinfo/community
>>
>> ___
>> Openmoko community mailing list
>> community@lists.openmoko.org
>> http://lists.openmoko.org/mailman/listinfo/community
>>
>>
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Transparent keyboard in illume

[Richard Kralovic]

Hello,

despite some skepticism about having transparent keyboard in illume, I
decided to try it. After some work, I got it working. More precisely, I
am using the qwo external keyboard (an implementation of quikwriting
technique); imho it's great with stylus, and also quite finger-friendly
when the keyboard is large enough. I think it's quite usable. As for
speed, displaying/hiding the keyboard is quicker than displaying/hiding
the default keyboard, since the application window is not resized (which
is usually quite slow).

I wrote a small howto about it, it's (together with screenshots) here:
http://kedrigern.dcs.fmph.uniba.sk/~riso/Openmoko/qwo/

Actually, to get it work, I had to fix some bugs/annoying features of
Xglamo. I reported these (together with patches) as ticket #2242 and
#2243 at docs.openmoko.org about one week ago. Unfortunately, I got no
answer regarding these patches. Would it be possible to accept them to
the openembedded repository and close the tickets?

Next, I had to force illume not to resize the running application when
displaying keyboard, and also not to force the width of the keyboard to
be equal to the width of the screen. Currently, I have only very ugly
hack to do this and I am not quite sure how to do it right. I am
thinking of making illume look for the _NET_WM_WINDOW_OPACITY property
on external keyboards, and behave in above-described way if this
property is set. Would this be acceptable for including upstream?

Greets
Richard

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community