Much better than having to switch off and on as I had to do with butterfly.
Maemo isn't Windows, so it seems to me that it ought to be possible to fix things without restarting all the time. Instead, surely one could use the terminal to restart a service/daemon/process to fix this until the bugs are ironed out. I'm at work so don't have time to look into this, but maybe next week when I'm off I'll have a poke about.
I'm new to Maemo (although have plenty of Unix experience). Anyone have any thoughts/info on this as a possibility?
I don't meant to sound like a fanboy, or be offtopic, but, for the record, one should not mistake bad application design or userbase with operating system limitation.
Windows only *requires* rebooting for kernel updates and non-stoppable services, like the filesystem driver. Everything else asks for reboots because they can't be bothered to stop services, close running programs or dismount hardware. Others do so just to be on the safe side.
On Windows 7, ATI/AMD update video drivers on the fly. Windows update does the same for NIC and sound cards at the very least. There are documented, mouse-only or keyboard only ways of restarting the GUI/Explorer for apply settings and load/unload extensions.
Also, nothing stops the user for updating files by hand via command line, it's right there in plain text.
Do you really think that developers reboot the system every compile/build?
I am aware that praising Windows in a Linux forums is not a good idea, but I'm not trying to dispense smugness, just trying to lower the myth count.
wow its seems to be buggy... after a few N900 restarted it has managed to work.
I'm not sure but has anyone notice the length of time before it manages to connect to the msn server during authentication. for me it take anthing between 15-30secs
Does anyone know the reason for this. I noticed it doesnt matter which type of connection I use it differs whilst all other IM "plugins" manages to log without a hitch.
wow its seems to be buggy... after a few N900 restarted it has managed to work.
I'm not sure but has anyone notice the length of time before it manages to connect to the msn server during authentication. for me it take anthing between 15-30secs
Does anyone know the reason for this. I noticed it doesnt matter which type of connection I use it differs whilst all other IM "plugins" manages to log without a hitch.
At the risk of sounding like a broken record....
What part of this is not a production release do people think means something other than - this still has kinks and bugs or it would be a production release?
What part of this is not a production release do people think means something other than - this still has kinks and bugs or it would be a production release?
I understand its not even release globally... But is there a way to post a bug to the dev or do I have to wait till the fixes are complete hoping it has been fixed
I was able to recover my IM connection from this same 'network error' problem by doing the ff:
- switch IM status to offline.
- switch connection type from wifi to gprs/3g
- switch IM status to online
I believe what needs to happen is all IM accounts have to be offline before switching to a different internet connection type.
In the my case, the problem occured after I switch from cellular connection to wifi so the steps listed above fixed the issue without rebooting my phone.
