The statement from @benk016 was purely speculation, not fact. With that said, of course customers find things that the QA staff does not - that IS the nature of software.
And mine just tongue and cheek. Lets think of us as alpha then.
I can't be. My dog is the Alpha.
Yes.
I got you beat!I see all of this new info on owner.ford.com as well, but no indication my Mach-E has received the OTA update yet. Pretty sure it's just work on the website and this info has already been available, but just now showing up.
Should add that the info is very obviously incorrect on a lot of tiles....
Certainly haven't seen my GOM show 331 mile range, ever.
is that the correct number of KM? there was another post where when you map the number shown to KM (although it says MI) it was actually the right number - so the site was just showing the wrong units. 364 KM would be about 226 MI.I got you beat!
How did you know it was not just a bunch of text pop ups? Anything really noticeable? Not too interested in slipping LTSC upgrades into a image with dsim too often. But for the first time I am just hoping for one update and it is to a vehicle. ?
For science purposes, I think you both should run your batteries down until the car dies and report back how many miles you actually achieved. Don't worry, Ford will provide a tow to the nearest charger.I got you beat!
Yes 364 KM = 226 M which is indeed what is displayed.
The percent charge and range usually match for me as well (at least in certain screens in the app), but the time to finish charging is sometimes wonky because it tells me it is charging and that it will finish yesterday lol. I also had to get used to the fact that it said 100% charge in some places in the app despite me setting a 90% limit, which shows properly in other places. The app still needs work for sure.
yeah, I think the Owner site is confused sometimes about Freedumb Units vs. Rest-of-World Units. maybe the Mars Climate Orbiter folks can help them out.
I think if Ford had adopted NFC for it’s key system, we’d be seeing as many posts about how poorly it’s implemented as we’re seeing regarding PAAK. Choose your poison.and you'd have to deal with phones that don't have NFC. there are phones shipping today - new phones - that don't have NFC. that might be silly, but here we are. we know at least two forum members own such phones.
I suspect some people with NFC would argue that "well I don't care about them, because mine would work better"... but Ford has to be careful about that kind of thinking.
however, the other piece is as mentioned you're back to having to take the phone out (and in fact hold it to very specific places), like you would a key, like you're driving a 1975 Mustang II or something. If PaaK is truly to be a key fob replacement, it's got to work in your pocket, including in colder climates where you've got potentially your phone buried in a pocket and you have heavy gloves on. NFC simply doesn't do that because of the NF part.
NFC is in some ways fundamentally broken for this use case - just broken in different ways than BT. If you live in Silicon Valley, you wouldn't have to deal with those ways. But, ask a certainsoftware companycar maker about how designing for moderate cold as the worst level of cold is working out.
I doubt it. And I think the Beta initially had 2 OTA's in it according to the email that was sent to people to sign up for it. You'd get one, and then a few weeks later get a 2nd one.
