Intone hangs after pause

2012-04-07 Thread Matthias Apitz

Hello,

I'm playing a bit around with other FR features... and faced the
following problem: Playing Mp3 with Intone works fine, even moving
between the tracks; but when you pause a song it does not restart; it
must be an issue with mplayer, because when you start 

$ mplayer Track03.mp3

from a ssh session and hit 'p' or 'space' it pauses, but never
continues; when I do this in my FreeBSD laptop it looks like this:

  =  PAUSE  =
  A:   7.6 (07.5) of 211.0 (03:31.0)  1.4% 

in the SHR the PAUSE line only shows up for half of a second and after this it
sits there; only Ctrl-C helps.

Any help?

matthias
-- 
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e  - w http://www.unixarea.de/
UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5

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


Next Openmoko "Stammtisch" in Munich

2012-04-07 Thread Dr. H. Nikolaus Schaller
I am not sure if everybody is monitoring the http://freeyourphone.de
forum, but I have seen that the next "Stammtisch" is now scheduled
for

Wednesday, 18th April 2012, 19:00

in Munich, Germany:

http://freeyourphone.de/portal_v1/viewtopic.php?f=71&t=2234#p19450
http://www.doodle.com/4688ybpgnngksraq

It appears to have a record breaking number (11) of
registrations this time...

Happy Easter weekend and many easter eggs :)

Nikolaus

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


Re: Boot2Gecko - Open Web Device

2012-04-07 Thread arne anka


The Open Web Device is also using a Linux Kernel (the same
one used by Android devices) which is also open. This is a
100% open project [...]

 should fire up all the alarms.  Sure, the kernel is open.  What
 about the drivers?  Are we going to be playing the "open shim to
 closed drivers" game again?  Is the video driver open?  Is the
 modem driver open?  Is the audio driver open?  Is the GPS driver
 open?  Are *ALL* the drivers open?


since the OP posted this in the OM mailing list, s/he clearly has the  
GTAXX devices in mind -- and, yes those drivers _are_ open.
which devices the B2G project has in mind does not concern us -- so,  
please, don't discuss that here but go to the B2G site and vent your  
concerns there.



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


Re: Boot2Gecko - Open Web Device

2012-04-07 Thread Marcelo E. Magallon
On Fri, Apr 06, 2012 at 11:48:59PM +, elf Pavlik wrote:

> "The heart of the system is Mozilla's Boot2Gecko, which has
> always been open and opensource. The Open Web Device is also
> using a Linux Kernel (the same one used by Android devices)
> which is also open. This is a 100% open project where, for
> instance, operators and OEMs can actively and openly contribute
> to the code, instead of Mozilla developing internally and
> making code drops available."

 Are we falling into the same trap *again* (and by "again" I mean
 "the 6th or 7th time in a row")?

 The fact that the site has a *flash* video should tell you
 something about the level of commitment to openness and
 interoperability, but even if you choose to ignore that, this
 sentence:

The Open Web Device is also using a Linux Kernel (the same
one used by Android devices) which is also open. This is a
100% open project [...]

 should fire up all the alarms.  Sure, the kernel is open.  What
 about the drivers?  Are we going to be playing the "open shim to
 closed drivers" game again?  Is the video driver open?  Is the
 modem driver open?  Is the audio driver open?  Is the GPS driver
 open?  Are *ALL* the drivers open?

 If this is the measure of openness they are using, Android is
 100% open, too.  Manufacturers throw a couple of closed drivers
 underneath and a couple of closed "UI differentiators" on top,
 but hey, the stack is open.

operators and OEMs can actively and openly contribute to the
code, instead of Mozilla developing internally and making
code drops available.

 The keyword here is "can".

 I'm sorry to sound bitter, but I've seen variations of this for
 the last 15 years, and I don't blame manufacturers, I blame
 users who have consistently accepted "90% open" for "100% open",
 praise the manufactures for throwing them a bone, and then come
 back complaining to the developers of the actually open stuff
 because the other 10%, which is what they actually care about,
 doesn't work as well as they demand it to.

 Marcelo

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