I appreciate your post, but my issue is that the watch doesn't seem to switch over to wifi if I am making a call and exit Bluetooth range, the call just drops. Is this your experience too?
I haven't experienced this but it is not surprising to me. I have 2 microcell towers in my home that operate through wifi and when I am on a phone call on my iPhone and then walk to another part of the house where the signal hands off to the other cell tower, my phone call gets dropped. The instructions for the cell towers say this is normal. So, it is not a surprise that when you are on a phone call through bluetooth and then walk out of range of your phone to wifi, the call will drop. So, you either should make the call on bluetooth and stay in that range or make the call from wifi and stay in that range. In short, your issue probably isn't an issue but a normal consequence of switching between signals.
Hmmm… odd. I know when I am on my iPhone in the car, I have never had a connection drop unless we moved out of an area with service. I would think that I have switched towers at least once in that situation? On the subject of the watch, to be clearer, the call doesn't just drop, but in those parts of the house the watch can't do anything requiring the phone, yet it still says it's connected. Calling is just the only activity on the watch that requires consistent high bandwidth so I used it as an example.
Well, for what it is worth, sometimes when I go out of bluetooth range, my watch shows the red disconnected icon for a short time and then it disappears when it connects to wifi and sometimes it can take about 2 to 5 minutes. But most times it transfers to wifi instantly. I would say 90% of the time it transfers instantly, but that other 10% is annoying. If it were happening to me all the time though, I would think my watch is still trying to connect to 5GHz instead of 2.4 GHz and so I would try to go through the wifi setup process again as outlined in that article link I posted.
I almost never see the red icon. In fact, sometimes I have found it works for a while after I moved away from it, but then stops working after a bit until I move either much further or much closer to it. Typically I experience this when I am about two stories below the phone, which in my experience is sometimes within Bluetooth range but never useful at that point. But if the watch isn't working fast enough over Bluetooth it should fall back to wifi after a few seconds right? Anyway, I have found that if I move to the furthest corner of my house I never have connection problems presumably because it has switched completely over to wifi.
I'll look into that. So for you 90% of the time when the watch says it's connected everything works the same even when you are away from the phone? Oddly enough in those places in my house I find Siri often works fine and messages send, just really slowly, but third party apps and calling don't work quite right until either I move farther or closer to the watch. Just double checking those things are working for the most part in your experience.
Yes, they all work for me.
It could be a problem with the router. FIOS makes us use their router which is okay at best. As for coverage, we have at least four Wireless Access Points around the house, so I doubt that is the issue.
import WatchKit
import Foundation
class InterfaceController: WKInterfaceController {
@IBOutlet var interfaceImage: WKInterfaceImage! //wire this up
@IBOutlet var reloadButton: WKInterfaceButton! //wire this up
var task: NSURLSessionDownloadTask? = nil
override func awakeWithContext(context: AnyObject?) {
super.awakeWithContext(context)
reload()
}
@IBAction func reload() { //wire this up to the reload button
reloadButton.setEnabled(false)
interfaceImage.setImage(nil)
let session = NSURLSession(configuration: NSURLSessionConfiguration.defaultSessionConfiguration())
task = session.downloadTaskWithURL(NSURL(string: "[URL]https://developer.apple.com/assets/elements/icons/128x128/watchkit_2x.png[/URL]")!, completionHandler: { (url:NSURL?,response: NSURLResponse?, err: NSError?) -> Void in
let image = UIImage(data: NSData(contentsOfURL: url!)!)
self.interfaceImage.setImage(image)
self.reloadButton.setEnabled(true)
})
task!.resume()
}
override func willActivate() {
super.willActivate()
}
override func didDeactivate() {
super.didDeactivate()
}
}What I suspect at this point is that perhaps bluetooth wasn't the problem at all-- rather it seems the LAN connection was what is breaking. Like I said though, nothing conclusive yet.