Re: 1024#

2009-10-07 Thread Ivan Shirokov
Thanks a lot. I'll give it a try =)

On Wed, Oct 7, 2009 at 1:36 PM, Thomas HOCEDEZ  wrote:
> David Garabana Barro a écrit :
>> On Wednesday 07 October 2009 10:57:02 Christ van Willegen wrote:
>>
>>> Hi,
>>>
>>> On Wed, Oct 7, 2009 at 10:50 AM, Ivan Shirokov 
>>>
>> wrote:
>>
>>>> I've been wondering if all the freerunners are affected by bug #1024?
>>>>
>>
>> No, not all FR are affected, AFAIK
>>
>>
>>> I've been wondering the same thing...
>>>
>>> It would seem that the extra current draw in suspend would affect all
>>> FRs, so having a #1024 fix-party would be a good idea in any case (?).
>>>
>>
>> #1024 is not causing extra current drain, but the software solution to this
>> bug:
>> Not allowing Calypso entering deep sleep mode.
>>
>> You can check if your FR is suffering from #1024 editting 
>> /etc/frameworkd.conf
>> and changing
>>
>> ti_calypso_deep_sleep = never
>>
>> to
>>
>> ti_calypso_deep_sleep = always
>>
>> then restarting framework:
>>
>> /etc/init.d/frameworkd restart
>>
>> After doing so, if your FR suffers from this bug, your modem will 
>> continuously
>> register/unregister from GSM network when suspended, and you will lose calls
>>
>> On my case, it was nearly impossible to call FR when suspended + calypso deep
>> sleep.
>>
>> But not all FR suffer from this bug. You should try it after fixing it.
>>
>>
> Most of GTA02-A5/A6 have this bug.
> Once TI_CALYPSO_DEEP_SLEEP set to "always", you can check with a little
> script done by KaZEr (see bleow)
> Launch it on screen, and redirect output to a file.
>
> If you have something like
> [2009-09-09 12:36:09.189663] Signal : cid=3BB3, lac=0D48
> [2009-09-09 12:36:15.088936] Signal : cid=3BB3, lac=0D48
> [2009-09-09 12:38:10.442808] Signal : cid=3BB3, lac=0D48
> [2009-09-09 12:38:13.020126] Signal : cid=3BB3, lac=0D48
> [2009-09-09 12:40:25.772918] Signal : cid=3BB3, lac=0D48
> [2009-09-09 12:40:28.620096] Signal : cid=3BB3, lac=0D48
> [2009-09-09 12:41:17.557676] Signal : cid=3BB3, lac=0D48
> [2009-09-09 12:41:20.404582] Signal : cid=3BB3, lac=0D48
>
> Then you have the bug (trying to connect to GSM every second!)
>
> regards
>
> AstHrO
>
> Here's KaZeR's script :
> --
> #!/usr/bin/python
>
> import dbus
> import dbus.glib
> import gobject
> import datetime
>
> def onNetworkStatus(status ):
>        print '[%s] Signal : cid=%s, lac=%s' %
> (datetime.datetime.now(),status['cid'],status['lac'] )
>
> bus = dbus.SystemBus();
>
> bus.add_signal_receiver( onNetworkStatus,
>                         "Status",
>                         "org.freesmartphone.GSM.Network",
>                         "org.freesmartphone.ogsmd",
>                         "/org/freesmartphone/GSM/Device" )
>
> gobject.threads_init()
> dbus.glib.init_threads()
> main_loop = gobject.MainLoop()
> main_loop.run()
>
>
> --
>
> ___
> 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


1024#

2009-10-07 Thread Ivan Shirokov
Hello.
I've been wondering if all the freerunners are affected by bug #1024?
I've got 2.6 one.
And if not, how can I determine if mine is affected?

Thanks a lot for any help and sorry for a nub question =)

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


Re: why openmoko is so slow? Is it a joke?

2009-07-13 Thread Ivan Shirokov
On Mon, Jul 13, 2009 at 7:01 PM, mobi phil  wrote:

>
>>
>> That depends on your sense of humour ;-)
>>
>>
>  Well, I would say it was a very bad joke. I spent eq. of 400 dolars, I
> was waiting 1 year for glamo acceleration etc, etc. that would make the
> phone usable etc, and it turns out, that it will never be. With the slow
> bus, one can forget about acceleration... What can be accelerated if you
> have to send information about complex bitmaps...
>

That's really sad =(
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Watching videos on neo freerunner (openmoko 2008.12) mplayer-glamo

2009-04-08 Thread Ivan Shirokov
nope. I still see something like this in console

r...@om-gta02:~# ./vidplay /media/card/film01-FR.avi
> [AO OSS] audio_setup: Can't open audio device /dev/dsp: No such file or
> directory
> DVB card number must be between 1 and 4
>
>
>
> Your system is too SLOW to play this!  
>
>
> Possible reasons, problems, workarounds:
> - Most common: broken/buggy _audio_ driver
>   - Try -ao sdl or use the OSS emulation of ALSA.
>   - Experiment with different values for -autosync, 30 is a good start.
> - Slow video output
>   - Try a different -vo driver (-vo help for a list) or try -framedrop!
> - Slow CPU
>   - Don't try to play a big DVD/DivX on a slow CPU! Try some of the
> lavdopts,
> e.g. -vfm ffmpeg -lavdopts lowres=1:fast:skiploopfilter=all.
> - Broken file
>   - Try various combinations of -nobps -ni -forceidx -mc 0.
> - Slow media (NFS/SMB mounts, DVD, VCD etc)
>   - Try -cache 8192.
> - Are you using -cache to play a non-interleaved AVI file?
>   - Try -nocache.
> Read DOCS/HTML/en/video.html for tuning/speedup tips.
> If none of this helps you, read DOCS/HTML/en/bugreports.html.


And some kind of noise on the FR screen.
I think it can be caused by wrong file converting.
Or maybe I should try OM2008.12 instead of SFO.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Watching videos on neo freerunner (openmoko 2008.12) mplayer-glamo

2009-04-07 Thread Ivan Shirokov
Does it work for FSO? Somehow it hangs up my FR. And there's something like
"Your system is too slow" in the console =(

On Sun, Jan 11, 2009 at 9:31 PM, pottwal4  wrote:

> Hi again.
> > pottwal4 wrote:
> >
> >> r...@om-gta02:~# mplayer -vo xover:glamo -fs
> /media/card/big_buck_bunny_320.avi
> >>
> > mplayer doesn't know on which display it should open the video.
> > Try (one line):
> > DISPLAY=:0 mplayer -vo xover:glamo -fs /media/card/big_buck_bunny_320.avi
>
> Thanks Daniel, you was right! There was a problem concerning the
> $DISPLAY-Variable. But there was an other one, which I fixed, choosing
> the output device "-vo glamo" instead of "-vo xover:glamo".
>
> So for everyone, how cares this what I do to get the example video
> running on the freerunner (inspired by
> "http://wiki.openmoko.org/wiki/Video_Player";):
>
> 1. Download an unpack mplayer-glamo
> (http://downloads.tuxfamily.org/3v1deb/openmoko/mplayer-glamo.tar.bz2)
>
> 2. Write a short bash-script "vidplay" to start the video (and save it
> on the Freerunner and make it executable (with chmod +x vidplay)):
> #!/bin/sh
> DISPLAY=:0
> xrandr -display :0 --output default --mode 240x320
> mplayer -vo glamo "$1" > /dev/null
> xrandr -display :0 --output default --mode 480x640
> reset
>
> 3. Encode a video-file on my PC with:
> mencoder video-file -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300
> -vf scale=320:240,eq2=1.2:0.5:-.025,rotate=2 -oac mp3lame -lameopts
> br=64:cbr -o video-file-FR.avi
>
> 4. Transfer this file from PC to Freerunner (using scp)
> scp video-file r...@phone:/media/card/
>
> 5. Considering that the video-start-script and the video-file are now
> both located on the Freerunner in directory /media/card/, start the
> video with:
> cd /media/card
> ./vidplay video-file
>
> ___
> 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