Re: GSM errors after 1024 fix
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-tp3827146p3827502.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: GSM errors after 1024 fix
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 the gsm once in a while. i updated to the latest fso packages of debian tuesday and zhone would not connect to fso at all -- something about not being able to enable gsm, gsm being in state enabling or to that effect. before, i could restart frameworkd and it worked, last resort was reboot. after several frameworkd restarts and two reboots i decided to revert to gsmwhtsitsnamemuxer, which seems to work far better (though with some minor flaws. connection to network is sometimes lost and i need to call twice to actually call). ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM errors after 1024 fix
have you changed the deep sleep mode setting? or have you done an opkg update after the fix? if yes can you revert back and check. also check if recamping has stopped after the fix - just to be sure the fix was ok. On 10/15/09, c_c cchan...@yahoo.com wrote: 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-tp3827146p3827502.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 -- -- Please use Firefox as your web browser. Its protects you from spyware and is also a very feature rich browser. www.firefox.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM errors after 1024 fix
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 that it still works flawlessly here. Perhaps software these days starts to rot, just as organic material ;) :M: ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM errors after 1024 fix
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 any development on it last. i am perfectly open to any suggestion how to make it work again, but so far i am stuck -- and since the fr is my sole phone it has to work most of the day. tried two different frameworkd.conf, mine, so far working, and one posted on the list (smartphone-userland, iirc) said to be working well as well. the issues with fso-abyss remained regardless. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM errors after 1024 fix
Hi, Well, mine is working for now. I managed to reboot it to show android to a friend - and it registered both in android and in shr-u - after I 'thumped' it a few times ;-) It might be because of some loose connection - I intend getting it checked soon - just need some time from pending stuff. Definitely a hardware problem - unless 'organic' software starts responding to thumping too ;-) BTW - I did switch the modem to 'always' and there haven't been any updates to shr-u for a long time now - so the software is the same as before the buzz fix. 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 Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM errors after 1024 fix
Did u manage to register at all after the fix? Or the error started later? On 10/15/09, c_c cchan...@yahoo.com wrote: Hi, Thought I'll start a new thread. I got the buzz and 1024 fixes done at Delhi yesterday (thanks Zoheb and Rakshat). But after a few restarts I'm facing this new problem - my modem doesn't register and I get errors like :- 2009.10.15 07:29:37.114 frameworkd.resource INFO setting resource status for GSM from enabled to disabling 2009.10.15 07:29:38.235 frameworkd.resource INFO setting resource status for GSM from disabling to disabled 2009.10.15 07:29:38.395 ophoned.protocol INFO removing protocol GSM 2009.10.15 07:29:43.927 frameworkd.resource INFO setting resource status for GSM from disabled to enabling 2009.10.15 07:29:43.948 ogsmd.channelINFO CallChannel via unknown: Creating channel with timeout = 3600 seconds 2009.10.15 07:29:43.996 ogsmd.channelINFO UnsolicitedResponseChannel via unknown: Creating channel with timeout = 300 seconds 2009.10.15 07:29:44.99 ogsmd.channelINFO MiscChannel via unknown: Creating channel with timeout = 300 seconds 2009.10.15 07:29:44.149 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:29:57.870 ogsmd.modem.abstract ERRORcould not open channel MISC, retrying in 2 seconds 2009.10.15 07:29:57.880 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:30:11.55 ogsmd.modem.abstract ERRORcould not open channel UNSOL, retrying in 2 seconds 2009.10.15 07:30:11.65 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:30:24.375 ogsmd.modem.abstract ERRORcould not open channel CALL, retrying in 2 seconds 2009.10.15 07:30:24.502 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:30:37.700 ogsmd.modem.abstract ERRORcould not open channel MISC, retrying in 2 seconds 2009.10.15 07:30:37.710 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:30:50.900 ogsmd.modem.abstract ERRORcould not open channel UNSOL, retrying in 2 seconds 2009.10.15 07:30:50.910 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:31:04.100 ogsmd.modem.abstract ERRORcould not open channel CALL, retrying in 2 seconds 2009.10.15 07:31:04.109 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:31:17.300 ogsmd.modem.abstract ERRORcould not open channel MISC, retrying in 2 seconds 2009.10.15 07:31:17.310 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:31:30.485 ogsmd.modem.abstract ERRORcould not open channel UNSOL, retrying in 2 seconds 2009.10.15 07:31:30.495 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:31:43.675 ogsmd.modem.abstract ERRORcould not open channel CALL, retrying in 2 seconds 2009.10.15 07:31:43.805 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:31:56.985 ogsmd.modem.abstract ERRORcould not open channel MISC, retrying in 2 seconds 2009.10.15 07:31:56.997 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:32:10.355 ogsmd.modem.abstract ERRORcould not open channel UNSOL, retrying in 2 seconds 2009.10.15 07:32:10.365 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:32:23.540 ogsmd.modem.abstract ERRORcould 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 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. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- -- Please use Firefox as your web browser. Its protects you from spyware and is also a very feature rich browser. www.firefox.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
