Search results

Alternately (as an example), the maps system could be auto-downloading to populate(&update) the cache such that a 500 mile (or a user defined value) radius from the current location is always available... that would be more than enough to cover the entire US with zero driver input... as a...

The very concept of "offline maps" that you need to explicitly turn on&off is a broken concept (an ex-co-worker would call it an example of BAD: Broken As Designed). Read through caches that auto-populate & auto-update are not new or difficult concepts... and organizing it "by state" is strange...

Not (yet) on the new software, but I found that AA's phone (Samsung S22+) battery usage caused me to walk away from AA... the native Air apps are good enough and any benefit from AA didn't justify needing to plug in to keep my phone charged (note, the phone's battery usage is fine in other...

Nor was I asking for a prediction of the future, rather just a retrospective of the past... which was there in v1 (though I now concur that it likely was not the trip or SLC number, but rather a time average of recent usage more in line with the instantaneous usage graphic which is still present).

There is a big difference between reporting what the past (SLC or trip) values are versus what the future (battery charge to 0%) might be... the car just can't know how you will drive (as opposed to how you have been driving).

In reflection, that does more closely match my memory (i.e. not matching the trip info), but I also recall it not being a static number, perhaps a time average over the past minute or so (not as instantaneous as the graphic around/below the speed indicator, but not as long term as the trip...

I described a mi/kw number, running in real time... I know that it was there and recall my reaction when it was removed for v2.

Incorrect, it was there in v1 of the sw... I used it heavily, and it changed and tracked the value in the "trip" screen, as opposed to being a static EPA estimate...

And yet, it was there in v1 of the sw, and other similar data such as the SOC or Trip# odo and current battery SOC are there... so I would call BS (i.e. lots of salt) on this ex-employee's story. And even so, as pointed out in other comments, then put it elsewhere on the (multitude of) screens...

Good thought, settings=>vehicle=>tires as I recall, tell it you are on 21" (or 20") and then correct the lie by going back to 19" (in case an internal setting has gone astray and may be corrected with the externalized setting, I've seen sw do stranger things)...

Yes, do write [email protected] about this proposal/request, I just did so this afternoon... converting a hard to use (dangerous) touch screen control to a safe, easy to use hardware control is a win (and if some don't like that change, there could always be a settings switch to control...

I remember, oh so long ago, when the m/kw # was displayed under the SLC/trip mileage #... I miss that, and wish we had it back... I also would love to see the 4 tire pressure #s displayed in a compact manner on the main screen...

As I recall, swift mode warns you that you shouldn't use it with the AS tires...

On a 2024 you bought new... it seems you don't use the car at all... or is that a typo?

Did the driver's seat have a floor mat, and if so, which one?

Assuming you are referring to the "battery_health_level" value, mine (from Aug) is indeed different: Field 11, battery_health_level: 96.00000143051147 and I would expect the capacity numbers to not vary in many cases (i.e. a design point for a given battery size, not the actual capacity).

Good point, though it would also point to different behavior just based upon time of day (daylight vs nighttime)... has that been observed? (I don't use HFDA myself, as I LIKE to drive the car. ;-)

I wonder to what extent a good GPS fix is needed for HFDA to work (I suspect GPS is involved otherwise HFDA would work on any road just based upon the other sensors)... GPS fix quality does vary with the weather and other factors, and the difference between a fix that is accurate to single digit...

I find that while this is true at times, there are other times when I need to be 30-ish yards from the car before it locks... personally, I'd like more consistency of behavior as the bigger issue to address. In all cases, I'm using PaaK, so I would expect a fairly strong & consistent BT signal...

Wonder how having that fridge plugged in also was affecting your charge state (as it cycled on & off)...