EDJE key-pressed events from textblocks?
Hi! I modified the zhone-app (I made an extra-style with small font to show all 160 chars at sms-input) but now I wanted to see how many chars I already have entered. Is there a key-pressed-event or some other way to count the chars enteres in the zhone-text-edit - edc? It uses the textblock-part from EDJE and I am correct to assume, that it's a direct text-input (without the python-script handling the pressed keys?). It's just a minor question, but I think it's nice to know how many chars are left. (Or do you have another simple and fingerfriendly programm that has zhone's abilities that I could use instead?) Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ffalarms 0.2.1 and atd-over-fso (now works on SHR-testing)
Hm... I looked at the sources from atd-over-fso (but I'm no expert... so
maybe it's not my place to say this) and I think maybe otimed is not
there anymore.
If you look in the specs, there are some things, but no otimed.
http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/index.html;hb=HEAD
Łukasz Pankowski schrieb:
Timo Scheffler timo.scheff...@uni-oldenburg.de writes:
Wrong Link, here is the example:
#!/usr/bin/env python
import dbus
import time
# Wakeup in 60 seconds
wakeuptime=str(time.time()+60)
system_bus = dbus.SystemBus()
rtc_object = system_bus.get_object('org.freesmartphone.odeviced',
'/org/freesmartphone/Device/RealTimeClock/0')
rtc_interface = dbus.Interface(rtc_object,
dbus_interface='org.freesmartphone.Device.RealTimeClock')
rtc_interface.SetWakeupTime(wakeuptime)
atd-over-fso works on top of org.freesmartphone.Time.Alarm
http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Time.Alarm.html;hb=HEAD
and should be equivalent to to attached aldbus.py script, you will have
stop atd-over-fso (/etc/init.d/atd stop) as the script uses its dbus
name. (atd-over-fso also sets rtc from time(NULL) when setting the
alarm).
You can set the alarm time from the console and list the alarms to
compared displayed timestamps with time.time():
$ ffalarms -s 7:00
$ ffalarms -l
1240981200 Wed Apr 29 07:00:00 2009
$ TZ=UTC ffalarms -l
1240981200 Wed Apr 29 05:00:00 2009
$ ls -l /var/spool/at/
-rwxr-xr-x1 root root 1320 Apr 28 21:01
1240981200.ffalarms.6399
p-w--w--w-1 root root0 Apr 28 21:01 trigger
it may be some kind of timezone problem, you may also try to set alarm
an hour before/later to see whether this will wake up the phone.
___
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: ffalarms 0.2.1 and atd-over-fso (now works on SHR-testing)
I installed ffalarms and love it, but the wakeup from suspend doesn't work... I use FSO 5 and the ffalarms 0.2.1 and atd-over-fso with python 2.6 package. Is there anything to configure, so that it might work? (At least my phone doesn't goes to sleep by itself, so thats no issue... but that's another problem with fso5 :D). Timo Helge Hafting schrieb: kimaidou wrote: Hi Lukasz 1st, thanks for this great application. I would like to know: * if you planed to release a deb package for the debian based distros * if you planned to add the features wich mimate the sun rising by increasing the light step by step as the sound increase the volume. The best would be to go from red to orange, then yello then white :D Thx again 2009/4/27 Łukasz Pankowski lukp...@o2.pl Steven ** montgoss+openmokocommun...@gmail.com mailto:montgoss%2bopenmokocommun...@gmail.com writes: A well written app that works quite well under latest SHR-testing (installed via opkg directly from SHR feeds). Nice to hear. One area I think needs improvement ASAP: my Freerunner suspends (thus silencing the alarm) before the alarm gets loud enough to really wake me up. SHR goes back to suspended after about 1 minute even if ffalarms is playing the alarm. There are two things that would help this: 1. Make the loudness increase by more with each step. Ideally this would be configurable. Currently it increases the volume +1 each second, I may make the time between increases configurable in config file if you insist that fixing point 2. (see below) is not enough for you. 2. Make ffalarms prevent suspend for a time, maybe 5 minutes. (Note that it would be REALLY bad to prevent suspend indefinitely, as I might forget I set an alarm and walk away from the phone, only to come back hours later to an empty battery) I will try to fix the suspend issue this weekend (time is scarce) that is avoid suspending until you stop the alarm. Please keep the alarm going for 15min or so - it is possible to sleep through 5 min. :-) 15 min won't hurt the battery much. Also, consider using the vibrator when the ringing gets loud. That helps if the phone is inside a pocket, in a noisy place. Thanks for a fine and useful app! Helge Hafting ___ 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: ffalarms 0.2.1 and atd-over-fso (now works on SHR-testing)
I suppose the atd doesn't wake the openmoko up at the right time (I used your ipk from the project site). I just tried waking the Openmoko up using the FSO api and was successful :) I think it would be great to abstract the scheduling part, so that you could use FSO api or at (to support 2008.12, SHR should be able to do FSO api?) to set the alarm? At least using FSO api you set a unix_timestamp, so alarms for tomorrow or the day after tomorrow are no problem... But you can't register more than one wakeup at a time (own handling would be necessary)... Just some thoughts... because I love your gui and would be willing to do something about using the FSO api (but also contribute to the main thing instead of doing my own version). Example of setting the wakeup time using FSO api can be found here [1]. Timo [1]: http://wiki.openmoko.org/wiki/User:Sparrow Helge Hafting schrieb: Timo Scheffler wrote: I installed ffalarms and love it, but the wakeup from suspend doesn't work... I use FSO 5 and the ffalarms 0.2.1 and atd-over-fso with python 2.6 package. Is there anything to configure, so that it might work? (At least my phone doesn't goes to sleep by itself, so thats no issue... but that's another problem with fso5 :D). It wakes up from suspend for me - but that might be a difference between FSO and the SHR that I use. Helge Hafting ___ 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: ffalarms 0.2.1 and atd-over-fso (now works on SHR-testing)
Wrong Link, here is the example:
#!/usr/bin/env python
import dbus
import time
# Wakeup in 60 seconds
wakeuptime=str(time.time()+60)
system_bus = dbus.SystemBus()
rtc_object = system_bus.get_object('org.freesmartphone.odeviced',
'/org/freesmartphone/Device/RealTimeClock/0')
rtc_interface = dbus.Interface(rtc_object,
dbus_interface='org.freesmartphone.Device.RealTimeClock')
rtc_interface.SetWakeupTime(wakeuptime)
Timo Scheffler schrieb:
I suppose the atd doesn't wake the openmoko up at the right time (I
used your ipk from the project site).
I just tried waking the Openmoko up using the FSO api and was successful :)
I think it would be great to abstract the scheduling part, so that you
could use FSO api or at (to support 2008.12, SHR should be able to do
FSO api?) to set the alarm?
At least using FSO api you set a unix_timestamp, so alarms for tomorrow
or the day after tomorrow are no problem... But you can't register more
than one wakeup at a time (own handling would be necessary)...
Just some thoughts... because I love your gui and would be willing to do
something about using the FSO api (but also contribute to the main thing
instead of doing my own version).
Example of setting the wakeup time using FSO api can be found here [1].
Timo
[1]: http://wiki.openmoko.org/wiki/User:Sparrow
Helge Hafting schrieb:
Timo Scheffler wrote:
I installed ffalarms and love it, but the wakeup from suspend doesn't
work... I use FSO 5 and the ffalarms 0.2.1 and atd-over-fso with python
2.6 package.
Is there anything to configure, so that it might work?
(At least my phone doesn't goes to sleep by itself, so thats no issue...
but that's another problem with fso5 :D).
It wakes up from suspend for me - but that might be a difference between
FSO and the SHR that I use.
Helge Hafting
___
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: bicycling with OpenMoko
Not my pictures :) I was too lazy too make pictures of my own creation... I use the internal GPS and most of the time it is good. Joerg Reisenweber schrieb: Am Do 23. April 2009 schrieb Timo Scheffler: That's the way to go :) I made something simple in about half an hour, using this [1] as insipration. Just get some Polymethylmethacrylat (PMMA - Plexiglas - marketing name here), a spare socket from a removable light, a jigsaw and a heat gun :) After you have something like this [2] you simply glue it on the socket with much hot melt adhesive and there you go. :) Btw. the hole in the Neo is great to tie it to the holder - just in case some accident happens or so. Timo [1]: http://www.rabenfrost.net/openmoko/bikemount/stencil.svg [2]: http://www.rabenfrost.net/openmoko/bikemount/100_5593.JPG WTF is this ugly black thing on top of it? ;-) Don't you know builtin GPS isn't that bad anymore, after kernelpatch (and 10pF on uSD)? cool :-) /j ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ffalarms 0.2.1 and atd-over-fso (now works on SHR-testing)
You're right.
It's set to GMT and I have GMT +2 ...
What do I have to do to fix it? *feels like newbie*
Łukasz Pankowski schrieb:
Timo Scheffler timo.scheff...@uni-oldenburg.de writes:
Wrong Link, here is the example:
#!/usr/bin/env python
import dbus
import time
# Wakeup in 60 seconds
wakeuptime=str(time.time()+60)
system_bus = dbus.SystemBus()
rtc_object = system_bus.get_object('org.freesmartphone.odeviced',
'/org/freesmartphone/Device/RealTimeClock/0')
rtc_interface = dbus.Interface(rtc_object,
dbus_interface='org.freesmartphone.Device.RealTimeClock')
rtc_interface.SetWakeupTime(wakeuptime)
atd-over-fso works on top of org.freesmartphone.Time.Alarm
http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Time.Alarm.html;hb=HEAD
and should be equivalent to to attached aldbus.py script, you will have
stop atd-over-fso (/etc/init.d/atd stop) as the script uses its dbus
name. (atd-over-fso also sets rtc from time(NULL) when setting the
alarm).
You can set the alarm time from the console and list the alarms to
compared displayed timestamps with time.time():
$ ffalarms -s 7:00
$ ffalarms -l
1240981200 Wed Apr 29 07:00:00 2009
$ TZ=UTC ffalarms -l
1240981200 Wed Apr 29 05:00:00 2009
$ ls -l /var/spool/at/
-rwxr-xr-x1 root root 1320 Apr 28 21:01
1240981200.ffalarms.6399
p-w--w--w-1 root root0 Apr 28 21:01 trigger
it may be some kind of timezone problem, you may also try to set alarm
an hour before/later to see whether this will wake up the phone.
___
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: ffalarms 0.2.1 and atd-over-fso (now works on SHR-testing)
r...@om-gta02:~# cat /etc/timezone Europe/Berlin /etc/localtime == /usr/share/zoneinfo/Europe/Berlin (wasn't overwritten at boot, checked using md5sum) The clock on the phone is right: r...@om-gta02:/etc# date Tue Apr 28 23:59:56 CEST 2009 Here are some reports from your test commands: r...@om-gta02:/etc# ffalarms -s 7:00 r...@om-gta02:/etc# ffalarms -l 1240981200 Wed Apr 29 07:00:00 2009 r...@om-gta02:/etc# TZ=UTC ffalarms -l 1240981200 Wed Apr 29 05:00:00 2009 r...@om-gta02:/etc# ls -l /var/spool/at/ -rwxr-xr-x1 root root 1302 Apr 29 00:00 1240981200.ffalarms.1856 p-w--w--w-1 root root0 Apr 29 00:00 trigger Looks exactly like your test... so what can be wrong... hm. Łukasz Pankowski schrieb: Timo Scheffler timo.scheff...@uni-oldenburg.de writes: You're right. It's set to GMT and I have GMT +2 ... What do I have to do to fix it? *feels like newbie* I would first check $ cat /etc/timezone Europe/Warsaw And set it to what I need if says something different $ echo Europe/Warsaw /etc/timezone Something must recreate /etc/localtime during boot time (doing it by hand is described in the message below). If the problem comes back (I did not have this problem) you may look at [SHR] timezone broken again thread http://kerneltrap.org/mailarchive/openmoko-community/2009/4/15/5505084 ___ 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: bicycling with OpenMoko
That's the way to go :) I made something simple in about half an hour, using this [1] as insipration. Just get some Polymethylmethacrylat (PMMA - Plexiglas - marketing name here), a spare socket from a removable light, a jigsaw and a heat gun :) After you have something like this [2] you simply glue it on the socket with much hot melt adhesive and there you go. :) Btw. the hole in the Neo is great to tie it to the holder - just in case some accident happens or so. Timo [1]: http://www.rabenfrost.net/openmoko/bikemount/stencil.svg [2]: http://www.rabenfrost.net/openmoko/bikemount/100_5593.JPG Al Johnson schrieb: On Thursday 23 April 2009, ivvmm wrote: Hey, seen many messages about audio mapping the OSM with new app called 'Dictator' in neighbour thread and so on. But the first question that rises here is how to mount the phone on your bike? I made a mount out of polymorph - a trade name for a low melt plastic that feels similar to nylon, but becomes like putty at ~60C. Someone else routed a recess in a sheet of chipboard. I saw pictures of one made from folded acrylic sheet - very neat! Some have used commercial generic phone/pda holders. You could even go the whole hog and get an Otterbox PDA case with bike mount for all-weather ruggedness. At the other end of the scale someone was using a cable tie through the hole in the phone and round the handlebars! ___ 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
[FSO] Trigger querty-keyboard from inside application
Hi! I'm just starting to script something useful using fso, python and edje. I have some questions about the keyboard which I couldn't find the answer to... 1. Is there a way to trigger the keyboard using the framework or some other command I can let the python script work with? When a text-field gets focus, the keyboard should automaticaly appear (and since it's not like that now, my app could take care of that). 2. Where can I adjust the keyboard to have the Terminal-Layout as default after booting? Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
SIDplay on openmoko?
Hello! Has somebody seen sidplay on the openmoko or has a hint how to play SIDs? Is it complicated to cross-compile such a program for the openmoko? (I think there are Wiki entrys... but I ask, because maybe somebody already built it for the openmoko). Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Qtopia 4.3.3 Alarm Clock not starting after wake up
Hello! I'm using Qtopia 4.3.3 (installed via the rootfs image from qtopia.net). If I set the Alarm Clock and the phone doesn't suspend until the time for the alarm has come, it works as expected. But if the openmoko goes to sleep and the time arrives, it wakes up but there is no alarm clock (not ringing, no application or notice on the screen, just the homescreen or whatever was shown as it went to sleep). I think by the time the openmoko is resumed, the point in time when the alarm would start is already in the past. If I could change the alarm clock to set the wakeup time for the phone to 5 seconds before the alarm clock is triggered, it would be awake and the alarm would work. Maybe you know a fix for this or know another reason why the clock isn't working (in case I got the wrong idea of how the system works) and would bother to tell me. :) Thanks in advance, Timo Scheffler ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ASU : can't import vcf contacts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I experimented with it as well and found that the vCards I get from exporting with Thunderbird Adressbook with the MoreFunctionsForAddressBook Plugin works. They look like this: BEGIN:VCARD VERSION:2.1 N;CHARSET=UTF-8:Mustermann;Max FN;CHARSET=UTF-8:Max Mustermann ADR;HOME;POSTAL;CHARSET=UTF-8:;;;City;;12345;Deutschland TEL;WORK;VOICE:0123456789 TEL;HOME;VOICE:0123456789 TEL;CELL;VOICE:0123456789 EMAIL;PREF;INTERNET:[EMAIL PROTECTED] END:VCARD I even could export 75 contacts, cat them into one file and import them all at once using the information from the wiki. julien cubizolles schrieb: I tried the method described in http://wiki.openmoko.org/wiki/Import_Vcf_Contacts#Import_for_ASU.2FQtopia but it fails with : On the ssh xterm LD_LIBRARY_PATH=/opt/Qtopia/lib /opt/Qtopia/bin/addressbook /home/root/test.vcf QImage::scaled: Image is a null image QPixmap::fromImage: Cannot convert a null image QPixmap::fromImage: Cannot convert a null image QCoreApplication::postEvent: Unexpected null receiver On the Freerunner : The VCard document did not contain any valid contacts The vcard is just : BEGIN:VCARD VERSION:3.0 FN:John Doe N:Doe; John EMAIL;TYPE=OTHER:[EMAIL PROTECTED] TEL;TYPE=WORK,VOICE:01 43 27 28 44 END:VCARD What can be wrong ? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAki0CIYACgkQVX1dHwovnRHtbACg0Cugn3do5jDZKEbAN6v+MIwX VmsAoIx0eLYm56tQDryEGvM1EYZAp2/4 =I82e -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
