@marke08 , ah of course. Yes the vehicle simply stops charging once it reaches its limit, any drain from then on is taken from the battery. I believe the battery heater though comes from the charger still while connected, not from the battery itself, but I could be wrong there.
-
@sku100 , indeed I have been.
There was quite a lot network security improvements in the latest version, most notably is certificate pinning to all of Tesla's services. This ensures your connection is private when sending or receiving sensitive data to and from Tesla's servers stopping a vast majority of man-in-the-middle attacks.
These improvements caused a domino effect calling for a consolidation and refactor of network-related code which caused a few backwards compatibility issues. I extensively tested and fixed all of them, however there was one regarding Widgets that simply couldn't be avoided impacting only some Android launchers out there, this is likely what you encountered. Widgets are special since they are really more like plugins read into another app, in this case a launcher, so worst case a simple remove and re-add of a widget will correct things this time around.
Anyway, good news is this type of refactor was done future-proof and really shouldn't be needed ever again, sorry for the inconvenience.
-
@Hacksaw , sorry for the delay, Gear interest has been frequent and mounting as time goes on. It's a platform I'm serious about expanding to, especially with half the work already done by using the preexisting Wear support's service. It comes down to logistics at this point, it'll be a sizable workload to bite off when the time comes and I don't plan on stopping it once started since context switching only delays everything. I will get the mobile app into refinement mode then tackle Gear support, where refinement mode means Wear support finished.
Wear summon support has been delayed a few times, the recent location screen extraction to its own activity took precedent as more and more Samsung users were hit with flashing screens due to a Samsung-only bug with map views located inside view pagers.
The recent network security improvements took precedent as well, it also included important reliability fixes to background services caused by
Android Oreo's new background execution limits.
I'll be back working on Wear summon support here soon, good news is there really isn't much left to be done there either.