I have an application that will have no User Interface (not exactly none altogether but VERY minimal).
I want it to scan for Wifi access points at regular intervals, check the connected state of Wifi and check the connected level of the currently connected access point. It also listens for the OUT_GOING_CALL broadcast and traps the call if connected to wifi and then pops up a dialog that tells the user the call has been blocked and offers the user cheaper options than Gsm if there are any. I currently use the Broadcasts to get the Scan Results and to get changes in the connected Level of the wifi connection also. However I had thought that moving these to a service of my own would be a good idea, however would I be better leaving them as Broadcast Recievers in Non Activtiy and Non Service classes and just make the main Engine of the application a service that turns on and off these broadcasts from there Classes (Objects) ? So I was wondering would having several services, one that does the wifi stuff, one that does the call monitoring, and one that drives the whole thing? Or would I be better off using BroadcastRecievers to listen out for changes instead and implement a timertask to scan for access points and only have one service being the engine that drives it all? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
