This is what I am fearful wil happen with having CarPlay in your car. You'll still only get like 3 years out of your brand new car before it doesn't work anymore.
----------
I see 'em everyday here in LA.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Chevrolet's Upcoming 2016 Volt Plug-in Hybrid Spotted With CarPlay Integration
- Thread starter MacRumors
- Start date
- Sort by reaction score
----------
HobeSoundDarryl
macrumors G5
Yea, I've seen several kits where one can install an iPad or iPad Mini in their dash. Here's a few good (picture) examples: http://www.6speedonline.com/forums/996/301123-ipad-mini-dash-install-996-mkii.html IMO, they look good there in some of those kits. Wouldn't it be great if Carplay had gone that way? Make the in-dash mount have the connectors for things like rear camera connections, steering wheel controls and make Carplay run as an app on the iPad or Mini screen.
If we didn't want to pop our iPads in and out of our car, this would drive the sales of either 2 tablets for "latest & greatest" or maybe make Carplay work just as fully with the more recent, but prior generation so we could "give" our old iPad to our cars. That would bite into the used iPad market as probably at least some people would want to hang on to their prior iPad to use this way. With fewer recent iPads for sale, maybe more new iPads would sell?
With this idea, I suspect it would be more natural to update to newer iPads than people will want to update to next generation Carplay units. Its kind of the same argument against an Apple Television vs.
TV. Buying the brains box more often tends to make more sense than buying the whole box.Yea Appleweek, that's just like searching for Washington area airports (something just about all other travel software can handle). Again
It's the same in the UK. Some of the London airports are not in London but are close to it.
Search for "Gatwick Airport London" and it looks for places in London with Gatwick Airport in their name (e.g. taxi places). Search for "London Gatwick Airport" or "Gatwick Airport" and you get the correct result. Heathrow and London City are the only two airports actually in London.
Same if you said "Washington Dulles Airport" it works, but "Dulles Airport Washington DC" is just wrong, the way the search is implemented it looks specifically for that search term within DC only. Washington DC has no airports of its own, all are in nearby states.
Also airport codes seem to work e.g. IAD, DCA, BWI for the Washington area airports. LHR, LGW, LTN, STN, LCY for the London area airports.
Apple Maps search is never going to match Google's searching ability, but in my experience if you ask it correctly you get what you want back.
So what do we know
- Entering the official name of the airport will work e.g. "Washington Dulles International Airport"
- Entering shorter forms of the name will work e.g. "Dulles Airport", "Washington Dulles", etc will work in most situations unless it's ambiguous.
- Entering the airport codes will work.
- What won't work is adding incorrect city/state information at the end of the airport name.
The ATV thing is the other way around. The ATV works forever with newer iPhones, but an old iPhone won't work fully with new ATVs. It's also like that with iPhone apps. I don't think there's ever been such thing as an iPhone being too new to work with something software-based.
HobeSoundDarryl
macrumors G5
Again, I appreciate the endless defense for Apple. And again, I'm a fellow Apple consumer trying to use his Apple tech just like anyone else here. I just don't fall into line that Apple is always right in all things and any crits must be redirected or refuted no matter what.
I also travel to other places like Cincinnati, flying into Cincinnati's airport which happens to NOT be in Cincinnati but across the river (and state line) in Hebron, Kentucky. Try "Cincinnati Airport" or even "Cincinnati Airport Cincinnati" and, instead of being "just wrong", Apple Maps can get that one right.
I also travel to New York City, often flying into Newark which is in New Jersey if anyone wouldn't know. But let's assume I don't know so I type in "Newark Airport, New York" and Apple maps also gets that "just wrong" one right too.
"Cincinnati Airport, Cincinnati": Apple gets it right
"Newark Airport, New York": Apple gets it right
"Dulles Airport, Washington DC": Apple points to a Taxi Cab company... but I- not Apple Maps- am "just wrong".
Thanks for the education on punching in just the airport name when I happen to know it.
Last edited:
EXACTLY. Daryl, when you search for incorrect locations you can't fault the system for not reading your mind. Garbage In, Garbage Out.
I actually prefer Apples more precise search than Google Maps. Anyone ever consider for a second that you're ACTUALLY in DC and you're searching for a Dulles Airport taxi service? The Apple Maps algorithm is more precise/accurate in giving me what I'm searching for: locations in DC that contain "Dulles" so I can find a taxi to get to the airport.
I prefer conformity and standards than a loose, wayward, and unpredictable search (Google) that tries to guess what I want and present it as fact. There are no "airports" in "Washington DC". Why is Google telling me there is????
HobeSoundDarryl
macrumors G5
Keywords "Airport" vs. "Taxi". If I wanted to find Dulles Taxi, I'd enter that. It's when I enter Dulles Airport and it points me to Dulles Taxi that I find issue. If it was the other way, I'd find issue too.
And for about the 10th time, this is just ONE example. Apple Maps took us to the wrong place a few nights ago too. It happens. None of them are flawless but I have high expectations of "just works" from Apple. I'd rather not have to rely on someone else's App when Apple has had a couple of years to get this one on par.
But why should they even try? With fans like you ready to jump on fellow Apple consumers, call them "idiot", and spin "user error" why should Apple try to do anything about their issues? They are perfection. It's anyone who doesn't agree that they are perfection that must be wrong... err, I mean an "idiot".
And for about the 10th time, this is just ONE example. Apple Maps took us to the wrong place a few nights ago too. It happens. None of them are flawless but I have high expectations of "just works" from Apple. I'd rather not have to rely on someone else's App when Apple has had a couple of years to get this one on par.
But why should they even try? With fans like you ready to jump on fellow Apple consumers, call them "idiot", and spin "user error" why should Apple try to do anything about their issues? They are perfection. It's anyone who doesn't agree that they are perfection that must be wrong... err, I mean an "idiot".
Last edited:
Don't get me confused, Apple does plenty things wrong IMO.
BUT in this case tho, I have to more blame the user over Apple Maps. For the 11th time, you keep repeating you searched for "Dulles Airport", but once again that's a lie because again you searched for "Dulles Airport" in "Washington DC". Accordingly Apple Maps gave you exactly what you asked for --- and in retrospect it was overly-accurate. Stop saying you searched for Dulles Airport when I think it's clear now to everyone here that it was your query which was inaccurate. If you had any doubt where Dulles Airport was legitimately located, you could have omit your guess "Washington DC" and Tada..... Apple woulda give u the right result.
And yes, I too have ridiculously high standards from Apple so I can understand your letdown feeling. But please continue to use Apple Maps, just search it right.
It should, but nothing in this world is perfect.
It's an illusion to think there will be no mistakes in maps, you know, things change continuously.
On my iphone, I open Apple Maps, click the search box and begin to type "Dulles Airport" I get to "Dulles" and I have an auto suggest of "Dulles International Airport" (Which is correct)
Same for Reagan Airport, I get to "Reagan Air" and "Ronald Reagan National Airport" is the number one suggestion (Which is correct)
I think your "gotcha" is that neither Dulles or Ronal Reagan are in Washington DC. they are both in Virginia. So if you ignore, or for some reason, don't get the auto suggestions and type "Dulles Airport Washington DC" You get the only business named "Dulles Airport" in DC, the taxi company.
If I type "Dulles Airport Washington DC" in Google maps, the first two suggestions are the Car Service and the Taxi. The third suggestion is the airport. However If I do not use the suggestions and just press enter, Google maps does take me to the airport.
Last edited:
Sorry to berate you here, but I wanted to offer an actual suggestion on how to get better results from Apple maps.
Use the auto suggest. I know that people frequently do no know the exact name and/or location of what they are looking for; but I find that if I'm paying attention to the auto suggestions as I type I will see the specific thing I'm looking for appear.
What Google does much better is intelligently autocorrect mis-located/mis-spelled searches, if I just type a search and press enter.
However I find that Apples Auto suggest is Better than Google's
I was looking for a restaurant near me (bay area CA) called "fresh Pixx" (pronounced "fresh Picks") I had no idea it was spelled "pixx" however with apple maps, I typed "fresh P" and the top suggestion is the correct address. (and all of the top suggestions are near me )
In Google maps, I get to "fresh" and the suggestions are all over the world (Cities in NY, MA, Australia...) I get all the way to "Fresh Pi" and the last suggestion is the right one.
however if I type "fresh Picks Dublin ca" Google will find it, but Apple will not.
So I think these sort of issues have more to do with apple's search algorithm. (I think it lacks a "Phonetic" spell checker, but I'm just guessing)
HobeSoundDarryl
macrumors G5
Again, I often feed Maps the added information I have rather than just some of the information as it's taught me it may guess very wrong with less information. For example, when I chose to try Reagan Airport, it pinned a tiny airport near Waco, Texas (Marlin Airport) rather than the intended one near Washington DC. Proof: https://www.dropbox.com/s/qefrdxglf5zvwbn/reaganyieldsmarlin.jpg?dl=0 (it needed "Ronald" to get it right) Presumably Reagan and Marlin are commonly confused?
Cincinnati Airport is not in Cincinnati (but in Kentucky). If you enter the "wrong" thing: "Cincinnati Airport Cincinnati", Maps will guess right. And I just can't imagine people trying to map that airport entering "Kentucky Airport" or "Cincinnati Airport Kentucky" to be technically correct.
NYC is generally thought of as having 3 major airports. 2 are in NY but one is in Newark, New Jersey. Be an "idiot" and enter "Newark Airport, New York" and Apple Maps will get it right too.
An "idiot" might see that as a search term consistency, maybe even get used to it.
Dulles, Reagan and Washington airports are presented as Washington DC area airports in Kayak, Orbitz, etc. Look them up and they present themselves as Washington Dulles or Ronald Reagan Washington International Airport (not Virginia Dulles International Airport or Ronald Reagan Virginia International Airport).
Yes, it's true that if I just enter "Dulles Airport", Apple Maps will pin the airport and not the cab company (but that same approach with "Reagan Airport" doesn't work). So I learned something from this thread. Now what about lots of other people that from booking via Kayak or Orbitz don't know (or notice) that Dulles or Reagan are actually in Virginia and Washington (airport) is in Maryland? What about lots of people who don't know what I learned in this thread and also try to enter it with added information than just the airport name because they've had enough experiences with entering less than they have and having it pin something like a tiny airport in Texas? What about the people who fly in and out of Cincinnati and Newark and those "wrong" entries work right in Maps who then visit D.C. and what has worked right before doesn't work right there?
Another thing I learned in this thread is that Apple keywords appear to be dominated by city & state over a keyword like "airport", which IMO, is the most important word of the 4 I entered. If I wanted "taxi", I'd have entered "taxi" instead of "airport".
Why do people use Maps? Probably much of it is to get to/from places like airports, hotels, etc when traveling. You'd think that a Maps app would give weight to such mainstream popular searches, meaning if one of the keywords is "airport", the user is probably wanting to locate an airport instead of a taxi business (or at least present both options so the user can choose airport instead of the taxi business). I have to believe people searching for "Dulles Airport Washington DC" are probably overwhelmingly trying to get to Dulles Airport vs. the cab company. It seems like the Maps database would overweight the airport and maybe even allow the "wrong" technical terms of "Washington DC" to work much like it does with "Cincinnati" or "New York" for those other airports.
But what do I know? As I've been hammered over and over that it's MY user error on a technicality (and everyone's ignoring how the wrong entries for Cincinnati and Newark work just fine in Maps), I tire of fighting the "Apple is always right" brigade. I'll simply point out again that Google Maps seems to be better at guessing that someone entering the term "airport" probably wants an airport instead of a cab company, even if that airport is not located within the DC boundaries. To hook this into the point of this thread, if I had a choice of Maps app for a $30K-$50K car, I wouldn't be thrilled to be somewhat locked in with Apple Maps "as is". More than once it's pinned a Marlin instead of a Reagan in my searches (and I'm quite the Apple guy myself). Hopefully it will get much better for even "idiot" searches by the time people are actually buying these cars... and relying on it.
Cincinnati Airport is not in Cincinnati (but in Kentucky). If you enter the "wrong" thing: "Cincinnati Airport Cincinnati", Maps will guess right. And I just can't imagine people trying to map that airport entering "Kentucky Airport" or "Cincinnati Airport Kentucky" to be technically correct.
NYC is generally thought of as having 3 major airports. 2 are in NY but one is in Newark, New Jersey. Be an "idiot" and enter "Newark Airport, New York" and Apple Maps will get it right too.
An "idiot" might see that as a search term consistency, maybe even get used to it.
Dulles, Reagan and Washington airports are presented as Washington DC area airports in Kayak, Orbitz, etc. Look them up and they present themselves as Washington Dulles or Ronald Reagan Washington International Airport (not Virginia Dulles International Airport or Ronald Reagan Virginia International Airport).
Yes, it's true that if I just enter "Dulles Airport", Apple Maps will pin the airport and not the cab company (but that same approach with "Reagan Airport" doesn't work). So I learned something from this thread. Now what about lots of other people that from booking via Kayak or Orbitz don't know (or notice) that Dulles or Reagan are actually in Virginia and Washington (airport) is in Maryland? What about lots of people who don't know what I learned in this thread and also try to enter it with added information than just the airport name because they've had enough experiences with entering less than they have and having it pin something like a tiny airport in Texas? What about the people who fly in and out of Cincinnati and Newark and those "wrong" entries work right in Maps who then visit D.C. and what has worked right before doesn't work right there?
Another thing I learned in this thread is that Apple keywords appear to be dominated by city & state over a keyword like "airport", which IMO, is the most important word of the 4 I entered. If I wanted "taxi", I'd have entered "taxi" instead of "airport".
Why do people use Maps? Probably much of it is to get to/from places like airports, hotels, etc when traveling. You'd think that a Maps app would give weight to such mainstream popular searches, meaning if one of the keywords is "airport", the user is probably wanting to locate an airport instead of a taxi business (or at least present both options so the user can choose airport instead of the taxi business). I have to believe people searching for "Dulles Airport Washington DC" are probably overwhelmingly trying to get to Dulles Airport vs. the cab company. It seems like the Maps database would overweight the airport and maybe even allow the "wrong" technical terms of "Washington DC" to work much like it does with "Cincinnati" or "New York" for those other airports.
But what do I know? As I've been hammered over and over that it's MY user error on a technicality (and everyone's ignoring how the wrong entries for Cincinnati and Newark work just fine in Maps), I tire of fighting the "Apple is always right" brigade. I'll simply point out again that Google Maps seems to be better at guessing that someone entering the term "airport" probably wants an airport instead of a cab company, even if that airport is not located within the DC boundaries. To hook this into the point of this thread, if I had a choice of Maps app for a $30K-$50K car, I wouldn't be thrilled to be somewhat locked in with Apple Maps "as is". More than once it's pinned a Marlin instead of a Reagan in my searches (and I'm quite the Apple guy myself). Hopefully it will get much better for even "idiot" searches by the time people are actually buying these cars... and relying on it.
Last edited:
this car looks nice. I've been drooling for a tesla since the model s was introduced but this might be a more viable option for the next 3 years until tesla prices come down a bit. Perfect for commuting to work and with the gas tank also works for long trips. Just wish it wasn't a chevy :/
any rumors on pricing?
Have they mentioned if it will have a remote starting option? starting it with an iPhone from my bedroom on a cold morning would be SWEET
any rumors on pricing?
Have they mentioned if it will have a remote starting option? starting it with an iPhone from my bedroom on a cold morning would be SWEET
My Volt had remote start via the OnStar iOS App, as does my current Fusion Energi via Ford's equivalent app. (In fact the Ford has schedules you can set to have the car preconditioned for specific times) It is indeed very nice to pre-condition the cabin while still plugged into 220v so as not to waste battery on the heater/air conditioning.
UPDATE:
As for pricing - the rumors over at http://gm-volt.com are all over the place but most believe it will stay right around the 2015 price whose base MSRP is just under $35k before any federal and/or local tax credit (many get the IRS $7,500 tax credit, bringing the base net cost to $27,500.)
Last edited:
awesome thank you!
----------
I have one more question, when you take it for long trips does the gas milage get an average between the electric and gas? For instance will your ACTUAL gas milage be high like in the 60's or 70's because it's using a combination of gas and electric? or will it just use electric at lower speeds and rely exclusively on to ~35mpg gas tank?
I live in DC and Apple Maps works fine around here. Including getting to Dulles Airport.
With CarPlay, and presumably Android Auto, there is rich functionality layer that sits between the user and the back end. When you use CarPlay, you are using a version of iOS which in turn talks to the car.
Much like the Apple Watch is more dumb than smart (and relies on the connectivity with the iPhone to do much of its work), CarPlay relies on the iPhone, not the embedded OS in the car, for it's high level functionality.The embedded system simply takes the handoff but is not the QB - interactivity, GUI, computation for navigation, making a phone call, accessing music etc...are handled by the top level OS - in this case, iOS.
The sea change, whether for Apple or Google, is beginning to move the core comm/entertainment functionality out of the car OS and into the users device of choice.
Nonetheless, it will be interesting to see how the next 12-18 months evolve for CarPlay.
Much like the Apple Watch is more dumb than smart (and relies on the connectivity with the iPhone to do much of its work), CarPlay relies on the iPhone, not the embedded OS in the car, for it's high level functionality.The embedded system simply takes the handoff but is not the QB - interactivity, GUI, computation for navigation, making a phone call, accessing music etc...are handled by the top level OS - in this case, iOS.
The sea change, whether for Apple or Google, is beginning to move the core comm/entertainment functionality out of the car OS and into the users device of choice.
Nonetheless, it will be interesting to see how the next 12-18 months evolve for CarPlay.
Since this is heading off topic, I've started a new thread and replied here: https://forums.macrumors.com/posts/20678118/
I'm in the UK. I misspelled Dulles Airport and searched for "Dules Airport" on an iPhone 6+ and it took me straight there, no problems.
To get to Dulles Airport you have to search for "Washington Dulles Airport"! It then points to the Airport.