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
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
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
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
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
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
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
7 matches
Mail list logo
