Re: testing Litephone, new phone interface

2009-08-21 Thread dorje


rusolis wrote:
 
 I hope you have fun
 

Ok... I use litephone as dailyphone since 2 weeks now and I really love it!
:)



-- 
View this message in context: 
http://n2.nabble.com/testing-Litephone-new-phone-interface-tp3336730p3489235.html
Sent from the Openmoko Community mailing list archive at Nabble.com.

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


Re: testing Litephone, new phone interface

2009-08-20 Thread Denis Johnson
On Tue, Jul 28, 2009 at 8:27 AM, Michal Brzozowski ruso...@poczta.fmwrote:

 Hi,

 I gave it a try and wrote an FSO based phone app in Qt. It's using the new
 PIM service, and since that's not completely stable yet, there are a few
 problems. I'm releasing this anyway, to help test FSO, and meanwhile get
 some feedback on the gui and general idea. Consider it an alpha release.
 There might be little bugs here and there.



Just tried it, love the approach of having everything in one place.
Excellent keep it up.

I did notice that it seems some contacts are skipped between the
alphabetical  buttons/tabs on the right. iow, there are some contact that
are not listed. But you may already be aware of that one.

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


Re: testing Litephone, new phone interface

2009-08-14 Thread Dan Staley
Hi, I decided I wanted to try out litephone on the latest SHR-U and I
followed the steps above.  However whenever I run the gsm registering script
I run into problems.

The first time I run it, I get:
Enabling GSM for ever
/org/freesmartphone/Usage: SetResourcePolicy failed:
org.freedesktop.DBus.Error.NoReply
Turning antenna on
/org/freesmartphone/GSM/Device: SetAntennaPower failed:
org.freesmartphone.Resource.NotEnabled
Registering
/org/freesmartphone/GSM/Device: Register failed:
org.freesmartphone.Resource.NotEnabled


And then any time after that, I get:
Enabling GSM for ever
/org/freesmartphone/Usage: SetResourcePolicy failed:
org.freesmartphone.Usage.ResourceUnknown
Turning antenna on
/org/freesmartphone/GSM/Device: SetAntennaPower failed:
org.freesmartphone.Resource.NotEnabled
Registering
/org/freesmartphone/GSM/Device: Register failed:
org.freesmartphone.Resource.NotEnabled


I assumed that perhaps I just needed to restart frameworkd...but that didnt
help.  Has anyone else experienced this?  Am I just missing something?

Thanks,
-Dan Staley

On Mon, Jul 27, 2009 at 6:27 PM, Michal Brzozowski ruso...@poczta.fmwrote:

 Hi,

 I gave it a try and wrote an FSO based phone app in Qt. It's using the new
 PIM service, and since that's not completely stable yet, there are a few
 problems. I'm releasing this anyway, to help test FSO, and meanwhile get
 some feedback on the gui and general idea. Consider it an alpha release.
 There might be little bugs here and there.

 The basic idea on the GUI is that it is packed in one window, the various
 'modules' (contacts, messages, dialer, etc) placed into tabs. No popup
 windows.
 Screenshot:
 http://pvtrace.com/litephone/litephone1.png

 The best way to use it on SHR is to stop ophoned, turn on the GSM service
 and register by hand, wait for some initialization in opimd, and then start
 the phone app. Technically you can just start the phone, and it will init
 GSM, but due to a bug in opimd, messages and contacts will start duplicating
 when you exit and run it again.

 The steps:
  - Install all the ipks from http://pvtrace.com/litephone/ (qt deps and
 phone app itself).
  - Run /etc/init.d/x-something stop
  - Move /etc/X11/Xsession.d/80ophonekitd somewhere else (like your home
 dir).
  - Run the script http://pvtrace.com/litephone/gsm_register.sh (this will
 enable gsm and register, and will stay like that until you turn it off by
 hand)
  - Run /etc/init.d/x-something start
  - Get the style definition http://pvtrace.com/litephone/style_sheet.conf
  - Run 'phone style_sheet.conf'

 If you don't see your contacts and messages, try exiting and running again.
 opimd does some initialization upon GSM start that takes 1-2 minutes and
 currently there is no signal implemented that notifies about it.

 Making and receiving calls and messages should work without problems. You
 can add, edit and delete contacts, but deleting messages doesn't work
 because it's not implemented in opimd yet.

 Scrolling lists (contacts, etc) is done by click, not by drag (I hate
 drag-scrolling). Contacts have a smaller sparse list on the right that
 lets you scroll faster.

 The way composing new messages works is when you hit 'text' or 'reply'
 somewhere and a 'compose' tab is not created yet, it creates one with an
 appropriate recipient. If one is open already, it just adds to the list of
 recipients. So the way to send a message to multiple recipients is to keep
 going back to Contacts for example, and add them one by one. While it's not
 very intuitive, it's simple and it works :-)

 I hope you have fun
 Michal

 ___
 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: testing Litephone, new phone interface

2009-08-14 Thread Dan Staley
Opps.  Forget I said anything.  I DID just need to restart frameworkdI
just needed to wait longer for it to finish initializing.

-Dan Staley


On Fri, Aug 14, 2009 at 10:58 AM, Dan Staley daniel.l.sta...@gmail.comwrote:

 Hi, I decided I wanted to try out litephone on the latest SHR-U and I
 followed the steps above.  However whenever I run the gsm registering script
 I run into problems.

 The first time I run it, I get:
 Enabling GSM for ever
 /org/freesmartphone/Usage: SetResourcePolicy failed:
 org.freedesktop.DBus.Error.NoReply
 Turning antenna on
 /org/freesmartphone/GSM/Device: SetAntennaPower failed:
 org.freesmartphone.Resource.NotEnabled
 Registering
 /org/freesmartphone/GSM/Device: Register failed:
 org.freesmartphone.Resource.NotEnabled


 And then any time after that, I get:
 Enabling GSM for ever
 /org/freesmartphone/Usage: SetResourcePolicy failed:
 org.freesmartphone.Usage.ResourceUnknown
 Turning antenna on
 /org/freesmartphone/GSM/Device: SetAntennaPower failed:
 org.freesmartphone.Resource.NotEnabled
 Registering
 /org/freesmartphone/GSM/Device: Register failed:
 org.freesmartphone.Resource.NotEnabled


 I assumed that perhaps I just needed to restart frameworkd...but that didnt
 help.  Has anyone else experienced this?  Am I just missing something?

 Thanks,
 -Dan Staley

 On Mon, Jul 27, 2009 at 6:27 PM, Michal Brzozowski ruso...@poczta.fmwrote:

 Hi,

 I gave it a try and wrote an FSO based phone app in Qt. It's using the new
 PIM service, and since that's not completely stable yet, there are a few
 problems. I'm releasing this anyway, to help test FSO, and meanwhile get
 some feedback on the gui and general idea. Consider it an alpha release.
 There might be little bugs here and there.

 The basic idea on the GUI is that it is packed in one window, the various
 'modules' (contacts, messages, dialer, etc) placed into tabs. No popup
 windows.
 Screenshot:
 http://pvtrace.com/litephone/litephone1.png

 The best way to use it on SHR is to stop ophoned, turn on the GSM service
 and register by hand, wait for some initialization in opimd, and then start
 the phone app. Technically you can just start the phone, and it will init
 GSM, but due to a bug in opimd, messages and contacts will start duplicating
 when you exit and run it again.

 The steps:
  - Install all the ipks from http://pvtrace.com/litephone/ (qt deps and
 phone app itself).
  - Run /etc/init.d/x-something stop
  - Move /etc/X11/Xsession.d/80ophonekitd somewhere else (like your home
 dir).
  - Run the script http://pvtrace.com/litephone/gsm_register.sh (this will
 enable gsm and register, and will stay like that until you turn it off by
 hand)
  - Run /etc/init.d/x-something start
  - Get the style definition http://pvtrace.com/litephone/style_sheet.conf
  - Run 'phone style_sheet.conf'

 If you don't see your contacts and messages, try exiting and running
 again. opimd does some initialization upon GSM start that takes 1-2 minutes
 and currently there is no signal implemented that notifies about it.

 Making and receiving calls and messages should work without problems. You
 can add, edit and delete contacts, but deleting messages doesn't work
 because it's not implemented in opimd yet.

 Scrolling lists (contacts, etc) is done by click, not by drag (I hate
 drag-scrolling). Contacts have a smaller sparse list on the right that
 lets you scroll faster.

 The way composing new messages works is when you hit 'text' or 'reply'
 somewhere and a 'compose' tab is not created yet, it creates one with an
 appropriate recipient. If one is open already, it just adds to the list of
 recipients. So the way to send a message to multiple recipients is to keep
 going back to Contacts for example, and add them one by one. While it's not
 very intuitive, it's simple and it works :-)

 I hope you have fun
 Michal

 ___
 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: testing Litephone, new phone interface

2009-08-14 Thread Michal Brzozowski
Oh, you don't need the script anymore. This issue happens when frameworkd
hasn't powered up yet (it takes a few minutes).

Check the newest litephone package from http://pvtrace.com/litephone/

It should wait for frameworkd to start up.

2009/8/14 Dan Staley daniel.l.sta...@gmail.com

 Hi, I decided I wanted to try out litephone on the latest SHR-U and I
 followed the steps above.  However whenever I run the gsm registering script
 I run into problems.

 The first time I run it, I get:
 Enabling GSM for ever
 /org/freesmartphone/Usage: SetResourcePolicy failed:
 org.freedesktop.DBus.Error.NoReply
 Turning antenna on
 /org/freesmartphone/GSM/Device: SetAntennaPower failed:
 org.freesmartphone.Resource.NotEnabled
 Registering
 /org/freesmartphone/GSM/Device: Register failed:
 org.freesmartphone.Resource.NotEnabled


 And then any time after that, I get:
 Enabling GSM for ever
 /org/freesmartphone/Usage: SetResourcePolicy failed:
 org.freesmartphone.Usage.ResourceUnknown
 Turning antenna on
 /org/freesmartphone/GSM/Device: SetAntennaPower failed:
 org.freesmartphone.Resource.NotEnabled
 Registering
 /org/freesmartphone/GSM/Device: Register failed:
 org.freesmartphone.Resource.NotEnabled


 I assumed that perhaps I just needed to restart frameworkd...but that didnt
 help.  Has anyone else experienced this?  Am I just missing something?

 Thanks,
 -Dan Staley

 On Mon, Jul 27, 2009 at 6:27 PM, Michal Brzozowski ruso...@poczta.fmwrote:

 Hi,

 I gave it a try and wrote an FSO based phone app in Qt. It's using the new
 PIM service, and since that's not completely stable yet, there are a few
 problems. I'm releasing this anyway, to help test FSO, and meanwhile get
 some feedback on the gui and general idea. Consider it an alpha release.
 There might be little bugs here and there.

 The basic idea on the GUI is that it is packed in one window, the various
 'modules' (contacts, messages, dialer, etc) placed into tabs. No popup
 windows.
 Screenshot:
 http://pvtrace.com/litephone/litephone1.png

 The best way to use it on SHR is to stop ophoned, turn on the GSM service
 and register by hand, wait for some initialization in opimd, and then start
 the phone app. Technically you can just start the phone, and it will init
 GSM, but due to a bug in opimd, messages and contacts will start duplicating
 when you exit and run it again.

 The steps:
  - Install all the ipks from http://pvtrace.com/litephone/ (qt deps and
 phone app itself).
  - Run /etc/init.d/x-something stop
  - Move /etc/X11/Xsession.d/80ophonekitd somewhere else (like your home
 dir).
  - Run the script http://pvtrace.com/litephone/gsm_register.sh (this will
 enable gsm and register, and will stay like that until you turn it off by
 hand)
  - Run /etc/init.d/x-something start
  - Get the style definition http://pvtrace.com/litephone/style_sheet.conf
  - Run 'phone style_sheet.conf'

 If you don't see your contacts and messages, try exiting and running
 again. opimd does some initialization upon GSM start that takes 1-2 minutes
 and currently there is no signal implemented that notifies about it.

 Making and receiving calls and messages should work without problems. You
 can add, edit and delete contacts, but deleting messages doesn't work
 because it's not implemented in opimd yet.

 Scrolling lists (contacts, etc) is done by click, not by drag (I hate
 drag-scrolling). Contacts have a smaller sparse list on the right that
 lets you scroll faster.

 The way composing new messages works is when you hit 'text' or 'reply'
 somewhere and a 'compose' tab is not created yet, it creates one with an
 appropriate recipient. If one is open already, it just adds to the list of
 recipients. So the way to send a message to multiple recipients is to keep
 going back to Contacts for example, and add them one by one. While it's not
 very intuitive, it's simple and it works :-)

 I hope you have fun
 Michal

 ___
 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: testing Litephone, new phone interface

2009-08-05 Thread Helge Hafting
Michal Brzozowski wrote:
 2009/8/3 Helge Hafting helge.haft...@hist.no 
 mailto:helge.haft...@hist.no
 
 Michal Brzozowski wrote:
 
   Litephone beta1 is available here:
   http://pvtrace.com/litephone/litephone_0.0.1-r2_armv4t.ipk
 
 Beta impressions:
 
 * When the phone rings, please have litephone jump to the foreground.
   Currently, I have to wade through several other running apps in order
   to pick up the phone.
 
 
 I was wondering when someone brings this up :-). Actually I don't like 
 the idea of poping up the phone window when the user is doing something. 

Normally, I am very much against popups, because they interrupt other 
work. A ringing phone is different. It is already an interruption, and
one that has to be handled in real-time too.

If I don't want to answer, I still want to reject the call. So I
need some sort of UI when it rings, and it had better not be cumbersome 
just because some other app was on top. Of course, a popup is not
the only way.

I have been thinking that since this is a _phone_, then perhaps the AUX
button should pick up the phone whenever it rings, and hang up whenever
there is a call in progress. That would get rid of many problems. In 
particular, one doesn't even have to look at the screen at all.

Other popular uses for AUX could still work - when there isn't a call
in progress. It is not as if I tend to lock the screen while talking...


 I have a plan to show a little xshape gadget on the bottom of the screen 
 on incoming call or sms. On call it would probably show 
 accept/reject/mute buttons, the first one additonally bringing up the 
 phone window on click. On sms it would display the content in a one line 
 pager style, and have show/hide message buttons.
 
 I wonder what you think about this idea :-)

That seems ok too.

 * Deleting a message (up-to-date SHR unstable) gives a screenful
   of error messages. But the message was deleted.
 
 
 Yes, although I think deleting did work for a while.
 
 Here's the error (for Sebastian :-)):
 http://pvtrace.com/litephone/delete_errors.txt
 
 The message was probably not deleted, you will notice on restarting 
 litephone (it just deleted it from cache)

I noticed it showed up in shr messages.

Helge Hafting

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


Re: testing Litephone, new phone interface

2009-08-03 Thread Helge Hafting
Michal Brzozowski wrote:

 Litephone beta1 is available here:
 http://pvtrace.com/litephone/litephone_0.0.1-r2_armv4t.ipk

Beta impressions:

* When the phone rings, please have litephone jump to the foreground.
   Currently, I have to wade through several other running apps in order
   to pick up the phone.

   Also, if some other program were in the foreground, remember that.
   Litephone should then reinstate the previous foreground app
   when the call ends.

   This is what you want if you use the phone as a gps map display,
   or play some game. You want to pick up the phone, but
   when you hang up, you want to continue with whatever you were doing.

* Similiar for SMS. Bring litephone to the foreground, if necessary.
   If the user just close/delete the message, then reinstate the
   previous foreground app. (But if the user do anything else in
   litephone, assume he/she wants to keep litephone in the
   foreground from now on. We don't want to do all sorts of
   work and suddenly have litephone disappear upon deleting the
   particular message that trigged the jump to the foreground. :-)

* Deleting a message (up-to-date SHR unstable) gives a screenful
   of error messages. But the message was deleted.

* When I answer the phone, it rings and vibrates for a while after
   I pressed answer, before the call comes through. That is annoying.
   I don't know if this can be improved in litephone, or if the
   problem is in the framework or something.

* The contact list has a second column, with 8 names. This allows
   quick jumping through the list to various positions. Excellent!

* Strange SMS view. Before, I could see who sent the message, and
   the first part of the text. And often enough, the first part is
   all I need to see. Some messages are short, just call me and such.

   Now, I see who sent the message, and a strange number. (database
   key???)  This number is not useful, please bring back the
   text snippet.

* Really long messages support scrolling. This is better than SHR. :-)

* When the user closes litephone, consider informing that
   no further calls or SMS will be received. This may not be obvious to
   all users, and phone functionality is an important part of the device.
   Still, if you make such a dialog, also add the
   don't show this warning again button for the expert users.


I might add this to the wiki - when/if the email address confirmation
comes through. :-/

Helge Hafting

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


Re: testing Litephone, new phone interface

2009-08-03 Thread Michal Brzozowski
2009/8/3 Helge Hafting helge.haft...@hist.no

 Michal Brzozowski wrote:

  Litephone beta1 is available here:
  http://pvtrace.com/litephone/litephone_0.0.1-r2_armv4t.ipk

 Beta impressions:

 * When the phone rings, please have litephone jump to the foreground.
   Currently, I have to wade through several other running apps in order
   to pick up the phone.


I was wondering when someone brings this up :-). Actually I don't like the
idea of poping up the phone window when the user is doing something. I have
a plan to show a little xshape gadget on the bottom of the screen on
incoming call or sms. On call it would probably show accept/reject/mute
buttons, the first one additonally bringing up the phone window on click. On
sms it would display the content in a one line pager style, and have
show/hide message buttons.

I wonder what you think about this idea :-)



 * Deleting a message (up-to-date SHR unstable) gives a screenful
   of error messages. But the message was deleted.


Yes, although I think deleting did work for a while.

Here's the error (for Sebastian :-)):
http://pvtrace.com/litephone/delete_errors.txt

The message was probably not deleted, you will notice on restarting
litephone (it just deleted it from cache)



 * When I answer the phone, it rings and vibrates for a while after
   I pressed answer, before the call comes through. That is annoying.
   I don't know if this can be improved in litephone, or if the
   problem is in the framework or something.


This is a frameworkd issue. I think with litephone it's a bit better than
with SHR-apps, although I'm not sure.



 * The contact list has a second column, with 8 names. This allows
   quick jumping through the list to various positions. Excellent!

 * Strange SMS view. Before, I could see who sent the message, and
   the first part of the text. And often enough, the first part is
   all I need to see. Some messages are short, just call me and such.

   Now, I see who sent the message, and a strange number. (database
   key???)  This number is not useful, please bring back the
   text snippet.


This was left by accident after debugging, sorry :-)
We are working on some better view in messages, phonelog and contacts



 * Really long messages support scrolling. This is better than SHR. :-)


Oh, good to know :-)




 * When the user closes litephone, consider informing that
   no further calls or SMS will be received. This may not be obvious to
   all users, and phone functionality is an important part of the device.
   Still, if you make such a dialog, also add the
   don't show this warning again button for the expert users.


 I might add this to the wiki - when/if the email address confirmation
 comes through. :-/


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


Re: testing Litephone, new phone interface

2009-08-03 Thread Timo Juhani Lindfors
Michal Brzozowski ruso...@poczta.fm writes:
  - Install all the ipks from http://pvtrace.com/litephone/ (qt deps and
 phone app itself).

Where's the source code?



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


Re: testing Litephone, new phone interface

2009-08-03 Thread Michal Brzozowski
http://www.sf.net/projects/litephone

2009/8/3 Timo Juhani Lindfors timo.lindf...@iki.fi

 Michal Brzozowski ruso...@poczta.fm writes:
   - Install all the ipks from http://pvtrace.com/litephone/ (qt deps and
  phone app itself).

 Where's the source code?



 ___
 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: testing Litephone, new phone interface

2009-08-03 Thread Al Johnson
On Monday 03 August 2009, Michal Brzozowski wrote:
 2009/8/3 Helge Hafting helge.haft...@hist.no

  Michal Brzozowski wrote:
   Litephone beta1 is available here:
   http://pvtrace.com/litephone/litephone_0.0.1-r2_armv4t.ipk
 
  Beta impressions:
 
  * When the phone rings, please have litephone jump to the foreground.
Currently, I have to wade through several other running apps in order
to pick up the phone.

 I was wondering when someone brings this up :-). Actually I don't like the
 idea of poping up the phone window when the user is doing something. I have
 a plan to show a little xshape gadget on the bottom of the screen on
 incoming call or sms. On call it would probably show accept/reject/mute
 buttons, the first one additonally bringing up the phone window on click.
 On sms it would display the content in a one line pager style, and have
 show/hide message buttons.

That sounds much better than popping up the phone window. Remember to make 
sure these appear somewhere other than where the keyboard is though!

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


Re: testing Litephone, new phone interface

2009-08-03 Thread Timo Juhani Lindfors
Michal Brzozowski ruso...@poczta.fm writes:
 http://www.sf.net/projects/litephone

Thanks, here's a list of comments:

1) Icons in Png directory are under Creative Commons license, created
   by Axialis Team, axialis.com. says README. There are multiple CC
   licenses, which one is this?

1) Same for source code. Even though the sourceforge project page says
   GPL you really should specify the license in the source repository
   too.

3) Would be nice to have at least minimal compilation instruction for
   those who don't have an offline copy of the wiki. Here's a patch:

Index: README
===
--- README  (revision 12)
+++ README  (working copy)
@@ -1,3 +1,8 @@
-This is the Litephone source distribution. Read 
http://wiki.openmoko.org/wiki/Developing_with_C%2B%2B_and_Qt for compile 
instructions.
+This is the Litephone source distribution. Read 
http://wiki.openmoko.org/wiki/Developing_with_C%2B%2B_and_Qt for compile 
instructions. If you are not cross-compiling you can just

+1) qmake-qt4
+2) make
+
+and then run the ./litephone executable. There is no install target currently.
+
 Icons in Png directory are under Creative Commons license, created by Axialis 
Team, axialis.com.


4) There's no --help: User needs to read the source to discover demo
   and nogsm modes. Consider something like


Index: main.cpp
===
--- main.cpp(revision 12)
+++ main.cpp(working copy)
@@ -6,6 +6,7 @@
 #include QDateTime
 #include QInputDialog
 #include QMessageBox
+#include iostream

 #include logger.h

@@ -931,7 +932,10 @@
phone.enableMockGsm();
 else if (argc  1  QString(argv[1]) == nogsm)
phone.disableGsm();
-else
+else if (argc  1  QString(argv[1]) == --help){
+std::cout  usage: litephone [demo|nogsm]  std::endl;
+return 0;
+} else
phone.enableGsm();

 return a.exec();


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


Re: testing Litephone, new phone interface

2009-07-31 Thread Michal Brzozowski
2009/7/30 Michal Brzozowski ruso...@poczta.fm


 About the crashes. My experience is that in only (and always) crashes when
 there's an error from FSO. So I'll upgrade the GUI to display the FSO error
 instead of crashing, and then we will be able to work on finding the
 problem. Some of the crashes I've already identified and they will be fixed
 in todays release.


Litephone beta1 is available here:
http://pvtrace.com/litephone/litephone_0.0.1-r2_armv4t.ipk

Changes:
 - don't crash on FSO errors, display them in an error console tab instead
 - PIN authorization, PIN changing, PIN authorization toggle
 - switching profiles
 - fixed some bugs that have been pointed out (probably not all)
 - don't need the gsm_register script anymore.

PIN entering is a bit lame now, I'll work on it a little bit.

Note: if you see duplicated contacts and messages, this is a bug in opimd.
Message deleting is, I think, still unimplemented.

Have fun,
Michal
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: testing Litephone, new phone interface

2009-07-31 Thread Sebastian Krzyszkowiak
On Fri, Jul 31, 2009 at 17:05, Michal Brzozowskiruso...@poczta.fm wrote:
 Note: if you see duplicated contacts and messages, this is a bug in opimd.
 Message deleting is, I think, still unimplemented.

Both things are fixed and package is now in repo.

-- 
Sebastian Krzyszkowiak
dos

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


Re: testing Litephone, new phone interface

2009-07-31 Thread KaZeR



rusolis wrote:
 
 2009/7/30 Michal Brzozowski ruso...@poczta.fm
 
 Litephone beta1 is available here:
 http://pvtrace.com/litephone/litephone_0.0.1-r2_armv4t.ipk
 
 

What about creating a repo ?
-- 
View this message in context: 
http://n2.nabble.com/testing-Litephone%2C-new-phone-interface-tp3336730p3363281.html
Sent from the Openmoko Community mailing list archive at Nabble.com.

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


Re: testing Litephone, new phone interface

2009-07-31 Thread Sebastian Krzyszkowiak
On Fri, Jul 31, 2009 at 17:05, Michal Brzozowskiruso...@poczta.fm wrote:
 2009/7/30 Michal Brzozowski ruso...@poczta.fm

 About the crashes. My experience is that in only (and always) crashes when
 there's an error from FSO. So I'll upgrade the GUI to display the FSO error
 instead of crashing, and then we will be able to work on finding the
 problem. Some of the crashes I've already identified and they will be fixed
 in todays release.

 Litephone beta1 is available here:
 http://pvtrace.com/litephone/litephone_0.0.1-r2_armv4t.ipk

 Changes:
  - don't crash on FSO errors, display them in an error console tab instead
  - PIN authorization, PIN changing, PIN authorization toggle
  - switching profiles
  - fixed some bugs that have been pointed out (probably not all)
  - don't need the gsm_register script anymore.

 PIN entering is a bit lame now, I'll work on it a little bit.

 Note: if you see duplicated contacts and messages, this is a bug in opimd.
 Message deleting is, I think, still unimplemented.

 Have fun,
 Michal

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



INFO: New dbus call: org.freesmartphone.ogsmd
/org/freesmartphone/GSM/Device org.freesmartphone.GSM.SIM
GetAuthCodeRequired;

You shouldn't use GetAuthCodeRequired, that's call for settings app.
You should listen to AuthStatus signal and check, if value is 'SIM
PIN' - then display PIN dialog.

Here new version of litephone still crashes. It reads contacts and few
messages, but it fails after that with:

INFO: New dbus call: org.freesmartphone.opimd
/org/freesmartphone/PIM/Messages/Queries/3
org.freesmartphone.PIM.MessageQuery GetResult;
Using **pending_return in dbus_connection_send_with_reply_setup()
without pending_setup is deprecated and strongly discouraged
INFO: Call was succesful
QDBusArgument: write from a read-only object
QDBusArgument: write from a read-only object
FATAL: data.cpp: 79 : void Data::sort(const QString, bool): check
failed: row.getValue(column, value):

You should provide more debug info, now I can't even see on which
message it crashes.

-- 
Sebastian Krzyszkowiak
dos

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


Re: testing Litephone, new phone interface

2009-07-31 Thread Michal Brzozowski
You are right, there should be more info, and it shouldn't crash, just
display the error in console. Looking at the error and source code, I think
the message is missing a Timestamp value. Is it possible?

2009/7/31 Sebastian Krzyszkowiak seba.d...@gmail.com


 Here new version of litephone still crashes. It reads contacts and few
 messages, but it fails after that with:

 INFO: New dbus call: org.freesmartphone.opimd
 /org/freesmartphone/PIM/Messages/Queries/3
 org.freesmartphone.PIM.MessageQuery GetResult;
 Using **pending_return in dbus_connection_send_with_reply_setup()
 without pending_setup is deprecated and strongly discouraged
 INFO: Call was succesful
 QDBusArgument: write from a read-only object
 QDBusArgument: write from a read-only object
 FATAL: data.cpp: 79 : void Data::sort(const QString, bool): check
 failed: row.getValue(column, value):

 You should provide more debug info, now I can't even see on which
 message it crashes.

 --
 Sebastian Krzyszkowiak
 dos

 ___
 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: testing Litephone, new phone interface

2009-07-31 Thread Sebastian Krzyszkowiak
On Fri, Jul 31, 2009 at 17:29, Michal Brzozowskiruso...@poczta.fm wrote:
 You are right, there should be more info, and it shouldn't crash, just
 display the error in console. Looking at the error and source code, I think
 the message is missing a Timestamp value. Is it possible?

 2009/7/31 Sebastian Krzyszkowiak seba.d...@gmail.com


 Here new version of litephone still crashes. It reads contacts and few
 messages, but it fails after that with:

 INFO: New dbus call: org.freesmartphone.opimd
 /org/freesmartphone/PIM/Messages/Queries/3
 org.freesmartphone.PIM.MessageQuery GetResult;
 Using **pending_return in dbus_connection_send_with_reply_setup()
 without pending_setup is deprecated and strongly discouraged
 INFO: Call was succesful
 QDBusArgument: write from a read-only object
 QDBusArgument: write from a read-only object
 FATAL: data.cpp: 79 : void Data::sort(const QString, bool): check
 failed: row.getValue(column, value):

 You should provide more debug info, now I can't even see on which
 message it crashes.

 --
 Sebastian Krzyszkowiak
 dos

It's possible, you shouldn't rely on it.

-- 
Sebastian Krzyszkowiak
dos

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


Re: testing Litephone, new phone interface

2009-07-31 Thread Michal Brzozowski
2009/7/31 Sebastian Krzyszkowiak seba.d...@gmail.com


  the message is missing a Timestamp value. Is it possible?



 It's possible, you shouldn't rely on it.


And how do I sort the messages then? Can you make a list of optional and
required fields?
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: testing Litephone, new phone interface

2009-07-31 Thread Sebastian Krzyszkowiak
On Fri, Jul 31, 2009 at 17:46, Michal Brzozowskiruso...@poczta.fm wrote:
 2009/7/31 Sebastian Krzyszkowiak seba.d...@gmail.com

  the message is missing a Timestamp value. Is it possible?



 It's possible, you shouldn't rely on it.

 And how do I sort the messages then? Can you make a list of optional and
 required fields?

I can't. In opimd you can store different types of messages: SMS, MMS,
IM, mails... Every type can have different fields. Just don't display
missing fields.

About sorting - I want to implement sorting in opimd soon by '_sortby'
field in query. And timestamps should be present on majority of
messages, but it's possible they won't be, so just leave it blank when
displaying and display that messages at end of list.

-- 
Sebastian Krzyszkowiak
dos

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


Re: testing Litephone, new phone interface

2009-07-31 Thread Michael 'Mickey' Lauer
Am Dienstag, den 28.07.2009, 15:10 +0200 schrieb Petr Vanek:
 I already have volume slider in libframeworkd-phonegui-efl, but now
 there is just no way to have volume handled correctly, so it can't be
 done now. If it is somewhere (Paroli, LitePhone), then it's done
 wrongly.
 
 so what is The right way of controlling volume?

The correct way to control volume is to associate a main volume control
for each and every scenario and then control main volume via FSO.

(This is work in progress)

:M:



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


Re: testing Litephone, new phone interface

2009-07-31 Thread Petr Vanek
 I already have volume slider in libframeworkd-phonegui-efl, but now
 there is just no way to have volume handled correctly, so it can't
 be done now. If it is somewhere (Paroli, LitePhone), then it's done
 wrongly.
 
 so what is The right way of controlling volume?

The correct way to control volume is to associate a main volume control
for each and every scenario and then control main volume via FSO.

(This is work in progress)

this is indeed a good news then.

Petr


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


Re: testing Litephone, new phone interface

2009-07-30 Thread Helge Hafting
KaZeR wrote:
[...]
 I believe that the style_sheet part isn't needed anymore, and instead you
 can use other parameters (like demo, etc).
 I simply ran litephone, in my case and it worked.

Thanks, that worked.

My impressions after testing a bit:

* Looks good, is responsive

* The contact list doesn't have finger scrolling. It jumps when I
   select a message close to the bottom though.

   Finger scrolling is even easier. Just put the finger on the screen
   and drag up or down as necessary.

* Calling and receiving works, but is fragile. Once, litephone didn't
   notice that the other end hung up. The call was terminated, and when
   the other side called back, litephone still was stuck with the
   screen for the previous call.

   I could not reproduce this though, further calls worked
   as expected.

* Entering unicode text into a message doesn't work, I get
   garbage text instead. Strange, because
   stored unicode messages show up fine in the viewer. Most of the
   world uses more than ascii. The shr messaging app has no problems
   with this.

* There seems to be no way to forward a message to others. Shr messaging
   also lack this, you have the chance to be first. :-)

* Messages cannot be deleted. (Not implemented yet?)
   Please note that the inbox can accumulate lots of messages quickly.
   Deleting one-by-one is fine for deleting a few messages, but
   cumbersome for many. This is a typical problem with many
   phones - click once to select, click once to delete, then wait
   as deletion happens, then click to select, click to delete, wait ...
   Still - you're better than shr with its 3-click deletion.

   Mass deletion is very useful. One way is to have a little checkbox
   at the end of each message in the list. One can then check
   several messages quickly, and hit delete to get rid of
   them all. This way, the user don't have to wait for
   each deletion. If deleting 50 messages is slow, then the
   user simply pockets the phone or play a game while waiting. :-)



===
Crashes:

I tried to save my changes to a contact, and litephone died.
(The contact name contained parentheses, I hope that
  didn't crash it.)
Restarting it worked.

After sending myself some messages, litephone crashed and
can no longer be started on my phone. I get:
INFO: refresh msgs
FATAL: main.cpp: 236 : void PhoneWindow::refreshMessages(): check 
failed: messages.getRow(i).getValue(Content, content):
Deleting the messages through shr-messages did not help.
I'll try again when there is an updated version.


Helge Hafting

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


Re: testing Litephone, new phone interface

2009-07-30 Thread Sebastian Krzyszkowiak
On Thu, Jul 30, 2009 at 07:57, Michal Brzozowskiruso...@poczta.fm wrote:
 The updating contact issues I know about, and it's fixed for beta release.
 If Sebastian has implemented Message.Delete in opimd, then the release
 should have full functionality.

I think it's implemented, but you should test it anyway.

 Sebastian, did you fix the data duplication bug already?

I think it's fixed, but you should test it anyway :D

-- 
Sebastian Krzyszkowiak
dos

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


Re: testing Litephone, new phone interface

2009-07-30 Thread Sebastian Krzyszkowiak
On Thu, Jul 30, 2009 at 12:21, Helge Haftinghelge.haft...@hist.no wrote:
 * Messages cannot be deleted. (Not implemented yet?)

For that wait for frameworkd upgrade.

 Deleting the messages through shr-messages did not help.

It can't help at all, as libframeworkd-phonegui-efl doesn't use opimd yet.

-- 
Sebastian Krzyszkowiak
dos

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


Re: testing Litephone, new phone interface

2009-07-30 Thread Michal Brzozowski
Thanks Helge, this is very helpful. I agree with all the feature requests.
Could you please put them on the wiki [1]?

About the crashes. My experience is that in only (and always) crashes when
there's an error from FSO. So I'll upgrade the GUI to display the FSO error
instead of crashing, and then we will be able to work on finding the
problem. Some of the crashes I've already identified and they will be fixed
in todays release.

[1] http://wiki.openmoko.org/wiki/Litephone

Michal


2009/7/30 Helge Hafting helge.haft...@hist.no

 KaZeR wrote:
 [...]

 I believe that the style_sheet part isn't needed anymore, and instead you
 can use other parameters (like demo, etc).
 I simply ran litephone, in my case and it worked.


 Thanks, that worked.

 My impressions after testing a bit:

 * Looks good, is responsive

 * The contact list doesn't have finger scrolling. It jumps when I
  select a message close to the bottom though.

  Finger scrolling is even easier. Just put the finger on the screen
  and drag up or down as necessary.

 * Calling and receiving works, but is fragile. Once, litephone didn't
  notice that the other end hung up. The call was terminated, and when
  the other side called back, litephone still was stuck with the
  screen for the previous call.

  I could not reproduce this though, further calls worked
  as expected.

 * Entering unicode text into a message doesn't work, I get
  garbage text instead. Strange, because
  stored unicode messages show up fine in the viewer. Most of the
  world uses more than ascii. The shr messaging app has no problems
  with this.

 * There seems to be no way to forward a message to others. Shr messaging
  also lack this, you have the chance to be first. :-)

 * Messages cannot be deleted. (Not implemented yet?)
  Please note that the inbox can accumulate lots of messages quickly.
  Deleting one-by-one is fine for deleting a few messages, but
  cumbersome for many. This is a typical problem with many
  phones - click once to select, click once to delete, then wait
  as deletion happens, then click to select, click to delete, wait ...
  Still - you're better than shr with its 3-click deletion.

  Mass deletion is very useful. One way is to have a little checkbox
  at the end of each message in the list. One can then check
  several messages quickly, and hit delete to get rid of
  them all. This way, the user don't have to wait for
  each deletion. If deleting 50 messages is slow, then the
  user simply pockets the phone or play a game while waiting. :-)



 ===
 Crashes:

 I tried to save my changes to a contact, and litephone died.
 (The contact name contained parentheses, I hope that
  didn't crash it.)
 Restarting it worked.

 After sending myself some messages, litephone crashed and
 can no longer be started on my phone. I get:
 INFO: refresh msgs
 FATAL: main.cpp: 236 : void PhoneWindow::refreshMessages(): check failed:
 messages.getRow(i).getValue(Content, content):
 Deleting the messages through shr-messages did not help.
 I'll try again when there is an updated version.


 Helge Hafting


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


Re: testing Litephone, new phone interface

2009-07-30 Thread Pieter Colpaert
Hi!

I've been testing it too. Though, I lack add this number to your
contacts buttons. For instance when you just messaged a friend, there is
no way of adding him to your contacts.

Good app though! Very promising, I'm shocked I like qt that much ;)

Pieter

On Thu, 2009-07-30 at 07:57 +0200, Michal Brzozowski wrote:
 2009/7/29 KaZeR ka...@altern.org
 
 Hello list.
 
 I've tested litephone, and i like the concept behind it.
 Switching from
 contacts to messages to phone logs is done in a breath. I also
 like the
 possibility to change the volume during call, even if it's not
 done in the
 cleaner way : at least, it works. Scrolling is a bit awkward
 at the
 beginning but with the shortcuts on the right side you can
 find a contact in
 a 120+ list quite fast.
 
 Only issue i noticed so far : keypad doesn't work in calls : i
 called my
 voice mail and was unable to navigate in its menu.
 
 Also, deleting sms can be done using
 org.freesmartphone.GSM.SIM.DeleteMessage(int(message)) : it
 could be useful
 :)
 
 Otherwise, very promising app. Please convert
 http://pvtrace.com/litephone/
 into a repository so that i can keep it up to date easily.
 
 Thanks for testing! I wasn't aware of the keypad issue, actually I
 forgot you should be able to use during calls :-), I'll fix it.
 
 The updating contact issues I know about, and it's fixed for beta
 release. If Sebastian has implemented Message.Delete in opimd, then
 the release should have full functionality.
 
 The beta release should come later today (european time :-)).
 
 Sebastian, did you fix the data duplication bug already?
 


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


Re: testing Litephone, new phone interface

2009-07-29 Thread KaZeR

Hello list.

I've tested litephone, and i like the concept behind it. Switching from
contacts to messages to phone logs is done in a breath. I also like the
possibility to change the volume during call, even if it's not done in the
cleaner way : at least, it works. Scrolling is a bit awkward at the
beginning but with the shortcuts on the right side you can find a contact in
a 120+ list quite fast.

Only issue i noticed so far : keypad doesn't work in calls : i called my
voice mail and was unable to navigate in its menu.

Also, deleting sms can be done using
org.freesmartphone.GSM.SIM.DeleteMessage(int(message)) : it could be useful
:)

Otherwise, very promising app. Please convert http://pvtrace.com/litephone/
into a repository so that i can keep it up to date easily.
-- 
View this message in context: 
http://n2.nabble.com/testing-Litephone%2C-new-phone-interface-tp3336730p3349281.html
Sent from the Openmoko Community mailing list archive at Nabble.com.

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


Re: testing Litephone, new phone interface

2009-07-29 Thread KaZeR

Ah, i had a crash when updating a contact :)

INFO: Updating contact
INFO: New dbus call: org.freesmartphone.opimd
/org/freesmartphone/PIM/Contacts org.freesmartphone.PIM.Contacts Query;
Using **pending_return in dbus_connection_send_with_reply_setup() without
pending_setup is deprecated and strongly discouraged
FATAL: DBus error: org.freedesktop.DBus.Python.sre_constants.error Traceback
(most recent call last):
  File /usr/lib/python2.6/site-packages/dbus/service.py, line 702, in
_message_cb
retval = candidate_method(self, *args, **keywords)
  File
/usr/lib/python2.6/site-packages/framework/subsystems/opimd/pimd_contacts.py,
line 874, in Query
return self.query_manager.process_query(query, sender)
  File
/usr/lib/python2.6/site-packages/framework/subsystems/opimd/pimd_contacts.py,
line 630, in process_query
query_handler = SingleQueryHandler(query, self._contacts, dbus_sender)
  File
/usr/lib/python2.6/site-packages/framework/subsystems/opimd/pimd_contacts.py,
line 437, in __init__
self.entries = matcher.match(self._contacts)
  File
/usr/lib/python2.6/site-packages/framework/subsystems/opimd/pimd_contacts.py,
line 75, in match
match = contact.match_query(self.query_obj)
  File
/usr/lib/python2.6/site-packages/framework/subsystems/opimd/pimd_contacts.py,
line 370, in match_query
matcher = re.compile(field_value)
  File /usr/lib/python2.6/re.py, line 190, in compile
return _compile(pattern, flags)
  File /usr/lib/python2.6/re.py, line 245, in _compile
raise error, v # invalid expression
error: nothing to repeat


-- 
View this message in context: 
http://n2.nabble.com/testing-Litephone%2C-new-phone-interface-tp3336730p3349360.html
Sent from the Openmoko Community mailing list archive at Nabble.com.

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


Re: testing Litephone, new phone interface

2009-07-29 Thread Sebastian Krzyszkowiak
On Wed, Jul 29, 2009 at 14:14, KaZeRka...@altern.org wrote:
 Also, deleting sms can be done using
 org.freesmartphone.GSM.SIM.DeleteMessage(int(message)) : it could be useful
 :)

Nooo, no GSM.SIM! That's evil :P I've implemented deleting messages
from SIM in opimd few days ago. With upgrade it should automatically
work in litephone.

About that traceback: I already told author, that everything he
queries in opimd must be correct regular expression. Looks like he
didn't listen to me :D

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



Re: testing Litephone, new phone interface

2009-07-29 Thread KaZeR



Sebastian Krzyszkowiak wrote:
 
 Nooo, no GSM.SIM! That's evil :P I've implemented deleting messages
 from SIM in opimd few days ago. With upgrade it should automatically
 work in litephone.
 
Ah, apologies, then. Would you mind to enlight me about the right way of
doing it then? Is it documented somewher? I undestand that you can't spend
your time writing doc, but.. sometimes.. it's useful ;)
I have a very old (but useful) script to read, answer and delete sms from a
shell, it might need to be enhanced then (i'm still currently storing my
smses only on SIM because i do not know how to do otherwise, so i'm still
limited to 50 messages when i would like to be able to read them in a
discussion-like view).


Sebastian Krzyszkowiak wrote:
 
 About that traceback: I already told author, that everything he
 queries in opimd must be correct regular expression. Looks like he
 didn't listen to me :D
 
Maybe my package isn't up to date :)

-- 
View this message in context: 
http://n2.nabble.com/testing-Litephone%2C-new-phone-interface-tp3336730p3349652.html
Sent from the Openmoko Community mailing list archive at Nabble.com.

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


Re: testing Litephone, new phone interface

2009-07-29 Thread KaZeR



Helge Hafting wrote:
 
 
 I installed on shr-unstable, killed ophonekitd, ran the registration 
 script and started litephone like this:
 
 $ litephone style_sheet.conf
 
 

I believe that the style_sheet part isn't needed anymore, and instead you
can use other parameters (like demo, etc).
I simply ran litephone, in my case and it worked.
-- 
View this message in context: 
http://n2.nabble.com/testing-Litephone%2C-new-phone-interface-tp3336730p3349770.html
Sent from the Openmoko Community mailing list archive at Nabble.com.

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


Re: testing Litephone, new phone interface

2009-07-29 Thread Christophe M
Hi guys,I'm preparing an image based on shr witch works with Qalee, just
wait some few days :)
I plan to integrate it in Qalee in the future ...


2009/7/29 KaZeR ka...@altern.org




 Helge Hafting wrote:
 
 
  I installed on shr-unstable, killed ophonekitd, ran the registration
  script and started litephone like this:
 
  $ litephone style_sheet.conf
 
 

 I believe that the style_sheet part isn't needed anymore, and instead you
 can use other parameters (like demo, etc).
 I simply ran litephone, in my case and it worked.
 --
 View this message in context:
 http://n2.nabble.com/testing-Litephone%2C-new-phone-interface-tp3336730p3349770.html
 Sent from the Openmoko Community mailing list archive at Nabble.com.

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




-- 
__

http://think-free.homelinux.org
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: testing Litephone, new phone interface

2009-07-29 Thread Sebastian Krzyszkowiak
On Wed, Jul 29, 2009 at 15:19, KaZeRka...@altern.org wrote:



 Sebastian Krzyszkowiak wrote:

 Nooo, no GSM.SIM! That's evil :P I've implemented deleting messages
 from SIM in opimd few days ago. With upgrade it should automatically
 work in litephone.

 Ah, apologies, then. Would you mind to enlight me about the right way of
 doing it then? Is it documented somewher? I undestand that you can't spend
 your time writing doc, but.. sometimes.. it's useful ;)
 I have a very old (but useful) script to read, answer and delete sms from a
 shell, it might need to be enhanced then (i'm still currently storing my
 smses only on SIM because i do not know how to do otherwise, so i'm still
 limited to 50 messages when i would like to be able to read them in a
 discussion-like view).

http://docs.freesmartphone.org/

And when you are using Litephone (or any other opimd based gui - don't
do that on ogsmd only gui!), then just set SQLite-Messages as default
backend in Messages domain. You can do that from SHR Settings.

-- 
Sebastian Krzyszkowiak
dos

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


Re: testing Litephone, new phone interface

2009-07-29 Thread Michal Brzozowski
2009/7/29 KaZeR ka...@altern.org


 Hello list.

 I've tested litephone, and i like the concept behind it. Switching from
 contacts to messages to phone logs is done in a breath. I also like the
 possibility to change the volume during call, even if it's not done in the
 cleaner way : at least, it works. Scrolling is a bit awkward at the
 beginning but with the shortcuts on the right side you can find a contact
 in
 a 120+ list quite fast.

 Only issue i noticed so far : keypad doesn't work in calls : i called my
 voice mail and was unable to navigate in its menu.

 Also, deleting sms can be done using
 org.freesmartphone.GSM.SIM.DeleteMessage(int(message)) : it could be useful
 :)

 Otherwise, very promising app. Please convert
 http://pvtrace.com/litephone/
 into a repository so that i can keep it up to date easily.


Thanks for testing! I wasn't aware of the keypad issue, actually I forgot
you should be able to use during calls :-), I'll fix it.

The updating contact issues I know about, and it's fixed for beta release.
If Sebastian has implemented Message.Delete in opimd, then the release
should have full functionality.

The beta release should come later today (european time :-)).

Sebastian, did you fix the data duplication bug already?
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: testing Litephone, new phone interface

2009-07-28 Thread Michal Brzozowski
2009/7/28 jeremy jozwik jerjoz.for...@gmail.com

 On Mon, Jul 27, 2009 at 3:27 PM, Michal Brzozowskiruso...@poczta.fm
 wrote:
  Hi,
  The basic idea on the GUI is that it is packed in one window, the various
  'modules' (contacts, messages, dialer, etc) placed into tabs. No popup
  windows.
  Screenshot:
  http://pvtrace.com/litephone/litephone1.png
  Openmoko community mailing list
  community@lists.openmoko.org
  http://lists.openmoko.org/mailman/listinfo/community

 i like this basic idea. not having to wait for dialer to load. wait
 for messages to load. waiting for applications sucks on the freerunner
 so the less i have to load the better.


That's right. The other thing that bugged me in SHR and Paroli was that when
you have many apps open, and you want to, lets say, send a message, you have
to go through all the windows to see if you have the messages window open.
And when you're just using applications the phone apps get in your way all
the time. Ideally the phone app should be on a different workspace activated
by AUX or something, so when you just switch windows you don't see it at
all.



 i dont think i will be trying this one though, the install seems a bit
 too complex and being that its unstable to you eliminates my chances
 of using it.


The app itself is pretty stable, after all it's just gui bound to dbus
calls. The problem is that you have to use bleeding edge FSO, and it
currently crashes on any FSO error. It's the first thing I'm going to fix.
But you can use it along ophonekitd and SHR apps with no problems. It would
be very helpful to get feedback on the gui.

I'll set up an svn repo today. Any hints where's the best place?

I've put some more screenshots on
http://pvtrace.com/litephone/
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: testing Litephone, new phone interface

2009-07-28 Thread Adolph J. Vogel
Looks very promising. From the stylesheet I see that the colors are 
customizable. Is it possible to change the layout of the gui?

Regards, Adolph


-- 
Adolph J. Vogel BEng(Hons)




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


Re: testing Litephone, new phone interface

2009-07-28 Thread David Reyes Samblas Martinez
Christophe, this can be a great alternative to get rid of Zhone in the
Qalee distro!!!

-- 
David Reyes Samblas Martinez
http://www.tuxbrain.com
Open ultraportable  embedded solutions
Openmoko, Openpandora,  Arduino
Hey, watch out!!! There's a linux in your pocket!!!

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


Re: testing Litephone, new phone interface

2009-07-28 Thread Petr Vanek
 - Install all the ipks from http://pvtrace.com/litephone/ (qt deps and
phone app itself).

 * ERROR: Cannot satisfy the following dependencies for qt4-x11-free:
 *  libqtcore4 (= 4.4.3) *  libqtcore4 (= 4.4.3) * 
 * ERROR: Cannot satisfy the following dependencies for litephone:
 *  libqtgui4 (= 4.4.3) *  libqtcore4 (= 4.4.3) * 

where do you get these from?

Petr


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


Re: testing Litephone, new phone interface

2009-07-28 Thread Michal Brzozowski
2009/7/28 Adolph J. Vogel ajvo...@tuks.co.za

 Looks very promising. From the stylesheet I see that the colors are
 customizable. Is it possible to change the layout of the gui?


No, ATM gui is hardcoded. But you can change stuff like margins, and other
properties (quite a lot).

I've set the package up properly. Now the style_sheet.conf is put in
/etc/litephone/, and loaded automatically. You can run it in 3 modes (note
that the binary name change):

litephone demo - runs it with bogus data (contacts, etc), and generates
bogus call and message events. You can test most of the gui this way.

litephone nogsm - runs it with bogus data, no events

litephone - normal mode

http://pvtrace.com/litephone/litephone_0.0.1-r1_armv4t.ipk
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: testing Litephone, new phone interface

2009-07-28 Thread Michal Brzozowski
2009/7/28 Petr Vanek van...@penguin.cz

  - Install all the ipks from http://pvtrace.com/litephone/ (qt deps and
 phone app itself).

  * ERROR: Cannot satisfy the following dependencies for qt4-x11-free:
 *  libqtcore4 (= 4.4.3) *  libqtcore4 (= 4.4.3) *
  * ERROR: Cannot satisfy the following dependencies for litephone:
 *  libqtgui4 (= 4.4.3) *  libqtcore4 (= 4.4.3) *

 where do you get these from?


I just uploaded them to http://pvtrace.com/litephone/
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: testing Litephone, new phone interface

2009-07-28 Thread Michal Brzozowski
2009/7/28 Michal Brzozowski ruso...@poczta.fm

 2009/7/28 Petr Vanek van...@penguin.cz

  - Install all the ipks from http://pvtrace.com/litephone/ (qt deps and
 phone app itself).

  * ERROR: Cannot satisfy the following dependencies for qt4-x11-free:
 *  libqtcore4 (= 4.4.3) *  libqtcore4 (= 4.4.3) *
  * ERROR: Cannot satisfy the following dependencies for litephone:
 *  libqtgui4 (= 4.4.3) *  libqtcore4 (= 4.4.3) *

 where do you get these from?


 I just uploaded them to http://pvtrace.com/litephone/


Wiki page:
http://wiki.openmoko.org/wiki/Litephone
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: testing Litephone, new phone interface

2009-07-28 Thread Nicola Mfb
On Tue, Jul 28, 2009 at 9:12 AM, David Reyes Samblas
Martinezda...@tuxbrain.com wrote:
 Christophe, this can be a great alternative to get rid of Zhone in the
 Qalee distro!!!

Oh! another nice news, someone working on a QT/X11/FSO based distro
:), going to test in next days!
If interested I may finally decide to exit the prototype phase for NWA:

http://wiki.openmoko.org/wiki/NWA

P.s. what's about the window manager? it may be nice to take a look at
http://qlwm.get.to/ patching it to become an embedded wm :)

Regards

Nicola

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


Re: testing Litephone, new phone interface

2009-07-28 Thread Michal Brzozowski
2009/7/28 Nicola Mfb nicola@gmail.com

 P.s. what's about the window manager? it may be nice to take a look at
 http://qlwm.get.to/ patching it to become an embedded wm :)


I've worked on Icewm a little bit, it's good for the Neo. What features do
you think a WM needs? I think it's just putting all windows to full screen
and switching between them. Bigger problem is a good launcher that works
without E.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: testing Litephone, new phone interface

2009-07-28 Thread David Reyes Samblas Martinez
snip
 Bigger problem is a good launcher that works
 without E.
Qalee includes a launcher , and has not E :)

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





-- 
David Reyes Samblas Martinez
http://www.tuxbrain.com
Open ultraportable  embedded solutions
Openmoko, Openpandora,  Arduino
Hey, watch out!!! There's a linux in your pocket!!!

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


Re: testing Litephone, new phone interface

2009-07-28 Thread Michal Brzozowski
2009/7/28 David Reyes Samblas Martinez da...@tuxbrain.com

 snip
  Bigger problem is a good launcher that works
  without E.
 Qalee includes a launcher , and has not E :)


Please, I want that launcher :-)
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: testing Litephone, new phone interface

2009-07-28 Thread Christophe M
Thanks david, I'll have a look at this and try to integrate it with Qalee,
maybe we'll have it in the 0.0.3 release :). I 'just' have to update the fso
stack to the new one ...
Nicola  Qalee is a environment developed for the freerunner witch integrate
a windows manager ;)


-- 
__

http://think-free.homelinux.org
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: testing Litephone, new phone interface

2009-07-28 Thread Christophe M
Is the source code available anywhere ?



2009/7/28 Christophe M meumeu1...@gmail.com

 Thanks david, I'll have a look at this and try to integrate it with Qalee,
 maybe we'll have it in the 0.0.3 release :).  I 'just' have to update the
 fso stack to the new one ...
 Nicola  Qalee is a environment developed for the freerunner witch
 integrate a windows manager ;)


 --
 __

 http://think-free.homelinux.org




-- 
__

http://think-free.homelinux.org
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: testing Litephone, new phone interface

2009-07-28 Thread Petr Vanek
  - Install all the ipks from http://pvtrace.com/litephone/ (qt deps
  and
 phone app itself).

  * ERROR: Cannot satisfy the following dependencies for qt4-x11-free:
 *  libqtcore4 (= 4.4.3) *  libqtcore4 (= 4.4.3) *
  * ERROR: Cannot satisfy the following dependencies for litephone:
 *  libqtgui4 (= 4.4.3) *  libqtcore4 (= 4.4.3) *

 where do you get these from?


I just uploaded them to http://pvtrace.com/litephone/


thank you Michal. I seems very nice and usable. of course, this is early
stage, but it has features that shr-phone apps might take ages to get -
phone volume, using opimd backends, integration of contacts with phone
log, sms...

while i am happy to see litephone, i know it just put us one step aside
from the ahead direction...

Petr



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


Re: testing Litephone, new phone interface

2009-07-28 Thread Sebastian Krzyszkowiak
On Tue, Jul 28, 2009 at 14:37, Petr Vanekvan...@penguin.cz wrote:
  - Install all the ipks from http://pvtrace.com/litephone/ (qt deps
  and
 phone app itself).

  * ERROR: Cannot satisfy the following dependencies for qt4-x11-free:
         *  libqtcore4 (= 4.4.3) *  libqtcore4 (= 4.4.3) *
  * ERROR: Cannot satisfy the following dependencies for litephone:
         *  libqtgui4 (= 4.4.3) *  libqtcore4 (= 4.4.3) *

 where do you get these from?


I just uploaded them to http://pvtrace.com/litephone/


 thank you Michal. I seems very nice and usable. of course, this is early
 stage, but it has features that shr-phone apps might take ages to get -
 phone volume, using opimd backends, integration of contacts with phone
 log, sms...

 while i am happy to see litephone, i know it just put us one step aside
 from the ahead direction...

 Petr

I already have volume slider in libframeworkd-phonegui-efl, but now
there is just no way to have volume handled correctly, so it can't be
done now. If it is somewhere (Paroli, LitePhone), then it's done
wrongly.

-- 
Sebastian Krzyszkowiak
dos

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


Re: testing Litephone, new phone interface

2009-07-28 Thread Petr Vanek
I already have volume slider in libframeworkd-phonegui-efl, but now
there is just no way to have volume handled correctly, so it can't be
done now. If it is somewhere (Paroli, LitePhone), then it's done
wrongly.

so what is The right way of controlling volume?

Petr


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


Re: testing Litephone, new phone interface

2009-07-28 Thread Sebastian Krzyszkowiak
On Tue, Jul 28, 2009 at 15:10, Petr Vanekvan...@penguin.cz wrote:
I already have volume slider in libframeworkd-phonegui-efl, but now
there is just no way to have volume handled correctly, so it can't be
done now. If it is somewhere (Paroli, LitePhone), then it's done
wrongly.

 so what is The right way of controlling volume?

 Petr

We're using sound scenarios, which are also bad. We have to know,
which alsa controls we should change with that slider on every
scenario and on every device, but ATM there is no infrastructure for
that. ogsmd's SetSpeakerVolume is bad, as it's about modem's volume,
not alsa's.

-- 
Sebastian Krzyszkowiak
dos

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


Re: testing Litephone, new phone interface

2009-07-28 Thread Michal Brzozowski
2009/7/28 Sebastian Krzyszkowiak seba.d...@gmail.com

 ogsmd's SetSpeakerVolume is bad, as it's about modem's volume,
 not alsa's.


But it works?
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: testing Litephone, new phone interface

2009-07-28 Thread Sebastian Krzyszkowiak
On Tue, Jul 28, 2009 at 15:47, Michal Brzozowskiruso...@poczta.fm wrote:
 2009/7/28 Sebastian Krzyszkowiak seba.d...@gmail.com

 ogsmd's SetSpeakerVolume is bad, as it's about modem's volume,
 not alsa's.

 But it works?

Are you sure it will work on every device FSO wants to support?

-- 
Sebastian Krzyszkowiak
dos

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


Re: testing Litephone, new phone interface

2009-07-28 Thread Michal Brzozowski
2009/7/28 Sebastian Krzyszkowiak seba.d...@gmail.com

 On Tue, Jul 28, 2009 at 15:47, Michal Brzozowskiruso...@poczta.fm wrote:
  2009/7/28 Sebastian Krzyszkowiak seba.d...@gmail.com
 
  ogsmd's SetSpeakerVolume is bad, as it's about modem's volume,
  not alsa's.
 
  But it works?

 Are you sure it will work on every device FSO wants to support?


First I'll make sure it works on the device in my pocket, then I'll think
about the other 10k devices that FSO wants to support.

To be more serious, what kind of a problem is it to change the dbus call
later, when FSO exports one? Are you going to wait x months to do it the
'right' way, while users can't change their call volume?
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: testing Litephone, new phone interface

2009-07-28 Thread Michal Brzozowski
2009/7/28 Petr Vanek van...@penguin.cz


 while i am happy to see litephone, i know it just put us one step aside
 from the ahead direction...


What's the ahead direction then?
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: testing Litephone, new phone interface

2009-07-28 Thread Petr Vanek
 while i am happy to see litephone, i know it just put us one step
 aside from the ahead direction...


What's the ahead direction then?


this is certainly a very good question. i guess perhaps one day it will
be one or none of the following:

http://shr-project.org/trac/wiki/SHR%20Applications
http://dufoun.cz/
http://wiki.openmoko.org/wiki/Litephone
http://wiki.openmoko.org/wiki/Paroli
http://wiki.openmoko.org/wiki/Tichy
http://wiki.openmoko.org/wiki/Zhone

and i might be forgetting some...

cheers
Petr


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


Re: testing Litephone, new phone interface

2009-07-28 Thread Nicola Mfb
On Tue, Jul 28, 2009 at 11:43 AM, Michal Brzozowskiruso...@poczta.fm wrote:
 2009/7/28 Nicola Mfb nicola@gmail.com

 P.s. what's about the window manager? it may be nice to take a look at
 http://qlwm.get.to/ patching it to become an embedded wm :)

 I've worked on Icewm a little bit, it's good for the Neo. What features do
 you think a WM needs? I think it's just putting all windows to full screen
 and switching between them. Bigger problem is a good launcher that works
 without E.

Well, every wm doing that is sufficient for embedded devices, so
MatchBox or Illume are well suited (or your patched icewm).

IMHO patching qlwm may give some advantages:

*) it fits nice in a quite totally qt based phone/desktop stack
*) interoperation between application and wm may be easy, developers
may go further without the need of learning different
language/toolkits
*) easy consistent look  feel with applications as the graphics/text
engine would be the same
*) maintaining a c++ wm may be easy and modular by the nature of the language
*) making it pluggable is easy due to the inner plugin api of qt and
the signal slot mech that make api interfaces dynamic
*) qt developers may be attracted in enhancements without going too
deeply in XLib programming
*) the nice side effect to have qt library always preloaded, so other
application loads go fast
*) interest from other community going to use QT for their stack (maemo)
*) qt is supporting embedded deeply due to its historical embedded
support and new Nokia interest (qtopia, qml, kinetic), so we may
expect great improvements in the library
*) a professional support (believe me trolls are fast and reactive)

And last, a sane competition awaking developers ;)

Regards

 Nicola

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


Re: testing Litephone, new phone interface

2009-07-28 Thread Michal Brzozowski
2009/7/28 Petr Vanek van...@penguin.cz

 What's the ahead direction then?
 

 this is certainly a very good question. i guess perhaps one day it will
 be one or none of the following:

 http://shr-project.org/trac/wiki/SHR%20Applications
 http://dufoun.cz/
 http://wiki.openmoko.org/wiki/Litephone
 http://wiki.openmoko.org/wiki/Paroli
 http://wiki.openmoko.org/wiki/Tichy
 http://wiki.openmoko.org/wiki/Zhone

 and i might be forgetting some...


The more the better, is my philosophy.

To stay on topic.

You can find the Litephone code on sf.net/litephone
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: testing Litephone, new phone interface

2009-07-28 Thread Petr Vanek
The more the better, is my philosophy.

thanx for offering choices :)

You can find the Litephone code on sf.net/litephone

here is working link: http://sourceforge.net/projects/litephone/

cheers

Petr





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


testing Litephone, new phone interface

2009-07-27 Thread Michal Brzozowski
Hi,

I gave it a try and wrote an FSO based phone app in Qt. It's using the new
PIM service, and since that's not completely stable yet, there are a few
problems. I'm releasing this anyway, to help test FSO, and meanwhile get
some feedback on the gui and general idea. Consider it an alpha release.
There might be little bugs here and there.

The basic idea on the GUI is that it is packed in one window, the various
'modules' (contacts, messages, dialer, etc) placed into tabs. No popup
windows.
Screenshot:
http://pvtrace.com/litephone/litephone1.png

The best way to use it on SHR is to stop ophoned, turn on the GSM service
and register by hand, wait for some initialization in opimd, and then start
the phone app. Technically you can just start the phone, and it will init
GSM, but due to a bug in opimd, messages and contacts will start duplicating
when you exit and run it again.

The steps:
 - Install all the ipks from http://pvtrace.com/litephone/ (qt deps and
phone app itself).
 - Run /etc/init.d/x-something stop
 - Move /etc/X11/Xsession.d/80ophonekitd somewhere else (like your home
dir).
 - Run the script http://pvtrace.com/litephone/gsm_register.sh (this will
enable gsm and register, and will stay like that until you turn it off by
hand)
 - Run /etc/init.d/x-something start
 - Get the style definition http://pvtrace.com/litephone/style_sheet.conf
 - Run 'phone style_sheet.conf'

If you don't see your contacts and messages, try exiting and running again.
opimd does some initialization upon GSM start that takes 1-2 minutes and
currently there is no signal implemented that notifies about it.

Making and receiving calls and messages should work without problems. You
can add, edit and delete contacts, but deleting messages doesn't work
because it's not implemented in opimd yet.

Scrolling lists (contacts, etc) is done by click, not by drag (I hate
drag-scrolling). Contacts have a smaller sparse list on the right that
lets you scroll faster.

The way composing new messages works is when you hit 'text' or 'reply'
somewhere and a 'compose' tab is not created yet, it creates one with an
appropriate recipient. If one is open already, it just adds to the list of
recipients. So the way to send a message to multiple recipients is to keep
going back to Contacts for example, and add them one by one. While it's not
very intuitive, it's simple and it works :-)

I hope you have fun
Michal
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: testing Litephone, new phone interface

2009-07-27 Thread jeremy jozwik
On Mon, Jul 27, 2009 at 3:27 PM, Michal Brzozowskiruso...@poczta.fm wrote:
 Hi,
 The basic idea on the GUI is that it is packed in one window, the various
 'modules' (contacts, messages, dialer, etc) placed into tabs. No popup
 windows.
 Screenshot:
 http://pvtrace.com/litephone/litephone1.png
 Openmoko community mailing list
 community@lists.openmoko.org
 http://lists.openmoko.org/mailman/listinfo/community

i like this basic idea. not having to wait for dialer to load. wait
for messages to load. waiting for applications sucks on the freerunner
so the less i have to load the better.
i dont think i will be trying this one though, the install seems a bit
too complex and being that its unstable to you eliminates my chances
of using it.

looks VERY promising though. cant wait to see how this develops

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


Re: testing Litephone, new phone interface

2009-07-27 Thread Michal Brzozowski
2009/7/28 Michal Brzozowski ruso...@poczta.fm

 The best way to use it on SHR is to stop ophoned, turn on the GSM service
 and register by hand, wait for some initialization in opimd, and then start
 the phone app. Technically you can just start the phone, and it will init
 GSM, but due to a bug in opimd, messages and contacts will start duplicating
 when you exit and run it again.


I forgot. If you don't feel safe killing ophonekitd, you can run litephone
together with ophonekitd, and it won't cause problems, except that on
incoming calls and messages you will get pop ups from ophonekitd. It's ok to
switch the window and for example pick up the call in litephone. Thanks to
the nice FSO api, they should work together flawlessly.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: testing Litephone, new phone interface

2009-07-27 Thread pike
Hi

 I gave it a try and wrote an FSO based phone app in Qt.
  http://pvtrace.com/litephone/litephone1.png

Looks very nice !
The liter the better.
Have you got more screensnaps ?
What does it look like with a keyboard ?


curious,
*-pike

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


Re: testing Litephone, new phone interface

2009-07-27 Thread Nicola Mfb
On Tue, Jul 28, 2009 at 12:27 AM, Michal Brzozowskiruso...@poczta.fm wrote:
 Hi,

 I gave it a try and wrote an FSO based phone app in Qt. It's using the new

Finally a monolitic/one-shot-loading/fso phone app with my preferred toolkit :)
I cannot test it before a couple of days, will report soon.
I will be happy to contribute with coding/patches, did you setup a
git/subversion/... source repository?

Nicola

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