[ I think this discussion is now going more into the realm of the "devel" list. Added Cc and Reply-To to that effect. Let's see if this works ;-) ]
Michael 'Mickey' Lauer wrote: > Fwiw, the FSO team has finally chosen to base their networking on Intel's > connman. It's not very high on our priority list, but it's present. Thanks ! Now, what do I do with people who have WLAN problems right now ? That's the old problem not having a clear direction for the network manager caused for WLAN debugging: many of the reports were from a fairly high-level view, which always made the dysfunctional network manager a potential influence. This could be "solved" by asking people to use command-line tools like iwconfig, but there was still the risk of the network manager kicking in. So the user space would have to be silenced as well. Of course, just asking people to "kill all the daemons" doesn't guarantee that they'll really catch everything. Suspend/resume now adds another problem: if involuntary suspend cannot be prevented, and the network manager isn't ready yet, the network will appear to fail from time to time. (Because the WLAN module gets reset during resume.) One option would be to just ignore the higher layers of user space for now and work on customized systems that don't go beyond a shell and that never suspend unless explicitly told to do so. That would allow the debugging to proceed, but it would of course not make the whole phone more useful for our users. So ... is there something better we can do ? - Werner
