maemo.org - Talk - View Single Post

Jare	2014-01-15 , 16:31
Posts: 26 \| Thanked: 97 times \| Joined on Dec 2011	#15

Originally Posted by Fuzzillogic

However, it seems that after disabling the tethering, wifi has issues reconnecting. Wifi is quite buggy anyway in the current Sailfish release, so I guess it's not even therering-gui's fault. A reboot fixes it, but perhaps less drastic measures are enough. On the N9, restarting the ICD2 service often helped. Is there something alike on Jolla?

The tethering gui will handle wifi device state during bluetooth tethering too, so either it triggers a bug in Jolla's connection agent or it's a bug in the tethering gui. Anyway the tethering gui only switches wifi radio on/off and a change in wifi radio state is automatically signaled to all listeners by connman, so there shouldn't be too much to do wrong.

For me it seems that the issues with wifi and mobile data connections were actually worsened by the current Sailfish release. There are especially issues with wifi auto-connect, so at the moment I'm kind of waiting for a new Sailfish release.

What kind of state the wifi adapter ends up in your case? Does it show a star in the status icon and fail to auto-connect or does it fail completely and display a "problem with connection" error and/or an exclamation mark in the status icon?

Originally Posted by bennypr0fane

Actually, it says in the first post that it has infrastructure mode.
Does it, Jare?
All kinds of devices have trouble dealing with ad-hoc connections, not just Android, and even if they're supposed to support it (ftr, I haven't tested the app yet).

Yes, it creates an infrastructure network instead of ad-hoc.

Quote & Reply |

The Following User Says Thank You to Jare For This Useful Post:
Kaacz