Posts tagged with “Freerunner”
Virtual Keyboard
I just found this little EFL-testapp:
It’s an app written by Gustavo Sverzut Barbieri. It’s an Iphone like virtual keyboard. You can find the sourcecode on googlecode..
I had to apply a little change to the code, to get it running on the Freerunner.
I changed lines 206-210 to this:
if ecore.evas.engine_type_supported_get(“software_16_x11”):
ee = ecore.evas.SoftwareX11_16(w=WIDTH, h=HEIGHT)
else:
print “warning: x11-16 is not supported, fallback to x11”
ee = ecore.evas.SoftwareX11(w=WIDTH, h=HEIGHT)
Maybe someone likes to modify this code and build a real virtural keyboard for SHR out of it?
I hope i could motivate someone, as this would be a really nice keyboard.
fsoraw and neon
Today I decided to try out the picture-viewing-app “neon” [1] [2] on my Freerunner. This app is really amazing! It is pretty fast and provides very cool features like auto rotating images by dimensions, auto rotating window using accelerometers and of course zooming, manual rotating images, slide-show, the basic stuff. And if you use the b_and_w theme it looks pretty elegant.
All in all i can say: I love this app! And therefore i created a ticket in the SHR-Trac to add neon to the SHR-Feed [3].
After a while of using neon I found a few things that couldn’t satisfy my expectations:
- 1st the white background of the b_and_w theme, which is visible if a picture doesn’t fill the screen. But a short look in the neon-SVN and one edje_cc later I had created a edje-file for b_and_w theme, which has a black background [4].
- 2nd issue was that the display of the Freerunner blanked while looking at pictures. This is where “fsoraw” [5] [6] comes on. Fsoraw (FSO Resource Allocation Wrapper) is a wrapper utility to launch applications preallocating system resources from FSO. That means you can activate e.g. the “Display”-resource, just by editing the .desktop file of an app. This way I edited my /usr/share/applications/neon.desktop to allocate the “CPU” and “Display” resources, to avoid suspending and display blanking. Furthermore, I customised the neon parameters to activate the picture and window auto rotating stuff, to use the b_and_w theme and to start in my “Bilder” (=pictures) folder. The Exec line of the .desktop file now looks like this:
Exec=fsoraw -r CPU,Display — neon -f -r 0 -R 1 -t b_and_w /media/mmcblk0p3/Bilder
Have fun with neon and use fsoraw (e.g. for mokomaze, too):
Exec=fsoraw -r CPU,Display mokomaze[1] neon project page
[2] neon in om-wiki
[3] shr #596
[4] download this edje-file
[5] fsoraw project page
[6] fsoraw in om-wiki
Openmoko: The Echo Bug
Since a very long time there is a very annoing bug (#1267), the ‘Echo Bug’. But about a week ago there was a very interesting post on the community-mailinglist: Echo issue on OM2008.08 solved, which describes how to solve this bug.
The mail provides a patch and binary files, too. So we don’t have to compile code to get the fix.
Installing the binary files is pretty easy, just follow these steps:
1. download files
http://danielnoethen.de/libqtopiaphonemodem.so.4.3.2
http://danielnoethen.de/gsmhandset.state
2. upload these files to you Neo
scp libqtopiaphonemodem.so.4.3.2 root@moko:/opt/Qtopia/lib/libqtopiaphonemodem.so.4.3.2scp gsmhandset.state root@moko:/usr/share/openmoko/scenarios/gsmhandset.state
3. restart Qtopia
/etc/init.d/xserver-nodm restart
That’s it!
Now you should be able to call someone without annoing him with his own echo.
I tested this fix on my FDOM-20080927, but it should also work on every distribution using the Qtopia phone-stack. Furthermore the fix is known by the developers and is ‘in testing’, so it should get into the official sources soon.
Attention: as zecke says in his post (http://zecke.blogspot.com) overwriting the binary library-file is a very dirty way to get this fix and it can lead to chaos in the packagemanager. A cleaner way would be to use the openmoko-testing feeds and upgrade using the package-manager.