I
can use another phone instead.
Thanks.
[working] http://n2.nabble.com/file/n3857557/frameworkd.log frameworkd.log
[not working]
--
View this message in context:
http://n2.nabble.com/GSM-errors-after-1024-fix-tp3827146p3857557.html
Sent from the Openmoko Community ma
Framework not being able to open a new channel means fso-abyss is not able
to register a channel with the multiplexer. That it only works 4 out of 5
times sounds like a race condition. Do you have anything else installed that
could compete with fso-abyss over the GSM resource?
:M:
_
ges?
--
View this message in context:
http://n2.nabble.com/GSM-errors-after-1024-fix-tp3827146p3856574.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
On Mon, 19 Oct 2009 17:15:18 +0200
Michael 'Mickey' Lauer (M'L) wrote:
>Am Montag, den 19.10.2009, 12:46 +0200 schrieb Petr Vanek:
>> On Mon, 19 Oct 2009 01:50:51 -0400
>> David Ford (DF) wrote:
>>
>> >actually i was vague/misleading in what i wrote. what i would like
>> >to see is for the end
Am Montag, den 19.10.2009, 12:46 +0200 schrieb Petr Vanek:
> On Mon, 19 Oct 2009 01:50:51 -0400
> David Ford (DF) wrote:
>
> >actually i was vague/misleading in what i wrote. what i would like to
> >see is for the end user to be notified in a friendly fashion. like
> >injecting a service messag
On Mon, 19 Oct 2009 01:50:51 -0400
David Ford (DF) wrote:
>actually i was vague/misleading in what i wrote. what i would like to
>see is for the end user to be notified in a friendly fashion. like
>injecting a service message into opimd/sms buffer
sounds like a good communication method for th
actually i was vague/misleading in what i wrote. what i would like to
see is for the end user to be notified in a friendly fashion. like
injecting a service message into opimd/sms buffer
Petr Vanek wrote:
> It exists already.
>
> ...another way is to use frameworkd with ti_calypso_sleep_mode =
>
On Mon, 19 Oct 2009 00:32:28 -0400
David Ford (DF) wrote:
>can't we build in detection for that?
>
>Michael 'Mickey' Lauer wrote:
>> (NB: This compact debug output form is not optimal for recognizing
>> #1024 anyways, you should rather watch for CSQ and CREG messages. If
>> CSQ suddenly drops to
can't we build in detection for that?
Michael 'Mickey' Lauer wrote:
> (NB: This compact debug output form is not optimal for recognizing #1024
> anyways, you should rather watch for CSQ and CREG messages. If CSQ suddenly
> drops to 99 and you get thrown out of the cell, then it's 100% clear you
>How did you ever get it to work in the first place? I noticed the
> Debian
> package appearing and installed it, but never found all of the required
> documentation to actually use it:
i don't remember exactly, but i think the only change was setting the
muxer to fso-abyss in frameworkd.c
>Yes, just use frameworkd with ti_calypso_sleep_mode = 'adaptive' and
>inspect the logs. Frameworkd will tell you, when a real recamping
>exists.
makes sense, thank you
Petr
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists
>How about this output:
>[2009-10-18 13:37:02.701925] Signal : cid=9E4A, lac=17A2
>[2009-10-18 13:37:26.813505] Signal : cid=7149, lac=17A2
>[2009-10-18 13:41:22.576405] Signal : cid=9E4A, lac=17A2
>[2009-10-18 13:45:48.512750] Signal : cid=7149, lac=17A2
>[2009-10-18 13:49:10.453532] Signal : cid
On 10/18/09, Petr Vanek wrote:
>>> I get messages like
>>>[2009-10-18 07:51:27.107655] Signal : cid=4E91, lac=006A
>>>[2009-10-18 07:52:45.145288] Signal : cid=4E7B, lac=006A
>>>[2009-10-18 07:53:18.218122] Signal : cid=4E91, lac=006A
>>>...
>>> So I guess my #1024 is not fixed :-(
>>
>>The thre
>> I get messages like
>>[2009-10-18 07:51:27.107655] Signal : cid=4E91, lac=006A
>>[2009-10-18 07:52:45.145288] Signal : cid=4E7B, lac=006A
>>[2009-10-18 07:53:18.218122] Signal : cid=4E91, lac=006A
>>...
>> So I guess my #1024 is not fixed :-(
>
>The three lines you quoted are not showing #102
>Hi,
> I get messages like
>[2009-10-18 07:51:27.107655] Signal : cid=4E91, lac=006A
>[2009-10-18 07:52:45.145288] Signal : cid=4E7B, lac=006A
>[2009-10-18 07:53:18.218122] Signal : cid=4E91, lac=006A
>...
> So I guess my #1024 is not fixed :-(
The three lines you quoted are not showing #1024.
.nabble.com/GSM-errors-after-1024-fix-tp3827146p3842955.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://www.freesmartphone.org/index.php/Implementations/fso-abyss.
:M:
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
On Thu, Oct 15, 2009 at 12:48:50PM +0200, arne anka wrote:
> try the other muxer, gsmwhatsitsname, instead.
> to me it seems, fso-abyss has detoriated into almost unusability over the
> last months.
How did you ever get it to work in the first place? I noticed the Debian
package appearing and
Somehow, I can't seem to notice any significant increase in the battery
standby time either. How do I check for the modem recamping?
--
View this message in context:
http://n2.nabble.com/GSM-errors-after-1024-fix-tp3827146p3833238.html
Sent from the Openmoko Comm
> Wow, that'd be quite an achiement considering that I didn't do any
> development on it. Note that it still works flawlessly here. Perhaps
> software these days starts to rot, just as organic material ;)
well, debian's release cycle is somewhat detached from upstream.
i don't know when you "did a
Am Donnerstag, den 15.10.2009, 12:48 +0200 schrieb arne anka:
> try the other muxer, gsmwhatsitsname, instead.
> to me it seems, fso-abyss has detoriated into almost unusability over the
> last months.
Wow, that'd be quite an achiement considering that I didn't do any
development on it. Note tha
u manage to register at all after the fix? Or the error started later?
>>
> Seems like I can register once in every 4/5 reboots. I'm registered now
> after 5 reboots.
> --
> View this message in context:
> http://n2.nabble.com/GSM-errors-after-1024-fix-tp3827146p38275
try the other muxer, gsmwhatsitsname, instead.
to me it seems, fso-abyss has detoriated into almost unusability over the
last months.
when is started with it, month ago, it worked flawlessly, after doing an
update to a more recent version of fso in july/august, zhone had issues
requesting th
rakshat wrote:
>
> Did u manage to register at all after the fix? Or the error started later?
>
Seems like I can register once in every 4/5 reboots. I'm registered now
after 5 reboots.
--
View this message in context:
http://n2.nabble.com/GSM-errors-after-1024-fix-tp382714
ERROR could not open channel
> CALL, retrying in 2 seconds
> 2009.10.15 07:32:23.550 ogsmd.modems.ti_calypso INFO Requesting new
> channel from 'fso-abyss'
>
> and so on
>
> Any ideas what the problem could be? What do MISC, UNSOL and CA
#x27;fso-abyss'
and so on....
Any ideas what the problem could be? What do MISC, UNSOL and CALL mean?
Thanks.
--
View this message in context:
http://n2.nabble.com/GSM-errors-after-1024-fix-tp3827146p3827146.html
Sent from the Openmoko Community mailing list archive at Nabble.com.
__
26 matches
Mail list logo
