I am pretty sure that this issue is related to authentication between Rogers here in Canada and the network that Tesla uses. This is not dissimilar to issues I have seen with my phone while roaming in the US. And given the title of this thread this didn't exist in the past on the Model S, but I didn't own a Tesla at that time.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
mknox
Well-Known Member
I feel for you guys, I really do... but I'm more intrigued by the fact that I don't seem to have the problem to nearly the extent of others. Other than a very small handful of times, the only time I see a similar big long delay in connecting is when I manually do a re-boot myself. I don't even consider it a problem on my car. It's just bizarre how different seemingly identical cars can be.
beeeerock
Active Member
I would agree completely... I've seen zero change in reliability over the last 3 or 4 updates (or whatever it's been). Given that my Rogers phone can roam to Bellus without any issues, I don't understand the problem. I would drop a call on my phone if it happened while talking, but I wouldn't have to reboot, hold my tongue a certain way and make a small sacrifice to the Ghost of Marconi.
As I've said before, it really shouldn't be this difficult to make reliable, given virtually every cell phone on the planet can do it without any fuss.
Duckjybe
Member
Currently testing 2.5.36 (which I received this morning) with Energy Savings = ON, Always connected unchecked. May I remind people here that the widespread problem is with these settings (although Always connected checked with Energy Savings ON also seems to have problems)
beeeerock
Active Member
I've always had 'Always Connected' set to 'on', AND 'Energy Savings' set to 'off'. That is, what one would assume would be the most reliable combination of settings, albeit at the price of more energy consumption. It's still causing me regular grief.
Reading further, it appears that 'Energy Savings' might default to 'on' during nighttime hours...however my problems typically happen in the middle of the day, while actively using the connection (Slacker). So it wouldn't seem to be a problem with waking up the system.
If anything this is actually getting worse for me and I got the latest firmware upgrade installed yesterday morning. Since then I have had outages for 2 out of 3 trips in my car. And I also had an outage on my way into the office yesterday as well.
mrElbe
Active Member
Knock on plastic, I am the same as mknox; no dropouts. Driving to Elmira ON and back today and tomorrow to north of Philadelphia via Kingston Supercharger. Stay tuned ( connected? ).
mknox
Well-Known Member
When I do a re-boot in Canada, it takes maybe 1 or 2 minutes for everything to come back: bars, 3G symbol and music playing. I had to do a re-boot at my daughter's place in Illinois (touch screen became unresponsive) back in June and noticed the 3G was restored almost immediately.
mrElbe
Active Member
mrElbe
Active Member
Did a test coming back from Philadelphia. Turned on Energy Saving and turned off Always connected. Absolutely no problem waking up and immediately connecting in PA, NJ, NY.
As soon as I crossed the border into Canada today at the Rainbow bridge, the 3G dropped dead. Near the QEW and 405 merge I then turned off Energy Saving and turned on Always connected and 3G immediately connected with full bars.
My conclusion: it is definitely a roaming issue.
As soon as I crossed the border into Canada today at the Rainbow bridge, the 3G dropped dead. Near the QEW and 405 merge I then turned off Energy Saving and turned on Always connected and 3G immediately connected with full bars.
My conclusion: it is definitely a roaming issue.
Support is usually pretty good but this is something that head office in Cali can't really test since it seems to only occur when the connection is being made through Rogers' (or perhaps Belus as well) network. My one pet peeve is that the designers need a more global perspective - like not putting sensors in concave holes that fill up with snow (look under your front nose cone for that one).
@tdavis1198 - a suggestion that you add your city to location rather than just Canada as it can be useful when people respond.
@tdavis1198 - a suggestion that you add your city to location rather than just Canada as it can be useful when people respond.
Canuck
Well-Known Member
To the new people: Turn off energy savings and always stay connected and it helps.
Soolim
Member
Discussed this with the SC, and actually tried it a few weeks ago, sad to say that it did not help me. YMMV.
SC also said that having always connected draws power from the 12V battery. Since it did not worked for me, I went back to my old settings. Still hoping that Tesla will fix this firmware issue (according to SC).
beeeerock
Active Member
I'm beginning to wonder if the problem occurs when Rogers service drops out and the car roams to Belus (assuming it does). Rogers added that roaming service over to Belus for phones recently at no extra charge... I don't know if the Jasper SIM would have caused it to happen anyway, or differently. When a Rogers phone does it, the call drops, or the data transport fails... but service becomes available shortly once the roaming handshakes are done. It feels to me like the IP tunnel constructed via the Rogers or Belus connection simply doesn't want to reset to the new IP assigned to the car when roaming occurs. This could even be the fault of the Jasper end of the tunnel for all we know, which would explain the delays in getting it sorted out.
Depending on the carrier used in the US, perhaps roaming doesn't happen often or at all... which would explain why we're complaining and our friends south of the 49th aren't...
My longest 'outage' was almost 48 hours... and I have pretty much always had 'always connected' checked, with no power savings selected.
My service person told me the LTE upgrade does nothing for this problem in Canada, as far as they've seen.
That Rogers service, called Rogers-EXT, is rather new and I think this problem predates that problem. But I don't think what you describe is happening as this happens in areas with strong Rogers signals. If it happened like you described then we should also occasionally see Rogers-EXT on our phones and I never see that unless I leave Rogers' coverage area.
Tried it, did not help. This morning two reboots and still did not connect. Its really annoying as so many of the cool features disappear with no connection
- - - Updated - - -
- - - Updated - - -
Spoke to the SC, told me that i should solve the problem by tethering to my phone. Not really a great solution. Looks like this problem has been ongoing since Nov, 2014 without any resolution. Maybe its not as simple as it looks to solve.
Similar threads
